From: Andrei Borzenkov <arvidjaar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: lyndat3-p/IIKWkZnU0S+FvcfC7Uqw@public.gmane.org
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: How to have dracut conditionally add different kernel modules for different kernels?
Date: Sun, 12 Apr 2015 11:11:54 +0300 [thread overview]
Message-ID: <20150412111154.5de2405f@opensuse.site> (raw)
In-Reply-To: <1428693113.1734218.251850073.54517680-2RFepEojUI2N1INw9kWLP6GC3tUn3ZHUQQ4Iyu8u01E@public.gmane.org>
В Fri, 10 Apr 2015 12:11:53 -0700
lyndat3-p/IIKWkZnU0S+FvcfC7Uqw@public.gmane.org пишет:
> 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?
Not sure about the "right" way, but dracut configuration files are
shell scripts, so you can implement the same logic in /etc/dracut.d
snippet, something like
if is_xen_kernel ; then
add_drivers+=" ..."
fi
where is_xen_kernel does whatever check is required to detect domU
kernel.
next prev parent reply other threads:[~2015-04-12 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 19:11 How to have dracut conditionally add different kernel modules for different kernels? lyndat3-p/IIKWkZnU0S+FvcfC7Uqw
[not found] ` <1428693113.1734218.251850073.54517680-2RFepEojUI2N1INw9kWLP6GC3tUn3ZHUQQ4Iyu8u01E@public.gmane.org>
2015-04-12 8:11 ` Andrei Borzenkov [this message]
[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=20150412111154.5de2405f@opensuse.site \
--to=arvidjaar-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lyndat3-p/IIKWkZnU0S+FvcfC7Uqw@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