X-Git-Url: http://www.dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=sgml%2Finstallation_en.sgml;h=0d314c39e43c8d73776d82872fcd9609274cf2c3;hb=refs%2Fheads%2Fstaging;hp=de183687366966dc5807fe9610983e452fdf5000;hpb=90a05bee744c82d66ffdd0a0548b2ae97d7dfb56;p=spider.git diff --git a/sgml/installation_en.sgml b/sgml/installation_en.sgml index de183687..0d314c39 100644 --- a/sgml/installation_en.sgml +++ b/sgml/installation_en.sgml @@ -36,7 +36,7 @@ know how to use tar and how to edit files using your favourite editor. The crucial ingredient for all of this is . Earlier versions of Spider required perl 5.004, however it is now STRONGLY recommended -that you use at least version 5.005_03 as this is the version being used +that you use at least version 5.6.1 as this is the version being used in the development of Spider.

@@ -48,15 +48,31 @@ perl distribution.

- - - + this is included in perl 5.6.1 and above + + (for perl 5.00403 and lower) - - + + (for perl versions lower than 5.8 ) +

+On most modern distributions most (if not all) the modules you will need are either included or +can be loaded automatically. Please consult your distro's instructions for loading new programs +and look for modules that usually start with the string "perl-". For instance:- + + +Mandrake: urpmi perl-TimeDate perl-Digest-SHA1 perl-Curses perl-Net-Telnet +Redhat/Fedora: up2date perl-TimeDate perl-Digest-SHA1 perl-Curses perl-Net-Telnet +SuSE: use yast +Debian: use apt-get + + +

+Some distros are now packaging perl-DB_File separately as well, so you may have to add that to the list +above. +

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 @@ -66,54 +82,61 @@ that's where you have put them. Log in as 'root', and make sure you're at '/root' before you continue. Here are exactly the commands you must issue next: - -# tar xvfz /usr/local/packages/Data-Dumper-2.101.tar.gz -# cd Data-Dumper-2.101 +# tar xvfz /usr/local/packages/TimeDate-2.27.tar.gz +# cd TimeDate-2.27 # perl Makefile.PL # make test # make install # cd .. # -# tar xvfz /usr/local/packages/TimeDate-1.10.tar.gz -# cd TimeDate-1.10 +# tar xvfz /usr/local/packages/Net-Telnet-3.03.tar.gz +# cd Net-Telnet-3.02 # perl Makefile.PL # make test # make install # cd .. # -# tar xvfz /usr/local/packages/IO-1.20.tar.gz -# cd IO-1.20 +# tar xvfz /usr/local/packages/Curses-1.08a.tar.gz +# cd Curses-1.08a # perl Makefile.PL # make test -# make install UNINST=1 +# make install # cd .. # -# tar xvfz /usr/local/packages/Net-Telnet-3.03.tar.gz -# cd Net-Telnet-3.02 +# tar xvfz /usr/local/packages/Time-HiRes-01.20.tar.gz +# cd Time-HiRes-01.20 # perl Makefile.PL # make test # make install # cd .. # -# tar xvfz /usr/local/packages/Curses-1.06.tar.gz -# cd Curses-1.06 +# tar xvfz /usr/local/packages/Digest-SHA1-2.01.tar.gz +# cd Digest-SHA1-2.01 # perl Makefile.PL # make test # make install # cd .. + + +

+Only if you need to do these because your perl is old:- + + # -# tar xvfz /usr/local/packages/Time-HiRes-01.20.tar.gz -# cd Time-HiRes-01.20 +# tar xvfz /usr/local/packages/IO-1.20.tar.gz +# cd IO-1.20 # perl Makefile.PL # make test -# make install +# make install UNINST=1 # cd .. # -# tar xvfz /usr/local/packages/Digest-SHA1-2.01.tar.gz -# cd Digest-SHA1-2.01 +# tar xvfz /usr/local/packages/Data-Dumper-2.101.tar.gz +# cd Data-Dumper-2.101 # perl Makefile.PL # make test # make install # cd .. +#

