Bug 65250 - mkinitrd shouln't quit when module not found.
mkinitrd shouln't quit when module not found.
Product: Red Hat Linux
Classification: Retired
Component: mkinitrd (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Matt Wilson
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2002-05-20 18:08 EDT by hjl
Modified: 2007-04-18 12:42 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-05-20 18:08:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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

  None (edit)
Description hjl 2002-05-20 18:08:08 EDT
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 18:08:49 EDT
Created attachment 58046 [details]
A patch to skip a kernel module.
Comment 2 Erik Troan 2002-05-20 21:12:09 EDT
I disagree -- many (certainly most new users) need to see this as an error

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-20 22:25:00 EDT
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.