On Wednesday 24 January 2007 15:08, M Harris wrote:
On Tuesday 23 January 2007 02:30, Stevens wrote:
It was then a simple matter of giving grub the right info so it would boot and, once booted, I changed that damned driver back. Oops!
... beauty babe...
What you just experienced is (IMHO) one of the main reasons to use grub... because it can be directed (altered) at bootup. Even though you made an error you were able to correct it easily.... grub(1) other bootloaders(0).
Yes, but many people would say there is another side to the story. (just playing devils advocate here) What if the machine you are working on is remote? and the boot (grub) wasn't set up right? If you try to reboot the machine, you'll never hear from it again until someone comes to the console. (who hopefully knows enough to fix things) The argument is that when you run lilo to do the setup, it checks for all mounted filesystems that it needs and whether there are any errors in the config. Thus you are forewarned about errors. So like everything else in linux-life, there are choices to be made. I use grub myself.... and I don't work on machines remotely. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org