Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#24204 - [initscripts] Runlevel Parameter ignored
Attached to Project:
Arch Linux
Opened by Christian Katterl (theCat) - Tuesday, 10 May 2011, 10:29 GMT
Last edited by Tom Gundersen (tomegun) - Wednesday, 15 June 2011, 06:14 GMT
Opened by Christian Katterl (theCat) - Tuesday, 10 May 2011, 10:29 GMT
Last edited by Tom Gundersen (tomegun) - Wednesday, 15 June 2011, 06:14 GMT
|
DetailsDescription:
When trying to append the runlevel at boot-time (for example in grub, syslinux...) usually adding the number of the desired runlevel helped to boot automatically into this runlevel. Since initscripts 2011.04.1-2 (and at least in combination with kernel 2.6.38.5-1) this does not work anymore Additional info: * kernel26 (2.6.38.5-1) * Boot Options runlevel 3: "kernel /vmlinuz26 root=/dev/sda2 resume=/dev/sda3 ro 3" * Boot Options runlevel 5: "kernel /vmlinuz26 root=/dev/sda2 resume=/dev/sda3 ro 5" |
This task depends upon
Closed by Tom Gundersen (tomegun)
Wednesday, 15 June 2011, 06:14 GMT
Reason for closing: Works for me
Additional comments about closing: Reporter can't reproduce.
Wednesday, 15 June 2011, 06:14 GMT
Reason for closing: Works for me
Additional comments about closing: Reporter can't reproduce.
DAEMONS=(syslog-ng !crond @network @ntp)
Before the Update (Kernel and initscripts) everything worked perfectly.
Now i can choose whatever i want in kernel parameters, always runlevel 3 is bootet (because it's default in /etc/inittab)
Hint:
Using "init 5" at the console works fine, runlevel 5 is started.
The problem persists in these versions too.
Chris
In my tests it work as expected.
Chris
I could test it on my workstation but not on the system where i detected this problem first.
The 'source-machine' was a live-system built using larch.
As aufs2 is not in the repositories for the moment i cannot test it on this live-system.
Chris