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

Message-ID: <20080303141203.GB12606@elf.ucw.cz>
Date:	Mon, 3 Mar 2008 15:12:03 +0100
From:	Pavel Machek <pavel@....cz>
To:	Pawel Plociennik <paplociennik@...il.com>
Cc:	Guillaume Chazarain <guichaz@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] chroot= as a new kernel parameter

On Sun 2008-03-02 20:09:03, Pawel Plociennik wrote:
> On Sunday 02 March 2008 13:05, Guillaume Chazarain wrote:
> 
> > You mean pid 1, right? ;-)
> Of course that (my brain has been mistaked) :-(
> > 
> > Sure, but chroot should then exec /sbin/init as per the given kernel
> > command line. And then you run a real init.
> > 
> > I cannot try it as I don't have another distribution installed in a
> > subdirectory, but if you could test it we would quickly know if it
> > works or not.
> > 
> You have right.
> I have tested that and it  *works* :-)
> so I thing that my patch is *unnecessary* now :-(

Actually I disagree here. This means that if distro in / breaks, you
will not be able to boot in ditstro in /foo any more :-(.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/