On Sat, 2005-03-26 at 08:37 +1200, Rob Wood wrote: > Greetings, > Thanks to all the people who helped on this and my SuSE is now back up > and running. > > Whilst the following worked Ok, I did not understand 100% what was > happening, especially the "proc" part. > > "Then mount proc and chroot into that file system: > > # mount -t proc none /mnt/suse/proc > # chroot /mnt/suse /bin/bash" > > Any clarification would be welcome
ve only give you as much information as you need. Actually first you need to understand chroot. chroot changes the root directory to another directory, so /mnt/suse "disappears" and all you see is whats under there. /mnt/suse/ becomes / /mnt/suse/bin/ becomes /bin/ /mnt/suse/proc becomes /proc etc. One use of chroot is to get "inside" a separate file system, like you did - once you typed the chroot line you were "inside" the normal suse root filesystem, as if you had booted into suse and were sitting at a console. this is useful for installing and repairing. most installers will chroot into the target file system and then install their packages. /proc is not a virtual filesystem used to access the kernel. For example /proc/interrupts is a virtual file that tells you what interrupts are being used. A lot of linux programs including grub make use of this info. When you chroot to /mnt/suse this info is no longer available as when you are chrooted you cannot see outside /mnt/suse. So you need to mount the proc file system again as /mnt/suse/proc so it appears in the right place when you chroot. make sense? I hope so. > > Woodsey > > Nick Rout wrote: > > > > > I don't give guarantees, but yes it should be fine :-) > -- Nick Rout <[EMAIL PROTECTED]>
