From: Al Boldi <a1426z@gawab.com>
To: linux-kernel@vger.kernel.org
Cc: hpa@zytor.com, akpm@linux-foundation.org
Subject: Re: [PATCH] init: Introduce rootdir bootparm to select which dir to sys_chroot
Date: Wed, 7 Nov 2007 23:10:20 +0300 [thread overview]
Message-ID: <200711072310.20715.a1426z@gawab.com> (raw)
In-Reply-To: <200711061340.26112.a1426z@gawab.com>
Al Boldi wrote:
> This patch introduces a rootdir kernel boot parameter, which specifies the
> path to the kernel sys_chroot boot dir.
>
> This is useful for systems that have more than one distribution installed
> on the same fs/partition.
>
>
> Cc: H. Peter Anvin <hpa@zytor.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Signed-off-by: Al Boldi <a1426z@gawab.com>
>
> ---
>
> --- a/init/do_mounts.c
> +++ b/init/do_mounts.c
> @@ -252,6 +252,15 @@ __setup("rootflags=", root_data_setup);
> __setup("rootfstype=", fs_names_setup);
> __setup("rootdelay=", root_delay_setup);
>
> +static char * __initdata root_dir;
> +static int __init root_dir_setup(char *str)
> +{
> + root_dir = strcat("./",str);
This line is probably using an overloaded function that does not exist.
Use this instead:
static char __initdata root_dir[128];
static int __init root_dir_setup(char *str)
{
strcpy(root_dir, "./");
strlcat(root_dir, str, sizeof(root_dir) - strlen(root_dir) - 1);
return 1;
}
> +__setup("rootdir=", root_dir_setup);
> +
> static void __init get_fs_names(char *page)
> {
> char *s = page;
> @@ -469,6 +478,10 @@ void __init prepare_namespace(void)
> mount_root();
> out:
> sys_mount(".", "/", NULL, MS_MOVE, NULL);
> +
> + if(root_dir)
> + sys_chdir(root_dir);
> +
> sys_chroot(".");
> security_sb_post_mountroot();
> }
Thanks!
--
Al
next prev parent reply other threads:[~2007-11-06 20:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 10:40 [PATCH] init: Introduce rootdir bootparm to select which dir to sys_chroot Al Boldi
2007-11-07 20:10 ` Al Boldi [this message]
2007-11-06 20:13 ` H. Peter Anvin
2007-11-07 21:13 ` Al Boldi
2007-11-06 21:25 ` H. Peter Anvin
2007-11-09 4:36 ` Andrew Morton
2007-11-09 4:57 ` 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=200711072310.20715.a1426z@gawab.com \
--to=a1426z@gawab.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--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