From: UUCP%"mark@infopiz.uucp" 23-SEP-1989 09:10:39.80 To: simpact!jeh CC: Subj: UUCP Grade Info Received: from infopiz by simpact.com (DECUS UUCP w/Smail); Sat, 23 Sep 89 09:10:36 PDT Received: by infopiz.UUCP (DECUS UUCP w/Smail); Sat, 23 Sep 89 09:06:12 PDT Date: Sat, 23 Sep 89 09:06:12 PDT From: Mark Pizzolato 415-369-9366 To: simpact!jeh Subject: UUCP Grade Info X-VMS-Mail-To: UUCP%"simpact!jeh" Jamie, What follows are the significant messages from a track of things that I was collecting since last spring. Keep me informed as you work on this. Mark From: VS3100::MARK "Mark Pizzolato 415-369-9366" 2-MAY-1989 09:07:44.09 To: UUCP%"rick@uunet.uu.net" CC: MARK Subj: Re: SunOS 4.0 graded uucp service Rick: Your recent posting (Message-ID:<53614@uunet.UU.NET>) was the last (at least as of today) part of a choppy discussion about uucp "grades". I'm working on implementing a UUCP which runs on VAX/VMS systems. This effort, formerly known as VMSNET, has officially been renamed to "DECUS uucp", and is about to be released to the world at large at the DECUS symposium next week in Atlanta. We (the developers), have not yet addressed any details regarding "grades". I would be interested in some detail about how other current uucp implementations use and interface these concepts. - What are the standard grades that are used, for mail, news batches, etc.? - Is a different grade typically used for news "ihave" and/or "sendme" messages than "normal" batched news data? - How is the work on "ONLY grade == 'n'" or "ONLY on grade <= 'n'" conveyed to uucico for a particular dialogue? - I presume this is part of the systems file entry, but how is this specified for a particular entry? - How is the concept that "I'm only working on grade <= 'n' conveyed to the remote (dialed) uucico, so he doesn't just send you everything that he may have queued up (after you have sent your stuff)? - I presume that this is part of the initial message that the master side sends in response to the "Shere" message. (i.e. "\20Smastername \0", If this is so, what are the form of these "misc flags" with respest to this "grade" type of stuff. I currently have active connections to three type other hosts (i.e. ones willing to screw around and test) SunOS 3.5, a Ridge-32 (Sys V, of I'm not sure what vintage), and others like myself. Any info regarding the above questions will be greatly appreciated. Thanks. -- Mark Pizzolato - INFO COMM Computer Consulting, Redwood City, Ca PHONE: (415)369-9366 UUCP: mark@infopiz.UUCP uunet!lupine!infopiz!mark From: VN%"lupine!uunet!rick" 3-MAY-1989 15:30:11.64 To: lupine!infopiz!mark CC: Subj: Re: SunOS 4.0 graded uucp service Received: from lupine by infopiz.UUCP (VMSnet UUCP w/Smail); Wed, 3 May 89 15:30:09 PDT Received: by lupine.UUCP (5.52/4.7) id AA13884; Wed, 3 May 89 15:27:38 PDT Received: by uunet.uu.net (5.61/1.14) id AA26225; Wed, 3 May 89 18:27:31 -0400 Date: Wed, 3 May 89 18:27:31 -0400 From: lupine!uunet!rick (Rick Adams) Message-Id: <8905032227.AA26225@uunet.uu.net> To: lupine!infopiz!mark Subject: Re: SunOS 4.0 graded uucp service I will eventually reply, but the informaiton you want is in my head and not written down anywhere. I dont have time to put it in a coherent form. From: VS3100::SYSTEM "Mark Pizzolato 415-369-9366" 15-AUG-1989 16:24:47.65 To: UUCP%"csg@pyramid.pyramid.com" CC: SYSTEM Subj: Question about UUCP startup Carl, A few weeks back you were involved in a discussion about UUCP startup in the comp.mail.uucp newsgroup. One thing you said in your message was: > The present "world authorities" on UUCP would be Peter or Rick Adams, plus a > gaggle of peripheral hangers-on like Guy Harris, Henry Spencer, and myself. > Someone at AT&T has also been hacking on BNU a lot, but has so far had the > good sense not to identify themselves. All of us are pretty busy, so if we > don't reply to your mail, it's probably because we're ignoring you. :-) Since you claim to be somewhat of a "world authority" on UUCP, I had the following question that I asked of Rick Adams, which he promised to "eventually" reply about, but obviously has been too busy. I'm working on implementing a UUCP which runs on VAX/VMS systems. This effort, formerly known as VMSNET, has officially been renamed to "DECUS uucp", and has been released to the world at large at the DECUS symposium last May in Atlanta. We (the developers), have not yet addressed any details regarding "grades". I would be interested in some detail about how other current uucp implementations use and interface these concepts. - What are the standard grades that are used, for mail, news batches, etc.? - Is a different grade typically used for news "ihave" and/or "sendme" messages than "normal" batched news data? - How is the work on "ONLY grade == 'n'" or "ONLY on grade <= 'n'" conveyed to uucico for a particular dialogue? - I presume this is part of the systems file entry, but how is this specified for a particular entry? - How is the concept that "I'm only working on grade <= 'n' conveyed to the remote (dialed) uucico, so he doesn't just send you everything that he may have queued up (after you have sent your stuff)? - I presume that this is part of the initial message that the master side sends in response to the "Shere" message. (i.e. "\20Smastername \0", If this is so, what are the form of these "misc flags" with respest to this "grade" type of stuff. I currently have active connections to three type other hosts (i.e. ones willing to screw around and test) SunOS 3.5, a Ridge-32 (Sys V, of I'm not sure what vintage), and others like myself. Any info regarding the above questions will be greatly appreciated. Thanks. -- Mark Pizzolato - INFO COMM Computer Consulting, Redwood City, Ca PHONE: (415)369-9366 UUCP: mark@infopiz.UUCP uunet!lupine!infopiz!mark From: UUCP%"csg@pyramid.pyramid.com" 16-AUG-1989 11:38:23.58 To: Mark Pizzolato CC: Subj: Re: Question about UUCP startup Received: from athertn by infopiz.UUCP (DECUS UUCP w/Smail); Wed, 16 Aug 89 11:38:18 PDT Received: by athertn.UUCP (smail2.3) id AA16656; 16 Aug 89 11:11:10 PDT (Wed) Received: by pyramid.pyramid.com (5.61/OSx5.0-890710) id AA01880; Wed, 16 Aug 89 10:36:16 -0700 Date: Wed, 16 Aug 89 10:36:16 -0700 From: csg@pyramid.pyramid.com (Carl S. Gutekunst) Message-Id: <8908161736.AA01880@pyramid.pyramid.com> To: Mark Pizzolato Cc: rick@uunet.uu.net Subject: Re: Question about UUCP startup In-Reply-To: Your message of Tue, 15 Aug 89 16:24:39 PDT <8908161246.AA20984@pyramid.pyramid.com> >Since you claim to be somewhat of a "world authority" on UUCP.... No, just one in the gaggle. :-) > - What are the standard grades that are used, for mail, news batches, > etc.? > - Is a different grade typically used for news "ihave" and/or "sendme" > messages than "normal" batched news data? The defaults are set by uux and uucp at 'A' and 'n', respectively. Anything else is pure convention, wired into people's sendmail configuration or hourly shell scripts. There are no set "standards" for grades for particular kinds of traffic. Most sites that use sendmail use grade 'C' for mail; others just take the uux default of 'A'. Pyramid and UUNet start mail at grade 'C', and back off one grade for every 2KB (or maybe 4KB) of file size. This is a feature of uux in 4.3BSD-tahoe (called "grade delta", not available in any other version of uux. At the very least, it ensures that the smallest files are transferred first. The netnews 2.11 sources set the grade for all news to 'd'. This would apply to everything -- unbatched news, batches, ihave, sendme. Everything. Here, we use different grades based on the newsgroup and on the site to which the news is being sent. Bay Area is sent at 'p'; comp.all groups at 'r', and so on; I think talk.all is sent at 'y'. :-) We pass news to our feeds at grade 'E', both ihave/sendme and the actual articles, although they could be at different grades if we chose. We don't do ihave/sendme to the leaf nodes for obvious reasons. > - How is the work on "ONLY grade == 'n'" or "ONLY on grade <= 'n'" > conveyed to uucico for a particular dialogue? Two ways. Uucico accepts a command line option, '-g', that sets the minimum grade for the present invokation of uucico. That means that only jobs at the specified grade or higher will be transferred. If the -s option is not used, and there is no work at or above the specified grade, then the site will not be called. The other way is through the time-to-call field of the L.sys file. If you want the full semantics, I'll forward you a copy of the L.sys man page. This is implemented by 4.3BSD UUCP, and by Peter Honeyman's own HDB, but *not* by the BNU UUCP that AT&T is shipping these days. We make extensive use of the -g option in our hourly UUCP script, like this: # If the time is right, poll certain sites. Note that news also does # polling; check ~news/nn.hourly. # hour=`expr "\`date\`" : ".*\(..\)\:..\:.."` # # Try to send all unfinished business. Grading is used to restrict # certain classes of transfers to certain times of day. Default for # uux is -gA and for uucp is -gn; we use -go through -gz for news. # case $hour in 0[0-7]) uucico -r1 -gn 2>/dev/null ;; 0[8-9]) uucico -r1 -gN 2>/dev/null ;; 1[0-6]) uucico -r1 -gN 2>/dev/null ;; 1[7-9]) uucico -r1 -gZ 2>/dev/null ;; 2[0-2]) uucico -r1 -gZ 2>/dev/null ;; 23) uucico -r1 -gn 2>/dev/null ;; esac Note that the grade delta we use on mail now has a significant effect: any mail below grade 'N' will not be forwarded during business hours, unless the other host calls us. Most news won't be forwarded at all -- except that we do poll all our news sites regularly. That keeps news off the lines except when we want it. > - How is the concept that "I'm only working on grade <= 'n' conveyed > to the remote (dialed) uucico? It's part of the Shostname message sent by the master: \020Shostname -Q0 -pG -vgrade=G -x9 \0 ^^^^^^^^^^^^^ The two conventions of -pG and -vgrade=G hail from different incarnations of UUCP. 4.3BSD sends and accepts both. HoneyDanBer sends and accepts only the -vgrade=G form. The slave site does *not* have to honor the grade option, and most implementations in fact do not. > I currently have active connections to three type other hosts >(i.e. ones willing to screw around and test) SunOS 3.5, a Ridge-32 (Sys >V, of I'm not sure what vintage), and others like myself. Ugh. You've picked some really terrible machines to use as models. SunOS 3.5 uses a really old and crufty UUCP that was essentially a hack by Bill Shannon when he was at Duke University. Ridge ROS is SVRV, little more than Version 7 UNIX UUCP. Get a look at Ultrix, 4.3BSD, or SVR3.2. Unfortunately, there is no way for me to get you a login on a Pyramid system to play with. From: UUCP%"csg@pyramid.pyramid.com" 17-AUG-1989 10:51:41.69 To: Mark Pizzolato CC: Subj: Re: Question about UUCP startup Received: from athertn by infopiz.UUCP (DECUS UUCP w/Smail); Thu, 17 Aug 89 10:51:31 PDT Received: by athertn.UUCP (smail2.3) id AA29415; 17 Aug 89 09:34:44 PDT (Thu) Received: by pyramid.pyramid.com (5.61/OSx5.0-890710) id AA18800; Thu, 17 Aug 89 09:24:03 -0700 Date: Thu, 17 Aug 89 09:24:03 -0700 From: csg@pyramid.pyramid.com (Carl S. Gutekunst) Message-Id: <8908171624.AA18800@pyramid.pyramid.com> To: Mark Pizzolato Subject: Re: Question about UUCP startup In-Reply-To: Your message of Wed, 16 Aug 89 11:54:41 PDT <8908170509.AA28518@pyramid.pyramid.com> L.SYS(5-ucb) L.SYS(5-ucb) NAME L.sys - UUCP remote host description file DESCRIPTION The L.sys file is consulted by the UUCP daemon uucico(8C) for information on remote systems. L.sys includes the sys- tem name, appropriate times to call, phone numbers, and a login and password for the remote system. L.sys is thus a privileged file, owned by the UUCP Administrator; it is accessible only to the Administrator and to the superuser. Each line in L.sys describes one connection to one remote host, and has the form: System Times Caller Class Device/Phone_Number [Expect Send].... Fields can be separated by any number of blanks or tabs. Lines beginning with a `#' character are comments; long lines can be continued by appending a `\' character to the end of the line. The first five fields (System through Device/Phone_Number) specify the hardware mechanism that is necessary to make a connection to a remote host, such as a modem or network. Uucico searches from the top down through L.sys to find the desired System; it then opens the L-devices(5) file and searches for the first available device with the same Cal- ler, Class, and (possibly) Device. (``Available'' means that the device is ready and not being used for something else.) Uucico attempts a connection using that device; if the connection cannot be made (for example, a dialer gets a busy signal), uucico tries the next available device. If this also fails, it returns to L.sys to look for another line for the same System. If none is found, uucico gives up. The System Field System is the hostname of the remote system. Every machine with which this system communicates via UUCP should be listed, regardless of who calls whom. Systems not listed in L.sys will not be permitted a connection. The local host- name should not appear here for security reasons. The Times Field Times is a comma-separated list of the times of the day and week that calls are permitted to this System. Times is most commonly used to restrict long distance telephone calls to those times when rates are lower. List items are construc- ted as follows: keywordhhmm-hhmm/grade;retry_time Keyword is required, and must be one of the following: Rev. Page 1 L.SYS(5-ucb) L.SYS(5-ucb) Any Any time, any day of the week. Wk Any weekday. In addition, Mo, Tu, We, Th, Fr, Sa, and Su can be used for Monday through Sunday, respectively. Evening When evening telephone rates are in effect, from 1700 to 0800 Monday through Friday, and all day Saturday and Sunday. Evening is the same as Wk1700-0800,Sa,Su. Night When nighttime telephone rates are in effect, from 2300 to 0800 Monday through Friday, all day Satur- day, and from 2300 to 1700 Sunday. Night is the same as Any2300-0800,Sa,Su0800-1700. NonPeak The discount period for Tymnet and PC Pursuit, from 1800 to 0700 Monday through Friday, and all day Saturday and Sunday. NonPeak is the same as Wk1800-0700,Sa,Su. Never Never call; calling into this System is forbidden or impossible. This is intended for polled connec- tions, where the remote system calls into the local machine periodically. This is necessary when one of the machines is lacking either dial-in or dial-out modems. The optional hhmm-hhmm subfield provides a time range that modifies the keyword. hhmm refers to hours and minutes in 24-hour time (from 0000 to 2359). The time range is permit- ted to ``wrap'' around midnight, and will behave in the obvious way. It is invalid to follow the Evening and Night keywords with a time range. The grade subfield is optional; if present, it is composed of a `/' (slash) and single character denoting the grade of the connection, from 0 to 9, A to Z, or a to z. This speci- fies that only requests of grade grade or better will be transferred during this time. (The grade of a request or job is specified when it is queued by uucp or uux.) The retry_time subfield is optional; it must be preceded by a `;' (semicolon) and specifies the time, in minutes, before a failed connection may be tried again. (This restriction is in addition to any constraints imposed by the rest of the Time field.) By default, the retry time starts at 10 minutes and gradually increases at each failure, until after 26 tries uucico gives up completely (MAX RETRIES). If the retry time is too small, uucico may run into MAX RETRIES too soon. The Caller Field Rev. Page 2 L.SYS(5-ucb) L.SYS(5-ucb) Caller is the type of device used. For complete descrip- tions of the callers, see L-devices (5). The Caller field must contain one of the following: ACU Automatic call unit or auto-dialing modem, such as the Hayes Smartmodem 1200 or Novation ``Smart Cat''. DIR Direct connect; hardwired line (usually RS-232) to a remote system. DK AT&T Datakit. (Not available on the Pyramid). MICOM Direct (hardwired) line to a Micom dataswitch. PAD X.25/X.29 PAD connection. PNET Purdue network connection. (Not available on the Pyramid.) SYTEK Sytek high-speed dedicated network connection. TCP Berkeley TCP/IP or 3Com UNET connection. These are mutually exclusive. (Berkeley TCP/IP is supported on the Pyramid.) TCP ports do not need entries in L-devices since all the necessary information is contained in L.sys. If several alternate ports or network connections should be tried, use multiple L.sys entries. The Class Field Class is usually the linespeed (baud) of the device, typi- cally 300, 1200, or 2400 for ACU devices and 9600 for direct lines. Valid values are device dependent, and are specified in the L-devices file. On some devices, the speed may be preceded by a non-numeric prefix. This is used in L-devices to distinguish among dev- ices that have identical Caller and speed, but yet are dis- tinctly different. For example, ``1200'' could refer to all Bell 212-compatible modems, ``V1200'' to Racal-Vadic modems, and ``C1200'' to CCITT modems, all at 1200 baud. On TCP connections, Class is the port number (an integer number) or a port name from /etc/services that is used to make the connection. For standard Berkeley TCP/IP, UUCP normally uses port number 540. On PAD connections, Class denotes the interface speed. This is required on external PADs (which are connected to the host via a direct RS-232 line), and may be necessary on internal PADs (which pass the interface speed on to the remote PAD). Rev. Page 3 L.SYS(5-ucb) L.SYS(5-ucb) The Device/Phone_Number Field Device/Phone_Number varies based on the Caller field. For ACU devices, this is the phone number to dial. The phone number may include the same characters as are valid for a standard AT&T UN56 Automatic Call Unit; these are mapped into the correct phone number characters for the dialer: 0 - 9 digits 0 to 9 * or : dial * (star) # or ; dial # (number sign) - or , 1 to 4-second pause (dialer dependent) = or w wait for secondary dial tone (implemented as a pause on many dialers) @ or a wait for secondary answer (not available on most dialers) ! or f flash switchhook for one second (not availa- ble on most dialers) Other characters are dialer dependent. Generally standard telephone punctuation characters (such as the slash and parentheses) are ignored, although uucico does not guarantee this. Use of the , (comma) and - (hyphen) solely for impro- ved readability is discouraged, since the pauses will slow down dialing and invoke unexpected side effects on some dialers. The phone number can be preceded by an alphabetic string; the string is indexed and converted through the L-dialcodes(5) file. For DIR devices, the Device/Phone_Number field contains the name of the device in /dev that is used to make the connec- tion. There must be a corresponding line in L-devices with identical Caller, Class, and Device fields. For MICOM and for PNET, TCP, and other network callers, Device/Phone_Number holds the true network name of the remote system, which may be different from its UUCP name. For PAD connections, Device/Phone_Number is composed of an (up to) 14 digit network address for the remote system, fol- lowed by optional facilities request codes. Each facilities request is entered as a single alphabetic character, fol- lowed by an optional numeric argument. Commas may be used after the address and between facilities requests to improve readability. The following facilities requests are understood by uucico, and may or may not be recognized by all PADs and networks: Bn Specify bilateral closed user group ID. This is a variant of the closed user group ID, described below. Rev. Page 4 L.SYS(5-ucb) L.SYS(5-ucb) C Request charging information. Ds Specify the call user data field of the call request packet. All characters following the `D' up to the end of the Phone_Number field are sent to the remote as call user data. The call user data field may not include the characters `+' or `\r' (carriage return), and is normally limited to 12 characters. If both the PAD and the network support the Fast Select facility, then the call user data field may contain up to 128 characters. F Force fast select. This extends the maximum size of the call user data field from 12 to 128 characters. Uucico automatically selects this facility if the call user data is longer than 12 characters. Gn Specify a closed user group ID. This is a two-digit access code (range 0 to 99) that may be necessary when calling certain hosts or networks, or to over- ride a default set by the network. Ns Specify the Network User Identification (NUI) string. Some networks require the NUI as a password. All characters following the `N' up to the first comma (`,') or the end of the Phone_Number field are sent to the remote as the NUI. The NUI string may not include the characters `+', '-', comma, space, '\177' (DEL), or `\r' (carriage return). The length of the string is network depen- dent. Pn Specify packet size, in bytes. The argument must be one of 16, 32, 64, 128, 256, 512, 1024, 2048, or 4096. The default and international standard is 128. Q Place a priority call. (This is only available on Datapac. Priority calling and the use of the request code Q are undefined in the X.28 standard.) R Reverse the charges (collect call). The remote sys- tem will be asked to accept the packet charges for the call. Note that on some PADs this is the default, unless a special login sequence has been entered. @n Specify the throughput class. This is an integer value from 75 to 48000 that corresponds to the actual data rate expected from the connection. It is used by the PAD and the network to estimate the amount of resources needed to maintain efficient communication. By default the throughput class is Rev. Page 5 L.SYS(5-ucb) L.SYS(5-ucb) the same as the physical line speed; there is almost never any reason to change it. (The X.28 standard request code for throughput class is D, not @. The character was changed so that D could be used to mark the start of the user data field.) Wn Specify window size. This is the number of packets that may remain unacknowledged at a time. The default is 2; the permitted range is 1 to 7. Expect/Send Scripts Expect and Send refer to an arbitrarily long set of strings that alternately specify what to expect and what to send to login to the remote system once a physical connection has been established. A complete set of expect/send strings is referred to as an expect/send script or chat script. The same syntax is used in the L-devices file to interact with the dialer prior to making a connection. The complete for- mat for one expect/send pair is: expect~timeout-failsend-expect~timeout send Expect, send, and failsend are character strings. Expect is compared against incoming text from the remote host; send is sent back when expect is matched. By default, the send is followed by a `\r' (carriage return). If the expect string is not matched within timeout seconds (default 45), then it is assumed that the match failed. The `expect-failsend- expect' notation provides a limited loop mechanism; if the first expect string fails to match, then the failsend string between the hyphens is transmitted, and uucico waits for the second expect string. This can be repeated indefinitely. When the last expect string fails, uucico hangs up and logs that the connection failed. The timeout can optionally be specified by appending the parameter `~nn' to the expect string, where nn is the timeout time in seconds. The timeout argument will be quietly ignored and treated as a normal part of the expect string if the timeout is non numeric, or if the `~' is the last character of the expect string. The ? character provides a wild-card in expect strings; it will match any character. Backslash escapes that may be imbedded in the expect or send strings include: \n Newline. \r Carriage Return. \s Space. \xxx Where xxx is an octal constant; denotes the corresponding ASCII character. Rev. Page 6 L.SYS(5-ucb) L.SYS(5-ucb) The following escapes may be used only in the send string: \b Generate a 3/10 second BREAK. \bn Generate an n/10 second BREAK. \c Suppress the implied \r at the end of the string. \d Delay for 1 second. \D Interpolate the Device/Phone_Number field. \Dn Interpolate the nth subfield of the Device/Phone_Number field. Subfields are separated by commas. \K Generate a 3/10 second BREAK (same as \b). \p Pause for about 3/10 second. \T Interpolate the phone number converted through L-dialcodes. \Tn Interpolate the nth subfield of the phone num- ber. The backslash can also be used to protect the `-', `?', and `~' characters, which have special meanings in expect strings. As a special case, an empty pair of double-quotes "" in the expect string is interpreted as ``expect nothing''; that is, transmit the send string regardless of what is received. Empty double-quotes in the send string cause a lone `\r' (carriage return) to be sent. One of the following keywords may be substituted for the send string: BREAK Generate a 3/10 second BREAK BREAKn Generate an n/10 second BREAK CR Send a Carriage Return (same as ""). EOT Send an End-Of-Transmission character, ASCII \004. Note that this will cause most hosts to hang up. NL Send a Newline. PAUSE Pause for 3 seconds. PAUSEn Pause for n seconds. P_ODD Use odd parity on future send strings. P_ONE Use parity one on future send strings. P_EVEN Use even parity on future send strings. (Default) P_ZERO Use parity zero on future send strings. Finally, if the expect string consists of the keyword ABORT, then the string following is used to arm an abort trap. If that string is subsequently received any time prior to the completion of the entire expect/send script, then uucico will abort, just as if the script had timed out. This is useful for trapping error messages from port selectors or front-end processors such as ``Host Unavailable'' or ``Sys- tem is Down.'' Rev. Page 7 L.SYS(5-ucb) L.SYS(5-ucb) For example: "" "" ogin:--ogin: nuucp ssword: ufeedme This is executed as, ``When the remote system answers, expect nothing. Send a carriage return. Expect the remote to transmit the string `ogin:'. If `ogin:' is not matched within 45 seconds, send another carriage return, and wait again. When `ogin:' is received, send it the string `nuucp'. Then expect the string `ssword:'; when that is received, send `ufeedme'.'' FILES /usr/lib/uucp/L.sys /usr/lib/uucp/UUAIDS/L.sys L.sys example SEE ALSO uucp(1C), uux(1C), L-devices(5), services(5), uucico(8C) ``SMM:9 -- UUCP Implementation Description,'' and ``SMM:21 -- A Dial-Up Network of UNIX Systems'' in the Berkeley UNIX System Manager's Manual. BUGS ``ABORT'' in the send/expect script is expressed ``backwards''; that is, it should be written `` expect ABORT'' but instead it is `` ABORT expect''. Several of the backslash escapes in the send/expect strings are confusing and/or different from those used by early Sys- tem V and HoneyDanBer UUCP. For example, `\b' requests a BREAK, while practically everywhere else `\b' means back- space. `\t' for tab and `\f' for formfeed are not implemen- ted. `\s' is a kludge; it would be more sensible to be able to delimit strings with quotation marks or escape a ` ' with a backslash. Rev. Page 8 From: DCS::JEH "Jamie Hanrahan" 30-SEP-1989 23:19:19.14 To: jeh CC: Subj: Re: Info on grade and seqno in Shere/Shostname startup sequence X-News: simpact comp.mail.uucp:146 From: honey@terminator.cc.umich.edu (Peter Honeyman) Subject:Re: Info on grade and seqno in Shere/Shostname startup sequence Date: 30 Sep 89 22:20:15 GMT Message-ID:<1989Sep30.222015.22608@terminator.cc.umich.edu> Phil Budne writes: >I think the lore is that -vgrade= is (largely) historical. honey danber uses -vgrade= -- rick was being nice to at&t. (at&t did not return the favor.) using the private sequence number is not recommended -- it has never been tested ... peter