[EMAIL PROTECTED] wrote: > Simon, > > I have both x86-64 and i686 images on one x86-64 machine. The i686 > exists in a chroot environment so that I can admin both architectures > on one machine (works great!). I share files across the images by > using mount with the "-o bind " option. Here is what I do on boot to > share parts of the x86-64 image with the i686 chroot. It can be done > for any file. You could also create hard links if the images are on > the same file system, but mine are not. > > mount -o bind /dev /var/lib/systemimager/images/aes-i686/dev >/dev/null & > mount -o bind /dev/pts /var/lib/systemimager/images/aes-i686/dev/pts > >/dev/null & > mount -o bind /dev/shm /var/lib/systemimager/images/aes-i686/dev/shm > >/dev/null & > mount -o bind /proc /var/lib/systemimager/images/aes-i686/proc >/dev/null > & > mount -o bind /proc/bus/usb > /var/lib/systemimager/images/aes-i686/proc/bus/usb >/dev/null & > mount -o bind /sys /var/lib/systemimager/images/aes-i686/sys >/dev/null & > mount -o bind /tmp /var/lib/systemimager/images/aes-i686/tmp >/dev/null & > mount -o bind /usr/portage > /var/lib/systemimager/images/aes-i686/usr/portage/ >/dev/null & > mount -o bind /usr/local /var/lib/systemimager/images/aes-i686/usr/local > > /dev/null & > mount -o bind /var/lib/systemimager/overrides > /var/lib/systemimager/images/aes-i686/var/lib/systemimager/overrides > > /dev/null & > mount -o bind /var/lib/systemimager/scripts > /var/lib/systemimager/images/aes-i686/var/lib/systemimager/scripts > > /dev/null &
cool! :-) curious: why are you sharing also /dev, /proc and /sys dirs? -Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
