mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Seewer Philippe <philippe.seewer-omB+W0Dpw2o@public.gmane.org>
To: initramfs <initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: including python in the initramfs
Date: Wed, 17 Jun 2009 09:06:51 +0200	[thread overview]
Message-ID: <4A38960B.20305@bfh.ch> (raw)
In-Reply-To: <4A37EA8E.7090508-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

Warren Togami wrote:
[snip]
> This is a good case for the modules.d design of dracut.  Write your own 
> module that does whatever you want, and install that module only in 
> cases where you generate the initrd for your XO.  Your special module 
> does not belong in dracut upstream.

I agree. That's what the module system is designed for among other 
things. Have a look at README.modules and the currently available 
modules, that should give you an idea on how to proceed.

Regards,
Philippe
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-06-17  7:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16 17:40 including python in the initramfs Daniel Drake
2009-06-16 18:22 ` Victor Lowther
     [not found]   ` <A4EC33E8-3A45-4A6B-AE97-5B48EA425F75-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-06-16 18:49     ` Daniel Drake
2009-06-16 18:55       ` Warren Togami
     [not found]         ` <4A37EA8E.7090508-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-17  7:06           ` Seewer Philippe [this message]
     [not found]             ` <4A38960B.20305-omB+W0Dpw2o@public.gmane.org>
2009-06-17  8:28               ` Daniel Drake
2009-06-16 18:26 ` Warren Togami

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=4A38960B.20305@bfh.ch \
    --to=philippe.seewer-omb+w0dpw2o@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