Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Even more useful' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Even more useful
Authored by: allard on Dec 23, '02 04:10:09AM

You can use this with OrorobosOSX or XDarwain if you want to as well. Open a terminal and launch Xnest :1 -broadcast or Xnest :1 -query {hostname}. Works like a charm!

//johan



[ Reply to This | # ]
huh?
Authored by: macubergeek on Dec 24, '02 07:09:12AM

How is this different from forwarding or blowing back X windows?



[ Reply to This | # ]
RE: huh?
Authored by: lieb on Dec 29, '02 01:07:08AM

The difference is with XDM you're getting the complete desktop from the remote system. In essence your Mac just becomes a dumb X terminal. This can be useful for accessing Suns or SGIs or similar systems. These systems can be hard to navigate unless you get the whole desktop, menu system etc.

Also in this mode you're not running a local window manager. The window manager is provided by the remote system.
I don't know that I'd use a Mac this way very much but I have setup a bunch of bare bones linux boxes that just have decent video cards and monitors that just come up with an XDM login to a remote system. Very useful in a lab if you have a good server.



[ Reply to This | # ]
RE: huh?
Authored by: berniemosler on Mar 07, '03 07:39:57PM

i used the command "X -query ip-adress -quartz" in terminal to get the desktop of a sgi in our local network. But after the start of XDarwin there are some infos in the terminal ending with "screen 0 added ...." and "screen 0 placed at X11 coordinate ..." and then nothing happened.
XDM on the sgi is running.
Did you ever use this command? Did it work for you?
I think I've done this a year ago with 10.1 and get the graphic-login screen of the sgi, but don't know the syntax anymore. I think there was an additional display option in the command but it didn't work. So, did you have some additional informations or know where to get one?



[ Reply to This | # ]
Xvnc and XDM
Authored by: steventamm on Dec 28, '02 03:33:58AM

If you don't want to bother with setting up an X terminal, you can use vnc. It's often faster than X, can use ssh tunnelling, and run cross platform (although the OSX viewers are of varying quality). If you setup it up, you can even use a java applet to connect to the machine. I have a page on how to setup xdm on OSX and Xvnc.

http://homepage.mac.com/steventamm/software/xdmvnc.html

You can get the latest version, vnc-3.3.6, from fink. You can also setup an aqua vnc server, and I use one daily, but it requires significantly more fiddling. Look at http://osxvnc.sourceforge.net



[ Reply to This | # ]
Xnest network issues
Authored by: gagern on Jun 09, '10 04:39:18AM

Took me some time to get this working on my setup. Today I finally managed to get it operational, so here are two more useful pieces of information on how to deal with some issues.

Make sure to allow Xnest in the firewall settings in the security panel of your system settings. Seems automatic firewall settings don't allow incoming connections to Xnest, causing a lot of TCP SYN packets to a listening socket but still no connection.

If you have multiple network connections (i.e. multihomed setup), give -from IP on the Xnest command line in order to set the IP address the remote machine (X client) shall use to talk to your machine (X server). Useful for VPN setups.



[ Reply to This | # ]
Xnest network issues
Authored by: jc1350 on Jul 22, '10 12:52:42PM

Thank your for this tip. I have been pulling my hair out trying to figure out why Xnest stopped working and all I got was a black screen. Using the last part of your tip (multihomed systems use -from) was the fix. I would never have thought of that.



[ Reply to This | # ]