Linux - Jnos Setup and Config HOW-TOBy John Martin KF8KK Compiling the latest Jnos
|
|
| Compiling your copy of Jnos isn't as
hard as one might think. It's a process that you really need to
become accustomed to in order to enable all the functions that you need
and to keep your system up to date.
The primary reason for installing Slackware 10 on the machine is to make the system more in keeping with that used by Maiko VE4KLM, and such, to allow us to keep up with the updates without having to deal with a myriad of complications. Because of our setup, the instructions for compiling Jnos that Maiko provides works in our case, without modification.
|
|
| From the CDrom with Jnos
on it that we created earlier you should also have a copy of the latest
Jnos source code for Linux.
I like to copy the source code downloads to a directory I have created called /jnos/linux/source. Copy the new Jnos source (at the time of this
writing it is Jnos2.0e) into this directory. At this point, simply follow Maiko's directions which will be as follows: From the /jnos/linux/source directory: Then: And finally 'cd jnos2' to change into the jnos2 directory where all the source files exist.
|
|
| The file that determines our particular
jnos options is called 'config.h'. Maiko supplies his version as
the file config.h.ve4klm. We need to copy this to just plain 'config.h'
and do so with the following command:
cp config.h.ve4klm config.h While we could leave the config.h unedited and compile Jnos as it is (providing a copy of the newest version), the jnos produced might not have all the features enabled (or too many enabled) that we need. You can edit config.h in a text editor as you do with the autoexec.nos and other files in order to switch various portions of jnos on or off. When you are done with your changes to config.h issue the following commands: make clean Once 'make' starts running it will take a few minutes to compile jnos. This could be near 15-20 minutes if you are running a slower computer. You will see many lines of text scroll across the screen-- and a few 'warnings'. If the compiler (the gcc compiler is called when you issue the 'make' command) finishes without errors you will have a fresh new file called 'jnos' in the directory. You must now copy this new jnos to the main jnos directory where the program is run from. This can be done with the command: cp jnos /jnos/
|
|
| At this point you should 'cd
/jnos' back to the /jnos directory and then
start Jnos with 'startnos' and note that the new version number appears
on the banner as it's starting up.
If you turned on the converse server in the config.h file before you compiled you should find that those loading errors related to converse are no longer showing up.
|
|
| As an aside, whenever I compile a new
version of jnos, I name it with the version number 'jnos20e' instead of
just 'jnos'.
You can do this if you wish, but you MUST make sure to edit the /usr/sbin/startnos file so that it starts up the new version when you issue the 'startnos' command.
|
|
| While this is the end of the Linux Jnos installationg pages at the moment, more will be coming soon. As I promised earlier, Jnos installation for DOS will eventually appear here also. Thanks for your patience 73 KF8KK 5/30/06 | |
| Introduction Obtaining The Software Installing a DOS partition Slackware Installation A Slackware Installation B Selecting Packages Configuring Linux Linux Network Configuration Starting Slackware Linux Basic Jnos Installation Jnos Localization & Config Starting Jnos Compiling Jnos |
|