Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!zaphod.mps.ohio-state.edu!usc!snorkelwacker!bloom-beacon!POSEUR.JPL.NASA.GOV!earle
From: earle@POSEUR.JPL.NASA.GOV (Greg Earle - Sun JPL on-site Software Support)
Newsgroups: comp.windows.x
Subject: Re: X-windows DISPLAY environment variable
Message-ID: <9007042000.AA08476@poseur.jpl.nasa.gov>
Date: 4 Jul 90 20:00:02 GMT
References: <26900123@m.cs.uiuc.edu>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: Sun Microsystems - JPL on-site Software Support
Lines: 27

In xpert/comp.windows.x article <26900123@m.cs.uiuc.edu> Alan Carroll writes:
>Re: Setting DISPLAY across telnet/rlogin
>
>Both telnet and rlogin preserve the TERM variable (at least in my experience -
>maybe it fails in some locations). You can use this fact to pass additional
>information along by setting TERM to be something like "real_term@display",
>and then having the .login / .profile pick look at TERM, and if it's of this
>form, extract the information, set DISPLAY, and fix TERM to be just
>"real_term" again. rlogin and telnet can then be aliased/functioned to set
>TERM appropriately just before executing the real binary.

If you can find Dave Borman's recent posting to TCP-IP/comp.protocols.tcp-ip,
the new release of the pre-4.4BSD telnet/telnetd client and server now
contains support for negotiation of the XDISPLOC telnet option, as long as
the `login' program on the telnetd server end supports the `-p' flag to
preserve the environment variables.  I suspect that as this version is
widely distributed and implemented, it will make this issue a moot point.
(I presume that setting DISPLAY from XDISPLOC will be rather straightforward)

--


-- 
	Greg Earle			| "This is Kraft.  It uses a blue box.
	Sun Microsystems, Inc.		|  This is Stouffer's.  It uses red.
	earle@poseur.JPL.NASA.GOV	|  The choice is yours."
	earle@Sun.COM			|  Pretty damn convincing argument, eh?