<P>This section describes the installation of DX Spider v1.35 on a
<AHREF="http://www.redhat.com">RedHat</A> 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
<P>I am assuming a general knowledge of Linux and its commands. You should know how to use <EM>tar</EM> and how to edit files using your favourite editor.
<P>
<P>The crucial ingredient for all of this is
<AHREF="http://www.perl.org">Perl 5.004</A>.Now I know Perl 5.005 is out and this will almost certainly work with it, but
<AHREF="http://www.redhat.com">RedHat 5.1</A> comes with 5.004. <EM>Be Warned</EM>, earlier versions of
<AHREF="http://www.redhat.com">RedHat</A><B>do not</B> come with 5.004 as standard, you need to
<AHREF="ftp://upgrade.redhat.com">upgrade</A><P>
<P>In addition to the standard Red Hat distribution you will require the following
<P>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.
<P>Login as root and create a user to run the cluster under. <B><I>UNDER NO CIRCUMSTANCES USE ROOT AS THIS USER!</I></B>. I am going to use the name <EM>sysop</EM>. 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.
<P>
<P>
<BLOCKQUOTE><CODE>
<PRE>
# adduser -m sysop
</PRE>
</CODE></BLOCKQUOTE>
<P>
<P>Now set a password for the user ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
# passwd sysop
# New UNIX password:
# Retype new UNIX password:
passwd: all authentication tokens updated successfully
</PRE>
</CODE></BLOCKQUOTE>
<P>
<H2><ANAME="ss1.3">1.3 Installing the software</A>
<P>If you do not have the command <EM>groupadd</EM> available to you simply add a line in /etc/group by hand.
<P>
<BLOCKQUOTE><CODE>
<PRE>
# vi /etc/group (or your favorite editor)
</PRE>
</CODE></BLOCKQUOTE>
<P>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
<P><CODE>spider:x:251:sysop,g0vgs,root</CODE>
<P>
<P>The next step is to set the permissions on the Spider directory tree and files ....
<P>
<BLOCKQUOTE><CODE>
<PRE>
# chown -R sysop.spider spider
# find . -type d -exec chmod 2775 {} \;
# find . -type f -exec chmod 775 {} \;
</PRE>
</CODE></BLOCKQUOTE>
<P>
<P>This last step allows various users of the group <EM>spider</EM> 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.
<P>
<P>Finally, you need to fix the permissions on the ax25_call and netrom_call programs. Check where they are with the <EM>locate</EM> command and alter the permissions with the <EM>chmod</EM> command like this ..
<P>
<BLOCKQUOTE><CODE>
<PRE>
# chown root ax25_call netrom_call
# chmod 4775 ax25_call netrom_call
</PRE>
</CODE></BLOCKQUOTE>
<P>
<H2><ANAME="ss1.4">1.4 Setting callsigns etc</A>
</H2>
<P>Now login to your machine as the user you created earlier. In my case that user is called <EM>sysop</EM>. Once logged in, issue the following commands ....
<P>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 ....
<P>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!
<P>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 ....
<P>
<BLOCKQUOTE><CODE>
<PRE>
G0VGS de GB7MBC 19-Nov-1999 2150Z >
</PRE>
</CODE></BLOCKQUOTE>
<P>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 ....
<P>
<BLOCKQUOTE><CODE>
<PRE>
shutdown
</PRE>
</CODE></BLOCKQUOTE>
<P>
<P>and both the cluster and the client should return to Linux prompts.