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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 7 Mar 2008 00:23:41 -0800
From:	Chris Wedgwood <cw@...f.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Pawel Plociennik <paplociennik@...il.com>,
	Pavel Machek <pavel@....cz>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2.6.24] chroot= as a new kernel parameter

On Thu, Mar 06, 2008 at 12:37:29PM +0100, Ingo Molnar wrote:

> while i have no personal use for chroot=, i generally test distros
> that way, yes - and i try to keep them as unmodified as possible.

It's not clear to me how this would work.

If the distro uses an initrd (most do now?) how will this work?  The
chroot will happen inside the initrd which will then break (because
/init won't be there).

> _Everything_ we do on the boot commandline that affects user-space
> can be done in an initrd in theory - but still we have hundreds of
> boot options.

Precendent alone isn't a good reason to do something, a change should
have merit of it's own.

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