mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: linux-kernel@vger.kernel.org
Cc: Chris Wright <chrisw@osdl.org>, Rik van Riel <riel@redhat.com>,
	torvalds@osdl.org, greg@kroah.com, vserver@solucorp.qc.ca
Subject: Re: [vserver] Re: sys_vserver
Date: Wed, 1 Oct 2003 16:05:26 -0700	[thread overview]
Message-ID: <20031001160526.R14398@osdlab.pdx.osdl.net> (raw)
In-Reply-To: <20031001225247.GA26496@DUK2.13thfloor.at>; from herbert@13thfloor.at on Thu, Oct 02, 2003 at 12:52:48AM +0200

* Herbert Poetzl (herbert@13thfloor.at) wrote:
> 
> hmm, okay I see it now clearly, we should take
> the approach which was so successful for scsi ...
> 
> echo "vserver add-new-vserver 100 0 1 192 0 0 1" >/proc/1/attr/new
> 
> and of course to 'change' the context, a simple
> 
> echo "vserver change-to-old-context 100" >/proc/self/attr/migrate
> (and it was never seen again, because it vanished in context 100)
> 
> will be sufficient ...

Sorry if I don't follow your example correctly.  There is an attr/prev
as well as attr/current, if you are worried the previous context would
be lost.

> seriously I am completely on your side if we talk about
> limiting a process or changing it's environment, even
> if we talk about setting a class assignment, but I just 
> don't believe it's the perfect solution for everything ...

Yes, I agree, it won't be useful for everything, but where
possible/sensible, we should reuse it.

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

      reply	other threads:[~2003-10-01 23:05 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                 ` sys_vserver Chris Wright
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 [this message]

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=20031001160526.R14398@osdlab.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=greg@kroah.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®