Re: DISPLAY=Windows-Machine:0.0 ?
From: Dances With Crows (danceswithcrows_at_usa.net)
Date: 07/04/03
- Next message: Christopher Browne: "Re: Question about merits of transaction filesystems in relation to the FS corruption"
- Previous message: Todd Knarr: "Re: DISPLAY=Windows-Machine:0.0 ?"
- In reply to: Ian Gil: "DISPLAY=Windows-Machine:0.0 ?"
- Next in thread: Ian Northeast: "Re: DISPLAY=Windows-Machine:0.0 ?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 4 Jul 2003 03:10:05 GMT
On Fri, 04 Jul 2003 02:22:07 GMT, Ian Gil staggered into the Black Sun
and said:
> Is it possible to direct an X display to a windows machine?
Explain what you mean more fully. I can tell you that it's possible to
make an X client display on any machine that's running an X server. An
X client is almost any GUI program running under a Unix-like system;
popular examples include xterm, xeyes, mozilla, and mplayer.
> A few years ago I don't beleive this was possible but I'm wondering if
> now there might be some windows program I can run to capture an
> X-windows display.
Capture an X display? What, precisely, do you want to accomplish? I'm
going to assume you meant "How do I start X clients on a remote Unix
machine and have them display on a Windows machine". If you need to do
something like make an MPEG-1 movie of an X client, that's a whole
'nother topic.
If you want an X server that runs on 'Doze, the Cygwin folks have one.
You start the X server on your 'Doze machine, then you ssh -X into the
machine where the X client lives, then you start an X client by entering
"xterm &" into the ssh session. Commercial X servers for 'Doze also
exist, Hummingbird Exceed is popular.
If you don't want to run individual clients, but you want a full desktop
thing, you need to set up XDMCP on your Unix-like machine. The XDMCP
Howto can help with this. Then, you start the X server on the 'Doze
machine like so:
X -query remote.unix.machine
...and you should see an xdm/kdm/gdm screen running on the remote unix
machine, provided you've set up XDMCP correctly.
Another option is TightVNC Viewer on the 'Doze machine, and krfb (KDE
3.0 and below) or KDE Desktop Sharing (KDE 3.1 and up) or x0rfbserver
running on the Unix machine. This lets you connect to a running Unix
machine's X desktop, instead of starting a whole new X session. VNC is
less stateful than X, which may be an advantage. I use TightVNC all the
time; I have Windows TightVNC server running on my work machine, and KDE
Desktop Sharing running on my laptop. With "vncviewer work.machine", I
can do almost everything I could do if I were sitting at the console of
that 'Doze2K system from my home machine 11 miles away, minus cablemodem
lag. HTH,
-- Matt G|There is no Darkness in Eternity/But only Light too dim for us to see Brainbench MVP for Linux Admin / http://www.brainbench.com / "He is a rhythmic movement of the -----------------------------/ penguins, is Tux." --MegaHAL
- Next message: Christopher Browne: "Re: Question about merits of transaction filesystems in relation to the FS corruption"
- Previous message: Todd Knarr: "Re: DISPLAY=Windows-Machine:0.0 ?"
- In reply to: Ian Gil: "DISPLAY=Windows-Machine:0.0 ?"
- Next in thread: Ian Northeast: "Re: DISPLAY=Windows-Machine:0.0 ?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|