Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ORION.MC.DUKE.EDU!bet
From: bet@ORION.MC.DUKE.EDU (Bennett Todd)
Newsgroups: gnu.bash.bug
Subject: Re: key binding/stty character conflict
Message-ID: <8907131644.AA03096@orion>
Date: 13 Jul 89 16:44:07 GMT
References: <8907122237.AA10749@comp.vuw.ac.nz>
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 19

I used to use ecsh on our systems; I am gradually converting users over
to bash. The biggest problem with ecsh is that it constantly did major
tty setting and resetting, and this tickled a bug in the SunOS 4.x tty
driver, which locked the console fatally requiring rebooting when
someone typed ^S. The situation, as far as I could tell, was that due to
output buffering ecsh would get the tty back while the previous
command's output was draining. The ^S would have been processed, leaving
the tty's output frozen, and ecsh would change the tty settings leaving
no character capable of restoring output. I was unable to find anything
that could be done either on the console or from another machine via
rlogin to unlock the console. I tried unsuccessfully to modify ecsh to
prevent it from having this problem. Bash doesn't currently have this
problem. 

Bash might not necessarly acquire this problem if you modify it as Ray
requested; it is a possibility to beware however.

-Bennett
bet@orion.mc.duke.edu