Bug 234489

Summary: RHEL5 module-init-tools: add --no-mkinitrd option to weak-modules
Product: Red Hat Enterprise Linux 5 Reporter: Matt Domsch <matt_domsch>
Component: module-init-toolsAssignee: Jon Masters <jcm>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5.0CC: wwlinuxengineering
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-04-10 09:47:00 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:
Bug Depends On:    
Bug Blocks: 223278    

Description Matt Domsch 2007-03-29 16:35:34 UTC 
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 09:47:00 UTC 

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