How to get rid of old kernel files?

Community Support question - to convert into a paid question, click here

Lines in bold below have not yet been seen by the customer - those in blue are from the customer

Username : Date : Action : Comments [ close all ]
junderwd : 24/06/03 08:27 PM : Incident created -   I've updated my kernel from 2.4.19-16 to 2.4.19-32. All seemed ok, so I executed urpme kernel-2.4.19-16mdk-1-1mdk which I hoped would remove the old kernel files. Afterwards, rpm -qa |grep kernel reported only 2.4.19-32. BUT I found I could still boot into 2.4.19-16 from lilo, by clicking on the final stanza which I had edited prior to installing the new kernel. Locate 2.4.19-16 finds /lib/modules/2.4.19-16mdk and /lib/modules/2.4.19-16mdk/misc and nothing else. Neither kpackage, nor RpmDrake lists any kernel-2.4.19-16 files as installed. Can somebody please tell me where the old kernel is hinding in my system? Also, I edited /etc/lilo.conf to remove the last stanza (for 2.4.19-16), but lilo still lists this option and enables me to boot into the old kernel (as reported by uname -r). I hope someone will tell me how to remove the old stuff completely! junderwd
Linegod_7611 : 25/06/03 06:26 AM : Reply received -   After editing lilo, did you run '/sbin/lilo'? If so, could you provide the output of the following commands: # cat /etc/lilo # rpm -qa|grep kernel ---- Note: If this answer resolves your problem, please remember to close this incident.
junderwd : 25/06/03 06:11 PM : More info provided -   Thanks linegod. I've run /sbin/lilo and the 2.4.19-16 option has gone from my lilo boot menu.rpm -qa |grep kernel lists: kernel-source-2.4.19-32mdk, kernel-headers-2.4.18-41mdk, kernel-BOOT-2.4.19.32mdk-1-1mdk and kernel-2.4.19-32mdk-1-1mdk. Please tell me this means the old stuff from 19-16 has been wiped from my system?
Linegod_7611 : 25/06/03 08:36 PM : Reply received -   Yup, it's gone. You can also get rid of the 'BOOT' kernel also, it's not required. ---- Note: If this answer resolves your problem, please remember to close this incident.
junderwd : 26/06/03 10:14 PM : Incident closed -

---