+Changes to the UUCP Implementation
+.PP
+The demands placed on UUCP networking,
+and new technology,
+have prompted several changes and improvements to the UUCP software.
+Such things as low cost, autodial, autoanswer, high speed modems,
+and the availability of X.25 and TCP/IP as carriers,
+have encouraged new facilities in UUCP to be developed.
+.PP
+The following areas have been changed between the 4.2 and 4.3 BSD releases.
+.IP \(bu 3
+General fixes and performance improvements.
+.IP \(bu 3
+Administration control facilites.
+.IP \(bu 3
+Modem and autodialer support has been extended.
+.IP \(bu 3
+New protocols for different transport media.
+.IP \(bu 3
+Security enhancements.
+.SH
+Fixes and performance improvements.
+.PP
+Many of the fixes related to portability considerations,
+and improvements as provided by the USENET community.
+.PP
+The \fIsitename\fR truncation length as been extended to 14 characters from
+the original 7 characters.
+This maintains compatibility with the current System V version of UUCP.
+.PP
+An effort as been made to improve the overall performance of the UUCP system
+by organizing its workload in a more sensible way.
+For example the program \fIuucico\fR will not resend files it has already sent,
+when the files are specified in one ``C.'' file.
+.SH
+Administration and control facilities.
+.PP
+There is a new program, \fIuuq\fR,
+to give more descriptive information on status of jobs in the UUCP spool queue.
+It also allows the user to delete spooled requests,
+still in the queue.
+.PP
+In the past, on large UUCP sites,
+the spool directory could grow large with many files
+within the ``/usr/spool/uucp'' directory.
+To help the UUCP administrator control the system,
+a number of subdirectories have been created to easy this congestion.
+.PP
+The system status ``STST'' files are kept in a subdirectory.
+.PP
+Corrupted ``C.'' and ``X.'' files,
+that could not be processed,
+are placed in the ``CORRUPT'' subdirectory,
+instead of just exiting.
+.PP
+Lock files may be kept in a subdirectory,
+``LCK'',
+if desired.
+.PP
+If an ``X.'' request fails,
+the notification is returned to the originator of the request,
+instead of ``uucp'' on the previous system.
+.PP
+There is a new \fIsystem\fR file, ``L.aliases'',
+that may be used when a site changes it's name.
+All the utilities,
+\fIuucp\fR, \fIuux\fR, \fIuucico\fR, etc.,
+all check ``L.aliases''.
+.SH
+Modem and autodialer support:
+.PP
+In a short period of time,
+there has been a big increase in the transfer rates and capabilites
+that are being provided with modern modems.
+Most modems will allow several combinations of baud rate,
+and provide autodial and autoanswer facilites as well.
+.PP
+Most sites will have but a few modems,
+they are therefore a precious resource an effort has been made to use them
+to maximum potential.
+The \fIuucico\fR program now has code to dial in and out on the same device,
+if that modem as both autodial and autoanswer provision.
+.PP
+There is a new dialing facility \fIacucntrl\fR that has been built to handle
+some of the changes in modem technology.
+There are a number of new modems and autodialers that can now be handled.
+Here is a list of some of the new devices:
+Racal Vadic 212,
+Racal Vadic 811 dialer with 831 adaptor,
+Racal Vadic 820 dialer with 831 adaptor,
+Racal Vadic MACS 811 dialer with 831 adaptor,
+Racal Vadic MACS 820 dialer with 831 adaptor,
+Dec DF112,
+Novation,
+Penril,
+Hayes 2400 Smartmodem,
+Concord Data Systems CDS 224,
+ATT 2224 2400 baud modem.
+.PP
+It now correctly does the closing hangup sequence.
+.PP
+It will try up to TRYCALLS to dial a site
+instead of one try for each dialer.
+.SH
+New protocols for different transportation mediums
+.PP
+The UUCP software has had provision for different protocols
+to be used in the sending and receiving of data,
+but originaly only one was implemented
+and this is the one that is largely used throughout the UUCP community.
+The standard `g' protocol,
+has a maxium throughput around 9000 baud,
+regardless of the physical medium.
+The use of checksums and the like are of little use when the protocol
+is bounded within another protocol such as TCP or X.25.
+It is a waste of time and cpu resources to calculate CRC's
+when the carrier already provides error free transmissions.
+The UUCP system did not utilize LAN's and high speed carriers well.
+Two new protocols have been added
+to provide for efficient use of new carrier facilities.
+The protocols now available to UUCP are:
+.DS
+`t' protocol, optimised for use on TCP/IP carriers.
+`f' protocol, optimised for use on X.25 PAD carriers.
+`g' protocol, standard UUCP protocol used for dialup or hardwired lines.
+.DE
+.PP
+The `t' protocol presumes an error free channel,
+and is essentially the `g' protocol without the checksumming and packetizing.
+Other changes where necessary to run UUCP on top of a TCP carrier,
+the code could not do ioctl's on sockets that are connections to remote hosts.
+.PP
+The `f' protocol relies on flow control of the data stream.
+It is meant for working over links that can be guaranteed to be errorfree,
+specifically X.25/PAD links.
+A checksum is calculated over a whole file only.
+If a transport fails the receiver can request retransmissions.
+This protocol uses a 7-bit datapath only,
+so it may be used on carriers that are not 8-bit transparent.
+.PP
+As well as adding new protocols,
+the existing `g' protocol code has been cleaned up.
+.SH
+Changes to \fIuucico\fR
+.PP
+You can specify a maximum grade to send either
+on the command line using (-gX)
+or in the ``L.sys'' file
+.DS
+Any/C|Evening will only send grade C,
+.DE
+usually mail,
+or higher during the day and will send everything in the evening
+See Figure 5.
+.SH
+UUCP System files.
+.PP
+The \fIsystem\fR files in the ``/usr/lib/uucp'' directory can contain comments,
+by putting a `#' as the first character on a line.
+Lines may be continued by placing a `\\' as the last character of a line.
+This is helpful in making an understandable \fIL.sys\fR file.
+.PP
+Some new options are available to \fIuucico\fR, these include:
+.RS
+.IP -R
+This flag reverses \fIuucico\fR role.
+Let the remote system be master first instead of being the slave.
+.IP -L
+\fIuucico\fR will only call ``local'' sites.
+Local sites are those sites having one of
+\fBLOCAL\fR, \fBTCP\fR or \fBDIRECT\fR in the CALLER field of ``L.sys''.
+.RE
+.PP
+If ``/etc/nologin'' is present,
+usually created by \fIshutdown\fR,
+\fIuucico\fR and \fIuuxqt\fR will gracefully exit,
+instead of getting killed off when the system goes down.
+.PP
+Does an exponential backoff on retry time if call fails
+instead of always waiting the default 5 minutes.
+The default may be overridden by adding ",TIME" to the time field in ``L.sys''.
+.DS
+ucbvax Any,2
+.DE
+will use a default retry time of 2 minutes.
+.PP
+If \fIuucico\fR receives a SIGFPE while running,
+it will toggle debugging on and off.
+.PP
+It will not send files to remote system if the remote system
+is returning an out of temp space error.
+.PP
+Add ABORT sequence to the expect/send sequence so it does not have
+to wait for timeout if cannot get through a dataswitch.
+See figure X.
+This example will only call noao in the evening.
+It will expect nothing,
+then wait 1 second (\ed),
+and then send a carriage return.
+Look for CLASS, then send NOAOUUCP.
+From then on,
+if it sees the word Down before finishing logging in,
+it will hang up immediately.
+In the mean time,
+it looks for GO,
+when received,
+delay 1 second and then send a CR.
+Look for ``ogin:'', etc.
+This abort sequence is useful
+if you must go through a dataswitch to get to the computer.
+.PP
+The time field in the ``L.sys'' file now handles
+"Evening" and "Night" in addition to:
+.DS
+Any, Mo, Tu, We, Th, Fr, Sa, Su.
+.DE
+Evening and Night are defined to be:
+.DS
+Evening = Wk1700-0800|Sa|Su
+Night = Any2300-0800|Sa|Su0800-1700
+.DE
+.PP
+The expect/send code now handles '\e' sequences:
+.RS
+.IP "s"
+indicates a space
+.IP "d"
+indicates a delay 1 second
+.IP "r"
+indicates a carriage return with no linefeed
+.IP "b"
+indicates a break
+.IP "c"
+indicates do not send a CR after these characters
+.IP "xxx"
+the octal character xxx (e.g. \es == \e040
+.RE
+.PP
+The file \fIL-devices\fR now handles "chat" scripts,
+to help get through local port selectors and smart modems.
+This helps keep \fIL.sys\fR readable but increases functionality.
+See figure 4.
+.PP
+For compatibility with System V UUCP system,
+in the Date fields of ``L.sys'':
+.DS
+`|' was changed to `,' (| is supported, but not encouraged)
+`,' was changed to `;' (to allow , to be the date seperator)
+.DE
+.PP
+For Honey DanBer compatibility,
+the Grade flag is now passed as:
+.DS
+-vgrade=X
+.DE
+instead of the old -pX
+.PP
+You can specify a time for the expect send sequences with ~ instead
+of getting the default MAXMSGTIME.
+For example:
+.DS
+system Any ACU 1200 1234567 ogin~20--ogin~10--ogin user password pw
+.DE
+will look for ``ogin'' for 20 seconds,
+then send CR,
+look for ``ogin'' for 10 seconds,
+send a CR and look for ``ogin'' for MAXMSGTIME seconds
+.PP
+Added code to support GTEs PC Pursuit service.
+It's mainly the handling of the dialback they use.
+.PP
+Added time "NonPeak" for Tymnet/Telenet services that charge lower rates
+from 6pm-7am M-F and Sat & Sun.
+.SH
+Security enhancements.
+.PP
+Running \fIuucico\fR with debugging turned on,
+requires ``L.sys'' to have read access.
projects / unix-history / commitdiff