Bug#387780: initramfs-tools: power cut during update-initramfs leaves system unbootable

[Sven Luther <sven.luther@wanadoo.fr>]

On Wed, Sep 20, 2006 at 11:00:21AM +0200, maximilian attems wrote:
> On Wed, Sep 20, 2006 at 10:17:12AM +0200, Sven Luther wrote:
> > What about backuping the currently running one ? Or keeping load of backups ? 
> > 
> > But the idea was to ask this in a debconf question at lower priorities :
> > 
> >   We have detected multiple kernels installed.
> >     current default is : ...
> >     previous default was : ...
> >     currently running kernel is : ...
> >     newly installed kernel is : ...
> >     list of available kernels :
> >       ...
> 
> nono, not debconf please.

Why not debconf ? 

> > Then the user can change either the default or backup kernels, and how many he
> > would like to save and so on.
> > 
> > ramdisk generators, bootloaders and co should share in this scheme, and
> > everything will work happily thereafter.
> 
> the idea is to backup on an update call any initramfs 
> that is older than a certain time, lets say 6h or maybe 24h
> thus not created while upgrading mdadm, udev, usplash, cryptsetup or
> so together.

This will not guarantee you that you backup the right one, and doesn't work in
coordination with the bootloaders.

> will be in 0.81 update-initramfs.

Ok, but i think it is a partial solution and misses the complete problem.

Friendly,

Sven Luther