Re: [PATCH] Re: control what kernel modules get loaded into ramdisk

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 11/03/2009 11:25 AM, Dan Horák wrote:
Dan Horák píše v Po 02. 11. 2009 v 18:34 +0100:
Hello,

I started to use dracut for preparing generic ramdisk for Fedora/ARM.
The issue with ramdisks on ARM is that they are usually limited in size
because they are stored in the internal flash memories whose capacity
can be 8 or 16 MB (for kernel, ramdisk and other stuff) in the
commercial devices (like NAS from QNAP). So I used the
"omit_dracutmodules" option in the config file to drop stuff like i18n,
plymouth etc. It works, the created ramdisk is usable, but what remains
quite large are the kernel modules for all filesystems. The ability to

I have solved the problem with filesystem modules with an introduction
of new command line/config file parameter. It controls the list of
filesystem modules that will be included when running in generic mode.
See the attached patch for details.

limit the list of drivers for block devices would be also nice. Is there
a way to control what kernel modules get loaded into the ramdisk, like
some black- or whitelist?


Dan


s/kenrel/kernel/

s/modules to be loaded into generic initramfs/modules to be included in the generic initramfs/
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux