From: "H. Peter Anvin" <hpa@zytor.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Michael Neuling <mikey@neuling.org>,
klibc@zytor.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
miltonm@bga.com, Al Viro <viro@ftp.linux.org.uk>
Subject: Re: [klibc] Re: [PATCH] initramfs: CPIO unpacking fix
Date: Wed, 22 Mar 2006 08:05:14 -0800 [thread overview]
Message-ID: <442175BA.6000207@zytor.com> (raw)
In-Reply-To: <4420F93C.1050705@garzik.org>
Jeff Garzik wrote:
>
> For the kernel, I would regard that as needless code... Coding for a
> chain of CPIO archives overwriting each other seems like overengineering.
>
No, it's actually significant. The ability to compose initramfs
contents from multiple sources is one of the major improvements over initrd.
For example, people has asked that kinit should be able to be called
from user-provided (initrd-loaded) initramfs code. The easiest way to
do that is to have the in-kernel module have:
/init -> /kinit
/kinit
... and allow /init to be overwritten.
-hpa
next prev parent reply other threads:[~2006-03-22 16:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-16 7:37 [PATCH] Chained CPIOs writing to the same file bug Michael Neuling
[not found] ` <20060217160621.99b0ffd4.mikey@neuling.org>
2006-02-21 23:45 ` [PATCH] initramfs: multiple CPIO unpacking fix Michael Neuling
2006-02-22 2:14 ` [klibc] " Jeff Bailey
2006-02-22 2:17 ` H. Peter Anvin
2006-03-22 6:12 ` [PATCH] initramfs: " Michael Neuling
2006-03-22 7:14 ` Jeff Garzik
2006-03-22 16:05 ` H. Peter Anvin [this message]
2006-03-22 22:23 ` Rob Landley
2006-03-22 23:22 ` Jeff Garzik
2006-04-07 17:33 ` H. Peter Anvin
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=442175BA.6000207@zytor.com \
--to=hpa@zytor.com \
--cc=jeff@garzik.org \
--cc=klibc@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikey@neuling.org \
--cc=miltonm@bga.com \
--cc=viro@ftp.linux.org.uk \
/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