CPAN and perl installation

From: djk Date: Wed, 2 Dec 1998 19:27:28 +0000 (+0000) Subject: started docs X-Git-Tag: SPIDER_1_5~1 X-Git-Url: http://dxcluster.net/gitweb/gitweb.cgi?a=commitdiff_plain;h=1c42110560587b23608f4e4262c0334a617e6e6d;p=spider.git started docs --- diff --git a/html/cpan.html b/html/cpan.html index 87379f52..d07d367e 100644 --- a/html/cpan.html +++ b/html/cpan.html @@ -1,11 +1,20 @@ - -CPAN and perl installation - - -

CPAN and perl installation

- -

+  
+	CPAN and perl installation
+  
+  
+	CPAN and perl installation
+    
+    
+
+
+Last modified: Wed Dec  2 18:12:42 GMT 1998
+
+
+	I have captured a typical CPAN load here for your information. The details may be slightly
+	  different, but it should give you a vague idea of how it all goes together.
+	
Please note note warnings about loading libnet
+	
 [root@rufus djk]# perl -MCPAN -e shell
 
 We have to reconfigure CPAN.pm due to following uninitialized parameters:
@@ -404,7 +413,15 @@ with spaces. If you do not have a host available for any of the
 services, then enter a single space, followed by . To accept the
 default, hit 
 
-Enter a list of available NNTP hosts : [news]  
+	
+	
+	  ***

+	  *** DO NOT ACCEPT THE DEFAULTS!!! (ed), please enter <space><cr> ***

+	  ***

+	
+	+
+Enter a list of available NNTP hosts : [news]     
 Enter a list of available SMTP hosts : [mailhost]  
 Enter a list of available POP3 hosts : []  
 Enter a list of available SNPP hosts : []  
@@ -778,8 +795,8 @@ Appending installation info to /usr/lib/perl5/i386-linux/5.00404/perllocal.pod
 
 cpan> q
 Lockfile removed.
-
-
-Version: $Id$
-
+

Version: $Id$

+ diff --git a/html/index.html b/html/index.html index e69de29b..bd4e787e 100644 --- a/html/index.html +++ b/html/index.html @@ -0,0 +1,26 @@ + + + + DXSpider + + + +

DXSpider

+ +

+ + +Last modified: Wed Dec 2 18:28:15 GMT 1998 + +

The DXSpider dx cluster system is written in perl5 as an exercise in self-training + for both protocol research and teaching myself perl. +

This document will contain all the instructions for its installation and use - + eventually +

Installation of the main cluster software. +
Installing the lastest version of CPAN. +

+ + diff --git a/html/install.html b/html/install.html index e69de29b..5ffef8d1 100644 --- a/html/install.html +++ b/html/install.html @@ -0,0 +1,221 @@ + + + + Installing Spider + + + +

Installing Spider

+ +

+ + +Last modified: Wed Dec 2 18:19:38 GMT 1998 + + +

This version of dxspider requires perl5 (it is written entirely in perl5 and + makes extensive use of perl objects). This program is known to work with + RedHat 5.1 perl5_004.

+ +

In addition to the standard perl5 distribution you will require to load the + the following modules:-

+ +

CPAN - this has a load of the standard extra stuff in it. To load it type:- + +
```
+  # perl -MCPAN -e shell
+  cpan> install Bundle::CPAN
+  cpan> q
+     
```
+ +
Please sure there were no errors, be particularly careful when installing + libwww stuff, I would suggest 'no host lookups' and pressing <space> and + enter for each of the offered default hostnames.
+ +
I have monitored a typical load of CPAN which you can + look at here
+ +
Date::Parse, MLDBM, IO::Select + +
As you have so carefully loaded it, I suggest you use the CPAN system + above:-
+
```
+  # perl -MCPAN -e shell
+  cpan> install Date::Parse
+  ..
+  ..
+  cpan> install MLDBM
+  ..
+  ..
+  cpan> install IO::Select
+        
```
+
In order to use IO::Select you will need to
+
```
+  # cd /root/.cpan/build/IO-1.20  
+  # make install UNINST=1
+        
```
+
The 'cd' is to the place where CPAN sets up its local cache. The example + shown is for Linux defaults.
+ +
select a user to run the cluster as UNDER _NO_ CIRCUMSTANCES USE ROOT. + +
I say again DO NOT USE root.
+ +
Pick an existing user or create a new one. Don't care which. I don't know + your security requirements.
+ +
login as root (I shall use 'jim' for any examples).
+ +

