Hi, > BTW: years and several (B)LFS ago, I could happily run X clients in > chroot and get the windows on the server running on the host system. > This no longer works: xterm Xt error: Can't open display: :0.0 (of > course I did xhost +localhost; even xhost + doesn't help). Now I have to > run an X server on a second machine, just to be able to unpack the JDK > sources.
You certainly can still do what you're wanting to; what's changed is the defaults in the SSH server config. There are a number of machines here that are "headless" and only accessible via X. There are a number of different ways to set up your sshd; it's common to set it up so each app <thinks> it's DISPLAY is something like "localhost:10.0" but in reality that app is running on a machine 3 floors down. See "man sshd_config & search for X11UseLocalhost for an explanation as to what's going on there. It's also possible to set the machine up so it's "completely open" and someone else can cause windows to appear on your display (which was one of my favorite practical jokes). "man ssh_config" and "man sshd_config" will give you the details; you probably are going to want to focus on ForwardAgent, ForwardX11, ForwardX11Trusted, X11Forwarding - the names of the parameters are, fortunately, prettty obvious. You'll notice that sshd has a wealth of configuration parameters and capabilities, including port forwarding and tunnelling. It's even possible to pre-exchange keys and automate login from one machine to another. Can't really pass along much more than that as your sshd config files have to be set up appropriately for your network, too. A word of caution; while a lot of these features can be handy, you can also end up with one or more security holes, some of which are pretty big. But then, "xhost +" isn't for untrusted networks either. - Larry -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
