On Tue, Jul 19, 2005 at 08:10:52PM +0800, Julian Elischer wrote: > Running a 4.x based jail on a 6 or 5 based system. > > The following ammusing (well not really) event happens if you > try to run an xdm in a 4.x jail under 5.x or 6.x to control > a remote xterminal using the 5.x supplied devfs in the jail. > > * Xdm shows a login window on the remote xterminal. (so far so good) > * User logs in. > * Xdm fires up a xterm etc. (whatever the user has in his .Xsession). > * Xterm immediatly quits because there is no /dev/tty in the jail > because the xterm has no controlling terminal having been started by > xdm which is a daemon. > * Session aborts. > > I'm guessing that xterm in 5.x was fixed to not require the existence > of /dev/tty.. Was that fix made by someone here? does anyone know if > it wasmajor? It might have been a change outside xterm (I don't recall a change with this symptom in xterm). A quick way to check would be to compile xterm from source and test that. ftp://invisible-island.net/xterm/ (at least that's what I would do ;-) > If you run it all by hand it works fine because you have a controlling > terminal and thus a 'tty' shows up in devfs. > > As an aside note.. in my older devfs 'tty' always existed but it would > return ENXIO for I/O if you didn't have a controlling terminal.. more > like happened before.. > > Anyone have any good suggestions as to how to get around this other > than to fix all the x clients..?. not all of them care about the controlling terminal -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:39 UTC