Bug#383600: behaviour of update-initramfs -u has changed, only updates latest kernel initrd

[Eduard Bloch <edi@gmx.de>]

#include <hallo.h>
* Michael Biebl [Fri, Aug 18 2006, 01:07:34PM]:
> Eduard Bloch wrote:
> > #include <hallo.h>
> > * Michael Biebl [Fri, Aug 18 2006, 10:26:53AM]:
> >> I suggest to revert to the old behaviour and make "-u" update all
> >> installed kernels. Atm I have to specify each kernel separately vi -k to
> >> update them all.
> > 
> > Why should one update _all_ initramfs images when beeing interested in
> > only single one? 
> 
> Why should I be only interested in only a single one? If I install e.g.

Because usualy it gets executed when you install a kernel-image package?

> the uswsusp package (which has to update the initrd because it has to
> install a resume binary there) I'd expect the package to work with all
> kernels I have installed not only a single one.

That's orthogonal to the regular usage of mkinitramfs. uswsusp package
is the right one to add a call to update ALL initrds.

> In addition only the newest kernel installed is updated, which is very
> confusing imho. If it all, it should update the initrd of the currently
> running kernel.

Does not confuse me at all. The package beeing installed cares about its
own setup. Not more, not less. No need to touch non-involved packges.

> > This also increases the risk for breaking ALL WORKING
> > initramfs images in the case where a new bug in initramfs-tools appears.
> 
> As you already said, if it's a bug in initramfs-tools, it should be

Don't reintepret my statements to something you like. Risk for a fact
!= known fact. If there is a known bug in initramfs-tools which is fixed
with an upgraded version, then it could and should be executed for all
initrds.

Eduard.

-- 
<Joey> umh... zwischen gestern und heute haette eigentlich auch locker
	noch ein Tag reingepasst...
<youam> Joey: diesen tag nennt man "nacht" und kennzeichnet ihn durch
	das fehlen des gelben balls im blauen raum