I hadn't screwed up with lilo in many, many moons. But guess what I did this am.....forgot to run lilo after a kernel upgrade. Couldn't find my latest Slackware disc either. Bah.
BUT - I do have an old instance of Slackware on another partition. Booted to that and fixed up lilo.conf, then ran lilo and booted back to my new partition and ran lilo again. Took maybe 10 minutes to get back to normal. I almost deleted that old Slackware for non use. Its use I found out is to protect my old arse!
I do that too whenever I need to fix something like that, but I have multiple distros on multiple drives - Slackware, Arch, CachyOS, Fedora, and Debian (and GhostBSD). Mostly I'm in the first three. I haven't used Lilo in years, one of the first things I do on a new Slackware install is install and setup Grub.
