Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!munnari.OZ.AU!news.mel.connect.com.au!news.mel.aone.net.au!news.mira.net.au!pumpkin.pangea.ca!www.nntp.primenet.com!nntp.primenet.com!news.mathworks.com!news-xfer.cybernet.dk!news.onramp.net!news.nkn.net!news.panther.net!nemesis!hammy!news-in.iadfw.net!news.gymnet.com!LSNT1!lsbsdi6.lightspeed.net!news3.crl.com!nntp3.crl.com!data.ramona.vix.com!sonysjc!sonybc!newsjunkie.ans.net!newsfeeds.ans.net!news-wa s.dfn.de!news.maxwell.syr.edu!cpk-news-hub1.bbnplanet.com!su-news-feed4.bbnplanet.com!news.bbnplanet.com!netapp.com!netapp.com!not-for-mail From: guy@netapp.com (Guy Harris) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Difference between rlogin and telnet Date: 30 May 1997 12:24:57 -0700 Organization: Network Appliance Lines: 24 Message-ID: <8452F5939CBDAFCB.0EB1E00D639F52B6.BE314587AA23BD99@library-proxy.airnews.net> X-Orig-Message-ID: <5mn9i9$4ts@tooting.netapp.com> References: <864993028.196308@reef.island.net.au> <5mmvkd$8kq@ui-gate.utell.co.uk> <5mn8in$dve@netaxs.com> NNTP-Proxy-Relay: library.airnews.net NNTP-Posting-Host: biceps.gymnet.com Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:42227 A. Karl Heller <heller@cdnow.com> wrote: > I believe rlogin also passes some terminal information that telnet does >not. "telnet" is a class of programs, not a program; Telnet is a protocol, but an extensible one. I.e., Telnet allows one to pass the terminal type over the wire with the terminal-type option (RFC 1091), and the terminal speed over the wire with the terminal speed option (RFC 1079), but not all Telnet clients necessarily use this option if available and not all Telnet servers necessarily make this option available. The same applies to the Telnet window size option (RFC 1073). (Now, there *is* the issue of what you send over the wire with the terminal-type option; the RFC says you should use one of the terminal types from the "Assigned Numbers" RFC, but the BSD Telnets have, at least in the past, ignored that and just sent the value of $TERM. I suppose that allows one to handle terminals not in the terminal type list, but it could cause problems if one of the systems involved doesn't happen to use the same terminal-type names that UNIX "termcap" and "terminfo" databases use....)