Greetings JNOS users,

I present to you JNOS 2.0f

1) There is NO incremental update from previous versions, too much
   has changed, and a mass compile is required anyways.

   Put the compressed tar file into an empty directory, then from
   within that directory, issue the following commands :

    gunzip jnos20f.tar.gz
    tar xvf jnos20f.tar
    cd jnos2

2) Before you compile you will need a config.h file. If you have your
   own from a previous version, then copy it over, ie :

    cp <path to your config.h> config.h

   BUT perhaps do a 'diff' between yours and the official development
   copy (see below) to see what new #define's you might be missing out
   on. Probably they are not a big deal, but you should know anyways.

   If you do not have your own config.h and are doing this for the first
   time, then copy my development version over using the following cmd :

    cp config.dev.h config.h

   If desired, now edit the config.h file to suit your preferences.

3) To compile and link JNOS, just enter the 'make' command.

   Please note that warnings will happen, I know about them already, so
   please ignore them. There is NO need to run 'make depend', even though
   it does work now, I never use it, and don't see the need right now.

4) That's it, if all goes well, you should have a new 'jnos' binary.

5) Why is 'jnos' binary so large AND what to do about JNOS crashing !

   Note that my makefile has debugging turned on, so any 'jnos' binary
   you compile will be large (because it contains debuggin info). If you
   are not at all interested in debugging, then you can reduce the size
   of the 'jnos' binary using the following command :

    strip jnos

   which will strip out the debugging information and symbol table.

   If you ARE interested in helping me fix bugs, then I encourage you to
   run the GDB debugger that comes with most linux distros, AND make sure
   you do NOT strip the 'jnos' binary, since it contains important info for
   the debugger to use when a crash occurs.

   Using GDB is easy. With JNOS running already, find out it's pid, using
   the linux command, 'ps -ef | grep jnos'. Once you know what the pid is,
   then run the gdb debugger something like this :

    gdb -p pid

   GDB will load, JNOS will hang temporarily, and GDB will suddenly give
   you a prompt. Enter the command, 'continue', at the prompt, and JNOS
   will continue to run again.

   When a crash occurs, GDB will break out to the prompt again, and JNOS
   will hang. Take a screen shot of what GDB printed out, then type in
   the command, 'back full', at the GDB prompt, and note the info that
   appears. Please send all of that information to me, with a brief
   explanation of what might have been going on at the time.

   If you have JNOS logging in effect, please send me the log file at
   the time of the crash if you don't mind. Logs are under /jnos/logs/
   directory (by default).

21Dec2007
Maiko Langelaar / VE4KLM
JNOS 2.0f released