Commit | Line | Data |
---|---|---|
9ae2013b BJ |
1 | A substantial number of minor changes were made to ``uucp'' |
2 | at the end of February and early March, before Dave Nowitz returned | |
3 | to Piscataway. Changes made after March, 15, 1979, will be available through | |
4 | stockroom category, ``uucp_changes''. Any installation with a version | |
5 | of ``uucp'' obtained before March 15, should obtain the whole | |
6 | distribution afresh. | |
7 | ||
8 | Most of the changes are relatively benign. See the file CHANGES | |
9 | for a list of what has been done. PLEASE NOTE that there is one | |
10 | important difference between the present version and previous versions: | |
11 | there is a change to the file ``L-devices''. For each entry representing | |
12 | an ACU insert the string "ACU " at the beginning of the line; for each | |
13 | direct connection, insert "DIR ". This should take all of a minute. | |
14 | ||
15 | Two short shell procedures, ``uutest'' and ``uucheck'' are | |
16 | included in the distribution. You may find them useful for administrative | |
17 | purposes. Put links to them in your personal bin directory. (On | |
18 | our system, they live in /usr/lib/uucp.) | |
19 | ||
20 | PWB 1.2 SYSTEMS | |
21 | There is a new stockroom category, called ``pwbuucp'', (made March 21) | |
22 | which gives additional information regarding installing uucp on PWB 1.2 | |
23 | systems. This information is by courtesy of Brian Redman. | |
24 | ||
25 | GENERAL INSTRUCTIONS | |
26 | Before running "uucp", you should change the define for "MYNAME" | |
27 | in "uucp.h" to whoever you are, and recompile. | |
28 | As delivered, "uucp" thinks that it is running on the ``usg'' system. | |
29 | ||
30 | NOTE - To export executable code: | |
31 | A new routine (uucpname.c) has been added which returns the local uucp name. | |
32 | If no action is taken, this routine will return the value | |
33 | of "MYNAME". By defining "UNAME" as value 1 in "uucp.h", the value returned | |
34 | is determined by a call to "uname(&utsname)" where utsname is a structure | |
35 | which contains an element "nodename" - the uucpname for the local system. | |
36 | ||
37 | Since all ACUs are not created equal, the last character which must | |
38 | be sent to the ACU may differ on your system. The value "ACULAST" in | |
39 | "uucp.h" should be modified if necessary. | |
40 | ||
41 | To run successfully you will need to provide working | |
42 | versions of the following files: | |
43 | ||
44 | L-devices entries for call-units and hard-wired connections | |
45 | L-dialcodes decodes abbreviations occurring in L.sys | |
46 | L.sys pertinent details about other systems that you | |
47 | may call, as the result of prior agreement. | |
48 | USERFILE user accessibility information | |
49 | ||
50 | The information in these files is specific to each installation. | |
51 | The versions supplied are arbitrarily modified versions of files | |
52 | used on the Usg machine, and are provided only for your | |
53 | information. | |
54 | ||
55 | As delivered, "uucp" is set up to use the following | |
56 | directories (contrary to some documentation): | |
57 | ||
58 | /usr/src/cmd/uucp source files | |
59 | /usr/lib/uucp executable programs and data files | |
60 | /usr/spool/uucp work-in-progress | |
61 | /usr/lib/uucp/.XQTDIR work area for "uuxqt" | |
62 | /usr/spool/uucppublic uucp public directory | |
63 | ||
64 | "/usr/bin/uucp (uux)" is linked to "/usr/lib/uucp/uucp (uux)". | |
65 | ||
66 | NOTE - some resent changes have moved some to the directories. | |
67 | The names appear in uucp.h and the "uucp.mk" file. | |
68 | (SPOOL, XQTDIR, PUBDIR, INSDIR, THISDIR) | |
69 | The login directory for the uucp login(s) should be the PUBDIR | |
70 | directory. | |
71 | ||
72 | Note also that there is an array called "Cmds" in the file | |
73 | "uuxqt.c" which names the commands which may be executed at | |
74 | the request of a remote user, via "uux". You will most probably | |
75 | wish to modify the initialization of this array, to reflect the | |
76 | commands you are willing to allow on your system. | |
77 | ||
78 | The ``mail'' command has been modified, so that it may | |
79 | only be used to send mail, when it is invoked under a name beginning | |
80 | with 'r'. (In the receive mode, it can be used to invoke a shell, | |
81 | thus creating a potential security hole.) | |
82 | When sending mail to a remote site, ``mail'' invokes the ``rmail'' | |
83 | command at the remote site. Hence you should create an ``rmail'' | |
84 | command by linking to ``/bin/mail", and ensure that ``Cmds'' | |
85 | contains an entry for ``rmail'', but not ``mail''. | |
86 | ||
87 | Note that other systems which may contact you via "uucp" | |
88 | will have to login using information that you supply. When UNIX/TS is | |
89 | delivered there is a user "uucp" (with no initial password) whose | |
90 | default shell is (and must be) "/usr/lib/uucp/uucico". If you | |
91 | wish to use "uucp" to contact other systems you will need to | |
92 | obtain username and password information from them in advance and | |
93 | to store this in "L.sys". Since the file "L.sys" contains | |
94 | sensitive information about how to access other systems which are | |
95 | willing to converse with you, it is important that the "L.sys" | |
96 | file be properly protected. You will find that ensuring a high | |
97 | level of protection is not a trivial task. As a minimum you will | |
98 | need to set correctly the permissions on the file itself, its | |
99 | parent directory and every executable "set-uid-to-root" file in | |
100 | your whole system ... and then ensure that the root password is | |
101 | secure ... as a bare minimum. | |
102 | ||
103 | The programs "uuclean" and "uulog" are provided for | |
104 | housekeeping. These should be run frequently, e.g. by "cron". | |
105 | Prototypes of procedures that may be run by "cron" are provided | |
106 | here as the files "uudemon.*". Note also that "uudemon.hr" | |
107 | starts up "uucico" to initiate transfers that have been delayed | |
108 | for some reason, or to poll passive systems for work. | |
109 | ||
110 | Some installations may wish to use both the old and new | |
111 | versions of "uucp" concurrently for a while. This will be because some | |
112 | but not all of your correspondents have made the switch from the | |
113 | old to the new. The old version is no longer supported and the | |
114 | switch should be made as soon as possible. In the interim, you | |
115 | may replace the /usr/bin/uucp (which is linked to | |
116 | /usr/lib/uucp/uucp) by a shell procedure such as: | |
117 | ||
118 | for i in $* | |
119 | do | |
120 | case $i in | |
121 | old!* | dull!* | slow!* ) | |
122 | /usr/lib/uucp/olduucp $* | |
123 | echo old uucp used | |
124 | exit;; | |
125 | esac | |
126 | /usr/lib/uucp/uucp $* | |
127 | ||
128 | (This assumes that the old version of "uucp" has been moved to "olduucp".) | |
129 | ||
130 | For further information contact D. Nowitz (PY 6120) or | |
131 | J. Lions (MH 5667) or U. Arazy (MH 7659). |