Your message dated Sat, 26 Jan 2008 16:34:34 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#454343: chroot gives misleading error message when cannot
run dynamically linked binary
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: coreutils
Version: 5.97-5.3
Running `chroot /chroot` results in the following error message:
# chroot /chroot
chroot: cannot run command `/bin/bash': No such file or directory
Despite the fact that the binary is there.
# ls -l /chroot/bin/bash
-rwxr-xr-x 3 root root 677184 2006-12-11 16:20 /chroot/bin/bash*
I get similar error messages when trying to run false, ls, pwd,
scponly, and true instead of bash. However, if I try to run sash,
everything works perfectly.
# chroot /chroot /bin/sash
Stand-alone shell (version 3.7)
>
My suspicion is that chroot can't start bash or the other programs
because they rely on linux-gate.so.1 (according to ldd), and that
library is not in my chrooted environment. However, that's beyond the
scope of this bug.
I'm reporting this bug because the error message that chroot yields,
namely "no such file or directory" is wrong. Instead it should say
something to the effect of "Missing shared library
/lib/ld-linux.so.2", depending on the actual problem.
I am using Debian GNU/Linux (etch), kernel 2.6.18-5-486, and libc6
2.3.6.ds1-13etch2.
Am I right to report the bug here, or should I just go upstream? A lot
of people on the internet have the same problem as me that aren't
using Debian.
--- End Message ---
--- Begin Message ---
On Tue, Dec 04, 2007 at 03:27:26PM -0700, Bob Proulx wrote:
In this case the coreutils chroot utility is simply the middle man.
Yup. Closing the bug, since there's nothing that can be done about it in
chroot(8).
Mike Stone
--- End Message ---
