Bug 98340 - mkinitrd ignores options param from /etc/modules.conf
mkinitrd ignores options param from /etc/modules.conf
Product: Red Hat Linux
Classification: Retired
Component: mkinitrd (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2003-07-01 10:01 EDT by Bill Peck
Modified: 2007-04-18 12:55 EDT (History)
0 users

See Also:
Fixed In Version: 3.4.47
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-07-01 10:16:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bill Peck 2003-07-01 10:01:41 EDT
Description of problem:
Setting options scsi_mod max_scsi_luns=128 and running mkinitrd should create
a ramdisk image with insmod scsi_mod max_scsi_luns=128 but it doesn't.

Looking a little closer at the mkinitrd script it seems that the following line
has changed in Shrike:

module=`echo $MODULE | sed "s|.*/||"`

in Enigma 7.2 the line is :

module=`echo $MODULE | sed "s|.*/||" | sed "s/.o$//"`

Which works.  I checked documentation for mkinitrd but I can't find any mention
of a change in how this should work. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. add options scsi_mod max_scsi_luns=128 to /etc/modules.conf
2. mkinitrd -f /boot/initrd.img 2.4.20-8
3. reboot or check the initrd.img file..  you will see no mention of max_scsi_luns
Actual results:
no options will be picked up by mkinitrd

Expected results:
options will be picked up

Additional info:
Comment 1 Jeremy Katz 2003-07-01 10:16:26 EDT
Fixed since 3.4.47

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