On Wed, Apr 3, 2013 at 4:34 AM, Raymond Wooninck
On Wednesday 03 April 2013 12:13:50 Andrey Borzenkov wrote:
What exactly is dracut needed for there? Or to put it the other way around what's missing from mkinitrd?
A maintainer. I for one would like to see us switching to dracut yesterday.
I'm not sure I understand, what lacks maintainer - mkinitrd or dracut? In case of dracut I'd tentatively volunteer to (co-)maintain it.
Hi Andrey,
As Frederic already indicated mkinitrd seems to be the one missing the maintainership. However we would welcome any help we can get to really exploit dracut and to have it replace mkinitrd in openSUSE 13.1.
The main devel package is in the Base:System repository and currently Christian Rodriguez and I are maintaining it. A couple of months ago I took it upon me to get dracut into openSUSE, but unfortunately due to an work overload at my normal job, I am not able to spend that much time on it.
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. The key for me was that I had to refer to the (very good!) Fedora documentation to add: rd.auto to the kernel/initrd commandline. I still can't get dracut to decrypt my swap partition. I am interested in helping out with a transition to dracut. Besides testing, what might be the best way for me to contribute? -- Jon -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org