Bug 129099 - Lost ability to specify boot level in a kernel boot command
Lost ability to specify boot level in a kernel boot command
Status: CLOSED DUPLICATE of bug 129057
Product: Fedora
Classification: Fedora
Component: mkinitrd (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
David Lawrence
Depends On:
Blocks: FC3Target
  Show dependency treegraph
Reported: 2004-08-03 21:02 EDT by Michal Jaegermann
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 14:04:55 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michal Jaegermann 2004-08-03 21:02:52 EDT
Description of problem:

'cat /proc/cmdline' shows 'ro root=LABEL=/12 selinux=0 3'
but '/sbin/runlevel' comes with 'N 5' anyway, or more precisely
grabs runlevel from /etc/inittab unconditionally, and the machine
boots into runlevel 5.  Similarly arguments as "single" or "S"
also do not have any effect.  Very annoying when one tries
to diagnose a problem which depends on a runlevel.

Not that sure if the problem is really in SysVinit.

Version-Release number of selected component (if applicable):

How reproducible:
Comment 1 Michal Jaegermann 2004-08-04 03:00:37 EDT
Ah, this really looks like a result of a "new-style" mkinitrd
(cpio archive instead of a file system) and replacing initrd
with the one generated with a help of mkinitrd from FC2 restores
an ability to specify a boot level.  Moreover this is architecture
independent.  If something is missing on new initrd or a kernel
is not playing with it corectly I cannot tell; at least for now.
In any case /sbin/init seems to be innocent.  Reclassified.
Comment 2 Bill Nottingham 2004-08-04 11:41:09 EDT

*** This bug has been marked as a duplicate of 129057 ***
Comment 3 Red Hat Bugzilla 2006-02-21 14:04:55 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.