There are several source modifications that may be required before the system programs are compiled. These relate to the directories used during compilation, the directories used during execution, and the local uucp system-name.
The four directories are:
The names given in parentheses above are the default values for the directories. The italicized named lib, program, xqtdir, and spool will be used in the following text to represent the appropriate directory names.
There are two files which may require modification, the makefile file and the uucp.h file. The following paragraphs describe the modifications. The modes of spool and xqtdir should be made ``0777''.
Change the program and the spool names from the default values to the directory names to be used on the local system using global edit commands.
Change the define value for MYNAME to be the local uucp system-name.
There are several make variable definitions which may need modification.
will compile the entire system. The command
will copy the commands to the to the appropriate directories.
The programs uucp, uux, and uulog should be put in ``/usr/bin''. The programs uuxqt, uucico, and uuclean should be put in the program directory.
There are four files which are required for execution, all of which should reside in the program directory. The field separator for all files is a space unless otherwise specified.
This file contains entries for the call-unit devices and hardwired connections which are to be used by uucp. The special device files are assumed to be in the /dev directory. The format for each entry is
where;
The line
would be set up for a system which had device cul0 wired to a call-unit cua0 for use at 300 baud.
This file contains entries with location abbreviations used in the L.sys file (e.g. py, mh, boston). The entry format is
where;
The line
would be set up so that entry py7777 would send 165-7777 to the dial-unit.
It is assumed that the login name used by a remote computer to call into a local computer is not the same as the login name of a normal user of that local machine. However, several remote computers may employ the same login name.
Each computer is given a unique system name which is transmitted at the start of each call. This name identifies the calling machine to the called machine.
This file contains user accessibility information. It specifies four types of constraint;
Each line in the file has the following format
where;
The constraints are implemented as follows.
The line
allows machine m to login with name u and request the transfer of files whose names start with ``/usr/xyz''.
The line
allows the ordinary user dan to issue commands for files whose name starts with ``/usr/dan''.
The lines
allows any remote machine to login with name u, but if its system name is not m, it can only ask to transfer files whose names start with ``/usr/spool''.
The lines
allows any user to transfer files beginning with ``/usr'' but the user with login root can transfer any file.
Each entry in this file represents one system which can be called by the local uucp programs. The fields are described below.
The name of the remote system.
This is a string which indicates the days-of-week and times-of-day when the system should be called (e.g. MoTuTh0800-1730).
The day portion may be a list containing some of
or it may be Wk for any week-day or Any for any day.
The time should be a range of times (e.g. 0800-1230). If no time portion is specified, any time of day is assumed to be ok for the call.
This is either ACU or the hardwired device to be used for the call. For the hardwired case, the last part of the special file name is used (e.g. tty0).
This is the line speed for the call (e.g. 300).
The phone number is made up of an optional alphabetic abbreviation and a numeric part. The abbreviation is one which appears in the L-dialcodes file (e.g. mh5900, boston995-9980).
For the hardwired devices, this field contains the same string as used for the device field.
The login information is given as a series of fields and subfields in the format
where; expect is the string expected to be read and send is the string to be sent when the expect string is received.
The expect field may be made up of subfields of the form
where the send is sent if the prior expect is not successfully read and the expect following the send is the next expected string.
There are two special names available to be sent during the login sequence. The string EOT will send an EOT character and the string BREAK will try to send a BREAK character. (The BREAK character is simulated using line speed changes and null characters and may not work on all devices and/or systems.)
A typical entry in the L.sys file would be
The expect algorithm looks at the last part of the string as illustrated in the password field.