Description of problem: /etc/event.d/rcS is not run on booting single user kernel Version-Release number of selected component (if applicable): 8.76.2 How reproducible: boot into grub, edit kernel command line, add 'single', boot kernel Steps to Reproduce: 1. boot into grub 2. edit kernel commandline, add 'single' 3. boot kernel Actual results: Shell Expected results: Login prompt Additional info:
If you boot into single user mode, rc.sysinit runs and then you get a shell; this is the same behavior that has existed since the dawn of time in Red Hat Linux, Fedora, and RHEL.
/etc/event.d/rcS could provide some security. I did not say it was different from previous redhat/fedora releases. I stated it was not run. You imply this is the expected behaviour because you want the system open immediately to everyone who has physical access. Even this small barrier is not in place. Not even a hint on how to place it there. In the `old days` we could edit the inittab. And now?
Edit rcS-sulogin.
(Note that in Fedora 10, due to an upstart update, things may move slightly.)
You mean it has been made ahrder to ask for a password on single user mode and that it hasn't been documented how to do so? I was told this change (from inittab to this) was meant as an improvement. No I am not bashing something. I want to be able to find my way through configging.
(In reply to comment #5) > You mean it has been made ahrder to ask for a password on single user mode and > that it hasn't been documented how to do so? It's changed from editing one file to editing a different file. I'm not sure how that's harder. It was mentioned in the release notes as: http://docs.fedoraproject.org/release-notes/f9/en_US/sn-System-Services.html#sn-Upstart although there isn't a one-to-one mapping of what goes where. The comment in inittab I suppose could be improved on sulogin, but it does give the idea of where to look.