Removing old kernels that are not actually installed

[NoOp]

On 04/26/2012 02:32 PM, William Scott Lockwood III wrote:
> On Thu, Apr 26, 2012 at 4:21 PM, NoOp <glgxg at sbcglobal.net> wrote:
>> On 04/26/2012 02:00 AM, Colin Law wrote:
>>> I know how to remove old kernels by finding them in synaptic an
>>> uninstalling them but I have a machine that has been through numerous
>>> upgrades over the years and seems to have ended up with a number of
>>> kernels in /boot that are found by update-grub but according to
>>> synaptic are not installed.  For example:
>>>
>>> ~$ ls /boot/*2.6.27*
>>> /boot/abi-2.6.27-11-generic         /boot/System.map-2.6.27-11-generic
>>> /boot/config-2.6.27-11-generic      /boot/vmcoreinfo-2.6.27-11-generic
>>> /boot/initrd.img-2.6.27-11-generic  /boot/vmlinuz-2.6.27-11-generic
>>>
>>> Can I just remove all these files?
>>>
>>> Colin
>>>
>>
>> Yes - as long as you are no longer using 2.6.27-*
> 
> The proper way to remove them is better of course - use apt-get or
> aptitude to remove the packages that installed them.

"upgrades over the years and seems to have ended up with a number of
kernels in /boot that are found by update-grub but according to
synaptic are not installed."

If they are not shown as installed in Synaptic, then I doubt that they
can be removed by apt-get or aptitude.

> 
> Hint: dpkg -l | grep linux
> 

It's probably helpful to point out that installed packages are preceded
by 'ii'.