Ryan Tsai wrote:
Au contreir (sp?) - as far as I understand what LILO does is to record the actual block numbersYeah, 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.
LILO embeds the config file in its bootsector, while GRUB needs to load it
everytime it boots. So I guess that means LILO only needs access to the
config file when its installed, whereas GRUB needs to remember where the
config file is physically.
of the file's data in its boot sector then access it directly (not via the filesystem). GRUB, on the
other hand, know about filesystem formats and how to translate file paths to blocks on the file
system. That's why you don't have to update GRUB every time you change the configuration -
GRUB just knows where to look for the files it needs under the filesystem and read them
directly at boot time.
That's also why I'd expect GRUB not to have a limit on the file's place in the partition.
But I'm no expert - my main experience with GRUB is on an 80Mb ReiserFS filesystem.
I don't think GRUB has such limitation, I have my /boot patition about 50Ditto. Just have a backup plan in case you lock yourself out of your own disk (e.g.
gigs into the disk and GRUB works fine.
I'd say give it a go, doesn't hurt trying.
have a LiveCD/RescueCD which can read your HD handy).
Yeah you're right about grub-install, didn't see that one.
Ryan
--Amos
-- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html