From: Chris Wright <chrisw@osdl.org>
To: Rik van Riel <riel@redhat.com>
Cc: Chris Wright <chrisw@osdl.org>, James Morris <jmorris@redhat.com>,
torvalds@osdl.org, greg@kroah.com, linux-kernel@vger.kernel.org,
vserver@solucorp.qc.ca
Subject: Re: sys_vserver
Date: Wed, 1 Oct 2003 16:32:03 -0700 [thread overview]
Message-ID: <20031001163203.U14398@osdlab.pdx.osdl.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0310011916260.4454-100000@chimarrao.boston.redhat.com>; from riel@redhat.com on Wed, Oct 01, 2003 at 07:17:44PM -0400
* Rik van Riel (riel@redhat.com) wrote:
> On Wed, 1 Oct 2003, Chris Wright wrote:
> > * James Morris (jmorris@redhat.com) wrote:
> > > I think virtualization is important/useful enough to warrant an API of
> > > it's own. It could be similar to LSM, e.g. allow pluggable
> > > virtualization modules, with no cost for the base kernel.
> >
> > Doesn't sound like 2.6 material.
>
> Maybe not, but it does sound like something we want to be
> ready by the time 2.7 is forked ;)
Yes, good point ;-) And I do agree it's a useful concept.
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2003-10-01 23:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 18:51 sys_vserver Chris Wright
2003-10-01 18:58 ` sys_vserver Rik van Riel
2003-10-01 19:15 ` sys_vserver Chris Wright
2003-10-01 19:21 ` sys_vserver Rik van Riel
2003-10-01 19:47 ` sys_vserver Herbert Poetzl
2003-10-01 21:16 ` sys_vserver Chris Wright
2003-10-01 21:44 ` sys_vserver Rik van Riel
2003-10-01 22:57 ` sys_vserver James Morris
2003-10-01 23:14 ` sys_vserver Chris Wright
2003-10-01 23:17 ` sys_vserver Rik van Riel
2003-10-01 23:32 ` Chris Wright [this message]
2003-10-01 23:22 ` sys_vserver Linus Torvalds
2003-10-01 23:28 ` sys_vserver Rik van Riel
2003-10-01 22:52 ` [vserver] sys_vserver Herbert Poetzl
2003-10-01 23:05 ` Chris Wright
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=20031001163203.U14398@osdlab.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=greg@kroah.com \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--cc=torvalds@osdl.org \
--cc=vserver@solucorp.qc.ca \
/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
all inboxes | Powered by JetHome®