![](https://seccdn.libravatar.org/avatar/cb2aaf49f775c94d4056311eef22be7b.jpg?s=120&d=mm&r=g)
On 05.04.2013 13:20, Ludwig Nussel wrote:
Stephan Kulow wrote:
On 03.04.2013 09:26, Ludwig Nussel wrote:
Cristian Rodríguez wrote:
El 02/04/13 16:09, Christian Boltz escribió:
At the moment you'll break lots of packages and, more important, break lots of basic features like RAID and LVM.
RAID and LVM already have systemd support upstream, to make it work, last time I checked it required dracut.
What exactly is dracut needed for there? Or to put it the other way around what's missing from mkinitrd?
A maintainer.
That's the information that was missing so far. At least it wasn't obvious to me. From a technical PoV I don't see the superiority of dracut. It looks like just another flavor of the same shell script mess. So by switching to dracut right now we would not switch to some next generation initrd that can to things in smarter ways.
I'm reluctant to waste time dealing with things like e.g. modules.d/90crypt/cryptroot-ask.sh. That feels like boot.crypto which was rightfully killed by systemd raising from the dead.
That's why dracut maintainers are working on integrating systemd into initrd - and mkinitrd maintainers are not. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org