From: Seewer Philippe <philippe.seewer-omB+W0Dpw2o@public.gmane.org>
To: Thiago Galesi <thiagogalesi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Victor Lowther
<victor.lowther-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"<initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>"
<initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Dracut on different distros?
Date: Wed, 4 Mar 2009 17:44:15 +0100 [thread overview]
Message-ID: <49AEAFDF.6010405@bfh.ch> (raw)
In-Reply-To: <82ecf08e0903040820t42775dd8s56e32d9d5dd53c36-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Thiago Galesi wrote:
>>> Certainly stupid me can't think of a way to be sure we "really really"
>>> have all block drivers without including every single .ko. Leave it to the
>>> user to specifically set drivers or the Distro to tell Dracut which drivers
>>> to include.
>> Indeed.
>>
>
> Isn't this two different things?
>
> I mean, it's one thing to have a "generic" initrd for, I dunno, live
> CDs, etc and another thing to generate for a specific
> computer/installation. And even installation triggers run mkinitrd (or
> similar), no?
It entirely depends on your point of view. The contents of the actually
generated initrd might be very different. At least the contained modules
could differ, the rest of the initrd could actually be the same.
And how we generate those images might not differ from use-case to the
next at all.
--
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
next prev parent reply other threads:[~2009-03-04 16:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 15:10 Dracut on different distros? Seewer Philippe
[not found] ` <49AE99D2.1000501-omB+W0Dpw2o@public.gmane.org>
2009-03-04 16:05 ` Victor Lowther
[not found] ` <0227279C-8C23-4501-B163-04470D0C0F35-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-03-04 16:20 ` Thiago Galesi
[not found] ` <82ecf08e0903040820t42775dd8s56e32d9d5dd53c36-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-03-04 16:44 ` Seewer Philippe [this message]
2009-03-04 16:40 ` Seewer Philippe
[not found] ` <49AEAF16.6010008-omB+W0Dpw2o@public.gmane.org>
2009-03-04 17:28 ` Victor Lowther
[not found] ` <14BAD8D9-B114-4979-B9CE-BA20CEEF768D-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-03-05 7:23 ` Harald Hoyer
2009-03-04 18:12 ` Dave Jones
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=49AEAFDF.6010405@bfh.ch \
--to=philippe.seewer-omb+w0dpw2o@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=thiagogalesi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=victor.lowther-Re5JQEeQqe8AvxtiuMwx3w@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.