Bug 195964

Summary: mkinitrd should not insist on module tree being present
Product: [Fedora] Fedora Reporter: Steffen Kluge <kluge>
Component: mkinitrdAssignee: Peter Jones <pjones>
Status: CLOSED NOTABUG QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 5   
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: 2006-07-13 15:13:29 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 Steffen Kluge 2006-06-19 23:55:36 UTC 
Description of problem:

Trying to build an initrd for a monolithic kernel fails because mkinitrd expects
a module tree for a the kernel in /lib/modules and a modules.dep file in there.

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

mkinitrd-5.0.32-1

How reproducible:

Steps to Reproduce:
1. Build a custom kernel without module support
2. Try to make an initrd for it using mkinitrd
3.
  
Actual results:

mkinitrd stops with message:
No modules available for kernel "xyz"

Expected results:

An initrd matching the monolithic kernel should be built. There should be a
command line switch to mkinitrd that causes the module tree check to be skipped.

Additional info:

An initrd for a monolithic kernels is required when using a software RAID or LVM
device for the root filesystem. A workaround to the issue is creating the
expected directory under /lib/modules, and in there an empty modules.dep file.
Comment 1 Peter Jones 2006-07-13 15:13:29 UTC 
We don't support monolithic kernels.