From b0a36622df64075acf5709b4a89353012be1dd0b Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Sun, 26 Nov 2017 11:28:07 +0100 Subject: [PATCH] Changes.old: wsfix Signed-off-by: Michael Kerrisk --- Changes.old | 58 ++++++++++++++++++++++++++--------------------------- 1 file changed, 29 insertions(+), 29 deletions(-) diff --git a/Changes.old b/Changes.old index 7fea0cfad..cfeb673fc 100644 --- a/Changes.old +++ b/Changes.old @@ -13005,7 +13005,7 @@ dl_iterate_phdr.3 crypt.3 mtk, after a Fedora downstream patch Describe additional encryption algorithms. - See also: https://bugzilla.redhat.com/show_bug.cgi?id=428280. + See also: https://bugzilla.redhat.com/show_bug.cgi?id=428280. errno.3 mtk @@ -15090,19 +15090,19 @@ execve.2 Michael Kerrisk Linux now imposes a floor on the ARG_MAX limit Starting with Linux 2.6.23, the ARG_MAX limit became - settable via (1/4 of) RLIMIT_STACK. This broke ABI - compatibility if RLIMIT_STACK was set such that ARG_MAX - was < 32 pages. Document the fact that since 2.6.25 - Linux imposes a floor on ARG_MAX, so that the old limit - of 32 pages is guaranteed. + settable via (1/4 of) RLIMIT_STACK. This broke ABI + compatibility if RLIMIT_STACK was set such that ARG_MAX + was < 32 pages. Document the fact that since 2.6.25 + Linux imposes a floor on ARG_MAX, so that the old limit + of 32 pages is guaranteed. For some background on the changes to ARG_MAX in - kernels 2.6.23 and 2.6.25, see: + kernels 2.6.23 and 2.6.25, see: http://sourceware.org/bugzilla/show_bug.cgi?id=5786 http://bugzilla.kernel.org/show_bug.cgi?id=10095 http://thread.gmane.org/gmane.linux.kernel/646709/focus=648101, checked into 2.6.25 as - commit a64e715fc74b1a7dcc5944f848acc38b2c4d4ee2. + commit a64e715fc74b1a7dcc5944f848acc38b2c4d4ee2. Also some reordering/rewording of the discussion of ARG_MAX. @@ -15110,16 +15110,16 @@ fallocate.2 Michael Kerrisk Note lack of glibc wrapper; caller must use syscall(2) Glibc doesn't (and quite probably won't) include a - wrapper for this system call. Therefore, point out that - potential callers will need to use syscall(2), and rewrite - the RETURN VALUE text to show things as they would be if - syscall() is used. + wrapper for this system call. Therefore, point out that + potential callers will need to use syscall(2), and rewrite + the RETURN VALUE text to show things as they would be if + syscall() is used. Michael Kerrisk Refer reader to posix_fallocate(3) for portable interface Add a para to start of page that points out that this is the low-level, Linux-specific API, and point the reader to - posix_fallocate(3) for the portable API. + posix_fallocate(3) for the portable API. getdents.2 readdir.3 @@ -15148,7 +15148,7 @@ getdents.2 Michael Kerrisk s/dirent/linux_dirent/ The structure isn't currently defined in glibc headers, - and the kernel name of the structure is 'linux_dirent' (as + and the kernel name of the structure is 'linux_dirent' (as was already used in some, but not all, places in this page). getrlimit.2 @@ -15190,9 +15190,9 @@ umount.2 Michael Kerrisk Split umount*() out into a separate page The length of this page means that it's becoming difficult - to parse which info is specific to mount() versus - umount()/umount2(), so split the umount material out into - its own page. + to parse which info is specific to mount() versus + umount()/umount2(), so split the umount material out into + its own page. pause.2 Michael Kerrisk @@ -15206,12 +15206,12 @@ readdir.2 Michael Kerrisk s/dirent/old_linux_dirent/ Nowadays, this is the name of the structure in the - kernel sources. + kernel sources. Michael Kerrisk Remove words "which may change" These words are slightly bogus: although the interface - is obsolete, for ABI-compatibility reasons, the kernel folk - should never be changing this interface. + is obsolete, for ABI-compatibility reasons, the kernel folk + should never be changing this interface. Michael Kerrisk Remove header files from SYNOPSIS glibc doesn't provide any support for readdir(2), @@ -15261,7 +15261,7 @@ sigpending.2 Michael Kerrisk Explain how thread's pending signal set is defined The pending set is the union of per-thread pending signals - and process-wide pending signals. + and process-wide pending signals. sigprocmask.2 Michael Kerrisk @@ -15333,7 +15333,7 @@ floor.3 hsearch.3 André Goddard Rosa Call hdestroy() after using hash table created by hcreate(), - for the sake of completeness + for the sake of completeness mq_getattr.3 Michael Kerrisk @@ -22121,7 +22121,7 @@ Newly documented interfaces in existing pages fstatat.2 Michael Kerrisk [David Howells] Document AT_NO_AUTOMOUNT - This flag was added in Linux 2.6.38. + This flag was added in Linux 2.6.38. lseek.2 Michael Kerrisk [Eric Blake, Sunil Mushran] @@ -29819,7 +29819,7 @@ socket.7 Neil Horman Document the SO_RXQ_OVFL socket option Michael Kerrisk - Add kernel version number for SO_RXQ_OVFL + Add kernel version number for SO_RXQ_OVFL New and changed links @@ -30106,12 +30106,12 @@ sync.8 "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 + 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. + 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 ---------------------------