From: Dave Hansen <haveblue@us.ibm.com>
To: Sam Vilain <sam@vilain.net>
Cc: linux-kernel@vger.kernel.org,
Herbert Poetzl <herbert@13thfloor.at>,
"Eric W.Biederman" <ebiederm@xmission.com>,
OpenVZ developers list <dev@openvz.org>,
"Serge E.Hallyn" <serue@us.ibm.com>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [RFC] [PATCH 0/7] Some basic vserver infrastructure
Date: Tue, 21 Mar 2006 10:50:11 -0800 [thread overview]
Message-ID: <1142967011.10906.185.camel@localhost.localdomain> (raw)
In-Reply-To: <20060321061333.27638.63963.stgit@localhost.localdomain>
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
next parent reply other threads:[~2006-03-21 18:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060321061333.27638.63963.stgit@localhost.localdomain>
2006-03-21 18:50 ` Dave Hansen [this message]
2006-03-21 21:08 ` Sam Vilain
2006-03-21 21:32 ` Dave Hansen
2006-03-21 23:12 ` Sam Vilain
2006-03-22 5:18 ` Sam Vilain
2006-03-22 7:13 ` Eric W. Biederman
2006-03-23 4:17 ` Sam Vilain
2006-03-24 15:36 ` [Devel] " Kirill Korotaev
2006-03-27 12:45 ` Serge E. Hallyn
2006-03-28 5:28 ` Sam Vilain
2006-03-29 12:07 ` Kirill Korotaev
2006-03-29 13:47 ` Serge E. Hallyn
2006-03-29 21:30 ` Sam Vilain
2006-04-19 7:50 ` Eric W. Biederman
2006-04-19 21:42 ` Sam Vilain
2006-03-22 6:41 ` Eric W. Biederman
2006-03-23 4:29 ` Sam Vilain
2006-03-23 4:50 ` Andrew Morton
2006-03-24 15:38 ` Kirill Korotaev
2006-03-24 15:37 ` Kirill Korotaev
2006-03-24 20:28 ` Eric W. Biederman
2006-03-24 21:01 ` Herbert Poetzl
2006-03-24 21:13 ` Eric W. Biederman
2006-03-24 21:40 ` Herbert Poetzl
2006-03-24 22:30 ` Eric W. Biederman
2006-03-25 18:37 ` Eric W. Biederman
[not found] ` <20060321061333.27638.9112.stgit@localhost.localdomain>
2006-03-21 18:53 ` [RFC] [PATCH 1/7] Add process virtualisation umbrella structure (vx_info) Dave Hansen
2006-03-21 21:52 ` Sam Vilain
2006-03-22 2:02 ` Herbert Poetzl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1142967011.10906.185.camel@localhost.localdomain \
--to=haveblue@us.ibm.com \
--cc=akpm@osdl.org \
--cc=dev@openvz.org \
--cc=ebiederm@xmission.com \
--cc=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@vilain.net \
--cc=serue@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome