From: Seewer Philippe <philippe.seewer-omB+W0Dpw2o@public.gmane.org>
To: Victor Lowther <victor.lowther-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "<initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>"
<initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Dracut on different distros?
Date: Wed, 4 Mar 2009 17:40:54 +0100 [thread overview]
Message-ID: <49AEAF16.6010008@bfh.ch> (raw)
In-Reply-To: <0227279C-8C23-4501-B163-04470D0C0F35-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Victor Lowther wrote:
[snip]
>> Second I have to ask how far Dracut needs (and wants) to go with the
>> "One initrd to rule them all". The different distros will need to
>> customize the initrd anyway. Think in terms of splash-screens,
>> different versions of utilities and configs or just plain 'crazy and
>> convoluted'...
>
> I would have the goal of making dracut be able to generate a working
> no-frills initramfs with minimal (preferably no) distro customization,
> and have a hook structure that allows the distros to customize the
> initrams without having to patch things.
Yes, that's why I suggested Fallbacks (or maybe we should call them
"sane defaults").
I see a few problems with the modules/hook structure though: If, for
example, we provide a generic find-modules and the distro wants
completely other functionality, that part of Dracut would have to be
changed/disabled. That's a "patch" for me.
[snip]
>> I'm thinking of a debootstrappish system of suite/target (or
>> topic/flavour) where Dracut specifically delegates those tasks away it
>> cannot solve on its own. We might even provide some simple things like
>> just including all drivers for testing purposes or as a fallback
>> solution.
>
> Let's see how the current modules/hooks mechanism works for now. We can
> extend or scrap it if it turns out to not suit our needs.
I was thinking a bit along the line of what should be included on a
netboot initrd. Personally I wouldn't want to see hooks for cryptsetup
or lvm in it. Hence the idea of suite/target to select maybe a distro
(could be 'dracut' for generic) and different targets (might be netboot
or a combination of block,crypt,lvm).
But well... I guess I'm violating list rules again. Patches speak more
than words, I'll see what I can cook up.
--
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:40 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
2009-03-04 16:40 ` Seewer Philippe [this message]
[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=49AEAF16.6010008@bfh.ch \
--to=philippe.seewer-omb+w0dpw2o@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@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.