Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932104AbWAQQTZ (ORCPT ); Tue, 17 Jan 2006 11:19:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932106AbWAQQTZ (ORCPT ); Tue, 17 Jan 2006 11:19:25 -0500 Received: from elvis.mu.org ([192.203.228.196]:51702 "EHLO elvis.mu.org") by vger.kernel.org with ESMTP id S932104AbWAQQTY (ORCPT ); Tue, 17 Jan 2006 11:19:24 -0500 Message-ID: <43CD18FF.4070006@FreeBSD.org> Date: Tue, 17 Jan 2006 08:19:11 -0800 From: Suleiman Souhlal User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Serge Hallyn CC: linux-kernel@vger.kernel.org, Hubertus Franke , Cedric Le Goater , Dave Hansen Subject: Re: RFC [patch 00/34] PID Virtualization Overview References: <20060117143258.150807000@sergelap> In-Reply-To: <20060117143258.150807000@sergelap> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 807 Lines: 19 Serge Hallyn wrote: > The mechanism to start a container > is to 'echo "container_name" > /proc/container' which creates a new > container and associates the calling process with it. All subsequently > forked tasks then belong to that container. > There is a separate pid space associated with each container. > Only processes/task belonging to the same container "see" each other. Why does there need a separate pid space for each container? You don't really need one to make sure that only processes in the same containers can see each other. -- Suleiman - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/