On 02/06/10 11:50 AM, Boyd Stephen Smith Jr. wrote:
> On Wednesday 02 June 2010 10:47:26 H.S. wrote:
>> On 02/06/10 11:19 AM, Tom Furie wrote:
>>> On Wed, Jun 02, 2010 at 11:10:09AM -0400, H.S. wrote:
>>>>> H.S. wrote:
>>>>>> Now, after doing this, I still have this kernel in /boot:
>>>>>> $> ls -1 /boot/*trunk*
>>>>>> /boot/vmlinuz-2.6.32-trunk-686
>>>
>>> Since they are stale files, not associated with any installed package,
>>> why not simply delete the files?
>>
>> Yes, that is one option. But how do I make sure I got all the stale
>> files? If a package is known by apt, I can use "dpkg -L <package name"
>> to see which files are installed and where. In this case, however, dpkg
>> cannot tell me that.
>
> cruft can.
>
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
And besides these, cruft also listed tons of /boot/grub files as
unexplained.
--
Please reply to this list only. I read this list on its corresponding
newsgroup on gmane.org. Replies sent to my email address are just
filtered to a folder in my mailbox and get periodically deleted without
ever having been read.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/hu62es$pa...@dough.gmane.org
