https://bugzilla.novell.com/show_bug.cgi?id=809812 https://bugzilla.novell.com/show_bug.cgi?id=809812#c21 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sfalken@opensuse.org InfoProvider|werner@suse.com |sfalken@opensuse.org --- Comment #21 from Dr. Werner Fink <werner@suse.com> 2014-02-05 08:33:47 UTC --- Indeed I've submitted this. Nevertheless AFAIK dracut as successor does not have this sulogin nor the root password feature. And the original problem was/is that plymouth does lock the devices below /dev/console which fools e.g. sulogin as well as the following shell. The question is: How we can make sure that plymouth is really stopped before an emergency shell or and sulogin followed by an emergency shell? For mkinitrd I've used +emergency() { + local plymouth sulogin + if plymouth=$(type -p plymouth 2> /dev/null) ; then + $plymouth quit + $plymouth --wait + fi + if test -w /proc/splash ; then + echo verbose >| /proc/splash + fi + cd / + echo -n "${1+$@} -- " + if sulogin=$(type -p sulogin 2> /dev/null); then + echo "exiting to $sulogin" + PATH=$PATH PS1='$ ' $sulogin /dev/console + else + echo "exiting to /bin/sh" + PATH=$PATH PS1='$ ' /bin/sh -i + fi +} as replacement for all /bin/bash emergency shells. The question is if dracut does the same? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.