This came up on the user@ list recently so I filed a docs bug. The gist is that because it boots graphically, and Anaconda inst.rescue is text based, there's no rescue. Further, rescue.target and emergency.target aren't functional either because systemd requires root login password for those, but the lives don't have a root password set.
So what I've suggested in the bug for docs is the user can use init=/bin/bash if they need access to a shell, but... I'm not really sure if there's a better way to handle this? Suggest the user download a netinstall image for rescue?
https://bugzilla.redhat.com/show_bug.cgi?id=1374064
On Sep 7, 2016 3:43 PM, "Chris Murphy" lists@colorremedies.com wrote:
This came up on the user@ list recently so I filed a docs bug. The gist is that because it boots graphically, and Anaconda inst.rescue is text based, there's no rescue. Further, rescue.target and emergency.target aren't functional either because systemd requires root login password for those, but the lives don't have a root password set.
So what I've suggested in the bug for docs is the user can use init=/bin/bash if they need access to a shell, but... I'm not really sure if there's a better way to handle this? Suggest the user download a netinstall image for rescue?
https://bugzilla.redhat.com/show_bug.cgi?id=1374064
-- Chris Murphy --
This isn't a new question, FWIW; anaconda rescue mode is explicitly a feature of images that boot directly to anaconda. We should make this more clear and offer alternatives for live image operations, probably. Thanks for bringing it up!
--Pete
desktop@lists.fedoraproject.org