linux-kernel - Re: [PATCH 2.6.24] chroot= as a new kernel parameter

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <alpine.DEB.1.00.0803072330080.7723@sheep.housecafe.de>
Date:	Fri, 7 Mar 2008 23:32:37 +0100 (CET)
From:	Christian Kujau <lists@...dbynature.de>
To:	devzero@....de
cc:	ingo@...e.hu, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2.6.24] chroot= as a new kernel parameter

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

>> * H. Peter Anvin <hpa@...or.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/