On (03/11/06 13:12), michael wrote: > On Fri, 03 Nov 2006 17:24:23 +0000, Peter Hillier-Brook wrote > > Following updates I find I have several redundant kernels and > > corresponding entries in GRUB. Is there a preferred method of > > removing these, once I have established stability with later > > versions, or is my first thought of 'rm'ing the relevant files and > > editing menu.lst good enough? > > I have a similar problem: > > I have an etch box with custom compiled kernels from kernel-package. > I've installed a bunch with dpkg -i and used apt to remove them. > But dpkg still shows them in the the list of packages. > For example: > > host:~# dpkg --get-selections |grep linux-image > linux-image-2.6.16-2-k7 purge > linux-image-2.6.17 purge > linux-image-2.6.17-2-486 purge > linux-image-2.6.17-2-686 install > linux-image-2.6.17-2-k7 purge > linux-image-2.6.17etalon-k7 purge > > Is there a way to remove the packages marked "purge"?
Caveat: do not purge the kernel you're running.... that said: $ uname -a //will show you the kernel you're running $ sudo aptitude install linux-image-2.6.17-2-686 when finished reboot, $ uname -a //will show you the kernel you're running $ sudo aptitude purge linux-image-2.6.16-2-k7 linux-image-2.6.17 linux-image-2.6.17-2-486 linux-image-2.6.17-2-k7 linux-image-2.6.17etalon-k7 $ sudo aptitude clean //to clean the package cache apt(itiude) will sort the menu.lst Regards Clive -- www.clivemenzies.co.uk ... ...strategies for business -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
