[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: trying to understand/purge linux-image-2.6.32-trunk-686

On Wednesday 02 June 2010 11:55:55 H.S. wrote:
> I tried cruft on my /boot partition and got more than I bargained for.
> It listed the files related to the package in question and some others
> too. They are:
>         /boot/System.map-2.6.32-trunk-686
>         /boot/config-2.6.32-trunk-686
>         /boot/initrd.img-2.6.17-2-486.bak
>         /boot/initrd.img-2.6.26-2-686
>         /boot/initrd.img-2.6.26-2-686.bak
>         /boot/initrd.img-2.6.32-3-686
>         /boot/initrd.img-2.6.32-trunk-686
>         /boot/initrd.img-2.6.32-trunk-686.bak
>         /boot/vmlinuz-2.6.32-trunk-686
> I understand the files with 'trunk' in them, but the rest I am not why
> they are there since I have the following kernels installed:
> $> dpkg -l linux-image* | grep ^i | awk '{print $2}'
> linux-image-2.6-686
> linux-image-2.6.26-2-686
> linux-image-2.6.32-3-686
> linux-image-686

Then you can (or at least should be able to) confirm that the files listed are 
not "owned" by those packages.

They may still be important files for your system, and the {pre,post}inst 
routines may have created them.  However, they are unknown to the dpkg 
database, which is why cruft identifies them.

I'm sure the cruft maintainer / upstream would like your assistance in making 
cruft better.

> And besides these, cruft also listed tons of /boot/grub files as
> unexplained.

Are they owned by a package?
Boyd Stephen Smith Jr.           	 ,= ,-_-. =.
bss@iguanasuicide.net            	((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy 	 `-'(. .)`-'
http://iguanasuicide.net/        	     \_/

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply to: