public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Vilain <sam@vilain.net>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, Kirill Korotaev <dev@sw.ru>,
	herbert@13thfloor.at, devel@openvz.org,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	xemul@sw.ru, James Morris <jmorris@namei.org>
Subject: Re: [PATCH 0/7] uts namespaces: Introduction
Date: Mon, 10 Apr 2006 13:15:54 +1200	[thread overview]
Message-ID: <4439B1CA.2080806@vilain.net> (raw)
In-Reply-To: <20060407234815.849357768@sergelap>

Serge,

I have just imported your series into the GIT repository where I have
been collating the various recent related submissions at:

  git://vserver.utsl.gen.nz/vserver

A summary of the submissions imported to date are at:

  http://www.utsl.gen.nz/gitweb/?p=vserver;a=heads

I will endeavour to continue to collect and catalogue all vserver
related submissions I receive, see on LKML, or get pull requests for, as
a part of my efforts to merge this functionality.

Sam.

Serge E. Hallyn wrote:

>Introduce utsname namespaces.  Instead of a single system_utsname
>containing hostname domainname etc, a process can request it's
>copy of the uts info to be cloned.  The data will be copied from
>it's original, but any further changes will not be seen by processes
>which are not it's children, and vice versa.
>
>This is useful, for instance, for vserver/openvz, which can now clone
>a new uts namespace for each new virtual server.
>
>Aside from the debugging patch which comes last, this patchset does
>not actually implement a way for processes to unshare the uts namespace.
>The proper unsharing semantics are to be worked out later.
>
>Changes since last submission:
>  Restructured patchset so it compiles after each patch
>  Removed EXPORT_SYMBOL for unshare_uts_ns and free_uts_ns.
>    The former is now in the debugging pach and the latter gone
>    entirely, as unsharing is likely not something to be done
>    from modules!
>
>-serge
>
>
>  
>


  parent reply	other threads:[~2006-04-10  1:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060407234815.849357768@sergelap>
     [not found] ` <20060408045206.EAA8E19B8FF@sergelap.hallyn.com>
2006-04-08  7:09   ` [PATCH 3/7] uts namespaces: use init_utsname when appropriate Eric W. Biederman
2006-04-08 20:27     ` Serge E. Hallyn
2006-04-09  9:44       ` Eric W. Biederman
2006-04-09 10:14         ` Christoph Hellwig
2006-04-09 10:25           ` Christoph Hellwig
2006-04-09 10:36             ` Eric W. Biederman
2006-04-10 20:39         ` Serge E. Hallyn
2006-04-10 20:46           ` Serge E. Hallyn
2006-04-08 23:44     ` Sam Vilain
2006-04-09  0:12       ` [Devel] " Kir Kolyshkin
2006-04-09  9:25         ` Eric W. Biederman
2006-04-10  1:15 ` Sam Vilain [this message]
     [not found] ` <20060408045206.EFDD819B901@sergelap.hallyn.com>
2006-04-10 16:06   ` [Devel] [PATCH 4/7] uts namespaces: implement utsname namespaces Cedric Le Goater
2006-04-10 20:48     ` Serge E. Hallyn
2006-05-01 19:53 [PATCH 0/7] uts namespaces: Introduction Serge E. Hallyn

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=4439B1CA.2080806@vilain.net \
    --to=sam@vilain.net \
    --cc=dev@sw.ru \
    --cc=devel@openvz.org \
    --cc=ebiederm@xmission.com \
    --cc=herbert@13thfloor.at \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=serue@us.ibm.com \
    --cc=xemul@sw.ru \
    /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