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: <3d8471ca0803021005o46f99282l77d412306877607a@mail.gmail.com>
Date:	Sun, 2 Mar 2008 19:05:49 +0100
From:	"Guillaume Chazarain" <guichaz@...il.com>
To:	"Pawel Plociennik" <paplociennik@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] chroot= as a new kernel parameter

On Mon, Mar 3, 2008 at 12:59 AM, Pawel Plociennik
<paplociennik@...il.com> wrote:
> On Sunday 02 March 2008 11:00, Guillaume Chazarain wrote:
>  > Wouldn't booting with 'init=/usr/sbin/chroot /path /sbin/init' achieve
>  > the same effect?

>  I think that procces which has pid 0 is a special procces

You mean pid 1, right? ;-)

> because it
>  removes a *zombie* procceses so it is good to use a *dedicated*
>  program for it such as a /sbin/init .
>  /usr/sbin/chroot doesn't remove a *zombie* procceses :-(

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.

Thanks.

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