On Wed, Jul 22, 2009 at 10:38 PM, John<johnrchamp...@columbus.rr.com> wrote: > On (20/07/09 23:49), Javier Barroso wrote: > | Hi, > | On Tue, Jul 14, 2009 at 8:47 PM, John<johnrchamp...@columbus.rr.com> wrote: > | > I've run a chroot of stable, starting with sarge, currently etch, for > several years. The relevant line in /etc/inittab has been > "8:23:respawn:/usr/sbin/chroot /[chroot] /sbin/getty 38400 tty8" and it > worked. Until the past month or so, when the chroot has consistently failed, > with the following messages: > | > > | > /usr/sbin/chroot: cannot run command '/sbin/getty': No such file or > directory > | > (repeated a number of times) > | Did you check $(ldd /sbin/getty) files inside your chroot (and the > | same /sbin/getty) are fine ? > > Hi, Javier, > > Since chroot fails, I am not sure, but there's a difference in what is > returned by ldd for /sbin/getty and /[chroot]/sbin/getty. What is > returned for the first includes " libc.so.6 => /lib/i686/cmov/libc.so.6 > (0xb7f5d000)" but the closest thing to a corresponding directory for > the chroot, /[chroot]/lib/i486-linux-gnu, is empty. Does this mean > there's an issue with the chrooted libc6? I think, you should have all files referencered in ldd /[chroot]/sbin/getty output in your /[chroot]/ environment.
I had a similar problem, because my chroot was missing /lib64 directory I don't know /lib/i486-linux-gnu directory meaning and if it is ok to have it empty. Good luck! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
