<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.6.2">
</HEAD>
<BODY>
Hi again,<BR>
<BR>
I started this thread thinking I had a niche issue with the wl2k interface.<BR>
I do...<BR>
Then the discussion turned into something else I'm up to.<BR>
I have an opportunity for those of us who want a training manual --> write it.<BR>
<BR>
I've begun creating what I call an "Owners Manual". My task is to tie together loosely related stuff.<BR>
I considered the wiki approach, but ended up with the pdf approach so I could "take it with me".<BR>
The SCS manual comes as a pdf, so why not jnos too?<BR>
<BR>
In any case, it is now 140 pages with a basic structure and no frills like the configuration we have discussed here.<BR>
The manual lacks this tutorial for configuring and using what Andre called his "a form of" forwarding in network terms along with jnos terms so the whole issue is tied together with a ribbon. And then do it several times for several ways of assembling jnos into a network. One subject I am headed toward is Maiko's configuration that talks to wl2k.<BR>
<BR>
I'll post the manual soon as I have permission from original authors to include their documents in my collection.<BR>
<BR>
My approach so far has been to collect web based suff about jnos, try it out on my installation, then include it if it works for me. The major topics thus far are "BBS user", "administrator user", "system configurator", "compile it". You see I'm doing the same learning thing as I go that you are Tim.<BR>
<BR>
So here is my take on the manual issue:<BR>
If anyone has material as a result of installing jnos in a novel way, send it to me for inclusion into the Owners Manual. I'll take on the task of presentation if it is not already done. What material? descriptive text / autoexec.nos / domain.txt / help / ...<BR>
<BR>
Oh yes - I was going to redistribute help files too. For example - the first thing I needed to do was turn the names into lower case for Linux / a tedium no one needs to replicate. The second thing was to personalize certain entries as a subject in the Manual.<BR>
<BR>
There is a LOT of material relative to nos presently on the web. My work might re-publish a couple percent of it tailored toward the newer developments such as Maikos work with Jnos, Andres work as user if he wants to share it, ampr.net, interface with others like wl2k. I doubt nos will reemerge as a major force in ham networking, but my objective is to tie together current material as one perspective for those who want to spin nos into something (else ?).<BR>
<BR>
So there it is - another nos ticket item. If it is to be meaningful it could use help of others both in material and review prior to publishing. If you wait for me you will wait longer and have less in the product...<BR>
<BR>
Anyone else want to be part of this?<BR>
<BR>
Oh, as a parting thought: I'm headed toward two configurations for my jnos platforms. The first is Internet connected as is the conventional ampr.net configuration for use at home. The second is a mobile configuration that fosters localized networking over multiple VHF/UHF RF paths - perhaps with a HF long path to remote ampr.net or wl2k or something else. I am seeking out those things that extend IP over RF, and those things that enable a small localized group to quickly form-work together-tap Internet resources-disband as the job completes...<BR>
<BR>
On Fri, 2006-02-24 at 12:39 +0100, Torsten Harenberg wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Dear all,</FONT>
<FONT COLOR="#000000">Tim Gorman wrote:</FONT>
<FONT COLOR="#000000">> I'm still learning all this and the going is slow. </FONT>>SNIP<
</PRE>
</BLOCKQUOTE>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<BR>
73<BR>
de Skip k8rra k<BR>
<BR>
<BR>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>