On Mon, 2006-09-04 at 14:34 -0500, Seb wrote: > I'm trying to create a chroot in a AMD64 Debian system, following a how-to > posted from http://www.debian-administration.org/articles/356. However, > I'm not comfortable messing with my main system config files (like > /et/ld.so.conf), which the how-to suggests. For other reasons, I also had > the ia32-libs package installed, so I thought I could avoid messing my > /etc/ld.so.conf and thought that the chroot should be able to use the > libraries from ia32-libs. I can see I already have the /lib/ld-linux.so.2 > link. Is this sensible? if not, is there some alternative?
This is so you can use the 32-bit libraries in the 64-bit system. It is unnecessary if you do all your 32-bit stuff in the chroot. > I'm also not sure about what and how things should mounts be specified in > /etc/fstab. The how-to above says to use this: > > /home /var/sid-386-chroot/home none bind 0 0 > /tmp /var/sid-386-chroot/tmp none bind 0 0 > proc /var/sid-386-chroot/proc proc defaults 0 0 This looks right to me; it is what I have done. > I've been advised to also mount /etc read-only, in order to avoid copying > files around (very error prone) to the chroot. Other how-tos also > recommend mounting /dev, so people are using very different ways to > install a chroot. Can somebody please suggest what the best method is? I wouldn't mount /etc to the chroot, and /dev hasn't ever been necessary. Someone else needs to help out here... In that HOWTO, _I_ would skip 1.3, 1.4, and 1.5. The only changes I make to the real system is to /etc/fstab. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
