*BSD News Article 26286


Return to BSD News archive

Newsgroups: comp.unix.bsd
Path: sserve!newshost.anu.edu.au!munnari.oz.au!bunyip.cc.uq.oz.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!news.kei.com!nic.hookup.net!swrinde!cs.utexas.edu!uunet!spcuna!spcvxb!terry
From: terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.)
Subject: Re: Logging into BSDI BSD/386
Nntp-Posting-Host: spcvxa.spc.edu
References: <CJw7A1.2J4@news.direct.net>
Sender: news@spcuna.spc.edu (Network News)
Organization: St. Peter's College, US
Date: Thu, 20 Jan 1994 10:14:08 GMT
Message-ID: <1994Jan20.051408.1@spcvxb.spc.edu>
Lines: 22

In article <CJw7A1.2J4@news.direct.net>, jeffw@indirect.com (Jeffrey D. Wheelhouse) writes:
> I'm setting up a BSDI BSD/386 machine, and I'm having a problem with
> remote logins to the machine.  On console, it behaves, but if you 
> telnet into it, It does not always carriage return.  It linefeeds fine,
> but carriage returns are pretty sporadic.  This makes the output from
> commands like "ls -l" and "finger" pretty useless.  Does anyone know
> what might cause this, and how to fix it?

  What sort of system are you telneting in from? There are a number of
quirks in the telnet protocol which make interoperation "exciting" on
occasion. When comparing the telnet sources that have come with various
CSRG BSD releases, I see a number of changes that cause interoperability
problems. Oddly, there aren't any warnings about this in most of the
sources.

  You might try fetching the Net-2 telnet sources and compiling it on
your non-BSDI system and see if that helps. Various folks have suggested
playing with the KLUDGELINEMODE define in the BSDI telnet code as well.

	Terry Kennedy		Operations Manager, Academic Computing
	terry@spcvxa.bitnet	St. Peter's College, Jersey City, NJ USA
	terry@spcvxa.spc.edu	+1 201 915 9381