Hi, > > While being at it: anaconda seems to explicitly call dracut to > > generate > > the initrd (according to the messages it prints). What is the reason > > for this? Shouldn't this already happen as part of the rpm > > transaction, > > when the kernel install scripts are running? > IIRC the main reason is the esentially random package installation > order during the RPM transaction. Current kernel.spec runs dracut in %posttrans, probably exactly to make sure it only runs after everything is actually installed. > One concrete issue this caused was that users would use specific > characters in their LUKS password, Anaconda would make sure the given > package containing the layout is installed, but it would come after the > kernel package in the transaction & the layout would be missing from > the initrd. As a result, the user would not be able to type their > password. Ok. > In any case, this situation is sub-optimal, as we currently run dracut > at least twice - once via the kernel RPM script trigger and then again > when Anaconda triggers it. We really need to finally reach out to the > kernel package maintainers and device some mechanism that tells the > kernel package to skip the dracut run during the installation. Hmm, that is somehow the wrong direction. IMHO we should fix package dependencies (assuming this is a problem still) to make sure the initrd is always generated correctly during package installation instead of having anaconda workaround broken dependencies. take care, Gerd _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
