<TITLE>The DXSpider Installation Manual v1.50: Linux Installation </TITLE>
<LINK HREF="installation-2.html" REL=next>
<TITLE>The DXSpider Installation Manual v1.50: Linux Installation </TITLE>
<LINK HREF="installation-2.html" REL=next>
</H2>
<P>This section describes the installation of DX Spider v1.50 on a
<A HREF="http://www.redhat.com">RedHat</A> Linux Distribution.
</H2>
<P>This section describes the installation of DX Spider v1.50 on a
<A HREF="http://www.redhat.com">RedHat</A> Linux Distribution.
<P>The crucial ingredient for all of this is
<A HREF="http://www.perl.org">Perl</A>. Earlier versions of
Spider required perl 5.004, however it is now <I>STRONGLY</I> recommended
that you use at least version 5.005_03 as this is the version being used
<P>The crucial ingredient for all of this is
<A HREF="http://www.perl.org">Perl</A>. Earlier versions of
Spider required perl 5.004, however it is now <I>STRONGLY</I> recommended
that you use at least version 5.005_03 as this is the version being used
-<A HREF="http://www.cpan.org/modules/by-module/">http://www.cpan.org/modules/bymodule/</A> , please note however that with later versions of perl, some of these
+<A HREF="http://www.cpan.org/modules/by-module/">http://www.cpan.org/modules/by-module/</A> , please note however that with later versions of perl, some of these
modules may be included with the distribution. Get the modules anyway and try
to install as below. If they complain, they are probably already a part of your
modules may be included with the distribution. Get the modules anyway and try
to install as below. If they complain, they are probably already a part of your
<LI>
<A HREF="http://www.cpan.org/modules/by-module/Date/TimeDate-1.10.tar.gz">TimeDate-1.10.tar.gz</A></LI>
<LI>
<A HREF="http://www.cpan.org/modules/by-module/IO/IO-1.20.tar.gz">IO-1.20.tar.gz (for perl 5.00403 and lower)</A></LI>
<LI>
<LI>
<A HREF="http://www.cpan.org/modules/by-module/Date/TimeDate-1.10.tar.gz">TimeDate-1.10.tar.gz</A></LI>
<LI>
<A HREF="http://www.cpan.org/modules/by-module/IO/IO-1.20.tar.gz">IO-1.20.tar.gz (for perl 5.00403 and lower)</A></LI>
<LI>
<P>Copy the CPAN modules listed above to a convenient place on your computer. One good
place would be /usr/local/packages, and the instructions which follow will assume that
<P>Copy the CPAN modules listed above to a convenient place on your computer. One good
place would be /usr/local/packages, and the instructions which follow will assume that
-that's where you have put them.
-<P>
-<P>Log in as 'root', and make sure you're at '/root' before you continue. Here are exactly the commands you must issue next: -
+that's where you have put them.</P>
+
+<P>Log in as 'root', and make sure you're at '/root' before you continue. Here are exactly the commands you must issue next: -</P>
-nearly are! Pay particular attention to the instructions of <EM>IO</EM>, above.
-<P>
-<P>
-<H2><A NAME="ss1.2">1.2 Preparation</A>
+nearly are! Pay particular attention to the instructions of <EM>IO</EM>, above.</P>
+
+
+<H2><A NAME="ss1.2">1.2</A> <A HREF="installation.html#toc1.2">Preparation</A>
</H2>
<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
</H2>
<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
<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,
<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,
<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
<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 ....
+should look something like this</P>
+<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>
<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
<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
<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
<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
-<P>
-<P>This is the sysop user callsign, normally your own.
-<P>
-<P><B>PLEASE USE CAPITAL LETTERS FOR CALLSIGNS</B>
-<P>
+</P>
+
+<P>This is the sysop user callsign, normally your own.</P>
+
+<P><B>PLEASE USE CAPITAL LETTERS FOR CALLSIGNS</B></P>
+
<P>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
<P>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><CODE>$myemail = "ianmaude\@btinternet.com";</CODE>
-<P>
+lines look a little odd. Take this line for example ....</P>
+<P><CODE>$myemail = "ianmaude\@btinternet.com";</CODE></P>
+
<P>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
<P>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
<EM>incoming</EM> connects at the moment. Before you can use it though it
has to be "made". CD to /spider/src and type <EM>make</EM>. You
should see the output on your screen and hopefully now have a small C program
<EM>incoming</EM> connects at the moment. Before you can use it though it
has to be "made". CD to /spider/src and type <EM>make</EM>. You
should see the output on your screen and hopefully now have a small C program
-called <EM>client</EM>. Leave it in this directory.
-<P>
-<P>
-<H2><A NAME="ss1.6">1.6 Starting up for the first time</A>
+called <EM>client</EM>. Leave it in this directory.</P>
+
+
+<H2><A NAME="ss1.6">1.6</A> <A HREF="installation.html#toc1.6">Starting up for the first time</A>
<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
<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
<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
<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