Home • Download / Compile / Install

The all important Release History

  • PLEASE read the release history before going any further.
  • Tar files of current and past releases

    jnos 2.0m.5C (update)Nov 1, 2020tar.gztgz
    jnos 2.0m.4 (current)Aug 20, 2020tar.gztgz
    jnos 2.0m (previous)Nov 27, 2019tar.gztgz
    jnos 2.0k.3B (old)Aug 10, 2019tar.gztgz

    My Rsync Repository

    Use the rsync command to download the latest source code :

          rsync -a www.langelaar.net::jnos2 <path>

      where <path> is the directory you want the source put (can be empty or existing source)

    If you are running 2.0m or later, then you can run rsync at any time to get updates.

       NOTE : if you have an existing config.h file, it will NOT be overwritten.

    My Github Site

      Check out https://github.com/mlangelaar/jnos2 - patched to 2.0m.4 already.

    The config.h header file and it's default

    Pay special attention to how the config.h file is handled. The rsync service has been around since middle of May 2010, and since it came out I have always suggested to people that if your original source is from before that time, you should really just start with a new empty directory, with your original config.h as the only file, then run rsync to get the latest source. BUT ...

    Lots has changed since, so if your source is even older then the current 2.0m release, you should probably start with an empty directory. You can probably get away with using your existing config.h, or you can let the './configure' script put in the default config.h for you (it simply copies over the config.h.default), and then edit the newly placed config.h instead, using your original config.h to figure out which directives to #define or #undef - whatever works best for you. The important thing is run a diff between your config.h and config.h.default to see what features you might be missing out on. I suppose one could write a utility program to do just that, and I should really reorganize the way all the new options appear in the 'config.h.default' file.

    The original 1.11f (linux) config.h should work too, if you decide to migrate from that era ...

    Compiling and Installing Binaries

    As of version 2.0m you compile as follows :

      make clean
      cp -rp jnos jnospwmgr usage /jnos

    It is recommended to do the make clean, to clear out old objects, libraries, and binaries.
     (assumption is made above that you already have a /jnos directory installed)

    If you forget to run ./configure after a fresh install or make clean, then 'make' will tell you to run it :)

    Installing JNOS

    JNOS can be complicated, install can be simple, configuration can be maddening, it's quite technical :]

    There are many websites and wikis out there to help one setup JNOS, but for starters ...

       you 'could' run the JNOS 2.0 installer to create a basic configuration ...

    * last updated on Sunday, November 1, 2020