tty000 'n' uucico (ph0 TCSBRK kills tty000)

[Michael Ditto]

In article <14 at sialis.Sialis.MN.ORG> rjg at sialis.mn.org (Robert J. Granvin) writes:
>The instant you send the BREAK,
  [ to the OBM ]
>                            tty000 goes out to lunch.  All output to
>the device is buffered, and not sent, and input is not accepted from
>the terminal.  If you don't send a BREAK, the terminal remains
>(apparently) unaffected.
>
>The remote terminal will 'return to life' when the call is complete
>and uucico starts up _another_ call.

I have seen this; it's quite easily reproducable.  In particular, I
often log in via tty000 and "cu" out via ph0.  If I type ~%break to
cu, my terminal (on tty000) freezes (no input or output).  A bit of
experimenting revealed that SETTING the stty settings of ph0 will
cause tty000 to return to life (i.e., going to the console and running
"stty 1200 < /dev/ph0" makes everything work again).

I don't think I knew about the bug when I was covered by warranty,
and my current solution is just to avoid typing ~%break.

>I can't believe that no one else out there has run across this, and I
>find it hard to believe that AT&T has no knowledge of it (even though
>the person(s) on the phone may not have, though).

If you think it will help, I'll call the hotline and complain.

-- 
					-=] Ford [=-

	.		.		(In Real Life: Mike Ditto)
.	    :	       ,		ford at kenobi.cts.com
This space under construction,		...!ucsd!elgar!ford
pardon our dust.			ditto at cbmvax.commodore.com