Quote:
Originally Posted by Jonathan183 Interesting problem ... when you try Code: chroot /mnt/hda1 /bin/bash
and get the permission failure what is the full output you get for mount?
what commands had you used before chroot? |
Here's the output of
mount:
/dev/hda4 on / type ext3 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/hda3 on /home type ext3 (rw)
/dev/hda1 on /mnt/hda1 type ext3 (rw,noexec,nosuid,nodev)
none on /mnt/hda1/proc type proc (rw)
/dev on /mnt/hda1/dev type none (rw,bind)
As you can see, I've got proc and dev mounted as specified. I mounted them first, then tried to chroot. Last night I thought it might be an X problem but I tried again just now from a virtual console and got the same results. I'm pretty sure it isn't the chroot that's failing, it's bash. I can't run
any of the Gentoo commands, not even ldconfig, which is statically linked. Well, like Mike says, I can use Ubuntu to get round that but it irritates me when things happen that don't seem to have a rational explanation - especially in Linux!