compat: failed to enter rc1.d by putting 1 in boot param
Bug #85014 reported by
Steven Shiau
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart |
Invalid
|
Low
|
Unassigned | ||
upstart (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Binary package hint: upstart
I am using Ubuntu Edgy. The upstart is 0.2.7-7. When I tried to enter
runlevel 1 by put "1" in kernel boot param in /boot/grub/
example:
----------------
title Ubuntu, kernel 2.6.17-11-generic
root (hd0,0)
kernel /boot/vmlinuz-
splash
initrd /boot/initrd.
quiet
savedefault
boot
----------------
My edgy box still enters runlevel 2. Is this a normal situation ? Does anyone has same problem ?
Thanks in advance.
Changed in upstart: | |
status: | Confirmed → Triaged |
status: | Confirmed → Triaged |
Changed in upstart: | |
milestone: | 0.5 → none |
Changed in upstart: | |
milestone: | none → 0.5-later |
Changed in upstart: | |
milestone: | 0.5-later → none |
summary: |
- Fail to enter rc1.d by putting 1 in bootparam in edgy + compat: failed to enter rc1.d by putting 1 in boot param |
To post a comment you must log in.
This is caused by the rc-default script, which invokes the default runlevel once the rcS job has stopped.
It does this by a combination of grep on the command-line and /etc/inittab files, then invoking telinit with whatever argument it found.
It only handles -s/single/S being on the command line, because that's all I knew about at the time -- it would need patching/modifying to also look for the other runlevel names and set $RL appropriately.