Start of man-pages-3.30: updating Changes and Changes.old

1 files changed, 207 insertions, 0 deletions

diff --git a/Changes.old b/Changes.old
index ad70cfd35..68f634ba2 100644
--- a/Changes.old
+++ b/Changes.old
@@ -20823,3 +20823,210 @@ sigevent.7
 suffixes.7
     Michael Kerrisk
         Change explanation of ".rpm" to "RPM software package"
+
+
+==================== Changes in man-pages-3.29 ====================
+
+Released: 2010-10-19, Detroit
+
+
+Contributors
+------------
+
+The following people contributed notes, ideas, or patches that have
+been incorporated in changes in this release:
+
+Balazs Scheidler <bazsi@balabit.hu>
+David Prevot <davidp@altern.org>
+Denis Barbier <bouzim@gmail.com>
+Guillem Jover <guillem@hadrons.org>
+Ivana Varekova <varekova@redhat.com>
+Lennart Poettering <mzxreary@0pointer.de>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Sam Varshavchik <mrsam@courier-mta.com>
+Simon Paillard <simon.paillard@resel.enst-bretagne.fr>
+Stephan Mueller <stephan.mueller@atsec.com>
+Thomas Jarosch <thomas.jarosch@intra2net.com>
+Yuri Kozlov <yuray@komyakino.ru>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+subpage_prot.2
+    Michael Kerrisk
+        New page documenting the PowerPC-specific subpage_prot(2)
+
+aio_init.3
+    Michael Kerrisk
+        New page documenting aio_init(3)
+
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+posix_fadvise.2
+    Michael Kerrisk
+        Document the architecture-specific arm_fadvise64_64() system call
+            This ARM-specific system call fixes the argument ordering
+            for that architecture. Since Linux 2.6.14.
+
+sync_file_range.2
+    Michael Kerrisk
+        Document the architecture-specific sync_file_range2() system call
+            As described in commit edd5cd4a9424f22b0fa08bef5e299d41befd5622,
+            the sync_file_range() argument order is broken for some
+            architectures (PowerPC, ARM, tile). The remedy was a different
+            system call using the right argument order on those architectures.
+
+psignal.3
+    Guillem Jover
+        Document psiginfo()
+            psiginfo() was added to glibc in version 2.10.
+    Michael Kerrisk
+        Add details, VERSIONS, and BUGS for psiginfo()
+
+ip.7
+    Balazs Scheidler
+        Document IP_RECVORIGDSTADDR
+        Document IP_TRANSPARENT
+    Michael Kerrisk
+        Document IP_FREEBIND
+            Text based on input from Lennart Poettering and Balazs Scheidler.
+            See https://bugzilla.kernel.org/show_bug.cgi?id=20082
+
+
+New and changed links
+---------------------
+
+arm_fadvise64_64.2
+    Michael Kerrisk
+        New link to posix_fadvise.2
+
+arm_sync_file_range.2, sync_file_range2.2
+    Michael Kerrisk
+        New links to sync_file_range.2
+
+arrm_fadvise.2
+    Michael Kerrisk
+        New link to posix_fadvise.2
+
+psiginfo.3
+    Guillem Jover
+        New link to psignal.3
+
+
+Global changes
+--------------
+
+Many pages
+    Michael Kerrisk
+        global fix: s/Unix/UNIX/
+            The man pages were rather inconsistent in the use of "Unix"
+            versus "UNIX". Let's go with the trademark usage.
+
+Various pages
+    Michael Kerrisk
+        Global fix: s/pseudo-terminal/pseudoterminal/
+
+grantpt.3, ptsname.3, unlockpt.3, pts.4
+    Michael Kerrisk
+        Global fix: s/pty/pseudoterminal/
+
+recv.2, cmsg.3, unix.7
+    Michael Kerrisk
+        global fix: s/UNIX socket/UNIX domain socket/
+
+fmtmsg.3, gethostbyname.3, termios.3
+    Michael Kerrisk
+        Global fix: s/Unixware/UnixWare/
+
+
+Changes to individual pages
+---------------------------
+
+inotify_rm_watch.2
+    Michael Kerrisk
+        SYNOPSIS: fix type of 'wd' argument
+
+posix_fadvise.2
+    Michael Kerrisk
+        Rewrite VERSIONS, noting that the system call is fadvise64()
+
+syscalls.2
+    Michael Kerrisk
+        Add the PowerPC-specific subpage_prot() system call
+        Add sync_file_range2()
+
+truncate.2
+    Michael Kerrisk
+        Fix feature test macros
+
+aio_cancel.3
+aio_error.3
+aio_fsync.3
+aio_read.3
+aio_return.3
+aio_suspend.3
+aio_write.3
+    Michael Kerrisk
+        SEE ALSO: Add lio_listio(3)
+
+gai_cancel.3
+gai_error.3
+gai_suspend.3
+    Michael Kerrisk
+        Make these into links
+            In the previous release, these files were accidentally made copies
+            of getaddrinfo_a.3, instead of being made as link files.
+
+getifaddrs.3
+    Thomas Jarosch
+        Prevent possible NULL pointer access in example program
+
+malloc.3
+    Michael Kerrisk
+        Emphasize that malloc() and realloc() do not initialize allocated memory
+
+malloc_hook.3
+    Ivana Varekova
+        Warn that these functions are deprecated
+
+strcpy.3
+    Michael Kerrisk
+        Formatting fixes in strncpy() example implementation code
+
+ip.7
+    Michael Kerrisk
+        Reword NOTES on Linux-specific options
+
+sigevent.7
+    Michael Kerrisk
+        SEE ALSO: Add aio_read(3), aio_write(3), and lio_listio(3)
+
+unix.7
+    Michael Kerrisk
+        Document the autobind feature
+    Michael Kerrisk
+        Fix description of abstract socket names
+            As reported by Lennart Poettering:
+                The part about "abstract" sockets is misleading as it suggests
+                that the sockaddr returned by getsockname() would necessarily
+                have the size of sizeof(struct sockaddr), which however is not
+                the case: getsockname() returns exactly the sockaddr size that
+                was passed in on bind(). In particular, two sockets that are
+                bound to the same sockaddr but different sizes are completely
+                independent.
+            See https://bugzilla.kernel.org/show_bug.cgi?id=19812
+    Michael Kerrisk
+        Fix description of "pathname" sockets
+            As reported by Lennart Poettering:
+               The part about "pathname" sockets suggests usage of
+               sizeof(sa_family_t) + strlen(sun_path) + 1
+               for calculating the sockaddr size. Due to alignment/padding
+               this is probably not a good idea. Instead, one should use
+               offsetof(struct sockaddr_un, sun_path) + strlen() + 1
+               or something like that.
+            See https://bugzilla.kernel.org/show_bug.cgi?id=19812