uucp VS 4.2

[code 101]

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:- at -in:.  who is now responsible
for changing the L.sys files on the neighboring sites?
	peter honeyman