>> * 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 > `- <pid1> > `- <tid1> > ... > <tidN> > files > `- 1 -> /* made as a symlink */ > 2 -> /* if socket point to net/ objects */ > memory > `- <vma1> -> /* symlink to mm objects */ > <pid2> > ... > <pidN> > mm > ipc > network > > and so on and so forth. We need to dig on this idea. RFC ? C. _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
