From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cedric Le Goater Subject: Re: [DRAFT] Container mini-summit notes v0.01 Date: Thu, 06 Sep 2007 13:22:11 +0200 Message-ID: <46DFE2E3.20003@fr.ibm.com> References: <46DE9E1C.6010309@fr.ibm.com> <46DEEBED.5010303@openvz.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <46DEEBED.5010303-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Pavel Emelyanov Cc: Linux Containers List-Id: containers.vger.kernel.org >> * possible direction for C/R user api >> . checkpoint/restart syscalls >> . C/R file systems >> solves the set id issue >> elegant but exposes too much the ABI > > I vote for the filesystem :) I'd add more details as we did on mini-summit. > > tasks > `- > `- > ... > > files > `- 1 -> /* made as a symlink */ > 2 -> /* if socket point to net/ objects */ > memory > `- -> /* symlink to mm objects */ > > ... > > mm > ipc > network > > and so on and so forth. We need to dig on this idea. RFC ? C.