From: Christoph Hellwig <hch@infradead.org>
To: initramfs@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>,
Dave Jones <davej@redhat.com>,
cjwatson@ubuntu.com, Hannes Reinecke <hare@suse.de>
Subject: Re: Dracut -- Cross distribution initramfs infrastructure
Date: Wed, 17 Dec 2008 14:07:01 -0500 [thread overview]
Message-ID: <20081217190700.GA15377@infradead.org> (raw)
In-Reply-To: <1229540094.28858.150.camel@aglarond.local>
On Wed, Dec 17, 2008 at 01:54:54PM -0500, Jeremy Katz wrote:
> As davej started talking about a few months ago at Kernel Summit and
> LPC, there's a lot of duplication between distros on the tools used to
> generate the initramfs as well as the contents and how the initramfs
> works. Ultimately, there's little reason for this not to be something
> that is shared and worked on by everyone. Added to this is the fact
> that everyone's infrastructures for this have grown up over a long-ish
> period of time without significant amounts of reworking for the way that
> the kernel and early boot works these days.
>
> Therefore I've started on a new project, dracut, to try to be a new
> initramfs tool that can be used across various distributions. From the
> README...
It looks like Hannes has also been working on a new, modular initramfs
for a while:
http://git.kernel.org/?p=linux/kernel/git/hare/mkinitrd.git;a=summary
I hope you guys can get together and agree on one implementation..
next prev parent reply other threads:[~2008-12-17 19:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 18:54 Jeremy Katz
2008-12-17 19:07 ` Christoph Hellwig [this message]
2008-12-18 7:36 ` Hannes Reinecke
2008-12-19 7:41 ` Seewer Philippe
2008-12-19 8:18 ` Bernhard Walle
2008-12-19 13:55 ` Hannes Reinecke
2008-12-19 15:27 ` Theodore Tso
2008-12-19 16:56 ` Jeremy Katz
2008-12-20 13:50 ` Daniel Pittman
2008-12-20 18:22 ` Dave Jones
2009-01-07 16:04 ` Hannes Reinecke
2008-12-17 19:31 ` Neil Horman
2008-12-18 9:27 ` Loïc Grenié
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=20081217190700.GA15377@infradead.org \
--to=hch@infradead.org \
--cc=cjwatson@ubuntu.com \
--cc=davej@redhat.com \
--cc=hare@suse.de \
--cc=initramfs@vger.kernel.org \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome