Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site codas.UUCP Path: utzoo!watmath!clyde!bonnie!akgua!akguc!codas!mikel From: mikel@codas.UUCP (Mikel Manitius) Newsgroups: net.bugs.usg Subject: Re: bug in tty driver? Message-ID: <130@codas.UUCP> Date: Thu, 3-Oct-85 19:32:33 EDT Article-I.D.: codas.130 Posted: Thu Oct 3 19:32:33 1985 Date-Received: Mon, 7-Oct-85 03:49:19 EDT References: <1251@hcrvx1.UUCP> Organization: AT&T Information Systems (SDSS) - Orlando Lines: 42 > Description: > > The following combination of events seems to cause reads of a tty to return > EOF (VAX System V, Rel 2.0, Version 2; but may apply to your system as well): > > 1) type a character, then backspace > 2) have your terminal set into raw mode, then back to canonical mode > > This problem arises (for example), if I type vnews, then n^H, and vnews > decides I have no news. > > Prove it: > > Place the following text in a file called "foo". > sleep 10 > : remember previous settings > x=`stty -g` > stty raw > stty $x > > Now type: > sh foo > x^H > After 10 seconds, your shell will exit. This applies to both the tty driver > and the sxt driver. > Ron Williams > utzoo!hcrvax!hcrvx1!ronald I have tried this on my 3B2 5.2 2.0, it does not throw generate an EOF for me, however it does create other problems: After running foo, when I type a character, it is not echoed, the next time I type it, I get a bell, and the procedure repeats itself, when I try to type different characters, I get just bells, only when I generate some activity on the keyboard (ie: typing many characters per second) do they begin to echo. This is quite interresting. -- ======= Mikel Manitius ==----===== AT&T ...!{ihnp4!}codas!mikel ==------===== Information Systems (305) 869-2462 ===----====== SDSS Regional Support AT&T-IS ETN: 755 =========== Altamonte Springs, FL My opinions are my own. =======