Date: Thu, 6 Mar 2008 12:37:29 +0100
From: Ingo Molnar <mingo@elte.hu>
To: Chris Wedgwood <cw@f00f.org>
Cc: Pawel Plociennik <paplociennik@gmail.com>, Pavel Machek <pavel@ucw.cz>,
       linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.24] chroot= as a new kernel parameter
Message-ID: <20080306113729.GA18403@elte.hu>
References: <200803060001.38432.paplociennik@gmail.com> <20080306103422.GA5511@puku.stupidest.org> <20080306104448.GG13391@elte.hu> <20080306112212.GA9261@puku.stupidest.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20080306112212.GA9261@puku.stupidest.org>
User-Agent: Mutt/1.5.17 (2007-11-01)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 923
Lines: 24


* 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.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/