#10444 NORM Not Tri: Single user mode on an XO starts dueling shell prompts, keeps others running
Zarro Boogs per Child
bugtracker at laptop.org
Mon Nov 15 15:18:56 EST 2010
#10444: Single user mode on an XO starts dueling shell prompts, keeps others
running
-----------------------------------+----------------------------------------
Reporter: greenfeld | Owner: dsd
Type: defect | Status: new
Priority: normal | Milestone: Not Triaged
Component: initscripts | Version: Development build as of this date
Resolution: | Keywords:
Next_action: never set | Verified: 0
Deployment_affected: | Blockedby:
Blocking: |
-----------------------------------+----------------------------------------
Comment(by greenfeld):
Replying to [comment:1 dsd]:
> The init man page basically says that using runlevel S is invalid.
Interesting; this may vary between inits, as well as the scripts
underlying them. "init 1" does behave as expected.
On a pre-F14 system, the telinit(8) man page {using the upstart sysinit}
says S or s puts the system in single user mode without stopping anything.
On my laptop {using sysvinit}, s or S brings the system to single user
mode gracefully, and according to the man page can function even without
/etc/inittab present. No mention of leaving other processes running is
made. F11 uses sysvinit 2.86 just like my cloned Gentoo laptop does, but
points to a different source URL.
I don't think FreeBSD's init knows what S or s is. Google suggests that
other *NIX's may treat S or s to mean "start single user mode with the
terminal on this console".
So this may indeed be as designed, just distribution dependent.
--
Ticket URL: <http://dev.laptop.org/ticket/10444#comment:2>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list