Date: Fri, 10 Oct 1997 11:48:49 -0400 From: Ron Steele <ron@dc.infi.net> To: freebsd-questions@FreeBSD.ORG Subject: Re: Re-directing X windows to a remote machine.. Message-ID: <3.0.3.32.19971010114849.00839220@shellhost.dc.infi.net> In-Reply-To: <Pine.BSF.3.96.971010095431.28820D-100000@spiv.fnal.gov> References: <2.2.32.19971010060708.0076fce8@midwest.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At 09:58 AM 10/10/97 -0500, Richard M. Neswold wrote: >On Fri, 10 Oct 1997, Jonathan E. Lyons wrote: > >> Is there a FAQ that spells out how to re-direct a freebsd X windows >> desktop to a remote win95/nt machine? > >[ snip ] > >> Btw is this even possible??!? > >Use 'xdm'. It will manage X sessions on local and remote machines. There is >a file, /usr/X11R6/lib/X11/xdm/Xservers, that tells 'xdm' which displays to >control. If you comment out the local server and add your Win95 machine, xdm >will control the Win95 box, only. > In a slightly more generic/lower level view: X programs send their output to where ever the DISPLAY environment variable is set (barring command line intervention). To send the input/output of your X environment to another machine, set the DISPLAY variable to the IP address of the other machine, with the display number appended to it. Suppose your nt/win95 machine is at 10.10.10.2 then export DISPLAY=10.10.10.2:0 will do the trick. (ksh or bash format) You may also see this written as 10.10.10.2:0.0. The second 0 is implied in the first format. On a program by program basis, X programs all take the command line parameter "-display" with an argument in the same format as the DISPLAY environment varible. Of course you must have an X server (like Exceed) running on the Win95 box. Ron
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.3.32.19971010114849.00839220>