[opensuse-factory] Going forward with Plymouth (based on dracut changes)
Hi, Based on the recent changes for Dracut and making it replace mkinitrd, also has some consequences for Plymouth. Using Dracut at the moment would generate a smaller initrd file, then utilizing mkinitrd. Main reason for this is not that Dracut is so much smarter, but more that only partial Plymouth support is provided. The initrd that Dracut generated does not include the Pango libraries/modules and Font that is required to present the user with a question or comments during the boot process. In most cases this is never used, but for those users that utilize encrypted disks, this would be a major issue. This particular combination has been always a hot topic in the past and I would like to resolve it in the best way possible. As far as I can see, we have the following possibilities: 1) Drop the ask-for-password stuff from Plymouth, which would allow us to drop the additional library requirements. This would mean that the password for encrypted disks is validated before plymouth starts (all within the initrd) 2) Drop plymouth from initrd and start plymouth from disk after password, etc have been required. This would then be the task for systemd, which already has this support. 3) Try to establish a checking mechanism that implements option 2 for particular kernels/encrypted root/swap disks. For the other users there is no change. Option 2 would be easy to implement. For the others I don't know and I might have to rely on others to support me. However I would like to have your opinion on the right way forward. Thanks Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (14)
-
Andreas Schwab
-
Andrey Borzenkov
-
brian@aljex.com
-
Bruno Friedmann
-
Cristian Rodríguez
-
Frederic Crozat
-
Jan Engelhardt
-
Jeff Mahoney
-
Ludwig Nussel
-
Per Jessen
-
Philipp Wagner
-
Rajko
-
Raymond Wooninck
-
Yamaban