Xref: utzoo comp.protocols.tcp-ip:12543 comp.windows.x:25625
Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!rutgers!mephisto!prism!gs26
From: gs26@prism.gatech.EDU (Glenn R. Stone)
Newsgroups: comp.protocols.tcp-ip,comp.windows.x
Subject: Re: Magic cookies over Telnet
Keywords: Telnet, options, XDISPLOC, X11, magic cookie
Message-ID: <12461@hydra.gatech.EDU>
Date: 12 Aug 90 16:43:36 GMT
References: <2432@dino.cs.iastate.edu>
Followup-To: comp.protocols.tcp-ip
Organization: Dead Poets Society
Lines: 26

In <2432@dino.cs.iastate.edu> hascall@cs.iastate.edu (John Hascall) writes:

> What I was thinking of doing was passing the magic-cookie [DISPLAY variable]
>to the remote-end through another Telnet option.  Has anyone else thought
>about/done this (I didn't find a RFC)?  Does any one have any comments
>on the good/badness of this?

This smells more like what rlogin does...  Telnet doesn't need to be passing
environment variables, since I might (and do, occasionally) be telnetting
to a VMS machine, or (angels and ministers of grace defend us) a CYBER...

Rlogin's Bugs section in TFM already says it should propogate more of the
environment... how much more is open to debate, but it already says that
rows and columns are supported on some systems.... hmmm.. p'raps there
is a need for xrlogin, to propogate such neat things as color, stty settings,
etc?  I don't think all this info needs to be in the standard package, 
simply because the vast majority of what's going on out there is still being
done on damn-3a's and Real PC's with a serial port out the back. (you wouldn't
believe the number of old 4.77mHz boxes still being pounded on every day on
this campus... but I digress.)

If the env-variable passing is already there, it shouldn't be too hard to
extend rlogin into xrlogin, and drop One More File into ..../contrib...

-- Glenn R. Stone
gs26@prism.gatech.edu