With initscripts-9.47-1.fc19.x86_64, I have these lines in /etc/sysconfig/init (unchanged since installation): # Set to '/sbin/sulogin' to prompt for password on single-user mode # Set to '/sbin/sushell' otherwise SINGLE=/sbin/sushell However, when booting in single user mode (by appending "1" to the kernel command line), I'm still prompted for the password. This requires either a documentation change or a behavioral change.
This was changed between F18 and F19 in systemd. I will remove this line from the config and I will write some explanatory comment.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
The explanatory comment was never added except I guess in the changelog: * Fri Jul 12 2013 Lukáš Nykrýn <lnykryn> - 9.48-1 - man: add systemd man pages to service.8 "see also" section - add possibility to set domainname through /etc/sysconfig/network - rename_device: don't wait for lock with lower permissions - 256term.csh: remove quotes around variable (#979796) - drop useless variables from /etc/sysconfig/init - readonly-root: rpcidmapd restart is not needed anymore - ifup-eth: print error only if arping is really called (#974603) - readonly-root: Add /var/lib/samba to rwtab I used to manually edit /etc/sysconfig/init to turn on where root password was required when booting to single user mode because I run a lab of computers used by students and I didn't want them to get to root easily. It would be nice if there was a way to disable that behavior so a user could set a password-less single user mode. I realize systemd changed its default behavior and perhaps this request should be filed against the systemd package? What do others say?
I think this report should be closed as the issue has been resolved, now /etc/sysconfig/init doesn't mention /sbin/{sulogin,sushell} at all... TBH, I don't know if a bug report against systemd would make the maintainer restore the old behaviour or not. Basically one can restore the old behaviour by copying /usr/lib/systemd/system/rescue.service to /etc/systemd/system and changing the ExecStart line to: ExecStart=-/bin/bash -c "exec /sbin/sushell"
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.