В Wed, 3 Apr 2013 08:19:00 -0500
Jon Nelson
We are tracking the releases and the package is in openSUSE Factory. I guess the main thing to do is to validate if all angles are covered when using dracut to generate the inird instead of mkinitrd. This would be specifically with LUKS/crypt support.
I use LUKS for root and - while it took me a few tries - I do have a working system that boots just fine with either dracut or mkinitrd-built initrds.
May be I miss something obvious but I recently did several test installations on LVM on encrypted container and did not have a single issue except lack of out-of-the box support in grub2 (it is a single parameter in /etc/default/grub). But it was definitely *not* a problem in initrd or boot.crypto. And if you use separate /boot (which installer forces anyway) then it works out of the box using vanilla installer. So may someone explain what are these problems with crypto mentioned here? I could imagine problem with additional file systems but then it is out of scope for mkinitrd/dracut. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org