One important thing that leaves out is the interaction that this codehas with the rest of the kernel. That's critically important whenconsidering long-term maintenance, and I'd be curious how the OpenVZfolks view it.

> Now, we've gone in blind before - most notably on the> containers/cgroups/namespaces stuff. That hail mary pass worked out> acceptably, I think. Maybe we got lucky. I thought that> net-namespaces in particular would never get there, but it did.> > That was a very large and quite long-term-important user-visible> feature.> > checkpoint/restart/migration is also a long-term-...-feature. But if> at all possible I do think that we should go into it with our eyes a> little less shut.

One thing Ingo has asked for that I understand a bit more clearly is aprogrammatic statement of what is and is not covered by this currentcode. That's certainly one eye-opening activity which I'll get toimmediately.