Path: utzoo!attcan!telly!lethe!torsqnt!jarvis.csri.toronto.edu!mailrus!uwm.edu!gem.mps.ohio-state.edu!usc!ucsd!ucbvax!ucbarpa.Berkeley.EDU!edward
From: edward@ucbarpa.Berkeley.EDU (Edward Wang)
Newsgroups: comp.dcom.modems
Subject: Re: Bizarre crosstalk causes crashes
Keywords: low noise cable rec wanted
Message-ID: <31452@ucbvax.BERKELEY.EDU>
Date: 22 Sep 89 20:07:12 GMT
References: <43@octel.UUCP>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: edward@ucbarpa.Berkeley.EDU.UUCP (Edward Wang)
Organization: University of California, Berkeley
Lines: 14

In article <43@octel.UUCP> mike@octel.UUCP (Michael D. Crawford) writes:
>getty displays "Octel Communications Sun UNIX 4.0.1"
>getty recieves something like "mkkoummu{;pkwww", then execs "login
>mkkoummu{;pkwww".  . . .

That's the reason for the one second delay in the Version 7 getty.
When fixing the wiring is beyond your control, add pf#1 to your gettytab.
Things are much worse once somebody logs in (and unplugs the terminal,
or switches the line away from it, which people do all too often here),
echo is turned on and the line starts to bounce characters back and forth
at full baud rate.  What fun!

Anyway, this is my pet peeve.  TTY drivers should have input
limiting when echo is on.