Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site down.UUCP
Path: utzoo!watmath!clyde!floyd!harpo!ulysses!allegra!princeton!down!honey
From: honey@down.UUCP (code 101)
Newsgroups: net.bugs.4bsd,net.bugs.uucp
Subject: Re: uucp VS 4.2
Message-ID: <103@down.UUCP>
Date: Thu, 29-Mar-84 22:48:56 EST
Article-I.D.: down.103
Posted: Thu Mar 29 22:48:56 1984
Date-Received: Fri, 30-Mar-84 06:56:54 EST
References: <3689@utzoo.UUCP>
Organization: Princeton Univ. EECS
Lines: 15

when typing at a low baud rate to a uart listening at a high baud rate,
the uart can miss the stop bit(s), causing a framing error, yielding a
break.  thus, if getty is set up to switch from high baud rates to low
ones, it's convenient to type the line kill character a few times to
get to the right baud rate.  one string of bits that works better than
most is 0100, which is, you guessed it, @.

there are two lessons here: use getty choices in decreasing order, and
give @ special treatment.

re-iterating john linderman's original bug report, there's also the
fact that for years, sites in the know having been passing out L.sys
login scripts containing "" @ and in:-@-in:.  who is now responsible
for changing the L.sys files on the neighboring sites?
	peter honeyman