Bug 65250 - mkinitrd shouln't quit when module not found.
Summary: mkinitrd shouln't quit when module not found.
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: mkinitrd
Version: 7.3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Matt Wilson
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-05-20 22:08 UTC by hjl
Modified: 2007-04-18 16:42 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-05-20 22:08:55 UTC
Embargoed:


Attachments (Terms of Use)
A patch to skip a kernel module. (356 bytes, patch)
2002-05-20 22:08 UTC, hjl
no flags Details | Diff

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.


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