Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!rex!ben
From: ben@rex.uokhsc.edu (Benjamin Z. Goldsteen)
Subject: Re: Telnet terminal problems w/386BSD
Message-ID: <C6owI2.E9x@rex.uokhsc.edu>
Date: Sat, 8 May 1993 04:01:14 GMT
Reply-To: benjamin-goldsteen@uokhsc.edu
References: <PHILIP.34.736789260@shark.stmarys.ca> <1sek5a$mfm@lobster.sid.mcet.edu>
Organization: Health Sciences Center, University of Oklahoma
Lines: 78
johnj@lobster.sid.mcet.edu (John Jackson) writes:
>Philip Howard (Computer Services) (PHILIP@shark.stmarys.ca) wrote:
>: In article <1sa5rc$9r9@lobster.sid.mcet.edu> johnj@lobster.sid.mcet.edu (John Jackson) writes:
>: >From: johnj@lobster.sid.mcet.edu (John Jackson)
>: >Subject: Telnet terminal problems w/386BSD
>: >Date: 6 May 1993 04:57:16 GMT
>: >Hi:
>: >
>: > I have 386BSD 0.1 patch level 0.2.1. Telnet'ing in to the 386BSD
>: >box can be dicey.
>: I'm not experiencing EXACTLY these same problems, but an old TELNET from
>: Clarkson installed on our Novell system fails to connect at all (no
>: login prompt) and NCSA telnet connects properly 1/3 of the time. The rest of
>: the time NCSA echos everything locally in two annoying ways...
>: login: philip
>: philip
>: password: secretword
>: secretword
>: %
>I have also seen this happen using the latest NCSA telnet. Emacs also wiggs
>out. I just found CUTCP and it doesn't seem to have this problem. However,
>in talk CUTCP can't backspace - just ^H's show up and the delete key
>appears to do nothing. Also, Ctrl-C and Ctrl-Z don't work. ALT-Y, CUTCP's
>interupt process macro *does* seem to do what Ctrl-C should eb able to do.
>: --or--
>: login:
>: philip
>: password: /* no echo, as it should be */
>: secretword
>: %
>: I've "solved" the problem by using Kermit or by using TELNET from a
>: different system like VAX/VMS Multinet. On my Mac (I'm "bi" =|-) I found
>: that NCSA Telnet would lock up when it scrolled quickly through several
>: screenfuls of text eg; % man -c something. The connection wouldn't drop, but
>: the session would hang. Again, there were so many variables I just gave up
>: trying to isolate the problem.
>: I'm currently at patchlevel 0.2.3, but I haven't checked the Mac problem
>: since 0.1
What Telnet is being used in these BSD's? I havn't managed to get
either 386BSD or NetBSD running on my PC, yet, but I hope to soon. On
the other hand, I have spent a few minutes here and there debugging
telnet's.
Most of the problems I have had with telnet'ing is due to bad
telnetd's. I like the telnet package that is on
ftp.uu.net:/pub/networking/applic/telnet*
[that isn't the only place to get it, but it is the one I can remember
off hand]
I havn't used that version, but I have worked with an earlier version.
Implementing it on our DG/UX 4.3 machine solved most telnet problem
(except for those that were due to bad Telnet's...Telnet is a somewhat
complicated protocol...the fact that many implementations are poor makes
me a little dubious of OSI). If 386BSD/NetBSD uses the Net/2 telnet I
think you (the BSD community) ought to re-port this one back (some
SVR4ism creeped in -- the author works for Cray...and UNICOS is based on
System V). I would do it if I had a better PC.
BTW, you may still notice a problem with ^C -- some Telnet's convert ^C
into Interrupt Process -- which, according to author of the above
mentioned Telnet package, isn't correct unless you are in LINEMODE. The
trick is to disable the feature...
--
Benjamin Z. Goldsteen