On Thu, 13 Apr 2006 20:18:59 +0200 maximilian attems wrote: > 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. What in the above requires initramfs-tools to force-update ramdisks? When I install a ramdisk tool I _may_ want to use it for my default kernel, but possibly only as a fallback option for yaird. When I install evms I _may_ want to use it immediately, but possibly not. Ramdisks belong to the local admin, not to the ramdisk generator package. It is wrong to mess with them unconditionally! - Jonas -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er n_r: http://www.shibumi.org/eoti.htm
Attachment:
pgphcHhfpgVCj.pgp
Description: PGP signature