Date: Mon, 25 Feb 2008 14:24:12 +0100 From: Alexander Leidinger <Alexander@Leidinger.net> To: cali clarke <xorquewasp@googlemail.com> Cc: freebsd-hackers@freebsd.org Subject: Re: Anybody have a patch for pdksh derivatives, for jails? Message-ID: <20080225142412.hqn9n6kagw0w0w4o@webmail.leidinger.net> In-Reply-To: <5a08be760802241042x2cd93d63of5787a744e745fe5@mail.gmail.com> References: <5a08be760802241042x2cd93d63of5787a744e745fe5@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting cali clarke <xorquewasp@googlemail.com> (from Sun, 24 Feb 2008 =20 19:42:01 +0100): > 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. You don't give enough info. I assume you talk about a login into the =20 host system and then doing a "jexec X pdksh" to login into a jail. The =20 important question here is the how you login into the host system. > I wondered if anybody had patched their *ksh to workaround > this problem? So far it is not clear that the bug is within the *ksh. It may be also =20 the case that the problem should be fixed somewhere else. Bye, Alexander. --=20 It's easier to get forgiveness for being wrong than forgiveness for being right. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080225142412.hqn9n6kagw0w0w4o>