Date: Sun, 8 Dec 1996 09:44:21 +0100 (MET) From: J Wunsch <j@uriah.heep.sax.de> To: uhclem@nemesis.lonestar.org Cc: freebsd-bugs@freefall.freebsd.org Subject: Re: bin/1037 Message-ID: <199612080844.JAA29114@uriah.heep.sax.de> In-Reply-To: <199612072310.PAA14876@freefall.freebsd.org> from Frank Durda IV at "Dec 7, 96 03:10:02 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
As Frank Durda IV wrote: > [0]As above, replacing telnetd with the one shipped with 1.1.5.1 fixes > [0]this problem. > > [1] wollman@lcs.mit.edu then said: > [1]This is because the TELNET in 1.x had a broken LINEMODE. 2.x has a > [1]working LINEMODE, but this is sometimes not what programs expect. > > Hmm, this logic isn't obvious to me. It seems the goal is to have > the telnet session provide functionality identical of what you get > at the console or at any serial/dialup port. I don't understand > why "working" means to break what seems to be a basic compatibility > function of character I/O. Read the RFC about telnet linemode (RFC 1184) and its background and intentions, then you know why it behaves different than e.g. a serial console line. As Garrett (or was it Bruce?) pointed out, you are free to not use linemode, either by turning it off at the telnet prompt, or by running ``stty -extproc'' on the server side (which notifies telnetd to go into character-at-a-time mode). What might be useful (why isn't it already there?) is a command-line option on the telnet client to turn off linemode negotiation. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612080844.JAA29114>