Bug 129099

Summary: Lost ability to specify boot level in a kernel boot command
Product: [Fedora] Fedora Reporter: Michal Jaegermann <michal>
Component: mkinitrdAssignee: Jeremy Katz <katzj>
Status: CLOSED DUPLICATE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: notting
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:04:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 123268    

Description Michal Jaegermann 2004-08-04 01:02:52 UTC
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):
SysVinit-2.85-31

How reproducible:
Always

Comment 1 Michal Jaegermann 2004-08-04 07:00:37 UTC
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 15:41:09 UTC

*** This bug has been marked as a duplicate of 129057 ***

Comment 3 Red Hat Bugzilla 2006-02-21 19:04:55 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.