Various pages
Alain Portal
- Formating fixes.
+ Formatting fixes.
mlock.2
mprotect.2
strerror.3
mtk, after a note from Daniele Giacomini
- Modify SYNOPSIS to show protoypes of both versions of strerror_r(),
+ Modify SYNOPSIS to show prototypes of both versions of strerror_r(),
and make other small clarifications of the description regarding
the two versions.
proc.5
mtk
- The vaious CPU time fields in /proc/stat and /proc/PID/stat
+ The various CPU time fields in /proc/stat and /proc/PID/stat
return time in clock ticks (USER_HZ, cputime_to_clock_t(),
sysconf(_SC_CLK_TCK)).
Updated, clarified and expanded the description several
Michael Kerrisk
Global fix: s/(3)/(2)/ in section number xrefs for timer_*() API
The POSIX timers API is implemented (mostly) within the kernel,
- so thse interfaces are system calls. Although there are as yet
+ so these interfaces are system calls. Although there are as yet
no man pages, when they are added they should be in Section 2,
not 3. Therefore fix those pages that currently refer to these
interfaces as being in Section 3.
Major updates
Update the page to consolidate information from the
outdated man-pages quotactl.2 page and the quotactl.2
- page in the "quota-tools" pachage. The page in "quota-tools"
+ page in the "quota-tools" package. The page in "quota-tools"
has now been dropped by Jan Kara, so that there is just one
canonical quotactl.2 page (in pan-pages).
Michael Kerrisk
Jianhua Li <jhlicc@gmail.com>
Linus Nilsson <lajnold@gmail.com>
Lenaic Huard <lenaic.huard@laposte.net>
-mac@mcrowe.com
+Mac <mac@mcrowe.com>
Martin Schulze <joey@infodrom.org>
Maxin John <maxin.john@gmail.com>
Michael Kerrisk <mtk.manpages@gmail.com>
The following people contributed notes, ideas, or patches that have
been incorporated in changes in this release:
-caishuxian@gmail.com
+caishuxian <caishuxian@gmail.com>
Denis Barbier <bouzim@gmail.com>
Denis Silakov <silakov@ispras.ru>
der Mouse <mouse@rodents-montreal.org>
readdir.3
Michael Kerrisk
Clarify that "positive error numbers" are listed in ERRORS
- Reported-by fkater@googlemail.com
rexec.3
Michael Kerrisk
pthread_sigqueue.3
Michael Kerrisk
- New page documenting ptrhead_sigqueue()
+ New page documenting pthread_sigqueue()
pthread_sigqueue() is new in glibc 2.11 (requires a kernel with
rt_tgsigqueinfo(), added in Linux 2.6.31).
Change "should not overlap" to "must not overlap"
glibc 2.12 changed things so that applications that use memcpy() on
overlapping regions will encounter problems. (The standards have
- long said that the behavious is undefined if the memory areas
+ long said that the behaviors is undefined if the memory areas
overlap.)
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603144
timerfd_create.2
Michael Kerrisk [Josh Triplett]
- Note behavior when timerdfd_settime() old_value is NULL
+ Note behavior when timerfd_settime() old_value is NULL
See http://bugs.debian.org/cgi-bin/bugreport.cgi?641513
Tomislav Jonjic
Fix small error in description of timerfd_settime()
Salvo Tomaselli <tiposchi@tiscali.it>
Simone Piccardi <piccardi@truelite.it>
Slaven Rezic <srezic@iconmobile.com>
-starlight@binnacle.cx
+starlight <starlight@binnacle.cx>
Stephan Mueller <stephan.mueller@atsec.com>
Vijay Rao <vijay@portuosus.com>
Walter Haidinger <walter.haidinger@gmx.at>
PROTOTYPE: Fix return type of syncfs()
vfork.2
- Michael Kerrisk [starlight@binnacle.cx]
+ Michael Kerrisk [starlight]
Clarify what is duplicated in the child
Add some words to make it clear to the reader that vfork(),
like fork(), creates duplicates of process attributes
in the child.
Michael Kerrisk
Note clone() flags equivalent to vfork()
- Michael Kerrisk [starlight@binnacle.cx, Mike Frysinger]
+ Michael Kerrisk [starlight, Mike Frysinger]
Add some notes on reasons why vfork() still exists
- Michael Kerrisk [starlight@binnacle.cx]
+ Michael Kerrisk [starlight]
Clarify that calling *thread* is suspended during vfork()
Michael Kerrisk
CONFORMING TO: Note that POSIX.1-2001 marked vfork() obsolete
Akihiro MOTOKI <amotoki@gmail.com>
Andries E. Brouwer <Andries.Brouwer@cwi.nl>
-Angelo Borsotti <angelo.borsotti@gmail.com >
+Angelo Borsotti <angelo.borsotti@gmail.com>
Bjarni Ingi Gislason <bjarniig@rhi.hi.is>
Brian M. Carlson <sandals@crustytoothpaste.ath.cx>
-Casper.Dik@oracle.com
+Casper Dik <Casper.Dik@oracle.com>
David Prévot <taffit@debian.org>
D. Barbier <bouzim@gmail.com>
Eric Blake <eblake@redhat.com>
Nick Piggin <npiggin@gmail.com>
Paul Pluzhnikov <ppluzhnikov@google.com>
Petr Baudis <pasky@ucw.cz>
-Ralph Corderoy <ralph@inputplus.co.uk >
+Ralph Corderoy <ralph@inputplus.co.uk>
Rich Felker <bugdal@aerifal.cx>
Simone Piccardi <piccardi@truelite.it>
Simon Paillard <spaillard@debian.org>
Rewrite to focus on the system call interface, adding
some notes on the libaio wrapper differences.
See the following mail:
- 2012-05-07 "aio manuals", linux-man@vger.kernel.org
+ 2012-05-07 "aio manuals", linux-man@vger
http://thread.gmane.org/gmane.linux.man/1935/focus=2910
Other minor rewrites.
Upstreamed from Red Hat / Fedora
realpath.3
- Michael Kerrisk [Casper.Dik@oracle.com]
+ Michael Kerrisk [Casper Dik]
Remove note about Solaris possibly returning a relative path
syslog.3
Capitalize first word in heading, but otherwise use lower case,
except where English usage (e.g., proper nouns) or programming
language requirements (e.g., identifier names) dictate otherwise.
+
Many pages
Michael Kerrisk [Denys Vlasenko]
Remove double blank lines in output
lseek.2
Michael Kerrisk [Andreas Jaeger]
- _GNU_SOURCE must be defined to get SEEK_DATE and SEEK_HOLE definitions
+ _GNU_SOURCE must be defined to get SEEK_DATA and SEEK_HOLE definitions
See http://sourceware.org/bugzilla/show_bug.cgi?id=15312
mmap.2
Michael Kerrisk
Add EINVAL error for setstate()
Michael Kerrisk
- BUGS: inistate() does not return NULL on error
+ BUGS: initstate() does not return NULL on error
http://sourceware.org/bugzilla/show_bug.cgi?id=15380
random_r.3
David Prévot <taffit@debian.org>
Denys Vlasenko <dvlasenk@redhat.com>
Dmitry V. Levin <ldv@altlinux.org>
-Felix_Schulte@McAfee.com
-graud@gmx.com
+Felix Schulte <Felix_Schulte@McAfee.com>
+Graud <graud@gmx.com>
Michael Kerrisk <mtk.manpages@gmail.com>
Oleg Nesterov <oleg@redhat.com>
Peng Haitao <penght@cn.fujitsu.com>
cause the program to operate on uninitialized data.
setpgid.2
- Michael Kerrisk [graud@gmx.com]
+ Michael Kerrisk [Graud]
s/SIGTSTP/SIGTTIN/ when discussing reads from terminal
See https://bugzilla.kernel.org/show_bug.cgi?id=60504
Add open_by_handle_at(2) under CAP_DAC_READ_SEARCH
inotify.7
- Michael Kerrisk [Felix_Schulte@McAfee.com]
+ Michael Kerrisk [Felix Schulte]
Clarify description of IN_MOVED_FROM and IN_MOVED_TO
man-pages.7
Michael Kerrisk
BUGS: The O_SYNC and O_DSYNC flags are not modifiable using F_SETFL
Michael Kerrisk
- Add susbsections under BUGS
+ Add subsections under BUGS
There's several bugs listed. It's helpful to mark
them separately.
Michael Kerrisk
Neil Horman
Document the SO_RXQ_OVFL socket option
Michael Kerrisk
+ Add kernel version number for SO_RXQ_OVFL
New and changed links
socket.7
Michael Kerrisk
Add kernel version number for SO_BUSY_POLL
- Add kernel version number for SO_RXQ_OVFL
+
+
+==================== Changes in man-pages-3.62 ====================
+
+Released: 2014-03-11, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Cyril Hrubis <chrubis@suse.cz>
+Joseph S. Myers <joseph@codesourcery.com>
+Marius Gaubas <marius@livejournalinc.com>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Mike Frysinger <vapier@gentoo.org>
+Peng Haitao <penght@cn.fujitsu.com>
+Rick Stanley <rstanley@rsiny.com>
+Simon Paillard <spaillard@debian.org>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+locale.1
+ Michael Kerrisk [review from Mike Frysinger]
+ New page describing locale(1)
+
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+locale.5
+ Michael Kerrisk
+ Document LC_ADDRESS
+ Michael Kerrisk
+ Document LC_IDENTIFICATION
+ Michael Kerrisk
+ Document LC_MEASUREMENT
+ Michael Kerrisk
+ Document LC_NAME
+ Michael Kerrisk
+ Document LC_PAPER
+ Michael Kerrisk
+ Document LC_TELEPHONE
+
+
+Removed Pages
+-------------
+
+sync.8
+ Michael Kerrisk [Christoph Hellwig, Pádraig Brady]
+ Sometime in the 20th century (before my watch), a sync(8)
+ page into man-pages. It documents the sync command from
+ "fileutils", which long ago become coreutils, and the
+ piece under NOTES note some behavior of sync(2)
+ that ceased to be true many years ago. The man-pages
+ project generally focuses on only Linux kernel and
+ (g)libc interfaces, so this sync(8) page doesn't really
+ belong. Furthermore, coreutils has a sync(1) page which
+ covers the same command. After discussions on the
+ coreutils list, I've decided to retire this page from
+ man-pages.
+
+Changes to individual pages
+---------------------------
+
+clone.2
+ Michael Kerrisk
+ Note that CLONE_THREAD also in effect requires CLONE_VM
+
+stat.2
+ Michael Kerrisk [Marius Gaubas]
+ Warn the reader that the 'stat' structure definition is not precise
+ Padding fields aren't shown, and the order of fields varies
+ somewhat across architectures.
+
+gethostbyname.3
+ Michael Kerrisk
+ Remove redundant FTM requirements
+ _GNU_SOURCE implies _SVID_SOURCE and _BSD_SOURCE, so
+
+ _BSD_SOURCE || _SVID_SOURCE || _GNU_SOURCE
+
+ is the same as
+
+ _BSD_SOURCE || _SVID_SOURCE
+
+getutmp.3
+ Michael Kerrisk
+ SEE ALSO: add utmpdump(1)
+
+log1p.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions log1p(), log1pf() and log1pl() are thread safe.
+
+logb.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions logb(), logbf() and logbl() are thread safe.
+
+memccpy.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function memccpy() is thread safe.
+
+memchr.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions memchr(), memrchr() and rawmemchr() are thread safe.
+
+mktemp.3
+ Michael Kerrisk
+ Make warning not to use this function more prominent
+
+qecvt.3
+ Michael Kerrisk [Joseph S. Myers]
+ Recommend snprintf(3) not sprintf(3)
+
+raise.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function raise() is thread safe.
+
+remove.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function remove() is thread safe.
+
+sem_destroy.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function sem_destroy() is thread safe.
+
+sem_getvalue.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function sem_getvalue() is thread safe.
+
+sem_init.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function sem_init() is thread safe.
+
+sockatmark.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function sockatmark() is thread safe.
+
+strcpy.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions strcpy() and strncpy() are thread safe.
+ Michael Kerrisk [Rick Stanley]
+ Fix a bug, and improve discussion of forcing termination with strncpy()
+
+strspn.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions strspn() and strcspn() are thread safe.
+
+tempnam.3
+ Michael Kerrisk
+ Make warning not to use this function more prominent
+
+tmpnam.3
+ Michael Kerrisk
+ Recommend use mkstemp(3) or tmpfile(3) instead
+
+locale.5
+ Michael Kerrisk
+ Add intro section that lists all of the LC categories
+ Michael Kerrisk
+ 'p_cs_precedes' is for *positive* values
+ Michael Kerrisk
+ Clarify 'p_sign_posn' and 'n_sign_posn'; simplify 'n_sign_posn'
+ Add initial sentence for 'p_sign_posn' and 'n_sign_posn'.
+ Remove repeated list for 'n_sign_posn'.
+ Michael Kerrisk
+ Document LC_MESSAGES 'yesstr' and 'nostr'
+ Michael Kerrisk
+ Clarify LC_MONETARY 'n_cs_precedes'
+ Michael Kerrisk
+ LC_MONETARY: Document 'int_p_sign_posn' and 'int_n_sign_posn'
+ Michael Kerrisk
+ Clarify/rework 'p_cs_precedes' and 'n_cs_precedes'
+ Michael Kerrisk
+ LC_MONETARY: document 'int_p_sep_by_space' and 'int_n_sep_by_space'
+ Michael Kerrisk
+ Remove crufty reference to POSIX.2
+ Michael Kerrisk
+ LC_MONETARY: document 'int_p_cs_precedes' and 'int_n_cs_precedes'
+ Michael Kerrisk
+ Clarify/simplify 'n_sep_by_space'
+ Michael Kerrisk
+ LC_TIME: document 'cal_direction' and 'date_fmt'
+ Michael Kerrisk
+ Clarify 'p_sep_by_space'
+
+feature_test_macros.7
+ Michael Kerrisk
+ _BSD_SOURCE and _SVID_SOURCE are deprecated in glibc 2.20
+ Michael Kerrisk
+ _GNU_SOURCE implicitly defines other macros
+ Saying that _GNU_SOURCE has the "effects of" other macros is not
+ quite precise.
+ Michael Kerrisk
+ Reword glibc version for _ISOC95_SOURCE
+ Michael Kerrisk
+ _ISOC99_SOURCE also exposes C95 definitions
+ Michael Kerrisk
+ _ISOC11_SOURCE implies the effects of _ISOC99_SOURCE
+ Michael Kerrisk
+ Note version number for _POSIX_C_SOURCE >= 200112L implies C99/C95
+ _POSIX_C_SOURCE >= 200112L causes C95 definitions to be
+ exposed only since glibc 2.12 and C99 definitions only
+ since 2.10.
+ Michael Kerrisk
+ _XOPEN_SOURCE may implicitly define _POSIX_SOURCE and _POSIX_C_SOURCE
+ Michael Kerrisk
+ Reword glibc version for _ISOC99_SOURCE
+ Michael Kerrisk
+ Rework discussion of _ISOC99_SOURCE
+ Michael Kerrisk
+ Improve discussion of _DEFAULT_SOURCE
+ Michael Kerrisk
+ _POSIX_C_SOURCE >= 200112L implies C95 and C95 features
+
+
+
+==================== Changes in man-pages-3.63 ====================
+
+Released: 2014-03-18, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Carlos O'Donell <carlos@redhat.com>
+Christoph Hellwig <hch@infradead.org>
+Corrado Zoccolo <czoccolo@gmail.com>
+Gregory P. Smith <gps@google.com>
+Joseph S. Myers <joseph@codesourcery.com>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Mike Frysinger <vapier@gentoo.org>
+Peng Haitao <penght@cn.fujitsu.com>
+Phillip Susi <psusi@ubuntu.com>
+Robert P. J. Day <rpjday@crashcourse.ca>
+Stefan Puiu <stefan.puiu@gmail.com>
+Zhu Yanhai <zhu.yanhai@gmail.com>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+duplocale.3
+ Michael Kerrisk
+ New page documenting duplocale(3)
+
+newlocale.3
+ Michael Kerrisk [Mike Frysinger]
+ New page documenting newlocale(3) and freelocale(3)
+
+towlower.3
+ Michael Kerrisk
+ Largely rewrite description of towlower() to be simpler and clearer
+
+towupper.3
+ Michael Kerrisk
+ Largely rewrite description of towupper() to be simpler and clearer
+
+uselocale.3
+ Michael Kerrisk
+ New page documenting uselocale(3)
+
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+open.2
+ Michael Kerrisk
+ Document O_DSYNC and rewrite discussion of O_SYNC
+
+isalpha.3
+ Michael Kerrisk
+ Document the "_l" locale APIs
+ The GNU C library v2.3 added some locale APIs, most of which
+ were later specified in POSIX.1-2008, namely:
+
+ isalnum_l()
+ isalpha_l()
+ isblank_l()
+ iscntrl_l()
+ isdigit_l()
+ isgraph_l()
+ islower_l()
+ isprint_l()
+ ispunct_l()
+ isspace_l()
+ isupper_l()
+ isxdigit_l()
+ isascii_l()
+
+ Also update and correct various pieces in CONFORMING TO
+ (and remove a few crufty old pieces there).
+
+strerror.3
+ Michael Kerrisk
+ Document strerror_l()
+
+toupper.3
+ Michael Kerrisk
+ Document toupper_l() and tolower_l()
+
+towlower.3
+ Michael Kerrisk
+ Document towlower_l()
+
+towupper.3
+ Michael Kerrisk
+ Document towupper_l()
+
+proc.5
+ Michael Kerrisk
+ Document /proc/sys/kernel/random/uuid
+
+locale.7
+ Michael Kerrisk
+ Document LC_ADDRESS
+ Document LC_IDENTIFICATION
+ Document LC_MEASUREMENT
+ Document LC_NAME
+ Document LC_PAPER
+ Document LC_TELEPHONE
+
+
+New and changed links
+---------------------
+
+freelocale.3
+ Michael Kerrisk
+ New link to new newlocale.3 page
+
+isalnum_l.3
+isascii_l.3
+isblank_l.3
+iscntrl_l.3
+isdigit_l.3
+isgraph_l.3
+islower_l.3
+isprint_l.3
+ispunct_l.3
+isspace_l.3
+isupper_l.3
+isxdigit_l.3
+ Michael Kerrisk
+ New links to isalpha.3
+
+tolower_l.3
+toupper_l.3
+ Michael Kerrisk
+ New links to toupper.3
+
+towlower_l.3
+ Michael Kerrisk
+ New link to towlower.3
+
+towupper_l.3
+ Michael Kerrisk
+ New link to towupper.3
+
+
+Global changes
+--------------
+
+Various pages
+ Michael Kerrisk
+ Global change: "upper case" ==> "uppercase", "lower case" ==> lowercase"
+
+
+Changes to individual pages
+---------------------------
+
+mount.2
+ Michael Kerrisk
+ SEE ALSO: add blkid(1)
+
+msgop.2
+ Michael Kerrisk
+ Document two MSG_COPY failure modes
+ Since Linux 3.14, the kernel now diagnoses two errors
+ when using msgrcv() MSG_COPY:
+ * MSG_COPY must be specified with IPC_NOWAIT
+ * MSG_COPY can't be specified with MSG_EXCEPT
+
+open.2
+ Michael Kerrisk
+ Organize some material under additional subheadings in NOTES
+ There's an amorphous mass of material under NOTES. Structure
+ it with some subheadings, and do a little reorganizing.
+ Michael Kerrisk
+ Add other system calls and functions that are like openat()
+ fanotify_mark(2), name_to_handle_at(2), and scandirat(3) have a
+ directory file descriptor argument for the same reason as openat().
+ Also: reword the rationale for the *at() functions somewhat.
+ Michael Kerrisk
+ Clarify ELOOP error interaction with O_PATH
+
+readahead.2
+ Phillip Susi [Corrado Zoccolo, Gregory P. Smith, Zhu Yanhai, Michael Kerrisk, Christoph Hellwig]
+ Don't claim the call blocks until all data has been read
+ The readahead(2) man page was claiming that the call blocks until
+ all data has been read into the cache. This is incorrect.
+
+ See https://bugzilla.kernel.org/show_bug.cgi?id=54271
+
+stat.2
+ Michael Kerrisk
+ SEE ALSO: add ls(1) and stat(1)
+
+fts.3
+ Christoph Hellwig [Michael Kerrisk]
+ The fts(3) API does not work with LFS builds
+ As pointed out during a recent discussion on libc-hacker the
+ fts(3) APIs can't be used with large file offsets:
+
+ https://sourceware.org/bugzilla/show_bug.cgi?id=15838
+
+mbrtowc.3
+mbsnrtowcs.3
+mbsrtowcs.3
+mbtowc.3
+ Michael Kerrisk
+ Add entries in SEE ALSO
+ Mainly inspired by the POSIX pages.
+
+mbsinit.3
+ Michael Kerrisk
+ SEE ALSO: add mbrlen(3), mbrtowc(3), and wcrtomb(3)
+
+mbsrtowcs.3
+wcsrtombs.3
+ Michael Kerrisk
+ SEE ALSO: add mbsinit(3)
+
+mbstowcs.3
+ Michael Kerrisk [Stefan Puiu]
+ Add example program
+ And add some SEE ALSO entries
+
+memcmp.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function memcmp() is thread safe.
+
+memcpy.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function memcpy() is thread safe.
+
+memfrob.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function memfrob() is thread safe.
+
+memmem.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function memmem() is thread safe.
+
+memmove.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function memmove() is thread safe.
+
+mempcpy.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions mempcpy() and wmempcpy() are thread safe.
+
+memset.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function memset() is thread safe.
+
+strerror.3
+ Michael Kerrisk
+ CONFORMING TO: strerror() and strerror_r() are in POSIX.1-2008
+ Michael Kerrisk
+ Add SS heading for strerror_r()
+
+toupper.3
+ Michael Kerrisk
+ Rewrite to more explicitly bring locales into the discussion
+ Michael Kerrisk
+ Retitle BUGS section to NOTES
+ These are not really bugs, just background info.
+
+wcrtomb.3
+wcsnrtombs.3
+wcsrtombs.3
+wcstombs.3
+wctomb.3
+ Michael Kerrisk
+ SEE ALSO: add various entries
+ Mainly inspired by POSIX
+
+core.5
+ Mike Frysinger [Michael Kerrisk]
+ Document core_pattern %d specifier
+ Document %P core_pattern specifier
+ Michael Kerrisk
+ Rearrange core_pattern specifiers alphabetically
+
+locale.5
+ Michael Kerrisk
+ SEE ALSO: add newlocale(3) + duplocale(3)
+
+feature_test_macros.7
+ Michael Kerrisk [Joseph S. Myers]
+ Remove mention of bogus _ISOC95_SOURCE macro
+ The _ISOC95_SOURCE macro is defined in <features.h>, but it
+ does nothing. So remove discussion of it, and move some of
+ the discussion of C95 under the _ISOC99_SOURCE subhead.
+ Michael Kerrisk [Carlos O'Donell]
+ Add packaging note for _BSD_SOURCE/_SVID_SOURCE/_DEFAULT_SOURCE
+ To compile warning-free across glibc < 2.20 and glibc >= 2.20
+ code may been to define both _DEFAULT_SOURCE and either
+ _BSD_SOURCE or _SVID_SOURCE.
+ Michael Kerrisk
+ Reword description of C90
+
+locale.7
+ Michael Kerrisk
+ Add subsection on POSIX.1-2008 (originally GNU) extensions to locale API
+ Michael Kerrisk
+ Remove reference to LI18NUX2000
+ LI18NUX2000 is difficult to even find these days, and in any case
+ this page does not document gettext(), so notes about gettext()
+ in the CONFORMING TO section here make no sense.
+ Michael Kerrisk
+ SEE ALSO: add mbstowcs(3) and wcstombs(3)
+ SEE ALSO: add newlocale(3) + duplocale(3)
+
+man-pages.7
+ Michael Kerrisk
+ Add preferred term "superblock"
+ Michael Kerrisk
+ Add preferred terms "uppercase" and "lowercase"
+
+
+
+==================== Changes in man-pages-3.64 ====================
+
+Released: 2014-04-06, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Abhay Sachan <sachan.abhay@gmail.com>
+Alexey Samsonov <samsonov@google.com>
+Andrey Vagin <avagin@openvz.org>
+Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
+Christoph Hellwig <hch@infradead.org>
+David Prévot <taffit@debian.org>
+Eric Dumazet <edumazet@google.com>
+Eric W. Biederman <ebiederm@xmission.com>
+Jan Kara <jack@suse.cz>
+Kir Kolyshkin <kir@openvz.org>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Mike Frysinger <vapier@gentoo.org>
+NeilBrown <neilb@suse.de>
+Peng Haitao <penght@cn.fujitsu.com>
+Peter Hurley <peter@hurleysoftware.com>
+Petr Gajdos <pgajdos@suse.cz>
+Robert P. J. Day <rpjday@crashcourse.ca>
+Vince Weaver <vincent.weaver@maine.edu>
+Yuri Kozlov <yuray@komyakino.ru>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+open_by_handle_at.2
+ Michael Kerrisk [Mike Frysinger, Neil Brown, Aneesh Kumar K.V,
+ Christoph Hellwig]
+ New page describing name_to_handle_at(2) and open_by_handle_at(2)
+
+inotify.7
+ Michael Kerrisk
+ Rewrite introductory section
+ Reorganize "Limitations and caveats" subsection
+ Michael Kerrisk
+ Further describe the race when adding a watch to a new subtree
+ Michael Kerrisk
+ Directory renames may invalidate multiple paths cached by application
+ Michael Kerrisk
+ Add paragraph on cache consistency checking
+ Michael Kerrisk
+ Mention cache rebuilding to handle overflow events
+ Michael Kerrisk
+ Moving an object to another filesystem generates IN_DELETE_SELF
+ Michael Kerrisk [Jan Kara]
+ Add text on dealing with rename() events
+ Michael Kerrisk
+ Note rationale and consequences of event coalescing
+ Michael Kerrisk [Eric W. Biederman]
+ Inotify doesn't work for remote and pseudo filesystems
+ Michael Kerrisk
+ Add some examples of events generated by various system calls
+ Michael Kerrisk
+ BUGS: IN_ONESHOT does now cause IN_IGNORED when the watch is dropped
+ A silent change as a result of the fanotify work in kernel 2.6.36.
+ Michael Kerrisk
+ Note that IN_DELETE_SELF will be followed by IN_IGNORED
+ Michael Kerrisk
+ Note that IN_UNMOUNT will be followed by an IN_IGNORED event
+ Michael Kerrisk
+ Inotify does not report events for mmap(2) and msync(2)
+ Michael Kerrisk
+ Add examples of syscalls that trigger IN_ATTRIB
+ Michael Kerrisk
+ Add some examples of syscalls that trigger IN_MODIFY
+ Michael Kerrisk
+ execve(2) also generates IN_ACCESS
+ Michael Kerrisk
+ Add examples of syscalls that trigger IN_CREATE
+
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+perf_event_open.2
+ Vince Weaver [Michael Kerrisk]
+ Document the PERF_FLAG_FD_CLOEXEC flag
+ The Linux 3.14 release adds support for the PERF_FLAG_FD_CLOEXEC
+ flag.
+
+feature_test_macros.7
+ Michael Kerrisk
+ Document _LARGEFILE_SOURCE
+
+tcp.7
+ Michael Kerrisk [Eric Dumazet]
+ Document /proc/sys/net/ipv4/tcp_autocorking
+ Text heavily based on Documentation/networking/ip-sysctl.txt
+
+
+New and changed links
+---------------------
+
+name_to_handle_at.2
+ Michael Kerrisk
+ New link to new open_by_handle_at(2) page
+
+
+Global changes
+--------------
+
+fmemopen.3
+getaddrinfo.3
+mq_notify.3
+offsetof.3
+aio.7
+ Michael Kerrisk
+ Print size_t/ssize_t values using %z printf() modifier
+ There are fewer and fewer systems these days that don't
+ support the %z specifier mandated in C99. So replace the
+ use of %ld/%lu + (long) cast with %zd/%zu.
+
+
+Changes to individual pages
+---------------------------
+
+bdflush.2
+fsync.2
+sync.2
+ Kir Kolyshkin
+ SEE ALSO: remove update(8) reference
+ Remove reference to update(8) man page, since there is no such
+ page. This is an ancient BSD leftover I believe.
+
+chown.2
+ Michael Kerrisk
+ Note that 'dirfd' can be AT_FDCWD when AT_EMPTY_PATH is used
+
+getxattr.2
+ Abhay Sachan
+ Fix RETURN VALUE description
+ A EA can have length zero.
+
+inotify_add_watch.2
+ Michael Kerrisk
+ ERRORS: add ENAMETOOLONG
+
+inotify_init.2
+ Michael Kerrisk
+ Add pointer to inotify(7)
+
+link.2
+ Michael Kerrisk
+ When AT_EMPTY_PATH is specified, 'olddirfd' must not refer to a
+ directory
+
+mmap.2
+ Andrey Vagin
+ The file descriptor for a file mapping must be readable
+ There is no difference between MAP_SHARED and MAP_PRIVATE.
+
+open.2
+ Michael Kerrisk
+ SEE ALSO: add open_by_name_at(2)
+
+perf_event_open.2
+ Vince Weaver
+ Document PERF_EVENT_IOC_PERIOD behavior change
+ Linux 3.14 (in commit bad7192b842c83e580747ca57104dd51fe08c223)
+ changes the perf_event PERF_EVENT_IOC_PERIOD ioctl() behavior
+ on all architectures to update immediately, to match the behavior
+ found on ARM.
+
+stat.2
+ Michael Kerrisk
+ Note that 'dirfd' can be AT_FDCWD when AT_EMPTY_PATH is used
+
+syscalls.2
+ Michael Kerrisk
+ Add sched_getattr() and sched_setattr()
+ And update kernel version to 3.14
+
+abort.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function abort() is thread safe.
+
+confstr.3
+ Michael Kerrisk
+ SEE ALSO: add getconf(1), fpathconf(3), sysconf(3), pathconf(3)
+
+exit.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is not thread-safe
+ The function exit() is not thread safe.
+
+fenv.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions feclearexcept(), fegetexceptflag(), feraiseexcept(),
+ fesetexceptflag(), fetestexcept(), fegetround(), fesetround(),
+ fegetenv(), feholdexcept(), fesetenv(), feupdateenv(),
+ feenableexcept(), fedisableexcept() and fegetexcept() are thread
+ safe.
+
+fpathconf.3
+ Michael Kerrisk
+ SEE ALSO: add confstr(3)
+
+fseek.3
+ Michael Kerrisk [Petr Gajdos]
+ Document EINVAL error for negative file offset
+
+fseeko.3
+ Michael Kerrisk
+ Add feature test macro requirements
+
+fts.3
+ Michael Kerrisk [Mike Frysinger]
+ Remove mention of "32-bit systems" in BUGS
+
+fwide.3
+wprintf.3
+ Michael Kerrisk [Robert P. J. Day]
+ Remove mention of bogus _ISOC95_SOURCE feature test macro
+
+getline.3
+ Alexey Samsonov
+ Caller should free the allocated buffer even if getline() failed
+ Relevant discussion in glibc bugzilla:
+ https://sourceware.org/bugzilla/show_bug.cgi?id=5666
+
+getloadavg.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function getloadavg() is thread safe.
+
+getpt.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function getpt() is thread safe.
+
+if_nametoindex.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions if_nametoindex() and if_indextoname() are thread safe.
+
+index.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions index() and rindex() are thread safe.
+
+mkfifo.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions mkfifo() and mkfifoat() are thread safe.
+
+netlink.3
+ Michael Kerrisk
+ SEE ALSO: make the reference for libnetlink the libnetlink(3) man page
+
+random.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions random(), srandom(), initstate() and setstate()
+ are thread safe.
+
+random_r.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions random_r(), srandom_r(), initstate_r() and
+ setstate_r() are thread safe.
+
+sigvec.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions sigvec(), sigblock(), sigsetmask() and
+ siggetmask() are thread safe.
+
+ The macro sigmask() is thread safe.
+
+sysconf.3
+ Michael Kerrisk
+ SEE ALSO: add confstr(3)
+
+termios.3
+ Michael Kerrisk [Peter Hurley]
+ Fix error in discussion of MIN > 0, TIME == 0 noncanonical mode
+ As reported by Peter Hurley, for the MIN > 0, TIME == 0 case:
+
+ read() may unblock when MIN bytes are available but return
+ up to the 'count' parameter if more input arrives in between
+ waking and copying into the user buffer.
+ ...
+ read() may also _not_ return until MIN bytes have been
+ received, even if 'count' bytes have been received.
+ Michael Kerrisk
+ Add a note on interaction of O_NONBLOCK with noncanonical MIN/TIME
+ POSIX leaves the behavior open.
+ Michael Kerrisk
+ Clarify termination conditions for MIN > 0, TIME > 0
+ Michael Kerrisk
+ Clarify behavior if data is available before noncanonical read()
+ Michael Kerrisk
+ Add descriptive titles to noncanonical read() cases
+
+symlink.7
+ Michael Kerrisk
+ Add subsection on opening a symbolic link with O_PATH
+ Michael Kerrisk
+ name_to_handle_at(2) and open_by_handle_at(2) optionally follow symlinks
+ Michael Kerrisk
+ Mention use of readlink(2) to read contents of a symlink
+
+
+==================== Changes in man-pages-3.65 ====================
+
+Released: 2014-04-20, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Alex Thorlton <athorlton@sgi.com>
+Ashish Sangwan <a.sangwan@samsung.com>
+Christopher Covington <cov@codeaurora.org>
+Christoph Hellwig <hch@infradead.org>
+Craig McQueen <craig.mcqueen@beamcommunications.com>
+Dave Chinner <david@fromorbit.com>
+David Prévot <taffit@debian.org>
+Greg Troxel <gdt@ir.bbn.com>
+Matthew Dempsky <mdempsky@chromium.org>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Mike Frysinger <vapier@gentoo.org>
+Namjae Jeon <namjae.jeon@samsung.com>
+Peng Haitao <penght@cn.fujitsu.com>
+Petr Gajdos <pgajdos@suse.cz>
+Richard Hansen <rhansen@bbn.com>
+Simon Paillard <spaillard@debian.org>
+Steven Stewart-Gallus <sstewartgallus00@mylangara.bc.ca>
+Vince Weaver <vincent.weaver@maine.edu>
+Yuri Kozlov <yuray@komyakino.ru>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+inet_net_pton.3
+ Michael Kerrisk
+ New page describing inet_net_pton(3) and inet_net_ntop(3)
+
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+fallocate.2
+ Michael Kerrisk, Namjae Jeon [Christoph Hellwig, Dave Chinner]
+ Document FALLOC_FL_COLLAPSE_RANGE
+
+prctl.2
+ Michael Kerrisk [Alex Thorlton]
+ Document PR_SET_THP_DISABLE and PR_GET_THP_DISABLE
+
+proc.5
+ Michael Kerrisk
+ Document /proc/[pid]/stack
+ Michael Kerrisk
+ Document /proc/[pid]/clear_refs
+
+
+New and changed links
+---------------------
+
+inet_net_ntop.3
+ Michael Kerrisk
+ New link to new inet_net_pton.3
+
+
+Changes to individual pages
+---------------------------
+
+fcntl.2
+ Michael Kerrisk
+ Note the race when O_CLOEXEC is used at same time as fork()+execve()
+
+madvise.2
+ Michael Kerrisk
+ SEE ALSO: see prctl(2)
+ Because of PR_SET_THP_DISABLE.
+
+mlock.2
+ Michael Kerrisk
+ Describe treatment of MCL_FUTURE during fork(2) and execve(2)
+
+msync.2
+ Michael Kerrisk [Richard Hansen, Greg Troxel]
+ Warn that one of MS_SYNC or MS_ASYNC is required
+
+open.2
+ Michael Kerrisk
+ Add more detail on the race that O_CLOEXEC is designed to avoid
+ Michael Kerrisk [Matthew Dempsky]
+ Remove crufty text stating that O_DIRECTORY is Linux-specific
+ Michael Kerrisk
+ Note which filesystems support O_TMPFILE
+
+perf_event_open.2
+ Vince Weaver [Michael Kerrisk]
+ Clarify EACCES and EPERM errors
+ Clarify the reasons for EACCES and EPERM errors.
+ Vince Weaver [Michael Kerrisk]
+ Make the ERRORS section more comprehensive.
+ Determined both by code inspection and by writing a large
+ number of test programs.
+
+personality.2
+ Michael Kerrisk
+ Available execution domains are listed in <sys/personality.h>
+ Michael Kerrisk
+ Fix discussion of return value
+
+prctl.2
+ Michael Kerrisk
+ ERRORS: document EINVAL for PR_GET_NO_NEW_PRIVS
+ ERRORS: document EINVAL for PR_SET_PDEATHSIG
+ ERRORS: document EINVAL for PR_SET_TIMING
+ ERRORS: document EINVAL for PR_SET_DUMPABLE
+ ERRORS: document EINVAL for PR_SET_NO_NEW_PRIVS
+
+shmget.2
+ Michael Kerrisk
+ Rewrite description of SHMMNI default value
+ Michael Kerrisk
+ Note default value of SHMMAX
+ Note default value for SHMALL
+
+byteorder.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions htonl(), htons(), ntohl() and ntohs() are thread
+ safe.
+
+fexecve.3
+ Michael Kerrisk [Steven Stewart-Gallus]
+ If 'fd' is a close-on-exec file descriptor for a script, fexecve() fails
+ See https://bugzilla.kernel.org/show_bug.cgi?id=74481
+
+ffs.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions ffs(), ffsl() and ffsll() are thread safe.
+
+getauxval.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function getauxval() is thread safe.
+
+getcontext.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions getcontext() and setcontext() are thread safe.
+
+getsubopt.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function getsubopt() is thread safe.
+
+getutmp.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions getutmp() and getutmpx() are thread safe.
+
+inet.3
+ Michael Kerrisk
+ Note success and error return for inet_aton()
+
+inet.3
+ Michael Kerrisk [Craig McQueen]
+ The form 'a.b' if is suitable for Class A addresses (not class C)
+ Michael Kerrisk
+ SEE ALSO: add inet_net_pton(3)
+
+makecontext.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions makecontext() and swapcontext() are thread safe.
+
+pthread_attr_setdetachstate.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions pthread_attr_setdetachstate() and
+ pthread_attr_getdetachstate() are thread safe.
+
+pthread_attr_setguardsize.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions pthread_attr_setguardsize() and
+ pthread_attr_getguardsize() are thread safe.
+
+sigsetops.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions sigemptyset(), sigfillset(), sigaddset(),
+ sigdelset(), sigismember(), sigisemptyset(), sigorset() and
+ sigandset() are thread safe.
+
+proc.5
+ Petr Gajdos
+ Improve /proc/[pid]/smaps entries description
+ Michael Kerrisk
+ /proc/PID/smaps is present only if CONFIG_PROC_PAGE_MONITOR
+ Michael Kerrisk
+ Note kernel version for /proc/sys/kernel/{shmall,shmmax}
+ Michael Kerrisk
+ Note kernel version for /proc/sys/kernel/{msgmax,msgmnb}
+
+capabilities.7
+ Michael Kerrisk
+ SEE ALSO: add capsh(1)
+
+libc.7
+ Michael Kerrisk
+ Add musl libc
+
+
+==================== Changes in man-pages-3.66 ====================
+
+Released: 2014-05-08, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Alan Curry <rlwinm@sdf.org>
+Carsten Andrich <carsten.andrich@tu-ilmenau.de>
+Daniel Borkmann <dborkman@redhat.com>
+David Prévot <taffit@debian.org>
+Eric Siegerman <pub08-knl@davor.org>
+Heinrich Schuchardt <xypron.glpk@gmx.de>
+Jan Kara <jack@suse.cz>
+Jan Moskyto Matejka <mq@suse.cz>
+John Marshall <jm18@sanger.ac.uk>
+Lukáš Czerner <lczerner@redhat.com>
+Manfred Spraul <manfred@colorfullife.com>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Miklos Szeredi <miklos@szeredi.hu>
+Neil Horman <nhorman@tuxdriver.com>
+Peng Haitao <penght@cn.fujitsu.com>
+Peter Schiffer <pschiffe@redhat.com>
+Randy Dunlap <rdunlap@infradead.org>
+Silvan Jegen <s.jegen@gmail.com>
+Simon Paillard <spaillard@debian.org>
+Stefan Puiu <stefan.puiu@gmail.com>
+Steven Stewart-Gallus <sstewartgallus00@mylangara.bc.ca>
+Stijn Hinterding <contact@stijnhinterding.nl>
+Willem de Bruijn <willemb@google.com>
+Yuri Kozlov <yuray@komyakino.ru>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+fanotify_init.2
+ Heinrich Schuchardt, Michael Kerrisk
+ New page documenting fanotify_init(2)
+
+fanotify_mark.2
+ Heinrich Schuchardt, Michael Kerrisk
+ New page documenting fanotify_mark(2)
+
+sched_setscheduler.2
+ Michael Kerrisk
+ Page rewritten
+ Stripped out the general scheduling material, which
+ moved to sched(7), and rewrote much of the remainder.
+ Changed copyright and license since pretty much all
+ of the content was or is written by mtk.
+
+fanotify.7
+ Heinrich Schuchardt, Michael Kerrisk
+ New page providing overview of the fanotify API
+
+sched.7
+ Michael Kerrisk
+ New page providing an overview of the scheduling APIs
+ Most of this content derives from sched_setscheduler(2). In
+ preparation for adding a sched_setattr(2) page, it makes
+ sense to isolate out this general content to a separate
+ page that is referred to by the other scheduling pages.
+
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+fallocate.2
+ Lukas Czerner [Michael Kerrisk]
+ Document FALLOC_FL_ZERO_RANGE
+ FALLOC_FL_ZERO_RANGE was added in Linux 3.14,
+ for zeroing ranges in the allocated space in a file.
+
+rename.2
+ Miklos Szeredi [Michael Kerrisk]
+ Document renameat2() system call added in Linux 3.15
+
+shmop.2
+ Michael Kerrisk
+ Document SHM_EXEC
+
+
+Changes to individual pages
+---------------------------
+
+flock.2
+ Michael Kerrisk
+ Employ term "open file description" in DESCRIPTION
+ And include reference to open(2) for an explanation of the term.
+
+getpriority.2
+ Michael Kerrisk
+ SEE ALSO: add sched(7)
+
+getsockopt.2
+ Carsten Andrich
+ SEE ALSO: add packet(7)
+
+link.2
+ Michael Kerrisk [Steven Stewart-Gallus]
+ Document ENOENT error for linkat()
+ See https://bugzilla.kernel.org/show_bug.cgi?id=73301
+
+msgget.2
+ Michael Kerrisk
+ Reword EEXIST error
+
+msgop.2
+ Michael Kerrisk
+ Note capability required to raise MQ size beyond MSGMNB
+
+msync.2
+ Michael Kerrisk [Heinrich Schuchardt]
+ s/flushes... back to disk/flushes... back to filesystem/
+
+nice.2
+ Michael Kerrisk
+ SEE ALSO: add sched(7)
+
+open.2
+ Peter Schiffer
+ Update note on alignment of user buffer and file offset for O_DIRECT
+ The sentence in open(2) man page in notes for O_DIRECT flag:
+
+ "Under Linux 2.6, alignment to 512-byte boundaries suffices."
+
+ is not universally correct. The alignment is a property of the
+ storage, for example, 4k-sector drives with no 512 byte sector
+ emulation will be unable to perform 512-byte direct I/O.
+ Michael Kerrisk
+ Note some of the various synonyms for "open file description"
+ Michael Kerrisk
+ Remove repetitious text on use of fcntl() to change file status flags
+
+open_by_handle_at.2
+ Michael Kerrisk
+ Mention FreeBSD analogs
+
+posix_fadvise.2
+ Michael Kerrisk [Eric Siegerman]
+ Fix wording error under "Architecture-specific variants"
+ See https://bugzilla.kernel.org/show_bug.cgi?id=75431
+
+process_vm_readv.2
+ Michael Kerrisk [Stijn Hinterding]
+ Add feature test macro requirements
+ The _GNU_SOURCE FTM must be defined.
+
+read.2
+ Michael Kerrisk
+ BUGS: detail nonatomicity bug with respect to file offset updates
+ This bug was fixed in Linux 3.14, with commit
+ 9c225f2655e36a470c4f58dbbc99244c5fc7f2d4
+ See also http://thread.gmane.org/gmane.linux.kernel/1649458
+
+sched_get_priority_max.2
+ Michael Kerrisk
+ Small changes consistent with migration of content to sched(7)
+
+sched_rr_get_interval.2
+ Michael Kerrisk
+ Small changes consistent with migration of content to sched(7)
+
+sched_setaffinity.2
+ Michael Kerrisk
+ Small changes consistent with migration of content to sched(7)
+
+sched_setparam.2
+ Michael Kerrisk
+ Small changes consistent with migration of content to sched(7)
+
+sched_yield.2
+ Michael Kerrisk
+ Small changes consistent with migration of content to sched(7)
+
+semget.2
+ Michael Kerrisk
+ Consolidate discussion on noninitialization of semaphores
+ The fact that semget() does not initialize the semaphores
+ in a new set was covered in two places (in DESCRIPTION
+ and BUGS). Consolidate these into one place (in NOTES)
+ and also point out that POSIX.1-2008 says that a future
+ version of the standard may require an implementation to
+ initialize the semaphores to 0.
+ Michael Kerrisk
+ Clarify SEMMNS versus SEMMSL*SEMMNI
+ Michael Kerrisk
+ Rework EINVAL text a little
+ Michael Kerrisk
+ Clarify wording for EEXIST error
+
+shmget.2
+ Manfred Spraul
+ Clarify SHMALL
+ The default for SHMALL is a limit of 8 GB, regardless of
+ PAGE_SIZE. The current documentation does not mention that
+ and is therefore more difficult to understand than necessary.
+ Manfred Spraul
+ Correct math error
+ 2097152 is 2^21, not 2^20.
+ Michael Kerrisk
+ Reword EEXIST error
+ Michael Kerrisk
+ Clarify one of the EINVAL cases
+ Michael Kerrisk
+ Note that SHM_NORESERVE is a Linux extension
+ Michael Kerrisk [Simon Paillard]
+ Fix kernel version numbers in discussion of SHMALL
+ Michael Kerrisk
+ Rework EINVAL text
+ Michael Kerrisk
+ Move and rework discussion of mode bits
+ Michael Kerrisk
+ Reword description of O_EXCL
+
+shmop.2
+ Michael Kerrisk
+ Move fork(2), execve(2), _exit(2) discussion to NOTES
+ Michael Kerrisk
+ Add subheads for shmat() and shmdt()
+ Michael Kerrisk
+ Rework discussion of SHM_RDONLY and SHM_REMAP into list format
+ Michael Kerrisk
+ Structure the attach cases as a list
+
+sigaction.2
+ Alan Curry
+ Fix bad cross reference (times(2) not time(2))
+ The system call that reports child CPU usage is times(2),
+ not time(2).
+
+symlink.2
+ Michael Kerrisk [Steven Stewart-Gallus]
+ Document ENOENT error for symlinkat()
+ See https://bugzilla.kernel.org/show_bug.cgi?id=73301
+
+syscalls.2
+ Michael Kerrisk
+ Add renameat2()
+ And bump kernel version.
+
+write.2
+ Michael Kerrisk
+ BUGS: detail nonatomicity bug with respect to file offset updates
+ This bug was fixed in Linux 3.14, with commit
+ 9c225f2655e36a470c4f58dbbc99244c5fc7f2d4
+ See also http://thread.gmane.org/gmane.linux.kernel/1649458
+
+pthread_attr_setinheritsched.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions pthread_attr_setinheritsched() and
+ pthread_attr_getinheritsched() are thread safe.
+
+pthread_attr_setschedparam.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions pthread_attr_setschedparam() and
+ pthread_attr_getschedparam() are thread safe.
+
+pthread_attr_setschedpolicy.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions pthread_attr_setschedpolicy() and
+ pthread_attr_getschedpolicy() are thread safe.
+
+pthread_attr_setscope.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions pthread_attr_setscope() and pthread_attr_getscope()
+ are thread safe.
+
+pthread_attr_setstack.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions pthread_attr_setstack() and pthread_attr_getstack()
+ are thread safe.
+
+sched_getcpu.3
+ Michael Kerrisk
+ SEE ALSO: add sched(7)
+
+termios.3
+ Michael Kerrisk [Yuri Kozlov]
+ Rework intro text for 'c_oflag'
+ Michael Kerrisk
+ OFDEL is in POSIX.1-2001, so remove "(Not in POSIX)" text
+
+proc.5
+ Jan Moskyto Matejka [Randy Dunlap]
+ Improve description of /proc/stat 'intr' field
+ The sum at the beginning of line "intr" includes also
+ unnumbered interrupts.
+
+packet.7
+ Carsten Andrich [Neil Horman]
+ Improve sockopt documentation for packet sockets
+ Carsten Andrich [Willem de Bruijn]
+ PACKET_LOSS has inverse meaning
+ Stefan Puiu [Daniel Borkmann, Carsten Andrich]
+ Status in PACKET_RX_RING is actually a bit mask
+ Michael Kerrisk [Carsten Andrich]
+ SEE ALSO: add /tools/testing/selftests/net/psock_tpacket.c
+
+
+==================== Changes in man-pages-3.67 ====================
+
+Released: 2014-05-21, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Andy Lutomirski <luto@amacapital.net>
+Aurelien Jarno <aurelien@aurel32.net>
+Bill Allombert <ballombe@debian.org>
+Christoph Hellwig <hch@infradead.org>
+Davidlohr Bueso <davidlohr@hp.com>
+Heinrich Schuchardt <xypron.glpk@gmx.de>
+Ingo Schwarze <schwarze@usta.de>
+Jan Kara <jack@suse.cz>
+Jon Grant <jg@jguk.org>
+Juri Lelli <juri.lelli@gmail.com>
+Lucas De Marchi <lucas.demarchi@profusion.mobi>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Peng Haitao <penght@cn.fujitsu.com>
+Peter Zijlstra <peterz@infradead.org>
+Rasmus Villemoes <rv@rasmusvillemoes.dk>
+Sam Varshavchik <mrsam@courier-mta.com>
+Simon Paillard <spaillard@debian.org>
+Steven Stewart-Gallus <sstewartgallus00@mylangara.bc.ca>
+Török Edwin <edwin@etorok.net>
+William Morriss <wjmelements@gmail.com>
+Yuri Kozlov <yuray@komyakino.ru>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+sched_setattr.2
+ Michael Kerrisk, Peter Zijlstra [Juri Lelli]
+ New page describing sched_setattr(2) and sched_getattr(2)
+
+system.3
+ Michael Kerrisk
+ Rewrote large parts of the page and added a number of details
+
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+sched.7
+ Peter Zijlstra, Michael Kerrisk [Juri Lelli]
+ Document SCHED_DEADLINE
+
+New and changed links
+---------------------
+
+renameat2.2
+ Michael Kerrisk
+ New link to rename.2
+
+sched_getattr.2
+ Michael Kerrisk
+ New link to new sched_setattr
+
+
+Changes to individual pages
+---------------------------
+
+bind.2
+ Michael Kerrisk
+ ERRORS: Add EADDRINUSE for ephemeral port range exhaustion
+
+chown.2
+ Michael Kerrisk
+ NOTES: Add some subheadings
+
+connect.2
+ Michael Kerrisk [William Morriss]
+ ERRORS: Add EADDRNOTAVAIL for ephemeral port range exhaustion
+ Verified from testing and the kernel source.
+ See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745775
+ Michael Kerrisk
+ Remove mention of ip_local_port_range under EAGAIN error
+
+create_module.2
+delete_module.2
+init_module.2
+query_module.2
+ Michael Kerrisk [Lucas De Marchi]
+ Clarify glibc header file declaration/ABI wrapper details
+ create_module(), delete_module(), init_module(), and
+ query_module() are not declared in header files, but
+ through an accident of history glibc provides an ABI
+ for them that it continues to maintain, for
+ compatibility reasons.
+
+execve.2
+ Michael Kerrisk [Steven Stewart-Gallus]
+ Note SIGKILL case when execve() fails beyond the point of no return
+ Michael Kerrisk
+ NOTES: Add a subheading and reorder paragraphs
+
+fanotify_init.2
+ Heinrich Schuchardt [Michael Kerrisk]
+ Document range of permitted flags for event_f_flags
+ With a new patch included in the mm tree, event_f_flags is
+ checked for allowable values.
+
+fcntl.2
+ Michael Kerrisk
+ Add "file locking" subheading under NOTES
+
+fork.2
+ Michael Kerrisk
+ ERRORS: SCHED_DEADLINE tasks can fail with EAGAIN
+ SCHED_DEADLINE tasks can fail with EAGAIN unless the
+ reset-on-fork flag is set.
+
+futex.2
+ Michael Kerrisk
+ Note that there is no glibc wrapper
+
+getpriority.2
+ Rasmus Villemoes
+ Fix prototypes for getpriority() and setpriority()
+ The who argument has type id_t (which happens to be u32 on linux).
+
+get_robust_list.2
+ Rasmus Villemoes
+ Add <sys/types.h> to synopsis of get_robust_list()
+ If one were to implement wrappers for [gs]et_robust_list() using the
+ given prototypes, one would also have to include sys/types.h to get
+ a definition of size_t.
+
+getrusage.2
+ Michael Kerrisk [Bill Allombert]
+ _GNU_SOURCE must be defined to obtain RUSAGE_THREAD definition
+ See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746569
+
+link.2
+open.2
+ Andy Lutomirski [Michael Kerrisk]
+ Update AT_EMPTY_PATH and O_PATH documentation
+
+listen.2
+ Michael Kerrisk
+ ERRORS: Add EADDRINUSE for ephemeral port range exhaustion
+
+mbind.2
+ Rasmus Villemoes
+ Fix prototype for mbind(2)
+ The nmask argument is const. The return type in numaif.h is long.
+ (Well, at least <numaif.h> says nmask is const. The current kernel
+ does not define it as a const argument, but sys_mbind() only
+ passes it to get_nodes(), which does treat it as const.)
+
+msgop.2
+ Davidlohr Bueso [Michael Kerrisk]
+ Enhance description of "full queue" criteria
+
+poll.2
+ Rasmus Villemoes
+ Add <signal.h> to synopsis for ppoll()
+ One needs to #include <signal.h> to get the definition of the
+ type (sigset_t) of the mask argument to ppoll().
+
+readlink.2
+ Rasmus Villemoes
+ Fix return type of readlinkat()
+
+recv.2
+ Michael Kerrisk
+ Clarify details of msg_name and msg_namelen fields
+
+recvmmsg.2
+ Michael Kerrisk
+ Describe timeout bug
+ See https://bugzilla.kernel.org/show_bug.cgi?id=75371
+ and http://thread.gmane.org/gmane.linux.man/5677
+
+remap_file_pages.2
+ Andy Lutomirski [Christoph Hellwig, Andy Lutomirski]
+ remap_file_pages() has no benefit for real files
+ Linux commit 3ee6dafc677a68e461a7ddafc94a580ebab80735 caused
+ remap_file_pages to be emulated when used on real file.
+
+sched_get_priority_max.2
+ Michael Kerrisk
+ 'policy' can also be SCHED_DEADLINE
+
+sched_setaffinity.2
+ Rasmus Villemoes
+ Fix prototype for sched_setaffinity()
+ The mask argument is const.
+
+sched_setparam.2
+ Michael Kerrisk
+ ERRORS: mark errors that apply just for sched_setparam()
+ Michael Kerrisk
+ ERRORS: Add EINVAL for invalid arguments
+ Michael Kerrisk
+ SEE ALSO: add sched_setattr(2)
+
+sched_setscheduler.2
+ Michael Kerrisk
+ ERRORS: mark errors that apply just to sched_setscheduler()
+ Michael Kerrisk
+ ERRORS: add EINVAL case for pid < 0
+ Michael Kerrisk
+ ERRORS: separate out EINVAL cases
+
+semget.2
+ Michael Kerrisk
+ NOTES: Add subheadings and reorder paragraphs
+
+semop.2
+ Rasmus Villemoes
+ Fix prototypes for semop() and semtimedop()
+ The nsops arguments have type size_t, not unsigned, and the
+ timeout argument of semtimedop() is const.
+ Michael Kerrisk
+ NOTES: Add a subheading
+
+send.2
+ Michael Kerrisk
+ Add details on various 'msghdr' fields
+ Michael Kerrisk
+ ERRORS: Add EAGAIN for ephemeral port range exhaustion
+ Michael Kerrisk
+ Add some subheadings under DESCRIPTION
+
+shmget.2
+ Michael Kerrisk
+ NOTES: Add a subheading
+
+stat.2
+ Michael Kerrisk [Aurelien Jarno]
+ Describe feature test macro requirements for file type test macros
+ See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728240
+ Michael Kerrisk
+ Update FTM requirements for lstat()
+ Michael Kerrisk
+ Split discussion of 'st_mode' fields into type and permissions
+ Michael Kerrisk
+ Move text on S_I*() macros to follow text on S_I* macros
+ That ordering is more logical
+
+stime.2
+ Rasmus Villemoes
+ Fix prototype for stime()
+ The argument is const, both according to the actual header files and
+ according to <http://www.sco.com/developers/devspecs/vol1a.pdf>.
+
+syscall.2
+ Rasmus Villemoes
+ Fix prototype for syscall()
+ The first argument and the return value of syscall() has type long,
+ not int.
+
+getopt.3
+ Michael Kerrisk
+ EXAMPLE: Add subheadings to distinguish the two example programs
+
+malloc.3
+ Michael Kerrisk
+ Reword text referring to mallopt(3)
+ Linux libc is no longer "recent"; drop mention of it.
+
+pthread_attr_setinheritsched.3
+pthread_attr_setschedparam.3
+pthread_attr_setschedpolicy.3
+pthread_setaffinity_np.3
+pthread_setschedparam.3
+pthread_setschedprio.3
+pthread_yield.3
+pthreads.7
+ Michael Kerrisk
+ Change references to "sched_setscheduler(2)" to "sched(7)"
+ Change consistent with the fact that the scheduling overview
+ page is now sched(7) not sched_setscheduler(2).
+
+pthread_attr_setstackaddr.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions pthread_attr_setstackaddr() and
+ pthread_attr_getstackaddr() are thread safe.
+
+pthread_attr_setstacksize.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions pthread_attr_setstacksize() and
+ pthread_attr_getstacksize() are thread safe.
+
+pthread_kill.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function pthread_kill() is thread safe.
+
+pthread_kill_other_threads_np.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function pthread_kill_other_threads_np() is thread safe.
+
+pthread_self.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function pthread_self() is thread safe.
+
+pthread_setcancelstate.3
+ Michael Kerrisk
+ Add paragraph breaks to "Asynchronous cancelability" subsection
+
+pthread_setcancelstate.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions pthread_setcancelstate() and
+ pthread_setcanceltype() are thread safe.
+ Michael Kerrisk
+ NOTES: Add some subheadings
+
+pthread_setschedparam.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions pthread_setschedparam() and pthread_getschedparam()
+ are thread safe.
+
+pthread_setschedprio.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function pthread_setschedprio() is thread safe.
+
+pthread_sigmask.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function pthread_sigmask() is thread safe.
+
+pthread_sigqueue.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function pthread_sigqueue() is thread safe.
+
+pthread_testcancel.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function pthread_testcancel() is thread safe.
+
+pthread_yield.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function pthread_yield() is thread safe.
+
+remquo.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions remquo(), remquof() and remquol() are thread safe.
+
+rtime.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function rtime() is thread safe.
+
+sched_getcpu.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function sched_getcpu() is thread safe.
+
+stpcpy.3
+ Ingo Schwarze
+ Note some history of stpcpy()
+ Quoting Ingo:
+ I just noticed that the stpcpy(3) manual contains a speculation
+ that appears to be untrue on closer investigation: That function
+ did not originate in MS DOS, but in Lattice C on AmigaDOS.
+
+ Here is a patch against the git master HEAD to fix that, and add
+ some more historical information. To provide some background and
+ allow you to more easily verify the correctness of the patch, i'm
+ appending my mail to <misc@openbsd.org>, where i'm giving some
+ more details about the history and pointing to some primary
+ sources. That mail also contains the (similar, but shorter)
+ patch i just committed to the OpenBSD manual page.
+
+strcasecmp.3
+ Michael Kerrisk [Aurelien Jarno, Török Edwin]
+ Explain why strcasecmp()+strncasecmp() are also declared in <string.h>
+ See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729436
+
+strcpy.3
+ Michael Kerrisk
+ NOTES: Add a subheading
+
+fd.4
+ Michael Kerrisk [Sam Varshavchik]
+ Fix floppy disk device names
+ The naming convention shown in the page was ancient.
+ Now, the page is consistent with Documentation/devices.txt
+ (where it is noted that "The use of the capital letters
+ D, H and E for the 3.5" models have been deprecated, since
+ the drive type is insignificant for these devices"
+
+proc.5
+ Michael Kerrisk
+ Document /proc/timer_stats
+ Michael Kerrisk
+ (Briefly) document /proc/timer_list
+ Michael Kerrisk
+ Add /proc/sys/kernel/{sched_rt_period_us,sched_rt_runtime_us}
+ Reference sched(7) for an explanation of these two files
+
+capabilities.7
+ Michael Kerrisk
+ Mention sched_setattr(2) under CAP_SYS_NICE
+
+cpuset.7
+ Michael Kerrisk
+ SEE ALSO: add sched(7)
+
+credentials.7
+ Michael Kerrisk
+ Mention sched_getattr() as a place where credentials are checked
+
+fanotify.7
+ Heinrich Schuchardt [Jan Kara]
+ BUGS: error events can be lost when reading from fanotify FD
+ Michael Kerrisk [Heinrich Schuchardt]
+ Fix description of FAN_EVENT_NEXT()
+ FAN_EVENT_NEXT() does not update 'meta'; rather, it returns a
+ pointer to the next metadata structure. In addition, generally
+ rework the description to be a bit clearer and more detailed.
+ Heinrich Schuchardt
+ Document FAN_EVENT_METADATA_LEN
+
+ip.7
+ Michael Kerrisk
+ Note cases where an ephemeral port is used
+ Michael Kerrisk
+ Remove BUGS text on glibc failing to declare in_pktinfo
+ Michael Kerrisk
+ Clarify 'ip_local_port_range' and mention the term "ephemeral ports"
+ Michael Kerrisk
+ Note some more details about assignment of ephemeral ports
+ Michael Kerrisk
+ BUGS: ephemeral port range exhaustion is diagnosed inconsistently
+ Different system calls use different 'errno' values to diagnose
+ exhaustion of the ephemeral port range.
+
+sched.7
+ Michael Kerrisk
+ Document sched_rt_period_us and sched_rt_runtime_us /proc files
+ And rework and relocate the text on dealing with runaway
+ real-time processes.
+ Michael Kerrisk
+ Mention sched_setattr(2) in list of APIs that can change policies
+ Michael Kerrisk
+ sched_setattr(2) can also be used to set 'nice' value
+ Michael Kerrisk
+ Remove mention of sched_setscheduler() when talking about sched_priority
+ There are nowadays multiple ways to set sched_priority (and
+ in fact there always were, since we also had sched_setparam(2)).
+ Michael Kerrisk
+ SEE ALSO: Add Documentation/scheduler/sched-design-CFS.txt
+ Michael Kerrisk
+ Don't mention sched_setscheduler(2) in discussions of setting policies
+ In a couple of places, sched_setscheduler(2) is mentioned as the
+ way of setting policies. But now there is sched_setattr(2) as
+ well, rewrite the text in a more generic way.
+ Michael Kerrisk
+ Rework summary text describing sched_setattr(2) and sched_getattr(2)
+ Note that these APIs are a superset of sched_setscheduler(2)
+ and sched_getscheduler(2).
+ Michael Kerrisk
+ Remove crufty text relating to sched_setscheduler()
+ All of the removed text is in sched_setscheduler(2) and
+ should have been trimmed from this page.
+ Michael Kerrisk
+ SEE ALSO: Mention more files in Documentation/scheduler/ directory
+
+
+==================== Changes in man-pages-3.68 ====================
+
+Released: 2014-05-28, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Alastair McKinstry <mckinstry@computer.org>
+Carsten Grohmann <carstengrohmann@gmx.de>
+Colin Williams <colinwilliams1968@gmail.com>
+Heinrich Schuchardt <xypron.glpk@gmx.de>
+Lars Wirzenius <liw@iki.fi>
+Marko Myllynen <myllynen@redhat.com>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Peng Haitao <penght@cn.fujitsu.com>
+Rasmus Villemoes <rv@rasmusvillemoes.dk>
+Richard Braakman <richard.braakman@jollamobile.com>
+Simon Paillard <spaillard@debian.org>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+localedef.1
+ Marko Myllynen, Richard Braakman, Alastair McKinstry, Lars Wirzenius
+ New page for localedef(1)
+ Add new page based on Debian localedef(1) page.
+
+
+New and changed links
+---------------------
+
+procfs.5
+ New link to proc.5
+ Since the term "procfs" is widely used, it seems reasonable to have
+ a link from that name to proc(5).
+
+
+Changes to individual pages
+---------------------------
+
+locale.1
+ Marko Myllynen
+ Provide a step-by-step example of how to use a custom locale
+ Marko Myllynen
+ Use LC_TELEPHONE instead of LC_MESSAGES in the example
+ yesstr/nostr in LC_MESSAGES are planned to be changed at some
+ point [1], so it's better to provide an example which won't
+ be obsoleted by that change.
+
+ [1] https://sourceware.org/bugzilla/show_bug.cgi?id=16975
+
+adjtimex.2
+ Michael Kerrisk
+ Add feature test macro requirements
+
+clone.2
+ Michael Kerrisk
+ ERRORS: add cross-reference to fork(2) for explanation of EAGAIN
+
+fork.2
+ Michael Kerrisk
+ ERRORS: add pid_max and threads-max to EAGAIN
+ And rewrite text to be the same as pthread_create(3).
+
+getrlimit.2
+ Michael Kerrisk
+ RLIMIT_NPROC is not enforced if CAP_SYS_ADMIN or CAP_SYS_RESOURCE
+
+remap_file_pages.2
+ Rasmus Villemoes
+ Fix prototype
+ The pgoff argument has type size_t, not ssize_t (and in the
+ kernel it is unsigned long).
+
+set_mempolicy.2
+ Rasmus Villemoes
+ Fix prototype for set_mempolicy(2)
+ The nodemask argument is const. The return type in numaif.h is long.
+
+swapon.2
+ Rasmus Villemoes
+ Remove header from synopsis
+ The <asm/page.h> header is not readily available, and the comment
+ seems to indicate that it is for getting PAGE_SIZE. But it is
+ never mentioned why one would need to know that, and it is in any
+ case better obtained using sysconf(), provided by <unistd.h>.
+
+a64l.3
+ Rasmus Villemoes
+ Fix prototype for a64l()
+ The argument is const, both according to POSIX and the
+ glibc headers.
+
+adjtime.3
+ Rasmus Villemoes
+ Add required header
+ The prototype for adjtime(3) is declared in <sys/time.h>.
+
+argz_add.3
+ Rasmus Villemoes
+ Fix prototypes
+ Update the prototypes of argz_{delete,extract,next} to agree with
+ glibc headers and manual.
+
+bstring.3
+ Rasmus Villemoes
+ Fix prototypes
+ The length parameter n has type size_t in bcmp(), bcopy() and
+ bzero().
+
+envz_add.3
+ Rasmus Villemoes
+ Fix prototypes
+ The envz_len parameters for envz_entry() and envz_get() are not
+ passed by reference.
+
+fpathconf.3
+ Rasmus Villemoes
+ Fix prototype
+ The path argument to pathconf() is const.
+
+fseek.3
+ Rasmus Villemoes
+ Fix prototype
+ The pos argument to fsetpos() is const.
+
+gcvt.3
+ Rasmus Villemoes
+ Fix prototype
+ The ndigit parameter to gcvt() has type int.
+
+getaddrinfo_a.3
+ Rasmus Villemoes
+ Fix prototype
+ The pointer arguments to gai_suspend() are const.
+
+getauxval.3
+ Rasmus Villemoes
+ Fix permissions
+ There doesn't seem to be any reason for getauxval.3 to be
+ executable...
+
+getnameinfo.3
+ Rasmus Villemoes
+ Fix prototype
+ The hostlen and servlen parameters have type socklen_t.
+ (The types changed in glibc 2.2)
+ Michael Kerrisk
+ Note types of 'hostlen'; and 'servlen' in glibc < 2.2
+
+getrpcent.3
+ Rasmus Villemoes
+ Fix prototype
+ The argument to getrpcbyname() is const.
+
+getrpcport.3
+ Rasmus Villemoes
+ Add #include and fix prototype
+ The prototype for getrpcport() is obtained by #include'ing
+ <rpc/rpc.h>. Also, update its prototype.
+
+getspnam.3
+ Rasmus Villemoes
+ Fix prototype
+ The struct spwd argument to putspent() is const.
+
+getutent.3
+ Rasmus Villemoes
+ Fix prototypes
+ The arguments to getutid(), getutline(), and pututline()
+ are const.
+
+inet.3
+ Rasmus Villemoes
+ Fix prototype
+ The parameters to inet_makeaddr have type in_addr_t.
+
+inet_net_pton.3
+ Rasmus Villemoes
+ srcfix, cfix
+ Use a consistent style throughout the man-pages.
+
+key_setsecret.3
+ Rasmus Villemoes
+ Fix prototypes
+ Remove const qualifiers from arguments to key_decryptsession,
+ key_encryptsession, and key_setsecret.
+
+makecontext.3
+ Rasmus Villemoes
+ Fix prototype
+ The second argument to swapcontext() is const.
+
+makedev.3
+ Rasmus Villemoes
+ Fix prototype
+ gnu_dev_makedev, and hence its trivial macro wrapper makedev, takes
+ two unsigned int parameters; this is consistent with it being the
+ inverse of (gnu_dev_)major/minor, which return unsigned int.
+
+malloc_trim.3
+ Rasmus Villemoes
+ Fix prototype
+ As mentioned further down, malloc_trim returns an integer.
+
+mq_getattr.3
+ Rasmus Villemoes
+ Fix prototype
+ The newattr parameter to mq_setattr is const.
+
+newlocale.3
+ Marko Myllynen
+ List all available category masks
+ Michael Kerrisk
+ Add LC_ALL_MASK description
+
+nl_langinfo.3
+ Marko Myllynen
+ Expand the example code a bit
+ Better illustrate querying elements from different categories.
+
+perror.3
+ Rasmus Villemoes
+ Fix declaration
+ The elements of the array sys_errlist are also const.
+
+pthread_attr_setaffinity_np.3
+pthread_attr_setdetachstate.3
+pthread_attr_setguardsize.3
+pthread_attr_setinheritsched.3
+pthread_attr_setschedparam.3
+pthread_attr_setschedpolicy.3
+pthread_attr_setscope.3
+pthread_attr_setstack.3
+pthread_attr_setstackaddr.3
+pthread_attr_setstacksize.3
+ Rasmus Villemoes
+ Constify parameters
+ Each of the pthread_attr_get* functions extract some piece of
+ information from a pthread_attr_t, which is passed by const
+ reference. Add the const keyword to the prototypes of these
+ functions.
+
+pthread_cleanup_push_defer_np.3
+ Michael Kerrisk [Rasmus Villemoes]
+ Add feature test macro requirements
+
+pthread_create.3
+ Michael Kerrisk [Carsten Grohmann]
+ Add pid_max limit to EAGAIN error cases
+
+pthread_equal.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function pthread_equal() is thread safe.
+
+pthread_exit.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function pthread_exit() is thread safe.
+
+pthread_getcpuclockid.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function pthread_getcpuclockid() is thread safe.
+
+pthread_setaffinity_np.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions pthread_setaffinity_np() and
+ pthread_getaffinity_np() are thread safe.
+
+pthread_setconcurrency.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions pthread_setconcurrency() and
+ pthread_getconcurrency() are thread safe.
+
+pthread_setname_np.3
+ Rasmus Villemoes
+ Fix prototype
+ The name parameter of pthread_getname_np is an output parameter and
+ hence not const.
+
+pthread_setschedparam.3
+ Rasmus Villemoes
+ Fix prototypes
+ Add return type for pthread_{s,g}etschedparam.
+
+pthread_setschedprio.3
+ Rasmus Villemoes
+ Fix prototype
+ Add return type for pthread_setschedprio.
+
+pthread_sigqueue.3
+ Rasmus Villemoes
+ Add missing #include <signal.h>
+
+rcmd.3
+ Rasmus Villemoes
+ Fix prototypes
+ Unlike the BSDs, the second argument of rcmd() and rcmd_af() has
+ type unsigned short.
+ The first argument of iruserok_af() has type const void*.
+
+re_comp.3
+ Rasmus Villemoes
+ Fix prototypes
+ re_comp and re_exec take const char* arguments.
+
+resolver.3
+ Rasmus Villemoes
+ Fix prototypes and extern-declaration
+ Fix const- and signedness of various char* parameters.
+
+ Also, there is no "struct state", but _res is a struct
+ __res_state. (Actually, _res is errno-like in that it is really a
+ macro expanding to (*__res_state()).)
+
+rexec.3
+ Rasmus Villemoes
+ Fix prototypes
+ The user, passwd and cmd arguments to rexec and rexec_af are all
+ const.
+
+rtime.3
+ Rasmus Villemoes
+ Replace header
+ The header <rpc/des_crypt.h> does not provide rtime();
+ <rpc/auth_des.h> does, as is also implied in both the NOTES and
+ EXAMPLE sections.
+
+scandir.3
+ Rasmus Villemoes
+ Fix prototypes
+ The alphasort and versionsort functions take arguments of type
+ const struct dirent **, not const void *.
+
+setlocale.3
+ Michael Kerrisk [Marko Myllynen]
+ Simplify locale category listing and add GNU-specific locale categories
+ Some information that was here will move to locale(7).
+ Marko Myllynen
+ Remove now obsolete NOTES section
+
+setnetgrent.3
+ Rasmus Villemoes
+ Fix prototype
+ The buflen argument to getnetgrent_r has type size_t.
+
+sigvec.3
+ Rasmus Villemoes
+ Fix prototype
+ The vec argument to sigvec is const.
+
+tsearch.3
+ Rasmus Villemoes
+ Fix prototype
+ The rootp argument to tfind is "void * const *",
+ not "const void **".
+
+core.5
+ Michael Kerrisk
+ Core dump files are nowadays core.pid by default
+
+locale.5
+ Marko Myllynen
+ Document mon_grouping and grouping properly
+ Michael Kerrisk
+ Note default value for 'first_workday'
+ Michael Kerrisk [Marko Myllynen]
+ Add brief descriptions of collating-element and collating-symbol
+ Marko Myllynen
+ t_fmt_ampm is needed only for locales that employ AM/PM convention
+ Michael Kerrisk [Marko Myllynen]
+ Remove crufty reference to /usr/lib/nls/src
+ That file is nowhere to be found
+ Marko Myllynen
+ Clarify LC_TIME/am_pm and LC_NAME keywords usage
+ am_pm should be defined only if AM/PM convention is used to signal
+ applications they should not try to print them when using them in
+ unwanted.
+
+ Same for all LC_NAME keywords expect for name_fmt which should be
+ always defined.
+ Marko Myllynen
+ Clarify lang_term / lang_lib
+ As noted by Keld Simonsen in the lib-locales@sourceware mailing
+ list:
+
+ https://sourceware.org/ml/libc-locales/2014-q2/msg00008.html
+ From: Keld Simonsen <keld at rap dot rap dot dk>
+ To: Marko Myllynen <myllynen at redhat dot com>
+ Date: Tue, 29 Apr 2014 17:02:09 +0200
+
+ lang_term reflects ISO 639-2/T (terminology) codes, while
+ lang_lib reflects ISO 639-2/B (bibliographic) codes.
+ lang_term is preferred over lang_lib codes for locale names.
+ There are 20 specific ISO 639-2/B codes.
+ Marko Myllynen
+ Correct the FILES section
+
+proc.5
+ Michael Kerrisk
+ 'pid_max' is a system-wide limit on number of threads and processes
+ Since PIDs > /proc/sys/kernel/pid_max are not allocated, this
+ file thus also imposes a system-wide limit on the number of
+ threads and processes.
+
+capabilities.7
+ Michael Kerrisk
+ CAP_SYS_ADMIN allows overriding RLIMIT_NPROC
+ Michael Kerrisk
+ CAP_SYS_PTRACE allows process_vm_readv(2) and process_vm_writev(2)
+
+charsets.7
+ Michael Kerrisk [Marko Myllynen]
+ Remove crufty statement that Romanian may be switching to ISO 8859-16
+ Michael Kerrisk
+ Remove ancient paragraph on charsets supported in glibc 2.3.2
+ That test is rather ancient, and probably of little use.
+
+fanotify.7
+ Heinrich Schuchardt
+ Fix to example program: fanotify read() should use aligned buffer
+
+inotify.7
+ Heinrich Schuchardt
+ Add example program
+ This example of the usage of the inotify API shows the
+ usage of inotify_init1(2) and inotify_add_watch(2) as well
+ as polling and reading from the inotify file descriptor.
+ Heinrich Schuchardt
+ munmap() does not generate inotify events
+
+locale.7
+ Marko Myllynen [Michael Kerrisk]
+ Document the LOCPATH environment variable
+ Michael Kerrisk
+ Add further details on various categories
+
+
+
+==================== Changes in man-pages-3.69 ====================
+
+Released: 2014-06-14, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Cyril Hrubis <chrubis@suse.cz>
+Jan Chaloupka <jchaloup@redhat.com>
+Jeff Layton <jlayton@poochiereds.net>
+Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
+KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
+Marko Myllynen <myllynen@redhat.com>
+Michael Kerrisk <mtk.manpages@gmail.com>
+NeilBrown <neilb@suse.de>
+Peng Haitao <penght@cn.fujitsu.com>
+Petr Gajdos <pgajdos@suse.cz>
+Qian Lei <qianl.fnst@cn.fujitsu.com>
+Rasmus Villemoes <rv@rasmusvillemoes.dk>
+Vasiliy Kulikov <segoon@openwall.com>
+Walter Harms <wharms@bfs.de>
+Yuri Kozlov <yuray@komyakino.ru>
+
+Apologies if I missed anyone!
+
+
+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
+---------------------------
+
+locale.1
+ Marko Myllynen
+ Add FILES section, add charmap(5) reference
+ Marko Myllynen
+ Align with recent charmap(5) / repertoiremap(5) changes
+
+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]
+ Describe how to check whether the kernel supports a particular command
+ Michael Kerrisk
+ ERRORS: add EINVAL for invalid 'cmd'
+ Michael Kerrisk
+ Add para introducing advisory locks and noting existence of OFD locks
+ Michael Kerrisk [Jeff Layton]
+ Add notes on F_SETLKW deadlock detection and its limitations
+ Michael Kerrisk
+ Add an explicit note that mandatory locking is not in POSIX
+ Michael Kerrisk
+ Rewrite introductory paragraphs on mandatory locking
+ Make the structure more logical, and also explicitly mention
+ OFD locks.
+ 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
+ Explain POSIX background to EACCES/EAGAIN error for F_GETLK
+ Michael Kerrisk
+ Add NOTES subhead for record locking and NFS
+ Michael Kerrisk [NeilBrown]
+ Note treatment of locks when an NFS client loses contact with the server
+ Michael Kerrisk [Jeff Layton]
+ nfsv4leasetime controls the "contact lost" interval for NFSv4
+
+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
+ Move NOTES text describing implementation of flock()
+ Michael Kerrisk [NeilBrown]
+ Add more details on NFS, including Linux 2.6.37 changes
+ Also: move NOTES text describing interaction of fcntl()
+ and flock() locks.
+
+fork.2
+ Michael Kerrisk
+ Add notes on inheritance of flock() and OFD locks across fork()
+
+lseek.2
+ Michael Kerrisk
+ Add reference to open(2) for discussion of file descriptors and OFDs
+
+open.2
+ Michael Kerrisk
+ Rework and extend the discussion of open file descriptions
+
+open_by_handle_at.2
+ Rasmus Villemoes
+ Add reference to feature_test_macros(7)
+
+recvmmsg.2
+ Rasmus Villemoes
+ Add reference to feature_test_macros(7)
+
+remap_file_pages.2
+ Michael Kerrisk [Kirill A. Shutemov]
+ Note that remap_file_pages() is deprecated
+
+sendmmsg.2
+ Rasmus Villemoes
+ Add reference to feature_test_macros(7)
+
+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
+ Correct the description of the EAGAIN error
+ 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
+
+statfs.2
+ Cyril Hrubis
+ Update MAGIC constants
+ Most of the updates are taken from /usr/include/linux/magic.h,
+ some were found by grepping the Linux source code.
+ Cyril Hrubis [Michael Kerrisk]
+ fstatfs(2) was broken on file descriptors from pipe(2)
+
+syscalls.2
+ Michael Kerrisk
+ Note that remap_file_pages() is deprecated
+
+basename.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions basename() and dirname() are thread safe.
+
+catgets.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function catgets() is thread safe.
+
+getdate.3
+ Rasmus Villemoes
+ Use blank definition of _GNU_SOURCE in example program
+
+getdirentries.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function getdirentries() is thread safe.
+
+getdtablesize.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function getdtablesize() is thread safe.
+
+iconv.3
+ Qian Lei [Peng Haitao]
+ ATTRIBUTES: Note function that is thread-safe
+ The function iconv() is thread safe.
+ Michael Kerrisk
+ SEE ALSO: add iconvconfig(8)
+
+lockf.3
+ Qian Lei [Peng Haitao]
+ ATTRIBUTES: Note function that is thread-safe
+ The function lockf() is thread safe.
+
+malloc_get_state.3
+ Rasmus Villemoes
+ SYNOPSIS: use correct header
+ The nonstandard functions malloc_set_state() and
+ malloc_get_state() are provided by <malloc.h> not <stdlib.h>.
+
+malloc_usable_size.3
+ Qian Lei
+ ATTRIBUTES: Note function that is thread-safe
+ The function malloc_usable_size() is thread safe.
+
+matherr.3
+ Qian Lei [Peng Haitao]
+ ATTRIBUTES: Note function that is thread-safe
+ The function matherr() is thread safe.
+
+mkdtemp.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function mkdtemp() is thread safe.
+
+mkstemp.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions mkstemp(), mkostemp(), mkstemps() and mkostemps()
+ are thread safe.
+
+mq_close.3
+ Qian Lei
+ ATTRIBUTES: Note function that is thread-safe
+ The function mq_close() is thread safe.
+
+mq_getattr.3
+ Qian Lei
+ ATTRIBUTES: Note function that is thread-safe
+ The functions mq_getattr() and mq_setattr() are thread safe.
+
+mq_open.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function mq_open() is thread safe.
+
+mq_receive.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions mq_receive() and mq_timedreceive() are thread safe.
+
+mq_send.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions mq_send() and mq_timedsend() are thread safe.
+
+mq_unlink.3
+ Qian Lei
+ ATTRIBUTES: Note function that is thread-safe
+ The function mq_unlink() is thread safe.
+
+posix_fallocate.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function posix_fallocate() is thread safe.
+
+posix_openpt.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function posix_openpt() is thread safe.
+
+siginterrupt.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is not thread-safe
+ The function siginterrupt() is not thread safe.
+
+system.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function system() is thread safe.
+
+charmap.5
+ Marko Myllynen
+ Update to match current glibc
+ charmap(5) was outdated, bring it to closer to reality by fixing
+ syntax descriptions to match current glibc code and practices,
+ adding missing options, removing obsolete comments and references,
+ and removing now incorrect examples.
+
+locale.5
+ Marko Myllynen
+ Clarify AM/PM settings a bit
+ localedef(1) complains if really undefined, should be empty instead.
+ Also: add some SEE ALSO references.
+ Marko Myllynen
+ Document glibc conventions regarding days and week
+ Based on existing practice and glibc community wiki page at
+ https://sourceware.org/glibc/wiki/Locales
+
+proc.5
+ Michael Kerrisk [Jan Chaloupka, Walter Harms]
+ Add a brief description of /proc/fs
+
+repertoiremap.5
+ Marko Myllynen
+ New page for repertoiremap(5)
+ Rather obsolete feature but localedef(1) refers to repertoiremaps.
+
+bootparam.7
+ Petr Gajdos
+ Describe 'rootflags' and 'rootdelay' kernel parameters
+ Patch based on text from Documentation/kernel-parameters.txt
+
+charsets.7
+ Marko Myllynen
+ Update to reflect past developments
+ Rewrite the introduction to make Unicode's prominence more obvious.
+ Reformulate parts of the text to reflect current Unicode world.
+ Minor clarification for ASCII/ISO sections, some other minor fixes.
+ Marko Myllynen
+ List CJK encodings in the order of C, J, K
+
+environ.7
+ Michael Kerrisk
+ SEE ALSO: add env(1), printenv(1), ld.so(8)
+
+locale.7
+ Marko Myllynen
+ Add some SEE ALSO references
+
+man-pages.7
+ Michael Kerrisk
+ Note that .TH 'date' field is nowadays automatically updated by scripts
+
+signal.7
+ Michael Kerrisk
+ Describe EINTR semantics for recvmmsg(2)
+ Michael Kerrisk
+ Clarify text describing EINTR semantics for socket interfaces
+
+unicode.7
+ Marko Myllynen
+ Update to reflect past developments
+ The unicode(7) page will look more modern with few small changes:
+
+ - drop old BUGS section, editors cope with UTF-8 ok these days,
+ and perhaps the state-of-the-art is better described elsewhere
+ anyway than in a man page
+ - drop old suggestion about avoiding combined characters
+ - refer to LANANA for Linux zone, add registry file reference
+ - drop a reference to an inactive/dead mailing list
+ - update some reference URLs
+
+utf-8.7
+ Marko Myllynen
+ Drop an old comment about UTF-8 replacing ISO 8859
+ And add locale(1) under SEE ALSO.
+
+
+==================== Changes in man-pages-3.70 ====================
+
+Released: 2014-07-08, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Carlos O'Donell <carlos@redhat.com>
+Elie De Brauwer <eliedebrauwer@gmail.com>
+Florian Weimer <fweimer@redhat.com>
+Heinrich Schuchardt <xypron.glpk@gmx.de>
+Marko Myllynen <myllynen@redhat.com>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Nadav Har'El <nyh@math.technion.ac.il>
+NeilBrown <neilb@suse.de>
+Rich Felker <dalias@libc.org>
+Robert P. J. Day <rpjday@crashcourse.ca>
+Simon Paillard <spaillard@debian.org>
+Tomi Salminen <tlsalmin@gmail.com>
+Walter Harms <wharms@bfs.de>
+Yuri Kozlov <yuray@komyakino.ru>
+Кирилл <kirillnow@gmail.com>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+sprof.1
+ Michael Kerrisk [Marko Myllynen]
+ New page for the glibc sprof(1) command
+
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+epoll_ctl.2
+ NeilBrown
+ Document EPOLLWAKEUP
+
+epoll.7
+ NeilBrown
+ Document EPOLLWAKEUP
+
+
+Changes to individual pages
+---------------------------
+
+iconv.1
+iconvconfig.8
+ Marko Myllynen
+ Clarify gconv file terminology a bit
+
+ldd.1
+ Michael Kerrisk
+ SEE ALSO: add sprof(1)
+
+connect.2
+ Michael Kerrisk
+ ERRORS: add EPROTOTYPE
+ See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708394
+
+dup.2
+ Michael Kerrisk [Rich Felker]
+ Fix erroneous discussion regarding closing 'newfd' before calling dup2()
+ And propose a workaround if the caller cares about catching
+ close() time errors.
+
+ See http://stackoverflow.com/questions/23440216/race-condition-when-using-dup2#comment36888604_23444465
+ and http://austingroupbugs.net/view.php?id=411
+ Michael Kerrisk
+ Rework and enhance discussion of dup2()
+ In particular, note that dup2() performs the steps of closing
+ and reusing 'newfd' atomically.
+ Michael Kerrisk
+ Add subhead for dup3()
+
+epoll_ctl.2
+ Michael Kerrisk
+ BUGS: EPOLLWAKEUP is silently ignored without CAP_BLOCK_SUSPEND
+ If the caller does not have CAP_BLOCK_SUSPEND, then EPOLLWAKEUP
+ is silently ignored.
+
+fcntl.2
+ Michael Kerrisk [Tomi Salminen]
+ The return value for F_SETPIPE_SZ is the pipe capacity
+ Michael Kerrisk
+ ERRORS: Document ENOTDIR error for F_NOTIFY
+ Michael Kerrisk
+ Use proper page cross-references in F_NOTIFY discussion
+ Michael Kerrisk
+ Suggest the use of real-time signals with F_NOTIFY
+
+getitimer.2
+ Michael Kerrisk
+ Rewrite a few pieces to clarify some details
+
+inotify_add_watch.2
+ Michael Kerrisk
+ Clarify that the target of a watch is an i-node
+ The target of a watch is an i-node, not a pathname. Clarify
+ the text to prevent the reader possibly misunderstanding
+ that establishing watches by two different links to the same
+ file might create different watch descriptors.
+
+open.2
+ Michael Kerrisk [Кирилл]
+ O_CLOEXEC is also one the flags not ignored when O_PATH is specified
+
+pipe.2
+ Elie De Brauwer
+ PIPE_BUF is defined in limits.h
+ To make use of PIPE_BUF in an application one should include
+ <limits.h>. Adding a reference to this inclusion.
+
+poll.2
+ Michael Kerrisk [Nadav Har'El]
+ The negate-fd-to-ignore technique does not work for file descriptor 0
+ See https://bugzilla.kernel.org/show_bug.cgi?id=79411
+
+set_tid_address.2
+ Michael Kerrisk [Rich Felker]
+ Use "thread" rather than "process" in DESCRIPTION
+ Michael Kerrisk
+ SEE ALSO: add gettid(2)
+
+shmop.2
+ Michael Kerrisk
+ Explain SHMLBA in much more detail
+
+splice.2
+ Michael Kerrisk
+ Document EAGAIN error
+ See https://bugzilla.kernel.org/show_bug.cgi?id=48641
+
+syscalls.2
+ Carlos O'Donell
+ Add prlimit64(2)
+ While trying to reconcile the new features in glibc with the
+ documented entries in the linux kernel man pages I noticed that
+ glibc exports prlimit64 for use by 32-bit applications (as does
+ the linux kernel), but that prlimit64 was not defined in the
+ syscalls list or in the prlimit-related page.
+
+ This is not the complete fix for this, but I don't have the time
+ to explain why and when prlimit64 should be used (or how it should
+ be used safely). Therefore I'm just patching the syscalls.2 list
+ to show that prlimit64 exists and was added in 2.6.36 (verified
+ with git by checking out the tags before and after).
+
+syslog.2
+ Michael Kerrisk
+ Rework introductory paragraph
+ Michael Kerrisk [Robert P. J. Day]
+ Rework text describing loglevels
+ The kernel header file mentioned in the discussion of the KERN_*
+ constants has morphed and is no longer exported inside glibc.
+ And the definitions of the constants themselves changed subtly
+ with kernel commit 04d2c8c83d0e3ac5f78aeede51babb3236200112.
+ So, rewrite the description of the constants to be a bit more
+ abstract.
+ Michael Kerrisk
+ Rewrite parts of the page, and import /proc/sys/kernel/printk
+ * Move /proc/sys/kernel/printk from proc(5) to this page,
+ and correct various details in the discussion of that file.
+ * Rewrite and correct various other details on the page.
+ * Clean out some crufty text.
+ * Miscellaneous minor fixes.
+ Michael Kerrisk
+ Update SYSLOG_ACTION_CONSOLE_OFF + SYSLOG_ACTION_CONSOLE_ON description
+ Details changed in Linux 2.6.32
+
+tee.2
+ Michael Kerrisk
+ Document EAGAIN error
+ See https://bugzilla.kernel.org/show_bug.cgi?id=48641
+
+vmsplice.2
+ Michael Kerrisk
+ Document EAGAIN error
+ See https://bugzilla.kernel.org/show_bug.cgi?id=48641
+
+ether_aton.3
+ Michael Kerrisk
+ Make description of ether_line() bug a little more informative
+
+mallopt.3
+ Michael Kerrisk [Florian Weimer]
+ MALLOC_MMAP_THRESHOLD_ and MALLOC_MMAP_MAX_ *do* work in setgid programs
+ My testing on this point was bogus, overlooking details of
+ strace(1)'s behavior with setuid programs.
+
+ See https://sourceware.org/bugzilla/show_bug.cgi?id=12155
+
+printf.3
+ Michael Kerrisk [Rich Felker]
+ Remove libc4 and libc5 details
+ Rich Felker noted that "scare text" in the man page warned about
+ the use of snprintf() on libc, and that some people had cited
+ this as a reason not to use snprintf(). Linux libc is now
+ ancient history, so there is no real need to keep that text.
+ But, while we're at it, we may as well clear out all of the
+ other ancient libc4 and libc5 pieces in the page. They are
+ nowadays more clutter than help.
+ Michael Kerrisk
+ SUSv3 and later agree with C99 for the snprintf() return value
+ Determined by inspection of the SUSv3 and SUSv4 specifications.
+ Michael Kerrisk
+ Remove some old text about glibc 2.0 changes
+ We probably don't now need such ancient info.
+ Michael Kerrisk
+ Update references to standards for C and S conversion specifiers
+
+profil.3
+ Michael Kerrisk
+ SEE ALSO: add sprof(1)
+
+charmap.5
+ Marko Myllynen
+ Various minor updates and improvements
+ - more precise title
+ - extend description a bit
+ - document previously omitted WIDTH_DEFAULT
+ Marko Myllynen
+ Remove accidental ISO C compliance reference
+ glibc refers in locale/programs/charmap.c to ISO C 99 section
+ 7.17.(2) and ISO C 99 section 5.2.1.(3) that if a character map
+ is not ASCII compatible then the locale using it is not ISO C
+ compliant. This does not state anything about the character set
+ itself.
+
+proc.5
+ Michael Kerrisk
+ Replace /proc/sys/kernel/printk discussion with reference to syslog(2)
+ It makes more sense to have the /proc/sys/kernel/printk with
+ the related material in syslog(2).
+ Michael Kerrisk
+ Rewrite /proc/sys/kernel/printk description
+
+inotify.7
+ Michael Kerrisk
+ Clarify which events are generated for watched directories
+ Really, with respect to watched directories, events fall into
+ three classes (not two, as was shown):
+
+ * Events that can be generated only for the watched directory.
+ * Events that can be generated only for objects that are inside
+ the watched directory.
+ * Events that can be generated both for the watched directory
+ and for objects inside the directory.
+
+ So, mark these three classes more clearly in the list of inotify
+ events.
+ Heinrich Schuchardt [Michael Kerrisk]
+ BUGS: Note possible bug triggered by watch descriptor reuse
+ Watch descriptor IDs are returned by inotify_add_watch().
+ When calling inotify_rm_watch() an IN_IGNORED is placed on the
+ inotify queue pointing to the ID of the removed watch.
+
+ inotify_add_watch() should not return a watch descriptor ID for
+ which events are still on the queue but should return an
+ unused ID.
+
+ Unfortunately, the existing Kernel code does not provide such a
+ guarantee.
+
+ Actually, in rare cases watch descriptor IDs are returned by
+ inotify_add_watch() for which events are still on the inotify
+ queue.
+
+ See https://bugzilla.kernel.org/show_bug.cgi?id=77111
+ Michael Kerrisk
+ Add further detail to the watch descriptor reuse bug
+ As well as inotify_rm_watch(), file deletion and unmounting a
+ filesystem can also cause a watch descriptor to be deleted.
+ Michael Kerrisk
+ The watch descriptor reuse bug may be hard to hit in practice
+ Explain the circumstances in detail, indicating that the
+ bug may be very unlikely to occur in practice.
+ Michael Kerrisk
+ Clarify description of IN_EXCL_UNLINK
+ Clarify the text a little, in particular making it clearer
+ that the target of a watch is an i-node (not a pathname).
+ Michael Kerrisk
+ Clarify IN_ONESHOT explanation
+ Make it clearer that the target of monitoring is an i-node,
+ not a pathname.
+ Michael Kerrisk
+ Make comment on 'mask' field more accurate
+
+libc.7
+ Michael Kerrisk
+ Clarify man-pages policy on documenting C libraries other tahn glibc
+ Michael Kerrisk
+ Use absolute dates in discussion of libc vs glibc
+
+pipe.7
+ Elie De Brauwer
+ Add reference that the pipe capacity can be changed
+ In fcntl(2) F_SETPIPE_SZ, F_GETPIPE_SZ and
+ /proc/sys/fs/pipe-max-size are defined, however
+ pipe(7) still defines the pipe capacity as being
+ a static entity. Adding a reference to fcntl(2).
+ Michael Kerrisk [Walter Harms]
+ Clarify that since 2.6.35, 65535 bytes is the default pipe capacity
+
+ld.so.8
+ Michael Kerrisk
+ Clarify that LD_PROFILE can specify just a single shared object
+ Michael Kerrisk
+ Clarify that LD_PROFILE output is appended to target file
+ The LD_PROFILE output is appended to any existing
+ contents of the target file.
+ Michael Kerrisk
+ SEE ALSO: add sprof(1)
+
+
+==================== Changes in man-pages-3.71 ====================
+
+Released: 2014-08-17, Chicago
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Adrian Bunk <bunk@kernel.org>
+Damir Nedzibovic <d.nedzibovic@anoxtech.com>
+David Prévot <taffit@debian.org>
+D. Barbier <bouzim@gmail.com>
+Jakub Wilk <jwilk@debian.org>
+Jan Chaloupka <jchaloup@redhat.com>
+Marko Myllynen <myllynen@redhat.com>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Mike Frysinger <vapier@gentoo.org>
+NeilBrown <neilb@suse.de>
+Paul Jackson <pj@usa.net>
+Peng Haitao <penght@cn.fujitsu.com>
+Rahul Bedarkar <rahulbedarkar89@gmail.com>
+Rob Landley <rob@landley.net>
+Ryan Hammonds <rhammonds@unicoi.com>
+Simon Paillard <spaillard@debian.org>
+Ville Ylenius <ville@ylenius.net>
+Vince Weaver <vincent.weaver@maine.edu>
+Yuri Kozlov <yuray@komyakino.ru>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+group_member.3
+ Michael Kerrisk
+ New page documenting group_member(3)
+
+isfdtype.3
+ Michael Kerrisk
+ New page documenting isfdtype(3)
+
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+perf_event_open.2
+ Vince Weaver
+ Document new comm_exec flag
+ Linux 3.16 (more specifically, commit 82b897782d10fcc4 )
+ added support for differentiating between process renames
+ caused by exec versus those caused by other methods.
+ Vince Weaver
+ Document new mmap2 record type
+ Linux 3.16 (more specifically, commit a5a5ba72843dd05f9 )
+ enabled the enhanced mmap2 record support.
+ The interface was added in Linux 3.12 but disabled until
+ Linux 3.16.
+ Vince Weaver
+ Document PERF_SAMPLE_BRANCH_COND
+ Linux 3.16 (more specifically, commit bac52139f0b7ab31330 )
+ adds support for gathering PERF_SAMPLE_BRANCH_COND
+ conditional branch values when doing PERF_SAMPLE_BRANCH_STACK
+ sampling.
+
+proc.5
+ Michael Kerrisk
+ Document /proc/PID/comm
+ Michael Kerrisk
+ Document /proc/PID/pagemap
+ Michael Kerrisk
+ Document /proc/PID/personality
+ Michael Kerrisk
+ Document /proc/PID/syscall
+ Michael Kerrisk
+ Document /proc/kpagecount
+ Michael Kerrisk
+ Document /proc/kpageflags
+ Michael Kerrisk
+ Document /proc/sys/vm/overcommit_kbytes
+
+capabilities.7
+ Michael Kerrisk
+ Add CAP_AUDIT_READ
+ CAP_AUDIT_READ is new in Linux 3.16.
+
+
+Global changes
+--------------
+
+ldd.1
+clone.2
+execve.2
+getpagesize.2
+ioperm.2
+msgop.2
+readv.2
+recv.2
+select.2
+send.2
+seteuid.2
+shmop.2
+signal.2
+sync.2
+sysinfo.2
+utime.2
+abs.3
+atoi.3
+catopen.3
+clearenv.3
+ctime.3
+des_crypt.3
+ecvt.3
+flockfile.3
+fseeko.3
+ftime.3
+ftok.3
+ftw.3
+getcwd.3
+getdtablesize.3
+getline.3
+getpass.3
+getpass.3
+getutent.3
+glob.3
+insque.3
+lseek64.3
+memmem.3
+mkstemp.3
+mktemp.3
+on_exit.3
+openpty.3
+putenv.3
+putenv.3
+qecvt.3
+realpath.3
+realpath.3
+remove.3
+setbuf.3
+sigpause.3
+strftime.3
+strptime.3
+tzset.3
+xcrypt.3
+utmp.5
+environ.7
+ipv6.7
+packet.7
+ Michael Kerrisk
+ Remove ancient Linux libc details
+
+access.2
+brk.2
+chmod.2
+eventfd.2
+gethostname.2
+getpriority.2
+mmap.2
+poll.2
+ptrace.2
+readv.2
+sched_setaffinity.2
+select.2
+seteuid.2
+signalfd.2
+sync_file_range.2
+timer_create.2
+uname.2
+wait.2
+ Michael Kerrisk
+ NOTES: add "C library/kernel ABI differences" subheading
+
+
+Changes to individual pages
+---------------------------
+
+access.2
+ Michael Kerrisk
+ Glibc falls back to using access() on kernels that lack faccessat()
+
+bdflush.2
+fsync.2
+sync.2
+proc.5
+ Adrian Bunk
+ Change "sync(1)" to "sync(8)"
+
+bind.2
+ Michael Kerrisk [Ryan Hammonds]
+ Correct EINVAL error description
+ As pointed out by Ryan:
+
+ My application is trying to bind an IPv4 UDP socket to an
+ address. I've found that passing an invalid address length
+ to bind() causes bind to return EINVAL. According to the
+ bind(2) manpage, this should only occur when using unix
+ domain sockets (which I am not).
+
+chmod.2
+ Michael Kerrisk
+ Glibc falls back to chmod() on kernels that don't support fchmodat()
+ Michael Kerrisk
+ Glibc falls back to chown()/lchown() on kernels that lack fchownat()
+
+epoll_wait.2
+ Michael Kerrisk
+ NOTES: describe raw epoll_pwait() system call differences
+
+getgroups.2
+ Michael Kerrisk
+ SEE ALSO: add group_member(3)
+
+getpriority.2
+ Michael Kerrisk
+ Enhance discussion of kernel nice range versus user-space nice range
+ Michael Kerrisk
+ Move text describing nice range on other systems
+
+getrlimit.2
+ Michael Kerrisk
+ Add cross reference to core(5) in discussion of RLIMIT_CORE
+ Michael Kerrisk
+ Describe the "large" resource limit bug on 32-bit platforms
+ See https://bugzilla.kernel.org/show_bug.cgi?id=5042.
+ Michael Kerrisk
+ Glibc's setrlimit() and getrlimit() are implemented using prlimit()
+
+kexec_load.2
+ Michael Kerrisk
+ Note limit of 16 for 'nr_segments'
+ Michael Kerrisk
+ Clarify the 'flags' bits that contain the architecture
+ Michael Kerrisk
+ Add KEXEC_ARCH_68K to list of architectures for 'flags'
+ Michael Kerrisk
+ Reword description of 'flags' a little
+
+link.2
+ Michael Kerrisk
+ Glibc falls back to link() on kernels that lack linkat()
+ Unless 'flags' contains AT_SYMLINK_FOLLOW.
+
+mkdir.2
+ Michael Kerrisk
+ Glibc falls back to mkdir() on kernels that don't support mkdirat()
+
+perf_event_open.2
+ Vince Weaver
+ Clarify PERF_SAMPLE_STACK_USER usage
+ This clarifies the PERF_SAMPLE_STACK_USER section.
+ I found these issue while implementing some code that uses
+ the option. The important change is fixing the name of the
+ sample_stack_user parameter, the rest is just some wording
+ fixes and minor clarifications.
+ Vince Weaver
+ Clarify PERF_SAMPLE_DATA_SRC usage
+ When checking the fields in the PERF_SAMPLE_DATA_SRC type samples
+ you need to shift the masks before doing the compare.
+
+ Although the value you are checking (perf_mem_data_src) is
+ specified as a bitfield so this might all fall apart if trying
+ to access the field in a cross-endian way. The Power people
+ were working on this issue, not sure if they resolved it.
+
+poll.2
+ Michael Kerrisk
+ Describe fifth argument (sigsetsize) of raw ppoll() system call
+
+process_vm_readv.2
+ Michael Kerrisk [Ville Ylenius]
+ Fix typo in example program
+
+readlink.2
+ Michael Kerrisk
+ Glibc falls back to readlink() on kernels that lack readlinkat()
+
+recv.2
+ Michael Kerrisk
+ 'addrlen' should be NULL (not 0) if we don't need sender address
+
+rename.2
+ Michael Kerrisk
+ Glibc falls back to rename() when the kernel doesn't have renameat()
+
+sigwaitinfo.2
+ Michael Kerrisk
+ The raw sigtimedwait() system call has a fifth argument
+
+symlink.2
+ Michael Kerrisk
+ Glibc falls back to symlink() on kernels that lack symlinkat()
+
+sysinfo.2
+ Michael Kerrisk
+ Add VERSIONS section
+
+unlink.2
+ Michael Kerrisk
+ Glibc falls back to unlink() or rmdir() on kernels that lack unlinkat()
+
+atoi.3
+ Michael Kerrisk
+ Downgrade discussion of atoq()
+ Remove most references to atoq() in this page, since this function
+ was present only in Linux libc (not glibc).
+
+cerf.3
+cexp2.3
+clog2.3
+ Michael Kerrisk
+ Update version number on "Not yet in glibc" sentence
+
+fgetgrent.3
+getgrent.3
+getgrent_r.3
+getgrnam.3
+ Michael Kerrisk [Rob Landley]
+ Clarify that 'gr_mem' is a NULL-terminated array of pointers
+
+fseeko.3
+ Michael Kerrisk
+ Add VERSIONS section
+
+ftw.3
+ Michael Kerrisk
+ Add VERSIONS section
+
+getauxval.3
+ Michael Kerrisk
+ Document ENOENT error
+ And add an entry to BUGS explaining the ambiguity that was
+ present before the addition of this error.
+
+getgrouplist.3
+ Michael Kerrisk
+ SEE ALSO: add group_member(3)
+
+getline.3
+ Rahul Bedarkar
+ Close opened file at end of example program
+
+memmem.3
+ Michael Kerrisk
+ Rewrite text of glibc 2.0 bug
+
+printf.3
+ Michael Kerrisk [Jakub Wilk]
+ Clarify details of the %n conversion specifier
+ See http://bugs.debian.org/756602
+ Michael Kerrisk [Jakub Wilk]
+ Note use of 'j', 'z', and 't' length modifiers for '%n'
+ See http://bugs.debian.org/756602
+ Michael Kerrisk
+ Update with some SUSv3 details
+
+setbuf.3
+ Michael Kerrisk
+ Remove ancient Linux libc and 4.x BSD details
+
+strstr.3
+ Michael Kerrisk
+ Remove discussion of Linux libc bugs
+ Linux libc is old enough that we needn't care any longer.
+
+strtod.3
+ Michael Kerrisk
+ Explain NAN(n-char-sequence)
+
+strtod.3
+ Michael Kerrisk
+ SEE ALSO: add nan(3), nanf(3), NANL(3)
+
+updwtmp.3
+ Michael Kerrisk
+ Replace AVAILABILITY section with note to link logwtmp() using -lutil
+ Linux libc details are no longer needed these days.
+
+core.5
+ Rahul Bedarkar
+ Close opened file in example program
+
+proc.5
+ Michael Kerrisk
+ Fix kernel version numbers for /proc/PID/stat fields
+
+proc.5
+ Jan Chaloupka
+ Add missing proc stats fields
+ Adding missing proc stats fields from
+ https://www.kernel.org/doc/Documentation/filesystems/proc.txt
+ Michael Kerrisk [Simon Paillard]
+ Remove crufty text under 'timer_stats'
+ Michael Kerrisk
+ Update /proc/PID/stat 'state' field documentation
+ Michael Kerrisk
+ Improve description of /proc/PID/stat fields added in Linux 3.3 and 3.5
+ Michael Kerrisk
+ Refer to getauxval(3) in discussion of /proc/PID/auxv
+ Michael Kerrisk
+ Rework formatting of /proc/PID/stat list
+ Make the field numbers more prominent.
+ Michael Kerrisk
+ Note that /proc/PID/cmdline is read-only
+ Michael Kerrisk
+ Rework discussion of CommitLimit and /proc/sys/vm/overcommit_memory
+ Michael Kerrisk
+ Improve discussion of /proc/sys/vm/overcommit_ratio
+
+charsets.7
+ David Prévot [Marko Myllynen]
+ Tidy up list
+ Remove German from main list, to be consistent with earlier
+ removal of Dutch and French (in commit a8ed5f7430e0d1).
+
+inotify.7
+ Michael Kerrisk
+ Note that IN_ONLY_DIR can be used to avoid races
+ Michael Kerrisk
+ Note that insertion of IN_MOVED_FROM+IN_MOVED_TO pair is not atomic
+ Michael Kerrisk
+ Mention use of timeout when reading IN_MOVED_TO after IN_MOVED_FROM
+
+man-pages.7
+ Michael Kerrisk
+ Add description of "C library/kernel ABI differences" subsection
+ Michael Kerrisk
+ Rework text describing sections (stylistic improvements)
+
+vdso.7
+ Mike Frysinger
+ Add new i386 vdso symbols in Linux 3.15
+ Michael Kerrisk
+ Note kernel version that exports new i386 symbols (Linux 3.15)
+
+
+==================== Changes in man-pages-3.72 ====================
+
+Released: 2014-09-07, Mountain View
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Christian von Roques <roques@mti.ag>
+Holger Hans Peter Freyther <holger@moiji-mobile.com>
+Michael Haardt <michael@moria.de>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Mike Frysinger <vapier@gentoo.org>
+Peter Schiffer <pschiffe@redhat.com>
+Rusty Russell <rusty@rustcorp.com.au>
+Sorin Dumitru <sdumitru@ixiacom.com>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+memusage.1
+ Peter Schiffer, Michael Kerrisk [Jan Chaloupka]
+ New page for glibc memusage(1) command
+
+memusagestat.1
+ Peter Schiffer [Jan Chaloupka, Michael Kerrisk]
+ New page for glibc memusagestat(1) command
+
+mtrace.1
+ Peter Schiffer [Jan Chaloupka]
+ New page describing the glibc mtrace(1) command
+
+
+Changes to individual pages
+---------------------------
+
+connect.2
+ Michael Haardt
+ Note that a new socket should be used if connect() fails
+
+fcntl.2
+ Michael Kerrisk
+ One must define _GNU_SOURCE to get the F_OFD_* definitions
+
+poll.2, select.2
+ Rusty Russell
+ Fix erroneous description of "available for write".
+ POSIX says: "POLLOUT Normal data may be written without
+ blocking.". This "may" is misleading, see the POSIX
+ write page:
+
+ Write requests to a pipe or FIFO shall be handled in the
+ same way as a regular file with the following exceptions:
+ ...
+ If the O_NONBLOCK flag is clear, a write request may cause
+ the thread to block, but on normal completion it shall
+ return nbyte.
+ ...
+ When attempting to write to a file descriptor (other than a
+ pipe or FIFO) that supports non-blocking writes and cannot
+ accept the data immediately:
+
+ If the O_NONBLOCK flag is clear, write() shall block the
+ calling thread until the data can be accepted.
+
+ If the O_NONBLOCK flag is set, write() shall not block the
+ thread. If some data can be written without blocking the
+ thread, write() shall write what it can and return the
+ number of bytes written. Otherwise, it shall return -1 and
+ set errno to [EAGAIN].
+
+ The net result is that write() of more than 1 byte on a
+ socket, pipe or FIFO which is "ready" may block: write()
+ (unlike read!) will attempt to write the entire buffer and
+ only return a short write under exceptional circumstances.
+
+ Indeed, this is the behaviour we see in Linux:
+
+ https://github.com/rustyrussell/ccan/commit/897626152d12d7fd13a8feb36989eb5c8c1f3485
+ https://plus.google.com/103188246877163594460/posts/BkTGTMHDFgZ
+
+errno.3
+ Michael Kerrisk
+ SEE ALSO: add errno(1)
+
+rtnetlink.3
+ Holger Hans Peter Freyther
+ Fix parameters for the send() call in the example
+
+inotify.7
+ Michael Kerrisk
+ IN_OPEN and IN_CLOSE_NOWRITE can also occur for directories
+ Michael Kerrisk
+ IN_CLOSE_WRITE occurs only for files (not monitored directory)
+ Michael Kerrisk
+ IN_MODIFY is generated for files only (not monitored directories)
+ Michael Kerrisk
+ IN_ACCESS occurs only for files inside directories
+ IN_ACCESS does not occur for monitored directory.
+
+packet.7
+ Sorin Dumitru
+ Fix include file
+ It looks like most of the socket options from this man pages
+ are not defined in <netpacket/packet.h>. They are defined in
+ <linux/if_packet.h> so we should include that one.
+
+
+==================== Changes in man-pages-3.73 ====================
+
+Released: 2014-09-21, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+David Prévot <taffit@debian.org>
+Eric W. Biederman <ebiederm@xmission.com>
+J. Bruce Fields <bfields@fieldses.org>
+Justin Cormack <justin@street-vision.com>
+Lorenzo Beretta <lory.fulgi@infinito.it>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Rob Landley <rob@landley.net>
+Serge E. Hallyn <serge@hallyn.com>
+Serge Hallyn <serge.hallyn@ubuntu.com>
+Vasily Kulikov <segoon@openwall.com>
+Vincent Lefevre <vincent@vinc17.net>
+Vitaly Rybnikov <frodox@zoho.com>
+Yuri Kozlov <yuray@komyakino.ru>
+
+Apologies if I missed anyone!
+
+
+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
+
+flock.2
+ Michael Kerrisk [J. Bruce Fields]
+ Don't mention "classical BSD" in discussion of fcntl()/flock interaction
+ The noninteraction of flock(2) and fcntl(2) locks does
+ not seem to be classical BSD semantics (at least, checking
+ the 4.4BSD sources suggest that the lock types do interact,
+ although there have been other systems also where fcntl()
+ and flock() locks do not interact). So, fix the text
+ discussing "classical BSD" lock semantics.
+
+getunwind.2
+ Michael Kerrisk [Yuri Kozlov]
+ Fix description of return value
+ s/size of unwind table/size of the unwind data/
+
+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
+
+semop.2
+ Michael Kerrisk
+ Refer to clone(2) for semantics of CLONE_SYSVSEM and semadj lists
+
+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
+
+clock.3
+ Michael Kerrisk [Vincent Lefevre]
+ The implementation uses clock_gettime() was to improve *accuracy*
+ (The man page text mistakenly used the word "precision".)
+
+drand48.3
+ Michael Kerrisk [Lorenzo Beretta]
+ Remove crufty text about SVID 3 marking drand48() obsolete
+ See http://bugs.debian.org/758293
+
+proc.5
+ Michael Kerrisk
+ Move /proc/[pid]/mounts text to namespaces.7
+ Michael Kerrisk
+ Move /proc/[pid]/mountstats text to namespaces.7
+
+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
+
+mq_overview.7
+ Michael Kerrisk
+ Refer to namespaces(7) for info on POSIX MQs and IPC namespaces
+
+svipc.7
+ Michael Kerrisk
+ Refer to namespaces(7) for info on System V IPC and IPC namespaces
+
+
+==================== Changes in man-pages-3.74 ====================
+
+Released: 2014-10-03, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Arto Bendiken <arto@bendiken.net>
+Ben Hutchings <ben@decadent.org.uk>
+Benjamin Herr <ben@0x539.de>
+C. Alex North-Keys <erlkonig@talisman.org>
+Carlos O'Donell <carlos@redhat.com>
+Cyril Hrubis <chrubis@suse.cz>
+Davidlohr Bueso <dave@stgolabs.net>
+Doug Ledford <dledford@redhat.com>
+Elie De Brauwer <eliedebrauwer@gmail.com>
+Heinrich Schuchardt <xypron.glpk@gmx.de>
+Jonny Grant <jg@jguk.org>
+Lanchon <lanchon@gmail.com>
+Manfred Spraul <manfred@colorfullife.com>
+Marko Myllynen <myllynen@redhat.com>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Shriramana Sharma <samjnaa@gmail.com>
+Thomas Mack <mack@ifis.cs.tu-bs.de>
+Wieland Hoffmann <themineo@gmail.com>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+pldd.1
+ Michael Kerrisk
+ New page for pldd(1) command added to glibc in version 2.15
+
+cp1252.7
+ Marko Myllynen
+ New page documenting CP 1252
+ CP 1252 is probably one of the most used Windows Code Pages so
+ let's add a page for it alongside with the already provided
+ CP 1251 page.
+
+ Table generated from /usr/share/i18n/charmaps/CP1252.
+
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+mq_overview.7
+ Michael Kerrisk
+ Document /proc/sys/fs/mqueue/msgsize_default
+ Michael Kerrisk
+ Document /proc/sys/fs/mqueue/msg_default
+
+
+Changes to individual pages
+---------------------------
+
+ldd.1
+ Michael Kerrisk
+ SEE ALSO: add pldd(1)
+
+execve.2
+ Michael Kerrisk [C. Alex North-Keys]
+ Remove unneeded ".sh" extension in interpreter script example
+ See https://bugzilla.kernel.org/show_bug.cgi?id=84701
+
+fanotify_init.2
+ Heinrich Schuchardt
+ BUGS: O_CLOEXEC is ignored
+ Michael Kerrisk [Heinrich Schuchardt]
+ The 'event_f_flags' failure to check invalid flags was fixed in 3.15
+
+fanotify_mark.2
+ Michael Kerrisk
+ Note that various bugs were fixed in Linux 3.16
+
+getrlimit.2
+ Michael Kerrisk [Doug Ledford]
+ Since Linux 3.5, the accounting formula for RLIMIT_MSGQUEUE has changed
+
+open.2
+ Michael Kerrisk [Shriramana Sharma]
+ Fix number and formula in description of EOVERFLOW error
+
+readlink.2
+ Michael Kerrisk [Ben Hutchings]
+ Fix description of readlinkat() with empty 'pathname'
+ Michael Kerrisk
+ SEE ALSO: add realpath(3)
+
+sched_setattr.2
+sched_setscheduler.2
+ Michael Kerrisk
+ SEE ALSO: add chrt(1)
+
+shmget.2
+ Manfred Spraul [Michael Kerrisk, Davidlohr Bueso]
+ Update for increase of SHMALL and SHMMAX
+ The default values of SHMALL and SHMMAX have been increased.
+
+syscalls.2
+ Michael Kerrisk
+ Add 3 new system calls added in Linux 3.17
+
+vmsplice.2
+ Cyril Hrubis
+ vmsplice() does not fail when nr_segs==0
+ This nr_segs==0 case is no-op; the call succeeds and no
+ EINVAL error is returned.
+
+dlopen.3
+ Michael Kerrisk
+ SEE ALSO: add pldd(1)
+
+fseeko.3
+ Michael Kerrisk [Thomas Mack]
+ _FILE_OFFSET_BITS must be defined before including any header file
+
+getgrent.3
+ Carlos O'Donell
+ Add ENOENT and EAGAIN to error list
+
+mq_getattr.3
+ Michael Kerrisk
+ Add an example program
+ The example program can be used to discover the default
+ 'mq_maxmsg' and 'mq_msgsize' values used to create a queue with
+ a mq_open(3) call in which 'attr' is NULL.
+
+mq_open.3
+ Michael Kerrisk
+ Two /proc files control the defaults for the attrp==NULL case
+ Refer the reader to the discussion in mq_overview(7) for a
+ discussion of these files, which exist since Linux 3.5.
+
+realpath.3
+ Michael Kerrisk
+ SEE ALSO: add realpath(1)
+
+proc.5
+ Elie De Brauwer
+ Document /proc/buddyinfo
+ This patch adds a short description about the contents of
+ /proc/buddyinfo and how this file can be used to assist
+ in checking for memory fragmentation issues.
+ Michael Kerrisk
+ Mention pmap(1) in discussion of /proc/PID/smaps
+
+armscii-8.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+ascii.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+ This and [the related *.7] patches will provide unification of
+ charset pages, minor cleanups, and some unifying cosmetic
+ changes. References are adjusted so that all pages include
+ a reference to charsets(7), which contains a description of
+ these sets, stray comments are removed, some obsolete
+ statements (like ISO 8859-1 being the de-facto ASCII
+ replacement) are removed, and some minor reformatting
+ to minimize diff's between the pages are done.
+
+ The actual substance, the character tables, remain unchanged.
+
+ This series changes the following pages (under man7): ascii,
+ armscii, cp1251, koi8-r, koi8-u, and all of iso_8859-*.
+
+cp1251.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-10.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-11.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-13.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-14.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-15.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-16.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-1.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-2.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-3.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-4.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-5.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-6.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-7.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-8.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-9.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+koi8-r.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+ - remove stray comments, streamline description
+ (charsets(7) and Wikipedia provide more detailed
+ and up-to-date description)
+ - list differences between koi8-r.7 vs koi8-u.7
+
+koi8-u.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+ - remove stray comments, streamline description
+ (charsets(7) and Wikipedia provide more detailed
+ and up-to-date description)
+ - list differences between koi8-r.7 vs koi8-u.7
+
+mq_overview.7
+ Michael Kerrisk
+ Update queues_max details for Linux 3.14
+ And in general rework the text a little.
+ Michael Kerrisk
+ Update discussion of HARD_MSGMAX
+ The limit has changed in 2.6.33 and then again in 3.5.
+ Michael Kerrisk [Arto Bendiken]
+ Update details for 'queues_max' limit
+ Things changed in Linux 3.5.
+ See https://bugs.launchpad.net/bugs/1155695
+ Michael Kerrisk
+ Update details on defaults and ceiling for 'msgsize_max' limit
+ Michael Kerrisk
+ Rework discussion of HARD_MSGMAX
+ Michael Kerrisk [Davidlohr Bueso]
+ Various fixes after review from Davidlohr Bueso
+
+sched.7
+ Michael Kerrisk
+ SEE ALSO: add taskset(1)
+
+ld.so.8
+ Michael Kerrisk
+ SEE ALSO: add pldd(1)
+ Michael Kerrisk
+ SEE ALSO: add dlopen(3)
+ Michael Kerrisk
+ SEE ALSO: add ld(1)
+
+
+
+==================== Changes in man-pages-3.75 ====================
+
+Released: 2014-10-15, Düsseldorf
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Jonny Grant <jg@jguk.org>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Robert Schweikert <rjschwei@suse.com>
+Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
+Walter Harms <wharms@bfs.de>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+pthread_rwlockattr_setkind_np.3
+ Robert Schweikert [Michael Kerrisk]
+ New page documenting pthread_rwlockattr_[sg]etkind_np(3)
+ Documents pthread_rwlockattr_setkind_np(3) and
+ pthread_rwlockattr_getkind_np(3).
+
+
+New and changed links
+---------------------
+
+pthread_rwlockattr_getkind_np.3
+ Robert Schweikert
+ New link to pthread_rwlockattr_setkind_np(3)
+
+
+Changes to individual pages
+---------------------------
+
+readlink.2
+ Michael Kerrisk [Jonny Grant]
+ Add free() call to example program
+
+readv.2
+ Michael Kerrisk
+ The raw preadv() and pwritev() syscalls split 'offset' into 2 arguments
+
+signal.7
+ Michael Kerrisk
+ pthread_mutex_lock() and pthread_cond_wait() are restartable
+ pthread_mutex_lock(, pthread_cond_wait(), and related APIs are
+ automatically restarted if interrupted by a signal handler.
+
+unix.7
+ Michael Kerrisk [Carlos O'Donell, David Miller, Tetsuo Handa]
+ Various additions and rewordings
+ Notable changes:
+ * Clarify some details for pathname sockets.
+ * Add some advice on portably coding with pathname sockets.
+ * Note the "buggy" behavior for pathname sockets when
+ the supplied pathname is 108 bytes (after a report by
+ Tetsuo Handa).
+
+
+==================== Changes in man-pages-3.76 ====================
+
+Released: 2014-12-31, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Adam Jiang <jiang.adam@gmail.com>
+Andrea Balboni <andrea.balboni@unimore.it>
+Andreas Schwab <schwab@suse.de>
+Bernhard Walle <bernhard@bwalle.de>
+Carlos O'Donell <carlos@redhat.com>
+David Wragg <david@wragg.org>
+Florian Westphal <fw@strlen.de>
+Heinrich Schuchardt <xypron.glpk@gmx.de>
+Huxiaoxiang <huxiaoxiang@huawei.com>
+Jan Chaloupka <jchaloup@redhat.com>
+Jonathan Wakely <jwakely@redhat.com>
+Jonny Grant <jg@jguk.org>
+Josh Triplett <josh@joshtriplett.org>
+Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
+Laurent Georget <laurent.georget@supelec.fr>
+Manuel López-Ibáñez <lopezibanez@gmail.com>
+Marko Myllynen <myllynen@redhat.com>
+Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
+Mel Gorman <mgorman@suse.de>
+Michael Gehring <mg@ebfe.org>
+Michael Haardt <michael@moria.de>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Mike Frysinger <vapier@gentoo.org>
+Rasmus Villemoes <rv@rasmusvillemoes.dk>
+Richard Weinberger <richard@nod.at>
+Rich Felker <dalias@libc.org>
+Scott Harvey <scott.harvey@stonybrook.edu>
+Siddhesh Poyarekar <siddhesh.poyarekar@gmail.com>
+Simon Newton <nomis52@gmail.com>
+Simon Paillard <spaillard@debian.org>
+Sven Hoexter <sven@stormbind.net>
+Tobias Werth <werth@cs.fau.de>
+Weijie Yang <weijie.yang.kh@gmail.com>
+Will Newton <will.newton@linaro.org>
+Yuri Kozlov <yuray@komyakino.ru>
+刘湃 <liupai_work@163.com>
+尹杰 <writalnaie@gmail.com>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+adjtimex.2
+ Laurent Georget
+ Add fields in struct timex description
+ This patch updates the man page with the new fields added in
+ struct timex since last edition of the man page.
+ Laurent Georget [Michael Kerrisk]
+ Document ADJ_TAI
+ Michael Kerrisk
+ Improve description of ADJ_OFFSET_SINGLESHOT
+ Michael Kerrisk
+ Add brief documentation of ADJ_MICRO and ADJ_NANO
+ Michael Kerrisk
+ Reformat return value list
+ And remove numeric values, since they're not needed
+ Michael Kerrisk
+ Other 'modes' bits are ignored on ADJ_OFFSET_*
+ Other bits in 'modes' are ignored if modes contains
+ ADJ_OFFSET_SINGLESHOT or ADJ_OFFSET_SS_READ.
+ Michael Kerrisk
+ Add nanosecond details
+ Fixes https://bugzilla.kernel.org/show_bug.cgi?id=61171.
+ Michael Kerrisk
+ Document ADJ_OFFSET_SS_READ
+ Michael Kerrisk
+ Reformat 'times' flags as list
+ And remove numeric values, since they're not needed.
+ Michael Kerrisk
+ Note effect of ADJ_NANO for ADJ_SETOFFSET
+ Michael Kerrisk
+ Add comment noting that timex structure contains padding bytes
+ Michael Kerrisk
+ Add more details to description of 'tai' field
+ Michael Kerrisk
+ Note meaning of "PLL" abbreviation
+ Michael Kerrisk
+ Clarify which 'timex' field is used by each 'modes' bit
+ Michael Kerrisk
+ Document timex 'status' bits
+ Michael Kerrisk
+ Clarify treatment of other 'modes' bits for ADJ_OFFSET_*
+ Michael Kerrisk
+ Update RFC number: RFC 5905 obsoletes RFC 1305
+ Michael Kerrisk
+ Briefly document ADJ_SETOFFSET
+ Michael Kerrisk
+ Note PPS (pulse per second) fields in timex structure
+
+sigreturn.2
+ Michael Kerrisk
+ Add (a lot) more detail on the signal trampoline
+ And rewrite much of the page.
+
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+proc.5
+ Bernhard Walle
+ Document /proc/thread-self
+ /proc/thread-self has been introduced in Linux 3.17 with
+ commit 0097875bd41528922fb3bb5f348c53f17e00e2fd.
+ Sven Hoexter [Michael Kerrisk, Kamezawa Hiroyuki]
+ Document "VmSwap" field of /proc/[pid]/status
+ Florian Westphal
+ Document /proc/net/netfilter/nfnetlink_queue
+
+
+Changes to individual pages
+---------------------------
+
+localedef.1
+ Marko Myllynen
+ Mention default path for compiled files
+
+clock_nanosleep.2
+ Michael Kerrisk
+ Note that 'clock_id' can also be a CPU clock ID
+
+epoll_ctl.2
+ Michael Kerrisk
+ Regular files and directories can't be monitored with epoll_ctl()
+
+ioctl.2
+ Heinrich Schuchardt
+ Rename 'd' argument to 'fd' in text
+ In most other manpages file descriptors are called 'fd'.
+ This patches renames attribute 'd' to 'fd'.
+
+madvise.2
+ Michael Kerrisk
+ VERSIONS: Support for madvise() is now configurable
+ Support for this system call now depends on the
+ CONFIG_ADVISE_SYSCALLS configuration option.
+
+open.2
+ Michael Kerrisk
+ Enhance rationale discussion for openat() and friends
+
+posix_fadvise.2
+ Mel Gorman
+ Document the behavior of partial page discard requests
+ It is not obvious from the interface that "partial page discard"
+ requests are ignored. It should be spelled out.
+ Michael Kerrisk [Weijie Yang]
+ ERRORS: Since 2.6.16, the kernel correctly deals with the ESPIPE case
+ Michael Kerrisk
+ Support for fadvise64() is now configurable
+ Support for this system call now depends on the
+ CONFIG_ADVISE_SYSCALLS configuration option.
+
+prctl.2
+ Andreas Schwab
+ Correct description of null-termination in PR_GET_NAME and PR_SET_NAME
+ The size of the process name has always been at most 16 byte
+ _including_ the null terminator. This also means that the
+ name returned by PR_GET_NAME is always null-terminated.
+ Michael Kerrisk
+ PR_SET_NAME silently truncates strings that exceed 16 bytes
+
+restart_syscall.2
+ Michael Kerrisk
+ Add some text explaining why restart_syscall() exists
+
+sched_setaffinity.2
+ Michael Kerrisk
+ NOTES: Add paragraph on how to discover set of CPUs available on system
+ Michael Kerrisk
+ SEE ALSO: add nproc(1) and lscpu(1)
+
+select.2
+ Michael Kerrisk
+ SEE ALSO: add restart_syscall(2)
+
+semop.2
+ Michael Kerrisk
+ Add note that interrupted semtimedop() returns 'timeout' unchanged
+ Michael Kerrisk
+ Remove information about semtimedop() EAGAIN that is repeated elsewhere
+ Michael Kerrisk
+ Add subsection head for semtimedop()
+
+setsid.2
+ Michael Kerrisk
+ Rewrite some pieces and add some details
+ Among other changes, add an explanation of why setsid() can't
+ be called from a process group leader
+
+sgetmask.2
+ Michael Kerrisk
+ Since 3.16, support for these system calls is configurable
+ Support for these calls is now dependent on the setting of the
+ CONFIG_SGETMASK_SYSCALL option.
+
+sigaction.2
+ Michael Kerrisk
+ Document SA_RESTORER
+ Michael Kerrisk
+ Add some detail on the sa_restorer field
+ Michael Kerrisk
+ SEE ALSO: add sigreturn(2)
+
+splice.2
+ Michael Kerrisk
+ Reformat description of 'fd_in' and 'off_in' to improve readability
+
+syscall.2
+ Michael Kerrisk
+ SEE ALSO: add errno(3)
+
+syscalls.2
+ Michael Kerrisk
+ SEE ALSO: add errno(3)
+ Michael Kerrisk
+ 3.19 adds execveat()
+ Michael Kerrisk
+ Add bpf(2) to list
+
+tee.2
+ Michael Kerrisk
+ Add shell session demonstrating use of the example program
+
+tkill.2
+ Michael Kerrisk [Rich Felker]
+ Remove bogus text saying tgid==-1 makes tgkill() equivalent to tkill()
+
+abort.3
+ Michael Kerrisk
+ Note that SIGABRT is raised as though raise(3) is called
+ Also note that abort() is POSIX.1-2008 compliant.
+
+cmsg.3
+ David Wragg
+ Ensure buf is suitably aligned in sending example
+ Inspection of the definition of CMSG_FIRSTHDR (both in glibc and
+ the suggested definition in RFC3542) shows that it yields the
+ msg_control field. So when sending, the pointer placed in
+ msg_control should be suitably aligned as a struct cmsghdr.
+ In the sending example, buf was declared as a bare char array,
+ and so is not necessarily suitably aligned.
+
+ The solution here involves placing buf inside a union, and is
+ based on the sockets/scm_rights_send.c sample from The Linux
+ Programming Interface "dist" source code collection.
+
+exp10.3
+ Michael Kerrisk
+ Before glibc 2.19, exp() did not give ERANGE error on underflow
+ http://sources.redhat.com/bugzilla/show_bug.cgi?id=6787
+
+ftw.3
+ Michael Kerrisk
+ FTW_CHDIR has no effect on the 'fpath' argument passed to fn()
+
+getopt.3
+ Michael Kerrisk [Jonny Grant]
+ Ensure that 'nsecs' is used
+
+ilogb.3
+ Michael Kerrisk [Will Newton]
+ Since glibc 2.16, ilogb() does correctly diagnose domain errors
+
+memcmp.3
+ Michael Haardt
+ Document return value for n==0 case
+ Michael Haardt
+ Warn against use of memcmp() for comparing security-critical data
+
+mq_open.3
+ Michael Kerrisk
+ Document the O_CLOEXEC flag
+ Michael Kerrisk
+ Place 'flags' constants in alphabetical order
+
+pow.3
+ Manuel López-Ibáñez
+ Add note on performance characteristics of pow()
+
+pthread_setschedparam.3
+ Simon Newton
+ Fix logic error in example program
+ The example program will crash if -A is used, since 'attr'
+ is uninitialized.
+
+ $ ./a.out -A
+ *** Error in `./a.out': free(): invalid pointer: 0xb779c3c4 ***
+ Aborted (core dumped)
+ 刘湃
+ Small fixes to example program
+
+sigvec.3
+ Michael Kerrisk
+ Starting with version 2.21, glibc no longer exports sigvec()
+
+sysconf.3
+ Josh Triplett
+ Document _SC_NGROUPS_MAX
+ Already documented in getgroups(2), but not in sysconf(3).
+
+termios.3
+ Michael Kerrisk
+ SEE ALSO: add tset(1)
+
+tgamma.3
+ Michael Kerrisk
+ Since glibc 2.18, errno is correctly set to EDOM when (x == -infinity))
+
+wordexp.3
+ Carlos O'Donell
+ Make it clear that WRDE_NOCMD prevents command substitution
+ The use of WRDE_NOCMD prevents command substitution. If the flag
+ WRDE_NOCMD is set then no command substitution shall occur and
+ the error WRDE_CMDSUB will be returned if such substitution is
+ requested when processing the words.
+
+ The manual page as-is makes it seem like the command substitution
+ occurs, and an error is returned *after* the substitution.
+ This patch clarifies that.
+
+locale.5
+ Marko Myllynen
+ Describe the formats of values
+ locale(5) describes what a locale should define but doesn't
+ spell out how (in what format). The patch attempts to address
+ this, it also has few trivial additional enhancements.
+
+ * Reference to locale(7) for category descriptions.
+ * Clarify first_workday in NOTES a bit.
+ * Add upstream BZ reference for two missing LC_ADDRESS fields.
+ Marko Myllynen
+ Fix miscoded character
+
+resolv.conf.5
+ Jan Chaloupka
+ Add missing no-tld-query option
+ Based on commit [1], the no-tld-query option exists for
+ resolv.conf configuration file. Description of this option
+ is provided in [2]. This patch just copies this option
+ into resolv.conf.5 man page. Plus changes 'a' member
+ into 'an' before 'unqualified name as if it ...'
+ on the third line of [2]. Based on [3], this option
+ was added in glibc 2.14 as solving [4] bug.
+
+ [1] https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=f87dfb1f11c01f2ccdc40d81e134cd06b32e28e8
+ [2] http://www.daemon-systems.org/man/resolv.conf.5.html man page.
+ [3] https://sourceware.org/git/?p=glibc.git;a=blob;f=NEWS;h=952f32af17e7fb49c4c1a305de673a13075bfaf5;hb=f87dfb1f11c01f2ccdc40d81e134cd06b32e28e8
+ [4] https://sourceware.org/bugzilla/show_bug.cgi?id=12734
+
+credentials.7
+ Josh Triplett
+ Cross-reference getgroups(2)
+ Since credentials.7 discusses supplementary GIDs, it should
+ reference getgroups(2).
+
+fanotify.7
+ Heinrich Schuchardt
+ Allow relative paths in example
+ The current example code requires passing an absolute
+ path to the mount to be watched.
+
+ By passing AT_FDCWD to fanotify_mark it can use both
+ absolute and relative paths.
+ Heinrich Schuchardt
+ fallocate(2) creates no events
+ fallocate(2) should create FAN_MODIFY events but does not.
+ Heinrich Schuchardt [Michael Kerrisk]
+ fanotify notifies only events generated on the same mount
+ Unfortunately, fanotify does not inform listeners for all paths
+ under which a touched filesystem object is visible, but only the
+ listener using the same path as the process touching the
+ filesystem object.
+ Heinrich Schuchardt
+ Update BUGS to note bugs still not fixed in 3.17
+ I bumped the Linux version number in the BUGS section to 3.17.
+
+inotify.7
+ Heinrich Schuchardt
+ fallocate(2) does not trigger inotify events
+ Calling fallocate(2) does not result in inotify events.
+
+locale.7
+ Marko Myllynen
+ Improve LOCPATH description
+ LOCPATH is ignored by privileged programs.
+
+ Add locale archive references.
+
+ Add FILES section.
+
+man-pages.7
+ Michael Kerrisk [Laurent Georget]
+ Clarify that SEE ALSO entries may refer to pages from other projects
+
+signal.7
+ Michael Kerrisk
+ Mention other "slow devices"
+ Reads from eventfd(2), signalfd(2), timerfd(2), inotify(7),
+ and fanotify(7) file descriptors are also slow operations
+ that are restartable.
+ Michael Kerrisk
+ Fix SO_RECVTIMEO/ SO_SENDTIMEO confusion in text
+ Michael Kerrisk
+ Since Linux 3.8, reads on inotify(7) file descriptors are restartable
+ Michael Kerrisk
+ inotify(7) reads no longer show the odd EINTR error after SIGCONT
+ Since kernel 3.7, reads from inotify(7) file descriptors no longer
+ show the (Linux oddity) behavior of failing with EINTR when the
+ process resumes after a stop signal + SIGCONT.
+ Michael Kerrisk
+ SEE ALSO: add sigreturn(2)
+
+unix.7
+ Michael Kerrisk [Scott Harvey]
+ Fix buglet in code snippet in BUGS section
+
+ld.so.8
+ Carlos O'Donell
+ Add --inhibit-cache option
+ The dynamic loader has 6 options, only 5 are documented.
+ This patch documents the sixth option i.e. `--inhibit-cache`.
+ Jonathan Wakely [Siddhesh Poyarekar]
+ Correct documentation of $ORIGIN
+ As noted by Siddhesh:
+
+ The ld.so man page says:
+
+ $ORIGIN (or equivalently ${ORIGIN})
+ This expands to the directory containing the
+ application executable. Thus, an application located
+ in somedir/app could be compiled with
+
+ This is incorrect since it expands to the directory containing
+ the DSO and not the application executable. This seems like
+ deliberate behaviour in dl-object.c, so it needs to be fixed in
+ the man page.
+
+ See http://stackoverflow.com/questions/26280738/what-is-the-equivalent-of-loader-path-for-rpath-specification-on-linux/26281226#26281226
+
+
+
+==================== Changes in man-pages-3.77 ====================
+
+Released: 2015-01-10, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Akihiro Motoki <amotoki@gmail.com>
+Alexandre Bique <bique.alexandre@gmail.com>
+Andre Majorel <aym-xunil@teaser.fr>
+Andy Lutomirski <luto@amacapital.net>
+Daniel Borkmann <dborkman@redhat.com>
+Dave Hansen <dave.hansen@intel.com>
+Elie De Brauwer <eliedebrauwer@gmail.com>
+Heinrich Schuchardt <xypron.glpk@gmx.de>
+Ignat Loskutov <ignat.loskutov@gmail.com>
+Jeff Epler <jepler@unpythonic.net>
+Jérôme Pouiller <jezz@sysmic.org>
+Kees Cook <keescook@chromium.org>
+Laurent Georget <laurent.georget@supelec.fr>
+Masanari Iida <standby24x7@gmail.com>
+Michael Haardt <michael@moria.de>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Mike Frysinger <vapier@gentoo.org>
+Richard Cochran <richardcochran@gmail.com>
+Stephan Mueller <stephan.mueller@atsec.com>
+Troy Davis <troy@yort.com>
+Vince Weaver <vincent.weaver@maine.edu>
+Will Drewry <wad@chromium.org>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+seccomp.2
+ Kees Cook, Michael Kerrisk, Will Drewry [Andy Lutomirski]
+ New page documenting seccomp(2)
+ Combines documentation from prctl, in-kernel seccomp_filter.txt
+ and dropper.c, along with details specific to the new system call.
+
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+netlink.7
+ Stephan Mueller [Michael Kerrisk]
+ Add NETLINK_CRYPTO
+
+
+Changes to individual pages
+---------------------------
+
+adjtimex.2
+ Laurent Georget [Richard Cochran, Jeff Epler]
+ Clarify the 'ppm scaling' used in struct timex
+ This patch makes explicit and clarifies the unit used for
+ the fields "freq", "ppsfreq" and "stabil" in struct timex.
+ Michael Kerrisk [Masanari Iida]
+ Note that TIME_ERROR is the modern synonym for TIME_BAD
+
+perf_event_open.2
+ Vince Weaver
+ Clarify the PERF_FLAG_FD_* flags
+ This change clarifies the behavior of the PERF_FLAG_FD_OUTPUT and
+ PERF_FLAG_FD_NO_GROUP flags to perf_event_open(), and removes
+ the related FIXME comments.
+
+ While writing tests to validate the behavior of these flags I
+ discovered that PERF_FLAG_FD_OUTPUT has been broken since the
+ 2.6.35 kernel release.
+
+prctl.2
+ Dave Hansen [Michael Kerrisk]
+ Add description of Intel MPX calls
+ The 3.19 kernel will have support for Intel MPX, including
+ a pair of new prctl() calls (PR_MPX_ENABLE_MANAGEMENT and
+ PR_MPX_DISABLE_MANAGEMENT) for enabling and disabling the
+ kernel's management of the "bounds tables". Add a
+ descriptions of the interface.
+ Michael Kerrisk
+ Add mention of seccomp(2) under PR_SET_SECCOMP
+ Michael Kerrisk
+ Suggest /proc/PID/status "Seccomp" as alternative to PR_GET_SECCOMP
+ Michael Kerrisk
+ SIGKILL can also occur PR_GET_SECCOMP in SECCOMP_MODE_FILTER mode
+ Kees Cook [Andy Lutomirski]
+ Document SECCOMP_MODE_FILTER vs EFAULT
+ This notes the distinction made between EINVAL and EFAULT when
+ attempting to use SECCOMP_MODE_FILTER with PR_SET_SECCOMP.
+
+setns.2
+pid_namespaces.7
+ Mike Frysinger
+ Elaborate discussion of the PID namespace descendant limitation
+ The setns(2) man page already mentions that CLONE_NEWPID may only
+ be used with descendant namespaces, but this nuance could be
+ listed in a few more places so it is not missed.
+
+shmget.2
+ Michael Kerrisk [Akihiro Motoki]
+ Make wording of SHMALL description a little clearer
+
+sigaction.2
+ Michael Kerrisk
+ Add siginfo_t fields for SECCOMP_RET_TRAP
+
+memchr.3
+strstr.3
+ Alexandre Bique
+ Reference memmem(3) in SEE ALSO section
+
+memcmp.3
+ Michael Kerrisk [Michael Haardt]
+ NOTES: add some detail on avoiding memcmp() of cryptographic data
+ Wording largely based on comments from Michael Haardt.
+
+pthread_tryjoin_np.3
+ Jérôme Pouiller [Michael Kerrisk]
+ Document EINVAL error for pthread_timedjoin_np()
+
+mem.4
+ Elie De Brauwer
+ /dev/kmem depends on CONFIG_DEVKMEM
+ Elie De Brauwer
+ Correct /dev/port group in example
+ mem.4 mentions that group for /dev/port should be set to 'mem'
+ However, all other files (/dev/mem and /dev/kmem) use the kmem
+ group in their examples and on my system /dev/port belongs to
+ kmem. Hence the 'mem' group was probably a typo:
+ Elie De Brauwer
+ Add CONFIG_STRICT_DEVMEM
+ Since 2.6.26 the CONFIG_NONPROMISC_DEVMEM options limits the
+ physical addresses which can be accessed through /dev/mem.
+
+random.4
+ Heinrich Schuchardt
+ Describe handling of O_NONBLOCK
+ /dev/random and /dev/urandom treat O_NONBLOCK differently.
+ This should be described in the manpage.
+ Heinrich Schuchardt
+ Mention PRNG used by urandom
+ /dev/urandom uses a pseudo-random number generator to replace
+ missing entropy.
+
+proc.5
+ Michael Kerrisk
+ Document "Seccomp" field of /proc/PID/status
+
+epoll.7
+ Michael Kerrisk [Ignat Loskutov]
+ Use epoll_create1() rather than epoll_create() in the code example
+ epoll_create1() is more or less the preferred API for new
+ applications, since it allows for some flags and avoids the
+ misdesigned epoll_create() argument, and so it seems sensible
+ to use that in the example, rather than epoll_create().
+
+tcp.7
+ Troy Davis
+ Clarify tcp_tw_recycle on Internet-facing hosts
+ Clarify that tcp_tw_recycle will break communication with many
+ general-purpose remote Internet hosts (namely, remote NAT devices)
+ even when the Linux device itself is not behind NAT.
+
+
+==================== Changes in man-pages-3.78 ====================
+
+Released: 2015-01-22, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Akihiro Motoki <amotoki@gmail.com>
+Alexey Ishchuk <aishchuk@linux.vnet.ibm.com>
+Carlos O'Donell <carlos@redhat.com>
+Christian Seiler <christian@iwakd.de>
+Daniel J Blueman <daniel@quora.org>
+David Drysdale <drysdale@google.com>
+David Herrmann <dh.herrmann@gmail.com>
+Elie De Brauwer <eliedebrauwer@gmail.com>
+Elliot Hughes <enh@google.com>
+Jessica McKellar <jessica.mckellar@gmail.com>
+Kees Cook <keescook@chromium.org>
+Michael Hayes <mike@aiinc.ca>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Rich Felker <dalias@aerifal.cx>
+Vince Weaver <vincent.weaver@maine.edu>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+execveat.2
+ David Drysdale, Michael Kerrisk [Rich Felker]
+ New page for execveat(2)
+
+memfd_create.2
+ Michael Kerrisk, David Herrmann
+ New page for memfd_create() system call
+ Including notes about file sealing
+
+s390_pci_mmio_write.2
+ Alexey Ishchuk
+ New page for s390 s390_pci_mmio_write() and s390_pci_mmio_read()
+ New manual page for the new PCI MMIO memory access system
+ calls, s390_pci_mmio_write() and s390_pci_mmio_read(),
+ added for the s390 platform.
+
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+fcntl.2
+ David Herrmann [Michael Kerrisk]
+ Document F_ADD_SEALS and F_GET_SEALS commands
+
+proc.5
+ Elie De Brauwer
+ Document /proc/sys/vm/compact_memory
+ Michael Kerrisk
+ Document /proc/sys/fs/nr_open
+
+
+New and changed links
+---------------------
+
+s390_pci_mmio_read.2
+ Michael Kerrisk
+ New link to new s390_pci_mmio_write(2) page
+
+
+Changes to individual pages
+---------------------------
+
+dup.2
+ Michael Kerrisk
+ Add reference to RLIMIT_NOFILE for EMFILE error
+ Michael Kerrisk
+ Add reference to RLIMIT_NOFILE for EBADF error on 'newfd'.
+
+execve.2
+fexecve.3
+ Michael Kerrisk
+ SEE ALSO: add execveat(2)
+
+fallocate.2
+mmap.2
+open.2
+truncate.2
+write.2
+ Michael Kerrisk
+ ERRORS: add EPERM for operation denied by file seal
+
+fcntl.2
+ Michael Kerrisk
+ ERRORS: add EBUSY case for F_SETPIPE_SZ
+ Michael Kerrisk
+ Add reference to RLIMIT_NOFILE for F_DUPFD EINVAL error on 'arg'.
+ Michael Kerrisk
+ ERRORS: add open file description lock error cases
+
+getrlimit.2
+ Michael Kerrisk
+ Update text on RLIMIT_NOFILE ceiling to refer to /proc/sys/fs/file-max
+
+mbind.2
+ Michael Kerrisk [Daniel J Blueman]
+ Clarify EFAULT text
+
+mmap.2
+shmget.2
+shm_open.3
+ Michael Kerrisk
+ SEE ALSO: add memfd_create(2)
+
+open.2
+ Michael Kerrisk
+ Refer to RLIMIT_NOFILE for explanation of EMFILE error
+ Michael Kerrisk
+ Add execveat(2) in system call list under "Rationale for openat()"
+
+perf_event_open.2
+ Vince Weaver
+ Clarify description of overflow events
+ Update the perf_event_open manpage to be more consistent when
+ discussing overflow events. It merges the discussion of
+ poll-type notifications with those generated by SIGIO
+ signal handlers.
+ This addresses the remaining FIXMEs is the document.
+ Vince Weaver
+ Remove inaccurate paragraph describing attr.config
+ Remove an inaccurate paragraph about values in the attr.config
+ field. This information was never true in any released kernel;
+ it somehow snuck into the manpage because it is still described
+ this way in tools/perf/design.txt in the kernel source tree.
+ Michael Kerrisk
+ Correct the kernel version number for PERF_COUNT_HW_CACHE_NODE
+ Michael Kerrisk
+ Add some kernel version numbers to various fields and constants
+
+ptrace.2
+sigaction.2
+seccomp.2
+ Kees Cook
+ Ptrace and siginfo details
+ While writing some additional seccomp tests, I realized
+ PTRACE_EVENT_SECCOMP wasn't documented yet. Fixed this, and added
+ additional notes related to ptrace events SIGTRAP details.
+
+readv.2
+ Michael Kerrisk
+ Update details on glibc readv()/writev() wrapper behavior
+ And add a historical detail about Linux 2.0.
+
+select.2
+ Michael Kerrisk
+ Mention RLIMIT_NOFILE as a possible cause of EINVAL error
+
+syscall.2
+ Kees Cook
+ Add arm64 and mips
+ Add mips and arm64 to tables, along with some further
+ details on these architectures,
+
+syscalls.2
+ Michael Kerrisk
+ Add s390_pci_mmio_read(2) and s390_pci_mmio_write(2)
+ Michael Kerrisk
+ Note kernel() version that introduced get_kernel_syms()
+ Note kernel version that introduced ppc_rtas()
+ Note kernel version that introduced create_module()
+ Note kernel version that added setup()
+ Michael Kerrisk
+ Remove some details for sync_file_range2()
+ Make the table a bit simpler. The details can anyway be
+ found in the system call man page.
+
+utimensat.2
+ Michael Kerrisk [Elliot Hughes]
+ If both tv_sec fields are UTIME_OMIT, the file need not exist
+ As noted by Elliot, if both tv_sec fields are UTIME_OMIT,
+ utimensat() will return success even if the file does not exist.
+
+errno.3
+ Michael Kerrisk
+ The RLIMIT_NOFILE resource limit is a common cause of EMFILE
+
+exec.3
+ Michael Kerrisk
+ SEE ALSO: add execveat(2)
+
+fclose.3
+ Carlos O'Donell
+ Consistency fix: use "stream" as name for "FILE *" argument
+ Harmonize all the manual pages to use "stream" for FILE*
+ instead of randomly using "fp" or "stream." Choosing something
+ and being consistent helps users scan the man pages quickly
+ and understand what they are looking at.
+
+fexecve.3
+ Michael Kerrisk
+ Rewrite the script+close-on-exec problem as a BUG
+ Also, add one or two details about this scenario.
+ Michael Kerrisk
+ The natural idiom when using fexecve() is to use the close-on-exec flag
+
+fmemopen.3
+ Michael Kerrisk
+ Consistency fix: use "stream" as name for "FILE *" argument
+
+fopencookie.3
+ Michael Kerrisk
+ Consistency fix: use "stream" as name for "FILE *" argument
+
+getgrent_r.3
+ Carlos O'Donell
+ Consistency fix: use "stream" as name for "FILE *" argument
+
+getline.3
+ Michael Kerrisk
+ Consistency fix: use "stream" as name for "FILE *" argument
+
+getmntent.3
+ Carlos O'Donell
+ Consistency fix: use "stream" as name for "FILE *" argument
+
+getpw.3
+ Michael Kerrisk [Carlos O'Donell]
+ Describe return value when 'uid' is not found
+
+getpwent_r.3
+ Carlos O'Donell
+ Consistency fix: use "stream" as name for "FILE *" argument
+
+getspnam.3
+ Carlos O'Donell
+ Consistency fix: use "stream" as name for "FILE *" argument
+
+malloc_info.3
+ Carlos O'Donell
+ Consistency fix: use "stream" as name for "FILE *" argument
+
+posix_fallocate.3
+ Michael Kerrisk
+ Note that posix_fallocate() is implemented using fallocate(2)
+
+putgrent.3
+ Carlos O'Donell
+ Consistency fix: use "stream" as name for "FILE *" argument
+ Harmonize all the manual pages to use "stream" for FILE*
+ instead of randomly using "fp" or "stream." Choosing something
+ and being consistent helps users scan the man pages quickly
+ and understand what they are looking at.
+
+locale.5
+ Akihiro Motoki
+ Correct variable name
+
+proc.5
+ Michael Kerrisk
+ Remove bogus statement about NR_OPEN being a ceiling for file-max
+
+
+==================== Changes in man-pages-3.79 ====================
+
+Released: 2015-02-01, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Akihiro Motoki <amotoki@gmail.com>
+Heinrich Schuchardt <xypron.glpk@gmx.de>
+J William Piggott <elseifthen@gmx.com>
+Masanari Iida <standby24x7@gmail.com>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Scot Doyle <lkml14@scotdoyle.com>
+Sergey V. Zubkov <cubbi@cubbi.com>
+Stephan Mueller <stephan.mueller@atsec.com>
+Vince Weaver <vincent.weaver@maine.edu>
+Vivek Goyal <vgoyal@redhat.com>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+getrandom.2
+ Heinrich Schuchardt, Theodore T'so, Michael Kerrisk
+ New page documenting getrandom(2)
+ Kernel 3.17 introduces a new system call getrandom(2).
+
+kexec_load.2
+ Vivek Goyal, Michael Kerrisk
+ Add documentation of kexec_file_load(2)
+ Michael Kerrisk, Vivek Goyal
+ Rewrite and extend documentation of kexec_load().
+
+
+New and changed links
+---------------------
+
+kexec_file_load.2
+ Michael Kerrisk
+ New link to kexec_load.2
+
+Changes to individual pages
+---------------------------
+
+personality.2
+ Michael Kerrisk
+ SEE ALSO: add setarch(8)
+
+prctl.2
+ Michael Kerrisk
+ Unused arguments of PR_MPX_(EN,DIS}ABLE_MANAGEMENT must be zero
+
+reboot.2
+ Michael Kerrisk
+ SEE ALSO: add kexec_load(2)
+
+socket.2
+ Stephan Mueller
+ document AF_ALG
+ Add a reference to the AF_ALG protocol accessible via socket(2).
+
+fflush.3
+ Michael Kerrisk [Sergey V. Zubkov]
+ Clarify that flushing of input streams occurs only for seekable files
+ See https://bugzilla.kernel.org/show_bug.cgi?id=91931
+ Michael Kerrisk [Sergey V. Zubkov]
+ POSIX.1-2008 specifies the behavior when flushing input streams
+ POSIX.1-2001 did not have a specification for input streams,
+ but POSIX.1-2008 added one.
+
+getopt.3
+ Michael Kerrisk
+ SEE ALSO: add getopt(1)
+
+random.3
+ Heinrich Schuchardt
+ SEE ALSO: add getrandom(2)
+
+termios.3
+ Michael Kerrisk
+ SEE ALSO: add reset(1), setterm(1), tput(1)
+
+tzset.3
+ J William Piggott
+ Document behavior when TZ filespec omits the colon
+ If the TZ filespec omits the leading colon, glibc will parse
+ it for any valid format, i.e., it will still work.
+ J William Piggott
+ Add description for posixrules file
+ J William Piggott
+ Correct system timezone file path
+ J William Piggott
+ There are only two TZ formats
+ tzset(3) currently states that there are three TZ formats. The
+ first two it lists are actually variations of the POSIX-style
+ TZ format, of which there are at least five variations.
+
+ This patch corrects this to match the POSIX specification of
+ TZ having only two formats.
+ J William Piggott
+ Filespec omitted incorrect
+ Paragraph three of the DESCRIPTION section says
+ that when TZ is set, but empty, then UTC is used.
+
+ Later it says if the TZ filespec is omitted then the file
+ /usr/share/zoneinfo/localtime is used. This is incorrect,
+ it will use UTC in that case as well.
+ J William Piggott
+ Fix incorrect TZ string representation
+ The TZ string representation indicates that the start/end
+ rules are required; this is incorrect.
+ J William Piggott
+ Add ENVIRONMENT section + other rearrangements
+ FILES section was overly verbose and included
+ environment variables. Added ENVIRONMENT section,
+ removing ENV VARS from the FILES section.
+
+random.4
+ Heinrich Schuchardt
+ SEE ALSO: add getrandom(2)
+
+passwd.5
+ Michael Kerrisk
+ SEE ALSO: add chfn(1), chsh(1)
+
+capabilities.7
+ Michael Kerrisk
+ SEE ALSO: add setpriv(1)
+
+signal.7
+ Michael Kerrisk
+ Add getrandom(2) to list of restartable system calls
+ Michael Kerrisk
+ Add F_OFD_SETLKW to list of restartable operations
+
+
+
+==================== Changes in man-pages-3.80 ====================
+
+Released: 2015-02-21, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Akihiro Motoki <amotoki@gmail.com>
+Andy Lutomirski <luto@amacapital.net>
+Bill McConnaughey <mcconnau@biochem.wustl.edu>
+Chris Mayo <aklhfex@gmail.com>
+Christophe Blaess <Christophe@blaess.fr>
+David Wilson <dw@botanicus.net>
+Denys Vlasenko <dvlasenk@redhat.com>
+Doug Goldstein <cardoe@gentoo.org>
+Eric Wong <normalperson@yhbt.net>
+Heinrich Schuchardt <xypron.glpk@gmx.de>
+J William Piggott <elseifthen@gmx.com>
+James Hunt <james.hunt@ubuntu.com>
+Jan Chaloupka <jchaloup@redhat.com>
+Jan Stancek <jstancek@redhat.com>
+Jeff Layton <jlayton@poochiereds.net>
+Jens Thoms Toerring <jt@toerring.de>
+Kevin Easton <kevin@guarana.org>
+Luke Faraone <lfaraone@debian.org>
+Mark Seaborn <mseaborn@chromium.org>
+Mathieu Malaterre <malat@debian.org>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Michal Hocko <mhocko@suse.cz>
+Minchan Kim <minchan@kernel.org>
+Patrick Horgan <phorgan1@gmail.com>
+Peng Haitao <penght@cn.fujitsu.com>
+Ralf Baechle <ralf@linux-mips.org>
+Rob Somers <uberkermit@gmail.com>
+Simon Paillard <spaillard@debian.org>
+Stephen Smalley <sds@tycho.nsa.gov>
+Tao Ma <tao.ma@oracle.com>
+Tobias Herzke <tobias.linuxpatches.2014@gi2.herzkes.de>
+Vince Weaver <vincent.weaver@maine.edu>
+Vlastimil Babka <vbabka@suse.cz>
+Zbigniew Brzeziński <zbigniew.brzezinski@student.put.poznan.pl>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+ioctl_fat.2
+ Heinrich Schuchardt [Michael Kerrisk]
+ New man page for the ioctl(2) FAT API
+ The ioctl(2) system call may be used to retrieve information about
+ the FAT file system and to set file attributes.
+
+madvise.2
+ Michael Kerrisk
+ Summary: this page has been significantly reorganised and rewritten
+ Michael Kerrisk
+ Recast discussion of 'advice' into two groups of values
+ madvise() is one of those system calls that has congealed over
+ time, as has the man page. It's helpful to split the discussion
+ of 'advice' into those flags into two groups:
+
+ * Those flags that are (1) widespread across implementations;
+ (2) have counterparts in posix_madvise(3); and (3) were present
+ in the initial Linux madvise implementation.
+ * The rest, which are values that (1) may not have counterparts
+ in other implementations; (2) have no counterparts in
+ posix_madvise(3); and (3) were added to Linux in more recent
+ times.
+ Michael Kerrisk
+ Explicitly list the five flags provided by posix_fadvise()
+ Over time, bit rot has afflicted this page. Since the original
+ text was written many new Linux-specific flags have been added.
+ So, now it's better to explicitly list the flags that
+ correspond to the POSIX analog of madvise().
+ Jan Chaloupka [Hugh Dickins, Michael Kerrisk]
+ Starting with Linux 3.5, more file systems support MADV_REMOVE
+ Michael Kerrisk
+ Split EINVAL error into separate cases
+ Michael Kerrisk
+ Explain MADV_REMOVE in terms of file hole punching
+ Michael Kerrisk
+ MADV_REMOVE can be applied only to shared writable mappings
+ Michael Kerrisk
+ MADV_REMOVE cannot be applied to locked or Huge TLB pages
+ Michael Kerrisk [Vlastimil Babka]
+ Clarify that MADV_DONTNEED has effect on pages only if it succeeds
+ Michael Kerrisk [Vlastimil Babka]
+ Clarifications for MADV_DONTNEED
+ Michael Kerrisk [Michal Hocko]
+ Improve MADV_DONTNEED description
+ Michael Kerrisk
+ MADV_DONTNEED cannot be applied to Huge TLB or locked pages
+ Michael Kerrisk [Vlastimil Babka]
+ Remove mention of "shared pages" as a cause of EINVAL for MADV_DONTNEED
+ Michael Kerrisk [Vlastimil Babka]
+ Note Huge TLB as a cause of EINVAL for MADV_DONTNEED
+ Michael Kerrisk [Minchan Kim]
+ Add mention of VM_PFNMAP in discussion of MADV_DONTNEED and MADV_REMOVE
+ Michael Kerrisk
+ Drop sentence saying that kernel may ignore 'advice'
+ The sentence creates misunderstandings, and does not really
+ add information.
+ Michael Kerrisk
+ Note that some Linux-specific 'advice' change memory-access semantics
+ Michael Kerrisk
+ NOTES: Remove crufty text about "command" versus "advice"
+ The point made in this fairly ancient text is more or less evident
+ from the DESCRIPTION, and it's not clear what "standard" is being
+ referred to.
+ Michael Kerrisk
+ Mention POSIX.1-2008 addition of POSIX_MADV_NOREUSE
+ Michael Kerrisk
+ Remove "POSIX.1b" from CONFORMING TO
+ Michael Kerrisk
+ Move mention of posix_fadvise() from CONFORMING TO to SEE ALSO
+ Michael Kerrisk
+ ERRORS: add EPERM error case for MADV_HWPOISON
+ Michael Kerrisk
+ Note that madvise() is nonstandard, but widespread
+
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+proc.5
+ Michael Kerrisk
+ (Briefly) document /proc/PID/attr/socketcreate
+ Michael Kerrisk
+ (Briefly) document /proc/PID/attr/keycreate
+ Michael Kerrisk [Stephen Smalley]
+ Document /proc/PID/attr/{current,exec,fscreate,prev}
+ Heavily based on Stephen Smalley's text in
+ https://lwn.net/Articles/28222/
+ From: Stephen Smalley <sds@epoch.ncsc.mil>
+ To: LKML and others
+ Subject: [RFC][PATCH] Process Attribute API for Security Modules
+ Date: 08 Apr 2003 16:17:52 -0400
+ Michael Kerrisk
+ Document /proc/sys/kernel/auto_msgmni
+
+socket.7
+ David Wilson [Michael Kerrisk]
+ Document SO_REUSEPORT socket option
+
+
+New and changed links
+---------------------
+
+get_thread_area.2
+ Andy Lutomirski
+ Make get_thread_area.2 a link to rewritten set_thread_area.2 page
+
+
+Changes to individual pages
+---------------------------
+
+time.1
+ Michael Kerrisk
+ Make option argument formatting consistent with other pages
+
+access.2
+ Denys Vlasenko
+ Explain how access() check treats capabilities
+ We have users who are terribly confused why their binaries
+ with CAP_DAC_OVERRIDE capability see EACCESS from access() calls,
+ but are able to read the file.
+
+ The reason is access() isn't the "can I read/write/execute this
+ file?" question, it is the "(assuming that I'm a setuid binary,)
+ can *the user who invoked me* read/write/execute this file?"
+ question.
+
+ That's why it uses real UIDs as documented, and why it ignores
+ capabilities when capability-endorsed binaries are run by non-root
+ (this patch adds this information).
+
+ To make users more likely to notice this less-known detail,
+ the patch expands the explanation with rationale for this logic
+ into a separate paragraph.
+
+arch_prctl.2
+set_thread_area.2
+get_thread_area.2
+ Andy Lutomirski
+ Improve TLS documentation
+ The documentation for set_thread_area was very vague. This
+ improves it, accounts for recent kernel changes, and merges
+ it with get_thread_area.2.
+
+ get_thread_area.2 now becomes a link.
+
+ While I'm at it, clarify the related arch_prctl.2 man page.
+
+cacheflush.2
+ Ralf Baechle
+ Update some portability details and bugs
+ Michael Kerrisk
+ Refer reader to BUGS in discussion of EINVAL error
+
+capget.2
+ Michael Kerrisk
+ Document V3 capabilities constants
+ Michael Kerrisk
+ Rewrite discussion of kernel versions that support file capabilities
+ File capabilities ceased to be optional in Linux 2.6.33.
+
+clone.2
+ Peng Haitao
+ Fix description of CLONE_PARENT_SETTID
+ CLONE_PARENT_SETTID only stores child thread ID in parent memory.
+
+clone.2
+execve.2
+ Kevin Easton
+ Document interaction of execve(2) with CLONE_FILES
+ This patch the fact that a successful execve(2) in a process that
+ is sharing a file descriptor table results in unsharing the table.
+
+ I discovered this through testing and verified it by source
+ inspection - there is a call to unshare_files() early in
+ do_execve_common().
+
+fcntl.2
+ Michael Kerrisk [Jeff Layton]
+ Clarify cases of conflict between traditional record and OFD locks
+ Verified by experiment on Linux 3.15 and 3.19rc4.
+
+fork.2
+ Michal Hocko
+ EAGAIN is not reported when task allocation fails
+ I am not sure why we have:
+
+ "EAGAIN fork() cannot allocate sufficient memory to copy
+ the parent's page tables and allocate a task structure
+ or the child."
+
+ The text seems to be there from the time when man-pages
+ were moved to git so there is no history for it.
+
+ And it doesn't reflect reality: the kernel reports both
+ dup_task_struct and dup_mm failures as ENOMEM to the
+ userspace. This seems to be the case from early 2.x times
+ so let's simply remove this part.
+ Heinrich Schuchardt
+ Child and parent run in separate memory spaces
+ fork.2 should clearly point out that child and parent
+ process run in separate memory spaces.
+ Michael Kerrisk
+ NOTES: add "C library/kernel ABI differences" subheading
+
+getpid.2
+ Michael Kerrisk
+ NOTES: add "C library/kernel ABI differences" subheading
+
+getxattr.2
+ Michael Kerrisk
+ Various rewordings plus one or two details clarified
+ Michael Kerrisk
+ Add pointer to example in listxattr(2)
+
+killpg.2
+ Michael Kerrisk
+ NOTES: add "C library/kernel ABI differences" subheading
+
+listxattr.2
+ Heinrich Schuchardt
+ Provide example program
+ Michael Kerrisk
+ Reword discussion of size==0 case
+ Michael Kerrisk
+ Add note on handling increases in sizes of keys or values
+ Michael Kerrisk
+ Remove mention of which filesystems implement ACLs
+ Such a list will only become outdated (as it already was).
+
+migrate_pages.2
+ Jan Stancek
+ Document EFAULT and EINVAL errors
+ I encountered these errors while writing testcase for migrate_pages
+ syscall for LTP (Linux test project).
+
+ I checked stable kernel tree 3.5 to see which paths return these.
+ Both can be returned from get_nodes(), which is called from:
+ SYSCALL_DEFINE4(migrate_pages, pid_t, pid, unsigned long, maxnode,
+ const unsigned long __user *, old_nodes,
+ const unsigned long __user *, new_nodes)
+
+ The testcase does following:
+ EFAULT
+ a) old_nodes/new_nodes is area mmaped with PROT_NONE
+ b) old_nodes/new_nodes is area not mmapped in process address
+ space, -1 or area that has been just munmmaped
+
+ EINVAL
+ a) maxnodes overflows kernel limit
+ b) new_nodes contain node, which has no memory or does not exist
+ or is not returned for get_mempolicy(MPOL_F_MEMS_ALLOWED).
+
+modify_ldt.2
+ Andy Lutomirski
+ Overhaul the documentation
+ This clarifies the behavior and documents all four functions.
+ Andy Lutomirski
+ Clarify the lm bit's behavior
+ The lm bit should never have existed in the first place. Sigh.
+
+mprotect.2
+ Mark Seaborn
+ Mention effect of READ_IMPLIES_EXEC personality flag
+ I puzzled over mprotect()'s effect on /proc/*/maps for a while
+ yesterday -- it was setting "x" without PROT_EXEC being specified.
+ Here is a patch to add some explanation.
+
+msgget.2
+ Michael Kerrisk
+ Add details of MSGMNI default value
+
+msgop.2
+ Michael Kerrisk
+ Clarify wording of MSGMAX and MSGMNB limits
+
+perf_event_open.2
+ Vince Weaver
+ Clarify PERF_EVENT_IOC_REFRESH behavior
+ Currently the PERF_EVENT_IOC_REFRESH ioctl, when applied to a group
+ leader, will refresh all children. Also if a refresh value of 0
+ is chosen then the refresh becomes infinite (never runs out).
+ Back in 2011 PAPI was relying on these behaviors but I was told
+ that both were unsupported and subject to being removed at any time.
+ (See https://lkml.org/lkml/2011/5/24/337 )
+ However the behavior has not been changed.
+
+ This patch updates the manpage to still list the behavior as
+ unsupported, but removes the inaccurate description of it
+ only being a problem with 2.6 kernels.
+
+prctl.2
+ Michael Kerrisk [Bill McConnaughey]
+ Mention file capabilities in discussion of PR_SET_DUMPABLE
+ Michael Kerrisk
+ Greatly expand discussion of "dumpable" flag
+ In particular, detail the interactions with
+ /proc/sys/fs/suid_dumpable.
+ Michael Kerrisk
+ Reorder paragraphs describing PR_SET_DUMPABLE
+ Michael Kerrisk
+ Mention SUID_DUMP_DISABLE and SUID_DUMP_USER under PR_SET_DUMPABLE
+ Michael Kerrisk
+ Executing a file with capabilities also resets the parent death signal
+
+ptrace.2
+ James Hunt
+ Explain behaviour should ptrace tracer call execve(2)
+ This behaviour was verified by reading the kernel source and
+ confirming the behaviour using a test program.
+ Denys Vlasenko
+ Add information on PTRACE_SEIZE versus PTRACE_ATTACH differences
+ Extend description of PTRACE_SEIZE with the short summary of its
+ differences from PTRACE_ATTACH.
+
+ The following paragraph:
+
+ PTRACE_EVENT_STOP
+ Stop induced by PTRACE_INTERRUPT command, or group-stop, or ini-
+ tial ptrace-stop when a new child is attached (only if attached
+ using PTRACE_SEIZE), or PTRACE_EVENT_STOP if PTRACE_SEIZE was used.
+
+ has an editing error (the part after last comma makes no sense).
+ Removing it.
+
+ Mention that legacy post-execve SIGTRAP is disabled by PTRACE_SEIZE.
+
+sched_setattr.2
+ Michael Kerrisk [Christophe Blaess]
+ SYNOPSIS: remove 'const' from 'attr' sched_getattr() argument
+
+semget.2
+ Michael Kerrisk
+ Note default value for SEMMNI and SEMMSL
+
+semop.2
+ Michael Kerrisk
+ Note defaults for SEMOPM and warn against increasing > 1000
+
+sendfile.2
+ Eric Wong
+ Caution against modifying sent pages
+
+setxattr.2
+ Michael Kerrisk
+ ERRORS: add ENOTSUP for invalid namespace prefix
+ Michael Kerrisk
+ Remove redundant text under ENOTSUP error
+ Michael Kerrisk
+ Note that zero-length attribute values are permitted
+ Michael Kerrisk
+ Rework text describing 'flags' argument
+
+stat.2
+ Michael Kerrisk
+ NOTES: add "C library/kernel ABI differences" subheading
+
+statfs.2
+ Michael Kerrisk [Jan Chaloupka]
+ Document the 'f_flags' field added in Linux 2.6.36
+ Michael Kerrisk
+ Clarify that 'statfs' structure has some padding bytes
+ The number of padding bytes has changed over tyme, as some
+ bytes are used, so describe this aspect of the structure
+ less explicitly.
+ Tao Ma
+ Add OCFS2_SUPER_MAGIC
+ Michael Kerrisk
+ Use __fsword_t in statfs structure definition
+ This more closely matches modern glibc reality.
+ Michael Kerrisk
+ Add a note on the __fsword_t type
+ Michael Kerrisk
+ Document 'f_spare' more vaguely
+
+wait.2
+ Michael Kerrisk
+ Note that waitpid() is a wrapper for wait4()
+ Michael Kerrisk
+ Note that wait() is a library function implemented via wait4()
+
+wait4.2
+ Michael Kerrisk
+ NOTES: add "C library/kernel ABI differences" subheading
+
+encrypt.3
+ Rob Somers
+ Improve code example
+ I (and some others) found that the original example code
+ did not seem to work as advertised. The new code (used by
+ permission of the original author, Jens Thoms Toerring)
+ was found on comp.os.linux.development.
+
+mktemp.3
+ Luke Faraone
+ DESCRIPTION reference to BUGS corrected
+ mktemp(3)'s DESCRIPTION referenced NOTES, but no such
+ section exists. Corrected to refer to BUGS.
+
+pthread_attr_setschedparam.3
+ Tobias Herzke
+ Describe EINVAL in ERRORS
+
+resolver.3
+host.conf.5
+ Simon Paillard
+ host.conf 'order' option deprecated, replaced by nsswitch.conf(5)
+ http://www.sourceware.org/bugzilla/show_bug.cgi?id=2389
+ http://repo.or.cz/w/glibc.git/commit/b9c65d0902e5890c4f025b574725154032f8120a
+
+ Reported at http://bugs.debian.org/270368,
+ http://bugs.debian.org/396633, and http://bugs.debian.org/344233.
+
+statvfs.3
+ Michael Kerrisk
+ Document missing 'f_flag' bit values
+ And reorganize information relating to which flags are in
+ POSIX.1.
+ Michael Kerrisk [Jan Chaloupka]
+ statvfs() now populates 'f_flag' from statfs()'s f_flag field
+ These changes came with glibc 2.13, and the kernel's addition of
+ a 'f_flags' field in Linux 2.6.36.
+
+syslog.3
+ Michael Kerrisk [Doug Goldstein]
+ Remove unneeded <stdarg.h>
+ vsyslog() does not need this.
+
+tzset.3
+ J William Piggott
+ Add offset format
+ tzset.3 does not illustrate the POSIX offset format.
+ Specifically, there is no indication in the manual
+ what the optional components of it are.
+
+random.4
+ Michael Kerrisk
+ Note maximum number of bytes returned by read(2) on /dev/random
+ Michael Kerrisk [Mathieu Malaterre]
+ Since Linux 3.16, reads from /dev/urandom return at most 32 MB
+ See https://bugs.debian.org/775328 and
+ https://bugzilla.kernel.org/show_bug.cgi?id=80981#c9
+
+core.5
+ Michael Kerrisk [Bill McConnaughey]
+ Executing a file that has capabilities also prevents core dumps
+ Michael Kerrisk
+ Document "%i" and "%I" core_pattern specifiers
+
+intro.5
+ Michael Kerrisk
+ Remove words "and protocols"
+ There are no protocol descriptions in Section 5. Protocols are
+ in Section 7.
+
+proc.5
+ Michael Kerrisk
+ Add reference to prctl(2) in discussion of /proc/sys/fs/suid_dumpable
+ And note that /proc/sys/fs/suid_dumpable defines the
+ value assigned to the process "dumpable" flag in certain
+ circumstances.
+ Michael Kerrisk
+ Note that CAP_SYS_ADMIN is required to list /proc/PID/map_files
+ This might however change in the future; see the Jan 2015 LKML thread:
+
+ Re: [RFC][PATCH v2] procfs: Always expose /proc/<pid>/map_files/
+ and make it readable
+
+resolv.conf.5
+ Michael Kerrisk
+ SEE ALSO: add nsswitch.conf(5)
+
+capabilities.7
+ Michael Kerrisk
+ Mention SECBIT_KEEP_CAPS as an alternative to prctl() PR_SET_KEEPCAPS
+ Chris Mayo
+ NOTES: add last kernel versions for obsolete options
+ The CONFIG_SECURITY_CAPABILITIES option was removed by
+ commit 5915eb53861c5776cfec33ca4fcc1fd20d66dd27
+
+ The CONFIG_SECURITY_FILE_CAPABILITIES option removed in
+ Linux 2.6.33 as already mentioned in DESCRIPTION.
+
+pthreads.7
+ Michael Kerrisk
+ SEE ALSO: add fork(2)
+
+unix.7
+ Jan Chaloupka
+ Mention SOCK_STREAM socket for ioctl_type of ioctl()
+ from https://bugzilla.redhat.com/show_bug.cgi?id=1110401.
+
+ unix.7 is not clear about socket type of ioctl_type argument of
+ ioctl() function. The description of SIOCINQ is applicable only
+ for SOCK_STREAM socket. For SOCK_DGRAM, udp(7) man page gives
+ correct description of SIOCINQ
+
+ldconfig.8
+ Michael Kerrisk
+ Place options in alphabetical order
+ Michael Kerrisk
+ Note glibc version number for '-l' option
+ Michael Kerrisk
+ Document -c/--format option
+ Michael Kerrisk
+ Add long form of some options
+ Michael Kerrisk [Patrick Horgan]
+ ld.so.conf uses only newlines as delimiters
+ mtk: confirmed by reading source of parse_conf() in
+ elf/ldconfig.c.
+ Michael Kerrisk
+ Document -V/--version option
+ Michael Kerrisk
+ Document -i/--ignore-aux-cache option
+
+ld.so.8
+ Michael Kerrisk
+ Relocate "Hardware capabilities" to be a subsection under notes
+ This is more consistent with standard man-pages headings
+ and layout.
+ Michael Kerrisk
+ (Briefly) document LD_TRACE_PRELINKING
+ Michael Kerrisk
+ Remove duplicate description of LD_BIND_NOT
+
+
+==================== Changes in man-pages-3.81 ====================
+
+Released: 2015-03-02, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Alexandre Oliva <aoliva@redhat.com>
+Carlos O'Donell <carlos@redhat.com>
+Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Peng Haitao <penght@cn.fujitsu.com>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+attributes.7
+ Alexandre Oliva, Michael Kerrisk [Carlos O'Donell]
+ New page describing POSIX safety concepts
+
+
+Global changes
+--------------
+
+Many pages
+ Peng Haitao, Michael Kerrisk
+ Reformat existing thread-safety information to use a
+ tabular format, rather than plain text.
+
+
+Changes to individual pages
+---------------------------
+
+mmap.2
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function mmap() and munmap() are thread safe.
+
+a64l.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+acos.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function acos(), acosf() and acosl() are thread safe.
+
+acosh.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function acosh(), acoshf() and acoshl() are thread safe.
+
+addseverity.3
+ Ma Shimiao
+ ATTRIBUTES: Note function is thread-safe
+ The function addseverity() is thread safe.
+
+aio_cancel.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The function aio_cancel() is thread safe.
+
+aio_fsync.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The function aio_fsync() is thread safe.
+
+aio_read.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The function aio_read() is thread safe.
+
+aio_suspend.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The function aio_suspend() is thread safe.
+
+aio_write.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The function aio_write() is thread safe.
+
+argz_add.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+
+asin.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function asin(), asinf() and asinl() are thread safe.
+
+assert.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ Its marking matches glibc marking.
+
+assert_perror.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ Its marking matches glibc marking.
+
+atan2.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function atan2(), atan2f() and atan2l() are thread safe.
+
+atanh.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function atanh(), atanhf() and atanhl() are thread safe.
+
+backtrace.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The markings match glibc markings.
+
+btowc.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The function btowc() in glibc is thread safe.
+ Its marking matches glibc marking.
+
+cabs.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function cabs(), cabsf() and cabsl() are thread safe.
+
+cacos.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function cacos(), cacosf() and cacosl() are thread safe.
+
+cacosh.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions cacosh(), cacoshf() and cacoshl() in glibc are
+ thread safe. Its markings match glibc markings.
+
+canonicalize_file_name.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The functions canonicalize_file_name() in glibc is thread safe.
+ Its marking matches glibc marking.
+
+carg.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function carg(), cargf() and cargl() are thread safe.
+
+casin.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions casin(), casinf() and casinl() are thread safe.
+ Their markings match glibc markings.
+
+casinh.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions casinh(), casinhf() and casinhl() in glibc are
+ thread safe. Its markings match glibc markings.
+
+catan.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions catan(), catanf() and catanl() are thread safe.
+ Their markings match glibc markings.
+
+catanh.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions catanh(), catanhf() and catanhl() in glibc are
+ thread safe. Its markings match glibc markings.
+
+catopen.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions catopen() and catclose() are thread safe.
+
+cfree.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The function cfree() in glibc is thread safe.
+ Its marking matches glibc marking.
+
+clog10.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions clog10(), clog10f() and clog10l() in glibc are
+ thread safe. Its markings match glibc markings.
+
+clog.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function clog(), clogf() and clogl() are thread safe.
+
+closedir.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The function closedir() in glibc is thread safe.
+ Its marking matches glibc marking.
+
+confstr.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The function confstr() is thread safe.
+
+cosh.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions cosh(), coshf() and coshl() in glibc are thread safe.
+ Its markings match glibc markings.
+
+cpow.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions cpow(), cpowf() and cpowl() in glibc are thread safe.
+ Its markings match glibc markings.
+
+crypt.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+ctermid.3
+ Ma Shimiao
+ Modify thread-safety information
+ According to the change of source code, ctermid's level has been
+ changed from MT-Unsafe to MT-Safe. After modifying, the marking
+ matches the glibc marking.
+
+drand48.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+drand48_r.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+ecvt.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be same as glibc manual.
+
+ecvt_r.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The markings match glibc markings.
+
+encrypt.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+envz_add.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The markings match glibc markings.
+
+exec.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions execl(), execlp(), execle(), execv(), execvp() and
+ execvpe() are thread safe.
+
+exit.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+exp10.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+
+exp2.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function exp2(), exp2f() and exp2l() are thread safe.
+
+exp.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function exp(), expf() and expl() are thread safe.
+
+fclose.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The function fclose() is thread safe.
+ Its marking matches glibc marking.
+
+fcloseall.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+fgetc.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The markings match glibc markings.
+
+fgetwc.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The markings match glibc markings.
+
+fgetws.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The marking matches glibc marking.
+
+fmod.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function fmod(), fmodf() and fmodl() are thread safe.
+
+fnmatch.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function fnmatch() is thread safe with exceptions.
+
+fopen.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The markings match glibc markings.
+
+fopencookie.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The marking matches glibc marking.
+
+fread.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions fread() and fwrite() are thread safe.
+
+gamma.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are not thread-safe
+ The functions gamma(), gammaf() and gammal() are not thread safe.
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+getcontext.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+getcwd.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions getcwd(), getwd() and get_current_dir_name() are
+ thread safe.
+
+getdate.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+getenv.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions getenv() and secure_getenv() are thread safe.
+
+getfsent.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are not thread-safe
+ The functions setfsent(), getfsent(), endfsent(), getfsspec()
+ and getfsfile() are not thread safe.
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+getgrent.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ Its marking matches glibc marking.
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+getgrnam.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+getgrouplist.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function getgrouplist() is thread safe with exceptions.
+
+getlogin.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+getopt.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are not thread-safe
+ The functions getopt(), getopt_long() and getopt_long_only() are
+ not thread safe.
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+getpass.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+getpwent.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+getpwnam.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+gets.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ Its marking matches glibc marking.
+
+getw.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions getw() and putw() are thread safe.
+
+gnu_get_libc_version.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions gnu_get_libc_version() and gnu_get_libc_release()
+ are thread safe.
+
+hsearch.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+iconv.3
+ Peng Haitao
+ Modify thread-safety information
+
+inet.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread safe with exceptions
+ The functions inet_aton() and inet_addr() are thread safe with
+ exceptions.
+ The functions inet_network(), inet_ntoa(), inet_makeaddr(),
+ inet_lnaof() and inet_netof() are thread safe.
+ Modify thread-safety information
+ After researching and talking, we think inet_network() and
+ inet_ntoa() should be marked with locale.
+ After changing, the markings match glbc markings.
+
+inet_pton.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function inet_pton() is thread safe with exceptions.
+
+iswdigit.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function iswdigit() is thread safe with exceptions.
+
+iswgraph.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function iswgraph() is thread safe with exceptions.
+
+iswlower.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function iswlower() is thread safe with exceptions.
+
+iswprint.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function iswprint() is thread safe with exceptions.
+
+iswpunct.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function iswpunct() is thread safe with exceptions.
+
+iswspace.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function iswspace() is thread safe with exceptions.
+
+iswupper.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function iswupper() is thread safe with exceptions.
+
+iswxdigit.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function iswxdigit() is thread safe with exceptions.
+
+j0.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function j0(), j1f() jnl() and so on are thread safe.
+
+lio_listio.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ Its marking matches glibc marking.
+
+log10.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function log10(), log10f() and log10l() are thread safe.
+
+log2.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function log2(), log2f() and log2l() are thread safe.
+
+log.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function log(), logf() and logl() are thread safe.
+
+makecontext.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+makedev.3
+ Peng Haitao
+ ATTRIBUTES: Note macros that are thread-safe
+ The macros makedev(), major() and minor() are thread safe.
+
+malloc.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function malloc(), free(), calloc() and realloc() are
+ thread safe.
+
+mblen.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+mbstowcs.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The marking matches glibc marking.
+
+mbtowc.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is not thread-safe
+ The function mbtowc() is not thread safe.
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+mktemp.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function mktemp() is thread safe.
+
+mtrace.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are not thread-safe
+ The functions mtrace() and muntrace() are not thread safe.
+
+nan.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The markings match glibc markings.
+
+nl_langinfo.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function nl_langinfo() is thread safe with exceptions.
+
+opendir.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The markings match glibc markings.
+
+pow10.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function pow10(), pow10f() and pow10l() are thread safe.
+
+pow.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function pow(), powf() and powl() are thread safe.
+
+pthread_setcancelstate.3
+ Michael Kerrisk
+ Add async-signal-safety information
+
+ptsname.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+putenv.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-unsafe
+ The function putenv() is thread unsafe.
+
+puts.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions fputc(), fputs(), putc(), putchar() and puts() are
+ thread safe.
+
+putwchar.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The marking matches glibc marking.
+
+qecvt.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be same as glibc manual.
+
+rand.3
+ Peng Haitao
+ ATTRIBUTES: Note macros that are thread-safe
+ The functions rand(), rand_r() and srand() are thread safe.
+
+random_r.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+readdir.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be same as glibc manual.
+
+realpath.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The marking matches glibc marking.
+
+regex.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread safe with exceptions
+ The functions regcomp() and regexec() are thread safe with
+ exceptions.
+ The functions regerror() and regfree() are thread safe.
+
+remainder.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The markings match glibc markings.
+
+scalb.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function scalb(), scalbf() and scalbl() are thread safe.
+
+setenv.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-unsafe
+ The function setenv() and unsetenv() are thread unsafe.
+
+siginterrupt.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+sigset.3
+ Peng Haitao
+ ATTRIBUTES: Note macros that are thread-safe
+ The functions sigset(), sighold(), sigrelse() and sigignore()
+ are thread safe.
+
+sinh.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function sinh(), sinhf() and sinhl() are thread safe.
+
+sqrt.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function sqrt(), sqrtf() and sqrtl() are thread safe.
+
+stdarg.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+stdio_ext.3
+ Ma Shimiao
+ Modify thread-safety information
+ Change the thread safety information to be the same as glibc.
+
+strcasecmp.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread safe with exceptions
+ The functions strcasecmp() and strncasecmp() are thread safe
+ with exceptions.
+
+strerror.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+strfmon.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ Its marking matches glibc marking.
+
+strfry.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function strfry() is thread safe.
+
+strftime.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function strftime() is thread safe with exceptions.
+
+strptime.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function strptime() is thread safe with exceptions.
+
+strtok.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+strverscmp.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function strverscmp() is thread safe.
+
+strxfrm.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The marking matches glibc marking.
+
+syslog.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread safe with exceptions
+ The functions openlog() and closelog() are thread safe.
+ The functions syslog() and vsyslog() are thread safe with
+ exceptions.
+
+tempnam.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function tempnam() is thread safe.
+
+termios.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+ Ma Shimiao
+ Modify thread-safety information
+ As this is man page for Linux, we don't need thread safety
+ information for bsd
+
+tgamma.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions tgamma(), tgammaf() and tgammal() in glibc are
+ thread safe. Its markings match glibc markings.
+
+timegm.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread safe with exceptions
+ The functions timelocal() and timegm() are thread safe with
+ exceptions.
+
+tmpfile.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ Its markings match glibc markings.
+
+tmpnam.3
+ Peng Haitao
+ Modify thread-safety information
+ When the argument s is NULL, tmpnam() should be MT-Unsafe.
+
+toupper.3
+ Ma Shimiao
+ Modify thread-safety information
+ After researching and talking, we think toupper() and tolower()
+ should not be marked with locale.
+ After changing, the markings match glbc markings.
+
+tsearch.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions' markings match glibc markings.
+
+ttyname.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be same as glibc manual.
+
+tzset.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function tzset() is thread safe with exceptions.
+
+wcsdup.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ Its marking matches glibc marking.
+
+wctomb.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+y0.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function y0(), y1f() ynl() and so on are thread safe.
+
+man-pages.7
+ Michael Kerrisk
+ Refer reader to attributes(7) for details of ATTRIBUTES section
+ Michael Kerrisk
+ SEE ALSO: add attributes(7)
+
+pthreads.7
+ Michael Kerrisk
+ SEE ALSO: add attributes(7)
+
+standards.7
+ Michael Kerrisk
+ SEE ALSO: add attributes(7)
+
+
+
+==================== Changes in man-pages-3.82 ====================
+
+Released: 2015-03-29, Paris
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Alban Crequy <alban.crequy@gmail.com>
+Andy Lutomirski <luto@amacapital.net>
+Bert Wesarg <bert.wesarg@googlemail.com>
+Bill Pemberton <wfp5p@worldbroken.com>
+Chris Delozier <c.s.delozier@gmail.com>
+David Madore <david.madore@ens.fr>
+Dmitry Deshevoy <mityada@gmail.com>
+Eric W. Biederman <ebiederm@xmission.com>
+Heinrich Schuchardt <xypron.glpk@gmx.de>
+Jakub Wilk <jwilk@debian.org>
+Jann Horn <jann@thejh.net>
+Jason Vas Dias <jason.vas.dias@gmail.com>
+Josh Triplett <josh@joshtriplett.org>
+J William Piggott <elseifthen@gmx.com>
+Kees Cook <keescook@chromium.org>
+Konstantin Shemyak <konstantin@shemyak.com>
+Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
+Matt Turner <mattst88@gmail.com>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Michael Witten <mfwitten@gmail.com>
+Mikael Pettersson <mikpelinux@gmail.com>
+Namhyung Kim <namhyung@gmail.com>
+Nicolas FRANCOIS <nicolas.francois@centraliens.net>
+Paul E Condon <pecondon@mesanetworks.net>
+Peter Adkins <peter.adkins@kernelpicnic.net>
+Scot Doyle <lkml14@scotdoyle.com>
+Shawn Landden <shawn@churchofgit.com>
+Stéphane Aulery <saulery@free.fr>
+Stephen Smalley <sds@tycho.nsa.gov>
+Taisuke Yamada <tai@rakugaki.org>
+Torvald Riegel <triegel@redhat.com>
+Vincent Lefevre <vincent@vinc17.net>
+<ygrex@ygrex.ru>
+Yuri Kozlov <yuray@komyakino.ru>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+nptl.7
+ Michael Kerrisk
+ New page with details of the NPTL POSIX threads implementation
+
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+user_namespaces.7
+ Eric W. Biederman [Michael Kerrisk]
+ Document /proc/[pid]/setgroups
+
+
+Changes to individual pages
+---------------------------
+
+intro.1
+ Stéphane Aulery
+ Prompt is not % but $
+ Stéphane Aulery
+ Various improvements
+ - Add reference to other common shells dash(1), ksh(1)
+ - Add a reference to stdout(3)
+ - Separate cp and mv descriptions
+ - Add examples of special cases of cd
+ - Add su(1) and shutdown(8) references for section Logout
+ and poweroff
+ - Move Control-D to section Logout and poweroff
+ - Fix some little formatting errors
+ Stéphane Aulery
+ Add cross references cited
+ Stéphane Aulery
+ Order SEE ALSO section
+
+clone.2
+ Josh Triplett
+ Document that clone() silently ignores CLONE_PID and CLONE_STOPPED
+ Normally, system calls return EINVAL for flags they don't support.
+ Explicitly document that clone does *not* produce an error for
+ these two obsolete flags.
+ Michael Kerrisk
+ Small rewording of explanation of clone() wrt threads
+ Clone has so many effects that it's an oversimplification to say
+ that the *main* use of clone is to create a thread. (In fact,
+ the use of clone() to create new processes may well be more
+ common, since glibc's fork() is a wrapper that calls clone().)
+
+getgroups.2
+ Michael Kerrisk [Shawn Landden]
+ Add discussion of NPTL credential-changing mechanism
+ At the kernel level, credentials (UIDs and GIDs) are a per-thread
+ attribute. NPTL uses a signal-based mechanism to ensure that
+ when one thread changes its credentials, all other threads change
+ credentials to the same values. By this means, the NPTL
+ implementation conforms to the POSIX requirement that the threads
+ in a process share credentials.
+ Michael Kerrisk
+ ERRORS: add EPERM for the case where /proc/PID/setgroups is "deny"
+ Michael Kerrisk
+ Note capability associated with EPERM error for setgroups(2)
+ Michael Kerrisk
+ Refer reader to user_namespaces(7) for discussion of /proc/PID/setgroups
+ The discussion of /proc/PID/setgroups has moved from
+ proc(5) to user_namespaces(7).
+
+getpid.2
+ Michael Kerrisk
+ Note that getppid() returns 0 if parent is in different PID namespace
+
+getsockopt.2
+ Konstantin Shemyak
+ Note RETURN VALUE details when netfilter is involved
+
+ioctl_list.2
+ Heinrich Schuchardt
+ SEE ALSO ioctl_fat.2
+ Add FAT_IOCTL_GET_VOLUME_ID
+ SEE ALSO ioctl_fat.2
+ Heinrich Schuchardt
+ include/linux/ext2_fs.h
+ Include linux/ext2_fs.h does not contain any ioctl definitions
+ anymore.
+
+ Request codes EXT2_IOC* have been replaced by FS_IOC* in
+ linux/fs.h.
+
+ Some definitions of FS_IOC_* use long* but the actual code expects
+ int* (see fs/ext2/ioctl.c).
+
+msgop.2
+ Bill Pemberton
+ Remove EAGAIN as msgrcv() errno
+ The list of errnos for msgrcv() lists both EAGAIN and ENOMSG as
+ the errno for no message available with the IPC_NOWAIT flag.
+ ENOMSG is the errno that will be set.
+ Bill Pemberton
+ Add an example program
+
+open.2
+ Michael Kerrisk [Jason Vas Dias]
+ Mention blocking semantics for FIFO opens
+ See https://bugzilla.kernel.org/show_bug.cgi?id=95191
+
+seccomp.2
+ Jann Horn [Kees Cook, Mikael Pettersson, Andy Lutomirski]
+ Add note about alarm(2) not being sufficient to limit runtime
+ Jann Horn
+ Explain blacklisting problems, expand example
+ Michael Kerrisk [Kees Cook]
+ Add mention of libseccomp
+
+setgid.2
+ Michael Kerrisk
+ Clarify that setgid() changes all GIDs when caller has CAP_SETGID
+ Michael Kerrisk [Shawn Landden]
+ Add discussion of NPTL credential-changing mechanism
+ At the kernel level, credentials (UIDs and GIDs) are a per-thread
+ attribute. NPTL uses a signal-based mechanism to ensure that
+ when one thread changes its credentials, all other threads change
+ credentials to the same values. By this means, the NPTL
+ implementation conforms to the POSIX requirement that the threads
+ in a process share credentials.
+
+setresuid.2
+ Michael Kerrisk [Shawn Landden]
+ Add discussion of NPTL credential-changing mechanism
+ At the kernel level, credentials (UIDs and GIDs) are a per-thread
+ attribute. NPTL uses a signal-based mechanism to ensure that
+ when one thread changes its credentials, all other threads change
+ credentials to the same values. By this means, the NPTL
+ implementation conforms to the POSIX requirement that the threads
+ in a process share credentials.
+
+setreuid.2
+ Michael Kerrisk [Shawn Landden]
+ Add discussion of NPTL credential-changing mechanism
+ At the kernel level, credentials (UIDs and GIDs) are a per-thread
+ attribute. NPTL uses a signal-based mechanism to ensure that
+ when one thread changes its credentials, all other threads change
+ credentials to the same values. By this means, the NPTL
+ implementation conforms to the POSIX requirement that the threads
+ in a process share credentials.
+ Michael Kerrisk
+ SEE ALSO: add credentials(7)
+
+setuid.2
+ Michael Kerrisk
+ Clarify that setuid() changes all UIDs when caller has CAP_SETUID
+ Michael Kerrisk [Shawn Landden]
+ Add discussion of NPTL credential-changing mechanism
+ At the kernel level, credentials (UIDs and GIDs) are a per-thread
+ attribute. NPTL uses a signal-based mechanism to ensure that
+ when one thread changes its credentials, all other threads change
+ credentials to the same values. By this means, the NPTL
+ implementation conforms to the POSIX requirement that the threads
+ in a process share credentials.
+
+sigaction.2
+ Michael Kerrisk
+ Add discussion of rt_sigaction(2)
+ Michael Kerrisk
+ Note treatment of signals used internally by NPTL
+ The glibc wrapper gives an EINVAL error on attempts to change the
+ disposition of either of the two real-time signals used by NPTL.
+
+sigpending.2
+ Michael Kerrisk
+ Add discussion of rt_sigpending(2)
+
+sigprocmask.2
+ Michael Kerrisk
+ Add discussion of rt_sigprocmask(2)
+ Michael Kerrisk
+ Note treatment of signals used internally by NPTL
+ The glibc wrapper silently ignores attempts to block the two
+ real-time signals used by NPTL.
+
+sigreturn.2
+ Michael Kerrisk
+ Add discussion of rt_sigreturn(2)
+
+sigsuspend.2
+ Michael Kerrisk
+ Add discussion of rt_sigsuspend(2)
+
+sigwaitinfo.2
+ Michael Kerrisk
+ Note treatment of signals used internally by NPTL
+ The glibc wrappers silently ignore attempts to wait for
+ signals used by NPTL.
+ Michael Kerrisk
+ Add discussion of rt_sigtimedwait(2)
+
+socket.2
+ Heinrich Schuchardt
+ SEE ALSO close(2)
+ The description mentions close(2). Hence it should also be
+ referenced in the SEE ALSO section.
+
+syscall.2
+ Jann Horn
+ Add x32 ABI
+
+umount.2
+ Eric W. Biederman
+ Document the effect of shared subtrees on umount(2)
+ Eric W. Biederman
+ Correct the description of MNT_DETACH
+ I recently realized that I had been reasoning improperly about
+ what umount(MNT_DETACH) did based on an insufficient description
+ in the umount.2 man page, that matched my intuition but not the
+ implementation.
+
+ When there are no submounts, MNT_DETACH is essentially harmless to
+ applications. Where there are submounts, MNT_DETACH changes what
+ is visible to applications using the detach directories.
+ Michael Kerrisk
+ Move "shared mount + umount" text to a subsection in NOTES
+
+aio_return.3
+ Stéphane Aulery
+ Document the return value on error
+ Reported by Alexander Holler <holler@ahsoftware.de>
+
+clock.3
+ Stéphane Aulery
+ CLOCKS_PER_SEC = 1000000 is required by XSI, not POSIX
+ Debian Bug #728213 reported by Tanaka Akira <akr@fsij.org>
+
+ See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728213
+
+dlopen.3
+ Michael Kerrisk
+ Amend error in description of dlclose() behavior
+ The current text says that unloading depends on whether
+ the reference count falls to zero *and no other libraries
+ are using symbols in this library*. That latter text has
+ been there since man-pages-1.29, but it seems rather dubious.
+ How could the implementation know whether other libraries
+ are still using symbols in this library? Furthermore, no
+ other implementation's man page mentions this point.
+ Seems best to drop this point.
+ Michael Kerrisk
+ Add some details for RTLD_DEFAULT
+ Michael Kerrisk
+ Add some details on RTLD_NEXT and preloading
+ Michael Kerrisk
+ RTLD_NEXT works for symbols generally, not just functions
+ The common use case is for functions, but RTLD_NEXT
+ also applies to variable symbols.
+ Michael Kerrisk
+ dlclose() recursively closes dependent libraries
+ Note that dlclose() recursively closes dependent libraries
+ that were loaded by dlopen()
+ Michael Kerrisk
+ Rename second dlopen() argument from "flag" to "flags"
+ This is more consistent with other such arguments
+ Michael Kerrisk
+ Reformat text on RTLD_DEFAULT and RTLD_NEXT
+
+fmemopen.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The markings match glibc markings.
+
+fpathconf.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The marking matches glibc marking.
+
+fputwc.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The marking matches glibc marking.
+
+fputws.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The marking matches glibc marking.
+
+fseek.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The markings match glibc markings.
+
+fseeko.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The markings match glibc markings.
+
+gcvt.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The marking matches glibc marking.
+
+getline.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The marking matches glibc marking.
+
+getwchar.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The marking matches glibc marking.
+
+hypot.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The markings match glibc markings.
+
+iconv_open.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The marking matches glibc marking.
+
+if_nameindex.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The markings match glibc markings.
+
+initgroups.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The markings match glibc markings.
+
+mq_open.3
+ Torvald Riegel
+ Add EINVAL error case for invalid name
+ This behavior is implementation-defined by POSIX. If the name
+ doesn't start with a '/', glibc returns EINVAL without attempting
+ the syscall.
+
+popen.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The marking matches glibc marking.
+
+pthread_kill.3
+ Michael Kerrisk
+ Note treatment of signals used internally by NPTL
+ The glibc pthread_kill() function gives an error on attempts
+ to send either of the real-time signals used by NPTL.
+
+pthread_sigmask.3
+ Michael Kerrisk
+ Note treatment of signals used internally by NPTL
+ The glibc implementation silently ignores attempts to block the two
+ real-time signals used by NPTL.
+
+pthread_sigqueue.3
+ Michael Kerrisk
+ Note treatment of signals used internally by NPTL
+ The glibc pthread_sigqueue() function gives an error on attempts
+ to send either of the real-time signals used by NPTL.
+
+resolver.3
+ Stéphane Aulery [Jakub Wilk]
+ Document missing options used by _res structure indicate defaults
+ Missing options: RES_INSECURE1, RES_INSECURE2, RES_NOALIASES,
+ USE_INET6, ROTATE, NOCHECKNAME, RES_KEEPTSIG, BLAST, USEBSTRING,
+ NOIP6DOTINT, USE_EDNS0, SNGLKUP, SNGLKUPREOP, RES_USE_DNSSEC,
+ NOTLDQUERY, DEFAULT
+
+ Written from the glibc source and resolv.conf.5.
+
+ See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527136
+ Stéphane Aulery
+ RES_IGNTC is implemented
+
+rint.3
+ Matt Turner
+ Document that halfway cases are rounded to even
+ Per IEEE-754 rounding rules.
+
+ The round(3) page describes the behavior of rint and nearbyint
+ in the halfway cases by saying:
+
+ These functions round x to the nearest integer, but round
+ halfway cases away from zero [...], instead of to the
+ nearest even integer like rint(3)
+
+sigqueue.3
+ Michael Kerrisk
+ NOTES: add "C library/kernel ABI differences" subheading
+ Michael Kerrisk
+ Clarify version info (mention rt_sigqueueinfo())
+
+sigsetops.3
+ Michael Kerrisk
+ Note treatment of signals used internally by NPTL
+ The glibc sigfillset() function excludes the two real-time
+ signals used by NPTL.
+
+sigwait.3
+ Michael Kerrisk
+ Note treatment of signals used internally by NPTL
+ The glibc sigwait() silently ignore attempts to wait for
+ signals used by NPTL.
+
+strcoll.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The markings match glibc markings.
+
+strdup.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The marking matches glibc marking.
+
+tzset.3
+ J William Piggott
+ Add 'std' quoting information
+
+ulimit.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The marking matches glibc marking.
+
+wcstombs.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The marking matches glibc marking.
+
+wctob.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The marking matches glibc marking.
+
+xdr.3
+ Taisuke Yamada
+ Clarified incompatibility and correct usage of XDR API
+ See http://bugs.debian.org/628099
+
+console_codes.4
+ Scot Doyle
+ Add Console Private CSI sequence 15
+ An undocumented escape sequence in drivers/tty/vt/vt.c brings the
+ previously accessed virtual terminal to the foreground.
+ mtk: Patch misattributed to Taisuke Yamada in Git commit
+ because of a muck up on my part.
+ Michael Kerrisk
+ Add kernel version number for CSI sequence 15
+
+random.4
+ Michael Kerrisk
+ Fix permissions shown for the devices
+ These days, the devices are RW for everyone.
+
+filesystems.5
+ Michael Kerrisk
+ Remove dubious claim about comparative performance of ext2
+ Perhaps it was the best filesystem performance-wise in
+ the 20th century, when that text was written. That probably
+ ceased to be true quite a long time ago, though.
+ Stéphane Aulery
+ Add cross references for ext filesystems
+ Stéphane Aulery
+ Specifies the scope of this list and its limits.
+
+host.conf.5
+hosts.5
+resolv.conf.5
+ Stéphane Aulery [Paul E Condon]
+ Cross references of these pages.
+ See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=298259
+
+host.conf.5
+ Stéphane Aulery
+ Rework discussion of nospoof, spoofalert, spoof and RESOLV_SPOOF_CHECK
+ The keywords and environment variables "nospoof", "spoofalert",
+ "spoof" and RESOLV_SPOOF_CHECK were added to glibc 2.0.7 but
+ never implemented
+
+ Move descriptions to historical section and reorder it for clarity
+
+ See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773443
+
+hosts.5
+ Stéphane Aulery [Vincent Lefevre]
+ Mention 127.0.1.1 for FQDN and IPv6 examples
+ See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562890
+
+proc.5
+ Taisuke Yamada
+ Document /proc/PID/status VmPin field
+ See https://bugs.launchpad.net/bugs/1071746
+ Michael Kerrisk
+ Document (the obsolete) /proc/PID/seccomp
+ Michael Kerrisk
+ Replace description of 'uid_map' with a reference to user_namespaces(7)
+ All of the information in proc(5) was also present in
+ user_namespaces(7), but the latter was more detailed
+ and up to date.
+ Taisuke Yamada
+ Fix SELinux /proc/pid/attr/current example
+ Since the /proc/pid/attr API was added to the kernel, there
+ have been a couple of changes to the SELinux handling of
+ /proc/pid/attr/current. Fix the SELinux /proc/pid/attr/current
+ example text to reflect these changes and note which kernel
+ versions first included the changes.
+
+securetty.5
+ Stéphane Aulery [Nicolas FRANCOIS]
+ Note that the pam_securetty module also uses this file
+ See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528015
+
+ This patch is a modified version of the one proposed without
+ parts specific to Debian.
+
+boot.7
+ Michael Witten
+ Copy edit
+ While a lot of the changes are issues of presentation,
+ there are also issues of grammar and punctuation.
+ Michael Witten
+ Mention `systemd(1)' and its related `bootup(7)'
+ It's important that the reader receive contemporary information.
+
+credentials.7
+ Michael Kerrisk
+ SEE ALSO: add pthreads(7)
+ Michael Kerrisk
+ Add reference to nptl(7)
+
+feature_test_macros.7
+ Michael Kerrisk
+ Update discussion of _FORTIFY_SOURCE
+ Since the initial implementation a lot more checks were added.
+ Describe all the checks would be too verbose (and would soon
+ fall out of date as more checks are added). So instead, describe
+ the kinds of checks that are done more generally.
+ Also a few other minor edits to the text.
+
+hier.7
+ Stéphane Aulery
+ First patch of a series to achieve compliance with FHS 2.3
+ Stéphane Aulery
+ SGML and XML directories are separated in FHS 2.3
+ Stéphane Aulery
+ Add missing directories defined by FHS 2.3
+ Stéphane Aulery
+ Identify which directories are optional
+ Stéphane Aulery
+ Document /initrd, /lost+found and /sys
+ Ubuntu Bug #70094 reported by Brian Beck
+ https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/70094
+ Stéphane Aulery
+ Explain YP, which is not obvious
+
+ipv6.7
+ Stéphane Aulery [David Madore]
+ SOL_IPV6 and other SOL_* options socket are not portable
+ See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472447
+
+man-pages.7
+ Michael Kerrisk [Bill Pemberton]
+ Add indent(1) command that produces desired formatting for example code
+ Stéphane Aulery
+ Improve description of sections in accordance with intro pages
+
+packet.7
+ Michael Kerrisk
+ Rework description of fanout algorithms as list
+ Michael Kerrisk
+ Remove mention of needing UID 0 to create packet socket
+ The existing text makes no sense. The check is based
+ purely on a capability check. (Kernel function
+ net/packet/af_packet.c::packet_create()
+ Michael Kerrisk
+ Remove text about ancient glibc not defining SOL_PACKET
+ This was fixed in glibc 2.1.1, which is a long while ago.
+ And in any case, there is nothing special about this case;
+ it's just one of those times when glibc lags.
+ Michael Kerrisk
+ Rework description of 'sockaddr_ll' fields as a list
+ Michael Kerrisk
+ Various minor edits
+
+pthreads.7
+ Michael Kerrisk
+ Add references to nptl(7)
+
+raw.7
+ Michael Kerrisk
+ Rephrase "Linux 2.2" language to "Linux 2.2 or later"
+ The man page was written in the LInux 2.2 timeframe, and
+ some phrasing was not future-proof.
+
+signal.7
+ Michael Kerrisk
+ Note when Linux added realtime signals
+ Michael Kerrisk
+ Correct the range of realtime signals
+ Michael Kerrisk
+ Summarize 2.2 system call changes that resulted from larger signal sets
+ Michael Kerrisk
+ SEE ALSO: add nptl(7)
+
+tcp.7
+ Peter Adkins
+ Document removal of TCP_SYNQ_HSIZE
+ Looking over the man page for 'tcp' I came across a reference to
+ tuning the 'TCP_SYNQ_HSIZE' parameter when increasing
+ 'tcp_max_syn_backlog' above 1024. However, this static sizing was
+ removed back in Linux 2.6.20 in favor of dynamic scaling - as
+ part of commit 72a3effaf633bcae9034b7e176bdbd78d64a71db.
+
+user_namespaces.7
+ Eric W. Biederman
+ Update the documentation to reflect the fixes for negative groups
+ Files with access permissions such as rwx---rwx give fewer
+ permissions to their group then they do to everyone else. Which
+ means dropping groups with setgroups(0, NULL) actually grants a
+ process privileges.
+
+ The unprivileged setting of gid_map turned out not to be safe
+ after this change. Privileged setting of gid_map can be
+ interpreted as meaning yes it is ok to drop groups. [ Eric
+ additionally noted: Setting of gid_map with privilege has been
+ clarified to mean that dropping groups is ok. This allows
+ existing programs that set gid_map with privilege to work
+ without changes. That is, newgidmap(1) continues to work
+ unchanged.]
+
+ To prevent this problem and future problems, user namespaces were
+ changed in such a way as to guarantee a user can not obtain
+ credentials without privilege that they could not obtain without
+ the help of user namespaces.
+
+ This meant testing the effective user ID and not the filesystem
+ user ID, as setresuid(2) and setregid(2) allow setting any process
+ UID or GID (except the supplementary groups) to the effective ID.
+
+ Furthermore, to preserve in some form the useful applications
+ that have been setting gid_map without privilege, the file
+ /proc/[pid]/setgroups was added to allow disabling setgroups(2).
+ With setgroups(2) permanently disabled in a user namespace, it
+ again becomes safe to allow writes to gid_map without privilege.
+ Michael Kerrisk
+ Rework some text describing permission rules for updating map files
+ No (intentional) change to the facts, but this restructuring
+ should make the meaning easier to grasp.
+ Michael Kerrisk
+ Update kernel version associated with 5-line limit for map files
+ As at Linux 3.18, the limit is still five lines, so mention the
+ more recent kernel version in the text.
+ Michael Kerrisk [Alban Crequy]
+ Handle /proc/PID/setgroups in the example program
+ Michael Kerrisk
+ Rework text describing restrictions on updating /proc/PID/setgroups
+ No (intentional) changes to factual description, but the
+ restructured text is hopefully easier to grasp.
+ Michael Kerrisk
+ Explain why the /proc/PID/setgroups file was added
+
+ldconfig.8
+ Michael Kerrisk
+ Note use of /lib64 and /usr/lib64 on some 64-bit architectures
+
+ld.so.8
+ Michael Kerrisk
+ Note the use of /lib64 and /usr/lib64 on some 64-bit architectures
+
+
+
+==================== Changes in man-pages-3.83 ====================
+
+Released: 2015-04-19, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Andreas Baak <andreas.baak@gmail.com>
+Andreas Dilger <adilger@dilger.ca>
+cdlscpmv <cdlscpmv@gmail.com>
+Cyrill Gorcunov <gorcunov@openvz.org>
+Darrick J. Wong <darrick.wong@oracle.com>
+David Rientjes <rientjes@google.com>
+Dima Tisnek <dimaqq@gmail.com>
+Eric Sandeen <sandeen@redhat.com>
+Fabien Pichot <fpichot@bouledef.eu>
+Felix Sedlmeier <sedlmeier@gmx.de>
+Gleb Fotengauer-Malinovskiy <glebfm@altlinux.org>
+Heinrich Schuchardt <xypron.glpk@gmx.de>
+Jann Horn <jann@thejh.net>
+Jon Grant <jg@jguk.org>
+Jonny Grant <jg@jguk.org>
+Kees Cook <keescook@chromium.org>
+Masanari Iida <standby24x7@gmail.com>
+Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Nikos Mavrogiannopoulos <nmav@gnutls.org>
+Omar Sandoval <osandov@osandov.com>
+Pierre Chifflier <pollux@debian.org>
+Robin H. Johnson <robbat2@gentoo.org>
+Rob Landley <rob@landley.net>
+Theodore Ts'o <tytso@mit.edu>
+Vlastimil Babka <vbabka@suse.cz>
+Walter Harms <wharms@bfs.de>
+William Woodruff <william@tuffbizz.com>
+YOSHIFUJI Hideaki <hideaki.yoshifuji@miraclelinux.com>
+Zeng Linggang <zenglg.jy@cn.fujitsu.com>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+posix_madvise.3
+ Michael Kerrisk
+ New page documenting posix_madvise(3)
+
+ftw.3
+ Michael Kerrisk
+ Reorganize the page to give primacy to nftw()
+ nftw() is the better API, and POSIX.1-2008 marks ftw() obsolete.
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+getdents.2
+ Michael Kerrisk [Dima Tisnek]
+ Document getdents64()
+ See https://bugzilla.kernel.org/show_bug.cgi?id=14795
+
+mount.2
+ Michael Kerrisk, Theodore Ts'o [Eric Sandeen, Andreas Dilger,
+ Omar Sandoval, Darrick J. Wong]
+ Document MS_LAZYTIME
+
+proc.5
+ Michael Kerrisk
+ Document /proc/sys/kernel/randomize_va_space
+ Michael Kerrisk
+ Document /proc/PID/fdinfo epoll format
+ Michael Kerrisk
+ Describe /proc/PID/fdinfo eventfd format
+ Michael Kerrisk
+ Document /proc/PID/fdinfo signalfd format
+
+
+New and changed links
+---------------------
+
+newfstatat.2
+ Michael Kerrisk
+ New link to fstatat64.2
+
+prlimit64.2
+ Michael Kerrisk
+ New link to getrlimit.2
+
+
+Global changes
+--------------
+
+Various section 3 math pages
+ Michael Kerrisk
+ Note that these functions are also in POSIX.1-2001 and POSIX.1-2008
+
+
+Changes to individual pages
+---------------------------
+
+getent.1
+ Robin H. Johnson
+ Document options
+ The options to getent are now documented, after being around for
+ nearly a decade without changes.
+ Michael Kerrisk
+ Document help and version options
+
+fallocate.2
+ Michael Kerrisk
+ Fix kernel version number for FALLOC_FL_ZERO_RANGE
+ FALLOC_FL_ZERO_RANGE was added in 3.15, not 3.14.
+ Michael Kerrisk
+ Note that SMB3 added FALLOC_FL_ZERO_RANGE support in Linux 3.17
+
+getrlimit.2
+ Michael Kerrisk
+ Note that the underlying system call for prlimit() is prlimit64()
+ Michael Kerrisk
+ Remove "_FILE_OFFSET_BITS == 64" from prlimit() FTM requirements
+ "_FILE_OFFSET_BITS == 64" is not needed to get the prlimit()
+ declaration.
+
+ioctl_list.2
+ Nikos Mavrogiannopoulos
+ SIOCADDRT accepts in6_rtmsg in INET6 protocol
+ Heinrich Schuchardt
+ TFD_IOC_SET_TICKS
+ timerfd_create.2 mentions TFD_IOC_SET_TICKS. We should add it to
+ ioctl_list.2, too.
+
+llseek.2
+ Michael Kerrisk
+ Advise reader to use lseek(2) instead
+ Michael Kerrisk
+ llseek() exists on 32-bit platforms to support seeking to large offsets
+
+madvise.2
+ David Rientjes
+ Specify MADV_REMOVE returns EINVAL for hugetlbfs
+ madvise(2) actually returns with error EINVAL for MADV_REMOVE
+ when used for hugetlb VMAs, not EOPNOTSUPP, and this has been
+ the case since MADV_REMOVE was introduced in commit f6b3ec238d12
+ ("madvise(MADV_REMOVE): remove pages from tmpfs shm backing
+ store"). Specify the exact behavior.
+ Michael Kerrisk
+ SEE ALSO: add posix_madvise(2)
+
+poll.2
+ Michael Kerrisk [Andreas Baak]
+ SEE ALSO: add epoll(7)
+
+posix_fadvise.2
+ Michael Kerrisk
+ Add "C library/kernel ABI differences" subsection
+
+pread.2
+ Michael Kerrisk
+ Add "C library/kernel ABI differences" subsection
+
+seccomp.2
+ Michael Kerrisk [Pierre Chifflier, Kees Cook]
+ Note that seccomp_data is read-only
+
+stat.2
+ Michael Kerrisk
+ Add some details on various "stat" versions
+ Three versions of "stat" appeared on 32-bit systems,
+ dealing with structures of different (increasing) sizes.
+ Explain some of the details, and also note that the
+ situation is simpler on modern 64-bit architectures.
+ Michael Kerrisk
+ Add mention of newfstatat()
+ The underlying system call for fstatat() is newfstatat()
+ on some architectures.
+
+symlink.2
+ Michael Kerrisk [Jonny Grant]
+ ERRORS: add linkpath=="" case for ENOENT
+
+syscalls.2
+ Michael Kerrisk
+ Remove prlimit()
+ There really is only the prlimit64() system call.
+ Michael Kerrisk
+ Add some details about the "multiple versions of system calls"
+ The multiple-system-call-version phenomenon is particularly a
+ feature of older 32-bit platforms. Hint at that fact in the text.
+
+timerfd_create.2
+ Cyrill Gorcunov [Michael Kerrisk]
+ Document TFD_IOC_SET_TICKS ioctl() operation
+ Michael Kerrisk
+ Add some details to C library/kernel ABI differences
+
+unshare.2
+ Michael Kerrisk [Fabien Pichot]
+ Remove mention of "System V" from discussion of CLONE_NEWIPC
+ These days, CLONE_NEWIPC also affects POSIX message queues.
+
+asprintf.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+carg.3
+ Michael Kerrisk
+ Add introductory sentence explaining what these functions calculate
+
+ccos.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ Michael Kerrisk
+ Add introductory sentence explaining what these functions calculate
+
+ccosh.3
+ Michael Kerrisk
+ Add introductory sentence explaining what these functions calculate
+
+cexp.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+
+clock.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that is thread-safe
+
+clog.3
+ Michael Kerrisk
+ Add introductory sentence explaining what these functions calculate
+
+csin.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ Michael Kerrisk
+ Add introductory sentence explaining what these functions calculate
+
+csinh.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ Michael Kerrisk
+ Add introductory sentence explaining what these functions calculate
+
+csqrt.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ Michael Kerrisk
+ Simplify description of what these functions calculate
+
+ctan.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ Michael Kerrisk
+ Add introductory sentence explaining what these functions calculate
+
+ctanh.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ Michael Kerrisk
+ Add introductory sentence explaining what these functions calculate
+
+ctime.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+exec.3
+ Michael Kerrisk
+ SYNOPSIS: Clarify calling signature for execl() and execlp()
+ Michael Kerrisk [Andreas Baak]
+ Correct prototype for execle()
+ Make the prototype shown into correct C.
+
+ftw.3
+ Michael Kerrisk [Felix Sedlmeier]
+ ftw() and nftw() differ for the non-stat-able symlink case
+ The POSIX specification of ftw() says that an un-stat-able
+ symlink may yield either FTW_NS or FTW_SL. The specification
+ of nftw() does not carry this statement.
+ Michael Kerrisk
+ CONFORMING TO: add POSIX.1-2008
+ Michael Kerrisk
+ Update POSIX version references in NOTES
+
+getcwd.3
+ Jann Horn [Michael Kerrisk]
+ Note behavior for unreachable current working directory
+ Michael Kerrisk
+ Add ENOMEM error
+
+gethostbyname.3
+ Michael Kerrisk [Jonny Grant]
+ Clarify that NO_ADDRESS and NO_DATA are synonyms
+ Michael Kerrisk
+ Add some detail for NO_DATA
+ Text consistent with POSIX and FreeBSD's gethostbyname() man page.
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+getnetent.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+get_nprocs_conf.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+getutent.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+glob.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+insque.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+
+login.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+lseek64.3
+ Michael Kerrisk
+ Clarify details with respect to 32-bit and 64-bit systems
+
+malloc.3
+ Michael Kerrisk
+ Add ENOMEM error
+
+mbsnrtowcs.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that isn't thread-safe
+
+mbsrtowcs.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that isn't thread-safe
+
+mq_notify.3
+ Michael Kerrisk
+ Add "C library/kernel ABI differences" subsection
+
+mq_open.3
+ Michael Kerrisk [Fabien Pichot]
+ NOTES: explain differences from the underlying system call
+ The check for the slash at the start of a pathname is done in glibc
+
+openpty.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+perror.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+posix_memalign.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+printf.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+ Walter Harms [Michael Kerrisk]
+ Simplify the example code
+
+qsort.3
+ Michael Kerrisk [Rob Landley]
+ alphasort() and versionsort() are not suitable for 'compar'
+ In glibc 2.10, the prototypes of alphasort() and versionsort()
+ were changed so that the arguments switched from 'const void *' to
+ 'const struct dirent **', to match the POSIX.1-2008 specification
+ of alphasort(). As such, compiler warnings will result if
+ these functions are used as the arguments of qsort().
+
+ warning: passing argument 4 of 'qsort' from incompatible
+ pointer type
+ expected '__compar_fn_t' but argument is of type
+ 'int (*)(const struct dirent **, const struct dirent **)'
+
+ Therefore, remove the ancient NOTES text suggesting that
+ alphasort() and versionsort() can be used as suitable
+ 'compar' arguments for qsort().
+
+realpath.3
+ Michael Kerrisk [Jon Grant]
+ Add ENOMEM error
+
+scandir.3
+ Michael Kerrisk
+ glibc 2.10 changed the argument types for alphasort() and versionsort()
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+scanf.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+setnetgrent.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+significand.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+
+strcasecmp.3
+ Michael Kerrisk [Jonny Grant]
+ Clarify that strcasecmp() does a byte-wise comparison
+ Michael Kerrisk
+ CONFORMING TO: add POSIX.1-2008
+
+unlocked_stdio.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+updwtmp.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+wcrtomb.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that isn't thread-safe
+
+wcsnrtombs.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that isn't thread-safe
+
+wcsrtombs.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that isn't thread-safe
+
+wordexp.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+wprintf.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+proc.5
+ Michael Kerrisk
+ Describe "mnt_id" field of /proc/PID/fdinfo
+ Michael Kerrisk
+ Note that abstract sockets are included in /proc/net/unix
+ Michael Kerrisk
+ Update description /proc/sys/unix 'Type' field
+ The existing text was very crufty. UNIX domain sockets
+ support more than SOCK_STREAM for a _very_ long time now.
+ Michael Kerrisk
+ Add some detail to /proc/PID/timers
+ Michael Kerrisk [Vlastimil Babka]
+ Enhance discussion of /proc/PID/status 'VmSwap' field
+
+epoll.7
+ Michael Kerrisk
+ SEE ALSO: add poll(2) and select(2)
+
+icmp.7
+ YOSHIFUJI Hideaki/吉藤英明
+ Document net.ipv4.ping_group_range knob
+
+nptl.7
+ Michael Kerrisk
+ Add reference to timer_create(2)
+
+
+==================== Changes in man-pages-4.00 ====================
+
+Released: 2015-05-07, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Advait Dixi <advaitdixit@hotmail.com>
+Alain Kalker <a.c.kalker@gmail.com>
+Andi Kleen <andi@firstfloor.org>
+Andreas Gruenbacher <agruenba@redhat.com>
+Andreas Heiduk <asheiduk@googlemail.com>
+Askar Safin <safinaskar@mail.ru>
+Brice Goglin <Brice.Goglin@inria.fr>
+Cameron Norman <camerontnorman@gmail.com>
+Carlos O'Donell <carlos@redhat.com>
+Chris Metcalf <cmetcalf@tilera.com>
+Christophe Lohr <Christophe.Lohr@telecom-bretagne.eu>
+Christopher Head <chead@chead.ca>
+Christoph Hellwig <hch@infradead.org>
+David Wilcox <davidvsthegiant@gmail.com>
+Denis Du <denisdu@ruggedcom.com>
+Egmont Koblinger <egmont@gmail.com>
+Filipe Brandenburger <filbranden@gmail.com>
+Filipus Klutiero <chealer@gmail.com>
+Florian Weimer <fweimer@redhat.com>
+Frédéric Maria <frederic.maria@free.fr>
+Gleb Fotengauer-Malinovskiy <glebfm@altlinux.org>
+Graham Shaw <gdshaw@riscpkg.org>
+Gregor Jasny <igjasny@googlemail.com>
+Guillem Jover <guillem@hadrons.org>
+Guy Harris <guy@alum.mit.edu>
+Heinrich Schuchardt <xypron.glpk@gmx.de>
+Ian Pilcher <arequipeno@gmail.com>
+Jann Horn <jann@thejh.net>
+Jason Newton <nevion@gmail.com>
+J. Bruce Fields <bfields@fieldses.org>
+Jiri Pirko <jpirko@redhat.com>
+Joachim Wuttke <j.wuttke@fz-juelich.de>
+Joern Heissler <contact@joern.heissler.de>
+Jonathan Nieder <jrnieder@gmail.com>
+Joonas Salo <salo.joonas@gmail.com>
+Jussi Lehtola <jussilehtola@fedoraproject.org>
+Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
+KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
+Laurence Gonsalves <laurence@xenomachina.com>
+Magnus REFTEL <magnus.xm.reftel@stericsson.com>
+Michael Kerrisk <mtk.manpages@gmail.com>
+NeilBrown <neilb@suse.de>
+Regid Ichira <regid23@nt1.in>
+Sam Varshavchik <mrsam@courier-mta.com>
+Steinar H. Gunderson <sgunderson@bigfoot.com>
+Stéphane Aulery <saulery@free.fr>
+Stephane Fillod <fillods@users.sf.net>
+Tetsuo Handa <from-linux-kernel@i-love.sakura.ne.jp>
+Thomas Hood <jdthood@gmail.com>
+Urs Thuermann <urs@isnogud.escape.de>
+Vasiliy Kulikov <segooon@gmail.com>
+Vegard Nossum <vegard.nossum@gmail.com>
+Weijie Yang <weijie.yang@samsung.com>
+William Woodruff <william@tuffbizz.com>
+Zeng Linggang <zenglg.jy@cn.fujitsu.com>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+get_phys_pages.3
+ William Woodruff
+ Document get_phys_pages() and get_avphys_pages()
+
+loop.4
+ Urs Thuermann, Michael Kerrisk
+ New page documenting the loop device
+
+xattr.7
+ Andreas Gruenbacher
+ Import attr(5) man page from the 'attr' project
+ After discussions with Andreas Gruenbacher, it makes sense to
+ move this page into man-pages, since it mostly relates to
+ kernel details. Since this is an overview page,
+ we'll move it to Section 7.
+ Michael Kerrisk
+ Rename page
+ "xattr" is a more meaningful name than "attr" (it resonates
+ with the names of the system calls), so as long as we are
+ moving the page to a new section, we'll change the name as well,
+ and retain an acl(5) link so that old references remain valid.
+
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+mmap.2
+ Michael Kerrisk [Andi Kleen]
+ Document MAP_HUGE_2MB, MAP_HUGE_1GB, and MAP_HUGE_SHIFT
+
+shmget.2
+ Michael Kerrisk [Andi Kleen]
+ Document SHM_HUGE_2MB, SHM_HUGE_1GB, and SHM_HUGE_SHIFT
+
+resolver.3
+ Michael Kerrisk [Jonathan Nieder]
+ Add descriptions of some other resolver functions
+ Add res_ninit(), res_nquery(), res_nsearch(),
+ and res_nquerydomain(), res_nmkquery(), res_nsend().
+
+tty_ioctl.4
+ Frédéric Maria [Stephane Fillod, Andreas Heiduk]
+ Document TIOCMIWAIT and TIOCGICOUNT
+ Michael Kerrisk
+ Document TIOCGEXCL
+ Michael Kerrisk
+ Document TIOGCPKT
+ Michael Kerrisk
+ Document TIOCSPTLCK
+ Michael Kerrisk
+ Document TIOCGPTLCK
+
+
+New and changed links
+---------------------
+
+CMSG_DATA.3
+ Michael Kerrisk
+ New link to cmsg(3)
+
+CMSG_LEN.3
+ Michael Kerrisk
+ New link to cmsg(3)
+
+dprintf.3
+ Michael Kerrisk
+ Convert to a link to printf.3
+
+get_avphys_pages.3
+ William Woodruff
+ New link to new get_phys_pages.3 page
+
+res_ninit.3
+res_nmkquery.3
+res_nquery.3
+res_nquerydomain.3
+res_nsearch.3
+res_nsend.3
+ Michael Kerrisk
+ New links to resolver(3) man page
+
+loop-control.4
+ Michael Kerrisk
+ New link to loop.4
+
+attr.5
+ Michael Kerrisk
+ New link to xattr(7)
+
+
+Global changes
+--------------
+
+chown.2
+execve.2
+prctl.2
+truncate.2
+proc.5
+capabilities.7
+ld.so.8
+ Michael Kerrisk
+ Tighter wording: 'mode bit' rather than 'permission bit'
+ For sticky, set-UID, and set-GID mode bits (as used in POSIX).
+
+
+Changes to individual pages
+---------------------------
+
+add_key.2
+keyctl.2
+request_key.2
+ Michael Kerrisk
+ SEE ALSO: add keyrings(7)
+
+add_key.2
+request_key.2
+ Michael Kerrisk
+ SEE ALSO: add keyctl(3)
+
+epoll_ctl.2
+ Michael Kerrisk
+ After EPOLLHUP, EOF will be seen only after all data has been consumed
+
+epoll_wait.2
+ Michael Kerrisk
+ Clarify that signal mask treatment in epoll_pwait() is per-thread
+ s/sigprocmask()/pthread_sigmask()/
+
+fcntl.2
+ Michael Kerrisk [Vegard Nossum]
+ Note an F_SETSIG corner case
+
+get_mempolicy.2, set_mempolicy
+ Brice Goglin
+ Policy is per thread, not per process
+
+getxattr.2
+listxattr.2
+removexattr.2
+setxattr.2
+capabilities.7
+ Michael Kerrisk
+ Adjust "attr(5)" references to "xattr(7)"
+
+ioctl.2
+ Michael Kerrisk
+ SEE ALSO: add console_ioctl(2) and tty_ioctl(2)
+
+listxattr.2
+xattr.7
+ Michael Kerrisk
+ Describe listxattr(2) E2BIG error and document it as a BUG
+
+mkdir.2
+ Michael Kerrisk
+ Wording fixes + point reader at stat(2) for explanation of file mode
+ Michael Kerrisk [Andreas Grünbacher]
+ Further tweaks to text on S_ISVTX and 'mode' argument
+
+mknod.2
+ Michael Kerrisk
+ Rewordings + point reader at stat(2) for details of mode bits
+
+mmap.2
+ Michael Kerrisk
+ Remove text that implies that munmap() syncs MAP_SHARED mapping to file
+ The existing text in this page:
+
+ MAP_SHARED Share this mapping. Updates to the mapping
+ are visible to other processes that map this
+ file, and are carried through to the underly‐
+ ing file. The file may not actually be
+ updated until msync(2) or munmap() is called.
+
+ implies that munmap() will sync the mapping to the underlying
+ file. POSIX doesn't require this, and some light reading of the
+ code and some light testing (fsync() after munmap() of a large
+ file) also indicates that Linux doesn't do this.
+
+msync.2
+ Michael Kerrisk
+ Rework text of DESCRIPTION
+ Rewrite the text somewhat, for easier comprehension.
+ No (intentional) changes to factual content
+
+nfsservctl.2
+ Michael Kerrisk [J. Bruce Fields]
+ Note that nfsservctl() was replaced by files in nfsd filesystem
+
+open.2
+ Michael Kerrisk [Andreas Gruenbacher]
+ open() honors the S_ISVTX, S_ISUID, and S_ISGID bits in 'mode'
+ Michael Kerrisk
+ Tighten wording: use 'mode bit' rather than 'permission bit'
+ Michael Kerrisk [NeilBrown]
+ BUGS: O_CREAT | O_DIRECTORY succeeds if pathname does not exist
+
+poll.2
+ Michael Kerrisk [Ian Pilcher]
+ Clarify that signal mask treatment in ppoll() is per-thread
+ s/sigprocmask()/pthread_sigmask()/
+ Michael Kerrisk [Sam Varshavchik]
+ After POLLHUP, EOF will be seen only after all data has been consumed
+ Michael Kerrisk
+ Make it clearer which bits are ignored in 'events'
+
+prctl.2
+ Michael Kerrisk [David Wilcox, Filipe Brandenburger]
+ Note that "parent" for purposes of PR_SET_DEATHSIG is a *thread*
+ See https://bugzilla.kernel.org/show_bug.cgi?id=43300
+
+sendfile.2
+ Michael Kerrisk [Jason Newton]
+ Note that sendfile does not support O_APPEND for 'out_fd'
+ See https://bugzilla.kernel.org/show_bug.cgi?id=82841
+ Michael Kerrisk [Gregor Jasny]
+ RETURN VALUE: note the possibility of "short sends"
+ See https://bugzilla.kernel.org/show_bug.cgi?id=97491
+ Michael Kerrisk [Askar Safin]
+ Clarify text on 'out_fd' and regular files in Linux 2.4
+ See https://bugzilla.kernel.org/show_bug.cgi?id=86001
+
+shutdown.2
+ Michael Kerrisk [Stéphane Aulery]
+ BUGS: UNIX domain sockets now detect invalid 'how' values
+ Bug fixed in Linux 3.7.
+ See https://bugzilla.kernel.org/show_bug.cgi?id=47111
+
+sigaction.2
+ Michael Kerrisk
+ Refer the reader to fcntl(2) F_SETSIG for further details on si_fd
+
+stat.2
+ Jann Horn
+ Add note about stat() being racy
+ Andreas Gruenbacher
+ Improve description of some mode constants
+ Michael Kerrisk [Andreas Grünbacher]
+ Remove excessive leading zeros on some constants
+ Michael Kerrisk
+ Add text on POSIX terms "file mode bits" and "file permission bits"
+ Recent changes to various pages employ this distinction.
+ Michael Kerrisk
+ Tighten wording: use 'mode bit' rather than 'permission bit'
+ According to POSIX, the the 9 UGO*RWX bits are permissions, and
+ 'mode' is used to refer to collectively to those bits plus sticky,
+ set-UID, and set_GID bits.
+
+syslog.2
+ Michael Kerrisk
+ SEE ALSO: add dmesg(1)
+
+umask.2
+open.2
+mknod.2
+mkdir.2
+ Andreas Gruenbacher
+ Explain what default ACLs do
+ Explain the effect that default ACLs have (instead of the umask)
+ in umask.2. Mention that default ACLs can have an affect in
+ open.2, mknod.2, and mkdir.2.
+
+unshare.2
+ Michael Kerrisk [Florian Weimer]
+ Give the reader a hint that unshare() works on processes or threads
+ See https://bugzilla.kernel.org/show_bug.cgi?id=59281
+
+atexit.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+bsearch.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+cmsg.3
+ Michael Kerrisk [Christopher Head]
+ Fix error in SCM_RIGHTS code sample
+ Remove erroneous second initialization of msg.msg_controllen
+ in the example code for SCM_RIGHTS.
+ See https://bugzilla.kernel.org/show_bug.cgi?id=15952
+
+CPU_SET.3
+ Chris Metcalf
+ Clarify language about "available" cpus
+ The CPU_SET.3 man page uses the adjective "available" when
+ explaining what the argument to CPU_SET() means. This is
+ confusing, since "available" isn't well-defined. The kernel
+ has a set of adjectives (possible, present, online, and active)
+ that qualify cpus, but normally none of these are what the
+ cpu_set_t bit index means: it's just "which cpu", using the
+ kernel's internal numbering system, even if that cpu isn't
+ possible or present.
+
+ This change removes the word "available" and adds a sentence
+ warning that cpu sets may not be contiguous due to dynamic
+ cpu hotplug, etc.
+
+err.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+ftw.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+gethostbyname.3
+ Carlos O'Donell
+ NSS plugins searched first
+ Carlos O'Donell
+ "order" is obsolete
+
+gethostid.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are/aren't thread-safe
+
+getmntent.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are/aren't thread-safe
+
+get_nprocs_conf.3
+ Michael Kerrisk
+ Use exit() rather than return in main()
+
+getopt.3
+ Michael Kerrisk [Guy Harris]
+ Remove crufty BUGS section
+ See https://bugzilla.kernel.org/show_bug.cgi?id=90261
+
+iconv_close.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+inet_ntop.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+longjmp.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+lsearch.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+mcheck.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+on_exit.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+printf.3
+ Michael Kerrisk [Egmont Koblinger]
+ Merge dprintf() and vdprintf() discussion into this page
+ Michael Kerrisk
+ SEE ALSO: add puts(3)
+ Michael Kerrisk
+ Move return value discussion to proper RETURN VALUE section
+
+putpwent.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+qsort.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+regex.3
+ Michael Kerrisk [Laurence Gonsalves]
+ Fix error in description of 'cflags'
+ 'cflags' is a bit mask of *zero* (not one) or more flags.
+
+resolver.3
+ Stéphane Aulery
+ Add info about RES_INSECURE1 and RES_INSECURE2 option in debug mode
+
+scanf.3
+ Joern Heissler
+ Improve description of %n specifier
+
+setjmp.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+setlocale.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that isn't thread-safe
+
+setlogmask.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that isn't thread-safe
+
+sleep.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that isn't thread-safe
+
+strsignal.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that isn't thread-safe
+
+sysconf.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+undocumented.3
+ William Woodruff
+ Remove documented functions
+
+tty_ioctl.4
+ Michael Kerrisk [Denis Du]
+ Fix error in code example
+
+proc.5
+ Michael Kerrisk [Cameron Norman, Vasiliy Kulikov]
+ Document /proc mount options
+ Document the 'hidepid' and 'gid' mount options that were added in
+ Linux 3.3. See https://bugzilla.kernel.org/show_bug.cgi?id=90641
+ Based on text by Vasiliy Kulikov in
+ Documentation/filesystems/proc.txt.
+ Michael Kerrisk [Kirill A. Shutemov]
+ Improve description of /proc/PID/status
+ Guillem Jover
+ Document /proc/PID/exe behaviour on unlinked pathnames
+ Michael Kerrisk [Weijie Yang]
+ Document /proc/PID/status VmPMD
+
+resolv.conf.5
+ Stéphane Aulery [Thomas Hood]
+ Document use-vc option added to glibc 2.14
+ Fix Ubuntu bug #1110781:
+ https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/1110781
+ Stéphane Aulery [Thomas Hood]
+ Document RES_SNGLKUPREOP
+ Fix Ubuntu bug #1110781:
+ https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/1110781
+
+tzfile.5
+ Sam Varshavchik
+ Add various details on version 2 format
+
+aio.7
+ Michael Kerrisk
+ Add details and update URL for OLS 2003 paper on AIO
+
+bootparam.7
+ Michael Kerrisk [Alain Kalker]
+ Update discussion of 'debug' option
+ See https://bugzilla.kernel.org/show_bug.cgi?id=97161
+ Michael Kerrisk
+ Summary of multiple changes: remove cruft from this page.
+ Much of the detail on hardware specifics in this page dates
+ from the 20th century. (The last major update to this page was in
+ man-pages-1.14!) It's hugely out of date now (many of these
+ devices disappeared from the kernel years ago.) So, I've taken
+ a large scythe to the page to remove anything that looks
+ seriously dated. In the process, the page has shrunk to less
+ than 50% of its previous size.
+ Michael Kerrisk
+ Remove "buff=" details
+ This seems to have gone away in Linux 2.2.
+ Michael Kerrisk
+ Remove crufty "Mouse drivers" options
+ Michael Kerrisk
+ Remove crufty "General non-device-specific boot arguments" options
+ Michael Kerrisk
+ Remove crufty "Hard disks" options
+ Michael Kerrisk
+ Remove crufty "mem=" details
+ Michael Kerrisk
+ Remove crufty details on IBM MCA bus devices
+ Michael Kerrisk
+ Remove 'swap=" details
+ This seems to have gone away in Linux 2.2,
+ Michael Kerrisk
+ Remove crufty floppy disk driver options
+ In the specific case of floppy drives: the drivers still
+ exist, but it's been a while since most of saw these devices
+ in the wild. So, just refer the reader to the kernel source
+ file for details. (The detail in this man page was after all
+ originally drawn from that file.)
+ Remove crufty "ISDN drivers" options
+ Michael Kerrisk
+ Remove crufty "line printer driver" options
+ Michael Kerrisk
+ Remove crufty "Serial port drivers" options
+ Michael Kerrisk
+ Remove crufty reference to CONFIG_BUGi386
+ That option disappeared in Linux 2.4.
+ Michael Kerrisk
+ Remove crufty text
+ "bootsetups array" dates from Linux 2.0.
+ Michael Kerrisk
+ Remove crufty "Video hardware" options
+ Michael Kerrisk
+ Remove crufty SCSI device driver options
+
+fanotify.7
+ Michael Kerrisk [Heinrich Schuchardt]
+ Since Linux 3.19, fallocate(2) generates FAN_MODIFY events
+
+inotify.7
+ Michael Kerrisk [Heinrich Schuchardt]
+ Since Linux 3.19, fallocate(2) generates IN_MODIFY events
+
+ip.7
+ Michael Kerrisk
+ Explain how IP_ADD_MEMBERSHIP determines its argument type
+ Michael Kerrisk [Jiri Pirko, Magnus REFTEL]
+ Clarify details of the IP_MULTICAST_IF socket option
+ Michael Kerrisk [Advait Dixi]
+ Remove dubious text that says that SO_PRIORITY sets IP TOS
+ See https://bugzilla.kernel.org/show_bug.cgi?id=35852
+ Michael Kerrisk
+ Relocate misplaced text describing ENOPROTOOPT error
+
+packet.7
+ Graham Shaw
+ Add sll_protocol to list of required fields for outbound packets
+
+pthreads.7
+ Michael Kerrisk [KOSAKI Motohiro]
+ Using thread IDs whose lifetime has expired gives undefined behavior
+ See https://bugzilla.kernel.org/show_bug.cgi?id=53061
+
+raw.7
+ Michael Kerrisk [Tetsuo Handa]
+ For incoming datagrams, sin_port is set to zero
+ Michael Kerrisk
+ Mention sendto(), recvfrom(), and so on when discussing address format
+ This gives the reader a little context for the following
+ discussion of 'sin_port'.
+ Michael Kerrisk
+ Remove crufty reference to <netinet/in.h>
+ Michael Kerrisk
+ Replace reference to RFC 1700 with pointer to IANA protocol number list
+
+signal.7
+ Michael Kerrisk [Steinar H. Gunderson]
+ Clarify that I/O operations on disks are not interrupted by signals
+ See https://bugzilla.kernel.org/show_bug.cgi?id=97721
+
+unix.7
+ Michael Kerrisk [Christophe Lohr]
+ Remove mention of UNIX_PATH_MAX
+ This kernel constant is not exposed to user space.
+ Michael Kerrisk
+ Note the 108 bytes for sun_path is how things are done on Linux
+ And refer the reader to NOTES for discussion of portability.
+
+xattr.7
+ Michael Kerrisk
+ Document EA limits for Btrfs
+ Michael Kerrisk
+ Document VFS-imposed limits on EAs
+ VFS imposes a 255-byte limit on EA names, and a 64kB limit on
+ EA values.
+ Michael Kerrisk
+ The ext[234] block limitation applies to sum of all EAs
+ It is not a per-EA limit.
+ Michael Kerrisk
+ Clarify permissions required to work with 'user' EAs
+ Michael Kerrisk
+ ext2 and ext3 no longer need mounting with 'user_xattr' for user EAs
+ Michael Kerrisk
+ Add various relevant pages to SEE ALSO
+ Michael Kerrisk
+ Add CONFORMING TO section
+ Michael Kerrisk
+ Modify headings to man-pages norms
+ Michael Kerrisk
+ Btrfs also supports extended attributes
+ Michael Kerrisk
+ File capabilities are implemented using *security* attributes
+ Not *system* attributes
+ Michael Kerrisk
+ Describe limit on EA values for JFS, XFS, and Reiserfs
+ Michael Kerrisk
+ Explicitly mention some of the xattr system calls in DESCRIPTION
+ Naming the system calls helps to orient the reader
+
+nscd.8
+ Michael Kerrisk
+ Add mention of 'services' and 'netgroup' databases
+ This makes the page consistent with nscd.conf(5).
+
+
+==================== Changes in man-pages-4.01 ====================
+
+Released: 2015-07-23, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Alexei Starovoitov <ast@plumgrid.com>
+Andries E. Brouwer <Andries.Brouwer@cwi.nl>
+Arjun Shankar <arjun@redhat.com>
+Ashish Sangwan <a.sangwan@samsung.com>
+Ben Woodard <woodard@redhat.com>
+Carlos O'Donell <carlos@redhat.com>
+Christoph Thompson <cjsthompson@gmail.com>
+Cortland Setlow <cortland.setlow@gmail.com>
+Daniel Borkmann <daniel@iogearbox.net>
+David Leppik <dleppik@vocalabs.com>
+Dilyan Palauzov <dilyan.palauzov@aegee.org>
+Doug Klima <cardoe@gentoo.org>
+Eric B Munson <emunson@akamai.com>
+Florian Weimer <fweimer@redhat.com>
+Hack NDo <hackndo@gmail.com>
+Jann Horn <jann@thejh.net>
+Jens Axboe <axboe@fb.com>
+Jian Wen <wenjianhn@gmail.com>
+Joerg Roedel <jroedel@suse.de>
+Julian Orth <ju.orth@gmail.com>
+Kees Cook <keescook@chromium.org>
+Laszlo Ersek <lacos@caesar.elte.hu>
+Marko Myllynen <myllynen@redhat.com>
+Mehdi Aqadjani Memar <m.aqadjanimemar@student.vu.nl>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Michal Hocko <mhocko@suse.cz>
+Mike Frysinger <vapier@gentoo.org>
+Mike Hayward <hayward@loup.net>
+Miklos Szeredi <miklos@szeredi.hu>
+Namhyung Kim <namhyung@gmail.com>
+Namjae Jeon <namjae.jeon@samsung.com>
+Nathan Lynch <nathan_lynch@mentor.com>
+NeilBrown <neilb@suse.de>
+Pádraig Brady <P@draigBrady.com>
+Pavel Machek <pavel@ucw.cz>
+Peter Hurley <peter@hurleysoftware.com>
+Sam Varshavchik <mrsam@courier-mta.com>
+Scot Doyle <lkml14@scotdoyle.com>
+Stephan Mueller <stephan.mueller@atsec.com>
+Tobias Stoeckmann <tobias@stoeckmann.org>
+Tulio Magno Quites Machado Filho <tuliom@linux.vnet.ibm.com>
+Uwe Kleine-König <uwe+debian@kleine-koenig.org>
+Vegard Nossum <vegard.nossum@oracle.com>
+Ville Skyttä <ville.skytta@iki.fi>
+Vince Weaver <vincent.weaver@maine.edu>
+Zeng Linggang <zenglg.jy@cn.fujitsu.com>
+文剑 <wenjianhn@gmail.com>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+bpf.2
+ Alexei Starovoitov, Michael Kerrisk [Daniel Borkmann]
+ New page documenting bpf(2)
+
+__ppc_get_timebase.3
+ Tulio Magno Quites Machado Filho
+ New page documenting __ppc_get_timebase() and __ppc_get_timebase_freq()
+ Glibc 2.16 was released with a new function for the Power
+ architecture that can read its Time Base Register.
+ Glibc 2.17 adds a function to read the frequency at which the Time
+ Base Register of Power processors is updated.
+
+queue.3
+ Michael Kerrisk [David Leppik, Doug Klima]
+ Reimport from latest FreeBSD page
+ Long ago, Doug Klima noted that many macros were not
+ documented in the queue(3) page. Fix by reimporting from
+ latest [1] FreeBSD man page.
+
+ [1] Revision 263142, Modified Fri Mar 14 03:07:51 2014 UTC
+
+ This also fixes https://sourceware.org/bugzilla/show_bug.cgi?id=1506
+
+ This time, I'll learn from past mistakes and not convert
+ from 'mdoc' to 'man' macros.
+ Michael Kerrisk
+ Use subsections in DESCRIPTION
+ Michael Kerrisk
+ Remove SEE ALSO reference to nonexistent tree(3)
+ Michael Kerrisk
+ Use real hyphens in code samples
+ Michael Kerrisk
+ Comment out text for functions not in glibc
+ Michael Kerrisk
+ Replace HISTORY with CONFORMING TO
+
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+rename.2
+ Michael Kerrisk [Miklos Szeredi]
+ Document RENAME_WHITEOUT
+ Heavily based on text by Miklos Szeredi.
+
+
+New and changed links
+---------------------
+
+__ppc_get_timebase_freq.3
+ Tulio Magno Quites Machado Filho
+ New link to new __ppc_get_timebase(3) page
+
+LIST_EMPTY.3
+LIST_FIRST.3
+LIST_FOREACH.3
+LIST_HEAD_INITIALIZER.3
+LIST_INSERT_BEFORE.3
+LIST_NEXT.3
+SLIST_EMPTY.3
+SLIST_ENTRY.3
+SLIST_FIRST.3
+SLIST_FOREACH.3
+SLIST_HEAD.3
+SLIST_HEAD_INITIALIZER.3
+SLIST_INIT.3
+SLIST_INSERT_AFTER.3
+SLIST_INSERT_HEAD.3
+SLIST_NEXT.3
+SLIST_REMOVE.3
+SLIST_REMOVE_HEAD.3
+STAILQ_CONCAT.3
+STAILQ_EMPTY.3
+STAILQ_ENTRY.3
+STAILQ_FIRST.3
+STAILQ_FOREACH.3
+STAILQ_HEAD.3
+STAILQ_HEAD_INITIALIZER.3
+STAILQ_INIT.3
+STAILQ_INSERT_AFTER.3
+STAILQ_INSERT_HEAD.3
+STAILQ_INSERT_TAIL.3
+STAILQ_NEXT.3
+STAILQ_REMOVE.3
+STAILQ_REMOVE_HEAD.3
+TAILQ_CONCAT.3
+TAILQ_EMPTY.3
+TAILQ_FIRST.3
+TAILQ_FOREACH.3
+TAILQ_FOREACH_REVERSE.3
+TAILQ_HEAD_INITIALIZER.3
+TAILQ_INSERT_BEFORE.3
+TAILQ_LAST.3
+TAILQ_NEXT.3
+TAILQ_PREV.3
+TAILQ_SWAP.3
+ Michael Kerrisk
+ New links to queue.3
+
+
+Global changes
+--------------
+
+Various pages
+ Michael Kerrisk [Andries E. Brouwer]
+ Remove "ABI" from "C library/kernel ABI differences" subheadings
+ The "ABI" doesn't really convey anything significant in
+ the title. These subsections are about describing differences
+ between the kernel and (g)libc interfaces.
+
+
+Changes to individual pages
+---------------------------
+
+intro.1
+ Michael Kerrisk [Andries E. Brouwer]
+ Drop intro paragraph on '$?' shell variable
+ As Andries notes, this piece of text is rather out of place in
+ a page that was intended to provide a tutorial introduction for
+ beginners logging in on a Linux system.
+
+locale.1
+ Marko Myllynen
+ A minor output format clarification
+ A minor clarification for the locale output format which was
+ brought up at
+ https://sourceware.org/bugzilla/show_bug.cgi?id=18516.
+
+ For reference, see
+ https://sourceware.org/bugzilla/show_bug.cgi?id=18516
+ http://pubs.opengroup.org/onlinepubs/9699919799/utilities/locale.html
+
+ Add CONFORMING TO section
+
+capget.2
+ Julian Orth
+ Clarify that hdrp->pid==0 is equivalent gettid() not getpid()
+
+chroot.2
+ Jann Horn
+ chroot() is not intended for security; document attack
+ It is unfortunate that this discourages this use of chroot(2)
+ without pointing out alternative solutions - for example,
+ OpenSSH and vsftpd both still rely on chroot(2) for security.
+
+ Bind mounts should theoretically be usable as a replacement, but
+ currently, they have a similar problem (CVE-2015-2925) that hasn't
+ been fixed in ~6 months, so I'd rather not add it to the manpage
+ as a solution before a fix lands.
+
+clock_getres.2
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+eventfd.2
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+execve.2
+ Michael Kerrisk
+ Elaborate on envp/argv as NULL behavior
+
+_exit.2
+ Michael Kerrisk
+ Open stdio frames are not flushed, temporary files are deleted
+ Many years ago, text was added to the page saying that it is
+ implementation-dependent whether stdio streams are flushed and
+ whether temporary are removed. In part, this change appears to
+ be because POSIX.1-2001 added text related to this point.
+ However, that seems to have been an error in POSIX, and the
+ text was subsequently removed for POSIX.1-2008. See
+ https://collaboration.opengroup.org/austin/interps/documents/9984/AI-085.txt
+ Austin Group Interpretation reference 1003.1-2001 #085
+
+fallocate.2
+ Namjae Jeon [Michael Kerrisk]
+ Document FALLOC_FL_INSERT_RANGE
+ Michael Kerrisk
+ Since Linux 4.2, ext4 supports FALLOC_FL_INSERT_RANGE
+
+fcntl.2
+ Michael Kerrisk
+ OFD locks are proposed for inclusion in the next POSIX revision
+
+getrlimit.2
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+getrusage.2
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+gettid.2
+ Michael Kerrisk
+ Note that for a thread group leader, gettid() == getpid()
+
+iopl.2
+ Michael Kerrisk
+ Remove some historical libc5 and glibc 1 details
+ These details are ancient, and long ago ceased to be relevant.
+
+ioprio_set.2
+ Michael Kerrisk [Jens Axboe]
+ Document meaning of ioprio==0
+
+mlock.2
+ Michael Kerrisk [Mehdi Aqadjani Memar]
+ Document another ENOMEM error case
+ ENOMEM can occur if locking/unlocking in the middle of a region
+ would increase the number of VMAs beyond the system limit (64k).
+
+mmap.2
+ Michal Hocko [Eric B Munson]
+ Clarify MAP_POPULATE
+ David Rientjes has noticed that MAP_POPULATE wording might promise
+ much more than the kernel actually provides and intends to provide.
+ The primary usage of the flag is to pre-fault the range. There is
+ no guarantee that no major faults will happen later on. The pages
+ might have been reclaimed by the time the process tries to access
+ them.
+ Michal Hocko [Eric B Munson]
+ Clarify MAP_LOCKED semantics
+ MAP_LOCKED had a subtly different semantic from mmap(2)+mlock(2)
+ since it has been introduced.
+ mlock(2) fails if the memory range cannot get populated to
+ guarantee that no future major faults will happen on the range.
+ mmap(MAP_LOCKED) on the other hand silently succeeds even if
+ the range was populated only partially.
+
+ Fixing this subtle difference in the kernel is rather awkward
+ because the memory population happens after mm locks have been
+ dropped and so the cleanup before returning failure (munlock)
+ could operate on something else than the originally mapped area.
+
+ E.g. speculative userspace page fault handler catching SEGV and
+ doing mmap(fault_addr, MAP_FIXED|MAP_LOCKED) might discard portion
+ of a racing mmap and lead to lost data. Although it is not clear
+ whether such a usage would be valid, mmap page doesn't explicitly
+ describe requirements for threaded applications so we cannot
+ exclude this possibility.
+
+ This patch makes the semantic of MAP_LOCKED explicit and suggests
+ using mmap + mlock as the only way to guarantee no later major
+ page faults.
+ Michael Kerrisk
+ ERRORS: point out that ENOMEM can occur even for munmap()
+
+mprotect.2
+ Michael Kerrisk
+ Note ENOMEM error that can occur when we reach limit on maximum VMAs
+
+open.2
+read.2
+write.2
+ Michael Kerrisk [Mike Hayward]
+ Clarify that O_NONBLOCK is a no-op for regular files and block devices
+
+perf_event_open.2
+ Vince Weaver [Joerg Roedel]
+ Exclude_host/exclude_guest clarification
+ This patch relates to the exclude_host and exclude_guest bits added
+ by the following commit:
+
+ exclude_host, exclude_guest; Linux 3.2
+ commit a240f76165e6255384d4bdb8139895fac7988799
+ Author: Joerg Roedel <joerg.roedel@amd.com>
+ Date: Wed Oct 5 14:01:16 2011 +0200
+
+ perf, core: Introduce attrs to count in either host or guest mode
+
+ The updated manpage text clarifies that the "exclude_host" and
+ "exclude_guest" perf_event_open() attr bits only apply in the
+ context of a KVM environment and are currently x86 only.
+ Vince Weaver
+ Document PERF_SAMPLE_REGS_INTR
+ This patch relates to the addition of PERF_SAMPLE_REGS_INTR
+ support added in the following commit:
+
+ perf_sample_regs_intr; Linux 3.19
+ commit 60e2364e60e86e81bc6377f49779779e6120977f
+ Author: Stephane Eranian <eranian@google.com>
+
+ perf: Add ability to sample machine state on interrupt
+
+ The primary difference between PERF_SAMPLE_REGS_INTR and the
+ existing PERF_SAMPLE_REGS_USER is that the new support will
+ return kernel register values. Also if precise_ip is
+ set higher than 0 then the PEBS register state will be returned
+ rather than the saved interrupt state.
+
+ This patch incorporates feedback from Stephane Eranian and
+ Andi Kleen.
+
+prctl.2
+seccomp.2
+ Michael Kerrisk
+ Clarify that SECCOMP_SET_MODE_STRICT disallows exit_group(2)
+ These days, glibc implements _exit() as a wrapper around
+ exit_group(2). (When seccomp was originally introduced, this was
+ not the case.) Give the reader a clue that, despite what glibc is
+ doing, what SECCOMP_SET_MODE_STRICT permits is the true _exit(2)
+ system call, and not exit_group(2).
+
+pread.2
+read.2
+readv.2
+sendfile.2
+write.2
+ Michael Kerrisk
+ Clarify that Linux limits transfers to a maximum of 0x7ffff000 bytes
+ See https://bugs.debian.org/629994 and
+ https://bugs.debian.org/630029.
+
+pread.2
+ Michael Kerrisk
+ Rewrite RETURN VALUE section
+ (Also drop the text on pwrite() returning zero; that seems bogus.)
+
+ptrace.2
+ Michael Kerrisk [Vegard Nossum]
+ PTRACE_O_TRACEEXIT clarification
+
+readv.2
+ Michael Kerrisk
+ Remove BUGS heading
+ The text on mixing I/O syscalls and stdio is a general point
+ of behavior. It's not a bug as such.
+
+recv.2
+send.2
+ Michael Kerrisk
+ Explain some subtleties of MSG_DONTWAIT versus O_NONBLOCK
+
+rename.2
+ Michael Kerrisk
+ Michael Kerrisk
+ Note that RENAME_NOREPLACE can't be employed with RENAME_EXCHANGE
+
+sched_setaffinity.2
+ Michael Kerrisk
+ Add an example program
+ Michael Kerrisk [Florian Weimer]
+ Explain how to deal with 1024-CPU limitation of glibc's cpu_set_t type
+ Michael Kerrisk
+ Mention the use of the 'isolcpus' kernel boot option
+
+sched_setattr.2
+ Julian Orth
+ Remove a const attribute
+ The attr argument of sched_setattr was documented as const but the
+ kernel will modify the size field of this struct if it contains an
+ invalid value. See the documentation of the size field for details.
+
+seccomp.2
+ Michael Kerrisk
+ SEE ALSO: add bpf(2)
+
+send.2
+ Michael Kerrisk
+ Expand on subtleties of MSG_NOSIGNAL versus ignoring SIGPIPE
+
+sigaltstack.2
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+socket.2
+ Stephan Mueller
+ Update documentation reference for AF_ALG
+
+truncate.2
+ Michael Kerrisk
+ ERRORS: ftruncate() can fail if the file descriptor is not writable
+
+utimensat.2
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+ After research, We think utimensat() and futimens() are thread-safe.
+ But, there are not markings of utimensat() and futimens() in glibc
+ document.
+
+clearenv.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is not thread-safe
+
+dl_iterate_phdr.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+error.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are/aren't thread-safe
+
+fexecve.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+fpurge.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+fread.3
+ Andries E. Brouwer
+ Clarify terminology
+ In the "RETURN VALUE" section the word item is in italics
+ as if it were one of the function parameters. But the word
+ "item" occurs here for the first time, earlier the text
+ uses "element". [Patch improves this.]
+
+fts.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are/aren't thread-safe
+
+getaddrinfo.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+getaddrinfo_a.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+getauxval.3
+ Michael Kerrisk
+ File capabilities also trigger AT_SECURE
+ Michael Kerrisk
+ (Briefly) document AT_HWCAP2
+
+getgrent_r.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are/aren't thread-safe
+
+gethostbyname.3
+ Michael Kerrisk [Laszlo Ersek]
+ Remove mention of IPv6 addresses, which are not supported
+ As reported by Laszlo Ersek:
+
+ gethostbyname(3) fails to resolve the IPv6 address "::1",
+ but the manual page says: "If name is an IPv4 or IPv6 address,
+ no lookup is performed and gethostbyname() simply copies name
+ into the h_name field [...]".
+
+ Debian bug report:
+ http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=455762
+
+ glibc bug report:
+ http://sourceware.org/bugzilla/show_bug.cgi?id=5479
+
+ SUSv3 link for gethostbyname(3):
+ http://www.opengroup.org/onlinepubs/000095399/functions/gethostbyname.html
+
+ It seems that the glibc behavior is conformant, and the manual
+ page is in error.
+
+getifaddrs.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+getnameinfo.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+getnetent_r.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+getprotoent.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+getprotoent_r.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+getpw.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+getpwent_r.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are/aren't thread-safe
+
+getrpcent.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are/aren't thread-safe
+
+getrpcent_r.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+getrpcport.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+getservent.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+getservent_r.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+gsignal.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+key_setsecret.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+malloc_get_state.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+malloc_info.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+malloc_stats.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+malloc_trim.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+MB_LEN_MAX.3
+ Michael Kerrisk
+ Clarify meaning of MB_LEN_MAX
+ Michael Kerrisk [Pádraig Brady]
+ MB_LEN_MAX is 16 in modern glibc versions
+
+memcpy.3
+ Michael Kerrisk
+ NOTES: describe the glibc 2.13 changes that revealed buggy applications
+ Adding a note on this point seems worthwhile as a way of
+ emphasizing the point that the buffers must not overlap.
+
+mq_notify.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+perror.3
+ Michael Kerrisk
+ Some wording improvements and clarifications
+
+profil.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is not thread-safe
+
+psignal.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+pthread_attr_init.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+ Michael Kerrisk
+ Use "%zd" for printing size_t in example code
+
+pthread_attr_setaffinity_np.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+pthread_cancel.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+pthread_cleanup_push.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+pthread_create.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+pthread_detach.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+pthread_getattr_np.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+pthread_join.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+pthread_setname_np.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+pthread_tryjoin_np.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+putgrent.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+rcmd.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are/aren't thread-safe
+
+resolver.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+rpc.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+rpmatch.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+sem_close.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+sem_open.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+setaliasent.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are/aren't thread-safe
+
+setlocale.3
+ Marko Myllynen
+ Update CONFORMING TO
+ http://pubs.opengroup.org/onlinepubs/9699919799/functions/setlocale.html
+
+setlocale.3
+ Marko Myllynen
+ Tweak C/POSIX locale portability description
+ As discussed earlier, the current description might be a little
+ bit too stringent, let's avoid the issue by describing the
+ portability aspect on a slightly higher level.
+
+ References:
+
+ http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap06.html
+ http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap07.html
+ http://pubs.opengroup.org/onlinepubs/9699919799/functions/setlocale.html
+
+shm_open.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+strfmon.3
+ Marko Myllynen
+ Document strfmon_l(3)
+ Describe strfmon_l(3).
+
+ http://pubs.opengroup.org/onlinepubs/9699919799/functions/strfmon.html
+ Marko Myllynen
+ Fix CONFORMING TO
+ AFAICS strfmon(3) is now defined in POSIX and the glibc
+ implementation is as specified there.
+
+ http://pubs.opengroup.org/onlinepubs/9699919799/functions/strfmon.html
+ Marko Myllynen
+ Rewrite the example
+ I think the example is more accurate when we use the exact
+ locale names and also the Euro sign where appropriate.
+
+xcrypt.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+xdr.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+console_codes.4
+ Scot Doyle [Pavel Machek, Michael Kerrisk]
+ Add CSI sequence for cursor blink interval
+ Add a Console Private CSI sequence to specify the current
+ console's cursor blink interval. The interval is specified
+ as a number of milliseconds until the next cursor display
+ state toggle, from 50 to 65535.
+
+null.4
+ Michael Kerrisk
+ Note that reads from /dev/zero are interruptible since Linux 2.6.31
+
+core.5
+ Michael Kerrisk
+ Mention 'coredump_filter' boot option
+
+host.conf.5
+ Michael Kerrisk
+ Wording fix: s/resolv+/the resolver library/
+ The term "resolv+" seems to be historical cruft.
+
+hosts.equiv.5
+ Carlos O'Donell
+ Fix format, clarify IdM needs, and provide examples.
+ In some recent work with a Red Hat customer I had the opportunity
+ to discuss the fine nuances of the ruserok() function and related
+ API which are used to implement rlogin and rsh.
+
+ It came to my attention after working with QE on some automated
+ internal testing that there were no good examples in the hosts.equiv
+ manual page showing how the format was supposed to work for this
+ file and for ~/.rhosts, worse the "format" line showed that there
+ should be spaces between arguments when that would clearly lead
+ to incorrect behaviour. In addition some things that the format
+ allows you to write are just wrong like "-host -user" which makes
+ no sense since the host is already rejected, and should be written
+ as "host -user" instead. I added notes in the example to make it
+ clear that "-host -user" is invalid.
+
+ I fixed three things:
+
+ (a) The format line.
+ - Either +, or [-]hostname, or +@netgrp or -@netgrp.
+ - Either +, or [-]username, or +@netgrp or -@netgrp.
+ - You must specify something in the hostname portion so remove
+ optional brackets.
+
+ (b) Clarify language around credentials
+ - If the host is not trusted you must provide credentials to
+ the login system and that could be anything really and it
+ depends on your configuration e.g. PAM or whatever IdM you have.
+
+ (c) Provide real-world examples
+ - Provide several real world examples and some corner case
+ examples for how you would write something. Hopefully others
+ can add examples as they see fit.
+ Michael Kerrisk [Carlos O'Donell, Arjun Shankar]
+ Improve explanation in EXAMPLE
+
+locale.5
+ Marko Myllynen
+ Document map to_inpunct, map to_outpunct
+ See e.g. fa_IR for reference.
+ Marko Myllynen
+ Document class in LC_CTYPE
+ See e.g. the locale zh_CN and
+
+ http://en.cppreference.com/w/cpp/string/wide/towctrans
+ http://en.cppreference.com/w/cpp/string/wide/wctrans
+ Marko Myllynen
+ Add iconv(1) reference
+ Marko Myllynen
+ Document character transliteration
+ See e.g. da_DK for reference.
+
+ (Not sure should we actually provide an example here?)
+ Marko Myllynen
+ Document era keywords
+ This patch completes the LC_TIME section - since these era
+ keywords are so tightly coupled, I'm providing them as a
+ single patch.
+
+ Based on
+ http://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap07.html
+ http://www.open-std.org/jtc1/SC22/WG20/docs/n972-14652ft.pdf
+ Marko Myllynen
+ Document default_missing
+ Marko Myllynen
+ Document outdigit and alt_digits
+ See e.g. fa_IR for reference.
+ Marko Myllynen
+ Refer to locale(7) more prominently
+ It's probably a good idea to refer to locale(7) so that a reader
+ can check what a category is about before describing them in
+ detail.
+ Marko Myllynen
+ Document charclass and charconv
+ See e.g. the locales ja_JP and ko_KR and
+
+ http://en.cppreference.com/w/cpp/string/wide/towctrans
+ http://en.cppreference.com/w/cpp/string/wide/wctrans
+ Marko Myllynen
+ Copy is not exclusive in LC_CTYPE and LC_COLLATE
+ See e.g. da_DK for reference.
+ Marko Myllynen
+ Remove the FIXME for timezone
+ The timezone of LC_TIME is not in POSIX, only 6 (out of ~300)
+ glibc locales define it, the glibc code comment below from
+ glibc.git/programs/ld-time.c seems to suggest it's not a good
+ idea, and there's been a proposal in upstream [1] to remove the
+ existing timezone definitions from glibc locales so I think
+ it's actually better to leave this one undocumented:
+
+ /* XXX We don't perform any tests on the timezone value since this is
+ simply useless, stupid $&$!@... */
+
+ 1) https://sourceware.org/ml/libc-alpha/2015-06/msg00098.html
+
+ Move the remaining LC_COLLATE FIXMEs together while at it.
+ Marko Myllynen
+ Fix country_isbn format
+ Both plain numbers and Unicode code points are used in
+ glibc locales but checking the code reveals that country_isbn
+ is handled like the rest of its category expect for country_num
+ which was clarified earlier.
+ Marko Myllynen
+ Sort according to the standard
+ Sort the options so that those defined in POSIX are listed first,
+ then followed by those defined in ISO/IEC TR 14652 in the order
+ of common convention in many widely used glibc locales.
+
+ Actual descriptions are unchanged.
+
+ http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap07.html
+ Marko Myllynen
+ Refer to strftime(3) where appropriate
+ The relationship between the locale time format syntax
+ and strftime() cannot be considered as obvious.
+ Marko Myllynen
+ Document map "totitle"
+ See e.g. locales/i18n for reference.
+ Michael Kerrisk [Marko Myllynen]
+ Remove BUGS section saying man page is not complete
+ To some degree, this is true of many pages. And anyway, this
+ page is much better after recent work by Marko.
+
+proc.5
+ Michael Kerrisk
+ List /proc/vmstat fields
+ Michael Kerrisk
+ Tweak /proc/vmstat text
+ Michael Kerrisk
+ Add /proc/crypto entry with a pointer to further information
+ Michael Kerrisk [Kees Cook]
+ Document /proc/sys/kernel/sysctl_writes_strict
+ Based on text in Documentation/sysctl/kernel.txt.
+ Michael Kerrisk
+ Move misordered /proc/[pid]/timers entry
+ Michael Kerrisk
+ Refer to bpf(2) for explanation of /proc/sys/net/core/bpf_jit_enable
+
+repertoiremap.5
+ Marko Myllynen
+ Symbolic names AKA mnemonics
+ A long time ago in glibc, repertoire maps were used (but they
+ were removed already in 2000), those mapping files were named
+ as mnemonics, so "mnemonic" is a term that would almost
+ certainly come up if somebody studies glibc side (perhaps even
+ the related standards like ISO 9945 [which I don't have access
+ to]) so I thought it's worth to mention to term in the man page
+ to make sure we're talking about the same thing, otherwise
+ someone might wonder is that something different or not.
+
+ IOW, symbolic names and mnemonics are often used interchangeably,
+ let's mention the other often used term in the page, too.
+
+capabilities.7
+ Michael Kerrisk
+ CAP_SYS_ADMIN allows calling bpf(2)
+
+locale.7
+ Marko Myllynen
+ LC_CTYPE determines transliteration rules on glibc systems
+
+packet.7
+ 文剑 [Cortland Setlow]
+ Fix description of binding a packet socket to an interface
+
+pty.7
+ NeilBrown [Peter Hurley]
+ Clarify asynchronous nature of PTY I/O
+ A PTY is not like a pipe - there may be delayed between data
+ being written at one end and it being available at the other.
+
+ This became particularly apparent after
+ commit f95499c3030f
+ ("n_tty: Don't wait for buffer work in read() loop")
+ in Linux 3.12
+
+ See also the mail thread at https://lkml.org/lkml/2015/5/1/35
+ Date Mon, 04 May 2015 12:32:04 -0400
+ From Peter Hurley <>
+ Subject Re: [PATCH bisected regression] input_available_p()
+ sometimes says 'no' when it should say 'yes'
+
+rtld-audit.7
+ Ben Woodard
+ Use correct printf() specifier for pointer types
+ In the example code you used %x rather than %p in the example
+ code for an audit library. The problem is that it truncates the
+ pointers on 64b platforms. So you get something like:
+
+ la_symbind64(): symname = strrchr sym->st_value = 0x7f4b8a3f8960
+ ndx = 222 flags = 0x0 refcook = 8b53e5c8 defcook = 8b537e30
+
+ rather than:
+
+ la_symbind64(): symname = fclose sym->st_value = 0x7fa452dd49b0
+ ndx = 1135 flags = 0x0 refcook = 0x7fa453f395c8 defcook = 0x7fa453f32e30
+
+ This has bitten me a handful of times when playing around with
+ audit test libraries to investigate its behavior.
+
+sched.7
+ Michael Kerrisk
+ Remove ancient, wildly optimistic prediction about future of RT patches
+ It seems the patches were not merged by 2.6.30...
+
+socket.7
+ Michael Kerrisk
+ SEE ALSO: add bpf(2)
+
+vdso.7
+ Nathan Lynch [Mike Frysinger]
+ Update for ARM
+ The 32-bit ARM architecture in Linux has gained a vDSO as of the
+ 4.1 release. (I was the primary author.)
+
+ Document the symbols exported by the ARM VDSO.
+
+ Accepted kernel submission:
+ http://lists.infradead.org/pipermail/linux-arm-kernel/2015-March/332573.html
projects / thirdparty / man-pages.git / blobdiff