From: ebiederm@xmission.com (Eric W. Biederman)
To: Michael Kerrisk <mtk.manpages@googlemail.com>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-man@vger.kernel.org, Kirill Korotaev <dev@openvz.org>,
Herbert Poetzl <herbert@13thfloor.at>,
Andrey Savochkin <saw@sw.ru>,
Subrata Modak <subrata@linux.vnet.ibm.com>
Subject: Re: CLONE_NEWUTS documentation
Date: Wed, 19 Nov 2008 17:21:56 -0800 [thread overview]
Message-ID: <m1y6zfgpjf.fsf@frodo.ebiederm.org> (raw)
In-Reply-To: <492464F8.8070101@gmail.com> (Michael Kerrisk's message of "Wed, 19 Nov 2008 14:11:52 -0500")
Michael Kerrisk <mtk.manpages@googlemail.com> writes:
> Serge, Eric,
>
> Below is a patch to document the CLONE_NEWUTS flag that was
> added in 2.6.19.
>
> Could you please review and let me know of improvements
> or inaccuracies?
>
> By the way, does anyone know where the UTS name in the uname()
> API comes from? My best guess is that it's from Unix Timesharing
> System, but I don't know this for sure.
>
> Cheers,
>
> Michael
>
> diff --git a/man2/clone.2 b/man2/clone.2
> index 7212332..80f9caf 100644
> --- a/man2/clone.2
> +++ b/man2/clone.2
> @@ -341,6 +340,33 @@ configuration option and that the process be privileged
> This flag can't be specified in conjunction with
> .BR CLONE_THREAD .
> .TP
> +.BR CLONE_NEWUTS " (since Linux 2.6.19)"
> +If
> +.B CLONE_NEWUTS
> +is set, then create the process in a new UTS namespace.
> +If this flag is not set, then (as with
> +.BR fork (2)),
> +the process is created in the same UTS namespace as
> +the calling process.
> +This flag is intended for the implementation of control groups.
See my previous email about containers vs control groups.
There are some corner cases with NFS usage in the kernel that still
need to be resolved but otherwise the uts namespace is considered correct
and complete.
Eric
next prev parent reply other threads:[~2008-11-20 1:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 19:11 CLONE_NEWUTS documentation Michael Kerrisk
2008-11-20 1:21 ` Eric W. Biederman [this message]
2008-11-20 11:51 ` Michael Kerrisk
2008-11-23 22:47 ` Serge E. Hallyn
2008-11-24 23:14 ` Michael Kerrisk
2008-11-24 23:45 ` Serge E. Hallyn
-- strict thread matches above, loose matches on Subject: below --
2007-08-05 9:35 Michael Kerrisk
2007-08-05 12:27 ` Eric W. Biederman
2007-08-06 6:36 ` Michael Kerrisk
2007-08-06 12:49 ` 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=m1y6zfgpjf.fsf@frodo.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=dev@openvz.org \
--cc=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@googlemail.com \
--cc=saw@sw.ru \
--cc=serue@us.ibm.com \
--cc=subrata@linux.vnet.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