<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Rick Stevens wrote: <blockquote cite="mid:1194648265.29675.1.camel@prophead.corp.publichost.com" type="cite"> <pre wrap="">On Fri, 2007-11-09 at 15:14 -0600, Aaron Konstam wrote: </pre> <blockquote type="cite"> <pre wrap="">On Fri, 2007-11-09 at 17:33 +0100, <a class="moz-txt-link-abbreviated" href="mailto:info@boer-software-en-webservices.nl">info@boer-software-en-webservices.nl</a> wrote: </pre> <blockquote type="cite"> <pre wrap="">Is it possible to define which modules mkinitrd should add to the initrd? I have a custom initrd, but after every kernel upgrade, it recreates the initrd. When it does this, I loose the extra module I need, so I end up recreating the initrd myself again. I know in Ubuntu and Debian there is a file somewhere in /etc/sysconfig that defines the modules to use when building the initrd. But I have yet to find this file in Fedora. </pre> </blockquote> <pre wrap="">The --with option in mkinitrd </pre> </blockquote> <pre wrap=""> mkinitrd will load any modules required to mount the root filesystem (e.g. SCSI, ext3, network [if / is on an NFS volume], etc.) If you need additional modules, then "--with=name-of-module" is required. ---------------------------------------------------------------------- - Rick Stevens, Principal Engineer <a class="moz-txt-link-abbreviated" href="mailto:rstevens@internap.com">rstevens@internap.com</a> - - CDN Systems, Internap, Inc. <a class="moz-txt-link-freetext" href="http://www.internap.com">http://www.internap.com</a> - - - - Animal testing is futile. They always get nervous and give the - - wrong answers - ---------------------------------------------------------------------- </pre> </blockquote> Yea, but when installing a new kernel, this "new" module would not be added to the new initrd. I have fedora installed, and sometimes I use vmware to load it, and sometimes I just boot to it. When I boot it, without using vmware, I need the sata_nv driver, but when I use vmware, it's not needed (some other vmware drivers are needed though). On Debian you would add the module to "/etc/mkinitrd/modules". Every time a new kernel would be installed it would recreate an initrd with the module(s) defined in that file. I was trying to find something like that on Fedora. </body> </html>