@@ -234,8 +257,9 @@ $mycall = "GB7DJK";

-This is the call sign of your cluster. If you use an SSID then include it here -also. +This is the call sign of your cluster. Here in the UK we have +separate callsigns for our cluster nodes. If you can't use a different callsign I suggest +you use an SSID of '-2' for the node callsign '$mycall'. $myalias = "G1TLH"; @@ -885,11 +909,74 @@ netrom connections.

This is dealt with in the previous section -Allowing telnet connects from users +Setting up telnet connects (from 1.47 onwards) + +

+>From version 1.47 you can choose to allow the perl cluster.pl program to +allow connections directly (i.e. not via the /spider/src/client +interface program). If you are using Windows then this is the only method +available of allowing incoming telnet connections. + +

+to make the change happen... + +

+Having done that, you need to copy the file +/spider/perl/Listeners.pm to /spider/local and +then edit it. You will need to uncomment the line containing &dquot;0.0.0.0&dquot; +and select the correct port to listen on. + +It comes out of the box looking something like:- + + +@listen = ( +# ["0.0.0.0", 7300], +); + + +Change it so that it looks like this:- + + +@listen = ( + ["0.0.0.0", 7300], +); + + +

+Later versions have more comments in the Listeners.pm file that +are designed to help you remove the correct '#' character. + +

+As standard, the listener will listen on all interfaces simultaneously. +If you require more control than this, you can specify each interface +individually:- + + +@listen = ( + ["gb7baa.dxcluster.net", 7300], + ["44.131.16.2", 6300], +); + + +

+This will only be successful if the IP addresses on each interface are static. +If you are using some kind of dynamic IP addressing then the 'default' method +is the only one that will work. + +

+Restart the cluster.pl program to enable the listener. + +

+One important difference with the internal listener is that no echoing +is done by the cluster program. Users will need to set 'local-echo' on in +their telnet clients if it isn't set automatically (as per the standards). +Needless to say this will probably only apply to Windows users. + +Allowing telnet connects from users (before version 1.47 or for special purposes)

>From version 1.47 there is a new (more efficient) way of doing this -(see next section) but, if you prefer, the method of doing it described +(see previous section) but, if you prefer, the method of doing it described here will continue to work just fine.

@@ -937,62 +1024,6 @@ telnet localhost 8000

You should now get the login prompt and be able to login as before. -Setting up telnet connects (from 1.47 onwards) - -

->From version 1.47 you can choose to allow the perl cluster.pl program to -allow connections directly (i.e. not via the /spider/src/client -interface program). If you are using Windows then this is the only method -available of allowing incoming telnet connections. - -

-To do this you need first to remove any line that you may previously have set -up in /etc/inetd.conf. Remember to:- - - -killall -HUP inetd - - -

-to make the change happen... - -

-Having done that, you need to copy the file -/spider/perl/Listeners.pm to /spider/local and -then edit it. You will need to uncomment the line containing &dquot;0.0.0.0&dquot; -and select the correct port to listen on. So that it looks like this:- - - -@listen = ( - ["0.0.0.0", 8000], -); - - -

-As standard, the listener will listen on all interfaces simultaneously. -If you require more control than this, you can specify each interface -individually:- - - -@listen = ( - ["gb7baa.dxcluster.net", 8000], - ["44.131.16.2", 6300], -); - - -

-This will only be successful if the IP addresses on each interface are static. -If you are using some kind of dynamic IP addressing then the 'default' method -is the only one that will work. - -

-Restart the cluster.pl program to enable the listener. - -

-One important difference with the internal listener is that no echoing -is done by the cluster program. Users will need to set 'local-echo' on in -their telnet clients if it isn't set automatically (as per the standards). -Needless to say this will probably only apply to Windows users. Setting up for AGW Engine (1.47 onwards)