On Saturday 31 May 2008 21:09:52 Alexander Meinke wrote: > However, I think this problem is [neither] mount nor bash related. Try > > # mount -tproc proc /mnt/rescue/proc > # mount -obind /dev /mnt/rescue/dev > # chroot /mnt/rescue /bin/bash
That's almost exactly what I did. To be certain, I tried it with the full paths you suggest, but of course I got the same result. > Especially check the permissions of /mnt/rescue/bin/bash and /bin/bash. > They should be at least 0755. As I said the first time, the permissions are the same on both, thus: # ls -l bin/bash -rwxr-xr-x 1 root root 772120 2008-05-29 17:29 bin/bash # ls -l /mnt/rescue/bin/bash -rwxr-xr-x 1 root root 772120 2008-05-29 17:29 /mnt/rescue/bin/bash As they're the same size, I assume they're the same version - but they could have been compiled with different USE flags. I'll look into that. [Later: on remerging bash in the main system the flags look perfectly innocent, and I can't imagine having set them differently on the rescue system; but I will look next time I boot the rescue system*.] > ... rebuild the package that include 'chroot' so that right permissions > are set for the program and its libs. The permissions are right already, but I'll do that anyway. > I hope this helps in any way and excuse me for that bad English. I've no difficulty following you :-) Thanks also to the others who've helped. Wolf's idea wouldn't help me because I want a separate system that will boot even if the main one won't. It's on a different physical disk as well. * Is there a way to find out what USE flags a package has been compiled with when it's not the current system but a rescue system mounted temporarily in it? Anyone? -- Rgds Peter -- gentoo-user@lists.gentoo.org mailing list
