Quote:
Originally Posted by GazL
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.