Bug 169712

Summary:	mkinitrd breaks processing of kernel boot arguments
Product:	[Fedora] Fedora	Reporter:	Michal Jaegermann <michal>
Component:	mkinitrd	Assignee:	Peter Jones <pjones>
Status:	CLOSED RAWHIDE	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	clydekunkel7734, ivazqueznet, umar
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	5.0.4-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-10-07 16:45:33 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:

Description Michal Jaegermann 2005-10-01 20:55:08 UTC

Description of problem:

With initrd created with mkinitrd 5.0.2-1 or 5.0.3-1 arguments like
bootlevel are ignored and a machine boots always to what is specified
in /etc/inittab.  This is not the case for an older kernel which I have
here and which is still using initrd done with 5.0.0-1; but if I replace
initrd for this kernel with a new one redone with 5.0.3-1 then an argument
specifying a desired boot level is immediately ignored.

Version-Release number of selected component (if applicable):
mkinitrd-5.0.2-1 and mkinitrd-5.0.3-1

How reproducible:
always

Comment 1 Sammy 2005-10-03 15:17:48 UTC

I can't even build a initrd image with older versions of 2.6.13 kernels. I am getting 
 
"cannot find module modprobe (aborting)" 
 
message and nothing is produced. Version 5.0.0 works perfectly but 5.0.2 and .3 does not. 
 
If this is due to kernel incompatibility then there should be a Requisite of some sort. 
Thanks

Comment 2 Peter Jones 2005-10-07 16:45:33 UTC

mkinitrd-5.0.4-1 should have command line parsing working again.