Right... so xdmcp you need to use within a nested X server (Xephyr or
Xnest). By design, that means the X server's display exists within
another window.
It doesn't make sense to have X11.app connect to another machind via
XDMCP. How would you even expect that to work from a usability
standpoint? Connecting over XDMCP and authing remotely will cause the
remote window manager to be used and not quartz-wm. That is by design
or xdmcp.
If you want to run remote applications and have them displayed locally
within quartz-wm, you need to ssh to the remote computer and tunnel
the X11 connection back over ssh.
Please explain your needs and I can hopefully explain the solution.
--Jeremy
On Nov 26, 2007, at 10:51, dp wrote:
Jeremy Huddleston wrote:
Those are by design for Xephyr and Xnest. Those run an X-server
within a window on another X server. If you don't want that, then
just run X11.app and start your applications within there.
Am I missing something here?
I think one of the objectives was to use xdmcp and for that the
solution suggested was Xephyr.
dp
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/x11-users/email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/x11-users/email@hidden
