Date: Sat, 7 Dec 1996 15:10:02 -0800 (PST) From: uhclem@nemesis.lonestar.org (Frank Durda IV) To: freebsd-bugs Subject: bin/1037 Message-ID: <199612072310.PAA14876@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/1037; it has been noted by GNATS. From: uhclem@nemesis.lonestar.org (Frank Durda IV) To: wollman@lcs.mit.edu, freebsd-gnats-submit@freefall.freebsd.org Cc: uhclem@nemesis.lonestar.org Subject: bin/1037 Date: Sat, 7 Dec 96 17:06 CST [0]uhclem@nemesis.lonestar.org (Frank Durda IV) said: [0]1. Login to stock shell with stock .cshrc/.login (csh with filec [0] enabled) [0]2. cd directory where above programs reside. [0]3. Type [c][CTRL][D] [0] system should display files that match, including chars.c. NORMAL [0]4. [CTRL][C]. [0]5. Telnet self [0]6. login (same csh/filec login used in steps 1-5) [0]7. cd directory where above programs reside. [0]8. Type [c][CTRL][D] [0] system should display files that match, but instead, simply [0] echos ^D. MALFUNCTION [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. In 1.1.5.1 and earlier plus BSD 4.3 and earlier, telnet sessions behaved the same as serial and console sessions. In 2.x and later, telnet sessions behave differently than serial and console sessions. The current state is considered "working"? In my opinion, current functionality of telnet is incompatible with previous versions and non-telnet operation, and that means telnetd is broken. In my opinion, applications should not have to be written to detect and handle serial, telnet and console sessions differently. Starting with 2.x applications apparently now have to make distinctions if they are to provide an identical functional user-interface on console, serial and telnet logins. If telnet isn't broken, is anybody planning to fix csh so CTRL-D behaves as documented when csh is used from a telnet session on FreeBSD 2.x? Frank Durda IV <uhclem@nemesis.lonestar.org>|"If the choices are "right" or uhclem%nemesis@rwsystr.nkn.net | or "tidy", I'll go with | "right" every time." or ...letni!rwsys!nemesis!uhclem |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612072310.PAA14876>