Last modified: 10 December 2000 by Ian Maude, G0VGS -
This section describes the installation of DX Spider v1.35 on a -RedHat -Linux Distribution. I do not intend to try and cover the installation of Linux or the setup of the AX25 utilities. -If you need help on this then read Iains original HOWTO on the -DXSpider -website. +
This section describes the installation of DX Spider v1.46 on a +RedHat Linux Distribution. +Wherever possible I will try to include differences for other distributions. +I do not intend to try and cover the installation of Linux or the setup +of the AX25 utilities. If you need help on this then read Iains original +installation guide that comes with the Spider distribution.
-
I am assuming a general knowledge of Linux and its commands. You should know how to use tar and how to edit -files using your favourite editor. +
I am assuming a general knowledge of Linux and its commands. You should +know how to use tar and how to edit files using your favourite editor.
The crucial ingredient for all of this is -Perl 5.004.Now I know Perl 5.005 -is out and this will almost certainly work with it, but -RedHat 5.1 comes -with 5.004. Be Warned, earlier versions of -RedHat do not -come with 5.004 as standard, you need to -upgrade
-
In addition to the standard Red Hat distribution you will require the following -CPAN modules: - +Perl. Earlier versions of +Spider required perl 5.004, however it is now STRONGLY recommended +that you use at least version 5.005_03 as this is the version being used +in the development of Spider. +
+
In addition to the standard Red Hat distribution you will require the +following modules from +http://www.cpan.org/CPAN.html ...
-
Do get the latest versions of these packages and install them but use the above list as the earliest -versions usable. +
Do get the latest versions of these packages and install them +but use the above list as the earliest versions usable.
I will assume that you have already downloaded the latest tarball of the DXSpider software and are ready to -install it. I am assuming version 1.35 for this section but of course you would use the latest version. +
I will assume that you have already downloaded the latest tarball of +the DXSpider software and are ready to install it. I am assuming version +1.46 for this section but of course you would use the latest version.
-
Login as root and create a user to run the cluster under. UNDER NO CIRCUMSTANCES USE ROOT AS THIS USER!. -I am going to use the name sysop. You can call it anything you wish. Depending on your security -requirements you may wish to use an existing user, however this is your own choice. +
Login as root and create a user to run the cluster under. UNDER +NO CIRCUMSTANCES USE ROOT AS THIS USER!. I am going to use +the name sysop. You can call it anything you wish. Depending +on your security requirements you may wish to use an existing user, +however this is your own choice.
@@ -89,26 +87,28 @@ passwd: all authentication tokens updated successfully
1.3 Installing the software
-Now to unpack the DX Spider distribution, set symbolic links and group permissions. Copy the tarball to /home/sysop
-and do the following.
+
Now to unpack the DX Spider distribution, set symbolic links and group
+permissions. Copy the tarball to /home/sysop and do the following.
# cd ~sysop
-# tar xvfz spider-1.35.tar.gz
+# tar xvfz spider-1.46.tar.gz
# ln -s ~sysop/spider /spider
# groupadd -g 251 spider (or another number)
-If you do not have the command groupadd available to you simply add a line in /etc/group by hand.
+
If you do not have the command groupadd available to you simply
+add a line in /etc/group by hand.
# vi /etc/group (or your favorite editor)
-You also need to add some others to the group, including your own callsign (this will be used as an alias) and root.
-The finished line in /etc/group should look something like this
+
You also need to add some others to the group, including your own callsign
+(this will be used as an alias) and root. The finished line in /etc/group
+should look something like this
spider:x:251:sysop,g0vgs,root
The next step is to set the permissions on the Spider directory tree and files ....
@@ -121,11 +121,13 @@ The finished line in /etc/group should look something like this
-
This last step allows various users of the group spider to have write access to all the directories. This -is not really needed just yet but will be useful when web interfaces start to appear. +
This last step allows various users of the group spider to have +write access to all the directories. This is not really needed just yet +but will be useful when web interfaces start to appear.
-
Finally, you need to fix the permissions on the ax25_call and netrom_call programs. Check where they are with the -locate command and alter the permissions with the chmod command like this .. +
Finally, you need to fix the permissions on the ax25_call and netrom_call +programs. Check where they are with the locate command and alter +the permissions with the chmod command like this ..
@@ -137,8 +139,8 @@ is not really needed just yet but will be useful when web interfaces start to ap
1.4 Setting callsigns etc
-Now login to your machine as the user you created earlier. In my case that user is called sysop. Once
-logged in, issue the following commands ....
+
Now login to your machine as the user you created earlier. In my case that
+user is called sysop. Once logged in, issue the following commands ....
@@ -151,19 +153,23 @@ $ vi DXVars.pm (or your favourite editor)
-
Using the distributed DXVars.pm as a a template, set your cluster callsign, sysop callsign and other user info to
-suit your own environment. Note that this a perl file which will be parsed and executed as part of the cluster. If
-you get it wrong then perl will complain when you start the cluster process. It is important only to alter the text
-of any section. Some of the lines look a little odd. Take this line for example ....
+
Using the distributed DXVars.pm as a a template, set your cluster callsign,
+sysop callsign and other user info to suit your own environment. Note that
+this a perl file which will be parsed and executed as part of the cluster. If
+you get it wrong then perl will complain when you start the cluster process.
+It is important only to alter the text of any section. Some of the lines look
+a little odd. Take this line for example ....
$myemail = "ianmaude\@btinternet.com";
-
There appears to be an extra slash in there. However this has to be there for the file to work so leave it in.
+
There appears to be an extra slash in there. However this has to be there
+for the file to work so leave it in.
PLEASE USE CAPITAL LETTERS FOR CALLSIGNS
-
DON'T alter the DXVars.pm (or any other file) in /spider/perl, they are overwritten with every release. Any files or
-commands you place in /spider/local or /spider/local_cmd will automagically be used in preference to the ones in
-/spider/perl EVEN while the cluster is running!
+
DON'T alter any file in /spider/perl, they are overwritten with every
+release. Any files or commands you place in /spider/local or /spider/local_cmd
+will automagically be used in preference to the ones in /spider/perl EVEN
+while the cluster is running!
Save the new file and change directory to ../perl ....
@@ -173,23 +179,25 @@ $ cd ../perl
-
Now type the following command which creates the basic user file with you as the sysop. +
Now type the following command which creates the basic user file with you as +the sysop.
-$ create_sysop.pl
+$ ./create_sysop.pl
We can now bring spider up for the first time and see if all is well or not! It should look something like this ... +
We can now bring spider up for the first time and see if all is well or not! +It should look something like this ...
-$ cluster.pl
-DXSpider DX Cluster Version 1.35
+$ ./cluster.pl
+DXSpider DX Cluster Version 1.46
Copyright (c) 1998 Dirk Koopman G1TLH
loading prefixes ...
loading band data ...
@@ -201,17 +209,18 @@ orft we jolly well go ...
-
If all is well then login on another term or console as sysop and cd to /spider/perl. Now issue the -following command ... +
If all is well then login on another term or console as sysop and +cd to /spider/src. Now issue the following command ...
-$ client.pl
+$ ./client
-
This should log you into the cluster as the sysop under the alias callsign we set earlier. In this case the callsign -is G0VGS. The cluster callsign is set in the DXVars.pm file in /spider/local. In this case we will assume that this +
This should log you into the cluster as the sysop under the alias callsign we +set earlier. In this case the callsign is G0VGS. The cluster callsign is set +in the DXVars.pm file in /spider/local. In this case we will assume that this was set as GB7MBC. You should therefore see this when you login ....
@@ -219,8 +228,9 @@ was set as GB7MBC. You should therefore see this when you login ....
G0VGS de GB7MBC 19-Nov-1999 2150Z >
If you do, congratulations! If not, look over the instructions again, you have probably missed something out. You -can shut spider down again with the command .... +
If you do, congratulations! If not, look over the instructions again, you +have probably missed something out. You can shut spider down again with the +command ....
@@ -230,6 +240,18 @@ shutdown
and both the cluster and the client should return to Linux prompts.
+
1.6 The Client program
+
+
+In earlier versions of Spider, all the processes were Perl scripts. This
+was fine but with a lot of users your computer memory would soon be used up.
+To combat this a new client was written in "C". This client only works for
+incoming connects at the moment. Before you can use it though it
+has to be "made". CD to /spider/src and type make. You
+should see the output on your screen and hopefully now have a small C program
+called client. Leave it in this directory.
+
+
Next
Previous