From: "H. Peter Anvin" <hpa@zytor.com>
To: Bodo Eggert <7eggert@gmx.de>
Cc: Al Boldi <a1426z@gawab.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH][retry-2] init: Introduce rootdir bootparm to select which dir to sys_chroot
Date: Sun, 18 Nov 2007 16:02:22 -0800 [thread overview]
Message-ID: <4740D28E.7080800@zytor.com> (raw)
In-Reply-To: <alpine.LSU.0.999.0711190042340.14144@be1.lrz>
Bodo Eggert wrote:
> On Sun, 18 Nov 2007, H. Peter Anvin wrote:
>> Bodo Eggert wrote:
>
>>> 1) This is useful for booting a rescue or test system, too. In those cases,
>>> you might want to have the old root moved somewhere.
>>> (Always "$rootdir/oldroot"? Additional parameter? I'm not sure ...)
>>>
>> Again, this is a good example of why this really shouldn't be additional
>> hacks in kernel space.
>
> ACK, but until kinit is default (and Godot arrives), this little hack does
> seem to be useful.
I disagree, on two accounts:
a. For as long as we keep throwing more crap into the kernel, kinit will
not get merged, because it "provides no new functionality."
b. You don't need kinit and kernel-tree integeration to do this in an
external initramfs. You can do this with any number of codebases as an
external initramfs.
-hpa
next prev parent reply other threads:[~2007-11-19 0:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9qVOO-4ZK-13@gated-at.bofh.it>
2007-11-18 19:53 ` [PATCH][retry-2] init: Introduce rootdir bootparm to select which dir to sys_chroot Bodo Eggert
2007-11-18 20:02 ` H. Peter Anvin
2007-11-18 23:50 ` Bodo Eggert
2007-11-19 0:02 ` H. Peter Anvin [this message]
2007-11-19 5:40 ` Al Boldi
2007-11-18 17:09 Al Boldi
2007-11-19 5:22 ` Arjan van de Ven
2007-11-19 5:56 ` Al Boldi
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=4740D28E.7080800@zytor.com \
--to=hpa@zytor.com \
--cc=7eggert@gmx.de \
--cc=a1426z@gawab.com \
--cc=akpm@linux-foundation.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