Bug 234489 - RHEL5 module-init-tools: add --no-mkinitrd option to weak-modules
RHEL5 module-init-tools: add --no-mkinitrd option to weak-modules
Status: CLOSED DUPLICATE of bug 229512
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: module-init-tools (Show other bugs)
5.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jon Masters
:
Depends On:
Blocks: 223278
  Show dependency treegraph
 
Reported: 2007-03-29 12:35 EDT by Matt Domsch
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-04-10 05:47:00 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Matt Domsch 2007-03-29 12:35:34 EDT
Description of problem:
/sbin/weak-modules always calls mkinitrd when it thinks the boot path modules
have changed.  Seems sane.  But in our factory, we'll use DKMS to install
several modules, and *then* at the end, will remake the initrd.  As it stands,
/sbin/weak-modules will create several initrds, and several new entries in grub,
which is somewhat confusing.

Please add an option --no-mkinitrd to /sbin/weak-modules to let DKMS avoid that
mkinitrd call.  We'll mkinitrd ourselves later.

Version-Release number of selected component (if applicable):
module-init-tools-3.3-0.pre3.1.16.el5
Comment 1 Jon Masters 2007-04-10 05:47:00 EDT

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

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