From 4bcd914bdf99b8ab78c7d6c67264f71f0e04e20d Mon Sep 17 00:00:00 2001 From: minima Date: Wed, 9 Feb 2005 11:10:54 +0000 Subject: [PATCH] fix some typos rearrange and update a few things in the installation manual --- html/installation_en-1.html | 32 +++-- html/installation_en-4.html | 123 +++++++++--------- html/installation_en.html | 4 +- html/spiderFAQ_en-1.html | 2 +- html/spiderFAQ_en-2.html | 27 ++-- html/spiderFAQ_en.html | 2 +- sgml/installation_en.sgml | 155 +++++++++++++---------- sgml/spiderFAQ_en.sgml | 30 +++-- txt/installation_en.txt | 246 ++++++++++++++++++++---------------- txt/spiderFAQ_en.txt | 50 ++++---- 10 files changed, 375 insertions(+), 296 deletions(-) diff --git a/html/installation_en-1.html b/html/installation_en-1.html index 7108902f..c3427b57 100644 --- a/html/installation_en-1.html +++ b/html/installation_en-1.html @@ -43,20 +43,36 @@ perl distribution.

  • Data-Dumper-2.101.tar.gz this is included in perl 5.6.1 and above
  • -TimeDate-1.10.tar.gz
    • +TimeDate-2.27.tar.gz
  • IO-1.20.tar.gz (for perl 5.00403 and lower)
  • Net-Telnet-3.03.tar.gz
  • -Curses-1.06.tar.gz
    • +Curses-1.08a.tar.gz
  • -Time-HiRes-01.20.tar.gz
    • +Time-HiRes-01.20.tar.gz (for perl versions lower than 5.8 )
  • Digest-SHA1-2.01.tar.gz

    • +

    +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:-

    +

    +

    +

    + +

    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 that's where you have put them.

    @@ -64,8 +80,8 @@ 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/TimeDate-1.10.tar.gz
-# cd TimeDate-1.10
+# tar xvfz /usr/local/packages/TimeDate-2.27.tar.gz
+# cd TimeDate-2.27
 # perl Makefile.PL
 # make test
 # make install
@@ -78,8 +94,8 @@ that's where you have put them.
    
 # make install
 # cd ..
 #
-# tar xvfz /usr/local/packages/Curses-1.06.tar.gz
-# cd Curses-1.06
+# tar xvfz /usr/local/packages/Curses-1.08a.tar.gz
+# cd Curses-1.08a
 # perl Makefile.PL
 # make test
 # make install
@@ -101,7 +117,7 @@ that's where you have put them.

    -

    Only if you need to do these (because your perl is old):-

    +

    Only if you need to do these because your perl is old:-

     #
diff --git a/html/installation_en-4.html b/html/installation_en-4.html
index 96ebacec..cfb04511 100644
--- a/html/installation_en-4.html
+++ b/html/installation_en-4.html
@@ -20,77 +20,97 @@
 
 
    This is dealt with in the previous section
    
 
-
    4.2 Allowing telnet connects from users 
+
    4.2 Setting up telnet connects (from 1.47 onwards)
 
    
 
-
     
->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 
-here will continue to work just fine.
    
+
    >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.
    
 
-
    Allowing telnet connections is quite simple.  Firstly you need to add a line 
-in /etc/services to allow connections to a port number, like this ....
    
+
    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 "0.0.0.0" 
+and select the correct port to listen on.
    
+
    It comes out of the box looking something like:-
    
 
    
 
    
 
    -spdlogin   8000/tcp     # spider anonymous login port
+@listen = (
+#    ["0.0.0.0", 7300],
+);
 
    
 
    
 
    
-
-
    Then add a line in /etc/inetd.conf like this ....
    
+
    Change it so that it looks like this:-
    
 
    
 
    
 
    -spdlogin stream tcp nowait root /usr/sbin/tcpd /spider/src/client login telnet
+@listen = (
+    ["0.0.0.0", 7300],
+);
 
    
 
    
 
    
 
-
    Once this is done, you need to restart inetd like this ....
    
+
    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:-
    
 
    
 
    
 
    -killall -HUP inetd
+@listen = (
+    ["gb7baa.dxcluster.net", 7300],
+    ["44.131.16.2", 6300],
+);
 
    
 
    
 
    
 
-
    Now login as sysop and cd spider/src. You can test that spider 
-is accepting telnet logins by issuing the following command ....
    
+
    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. 
    
+
+
    4.3 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 previous section) but, if you prefer, the method of doing it described 
+here will continue to work just fine.
    
+
+
    Allowing telnet connections is quite simple.  Firstly you need to add a line 
+in /etc/services to allow connections to a port number, like this ....
    
 
    
 
    
 
    -./client login telnet
+spdlogin   8000/tcp     # spider anonymous login port
 
    
 
    
 
    
 
-
    You should get a login prompt and on issuing a callsign, you will be given 
-access to the cluster.  Note, you will not get a password login.  There seems 
-no good reason for a password prompt to be given so it is not asked for.
    
-
-
    Assuming all is well, then try a telnet from your linux console ....
    
+
    Then add a line in /etc/inetd.conf like this ....
    
 
    
 
    
 
    -telnet localhost 8000
+spdlogin stream tcp nowait root /usr/sbin/tcpd /spider/src/client login telnet
 
    
 
    
 
    
 
-
    You should now get the login prompt and be able to login as before.
    
-
-
    4.3 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:-
    
+
    Once this is done, you need to restart inetd like this ....
    
 
    
 
    
 
    @@ -99,46 +119,31 @@ 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 "0.0.0.0" 
-and select the correct port to listen on. So that it looks like this:-
    
+
    Now login as sysop and cd spider/src. You can test that spider 
+is accepting telnet logins by issuing the following command ....
    
 
    
 
    
 
    -@listen = (
-    ["0.0.0.0", 8000],
-);
+./client login telnet
 
    
 
    
 
    
 
-
    As standard, the listener will listen on all interfaces simultaneously. 
-If you require more control than this, you can specify each interface 
-individually:-
    
+
    You should get a login prompt and on issuing a callsign, you will be given 
+access to the cluster.  Note, you will not get a password login.  There seems 
+no good reason for a password prompt to be given so it is not asked for.
    
+
+
    Assuming all is well, then try a telnet from your linux console ....
    
 
    
 
    
 
    -@listen = (
-    ["gb7baa.dxcluster.net", 8000],
-    ["44.131.16.2", 6300],
-);
+telnet localhost 8000
 
    
 
    
 
    
 
-
    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.
    
+
    You should now get the login prompt and be able to login as before.
    
 
-
    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. 
    
 
 
    4.4 Setting up for AGW Engine (1.47 onwards)
 
    
diff --git a/html/installation_en.html b/html/installation_en.html
index 31d730c7..156c8b50 100644
--- a/html/installation_en.html
+++ b/html/installation_en.html
@@ -55,8 +55,8 @@ Carroll, K1XX, (k1xx@ptcnh.net)March 2003 revision 0.7