From: Al Boldi <a1426z@gawab.com>
To: Christian Kujau <lists@nerdbynature.de>
Subject: Re: [PATCH 2.6.24] chroot= as a new kernel parameter
Date: Sat, 8 Mar 2008 19:34:03 +0300
User-Agent: KMail/1.5
Cc: LKML <linux-kernel@vger.kernel.org>
References: <200803081710.24137.a1426z@gawab.com> <alpine.DEB.1.00.0803081522240.7522@sheep.housecafe.de>
In-Reply-To: <alpine.DEB.1.00.0803081522240.7522@sheep.housecafe.de>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200803081934.03331.a1426z@gawab.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1164
Lines: 38

Christian Kujau wrote:
> On Sat, 8 Mar 2008, Al Boldi wrote:
> > Nice try, but this only works on the surface.  Try remounting root to see
> > what I mean.
>
> Are you suggesting that hpa's init= thingy doesn't support remounting
> root?

Exactly.

> If so, it'd have to be mentioned in kernel-parameters.txt as well.
>
> > Now, for a patch that actually does what we want, try this:
> > [PATCH][retry-2] init: Introduce rootdir bootparm to select which dir
> > to sys_chroot
>
> I didn't intend to introduce another bootparam, because of -ENOSKILL.
> But somewhere in this thread is a patch for the chroot= bootparam, I
> have not tested it though...

Sure,  your doc effort is much appreciated, but neither the proposed patch nor 
the init= trick works as advertised, due to some strange /dev/root 
dependencies.

Now, the rootdir= patch works around this by binding the rootdir before 
sys_chroot.


Thanks!

--
Al

--
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/