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

Bug#491443: marked as done (/var/lib/initramfs-tools/ not updated)



Your message dated Mon, 21 Jul 2008 10:06:42 +0200
with message-id <20080721080641.GB21220@stro.at>
and subject line Re: Bug#491443: /var/lib/initramfs-tools/ not updated
has caused the Debian Bug report #491443,
regarding /var/lib/initramfs-tools/ not updated
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
491443: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491443
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.92e
Severity: minor

Today i've changed "update_initramfs" variable from "yes" to "all".
The update-initramfs scripts seems to look at the contents of the directory "/var/lib/initramfs-tools/" to know for what image to update (it contain MD5 files, one for every initramfs created in this system). The problem is that nobody seems to care of cleaning that directory after a kernel removal, so it is full of obsolete files, that makes update-initramfs a bit noisy. On my system:

# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-2.6.25-2-686
update-initramfs: Generating /boot/initrd.img-2.6.24-1-686
/boot/initrd.img-2.6.23-1-686 does not exist. Cannot update.
/boot/initrd.img-2.6.22-3-686 does not exist. Cannot update.
/boot/initrd.img-2.6.22-2-686 does not exist. Cannot update.
/boot/initrd.img-2.6.22-1-686 does not exist. Cannot update.
/boot/initrd.img-2.6.21-2-686 does not exist. Cannot update.
/boot/initrd.img-2.6.21-1-686 does not exist. Cannot update.
/boot/initrd.img-2.6.20-1-686 does not exist. Cannot update.
/boot/initrd.img-2.6.18-4-686 does not exist. Cannot update.
/boot/initrd.img-2.6.18-3-686 does not exist. Cannot update.
/boot/initrd.img-2.6.18-2-686 does not exist. Cannot update.
/boot/initrd.img-2.6.18-1-686 does not exist. Cannot update.
/boot/initrd.img-2.6.18-1-486 does not exist. Cannot update.
/boot/initrd.img-2.6.17-2-686 does not exist. Cannot update.
/boot/initrd.img-2.6.16-2-686 does not exist. Cannot update.
#

In fact i've only the first two kernel installed.
Maybe when a kernel get purged, the removal scripts should clean its files under /var.

Regards.

Cesare.



--- End Message ---
--- Begin Message ---
On Sat, 19 Jul 2008, Cesare Leonardi wrote:

> Today i've changed "update_initramfs" variable from "yes" to "all".
> The update-initramfs scripts seems to look at the contents of the  
> directory "/var/lib/initramfs-tools/" to know for what image to update  
> (it contain MD5 files, one for every initramfs created in this system).
> The problem is that nobody seems to care of cleaning that directory  
> after a kernel removal, so it is full of obsolete files, that makes  
> update-initramfs a bit noisy. On my system:
>
> # update-initramfs -u
> update-initramfs: Generating /boot/initrd.img-2.6.25-2-686
> update-initramfs: Generating /boot/initrd.img-2.6.24-1-686
> /boot/initrd.img-2.6.23-1-686 does not exist. Cannot update.
> /boot/initrd.img-2.6.22-3-686 does not exist. Cannot update.
> /boot/initrd.img-2.6.22-2-686 does not exist. Cannot update.
> /boot/initrd.img-2.6.22-1-686 does not exist. Cannot update.
> /boot/initrd.img-2.6.21-2-686 does not exist. Cannot update.
> /boot/initrd.img-2.6.21-1-686 does not exist. Cannot update.
> /boot/initrd.img-2.6.20-1-686 does not exist. Cannot update.
> /boot/initrd.img-2.6.18-4-686 does not exist. Cannot update.
> /boot/initrd.img-2.6.18-3-686 does not exist. Cannot update.
> /boot/initrd.img-2.6.18-2-686 does not exist. Cannot update.
> /boot/initrd.img-2.6.18-1-686 does not exist. Cannot update.
> /boot/initrd.img-2.6.18-1-486 does not exist. Cannot update.
> /boot/initrd.img-2.6.17-2-686 does not exist. Cannot update.
> /boot/initrd.img-2.6.16-2-686 does not exist. Cannot update.
> #
>
> In fact i've only the first two kernel installed.
> Maybe when a kernel get purged, the removal scripts should clean its  
> files under /var.

right this is fixed in newer linux images on removal the sha1sum
disappears. for cleanup on those old non existant linux images
look into /var/lib/initramfs-tools as those kernels are not longer
around it is harmless to remove.

closing as only fixed in newer linux-images.

-- 
maks


--- End Message ---

Reply to: