On Mon, Aug 15, 2016 at 4:10 AM, J. Roeleveld <jo...@antarean.org> wrote: > > The ones created by genkernel or dracut always need a few iterations before > they work semi-reliably and are not flexible enough. > I have 2 disks in my laptop. Both are encrypted using LUKS and the same > passphrase. Neither genkernel nor dracut have the intelligence to ask me once > and try the key on both, only asking for a 2nd key when the provided one > doesn't work for both. > > I ended up writing my own, which has proven more reliable and stable. The > reduced size also makes maintenance less of an issue. >
Nothing wrong with this if you know what you're doing. Dracut is designed to be one-size-fits-all with a lot of logic to figure out what your system needs to boot. It is also somewhat dependent on a correct fstab. Don't take that for granted: the kernel doesn't look at fstab at all when mounting root, and neither do most of the other tools, so if your root partition isn't correctly defined in fstab you might never know it and dracut will get confused. If nothing else once it does have it correctly mounted it will read fstab and then mess it up when it re-mounts root per "your" instructions. If you just need to tweak dracut behavior you may be better off with a dracut module. They're just shell scripts and pretty simple to write. That lets you tweak something at some point during boot without having to build the entire thing yourself. And since it uses udev it is fairly robust against things like adding a drive and now the kernel re-letters everything. If you tweak it to use the same password for all drives I wouldn't be surprised if upstream accepts the patch... -- Rich