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.69 is released
Date: Sun, 15 Jun 2014 21:55:44 +0200 [thread overview]
Message-ID: <539DFA40.5010402@gmail.com> (raw)
Gidday,
The Linux man-pages maintainer proudly announces his 150th release
as project maintainer:
man-pages-3.69 - 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.69
A short summary of the release is blogged at:
http://linux-man-pages.blogspot.com/2014/06/man-pages-369-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.69 ====================
New and rewritten pages
-----------------------
iconv.1
Marko Myllynen [Michael Kerrisk]
New page for the iconv(1) command
iconvconfig.8
Marko Myllynen
New page for iconvconfig(8)
Newly documented interfaces in existing pages
---------------------------------------------
fcntl.2
Jeff Layton, Michael Kerrisk
Document open file description locks
As provided by the fcntl() operations F_OFD_SETLK,
F_OFD_SETLKW, and F_OFD_GETLK
Changes to individual pages
---------------------------
execve.2
Michael Kerrisk [NeilBrown]
Before kernel 2.6.0, RLIMIT_NPROC had no effect for set*uid()
Michael Kerrisk [Vasiliy Kulikov]
RLIMIT_NPROC is checked only if preceded by set*uid()
Michael Kerrisk [Vasiliy Kulikov, NeilBrown, KOSAKI Motohiro]
Document EAGAIN error
See also https://bugzilla.kernel.org/show_bug.cgi?id=42704
fcntl.2
Michael Kerrisk
Detail the limitations of traditional (process-associated) locks
Michael Kerrisk [Jeff Layton]
Add notes on F_SETLKW deadlock detection and its limitations
Michael Kerrisk [Jeff Layton]
Reword discussion of mandatory lock bug a little
Jeff Layton confirmed that the bug remains even in modern kernels.
Michael Kerrisk [NeilBrown]
Note treatment of locks when an NFS client loses contact with the server
flock.2
Michael Kerrisk
In some modern BSDs, fcntl() and flock() locks do interact
So, reword and extend the discussion of this topic in NOTES.
Michael Kerrisk [NeilBrown]
Add more details on NFS, including Linux 2.6.37 changes
open.2
Michael Kerrisk
Rework and extend the discussion of open file descriptions
remap_file_pages.2
Michael Kerrisk [Kirill A. Shutemov]
Note that remap_file_pages() is deprecated
seteuid.2
Michael Kerrisk
seteuid() and setegid() are implemented as library functions
Michael Kerrisk
Error checking should always be performed, even when caller is UID 0
setresuid.2
Michael Kerrisk
Document EAGAIN error that can occur after kernel alloc_uid() failure
Michael Kerrisk
Since Linux 3.1, the EAGAIN case for RLIMIT_NPROC no longer occurs
Michael Kerrisk
Error checking should always be performed, even when caller is UID 0
setreuid.2
Michael Kerrisk
Document EAGAIN error that can occur after kernel alloc_uid() failure
Michael Kerrisk
Error checking should always be performed, even when caller is UID 0
Michael Kerrisk
Add EAGAIN error for hitting RLIMIT_NPROC limit
Michael Kerrisk
Since Linux 3.1, the EAGAIN case for RLIMIT_NPROC no longer occurs
setuid.2
Michael Kerrisk
Document EAGAIN error that can occur after kernel alloc_uid() failure
Michael Kerrisk
Correct the description of the EAGAIN error
Michael Kerrisk
Error checking should always be performed, even when caller is UID 0
Michael Kerrisk
Since Linux 3.1, the EAGAIN case for RLIMIT_NPROC no longer occurs
--
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-06-16 4:12 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=539DFA40.5010402@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