On Sun, 2008-02-24 at 19:42 +0100, cali clarke wrote: > Hi. > > pdksh and derivatives (openbsd ksh, mirbsd mksh etc) all have > the same "bug" with regards to jails. On all of my systems, trying > to start *ksh in a jail results in a message that /dev/tty could > not be opened (device busy) and that the shell will not have > job control. For some reason, this makes pretty much any > curses or screen editor fail to run. > > Note that also, this problem does NOT occur if you use ssh > to enter the jail as I believe ssh handles tty allocation in > advance. > > I wondered if anybody had patched their *ksh to workaround > this problem? > > I've had a look at the sources myself and... ugh. The insides > of a unix shell are not something I particularly want to spend > much time examining...
Running something like 'jexec 1 /bin/sh' won't allow you to allocate a tty. If instead you enable sshd inside the jail, and ssh into the jail, sshd will allocate you a tty, and everything will work normally. HTH
signature.asc
Description: This is a digitally signed message part
