<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual : Installation (Original version by Iain Phillips, G0RDI)</TITLE>
+ <TITLE>The DXSpider Installation and Administration Manual : Installation (Original version by Iain Philipps, G0RDI)</TITLE>
<LINK HREF="adminmanual-2.html" REL=next>
<LINK HREF="adminmanual.html#toc1" REL=contents>
+<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
</HEAD>
<BODY>
<A HREF="adminmanual-2.html">Next</A>
Previous
<A HREF="adminmanual.html#toc1">Contents</A>
<HR>
-<H2><A NAME="s1">1. Installation (Original version by Iain Phillips, G0RDI)</A></H2>
+<H2><A NAME="s1">1. Installation (Original version by Iain Philipps, G0RDI)</A></H2>
-<P>Last modified: 10 December 2000 by Ian Maude, G0VGS
-<P>
<H2><A NAME="ss1.1">1.1 Introduction</A>
</H2>
-<P>This section describes the installation of DX Spider v1.35 on a
-<A HREF="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
-<A HREF="http://www.dxcluster.org">DXSpider</A>
-website.
+<P>This section describes the installation of DX Spider v1.46 on a
+<A HREF="http://www.redhat.com">RedHat</A> 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.
<P>
-<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>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
-<A HREF="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
-<A HREF="http://www.redhat.com">RedHat 5.1</A> comes
-with 5.004. <EM>Be Warned</EM>, earlier versions of
-<A HREF="http://www.redhat.com">RedHat</A> <B>do not</B>
-come with 5.004 as standard, you need to
-<A HREF="ftp://upgrade.redhat.com">upgrade</A><P>
-<P>In addition to the standard Red Hat distribution you will require the following
-<A HREF="http://www.cpan.org/CPAN.html">CPAN</A> modules: -
+<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
+in the development of Spider.
+<P>
+<P>In addition to the standard Red Hat distribution you will require the
+following modules from
+<A HREF="http://www.cpan.org/CPAN.html">http://www.cpan.org/CPAN.html</A> ...
<P>
<P>
<UL>
<LI> MD5-1.7.tar.gz</LI>
<LI> Data-Dumper-2.10.tar.gz</LI>
-<LI> FreezeThaw-0.3.tar.gz</LI>
-<LI> MLDBM-2.00.tar.gz</LI>
<LI> TimeDate-1.08.tar.gz</LI>
<LI> IO-1.20.tar.gz</LI>
<LI> Net-Telnet-3.02.tar.gz</LI>
</UL>
<P>
<P>
-<P><EM>Do</EM> get the latest versions of these packages and install them but use the above list as the earliest
-versions usable.
+<P><EM>Do</EM> get the latest versions of these packages and install them
+but use the above list as the earliest versions usable.
<P>
<H2><A NAME="ss1.2">1.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 1.35 for this section but of course you would use the latest version.
+<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.46 for this section but of course you would use the latest version.
<P>
-<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>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>
<H2><A NAME="ss1.3">1.3 Installing the software</A>
</H2>
-<P>Now to unpack the DX Spider distribution, set symbolic links and group permissions. Copy the tarball to /home/sysop
-and do the following.
+<P>Now to unpack the DX Spider distribution, set symbolic links and group
+permissions. Copy the tarball to /home/sysop and do the following.
<P>
<BLOCKQUOTE><CODE>
<PRE>
# 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)
</PRE>
</CODE></BLOCKQUOTE>
-<P>If you do not have the command <EM>groupadd</EM> available to you simply add a line in /etc/group by hand.
+<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>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 ....
</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>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>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>
<H2><A NAME="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>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>
<BLOCKQUOTE><CODE>
<PRE>
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<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>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><CODE>$myemail = "ianmaude\@btinternet.com";</CODE>
<P>
-<P>There appears to be an extra slash in there. However this has to be there for the file to work so leave it in.
+<P>There appears to be an extra slash in there. However this has to be there
+for the file to work so leave it in.
<P>
<P><B>PLEASE USE CAPITAL LETTERS FOR CALLSIGNS</B>
<P>
-<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>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!
<P>
<P>Save the new file and change directory to ../perl ....
<P>
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<P>Now type the following command which creates the basic user file with you as the sysop.
+<P>Now type the following command which creates the basic user file with you as
+the sysop.
<P>
<BLOCKQUOTE><CODE>
<PRE>
-$ create_sysop.pl
+$ ./create_sysop.pl
</PRE>
</CODE></BLOCKQUOTE>
<P>
<H2><A NAME="ss1.5">1.5 Starting up for the first time</A>
</H2>
-<P>We can now bring spider up for the first time and see if all is well or not! It should look something like this ...
+<P>We can now bring spider up for the first time and see if all is well or not!
+It should look something like this ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-$ 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 ...
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<P>If all is well then login on another term or console as <EM>sysop</EM> and cd to /spider/perl. Now issue the
-following command ...
+<P>If all is well then login on another term or console as <EM>sysop</EM> and
+cd to /spider/src. Now issue the following command ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-$ client.pl
+$ ./client
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<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
was set as GB7MBC. You should therefore see this when you login ....
<P>
<BLOCKQUOTE><CODE>
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>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>
<P>
<P>and both the cluster and the client should return to Linux prompts.
<P>
+<H2><A NAME="ss1.6">1.6 The Client program</A>
+</H2>
+
+<P>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
+<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>
<HR>
<A HREF="adminmanual-2.html">Next</A>
Previous
projects / spider.git / blobdiff