All of lore.kernel.org
 help / color / mirror / Atom feed
* control what kernel modules get loaded into ramdisk
@ 2009-11-02 17:34 Dan Horák
       [not found] ` <1257183267.3755.286.camel-Gu2OudDT4ISyu7giWUE+hA@public.gmane.org>
  0 siblings, 1 reply; 4+ messages in thread
From: Dan Horák @ 2009-11-02 17:34 UTC (permalink / raw)
  To: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org

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
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?


Thanks

Dan


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2009-11-03 11:07 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-11-02 17:34 control what kernel modules get loaded into ramdisk Dan Horák
     [not found] ` <1257183267.3755.286.camel-Gu2OudDT4ISyu7giWUE+hA@public.gmane.org>
2009-11-03 10:25   ` [PATCH] " Dan Horák
     [not found]     ` <1257243945.3790.45.camel-Gu2OudDT4ISyu7giWUE+hA@public.gmane.org>
2009-11-03 10:30       ` Harald Hoyer
     [not found]         ` <4AF0065A.4070100-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-11-03 11:07           ` Dan Horák

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.