Bug 767736

Summary: dracut options function does not match its man page description
Product: [Fedora] Fedora Reporter: Chris Murphy <bugzilla>
Component: dracutAssignee: dracut-maint
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 16CC: dracut-maint, harald, jonathan, vmclark
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-23 11:32:01 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:

Description Chris Murphy 2011-12-14 19:00:00 UTC
Description of problem:
--modules <list>
--add-drivers <list>
Do not work as described in the dracut man page (and probably others). Merely placing multiple modules after the parameter results in bogus files being created, and/or error messages.

Version-Release number of selected component (if applicable):
013-19.fc16

How reproducible:
Always

Steps to Reproduce Example 1:
dracut -f --modules plymouth btrfs initramfs-3.1.5-1.fc16.x86_64.img
  
Actual results Example 1:
Results in no errors, but results in a file "btrfs" being created. Size and modification date of initramfs-3.1.5-1.fc16.x86_64.img is unchanged.

Steps to Reproduce Example 2:
dracut -f --add-drivers vboxvideo drm initramfs-3.1.5-1.fc16.x86_64.img

Actual results Example 2:
Creation of file drm, initramfs-3.1.5-1.fc16.x86_64.img size and mod date/time unchanged, and a bunch of errors:

E: FATAL: Could not load /lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/modules.dep: No such file or directory
find: `/lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/': No such file or directory
E: FATAL: Could not load /lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/modules.dep: No such file or directory
find: `/lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/': No such file or directory
E: FATAL: Could not load /lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/modules.dep: No such file or directory
F: No modules.builtin.bin and modules.builtin found!
E: FATAL: Could not load /lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/modules.dep: No such file or directory
E: FATAL: Could not load /lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/modules.dep: No such file or directory
E: FATAL: Could not load /lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/modules.dep: No such file or directory
E: FATAL: Could not load /lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/modules.dep: No such file or directory
E: FATAL: Could not load /lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/modules.dep: No such file or directory
E: FATAL: Could not load /lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/modules.dep: No such file or directory
E: FATAL: Could not load /lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/modules.dep: No such file or directory
E: FATAL: Could not load /lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/modules.dep: No such file or directory
E: FATAL: Could not load /lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/modules.dep: No such file or directory
E: FATAL: Could not load /lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/modules.dep: No such file or directory
E: FATAL: Could not load /lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/modules.dep: No such file or directory
E: FATAL: Could not load /lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/modules.dep: No such file or directory
E: FATAL: Could not load /lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/modules.dep: No such file or directory
E: FATAL: Could not load /lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/modules.dep: No such file or directory
E: FATAL: Could not load /lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/modules.dep: No such file or directory
E: FATAL: Could not load /lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/modules.dep: No such file or directory
E: FATAL: Could not load /lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/modules.dep: No such file or directory
E: FATAL: Could not load /lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/modules.dep: No such file or directory
E: FATAL: Could not load /lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/modules.dep: No such file or directory
E: FATAL: Could not load /lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/modules.dep: No such file or directory
E: FATAL: Could not load /lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/modules.dep: No such file or directory
E: FATAL: Could not load /lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/modules.dep: No such file or directory
find: `/lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/': No such file or directory
find: `/lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/': No such file or directory
find: `/lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/': No such file or directory
find: `/lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/': No such file or directory
E: FATAL: Could not load /lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/modules.dep: No such file or directory
E: FATAL: Could not load /lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/modules.dep: No such file or directory
find: `/lib/modules/initramfs-3.1.5-1.fc16.x86_64.img/': No such file or directory

Expected results:
Either to work as the man page says, i.e. multiple modules listed after the parameter followed by spaces without quotes, or for the man page to reflect actual behavior.

Additional info:
If I put the list in quotes "mod1 mod2" then a single parameter works.
If I use multiple parameters each followed by one module, that works.

The man page very clearly says:
--add-drivers <list of kernel modules>
           specify a space-separated list of kernel modules to add to the initramfs. The kernel modules have to be specified
           without the ".ko" suffix. This parameter can be specified multiple times.
1.
The parameter is plural: drivers. Not --add-driver. 

2. Man page says <list of kernel modules>, plural.

3. Man page doesn't say the list needs to go inside of quotes.

4. In the above two examples, if I add <kernel release> to the end, dracut spits its man page back at me. No file created. No error.

Comment 1 Vern Clark 2011-12-14 23:04:20 UTC
Also add Examples to the man page to help understand the command

Comment 2 Harald Hoyer 2012-01-23 10:27:19 UTC
Thanks, fixed in the documentation.

Comment 3 Harald Hoyer 2012-01-23 11:32:01 UTC
dracut-014-61.git20120123.fc17