On Tue, Jun 18, 2013 at 12:35:23PM -0400, Gary Dale wrote: > On 18/06/13 10:35 AM, Lars Noodén wrote: > >On 06/18/2013 05:03 PM, Dirk wrote: > >>you are clearly talking out of your ass... a boot loader doesn't need > >>features other than loading the kernel... > >> > >>what crucial work do you do with the features of grub? spreadsheets? > >>presentations? project managing? or do you play it like a text adventure > >>figuring out what the grub rescue console actually does? > >> > >>*primitive is the best thing about lilo*... if you don't realize that > >>then you don't care if a part as stupid as the boot loader doesn't > >>work... because you have alternatives to linux.. > > > >Having just involuntarily bumped into the grub rescue console, I can say > >that LILO was much easier to work with and to figure out. In the case > >of grub I eventually had to give up and nuke the MBR from the rescue > >mode of the installation CD. grub is complex, grub2 more so. > > > >Regards, > >/Lars > > > > > > When GRUB came out, it's best feature was that you didn't need to > update it every time you installed a new kernel - something that > LILO required. With GRUB2, we're back to needing to update the boot > loader when the kernel changes.
Actually, you don't NEED to update GRUB2 when the kernel changes. If you use the /vmlinuz and /vmlinuz.old symlinks you can still have a pair of menu entries that point to them. However, doing so loses some user-friendliness (i.e. the ability to see what kernel you're booting. It could be argued, though, that many users neither care nor know whether they want to boot "Debian with Linux 3.8.0" or "Debian with Linux 3.8.0". They want Debian 7.0, with possibly "Debian 7.0, fallback kernel").
signature.asc
Description: Digital signature
