Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 83794

Summary: Request cramfs in default kernel
Product: [Retired] Red Hat Linux Reporter: Greg Hudson <ghudson>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED WONTFIX QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0CC: mitr
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-09-30 15:40:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Greg Hudson 2003-02-08 21:00:16 UTC
Currently, Red Hat builds cramfs as a kernel module.  One of the main purposes
of cramfs is to be used for initrd images, which requires cramfs be built into
the kernel.  (This is how Debian does initrds.)

Red Hat does not use cramfs for the initrd (although I think it would make your
lives simpler if you did, and it would mitigate bug 76237), but sometimes
customers may want to build their own initrd images, perhaps without modifying
the kernel device state or mount table.

cramfs is really tiny, so this shouldn't appreciably impact the kernel image size.

Comment 1 Bugzilla owner 2004-09-30 15:40:30 UTC
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/