The code listing at the end of the page tells me: Code Listing 6.5: Flushing the environment during chroot # env -i HOME=$HOME TERM=$TERM chroot /mnt/gentoo /bin/bash # /usr/sbin/env-update # source /etc/profile but the "env -i" line fails in Mandriva Linux 2005: [root@chrislap gentoo]# env -i HOME=/root TERM=$TERM chroot /mnt/gentoo /bin/bash env: chroot: Invalid argument [root@chrislap gentoo]# env -i HOME=/root TERM=emacs chroot /mnt/gentoo /bin/bash env: chroot: Invalid argument Using the full path to the 'chroot' command worked: [root@chrislap gentoo]# env -i HOME=$HOME TERM=$TERM /usr/sbin/chroot /mnt/gentoo /bin/bash bash-2.05b# Perhaps the documentation should mention that. Reproducible: Always Steps to Reproduce: See above.
Works perfectly here... You should file a bug with Mandriva, not a Gentoo problem. from man env: SYNOPSIS env [OPTION]... [-] [NAME=VALUE]... [COMMAND [ARG]...]
(In reply to comment #0) > The code listing at the end of the page tells me: > > Code Listing 6.5: Flushing the environment during chroot > > # env -i HOME=$HOME TERM=$TERM chroot /mnt/gentoo /bin/bash > # /usr/sbin/env-update > # source /etc/profile > > but the "env -i" line fails in Mandriva Linux 2005 You should post that on the Mandriva Support whatever site. Perhaps this version of env only recognizes commands when they are absolutely given. Check the manpage under Mandriva.
it sounds like your user's environment is incomplete in the Mandriva host if it were setup properly, /usr/sbin would be in root's environment
Well, I'm not sure... Here's a log of some commands that show more details. chroot is in the PATH. "env" works, but "env -i" doesn't: # type chroot chroot is hashed (/usr/sbin/chroot) # chroot / /bin/bash # exit # env chroot / /bin/bash # exit # env -i chroot / /bin/bash env: chroot: Invalid argument # env | grep PATH HELPPATH=/usr/openwin/lib/help NLSPATH=/usr/share/locale/%l/%N PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin:/usr/local/bin:/usr/local/sbin
sounds like the env is probably broken ? it looks like env first clears the environ due to the -i and then searches for the command in $PATH ... this clearly fails since the -i just nuked PATH on Gentoo systems, the specified command is searched for before nuking PATH which is why you can do `env -i chroot` putting the fullpath in the docs is not a good idea because not everyone puts chroot in /usr/sbin ... some people put it in /usr/bin (like Gentoo ;])
