From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Daniel Drake <dsd-2X9k7bc8m7Mdnm+yROfE0A@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Omit in /etc/dracut.conf is too strong
Date: Tue, 14 Sep 2010 13:39:47 +0200 [thread overview]
Message-ID: <4C8F5F03.4070006@redhat.com> (raw)
In-Reply-To: <AANLkTiksQ=j+2466KRjcPyogX5_iO35VFmshiHoS6GEW-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 13.09.2010 18:43, Daniel Drake wrote:
> Hi,
>
> I'm working on using a beefy build-machine to build the initramfs for
> the OLPC XO laptop (an embedded platform, in some respects).
> Specifically, I'm doing the initramfs build in the same RPM build
> process as the kernel. This will mean that it's not necessary to have
> dracut (and its many dependencies) installed on the laptops
> themselves.
>
> The initramfs for the XO laptops is funky and includes some strange
> stuff. It is also not possible to boot an OLPC XO initramfs on a
> "regular PC".
>
> So, on the build system, I install the dracut modules and exclude them
> in /etc/dracut.conf (this way, when upgrading the kernel on the build
> system, the OLPC-specific modules wont slip into the initramfs for the
> build system).
>
> Then from the build system for the XO kernel, I run:
> dracut --force -m 'dash olpc-activation rootfs-block terminfo
> udev-rules base' .....
>
> However, because olpc-activation is excluded in /etc/dracut.conf, it
> doesn't get included in the initramfs.
>
> I think in this case it makes sense for olpc-activation to be included
> given that I specifically requested it in a module list on the command
> line.
>
> Workaround for now:
> dracut -o ' ' --force -m 'dash olpc-activation rootfs-block terminfo
> udev-rules base' .....
>
> Daniel
Hmm, true... care to write a patch? :)
next prev parent reply other threads:[~2010-09-14 11:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 16:43 Omit in /etc/dracut.conf is too strong Daniel Drake
[not found] ` <AANLkTiksQ=j+2466KRjcPyogX5_iO35VFmshiHoS6GEW-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-09-14 11:39 ` Harald Hoyer [this message]
2010-09-14 12:14 ` Seewer Philippe
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=4C8F5F03.4070006@redhat.com \
--to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=dsd-2X9k7bc8m7Mdnm+yROfE0A@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 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.