possible bug in chroot from klibc?

[jordipujolp at gmail.com (Jordi Pujol)]

busybox is the current version in testing,

apt-cache policy busybox
busybox:
  Installed: 1:1.10.2-1
  Candidate: 1:1.10.2-1
  Version table:
 *** 1:1.10.2-1 0
        990 http://ftp.de.debian.org testing/main Packages
          9 http://ftp.ch.debian.org unstable/main Packages
        100 /var/lib/dpkg/status
     1:1.1.3-4 0
        300 http://ftp.ch.debian.org stable/main Packages

and klibc also,

apt-cache policy klibc-utils
klibc-utils:
  Installed: 1.5.12-1
  Candidate: 1.5.12-1
  Version table:
 *** 1.5.12-1 0
        990 http://ftp.de.debian.org testing/main Packages
          9 http://ftp.ch.debian.org unstable/main Packages
        100 /var/lib/dpkg/status
     1.4.34-2 0
        300 http://ftp.ch.debian.org stable/main Packages


El Saturday 09 August 2008 21:51:12 Jordi Pujol va escriure:
> Hello,
>
> testing the chroot command into live-initramfs I have experienced that does
> not interpret correctly the PATH
>
> Start a live system with break=live-bottom, and try this:
>
> # the PATH is correct
> (initramfs) echo $PATH
> /sbin:/usr/sbin:/bin:/usr/bin
>
> # using chroot from klibc gives an error,
> (initramfs) chroot /root which debconf-communicate
> execve: No such file or directory
>
> # using chroot from busybox is correct,
> (initramfs) busybox chroot /root which debconf-communicate
> /usr/bin/debconf-communicate
>
> testing more...
>
> Regards,
>
> Jordi Pujol