LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Pavel Machek <pavel@ucw.cz>
Cc: Ingo Molnar <mingo@elte.hu>, Chris Wedgwood <cw@f00f.org>,
Pawel Plociennik <paplociennik@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.24] chroot= as a new kernel parameter
Date: Thu, 06 Mar 2008 20:46:21 +0100 [thread overview]
Message-ID: <1204832781.6241.269.camel@lappy> (raw)
In-Reply-To: <20080306115315.GA8972@elf.ucw.cz>
On Thu, 2008-03-06 at 12:53 +0100, Pavel Machek wrote:
> On Thu 2008-03-06 12:37:29, Ingo Molnar wrote:
> >
> > * Chris Wedgwood <cw@f00f.org> wrote:
> >
> > > > But given an existing initrd (which might have come from the distro,
> > > > etc.) i prefer adding boot options instead of modifying the initrd.
> > >
> > > I assume this is so you have have /distro1 /distro2 and use your boot
> > > option to (help) select which one you boot into?
> >
> > while i have no personal use for chroot=, i generally test distros that
> > way, yes - and i try to keep them as unmodified as possible.
> >
> > "Use the initrd as an extended boot commandline" is a poor answer IMO.
> >
> > _Everything_ we do on the boot commandline that affects user-space can
> > be done in an initrd in theory - but still we have hundreds of boot
> > options.
>
> Yes, please. chroot= is useful, nonintrusive, and it just should be there.
As much as I hate initrd, and all features building dependencies on it,
I don't see the need for either initrd or kernel support for chroot= as
it can be trivially done using a slightly longer init=.
next prev parent reply other threads:[~2008-03-06 20:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 5:01 Pawel Plociennik
2008-03-06 4:58 ` H. Peter Anvin
2008-03-06 10:27 ` Ingo Molnar
2008-03-06 15:17 ` H. Peter Anvin
2008-03-06 20:57 ` Ingo Molnar
2008-03-06 21:05 ` H. Peter Anvin
2008-03-06 21:20 ` Pavel Machek
2008-03-06 21:30 ` H. Peter Anvin
2008-03-06 22:05 ` Matthias Schniedermeyer
2008-03-07 10:36 ` Bernd Petrovitsch
2008-03-07 12:28 ` H. Peter Anvin
2008-03-06 21:42 ` Ingo Molnar
2008-03-06 21:50 ` H. Peter Anvin
2008-03-06 22:22 ` Ingo Molnar
2008-03-07 4:53 ` Greg Schafer
2008-03-07 9:27 ` Måns Rullgård
2008-03-06 16:54 ` Pawel Plociennik
2008-03-06 15:47 ` Pawel Plociennik
2008-03-06 10:34 ` Chris Wedgwood
2008-03-06 10:44 ` Ingo Molnar
2008-03-06 11:22 ` Chris Wedgwood
2008-03-06 11:37 ` Ingo Molnar
2008-03-06 11:53 ` Pavel Machek
2008-03-06 19:46 ` Peter Zijlstra [this message]
2008-03-06 20:57 ` Willy Tarreau
2008-03-07 8:23 ` Chris Wedgwood
2008-03-07 21:04 devzero
2008-03-07 22:32 ` Christian Kujau
2008-03-08 14:10 Al Boldi
2008-03-08 14:28 ` Christian Kujau
2008-03-08 16:34 ` 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=1204832781.6241.269.camel@lappy \
--to=a.p.zijlstra@chello.nl \
--cc=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paplociennik@gmail.com \
--cc=pavel@ucw.cz \
--subject='Re: [PATCH 2.6.24] chroot= as a new kernel parameter' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).