Bug#444364: please stop rewriting all the initrds

[dean gaudet]

On Fri, 28 Sep 2007, martin f krafft wrote:

> also sprach dean gaudet <dean at arctic.org> [2007.09.28.0230 +0100]:
> > it is EXEPTIONALLY DANGEROUS to replace EVERY SINGLE initrd when mdadm is 
> > installed/upgraded.
> 
> Please STOP SCREAMING and look at the existing bugs before you reply
> new ones. 2.6.3-1 will not do this anymore. You could help testing:

i did search but obviously didn't search for the right things, alas.

> > but no this time i'll have to resort to a recovery CD.
> 
> There are backups of the initrds. Plus, I tend to make sure your
> initrd will not get corrupted.

unfortunately it happened on a box where i upgrade on unstable frequently 
but reboot infrequently... so the .bak had already been overwritten.  (in 
the end it was my own configuration problem which resulted in the initrd 
being unbootable).

i think i might make some @reboot cron job which saves away a copy of 
/boot/initrd-`uname -r` after a successful boot, so i always have 
something to fall back on.

thanks
-dean