From: ebiederm@xmission.com (Eric W. Biederman)
To: Michael Kerrisk <mtk-manpages@gmx.net>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>,
Kirill Korotaev <dev@openvz.org>,
Herbert Poetzl <herbert@13thfloor.at>,
Andrey Savochkin <saw@sw.ru>, Adrian Bunk <bunk@stusta.de>,
Cedric Le Goater <clg@fr.ibm.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: CLONE_NEWUTS documentation
Date: Sun, 05 Aug 2007 06:27:29 -0600 [thread overview]
Message-ID: <m1abt6kvym.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <46B599CA.9030302@gmx.net> (Michael Kerrisk's message of "Sun, 05 Aug 2007 11:35:06 +0200")
Michael Kerrisk <mtk-manpages@gmx.net> writes:
> Hello Serge,
>
> In 2.6.19, your patch to add support for CLONE_NEWUTS was included. Is
> there there some for-userland-programmers documentation of this flag
> somewhere? Would you be able to send some documentation to me (ideally as
> a patch to the clone.2 man page, but otherwise some plain text will do).
>
> If this flag is also supported for unshare(), then could you please send me
> a patch/text for that too?
Again a short summary
The utsname namespace encapsulates the global kernel identification stored
in struct utsname returned from uname(2).
It is a very trivial namespace but it allows you to set multiple hostnames
and nis domainnames on the same machine.
Eric
next prev parent reply other threads:[~2007-08-05 12:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 9:35 Michael Kerrisk
2007-08-05 12:27 ` Eric W. Biederman [this message]
2007-08-06 6:36 ` Michael Kerrisk
2007-08-06 12:49 ` Serge E. Hallyn
2008-11-19 19:11 Michael Kerrisk
2008-11-20 1:21 ` Eric W. Biederman
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
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=m1abt6kvym.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=bunk@stusta.de \
--cc=clg@fr.ibm.com \
--cc=dev@openvz.org \
--cc=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk-manpages@gmx.net \
--cc=saw@sw.ru \
--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
all inboxes | Powered by JetHome®