Quoting Eric W. Biederman (ebiederm@xxxxxxxxxxxx): > "Serge E. Hallyn" <serue@xxxxxxxxxx> writes: > > > Quoting Eric W. Biederman (ebiederm@xxxxxxxxxxxx): > >> "Serge E. Hallyn" <serue@xxxxxxxxxx> writes: > >> > >> > Right, the whole point of Daniel including a 'reading list' was just so > >> > that we can avoid wasting time discussing existing implementations. So > >> > he wasn't suggesting that we would be discussing those in detail, in > >> > fact quite the opposite. > >> > >> Right however he was suggesting we discuss how to implement it without > >> agreeing on basic principles. Maybe I'm wrong and all of the different > >> development groups have a common idea of what needs to be done but > >> I would be surprised if that were the case. > > > > IMO recent threads have clearly proven that you're right about basic > > principles. Question is what is the right level to start at first, and > > how do we go about reaching concensus? I.e. is the first question > > whether we should do a fully in-kernel checkpoint and restart vs > > entirely userspace vs a mix, or is there another place we should start? > > Where all good kernel features start. With the necessary mechanisms in > the kernel and the policy in user space. > > If we want to replay all of the user space actions to create the > environment at the time of the checkpoint we already have all of the > kernel support we need as the applications go to their current state > using current system calls. > > I think we want something a bit more efficient. > > > It sounds like you have some good ideas in any case on where to start so > > I'm glad you'll be there :) > > > Will we have a white board or a large piece paper or something we can draw > on and talk about? > > Eric Hi C., I'm sorry after all the emails I'm not straight on what we're actually getting. We have a U-shaped room, but do we have a blackboard or whiteboard? Is there a speakerphone? Wireless or at least wired internet? thanks, -serge _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers