This is a suggestion from Fabian Deutsch on the Fedora devel mailing list https://lists.fedoraproject.org/pipermail/devel/2014-January/194520.html Recently, we had a problem with an SELinux update which required a manual resolution which as more difficult than is ideal for most users. If the rescue boot config used permissive mode, the solution would have been to simply reboot into rescue mode, update, and reboot back to normal. That's still not ideal, but much easier than the current steps.
(In reply to Matthew Miller from comment #0) > This is a suggestion from Fabian Deutsch on the Fedora devel mailing list > https://lists.fedoraproject.org/pipermail/devel/2014-January/194520.html > > Recently, we had a problem with an SELinux update which required a manual > resolution which as more difficult than is ideal for most users. If the > rescue boot config used permissive mode, the solution would have been to > simply reboot into rescue mode, update, and reboot back to normal. That's > still not ideal, but much easier than the current steps. dracut does not set the boot parameters and cannot do that with /sbin/new-kernel-pkg
We don't have to be limited by dracut here. Anaconda is a powerful tool that should be capable of tacking this onto a rescue boot kernel line.
(In reply to Konstantin Ryabitsev from comment #2) > We don't have to be limited by dracut here. Anaconda is a powerful tool that > should be capable of tacking this onto a rescue boot kernel line. I picked this because dracut subpackage dracut-config-rescue is what creates the current rescue image and rescue boot menu entry.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.