LinuxQuestions.org - is it worth booting slack with Grub?

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - is it worth booting slack with Grub? (https://www.linuxquestions.org/questions/slackware-14/is-it-worth-booting-slack-with-grub-4175523111/)

Quote:

Originally Posted by dad_ (Post 5258269)

I disagree :) Forget to run lilo after new custom kernel build(or initrd rebuild, etc) and ... new kernel is unbootable for no reason (and no way to correct it at boot prompt if you don't have a backup kernel image in place). Such 'simplicity' is a bit too much(maybe OK back in 1994, but in 2014...). BTW in case of kernel package update lilo is not run for you by the package management utility AFAIR?

I train my students to shoot themselves in the foot on purpose, so they learn how to recover an unbootable system. Just use the installation medium as a rescue system.

http://www.microlinux.fr/slackware/L...scue-HOWTO.txt

Quote:

Originally Posted by GazL (Post 5258298)

No, there's a reason. ;)

If you don't run /sbin/lilo then the new one won't be bootable, but the old one will be (unless its sectors on disk have been overwitten - in which case I have to ask what you were thinking removing the old one before you know the new one even works? Also, /sbin/lilo will warn you about any missing files or misconfiguration when you run it, not leave you to find out about them after you reboot, when its too late. That sounds exactly like a 'commit' to me.

Yep, this has been my experience. The one or two times I have forgotten to run lilo after a kernel upgrade, the worst thing that has happened is that I have to sit through a reboot that loads my old kernel instead of my new.

I have so far never had a need for Grub on Slack (or, really, on anything; but they ship with it). YMMV.