one up / back to JNOS 2.0


   rsync -a <path>

   * where <path> is a directory where you want the source code placed.

Compile (default - off the shelf)

   cd <path>



Compile (custom - using an original config.h)

   cd <path>


   *** edit config.h with your favorite editor ***

   make clean



Editing config.h

Do NOT replace config.h with one you may have had from a previous version of JNOS, bad idea ...
   (the only exception to this is if you are already running JNOS 2.0o)

Instead, edit config.h based on preferences you may have had in an older version of the config.h file. At one time you could replace it, but too much has changed. My original intent was to allow older versions going way back, but then I messed it up with the addition of fixed #defines that really should have gone into the makefile instead. I want to return to the original intent, but not today ...

How the configure script works

The configure script will generate a new config.h file if one is not present. It does this by simply copying over the config.h.default file. If the configure script sees an existing config.h file, it will leave it alone, so when you do software updates it does not get clobbered. But the script is run a second time to ensure any makefile options are in sync with changes to config.h, so basically IF you edit config.h, you should do a make clean and run ./configure again.


These instructions sort of imply you already have a JNOS runtime area from previous experience, so assuming your JNOS runtime area is under the /jnos directory, you would run the following commands.

   cd <path>

   cp -rp jnos jnospwmgr usage /jnos

* Read the next section if you don't have a JNOS runtime area setup yet ...

So what about this JNOS runtime area ?

If you are new to JNOS then you need to first create the runtime area before you install the files in the previous section. Tradition has been to use /jnos as the directory name, but it can be whatever you have in mind. Just run the command below, before installing executables and usage files from previous section.

   mkdir /jnos

When you run JNOS for the first time, it will create all the necessary directories it needs to support the various services and operations it is capable of. So for instance, you could run the commands below.

   cd /jnos


If you like, bring up another terminal to monitor the main JNOS logfile, for instance:

   tail -f /jnos/logs/16May23

But all this really does is give you an empty JNOS instance with no interfaces, no radio ports, and no services. JNOS looks for a configuration file called 'autoexec.nos' when it starts up. This file is used to setup radio ports, network interfaces, services for TCP/IP, Node, BBS, APRS, and more.

So now things will get interesting. You will get frustrated. This can get quite technical at times. You may have to do a fair amount of reading. You may have to search online for examples. You could copy over an autoexec.nos file you got from a fellow ham or colleague and taylor it to your needs, but make sure you use your own callsign, set your own IP assignments. You will need to setup networking between linux and jnos, unless you want a pure standalone system. There is more, but this is all out of the scope of this section. There is a JNOS runtime installer I wrote some time ago. It is quite simplistic, and might be helpful (or not). You can click here for more information about it. It needs work ...

I will provide an example of my live autoexec.nos as well as how to setup linux to jnos networking
   (just give me a week or so to get this site organized, thanks for your patience)

* this page was last updated on Friday, May 3, 2024