Re: [RFC] [PATCH 0/7] Some basic vserver infrastructure

[Dave Hansen <haveblue@us.ibm.com>]

On Tue, 2006-03-21 at 18:13 +1200, Sam Vilain wrote:
> Here is a work in progress of trying to extract some the core vserver
> architecture and present it as an incremental set of patches.

Hi Sam,

These patches are certainly getting better and better broken out all the
time.  Nice work.

But, I worry that they just aren't generic enough yet.  I don't see any
response from any of the other "container/namespace/vps" people.  I fear
that this means that they don't look broadly useful enough, yet.

That said, at this point, I'd just about rather have _anything_ merged
than the nothing we have at this point.  As we throw patches back and
forth, we can't seem to agree on even some very small points.  

I also have a sinking feeling that everybody has gone back off and
continues to develop their own out-of-tree functionality, deepening the
patch divide.

Is there anything we could merge that we _all_ don't like?  I'm pretty
convinced that no single solution will support Eric's, OpenVZ's, and
VServer's _existing_ usage models.  Somebody is going to have to bend,
or nothing will ever get merged.  Any volunteers? ;)

What about going back to the very simple "struct container" on which to
build?

	http://lkml.org/lkml/2006/2/3/205

-- Dave

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/