1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
4 <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
5 <TITLE>The DXSpider Installation Manual v1.49: Linux Installation </TITLE>
6 <LINK HREF="installation-2.html" REL=next>
8 <LINK HREF="installation.html#toc1" REL=contents>
9 <link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
12 <A HREF="installation-2.html">Next</A>
14 <A HREF="installation.html#toc1">Contents</A>
16 <H2><A NAME="s1">1. Linux Installation </A></H2>
18 <H2><A NAME="ss1.1">1.1 Introduction</A>
21 <P>This section describes the installation of DX Spider v1.47 on a
22 <A HREF="http://www.redhat.com">RedHat</A> Linux Distribution.
23 Wherever possible I will try to include differences for other distributions.
24 I do not intend to try and cover the installation of Linux or the setup
25 of the AX25 utilities. If you need help on this then read Iains original
26 installation guide that comes with the Spider distribution.
28 <P>I am assuming a general knowledge of Linux and its commands. You should
29 know how to use <EM>tar</EM> and how to edit files using your favourite editor.
31 <P>The crucial ingredient for all of this is
32 <A HREF="http://www.perl.org">Perl</A>. Earlier versions of
33 Spider required perl 5.004, however it is now <I>STRONGLY</I> recommended
34 that you use at least version 5.005_03 as this is the version being used
35 in the development of Spider.
37 <P>In addition to the standard Red Hat distribution you will require the
38 following modules from
39 <A HREF="http://www.cpan.org/CPAN.html">http://www.cpan.org/CPAN.html</A> , please note however that with later versions of perl, some of these
40 modules may be included with the distribution. Get the modules anyway and try
41 to install as below. If they complain, they are probably already a part of your
47 <A HREF="http://www.cpan.org/modules/by-module/Data/Data-Dumper-2.10.tar.gz">Data-Dumper-2.10.tar.gz</A></LI>
49 <A HREF="http://www.cpan.org/modules/by-module/Date/TimeDate-1.10.tar.gz">TimeDate-1.10.tar.gz</A></LI>
51 <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>
53 <A HREF="http://www.cpan.org/modules/by-module/Net/Net-Telnet-3.02.tar.gz">Net-Telnet-3.02.tar.gz</A></LI>
55 <A HREF="http://www.cpan.org/modules/by-module/Curses/Curses-1.06.tar.gz">Curses-1.06.tar.gz</A></LI>
57 <A HREF="http://www.cpan.org/modules/by-module/Time/Time-HiRes-01.20.tar.gz">Time-HiRes-01.20.tar.gz</A></LI>
60 <P>Copy the CPAN modules listed above to a convenient place on your computer. One good
61 place would be /usr/local/packages, and the instructions which follow will assume that
62 that's where you have put them.
64 <P>Log in as 'root', and make sure you're at '/root' before you continue. Here are exactly the commands you must issue next: -
67 # tar xvfz /usr/local/packages/Data-Dumper-2.10.tar.gz
74 # tar xvfz /usr/local/packages/TimeDate-1.10.tar.gz
81 # tar xvfz /usr/local/packages/IO-1.20.tar.gz
85 # make install UNINST=1
88 # tar xvfz /usr/local/packages/Net-Telnet-3.02.tar.gz
95 # tar xvfz /usr/local/packages/Curses-1.06.tar.gz
102 # tar xvfz /usr/local/packages/Time-HiRes-01.20.tar.gz
103 # cd Time-HiRes-01.20
110 <P>Do not fall into the trap of thinking they're all the same, just because they
111 nearly are! Pay particular attention to the instructions of <EM>IO</EM>, above.
114 <H2><A NAME="ss1.2">1.2 Preparation</A>
117 <P>I will assume that you have already downloaded the latest tarball of
118 the DXSpider software and are ready to install it. I am assuming version
119 1.47 for this section but of course you would use the latest version.
121 <P>Login as root and create a user to run the cluster under. <B><I>UNDER
122 NO CIRCUMSTANCES USE ROOT AS THIS USER!</I></B>. I am going to use
123 the name <EM>sysop</EM>. You can call it anything you wish. Depending
124 on your security requirements you may wish to use an existing user,
125 however this is your own choice.
133 <P>For SUSE distributions, the command would be ..
141 <P>Now set a password for the user ...
147 # Retype new UNIX password:
148 passwd: all authentication tokens updated successfully
152 <H2><A NAME="ss1.3">1.3 Installing the software</A>
155 <P>Now to unpack the DX Spider distribution, set symbolic links and group
156 permissions. Copy the tarball to /home/sysop and do the following.
161 # tar xvfz spider-1.47.tar.gz
162 # ln -s ~sysop/spider /spider
163 # groupadd -g 251 spider (or another number)
167 <P>If you do not have the command <EM>groupadd</EM> available to you simply
168 add a line in /etc/group by hand.
172 # vi /etc/group (or your favorite editor)
176 <P>You also need to add some others to the group, including your own callsign
177 (this will be used as an alias) and root. The finished line in /etc/group
178 should look something like this
179 <P><CODE>spider:x:251:sysop,g0vgs,root</CODE>
181 <P>The next step is to set the permissions on the Spider directory tree and files ....
185 # chown -R sysop.spider spider
186 # find . -type d -exec chmod 2775 {} \;
187 # find . -type f -exec chmod 775 {} \;
191 <P>This last step allows various users of the group <EM>spider</EM> to have
192 write access to all the directories. This is not really needed just yet
193 but will be useful when web interfaces start to appear.
195 <P>Finally, you need to fix the permissions on the ax25_call and netrom_call
196 programs. Check where they are with the <EM>locate</EM> command and alter
197 the permissions with the <EM>chmod</EM> command like this ..
201 # chown root ax25_call netrom_call
202 # chmod 4775 ax25_call netrom_call
206 <H2><A NAME="ss1.4">1.4 Setting callsigns etc</A>
209 <P>Now login to your machine as the user you created earlier. In my case that
210 user is called <EM>sysop</EM>. Once logged in, issue the following commands ....
217 $ cp perl/DXVars.pm.issue local/DXVars.pm
219 $ vi DXVars.pm (or your favourite editor)
223 <P>Using the distributed DXVars.pm as a a template, set your cluster callsign,
224 sysop callsign and other user info to suit your own environment.
232 <P>This is the call sign of your cluster. If you use an SSID then include it here
241 <P>This is the sysop user callsign, normally your own.
243 <P><B>PLEASE USE CAPITAL LETTERS FOR CALLSIGNS</B>
245 <P>Note that this a perl file which will be parsed and executed as part of the
246 cluster. If you get it wrong then perl will complain when you start the cluster
247 process. It is important only to alter the text of any section. Some of the
248 lines look a little odd. Take this line for example ....
249 <P><CODE>$myemail = "ianmaude\@btinternet.com";</CODE>
251 <P>There appears to be an extra slash in there. However this has to be there
252 for the file to work so leave it in.
254 <P>DON'T alter any file in /spider/perl, they are overwritten with every
255 release. Any files or commands you place in /spider/local or /spider/local_cmd
256 will automagically be used in preference to the ones in /spider/perl EVEN
257 while the cluster is running!
259 <P>Save the new file and change directory to ../perl ....
267 <P>Now type the following command which creates the basic user file with you as
276 <H2><A NAME="ss1.5">1.5 The client program</A>
279 <P>In earlier versions of Spider, all the processes were Perl scripts. This
280 was fine but with a lot of users your computer memory would soon be used up.
281 To combat this a new client was written in "C". This client only works for
282 <EM>incoming</EM> connects at the moment. Before you can use it though it
283 has to be "made". CD to /spider/src and type <EM>make</EM>. You
284 should see the output on your screen and hopefully now have a small C program
285 called <EM>client</EM>. Leave it in this directory.
288 <H2><A NAME="ss1.6">1.6 Starting up for the first time</A>
291 <P>We can now bring spider up for the first time and see if all is well or not!
292 It should look something like this ...
297 DXSpider DX Cluster Version 1.47
298 Copyright (c) 1998 Dirk Koopman G1TLH
300 loading band data ...
301 loading user file system ...
302 starting listener ...
303 reading existing message headers
305 orft we jolly well go ...
309 <P>If all is well then login on another term or console as <EM>sysop</EM> and
310 cd to /spider/src. Now issue the following command ...
318 <P>This should log you into the cluster as the sysop under the alias callsign we
319 set earlier. In this case the callsign is G0VGS. The cluster callsign is set
320 in the DXVars.pm file in /spider/local. In this case we will assume that this
321 was set as GB7MBC. You should therefore see this when you login ....
325 G0VGS de GB7MBC 19-Nov-1999 2150Z >
329 <P>If you do, congratulations! If not, look over the instructions again, you
330 have probably missed something out. You can shut spider down again with the
339 <P>and both the cluster and the client should return to Linux prompts.
343 <A HREF="installation-2.html">Next</A>
345 <A HREF="installation.html#toc1">Contents</A>