From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: mtk.manpages@gmail.com
Subject: man-pages-4.02 is released
Date: Sun, 09 Aug 2015 08:17:01 +0200 [thread overview]
Message-ID: <55C6F05D.1040209@gmail.com> (raw)
Gidday,
The Linux man-pages maintainer proudly announces:
man-pages-4.02 - man pages for Linux
This release includes various new man pages and makes changes
in nearly 400 other pages, based on input and contributions from
around 15 people.
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_4.01
A short summary of the release is blogged at:
http://linux-man-pages.blogspot.com/2015/08/man-pages-402-is-released.html
The current version of the pages is browsable at:
http://man7.org/linux/man-pages/
A selection of changes in this release that may be interesting
for readers of this list is shown below.
Cheers,
Michael
==================== Changes in man-pages-4.02 ====================
New and rewritten pages
-----------------------
dladdr.3
Michael Kerrisk
New page documenting dladdr() and dladdr1()
Relocate/rewrite dladdr() text formerly contained in dlopen(3).
Add documentation of dladdr1().
dlinfo.3
Michael Kerrisk
New page describing dlinfo(3)
dlopen.3
Michael Kerrisk
This page was substantially rewritten and enhanced. Notably:
* the dladdr(), dlsym, dlvsym(), and dlerror() content were moved
to separate new pages
Newly documented interfaces in existing pages
---------------------------------------------
dlopen.3
Michael Kerrisk, Carlos O'Donell
Document dlmopen(3)
nl_langinfo.3
Sam Varshavchik, Michael Kerrisk
Add documentation for nl_langinfo_l(3)
__ppc_set_ppr_med.3
Gabriel F. T. Gomes
Document PPC functions providing access to PPR
GNU C Library 2.18 adds functions (__ppc_set_ppr_low(3),
__ppc_set_ppr_med(3), __ppc_set_ppr_med_low(3)) that provide
access to the Program Priority Register (PPR).
__ppc_yield.3
Gabriel F. T. Gomes
Document PPC performance-hint functions
GNU C Library 2.18 adds functions __ppc_yield(3), __ppc_mdoio(3),
and __ppc_mdoom(3) that can be used provide a hint that
performance could be improved if shared resources are released
for use by other processors.
Global changes
--------------
Very many pages
Michael Kerrisk
Update CONFORMING TO section to reflect POSIX.1-2001 and POSIX.1-2008
details. (By now, I believe all pages should be up to date with
respect to appropriately mentioning POSIX.1-2001 and POSIX.1-2008.)
Changes to individual pages
---------------------------
bpf.2
Daniel Borkmann
Various updates/follow-ups to address some fixmes
A couple of follow-ups to the bpf(2) man-page, besides others:
* Description of map data types
* Explanation on eBPF tail calls and program arrays
* Paragraph on tc holding ref of the eBPF program in the kernel
* Updated ASCII image with tc ingress and egress invocations
* __sync_fetch_and_add() and example usage mentioned on arrays
* minor reword on the licensing and other minor fixups
io_getevents.2
Michael Kerrisk
Note return value on interruption by a signal handler
Michael Kerrisk
Clarify details of return value for timeout-expired case
Michael Kerrisk
Clarify and extend discussion of 'timeout' argument
mmap.2
Michael Kerrisk
Note that 'length' need not be a page-size multiple for munmap()
Michael Kerrisk [David Rientjes, David Rientjes, Mike Kravetz]
Describe mmap()/munmap() argument requirements for huge-page mappings
fanotify.7
Heinrich Schuchardt
Clarify effects of file moves
If files or directories are moved to other mounts, the inode is
deleted. Fanotify marks are lost.
--
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:[~2015-08-09 6:17 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=55C6F05D.1040209@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.