mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Kujau <lists@nerdbynature.de>
To: devzero@web.de
Cc: ingo@elte.hu, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6.24] chroot= as a new kernel parameter
Date: Fri, 7 Mar 2008 23:32:37 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.1.00.0803072330080.7723@sheep.housecafe.de> (raw)
In-Reply-To: <187865500@web.de>

On Fri, 7 Mar 2008, devzero@web.de wrote:

>> * H. Peter Anvin <hpa@zytor.com> 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:

--- linux-2.6-git/Documentation/kernel-parameters.txt	2008-02-21 12:01:37.000000000 +0100
+++ linux-2.6-git/Documentation/kernel-parameters.txt.edited	2008-03-07 23:26:39.000000000 +0100
@@ -799,9 +799,12 @@ and is between 256 and 4096 characters.
  			See header of drivers/scsi/in2000.c.

  	init=		[KNL]
-			Format: <full_path>
+			Format: <full_path> <options>
  			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.

  	initcall_debug	[KNL] Trace initcalls as they are executed.  Useful
  			for working out where the kernel is dying during

Thanks,
Christian.
-- 
BOFH excuse #116:

the real ttys became pseudo ttys and vice-versa.

  reply	other threads:[~2008-03-07 22:32 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-07 21:04 devzero
2008-03-07 22:32 ` Christian Kujau [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-03-08 14:10 Al Boldi
2008-03-08 14:28 ` Christian Kujau
2008-03-08 16:34   ` Al Boldi
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
2008-03-06 20:57             ` Willy Tarreau
2008-03-07  8:23         ` Chris Wedgwood

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=alpine.DEB.1.00.0803072330080.7723@sheep.housecafe.de \
    --to=lists@nerdbynature.de \
    --cc=devzero@web.de \
    --cc=ingo@elte.hu \
    --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

all inboxes | Powered by JetHome®