Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!agate!howland.reston.ans.net!Germany.EU.net!wizard.pn.com!news1.channel1.com!news1.channel1.com!not-for-mail From: mcgovern@user1.channel1.com (Brian McGovern) Newsgroups: comp.os.386bsd.questions Subject: Telnet problems (FBSD 2.0) Date: 23 Dec 1994 00:07:05 -0500 Organization: Channel1 Communications Lines: 27 Message-ID: <3ddltp$64s@user1.channel1.com> NNTP-Posting-Host: user1.channel1.com To: hackers@freebsd.org Here is one for all you FreeBSD 2.0 Hackers. Since I've switched to FreeBSD 2.0, I've had some very interesting problems when telnetting to FreeBSD boxes, either with my DOS/Windows telnet, or another 2.0 system. With a Dos/windows client, I normally see each CR being treated as a CR/LF sequence, causing the equivelent of two enter key presses, which doesn't work with vertain commands well (like rm'ing a file taht needs confirmation, it chooses the default for me). Output of the same generates two LFs (and I'm assuming two CRs). Under FreeBSD 2.0, however, I see a different scheme form up. This time, carrige returns get displayed at ^M during gets() and related functions,but work fine at the command prompt. Operations from the console to the local machine always work fine. Console to other machines via telnet are as above. Rlogin from a console to another machine seems to be ok. Haven't tried it froma DOS PC. Rebooting the offending 2.0 system seems to work for awhile, but the 3rd or fourth session causes it to screw up again (or should I say 3rd or 4th login. There can be any number of sessions). I think its in telnetd, but after mulling through the sources, I can't find anything obvious. Any suggestions? -Brian