linux-kernel - Re: [PATCH] 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>] [day] [month] [year] [list]

Date:	Mon, 03 Mar 2008 17:08:26 +0100
From:	Bodo Eggert <7eggert@....de>
To:	Pavel Machek <pavel@....cz>,
	Guillaume Chazarain <guichaz@...il.com>,
	Pawel Plociennik <paplociennik@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] chroot= as a new kernel parameter

Pavel Machek <pavel@....cz> wrote:
>> On Sat, Mar 1, 2008 at 8:09 PM, Pawel Plociennik <paplociennik@...il.com>

>> >  In the short this patch has added a new chroot= kernel parameter which can
>> >  be used to changing a chroot of an init process before it will has been
>> >  runed.
>> 
>> Wouldn't booting with 'init=/usr/sbin/chroot /path /sbin/init' achieve
>> the same effect?
>> Haven't tested it, just wondering.
> 
> This breaks down when there's no distribution installed in /, or when
> distro in / is badly broken.

Yes.

Real life example: I set up a system in qemu and moved it to ~/temp/foo
in order to test it before overwriting the old system. I had to boot into
/bin/sh, mount the home disc and chroot into that directory.

OTOH, I'm not sure if the kernel would have found my home if it were on LVM.


--
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/