Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750814AbWBFJHH (ORCPT ); Mon, 6 Feb 2006 04:07:07 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750811AbWBFJHH (ORCPT ); Mon, 6 Feb 2006 04:07:07 -0500 Received: from mailhub.sw.ru ([195.214.233.200]:41331 "EHLO relay.sw.ru") by vger.kernel.org with ESMTP id S1750814AbWBFJHE (ORCPT ); Mon, 6 Feb 2006 04:07:04 -0500 Message-ID: <43E71219.90801@sw.ru> Date: Mon, 06 Feb 2006 12:08:41 +0300 From: Kirill Korotaev User-Agent: Mozilla/5.0 (X11; U; Linux i686; ru-RU; rv:1.2.1) Gecko/20030426 X-Accept-Language: ru-ru, en MIME-Version: 1.0 To: Hubertus Franke CC: Greg KH , Dave Hansen , Linus Torvalds , Kirill Korotaev , Andrew Morton , Linux Kernel Mailing List , clg@fr.ibm.com, alan@lxorguk.ukuu.org.uk, serue@us.ibm.com, arjan@infradead.org, Rik van Riel , Alexey Kuznetsov , Andrey Savochkin , devel@openvz.org, Pavel Emelianov Subject: Re: [RFC][PATCH 1/5] Virtualization/containers: startup References: <43E38BD1.4070707@openvz.org> <43E3915A.2080000@sw.ru> <1138991641.6189.37.camel@localhost.localdomain> <20060203201945.GA18224@kroah.com> <43E3BE66.6050200@watson.ibm.com> <43E615BA.1080402@sw.ru> <43E61C47.8070905@watson.ibm.com> In-Reply-To: <43E61C47.8070905@watson.ibm.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1047 Lines: 30 > Just lazy's man's development version of a faked sys_call to create the > container > without having to go through all architectures ... > Nothing permanent.. >>> How about an additional sys_exec_container( exec_args + >>> "container_name"). >>> This does all the work like exec, but creates new container >>> with name "..." and attaches task to new container. >>> If name exists, an error -EEXIST will be raised ! >> >> >> Why do you need exec? > > > (a) how do you create/destroy a container > (b) how do you attach yourself to it? a) create via syscall. destroyed when the last process dies in container. b) syscall which changes container. you need to close unneeded resources, change context and fork(). That's it. The whole process is exactly the same as if you changes UID. - 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/