Bug#362064: udev: udev tries to write to an installed, working initrd without asking

[maximilian attems <maks@sternwelten.at>]

severity 362064 wishlist
stop 

On Thu, 13 Apr 2006, Steve Langasek wrote:

> severity 362064 serious
> quit

i don't agree with the severity of this bug.
i'll present my arguments below.

been busy the last 2 weeks and see the other bug was escaleted too.
i disagree with the severity of #358397 too.
 
> On Thu, Apr 13, 2006 at 10:29:06AM +0200, maximilian attems wrote:
> 
> We've had this conversation before on IRC, and I don't believe there is any
> evidence that this is the case.  Until you can show some, I regard this bug
> as release-critical.

we had a short exchange about it, i don't remember any conclusion.

regarding the severity i may cite yourself #353809
-- snipp
"Nothing in this report has described actual breakage.  If using
initramfs-tools to generate initramfs images prevents the system from
booting, that is indeed a critical bug, but that's not the bug that Jonas
filed." 
--

by design initramfs-tools needs that:
a) allows each hook to add it's boot device detection scripts
if you want evms root you simply install evms. 
thanks to it's initramfs hook you get evms root support.

b) prevents races in install order:
mkinitramfs-kpkg run by newer linux-image when not _all_ hooks are
yet unpacked, so latest updated initramfs has all content.
thus _only_ latest initramfs gets updated.

c) allows moving around root
currently due to lvm2+mdadm not having yet the initramfs-tools hooks
the user does have to regenerate the initramfs when moving to lvm2
root. as the initramfs was generated before lvm2 installed.

regards

-- 
maks

ps added jbailey on cc as i may have forgot details about his
   implementation thoughts.