X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2Finstall.html;h=7b75e8cfd202e328cf60c1c836cfa01490aad2d6;hb=f8d23f0de888299ee510229861cbce4b6fd25e19;hp=74c432ce4bf80c7bce1c4df118da682a4d353bb1;hpb=69c8aeb338cc485103e289fbab7ec4e7e056ed20;p=spider.git diff --git a/html/install.html b/html/install.html index 74c432ce..7b75e8cf 100644 --- a/html/install.html +++ b/html/install.html @@ -1,10 +1,12 @@ - +s
This HOWTO describes the installation for DX Spider v1.11 on a "vanilla" +
This HOWTO describes the installation for DX Spider v1.30 on a "vanilla" RedHat 5.1 platform, and assumes that you have started with a clean disk, with nothing other than the standard Red Hat 5.1 distribution. I always select 'everything', and that seems to ensure that nothing is missed out :-) [ more normal people may like to try with less Ed ]. +
WARNING The perl on the vanilla RedHat 5.2 + (perl-5.004m4-1.i386.rpm) is BROKEN, please use the one + in the Download section. +
The crucial ingredient for all of this is Perl 5.004. Now I know Perl 5.005 is out and this will almost certainly work with it, but RedHat 5.1 comes with 5.004. @@ -32,21 +38,23 @@ Last modified: Sat Dec 19 16:10:14 GMT 1998 do not come with 5.004 as standard, you need to upgrade -
In addition to the standard Red Hat distribution you will require the following CPAN modules: - +
In addition to the standard Red Hat distribution you will require the following CPAN modules:
Do get the latest versions of these packages if any of the above list - is out of date. +
The modules above are the current versions found at www.cpan.org in the appropriate directories - + you can click on the links (above) to download them - particularly useful if you use the Lynx text HTML browser from your Linux box. + You may wish to check for more recent versions of these modules and use the newer ones if they are available.
+ +You'll also need the AX25 utility package. There is much debate about what is "best", what is "better". What works for 5.1 is this: -
@@ -85,36 +93,36 @@ Last modified: Sat Dec 19 16:10:14 GMT 1998 # make install # cd .. # -# tar xvfz /usr/local/packages/FreezeThaw-0.3.tar.gz -# cd FreezeThaw-0.3 +# tar xvfz /usr/local/packages/TimeDate-1.08.tar.gz +# cd TimeDate-1.08 # perl Makefile.PL # make test # make install # cd .. # -# tar xvfz /usr/local/packages/MLDBM-2.00.tar.gz -# cd MLDBM-2.00 +# 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/TimeDate-1.08.tar.gz -# cd TimeDate-1.08 +# tar xvfz /usr/local/packages/Net-Telnet-3.02.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.05.tar.gz +# cd Curses-1.05 # perl Makefile.PL # make test -# make install UNINST=1 +# make install # cd .. # -# tar xvfz /usr/local/packages/Net-Telnet-3.01.tar.gz -# cd Net-Telnet-3.01.tar.gz +# tar xvfz /usr/local/packages/Time-HiRes-01.20.tar.gz +# cd Time-HiRes-01.20 # perl Makefile.PL # make test # make install @@ -158,33 +166,97 @@ spider:x:251:sysop,g0rdi,root
This last step allows various users of group spider to have write access to all the directories. Not really needed for now but will be useful when web interfaces start to appear. -
To do this you should:-
-exec /spider/perl/client.pl <callsign> telnet --
Alternatively you can set up a real login for a person (or another cluster) by creating a login using:- -
-# useradd gb7djk +# cd /spider/src +# make ++ +
You can continue to use the perl client (/spider/perl/client.pl, but + support of this will gradually whither away. + +
+# useradd -m gb7djk # passwd gb7djk New UNIX password: Retype new UNIX password: passwd: all authentication tokens updated successfully-
and editing the /etc/passwd file to look like this (do substitute the correct callsigns here ;-):- + +
You can then either alter the default .bashrc so that it + contains just one line (assuming you use the default bash + shell). + +
+exec /spider/perl/client.pl <callsign> telnet ++ +
Alternatively you can alter the /etc/passwd thus:- +
fbb:x:505:505::/home/fbb:/bin/bash gb7djk:x:506:506::/home/gb7djk:/usr/bin/perl /spider/perl/client.pl gb7djk telnet-
Don't forget to give them a real password. This is really for network cluster logins. The telnet argument does two things, it sets the EOL convention to \n rather than AX25's \r and it automatically reduces the privilege of the <callsign> to a 'safe[r]' level.). + Don't forget to give them a real password. The telnet argument + does two things, it sets the EOL convention to \n rather than + AX25's \r and it automatically reduces the privilege of the + <callsign> to a 'safe[r]' level.). If the user or other cluster + program requires AX25 conventions to operate then you can use + ax25 instead. + +
Another thing you can do is to get inetd to listen + on a specific port and then start the client up directly. To + do this, create an entry in /etc/services with a + port number > 1000 that isn't used elsewhere eg:- + +
+gb7djk 8001/tcp +gb7tlh 8002/tcp ++ + Then create some lines in /etc/inetd.conf that look + like this:- + +
+gb7djk stream tcp nowait sysop /usr/sbin/tcpd /spider/src/client gb7djk telnet +gb7tlh stream tcp nowait sysop /usr/sbin/tcpd /spider/src/client gb7tlh telnet ++ + Please DON'T run the client as root you will only + come to regret it later when the next person finds a security hole + in DX Spider (there are bound to be some although I have tried to + avoid the obvious ones I could think of). + +
The only reason I would use this mechanism is for Internet connections + to other or from other clusters. Don't use this for normal users. + +
In the example I have used tcpd as the access control + mechanism to the port. Don't (I can't be bothered to emphasize + it any more) run a system like this without one, you are asking + for trouble. In fact I use the TIS + Firewall Toolkit myself, you may find this more intuitive + to use. The point is that gb7djk would only be coming + from one IP address, if it coming from another, it is an imposter! + +
You are responsible for arranging and looking after your + security - not me. +
-[ether] -NOCALL * * * * * * L -default * * * * * * - sysop /spider/perl/client.pl client.pl %u ax25 -<bbs> -NOCALL * * * * * * L -default * * * * * * - sysop /spider/perl/client.pl client.pl %u ax25 +[ether] +NOCALL * * * * * * L +default * * * * * * - sysop /spider/src/client client %u ax25 +<cluster> +NOCALL * * * * * * L +default * * * * * * - sysop /spider/src/client client %u ax25
where 'ether' and 'bbs' are appropriate KNOWN WORKING axport and nrport names respectively. Obviously you can use different names, callsigns or whatever for your purposes, but it is up to you to get it to work. Note I use BPQ over ethernet which why I have the port names I have. @@ -195,7 +267,7 @@ default * * * * * * - sysop /spider/perl/client.pl client.pl %u ax25
This has to be done to allow you to specify the correct callsigns on outgoing connects -
$ startx (much easier to use X) $ cd /spider @@ -255,20 +327,31 @@ $ client.pl gb7xxx (doesn't have to be uppercase). PC38^GB7JIM^~ <- the cluster thinks this is a cluster ^C <- to get out+
+
+$ console.pl ++
This is the normal way (as of version 1.30) of running the cluster system + as a sysop. It is a simple program client program that allows you to + press <up-arrow> <down-arrow> and use all the usual line editting + keystrokes that you can use on the unix shell under linux or bash. +
In addition, it will highlight certain type of lines in particular + colours and allow you to scroll the top window up and down with the + <page-up> and <page-down> keys.
You should now have a basic working system. Best of luck! Can I now draw your attention to - the Bug Reporting System. Some mailing lists will - be created RSN for more general discussions. + the Bug Reporting System.
Can I commend to you the Announcements mailing list to which you may - subscribe. + subscribe. This is a low volume mailing list which will send you announcements of new patches and such like things as they arise.
If you like what you see and want to be a part of the ongoing development then - subscribe - to the support mailing list which will be the initial focus of any discussions. + subscribe + to the support mailing list which will be the focus of any discussion/bug fixing etc.