Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel!munnari.oz.au!news.hawaii.edu!ames!elroy.jpl.nasa.gov!usc!snorkelwacker.mit.edu!bloom-picayune.mit.edu!news.mit.edu!raeburn From: raeburn@cambridge.cygnus.com (Ken Raeburn) Subject: Re: 386BSD: Dinky little socket(?) bug -- ^V as escape character? In-Reply-To: sim@cory.Berkeley.EDU's message of 30 Jul 92 11:35:45 GMT Message-ID: <RAEBURN.92Jul30145602@cambridge.cygnus.com> Sender: news@athena.mit.edu (News system) Nntp-Posting-Host: cambridge.cygnus.com Organization: Cygnus Support, Cambridge MA References: <sand.712454840@milton> <1992Jul30.011650.5292@pasteur.Berkeley.EDU> <1992Jul30.081047.16575@news.tu-graz.ac.at> <1992Jul30.113545.23558@pasteur.Berkeley.EDU> Date: Thu, 30 Jul 1992 18:56:23 GMT Lines: 15 In article <1992Jul30.113545.23558@pasteur.Berkeley.EDU> sim@cory.Berkeley.EDU (Peng-Toh Sim) writes: To get the "correct" behaviour, we can fix 386bsd or screen etc. or both!!! I think 386bsd should be fixed such that when ICANON is not set, IEXTEN functions are ignored. This still follows the above definition and yet will work well in practice because other POSIX programs that uses RAW mode will "forget" to turn off IEXTEN anyway. "Fixing" only 386bsd will get you the desired behavior, but the program would still be wrong. The "screen" code should be fixed to turn off IEXTEN, regardless of whether the kernel is changed. Leaving 386bsd as is will help catch other broken programs, so they can be repaired as well. I think that's reasonable, but I expect some aren't willing to put up with the annoyance.