Dracut looks to replace the initramfs patchwork

Posted Feb 5, 2009 9:43 UTC (Thu) by climent (guest, #7232)
Parent article: Dracut looks to replace the initramfs patchwork

Not only every basic feature will have to be implemented in dracut, but also every extended feature (read cryptofs/LUKS) will have to be. For all the distros.

The day that happens we have a replacement. Otherwise, I want to be able to boot from my encrypted partitions when i use my laptop.

Dracut looks to replace the initramfs patchwork

Posted Feb 5, 2009 14:22 UTC (Thu) by nix (subscriber, #2304) [Link] (1 responses)

Indeed. I have systems here that boot normally, systems here that need to
mount LVM, systems that mount LVM-atop-RAID, one bizarre system that has a
root filesystem on RAID-atop-LVM (!), a couple of systems whose RAID
arrays are assembled over the network block device, and one that never
actually mounts a root filesystem atop the rootfs but does all its work
from there.

Booting can be arbitrarily complicated: it must, no matter what, remain
possible to *replace* whatever standardized initramfs framework goes
upstream, because nothing will ever cope with all the utterly bizarre
corner cases.

Dracut looks to replace the initramfs patchwork

Posted Feb 5, 2009 16:19 UTC (Thu) by iabervon (subscriber, #722) [Link]

You'll never be able to make a single initramfs image that works for everything, but I don't see any reason that a single initramfs project couldn't have a per-kernel build process that would take a set of instructions on mounting the root filesystem as part of its configuration and generate an initramfs image that does it.