Bug 65250

Summary: mkinitrd shouln't quit when module not found.
Product: [Retired] Red Hat Linux Reporter: hjl
Component: mkinitrdAssignee: Matt Wilson <msw>
Status: CLOSED RAWHIDE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-05-20 22:08: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:
Attachments:
Description Flags
A patch to skip a kernel module. none

Description hjl 2002-05-20 22:08:08 UTC 
mkinitrd shouln't quit when a kernel module is not found.
It is entirely possible that the feature is builtin.
Comment 1 hjl 2002-05-20 22:08:49 UTC 
Created attachment 58046 [details]
A patch to skip a kernel module.
Comment 2 Erik Troan 2002-05-21 01:12:09 UTC 
I disagree -- many (certainly most new users) need to see this as an error
condition.

I've added a --builtin option which lets you tell mkinitrd certain modules
are built into the kernel, so "--builtin ext3" will stop it from looking for
ext3.o (and jbd.o as well). This isn't quite the same as what you wanted, but
hopefully it will work well enough.

Change in mkinitrd 3.3.11
Comment 3 hjl 2002-05-21 02:25:00 UTC 
I prefer something like --bultin-all so that I don't
have to change the script when my kernel changes.