From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: mtk.manpages@gmail.com
Subject: man-pages-3.73 is released
Date: Sun, 21 Sep 2014 13:58:49 +0200 [thread overview]
Message-ID: <541EBD79.706@gmail.com> (raw)
Gidday,
The Linux man-pages maintainer proudly announces:
man-pages-3.73 - man pages for Linux
Tarball download:
http://www.kernel.org/doc/man-pages/download.html
Git repository:
https://git.kernel.org/cgit/docs/man-pages/man-pages.git/
Online changelog:
http://man7.org/linux/man-pages/changelog.html#release_3.73
A short summary of the release is blogged at:
http://linux-man-pages.blogspot.com/2014/09/man-pages-373-is-released.html
The current version of the pages is browsable at:
http://man7.org/linux/man-pages/
A few changes in this release that may be of interest to readers of
this list are given below.
Cheers,
Michael
==================== Changes in man-pages-3.73 ====================
New and rewritten pages
-----------------------
namespaces.7
Michael Kerrisk [Eric W. Biederman]
New page providing overview of Linux namespaces
pid_namespaces.7
Michael Kerrisk [Eric W. Biederman, Vasily Kulikov, Rob Landley,
Serge Hallyn]
New page describing PID namespaces
user_namespaces.7
Michael Kerrisk [Eric W. Biederman, Andy Lutomirski, Serge Hallyn]
New page describing user namespaces.
Newly documented interfaces in existing pages
---------------------------------------------
clone.2
Eric W. Biederman [Michael Kerrisk]
Document CLONE_NEWUSER for creating a new user namespace
setns.2
Eric W. Biederman, Michael Kerrisk
Document the PID, user, and mount namespace support
Document CLONE_NEWPID, CLONE_NEWUSER, and CLONE_NEWNS flags.
unshare.2
Michael Kerrisk [Eric W. Biederman]
Document CLONE_NEWPID
Michael Kerrisk [Eric W. Biederman]
Document CLONE_NEWUSER
Michael Kerrisk
Document CLONE_THREAD, CLONE_SIGHAND, and CLONE_VM
Changes to individual pages
---------------------------
clone.2
Michael Kerrisk
Move some CLONE_NEWNET text to namespaces.7
Michael Kerrisk
Move some CLONE_NEWUTS text 2 to namespaces.7
Michael Kerrisk
Move some CLONE_NEWIPC text to namespaces.7
Michael Kerrisk
Reword discussion of CLONE_NEWNS, removing text also in namespaces(7)
Michael Kerrisk
Standardize text on CLONE_NEW* flags and CAP_SYS_ADMIN
Michael Kerrisk
EINVAL if (CLONE_NEWUSER|CLONE_NEWPID) && (CLONE_THREAD|CLONE_PARENT)
Michael Kerrisk
Add more detail on the meaning of CLONE_SYSVSEM
mount.2
Eric W. Biederman
Clarify use of 'mountflags' and 'data' for MS_REMOUNT
reboot.2
Michael Kerrisk [Justin Cormack, Eric W. Biederman]
Document effect of reboot() inside PID namespaces
seteuid.2
setgid.2
setresuid.2
setreuid.2
setuid.2
Michael Kerrisk
EINVAL can occur if UID/GID is not valid in caller's user namespace
setns.2
Michael Kerrisk [Eric W. Biederman]
Clarify capabilities required for reassociating with a mount namespace
Michael Kerrisk
Specify kernel version on each CLONE_NEW* flag
And remove text on flags from VERSIONS.
unshare.2
Michael Kerrisk
Add an example program
Michael Kerrisk
Clarify semantics of CLONE_SYSVSEM
Michael Kerrisk
CLONE_SYSVSEM does not require CAP_SYS_ADMIN
Michael Kerrisk
Note flags implied by CLONE_THREAD and CLONE_VM
capabilities.7
Michael Kerrisk
Refer reader to user_namespaces(7) for a discussion of capabilities
Michael Kerrisk
Document CAP_SETUID and CAP_SETGID for user namespace mappings
Michael Kerrisk
setns() needs CAP_SYS_ADMIN in the *target* namespace
Michael Kerrisk
Since Linux 3.8, user namespaces no longer require CAP_SYS_ADMIN
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
reply other threads:[~2014-09-21 11:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=541EBD79.706@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).