1. lilo.conf and lilo.conf~
I wonder if anyone knows what's going on. I've upgraded my kernel to a
newer one, and I went to change my /etc/lilo.conf file to get it to boot
into it correctly. So far so good, the online documentation was fine.
So now I had Windows, the older kernel and the newer kernel as options. So
far so good.
Then I decided to delete the older kernel. I deleted any of the files that
had anything related to the older kernel from /boot. I then changed
lilo.conf to remove the entry for the older kernel aswell.
I restart my computer and I get the exact same boot options - Windows,
Older kernel and new kernel.
After a bit of digging, I found there was a different file called
/etc/lilo.conf~ which had my old settings to boot. So this file was
probably the one it was using to choose my boot options. Why is that?
Also, it's weird because this old lilo.conf~ file which has the old kernel
still as an option runs fine.
When I select "linux" from Lilo, it boots into Linux fine, even there is no
"/boot/vmlinuz-2.4.2-1", (not even a hidden file of that name).
Here's a copy of linux.conf~ file in all its entirity:
(the linux.conf file is the same, just without the /boot/vmlinuz-2.4.2-2
Any help appreciated,
2. "no RSA support in libssl and libcrypto"
3. lilo/lilo.conf and lba32 command line
4. Sed 3.0
5. lilo can't find /etc/lilo.conf, even though it's there
6. SCSI Performance
7. lilo.conf ignored by lilo at boot time
8. sorry.. another X question from a newbie..
9. Does LILO use any other configuration file besides lilo.conf?
10. LILO - Can I add a command line argument to /etc/lilo.conf?
11. LILO not reading LILO.CONF
12. Lilo bombs on append line in lilo.conf
13. Sample lilo.conf to solve the LILO stops at LI problem