On 11 Jan, Lyle Chapman wrote:
> I have put in what I
> think are the right params in grub, but I get a parsing error.
Personally, although grub is more powerful and flexible than lilo, I
think it suffers from a major, major flaw: after changing the grub
config file, there's no way to run grub to test whether that config
will work. You just have to cross your fingers and reboot and hope for
the best.
At least running /sbin/lilo tells you instantly if you've got
/etc/lilo.conf correct or not.
<rant>
And if you do happen to find yourself in the invidious position of
having a hosed grub config (e.g. if you started installed SuSE 9.2 and
then realised you'd forgotten to note down the pre-existing partition
mount points, and abort the installation continuing with setting the
partitions, only to discover that it hosed your existing grub boot
config) - then even knowing that you have workable Linux kernels on an
un touched partition somewhere, if you could just remember where they
were - well, that's tough, since grub has insufficient built in
commands to let you find them, since it has no equivalent of "ls" in
its toolset. The closest you can come is test for the existence of a
named file ("find") or use tab completion
Oh, wait, wait, that's how you do an ls: you remember the string
"root (<TAB>" and "kernel /<TAB>" and you can work your way through the
filesystems. A little harder to remember than a command with a name
(like "ls" or "find"), but what can you expect from people who prefer
GNU "info" to Unix man pages?
</rant>
luke
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
