This is a patch, mostly bug fixes, some diagnostic stuff.

WARNING : this is for LINUX distributions only !

WARNING : only apply this if you are running JNOS 2.0d, nothing earlier !

The archive (source) file is called j20d1p.tar.gz. IMPORTANT - do NOT put it
in the 'jnos2' directory ! Instead put it at the same level as the 'jnos2'
directory, then run the following commands :

    gunzip j20d1p.tar.gz
    tar xvf j20d1p.tar
    cd jnos2

NOTE : I have included my 'config.h' - named config.dev.h - for reference
       purposes. That is what I use on my development system (linux).

Make sure you read the release history, especially the part about INP3 ...

If you have INP3 defined in your config.h, then you really should undefine
it, and then do a 'make clean', followed by a 'make'.

If you do NOT have INP3 defined, then all you should have to do is 'make'.

--- after the make is done ---

1) 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.

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

3) 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, 'where' or 'back', 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).

03Feb2006 - Maiko Langelaar / VE4KLM

* JNOS 2.0d1 patch released