X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=sgml%2Finstallation.sgml;h=286a8f8bd6f2ec93e317845d9d52e844e6bf2b4a;hb=7e16f0c1dcaef94c54a04fa4355d9741cd46f7cb;hp=50e9e5c272613c76cf6f2bc541c510a70212f4c0;hpb=14e5872f34acc3b869c3864510b10fd9929d728b;p=spider.git diff --git a/sgml/installation.sgml b/sgml/installation.sgml index 50e9e5c2..286a8f8b 100644 --- a/sgml/installation.sgml +++ b/sgml/installation.sgml @@ -6,8 +6,8 @@
In addition to the standard Red Hat distribution you will require the
-following modules from
+In addition to the standard Red Hat distribution you will require the
+following modules from
+This is the call sign of your cluster. If you use an SSID then include it here
+also.
+
+
+This is the sysop user callsign, normally your own.
+
+
+
+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 ....
$myemail = "ianmaude\@btinternet.com";
@@ -226,8 +255,6 @@ $myemail = "ianmaude\@btinternet.com";
There appears to be an extra slash in there. However this has to be there
for the file to work so leave it in.
-
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
@@ -298,6 +325,7 @@ was set as GB7MBC. You should therefore see this when you login ....
G0VGS de GB7MBC 19-Nov-1999 2150Z >
+
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 ....
@@ -339,6 +367,7 @@ is the user that should be doing that process.
Spider should now be running and you should be able to login using the
client program.
@@ -350,6 +379,7 @@ client program.
Spider should now be able to accept logins via telnet, netrom and ax25.
or, if you wish your users to be able to use SSID's on their callsigns ..
For most purposes this is not desirable. The only time you probably will
need this is when you need to allow other cluster nodes that are using SSID's
in. In this case it would probably be better to use the first example and
@@ -409,6 +441,7 @@ in /etc/services to allow connections to a port number, like this ....
spdlogin 8000/tcp # spider anonymous login port
+
Then add a line in /etc/inetd.conf like this ....
Now login as sysop and cd spider/src. You can test that spider
+
+Now login as sysop and cd spider/src. You can test that spider
is accepting telnet logins by issuing the following command ....
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.
@@ -643,7 +677,7 @@ or symbols:-
connects to GB7DJK-1 [instead of a script called gb7djk-1]).
-
+
There are many possible ways to configure the script but here are three examples,
one for a NETRom/AX25 connect, one for AGW engines and one for tcp/ip.
@@ -702,6 +736,7 @@ connection to GB7DJK-1 started
G0VGS de GB7MBC 13-Dec-1998 2043Z >
+
This will start a connection using the script called gb7djk-1. You can
follow the connection by watching the term or console from where you started
cluster.pl. From version 1.47 onwards, you will need to set/debug connect first.
@@ -794,6 +829,7 @@ connect telnet mary.lancs.ac.uk
'connect' ''
+
So, the first connection is made by Spider. This is fine as Spider uses the
Net_Telnet script from within perl. This actually uses TCP rather than TELNET
so no negotiation will be done on the first connection. Once connected to
@@ -833,7 +869,7 @@ This line works fine for RedHat distributions. It is also fine for SuSE up to
DX:235:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7
-
+
The line required for Slackware distributions is slightly different. My thanks to
Aurelio, PA3EZL for this information.
@@ -1019,31 +1055,43 @@ do it that way because it suits me.
Get the current version of the DX Spider distribution. This needs
to be v1.47 or later. You've got two ways (currently) of getting
this; either get a CVS update from sourceforge (if you don't know
-what this is, then it isn't for you) or get my package from:-
+what this is, then it isn't for you) or get the latest "official"
+release from:-
- The only difference between "CVSlatest.tgz" and the latest
+"official" release version is that it is more up to date. Don't confuse
+this TGZ file with "Downloading from Sourceforge with CVS" - they are two
+quite different things.
+
+
+If you went down the CVS route (ie installed wincvs and downloaded from
+sourceforge), then everything will be nicely
+set out on your local disk. If you got the TGZ file, unpack it to
somewhere convenient. The following examples assume that you put
it on drive "C:\", for convenience.
- You will need
-Ensure that your CVS session or your unZIPped file have left you
-with a directory "C:\spider\local"; if not, go to "C:\spider\"
-and create one. If "C:\spider" is missing, go back and figure out
-why, because it shouldn't be.
+Ensure that your CVS session or your WINunZIPped file have left you with
+a directory "C:\spider\local" and C:\spider\local_cmd"; if not, go to
+"C:\spider\" and create them. If "C:\spider" is missing, go back and
+figure out why, because it shouldn't be.
Now create your own local copy of the DXVars.pm file by:-
@@ -1072,12 +1120,59 @@ minimum you must adjust the following items in DXVars.pm:-
+If you want to enable inbound "TELNET" connections (or you are running
+Windows NT, 2000 or XP), you've got a little more work to do. From a
+handy "DOS box" that's not doing anything else, do the following:-
+
+ If your machine is connected to the internet I would recommend Anyway, if you are rewarded with a display which looks something like:-
-If you want to enable inbound "TELNET" connections, you've got a
-little more work to do. From a handy "DOS box" that's not doing
-anything else, do the following:-
-
- The interface is very basic. It is a simple command line. There are
+better looking interfaces. Most of the "standard" logging and DX
+Cluster access programs that are capable of connecting via a TCP or
+telnet connection will work as a "Sysop Console" client. You connect
+to "localhost" on the port that you defined in Listeners.pm (usually
+7300). I recommend packages like
-If you want to connect this to another cluster, then you'll want
-to negotiate a link with someone. For experimental purposes, I'm
-happy to allow folk to connect to GB7DXA (spud.ath.cx), on the
-understanding that the system may or may not be there and may or
-may not be connected to anything particularly useful at any given
-moment. Contact me by Email if you want me to set up a connection
-for you.
+If you want to connect this to another cluster, then you'll want to
+negotiate a link with someone. For experimental purposes, I'm happy to
+allow folk to connect to GB7DXA (spud.ath.cx), on the understanding
+that the system may or may not be there and may or may not be
+connected to anything particularly useful at any given moment. Contact
+me by