<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation Manual v1.48: Linux Installation </TITLE>
+ <TITLE>The DXSpider Installation Manual v1.49: Linux Installation </TITLE>
<LINK HREF="installation-2.html" REL=next>
<LINK HREF="installation.html#toc1" REL=contents>
<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> ...
+<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
+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
+perl distribution.
<P>
<P>
<UL>
<LI>
<A HREF="http://www.cpan.org/modules/by-module/Net/Net-Telnet-3.02.tar.gz">Net-Telnet-3.02.tar.gz</A></LI>
<LI>
-<A HREF="http://www.cpan.org/modules/by-module/Curses/Curses-1.05.tar.gz">Curses-1.05.tar.gz</A></LI>
+<A HREF="http://www.cpan.org/modules/by-module/Curses/Curses-1.06.tar.gz">Curses-1.06.tar.gz</A></LI>
<LI>
<A HREF="http://www.cpan.org/modules/by-module/Time/Time-HiRes-01.20.tar.gz">Time-HiRes-01.20.tar.gz</A></LI>
</UL>
<P>
-<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>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: -
<P>
# make install
# cd ..
#
-# tar xvfz /usr/local/packages/Curses-1.05.tar.gz
-# cd Curses-1.05
+# tar xvfz /usr/local/packages/Curses-1.06.tar.gz
+# cd Curses-1.06
# perl Makefile.PL
# make test
# make install
# cd ..
</PRE>
<P>
-<P>Do not fall into the trap of thinking they're all the same, just because they nearly are! Pay particular attention to the instructions of IO, above.
+<P>Do not fall into the trap of thinking they're all the same, just because they
+nearly are! Pay particular attention to the instructions of <EM>IO</EM>, above.
<P>
<P>
<H2><A NAME="ss1.2">1.2 Preparation</A>
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>For SUSE distributions, the command would be ..
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+# useradd -m sysop
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
<P>Now set a password for the user ...
<P>
<BLOCKQUOTE><CODE>
# groupadd -g 251 spider (or another number)
</PRE>
</CODE></BLOCKQUOTE>
+<P>
<P>If you do not have the command <EM>groupadd</EM> available to you simply
add a line in /etc/group by hand.
<P>
# vi /etc/group (or your favorite editor)
</PRE>
</CODE></BLOCKQUOTE>
+<P>
<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
</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 ....
+sysop callsign and other user info to suit your own environment.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+$mycall = "GB7DJK";
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>This is the call sign of your cluster. If you use an SSID then include it here
+also.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+$myalias = "G1TLH";
+</PRE>
+</CODE></BLOCKQUOTE>
+<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
+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>
-<P><B>PLEASE USE CAPITAL LETTERS FOR CALLSIGNS</B>
-<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
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<H2><A NAME="ss1.5">1.5 Starting up for the first time</A>
+<H2><A NAME="ss1.5">1.5 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>
+<H2><A NAME="ss1.6">1.6 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!
G0VGS de GB7MBC 19-Nov-1999 2150Z >
</PRE>
</CODE></BLOCKQUOTE>
+<P>
<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>
<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="installation-2.html">Next</A>
projects / spider.git / blobdiff