Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754909AbYCHOKz (ORCPT ); Sat, 8 Mar 2008 09:10:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753499AbYCHOKp (ORCPT ); Sat, 8 Mar 2008 09:10:45 -0500 Received: from [212.12.190.238] ([212.12.190.238]:35927 "EHLO raad.intranet" rhost-flags-FAIL-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1753463AbYCHOKp (ORCPT ); Sat, 8 Mar 2008 09:10:45 -0500 From: Al Boldi To: linux-kernel@vger.kernel.org Subject: Re: [PATCH 2.6.24] chroot= as a new kernel parameter Date: Sat, 8 Mar 2008 17:10:24 +0300 User-Agent: KMail/1.5 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <200803081710.24137.a1426z@gawab.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1336 Lines: 38 Christian Kujau wrote: > On Fri, 7 Mar 2008, devzero@web.de wrote: > >> * H. Peter Anvin wrote: > >>> init=/path/to/any/sbin/chroot /newroot /sbin/init > > Great, I was looking for something like this myself some time ago! > > > wouldn`t it be useful to add a hint to kernel-parameters.txt ? > > How about: > > init= [KNL] > - Format: > + Format: > Run specified binary instead of /sbin/init as init > - process. > + process. init= is able to take more than one option > + allowing us to do: > + init=/path/to/any/sbin/chroot /newroot /sbin/init > + ...and thus booting into /newroot. Nice try, but this only works on the surface. Try remounting root to see what I mean. 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 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/