Description of problem: Not sure if this is a sysvinit-tools bug or a systemd bug. I managed to get a corrupted filesystem, so the autofsck step in /etc/rc.sysinit failed, so it hit this code: str=$"(Repair filesystem)" PS1="$str \# # "; export PS1 [ "$SELINUX_STATE" = "1" ] && disable_selinux sulogin However, when it prompted for the root password, it would exit on the very first keypress and say 'Login incorrect.' and prompt again. Looks like the stty settings were all scrogged up. I suspect that the old sysvinit would set semi-sane settings on /dev/console, so sulogin "worked", but the new systemd code is failing to set stty settings. Version-Release number of selected component (if applicable): sysvinit-tools-2.87-5.dsf.fc15.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
initscripts doesn't touch the tty settings itself; this is likely one of plymouth or systemd.
More info: 1) If I passed '3' on the boot command line to go into runlevel 3, I ended up with messed up TTY settings on tty1 but correct settings on tty2. 2) While in runlevel 3, I did a 'telinit s' to go to single user - and although the stty settings were correct while in runlevel 3, the settings on the single-user shell *on that same VT* were again hosed up.
Oh, and I forgot - booting to single-user mode gets hosed up settings as well, so it's apparently *not* sulogin, which doesn't get run in that case.
It seems a duplicate of bug #636628.
*** This bug has been marked as a duplicate of bug 636628 ***