>> Q: What additional work needs to be done to it? A: Fill in the >> gory details following the examples so far. Current WIP includes >> inet sockets, event-poll, and early work on inotify, mount >> namespace and mount-points, pseudo file systems AM> Will this new code muck up the kernel, or will it be clean? I have (and have previously posted) prototype code to do c/r of open sockets, ignoring some things like updating timers and such. It looks rather similar to the existing UNIX bits, and is even easier in some ways. One particular use case is only migrating listening sockets and allowing the connected ones to be reset upon restart. That enables a bunch of things like apache, postfix, vncserver, and even sshd. I will pull the listen-only bits out of my current patch, scrape off a little bitrot, and post them in a few days. -- Dan Smith IBM Linux Technology Center email: danms@xxxxxxxxxx _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
