-
Notifications
You must be signed in to change notification settings - Fork 9
/
Copy pathREADME.INSTALL
110 lines (76 loc) · 2.98 KB
/
README.INSTALL
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
Guide to install FUNET-NJE software into UNIX systems.
by Matti Aarnio <[email protected]>
READ THE README.FUNET FILE!
READ THE funetnje.info / funetnje.ps DOCUMENT!
The configuration and installation is covered on the
funetnje.info/funetnje.ps -document, this file is from
the older era...
This version of software does not support any kind of
BISYNC-adapters available for various systems. Mainly
because I didn't have such interface available for testing...
However: TCP-IP interface works well (one of rare features
that are ALMOAST identical among various UNIXes).
When starting to do installation, you must determine few
system dependent features:
In Makefile:
Well, dependencies should be all right, some external defines
and route + install phases propably need an update.
Usage of `ranlib' depends upon your system, same with `install'
Choise of group-name used on client-program installation.
In detach.c:
See & try which setup works best. Quite well documented in there.
CONFIGURING SYSTEM:
Create a new group for FUNET-NJE internal use, say `bitnet'.
Decide and create your BITNET spool directory:
/usr/spool/bitnet
set its protection to be 2775 (or 2770), group-write is
needed. Set its group to be abovementioned `bitnet'.
(Mode 2xxx attempts to do BSD directory semantics on group
inheritance)
Decide where you put your user spool directories, exaple:
/usr/spool/bitspool
However HAVE THEM ON SAME PHYSICAL DEVICE so that rename(2)
(or rename(3)) can be used successfully to place files into
there. Directory can have protection 111, or 555. Nobody
(but root) need to have write-permission there.
Programs used for sending BITNET files are configured to
do a set-gid operation, and then write file to be spooled
into the `QUEUE' directory, and finally sending a submission
signal to the transporter.
More information from funetnje(8)
Sample version of /etc/funetnje.cf :
#
# Configuration file for FUNET-NJE program
#
NAME HAMSTER
IPADDRESS 128.214.6.100
QUEUE /usr/spool/bitnet
CMDMAILBOX /usr/spool/bitnet/.cmdpipe
LOG /usr/adm/bitnet.log
# this table is DBM/NDBM/GDBM binary file.
TABLE /usr/lib/funetnje.route
INFORM MEA@HAMSTER
USEREXITS /usr/local/lib/funetnje/file-exit.cf
MSGEXITS /usr/local/lib/funetnje/msg-exit.cf
LLEVEL 2
DEFAULT-ROUTE FIGBOX
LINE 0 SEARN
TYPE UNIX_TCP
BUFSIZE 1024
TIMEOUT 10
IPPORT 175
TCPNAME searn.sunet.se
TCP-SIZE 8192
MAX-STREAMS 7
LINE 1 FINTEST1
TYPE UNIX_TCP
BUFSIZE 1024
TIMEOUT 10
IPPORT 175
TCPNAME mea.utu.fi
TCP-SIZE 8192
MAX-STERAMS 7
Comments start with '#' or '*' on first column.
Otherwise white space (blanks and/or tabs) are freely usable.
Completely WHITE lines are suggested not to include anything but
newline.