type in the following:- +

+   # cd ~jim
+   # tar xvfz spider-x.x.tar.gz
+   # ln -s ~jim/spider /spider
+   # groupadd -g 251 spider       (or another number)
+   # vi /etc/group                (or your favorite editor)
+

+ +

add jim (or whatever) and root to the group spider + it should look something like:-

+ +

+     spider:x:251:jim,root
+     :x
+   # chown -R jim.spider spider
+   # find . -type d -exec chmod 2775 {} \;
+   # find . -type f -exec chmod 775 {} \;
+

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.

+ +

if you have any users that require network logins, set them up as real + users with useradd -m <callsign>. 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
+		
```
+ +
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.
+ +
for incoming AX25 connections you are expected to have got the AX25 + utilities setup, tested and working. See the AX25-HOWTO for more info + on this - it really is outside the scope of this document. I would + recommend using ax25-utils-2.1.42a-5.i386.rpm or above as a starting + point. DXSpider uses ax25d for incoming connections. You need to have + entries like this:- +
```
+   [ether]                                                                         
+   NOCALL   * * * * * *  L                                                         
+   default  * * * * * *  - jim /spider/perl/client.pl client.pl %u ax25
+   <bbs>
+   NOCALL   * * * * * *  L                                                         
+   default  * * * * * *  - jim /spider/perl/client.pl client.pl %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.
+ +
Find your netrom_call and ax25_call programs (which on + my system live in /usr/sbin and chmod them so that they are SUID root +
```
+   # chown root ax25_call netrom_call
+   # chmod 4775 ax25_call netrom_call
+        
```
+
This has to be done to allow you to specify the correct callsigns on outgoing connects
+ +
login as jim (or whatever) +
```
+   $ startx                     (much easier to use X)
+   $ cd /spider
+   $ mkdir local
+   $ mkdir local_cmd
+   $ cp perl/DXVars.pm local
+   $ cd local
+   $ vi DXVars.pm
+		
```
+
now alter your cluster callsign, sysop callsign and other user info + as you wish. Note that this a perl file which will parsed and executed + as part of the cluster. If you get it wrong then perl will complain + when you start the cluster process.
+ +
PLEASE USE CAPITAL LETTERS FOR CALLSIGNS
+ +
DON'T alter the DXVars.pm (or any other 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 whilst the cluster is running!
+
```
+   :x
+   
+   $ cd ../perl
+		
```
+ +
now create the basic user file with you as the sysop.
+
```
+   $ create_sysop.pl
+		
```
+ +
try and run the cluster program and see whether all the various rivets are + flying in approximate formation...
+ +
```
+   $ cluster.pl
+   DXSpider DX Cluster Version x.x
+   Copyright (c) 1998 Dirk Koopman G1TLH
+   loading prefixes ...
+   loading band data ...
+   loading user file system ...
+   starting listener ...
+   reading existing message headers
+   reading cron jobs
+   orft we jolly well go ...
+		
```
+ +
now log in again or start another rxvt or xterm +
```
+   $ client.pl
+		
```
+ +
you should now see a normal cluster prompt.
+ +
at the cluster prompt:-
+
```
+   G1JIM de GB7JIM 10-Sep-98 1000Z> set/node GB7XXX
+        
```
+ +
for every dxcluster you expect to connect to or from.
+ +
```
+   G1JIM de GB7JIM 10-Sep-98 1001Z> shutdown
+		
```
+ +
The cluster and the client should both go back to prompts + +
Restart the cluster. + +
The callsigns should be the sysop callsign and the cluster callsign + as per your modified DXVars.pm. You can check that the cluster + connections will work by:- +
```
+   $ client.pl gb7xxx      (doesn't have to be uppercase).
+   PC38^GB7JIM^~           <- the cluster thinks this is a cluster
+   ^C                      <- to get out
+        
```
+

+ +

Version: $Id$

+ +