Description of problem: when I switch to init 1 or when I boot to init 1, I am asked for root password: Give root password for maintenance (or type Control-D to continue): ctrl-d just shows it again and again. Version-Release number of selected component (if applicable): systemd-8-3.fc14.x86_64 How reproducible: always when boot to runlevel 1 Steps to Reproduce: 1. add 1 to the end of kernel command line or run "init 1" command Expected results: shell should be run without asking for password
s/sulogin/sushell/ in single.service should do it.
BTW, in upstart it is configurable whether to start sulogin or sushell in single-user mode using SINGLE=... in /etc/sysconfig/init.
Hmm, why would you want a password-less shell there?
History, more than anything else. It's always been that ay. In any case, s/sulogin/sushell/ is needed for SELinux reasons.
(In reply to comment #4) > In any case, s/sulogin/sushell/ is needed for SELinux reasons. I don't think so. They both give you an unconfined_t shell.
sulogin and sushell will. execing just a shell won't.
Well, but we currently use sulogin. I find it really weird if booting into single user mode would not ask for a password.
I'm not sure what to tell you. It's been the default that way for 15 years, for better or worse... have you really not noticed?
(In reply to comment #3) > Hmm, why would you want a password-less shell there? Typically, I use if (it's used) as rescue runlevel, e.g. if I don't know root password or authentication is broken or I need reset root password. It's better then init=/bin/bash But it would be nice to let administrator set sulogin instead sushell (sushell as default) via configuration variable like it's now done with upstart.
(In reply to comment #8) > I'm not sure what to tell you. It's been the default that way for 15 years, for > better or worse... have you really not noticed? I noticed, but I kinda assumed that was oversight.
This is fixed in 9-3/initscripts-9.19-1.