mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: lyndat3-p/IIKWkZnU0S+FvcfC7Uqw@public.gmane.org
To: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: How to have dracut conditionally add different kernel modules for different kernels?
Date: Fri, 10 Apr 2015 12:11:53 -0700	[thread overview]
Message-ID: <1428693113.1734218.251850073.54517680@webmail.messagingengine.com> (raw)

The distro I use, opensuse, has switched to using dracut for initrd creation.

Prior to dracut usage, kernel-flavor-specific loading -- particularly for the case of Xen -- could be defined in

 /etc/sysconfig/kernel
  ...
  INITRD_MODULES="processor thermal ahci fan jbd ext3 edd"
  DOMU_INITRD_MODULES="xennet xenblk"
  ...

On 'old' mkinitrd, if both -xen and non-xen kernels were installed, initrd's were created for each.  In the xen case the modules defined in "DOMU_INITRD_MODULES" were conditionally added to the initrd-xen.

Since the  switch to dracut, module config/loading is defined in dracut.conf & dracut.d/*conf

But the 

add_drivers+=" ... " 

is apparently added for all kernels.

What's the right way to add kernel-specific modules in dracut, so that for example the xen mods are ONLY added in the xen case?

LT

             reply	other threads:[~2015-04-10 19:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10 19:11 lyndat3-p/IIKWkZnU0S+FvcfC7Uqw [this message]
     [not found] ` <1428693113.1734218.251850073.54517680-2RFepEojUI2N1INw9kWLP6GC3tUn3ZHUQQ4Iyu8u01E@public.gmane.org>
2015-04-12  8:11   ` How to have dracut conditionally add different kernel modules for different kernels? Andrei Borzenkov
     [not found]     ` <20150412111154.5de2405f-stAJ6ESoqRzYCGPCin2YbQ@public.gmane.org>
2015-04-12 16:32       ` lyndat3-p/IIKWkZnU0S+FvcfC7Uqw

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1428693113.1734218.251850073.54517680@webmail.messagingengine.com \
    --to=lyndat3-p/iikwkznu0s+fvcfc7uqw@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox