On Sun, 2004-09-12 at 21:54 +1000, Ryan Tsai wrote: > Maybe grub cannot see the bind, it needs to see files in either your /boot > partition or directory physically. Which is logical when you think about it, > mount --bind is implemented by the Linux kernel, GRUB does not/cannot > require Linux to load. Is there any reason why you need to bind /home/boot > to /boot instead of just putting the files in /boot?
Yeah, the rather unfortunate fact that /boot lives about 100GB into the disk. Actually wait a moment, does GRUB have the same limitations about where /boot needs to be? I had assumed that it does because LILO does. That's something to research. re: GRUB's inability to track bind-mounts, LILO manages to untangle that particular mess. There's no reason that GRUB could not figure it out, but it may not be that smart. > Also with /sbin/grub-install you point to the actual device eg "grub-install > /dev/hde", not GRUB naming convention My understanding is that it can be either and it maps between the notations through /boot/grub/devices.map. > I'm not an expert in GRUB so I might be way off on the first point though Thanks for your help. James. -- James Gregory <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
-- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
