From: Pawel Plociennik <paplociennik@gmail.com>
To: Pavel Machek <pavel@ucw.cz>, linux-kernel@vger.kernel.org
Subject: [PATCH 2.6.24] chroot= as a new kernel parameter
Date: Thu, 6 Mar 2008 00:01:38 -0500 [thread overview]
Message-ID: <200803060001.38432.paplociennik@gmail.com> (raw)
Hi Andrew and other *real* hackers,
I have sent a *last* version of a patch which it has added a new kernel parameter chroot=It were discusioned a *long time* on a lkml so I hope that it will has been applied.
Thanks,Pawel
Acked-by: Pavel Machek <pavel@suse.cz>Signed-off-by: Pawel Plociennik <paplociennik@gmail.com>
---diff -urp linux-2.6.24-orig/Documentation/kernel-parameters.txt linux-2.6.24/Documentation/kernel-parameters.txt--- linux-2.6.24-orig/Documentation/kernel-parameters.txt 2008-02-25 20:53:26.000000000 -0500+++ linux-2.6.24/Documentation/kernel-parameters.txt 2008-03-04 09:51:52.000000000 -0500@@ -381,6 +381,8 @@ and is between 256 and 4096 characters. Value can be changed at runtime via /selinux/checkreqprot. + chroot= [KNL] change a root for init process.+ clock= [BUGS=X86-32, HW] gettimeofday clocksource override. [Deprecated] Forces specified clocksource (if available) to be useddiff -urp linux-2.6.24-orig/init/main.c linux-2.6.24/init/main.c--- linux-2.6.24-orig/init/main.c 2008-03-01 12:58:37.000000000 -0500+++ linux-2.6.24/init/main.c 2008-03-05 15:08:20.000000000 -0500@@ -755,8 +755,20 @@ static void __init do_pre_smp_initcalls( spawn_softlockup_task(); } +static void *chroot_str;+static int __init chroot_setup(char *str)+{+ chroot_str = str;+ return 1;+}+__setup("chroot=", chroot_setup);+ static void run_init_process(char *init_filename) {+ if (chroot_str)+ if (sys_chroot(chroot_str) < 0)+ panic("chroot=%s failed\n", chroot_str);+ argv_init[0] = init_filename; kernel_execve(init_filename, argv_init, envp_init); }ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next reply other threads:[~2008-03-05 23:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 5:01 Pawel Plociennik [this message]
2008-03-06 4:58 ` [PATCH 2.6.24] chroot= as a new kernel parameter 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
-- strict thread matches above, loose matches on Subject: below --
2008-03-07 21:04 devzero
2008-03-07 22:32 ` Christian Kujau
2008-03-08 14:10 Al Boldi
2008-03-08 14:28 ` Christian Kujau
2008-03-08 16:34 ` Al Boldi
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=200803060001.38432.paplociennik@gmail.com \
--to=paplociennik@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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