From: Alejandro Colomar Date: Sun, 4 Dec 2022 19:38:06 +0000 (+0100) Subject: Many pages: wfix X-Git-Tag: man-pages-6.02~67 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=b324e17d3208c940622ab192609b836928d5aa8d;p=thirdparty%2Fman-pages.git Many pages: wfix Refer consistently to software versions. In most cases, it is done as . In the case of Linux and glibc, use the project name, instead of other terms such as 'kernel' or 'library'. I found the uses of inconsistent language with the following: $ find man* -type f \ | xargs grep -i '\(since\|before\|after\|until\|to\|from\|in\|between\|version\|with\) \(kernel\|version\|2\.\|3\.\|4\.\|5\.\)' \ | sort However, I might have missed some cases. Anyway, 99% consistency is pretty good consistency. We'll fix the remaining cases as we see them. Signed-off-by: Alejandro Colomar --- diff --git a/man1/ldd.1 b/man1/ldd.1 index 9860c47cfc..56e5d9fa5d 100644 --- a/man1/ldd.1 +++ b/man1/ldd.1 @@ -83,7 +83,7 @@ and perhaps to execution of the program itself. .\" try_trace "$file" .\" in glibc 2.15, for example), but many distro versions of .\" ldd seem to remove that code path from the script. -(In glibc versions before 2.27, +(Before glibc 2.27, .\" glibc commit eedca9772e99c72ab4c3c34e43cc764250aa3e3c the upstream .B ldd diff --git a/man1/pldd.1 b/man1/pldd.1 index ce8bba1de3..5c0b818ae0 100644 --- a/man1/pldd.1 +++ b/man1/pldd.1 @@ -77,7 +77,7 @@ $ \fBgdb \-ex "set confirm off" \-ex "set height 0" \-ex "info shared" \e\fP .EE .in .SH BUGS -From glibc 2.19 to 2.29, +From glibc 2.19 to glibc 2.29, .B pldd was broken: it just hung when executed. .\" glibc commit 1a4c27355e146b6d8cc6487b998462c7fdd1048f diff --git a/man2/_exit.2 b/man2/_exit.2 index 9e9796f439..1ea5b80d43 100644 --- a/man2/_exit.2 +++ b/man2/_exit.2 @@ -111,7 +111,7 @@ to the parent process are performed only if this is the last thread in the thread group. .\" _exit() is used by pthread_exit() to terminate the calling thread .PP -In glibc up to version 2.3, the +Up to glibc 2.3, the .BR _exit () wrapper function invoked the kernel system call of the same name. Since glibc 2.3, the wrapper function invokes diff --git a/man2/accept.2 b/man2/accept.2 index 333d25ceb8..d852212e54 100644 --- a/man2/accept.2 +++ b/man2/accept.2 @@ -257,7 +257,7 @@ may be seen during a trace. The .BR accept4 () system call is available starting with Linux 2.6.28; -support in glibc is available starting with version 2.10. +support in glibc is available starting with glibc 2.10. .SH STANDARDS .BR accept (): POSIX.1-2001, POSIX.1-2008, diff --git a/man2/access.2 b/man2/access.2 index bbd806a5aa..1f5809b401 100644 --- a/man2/access.2 +++ b/man2/access.2 @@ -276,11 +276,11 @@ Write access was requested to an executable which is being executed. .SH VERSIONS .BR faccessat () -was added to Linux in kernel 2.6.16; -library support was added to glibc in version 2.4. +was added in Linux 2.6.16; +library support was added in glibc 2.4. .PP .BR faccessat2 () -was added to Linux in version 5.8. +was added in Linux 5.8. .SH STANDARDS .BR access (): SVr4, 4.3BSD, POSIX.1-2001, POSIX.1-2008. @@ -398,7 +398,7 @@ by making use of the .BR faccessat2 () system call where it is provided by the underlying kernel. .PP -In kernel 2.4 (and earlier) there is some strangeness in the handling of +In Linux 2.4 (and earlier) there is some strangeness in the handling of .B X_OK tests for superuser. If all categories of execute permission are disabled @@ -421,13 +421,13 @@ returns 0 for such files. Early 2.6 kernels (up to and including 2.6.3) also behaved in the same way as kernel 2.4. .PP -In kernels before 2.6.20, +Before Linux 2.6.20, these calls ignored the effect of the .B MS_NOEXEC flag if it was used to .BR mount (2) the underlying filesystem. -Since kernel 2.6.20, the +Since Linux 2.6.20, the .B MS_NOEXEC flag is honored. .SH SEE ALSO diff --git a/man2/adjtimex.2 b/man2/adjtimex.2 index c106928e92..209562b382 100644 --- a/man2/adjtimex.2 +++ b/man2/adjtimex.2 @@ -472,13 +472,13 @@ An attempt was made to set .I buf.freq to a value outside the range (\-33554432, +33554432). .\" From a quick glance, it appears there was no clamping or range check -.\" for buf.freq in kernels before 2.0 +.\" for buf.freq before Linux 2.0 .TP .BR EINVAL " (kernels before Linux 2.6.26)" An attempt was made to set .I buf.offset to a value outside the permitted range. -In kernels before Linux 2.0, the permitted range was (\-131072, +131072). +Before Linux 2.0, the permitted range was (\-131072, +131072). From Linux 2.0 onwards, the permitted range was (\-512000, +512000). .TP .B EINVAL diff --git a/man2/alloc_hugepages.2 b/man2/alloc_hugepages.2 index b1bd0e31c1..8903cbe06e 100644 --- a/man2/alloc_hugepages.2 +++ b/man2/alloc_hugepages.2 @@ -25,7 +25,7 @@ The system calls .BR alloc_hugepages () and .BR free_hugepages () -were introduced in Linux 2.5.36 and removed again in 2.5.54. +were introduced in Linux 2.5.36 and removed again in Linux 2.5.54. They existed only on i386 and ia64 (when built with .BR CONFIG_HUGETLB_PAGE ). In Linux 2.4.20, the syscall numbers exist, @@ -117,7 +117,7 @@ in the three variables HugePages_Total, HugePages_Free, Hugepagesize. These extinct system calls were specific to Linux on Intel processors. .SH NOTES These system calls are gone; -they existed only in Linux 2.5.36 through to 2.5.54. +they existed only in Linux 2.5.36 through to Linux 2.5.54. Now the hugetlbfs filesystem can be used instead. Memory backed by huge pages (if the CPU supports them) is obtained by using diff --git a/man2/bdflush.2 b/man2/bdflush.2 index 07ebeb9f2e..6bc8442ad9 100644 --- a/man2/bdflush.2 +++ b/man2/bdflush.2 @@ -94,7 +94,7 @@ Caller does not have the .B CAP_SYS_ADMIN capability. .SH VERSIONS -Since version 2.23, glibc no longer supports this obsolete system call. +Since glibc 2.23, glibc no longer supports this obsolete system call. .SH STANDARDS .BR bdflush () is Linux-specific and should not be used in programs diff --git a/man2/bpf.2 b/man2/bpf.2 index e92fa29b51..2923262bfa 100644 --- a/man2/bpf.2 +++ b/man2/bpf.2 @@ -1116,7 +1116,7 @@ files in the kernel source tree. .PP The kernel contains a just-in-time (JIT) compiler that translates eBPF bytecode into native machine code for better performance. -In kernels before Linux 4.15, +Before Linux 4.15, the JIT compiler is disabled by default, but its operation can be controlled by writing one of the following integer strings to the file diff --git a/man2/brk.2 b/man2/brk.2 index 92321ea0fa..31c167c569 100644 --- a/man2/brk.2 +++ b/man2/brk.2 @@ -35,7 +35,7 @@ Feature Test Macro Requirements for glibc (see ! (_POSIX_C_SOURCE >= 200112L)) .\" (_XOPEN_SOURCE >= 500 || .\" _XOPEN_SOURCE && _XOPEN_SOURCE_EXTENDED) && - From glibc 2.12 to 2.19: + From glibc 2.12 to glibc 2.19: _BSD_SOURCE || _SVID_SOURCE || ((_XOPEN_SOURCE >= 500) && ! (_POSIX_C_SOURCE >= 200112L)) diff --git a/man2/cacheflush.2 b/man2/cacheflush.2 index d80e75b2cf..aeea4dd581 100644 --- a/man2/cacheflush.2 +++ b/man2/cacheflush.2 @@ -128,7 +128,7 @@ instead of .I void * for the parameters. .SH BUGS -Linux kernels older than version 2.6.11 ignore the +Linux kernels older than Linux 2.6.11 ignore the .I addr and .I nbytes diff --git a/man2/capget.2 b/man2/capget.2 index 8148a7d815..32f00ce4d4 100644 --- a/man2/capget.2 +++ b/man2/capget.2 @@ -8,7 +8,7 @@ .\" Modified 2004-06-21, aeb .\" Modified 2008-04-28, morgan of kernel.org .\" Update in line with addition of file capabilities and -.\" 64-bit capability sets in kernel 2.6.2[45]. +.\" 64-bit capability sets in Linux 2.6.2[45]. .\" Modified 2009-01-26, andi kleen .\" .TH capget 2 (date) "Linux man-pages (unreleased)" @@ -100,7 +100,7 @@ and .I struct __user_cap_data_struct names because the typedefs are only pointers. .PP -Kernels prior to 2.6.25 prefer +Kernels prior to Linux 2.6.25 prefer 32-bit capabilities with version .BR _LINUX_CAPABILITY_VERSION_1 . Linux 2.6.25 added 64-bit capability sets, with version @@ -234,7 +234,7 @@ For kernels lacking VFS support, the .B CAP_SETPCAP capability is required. -(A bug in kernels before 2.6.11 meant that this error could also +(A bug in kernels before Linux 2.6.11 meant that this error could also occur if a thread without this capability tried to change its own capabilities by specifying the .I pid diff --git a/man2/chmod.2 b/man2/chmod.2 index 3bd2af6906..1171786cac 100644 --- a/man2/chmod.2 +++ b/man2/chmod.2 @@ -39,11 +39,11 @@ Feature Test Macro Requirements for glibc (see Since glibc 2.24: _POSIX_C_SOURCE >= 199309L .\" || (_XOPEN_SOURCE && _XOPEN_SOURCE_EXTENDED) - Glibc 2.19 to 2.23 + Glibc 2.19 to glibc 2.23 _POSIX_C_SOURCE - Glibc 2.16 to 2.19: + Glibc 2.16 to glibc 2.19: _BSD_SOURCE || _POSIX_C_SOURCE - Glibc 2.12 to 2.16: + Glibc 2.12 to glibc 2.16: _BSD_SOURCE || _XOPEN_SOURCE >= 500 || _POSIX_C_SOURCE >= 200809L Glibc 2.11 and earlier: @@ -301,8 +301,8 @@ The file is marked immutable or append-only. The named file resides on a read-only filesystem. .SH VERSIONS .BR fchmodat () -was added to Linux in kernel 2.6.16; -library support was added to glibc in version 2.4. +was added in Linux 2.6.16; +library support was added in glibc 2.4. .SH STANDARDS .BR chmod (), .BR fchmod (): diff --git a/man2/chown.2 b/man2/chown.2 index cd81f96cdf..09cc2dce2d 100644 --- a/man2/chown.2 +++ b/man2/chown.2 @@ -107,8 +107,8 @@ this also should happen when root does the the Linux behavior depends on the kernel version, and since Linux 2.2.13, root is treated like other users. .\" In Linux 2.0 kernels, superuser was like everyone else -.\" In 2.2, up to 2.2.12, these bits were not cleared for superuser. -.\" Since 2.2.13, superuser is once more like everyone else. +.\" In Linux 2.2, up to Linux 2.2.12, these bits were not cleared for superuser. +.\" Since Linux 2.2.13, superuser is once more like everyone else. In case of a non-group-executable file (i.e., one for which the .B S_IXGRP bit is not set) the @@ -279,8 +279,8 @@ The file is marked immutable or append-only. The named file resides on a read-only filesystem. .SH VERSIONS .BR fchownat () -was added to Linux in kernel 2.6.16; -library support was added to glibc in version 2.4. +was added in Linux 2.6.16; +library support was added in glibc 2.4. .SH STANDARDS .BR chown (), .BR fchown (), @@ -396,7 +396,7 @@ and .BR lchown () wrapper functions transparently deal with the variations across kernel versions. .PP -In versions of Linux prior to 2.1.81 (and distinct from 2.1.46), +Before Linux 2.1.81 (except 2.1.46), .BR chown () did not follow symbolic links. Since Linux 2.1.81, diff --git a/man2/clock_nanosleep.2 b/man2/clock_nanosleep.2 index e74ca616f1..5afc2025c8 100644 --- a/man2/clock_nanosleep.2 +++ b/man2/clock_nanosleep.2 @@ -176,7 +176,7 @@ The kernel does not support sleeping against this The .BR clock_nanosleep () system call first appeared in Linux 2.6. -Support is available in glibc since version 2.1. +Support is available since glibc 2.1. .SH STANDARDS POSIX.1-2001, POSIX.1-2008. .SH NOTES diff --git a/man2/clone.2 b/man2/clone.2 index a3e6188fd8..f04d713d17 100644 --- a/man2/clone.2 +++ b/man2/clone.2 @@ -10,7 +10,7 @@ .\" Modified 10 June 1995 by Andries Brouwer .\" Modified 25 April 1998 by Xavier Leroy .\" Modified 26 Jun 2001 by Michael Kerrisk -.\" Mostly upgraded to 2.4.x +.\" Mostly upgraded to Linux 2.4.x .\" Added prototype for sys_clone() plus description .\" Added CLONE_THREAD with a brief description of thread groups .\" Added CLONE_PARENT and revised entire page remove ambiguity @@ -22,7 +22,7 @@ .\" Modified 26 Jun 2001 by Michael Kerrisk .\" Updated notes for 2.4.7+ behavior of CLONE_THREAD .\" Modified 15 Oct 2002 by Michael Kerrisk -.\" Added description for CLONE_NEWNS, which was added in 2.4.19 +.\" Added description for CLONE_NEWNS, which was added in Linux 2.4.19 .\" Slightly rephrased, aeb. .\" Modified 1 Feb 2003 - added CLONE_SIGHAND restriction, aeb. .\" Modified 1 Jan 2004 - various updates, aeb @@ -465,7 +465,7 @@ is nonsensical and disallowed. .TP .BR CLONE_DETACHED " (historical)" For a while (during the Linux 2.5 development series) -.\" added in 2.5.32; removed in 2.6.0-test4 +.\" added in Linux 2.5.32; removed in Linux 2.6.0-test4 there was a .B CLONE_DETACHED flag, @@ -665,7 +665,7 @@ This flag can't be specified in conjunction with .TP .BR CLONE_NEWNET " (since Linux 2.6.24)" (The implementation of this flag was completed only -by about kernel version 2.6.29.) +by about Linux 2.6.29.) .IP If .B CLONE_NEWNET @@ -779,8 +779,8 @@ or For security reasons, .\" commit e66eded8309ebf679d3d3c1f5820d1f2ca332c71 .\" https://lwn.net/Articles/543273/ -.\" The fix actually went into 3.9 and into 3.8.3. However, user namespaces -.\" were, for practical purposes, unusable in earlier 3.8.x because of the +.\" The fix actually went into Linux 3.9 and into Linux 3.8.3. However, user namespaces +.\" were, for practical purposes, unusable in earlier Linux 3.8.x because of the .\" various filesystems that didn't support userns. .B CLONE_NEWUSER cannot be specified in conjunction with @@ -848,7 +848,7 @@ that did this.) The store operation completes before the clone call returns control to user space. .TP -.BR CLONE_PID " (Linux 2.0 to 2.5.15)" +.BR CLONE_PID " (Linux 2.0 to Linux 2.5.15)" If .B CLONE_PID is set, the child process is created with the same process ID as @@ -1590,7 +1590,7 @@ In the Linux 2.4.x series, .B CLONE_THREAD generally does not make the parent of the new thread the same as the parent of the calling process. -However, for kernel versions 2.4.7 to 2.4.18 the +However, from Linux 2.4.7 to Linux 2.4.18 the .B CLONE_THREAD flag implied the .B CLONE_PARENT diff --git a/man2/close_range.2 b/man2/close_range.2 index acafc0eba7..143970387e 100644 --- a/man2/close_range.2 +++ b/man2/close_range.2 @@ -75,7 +75,7 @@ Insufficient kernel memory was available. .SH VERSIONS .BR close_range () first appeared in Linux 5.9. -Library support was added in glibc in version 2.34. +Library support was added in glibc 2.34. .SH STANDARDS .BR close_range () is a nonstandard function that is also present on FreeBSD. diff --git a/man2/connect.2 b/man2/connect.2 index 9e462ccc59..86dfd98702 100644 --- a/man2/connect.2 +++ b/man2/connect.2 @@ -86,7 +86,7 @@ set to .BR AF_UNSPEC ; thereafter, the socket can be connected to another address. .RB ( AF_UNSPEC -is supported on Linux since kernel 2.2.) +is supported since Linux 2.2.) .SH RETURN VALUE If the connection or binding succeeds, zero is returned. On error, \-1 is returned, and diff --git a/man2/copy_file_range.2 b/man2/copy_file_range.2 index 1360338d96..ac74d9a07d 100644 --- a/man2/copy_file_range.2 +++ b/man2/copy_file_range.2 @@ -188,7 +188,7 @@ system call first appeared in Linux 4.5, but glibc 2.27 provides a user-space emulation when it is not available. .\" https://sourceware.org/git/?p=glibc.git;a=commit;f=posix/unistd.h;h=bad7a0c81f501fbbcc79af9eaa4b8254441c4a1f .PP -A major rework of the kernel implementation occurred in 5.3. +A major rework of the kernel implementation occurred in Linux 5.3. Areas of the API that weren't clearly defined were clarified and the API bounds are much more strictly checked than on earlier kernels. Applications should target the behaviour and requirements of 5.3 kernels. @@ -197,7 +197,7 @@ Since Linux 5.12, cross-filesystem copies can be achieved when both filesystems are of the same type, and that filesystem implements support for it. -See BUGS for behavior prior to 5.12. +See BUGS for behavior prior to Linux 5.12. .SH STANDARDS The .BR copy_file_range () @@ -223,7 +223,7 @@ such as the use of reflinks (i.e., two or more inodes that share pointers to the same copy-on-write disk blocks) or server-side-copy (in the case of NFS). .SH BUGS -In Linux kernels 5.3 to 5.11, +In Linux 5.3 to Linux 5.11, cross-filesystem copies were implemented by the kernel, if the operation was not supported by individual filesystems. However, on some virtual filesystems, diff --git a/man2/create_module.2 b/man2/create_module.2 index a5b8fb03c2..b9163ec112 100644 --- a/man2/create_module.2 +++ b/man2/create_module.2 @@ -16,7 +16,7 @@ create_module \- create a loadable module entry .fi .SH DESCRIPTION .IR Note : -This system call is present only in kernels before Linux 2.6. +This system call is present only before Linux 2.6. .PP .BR create_module () attempts to create a loadable module entry and reserve the kernel memory @@ -46,7 +46,7 @@ enough for the module. .B ENOSYS .BR create_module () is not supported in this version of the kernel -(e.g., the kernel is version 2.6 or later). +(e.g., Linux 2.6 or later). .TP .B EPERM The caller was not privileged @@ -54,7 +54,7 @@ The caller was not privileged .B CAP_SYS_MODULE capability). .SH VERSIONS -This system call is present on Linux only up until kernel 2.4; +This system call is present only up until Linux 2.4; it was removed in Linux 2.6. .\" Removed in Linux 2.5.48 .SH STANDARDS @@ -63,7 +63,7 @@ is Linux-specific. .SH NOTES This obsolete system call is not supported by glibc. No declaration is provided in glibc headers, but, through a quirk of history, -glibc versions before 2.23 did export an ABI for this system call. +glibc versions before glibc 2.23 did export an ABI for this system call. Therefore, in order to employ this system call, it was sufficient to manually declare the interface in your code; alternatively, you could invoke the system call using diff --git a/man2/delete_module.2 b/man2/delete_module.2 index 8c30fe3910..f4b57e2bee 100644 --- a/man2/delete_module.2 +++ b/man2/delete_module.2 @@ -167,7 +167,7 @@ The .BR delete_module () system call is not supported by glibc. No declaration is provided in glibc headers, but, through a quirk of history, -glibc versions before 2.23 did export an ABI for this system call. +glibc versions before glibc 2.23 did export an ABI for this system call. Therefore, in order to employ this system call, it is (before glibc 2.23) sufficient to manually declare the interface in your code; diff --git a/man2/dup.2 b/man2/dup.2 index 73e0a452ec..c65d153ae0 100644 --- a/man2/dup.2 +++ b/man2/dup.2 @@ -199,9 +199,8 @@ in .BR getrlimit (2)). .SH VERSIONS .BR dup3 () -was added to Linux in version 2.6.27; -glibc support is available starting with -version 2.9. +was added in Linux 2.6.27; +glibc support is available since glibc 2.9. .SH STANDARDS .BR dup (), .BR dup2 (): diff --git a/man2/epoll_create.2 b/man2/epoll_create.2 index 22485e6846..d7d92d917b 100644 --- a/man2/epoll_create.2 +++ b/man2/epoll_create.2 @@ -100,14 +100,14 @@ The system-wide limit on the total number of open files has been reached. There was insufficient memory to create the kernel object. .SH VERSIONS .BR epoll_create () -was added to the kernel in version 2.6. -Library support is provided in glibc starting with version 2.3.2. +was added in Linux 2.6. +Library support is provided in glibc 2.3.2. .PP .\" To be precise: kernel 2.5.44. .\" The interface should be finalized by Linux kernel 2.5.66. .BR epoll_create1 () -was added to the kernel in version 2.6.27. -Library support is provided in glibc starting with version 2.9. +was added in Linux 2.6.27. +Library support is provided in glibc 2.9. .SH STANDARDS .BR epoll_create () and diff --git a/man2/epoll_ctl.2 b/man2/epoll_ctl.2 index dbe6c0bb21..f02e5ff45d 100644 --- a/man2/epoll_ctl.2 +++ b/man2/epoll_ctl.2 @@ -371,10 +371,10 @@ This error can occur if refers to, for example, a regular file or a directory. .SH VERSIONS .BR epoll_ctl () -was added to the kernel in version 2.6. +was added to in Linux 2.6. .\" To be precise: kernel 2.5.44. .\" The interface should be finalized by Linux kernel 2.5.66. -Library support is provided in glibc starting with version 2.3.2. +Library support is provided in glibc 2.3.2. .SH STANDARDS .BR epoll_ctl () is Linux-specific. @@ -384,7 +384,7 @@ The interface supports all file descriptors that support .BR poll (2). .SH BUGS -In kernel versions before 2.6.9, the +Before Linux 2.6.9, the .B EPOLL_CTL_DEL operation required a non-null pointer in .IR event , @@ -394,7 +394,7 @@ Since Linux 2.6.9, can be specified as NULL when using .BR EPOLL_CTL_DEL . -Applications that need to be portable to kernels before 2.6.9 +Applications that need to be portable to kernels before Linux 2.6.9 should specify a non-null pointer in .IR event . .PP diff --git a/man2/epoll_wait.2 b/man2/epoll_wait.2 index 59ad4fa3ff..70c4e29936 100644 --- a/man2/epoll_wait.2 +++ b/man2/epoll_wait.2 @@ -209,17 +209,17 @@ file descriptor, or is less than or equal to zero. .SH VERSIONS .BR epoll_wait () -was added to the kernel in version 2.6. +was added in Linux 2.6. .\" To be precise: kernel 2.5.44. -.\" The interface should be finalized by Linux kernel 2.5.66. -Library support is provided in glibc starting with version 2.3.2. +.\" The interface should be finalized by Linux 2.5.66. +Library support is provided in glibc 2.3.2. .PP .BR epoll_pwait () -was added to Linux in kernel 2.6.19. -Library support is provided in glibc starting with version 2.6. +was added in Linux 2.6.19. +Library support is provided in glibc 2.6. .PP .BR epoll_pwait2 () -was added to Linux in kernel 5.11. +was added in Linux 5.11. .SH STANDARDS .BR epoll_wait (), .BR epoll_pwait (), @@ -274,7 +274,7 @@ wrapper function specifies this argument as a fixed value (equal to .IR sizeof(sigset_t) ). .SH BUGS -In kernels before 2.6.37, a +Before Linux 2.6.37, a .I timeout value larger than approximately .I LONG_MAX / HZ diff --git a/man2/eventfd.2 b/man2/eventfd.2 index 592b8536bb..d63ecdc42d 100644 --- a/man2/eventfd.2 +++ b/man2/eventfd.2 @@ -62,7 +62,7 @@ to achieve the same result. Provide semaphore-like semantics for reads from the new file descriptor. See below. .PP -In Linux up to version 2.6.26, the +Up to Linux 2.6.26, the .I flags argument is unused, and must be specified as zero. .PP @@ -247,13 +247,13 @@ There was insufficient memory to create a new eventfd file descriptor. .SH VERSIONS .BR eventfd () -is available on Linux since kernel 2.6.22. -Working support is provided in glibc since version 2.8. +is available since Linux 2.6.22. +Working support is provided since glibc 2.8. .\" eventfd() is in glibc 2.7, but reportedly does not build The .BR eventfd2 () -system call (see NOTES) is available on Linux since kernel 2.6.27. -Since version 2.9, the glibc +system call (see NOTES) is available since Linux 2.6.27. +Since glibc 2.9, the .BR eventfd () wrapper will employ the .BR eventfd2 () diff --git a/man2/execve.2 b/man2/execve.2 index 35eba65f10..5606fffbb3 100644 --- a/man2/execve.2 +++ b/man2/execve.2 @@ -384,14 +384,14 @@ constant (either defined in or available at run time using the call .IR "sysconf(_SC_ARG_MAX)" ). .PP -On Linux prior to kernel 2.6.23, the memory used to store the +Before Linux 2.6.23, the memory used to store the environment and argument strings was limited to 32 pages (defined by the kernel constant .BR MAX_ARG_PAGES ). On architectures with a 4-kB page size, this yields a maximum size of 128\ kB. .PP -On kernel 2.6.23 and later, most architectures support a size limit +On Linux 2.6.23 and later, most architectures support a size limit derived from the soft .B RLIMIT_STACK resource limit (see @@ -400,15 +400,15 @@ that is in force at the time of the .BR execve () call. (Architectures with no memory management unit are excepted: -they maintain the limit that was in effect before kernel 2.6.23.) +they maintain the limit that was in effect before Linux 2.6.23.) This change allows programs to have a much larger argument and/or environment list. -.\" For some background on the changes to ARG_MAX in kernels 2.6.23 and -.\" 2.6.25, see: +.\" For some background on the changes to ARG_MAX in Linux 2.6.23 and +.\" Linux 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. +.\" checked into Linux 2.6.25 as commit a64e715fc74b1a7dcc5944f848acc38b2c4d4ee2. For these architectures, the total size is limited to 1/4 of the allowed stack size. (Imposing the 1/4-limit @@ -679,7 +679,7 @@ ignores the set-user-ID and set-group-ID bits on scripts. .\" Linux versions have also had other security holes in .\" .BR execve () .\" that could be exploited for denial of service by a suitably crafted -.\" ELF binary. There are no known problems with 2.0.34 or 2.2.15. +.\" ELF binary. There are no known problems with Linux 2.0.34 or Linux 2.2.15. .SS execve() and EAGAIN A more detailed explanation of the .B EAGAIN @@ -701,10 +701,10 @@ and that change caused the process to exceed its .B RLIMIT_NPROC resource limit (i.e., the number of processes belonging to the new real UID exceeds the resource limit). -From Linux 2.6.0 to 3.0, this caused the +From Linux 2.6.0 to Linux 3.0, this caused the .BR set*uid () call to fail. -(Prior to 2.6, +(Before Linux 2.6, .\" commit 909cc4ae86f3380152a18e2a3c44523893ee11c4 the resource limit was not imposed on processes that changed their user IDs.) @@ -774,7 +774,7 @@ Since UNIX\ V7, both are NULL. .\" Linux versions have also had other security holes in .\" .BR execve () .\" that could be exploited for denial of service by a suitably crafted -.\" ELF binary. There are no known problems with 2.0.34 or 2.2.15. +.\" ELF binary. There are no known problems with Linux 2.0.34 or Linux 2.2.15. .SH EXAMPLES The following program is designed to be execed by the second program below. It just echoes its command-line arguments, one per line. diff --git a/man2/execveat.2 b/man2/execveat.2 index b8c3be2375..4c21ebebb9 100644 --- a/man2/execveat.2 +++ b/man2/execveat.2 @@ -147,8 +147,8 @@ is relative and is a file descriptor referring to a file other than a directory. .SH VERSIONS .BR execveat () -was added to Linux in kernel 3.19. -Library support was added to glibc in version 2.34. +was added in Linux 3.19. +Library support was added in glibc 2.34. .SH STANDARDS The .BR execveat () diff --git a/man2/fallocate.2 b/man2/fallocate.2 index 7bdd70aa3d..14a5b8a52b 100644 --- a/man2/fallocate.2 +++ b/man2/fallocate.2 @@ -390,7 +390,7 @@ or but the file referred to by .I fd is not a regular file. -.\" There was an inconsistency in 3.15-rc1, that should be resolved so that all +.\" There was an inconsistency in Linux 3.15-rc1, that should be resolved so that all .\" filesystems use this error for this case. (Tytso says ex4 will change.) .\" http://thread.gmane.org/gmane.comp.file-systems.xfs.general/60485/focus=5521 .\" From: Michael Kerrisk (man-pages @@ -465,11 +465,11 @@ but the file referred to by is currently being executed. .SH VERSIONS .BR fallocate () -is available on Linux since kernel 2.6.23. -Support is provided by glibc since version 2.10. +is available since Linux 2.6.23. +Support is provided since glibc 2.10. The .B FALLOC_FL_* -flags are defined in glibc headers only since version 2.18. +flags are defined in glibc headers only since glibc 2.18. .\" See http://sourceware.org/bugzilla/show_bug.cgi?id=14964 .SH STANDARDS .BR fallocate () diff --git a/man2/fanotify_init.2 b/man2/fanotify_init.2 index 34cf035249..ec1976efac 100644 --- a/man2/fanotify_init.2 +++ b/man2/fanotify_init.2 @@ -434,7 +434,7 @@ An invalid value was passed in or .IR event_f_flags . .B FAN_ALL_INIT_FLAGS -(deprecated since Linux kernel version 4.20) +(deprecated since Linux 4.20) .\" commit 23c9deeb3285d34fd243abb3d6b9f07db60c3cf4 defines all allowable bits for .IR flags . @@ -461,8 +461,7 @@ The fanotify API is available only if the kernel was configured with The operation is not permitted because the caller lacks a required capability. .SH VERSIONS .BR fanotify_init () -was introduced in version 2.6.36 of the Linux kernel and enabled in version -2.6.37. +was introduced in Linux 2.6.36 and enabled in Linux 2.6.37. .PP Prior to Linux 5.13, .\" commit 7cea2a3c505e87a9d6afc78be4a7f7be636a73a7 @@ -519,7 +518,7 @@ listening process itself generated the event. .SH STANDARDS This system call is Linux-specific. .SH BUGS -The following bug was present in Linux kernels before version 3.18: +The following bug was present before Linux 3.18: .IP \(bu 3 .\" Fixed by commit 0b37e097a648aa71d4db1ad108001e95b69a2da4 The @@ -527,7 +526,7 @@ The is ignored when passed in .IR event_f_flags . .PP -The following bug was present in Linux kernels before version 3.14: +The following bug was present before Linux 3.14: .IP \(bu 3 .\" Fixed by commit 48149e9d3a7e924010a0daab30a6197b7d7b6580 The diff --git a/man2/fanotify_mark.2 b/man2/fanotify_mark.2 index f49759ed4e..c1285987ea 100644 --- a/man2/fanotify_mark.2 +++ b/man2/fanotify_mark.2 @@ -763,8 +763,7 @@ This error can be returned only with an fanotify group that identifies filesystem objects by file handles. .SH VERSIONS .BR fanotify_mark () -was introduced in version 2.6.36 of the Linux kernel and enabled in version -2.6.37. +was introduced in Linux 2.6.36 and enabled in Linux 2.6.37. .SH STANDARDS This system call is Linux-specific. .SH NOTES @@ -814,7 +813,7 @@ events for both the ELF binary and interpreter, respectively: .EE .in .SH BUGS -The following bugs were present in Linux kernels before version 3.16: +The following bugs were present in before Linux 3.16: .IP \(bu 3 .\" Fixed by commit 0a8dd2db579f7a0ac7033d6b857c3d5dbaa77563 If diff --git a/man2/fcntl.2 b/man2/fcntl.2 index 6c51d7171b..228bba5ec7 100644 --- a/man2/fcntl.2 +++ b/man2/fcntl.2 @@ -297,7 +297,7 @@ covers bytes .IR l_start + l_len up to and including .IR l_start \-1. -This is supported by Linux since kernel versions 2.4.21 and 2.5.49. +This is supported since Linux 2.4.21 and Linux 2.5.49. .PP The .I l_type @@ -776,8 +776,7 @@ would report the socket as having an "exceptional condition".) .\" refers to a terminal device, then SIGIO .\" signals are sent to the foreground process group of the terminal. .IP -The following was true in 2.6.x kernels up to and including -kernel 2.6.11: +The following was true in Linux 2.6.x up to and including Linux 2.6.11: .RS .IP If a nonzero value is given to @@ -931,7 +930,7 @@ is the signal to send instead, and in this case additional info is available to the signal handler if installed with .BR SA_SIGINFO . .\" -.\" The following was true only up until 2.6.11: +.\" The following was true only up until Linux 2.6.11: .\" .\" Additionally, passing a nonzero value to .\" .B F_SETSIG @@ -1060,7 +1059,7 @@ values is specified in the integer Take out a read lease. This will cause the calling process to be notified when the file is opened for writing or is truncated. -.\" The following became true in kernel 2.6.10: +.\" The following became true in Linux 2.6.10: .\" See the man-pages-2.09 Changelog for further info. A read lease can be placed only on a file descriptor that is opened read-only. @@ -1316,7 +1315,7 @@ so that multiple notifications can be queued. .B NOTE: New applications should use the .I inotify -interface (available since kernel 2.6.13), +interface (available since Linux 2.6.13), which provides a much superior interface for obtaining notifications of filesystem events. See @@ -1904,7 +1903,7 @@ wrapper function transparently employs the more recent system call where it is available. .\" .SS Record locks -Since kernel 2.0, there is no interaction between the types of lock +Since Linux 2.0, there is no interaction between the types of lock placed by .BR flock (2) and @@ -2020,7 +2019,7 @@ operation avoids this problem. .\" indicate that ANY negative PGID value will cause F_GETOWN .\" to misinterpret the return as an error. Some other architectures .\" seem to have the same range check as i386. -Since glibc version 2.11, glibc makes the kernel +Since glibc 2.11, glibc makes the kernel .B F_GETOWN problem invisible by implementing .B F_GETOWN diff --git a/man2/flock.2 b/man2/flock.2 index 388057e99b..42fc1c5952 100644 --- a/man2/flock.2 +++ b/man2/flock.2 @@ -131,7 +131,7 @@ possibly implemented in terms of .BR fcntl (2), appears on most UNIX systems. .SH NOTES -Since kernel 2.0, +Since Linux 2.0, .BR flock () is implemented as a system call in its own right rather than being emulated in the GNU C library as a call to @@ -186,7 +186,7 @@ and occurs on many other implementations.) .\" Kernel 2.5.21 changed things a little: during lock conversion .\" it is now the highest priority process that will get the lock -- mtk .SS NFS details -In Linux kernels up to 2.6.11, +Up to Linux 2.6.11, .BR flock () does not lock files over NFS (i.e., the scope of locks was limited to the local system). @@ -223,7 +223,7 @@ see the discussion of the option in .BR nfs (5). .SS CIFS details -In Linux kernels up to 5.4, +Up to Linux 5.4, .BR flock () is not propagated over SMB. A file with such locks will not appear locked for remote clients. diff --git a/man2/fork.2 b/man2/fork.2 index 51caf5868a..5c94d4b535 100644 --- a/man2/fork.2 +++ b/man2/fork.2 @@ -268,7 +268,7 @@ is implemented using copy-on-write pages, so the only penalty that it incurs is the time and memory required to duplicate the parent's page tables, and to create a unique task structure for the child. .SS C library/kernel differences -Since version 2.3.3, +Since glibc 2.3.3, .\" nptl/sysdeps/unix/sysv/linux/fork.c rather than invoking the kernel's .BR fork () diff --git a/man2/futex.2 b/man2/futex.2 index c8504ff978..b815056d23 100644 --- a/man2/futex.2 +++ b/man2/futex.2 @@ -273,7 +273,7 @@ is one of the following: .\" .TP .BR FUTEX_WAIT " (since Linux 2.6.0)" -.\" Strictly speaking, since some time in 2.5.x +.\" Strictly speaking, since some time in Linux 2.5.x This operation tests that the value at the futex word pointed to by the address .I uaddr @@ -405,7 +405,7 @@ are ignored. .\" .TP .BR FUTEX_FD " (from Linux 2.6.0 up to and including Linux 2.6.25)" -.\" Strictly speaking, from Linux 2.5.x to 2.6.25 +.\" Strictly speaking, from Linux 2.5.x to Linux 2.6.25 This operation creates a file descriptor that is associated with the futex at .IR uaddr . @@ -1336,7 +1336,7 @@ operation. .\" Related to the preceding, Darren proposed that somewhere, man-pages .\" should document the following point: .\" -.\" While the Linux kernel, since 2.6.31, supports requeueing of +.\" While the Linux kernel, since Linux 2.6.31, supports requeueing of .\" priority-inheritance (PI) aware mutexes via the .\" FUTEX_WAIT_REQUEUE_PI and FUTEX_CMP_REQUEUE_PI futex operations, .\" the glibc implementation does not yet take full advantage of this. @@ -1524,7 +1524,7 @@ or .B FUTEX_WAIT_BITSET operation was interrupted by a signal (see .BR signal (7)). -In kernels before Linux 2.6.22, this error could also be returned for +Before Linux 2.6.22, this error could also be returned for a spurious wakeup; since Linux 2.6.22, this no longer happens. .TP .B EINVAL diff --git a/man2/futimesat.2 b/man2/futimesat.2 index d7de23f679..d91f1daca8 100644 --- a/man2/futimesat.2 +++ b/man2/futimesat.2 @@ -101,8 +101,8 @@ is relative and is a file descriptor referring to a file other than a directory. .SH VERSIONS .BR futimesat () -was added to Linux in kernel 2.6.16; -library support was added to glibc in version 2.4. +was added in Linux 2.6.16; +library support was added in glibc 2.4. .SH STANDARDS This system call is nonstandard. It was implemented from a specification that was proposed for POSIX.1, diff --git a/man2/get_kernel_syms.2 b/man2/get_kernel_syms.2 index 4bdd98b443..15e59d99ea 100644 --- a/man2/get_kernel_syms.2 +++ b/man2/get_kernel_syms.2 @@ -16,7 +16,7 @@ get_kernel_syms \- retrieve exported kernel and module symbols .fi .SH DESCRIPTION .BR Note : -This system call is present only in kernels before Linux 2.6. +This system call is present only before Linux 2.6. .PP If .I table @@ -56,7 +56,7 @@ There is only one possible error return: .BR get_kernel_syms () is not supported in this version of the kernel. .SH VERSIONS -This system call is present on Linux only up until kernel 2.4; +This system call is present only up until Linux 2.4; it was removed in Linux 2.6. .\" Removed in Linux 2.5.48 .SH STANDARDS @@ -65,7 +65,7 @@ is Linux-specific. .SH NOTES This obsolete system call is not supported by glibc. No declaration is provided in glibc headers, but, through a quirk of history, -glibc versions before 2.23 did export an ABI for this system call. +glibc versions before glibc 2.23 did export an ABI for this system call. Therefore, in order to employ this system call, it was sufficient to manually declare the interface in your code; alternatively, you could invoke the system call using diff --git a/man2/get_mempolicy.2 b/man2/get_mempolicy.2 index 90e65b537f..d055fcb7ad 100644 --- a/man2/get_mempolicy.2 +++ b/man2/get_mempolicy.2 @@ -238,7 +238,7 @@ cases.) .SH VERSIONS The .BR get_mempolicy () -system call was added to the Linux kernel in version 2.6.7. +system call was added in Linux 2.6.7. .SH STANDARDS This system call is Linux-specific. .SH NOTES diff --git a/man2/getcpu.2 b/man2/getcpu.2 index 32a5e926db..2ef34b7c3c 100644 --- a/man2/getcpu.2 +++ b/man2/getcpu.2 @@ -66,7 +66,7 @@ is set to indicate the error. Arguments point outside the calling process's address space. .SH VERSIONS .BR getcpu () -was added in kernel 2.6.19 for x86-64 and i386. +was added in Linux 2.6.19 for x86-64 and i386. Library support was added in glibc 2.29 (Earlier glibc versions did not provide a wrapper for this system call, necessitating the use of @@ -117,7 +117,7 @@ the returned information would be out of date. The caching mechanism was considered to cause problems when migrating threads between CPUs, and so the argument is now ignored. .\" -.\" ===== Before kernel 2.6.24: ===== +.\" ===== Before Linux 2.6.24: ===== .\" .I tcache .\" is a pointer to a .\" .IR "struct getcpu_cache" @@ -133,7 +133,7 @@ migrating threads between CPUs, and so the argument is now ignored. .\" will use it to speed up operation. .\" The information inside the cache is private to the system call .\" and should not be accessed by the user program. -.\" The information placed in the cache can change between kernel releases. +.\" The information placed in the cache can change between Linux releases. .\" .\" When no cache is specified .\" .BR getcpu () diff --git a/man2/gethostname.2 b/man2/gethostname.2 index 38c3e262c5..efaa4b8c1e 100644 --- a/man2/gethostname.2 +++ b/man2/gethostname.2 @@ -33,7 +33,7 @@ Feature Test Macro Requirements for glibc (see _XOPEN_SOURCE >= 500 || _POSIX_C_SOURCE >= 200112L || /* Glibc 2.19 and earlier */ _BSD_SOURCE .\" The above is something of a simplification -.\" also in glibc before 2.3 there was a bit churn +.\" also before glibc 2.3 there was a bit churn .fi .PP .BR sethostname (): @@ -98,7 +98,7 @@ is larger than the maximum allowed size. .RB "(glibc " gethostname ()) .I len is smaller than the actual size. -(Before version 2.1, glibc uses +(Before glibc 2.1, glibc uses .B EINVAL for this case.) .TP @@ -149,8 +149,8 @@ set to in this case, a terminating null byte is not included in the returned .IR name . .PP -Versions of glibc before 2.2 -.\" At least glibc 2.0 and 2.1, older versions not checked +Versions of glibc before glibc 2.2 +.\" At least glibc 2.0 and glibc 2.1, older versions not checked handle the case where the length of the .I nodename was greater than or equal to diff --git a/man2/getitimer.2 b/man2/getitimer.2 index 3c86acfd52..093752b620 100644 --- a/man2/getitimer.2 +++ b/man2/getitimer.2 @@ -227,7 +227,7 @@ timer may expire before the signal from a previous expiration has been delivered. The second signal in such an event will be lost. .PP -On Linux kernels before 2.6.16, timer values are represented in jiffies. +Before Linux 2.6.16, timer values are represented in jiffies. If a request is made set a timer with a value whose jiffies representation exceeds .B MAX_SEC_IN_JIFFIES @@ -243,10 +243,10 @@ the kernel uses a different internal representation for times, and this ceiling is removed. .PP On certain systems (including i386), -Linux kernels before version 2.6.12 have a bug which will produce +Linux kernels before Linux 2.6.12 have a bug which will produce premature timer expirations of up to one jiffy under some circumstances. -This bug is fixed in kernel 2.6.12. -.\" 4 Jul 2005: It looks like this bug may remain in 2.4.x. +This bug is fixed in Linux 2.6.12. +.\" 4 Jul 2005: It looks like this bug may remain in Linux 2.4.x. .\" http://lkml.org/lkml/2005/7/1/165 .PP POSIX.1-2001 says that @@ -254,10 +254,10 @@ POSIX.1-2001 says that should fail if a .I tv_usec value is specified that is outside of the range 0 to 999999. -However, in kernels up to and including 2.6.21, +However, up to and including Linux 2.6.21, Linux does not give an error, but instead silently adjusts the corresponding seconds value for the timer. -From kernel 2.6.22 onward, +From Linux 2.6.22 onward, this nonconformance has been repaired: an improper .I tv_usec diff --git a/man2/getpagesize.2 b/man2/getpagesize.2 index 10776a7382..18181fc28e 100644 --- a/man2/getpagesize.2 +++ b/man2/getpagesize.2 @@ -24,7 +24,7 @@ Feature Test Macro Requirements for glibc (see .nf Since glibc 2.20: _DEFAULT_SOURCE || ! (_POSIX_C_SOURCE >= 200112L) - Glibc 2.12 to 2.19: + Glibc 2.12 to glibc 2.19: _BSD_SOURCE || ! (_POSIX_C_SOURCE >= 200112L) Before glibc 2.12: _BSD_SOURCE || _XOPEN_SOURCE >= 500 diff --git a/man2/getpid.2 b/man2/getpid.2 index bb6f0f4abb..b0b78ed6f5 100644 --- a/man2/getpid.2 +++ b/man2/getpid.2 @@ -55,7 +55,7 @@ flag in .BR clone (2). .\" .SS C library/kernel differences -From glibc version 2.3.4 up to and including version 2.24, +From glibc 2.3.4 up to and including Linux 2.24, the glibc wrapper function for .BR getpid () cached PIDs, @@ -111,7 +111,7 @@ Furthermore, the complexity of the caching code had been the source of a few bugs within glibc over the years. .PP Because of the aforementioned problems, -since glibc version 2.25, the PID cache is removed: +since glibc 2.25, the PID cache is removed: .\" commit c579f48edba88380635ab98cb612030e3ed8691e .\" https://sourceware.org/glibc/wiki/Release/2.25#pid_cache_removal calls to diff --git a/man2/getpriority.2 b/man2/getpriority.2 index 432c15f402..75f8b5fc40 100644 --- a/man2/getpriority.2 +++ b/man2/getpriority.2 @@ -170,7 +170,7 @@ The details on the condition for depend on the system. The above description is what POSIX.1-2001 says, and seems to be followed on all System\ V-like systems. -Linux kernels before 2.6.12 required the real or +Linux kernels before Linux 2.6.12 required the real or effective user ID of the caller to match the real user of the process \fIwho\fP (instead of its effective user ID). Linux 2.6.12 and later require diff --git a/man2/getrandom.2 b/man2/getrandom.2 index bf5083383e..e66815450b 100644 --- a/man2/getrandom.2 +++ b/man2/getrandom.2 @@ -157,8 +157,8 @@ The glibc wrapper function for determined that the underlying kernel does not implement this system call. .SH VERSIONS .BR getrandom () -was introduced in version 3.17 of the Linux kernel. -Support was added to glibc in version 2.25. +was introduced in Linux 3.17. +Support was added in glibc 2.25. .SH STANDARDS This system call is Linux-specific. .SH NOTES diff --git a/man2/getresuid.2 b/man2/getresuid.2 index 878cdcfcff..da441d17fc 100644 --- a/man2/getresuid.2 +++ b/man2/getresuid.2 @@ -41,9 +41,9 @@ is set to indicate the error. One of the arguments specified an address outside the calling program's address space. .SH VERSIONS -These system calls appeared on Linux starting with kernel 2.1.44. +These system calls were added on Linux 2.1.44. .PP -The prototypes are given by glibc since version 2.3.2, +The prototypes are given since glibc 2.3.2, provided .B _GNU_SOURCE is defined. diff --git a/man2/getrlimit.2 b/man2/getrlimit.2 index 56003da49f..f9bfaf98b0 100644 --- a/man2/getrlimit.2 +++ b/man2/getrlimit.2 @@ -112,7 +112,7 @@ argument must be one of: This is the maximum size of the process's virtual memory (address space). The limit is specified in bytes, and is rounded down to the system page size. -.\" since 2.0.27 / 2.1.12 +.\" since Linux 2.0.27 / Linux 2.1.12 This limit affects calls to .BR brk (2), .BR mmap (2), @@ -190,8 +190,8 @@ catch this signal instead, in which case the relevant system call (e.g., fails with the error .BR EFBIG . .TP -.BR RLIMIT_LOCKS " (Linux 2.4.0 to 2.4.24)" -.\" to be precise: Linux 2.4.0-test9; no longer in 2.4.25 / 2.5.65 +.BR RLIMIT_LOCKS " (Linux 2.4.0 to Linux 2.4.24)" +.\" to be precise: Linux 2.4.0-test9; no longer in Linux 2.4.25 / Linux 2.5.65 This is a limit on the combined number of .BR flock (2) locks and @@ -230,7 +230,7 @@ and a process can lock bytes up to this limit in each of these two categories. .IP -In Linux kernels before 2.6.9, this limit controlled the amount of +Before Linux 2.6.9, this limit controlled the amount of memory that could be locked by a privileged process. Since Linux 2.6.9, no limits are placed on the amount of memory that a privileged process may lock, and this limit instead governs @@ -360,7 +360,7 @@ affects only calls to .BR madvise (2) specifying .BR MADV_WILLNEED . -.\" As at kernel 2.6.12, this limit still does nothing in 2.6 though +.\" As at Linux 2.6.12, this limit still does nothing in Linux 2.6 though .\" talk of making it do something has surfaced from time to time in LKML .\" -- MTK, Jul 05 .TP @@ -415,7 +415,7 @@ it is always possible to use to queue one instance of any of the signals that are not already queued to the process. .\" This replaces the /proc/sys/kernel/rtsig-max system-wide limit -.\" that was present in kernels <= 2.6.7. MTK Dec 04 +.\" that was present in Linux <= 2.6.7. MTK Dec 04 .TP .B RLIMIT_STACK This is the maximum size of the process stack, in bytes. @@ -624,7 +624,7 @@ For backward compatibility, glibc also provides All new applications should be written using .BR setrlimit (). .SS C library/kernel ABI differences -Since version 2.13, the glibc +Since glibc 2.13, the glibc .BR getrlimit () and .BR setrlimit () @@ -645,9 +645,9 @@ and signals delivered when a process encountered the soft and hard .B RLIMIT_CPU limits were delivered one (CPU) second later than they should have been. -This was fixed in kernel 2.6.8. +This was fixed in Linux 2.6.8. .PP -In 2.6.x kernels before 2.6.17, a +In Linux 2.6.x kernels before Linux 2.6.17, a .B RLIMIT_CPU limit of 0 is wrongly treated as "no limit" (like .BR RLIM_INFINITY ). @@ -658,9 +658,9 @@ but is actually treated as a limit of 1 second. A kernel bug means that .\" See https://lwn.net/Articles/145008/ .B RLIMIT_RTPRIO -does not work in kernel 2.6.12; the problem is fixed in kernel 2.6.13. +does not work in Linux 2.6.12; the problem is fixed in Linux 2.6.13. .PP -In kernel 2.6.12, there was an off-by-one mismatch +In Linux 2.6.12, there was an off-by-one mismatch between the priority ranges returned by .BR getpriority (2) and @@ -668,7 +668,7 @@ and This had the effect that the actual ceiling for the nice value was calculated as .IR "19\ \-\ rlim_cur" . -This was fixed in kernel 2.6.13. +This was fixed in Linux 2.6.13. .\" see http://marc.theaimsgroup.com/?l=linux-kernel&m=112256338703880&w=2 .PP Since Linux 2.6.12, @@ -698,7 +698,7 @@ The Linux-specific .B RLIMIT_RTTIME limit exhibits the same behavior when the soft limit is encountered. .PP -Kernels before 2.4.22 did not diagnose the error +Kernels before Linux 2.4.22 did not diagnose the error .B EINVAL for .BR setrlimit () @@ -758,7 +758,7 @@ wrapper function silently converted the limit value to .BR RLIM_INFINITY . In other words, the requested resource limit setting was silently ignored. .PP -Since version 2.13, +Since glibc 2.13, .\" https://www.sourceware.org/bugzilla/show_bug.cgi?id=12201 glibc works around the limitations of the .BR getrlimit () diff --git a/man2/getrusage.2 b/man2/getrusage.2 index 8d720ad2ad..7257d823df 100644 --- a/man2/getrusage.2 +++ b/man2/getrusage.2 @@ -9,7 +9,7 @@ .\" history, etc., see getrlimit.2 .\" .\" Modified 2004-11-16, mtk, Noted that the nonconformance -.\" when SIGCHLD is being ignored is fixed in 2.6.9. +.\" when SIGCHLD is being ignored is fixed in Linux 2.6.9. .\" 2008-02-22, Sripathi Kodi : Document RUSAGE_THREAD .\" 2008-05-25, mtk, clarify RUSAGE_CHILDREN + other clean-ups. .\" 2010-05-24, Mark Hills : Description of fields, @@ -212,7 +212,7 @@ is Linux-specific. Resource usage metrics are preserved across an .BR execve (2). .PP -In Linux kernel versions before 2.6.9, if the disposition of +Before Linux 2.6.9, if the disposition of .B SIGCHLD is set to .B SIG_IGN @@ -231,11 +231,11 @@ Ancient systems provided a .BR vtimes () function with a similar purpose to .BR getrusage (). -For backward compatibility, glibc (up until version 2.32) also provides +For backward compatibility, glibc (up until Linux 2.32) also provides .BR vtimes (). All new applications should be written using .BR getrusage (). -(Since version 2.33, glibc no longer provides an +(Since Linux 2.33, glibc no longer provides an .BR vtimes () implementation.) .PP diff --git a/man2/getsid.2 b/man2/getsid.2 index 837fe7e4eb..3afccbd9d6 100644 --- a/man2/getsid.2 +++ b/man2/getsid.2 @@ -56,7 +56,7 @@ No process with process ID .I pid was found. .SH VERSIONS -This system call is available on Linux since version 2.0. +This system call is available since Linux 2.0. .\" Linux has this system call since Linux 1.3.44. .\" There is libc support since libc 5.2.19. .SH STANDARDS diff --git a/man2/gettid.2 b/man2/gettid.2 index 3d3f697277..ba721da488 100644 --- a/man2/gettid.2 +++ b/man2/gettid.2 @@ -35,7 +35,7 @@ This call is always successful. .SH VERSIONS The .BR gettid () -system call first appeared on Linux in kernel 2.4.11. +system call first appeared in Linux 2.4.11. Library support was added in glibc 2.30. (Earlier glibc versions did not provide a wrapper for this system call, necessitating the use of diff --git a/man2/gettimeofday.2 b/man2/gettimeofday.2 index 8ef5ac271f..6f1cd33d65 100644 --- a/man2/gettimeofday.2 +++ b/man2/gettimeofday.2 @@ -90,7 +90,7 @@ If either or .I tz is NULL, the corresponding structure is not set or returned. -.\" FIXME . The compilation warning looks to be going away in 2.17 +.\" FIXME . The compilation warning looks to be going away in glibc 2.17 .\" see glibc commit 4b7634a5e03b0da6f8875de9d3f74c1cf6f2a6e8 (However, compilation warnings will result if .I tv diff --git a/man2/getxattr.2 b/man2/getxattr.2 index be08ac1ec3..82d8c711d2 100644 --- a/man2/getxattr.2 +++ b/man2/getxattr.2 @@ -119,8 +119,8 @@ In addition, the errors documented in .BR stat (2) can also occur. .SH VERSIONS -These system calls have been available on Linux since kernel 2.4; -glibc support is provided since version 2.3. +These system calls have been available since Linux 2.4; +glibc support is provided since glibc 2.3. .SH STANDARDS These system calls are Linux-specific. .\" .SH AUTHORS diff --git a/man2/idle.2 b/man2/idle.2 index 073e5197cc..37b936816c 100644 --- a/man2/idle.2 +++ b/man2/idle.2 @@ -5,7 +5,7 @@ .\" SPDX-License-Identifier: Linux-man-pages-copyleft .\" .\" Modified 21 Aug 1994 by Michael Chastain : -.\" Added text about calling restriction (new in kernel 1.1.20 I believe). +.\" Added text about calling restriction (new in Linux 1.1.20 I believe). .\" N.B. calling "idle" from user process used to hang process! .\" Modified Thu Oct 31 14:41:15 1996 by Eric S. Raymond .\" " diff --git a/man2/init_module.2 b/man2/init_module.2 index 0b43007011..0deb15ac4a 100644 --- a/man2/init_module.2 +++ b/man2/init_module.2 @@ -257,7 +257,7 @@ The .BR init_module () system call is not supported by glibc. No declaration is provided in glibc headers, but, through a quirk of history, -glibc versions before 2.23 did export an ABI for this system call. +glibc versions before glibc 2.23 did export an ABI for this system call. Therefore, in order to employ this system call, it is (before glibc 2.23) sufficient to manually declare the interface in your code; diff --git a/man2/inotify_init.2 b/man2/inotify_init.2 index 11a4bf0ecc..4f24543efe 100644 --- a/man2/inotify_init.2 +++ b/man2/inotify_init.2 @@ -83,10 +83,10 @@ Insufficient kernel memory is available. .SH VERSIONS .BR inotify_init () first appeared in Linux 2.6.13; -library support was added to glibc in version 2.4. +library support was added in glibc 2.4. .BR inotify_init1 () was added in Linux 2.6.27; -library support was added to glibc in version 2.9. +library support was added in glibc 2.9. .SH STANDARDS These system calls are Linux-specific. .SH SEE ALSO diff --git a/man2/ioctl_console.2 b/man2/ioctl_console.2 index 4eb66b2ba1..30a55633bb 100644 --- a/man2/ioctl_console.2 +++ b/man2/ioctl_console.2 @@ -7,16 +7,16 @@ .\" Modified, Thu Apr 20 22:08:17 1995, jrv@vanzandt.mv.com .\" Modified, Mon Sep 18 22:32:47 1995, hpa@storm.net (H. Peter Anvin) .\" FIXME The following are not documented: -.\" KDFONTOP (since 2.1.111) -.\" KDGKBDIACRUC (since 2.6.24) +.\" KDFONTOP (since Linux 2.1.111) +.\" KDGKBDIACRUC (since Linux 2.6.24) .\" KDSKBDIACR -.\" KDSKBDIACRUC (since 2.6.24) -.\" KDKBDREP (since 2.1.113) -.\" KDMAPDISP (not implemented as at 2.6.27) -.\" KDUNMAPDISP (not implemented as at 2.6.27) -.\" VT_LOCKSWITCH (since 1.3.47, needs CAP_SYS_TTY_CONFIG) -.\" VT_UNLOCKSWITCH (since 1.3.47, needs CAP_SYS_TTY_CONFIG) -.\" VT_GETHIFONTMASK (since 2.6.18) +.\" KDSKBDIACRUC (since Linux 2.6.24) +.\" KDKBDREP (since Linux 2.1.113) +.\" KDMAPDISP (not implemented as at Linux 2.6.27) +.\" KDUNMAPDISP (not implemented as at Linux 2.6.27) +.\" VT_LOCKSWITCH (since Linux 1.3.47, needs CAP_SYS_TTY_CONFIG) +.\" VT_UNLOCKSWITCH (since Linux 1.3.47, needs CAP_SYS_TTY_CONFIG) +.\" VT_GETHIFONTMASK (since Linux 2.6.18) .\" .TH ioctl_console 2 (date) "Linux man-pages (unreleased)" .SH NAME @@ -673,7 +673,7 @@ Linux 2.5.71. .BR TIOCLINUX ", " subcode = 0 Dump the screen. Disappeared in Linux 1.1.92. -(With kernel 1.1.92 or later, read from +(With Linux 1.1.92 or later, read from .I /dev/vcsN or .I /dev/vcsaN @@ -747,7 +747,7 @@ variable Dump screen width and height, cursor position, and all the character-attribute pairs. (Kernels 1.1.67 through 1.1.91 only. -With kernel 1.1.92 or later, read from +With Linux 1.1.92 or later, read from .I /dev/vcsa* instead.) .TP @@ -755,7 +755,7 @@ instead.) Restore screen width and height, cursor position, and all the character-attribute pairs. (Kernels 1.1.67 through 1.1.91 only. -With kernel 1.1.92 or later, write to +With Linux 1.1.92 or later, write to .I /dev/vcsa* instead.) .TP diff --git a/man2/ioctl_tty.2 b/man2/ioctl_tty.2 index b0ddeaad06..9c3145a41c 100644 --- a/man2/ioctl_tty.2 +++ b/man2/ioctl_tty.2 @@ -345,9 +345,9 @@ or .I /dev/tty0 to the given terminal. If that was a pseudoterminal master, send it to the slave. -In Linux before version 2.6.10, +Before Linux 2.6.10, anybody can do this as long as the output was not redirected yet; -since version 2.6.10, only a process with the +since Linux 2.6.10, only a process with the .B CAP_SYS_ADMIN capability may do this. If output was redirected already, then diff --git a/man2/ioctl_userfaultfd.2 b/man2/ioctl_userfaultfd.2 index 6b8d86f504..cb56315f25 100644 --- a/man2/ioctl_userfaultfd.2 +++ b/man2/ioctl_userfaultfd.2 @@ -92,7 +92,7 @@ fields to bit masks representing all the available features and the generic .BR ioctl (2) operations available. .PP -For Linux kernel versions before 4.11, the +Before Linux 4.11, the .I features field must be initialized to zero before the call to .BR UFFDIO_API , diff --git a/man2/ioprio_set.2 b/man2/ioprio_set.2 index ff1e72160e..f7878d60e0 100644 --- a/man2/ioprio_set.2 +++ b/man2/ioprio_set.2 @@ -221,7 +221,7 @@ As at kernel 2.6.17 the only such scheduler is the Completely Fair Queuing If no I/O scheduler has been set for a thread, then by default the I/O priority will follow the CPU nice value .RB ( setpriority (2)). -In Linux kernels before version 2.6.24, +Before Linux 2.6.24, once an I/O priority had been set using .BR ioprio_set (), there was no way to reset the I/O scheduling behavior to the default. @@ -333,7 +333,7 @@ Attempts to set very high priorities require the .B CAP_SYS_ADMIN capability. -Kernel versions up to 2.6.24 also required +Up to Linux 2.6.24 also required .B CAP_SYS_ADMIN to set a very low priority .RB ( IOPRIO_CLASS_IDLE ), diff --git a/man2/keyctl.2 b/man2/keyctl.2 index 0af1106a67..82553445d1 100644 --- a/man2/keyctl.2 +++ b/man2/keyctl.2 @@ -1393,7 +1393,7 @@ Should the timeout be reached, the persistent keyring will be removed and everything it pins can then be garbage collected. .IP -Persistent keyrings were added to Linux in kernel version 3.13. +Persistent keyrings were added in Linux 3.13. .IP The arguments .I arg4 @@ -1542,7 +1542,9 @@ as with SP800-108 (the counter KDF). .\" keyutils commit d68a981e5db41d059ac782071c35d1e8f3aaf61c This operation is exposed by .I libkeyutils -(from version 1.5.10 onwards) via the functions +(from +.I libkeyutils +1.5.10 onwards) via the functions .BR keyctl_dh_compute (3) and .BR keyctl_dh_compute_alloc (3). @@ -1751,7 +1753,7 @@ or (the key description) exceeded the limit (32 bytes and 4096 bytes respectively). .TP -.BR EINVAL " (Linux kernels before 4.12)" +.BR EINVAL " (before Linux 4.12)" .I operation was .BR KEYCTL_DH_COMPUTE , @@ -1831,7 +1833,7 @@ exceeds .B KEYCTL_KDF_MAX_OI_LEN (which is 64 currently). .TP -.BR ENFILE " (Linux kernels before 3.13)" +.BR ENFILE " (before Linux 3.13)" .I operation was .B KEYCTL_LINK diff --git a/man2/kill.2 b/man2/kill.2 index 0c57a9fb61..def4a99b66 100644 --- a/man2/kill.2 +++ b/man2/kill.2 @@ -131,16 +131,16 @@ for the permissions required for an unprivileged process to send a signal to another process. .\" In the 0.* kernels things chopped and changed quite .\" a bit - MTK, 24 Jul 02 -In kernels 1.0 to 1.2.2, a signal could be sent if the +In Linux 1.0 to 1.2.2, a signal could be sent if the effective user ID of the sender matched effective user ID of the target, or the real user ID of the sender matched the real user ID of the target. -From kernel 1.2.3 until 1.3.77, a signal could be sent if the +From Linux 1.2.3 until 1.3.77, a signal could be sent if the effective user ID of the sender matched either the real or effective user ID of the target. The current rules, which conform to POSIX.1, were adopted -in kernel 1.3.78. +in Linux 1.3.78. .SH BUGS -In 2.6 kernels up to and including 2.6.7, +In Linux 2.6 up to and including Linux 2.6.7, there was a bug that meant that when sending signals to a process group, .BR kill () failed with the error diff --git a/man2/link.2 b/man2/link.2 index 774e23631e..e00c8e3079 100644 --- a/man2/link.2 +++ b/man2/link.2 @@ -153,7 +153,7 @@ linkat(AT_FDCWD, "/proc/self/fd/", newdirfd, .EE .in .PP -Before kernel 2.6.18, the +Before Linux 2.6.18, the .I flags argument was unused, and had to be specified as 0. .PP @@ -336,8 +336,8 @@ is an empty string, and refers to a directory. .SH VERSIONS .BR linkat () -was added to Linux in kernel 2.6.16; -library support was added to glibc in version 2.4. +was added in Linux 2.6.16; +library support was added in glibc 2.4. .SH STANDARDS .BR link (): SVr4, 4.3BSD, POSIX.1-2001 (but see NOTES), POSIX.1-2008. @@ -360,8 +360,8 @@ POSIX.1-2001 says that should dereference .I oldpath if it is a symbolic link. -However, since kernel 2.0, -.\" more precisely: since kernel 1.3.56 +However, since Linux 2.0, +.\" more precisely: since Linux 1.3.56 Linux does not do so: if .I oldpath is a symbolic link, then diff --git a/man2/listen.2 b/man2/listen.2 index e0a4fb9164..615ded424f 100644 --- a/man2/listen.2 +++ b/man2/listen.2 @@ -137,7 +137,7 @@ argument is greater than the value in then it is silently capped to that value. Since Linux 5.4, the default in this file is 4096; in earlier kernels, the default value is 128. -In kernels before 2.4.25, this limit was a hard coded value, +Before Linux 2.4.25, this limit was a hard coded value, .BR SOMAXCONN , with the value 128. .\" The following is now rather historic information (MTK, Jun 05) diff --git a/man2/listxattr.2 b/man2/listxattr.2 index 8ca1b7f586..c417f9469f 100644 --- a/man2/listxattr.2 +++ b/man2/listxattr.2 @@ -133,8 +133,8 @@ In addition, the errors documented in .BR stat (2) can also occur. .SH VERSIONS -These system calls have been available on Linux since kernel 2.4; -glibc support is provided since version 2.3. +These system calls have been available since Linux 2.4; +glibc support is provided since glibc 2.3. .SH STANDARDS These system calls are Linux-specific. .\" .SH AUTHORS diff --git a/man2/lookup_dcookie.2 b/man2/lookup_dcookie.2 index 54e4922e11..d151465071 100644 --- a/man2/lookup_dcookie.2 +++ b/man2/lookup_dcookie.2 @@ -69,7 +69,7 @@ The buffer was not large enough to hold the path of the directory entry. Available since Linux 2.5.43. The .B ENAMETOOLONG -error return was added in 2.5.70. +error return was added in Linux 2.5.70. .SH STANDARDS .BR lookup_dcookie () is Linux-specific. diff --git a/man2/lseek.2 b/man2/lseek.2 index 2463a3e516..bace879304 100644 --- a/man2/lseek.2 +++ b/man2/lseek.2 @@ -60,7 +60,7 @@ If data is later written at this point, subsequent reads of the data in the gap (a "hole") return null bytes (\(aq\e0\(aq) until data is actually written into the gap. .SS Seeking file data and holes -Since version 3.1, Linux supports the following additional values for +Since Linux 3.1, Linux supports the following additional values for .IR whence : .TP .B SEEK_DATA diff --git a/man2/madvise.2 b/man2/madvise.2 index 9a3357b5ed..3cebb4c7ae 100644 --- a/man2/madvise.2 +++ b/man2/madvise.2 @@ -525,7 +525,7 @@ The operation can be applied only to private anonymous pages (see .BR mmap (2)). -In Linux before version 4.12, +Before Linux 4.12, .\" commit 93e06c7a645343d222c9a838834a51042eebbbf7 when freeing pages on a swapless system, the pages in the given range are freed instantly, diff --git a/man2/mbind.2 b/man2/mbind.2 index 9811690c25..d57021d415 100644 --- a/man2/mbind.2 +++ b/man2/mbind.2 @@ -296,7 +296,7 @@ then the call fails with the error if the existing pages in the memory range don't follow the policy. .\" According to the kernel code, the following is not true .\" --Lee Schermerhorn -.\" In 2.6.16 or later the kernel will also try to move pages +.\" In Linux 2.6.16 or later the kernel will also try to move pages .\" to the requested node with this flag. .PP If @@ -423,7 +423,7 @@ privilege. .SH VERSIONS The .BR mbind () -system call was added to the Linux kernel in version 2.6.7. +system call was added in Linux 2.6.7. .SH STANDARDS This system call is Linux-specific. .SH NOTES @@ -469,7 +469,7 @@ This method will work for .BR set_mempolicy (2), as well. .PP -Support for huge page policy was added with 2.6.16. +Support for huge page policy was added with Linux 2.6.16. For interleave policy to be effective on huge page mappings the policied memory needs to be tens of megabytes or larger. .PP diff --git a/man2/memfd_create.2 b/man2/memfd_create.2 index 3e3a57bf42..a477afe512 100644 --- a/man2/memfd_create.2 +++ b/man2/memfd_create.2 @@ -188,7 +188,7 @@ There was insufficient memory to create a new anonymous file. The .BR memfd_create () system call first appeared in Linux 3.17; -glibc support was added in version 2.27. +glibc support was added in glibc 2.27. .TP .B EPERM The diff --git a/man2/migrate_pages.2 b/man2/migrate_pages.2 index 77cfdde352..e9e95b4f63 100644 --- a/man2/migrate_pages.2 +++ b/man2/migrate_pages.2 @@ -137,7 +137,7 @@ could be found. .SH VERSIONS The .BR migrate_pages () -system call first appeared on Linux in version 2.6.16. +system call first appeared in Linux 2.6.16. .SH STANDARDS This system call is Linux-specific. .SH NOTES diff --git a/man2/mincore.2 b/man2/mincore.2 index 98eaf8025e..e1496fb7bb 100644 --- a/man2/mincore.2 +++ b/man2/mincore.2 @@ -130,7 +130,7 @@ and it is not available on all UNIX implementations. .\" .BR mincore () .\" function first appeared in 4.4BSD. .SH BUGS -Before kernel 2.6.21, +Before Linux 2.6.21, .BR mincore () did not return correct information for .B MAP_PRIVATE diff --git a/man2/mkdir.2 b/man2/mkdir.2 index 06a4367d37..421b03429f 100644 --- a/man2/mkdir.2 +++ b/man2/mkdir.2 @@ -205,8 +205,8 @@ does not support the creation of directories. refers to a file on a read-only filesystem. .SH VERSIONS .BR mkdirat () -was added to Linux in kernel 2.6.16; -library support was added to glibc in version 2.4. +was added in Linux 2.6.16; +library support was added in glibc 2.4. .SH STANDARDS .BR mkdir (): SVr4, BSD, POSIX.1-2001, POSIX.1-2008. diff --git a/man2/mknod.2 b/man2/mknod.2 index a8414deccf..119fab48ee 100644 --- a/man2/mknod.2 +++ b/man2/mknod.2 @@ -242,8 +242,8 @@ does not support the type of node requested. refers to a file on a read-only filesystem. .SH VERSIONS .BR mknodat () -was added to Linux in kernel 2.6.16; -library support was added to glibc in version 2.4. +was added in Linux 2.6.16; +library support was added in glibc 2.4. .SH STANDARDS .BR mknod (): SVr4, 4.4BSD, POSIX.1-2001 (but see below), POSIX.1-2008. diff --git a/man2/mlock.2 b/man2/mlock.2 index c08e7ad5b5..368be7c1e9 100644 --- a/man2/mlock.2 +++ b/man2/mlock.2 @@ -258,7 +258,7 @@ to perform the requested operation. .SH VERSIONS .BR mlock2 () is available since Linux 4.4; -glibc support was added in version 2.27. +glibc support was added in glibc 2.27. .SH STANDARDS .BR mlock (), .BR munlock (), @@ -465,9 +465,9 @@ a bug caused the .B MCL_FUTURE flag to be inherited across a .BR fork (2). -This was rectified in kernel 2.4.18. +This was rectified in Linux 2.4.18. .PP -Since kernel 2.6.9, if a privileged process calls +Since Linux 2.6.9, if a privileged process calls .I mlockall(MCL_FUTURE) and later drops privileges (loses the .B CAP_IPC_LOCK diff --git a/man2/mmap.2 b/man2/mmap.2 index bdd51013f0..7e75929d24 100644 --- a/man2/mmap.2 +++ b/man2/mmap.2 @@ -8,7 +8,7 @@ .\" Modified 2001-10-04 by John Levon .\" Modified 2003-02-02 by Andi Kleen .\" Modified 2003-05-21 by Michael Kerrisk -.\" MAP_LOCKED works from 2.5.37 +.\" MAP_LOCKED works from Linux 2.5.37 .\" Modified 2004-06-17 by Michael Kerrisk .\" Modified 2004-09-11 by aeb .\" Modified 2004-12-08, from Eric Estievenart @@ -61,7 +61,7 @@ and attempt to create the mapping there. If another mapping already exists there, the kernel picks a new address that may or may not depend on the hint. .\" Before Linux 2.6.24, the address was rounded up to the next page -.\" boundary; since 2.6.24, it is rounded down! +.\" boundary; since Linux 2.6.24, it is rounded down! The address of the new mapping is returned as the result of the call. .PP The contents of a file mapping (as opposed to an anonymous mapping; see @@ -248,7 +248,7 @@ Software that aspires to be portable should use the .B MAP_FIXED flag with care, keeping in mind that the exact layout of a process's memory mappings -is allowed to change significantly between kernel versions, +is allowed to change significantly between Linux versions, C library versions, and operating system releases. .I Carefully read the discussion of this flag in NOTES! .TP @@ -376,7 +376,7 @@ See also the discussion of the file .I /proc/sys/vm/overcommit_memory in .BR proc (5). -In kernels before 2.6, this flag had effect only for +Before Linux 2.6, this flag had effect only for private writable mappings. .TP .BR MAP_POPULATE " (since Linux 2.5.46)" @@ -611,7 +611,7 @@ argument asks for .B PROT_EXEC but the mapped area belongs to a file on a filesystem that was mounted no-exec. -.\" (Since 2.4.25 / 2.6.0.) +.\" (Since Linux 2.4.25 / Linux 2.6.0.) .TP .B EPERM The operation was prevented by a file seal; see @@ -864,7 +864,7 @@ This page describes the interface provided by the glibc .BR mmap () wrapper function. Originally, this function invoked a system call of the same name. -Since kernel 2.4, that system call has been superseded by +Since Linux 2.4, that system call has been superseded by .BR mmap2 (2), and nowadays .\" Since around glibc 2.1/2.2, depending on the platform. @@ -880,7 +880,7 @@ On Linux, there are no guarantees like those suggested above under By default, any process can be killed at any moment when the system runs out of memory. .PP -In kernels before 2.6.7, the +Before Linux 2.6.7, the .B MAP_POPULATE flag has effect only if .I prot @@ -892,11 +892,11 @@ SUSv3 specifies that should fail if .I length is 0. -However, in kernels before 2.6.12, +However, before Linux 2.6.12, .BR mmap () succeeded in this case: no mapping was created and the call returned .IR addr . -Since kernel 2.6.12, +Since Linux 2.6.12, .BR mmap () fails with the error .B EINVAL diff --git a/man2/mount.2 b/man2/mount.2 index 9e89c16ef1..ce743fcb29 100644 --- a/man2/mount.2 +++ b/man2/mount.2 @@ -440,7 +440,7 @@ If includes .B MS_BIND (available since Linux 2.4), -.\" since 2.4.0-test9 +.\" since Linux 2.4.0-test9 then perform a bind mount. A bind mount makes a file or a directory subtree visible at another point within the single directory hierarchy. @@ -843,7 +843,7 @@ The definitions of .BR MS_STRICTATIME , and .B MS_UNBINDABLE -were added to glibc headers in version 2.12. +were added to glibc headers in glibc 2.12. .\" .SH STANDARDS This function is Linux-specific and should not be used in @@ -852,7 +852,7 @@ programs intended to be portable. Since Linux 2.4 a single filesystem can be mounted at multiple mount points, and multiple mounts can be stacked on the same mount point. -.\" Multiple mounts on same mount point: since 2.3.99pre7. +.\" Multiple mounts on same mount point: since Linux 2.3.99pre7. .PP The .I mountflags @@ -863,7 +863,7 @@ occupy the low order 16 bits of .IR mountflags .) Specifying .B MS_MGC_VAL -was required in kernel versions prior to 2.4, +was required before Linux 2.4, but since Linux 2.4 is no longer required and is ignored if specified. .PP The original @@ -885,7 +885,7 @@ just silently ignored in this case. .\" The change is in patch-2.4.0-prerelease. .\" .SS Mount namespaces -Starting with kernel 2.4.19, Linux provides mount namespaces. +Starting with Linux 2.4.19, Linux provides mount namespaces. A mount namespace is the set of filesystem mounts that are visible to a process. Mount namespaces can be (and usually are) diff --git a/man2/move_pages.2 b/man2/move_pages.2 index 00f3aadd59..a37c7e6afd 100644 --- a/man2/move_pages.2 +++ b/man2/move_pages.2 @@ -56,7 +56,7 @@ moves pages of the calling process. .PP To move pages in another process requires the following privileges: .IP \(bu 3 -In kernels up to and including Linux 4.12: +Up to and including Linux 4.12: the caller must be privileged .RB ( CAP_SYS_NICE ) or the real or effective user ID of the calling process must match the @@ -218,7 +218,7 @@ to another user but did not have privilege to do so Process does not exist. .SH VERSIONS .BR move_pages () -first appeared on Linux in version 2.6.18. +first appeared in Linux 2.6.18. .SH STANDARDS This system call is Linux-specific. .SH NOTES diff --git a/man2/mprotect.2 b/man2/mprotect.2 index 066b7f4217..e24c4b93ec 100644 --- a/man2/mprotect.2 +++ b/man2/mprotect.2 @@ -176,7 +176,7 @@ Addresses in the range .IR addr + len \-1] are invalid for the address space of the process, or specify one or more pages that are not mapped. -(Before kernel 2.4.19, the error +(Before Linux 2.4.19, the error .B EFAULT was incorrectly produced for these cases.) .TP diff --git a/man2/mremap.2 b/man2/mremap.2 index 81cda37650..934cbbe339 100644 --- a/man2/mremap.2 +++ b/man2/mremap.2 @@ -280,7 +280,7 @@ with .B ENOMEM if the area cannot be populated. .PP -Prior to version 2.4, glibc did not expose the definition of +Prior to glibc 2.4, glibc did not expose the definition of .BR MREMAP_FIXED , and the prototype for .BR mremap () diff --git a/man2/msgget.2 b/man2/msgget.2 index 24a50f3bbf..4a03f665f4 100644 --- a/man2/msgget.2 +++ b/man2/msgget.2 @@ -194,7 +194,7 @@ Since Linux 3.19, the default value is 32,000. On Linux, this limit can be read and modified via .IR /proc/sys/kernel/msgmni . .SS Linux notes -Until version 2.3.20, Linux would return +Until Linux 2.3.20, Linux would return .B EIDRM for a .BR msgget () diff --git a/man2/nanosleep.2 b/man2/nanosleep.2 index 969c346093..a6f9e627f4 100644 --- a/man2/nanosleep.2 +++ b/man2/nanosleep.2 @@ -171,7 +171,7 @@ like .B SCHED_FIFO or .BR SCHED_RR . -This special extension was removed in kernel 2.5.39, +This special extension was removed in Linux 2.5.39, and is thus not available in Linux 2.6.0 and later kernels. .SH BUGS If a program that catches signals and uses diff --git a/man2/nfsservctl.2 b/man2/nfsservctl.2 index 4a893eb13a..b75a8e671d 100644 --- a/man2/nfsservctl.2 +++ b/man2/nfsservctl.2 @@ -62,8 +62,8 @@ On error, \-1 is returned, and .I errno is set to indicate the error. .SH VERSIONS -This system call was removed from the Linux kernel in version 3.1. -Library support was removed from glibc in version 2.28. +This system call was removed in Linux 3.1. +Library support was removed in glibc 2.28. .SH STANDARDS This call is Linux-specific. .SH SEE ALSO diff --git a/man2/open.2 b/man2/open.2 index 3c7ce161fe..a0e5070a89 100644 --- a/man2/open.2 +++ b/man2/open.2 @@ -261,8 +261,8 @@ and .I sysvgroups mount options described in .BR mount (8). -.\" As at 2.6.25, bsdgroups is supported by ext2, ext3, ext4, and -.\" XFS (since 2.6.14). +.\" As at Linux 2.6.25, bsdgroups is supported by ext2, ext3, ext4, and +.\" XFS (since Linux 2.6.14). .IP The .I mode @@ -390,7 +390,7 @@ If \fIpathname\fP is not a directory, cause the open to fail. .\" http://marc.theaimsgroup.com/?t=112748702800001&r=1&w=2 .\" [PATCH] open: O_DIRECTORY and O_CREAT together should fail .\" O_DIRECTORY | O_CREAT causes O_DIRECTORY to be ignored. -This flag was added in kernel version 2.1.126, to +This flag was added in Linux 2.1.126, to avoid denial-of-service problems if .BR opendir (3) is called on a @@ -541,14 +541,14 @@ error that can occur in this case is indistinguishable from the case where an open fails because there are too many symbolic links found while resolving components in the prefix part of the pathname.) .IP -This flag is a FreeBSD extension, which was added to Linux in version 2.1.126, +This flag is a FreeBSD extension, which was added in Linux 2.1.126, and has subsequently been standardized in POSIX.1-2008. .IP See also .B O_PATH below. .\" The headers from glibc 2.0.100 and later include a -.\" definition of this flag; \fIkernels before 2.1.126 will ignore it if +.\" definition of this flag; \fIkernels before Linux 2.1.126 will ignore it if .\" used\fP. .TP .BR O_NONBLOCK " or " O_NDELAY @@ -1239,7 +1239,7 @@ see also .B O_LARGEFILE above. This is the error specified by POSIX.1; -in kernels before 2.6.24, Linux gave the error +before Linux 2.6.24, Linux gave the error .B EFBIG for this case. .\" See http://bugzilla.kernel.org/show_bug.cgi?id=7253 @@ -1286,8 +1286,8 @@ flag was specified, and an incompatible lease was held on the file .BR fcntl (2)). .SH VERSIONS .BR openat () -was added to Linux in kernel 2.6.16; -library support was added to glibc in version 2.4. +was added in Linux 2.6.16; +library support was added in glibc 2.4. .SH STANDARDS .BR open (), .BR creat () @@ -1539,7 +1539,7 @@ new headers get at least semantics on pre-2.6.33 kernels. .\" .SS C library/kernel differences -Since version 2.26, +Since glibc 2.26, the glibc wrapper function for .BR open () employs the @@ -1547,7 +1547,7 @@ employs the system call, rather than the kernel's .BR open () system call. -For certain architectures, this is also true in glibc versions before 2.26. +For certain architectures, this is also true before glibc 2.26. .\" .SS NFS There are many infelicities in the protocol underlying NFS, affecting @@ -1832,7 +1832,7 @@ FreeBSD 4.x introduced a flag of the same name, but without alignment restrictions. .PP .B O_DIRECT -support was added under Linux in kernel version 2.4.10. +support was added in Linux 2.4.10. Older Linux kernels simply ignore this flag. Some filesystems may not implement the flag, in which case .BR open () diff --git a/man2/open_by_handle_at.2 b/man2/open_by_handle_at.2 index 1d10a9bdbe..e3c72c8330 100644 --- a/man2/open_by_handle_at.2 +++ b/man2/open_by_handle_at.2 @@ -367,7 +367,7 @@ is not valid. This error will occur if, for example, the file has been deleted. .SH VERSIONS These system calls first appeared in Linux 2.6.39. -Library support is provided in glibc since version 2.14. +Library support is provided since glibc 2.14. .SH STANDARDS These system calls are nonstandard Linux extensions. .PP diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2 index 2b7b19cb9b..8e94fb4ac6 100644 --- a/man2/perf_event_open.2 +++ b/man2/perf_event_open.2 @@ -374,7 +374,7 @@ is set to 64; this was the size of the first published struct. is 72, corresponding to the addition of breakpoints in Linux 2.6.33. .\" commit cb5d76999029ae7a517cb07dfa732c1b5a934fc2 .\" this was added much later when PERF_ATTR_SIZE_VER2 happened -.\" but the actual attr_size had increased in 2.6.33 +.\" but the actual attr_size had increased in Linux 2.6.33 .B PERF_ATTR_SIZE_VER2 is 80 corresponding to the addition of branch sampling in Linux 3.4. .\" commit cb5d76999029ae7a517cb07dfa732c1b5a934fc2 @@ -1169,8 +1169,8 @@ Do not include user callchains. .\" commit 13d7a2410fa637f450a29ecb515ac318ee40c741 .\" This is tricky; was committed during 3.12 development .\" but right before release was disabled. -.\" So while you could select mmap2 starting with 3.12 -.\" it did not work until 3.16 +.\" So while you could select mmap2 starting with Linux 3.12 +.\" it did not work until Linux 3.16 .\" commit a5a5ba72843dd05f991184d6cb9a4471acce1005 Generate an extended executable mmap record that contains enough additional information to uniquely identify shared mappings. @@ -1568,7 +1568,7 @@ metadata page that contains various bits of information such as where the ring-buffer head is. .PP -Before kernel 2.6.39, there is a bug that means you must allocate an mmap +Before Linux 2.6.39, there is a bug that means you must allocate an mmap ring buffer when sampling even if you do not plan to access it. .PP The structure of the first metadata mmap page is as follows: diff --git a/man2/personality.2 b/man2/personality.2 index c2979ab876..4be1b97f5d 100644 --- a/man2/personality.2 +++ b/man2/personality.2 @@ -101,7 +101,8 @@ Have .BR uname (2) report a 2.6.40+ version number rather than a 3.x version number. Added as a stopgap measure to support broken applications that -could not handle the kernel version-numbering switch from 2.6.x to 3.x. +could not handle the +kernel version-numbering switch from Linux 2.6.x to Linux 3.x. .TP .BR WHOLE_SECONDS " (since Linux 1.2.0)" No effect. @@ -247,7 +248,7 @@ This system call first appeared in Linux 1.1.20 (and thus first in a stable kernel release with Linux 1.2.0); library support was added in glibc 2.3. .\" personality wrapper first appeared in glibc 1.90, -.\" was added later in 2.2.91. +.\" was added later in glibc 2.2.91. .SH STANDARDS .BR personality () is Linux-specific and should not be used in programs intended to diff --git a/man2/pipe.2 b/man2/pipe.2 index 961768656d..6795fe1375 100644 --- a/man2/pipe.2 +++ b/man2/pipe.2 @@ -194,9 +194,8 @@ and support for notifications is not compiled into the kernel. .SH VERSIONS .BR pipe2 () -was added to Linux in version 2.6.27; -glibc support is available starting with -version 2.9. +was added in Linux 2.6.27; +glibc support is available starting with glibc 2.9. .SH STANDARDS .BR pipe (): POSIX.1-2001, POSIX.1-2008. diff --git a/man2/pkey_alloc.2 b/man2/pkey_alloc.2 index 24a83bce9f..d6d33e8d65 100644 --- a/man2/pkey_alloc.2 +++ b/man2/pkey_alloc.2 @@ -87,7 +87,7 @@ of available pkeys. .BR pkey_alloc () and .BR pkey_free () -were added to Linux in kernel 4.9; +were added in Linux 4.9; library support was added in glibc 2.27. .SH STANDARDS The diff --git a/man2/poll.2 b/man2/poll.2 index fa22e20025..965b62938f 100644 --- a/man2/poll.2 +++ b/man2/poll.2 @@ -369,7 +369,7 @@ wrapper function provides emulation using .PP The .BR ppoll () -system call was added to Linux in kernel 2.6.16. +system call was added in Linux 2.6.16. The .BR ppoll () library call was added in glibc 2.4. diff --git a/man2/posix_fadvise.2 b/man2/posix_fadvise.2 index 2ee2cf4bdb..57c65c8107 100644 --- a/man2/posix_fadvise.2 +++ b/man2/posix_fadvise.2 @@ -62,9 +62,9 @@ The specified data will be accessed in random order. .B POSIX_FADV_NOREUSE The specified data will be accessed only once. .IP -In kernels before 2.6.18, \fBPOSIX_FADV_NOREUSE\fP had the +Before Linux 2.6.18, \fBPOSIX_FADV_NOREUSE\fP had the same semantics as \fBPOSIX_FADV_WILLNEED\fP. -This was probably a bug; since kernel 2.6.18, this flag is a no-op. +This was probably a bug; since Linux 2.6.18, this flag is a no-op. .TP .B POSIX_FADV_WILLNEED The specified data will be accessed in the near future. @@ -121,7 +121,7 @@ An invalid value was specified for \fIadvice\fP. The specified file descriptor refers to a pipe or FIFO. .RB ( ESPIPE is the error specified by POSIX, -but before kernel version 2.6.16, +but before Linux 2.6.16, .\" commit 87ba81dba431232548ce29d5d224115d0c2355ac Linux returned .B EINVAL @@ -131,7 +131,7 @@ Kernel support first appeared in Linux 2.5.60; the underlying system call is called .BR fadvise64 (). .\" of fadvise64_64() -Library support has been provided since glibc version 2.2, +Library support has been provided since glibc 2.2, via the wrapper function .BR posix_fadvise (). .PP @@ -211,7 +211,7 @@ hidden from applications by the glibc wrapper function, which invokes the appropriate architecture-specific system call. .SH BUGS -In kernels before 2.6.6, if +Before Linux 2.6.6, if .I len was specified as 0, then this was interpreted literally as "zero bytes", rather than as meaning "all bytes through to the end of the file". diff --git a/man2/prctl.2 b/man2/prctl.2 index ef9e0dcf02..74f86ff492 100644 --- a/man2/prctl.2 +++ b/man2/prctl.2 @@ -229,14 +229,14 @@ Set the state of the "dumpable" attribute, which determines whether core dumps are produced for the calling process upon delivery of a signal whose default behavior is to produce a core dump. .IP -In kernels up to and including 2.6.12, +Up to and including Linux 2.6.12, .I arg2 must be either 0 .RB ( SUID_DUMP_DISABLE , process is not dumpable) or 1 .RB ( SUID_DUMP_USER , process is dumpable). -Between kernels 2.6.13 and 2.6.17, +Between Linux 2.6.13 and Linux 2.6.17, .\" commit abf75a5033d4da7b8a7e92321d74021d1fcfb502 the value 2 was also permitted, which caused any binary which normally would not be dumped @@ -297,8 +297,8 @@ directory is affected as described in Return (as the function result) the current state of the calling process's dumpable attribute. .\" Since Linux 2.6.13, the dumpable flag can have the value 2, -.\" but in 2.6.13 PR_GET_DUMPABLE simply returns 1 if the dumpable -.\" flags has a nonzero value. This was fixed in 2.6.14. +.\" but in Linux 2.6.13 PR_GET_DUMPABLE simply returns 1 if the dumpable +.\" flags has a nonzero value. This was fixed in Linux 2.6.14. .\" prctl PR_SET_ENDIAN .TP .BR PR_SET_ENDIAN " (since Linux 2.6.18, PowerPC only)" @@ -1930,7 +1930,7 @@ to \fIarg2\fP. is not currently implemented (attempting to set this mode will yield the error .BR EINVAL ). -.\" PR_TIMING_TIMESTAMP doesn't do anything in 2.6.26-rc8, +.\" PR_TIMING_TIMESTAMP doesn't do anything in Linux 2.6.26-rc8, .\" and looking at the patch history, it appears .\" that it never did anything. .\" prctl PR_GET_TIMING diff --git a/man2/pread.2 b/man2/pread.2 index df05c20801..9a97633235 100644 --- a/man2/pread.2 +++ b/man2/pread.2 @@ -93,9 +93,8 @@ The .BR pread () and .BR pwrite () -system calls were added to Linux in -version 2.1.60; the entries in the i386 system call table were added -in 2.1.69. +system calls were added in Linux 2.1.60; +the entries in the i386 system call table were added in Linux 2.1.69. C library support (including emulation using .BR lseek (2) on older kernels without the system calls) was added in glibc 2.1. @@ -112,7 +111,7 @@ without being affected by changes to the file offset by other threads. .\" .SS C library/kernel differences On Linux, the underlying system calls were renamed -in kernel 2.6: +in Linux 2.6: .BR pread () became .BR pread64 (), diff --git a/man2/process_vm_readv.2 b/man2/process_vm_readv.2 index d2f468d526..208d83a772 100644 --- a/man2/process_vm_readv.2 +++ b/man2/process_vm_readv.2 @@ -251,7 +251,7 @@ No process with ID exists. .SH VERSIONS These system calls were added in Linux 3.2. -Support is provided in glibc since version 2.15. +Support is provided since glibc 2.15. .SH STANDARDS These system calls are nonstandard Linux extensions. .SH NOTES diff --git a/man2/ptrace.2 b/man2/ptrace.2 index 7737da5f9c..a0cdede69b 100644 --- a/man2/ptrace.2 +++ b/man2/ptrace.2 @@ -834,7 +834,7 @@ Attach to the process specified in .IR pid , making it a tracee of the calling process. .\" No longer true (removed by Denys Vlasenko, 2011, who remarks: -.\" "I think it isn't true in non-ancient 2.4 and in 2.6/3.x. +.\" "I think it isn't true in non-ancient 2.4 and in Linux 2.6/3.x. .\" Basically, it's not true for any Linux in practical use. .\" ; the behavior of the tracee is as if it had done a .\" .BR PTRACE_TRACEME . @@ -1852,7 +1852,7 @@ set to or .IR (SIGTRAP|0x80) . .\" -.SS PTRACE_EVENT_SECCOMP stops (Linux 3.5 to 4.7) +.SS PTRACE_EVENT_SECCOMP stops (Linux 3.5 to Linux 4.7) The behavior of .B PTRACE_EVENT_SECCOMP stops and their interaction with other kinds @@ -2179,7 +2179,7 @@ the pending signal is injected. When one thread in a multithreaded process calls .BR execve (2), the kernel destroys all other threads in the process, -.\" In kernel 3.1 sources, see fs/exec.c::de_thread() +.\" In Linux 3.1 sources, see fs/exec.c::de_thread() and resets the thread ID of the execing thread to the thread group ID (process ID). (Or, to put things another way, when a multithreaded process does an @@ -2417,7 +2417,7 @@ unprivileged processes cannot trace processes that they cannot send signals to or those running set-user-ID/set-group-ID programs, for obvious reasons. Alternatively, the process may already be being traced, -or (on kernels before 2.6.26) be +or (before Linux 2.6.26) be .BR init (1) (PID 1). .TP @@ -2443,7 +2443,7 @@ setting unused/ignored arguments to or .IR "(void\ *)\ 0". .PP -In Linux kernels before 2.6.26, +Before Linux 2.6.26, .\" See commit 00cd5c37afd5f431ac186dd131705048c0a11fdb .BR init (1), the process with PID 1, may not be traced. @@ -2813,11 +2813,11 @@ parameter, and the return value is the error flag. The glibc wrapper function provides the API given in DESCRIPTION above, with the result being returned via the function return value. .SH BUGS -On hosts with 2.6 kernel headers, +On hosts with Linux 2.6 kernel headers, .B PTRACE_SETOPTIONS -is declared with a different value than the one for 2.4. -This leads to applications compiled with 2.6 kernel -headers failing when run on 2.4 kernels. +is declared with a different value than the one for Linux 2.4. +This leads to applications compiled with Linux 2.6 kernel +headers failing when run on Linux 2.4. This can be worked around by redefining .B PTRACE_SETOPTIONS to diff --git a/man2/query_module.2 b/man2/query_module.2 index c6ddd40ed6..6d6317f921 100644 --- a/man2/query_module.2 +++ b/man2/query_module.2 @@ -19,7 +19,7 @@ size_t " bufsize , .fi .SH DESCRIPTION .IR Note : -This system call is present only in kernels before Linux 2.6. +This system call is present only before Linux 2.6. .PP .BR query_module () requests information from the kernel about loadable modules. @@ -161,9 +161,9 @@ is set to the minimum size needed. .B ENOSYS .BR query_module () is not supported in this version of the kernel -(e.g., the kernel is version 2.6 or later). +(e.g., Linux 2.6 or later). .SH VERSIONS -This system call is present on Linux only up until kernel 2.4; +This system call is present only up until Linux 2.4; it was removed in Linux 2.6. .\" Removed in Linux 2.5.48 .SH STANDARDS diff --git a/man2/quotactl.2 b/man2/quotactl.2 index 9fb81801b4..437259a113 100644 --- a/man2/quotactl.2 +++ b/man2/quotactl.2 @@ -272,7 +272,7 @@ as follows: /* uint64_t is an unsigned 64\-bit integer; uint32_t is an unsigned 32\-bit integer */ -struct dqinfo { /* Defined since kernel 2.4.22 */ +struct dqinfo { /* Defined since Linux 2.4.22 */ uint64_t dqi_bgrace; /* Time before block soft limit becomes hard limit */ uint64_t dqi_igrace; /* Time before inode soft limit diff --git a/man2/read.2 b/man2/read.2 index 401a1bd3f5..13f999e7ba 100644 --- a/man2/read.2 +++ b/man2/read.2 @@ -212,7 +212,7 @@ and .BR readv (2). And among the effects that should be atomic across threads (and processes) are updates of the file offset. -However, on Linux before version 3.14, +However, before Linux 3.14, this was not the case: if two processes that share an open file description (see .BR open (2)) diff --git a/man2/readahead.2 b/man2/readahead.2 index 6021398717..11f850726f 100644 --- a/man2/readahead.2 +++ b/man2/readahead.2 @@ -67,7 +67,7 @@ can be applied. The .BR readahead () system call appeared in Linux 2.4.13; -glibc support has been provided since version 2.3. +glibc support has been provided since glibc 2.3. .SH STANDARDS The .BR readahead () diff --git a/man2/readlink.2 b/man2/readlink.2 index 05aa56bcb3..a9225e8ea7 100644 --- a/man2/readlink.2 +++ b/man2/readlink.2 @@ -188,8 +188,8 @@ is relative and is a file descriptor referring to a file other than a directory. .SH VERSIONS .BR readlinkat () -was added to Linux in kernel 2.6.16; -library support was added to glibc in version 2.4. +was added in Linux 2.6.16; +library support was added in glibc 2.4. .SH STANDARDS .BR readlink (): 4.4BSD @@ -200,7 +200,7 @@ POSIX.1-2001, POSIX.1-2008. .BR readlinkat (): POSIX.1-2008. .SH NOTES -In versions of glibc up to and including glibc 2.4, the return type of +Up to and including glibc 2.4, the return type of .BR readlink () was declared as .IR int . diff --git a/man2/readv.2 b/man2/readv.2 index 90e24654ff..d810f75bba 100644 --- a/man2/readv.2 +++ b/man2/readv.2 @@ -372,16 +372,16 @@ performed the analogous task using a temporary buffer and a call to .PP The need for this extra effort in the glibc wrapper functions went away with Linux 2.2 and later. -However, glibc continued to provide this behavior until version 2.10. -Starting with glibc version 2.9, +However, glibc continued to provide this behavior until glibc 2.10. +Starting with glibc 2.9, the wrapper functions provide this behavior only if the library detects -that the system is running a Linux kernel older than version 2.6.18 +that the system is running a Linux kernel older than Linux 2.6.18 (an arbitrarily selected kernel version). And since glibc 2.20 -(which requires a minimum Linux kernel version of 2.6.32), +(which requires a minimum of Linux 2.6.32), the glibc wrapper functions always just directly invoke the system calls. .SH BUGS -Linux 5.9 and 5.10 have a bug where +Linux 5.9 and Linux 5.10 have a bug where .BR preadv2 () with the .B RWF_NOWAIT diff --git a/man2/reboot.2 b/man2/reboot.2 index 3f7cee8f63..fcdc56a93e 100644 --- a/man2/reboot.2 +++ b/man2/reboot.2 @@ -13,7 +13,7 @@ Standard C library .RI ( libc ", " \-lc ) .SH SYNOPSIS .nf -.RB "/* Since kernel version 2.1.30 there are symbolic names " LINUX_REBOOT_* +.RB "/* Since Linux 2.1.30 there are symbolic names " LINUX_REBOOT_* for the constants and a fourth argument to the call: */ .PP .BR "#include " \ @@ -52,13 +52,13 @@ equals equals .B LINUX_REBOOT_MAGIC2 (that is, 672274793). -However, since 2.1.17 also +However, since Linux 2.1.17 also .B LINUX_REBOOT_MAGIC2A (that is, 85072278) -and since 2.1.97 also +and since Linux 2.1.97 also .B LINUX_REBOOT_MAGIC2B (that is, 369367448) -and since 2.5.71 also +and since Linux 2.5.71 also .B LINUX_REBOOT_MAGIC2C (that is, 537993216) are permitted as values for diff --git a/man2/recvmmsg.2 b/man2/recvmmsg.2 index eea0c99494..63a03bd39d 100644 --- a/man2/recvmmsg.2 +++ b/man2/recvmmsg.2 @@ -149,7 +149,7 @@ See also BUGS. The .BR recvmmsg () system call was added in Linux 2.6.33. -Support in glibc was added in version 2.12. +Support in glibc was added in glibc 2.12. .SH STANDARDS .BR recvmmsg () is Linux-specific. diff --git a/man2/remap_file_pages.2 b/man2/remap_file_pages.2 index d4272f0dfc..f6f69c078b 100644 --- a/man2/remap_file_pages.2 +++ b/man2/remap_file_pages.2 @@ -147,7 +147,7 @@ is invalid. The .BR remap_file_pages () system call appeared in Linux 2.5.46; -glibc support was added in version 2.3.3. +glibc support was added in glibc 2.3.3. .SH STANDARDS The .BR remap_file_pages () diff --git a/man2/removexattr.2 b/man2/removexattr.2 index e4adef15bf..626ad515d7 100644 --- a/man2/removexattr.2 +++ b/man2/removexattr.2 @@ -78,8 +78,8 @@ In addition, the errors documented in .BR stat (2) can also occur. .SH VERSIONS -These system calls have been available on Linux since kernel 2.4; -glibc support is provided since version 2.3. +These system calls have been available since Linux 2.4; +glibc support is provided since glibc 2.3. .SH STANDARDS These system calls are Linux-specific. .\" .SH AUTHORS diff --git a/man2/rename.2 b/man2/rename.2 index a912bbf387..661e582237 100644 --- a/man2/rename.2 +++ b/man2/rename.2 @@ -198,7 +198,7 @@ xfs (Linux 4.0); .\" tmpfs: commit 3b69ff51d087d265aa4af3a532fc4f20bf33e718 .\" cifs: commit 7c33d5972ce382bcc506d16235f1e9b7d22cbef8 .\" -.\" gfs2 in 4.2? +.\" gfs2 in Linux 4.2? .IP \(bu Support for many other filesystems was added in Linux 4.9, including ext2, minix, reiserfs, jfs, vfat, and bpf. @@ -490,11 +490,11 @@ but the caller does not have the capability. .SH VERSIONS .BR renameat () -was added to Linux in kernel 2.6.16; -library support was added to glibc in version 2.4. +was added in Linux 2.6.16; +library support was added in glibc 2.4. .PP .BR renameat2 () -was added to Linux in kernel 3.15; library support was added in glibc 2.28. +was added in Linux 3.15; library support was added in glibc 2.28. .SH STANDARDS .BR rename (): 4.3BSD, C89, C99, POSIX.1-2001, POSIX.1-2008. diff --git a/man2/rt_sigqueueinfo.2 b/man2/rt_sigqueueinfo.2 index 4e65946b93..ebf3c26591 100644 --- a/man2/rt_sigqueueinfo.2 +++ b/man2/rt_sigqueueinfo.2 @@ -168,10 +168,10 @@ was found. .SH VERSIONS The .BR rt_sigqueueinfo () -system call was added to Linux in version 2.2. +system call was added in Linux 2.2. The .BR rt_tgsigqueueinfo () -system call was added to Linux in version 2.6.31. +system call was added in Linux 2.6.31. .SH STANDARDS These system calls are Linux-specific. .SH NOTES diff --git a/man2/sched_setaffinity.2 b/man2/sched_setaffinity.2 index a2d7a264ac..a782a86c43 100644 --- a/man2/sched_setaffinity.2 +++ b/man2/sched_setaffinity.2 @@ -116,7 +116,7 @@ cgroups or the "cpuset" mechanism described in .TP .B EINVAL .RB ( sched_getaffinity () -and, in kernels before 2.6.9, +and, before Linux 2.6.9, .BR sched_setaffinity ()) .I cpusetsize is smaller than the size of the affinity mask used by the kernel. diff --git a/man2/sched_setattr.2 b/man2/sched_setattr.2 index 64fd7d4f60..a41402f637 100644 --- a/man2/sched_setattr.2 +++ b/man2/sched_setattr.2 @@ -407,7 +407,7 @@ instead of .B E2BIG for the case described in ERRORS. .PP -In Linux versions up to 5.3, +Up to Linux 5.3, .BR sched_getattr () failed with the error .B EFBIG diff --git a/man2/seccomp.2 b/man2/seccomp.2 index 80843b4815..583d07e90a 100644 --- a/man2/seccomp.2 +++ b/man2/seccomp.2 @@ -655,7 +655,7 @@ appear to return the value that the tracer puts in the return value register. .\" A related hole, using PTRACE_SYSCALL instead of SECCOMP_RET_TRACE, was .\" changed in arch-specific commits, e.g. 93e35efb8de4 for X86 and .\" 0f3912fd934c for ARM. -Before kernel 4.8, the seccomp check will not be run again after the tracer is +Before Linux 4.8, the seccomp check will not be run again after the tracer is notified. (This means that, on older kernels, seccomp-based sandboxes .B "must not" @@ -823,7 +823,7 @@ but the specified offset was not aligned to a 32-bit boundary or exceeded .IR "sizeof(struct\~seccomp_data)" . .TP .B EINVAL -.\" See kernel/seccomp.c::seccomp_may_assign_mode() in 3.18 sources +.\" See kernel/seccomp.c::seccomp_may_assign_mode() in Linux 3.18 sources A secure computing mode has already been set, and .I operation differs from the existing setting. @@ -842,7 +842,7 @@ was not valid or the length of the filter program was zero or exceeded Out of memory. .TP .B ENOMEM -.\" ENOMEM in kernel/seccomp.c::seccomp_attach_filter() in 3.18 sources +.\" ENOMEM in kernel/seccomp.c::seccomp_attach_filter() in Linux 3.18 sources The total length of all filter programs attached to the calling thread would exceed .B MAX_INSNS_PER_PATH diff --git a/man2/select.2 b/man2/select.2 index f13d204208..63652b77f9 100644 --- a/man2/select.2 +++ b/man2/select.2 @@ -15,7 +15,7 @@ .\" Modified Thu Feb 9 22:32:09 CET 2001 by bert hubert , aeb .\" Modified Mon Nov 11 14:35:00 PST 2002 by Ben Woodard .\" 2005-03-11, mtk, modified pselect() text (it is now a system -.\" call in 2.6.16. +.\" call in Linux 2.6.16. .\" .TH select 2 (date) "Linux man-pages (unreleased)" .SH NAME @@ -422,7 +422,7 @@ is invalid. Unable to allocate memory for internal tables. .SH VERSIONS .BR pselect () -was added to Linux in kernel 2.6.16. +was added in Linux 2.6.16. Prior to this, .BR pselect () was emulated in glibc (but see BUGS). @@ -622,7 +622,7 @@ that did not take a .I sigmask argument. .PP -In glibc versions 2.1 to 2.2.1, +From glibc 2.1 to glibc 2.2.1, one must define .B _GNU_SOURCE in order to obtain the declaration of @@ -667,7 +667,7 @@ According to POSIX, any such file descriptor that is specified in one of the sets should result in the error .BR EBADF . .PP -Starting with version 2.1, glibc provided an emulation of +Starting with glibc 2.1, glibc provided an emulation of .BR pselect () that was implemented using .BR sigprocmask (2) diff --git a/man2/semget.2 b/man2/semget.2 index 277cc0e20d..a15b472a99 100644 --- a/man2/semget.2 +++ b/man2/semget.2 @@ -245,7 +245,7 @@ call: .TP .B SEMMNI System-wide limit on the number of semaphore sets. -On Linux systems before version 3.19, +Before Linux 3.19, the default value for this limit was 128. Since Linux 3.19, .\" commit e843e7d2c88b7db107a86bd2c7145dc715c058f4 @@ -256,7 +256,7 @@ On Linux, this limit can be read and modified via the fourth field of .TP .B SEMMSL Maximum number of semaphores per semaphore ID. -On Linux systems before version 3.19, +Before Linux 3.19, the default value for this limit was 250. Since Linux 3.19, .\" commit e843e7d2c88b7db107a86bd2c7145dc715c058f4 diff --git a/man2/semop.2 b/man2/semop.2 index ad184829e2..bd85fdd2e9 100644 --- a/man2/semop.2 +++ b/man2/semop.2 @@ -358,10 +358,10 @@ the implementation dependent maximum value for .SH VERSIONS .BR semtimedop () first appeared in Linux 2.5.52, -and was subsequently backported into kernel 2.4.22. +and was subsequently backported into Linux 2.4.22. Glibc support for .BR semtimedop () -first appeared in version 2.3.3. +first appeared in Linux 2.3.3. .SH STANDARDS POSIX.1-2001, POSIX.1-2008, SVr4. .\" SVr4 documents additional error conditions EINVAL, EFBIG, ENOSPC. @@ -475,10 +475,10 @@ Linux adopts a third approach: decreasing the semaphore value as far as possible (i.e., to zero) and allowing process termination to proceed immediately. .PP -In kernels 2.6.x, x <= 10, there is a bug that in some circumstances +In Linux 2.6.x, x <= 10, there is a bug that in some circumstances prevents a thread that is waiting for a semaphore value to become zero from being woken up when the value does actually become zero. -This bug is fixed in kernel 2.6.11. +This bug is fixed in Linux 2.6.11. .\" The bug report: .\" http://marc.theaimsgroup.com/?l=linux-kernel&m=110260821123863&w=2 .\" the fix: diff --git a/man2/send.2 b/man2/send.2 index 86e40b0850..3f0b744301 100644 --- a/man2/send.2 +++ b/man2/send.2 @@ -142,7 +142,7 @@ The .I flags argument is the bitwise OR of zero or more of the following flags. -.\" FIXME . ? document MSG_PROXY (which went away in 2.3.15) +.\" FIXME . ? document MSG_PROXY (which went away in Linux 2.3.15) .TP .BR MSG_CONFIRM " (since Linux 2.3.15)" Tell the link layer that forward progress happened: you got a successful diff --git a/man2/sendfile.2 b/man2/sendfile.2 index 9dbe1691c4..07a2c5b35d 100644 --- a/man2/sendfile.2 +++ b/man2/sendfile.2 @@ -97,7 +97,7 @@ argument must correspond to a file which supports operations (i.e., it cannot be a socket). .PP -In Linux kernels before 2.6.33, +Before Linux 2.6.33, .I out_fd must refer to a socket. Since Linux 2.6.33 it can be any file. diff --git a/man2/sendmmsg.2 b/man2/sendmmsg.2 index f2c77444e7..4e5475c45a 100644 --- a/man2/sendmmsg.2 +++ b/man2/sendmmsg.2 @@ -130,7 +130,7 @@ See also BUGS. The .BR sendmmsg () system call was added in Linux 3.0. -Support in glibc was added in version 2.14. +Support in glibc was added in Linux 2.14. .SH STANDARDS .BR sendmmsg () is Linux-specific. diff --git a/man2/set_mempolicy.2 b/man2/set_mempolicy.2 index 6a90c2b449..4998ecb530 100644 --- a/man2/set_mempolicy.2 +++ b/man2/set_mempolicy.2 @@ -322,7 +322,7 @@ Insufficient kernel memory was available. .SH VERSIONS The .BR set_mempolicy () -system call was added to the Linux kernel in version 2.6.7. +system call was added in Linux 2.6.7. .SH STANDARDS This system call is Linux-specific. .SH NOTES diff --git a/man2/setfsgid.2 b/man2/setfsgid.2 index 0b5bb5c035..eb35af7e1d 100644 --- a/man2/setfsgid.2 +++ b/man2/setfsgid.2 @@ -49,7 +49,7 @@ saved set-group-ID, or current the filesystem user ID. On both success and failure, this call returns the previous filesystem group ID of the caller. .SH VERSIONS -This system call is present in Linux since version 1.2. +This system call is present since Linux 1.2. .\" This system call is present since Linux 1.1.44 .\" and in libc since libc 4.7.6. .SH STANDARDS diff --git a/man2/setfsuid.2 b/man2/setfsuid.2 index f908f6ac9e..167eca1e3b 100644 --- a/man2/setfsuid.2 +++ b/man2/setfsuid.2 @@ -60,7 +60,7 @@ saved set-user-ID, or current filesystem user ID. On both success and failure, this call returns the previous filesystem user ID of the caller. .SH VERSIONS -This system call is present in Linux since version 1.2. +This system call is present since Linux 1.2. .\" This system call is present since Linux 1.1.44 .\" and in libc since libc 4.7.6. .SH STANDARDS diff --git a/man2/setns.2 b/man2/setns.2 index f8ed48a668..1a7ede0a03 100644 --- a/man2/setns.2 +++ b/man2/setns.2 @@ -305,8 +305,8 @@ is a PID file descriptor but the process it refers to no longer exists .SH VERSIONS The .BR setns () -system call first appeared in Linux in kernel 3.0; -library support was added to glibc in version 2.14. +system call first appeared in Linux 3.0; +library support was added in glibc 2.14. .SH STANDARDS The .BR setns () diff --git a/man2/setresuid.2 b/man2/setresuid.2 index cf1d176b7e..081a8e920a 100644 --- a/man2/setresuid.2 +++ b/man2/setresuid.2 @@ -104,7 +104,7 @@ they also appear on HP-UX and some of the BSDs. .SH NOTES Under HP-UX and FreeBSD, the prototype is found in .IR . -Under Linux, the prototype is provided by glibc since version 2.3.2. +Under Linux, the prototype is provided since glibc 2.3.2. .PP The original Linux .BR setresuid () diff --git a/man2/setxattr.2 b/man2/setxattr.2 index aa7850dfe2..8c658223cc 100644 --- a/man2/setxattr.2 +++ b/man2/setxattr.2 @@ -138,8 +138,8 @@ or .I value exceeds a filesystem-specific limit. .SH VERSIONS -These system calls have been available on Linux since kernel 2.4; -glibc support is provided since version 2.3. +These system calls have been available since Linux 2.4; +glibc support is provided since glibc 2.3. .SH STANDARDS These system calls are Linux-specific. .\" .SH AUTHORS diff --git a/man2/shmctl.2 b/man2/shmctl.2 index 329007f9cc..6d330b6911 100644 --- a/man2/shmctl.2 +++ b/man2/shmctl.2 @@ -16,7 +16,7 @@ .\" Updated shmid_ds structure definitions .\" Added information on SHM_DEST and SHM_LOCKED flags .\" Noted that CAP_IPC_LOCK is not required for SHM_UNLOCK -.\" since kernel 2.6.9 +.\" since Linux 2.6.9 .\" Modified, 2004-11-25, mtk, notes on 2.6.9 RLIMIT_MEMLOCK changes .\" 2005-04-25, mtk -- noted aberrant Linux behavior w.r.t. new .\" attaches to a segment that has already been marked for deletion. @@ -325,12 +325,12 @@ will be set. .BR SHM_UNLOCK " (Linux-specific)" Unlock the segment, allowing it to be swapped out. .PP -In kernels before 2.6.10, only a privileged process +Before Linux 2.6.10, only a privileged process could employ .B SHM_LOCK and .BR SHM_UNLOCK . -Since kernel 2.6.10, an unprivileged process can employ these operations +Since Linux 2.6.10, an unprivileged process can employ these operations if its effective UID matches the owner or creator UID of the segment, and (for .BR SHM_LOCK ) @@ -338,10 +338,10 @@ the amount of memory to be locked falls within the .B RLIMIT_MEMLOCK resource limit (see .BR setrlimit (2)). -.\" There was some weirdness in 2.6.9: SHM_LOCK and SHM_UNLOCK could +.\" There was some weirdness in Linux 2.6.9: SHM_LOCK and SHM_UNLOCK could .\" be applied to a segment, regardless of ownership of the segment. .\" This was a botch-up in the move to RLIMIT_MEMLOCK, and was fixed -.\" in 2.6.10. MTK, May 2005 +.\" in Linux 2.6.10. MTK, May 2005 .SH RETURN VALUE A successful .B IPC_INFO @@ -402,7 +402,7 @@ operation, the index value specified in referred to an array slot that is currently unused. .TP .B ENOMEM -(In kernels since 2.6.9), +(Since Linux 2.6.9), .B SHM_LOCK was specified and the size of the to-be-locked segment would mean that the total bytes in locked shared memory segments would exceed @@ -429,7 +429,7 @@ and the process was not privileged (Linux: did not have the .B CAP_SYS_ADMIN capability). .IP -Or (in kernels before 2.6.9), +Or (before Linux 2.6.9), .B SHM_LOCK or .B SHM_UNLOCK diff --git a/man2/shmget.2 b/man2/shmget.2 index 83447aaba9..dfb0466cd9 100644 --- a/man2/shmget.2 +++ b/man2/shmget.2 @@ -383,7 +383,7 @@ The implementation has no specific limits for the per-process maximum number of shared memory segments .RB ( SHMSEG ). .SS Linux notes -Until version 2.3.30, Linux would return +Until Linux 2.3.30, Linux would return .B EIDRM for a .BR shmget () diff --git a/man2/shmop.2 b/man2/shmop.2 index cd91c99315..4be21d31bf 100644 --- a/man2/shmop.2 +++ b/man2/shmop.2 @@ -197,7 +197,7 @@ can fail with one of the following errors: There is no shared memory segment attached at .IR shmaddr ; or, -.\" The following since 2.6.17-rc1: +.\" The following since Linux 2.6.17-rc1: .I shmaddr is not aligned on a page boundary. .SH STANDARDS diff --git a/man2/sigaction.2 b/man2/sigaction.2 index b6ad9d63fd..dfb94fe4fb 100644 --- a/man2/sigaction.2 +++ b/man2/sigaction.2 @@ -459,24 +459,24 @@ these fields do not include the times used by waited-for children (unlike .BR getrusage (2) and .BR times (2)). -In kernels up to 2.6, and since 2.6.27, these fields report +Up to Linux 2.6, and since Linux 2.6.27, these fields report CPU time in units of .IR sysconf(_SC_CLK_TCK) . -In 2.6 kernels before 2.6.27, +In Linux 2.6 kernels before Linux 2.6.27, a bug meant that these fields reported time in units of the (configurable) system jiffy (see .BR time (7)). .\" FIXME . .\" When si_utime and si_stime where originally implemented, the .\" measurement unit was HZ, which was the same as clock ticks -.\" (sysconf(_SC_CLK_TCK)). In 2.6, HZ became configurable, and +.\" (sysconf(_SC_CLK_TCK)). In Linux 2.6, HZ became configurable, and .\" was *still* used as the unit to return the info these fields, .\" with the result that the field values depended on the .\" configured HZ. Of course, the should have been measured in .\" USER_HZ instead, so that sysconf(_SC_CLK_TCK) could be used to .\" convert to seconds. I have a queued patch to fix this: .\" http://thread.gmane.org/gmane.linux.kernel/698061/ . -.\" This patch made it into 2.6.27. +.\" This patch made it into Linux 2.6.27. .\" But note that these fields still don't return the times of .\" waited-for children (as is done by getrusage() and times() .\" and wait4()). Solaris 8 does include child times. @@ -658,7 +658,7 @@ AIO completed. .B SI_SIGIO Queued .B SIGIO -(only in kernels up to Linux 2.2; from Linux 2.4 onward +(only up to Linux 2.2; from Linux 2.4 onward .BR SIGIO / SIGPOLL fills in .I si_code @@ -668,9 +668,9 @@ as described below). .BR tkill (2) or .BR tgkill (2). -.\" SI_DETHREAD is defined in 2.6.9 sources, but isn't implemented +.\" SI_DETHREAD is defined in Linux 2.6.9 sources, but isn't implemented .\" It appears to have been an idea that was tried during 2.5.6 -.\" through to 2.5.24 and then was backed out. +.\" through to Linux 2.5.24 and then was backed out. .RE .PP The following values can be placed in @@ -1118,14 +1118,14 @@ for all of the fields of the .I siginfo_t that are relevant for that signal. .PP -In kernels up to and including 2.6.13, specifying +Up to and including Linux 2.6.13, specifying .B SA_NODEFER in .I sa_flags prevents not only the delivered signal from being masked during execution of the handler, but also the signals specified in .IR sa_mask . -This bug was fixed in kernel 2.6.14. +This bug was fixed in Linux 2.6.14. .\" commit 69be8f189653cd81aae5a74e26615b12871bb72e .SH EXAMPLES See diff --git a/man2/signalfd.2 b/man2/signalfd.2 index e72ddea279..5b2647e705 100644 --- a/man2/signalfd.2 +++ b/man2/signalfd.2 @@ -86,7 +86,7 @@ flag in .BR open (2) for reasons why this may be useful. .PP -In Linux up to version 2.6.26, the +Up to Linux 2.6.26, the .I flags argument is unused, and must be specified as zero. .PP @@ -329,12 +329,12 @@ Could not mount (internal) anonymous inode device. There was insufficient memory to create a new signalfd file descriptor. .SH VERSIONS .BR signalfd () -is available on Linux since kernel 2.6.22. -Working support is provided in glibc since version 2.8. +is available since Linux 2.6.22. +Working support is provided since glibc 2.8. .\" signalfd() is in glibc 2.7, but reportedly does not build The .BR signalfd4 () -system call (see NOTES) is available on Linux since kernel 2.6.27. +system call (see NOTES) is available since Linux 2.6.27. .SH STANDARDS .BR signalfd () and @@ -428,13 +428,13 @@ wrapper function will use .BR signalfd4 () where it is available. .SH BUGS -In kernels before 2.6.25, the +Before Linux 2.6.25, the .I ssi_ptr and .I ssi_int fields are not filled in with the data accompanying a signal sent by .BR sigqueue (3). -.\" The fix also was put into 2.6.24.5 +.\" The fix also was put into Linux 2.6.24.5 .SH EXAMPLES The program below accepts the signals .B SIGINT diff --git a/man2/sigpending.2 b/man2/sigpending.2 index 8c655ef974..517058b9eb 100644 --- a/man2/sigpending.2 +++ b/man2/sigpending.2 @@ -95,7 +95,7 @@ wrapper function hides these details from us, transparently calling when the kernel provides it. .\" .SH BUGS -In versions of glibc up to and including 2.2.1, +Up to and including glibc 2.2.1, there is a bug in the wrapper function for .BR sigpending () which means that information about pending real-time signals diff --git a/man2/sigreturn.2 b/man2/sigreturn.2 index 0548c8ec33..69d7b1d16b 100644 --- a/man2/sigreturn.2 +++ b/man2/sigreturn.2 @@ -26,7 +26,7 @@ when the process is rescheduled onto the CPU), it creates a new frame on the user-space stack where it saves various pieces of process context (processor status word, registers, signal mask, and signal stack settings). -.\" See arch/x86/kernel/signal.c::__setup_frame() [in 3.17 source code] +.\" See arch/x86/kernel/signal.c::__setup_frame() [in Linux 3.17 source code] .PP The kernel also arranges that, during the transition back to user mode, the signal handler is called, and that, upon return from the handler, diff --git a/man2/splice.2 b/man2/splice.2 index b5c453771f..136137c758 100644 --- a/man2/splice.2 +++ b/man2/splice.2 @@ -152,7 +152,7 @@ The target filesystem doesn't support splicing. .TP .B EINVAL The target file is opened in append mode. -.\" The append-mode error is given since 2.6.27; in earlier kernels, +.\" The append-mode error is given since Linux 2.6.27; in earlier kernels, .\" splice() in append mode was broken .TP .B EINVAL @@ -180,7 +180,7 @@ was not NULL, but the corresponding file descriptor refers to a pipe. The .BR splice () system call first appeared in Linux 2.6.17; -library support was added to glibc in version 2.5. +library support was added in glibc 2.5. .SH STANDARDS This system call is Linux-specific. .SH NOTES diff --git a/man2/spu_create.2 b/man2/spu_create.2 index 5b8263b252..ae59baeb9c 100644 --- a/man2/spu_create.2 +++ b/man2/spu_create.2 @@ -247,7 +247,7 @@ By convention, it gets mounted in .SH VERSIONS The .BR spu_create () -system call was added to Linux in kernel 2.6.16. +system call was added in Linux 2.6.16. .SH STANDARDS This call is Linux-specific and implemented only on the PowerPC architecture. diff --git a/man2/spu_run.2 b/man2/spu_run.2 index dfe5d9c839..00d5529860 100644 --- a/man2/spu_run.2 +++ b/man2/spu_run.2 @@ -184,7 +184,7 @@ loaded. .SH VERSIONS The .BR spu_run () -system call was added to Linux in kernel 2.6.16. +system call was added in Linux 2.6.16. .SH STANDARDS This call is Linux-specific and implemented only by the PowerPC architecture. diff --git a/man2/stat.2 b/man2/stat.2 index 33541f0cf4..6096f8f7d1 100644 --- a/man2/stat.2 +++ b/man2/stat.2 @@ -308,8 +308,8 @@ on a file whose size exceeds bytes. .SH VERSIONS .BR fstatat () -was added to Linux in kernel 2.6.16; -library support was added to glibc in version 2.4. +was added in Linux 2.6.16; +library support was added in glibc 2.4. .SH STANDARDS .BR stat (), .BR fstat (), diff --git a/man2/statx.2 b/man2/statx.2 index ca99f94639..960bc3c0ca 100644 --- a/man2/statx.2 +++ b/man2/statx.2 @@ -590,7 +590,7 @@ is relative and is a file descriptor referring to a file other than a directory. .SH VERSIONS .BR statx () -was added to Linux in kernel 4.11; library support was added in glibc 2.28. +was added in Linux 4.11; library support was added in glibc 2.28. .SH STANDARDS .BR statx () is Linux-specific. diff --git a/man2/subpage_prot.2 b/man2/subpage_prot.2 index 6a559e7162..374ddce9d8 100644 --- a/man2/subpage_prot.2 +++ b/man2/subpage_prot.2 @@ -4,7 +4,7 @@ .\" SPDX-License-Identifier: Linux-man-pages-copyleft .\" .\" Various pieces of text taken from the kernel source and the commentary -.\" in kernel commit fa28237cfcc5827553044cbd6ee52e33692b0faa +.\" in Linux commit fa28237cfcc5827553044cbd6ee52e33692b0faa .\" both written by Paul Mackerras .\" .TH subpage_prot 2 (date) "Linux man-pages (unreleased)" diff --git a/man2/swapon.2 b/man2/swapon.2 index 3395f74173..db9dc3dff7 100644 --- a/man2/swapon.2 +++ b/man2/swapon.2 @@ -160,11 +160,11 @@ The partition or path must be prepared with There is an upper limit on the number of swap files that may be used, defined by the kernel constant .BR MAX_SWAPFILES . -Before kernel 2.4.10, +Before Linux 2.4.10, .B MAX_SWAPFILES has the value 8; -since kernel 2.4.10, it has the value 32. -Since kernel 2.6.18, the limit is decreased by 2 (thus: 30) +since Linux 2.4.10, it has the value 32. +Since Linux 2.6.18, the limit is decreased by 2 (thus: 30) if the kernel is built with the .B CONFIG_MIGRATION option @@ -172,20 +172,20 @@ option .BR mbind (2) and .BR migrate_pages (2)). -Since kernel 2.6.32, the limit is further decreased by 1 +Since Linux 2.6.32, the limit is further decreased by 1 if the kernel is built with the .B CONFIG_MEMORY_FAILURE option. -Since kernel 5.14, the limit is further decreased by 4 +Since Linux 5.14, the limit is further decreased by 4 if the kernel is built with the .B CONFIG_DEVICE_PRIVATE option. .PP -Discard of swap pages was introduced in kernel 2.6.29, +Discard of swap pages was introduced in Linux 2.6.29, then made conditional on the .B SWAP_FLAG_DISCARD -flag in kernel 2.6.36, +flag in Linux 2.6.36, .\" To be precise: 2.6.35.5 which still discards the entire swap area when diff --git a/man2/symlink.2 b/man2/symlink.2 index 6f31302cc5..5662a991df 100644 --- a/man2/symlink.2 +++ b/man2/symlink.2 @@ -216,8 +216,8 @@ does not support the creation of symbolic links. is on a read-only filesystem. .SH VERSIONS .BR symlinkat () -was added to Linux in kernel 2.6.16; -library support was added to glibc in version 2.4. +was added in Linux 2.6.16; +library support was added in glibc 2.4. .SH STANDARDS .BR symlink (): SVr4, 4.3BSD, POSIX.1-2001, POSIX.1-2008. diff --git a/man2/sync.2 b/man2/sync.2 index 8a3c503353..f7c77c9fdd 100644 --- a/man2/sync.2 +++ b/man2/sync.2 @@ -90,7 +90,7 @@ storage space. .SH VERSIONS .BR syncfs () first appeared in Linux 2.6.39; -library support was added to glibc in version 2.14. +library support was added in glibc 2.14. .SH STANDARDS .BR sync (): POSIX.1-2001, POSIX.1-2008, SVr4, 4.3BSD. @@ -121,7 +121,7 @@ provide the same guarantees as called on every file in the system or filesystem respectively. .PP -In mainline kernel versions prior to 5.8, +In mainline kernel versions prior to Linux 5.8, .BR syncfs () will fail only when passed a bad file descriptor .RB ( EBADF ). @@ -133,7 +133,7 @@ to be written back since the last .BR syncfs () call. .SH BUGS -Before version 1.3.20 Linux did not wait for I/O to complete +Before Linux 1.3.20, Linux did not wait for I/O to complete before returning. .SH SEE ALSO .BR sync (1), diff --git a/man2/sync_file_range.2 b/man2/sync_file_range.2 index 2a3f0a5b6e..7557cad448 100644 --- a/man2/sync_file_range.2 +++ b/man2/sync_file_range.2 @@ -156,7 +156,7 @@ refers to something other than a regular file, a block device, or a directory. .SH VERSIONS .BR sync_file_range () -appeared on Linux in kernel 2.6.17. +appeared in Linux 2.6.17. .SH STANDARDS This system call is Linux-specific, and should be avoided in portable programs. diff --git a/man2/syscalls.2 b/man2/syscalls.2 index 94196cad04..b392d078fb 100644 --- a/man2/syscalls.2 +++ b/man2/syscalls.2 @@ -70,66 +70,66 @@ or have appeared since that kernel version. Note the following points: .IP \(bu 3 Where no kernel version is indicated, -the system call appeared in kernel 1.0 or earlier. +the system call appeared in Linux 1.0 or earlier. .IP \(bu Where a system call is marked "1.2" -this means the system call probably appeared in a 1.1.x kernel version, +this means the system call probably appeared in a Linux 1.1.x kernel version, and first appeared in a stable kernel with 1.2. (Development of the 1.2 kernel was initiated from a branch of kernel 1.0.6 via the 1.1.x unstable kernel series.) .IP \(bu Where a system call is marked "2.0" -this means the system call probably appeared in a 1.3.x kernel version, -and first appeared in a stable kernel with 2.0. -(Development of the 2.0 kernel was initiated from a branch of kernel -1.2.x, somewhere around 1.2.10, -via the 1.3.x unstable kernel series.) -.\" Was kernel 2.0 started from a branch of 1.2.10? +this means the system call probably appeared in a Linux 1.3.x kernel version, +and first appeared in a stable kernel with Linux 2.0. +(Development of the Linux 2.0 kernel was initiated from a branch of +Linux 1.2.x, somewhere around Linux 1.2.10, +via the Linux 1.3.x unstable kernel series.) +.\" Was Linux 2.0 started from a branch of Linux 1.2.10? .\" At least from the timestamps of the tarballs of -.\" of 1.2.10 and 1.3.0, that's how it looks, but in +.\" of Linux 1.2.10 and Linux 1.3.0, that's how it looks, but in .\" fact the diff doesn't seem very clear, the -.\" 1.3.0 .tar.bz is much bigger (2.0 MB) than the -.\" 1.2.10 .tar.bz2 (1.8 MB), and AEB points out the -.\" timestamps of some files in 1.3.0 seem to be older -.\" than those in 1.2.10. All of this suggests +.\" Linux 1.3.0 .tar.bz is much bigger (2.0 MB) than the +.\" Linux 1.2.10 .tar.bz2 (1.8 MB), and AEB points out the +.\" timestamps of some files in Linux 1.3.0 seem to be older +.\" than those in Linux 1.2.10. All of this suggests .\" that there might not have been a clean branch point. .IP \(bu Where a system call is marked "2.2" -this means the system call probably appeared in a 2.1.x kernel version, -and first appeared in a stable kernel with 2.2.0. -(Development of the 2.2 kernel was initiated from a branch of kernel -2.0.21 via the 2.1.x unstable kernel series.) +this means the system call probably appeared in a Linux 2.1.x kernel version, +and first appeared in a stable kernel with Linux 2.2.0. +(Development of the Linux 2.2 kernel was initiated from a branch of kernel +Linux 2.0.21 via the Linux 2.1.x unstable kernel series.) .IP \(bu Where a system call is marked "2.4" -this means the system call probably appeared in a 2.3.x kernel version, -and first appeared in a stable kernel with 2.4.0. -(Development of the 2.4 kernel was initiated from a branch of -kernel 2.2.8 via the 2.3.x unstable kernel series.) +this means the system call probably appeared in a Linux 2.3.x kernel version, +and first appeared in a stable kernel with Linux 2.4.0. +(Development of the Linux 2.4 kernel was initiated from a branch of +Linux 2.2.8 via the Linux 2.3.x unstable kernel series.) .IP \(bu Where a system call is marked "2.6" -this means the system call probably appeared in a 2.5.x kernel version, -and first appeared in a stable kernel with 2.6.0. -(Development of kernel 2.6 was initiated from a branch -of kernel 2.4.15 via the 2.5.x unstable kernel series.) +this means the system call probably appeared in a Linux 2.5.x kernel version, +and first appeared in a stable kernel with Linux 2.6.0. +(Development of Linux 2.6 was initiated from a branch +of Linux 2.4.15 via the Linux 2.5.x unstable kernel series.) .IP \(bu -Starting with kernel 2.6.0, the development model changed, -and new system calls may appear in each 2.6.x release. +Starting with Linux 2.6.0, the development model changed, +and new system calls may appear in each Linux 2.6.x release. In this case, the exact version number where the system call appeared is shown. -This convention continues with the 3.x kernel series, -which followed on from kernel 2.6.39; and the 4.x kernel series, -which followed on from kernel 3.19; and the 5.x kernel series, -which followed on from kernel 4.20. +This convention continues with the Linux 3.x kernel series, +which followed on from Linux 2.6.39; and the Linux 4.x kernel series, +which followed on from Linux 3.19; and the Linux 5.x kernel series, +which followed on from Linux 4.20. .IP \(bu In some cases, a system call was added to a stable kernel series after it branched from the previous stable kernel series, and then backported into the earlier stable kernel series. -For example some system calls that appeared in 2.6.x were also backported -into a 2.4.x release after 2.4.15. +For example some system calls that appeared in Linux 2.6.x were also backported +into a Linux 2.4.x release after Linux 2.4.15. When this is so, the version where the system call appeared in both of the major kernel series is listed. .PP -The list of system calls that are available as at kernel 5.14 +The list of system calls that are available as at Linux 5.14 (or in a few cases only on older kernels) is as follows: .\" .\" Looking at scripts/checksyscalls.sh in the kernel source is @@ -874,7 +874,7 @@ and exist as library routines. The slot for .BR phys (2) -is in use since kernel 2.1.116 for +is in use since Linux 2.1.116 for .BR umount (2); .BR phys (2) will never be implemented. @@ -887,7 +887,7 @@ and may never be in the standard kernel. .PP There was briefly .BR set_zone_reclaim (2), -added in Linux 2.6.13, and removed in 2.6.16; +added in Linux 2.6.13, and removed in Linux 2.6.16; this system call was never available to user space. .\" .SS System calls on removed ports @@ -1075,7 +1075,7 @@ the other versions are obsolete. .IP \(bu The .I rt_sig* -calls were added in kernel 2.2 to support the addition +calls were added in Linux 2.2 to support the addition of real-time signals (see .BR signal (7)). These system calls supersede the older system calls of the same @@ -1122,7 +1122,7 @@ s390x is the only 64-bit architecture that has .\" and .\" .IR sys_sysctl (). .\" -.\" In kernel 2.1.81, +.\" In Linux 2.1.81, .\" .BR lchown (2) .\" and .\" .BR chown (2) diff --git a/man2/sysctl.2 b/man2/sysctl.2 index 10b88834b6..679b20a74d 100644 --- a/man2/sysctl.2 +++ b/man2/sysctl.2 @@ -75,7 +75,7 @@ non-NULL, but allowed zero room in was not found. .SH VERSIONS This system call first appeared in Linux 1.3.57. -It was removed in Linux 5.5; glibc support was removed in version 2.32. +It was removed in Linux 5.5; glibc support was removed in glibc 2.32. .SH STANDARDS This call is Linux-specific, and should not be used in programs intended to be portable. diff --git a/man2/syslog.2 b/man2/syslog.2 index 4604c94850..a824250e45 100644 --- a/man2/syslog.2 +++ b/man2/syslog.2 @@ -54,13 +54,13 @@ are stored (regardless of their log level). In early kernels, .B LOG_BUF_LEN had the value 4096; -from kernel 1.3.54, it was 8192; -from kernel 2.1.113, it was 16384; -since kernel 2.4.23/2.6, the value is a kernel configuration option +from Linux 1.3.54, it was 8192; +from Linux 2.1.113, it was 16384; +since Linux 2.4.23/2.6, the value is a kernel configuration option .RB ( CONFIG_LOG_BUF_SHIFT , default value dependent on the architecture). .\" Under "General setup" ==> "Kernel log buffer size" -.\" For 2.6, precisely the option seems to have appeared in 2.5.55. +.\" For Linux 2.6, precisely the option seems to have appeared in Linux 2.5.55. Since Linux 2.6.6, the size can be queried with command type 10 (see below). .SS Commands The \fItype\fP argument determines the action taken by this function. @@ -209,7 +209,7 @@ and arguments are ignored. .PP All commands except 3 and 10 require privilege. -In Linux kernels before 2.6.37, +In Linux kernels before Linux 2.6.37, command types 3 and 10 are allowed to unprivileged processes; since Linux 2.6.37, these commands are allowed to unprivileged processes only if diff --git a/man2/tee.2 b/man2/tee.2 index 5b549c6b69..6c412a475b 100644 --- a/man2/tee.2 +++ b/man2/tee.2 @@ -104,7 +104,7 @@ Out of memory. The .BR tee () system call first appeared in Linux 2.6.17; -library support was added to glibc in version 2.5. +library support was added in glibc 2.5. .SH STANDARDS This system call is Linux-specific. .SH NOTES diff --git a/man2/timer_create.2 b/man2/timer_create.2 index bb5e6e2384..ea87e0743a 100644 --- a/man2/timer_create.2 +++ b/man2/timer_create.2 @@ -50,7 +50,7 @@ A nonsettable monotonically increasing clock that measures time from some unspecified point in the past that does not change after system startup. .\" Note: the CLOCK_MONOTONIC_RAW clock added for clock_gettime() -.\" in 2.6.28 is not supported for POSIX timers -- mtk, Feb 2009 +.\" in Linux 2.6.28 is not supported for POSIX timers -- mtk, Feb 2009 .TP .BR CLOCK_PROCESS_CPUTIME_ID " (since Linux 2.6.12)" A clock that measures (user and system) CPU time consumed by @@ -59,7 +59,7 @@ A clock that measures (user and system) CPU time consumed by .BR CLOCK_THREAD_CPUTIME_ID " (since Linux 2.6.12)" A clock that measures (user and system) CPU time consumed by the calling thread. -.\" The CLOCK_MONOTONIC_RAW that was added in 2.6.28 can't be used +.\" The CLOCK_MONOTONIC_RAW that was added in Linux 2.6.28 can't be used .\" to create a timer -- mtk, Feb 2009 .TP .BR CLOCK_BOOTTIME " (Since Linux 2.6.39)" @@ -315,7 +315,7 @@ Prior to this, glibc provided an incomplete user-space implementation .RB ( CLOCK_REALTIME timers only) using POSIX threads, -and in glibc versions before 2.17, +and before glibc 2.17, .\" glibc commit 93a78ac437ba44f493333d7e2a4b0249839ce460 the implementation falls back to this technique on systems running pre-2.6 Linux kernels. diff --git a/man2/timerfd_create.2 b/man2/timerfd_create.2 index 1b2fb3ff9b..967664eef8 100644 --- a/man2/timerfd_create.2 +++ b/man2/timerfd_create.2 @@ -464,13 +464,13 @@ is not properly initialized (one of the falls outside the range zero to 999,999,999). .TP .B EINVAL -.\" This case only checked since 2.6.29, and 2.2.2[78].some-stable-version. +.\" This case only checked since Linux 2.6.29, and Linux 2.2.2[78].some-stable-version. .\" In older kernel versions, no check was made for invalid flags. .I flags is invalid. .SH VERSIONS -These system calls are available on Linux since kernel 2.6.25. -Library support is provided by glibc since version 2.8. +These system calls are available since Linux 2.6.25. +Library support is provided since glibc 2.8. .SH STANDARDS These system calls are Linux-specific. .SH NOTES diff --git a/man2/times.2 b/man2/times.2 index 3526aea814..4f6aac5784 100644 --- a/man2/times.2 +++ b/man2/times.2 @@ -9,8 +9,8 @@ .\" Modified 13 Jun 02, Michael Kerrisk .\" Added note on nonstandard behavior when SIGCHLD is ignored. .\" Modified 2004-11-16, mtk, Noted that the nonconformance when -.\" SIGCHLD is being ignored is fixed in 2.6.9; other minor changes -.\" Modified 2004-12-08, mtk, in 2.6 times() return value changed +.\" SIGCHLD is being ignored is fixed in Linux 2.6.9; other minor changes +.\" Modified 2004-12-08, mtk, in Linux 2.6 times() return value changed .\" 2005-04-13, mtk .\" Added notes on nonstandard behavior: Linux allows 'buf' to .\" be NULL, but POSIX.1 doesn't specify this and it's nonportable. @@ -114,7 +114,7 @@ In POSIX.1-1996 the symbol \fBCLK_TCK\fP (defined in is mentioned as obsolescent. It is obsolete now. .PP -In Linux kernel versions before 2.6.9, +Before Linux 2.6.9, if the disposition of .B SIGCHLD is set to diff --git a/man2/tkill.2 b/man2/tkill.2 index 9f12355dac..05e19e295a 100644 --- a/man2/tkill.2 +++ b/man2/tkill.2 @@ -115,7 +115,7 @@ was added in Linux 2.5.75. .PP Library support for .BR tgkill () -was added to glibc in version 2.30. +was added in glibc 2.30. .SH STANDARDS .BR tkill () and diff --git a/man2/umount.2 b/man2/umount.2 index cf1f49332d..fc0e32feec 100644 --- a/man2/umount.2 +++ b/man2/umount.2 @@ -86,7 +86,7 @@ or .BR MNT_DETACH . .TP .BR UMOUNT_NOFOLLOW " (since Linux 2.6.34)" -.\" Later added to 2.6.33-stable +.\" Later added to Linux 2.6.33-stable Don't dereference .I target if it is a symbolic link. @@ -159,7 +159,7 @@ The caller does not have the required privileges. and .B MNT_EXPIRE .\" http://sourceware.org/bugzilla/show_bug.cgi?id=10092 -are available in glibc since version 2.11. +are available since glibc 2.11. .SH STANDARDS These functions are Linux-specific and should not be used in programs intended to be portable. diff --git a/man2/unlink.2 b/man2/unlink.2 index 2e88d312e2..c25860632d 100644 --- a/man2/unlink.2 +++ b/man2/unlink.2 @@ -163,7 +163,7 @@ An I/O error occurred. .B EISDIR .I pathname refers to a directory. -(This is the non-POSIX value returned by Linux since 2.1.132.) +(This is the non-POSIX value returned since Linux 2.1.132.) .TP .B ELOOP Too many symbolic links were encountered in translating @@ -254,8 +254,8 @@ is relative and is a file descriptor referring to a file other than a directory. .SH VERSIONS .BR unlinkat () -was added to Linux in kernel 2.6.16; -library support was added to glibc in version 2.4. +was added in Linux 2.6.16; +library support was added in glibc 2.4. .SH STANDARDS .BR unlink (): SVr4, 4.3BSD, POSIX.1-2001, POSIX.1-2008. diff --git a/man2/unshare.2 b/man2/unshare.2 index 7b09ecbcb1..8fdcd8761d 100644 --- a/man2/unshare.2 +++ b/man2/unshare.2 @@ -422,7 +422,7 @@ error above. .SH VERSIONS The .BR unshare () -system call was added to Linux in kernel 2.6.16. +system call was added in Linux 2.6.16. .SH STANDARDS The .BR unshare () diff --git a/man2/uselib.2 b/man2/uselib.2 index d7a6c2395b..3997e6d606 100644 --- a/man2/uselib.2 +++ b/man2/uselib.2 @@ -62,7 +62,7 @@ intended to be portable. .SH NOTES This obsolete system call is not supported by glibc. No declaration is provided in glibc headers, but, through a quirk of history, -glibc versions before 2.23 did export an ABI for this system call. +glibc before glibc 2.23 did export an ABI for this system call. Therefore, in order to employ this system call, it was sufficient to manually declare the interface in your code; alternatively, you could invoke the system call using diff --git a/man2/userfaultfd.2 b/man2/userfaultfd.2 index 64482b3700..3feb268093 100644 --- a/man2/userfaultfd.2 +++ b/man2/userfaultfd.2 @@ -77,7 +77,7 @@ and unread events are flushed. .PP Userfaultfd supports three modes of registration: .TP -.BR UFFDIO_REGISTER_MODE_MISSING " (since 4.10)" +.BR UFFDIO_REGISTER_MODE_MISSING " (since Linux 4.10)" When registered with .B UFFDIO_REGISTER_MODE_MISSING mode, user-space will receive a page-fault notification @@ -89,7 +89,7 @@ or an .B UFFDIO_ZEROPAGE ioctl. .TP -.BR UFFDIO_REGISTER_MODE_MINOR " (since 5.13)" +.BR UFFDIO_REGISTER_MODE_MINOR " (since Linux 5.13)" When registered with .B UFFDIO_REGISTER_MODE_MINOR mode, user-space will receive a page-fault notification @@ -102,7 +102,7 @@ until the page fault is resolved from user-space by an .B UFFDIO_CONTINUE ioctl. .TP -.BR UFFDIO_REGISTER_MODE_WP " (since 5.7)" +.BR UFFDIO_REGISTER_MODE_WP " (since Linux 5.7)" When registered with .B UFFDIO_REGISTER_MODE_WP mode, user-space will receive a page-fault notification @@ -176,8 +176,8 @@ single threaded non-cooperative userfaultfd manager implementations. .\" fault events in multi-threaded monitor. .\" .PP .\" FIXME elaborate about non-cooperating mode, describe its limitations -.\" for kernels before 4.11, features added in 4.11 -.\" and limitations remaining in 4.11 +.\" for kernels before Linux 4.11, features added in Linux 4.11 +.\" and limitations remaining in Linux 4.11 .\" Maybe it's worth adding a dedicated sub-section... .\" .PP @@ -269,7 +269,7 @@ userfaultfd can be used only with anonymous private memory mappings. Since Linux 4.11, userfaultfd can be also used with hugetlbfs and shared memory mappings. .\" -.SS Userfaultfd write-protect mode (since 5.7) +.SS Userfaultfd write-protect mode (since Linux 5.7) Since Linux 5.7, userfaultfd supports write-protect mode for anonymous memory. The user needs to first check availability of this feature using .B UFFDIO_API @@ -334,7 +334,7 @@ should have the flag .B UFFDIO_WRITEPROTECT_MODE_WP cleared upon the faulted page or range. .\" -.SS Userfaultfd minor fault mode (since 5.13) +.SS Userfaultfd minor fault mode (since Linux 5.13) Since Linux 5.13, userfaultfd supports minor fault mode. In this mode, diff --git a/man2/ustat.2 b/man2/ustat.2 index a7c991bbb6..f6044d7f99 100644 --- a/man2/ustat.2 +++ b/man2/ustat.2 @@ -70,10 +70,10 @@ does not refer to a device containing a mounted filesystem. .B ENOSYS The mounted filesystem referenced by .I dev -does not support this operation, or any version of Linux before -1.3.16. +does not support this operation, +or any version of Linux before Linux 1.3.16. .SH VERSIONS -Since version 2.28, glibc no longer provides a wrapper for this system call. +Since glibc 2.28, glibc no longer provides a wrapper for this system call. .SH STANDARDS SVr4. .\" SVr4 documents additional error conditions ENOLINK, ECOMM, and EINTR diff --git a/man2/utimensat.2 b/man2/utimensat.2 index 0a8774156d..404832e5c4 100644 --- a/man2/utimensat.2 +++ b/man2/utimensat.2 @@ -369,8 +369,8 @@ Search permission is denied for one of the prefix components of .IR pathname . .SH VERSIONS .BR utimensat () -was added to Linux in kernel 2.6.22; -glibc support was added with version 2.6. +was added in Linux 2.6.22; +glibc support was added with glibc 2.6. .PP Support for .BR futimens () @@ -459,7 +459,7 @@ Several bugs afflict .BR utimensat () and .BR futimens () -on kernels before 2.6.26. +before Linux 2.6.26. These bugs are either nonconformances with the POSIX.1 draft specification or inconsistencies with historical Linux behavior. .IP \(bu 3 diff --git a/man2/vfork.2 b/man2/vfork.2 index 1414ba80f3..b3c48d0b82 100644 --- a/man2/vfork.2 +++ b/man2/vfork.2 @@ -282,8 +282,8 @@ see .UE . In Linux, it has been equivalent to .BR fork (2) -until 2.2.0-pre6 or so. -Since 2.2.0-pre9 (on i386, somewhat later on +until Linux 2.2.0-pre6 or so. +Since Linux 2.2.0-pre9 (on i386, somewhat later on other architectures) it is an independent system call. Support was added in glibc 2.0.112. .SH BUGS @@ -300,7 +300,7 @@ signals; rather, output or .IR ioctl s are allowed and input attempts result in an end-of-file indication." .\" -.\" As far as I can tell, the following is not true in 2.6.19: +.\" As far as I can tell, the following is not true in Linux 2.6.19: .\" Currently (Linux 2.3.25), .\" .BR strace (1) .\" cannot follow diff --git a/man2/vmsplice.2 b/man2/vmsplice.2 index a12f6c8c93..01ac37b358 100644 --- a/man2/vmsplice.2 +++ b/man2/vmsplice.2 @@ -136,7 +136,7 @@ Out of memory. The .BR vmsplice () system call first appeared in Linux 2.6.17; -library support was added to glibc in version 2.5. +library support was added in glibc 2.5. .SH STANDARDS This system call is Linux-specific. .SH NOTES diff --git a/man2/wait4.2 b/man2/wait4.2 index 6f011fe0e2..44b507c4c9 100644 --- a/man2/wait4.2 +++ b/man2/wait4.2 @@ -38,7 +38,7 @@ Feature Test Macro Requirements for glibc (see || (_XOPEN_SOURCE >= 500 && ! (_POSIX_C_SOURCE >= 200112L || _XOPEN_SOURCE >= 600)) - From glibc 2.19 to 2.25: + From glibc 2.19 to glibc 2.25: _DEFAULT_SOURCE || _XOPEN_SOURCE >= 500 Glibc 2.19 and earlier: _BSD_SOURCE || _XOPEN_SOURCE >= 500 diff --git a/man2/write.2 b/man2/write.2 index 3135623a41..9f4a814b6a 100644 --- a/man2/write.2 +++ b/man2/write.2 @@ -297,7 +297,7 @@ and .BR writev (2). And among the effects that should be atomic across threads (and processes) are updates of the file offset. -However, on Linux before version 3.14, +However, before Linux 3.14, this was not the case: if two processes that share an open file description (see .BR open (2)) diff --git a/man3/__ppc_get_timebase.3 b/man3/__ppc_get_timebase.3 index 0c2f69e537..35ed99e358 100644 --- a/man3/__ppc_get_timebase.3 +++ b/man3/__ppc_get_timebase.3 @@ -40,10 +40,10 @@ which the Time Base Register is updated. GNU C Library support for .\" commit d9dc34cd569bcfe714fe8c708e58c028106e8b2e .BR __ppc_get_timebase () -has been provided since version 2.16 and +has been provided since glibc 2.16 and .\" commit 8ad11b9a9cf1de82bd7771306b42070b91417c11 .BR __ppc_get_timebase_freq () -has been available since version 2.17. +has been available since glibc 2.17. .SH STANDARDS Both functions are nonstandard GNU extensions. .SH EXAMPLES diff --git a/man3/__ppc_set_ppr_med.3 b/man3/__ppc_set_ppr_med.3 index 235eddc35b..37fbf139d7 100644 --- a/man3/__ppc_set_ppr_med.3 +++ b/man3/__ppc_set_ppr_med.3 @@ -67,12 +67,12 @@ The functions .BR __ppc_set_ppr_low (), and .BR __ppc_set_ppr_med_low () -are provided by glibc since version 2.18. +are provided since glibc 2.18. The functions .BR __ppc_set_ppr_very_low () and .BR __ppc_set_ppr_med_high () -first appeared in glibc in version 2.23. +first appeared in glibc 2.23. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/__ppc_yield.3 b/man3/__ppc_yield.3 index 06619cdc66..dc3748d39d 100644 --- a/man3/__ppc_yield.3 +++ b/man3/__ppc_yield.3 @@ -41,7 +41,7 @@ resources dedicated to the executing processor are released until all outstanding storage accesses to cacheable storage for which the data is not in the cache have been completed. .SH VERSIONS -These functions first appeared in glibc in version 2.18. +These functions first appeared in glibc 2.18. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/a64l.3 b/man3/a64l.3 index 477fe9a0e3..d0d268bb49 100644 --- a/man3/a64l.3 +++ b/man3/a64l.3 @@ -29,7 +29,7 @@ Feature Test Macro Requirements for glibc (see .nf _XOPEN_SOURCE >= 500 .\" || _XOPEN_SOURCE && _XOPEN_SOURCE_EXTENDED - || /* Glibc since 2.19: */ _DEFAULT_SOURCE + || /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _SVID_SOURCE .fi .SH DESCRIPTION @@ -98,7 +98,7 @@ If .I value is zero, it returns an empty string. .PP -These functions are broken in glibc before 2.2.5 +These functions are broken before glibc 2.2.5 (puts most significant digit first). .PP This is not the encoding used by diff --git a/man3/abs.3 b/man3/abs.3 index d2ceb88ab8..4b1e8879a0 100644 --- a/man3/abs.3 +++ b/man3/abs.3 @@ -95,11 +95,10 @@ is not defined. .PP The .BR llabs () -function is included in glibc since version 2.0. +function is included since glibc 2.0. The .BR imaxabs () -function is included in -glibc since version 2.1.1. +function is included since glibc 2.1.1. .PP For .BR llabs () diff --git a/man3/addseverity.3 b/man3/addseverity.3 index 0c33078a07..911ef767be 100644 --- a/man3/addseverity.3 +++ b/man3/addseverity.3 @@ -62,7 +62,7 @@ Possible errors include: out of memory, attempt to remove a nonexistent or default severity class. .SH VERSIONS .BR addseverity () -is provided in glibc since version 2.1. +is provided since glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/atanh.3 b/man3/atanh.3 index 9087190fe6..92f9df2846 100644 --- a/man3/atanh.3 +++ b/man3/atanh.3 @@ -144,7 +144,7 @@ is set to .B EDOM instead of the POSIX-mandated .BR ERANGE . -Since version 2.10, glibc does the right thing. +Since glibc 2.10, glibc does the right thing. .SH SEE ALSO .BR acosh (3), .BR asinh (3), diff --git a/man3/atoi.3 b/man3/atoi.3 index d59c4f4893..a74881247b 100644 --- a/man3/atoi.3 +++ b/man3/atoi.3 @@ -99,7 +99,7 @@ only. .\" is not provided by glibc. .\" The .\" .BR atoll () -.\" function is present in glibc 2 since version 2.0.2, but +.\" function is present since glibc 2.0.2, but .\" not in libc4 or libc5. .SH NOTES POSIX.1 leaves the return value of diff --git a/man3/backtrace.3 b/man3/backtrace.3 index 43c3612ad1..435f8f4c0a 100644 --- a/man3/backtrace.3 +++ b/man3/backtrace.3 @@ -134,7 +134,7 @@ on error, NULL is returned. .BR backtrace_symbols (), and .BR backtrace_symbols_fd () -are provided in glibc since version 2.1. +are provided since glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/btree.3 b/man3/btree.3 index 880aa28c85..5b0618ec8a 100644 --- a/man3/btree.3 +++ b/man3/btree.3 @@ -21,8 +21,8 @@ Standard C library .fi .SH DESCRIPTION .IR "Note well" : -This page documents interfaces provided in glibc up until version 2.1. -Since version 2.2, glibc no longer provides these interfaces. +This page documents interfaces provided up until glibc 2.1. +Since glibc 2.2, glibc no longer provides these interfaces. Probably, you are looking for the APIs provided by the .I libdb library instead. diff --git a/man3/cabs.3 b/man3/cabs.3 index bc36e7456b..fb0ebbaa87 100644 --- a/man3/cabs.3 +++ b/man3/cabs.3 @@ -21,7 +21,7 @@ These functions return the absolute value of the complex number .IR z . The result is a real number. .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/cacos.3 b/man3/cacos.3 index 027bb4d9ae..b30fe55e9c 100644 --- a/man3/cacos.3 +++ b/man3/cacos.3 @@ -31,7 +31,7 @@ One has: cacos(z) = \-i * clog(z + i * csqrt(1 \- z * z)) .fi .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/cacosh.3 b/man3/cacosh.3 index f6bd7e1472..3f20b1edc3 100644 --- a/man3/cacosh.3 +++ b/man3/cacosh.3 @@ -34,7 +34,7 @@ One has: cacosh(z) = 2 * clog(csqrt((z + 1) / 2) + csqrt((z \- 1) / 2)) .fi .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/carg.3 b/man3/carg.3 index c6e9cdff26..1dc0dde620 100644 --- a/man3/carg.3 +++ b/man3/carg.3 @@ -62,7 +62,7 @@ tan(carg(z)) = cimag(z) / creal(z) .SH RETURN VALUE The return value is in the range of [\-pi,pi]. .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/casin.3 b/man3/casin.3 index 548765d294..1024d2a5d2 100644 --- a/man3/casin.3 +++ b/man3/casin.3 @@ -30,7 +30,7 @@ One has: casin(z) = \-i clog(iz + csqrt(1 \- z * z)) .fi .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/casinh.3 b/man3/casinh.3 index 53ea3f7f88..4ea93659f8 100644 --- a/man3/casinh.3 +++ b/man3/casinh.3 @@ -32,7 +32,7 @@ casinh(z) = clog(z + csqrt(z * z + 1)) .EE .in .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/catan.3 b/man3/catan.3 index 54a9892d37..96f4ddc6d6 100644 --- a/man3/catan.3 +++ b/man3/catan.3 @@ -31,7 +31,7 @@ catan(z) = (clog(1 + i * z) \- clog(1 \- i * z)) / (2 * i) .EE .in .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/catanh.3 b/man3/catanh.3 index 933bf96e8d..e721e011c8 100644 --- a/man3/catanh.3 +++ b/man3/catanh.3 @@ -33,7 +33,7 @@ catanh(z) = 0.5 * (clog(1 + z) \- clog(1 \- z)) .EE .in .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/ccos.3 b/man3/ccos.3 index 746ae431cd..2177dcef43 100644 --- a/man3/ccos.3 +++ b/man3/ccos.3 @@ -28,7 +28,7 @@ ccos(z) = (exp(i * z) + exp(\-i * z)) / 2 .EE .in .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/ccosh.3 b/man3/ccosh.3 index 510a46d5e5..983b228692 100644 --- a/man3/ccosh.3 +++ b/man3/ccosh.3 @@ -28,7 +28,7 @@ ccosh(z) = (exp(z)+exp(\-z))/2 .EE .in .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH STANDARDS C99, POSIX.1-2001, POSIX.1-2008. .SH SEE ALSO diff --git a/man3/cexp.3 b/man3/cexp.3 index 8d89e1c56b..f39c65093d 100644 --- a/man3/cexp.3 +++ b/man3/cexp.3 @@ -29,7 +29,7 @@ cexp(I * z) = ccos(z) + I * csin(z) .EE .in .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/cexp2.3 b/man3/cexp2.3 index 0310845e93..c1c393dbd8 100644 --- a/man3/cexp2.3 +++ b/man3/cexp2.3 @@ -22,7 +22,7 @@ The function returns 2 raised to the power of .SH STANDARDS These function names are reserved for future use in C99. .PP -As at version 2.31, these functions are not provided in glibc. +As at glibc 2.31, these functions are not provided in glibc. .\" But reserved in NAMESPACE. .SH SEE ALSO .BR cabs (3), diff --git a/man3/cfree.3 b/man3/cfree.3 index 1b993b1752..b073b2bc17 100644 --- a/man3/cfree.3 +++ b/man3/cfree.3 @@ -45,7 +45,7 @@ This function should never be used. Use .BR free (3) instead. -Starting with version 2.26, it has been removed from glibc. +Starting with glibc 2.26, it has been removed from glibc. .SS 1-arg cfree In glibc, the function .BR cfree () @@ -108,7 +108,7 @@ The .BR cfree () function was removed .\" commit 025b33ae84bb8f15b2748a1d8605dca453fce112 -from glibc in version 2.26. +in glibc 2.26. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/cimag.3 b/man3/cimag.3 index 70f1db3955..58be1be2b4 100644 --- a/man3/cimag.3 +++ b/man3/cimag.3 @@ -28,7 +28,7 @@ z = creal(z) + I * cimag(z) .EE .in .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/clearenv.3 b/man3/clearenv.3 index 79ec2ead42..290b1831a0 100644 --- a/man3/clearenv.3 +++ b/man3/clearenv.3 @@ -23,7 +23,7 @@ Feature Test Macro Requirements for glibc (see .PP .BR clearenv (): .nf - /* Glibc since 2.19: */ _DEFAULT_SOURCE + /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _SVID_SOURCE || _BSD_SOURCE .fi .SH DESCRIPTION diff --git a/man3/clock_getcpuclockid.3 b/man3/clock_getcpuclockid.3 index 2813a912e9..e17e00a742 100644 --- a/man3/clock_getcpuclockid.3 +++ b/man3/clock_getcpuclockid.3 @@ -69,7 +69,7 @@ There is no process with the ID .SH VERSIONS The .BR clock_getcpuclockid () -function is available in glibc since version 2.2. +function is available since glibc 2.2. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/clog.3 b/man3/clog.3 index 1867bf8d8f..ded2513afc 100644 --- a/man3/clog.3 +++ b/man3/clog.3 @@ -42,7 +42,7 @@ Note that .I z close to zero will cause an overflow. .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/clog10.3 b/man3/clog10.3 index 5afe3d3e62..0e407a02ac 100644 --- a/man3/clog10.3 +++ b/man3/clog10.3 @@ -45,7 +45,7 @@ Note that .I z close to zero will cause an overflow. .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions first appeared in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/clog2.3 b/man3/clog2.3 index e0c7bd94fd..f147cb0292 100644 --- a/man3/clog2.3 +++ b/man3/clog2.3 @@ -33,7 +33,7 @@ close to zero will cause an overflow. .SH STANDARDS These function names are reserved for future use in C99. .PP -Not yet in glibc, as at version 2.19. +Not yet in glibc, as at glibc 2.19. .\" But reserved in NAMESPACE. .SH SEE ALSO .BR cabs (3), diff --git a/man3/conj.3 b/man3/conj.3 index 82a35f90cd..26742e5d42 100644 --- a/man3/conj.3 +++ b/man3/conj.3 @@ -29,7 +29,7 @@ cabs(z) = csqrt(z * conj(z)) .EE .in .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/cos.3 b/man3/cos.3 index 0258b368fd..9340ad6c7b 100644 --- a/man3/cos.3 +++ b/man3/cos.3 @@ -101,7 +101,7 @@ The variant returning also conforms to SVr4, 4.3BSD. .SH BUGS -Before version 2.10, the glibc implementation did not set +Before glibc 2.10, the glibc implementation did not set .\" http://sources.redhat.com/bugzilla/show_bug.cgi?id=6780 .I errno to diff --git a/man3/cosh.3 b/man3/cosh.3 index cc8d5210d9..8e529e3052 100644 --- a/man3/cosh.3 +++ b/man3/cosh.3 @@ -117,7 +117,7 @@ The variant returning also conforms to SVr4, 4.3BSD. .SH BUGS -In glibc version 2.3.4 and earlier, +In glibc 2.3.4 and earlier, an overflow floating-point .RB ( FE_OVERFLOW ) exception is not raised when an overflow occurs. diff --git a/man3/cpow.3 b/man3/cpow.3 index b6824b8ff2..be8edcbf4c 100644 --- a/man3/cpow.3 +++ b/man3/cpow.3 @@ -26,7 +26,7 @@ raised to the power .I x along the negative real axis.) .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/cproj.3 b/man3/cproj.3 index d839fe8615..c67284a6b4 100644 --- a/man3/cproj.3 +++ b/man3/cproj.3 @@ -27,7 +27,7 @@ itself. Every complex infinite value is projected to a single infinite value, namely to positive infinity on the real axis. .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/creal.3 b/man3/creal.3 index 3024580749..3c74fddb65 100644 --- a/man3/creal.3 +++ b/man3/creal.3 @@ -26,7 +26,7 @@ One has: z = creal(z) + I * cimag(z) .fi .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/csin.3 b/man3/csin.3 index 08dd9889f6..9e854395da 100644 --- a/man3/csin.3 +++ b/man3/csin.3 @@ -28,7 +28,7 @@ csin(z) = (exp(i * z) \- exp(\-i * z)) / (2 * i) .EE .in .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/csinh.3 b/man3/csinh.3 index 531921dd1c..b2437607e4 100644 --- a/man3/csinh.3 +++ b/man3/csinh.3 @@ -28,7 +28,7 @@ csinh(z) = (exp(z)\-exp(\-z))/2 .EE .in .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/csqrt.3 b/man3/csqrt.3 index debb868795..5bed49c41a 100644 --- a/man3/csqrt.3 +++ b/man3/csqrt.3 @@ -24,7 +24,7 @@ with a branch cut along the negative real axis. \fIcsqrt(\-1\-eps*I)\fP will be close to \-I, \fIif eps\fP is a small positive real number.) .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/ctan.3 b/man3/ctan.3 index fed2c56308..f6a10529f8 100644 --- a/man3/ctan.3 +++ b/man3/ctan.3 @@ -28,7 +28,7 @@ ctan(z) = csin(z) / ccos(z) .EE .in .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/ctanh.3 b/man3/ctanh.3 index 222eb18d1f..76b4f27c00 100644 --- a/man3/ctanh.3 +++ b/man3/ctanh.3 @@ -29,7 +29,7 @@ ctanh(z) = csinh(z) / ccosh(z) .EE .in .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/ctermid.3 b/man3/ctermid.3 index f94adb5a1e..2608b0375f 100644 --- a/man3/ctermid.3 +++ b/man3/ctermid.3 @@ -68,6 +68,6 @@ terminal; it may, for example, be .PP It is not assured that the program can open the terminal. .\" in glibc 2.3.x, x >= 4, the glibc headers threw an error -.\" if ctermid() was given an argument; fixed in 2.4. +.\" if ctermid() was given an argument; fixed in glibc 2.4. .SH SEE ALSO .BR ttyname (3) diff --git a/man3/dbopen.3 b/man3/dbopen.3 index 6e71f1f321..294b5fa6e3 100644 --- a/man3/dbopen.3 +++ b/man3/dbopen.3 @@ -25,8 +25,8 @@ Standard C library .fi .SH DESCRIPTION .IR "Note well" : -This page documents interfaces provided in glibc up until version 2.1. -Since version 2.2, glibc no longer provides these interfaces. +This page documents interfaces provided up until glibc 2.1. +Since glibc 2.2, glibc no longer provides these interfaces. Probably, you are looking for the APIs provided by the .I libdb library instead. diff --git a/man3/des_crypt.3 b/man3/des_crypt.3 index 8806cc9fd5..943cc7f783 100644 --- a/man3/des_crypt.3 +++ b/man3/des_crypt.3 @@ -129,7 +129,7 @@ is false only for the first two statuses. .\" So far the Sun page .\" Some additions - aeb .SH VERSIONS -These functions were added to glibc in version 2.1. +These functions were added in glibc 2.1. .PP Because they employ the DES block cipher, which is no longer considered secure, diff --git a/man3/dirfd.3 b/man3/dirfd.3 index 2bb00c10a5..1ddf89c1ad 100644 --- a/man3/dirfd.3 +++ b/man3/dirfd.3 @@ -81,7 +81,7 @@ T} Thread safety MT-Safe .SH STANDARDS POSIX.1-2008. This function was a BSD extension, present in 4.3BSD-Reno, not in 4.2BSD. -.\" It is present in libc5 (since 5.1.2) and in glibc2. +.\" It is present in libc5 (since 5.1.2) and in glibc 2. .SH SEE ALSO .BR open (2), .BR openat (2), diff --git a/man3/dl_iterate_phdr.3 b/man3/dl_iterate_phdr.3 index 69ee8376e5..de78300e50 100644 --- a/man3/dl_iterate_phdr.3 +++ b/man3/dl_iterate_phdr.3 @@ -183,7 +183,7 @@ function returns whatever value was returned by the last call to .IR callback . .SH VERSIONS .BR dl_iterate_phdr () -has been supported in glibc since version 2.2.4. +has been supported since glibc 2.2.4. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/drand48.3 b/man3/drand48.3 index 555acfda6f..280b0234af 100644 --- a/man3/drand48.3 +++ b/man3/drand48.3 @@ -49,7 +49,7 @@ All functions shown above: .\" .BR lcong48 (): .nf _XOPEN_SOURCE - || /* Glibc since 2.19: */ _DEFAULT_SOURCE + || /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _SVID_SOURCE .fi .SH DESCRIPTION diff --git a/man3/drand48_r.3 b/man3/drand48_r.3 index 1910cde79b..8ce24538b2 100644 --- a/man3/drand48_r.3 +++ b/man3/drand48_r.3 @@ -55,7 +55,7 @@ All functions shown above: .\" .BR seed48_r (), .\" .BR lcong48_r (): .nf - /* Glibc since 2.19: */ _DEFAULT_SOURCE + /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _SVID_SOURCE || _BSD_SOURCE .fi .SH DESCRIPTION diff --git a/man3/duplocale.3 b/man3/duplocale.3 index a92c067db6..99e5cde96b 100644 --- a/man3/duplocale.3 +++ b/man3/duplocale.3 @@ -57,7 +57,7 @@ Insufficient memory to create the duplicate locale object. .SH VERSIONS The .BR duplocale () -function first appeared in version 2.3 of the GNU C library. +function were added in glibc 2.3. .SH STANDARDS POSIX.1-2008. .SH NOTES diff --git a/man3/ecvt.3 b/man3/ecvt.3 index c01a6b4581..203d7e9040 100644 --- a/man3/ecvt.3 +++ b/man3/ecvt.3 @@ -37,7 +37,7 @@ Feature Test Macro Requirements for glibc (see (_XOPEN_SOURCE >= 500 && ! (_POSIX_C_SOURCE >= 200809L)) || /* Glibc >= 2.20 */ _DEFAULT_SOURCE || /* Glibc <= 2.19 */ _SVID_SOURCE - Glibc versions 2.12 to 2.16: + Glibc 2.12 to glibc 2.16: (_XOPEN_SOURCE >= 500 && ! (_POSIX_C_SOURCE >= 200112L)) || _SVID_SOURCE Before glibc 2.12: diff --git a/man3/ecvt_r.3 b/man3/ecvt_r.3 index c9e8dd6773..c544d85061 100644 --- a/man3/ecvt_r.3 +++ b/man3/ecvt_r.3 @@ -42,7 +42,7 @@ Feature Test Macro Requirements for glibc (see .BR qecvt_r (), .BR qfcvt_r (): .nf - /* Glibc since 2.19: */ _DEFAULT_SOURCE + /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _SVID_SOURCE || _BSD_SOURCE .fi .SH DESCRIPTION diff --git a/man3/endian.3 b/man3/endian.3 index 748c17c7d6..4365841233 100644 --- a/man3/endian.3 +++ b/man3/endian.3 @@ -80,7 +80,7 @@ from big-endian order to host byte order. The functions with names of the form "le\fInn\fPtoh" convert from little-endian order to host byte order. .SH VERSIONS -These functions were added to glibc in version 2.9. +These functions were added in glibc 2.9. .SH STANDARDS These functions are nonstandard. Similar functions are present on the BSDs, diff --git a/man3/euidaccess.3 b/man3/euidaccess.3 index 2a2c298fce..0997861001 100644 --- a/man3/euidaccess.3 +++ b/man3/euidaccess.3 @@ -52,7 +52,7 @@ As for .SH VERSIONS The .BR eaccess () -function was added to glibc in version 2.4. +function was added in glibc 2.4. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/exp10.3 b/man3/exp10.3 index ff826ddf1e..8aaa415858 100644 --- a/man3/exp10.3 +++ b/man3/exp10.3 @@ -47,7 +47,7 @@ when calling these functions. For a discussion of the errors that can occur for these functions, see .BR exp (3). .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions first appeared in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). @@ -70,7 +70,7 @@ T} Thread safety MT-Safe .SH STANDARDS These functions are GNU extensions. .SH BUGS -Prior to version 2.19, the glibc implementation of these functions did not set +Before glibc 2.19, the glibc implementation of these functions did not set .I errno to .B ERANGE diff --git a/man3/exp2.3 b/man3/exp2.3 index 8220feada7..08ff3a8d19 100644 --- a/man3/exp2.3 +++ b/man3/exp2.3 @@ -58,7 +58,7 @@ when calling these functions. For a discussion of the errors that can occur for these functions, see .BR exp (3). .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/expm1.3 b/man3/expm1.3 index 333b5ab780..c99644c92d 100644 --- a/man3/expm1.3 +++ b/man3/expm1.3 @@ -137,7 +137,7 @@ for some large negative .I x values (where the function result approaches \-1). .PP -Before approximately glibc version 2.11, +Before approximately glibc 2.11, .\" http://sources.redhat.com/bugzilla/show_bug.cgi?id=6814 .\" e.g., expm1(1e5) through expm1(1.00199970127e5), .\" but not expm1(1.00199970128e5) and beyond. @@ -148,11 +148,11 @@ for some large positive .I x values. .PP -Before version 2.11, -.\" It looks like the fix was in 2.11, or possibly 2.12. -.\" I have no test system for 2.11, but 2.12 passes. +Before glibc 2.11, +.\" It looks like the fix was in glibc 2.11, or possibly glibc 2.12. +.\" I have no test system for glibc 2.11, but glibc 2.12 passes. .\" From the source (sysdeps/i386/fpu/s_expm1.S) it looks -.\" like the changes were in 2.11. +.\" like the changes were in glibc 2.11. the glibc implementation did not set .\" http://sources.redhat.com/bugzilla/show_bug.cgi?id=6788 .I errno diff --git a/man3/fdim.3 b/man3/fdim.3 index d75b7ac42f..11faa2236e 100644 --- a/man3/fdim.3 +++ b/man3/fdim.3 @@ -65,7 +65,7 @@ An overflow floating-point exception .RB ( FE_OVERFLOW ) is raised. .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). @@ -88,7 +88,7 @@ T} Thread safety MT-Safe .SH STANDARDS C99, POSIX.1-2001, POSIX.1-2008. .SH BUGS -Before glibc version 2.24 +Before glibc 2.24 .\" https://www.sourceware.org/bugzilla/show_bug.cgi?id=6796 on certain architectures (e.g., x86, but not x86_64) these functions did not set diff --git a/man3/fenv.3 b/man3/fenv.3 index c364f87a05..337ff996ac 100644 --- a/man3/fenv.3 +++ b/man3/fenv.3 @@ -240,7 +240,7 @@ These functions return zero on success and nonzero if an error occurred. .\" This was corrected in Corrigendum 1 (ISO/IEC 9899:1999/Cor.1:2001(E)) .\" of the C99 Standard. .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). @@ -290,7 +290,7 @@ It is defined only if is defined. The C99 standard does not define a way to set individual bits in the floating-point mask, for example, to trap on specific flags. -Since version 2.2, glibc supports the functions +Since glibc 2.2, glibc supports the functions .BR feenableexcept () and .BR fedisableexcept () diff --git a/man3/ffs.3 b/man3/ffs.3 index f596561007..3c9a800d79 100644 --- a/man3/ffs.3 +++ b/man3/ffs.3 @@ -38,7 +38,7 @@ Feature Test Macro Requirements for glibc (see Since glibc 2.12: _XOPEN_SOURCE >= 700 || ! (_POSIX_C_SOURCE >= 200809L) - || /* Glibc since 2.19: */ _DEFAULT_SOURCE + || /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _BSD_SOURCE || _SVID_SOURCE Before glibc 2.12: none diff --git a/man3/finite.3 b/man3/finite.3 index 3a67b6b82e..a4eb822b04 100644 --- a/man3/finite.3 +++ b/man3/finite.3 @@ -35,26 +35,26 @@ Feature Test Macro Requirements for glibc (see .BR finitef (), .BR finitel (): .nf - /* Glibc since 2.19: */ _DEFAULT_SOURCE + /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _BSD_SOURCE || _SVID_SOURCE .PP .BR isinf (): _XOPEN_SOURCE >= 600 || _ISOC99_SOURCE - || /* Glibc since 2.19: */ _DEFAULT_SOURCE + || /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _BSD_SOURCE || _SVID_SOURCE .fi .PP .BR isinff (), .BR isinfl (): .nf - /* Glibc since 2.19: */ _DEFAULT_SOURCE + /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _BSD_SOURCE || _SVID_SOURCE .fi .PP .BR isnan (): .nf _XOPEN_SOURCE || _ISOC99_SOURCE - || /* Glibc since 2.19: */ _DEFAULT_SOURCE + || /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _BSD_SOURCE || _SVID_SOURCE .fi .PP @@ -62,7 +62,7 @@ Feature Test Macro Requirements for glibc (see .BR isnanl (): .nf _XOPEN_SOURCE >= 600 - || /* Glibc since 2.19: */ _DEFAULT_SOURCE + || /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _BSD_SOURCE || _SVID_SOURCE .fi .SH DESCRIPTION diff --git a/man3/fma.3 b/man3/fma.3 index 831886c06e..92c75acc86 100644 --- a/man3/fma.3 +++ b/man3/fma.3 @@ -141,7 +141,7 @@ These functions do not set .\" FIXME . Is it intentional that these functions do not set errno? .\" Bug raised: http://sources.redhat.com/bugzilla/show_bug.cgi?id=6801 .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/fmax.3 b/man3/fmax.3 index d9443ccc78..7f4a68db75 100644 --- a/man3/fmax.3 +++ b/man3/fmax.3 @@ -47,7 +47,7 @@ If both arguments are NaN, a NaN is returned. .SH ERRORS No errors occur. .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/fmemopen.3 b/man3/fmemopen.3 index 89f1dcf5e7..c5d2416856 100644 --- a/man3/fmemopen.3 +++ b/man3/fmemopen.3 @@ -185,13 +185,13 @@ returned by this function .BR fileno (3) will return an error if called on the returned stream). .PP -With version 2.22, binary mode (see below) was removed, +With glibc 2.22, binary mode (see below) was removed, many longstanding bugs in the implementation of .BR fmemopen () were fixed, and a new versioned symbol was created for this interface. .\" .SS Binary mode -From version 2.9 to 2.21, the glibc implementation of +From glibc 2.9 to glibc 2.21, the glibc implementation of .BR fmemopen () supported a "binary" mode, enabled by specifying the letter \(aqb\(aq as the second character in @@ -220,7 +220,7 @@ Binary mode was removed in glibc 2.22; a \(aqb\(aq specified in .I mode has no effect. .SH BUGS -In versions of glibc before 2.22, if +Before glibc 2.22, if .I size is specified as zero, .BR fmemopen () @@ -229,9 +229,9 @@ fails with the error .\" http://sourceware.org/bugzilla/show_bug.cgi?id=11216 It would be more consistent if this case successfully created a stream that then returned end-of-file on the first attempt at reading; -since version 2.22, the glibc implementation provides that behavior. +since glibc 2.22, the glibc implementation provides that behavior. .PP -In versions of glibc before 2.22, +Before glibc 2.22, specifying append mode ("a" or "a+") for .BR fmemopen () sets the initial buffer position to the first null byte, but @@ -241,7 +241,7 @@ the end of the stream) does not force subsequent writes to append at the end of the stream. This bug is fixed in glibc 2.22. .PP -In versions of glibc before 2.22, if the +Before glibc 2.22, if the .I mode argument to .BR fmemopen () @@ -258,7 +258,7 @@ However, in this case the glibc sets the buffer position to \-1. This bug is fixed in glibc 2.22. .PP -In versions of glibc before 2.22, +Before glibc 2.22, .\" https://sourceware.org/bugzilla/show_bug.cgi?id=14292 when a call to .BR fseek (3) diff --git a/man3/fmin.3 b/man3/fmin.3 index 76e493e3b7..8f83567f8a 100644 --- a/man3/fmin.3 +++ b/man3/fmin.3 @@ -47,7 +47,7 @@ If both arguments are NaN, a NaN is returned. .SH ERRORS No errors occur. .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/fmod.3 b/man3/fmod.3 index 1b340c61ac..4444fa5e9c 100644 --- a/man3/fmod.3 +++ b/man3/fmod.3 @@ -143,7 +143,7 @@ The variant returning also conforms to SVr4, 4.3BSD, C89. .SH BUGS -Before version 2.10, the glibc implementation did not set +Before glibc 2.10, the glibc implementation did not set .\" http://sources.redhat.com/bugzilla/show_bug.cgi?id=6784 .I errno to diff --git a/man3/fmtmsg.3 b/man3/fmtmsg.3 index 848a08a061..8e65183242 100644 --- a/man3/fmtmsg.3 +++ b/man3/fmtmsg.3 @@ -219,7 +219,7 @@ is the string printed when a message of this class is processed by .BR fmtmsg (). .SH VERSIONS .BR fmtmsg () -is provided in glibc since version 2.1. +is provided since glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/fopen.3 b/man3/fopen.3 index df1f05358e..1bd5726a6a 100644 --- a/man3/fopen.3 +++ b/man3/fopen.3 @@ -381,7 +381,7 @@ and .BR freopen () limits the number of characters examined in .I mode -to 7 (or, in glibc versions before 2.14, to 6, +to 7 (or, before glibc 2.14, to 6, which was not enough to include possible specifications such as "rb+cmxe"). The current implementation of .BR fdopen () diff --git a/man3/fseeko.3 b/man3/fseeko.3 index 7b4c1cce88..a56496e827 100644 --- a/man3/fseeko.3 +++ b/man3/fseeko.3 @@ -73,7 +73,7 @@ is set to indicate the error. See the ERRORS in .BR fseek (3). .SH VERSIONS -These functions are available under glibc since version 2.1. +These functions are available since glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/fts.3 b/man3/fts.3 index 0e78c81b65..ab3bd06593 100644 --- a/man3/fts.3 +++ b/man3/fts.3 @@ -786,7 +786,7 @@ T} Thread safety MT-Unsafe .SH STANDARDS 4.4BSD. .SH BUGS -In versions of glibc before 2.23, +Before glibc 2.23, .\" Fixed by commit 8b7b7f75d91f7bac323dd6a370aeb3e9c5c4a7d5 .\" https://sourceware.org/bugzilla/show_bug.cgi?id=15838 .\" https://sourceware.org/bugzilla/show_bug.cgi?id=11460 diff --git a/man3/ftw.3 b/man3/ftw.3 index a9eb9d0948..19a5b1ebf9 100644 --- a/man3/ftw.3 +++ b/man3/ftw.3 @@ -351,7 +351,7 @@ and that value is returned as the result of .BR nftw (). .SH VERSIONS .BR nftw () -is available under glibc since version 2.1. +is available since glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/futimes.3 b/man3/futimes.3 index 5aa5deb981..4050b6347d 100644 --- a/man3/futimes.3 +++ b/man3/futimes.3 @@ -76,7 +76,7 @@ is available since glibc 2.3. .BR lutimes () is available since glibc 2.6, and is implemented using the .BR utimensat (2) -system call, which is supported since kernel 2.6.22. +system call, which is supported since Linux 2.6.22. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/gcvt.3 b/man3/gcvt.3 index 2b6e4d64ae..abd2649858 100644 --- a/man3/gcvt.3 +++ b/man3/gcvt.3 @@ -31,7 +31,7 @@ Feature Test Macro Requirements for glibc (see (_XOPEN_SOURCE >= 500 && ! (_POSIX_C_SOURCE >= 200809L)) || /* Glibc >= 2.20 */ _DEFAULT_SOURCE || /* Glibc <= 2.19 */ _SVID_SOURCE - Glibc versions 2.12 to 2.16: + Glibc 2.12 to glibc 2.16: (_XOPEN_SOURCE >= 500 && ! (_POSIX_C_SOURCE >= 200112L)) || _SVID_SOURCE Before glibc 2.12: diff --git a/man3/getaddrinfo.3 b/man3/getaddrinfo.3 index 1c0d81c6cc..649a1b2716 100644 --- a/man3/getaddrinfo.3 +++ b/man3/getaddrinfo.3 @@ -321,7 +321,7 @@ field of the first of the .I addrinfo structures in the returned list is set to point to the official name of the host. -.\" In glibc prior to 2.3.4, the ai_canonname of each addrinfo +.\" Prior to glibc 2.3.4, the ai_canonname of each addrinfo .\" structure was set pointing to the canonical name; that was .\" more than POSIX.1-2001 specified, or other implementations provided. .\" MTK, Aug 05 diff --git a/man3/getaddrinfo_a.3 b/man3/getaddrinfo_a.3 index 9c1e677860..f1469d81ba 100644 --- a/man3/getaddrinfo_a.3 +++ b/man3/getaddrinfo_a.3 @@ -304,7 +304,7 @@ T} Thread safety MT-Safe .sp 1 .SH STANDARDS These functions are GNU extensions; -they first appeared in glibc in version 2.2.3. +they first appeared in glibc 2.2.3. .SH NOTES The interface of .BR getaddrinfo_a () diff --git a/man3/getauxval.3 b/man3/getauxval.3 index 0a92f2257e..a7b342d6c7 100644 --- a/man3/getauxval.3 +++ b/man3/getauxval.3 @@ -212,7 +212,7 @@ could be found in the auxiliary vector. .SH VERSIONS The .BR getauxval () -function was added to glibc in version 2.16. +function was added in glibc 2.16. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/getcwd.3 b/man3/getcwd.3 index 23b622ead0..c6b368e005 100644 --- a/man3/getcwd.3 +++ b/man3/getcwd.3 @@ -39,7 +39,7 @@ Feature Test Macro Requirements for glibc (see .nf Since glibc 2.12: (_XOPEN_SOURCE >= 500) && ! (_POSIX_C_SOURCE >= 200809L) - || /* Glibc since 2.19: */ _DEFAULT_SOURCE + || /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _BSD_SOURCE Before glibc 2.12: _BSD_SOURCE || _XOPEN_SOURCE >= 500 diff --git a/man3/getdtablesize.3 b/man3/getdtablesize.3 index 58be49be55..099f2fd692 100644 --- a/man3/getdtablesize.3 +++ b/man3/getdtablesize.3 @@ -26,7 +26,7 @@ Feature Test Macro Requirements for glibc (see .nf Since glibc 2.20: _DEFAULT_SOURCE || ! (_POSIX_C_SOURCE >= 200112L) - Glibc 2.12 to 2.19: + Glibc 2.12 to glibc 2.19: _BSD_SOURCE || ! (_POSIX_C_SOURCE >= 200112L) Before glibc 2.12: _BSD_SOURCE || _XOPEN_SOURCE >= 500 diff --git a/man3/getgrent.3 b/man3/getgrent.3 index bb7e409e3f..7e6a9e6c44 100644 --- a/man3/getgrent.3 +++ b/man3/getgrent.3 @@ -33,7 +33,7 @@ Feature Test Macro Requirements for glibc (see .nf _XOPEN_SOURCE >= 500 .\" || _XOPEN_SOURCE && _XOPEN_SOURCE_EXTENDED - || /* Glibc since 2.19: */ _DEFAULT_SOURCE + || /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _BSD_SOURCE || _SVID_SOURCE .fi .PP diff --git a/man3/getgrnam.3 b/man3/getgrnam.3 index 0f27c63100..be1e152477 100644 --- a/man3/getgrnam.3 +++ b/man3/getgrnam.3 @@ -238,8 +238,8 @@ situation: 0, ENOENT, EBADF, ESRCH, EWOULDBLOCK, EPERM, and probably others. .\" more precisely: .\" AIX 5.1 - gives ESRCH .\" OSF1 4.0g - gives EWOULDBLOCK -.\" libc, glibc up to version 2.6, Irix 6.5 - give ENOENT -.\" glibc since version 2.7 - give 0 +.\" libc, glibc up to glibc 2.6, Irix 6.5 - give ENOENT +.\" since glibc 2.7 - give 0 .\" FreeBSD 4.8, OpenBSD 3.2, NetBSD 1.6 - give EPERM .\" SunOS 5.8 - gives EBADF .\" Tru64 5.1b, HP-UX-11i, SunOS 5.7 - give 0 diff --git a/man3/getgrouplist.3 b/man3/getgrouplist.3 index 5f3b1f8d30..865513a7e2 100644 --- a/man3/getgrouplist.3 +++ b/man3/getgrouplist.3 @@ -104,7 +104,7 @@ T} Thread safety MT-Safe locale .SH STANDARDS This function is nonstandard; it appears on most BSDs. .SH BUGS -In glibc versions before 2.3.3, +Before glibc 2.3.3, the implementation of this function contains a buffer-overrun bug: it returns the complete list of groups for .I user diff --git a/man3/gethostbyname.3 b/man3/gethostbyname.3 index 6f7d5b2352..1114e85dd8 100644 --- a/man3/gethostbyname.3 +++ b/man3/gethostbyname.3 @@ -97,7 +97,7 @@ Feature Test Macro Requirements for glibc (see .nf Since glibc 2.19: _DEFAULT_SOURCE - Glibc 2.8 to 2.19: + Glibc 2.8 to glibc 2.19: _BSD_SOURCE || _SVID_SOURCE Before glibc 2.8: none @@ -107,7 +107,7 @@ Feature Test Macro Requirements for glibc (see .nf Since glibc 2.19 _DEFAULT_SOURCE || _POSIX_C_SOURCE < 200809L - Glibc 2.12 to 2.19: + Glibc 2.12 to glibc 2.19: _BSD_SOURCE || _SVID_SOURCE || _POSIX_C_SOURCE < 200809L Before glibc 2.12: none diff --git a/man3/gethostid.3 b/man3/gethostid.3 index a438ea580d..697a59719a 100644 --- a/man3/gethostid.3 +++ b/man3/gethostid.3 @@ -121,7 +121,7 @@ In the glibc implementation, the .I hostid is stored in the file .IR /etc/hostid . -(In glibc versions before 2.2, the file +(Before glibc 2.2, the file .I /var/adm/hostid was used.) .\" libc5 used /etc/hostid; libc4 didn't have these functions diff --git a/man3/getloadavg.3 b/man3/getloadavg.3 index 15bbabdc53..efc7f60e88 100644 --- a/man3/getloadavg.3 +++ b/man3/getloadavg.3 @@ -52,7 +52,7 @@ the number of samples actually retrieved is returned. .\" function appeared in .\" 4.3BSD Reno . .SH VERSIONS -This function is available in glibc since version 2.2. +This function is available since glibc 2.2. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/getnameinfo.3 b/man3/getnameinfo.3 index cc3a89a383..ea3e160ff9 100644 --- a/man3/getnameinfo.3 +++ b/man3/getnameinfo.3 @@ -210,7 +210,7 @@ suitable for error reporting. .I /etc/resolv.conf .SH VERSIONS .BR getnameinfo () -is provided in glibc since version 2.1. +is provided since glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). @@ -262,7 +262,7 @@ header file. The latter is a guess based on the services listed in the current Assigned Numbers RFC. .PP -Before glibc version 2.2, the +Before glibc 2.2, the .I hostlen and .I servlen diff --git a/man3/getnetent.3 b/man3/getnetent.3 index 5e03eba27f..08b3f8abfd 100644 --- a/man3/getnetent.3 +++ b/man3/getnetent.3 @@ -176,7 +176,7 @@ then data races could occur. .SH STANDARDS POSIX.1-2001, POSIX.1-2008, 4.3BSD. .SH NOTES -In glibc versions before 2.2, the +Before glibc 2.2, the .I net argument of .BR getnetbyaddr () diff --git a/man3/getopt.3 b/man3/getopt.3 index 9cfde37e6c..982ae187f3 100644 --- a/man3/getopt.3 +++ b/man3/getopt.3 @@ -324,7 +324,7 @@ This variable was used by wildcard expansion and so should not be considered as options. This behavior was removed in .BR bash (1) -version 2.01, but the support remains in glibc. +2.01, but the support remains in glibc. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/getpass.3 b/man3/getpass.3 index bc46ce440f..5ebff130f4 100644 --- a/man3/getpass.3 +++ b/man3/getpass.3 @@ -24,7 +24,7 @@ Feature Test Macro Requirements for glibc (see .nf Since glibc 2.2.2: _XOPEN_SOURCE && ! (_POSIX_C_SOURCE >= 200112L) - || /* Glibc since 2.19: */ _DEFAULT_SOURCE + || /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _BSD_SOURCE Before glibc 2.2.2: none diff --git a/man3/getpt.3 b/man3/getpt.3 index 76443e24ef..5018b5c4c7 100644 --- a/man3/getpt.3 +++ b/man3/getpt.3 @@ -44,7 +44,7 @@ can fail with various errors described in .BR open (2). .SH VERSIONS .BR getpt () -is provided in glibc since version 2.1. +is provided since glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/getpwent.3 b/man3/getpwent.3 index e236aeea8e..9e7c1ddb81 100644 --- a/man3/getpwent.3 +++ b/man3/getpwent.3 @@ -37,7 +37,7 @@ Feature Test Macro Requirements for glibc (see .nf _XOPEN_SOURCE >= 500 .\" || _XOPEN_SOURCE && _XOPEN_SOURCE_EXTENDED - || /* Glibc since 2.19: */ _DEFAULT_SOURCE + || /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _BSD_SOURCE || _SVID_SOURCE .fi .SH DESCRIPTION diff --git a/man3/getpwnam.3 b/man3/getpwnam.3 index c168eb11b0..5cc6121560 100644 --- a/man3/getpwnam.3 +++ b/man3/getpwnam.3 @@ -248,8 +248,8 @@ situation: 0, ENOENT, EBADF, ESRCH, EWOULDBLOCK, EPERM, and probably others. .\" more precisely: .\" AIX 5.1 - gives ESRCH .\" OSF1 4.0g - gives EWOULDBLOCK -.\" libc, glibc up to version 2.6, Irix 6.5 - give ENOENT -.\" glibc since version 2.7 - give 0 +.\" libc, glibc up to glibc 2.6, Irix 6.5 - give ENOENT +.\" since glibc 2.7 - give 0 .\" FreeBSD 4.8, OpenBSD 3.2, NetBSD 1.6 - give EPERM .\" SunOS 5.8 - gives EBADF .\" Tru64 5.1b, HP-UX-11i, SunOS 5.7 - give 0 diff --git a/man3/gets.3 b/man3/gets.3 index e50613c9c6..a1d7505748 100644 --- a/man3/gets.3 +++ b/man3/gets.3 @@ -65,7 +65,7 @@ POSIX.1-2008 marks obsolescent. ISO C11 removes the specification of .BR gets () -from the C language, and since version 2.16, +from the C language, and since glibc 2.16, glibc header files don't expose the function declaration if the .B _ISOC11_SOURCE feature test macro is defined. diff --git a/man3/getutmp.3 b/man3/getutmp.3 index 6c7c14fd4c..e4315d4c5d 100644 --- a/man3/getutmp.3 +++ b/man3/getutmp.3 @@ -34,7 +34,7 @@ function performs the converse operation. .SH RETURN VALUE These functions do not return a value. .SH VERSIONS -These functions first appeared in glibc in version 2.1.1. +These functions were added in glibc 2.1.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/getw.3 b/man3/getw.3 index 5692ad247f..c1529bc870 100644 --- a/man3/getw.3 +++ b/man3/getw.3 @@ -26,7 +26,7 @@ Feature Test Macro Requirements for glibc (see .nf Since glibc 2.3.3: _XOPEN_SOURCE && ! (_POSIX_C_SOURCE >= 200112L) - || /* Glibc since 2.19: */ _DEFAULT_SOURCE + || /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _BSD_SOURCE || _SVID_SOURCE Before glibc 2.3.3: _SVID_SOURCE || _BSD_SOURCE || _XOPEN_SOURCE diff --git a/man3/gnu_get_libc_version.3 b/man3/gnu_get_libc_version.3 index 0fd99d21c9..013caea4c8 100644 --- a/man3/gnu_get_libc_version.3 +++ b/man3/gnu_get_libc_version.3 @@ -28,7 +28,7 @@ available on the system. This will be a string such as .IR "stable" . .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions first appeared in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/grantpt.3 b/man3/grantpt.3 index ac373a6c4f..f139e94322 100644 --- a/man3/grantpt.3 +++ b/man3/grantpt.3 @@ -67,7 +67,7 @@ The argument is valid but not associated with a master pseudoterminal. .SH VERSIONS .BR grantpt () -is provided in glibc since version 2.1. +is provided since glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/hash.3 b/man3/hash.3 index 03bd1095a8..43924e9690 100644 --- a/man3/hash.3 +++ b/man3/hash.3 @@ -21,8 +21,8 @@ Standard C library .fi .SH DESCRIPTION .IR "Note well" : -This page documents interfaces provided in glibc up until version 2.1. -Since version 2.2, glibc no longer provides these interfaces. +This page documents interfaces provided up until glibc 2.1. +Since glibc 2.2, glibc no longer provides these interfaces. Probably, you are looking for the APIs provided by the .I libdb library instead. diff --git a/man3/hsearch.3 b/man3/hsearch.3 index 5c9836a822..a78d6c63eb 100644 --- a/man3/hsearch.3 +++ b/man3/hsearch.3 @@ -276,7 +276,7 @@ allow it to free them. SVr4 and POSIX.1-2001 specify that \fIaction\fP is significant only for unsuccessful searches, so that an \fBENTER\fP should not do anything for a successful search. -In libc and glibc (before version 2.3), the +In libc and glibc (before glibc 2.3), the implementation violates the specification, updating the \fIdata\fP for the given \fIkey\fP in this case. .PP diff --git a/man3/iconv.3 b/man3/iconv.3 index bc634624d6..579189fcb4 100644 --- a/man3/iconv.3 +++ b/man3/iconv.3 @@ -141,7 +141,7 @@ An invalid multibyte sequence has been encountered in the input. .B EINVAL An incomplete multibyte sequence has been encountered in the input. .SH VERSIONS -This function is available in glibc since version 2.1. +This function is available since glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/iconv_close.3 b/man3/iconv_close.3 index edebbd03af..7d008bed8b 100644 --- a/man3/iconv_close.3 +++ b/man3/iconv_close.3 @@ -32,7 +32,7 @@ returns 0; otherwise, it returns \-1 and sets .I errno to indicate the error. .SH VERSIONS -This function is available in glibc since version 2.1. +This function is available since glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/iconv_open.3 b/man3/iconv_open.3 index 939fe011bd..03dbb9d159 100644 --- a/man3/iconv_open.3 +++ b/man3/iconv_open.3 @@ -100,7 +100,7 @@ to is not supported by the implementation. .SH VERSIONS -This function is available in glibc since version 2.1. +This function is available since glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/ilogb.3 b/man3/ilogb.3 index 5145ace5e7..16cad06320 100644 --- a/man3/ilogb.3 +++ b/man3/ilogb.3 @@ -130,7 +130,7 @@ T} Thread safety MT-Safe C99, POSIX.1-2001, POSIX.1-2008. .SH BUGS .\" Bug raised: http://sources.redhat.com/bugzilla/show_bug.cgi?id=6794 -Before version 2.16, the following bugs existed in the +Before glibc 2.16, the following bugs existed in the glibc implementation of these functions: .IP \(bu 3 The domain error case where diff --git a/man3/insque.3 b/man3/insque.3 index 7570e1a312..23d6d32071 100644 --- a/man3/insque.3 +++ b/man3/insque.3 @@ -37,7 +37,7 @@ Feature Test Macro Requirements for glibc (see .nf _XOPEN_SOURCE >= 500 .\" || _XOPEN_SOURCE && _XOPEN_SOURCE_EXTENDED - || /* Glibc since 2.19: */ _DEFAULT_SOURCE + || /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _SVID_SOURCE .fi .SH DESCRIPTION diff --git a/man3/isalpha.3 b/man3/isalpha.3 index 3b0b6b4b3c..504bc047fc 100644 --- a/man3/isalpha.3 +++ b/man3/isalpha.3 @@ -62,7 +62,7 @@ Feature Test Macro Requirements for glibc (see .BR isascii (): .nf _XOPEN_SOURCE - || /* Glibc since 2.19: */ _DEFAULT_SOURCE + || /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _SVID_SOURCE .fi .PP diff --git a/man3/lgamma.3 b/man3/lgamma.3 index 86d06511ed..fdc507bad9 100644 --- a/man3/lgamma.3 +++ b/man3/lgamma.3 @@ -170,6 +170,6 @@ is set to .BR EDOM ; instead of the POSIX-mandated .BR ERANGE . -Since version 2.10, glibc does the right thing. +Since glibc 2.10, glibc does the right thing. .SH SEE ALSO .BR tgamma (3) diff --git a/man3/lockf.3 b/man3/lockf.3 index edea069a90..c6fcb1af3d 100644 --- a/man3/lockf.3 +++ b/man3/lockf.3 @@ -28,7 +28,7 @@ Feature Test Macro Requirements for glibc (see .nf _XOPEN_SOURCE >= 500 .\" || _XOPEN_SOURCE && _XOPEN_SOURCE_EXTENDED - || /* Glibc since 2.19: */ _DEFAULT_SOURCE + || /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _BSD_SOURCE || _SVID_SOURCE .fi .SH DESCRIPTION diff --git a/man3/log1p.3 b/man3/log1p.3 index 7de998552c..f8258e9d31 100644 --- a/man3/log1p.3 +++ b/man3/log1p.3 @@ -131,14 +131,14 @@ T} Thread safety MT-Safe C99, POSIX.1-2001, POSIX.1-2008. .\" BSD .SH BUGS -Before version 2.22, the glibc implementation did not set +Before glibc 2.22, the glibc implementation did not set .\" https://www.sourceware.org/bugzilla/show_bug.cgi?id=6792 .I errno to .B EDOM when a domain error occurred. .PP -Before version 2.22, the glibc implementation did not set +Before glibc 2.22, the glibc implementation did not set .\" https://www.sourceware.org/bugzilla/show_bug.cgi?id=6792 .I errno to diff --git a/man3/log2.3 b/man3/log2.3 index c0fa1a6b2e..9bf70652c0 100644 --- a/man3/log2.3 +++ b/man3/log2.3 @@ -59,7 +59,7 @@ when calling these functions. For a discussion of the errors that can occur for these functions, see .BR log (3). .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/lrint.3 b/man3/lrint.3 index abcb6b5c43..40be4e9319 100644 --- a/man3/lrint.3 +++ b/man3/lrint.3 @@ -77,7 +77,7 @@ These functions do not set .\" FIXME . Is it intentional that these functions do not set errno? .\" Bug raised: http://sources.redhat.com/bugzilla/show_bug.cgi?id=6798 .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/lround.3 b/man3/lround.3 index c68bc4439e..9eb5a3f37a 100644 --- a/man3/lround.3 +++ b/man3/lround.3 @@ -80,7 +80,7 @@ These functions do not set .\" FIXME . Is it intentional that these functions do not set errno? .\" Bug raised: http://sources.redhat.com/bugzilla/show_bug.cgi?id=6797 .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/lseek64.3 b/man3/lseek64.3 index b03070ef17..462c2bb691 100644 --- a/man3/lseek64.3 +++ b/man3/lseek64.3 @@ -97,7 +97,7 @@ is available only when one compiles with .PP The function .BR lseek64 () -.\" in glibc 2.0.94, not in 2.0.6 +.\" in glibc 2.0.94, not in glibc 2.0.6 is available since glibc 2.1. .\" .SS llseek() diff --git a/man3/makecontext.3 b/man3/makecontext.3 index 08fb456ff4..1cb1fe9b8e 100644 --- a/man3/makecontext.3 +++ b/man3/makecontext.3 @@ -88,7 +88,7 @@ Insufficient stack space left. .BR makecontext () and .BR swapcontext () -are provided in glibc since version 2.1. +are provided since glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). @@ -142,7 +142,7 @@ However, doing this is not guaranteed to be portable, is undefined according to the standards, and won't work on architectures where pointers are larger than .IR int s. -Nevertheless, starting with version 2.8, glibc makes some changes to +Nevertheless, starting with glibc 2.8, glibc makes some changes to .BR makecontext (), to permit this on some 64-bit architectures (e.g., x86-64). .SH EXAMPLES diff --git a/man3/malloc.3 b/man3/malloc.3 index ed1c604f0a..76cf9b40e1 100644 --- a/man3/malloc.3 +++ b/man3/malloc.3 @@ -227,7 +227,7 @@ limit described in .BR getrlimit (2). .SH VERSIONS .BR reallocarray () -first appeared in glibc in version 2.26. +was added in glibc 2.26. .PP .BR malloc () and related functions rejected sizes greater than diff --git a/man3/malloc_get_state.3 b/man3/malloc_get_state.3 index 8cb8184c12..6bcc8d6b07 100644 --- a/man3/malloc_get_state.3 +++ b/man3/malloc_get_state.3 @@ -18,7 +18,7 @@ Standard C library .fi .SH DESCRIPTION .IR Note : -these function are removed in glibc version 2.25. +these function are removed in glibc 2.25. .PP The .BR malloc_get_state () diff --git a/man3/malloc_info.3 b/man3/malloc_info.3 index bf063da93f..c7c74ea755 100644 --- a/man3/malloc_info.3 +++ b/man3/malloc_info.3 @@ -42,7 +42,7 @@ is set to indicate the error. was nonzero. .SH VERSIONS .BR malloc_info () -was added to glibc in version 2.10. +was added in glibc 2.10. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/mallopt.3 b/man3/mallopt.3 index e058b0dec4..c8c017c90c 100644 --- a/man3/mallopt.3 +++ b/man3/mallopt.3 @@ -111,7 +111,7 @@ If this bit is set, then, after printing any error message specified by bit 0, the program is terminated by calling .BR abort (3). -In glibc versions since 2.4, +Since glibc 2.4, if bit 0 is also set, then, between printing the error message and aborting, the program also prints a stack trace in the manner of @@ -162,7 +162,7 @@ and abort the program. Since glibc 2.3.4, the default value for the .B M_CHECK_ACTION parameter is 3. -In glibc version 2.3.3 and earlier, the default value is 1. +In glibc 2.3.3 and earlier, the default value is 1. .IP Using a nonzero .B M_CHECK_ACTION diff --git a/man3/memchr.3 b/man3/memchr.3 index fccb3f6bd3..5ad195d1b9 100644 --- a/man3/memchr.3 +++ b/man3/memchr.3 @@ -100,10 +100,10 @@ function returns a pointer to the matching byte, if one is found. If no matching byte is found, the result is unspecified. .SH VERSIONS .BR rawmemchr () -first appeared in glibc in version 2.1. +first appeared in glibc 2.1. .PP .BR memrchr () -first appeared in glibc in version 2.2. +first appeared in glibc 2.2. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/mempcpy.3 b/man3/mempcpy.3 index b0d059dabe..34228e382f 100644 --- a/man3/mempcpy.3 +++ b/man3/mempcpy.3 @@ -58,7 +58,7 @@ wide characters. .IR n . .SH VERSIONS .BR mempcpy () -first appeared in glibc in version 2.1. +first appeared in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/mkfifo.3 b/man3/mkfifo.3 index aeac3b3ff2..403b8869ca 100644 --- a/man3/mkfifo.3 +++ b/man3/mkfifo.3 @@ -163,10 +163,10 @@ is a file descriptor referring to a file other than a directory. \fIpathname\fP refers to a read-only filesystem. .SH VERSIONS .BR mkfifoat () -was added to glibc in version 2.4. +was added in glibc 2.4. It is implemented using .BR mknodat (2), -available on Linux since kernel 2.6.16. +available since Linux 2.6.16. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/mkstemp.3 b/man3/mkstemp.3 index 74dab4a922..8426462da3 100644 --- a/man3/mkstemp.3 +++ b/man3/mkstemp.3 @@ -37,7 +37,7 @@ Feature Test Macro Requirements for glibc (see .nf _XOPEN_SOURCE >= 500 .\" || _XOPEN_SOURCE && _XOPEN_SOURCE_EXTENDED - || /* Since glibc 2.12: */ _POSIX_C_SOURCE >= 200809L + || /* Glibc >= 2.12: */ _POSIX_C_SOURCE >= 200809L || /* Glibc <= 2.19: */ _SVID_SOURCE || _BSD_SOURCE .fi .PP @@ -48,7 +48,7 @@ Feature Test Macro Requirements for glibc (see .PP .BR mkstemps (): .nf - /* Glibc since 2.19: */ _DEFAULT_SOURCE + /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _SVID_SOURCE || _BSD_SOURCE .fi .PP diff --git a/man3/mktemp.3 b/man3/mktemp.3 index 586ac0f83d..6f80d580cb 100644 --- a/man3/mktemp.3 +++ b/man3/mktemp.3 @@ -33,7 +33,7 @@ Feature Test Macro Requirements for glibc (see .nf Since glibc 2.12: (_XOPEN_SOURCE >= 500) && ! (_POSIX_C_SOURCE >= 200112L) - || /* Glibc since 2.19: */ _DEFAULT_SOURCE + || /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _SVID_SOURCE || _BSD_SOURCE Before glibc 2.12: _BSD_SOURCE || _SVID_SOURCE || _XOPEN_SOURCE >= 500 diff --git a/man3/mpool.3 b/man3/mpool.3 index ea0c82a2a7..de6f023a8e 100644 --- a/man3/mpool.3 +++ b/man3/mpool.3 @@ -33,8 +33,8 @@ Standard C library .fi .SH DESCRIPTION .IR "Note well" : -This page documents interfaces provided in glibc up until version 2.1. -Since version 2.2, glibc no longer provides these interfaces. +This page documents interfaces provided up until glibc 2.1. +Since glibc 2.2, glibc no longer provides these interfaces. Probably, you are looking for the APIs provided by the .I libdb library instead. diff --git a/man3/mq_open.3 b/man3/mq_open.3 index 46838488e8..232cdfa300 100644 --- a/man3/mq_open.3 +++ b/man3/mq_open.3 @@ -285,7 +285,7 @@ without the preceding slash (i.e., .IR name+1 ) to the system call. .SH BUGS -In kernels before 2.6.14, +Before Linux 2.6.14, the process umask was not applied to the permissions specified in .IR mode . .SH SEE ALSO diff --git a/man3/nan.3 b/man3/nan.3 index 128151a849..0025f27436 100644 --- a/man3/nan.3 +++ b/man3/nan.3 @@ -66,7 +66,7 @@ On IEEE 754 systems, there are many representations of NaN, and selects one. On other systems it may do nothing. .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/newlocale.3 b/man3/newlocale.3 index c5dec82045..3da77490a4 100644 --- a/man3/newlocale.3 +++ b/man3/newlocale.3 @@ -187,7 +187,7 @@ The .BR newlocale () and .BR freelocale () -functions first appeared in version 2.3 of the GNU C library. +functions first appeared in glibc 2.3. .SH STANDARDS POSIX.1-2008. .SH NOTES diff --git a/man3/nextafter.3 b/man3/nextafter.3 index 384ff96961..f4911911f9 100644 --- a/man3/nextafter.3 +++ b/man3/nextafter.3 @@ -186,12 +186,12 @@ C99, POSIX.1-2001, POSIX.1-2008. This function is defined in IEC 559 (and the appendix with recommended functions in IEEE 754/IEEE 854). .SH BUGS -In glibc version 2.5 and earlier, these functions do not raise an underflow +In glibc 2.5 and earlier, these functions do not raise an underflow floating-point .RB ( FE_UNDERFLOW ) exception when an underflow occurs. .PP -Before glibc version 2.23 +Before glibc 2.23 .\" https://www.sourceware.org/bugzilla/show_bug.cgi?id=6799 these functions did not set .IR errno . diff --git a/man3/nextup.3 b/man3/nextup.3 index 19e99ecc69..9ee790a034 100644 --- a/man3/nextup.3 +++ b/man3/nextup.3 @@ -63,7 +63,7 @@ and similarly for the other types. See DESCRIPTION. .\" .SH ERRORS .SH VERSIONS -These functions first appeared in glibc in version 2.24. +These functions were added in glibc 2.24. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/open_memstream.3 b/man3/open_memstream.3 index 649b808f00..9d39edf9e5 100644 --- a/man3/open_memstream.3 +++ b/man3/open_memstream.3 @@ -128,7 +128,7 @@ returned by these functions .BR fileno (3) will return an error if called on the returned stream). .SH BUGS -In glibc before version 2.7, seeking past the end of a stream created by +Before glibc 2.7, seeking past the end of a stream created by .BR open_memstream () does not enlarge the buffer; instead the .BR fseek (3) diff --git a/man3/opendir.3 b/man3/opendir.3 index 4657bc8bce..5cd1fb51e0 100644 --- a/man3/opendir.3 +++ b/man3/opendir.3 @@ -90,7 +90,7 @@ Insufficient memory to complete the operation. \fIname\fP is not a directory. .SH VERSIONS .BR fdopendir () -is available in glibc since version 2.4. +is available since glibc 2.4. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/openpty.3 b/man3/openpty.3 index 191594f9d6..f247eb7b56 100644 --- a/man3/openpty.3 +++ b/man3/openpty.3 @@ -158,7 +158,7 @@ and .BR forkpty () in glibc 2.8. .PP -In versions of glibc before 2.0.92, +Before glibc 2.0.92, .BR openpty () returns file descriptors for a BSD pseudoterminal pair; since glibc 2.0.92, diff --git a/man3/perror.3 b/man3/perror.3 index a561cbd56c..db4bce4045 100644 --- a/man3/perror.3 +++ b/man3/perror.3 @@ -37,7 +37,7 @@ Feature Test Macro Requirements for glibc (see .IR sys_errlist , .IR sys_nerr : .nf - From glibc 2.19 to 2.31: + From glibc 2.19 to glibc 2.31: _DEFAULT_SOURCE Glibc 2.19 and earlier: _BSD_SOURCE @@ -99,7 +99,7 @@ the value of .I errno should be saved. .SH VERSIONS -Since glibc version 2.32, the declarations of +Since glibc 2.32, the declarations of .I sys_errlist and .I sys_nerr diff --git a/man3/posix_madvise.3 b/man3/posix_madvise.3 index 2639900bc4..501295239d 100644 --- a/man3/posix_madvise.3 +++ b/man3/posix_madvise.3 @@ -88,7 +88,7 @@ the caller's address space. .SH VERSIONS Support for .BR posix_madvise () -first appeared in glibc version 2.2. +was added in glibc 2.2. .SH STANDARDS POSIX.1-2001. .SH NOTES diff --git a/man3/posix_memalign.3 b/man3/posix_memalign.3 index de9d29a666..b08539b0a0 100644 --- a/man3/posix_memalign.3 +++ b/man3/posix_memalign.3 @@ -46,7 +46,7 @@ Feature Test Macro Requirements for glibc (see .nf Since glibc 2.12: (_XOPEN_SOURCE >= 500) && !(_POSIX_C_SOURCE >= 200112L) - || /* Glibc since 2.19: */ _DEFAULT_SOURCE + || /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _SVID_SOURCE || _BSD_SOURCE Before glibc 2.12: _BSD_SOURCE || _XOPEN_SOURCE >= 500 @@ -154,7 +154,7 @@ have been available since at least glibc 2.0. .PP The function .BR aligned_alloc () -was added to glibc in version 2.16. +was added in glibc 2.16. .PP The function .BR posix_memalign () diff --git a/man3/posix_openpt.3 b/man3/posix_openpt.3 index cb30c57249..ddb9f669dc 100644 --- a/man3/posix_openpt.3 +++ b/man3/posix_openpt.3 @@ -56,7 +56,7 @@ See .SH VERSIONS Glibc support for .BR posix_openpt () -has been provided since version 2.2.1. +has been provided since glibc 2.2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/posix_spawn.3 b/man3/posix_spawn.3 index dcfbb7d984..0a7617edfa 100644 --- a/man3/posix_spawn.3 +++ b/man3/posix_spawn.3 @@ -385,7 +385,7 @@ The feature test macro must be defined to obtain the definition of this constant. .\" This flag has been accepted in POSIX, see: .\" http://austingroupbugs.net/view.php?id=1044 -.\" and has been implemented in glibc since version 2.26 +.\" and has been implemented since glibc 2.26 .\" commit daeb1fa2e1b33323e719015f5f546988bd4cc73b .PP If diff --git a/man3/pow.3 b/man3/pow.3 index f762a93aa0..b90ae1a29b 100644 --- a/man3/pow.3 +++ b/man3/pow.3 @@ -353,7 +353,7 @@ A number of bugs .\" http://sources.redhat.com/bugzilla/show_bug.cgi?id=3866 in the glibc implementation of .BR pow () -were fixed in glibc version 2.16. +were fixed in glibc 2.16. .PP In glibc 2.9 and earlier, .\" @@ -364,14 +364,14 @@ is set to .B EDOM instead of the POSIX-mandated .BR ERANGE . -Since version 2.10, +Since glibc 2.10, .\" or possibly 2.9, I haven't found the source code change .\" and I don't have a 2.9 system to test glibc does the right thing. .PP -In version 2.3.2 and earlier, -.\" Actually, 2.3.2 is the earliest test result I have; so yet -.\" to confirm if this error occurs only in 2.3.2. +In glibc 2.3.2 and earlier, +.\" Actually, glibc 2.3.2 is the earliest test result I have; so yet +.\" to confirm if this error occurs only in glibc 2.3.2. when an overflow or underflow error occurs, glibc's .BR pow () generates a bogus invalid floating-point exception diff --git a/man3/pow10.3 b/man3/pow10.3 index 41e35284dd..613b835f5f 100644 --- a/man3/pow10.3 +++ b/man3/pow10.3 @@ -29,7 +29,7 @@ in TS\ 18661-4:2015. Those latter functions should be used in preference to the functions described in this page. .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. Since glibc 2.27, .\" glibc commit 5a80d39d0d2587e9bd8e72f19e92eeb2a66fbe9e the use of these functions in new programs is no longer supported. diff --git a/man3/printf.3 b/man3/printf.3 index 85a5db632f..5e7afd9e54 100644 --- a/man3/printf.3 +++ b/man3/printf.3 @@ -1023,7 +1023,7 @@ The glibc implementation of the functions and .BR vsnprintf () conforms to the C99 standard, that is, behaves as described above, -since glibc version 2.1. +since glibc 2.1. Until glibc 2.0.6, they would return \-1 when the output was truncated. .\" .SH HISTORY @@ -1199,8 +1199,8 @@ make_message(const char *fmt, ...) } .EE .PP -If truncation occurs in glibc versions prior to 2.0.6, this is treated as an -error instead of being handled gracefully. +If truncation occurs in glibc versions prior to glibc 2.0.6, +this is treated as an error instead of being handled gracefully. .SH SEE ALSO .BR printf (1), .BR asprintf (3), diff --git a/man3/psignal.3 b/man3/psignal.3 index 0d1d7078ad..9fd608c36d 100644 --- a/man3/psignal.3 +++ b/man3/psignal.3 @@ -77,7 +77,7 @@ functions return no value. .SH VERSIONS The .BR psiginfo () -function was added to glibc in version 2.10. +function was added in glibc 2.10. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). @@ -99,7 +99,7 @@ T} Thread safety MT-Safe locale .SH STANDARDS POSIX.1-2008, 4.3BSD. .SH BUGS -In glibc versions up to 2.12, +Up to glibc 2.12, .BR psiginfo () had the following bugs: .IP \(bu 3 diff --git a/man3/pthread_attr_setaffinity_np.3 b/man3/pthread_attr_setaffinity_np.3 index d8cfffba34..4366a48485 100644 --- a/man3/pthread_attr_setaffinity_np.3 +++ b/man3/pthread_attr_setaffinity_np.3 @@ -85,7 +85,7 @@ is too small). .RB ( pthread_attr_setaffinity_np ()) Could not allocate memory. .SH VERSIONS -These functions are provided by glibc since version 2.3.4. +These functions are provided since glibc 2.3.4. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/pthread_attr_setguardsize.3 b/man3/pthread_attr_setguardsize.3 index e37bb60b3a..5da9ac9002 100644 --- a/man3/pthread_attr_setguardsize.3 +++ b/man3/pthread_attr_setguardsize.3 @@ -83,7 +83,7 @@ On Linux these functions always succeed (but portable and future-proof applications should nevertheless handle a possible error return). .SH VERSIONS -These functions are provided by glibc since version 2.1. +These functions are provided since glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/pthread_attr_setsigmask_np.3 b/man3/pthread_attr_setsigmask_np.3 index 136ab6ae82..fbfb8fd492 100644 --- a/man3/pthread_attr_setsigmask_np.3 +++ b/man3/pthread_attr_setsigmask_np.3 @@ -68,7 +68,7 @@ On error, these functions return a positive error number. .RB ( pthread_attr_setsigmask_np ()) Could not allocate memory. .SH VERSIONS -These functions are provided by glibc since version 2.32. +These functions are provided since glibc 2.32. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/pthread_attr_setstack.3 b/man3/pthread_attr_setstack.3 index b263698ff0..3392c96d19 100644 --- a/man3/pthread_attr_setstack.3 +++ b/man3/pthread_attr_setstack.3 @@ -89,7 +89,7 @@ and .I stacksize is not both readable and writable by the caller. .SH VERSIONS -These functions are provided by glibc since version 2.2. +These functions are provided since glibc 2.2. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/pthread_attr_setstackaddr.3 b/man3/pthread_attr_setstackaddr.3 index 3905b9b13e..5dbaa5ab1c 100644 --- a/man3/pthread_attr_setstackaddr.3 +++ b/man3/pthread_attr_setstackaddr.3 @@ -60,7 +60,7 @@ No errors are defined (but applications should nevertheless handle a possible error return). .SH VERSIONS -These functions are provided by glibc since version 2.1. +These functions are provided since glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/pthread_attr_setstacksize.3 b/man3/pthread_attr_setstacksize.3 index 15f3a2c2e8..e206f8d9b5 100644 --- a/man3/pthread_attr_setstacksize.3 +++ b/man3/pthread_attr_setstacksize.3 @@ -60,7 +60,7 @@ if .I stacksize is not a multiple of the system page size. .SH VERSIONS -These functions are provided by glibc since version 2.1. +These functions are provided since glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/pthread_getattr_default_np.3 b/man3/pthread_getattr_default_np.3 index 8ecc8c6a95..4f89681046 100644 --- a/man3/pthread_getattr_default_np.3 +++ b/man3/pthread_getattr_default_np.3 @@ -58,7 +58,7 @@ is invalid, or the stack address attribute is set in .RB ( pthread_setattr_default_np ()) Insufficient memory. .SH VERSIONS -These functions are available in glibc since version 2.18. +These functions are available since glibc 2.18. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/pthread_getattr_np.3 b/man3/pthread_getattr_np.3 index 047379e5bb..f2c48c5624 100644 --- a/man3/pthread_getattr_np.3 +++ b/man3/pthread_getattr_np.3 @@ -75,7 +75,7 @@ if the .B RLIMIT_STACK resource limit is not supported. .SH VERSIONS -This function is available in glibc since version 2.2.3. +This function is available since glibc 2.2.3. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/pthread_getcpuclockid.3 b/man3/pthread_getcpuclockid.3 index 7bbc5bdee7..e05b9222ed 100644 --- a/man3/pthread_getcpuclockid.3 +++ b/man3/pthread_getcpuclockid.3 @@ -45,7 +45,7 @@ No thread with the ID .I thread could be found. .SH VERSIONS -This function is available in glibc since version 2.2. +This function is available since glibc 2.2. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/pthread_mutex_consistent.3 b/man3/pthread_mutex_consistent.3 index 2941e93ca3..d2a983db1c 100644 --- a/man3/pthread_mutex_consistent.3 +++ b/man3/pthread_mutex_consistent.3 @@ -46,7 +46,7 @@ it returns a positive error number to indicate the error. The mutex is either not robust or is not in an inconsistent state. .SH VERSIONS .BR pthread_mutex_consistent () -was added to glibc in version 2.12. +was added in glibc 2.12. .SH STANDARDS POSIX.1-2008. .SH NOTES diff --git a/man3/pthread_mutexattr_setrobust.3 b/man3/pthread_mutexattr_setrobust.3 index e8a9b344d1..a1205190db 100644 --- a/man3/pthread_mutexattr_setrobust.3 +++ b/man3/pthread_mutexattr_setrobust.3 @@ -124,7 +124,7 @@ was passed to .BR pthread_mutexattr_getrobust () and .BR pthread_mutexattr_setrobust () -were added to glibc in version 2.12. +were added in glibc 2.12. .SH STANDARDS POSIX.1-2008. .SH NOTES diff --git a/man3/pthread_setaffinity_np.3 b/man3/pthread_setaffinity_np.3 index 07b756f6be..fa487bddf5 100644 --- a/man3/pthread_setaffinity_np.3 +++ b/man3/pthread_setaffinity_np.3 @@ -94,7 +94,7 @@ No thread with the ID .I thread could be found. .SH VERSIONS -These functions are provided by glibc since version 2.3.4. +These functions are provided since glibc 2.3.4. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/pthread_setconcurrency.3 b/man3/pthread_setconcurrency.3 index e9e1146b08..d3f2636f6e 100644 --- a/man3/pthread_setconcurrency.3 +++ b/man3/pthread_setconcurrency.3 @@ -60,7 +60,7 @@ error ("the value specified by .I new_level would cause a system resource to be exceeded"). .SH VERSIONS -These functions are available in glibc since version 2.1. +These functions are available since glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/pthread_setname_np.3 b/man3/pthread_setname_np.3 index df51c8e4f2..c953dcca20 100644 --- a/man3/pthread_setname_np.3 +++ b/man3/pthread_setname_np.3 @@ -80,7 +80,7 @@ If either of these functions fails to open then the call may fail with one of the errors described in .BR open (2). .SH VERSIONS -These functions first appeared in glibc in version 2.12. +These functions were added in glibc 2.12. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/pthread_setschedprio.3 b/man3/pthread_setschedprio.3 index 965bfa8057..b3a9439ce1 100644 --- a/man3/pthread_setschedprio.3 +++ b/man3/pthread_setschedprio.3 @@ -60,7 +60,7 @@ POSIX.1 also documents an to an unsupported value") error for .BR pthread_setschedparam (3). .SH VERSIONS -This function is available in glibc since version 2.3.4. +This function is available since glibc 2.3.4. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/pthread_spin_init.3 b/man3/pthread_spin_init.3 index 23a8beb971..511820fee0 100644 --- a/man3/pthread_spin_init.3 +++ b/man3/pthread_spin_init.3 @@ -104,7 +104,7 @@ a new spin lock. .B ENOMEM Insufficient memory to initialize the spin lock. .SH VERSIONS -These functions first appeared in glibc in version 2.2. +These functions were added in glibc 2.2. .SH STANDARDS POSIX.1-2001. .PP diff --git a/man3/pthread_spin_lock.3 b/man3/pthread_spin_lock.3 index e8c8181bde..7a41f203dc 100644 --- a/man3/pthread_spin_lock.3 +++ b/man3/pthread_spin_lock.3 @@ -83,7 +83,7 @@ fails with the following errors: .B EBUSY The spin lock is currently locked by another thread. .SH VERSIONS -These functions first appeared in glibc in version 2.2. +These functions were added in glibc 2.2. .SH STANDARDS POSIX.1-2001. .SH NOTES diff --git a/man3/pthread_tryjoin_np.3 b/man3/pthread_tryjoin_np.3 index 86afc00293..874e67ebd6 100644 --- a/man3/pthread_tryjoin_np.3 +++ b/man3/pthread_tryjoin_np.3 @@ -92,7 +92,7 @@ terminated. never returns the error .BR EINTR . .SH VERSIONS -These functions first appeared in glibc in version 2.3.3. +These functions were added in glibc 2.3.3. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/ptsname.3 b/man3/ptsname.3 index 38fead7625..83e4c2496e 100644 --- a/man3/ptsname.3 +++ b/man3/ptsname.3 @@ -90,7 +90,7 @@ only) is too small. .SH VERSIONS .BR ptsname () -is provided in glibc since version 2.1. +is provided since glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/putenv.3 b/man3/putenv.3 index 2f81a97935..2674a4b960 100644 --- a/man3/putenv.3 +++ b/man3/putenv.3 @@ -35,7 +35,7 @@ Feature Test Macro Requirements for glibc (see .BR putenv (): .nf _XOPEN_SOURCE - || /* Glibc since 2.19: */ _DEFAULT_SOURCE + || /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _SVID_SOURCE .fi .SH DESCRIPTION @@ -100,7 +100,7 @@ one in glibc 2.0 is not, but the glibc 2.1 version is. .\" In no case will the old storage associated .\" to the environment variable itself be freed. .PP -Since version 2.1.2, the glibc implementation conforms to SUSv2: +Since glibc 2.1.2, the glibc implementation conforms to SUSv2: the pointer \fIstring\fP given to .BR putenv () is used. @@ -111,7 +111,8 @@ changing it later will change the environment. with an automatic variable as the argument, then return from the calling function while \fIstring\fP is still part of the environment.) -However, glibc versions 2.0 to 2.1.1 differ: a copy of the string is used. +However, from glibc 2.0 to glibc 2.1.1, it differs:r +a copy of the string is used. On the one hand this causes a memory leak, and on the other hand it violates SUSv2. .PP diff --git a/man3/qsort.3 b/man3/qsort.3 index bbd7b1986b..67ecd8cef8 100644 --- a/man3/qsort.3 +++ b/man3/qsort.3 @@ -82,7 +82,7 @@ and functions return no value. .SH VERSIONS .BR qsort_r () -was added to glibc in version 2.8. +was added in glibc 2.8. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/raise.3 b/man3/raise.3 index ce6eba7c40..ac9189f56a 100644 --- a/man3/raise.3 +++ b/man3/raise.3 @@ -64,9 +64,9 @@ T} Thread safety MT-Safe .SH STANDARDS POSIX.1-2001, POSIX.1-2008, C89, C99. .SH NOTES -Since version 2.3.3, glibc implements +Since glibc 2.3.3, .BR raise () -by calling +is implemented by calling .BR tgkill (2), .\" 2.3.2 used the obsolete tkill(), if available. if the kernel supports that system call. diff --git a/man3/random.3 b/man3/random.3 index 6b4f90e6da..6c8fb81b1b 100644 --- a/man3/random.3 +++ b/man3/random.3 @@ -39,7 +39,7 @@ Feature Test Macro Requirements for glibc (see .nf _XOPEN_SOURCE >= 500 .\" || _XOPEN_SOURCE && _XOPEN_SOURCE_EXTENDED - || /* Glibc since 2.19: */ _DEFAULT_SOURCE + || /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _SVID_SOURCE || _BSD_SOURCE .fi .SH DESCRIPTION diff --git a/man3/random_r.3 b/man3/random_r.3 index 914e6ea254..353aea08b3 100644 --- a/man3/random_r.3 +++ b/man3/random_r.3 @@ -35,7 +35,7 @@ Feature Test Macro Requirements for glibc (see .BR initstate_r (), .BR setstate_r (): .nf - /* Glibc since 2.19: */ _DEFAULT_SOURCE + /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _SVID_SOURCE || _BSD_SOURCE .fi .SH DESCRIPTION diff --git a/man3/rcmd.3 b/man3/rcmd.3 index b2fb892d47..93511eb3c7 100644 --- a/man3/rcmd.3 +++ b/man3/rcmd.3 @@ -249,7 +249,7 @@ The functions .BR rresvport_af (), and .BR ruserok_af () -functions are provide in glibc since version 2.2. +functions are provided since glibc 2.2. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). @@ -290,7 +290,7 @@ and are not present on as wide a range of systems. .BR iruserok () and .BR iruserok_af () -are declared in glibc headers only since version 2.12. +are declared in glibc headers only since glibc 2.12. .\" Bug filed 25 Nov 2007: .\" http://sources.redhat.com/bugzilla/show_bug.cgi?id=5399 .SH SEE ALSO diff --git a/man3/readdir.3 b/man3/readdir.3 index 54bfd88a5c..8eb85c9625 100644 --- a/man3/readdir.3 +++ b/man3/readdir.3 @@ -94,9 +94,9 @@ if further actions depend on the type of the file. .IP When a suitable feature test macro is defined .RB ( _DEFAULT_SOURCE -on glibc versions since 2.19, or +since glibc 2.19, or .B _BSD_SOURCE -on glibc versions 2.19 and earlier), +on glibc 2.19 and earlier), glibc defines the following macro constants for the value returned in .IR d_type : .RS diff --git a/man3/readdir_r.3 b/man3/readdir_r.3 index eaefbde873..38f87d1770 100644 --- a/man3/readdir_r.3 +++ b/man3/readdir_r.3 @@ -56,7 +56,7 @@ It is recommended that applications use .BR readdir (3) instead of .BR readdir_r (). -Furthermore, since version 2.24, glibc deprecates +Furthermore, since glibc 2.24, glibc deprecates .BR readdir_r (). The reasons are as follows: .IP \(bu 3 diff --git a/man3/realpath.3 b/man3/realpath.3 index 99dbef2fdf..451a6d9a1f 100644 --- a/man3/realpath.3 +++ b/man3/realpath.3 @@ -29,7 +29,7 @@ Feature Test Macro Requirements for glibc (see .nf _XOPEN_SOURCE >= 500 .\" || _XOPEN_SOURCE && _XOPEN_SOURCE_EXTENDED - || /* Glibc since 2.19: */ _DEFAULT_SOURCE + || /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _BSD_SOURCE .fi .SH DESCRIPTION @@ -93,7 +93,7 @@ Read or search permission was denied for a component of the path prefix. .I path is NULL. .\" (In libc5 this would just cause a segfault.) -(In glibc versions before 2.3, +(Before glibc 2.3, this error is also returned if .I resolved_path is NULL.) diff --git a/man3/recno.3 b/man3/recno.3 index 0c28f746c0..320285a840 100644 --- a/man3/recno.3 +++ b/man3/recno.3 @@ -21,8 +21,8 @@ Standard C library .fi .SH DESCRIPTION .IR "Note well" : -This page documents interfaces provided in glibc up until version 2.1. -Since version 2.2, glibc no longer provides these interfaces. +This page documents interfaces provided up until glibc 2.1. +Since glibc 2.2, glibc no longer provides these interfaces. Probably, you are looking for the APIs provided by the .I libdb library instead. diff --git a/man3/remquo.3 b/man3/remquo.3 index ef55a06a98..45a7ca6a22 100644 --- a/man3/remquo.3 +++ b/man3/remquo.3 @@ -111,7 +111,7 @@ These functions do not set .\" FIXME . Is it intentional that these functions do not set errno? .\" Bug raised: http://sources.redhat.com/bugzilla/show_bug.cgi?id=6802 .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/resolver.3 b/man3/resolver.3 index 070a87f1bc..f1ffd80969 100644 --- a/man3/resolver.3 +++ b/man3/resolver.3 @@ -272,7 +272,7 @@ Accept authoritative answers only. .BR res_send () continues until it finds an authoritative answer or returns an error. -This option was present but unimplemented in glibc until version 2.24; +This option was present but unimplemented until glibc 2.24; since glibc 2.25, it is deprecated, and its usage produces a warning. .TP .B RES_USEVC @@ -280,7 +280,7 @@ Use TCP connections for queries rather than UDP datagrams. .TP .BR RES_PRIMARY " (unimplemented; deprecated in glibc 2.25)" Query primary domain name server only. -This option was present but unimplemented in glibc until version 2.24; +This option was present but unimplemented until glibc 2.24; since glibc 2.25, it is deprecated, and its usage produces a warning. .TP .B RES_IGNTC @@ -356,20 +356,20 @@ time. Disable the modern BIND checking of incoming hostnames and mail names for invalid characters such as underscore (_), non-ASCII, or control characters. -This option was present in glibc until version 2.24; +This option was present until glibc 2.24; since glibc 2.25, it is deprecated, and its usage produces a warning. .TP .BR RES_KEEPTSIG " (unimplemented; deprecated in glibc 2.25)" Do not strip TSIG records. -This option was present but unimplemented in glibc until version 2.24; +This option was present but unimplemented until glibc 2.24; since glibc 2.25, it is deprecated, and its usage produces a warning. .TP .BR RES_BLAST " (unimplemented; deprecated in glibc 2.25)" Send each query simultaneously and recursively to all servers. -This option was present but unimplemented in glibc until version 2.24; +This option was present but unimplemented until glibc 2.24; since glibc 2.25, it is deprecated, and its usage produces a warning. .TP -.BR RES_USEBSTRING " (glibc 2.3.4 to 2.24)" +.BR RES_USEBSTRING " (glibc 2.3.4 to glibc 2.24)" Make reverse IPv6 lookups using the bit-label format described in RFC 2673; if this option is not set (which is the default), then nibble format is used. This option was removed in glibc 2.25, @@ -382,7 +382,7 @@ Use zone in IPv6 reverse lookup instead of .IR ip6.int , which is deprecated since glibc 2.3.4. -This option is present in glibc up to and including version 2.24, +This option is present up to and including glibc 2.24, where it is enabled by default. In glibc 2.25, this option was removed. .TP @@ -390,8 +390,8 @@ In glibc 2.25, this option was removed. Enables support for the DNS extensions (EDNS0) described in RFC 2671. .TP .BR RES_SNGLKUP " (since glibc 2.10)" -By default, glibc performs IPv4 and IPv6 lookups in parallel since -version 2.9. +By default, glibc performs IPv4 and IPv6 lookups in parallel +since glibc 2.9. Some appliance DNS servers cannot handle these queries properly and make the requests time out. This option disables the behavior and makes glibc diff --git a/man3/rexec.3 b/man3/rexec.3 index 0cdd0ac66f..7d1a6e00d2 100644 --- a/man3/rexec.3 +++ b/man3/rexec.3 @@ -125,7 +125,7 @@ or .SH VERSIONS The .BR rexec_af () -function was added to glibc in version 2.2. +function was added in glibc 2.2. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/round.3 b/man3/round.3 index 81140c56e3..f6b86c689b 100644 --- a/man3/round.3 +++ b/man3/round.3 @@ -57,7 +57,7 @@ itself is returned. No errors occur. POSIX.1-2001 documents a range error for overflows, but see NOTES. .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/scalbln.3 b/man3/scalbln.3 index 36c7448618..50e90c4c7e 100644 --- a/man3/scalbln.3 +++ b/man3/scalbln.3 @@ -123,7 +123,7 @@ An underflow floating-point exception .RB ( FE_UNDERFLOW ) is raised. .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/scandir.3 b/man3/scandir.3 index 66538b2af8..0e6721cb70 100644 --- a/man3/scandir.3 +++ b/man3/scandir.3 @@ -181,10 +181,10 @@ is a relative pathname and is a file descriptor referring to a file other than a directory. .SH VERSIONS .BR versionsort () -was added to glibc in version 2.1. +was added in glibc 2.1. .PP .BR scandirat () -was added to glibc in version 2.15. +was added in glibc 2.15. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/scanf.3 b/man3/scanf.3 index 211dd8ef6b..ba470a5c1c 100644 --- a/man3/scanf.3 +++ b/man3/scanf.3 @@ -678,7 +678,7 @@ is interpreted as a specifier for floating-point numbers (see above). .PP Support for the .B m -modifier was added to glibc starting with version 2.7, +modifier was added to glibc 2.7, and new programs should use that modifier instead of .BR a . .PP diff --git a/man3/seekdir.3 b/man3/seekdir.3 index 4f9121536e..ee21334415 100644 --- a/man3/seekdir.3 +++ b/man3/seekdir.3 @@ -30,7 +30,7 @@ Feature Test Macro Requirements for glibc (see .BR seekdir (): .nf _XOPEN_SOURCE - || /* Glibc since 2.19: */ _DEFAULT_SOURCE + || /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _BSD_SOURCE || _SVID_SOURCE .fi .SH DESCRIPTION @@ -68,7 +68,7 @@ T} Thread safety MT-Safe .SH STANDARDS POSIX.1-2001, POSIX.1-2008, 4.3BSD. .SH NOTES -In glibc up to version 2.1.1, the type of the +Up to glibc 2.1.1, the type of the .I loc argument was .IR off_t . diff --git a/man3/setenv.3 b/man3/setenv.3 index 7a377cdf8a..2b849cfa5b 100644 --- a/man3/setenv.3 +++ b/man3/setenv.3 @@ -141,7 +141,7 @@ contains an \(aq=\(aq character, then .BR setenv () should fail with the error .BR EINVAL ; -however, versions of glibc before 2.3.4 allowed an \(aq=\(aq sign in +however, versions of glibc before glibc 2.3.4 allowed an \(aq=\(aq sign in .IR name . .SH SEE ALSO .BR clearenv (3), diff --git a/man3/setjmp.3 b/man3/setjmp.3 index 6aa09913f0..d25541cd8c 100644 --- a/man3/setjmp.3 +++ b/man3/setjmp.3 @@ -160,7 +160,7 @@ is a function that will not. The behavior under Linux depends on the glibc version and the setting of feature test macros. -On Linux with glibc versions before 2.19, +Before glibc 2.19, .BR setjmp () follows the System V behavior by default, but the BSD behavior is provided if the diff --git a/man3/setlogmask.3 b/man3/setlogmask.3 index 546a04885d..ac8379b5dc 100644 --- a/man3/setlogmask.3 +++ b/man3/setlogmask.3 @@ -54,7 +54,7 @@ This function returns the previous log priority mask. .SH ERRORS None. .\" .SH NOTES -.\" The glibc logmask handling was broken in versions before glibc 2.1.1. +.\" The glibc logmask handling was broken before glibc 2.1.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/sigset.3 b/man3/sigset.3 index 83679c1368..46d15ee93b 100644 --- a/man3/sigset.3 +++ b/man3/sigset.3 @@ -187,7 +187,7 @@ and .BR sigsuspend (2) instead. .SH NOTES -These functions appeared in glibc version 2.1. +These functions appeared in glibc 2.1. .PP The .I sighandler_t @@ -229,7 +229,7 @@ See .BR sigpause (3) for details. .SH BUGS -In versions of glibc before 2.2, +Before glibc 2.2, .BR sigset () did not unblock .I sig @@ -238,7 +238,7 @@ if was specified as a value other than .BR SIG_HOLD . .PP -In versions of glibc before 2.5, +Before glibc 2.5, .BR sigset () does not correctly return the previous disposition of the signal in two cases. diff --git a/man3/sigvec.3 b/man3/sigvec.3 index 39939e30bb..abcae823a1 100644 --- a/man3/sigvec.3 +++ b/man3/sigvec.3 @@ -208,7 +208,7 @@ See the ERRORS under and .BR sigprocmask (2). .SH VERSIONS -Starting with version 2.21, the GNU C library no longer exports the +Starting with glibc 2.21, the GNU C library no longer exports the .BR sigvec () function as part of the ABI. (To ensure backward compatibility, diff --git a/man3/sin.3 b/man3/sin.3 index e517376280..1eaf7d7e93 100644 --- a/man3/sin.3 +++ b/man3/sin.3 @@ -105,7 +105,7 @@ The variant returning also conforms to SVr4, 4.3BSD, C89. .SH BUGS -Before version 2.10, the glibc implementation did not set +Before glibc 2.10, the glibc implementation did not set .\" http://sources.redhat.com/bugzilla/show_bug.cgi?id=6781 .I errno to diff --git a/man3/sincos.3 b/man3/sincos.3 index 518ab03c36..b5a0cabc82 100644 --- a/man3/sincos.3 +++ b/man3/sincos.3 @@ -67,7 +67,7 @@ An invalid floating-point exception .RB ( FE_INVALID ) is raised. .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). @@ -102,7 +102,7 @@ cc \-O \-lm \-fno\-builtin prog.c .EE .in .SH BUGS -Before version 2.22, the glibc implementation did not set +Before glibc 2.22, the glibc implementation did not set .\" https://www.sourceware.org/bugzilla/show_bug.cgi?id=15467 .I errno to diff --git a/man3/sockatmark.3 b/man3/sockatmark.3 index c6b8fd5c0c..0f2470b3ff 100644 --- a/man3/sockatmark.3 +++ b/man3/sockatmark.3 @@ -54,7 +54,7 @@ is not a file descriptor to which can be applied. .SH VERSIONS .BR sockatmark () -was added to glibc in version 2.2.4. +was added in glibc 2.2.4. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/statvfs.3 b/man3/statvfs.3 index a1790b2ac1..2d7ec43aa2 100644 --- a/man3/statvfs.3 +++ b/man3/statvfs.3 @@ -209,7 +209,7 @@ and .BR fstatfs (2) to support this library call. .PP -In glibc versions before 2.13, +Before glibc 2.13, .\" glibc commit 3cdaa6adb113a088fdfb87aa6d7747557eccc58d .BR statvfs () populated the bits of the @@ -220,7 +220,7 @@ However, starting with Linux 2.6.36, the underlying .BR statfs (2) system call provides the necessary information via the .I f_flags -field, and since glibc version 2.13, the +field, and since glibc 2.13, the .BR statvfs () function will use information from that field rather than scanning .IR /proc/mounts . diff --git a/man3/stpncpy.3 b/man3/stpncpy.3 index 94f4ebb044..41fd7aa41c 100644 --- a/man3/stpncpy.3 +++ b/man3/stpncpy.3 @@ -102,7 +102,7 @@ T} Thread safety MT-Safe .SH STANDARDS This function was added to POSIX.1-2008. Before that, it was a GNU extension. -It first appeared in version 1.07 of the GNU C library in 1993. +It first appeared in glibc 1.07 in 1993. .SH SEE ALSO .BR strncpy (3), .BR wcpncpy (3) diff --git a/man3/strchr.3 b/man3/strchr.3 index c099eebfd0..9ac84ee653 100644 --- a/man3/strchr.3 +++ b/man3/strchr.3 @@ -83,7 +83,7 @@ or a pointer to the null byte at the end of if the character is not found. .SH VERSIONS .BR strchrnul () -first appeared in glibc in version 2.1.1. +was added in glibc 2.1.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/strerror.3 b/man3/strerror.3 index 862e153ee0..65ecdf2097 100644 --- a/man3/strerror.3 +++ b/man3/strerror.3 @@ -190,7 +190,7 @@ On error, a (positive) error number is returned (since glibc 2.13), or \-1 is returned and .I errno -is set to indicate the error (glibc versions before 2.13). +is set to indicate the error (before glibc 2.13). .PP POSIX.1-2001 and POSIX.1-2008 require that a successful call to .BR strerror () diff --git a/man3/strfromd.3 b/man3/strfromd.3 index 4b13a27f1c..518551bbbf 100644 --- a/man3/strfromd.3 +++ b/man3/strfromd.3 @@ -153,7 +153,7 @@ The .BR strfromf (), and .BR strfroml () -functions are available in glibc since version 2.25. +functions are available since glibc 2.25. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7) diff --git a/man3/strsignal.3 b/man3/strsignal.3 index f66ae86cd5..70828c5a20 100644 --- a/man3/strsignal.3 +++ b/man3/strsignal.3 @@ -39,7 +39,7 @@ Feature Test Macro Requirements for glibc (see .PP .BR strsignal (): .nf - From glibc 2.10 to 2.31: + From glibc 2.10 to glibc 2.31: _POSIX_C_SOURCE >= 200809L Before glibc 2.10: _GNU_SOURCE @@ -114,7 +114,7 @@ and .BR sigabbrev_np () first appeared in glibc 2.32. .PP -Starting with version 2.32, +Starting with glibc 2.32, .\" glibc commit b1ccfc061feee9ce616444ded8e1cd5acf9fa97f the .I sys_siglist diff --git a/man3/system.3 b/man3/system.3 index 463716f48b..eaa708e047 100644 --- a/man3/system.3 +++ b/man3/system.3 @@ -178,7 +178,7 @@ are called during the execution of .BR system (). In the glibc implementation, such handlers are not called. .PP -In versions of glibc before 2.1.3, the check for the availability of +Before glibc 2.1.3, the check for the availability of .I /bin/sh was not actually performed if .I command diff --git a/man3/tan.3 b/man3/tan.3 index 2b558dec52..dc11a13bc5 100644 --- a/man3/tan.3 +++ b/man3/tan.3 @@ -130,7 +130,7 @@ The variant returning also conforms to SVr4, 4.3BSD, C89. .SH BUGS -Before version 2.10, the glibc implementation did not set +Before glibc 2.10, the glibc implementation did not set .\" http://sourceware.org/bugzilla/show_bug.cgi?id=6782 .I errno to diff --git a/man3/tcgetsid.3 b/man3/tcgetsid.3 index f78e6ec7da..544d9bdcbf 100644 --- a/man3/tcgetsid.3 +++ b/man3/tcgetsid.3 @@ -45,7 +45,7 @@ it has one but it is not described by .IR fd . .SH VERSIONS .BR tcgetsid () -is provided in glibc since version 2.1. +is provided since glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/telldir.3 b/man3/telldir.3 index f953638ffd..baf71f4cf9 100644 --- a/man3/telldir.3 +++ b/man3/telldir.3 @@ -28,7 +28,7 @@ Feature Test Macro Requirements for glibc (see .BR telldir (): .nf _XOPEN_SOURCE - || /* Glibc since 2.19: */ _DEFAULT_SOURCE + || /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _BSD_SOURCE || _SVID_SOURCE .fi .SH DESCRIPTION @@ -68,7 +68,7 @@ T} Thread safety MT-Safe .SH STANDARDS POSIX.1-2001, POSIX.1-2008, 4.3BSD. .SH NOTES -In glibc up to version 2.1.1, the return type of +Up to glibc 2.1.1, the return type of .BR telldir () was .IR off_t . diff --git a/man3/termios.3 b/man3/termios.3 index 4e49ac4e3f..ca90d28fb3 100644 --- a/man3/termios.3 +++ b/man3/termios.3 @@ -1178,7 +1178,7 @@ behaves like .SH BUGS .\" kernel 77e5bff1640432f28794a00800955e646dcd7455 .\" glibc 573963e32ffac46d9891970ddebde2ac3212c5c0 -On the Alpha architecture before Linux 4.16 (and glibc before 2.28), the +On the Alpha architecture before Linux 4.16 (and glibc before glibc 2.28), the .B XTABS value was different from .B TAB3 diff --git a/man3/tgamma.3 b/man3/tgamma.3 index 1374bd0692..b2905b3cb7 100644 --- a/man3/tgamma.3 +++ b/man3/tgamma.3 @@ -156,7 +156,7 @@ is set to .\" glibc (as at 2.8) also supports an inexact .\" exception for various cases. .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). @@ -186,7 +186,7 @@ that returns something else (see .BR gamma (3) for details). .SH BUGS -Before version 2.18, the glibc implementation of these functions did not set +Before glibc 2.18, the glibc implementation of these functions did not set .\" http://sources.redhat.com/bugzilla/show_bug.cgi?id=6809 .I errno to diff --git a/man3/toascii.3 b/man3/toascii.3 index 01ac6799aa..4b9f2a4770 100644 --- a/man3/toascii.3 +++ b/man3/toascii.3 @@ -25,7 +25,7 @@ Feature Test Macro Requirements for glibc (see .BR toascii (): .nf _XOPEN_SOURCE - || /* Glibc since 2.19: */ _DEFAULT_SOURCE + || /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _SVID_SOURCE || _BSD_SOURCE .fi .SH DESCRIPTION diff --git a/man3/trunc.3 b/man3/trunc.3 index 7a385671f8..7cbbfbb091 100644 --- a/man3/trunc.3 +++ b/man3/trunc.3 @@ -44,7 +44,7 @@ itself is returned. .SH ERRORS No errors occur. .SH VERSIONS -These functions first appeared in glibc in version 2.1. +These functions were added in glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/tsearch.3 b/man3/tsearch.3 index 2012a55ece..bb6d26bf68 100644 --- a/man3/tsearch.3 +++ b/man3/tsearch.3 @@ -193,7 +193,7 @@ return NULL if was NULL on entry. .SH VERSIONS .BR twalk_r () -is available in glibc since version 2.30. +is available since glibc 2.30. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/ttyslot.3 b/man3/ttyslot.3 index 0d2afd1578..1294562194 100644 --- a/man3/ttyslot.3 +++ b/man3/ttyslot.3 @@ -27,7 +27,7 @@ Feature Test Macro Requirements for glibc (see .nf Since glibc 2.24: _DEFAULT_SOURCE - From glibc 2.20 to 2.23: + From glibc 2.20 to glibc 2.23: _DEFAULT_SOURCE || (_XOPEN_SOURCE && _XOPEN_SOURCE < 500) Glibc 2.19 and earlier: _BSD_SOURCE || (_XOPEN_SOURCE && _XOPEN_SOURCE < 500) diff --git a/man3/tzset.3 b/man3/tzset.3 index a4930b3ff2..145e5dc14b 100644 --- a/man3/tzset.3 +++ b/man3/tzset.3 @@ -46,7 +46,7 @@ Feature Test Macro Requirements for glibc (see .IR daylight : .nf _XOPEN_SOURCE - || /* Glibc since 2.19: */ _DEFAULT_SOURCE + || /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _SVID_SOURCE .fi .SH DESCRIPTION diff --git a/man3/ualarm.3 b/man3/ualarm.3 index 3ce5ae5c2f..f4bb22923b 100644 --- a/man3/ualarm.3 +++ b/man3/ualarm.3 @@ -24,7 +24,7 @@ Feature Test Macro Requirements for glibc (see .nf Since glibc 2.12: (_XOPEN_SOURCE >= 500) && ! (_POSIX_C_SOURCE >= 200809L) - || /* Glibc since 2.19: */ _DEFAULT_SOURCE + || /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _BSD_SOURCE Before glibc 2.12: _BSD_SOURCE || _XOPEN_SOURCE >= 500 @@ -102,7 +102,7 @@ The type .I useconds_t is an unsigned integer type capable of holding integers in the range [0,1000000]. -On the original BSD implementation, and in glibc before version 2.1, +On the original BSD implementation, and in glibc before glibc 2.1, the arguments to .BR ualarm () were instead typed as diff --git a/man3/unlocked_stdio.3 b/man3/unlocked_stdio.3 index a9b250149c..89cf67ffb0 100644 --- a/man3/unlocked_stdio.3 +++ b/man3/unlocked_stdio.3 @@ -66,7 +66,7 @@ Feature Test Macro Requirements for glibc (see .BR putc_unlocked (), .BR putchar_unlocked (): .nf - /* Since glibc 2.24: */ _POSIX_C_SOURCE >= 199309L + /* Glibc >= 2.24: */ _POSIX_C_SOURCE >= 199309L || /* Glibc <= 2.23: */ _POSIX_C_SOURCE || /* Glibc <= 2.19: */ _SVID_SOURCE || _BSD_SOURCE .fi @@ -81,7 +81,7 @@ Feature Test Macro Requirements for glibc (see .BR fread_unlocked (), .BR fwrite_unlocked (): .nf - /* Glibc since 2.19: */ _DEFAULT_SOURCE + /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _SVID_SOURCE || _BSD_SOURCE .fi .PP diff --git a/man3/unlockpt.3 b/man3/unlockpt.3 index 5fea52e3f1..afba895b7c 100644 --- a/man3/unlockpt.3 +++ b/man3/unlockpt.3 @@ -58,7 +58,7 @@ The argument is not associated with a master pseudoterminal. .SH VERSIONS .BR unlockpt () -is provided in glibc since version 2.1. +is provided since glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/updwtmp.3 b/man3/updwtmp.3 index e7690a23f4..054884b910 100644 --- a/man3/updwtmp.3 +++ b/man3/updwtmp.3 @@ -62,7 +62,7 @@ Present on Solaris, NetBSD, and perhaps other systems. .SH NOTES For consistency with the other "utmpx" functions (see .BR getutxent (3)), -glibc provides (since version 2.1): +glibc provides (since glibc 2.1): .PP .in +4n .EX diff --git a/man3/uselocale.3 b/man3/uselocale.3 index 3238954ffd..a813fdc0a2 100644 --- a/man3/uselocale.3 +++ b/man3/uselocale.3 @@ -73,7 +73,7 @@ does not refer to a valid locale object. .SH VERSIONS The .BR uselocale () -function first appeared in version 2.3 of the GNU C library. +function first appeared in glibc 2.3. .SH STANDARDS POSIX.1-2008. .SH NOTES diff --git a/man3/usleep.3 b/man3/usleep.3 index ae8c7af439..87d16c7b9f 100644 --- a/man3/usleep.3 +++ b/man3/usleep.3 @@ -32,7 +32,7 @@ Feature Test Macro Requirements for glibc (see .nf Since glibc 2.12: (_XOPEN_SOURCE >= 500) && ! (_POSIX_C_SOURCE >= 200809L) - || /* Glibc since 2.19: */ _DEFAULT_SOURCE + || /* Glibc >= 2.19: */ _DEFAULT_SOURCE || /* Glibc <= 2.19: */ _BSD_SOURCE Before glibc 2.12: _BSD_SOURCE || _XOPEN_SOURCE >= 500 @@ -88,7 +88,7 @@ POSIX.1-2008 removes the specification of .BR usleep (). .PP On the original BSD implementation, -and in glibc before version 2.2.2, the return type of this function is +and before glibc 2.2.2, the return type of this function is .IR void . The POSIX version returns .IR int , diff --git a/man3/wcscasecmp.3 b/man3/wcscasecmp.3 index 4b1bfa445d..40d9a3d29d 100644 --- a/man3/wcscasecmp.3 +++ b/man3/wcscasecmp.3 @@ -71,7 +71,7 @@ ignoring case. .SH VERSIONS The .BR wcscasecmp () -function is provided in glibc since version 2.1. +function is provided since glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/wcsncasecmp.3 b/man3/wcsncasecmp.3 index 0b072369a5..06609df988 100644 --- a/man3/wcsncasecmp.3 +++ b/man3/wcsncasecmp.3 @@ -77,7 +77,7 @@ ignoring case. .SH VERSIONS The .BR wcsncasecmp () -function is provided in glibc since version 2.1. +function is provided since glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/wcsnlen.3 b/man3/wcsnlen.3 index c6e5d7cdcf..4aef4d5606 100644 --- a/man3/wcsnlen.3 +++ b/man3/wcsnlen.3 @@ -70,7 +70,7 @@ wide characters pointed to by .SH VERSIONS The .BR wcsnlen () -function is provided in glibc since version 2.1. +function is provided since glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/wcwidth.3 b/man3/wcwidth.3 index 0aa6c5cd5b..931ae30372 100644 --- a/man3/wcwidth.3 +++ b/man3/wcwidth.3 @@ -60,7 +60,7 @@ T} Thread safety MT-Safe locale .SH STANDARDS POSIX.1-2001, POSIX.1-2008. .PP -Note that glibc before 2.2.5 used the prototype +Note that before glibc 2.2.5, glibc used the prototype .PP .nf .BI "int wcwidth(wint_t " c ); diff --git a/man3/wordexp.3 b/man3/wordexp.3 index 4eb4c4143c..7893ddcded 100644 --- a/man3/wordexp.3 +++ b/man3/wordexp.3 @@ -174,7 +174,7 @@ unmatched quotes. .BR wordexp () and .BR wordfree () -are provided in glibc since version 2.1. +are provided since glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/xcrypt.3 b/man3/xcrypt.3 index 00a7b72b50..adf43e19c6 100644 --- a/man3/xcrypt.3 +++ b/man3/xcrypt.3 @@ -71,7 +71,7 @@ and .BR xdecrypt () return 1 on success and 0 on error. .SH VERSIONS -These functions are available in glibc since version 2.1. +These functions are available since glibc 2.1. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). diff --git a/man3/y0.3 b/man3/y0.3 index ddcd44229f..d7a90377e6 100644 --- a/man3/y0.3 +++ b/man3/y0.3 @@ -247,9 +247,9 @@ did not set .I errno for "range error: result underflow". .PP -In glibc version 2.3.2 and earlier, +In glibc 2.3.2 and earlier, .\" Actually, 2.3.2 is the earliest test result I have; so yet -.\" to confirm if this error occurs only in 2.3.2. +.\" to confirm if this error occurs only in glibc 2.3.2. these functions do not raise an invalid floating-point exception .RB ( FE_INVALID ) when a domain error occurs. diff --git a/man3type/stat.3type b/man3type/stat.3type index 23e45169dd..2a635a667b 100644 --- a/man3type/stat.3type +++ b/man3type/stat.3type @@ -135,7 +135,7 @@ via names of the form .IR st_atim.tv_nsec , if suitable test macros are defined. Nanosecond timestamps were standardized in POSIX.1-2008, -and, starting with version 2.12, +and, starting with glibc 2.12, glibc exposes the nanosecond component names if .B _POSIX_C_SOURCE is defined with the value 200809L or greater, or diff --git a/man4/cciss.4 b/man4/cciss.4 index cfc57efc01..a0ee99c1ad 100644 --- a/man4/cciss.4 +++ b/man4/cciss.4 @@ -15,7 +15,7 @@ modprobe cciss [ cciss_allow_hpsa=1 ] .SH DESCRIPTION .\" commit 253d2464df446456c0bba5ed4137a7be0b278aa8 .BR Note : -This obsolete driver was removed from the kernel in version 4.14, +This obsolete driver was removed in Linux 4.14, as it is superseded by the .BR hpsa (4) driver in newer kernels. diff --git a/man4/console_codes.4 b/man4/console_codes.4 index 72e9787572..880df050bb 100644 --- a/man4/console_codes.4 +++ b/man4/console_codes.4 @@ -774,10 +774,10 @@ scripts which exercise other features. ESC 8 (DECRC) is not able to restore the character set changed with ESC %. .SH BUGS -In 2.0.23, CSI is broken, and NUL is not ignored inside +In Linux 2.0.23, CSI is broken, and NUL is not ignored inside escape sequences. .PP -Some older kernel versions (after 2.0) interpret 8-bit control +Some older kernel versions (after Linux 2.0) interpret 8-bit control sequences. These "C1 controls" use codes between 128 and 159 to replace ESC [, ESC ] and similar two-byte control sequence initiators. diff --git a/man4/lirc.4 b/man4/lirc.4 index 30797a679f..68f665fc7c 100644 --- a/man4/lirc.4 +++ b/man4/lirc.4 @@ -369,7 +369,7 @@ The driver supports setting the receive carrier frequency using .BR LIRC_SET_REC_CARRIER . Any .B lirc -device since the drivers were merged in kernel release 2.6.36 +device since the drivers were merged in Linux 2.6.36 must have .B LIRC_CAN_SET_REC_CARRIER_RANGE set if @@ -410,7 +410,7 @@ or .SH BUGS Using these devices requires the kernel source header file .IR lirc.h . -This file is not available before kernel release 4.6. +This file is not available before Linux 4.6. Users of older kernels could use the file bundled in .UR http://www.lirc.org .UE . diff --git a/man4/random.4 b/man4/random.4 index 12c859248d..38396b6679 100644 --- a/man4/random.4 +++ b/man4/random.4 @@ -118,7 +118,7 @@ from .I /dev/random will return at most 512 bytes .\" SEC_XFER_SIZE in drivers/char/random.c -(340 bytes on Linux kernels before version 2.6.12). +(340 bytes before Linux 2.6.12). .PP Writing to \fI/dev/random\fP or \fI/dev/urandom\fP will update the entropy pool with the data written, but this will not result in a @@ -218,7 +218,7 @@ returns the size of the entropy pool in bits (see below). .SS /proc interfaces The files in the directory .I /proc/sys/kernel/random -(present since 2.3.16) provide additional information about the +(present since Linux 2.3.16) provide additional information about the .I /dev/random device: .TP diff --git a/man4/sk98lin.4 b/man4/sk98lin.4 index 6801b9ea1e..481ff6956e 100644 --- a/man4/sk98lin.4 +++ b/man4/sk98lin.4 @@ -44,7 +44,7 @@ sk98lin \- Marvell/SysKonnect Gigabit Ethernet driver v6.21 .ad l .hy 0 .BR Note : -This obsolete driver was removed from the kernel in version 2.6.26. +This obsolete driver was removed in Linux 2.6.26. .PP .B sk98lin is the Gigabit Ethernet driver for diff --git a/man4/st.4 b/man4/st.4 index 68ea2ff400..dc8621e39b 100644 --- a/man4/st.4 +++ b/man4/st.4 @@ -77,7 +77,7 @@ There is no corresponding block device. .PP The driver uses an internal buffer that has to be large enough to hold at least one tape block. -In kernels before 2.1.121, the buffer is +Before Linux 2.1.121, the buffer is allocated as one contiguous block. This limits the block size to the largest contiguous block of memory the kernel allocator can provide. @@ -96,7 +96,7 @@ In addition to this, the driver tries to allocate a larger temporary buffer at run time if necessary. However, run-time allocation of large contiguous blocks of memory may fail and it is advisable not to rely -too much on dynamic buffer allocation with kernels older than 2.1.121 +too much on dynamic buffer allocation before Linux 2.1.121 (this applies also to demand-loading the driver with kerneld or kmod). .PP The driver does not specifically support any tape drive brand or @@ -149,7 +149,7 @@ Device is usually created as a hard or soft link to the default tape device on the system. .PP -Starting from kernel 2.6.2, the driver exports in the sysfs directory +Starting from Linux 2.6.2, the driver exports in the sysfs directory .I /sys/class/scsi_tape the attached devices and some parameters assigned to the devices. .SS Data transfer @@ -177,13 +177,13 @@ byte count, an error is returned. In fixed-block mode the read byte counts can be arbitrary if buffering is enabled, or a multiple of the tape block size if buffering is disabled. -Kernels before 2.1.121 allow writes with +Before Linux 2.1.121 allow writes with arbitrary byte count if buffering is enabled. In all other cases -(kernel before 2.1.121 with buffering disabled or newer kernel) the +(before Linux 2.1.121 with buffering disabled or newer kernel) the write byte count must be a multiple of the tape block size. .PP -In the 2.6 kernel, the driver tries to use direct transfers between the user +In Linux 2.6, the driver tries to use direct transfers between the user buffer and the device. If this is not possible, the driver's internal buffer is used. @@ -271,7 +271,7 @@ Go to the end of the recorded media (for appending files). .TP .B MTERASE Erase tape. -With 2.6 kernel, short erase (mark tape empty) is performed if the +With Linux 2.6, short erase (mark tape empty) is performed if the argument is zero. Otherwise, long erase (erase all) is done. .TP @@ -319,7 +319,7 @@ is positive, it gives the size of partition 1 and partition If .I mt_count is zero, the tape is formatted into one partition. -From kernel version 4.6, +From Linux 4.6, .\" commit 8038e6456a3e6f5c4759e0d73c4f9165b90c93e7 a negative .I mt_count @@ -403,7 +403,7 @@ Set various drive and driver options according to bits encoded in .IR mt_count . These consist of the drive's buffering mode, a set of Boolean driver options, the buffer write threshold, defaults for the block size and -density, and timeouts (only in kernels 2.1 and later). +density, and timeouts (only since Linux 2.1). A single operation can affect only one item in the list below (the Booleans counted as one item.) .IP @@ -563,7 +563,7 @@ to instruct the driver not to use the command. The end result is that, with read-ahead and fixed-block mode, the tape may not be correctly positioned within a file when the device is closed. -With 2.6 kernel, the +With Linux 2.6, the default is true for drives supporting SCSI-3. .TP .BR MT_ST_NO_BLKLIMS " (Default: false)" @@ -629,7 +629,7 @@ and the default density code can be set with The values for the parameters are or'ed with the operation code. .PP -With kernels 2.1.x and later, the timeout values can be set with the +With Linux 2.1.x and later, the timeout values can be set with the subcommand .B MT_ST_SET_TIMEOUT ORed with the timeout in seconds. @@ -646,7 +646,7 @@ practical values for a specific drive. The timeouts set for one device apply for all devices linked to the same drive. .PP -Starting from kernels 2.4.19 and 2.5.43, the driver supports a status +Starting from Linux 2.4.19 and Linux 2.5.43, the driver supports a status bit which indicates whether the drive requests cleaning. The method used by the drive to return cleaning information is set using the @@ -771,7 +771,7 @@ the drive is set not to buffer data. .TP \fBGMT_CLN\fP(\fIx\fP) The drive has requested cleaning. -Implemented in kernels since 2.4.19 and 2.5.43. +Implemented since Linux 2.4.19 and Linux 2.5.43. .RE .TP \fImt_erreg\fP @@ -848,7 +848,7 @@ The requested operation could not be completed. The byte count in .BR read (2) is smaller than the next physical block on the tape. -(Before 2.2.18 and 2.4.0 the extra bytes have been +(Before Linux 2.2.18 and Linux 2.4.0 the extra bytes have been .\" Precisely: Linux 2.6.0-test6 silently ignored.) .TP diff --git a/man4/vcs.4 b/man4/vcs.4 index 9bda05d746..12ad4b500c 100644 --- a/man4/vcs.4 +++ b/man4/vcs.4 @@ -80,7 +80,7 @@ requests are supported. .\" .SH AUTHOR .\" Andries Brouwer .SH VERSIONS -Introduced with version 1.1.92 of the Linux kernel. +Introduced with Linux 1.1.92. .SH EXAMPLES You may do a screendump on vt3 by switching to vt1 and typing .PP diff --git a/man4/wavelan.4 b/man4/wavelan.4 index 45ac95f464..e5c5c7d9cd 100644 --- a/man4/wavelan.4 +++ b/man4/wavelan.4 @@ -17,7 +17,7 @@ wavelan \- AT&T GIS WaveLAN ISA device driver .fi .SH DESCRIPTION .I This driver is obsolete: -it was removed from the kernel in version 2.6.35. +it was removed in Linux 2.6.35. .PP .B wavelan is the low-level device driver for the NCR / AT&T / Lucent diff --git a/man5/acct.5 b/man5/acct.5 index e62c6d15df..0665dd3617 100644 --- a/man5/acct.5 +++ b/man5/acct.5 @@ -87,7 +87,7 @@ fields measure time in "clock ticks"; divide these values by .I sysconf(_SC_CLK_TCK) to convert them to seconds. .SS Version 3 accounting file format -Since kernel 2.6.8, +Since Linux 2.6.8, an optional alternative version of the accounting file can be produced if the .B CONFIG_BSD_PROCESS_ACCT_V3 @@ -131,7 +131,7 @@ struct acct_v3 { .SH VERSIONS The .I acct_v3 -structure is defined in glibc since version 2.6. +structure is defined since glibc 2.6. .SH STANDARDS Process accounting originated on BSD. Although it is present on most systems, it is not standardized, @@ -140,7 +140,7 @@ and the details vary somewhat between systems. Records in the accounting file are ordered by termination time of the process. .PP -In kernels up to and including 2.6.9, +Up to and including Linux 2.6.9, a separate accounting record is written for each thread created using the NPTL threading library; since Linux 2.6.10, diff --git a/man5/core.5 b/man5/core.5 index 92aa18fe7d..be9753250e 100644 --- a/man5/core.5 +++ b/man5/core.5 @@ -217,7 +217,7 @@ part of the core filename. The template may include \(aq/\(aq characters, which are interpreted as delimiters for directory names. The maximum size of the resulting core filename is 128 bytes (64 bytes -in kernels before 2.6.19). +before Linux 2.6.19). The default value in this file is "core". For backward compatibility, if .I /proc/sys/kernel/core_pattern @@ -237,7 +237,7 @@ its current working directory (found via and its root directory (see .BR chroot (2)). .PP -Since version 2.4, Linux has also provided +Since Linux 2.4, Linux has also provided a more primitive method of controlling the name of the core dump file. If the @@ -255,14 +255,14 @@ if is set to 2 ("suidsafe"), the pattern must be either an absolute pathname (starting with a leading \(aq/\(aq character) or a pipe, as defined below. .SS Piping core dumps to a program -Since kernel 2.6.19, Linux supports an alternate syntax for the +Since Linux 2.6.19, Linux supports an alternate syntax for the .I /proc/sys/kernel/core_pattern file. If the first character of this file is a pipe symbol (\fB|\fP), then the remainder of the line is interpreted as the command-line for a user-space program (or script) that is to be executed. .PP -Since kernel 5.3.0, +Since Linux 5.3.0, .\" commit 315c69261dd3fa12dbc830d4fa00d1fad98d3b03 the pipe template is split on spaces into an argument list .I before @@ -370,7 +370,7 @@ program is not guaranteed access to The default value for this file is 0. .\" .SS Controlling which mappings are written to the core dump -Since kernel 2.6.23, the Linux-specific +Since Linux 2.6.23, the Linux-specific .IR /proc/ pid /coredump_filter file can be used to control which memory segments are written to the core dump file in the event that a core dump is performed for the diff --git a/man5/filesystems.5 b/man5/filesystems.5 index 1596602086..1828cf0522 100644 --- a/man5/filesystems.5 +++ b/man5/filesystems.5 @@ -55,7 +55,7 @@ filesystem. It has been completely superseded by the second version of the extended filesystem .RB ( ext2 ) -and has been removed from the kernel (in 2.1.21). +and has been removed from the kernel (in Linux 2.1.21). .TP .B ext2 is a disk filesystem that was used by Linux for fixed disks @@ -117,7 +117,7 @@ filesystem support under Linux. .TP .B JFS is a journaling filesystem, developed by IBM, -that was integrated into Linux in kernel 2.4.24. +that was integrated into Linux 2.4.24. .TP .B minix is the filesystem used in the Minix operating system, the first to run @@ -135,7 +135,7 @@ optional period and 3 character extension. .B ncpfs is a network filesystem that supports the NCP protocol, used by Novell NetWare. -It was removed from the kernel in 4.17. +It was removed from the kernel in Linux 4.17. .IP To use .BR ncpfs , @@ -160,7 +160,7 @@ See .TP .B Reiserfs is a journaling filesystem, designed by Hans Reiser, -that was integrated into Linux in kernel 2.4.1. +that was integrated into Linux 2.4.1. .TP .B smb is a network filesystem that supports the SMB protocol, used by @@ -194,7 +194,7 @@ adds the capability to use long filenames under the MSDOS filesystem. .TP .B XFS is a journaling filesystem, developed by SGI, -that was integrated into Linux in kernel 2.4.20. +that was integrated into Linux 2.4.20. .TP .B xiafs was designed and implemented to be a stable, safe filesystem by @@ -204,7 +204,7 @@ requested features without undue complexity. The .B xiafs filesystem is no longer actively developed or maintained. -It was removed from the kernel in 2.1.21. +It was removed from the kernel in Linux 2.1.21. .SH SEE ALSO .BR fuse (4), .BR btrfs (5), diff --git a/man5/gai.conf.5 b/man5/gai.conf.5 index 7ecc823a4c..4c259b818a 100644 --- a/man5/gai.conf.5 +++ b/man5/gai.conf.5 @@ -62,7 +62,7 @@ Changing these defaults should hardly ever be necessary. The .I gai.conf .\" Added in 2006 -file is supported by glibc since version 2.5. +file is supported since glibc 2.5. .SH EXAMPLES The default table according to RFC\ 3484 would be specified with the following configuration file: diff --git a/man5/locale.5 b/man5/locale.5 index be54d86595..a391590a09 100644 --- a/man5/locale.5 +++ b/man5/locale.5 @@ -71,7 +71,7 @@ The following category sections are defined by POSIX: .IP \(bu .B LC_TIME .PP -In addition, since version 2.2, +In addition, since glibc 2.2, the GNU C library supports the following nonstandard categories: .IP \(bu 3 .B LC_ADDRESS diff --git a/man5/proc.5 b/man5/proc.5 index 1217cea897..38adcfaab9 100644 --- a/man5/proc.5 +++ b/man5/proc.5 @@ -16,7 +16,7 @@ .\" Modified 2002-07-22, 2003-05-27, 2004-04-06, 2004-05-25 .\" by Michael Kerrisk .\" 2004-11-17, mtk -- updated notes on /proc/loadavg -.\" 2004-12-01, mtk, rtsig-max and rtsig-nr went away in 2.6.8 +.\" 2004-12-01, mtk, rtsig-max and rtsig-nr went away in Linux 2.6.8 .\" 2004-12-14, mtk, updated 'statm', and fixed error in order of list .\" 2005-05-12, mtk, updated 'stat' .\" 2005-07-13, mtk, added /proc/sys/fs/mqueue/* @@ -375,7 +375,7 @@ For further information, see the kernel source file (or file .\" commit b68101a1e8f0263dbc7b8375d2a7c57c6216fb76 .I Documentation/security/keys.txt -on Linux between 3.0 and 4.13, or +between Linux 3.0 and Linux 4.13, or .\" commit d410fa4ef99112386de5f218dd7df7b4fca910b4 .I Documentation/keys.txt before Linux 3.0). @@ -396,7 +396,7 @@ all subsequently created sockets will be labeled with this context. See .BR sched (7). .TP -.IR /proc/ pid /auxv " (since 2.6.0)" +.IR /proc/ pid /auxv " (since Linux 2.6.0)" .\" Precisely: Linux 2.6.0-test7 This contains the contents of the ELF interpreter information passed to the process at exec time. @@ -432,7 +432,7 @@ The following values may be written to the file: .\" Internally: CLEAR_REFS_ALL Reset the PG_Referenced and ACCESSED/YOUNG bits for all the pages associated with the process. -(Before kernel 2.6.32, writing any nonzero value to this file +(Before Linux 2.6.32, writing any nonzero value to this file had this effect.) .TP 2 (since Linux 2.6.32) @@ -493,7 +493,7 @@ kernel configuration option is enabled. .IR /proc/ pid /cmdline This read-only file holds the complete command line for the process, unless the process is a zombie. -.\" In 2.3.26, this also used to be true if the process was swapped out. +.\" In Linux 2.3.26, this also used to be true if the process was swapped out. In the latter case, there is nothing in this file: that is, a read on this file will return 0 characters. The command-line arguments appear in this file as a set of @@ -1110,7 +1110,7 @@ on this file descriptor would return.) See .BR user_namespaces (7). .TP -.IR /proc/ pid /io " (since kernel 2.6.20)" +.IR /proc/ pid /io " (since Linux 2.6.20)" .\" commit 7c3ab7381e79dfc7db14a67c6f4f3285664e1ec2 This file contains I/O statistics for the process, for example: .IP @@ -1206,10 +1206,10 @@ Since Linux 2.6.36, .\" commit 3036e7b490bf7878c6dae952eec5fb87b1106589 this file is readable by all users on the system. .\" FIXME Describe /proc/[pid]/loginuid -.\" Added in 2.6.11; updating requires CAP_AUDIT_CONTROL +.\" Added in Linux 2.6.11; updating requires CAP_AUDIT_CONTROL .\" CONFIG_AUDITSYSCALL .TP -.IR /proc/ pid /map_files/ " (since kernel 3.3)" +.IR /proc/ pid /map_files/ " (since Linux 3.3)" .\" commit 640708a2cff7f81e246243b0073c66e6ece7e53e This subdirectory contains entries corresponding to memory-mapped files (see @@ -1253,7 +1253,7 @@ Permission to access this file is governed by a ptrace access mode check; see .BR ptrace (2). .IP -Until kernel version 4.3, +Until Linux 4.3, .\" commit bdb4d100afe9818aebd1d98ced575c5ef143456c this directory appeared only if the .B CONFIG_CHECKPOINT_RESTORE @@ -1352,7 +1352,7 @@ There are additional helpful pseudo-paths: .I [stack] The initial process's (also known as the main thread's) stack. .TP -.IR [stack: tid ] " (from Linux 3.4 to 4.4)" +.IR [stack: tid ] " (from Linux 3.4 to Linux 4.4)" .\" commit b76437579d1344b612cf1851ae610c636cec7db0 (added) .\" commit 65376df582174ffcec9e6471bf5b0dd79ba05e4a (removed) A thread's stack (where the @@ -1530,7 +1530,7 @@ process's mount namespace (see The format of this file is documented in .BR fstab (5). .IP -Since kernel version 2.6.15, this file is pollable: +Since Linux 2.6.15, this file is pollable: after opening the file for reading, a change in this file (i.e., a filesystem mount or unmount) causes .BR select (2) @@ -1624,8 +1624,8 @@ Since Linux 2.6.36, use of this file is deprecated in favor of .IR /proc/ pid /oom_score_adj . .TP .IR /proc/ pid /oom_score " (since Linux 2.6.11)" -.\" See mm/oom_kill.c::badness() in pre 2.6.36 sources -.\" See mm/oom_kill.c::oom_badness() after 2.6.36 +.\" See mm/oom_kill.c::badness() before Linux 2.6.36 sources +.\" See mm/oom_kill.c::oom_badness() after Linux 2.6.36 .\" commit a63d83f427fbce97a6cea0db2e64b0eb8435cd10 This file displays the current score that the kernel gives to this process for the purpose of selecting a process @@ -1634,8 +1634,8 @@ A higher score means that the process is more likely to be selected by the OOM-killer. The basis for this score is the amount of memory used by the process, with increases (+) or decreases (\-) for factors including: -.\" See mm/oom_kill.c::badness() in pre 2.6.36 sources -.\" See mm/oom_kill.c::oom_badness() after 2.6.36 +.\" See mm/oom_kill.c::badness() before Linux 2.6.36 sources +.\" See mm/oom_kill.c::oom_badness() after Linux 2.6.36 .\" commit a63d83f427fbce97a6cea0db2e64b0eb8435cd10 .RS .IP \(bu 3 @@ -1643,7 +1643,7 @@ whether the process is privileged (\-). .\" More precisely, if it has CAP_SYS_ADMIN or (pre 2.6.36) CAP_SYS_RESOURCE .RE .IP -Before kernel 2.6.36 +Before Linux 2.6.36 the following factors were also used in the calculation of oom_score: .RS .IP \(bu 3 @@ -1669,7 +1669,7 @@ or setting for the process. .TP .IR /proc/ pid /oom_score_adj " (since Linux 2.6.36)" -.\" Text taken from 3.7 Documentation/filesystems/proc.txt +.\" Text taken from Linux 3.7 Documentation/filesystems/proc.txt This file can be used to adjust the badness heuristic used to select which process gets killed in out-of-memory conditions. .IP @@ -1887,7 +1887,7 @@ check; see See .BR user_namespaces (7). .TP -.IR /proc/ pid /seccomp " (Linux 2.6.12 to 2.6.22)" +.IR /proc/ pid /seccomp " (Linux 2.6.12 to Linux 2.6.22)" This file can be used to read and change the process's secure computing (seccomp) mode setting. It contains the value 0 if the process is not in seccomp mode, @@ -1913,10 +1913,10 @@ field in .\" FIXME Describe /proc/[pid]/sessionid .\" commit 1e0bd7550ea9cf474b1ad4c6ff5729a507f75fdc .\" CONFIG_AUDITSYSCALL -.\" Added in 2.6.25; read-only; only readable by real UID +.\" Added in Linux 2.6.25; read-only; only readable by real UID .\" .\" FIXME Describe /proc/[pid]/sched -.\" Added in 2.6.23 +.\" Added in Linux 2.6.23 .\" CONFIG_SCHED_DEBUG, and additional fields if CONFIG_SCHEDSTATS .\" Displays various scheduling parameters .\" This file can be written, to reset stats @@ -1926,7 +1926,7 @@ field in .\" .\" FIXME Describe /proc/[pid]/schedstats and .\" /proc/[pid]/task/[tid]/schedstats -.\" Added in 2.6.9 +.\" Added in Linux 2.6.9 .\" CONFIG_SCHEDSTATS .TP .IR /proc/ pid /setgroups " (since Linux 3.19)" @@ -2245,13 +2245,13 @@ corresponding to the user-visible nice range of \-20 to 19. .IP Before Linux 2.6, this was a scaled value based on the scheduler weighting given to this process. -.\" And back in kernel 1.2 days things were different again. +.\" And back in Linux 1.2 days things were different again. .TP (19) \fInice\fP \ %ld The nice value (see .BR setpriority (2)), a value in the range 19 (low priority) to \-20 (high priority). -.\" Back in kernel 1.2 days things were different. +.\" Back in Linux 1.2 days things were different. .\" .TP .\" \fIcounter\fP %ld .\" The current maximum size in jiffies of the process's next timeslice, @@ -2264,19 +2264,19 @@ a value in the range 19 (low priority) to \-20 (high priority). .TP (20) \fInum_threads\fP \ %ld Number of threads in this process (since Linux 2.6). -Before kernel 2.6, this field was hard coded to 0 as a placeholder +Before Linux 2.6, this field was hard coded to 0 as a placeholder for an earlier removed field. .TP (21) \fIitrealvalue\fP \ %ld The time in jiffies before the next .B SIGALRM is sent to the process due to an interval timer. -Since kernel 2.6.17, this field is no longer maintained, +Since Linux 2.6.17, this field is no longer maintained, and is hard coded as 0. .TP (22) \fIstarttime\fP \ %llu The time the process started after system boot. -In kernels before Linux 2.6, this value was expressed in jiffies. +Before Linux 2.6, this value was expressed in jiffies. Since Linux 2.6, the value is expressed in clock ticks (divide by .IR sysconf(_SC_CLK_TCK) ). .IP @@ -2349,11 +2349,11 @@ The corresponding symbolic name can be found in .IR /proc/ pid /wchan . .TP (36) \fInswap\fP \ %lu -.\" nswap was added in 2.0 +.\" nswap was added in Linux 2.0 Number of pages swapped (not maintained). .TP (37) \fIcnswap\fP \ %lu -.\" cnswap was added in 2.0 +.\" cnswap was added in Linux 2.0 Cumulative \fInswap\fP for child processes (not maintained). .TP (38) \fIexit_signal\fP \ %d \ (since Linux 2.1.22) @@ -3163,7 +3163,7 @@ documentation available under the kernel source directory .\" commit 3b72c814a8e8cd638e1ba0da4dfce501e9dff5af (or .I Documentation/DocBook -before 4.10; +before Linux 4.10; the documentation can be built using a command such as .I make htmldocs in the root directory of the kernel source tree). @@ -3386,7 +3386,7 @@ r l l l. For further details on the meanings of these bits, see the kernel source file .IR Documentation/admin\-guide/mm/pagemap.rst . -Before kernel 2.6.29, +Before Linux 2.6.29, .\" commit ad3bdefe877afb47480418fdb05ecd42842de65e .\" commit e07a4b9217d1e97d2f3a62b6b070efdc61212110 .BR KPF_WRITEBACK , @@ -3491,7 +3491,7 @@ Because OFD locks are not owned by a single process (since multiple processes may have file descriptors that refer to the same open file description), the value \-1 is displayed in this field for OFD locks. -(Before kernel 4.14, +(Before Linux 4.14, .\" commit 9d5b86ac13c573795525ecac6ed2db39ab23e2a8 a bug meant that the PID of the process that initially acquired the lock was displayed instead of the value \-1.) @@ -3600,12 +3600,12 @@ It is more eligible to be reclaimed for other purposes. [To be documented.] .TP .IR Unevictable " %lu (since Linux 2.6.28)" -(From Linux 2.6.28 to 2.6.30, +(From Linux 2.6.28 to Linux 2.6.30, \fBCONFIG_UNEVICTABLE_LRU\fP was required.) [To be documented.] .TP .IR Mlocked " %lu (since Linux 2.6.28)" -(From Linux 2.6.28 to 2.6.30, +(From Linux 2.6.28 to Linux 2.6.30, \fBCONFIG_UNEVICTABLE_LRU\fP was required.) [To be documented.] .TP @@ -3854,7 +3854,7 @@ See also .BR lsmod (8). .TP .I /proc/mounts -Before kernel 2.4.19, this file was a list +Before Linux 2.4.19, this file was a list of all the filesystems currently mounted on the system. With the introduction of per-process mount namespaces in Linux 2.4.19 (see .BR mount_namespaces (7)), @@ -4289,7 +4289,7 @@ spent in various states: .I idle (4) Time spent in the idle task. .\" FIXME . Actually, the following info about the /proc/stat 'cpu' field -.\" does not seem to be quite right (at least in 2.6.12 or 3.6): +.\" does not seem to be quite right (at least in Linux 2.6.12 or Linux 3.6): .\" the idle time in /proc/uptime does not quite match this value This value should be USER_HZ times the second entry in the @@ -4392,7 +4392,7 @@ See also .BR swapon (8). .TP .I /proc/sys -This directory (present since 1.3.57) contains a number of files +This directory (present since Linux 1.3.57) contains a number of files and subdirectories corresponding to kernel variables. These variables can be read and in some cases modified using the \fI/proc\fP filesystem, and the (deprecated) @@ -4478,12 +4478,12 @@ This field is unused in Linux 2.2. is the number of unused dentries. .IP \(bu .I age_limit -.\" looks like this is unused in kernels 2.2 to 2.6 +.\" looks like this is unused in Linux 2.2 to Linux 2.6 is the age in seconds after which dcache entries can be reclaimed when memory is short. .IP \(bu .I want_pages -.\" looks like this is unused in kernels 2.2 to 2.6 +.\" looks like this is unused in Linux 2.2 to Linux 2.6 is nonzero when the kernel has called shrink_dcache_pages() and the dcache isn't pruned yet. .RE @@ -4913,10 +4913,10 @@ That is, suspend accounting if 2% or less space is free; resume it if 4% or more space is free; consider information about amount of free space valid for 30 seconds. .TP -.IR /proc/sys/kernel/auto_msgmni " (Linux 2.6.27 to 3.18)" +.IR /proc/sys/kernel/auto_msgmni " (Linux 2.6.27 to Linux 3.18)" .\" commit 9eefe520c814f6f62c5d36a2ddcd3fb99dfdb30e (introduces feature) .\" commit 0050ee059f7fc86b1df2527aaa14ed5dc72f9973 (rendered redundant) -From Linux 2.6.27 to 3.18, +From Linux 2.6.27 to Linux 3.18, this file was used to control recomputing of the value in .I /proc/sys/kernel/msgmni upon the addition or removal of memory or upon IPC namespace creation/removal. @@ -4942,7 +4942,7 @@ and reads from this file always return the value "0". See .BR capabilities (7). .TP -.IR /proc/sys/kernel/cap\-bound " (from Linux 2.2 to 2.6.24)" +.IR /proc/sys/kernel/cap\-bound " (from Linux 2.2 to Linux 2.6.24)" This file holds the value of the kernel .I "capability bounding set" (expressed as a signed decimal number). @@ -5039,7 +5039,7 @@ The default value in this file is .IR /proc/sys/kernel/htab\-reclaim " (before Linux 2.4.9.2)" (PowerPC only) If this file is set to a nonzero value, the PowerPC htab -.\" removed in commit 1b483a6a7b2998e9c98ad985d7494b9b725bd228, before 2.6.28 +.\" removed in commit 1b483a6a7b2998e9c98ad985d7494b9b725bd228, before Linux 2.6.28 (see kernel file .IR Documentation/powerpc/ppc_htab.txt ) is pruned @@ -5094,7 +5094,7 @@ in Linux 2.6.26 and earlier) option enabled. It is described by the Linux kernel source file .I Documentation/kmod.txt -(present only in kernel 2.4 and earlier). +(present only in Linux 2.4 and earlier). .TP .IR /proc/sys/kernel/modules_disabled " (since Linux 2.6.31)" .\" 3d43321b7015387cfebbe26436d0e9d299162ea1 @@ -5183,7 +5183,7 @@ On 64-bit systems, can be set to any value up to 2^22 .RB ( PID_MAX_LIMIT , approximately 4 million). -.\" Prior to 2.6.10, pid_max could also be raised above 32768 on 32-bit +.\" Prior to Linux 2.6.10, pid_max could also be raised above 32768 on 32-bit .\" platforms, but this broke /proc/[pid] .\" See http://marc.theaimsgroup.com/?l=linux-kernel&m=109513010926152&w=2 .TP @@ -5273,14 +5273,14 @@ Maybe to tell it what to do after rebooting? .TP .I /proc/sys/kernel/rtsig\-max -(Only in kernels up to and including 2.6.7; see +(Up to and including Linux 2.6.7; see .BR setrlimit (2)) This file can be used to tune the maximum number of POSIX real-time (queued) signals that can be outstanding in the system. .TP .I /proc/sys/kernel/rtsig\-nr -(Only in kernels up to and including 2.6.7.) +(Up to and including Linux 2.6.7.) This file shows the number of POSIX real-time signals currently queued. .TP .IR /proc/ pid /sched_autogroup_enabled " (since Linux 2.6.38)" @@ -5857,7 +5857,7 @@ In mode 1, the kernel pretends there is always enough memory, until memory actually runs out. One use case for this mode is scientific computing applications that employ large sparse arrays. -In Linux kernel versions before 2.6.0, any nonzero value implies mode 1. +Before Linux 2.6.0, any nonzero value implies mode 1. .IP In mode 2 (available since Linux 2.6), the total virtual address space that can be allocated @@ -6559,12 +6559,12 @@ Number of free CMA (Contiguous Memory Allocator) pages. .\" Present only if the kernel was configured with .\" .BR CONFIG_VM_EVENT_COUNTERS . .TP -.IR kswapd_low_wmark_hit_quickly " (since 2.6.33)" +.IR kswapd_low_wmark_hit_quickly " (since Linux 2.6.33)" .\" commit bb3ab596832b920c703d1aea1ce76d69c0f71fb7 .\" Present only if the kernel was configured with .\" .BR CONFIG_VM_EVENT_COUNTERS . .TP -.IR kswapd_high_wmark_hit_quickly " (since 2.6.33)" +.IR kswapd_high_wmark_hit_quickly " (since Linux 2.6.33)" .\" commit bb3ab596832b920c703d1aea1ce76d69c0f71fb7 .\" Present only if the kernel was configured with .\" .BR CONFIG_VM_EVENT_COUNTERS . diff --git a/man5/resolv.conf.5 b/man5/resolv.conf.5 index b44d92f2dc..e9622de4fc 100644 --- a/man5/resolv.conf.5 +++ b/man5/resolv.conf.5 @@ -227,7 +227,7 @@ this option is deprecated; applications should use rather than .BR gethostbyname (3). .TP -.BR ip6\-bytestring " (since glibc 2.3.4 to 2.24)" +.BR ip6\-bytestring " (since glibc 2.3.4 to glibc 2.24)" Sets .B RES_USEBSTRING in @@ -239,7 +239,7 @@ This option was removed in glibc 2.25, since it relied on a backward-incompatible DNS extension that was never deployed on the Internet. .TP -.BR ip6\-dotint / no\-ip6\-dotint " (glibc 2.3.4 to 2.24)" +.BR ip6\-dotint / no\-ip6\-dotint " (glibc 2.3.4 to glibc 2.24)" Clear/set .B RES_NOIP6DOTINT in @@ -254,7 +254,7 @@ when this option is set reverse IPv6 lookups are made in the .I ip6.arpa zone by default. -These options are available in glibc versions up to 2.24, where +These options are available up to glibc 2.24, where .B no\-ip6\-dotint is the default. Since @@ -275,7 +275,7 @@ Sets in .IR _res.options . By default, glibc performs IPv4 and IPv6 lookups in parallel since -version 2.9. +glibc 2.9. Some appliance DNS servers cannot handle these queries properly and make the requests time out. This option disables the behavior and makes glibc perform the IPv6 @@ -346,7 +346,7 @@ This means that applications can trust the AD bit in responses if the .B trust\-ad option has been set correctly. .IP -In glibc version 2.30 and earlier, +In glibc 2.30 and earlier, the AD is not set automatically in queries, and is passed through unchanged to applications in responses. .RE diff --git a/man5/slabinfo.5 b/man5/slabinfo.5 index a84014c2f8..5459122c10 100644 --- a/man5/slabinfo.5 +++ b/man5/slabinfo.5 @@ -188,15 +188,15 @@ Present throughout the Linux 2.2.x kernel series. .TP 1.1 Present in the Linux 2.4.x kernel series. -.\" First appeared in 2.4.0-test3 +.\" First appeared in Linux 2.4.0-test3 .TP 1.2 A format that was briefly present in the Linux 2.5 development series. -.\" from 2.5.45 to 2.5.70 +.\" from Linux 2.5.45 to Linux 2.5.70 .TP 2.0 Present in Linux 2.6.x kernels up to and including Linux 2.6.9. -.\" First appeared in 2.5.71 +.\" First appeared in Linux 2.5.71 .TP 2.1 The current format, which first appeared in Linux 2.6.10. diff --git a/man5/termcap.5 b/man5/termcap.5 index bdbc229b77..c6e18f3bfc 100644 --- a/man5/termcap.5 +++ b/man5/termcap.5 @@ -39,7 +39,7 @@ Fields are separated by \(aq:\(aq. The first field of each entry starts at the left-hand margin, and contains a list of names for the terminal, separated by \(aq|\(aq. .PP -The first subfield may (in BSD termcap entries from versions 4.3 and +The first subfield may (in BSD termcap entries from 4.3BSD and earlier) contain a short name consisting of two characters. This short name may consist of capital or small letters. In 4.4BSD, termcap entries this field is omitted. diff --git a/man7/aio.7 b/man7/aio.7 index 57791c14e0..d0d814cb24 100644 --- a/man7/aio.7 +++ b/man7/aio.7 @@ -140,7 +140,7 @@ structure was less than 0, or was greater than the limit returned by the call .IR sysconf(_SC_AIO_PRIO_DELTA_MAX) . .SH VERSIONS -The POSIX AIO interfaces are provided by glibc since version 2.1. +The POSIX AIO interfaces are provided by glibc since glibc 2.1. .SH STANDARDS POSIX.1-2001, POSIX.1-2008. .SH NOTES diff --git a/man7/capabilities.7 b/man7/capabilities.7 index d85c62f463..45ab7264b5 100644 --- a/man7/capabilities.7 +++ b/man7/capabilities.7 @@ -10,7 +10,7 @@ .\" 2008-07-15, Serge Hallyn .\" Document file capabilities, per-process capability .\" bounding set, changed semantics for CAP_SETPCAP, -.\" and other changes in 2.6.2[45]. +.\" and other changes in Linux 2.6.2[45]. .\" Add CAP_MAC_ADMIN, CAP_MAC_OVERRIDE, CAP_SETFCAP. .\" 2008-07-15, mtk .\" Add text describing circumstances in which CAP_SETPCAP @@ -41,7 +41,7 @@ while unprivileged processes are subject to full permission checking based on the process's credentials (usually: effective UID, effective GID, and supplementary group list). .PP -Starting with kernel 2.2, Linux divides the privileges traditionally +Starting with Linux 2.2, Linux divides the privileges traditionally associated with superuser into distinct units, known as .IR capabilities , which can be independently enabled and disabled. @@ -347,7 +347,7 @@ make changes to the .I securebits flags. .IP -If file capabilities are not supported (i.e., kernels before Linux 2.6.24): +If file capabilities are not supported (i.e., before Linux 2.6.24): grant or remove any capability in the caller's permitted capability set to or from any other process. (This property of @@ -582,7 +582,7 @@ Load and unload kernel modules and .BR delete_module (2)); .IP \(bu -in kernels before 2.6.25: +before Linux 2.6.25: drop capabilities from the system-wide capability bounding set. .PD .RE @@ -833,8 +833,8 @@ be changed and retrieved. The filesystem must support attaching capabilities to an executable file, so that a process gains those capabilities when the file is executed. .PP -Before kernel 2.6.24, only the first two of these requirements are met; -since kernel 2.6.24, all three requirements are met. +Before Linux 2.6.24, only the first two of these requirements are met; +since Linux 2.6.24, all three requirements are met. .\" .SS Notes to kernel developers When adding a new kernel feature that should be governed by a capability, @@ -986,7 +986,7 @@ this can be used to determine the highest bit that may be set in a capability set. .\" .SS File capabilities -Since kernel 2.6.24, the kernel supports +Since Linux 2.6.24, the kernel supports associating capability sets with an executable file using .BR setcap (8). The file capability sets are stored in an extended attribute (see @@ -1428,7 +1428,7 @@ operation. .PP Removing capabilities from the bounding set is supported only if file capabilities are compiled into the kernel. -In kernels before Linux 2.6.33, +Before Linux 2.6.33, file capabilities were an optional feature configurable via the .B CONFIG_SECURITY_FILE_CAPABILITIES option. @@ -1453,7 +1453,7 @@ back into the thread's inheritable set in the future. .PP .B "Capability bounding set prior to Linux 2.6.25" .PP -In kernels before 2.6.25, the capability bounding set is a system-wide +Before Linux 2.6.25, the capability bounding set is a system-wide attribute that affects all threads on the system. The bounding set is accessible via the file .IR /proc/sys/kernel/cap\-bound . @@ -1478,7 +1478,7 @@ in and rebuild the kernel. .PP The system-wide capability bounding set feature was added -to Linux starting with kernel version 2.2.11. +to Linux 2.2.11. .\" .\" .\" @@ -1564,7 +1564,7 @@ The new effective set must be a subset of the new permitted set. .\" For some background: .\" see http://lwn.net/Articles/280279/ and .\" http://article.gmane.org/gmane.linux.kernel.lsm/5476/ -Starting with kernel 2.6.26, +Starting with Linux 2.6.26, and with a kernel in which file capabilities are enabled, Linux implements a set of per-thread .I securebits @@ -1776,7 +1776,7 @@ $ \fBsudo strace \-o trace.log \-u ceci ./myprivprog\fP .EE .in .PP -From kernel 2.5.27 to kernel 2.6.26, +From Linux 2.5.27 to Linux 2.6.26, .\" commit 5915eb53861c5776cfec33ca4fcc1fd20d66dd27 removed .\" CONFIG_SECURITY_CAPABILITIES capabilities were an optional kernel component, @@ -1816,7 +1816,7 @@ It can be found at .UR https://git.kernel.org\:/pub\:/scm\:/libs\:/libcap\:/libcap.git\:/refs/ .UE . .PP -Before kernel 2.6.24, and from kernel 2.6.24 to kernel 2.6.32 if +Before Linux 2.6.24, and from Linux 2.6.24 to Linux 2.6.32 if file capabilities are not enabled, a thread with the .B CAP_SETPCAP capability can manipulate the capabilities of threads other than itself. diff --git a/man7/cpuset.7 b/man7/cpuset.7 index e3b9b403e6..9cc3c52ade 100644 --- a/man7/cpuset.7 +++ b/man7/cpuset.7 @@ -1323,7 +1323,7 @@ the process ID (PID) of a nonexistent process to a cpuset file. .\" ================== VERSIONS ================== .SH VERSIONS -Cpusets appeared in version 2.6.12 of the Linux kernel. +Cpusets appeared in Linux 2.6.12. .\" ================== NOTES ================== .SH NOTES Despite its name, the diff --git a/man7/credentials.7 b/man7/credentials.7 index 1ee4885579..35a98b2199 100644 --- a/man7/credentials.7 +++ b/man7/credentials.7 @@ -215,15 +215,15 @@ and Supplementary group IDs. This is a set of additional group IDs that are used for permission checks when accessing files and other shared resources. -On Linux kernels before 2.6.4, +Before Linux 2.6.4, a process can be a member of up to 32 supplementary groups; -since kernel 2.6.4, +since Linux 2.6.4, a process can be a member of up to 65536 supplementary groups. The call .I sysconf(_SC_NGROUPS_MAX) can be used to determine the number of supplementary groups of which a process may be a member. -.\" Since kernel 2.6.4, the limit is visible via the read-only file +.\" Since Linux 2.6.4, the limit is visible via the read-only file .\" /proc/sys/kernel/ngroups_max. .\" As at 2.6.22-rc2, this file is still read-only. A process can obtain its set of supplementary group IDs using diff --git a/man7/epoll.7 b/man7/epoll.7 index 3812d94e39..bdad0e40f7 100644 --- a/man7/epoll.7 +++ b/man7/epoll.7 @@ -236,7 +236,7 @@ call. .SS /proc interfaces The following interfaces can be used to limit the amount of kernel memory consumed by epoll: -.\" Following was added in 2.6.28, but them removed in 2.6.29 +.\" Following was added in Linux 2.6.28, but them removed in Linux 2.6.29 .\" .TP .\" .IR /proc/sys/fs/epoll/max_user_instances " (since Linux 2.6.28)" .\" This specifies an upper limit on the number of epoll instances @@ -250,7 +250,7 @@ The limit is per real user ID. Each registered file descriptor costs roughly 90 bytes on a 32-bit kernel, and roughly 160 bytes on a 64-bit kernel. Currently, -.\" 2.6.29 (in 2.6.28, the default was 1/32 of lowmem) +.\" Linux 2.6.29 (in Linux 2.6.28, the default was 1/32 of lowmem) the default value for .I max_user_watches is 1/25 (4%) of the available low memory, @@ -578,7 +578,7 @@ The .B epoll API was introduced in Linux kernel 2.5.44. .\" Its interface should be finalized in Linux kernel 2.5.66. -Support was added to glibc in version 2.3.2. +Support was added in glibc 2.3.2. .SH STANDARDS The .B epoll diff --git a/man7/fanotify.7 b/man7/fanotify.7 index 87417ed29f..a84e309941 100644 --- a/man7/fanotify.7 +++ b/man7/fanotify.7 @@ -907,9 +907,9 @@ in the response structure is not valid. This may occur when a response for the permission event has already been written. .SH VERSIONS -The fanotify API was introduced in version 2.6.36 of the Linux kernel and -enabled in version 2.6.37. -Fdinfo support was added in version 3.8. +The fanotify API was introduced in Linux 2.6.36 and +enabled in Linux 2.6.37. +Fdinfo support was added in Linux 3.8. .SH STANDARDS The fanotify API is Linux-specific. .SH NOTES diff --git a/man7/feature_test_macros.7 b/man7/feature_test_macros.7 index 6e704f0163..c8f2486a29 100644 --- a/man7/feature_test_macros.7 +++ b/man7/feature_test_macros.7 @@ -515,21 +515,21 @@ Defining this macro (with any value) implicitly defines .BR _POSIX_SOURCE , .B _POSIX_C_SOURCE with the value 200809L -(200112L in glibc versions before 2.10; -199506L in glibc versions before 2.5; -199309L in glibc versions before 2.1) +(200112L before glibc 2.10; +199506L before glibc 2.5; +199309L before glibc 2.1) and .B _XOPEN_SOURCE with the value 700 -(600 in glibc versions before 2.10; -500 in glibc versions before 2.2). +(600 before glibc 2.10; +500 before glibc 2.2). In addition, various GNU-specific extensions are also exposed. .IP Since glibc 2.19, defining .B _GNU_SOURCE also has the effect of implicitly defining .BR _DEFAULT_SOURCE . -In glibc versions before 2.20, defining +Before glibc 2.20, defining .B _GNU_SOURCE also had the effect of implicitly defining .B _BSD_SOURCE @@ -657,7 +657,7 @@ can now be fortified. .IP Use of this macro requires compiler support, available with .BR gcc (1) -since version 4.0. +since glibc 4.0. .IP Use of .B _FORTIFY_SOURCE @@ -676,9 +676,9 @@ then the following feature test macros are defined by default: .BR _POSIX_SOURCE , and .BR _POSIX_C_SOURCE =200809L -(200112L in glibc versions before 2.10; -199506L in glibc versions before 2.4; -199309L in glibc versions before 2.1). +(200112L before glibc 2.10; +199506L before glibc 2.4; +199309L before glibc 2.1). .PP If any of .BR __STRICT_ANSI__ , @@ -752,8 +752,8 @@ If is undefined, then the setting of .B _POSIX_C_SOURCE depends on the glibc version: -199506L, in glibc versions before 2.4; -200112L, in glibc 2.4 to 2.9; and +199506L, before glibc 2.4; +200112L, since glibc 2.4 to glibc 2.9; and 200809L, since glibc 2.10. .RE .PP diff --git a/man7/icmp.7 b/man7/icmp.7 index f96d4d1a53..4f151e79d3 100644 --- a/man7/icmp.7 +++ b/man7/icmp.7 @@ -52,8 +52,8 @@ cleared after a burst. A jiffy is a system dependent unit, usually 10ms on i386 and about 1ms on alpha and ia64. .TP -.IR icmp_destunreach_rate " (Linux 2.2 to 2.4.9)" -.\" Precisely: from 2.1.102 +.IR icmp_destunreach_rate " (Linux 2.2 to Linux 2.4.9)" +.\" Precisely: from Linux 2.1.102 Maximum rate to send ICMP Destination Unreachable packets. This limits the rate at which packets are sent to any individual route or destination. @@ -68,13 +68,13 @@ If this value is nonzero, Linux will ignore all requests. .TP .IR icmp_echo_ignore_broadcasts " (since Linux 2.2)" -.\" Precisely: from 2.1.68 +.\" Precisely: from Linux 2.1.68 If this value is nonzero, Linux will ignore all .B ICMP_ECHO packets sent to broadcast addresses. .TP -.IR icmp_echoreply_rate " (Linux 2.2 to 2.4.9)" -.\" Precisely: from 2.1.102 +.IR icmp_echoreply_rate " (Linux 2.2 to Linux 2.4.9)" +.\" Precisely: from Linux 2.1.102 Maximum rate for sending .B ICMP_ECHOREPLY packets in response to @@ -82,7 +82,7 @@ packets in response to packets. .TP .IR icmp_errors_use_inbound_ifaddr " (Boolean; default: disabled; since Linux 2.6.12)" -.\" The following taken from 2.6.28-rc4 Documentation/networking/ip-sysctl.txt +.\" The following taken from Linux 2.6.28-rc4 Documentation/networking/ip-sysctl.txt If disabled, ICMP error messages are sent with the primary address of the exiting interface. .IP @@ -97,22 +97,22 @@ then the primary address of the first non-loopback interface that has one will be used regardless of this setting. .TP .IR icmp_ignore_bogus_error_responses " (Boolean; default: disabled; since Linux 2.2)" -.\" precisely: since 2.1.32 -.\" The following taken from 2.6.28-rc4 Documentation/networking/ip-sysctl.txt +.\" precisely: since Linux 2.1.32 +.\" The following taken from Linux 2.6.28-rc4 Documentation/networking/ip-sysctl.txt Some routers violate RFC1122 by sending bogus responses to broadcast frames. Such violations are normally logged via a kernel warning. If this parameter is enabled, the kernel will not give such warnings, which will avoid log file clutter. .TP -.IR icmp_paramprob_rate " (Linux 2.2 to 2.4.9)" -.\" Precisely: from 2.1.102 +.IR icmp_paramprob_rate " (Linux 2.2 to Linux 2.4.9)" +.\" Precisely: from Linux 2.1.102 Maximum rate for sending .B ICMP_PARAMETERPROB packets. These packets are sent when a packet arrives with an invalid IP header. .TP .IR icmp_ratelimit " (integer; default: 1000; since Linux 2.4.10)" -.\" The following taken from 2.6.28-rc4 Documentation/networking/ip-sysctl.txt +.\" The following taken from Linux 2.6.28-rc4 Documentation/networking/ip-sysctl.txt Limit the maximum rates for sending ICMP packets whose type matches .I icmp_ratemask (see below) to specific targets. @@ -120,7 +120,7 @@ Limit the maximum rates for sending ICMP packets whose type matches otherwise the minimum space between responses in milliseconds. .TP .IR icmp_ratemask " (integer; default: see below; since Linux 2.4.10)" -.\" The following taken from 2.6.28-rc4 Documentation/networking/ip-sysctl.txt +.\" The following taken from Linux 2.6.28-rc4 Documentation/networking/ip-sysctl.txt Mask made of ICMP types for which rates are being limited. .IP Significant bits: IHGFEDCBA9876543210 @@ -151,7 +151,7 @@ I Address Mask Reply The bits marked with an asterisk are rate limited by default (see the default mask above). .TP -.IR icmp_timeexceed_rate " (Linux 2.2 to 2.4.9)" +.IR icmp_timeexceed_rate " (Linux 2.2 to Linux 2.4.9)" Maximum rate for sending .B ICMP_TIME_EXCEEDED packets. @@ -166,7 +166,7 @@ means no group is allowed to create ICMP Echo sockets. .SH VERSIONS Support for the .B ICMP_ADDRESS -request was removed in 2.2. +request was removed in Linux 2.2. .PP Support for .B ICMP_SOURCE_QUENCH diff --git a/man7/inotify.7 b/man7/inotify.7 index 8821e136f0..13b4fa4197 100644 --- a/man7/inotify.7 +++ b/man7/inotify.7 @@ -142,9 +142,9 @@ structure is thus The behavior when the buffer given to .BR read (2) is too small to return information about the next event depends -on the kernel version: in kernels before 2.6.21, +on the kernel version: before Linux 2.6.21, .BR read (2) -returns 0; since kernel 2.6.21, +returns 0; since Linux 2.6.21, .BR read (2) fails with the error .BR EINVAL . @@ -576,13 +576,13 @@ that can be created per real user ID. This specifies an upper limit on the number of watches that can be created per real user ID. .SH VERSIONS -Inotify was merged into the 2.6.13 Linux kernel. -The required library interfaces were added to glibc in version 2.4. +Inotify was merged into Linux 2.6.13. +The required library interfaces were added in glibc 2.4. .RB ( IN_DONT_FOLLOW , .BR IN_MASK_ADD , and .B IN_ONLYDIR -were added in glibc version 2.5.) +were added in glibc 2.5.) .SH STANDARDS The inotify API is Linux-specific. .SH NOTES @@ -805,9 +805,9 @@ generate events. .PP .\" FIXME . kernel commit 611da04f7a31b2208e838be55a42c7a1310ae321 -.\" implies that unmount events were buggy 2.6.11 to 2.6.36 +.\" implies that unmount events were buggy since Linux 2.6.11 to Linux 2.6.36 .\" -In kernels before 2.6.16, the +Before Linux 2.6.16, the .B IN_ONESHOT .I mask flag does not work. @@ -822,7 +822,7 @@ since Linux 2.6.36, an .B IN_IGNORED event is generated in this case. .PP -Before kernel 2.6.25, +Before Linux 2.6.25, .\" commit 1c17d18e3775485bf1e0ce79575eb637a94494a2 the kernel code that was intended to coalesce successive identical events (i.e., the two most recent events could potentially be coalesced diff --git a/man7/ip.7 b/man7/ip.7 index 243426ad45..010c30d3ee 100644 --- a/man7/ip.7 +++ b/man7/ip.7 @@ -323,7 +323,7 @@ is valid only for .BR setsockopt (2). .\" .TP -.BR IP_ADD_SOURCE_MEMBERSHIP " (since Linux 2.4.22 / 2.5.68)" +.BR IP_ADD_SOURCE_MEMBERSHIP " (since Linux 2.4.22 / Linux 2.5.68)" Join a multicast group and allow receiving data only from a specified source. Argument is an @@ -411,7 +411,7 @@ structure as described under .BR IP_ADD_SOURCE_MEMBERSHIP . .TP .BR IP_FREEBIND " (since Linux 2.4)" -.\" Precisely: 2.4.0-test10 +.\" Precisely: since Linux 2.4.0-test10 If enabled, this boolean option allows binding to an IP address that is nonlocal or does not (yet) exist. This permits listening on a socket, @@ -478,7 +478,7 @@ For the full description of multicast source filtering refer to RFC 3376. .TP .BR IP_MTU " (since Linux 2.2)" -.\" Precisely: 2.1.124 +.\" Precisely: since Linux 2.1.124 Retrieve the current known path MTU of the current socket. Returns an integer. .IP @@ -488,7 +488,7 @@ is valid only for and can be employed only when the socket has been connected. .TP .BR IP_MTU_DISCOVER " (since Linux 2.2)" -.\" Precisely: 2.1.124 +.\" Precisely: since Linux 2.1.124 Set or receive the Path MTU Discovery setting for a socket. When enabled, Linux will perform Path MTU Discovery as defined in RFC\ 1191 on @@ -633,7 +633,7 @@ This option is valid only for sockets. .TP .BR IP_OPTIONS " (since Linux 2.0)" -.\" Precisely: 1.3.30 +.\" Precisely: since Linux 1.3.30 Set or get the IP options to be sent with every packet from this socket. The arguments are a pointer to a memory buffer containing the options and the option length. @@ -701,7 +701,7 @@ is and this is never used for a control message type. .TP .BR IP_PKTINFO " (since Linux 2.2)" -.\" Precisely: 2.1.68 +.\" Precisely: since Linux 2.1.68 Pass an .B IP_PKTINFO ancillary message that contains a @@ -751,7 +751,7 @@ index overwrites for the routing table lookup. .TP .BR IP_RECVERR " (since Linux 2.2)" -.\" Precisely: 2.1.15 +.\" Precisely: since Linux 2.1.15 Enable extended reliable error message passing. When enabled on a datagram socket, all generated errors will be queued in a per-socket error queue. @@ -890,7 +890,7 @@ It sets or retrieves an integer boolean flag. defaults to off. .TP .BR IP_RECVOPTS " (since Linux 2.2)" -.\" Precisely: 2.1.15 +.\" Precisely: since Linux 2.1.15 Pass all incoming IP options to the user in a .B IP_OPTIONS control message. @@ -912,7 +912,7 @@ The ancillary message contains a .IR "struct sockaddr_in" . .TP .BR IP_RECVTOS " (since Linux 2.2)" -.\" Precisely: 2.1.68 +.\" Precisely: since Linux 2.1.68 If enabled, the .B IP_TOS ancillary message is passed with incoming packets. @@ -921,7 +921,7 @@ field of the packet header. Expects a boolean integer flag. .TP .BR IP_RECVTTL " (since Linux 2.2)" -.\" Precisely: 2.1.68 +.\" Precisely: since Linux 2.1.68 When this flag is set, pass a .B IP_TTL control message with the time-to-live @@ -931,14 +931,14 @@ Not supported for sockets. .TP .BR IP_RETOPTS " (since Linux 2.2)" -.\" Precisely: 2.1.15 +.\" Precisely: since Linux 2.1.15 Identical to .BR IP_RECVOPTS , but returns raw unprocessed options with timestamp and route record options not filled in for this hop. .TP .BR IP_ROUTER_ALERT " (since Linux 2.2)" -.\" Precisely: 2.1.68 +.\" Precisely: since Linux 2.1.68 Pass all to-be forwarded packets with the IP Router Alert option set to this socket. Valid only for raw sockets. @@ -1090,10 +1090,10 @@ meaning that the option is disabled. .\" .TP .IR ip_always_defrag " (Boolean; since Linux 2.2.13)" -[New with kernel 2.2.13; in earlier kernel versions this feature +[New with Linux 2.2.13; in earlier kernel versions this feature was controlled at compile time by the .B CONFIG_IP_ALWAYS_DEFRAG -option; this option is not present in 2.4.x and later] +option; this option is not present in Linux 2.4.x and later] .IP When this boolean flag is enabled (not equal 0), incoming fragments (parts of IP packets @@ -1113,14 +1113,14 @@ This is automagically turned on when masquerading or transparent proxying are configured. .\" .TP -.IR ip_autoconfig " (since Linux 2.2 to 2.6.17)" -.\" Precisely: since 2.1.68 +.IR ip_autoconfig " (since Linux 2.2 to Linux 2.6.17)" +.\" Precisely: since Linux 2.1.68 .\" FIXME document ip_autoconfig Not documented. .\" .TP .IR ip_default_ttl " (integer; default: 64; since Linux 2.2)" -.\" Precisely: 2.1.15 +.\" Precisely: since Linux 2.1.15 Set the default time-to-live value of outgoing packets. This can be changed per socket with the .B IP_TTL @@ -1140,7 +1140,7 @@ IP forwarding can be also set on a per-interface basis. .\" .TP .IR ip_local_port_range " (since Linux 2.2)" -.\" Precisely: since 2.1.68 +.\" Precisely: since Linux 2.1.68 This file contains two integers that define the default local port range allocated to sockets that are not explicitly bound to a port number\(emthat is, the range used for @@ -1188,7 +1188,7 @@ It is better to fix the broken routers on the path than to turn off Path MTU Discovery globally, because not doing it incurs a high cost to the network. .\" -.\" The following is from 2.6.12: Documentation/networking/ip-sysctl.txt +.\" The following is from Linux 2.6.12: Documentation/networking/ip-sysctl.txt .TP .IR ip_nonlocal_bind " (Boolean; default: disabled; since Linux 2.4)" .\" Precisely: patch-2.4.0-test10 @@ -1197,12 +1197,12 @@ If set, allows processes to to nonlocal IP addresses, which can be quite useful, but may break some applications. .\" -.\" The following is from 2.6.12: Documentation/networking/ip-sysctl.txt +.\" The following is from Linux 2.6.12: Documentation/networking/ip-sysctl.txt .TP .IR ip6frag_time " (integer; default: 30)" Time in seconds to keep an IPv6 fragment in memory. .\" -.\" The following is from 2.6.12: Documentation/networking/ip-sysctl.txt +.\" The following is from Linux 2.6.12: Documentation/networking/ip-sysctl.txt .TP .IR ip6frag_secret_interval " (integer; default: 600)" Regeneration interval (in seconds) of the hash secret (or lifetime diff --git a/man7/ipv6.7 b/man7/ipv6.7 index 64c167215c..7fe2d8d993 100644 --- a/man7/ipv6.7 +++ b/man7/ipv6.7 @@ -33,53 +33,53 @@ .\" IPV6_RECVRTHDR (2.6.14) .\" IPV6_RECVDSTOPTS (2.6.14) .\" -.\" IPV6_RECVPATHMTU (2.6.35, flag value added in 2.6.14) +.\" IPV6_RECVPATHMTU (Linux 2.6.35, flag value added in Linux 2.6.14) .\" commit 793b14731686595a741d9f47726ad8b9a235385a .\" Author: Brian Haley -.\" IPV6_PATHMTU (2.6.35, flag value added in 2.6.14) +.\" IPV6_PATHMTU (Linux 2.6.35, flag value added in Linux 2.6.14) .\" commit 793b14731686595a741d9f47726ad8b9a235385a .\" Author: Brian Haley -.\" IPV6_DONTFRAG (2.6.35, flag value added in 2.6.14) +.\" IPV6_DONTFRAG (Linux 2.6.35, flag value added in Linux 2.6.14) .\" commit 793b14731686595a741d9f47726ad8b9a235385a .\" Author: Brian Haley .\" commit 4b340ae20d0e2366792abe70f46629e576adaf5e .\" Author: Brian Haley .\" -.\" IPV6_RECVTCLASS (2.6.14) +.\" IPV6_RECVTCLASS (Linux 2.6.14) .\" commit 41a1f8ea4fbfcdc4232f023732584aae2220de31 .\" Author: YOSHIFUJI Hideaki .\" Based on patch from David L Stevens .\" -.\" IPV6_CHECKSUM (2.2) -.\" IPV6_NEXTHOP (2.2) -.\" IPV6_JOIN_ANYCAST (2.4.21 / 2.6) -.\" IPV6_LEAVE_ANYCAST (2.4.21 / 2.6) -.\" IPV6_FLOWLABEL_MGR (2.2.7 / 2.4) -.\" IPV6_FLOWINFO_SEND (2.2.7 / 2.4) -.\" IPV6_IPSEC_POLICY (2.6) -.\" IPV6_XFRM_POLICY (2.6) -.\" IPV6_TCLASS (2.6) +.\" IPV6_CHECKSUM (Linux 2.2) +.\" IPV6_NEXTHOP (Linux 2.2) +.\" IPV6_JOIN_ANYCAST (Linux 2.4.21 / Linux 2.6) +.\" IPV6_LEAVE_ANYCAST (Linux 2.4.21 / Linux 2.6) +.\" IPV6_FLOWLABEL_MGR (Linux 2.2.7 / Linux 2.4) +.\" IPV6_FLOWINFO_SEND (Linux 2.2.7 / Linux 2.4) +.\" IPV6_IPSEC_POLICY (Linux 2.6) +.\" IPV6_XFRM_POLICY (Linux 2.6) +.\" IPV6_TCLASS (Linux 2.6) .\" -.\" IPV6_ADDR_PREFERENCES (2.6.26) +.\" IPV6_ADDR_PREFERENCES (Linux 2.6.26) .\" commit 7cbca67c073263c179f605bdbbdc565ab29d801d .\" Author: YOSHIFUJI Hideaki -.\" IPV6_MINHOPCOUNT (2.6.35) +.\" IPV6_MINHOPCOUNT (Linux 2.6.35) .\" commit e802af9cabb011f09b9c19a82faef3dd315f27eb .\" Author: Stephen Hemminger -.\" IPV6_ORIGDSTADDR (2.6.37) +.\" IPV6_ORIGDSTADDR (Linux 2.6.37) .\" Actually a CMSG rather than a sockopt? .\" In header file, we have IPV6_RECVORIGDSTADDR == IPV6_ORIGDSTADDR .\" commit 6c46862280c5f55eda7750391bc65cd7e08c7535 .\" Author: Balazs Scheidler -.\" IPV6_RECVORIGDSTADDR (2.6.37) +.\" IPV6_RECVORIGDSTADDR (Linux 2.6.37) .\" commit 6c46862280c5f55eda7750391bc65cd7e08c7535 .\" Author: Balazs Scheidler .\" Support for IPV6_RECVORIGDSTADDR sockopt for UDP sockets .\" were contributed by Harry Mason. -.\" IPV6_TRANSPARENT (2.6.37) +.\" IPV6_TRANSPARENT (Linux 2.6.37) .\" commit 6c46862280c5f55eda7750391bc65cd7e08c7535 .\" Author: Balazs Scheidler -.\" IPV6_UNICAST_IF (3.4) +.\" IPV6_UNICAST_IF (Linux 3.4) .\" commit c4062dfc425e94290ac427a98d6b4721dd2bc91f .\" Author: Erich E. Hoover .\" @@ -146,7 +146,7 @@ struct sockaddr_in6 { in_port_t sin6_port; /* port number */ uint32_t sin6_flowinfo; /* IPv6 flow information */ struct in6_addr sin6_addr; /* IPv6 address */ - uint32_t sin6_scope_id; /* Scope ID (new in 2.4) */ + uint32_t sin6_scope_id; /* Scope ID (new in Linux 2.4) */ }; struct in6_addr { diff --git a/man7/locale.7 b/man7/locale.7 index 301fea9055..3a613dc668 100644 --- a/man7/locale.7 +++ b/man7/locale.7 @@ -295,8 +295,7 @@ struct lconv { .in .SS POSIX.1-2008 extensions to the locale API POSIX.1-2008 standardized a number of extensions to the locale API, -based on implementations that first appeared in version 2.3 -of the GNU C library. +based on implementations that first appeared in glibc 2.3. These extensions are designed to address the problem that the traditional locale APIs do not mix well with multithreaded applications and with applications that must deal with multiple locales. diff --git a/man7/man-pages.7 b/man7/man-pages.7 index 73c0522d11..0d58f81d5e 100644 --- a/man7/man-pages.7 +++ b/man7/man-pages.7 @@ -353,8 +353,8 @@ Patches to remedy this are welcome, but, from the perspective of programmers writing new code, this information probably matters only in the case of kernel interfaces that have been added in Linux 2.4 or later -(i.e., changes since kernel 2.2), -and library functions that have been added to glibc since version 2.1 +(i.e., changes since Linux 2.2), +and library functions that have been added to glibc since glibc 2.1 (i.e., changes since glibc 2.0). .IP The diff --git a/man7/math_error.7 b/man7/math_error.7 index c288c9618f..b2ff1c75d0 100644 --- a/man7/math_error.7 +++ b/man7/math_error.7 @@ -177,7 +177,7 @@ exceptions retrievable via is in use. The standards require that at least one be in use, but permit both to be available. -The current (version 2.8) situation under glibc is messy. +The current (glibc 2.8) situation under glibc is messy. Most (but not all) functions raise exceptions on errors. Some also set .IR errno . diff --git a/man7/mount_namespaces.7 b/man7/mount_namespaces.7 index dec0dedb9c..e9dea19553 100644 --- a/man7/mount_namespaces.7 +++ b/man7/mount_namespaces.7 @@ -1013,7 +1013,7 @@ in the new namespace, .BR unshare (1) (since .I util\-linux -version 2.27) in turn reverses the step performed by + 2.27) in turn reverses the step performed by .BR systemd (1), by making all mounts private in the new namespace. That is, diff --git a/man7/mq_overview.7 b/man7/mq_overview.7 index 8e3081917e..4e7ca8c67c 100644 --- a/man7/mq_overview.7 +++ b/man7/mq_overview.7 @@ -97,8 +97,8 @@ mq_unlink(3) mq_unlink(2) .TE .RE .SS Versions -POSIX message queues have been supported on Linux since kernel 2.6.6. -Glibc support has been provided since version 2.3.4. +POSIX message queues have been supported since Linux 2.6.6. +Glibc support has been provided since glibc 2.3.4. .SS Kernel configuration Support for POSIX message queues is configurable via the .B CONFIG_POSIX_MQUEUE @@ -136,7 +136,7 @@ value will be the smaller of .I msg_default and .IR msg_max . -Up until Linux 2.6.28, the default +Before Linux 2.6.28, the default .I mq_maxmsg was 10; from Linux 2.6.28 to Linux 3.4, the default was the value defined for the @@ -153,7 +153,7 @@ argument given to The default value for .I msg_max is 10. -The minimum value is 1 (10 in kernels before 2.6.28). +The minimum value is 1 (10 before Linux 2.6.28). The upper limit is .BR HARD_MSGMAX . The @@ -172,7 +172,7 @@ has changed across kernel versions: Up to Linux 2.6.32: .I 131072\~/\~sizeof(void\~*) .IP \(bu -Linux 2.6.33 to 3.4: +Linux 2.6.33 to Linux 3.4: .I (32768\~*\~sizeof(void\~*) / 4) .IP \(bu Since Linux 3.5: @@ -200,7 +200,7 @@ a new queue's default value is capped to the .I msgsize_max limit. -Up until Linux 2.6.28, the default +Before Linux 2.6.28, the default .I mq_msgsize was 8192; from Linux 2.6.28 to Linux 3.4, the default was the value defined for the @@ -217,7 +217,7 @@ argument given to The default value for .I msgsize_max is 8192 bytes. -The minimum value is 128 (8192 in kernels before 2.6.28). +The minimum value is 128 (8192 before Linux 2.6.28). The upper limit for .I msgsize_max has varied across kernel versions: @@ -226,7 +226,7 @@ has varied across kernel versions: Before Linux 2.6.28, the upper limit is .BR INT_MAX . .IP \(bu -From Linux 2.6.28 to 3.4, the limit is 1,048,576. +From Linux 2.6.28 to Linux 3.4, the limit is 1,048,576. .IP \(bu Since Linux 3.5, the limit is 16,777,216 .RB ( HARD_MSGSIZEMAX ). @@ -344,17 +344,17 @@ System V message queues; on the other hand POSIX message queues are less widely available (especially on older systems) than System V message queues. .PP -Linux does not currently (2.6.26) support the use of access control +Linux does not currently (Linux 2.6.26) support the use of access control lists (ACLs) for POSIX message queues. .SH BUGS -In Linux versions 3.5 to 3.14, the kernel imposed a ceiling of 1024 +Since Linux 3.5 to Linux 3.14, the kernel imposed a ceiling of 1024 .RB ( HARD_QUEUESMAX ) on the value to which the .I queues_max limit could be raised, and the ceiling was enforced even for privileged processes. This ceiling value was removed in Linux 3.14, -and patches to stable kernels 3.5.x to 3.13.x also removed the ceiling. +and patches to stable Linux 3.5.x to Linux 3.13.x also removed the ceiling. .PP As originally implemented (and documented), the QSIZE field displayed the total number of (user-supplied) diff --git a/man7/netdevice.7 b/man7/netdevice.7 index 67537aaff0..5fe93dce37 100644 --- a/man7/netdevice.7 +++ b/man7/netdevice.7 @@ -358,7 +358,7 @@ or structures, .B EFAULT will be returned. -.\" Slaving isn't supported in 2.2 +.\" Slaving isn't supported in Linux 2.2 .\" . .\" .TP .\" .BR SIOCGIFSLAVE ", " SIOCSIFSLAVE diff --git a/man7/netlink.7 b/man7/netlink.7 index a69c8cb53c..f57eb83f2c 100644 --- a/man7/netlink.7 +++ b/man7/netlink.7 @@ -47,7 +47,7 @@ neighbor setups, queueing disciplines, traffic classes, and packet classifiers (see .BR rtnetlink (7)). .TP -.BR NETLINK_W1 " (Linux 2.6.13 to 2.16.17)" +.BR NETLINK_W1 " (Linux 2.6.13 to Linux 2.16.17)" Messages from 1-wire subsystem. .TP .B NETLINK_USERSOCK @@ -104,7 +104,7 @@ See (or .I /Documentation/connector/connector.* .\" commit baa293e9544bea71361950d071579f0e4d5713ed -in kernel 5.2 and earlier) +in Linux 5.2 and earlier) in the Linux kernel source tree for further information. .TP .BR NETLINK_NETFILTER " (since Linux 2.6.14)" diff --git a/man7/path_resolution.7 b/man7/path_resolution.7 index 9e091e68c5..6f44d21474 100644 --- a/man7/path_resolution.7 +++ b/man7/path_resolution.7 @@ -103,7 +103,7 @@ exceeded ("Too many levels of symbolic links"). As currently implemented on Linux, the maximum number .\" MAXSYMLINKS is 40 of symbolic links that will be followed while resolving a pathname is 40. -In kernels before 2.6.18, the limit on the recursion depth was 5. +Before Linux 2.6.18, the limit on the recursion depth was 5. Starting with Linux 2.6.18, this limit .\" MAX_NESTED_LINKS was raised to 8. diff --git a/man7/pipe.7 b/man7/pipe.7 index 852cbd94fb..8af8932f38 100644 --- a/man7/pipe.7 +++ b/man7/pipe.7 @@ -110,7 +110,7 @@ an application should be designed so that a reading process consumes data as soon as it is available, so that a writing process does not remain blocked. .PP -In Linux versions before 2.6.11, the capacity of a pipe was the same as +Before Linux 2.6.11, the capacity of a pipe was the same as the system page size (e.g., 4096 bytes on i386). Since Linux 2.6.11, the pipe capacity is 16 pages (i.e., 65,536 bytes in a system with a page size of 4096 bytes). @@ -315,7 +315,7 @@ The target for delivery of signals must be set using the command. On Linux, .B O_ASYNC -is supported for pipes and FIFOs only since kernel 2.6. +is supported for pipes and FIFOs only since Linux 2.6. .SS Portability notes On some systems (but not Linux), pipes are bidirectional: data can be transmitted in both directions between the pipe ends. diff --git a/man7/pthreads.7 b/man7/pthreads.7 index 606085d8eb..0058cd1216 100644 --- a/man7/pthreads.7 +++ b/man7/pthreads.7 @@ -811,26 +811,26 @@ The information returned by .BR times (2) and .BR getrusage (2) -is per-thread rather than process-wide (fixed in kernel 2.6.9). +is per-thread rather than process-wide (fixed in Linux 2.6.9). .IP \(bu -Threads do not share resource limits (fixed in kernel 2.6.10). +Threads do not share resource limits (fixed in Linux 2.6.10). .IP \(bu -Threads do not share interval timers (fixed in kernel 2.6.12). +Threads do not share interval timers (fixed in Linux 2.6.12). .IP \(bu Only the main thread is permitted to start a new session using .BR setsid (2) -(fixed in kernel 2.6.16). +(fixed in Linux 2.6.16). .IP \(bu Only the main thread is permitted to make the process into a process group leader using .BR setpgid (2) -(fixed in kernel 2.6.16). +(fixed in Linux 2.6.16). .IP \(bu Threads have distinct alternate signal stack settings. However, a new thread's alternate signal stack settings are copied from the thread that created it, so that the threads initially share an alternate signal stack -(fixed in kernel 2.6.16). +(fixed in Linux 2.6.16). .PP Note the following further points about the NPTL implementation: .IP \(bu 3 diff --git a/man7/pty.7 b/man7/pty.7 index 79e646a866..bef60e9318 100644 --- a/man7/pty.7 +++ b/man7/pty.7 @@ -47,7 +47,7 @@ pseudoterminals. System V-style terminals are commonly called UNIX 98 pseudoterminals on Linux systems. .PP -Since kernel 2.6.4, BSD-style pseudoterminals are considered deprecated: +Since Linux 2.6.4, BSD-style pseudoterminals are considered deprecated: support can be disabled when building the kernel by disabling the .B CONFIG_LEGACY_PTYS option. @@ -74,12 +74,12 @@ in a call to .PP The Linux kernel imposes a limit on the number of available UNIX 98 pseudoterminals. -In kernels up to and including 2.6.3, this limit is configured +Up to and including Linux 2.6.3, this limit is configured at kernel compilation time .RB ( CONFIG_UNIX98_PTYS ), and the permitted number of pseudoterminals can be up to 2048, with a default setting of 256. -Since kernel 2.6.4, the limit is dynamically adjustable via +Since Linux 2.6.4, the limit is dynamically adjustable via .IR /proc/sys/kernel/pty/max , and a corresponding file, .IR /proc/sys/kernel/pty/nr , diff --git a/man7/rtnetlink.7 b/man7/rtnetlink.7 index be43227743..270c78acc1 100644 --- a/man7/rtnetlink.7 +++ b/man7/rtnetlink.7 @@ -117,7 +117,7 @@ in Linux 2.4 and earlier). Add, remove, or receive information about an IP address associated with an interface. In Linux 2.2, an interface can carry multiple IP addresses, -this replaces the alias device concept in 2.0. +this replaces the alias device concept in Linux 2.0. In Linux 2.2, these messages support IPv4 and IPv6 addresses. They contain an diff --git a/man7/sched.7 b/man7/sched.7 index a157c35ac9..8b50f54613 100644 --- a/man7/sched.7 +++ b/man7/sched.7 @@ -178,8 +178,8 @@ changes to a thread's priority (or policy) using any mechanism other than .BR pthread_setschedprio (3) should result in the thread being placed at the end of the list for its priority. -.\" In 2.2.x and 2.4.x, the thread is placed at the front of the queue -.\" In 2.0.x, the Right Thing happened: the thread went to the back -- MTK +.\" In Linux 2.2.x and Linux 2.4.x, the thread is placed at the front of the queue +.\" In Linux 2.0.x, the Right Thing happened: the thread went to the back -- MTK .IP \(bu A thread calling .BR sched_yield (2) @@ -213,7 +213,7 @@ retrieved using .\" by the process nice value -- MTK .\" .SS SCHED_DEADLINE: Sporadic task model deadline scheduling -Since version 3.14, Linux provides a deadline scheduling policy +Since Linux 3.14, Linux provides a deadline scheduling policy .RB ( SCHED_DEADLINE ). This policy is currently implemented using GEDF (Global Earliest Deadline First) @@ -421,16 +421,16 @@ The range of the nice value varies across UNIX systems. On modern Linux, the range is \-20 (high priority) to +19 (low priority). On some other systems, the range is \-20..20. -Very early Linux kernels (Before Linux 2.0) had the range \-infinity..15. +Very early Linux kernels (before Linux 2.0) had the range \-infinity..15. .\" Linux before 1.3.36 had \-infinity..15. -.\" Since kernel 1.3.43, Linux has the range \-20..19. +.\" Since Linux 1.3.43, Linux has the range \-20..19. .PP The degree to which the nice value affects the relative scheduling of .B SCHED_OTHER processes likewise varies across UNIX systems and across Linux kernel versions. .PP -With the advent of the CFS scheduler in kernel 2.6.23, +With the advent of the CFS scheduler in Linux 2.6.23, Linux adopted an algorithm that causes relative differences in nice values to have a much stronger effect. In the current implementation, each unit of difference in the @@ -544,7 +544,7 @@ This flag is disabled in child processes created by .BR fork (2). .\" .SS Privileges and resource limits -In Linux kernels before 2.6.12, only privileged +Before Linux 2.6.12, only privileged .RB ( CAP_SYS_NICE ) threads can set a nonzero static priority (i.e., set a real-time scheduling policy). @@ -593,12 +593,12 @@ matches the real or effective user ID of the target thread. Special rules apply for the .B SCHED_IDLE policy. -In Linux kernels before 2.6.39, +Before Linux 2.6.39, an unprivileged thread operating under this policy cannot change its policy, regardless of the value of its .B RLIMIT_RTPRIO resource limit. -In Linux kernels since 2.6.39, +Since Linux 2.6.39, .\" commit c02aa73b1d18e43cfd79c2f193b225e84ca497c8 an unprivileged thread can switch to either the .B SCHED_BATCH @@ -627,7 +627,7 @@ or .B SCHED_DEADLINE policy can potentially block all other threads from accessing the CPU forever. -Prior to Linux 2.6.25, the only way of preventing a runaway real-time +Before Linux 2.6.25, the only way of preventing a runaway real-time process from freezing the system was to run (at the console) a shell scheduled under a higher static priority than the tested application. This allows an emergency kill of tested @@ -643,7 +643,7 @@ See .BR getrlimit (2) for details. .PP -Since version 2.6.25, Linux also provides two +Since Linux 2.6.25, Linux also provides two .I /proc files that can be used to reserve a certain amount of CPU time to be used by non-real-time processes. @@ -667,7 +667,7 @@ The value in this file can range from \-1 to .BR INT_MAX \-1. Specifying \-1 makes the run time the same as the period; that is, no CPU time is set aside for non-real-time processes -(which was the Linux behavior before kernel 2.6.25). +(which was the behavior before Linux 2.6.25). The default value in this file is 950,000 (0.95 seconds), meaning that 5% of the CPU time is reserved for processes that don't run under a real-time or deadline scheduling policy. @@ -895,7 +895,7 @@ $ \fBecho 10 > /proc/self/autogroup\fP .SS Real-time features in the mainline Linux kernel .\" FIXME . Probably this text will need some minor tweaking .\" ask Carsten Emde about this. -Since kernel version 2.6.18, Linux is gradually +Since Linux 2.6.18, Linux is gradually becoming equipped with real-time capabilities, most of which are derived from the former .I realtime\-preempt @@ -942,11 +942,11 @@ Originally, Standard Linux was intended as a general-purpose operating system being able to handle background processes, interactive applications, and less demanding real-time applications (applications that need to usually meet timing deadlines). -Although the Linux kernel 2.6 +Although the Linux 2.6 allowed for kernel preemption and the newly introduced O(1) scheduler ensures that the time needed to schedule is fixed and deterministic irrespective of the number of active tasks, true real-time computing -was not possible up to kernel version 2.6.17. +was not possible up to Linux 2.6.17. .SH SEE ALSO .ad l .nh diff --git a/man7/sem_overview.7 b/man7/sem_overview.7 index 31bb048a66..1dfcf68ad4 100644 --- a/man7/sem_overview.7 +++ b/man7/sem_overview.7 @@ -85,7 +85,7 @@ the semaphore should be destroyed using The remainder of this section describes some specific details of the Linux implementation of POSIX semaphores. .SS Versions -Prior to kernel 2.6, Linux supported only unnamed, +Before Linux 2.6, Linux supported only unnamed, thread-shared semaphores. On a system with Linux 2.6 and a glibc that provides the NPTL threading implementation, diff --git a/man7/shm_overview.7 b/man7/shm_overview.7 index 14eb2ef5d5..ee3d7b3b6b 100644 --- a/man7/shm_overview.7 +++ b/man7/shm_overview.7 @@ -75,7 +75,7 @@ On Linux, shared memory objects are created in a .RB ( tmpfs (5)) virtual filesystem, normally mounted under .IR /dev/shm . -Since kernel 2.6.19, Linux supports the use of access control lists (ACLs) +Since Linux 2.6.19, Linux supports the use of access control lists (ACLs) to control the permissions of objects in the virtual filesystem. .SH NOTES Typically, processes must synchronize their access to a shared diff --git a/man7/signal.7 b/man7/signal.7 index 05d5cc9e19..06dc54324c 100644 --- a/man7/signal.7 +++ b/man7/signal.7 @@ -527,7 +527,7 @@ Signal 29 is on SPARC. .\" .SS Real-time signals -Starting with version 2.2, +Starting with Linux 2.2, Linux supports real-time signals as originally defined in the POSIX.1b real-time extensions (and now included in POSIX.1-2001). The range of supported real-time signals is defined by the macros @@ -612,7 +612,7 @@ According to POSIX, an implementation should permit at least (32) real-time signals to be queued to a process. However, Linux does things differently. -In kernels up to and including 2.6.7, Linux imposes +Up to and including Linux 2.6.7, Linux imposes a system-wide limit on the number of queued real-time signals for all processes. This limit can be viewed and (with privilege) changed via the @@ -706,7 +706,7 @@ Socket interfaces: .\" If a timeout (setsockopt()) is in effect on the socket, then these .\" system calls switch to using EINTR. Consequently, they and are not .\" automatically restarted, and they show the stop/cont behavior -.\" described below. (Verified from 2.6.26 source, and by experiment; mtk) +.\" described below. (Verified from Linux 2.6.26 source, and by experiment; mtk) .BR accept (2), .BR connect (2), .BR recv (2), diff --git a/man7/socket.7 b/man7/socket.7 index 2b191c7836..f957e18555 100644 --- a/man7/socket.7 +++ b/man7/socket.7 @@ -814,9 +814,9 @@ indicate a socket as readable only if at least bytes are available. .TP .BR SO_RCVTIMEO " and " SO_SNDTIMEO -.\" Not implemented in 2.0. -.\" Implemented in 2.1.11 for getsockopt: always return a zero struct. -.\" Implemented in 2.3.41 for setsockopt, and actually used. +.\" Not implemented in Linux 2.0. +.\" Implemented in Linux 2.1.11 for getsockopt: always return a zero struct. +.\" Implemented in Linux 2.3.41 for setsockopt, and actually used. Specify the receiving or sending timeouts until reporting an error. The argument is a .IR "struct timeval" . diff --git a/man7/tcp.7 b/man7/tcp.7 index 2430a084ca..1d8a26818e 100644 --- a/man7/tcp.7 +++ b/man7/tcp.7 @@ -74,7 +74,7 @@ .\" Author: Pavel Emelyanov .\" .\" TCP_FASTOPEN (3.6) -.\" (Fast Open server side implementation completed in 3.7) +.\" (Fast Open server side implementation completed in Linux 3.7) .\" http://lwn.net/Articles/508865/ .\" .\" TCP_TIMESTAMP (3.9) @@ -258,9 +258,9 @@ the corresponding option is enabled, and a zero value ("false") meaning that the option is disabled. .TP .IR tcp_abc " (Integer; default: 0; Linux 2.6.15 to Linux 3.8)" -.\" Since 2.6.15; removed in 3.9 +.\" Since Linux 2.6.15; removed in Linux 3.9 .\" commit ca2eb5679f8ddffff60156af42595df44a315ef0 -.\" The following is from 2.6.28-rc4: Documentation/networking/ip-sysctl.txt +.\" The following is from Linux 2.6.28-rc4: Documentation/networking/ip-sysctl.txt Control the Appropriate Byte Count (ABC), defined in RFC 3465. ABC is a way of increasing the congestion window .RI ( cwnd ) @@ -286,7 +286,7 @@ of two segments to compensate for delayed acknowledgements. .RE .TP .IR tcp_abort_on_overflow " (Boolean; default: disabled; since Linux 2.4)" -.\" Since 2.3.41 +.\" Since Linux 2.3.41 Enable resetting connections if the listening service is too slow and unable to keep up and accept them. It means that if overflow occurred due @@ -298,7 +298,7 @@ cannot be tuned to accept connections faster. Enabling this option can harm the clients of your server. .TP .IR tcp_adv_win_scale " (integer; default: 2; since Linux 2.4)" -.\" Since 2.4.0-test7 +.\" Since Linux 2.4.0-test7 Count buffering overhead as .IR "bytes/2^tcp_adv_win_scale" , if @@ -323,7 +323,7 @@ default value of 2 implies that the space used for the application buffer is one fourth that of the total. .TP .IR tcp_allowed_congestion_control " (String; default: see text; since Linux 2.4.20)" -.\" The following is from 2.6.28-rc4: Documentation/networking/ip-sysctl.txt +.\" The following is from Linux 2.6.28-rc4: Documentation/networking/ip-sysctl.txt Show/set the congestion control algorithm choices available to unprivileged processes (see the description of the .B TCP_CONGESTION @@ -353,7 +353,7 @@ socket option to obtain optimal behavior when they know how/when to uncork their sockets. .TP .IR tcp_available_congestion_control " (String; read-only; since Linux 2.4.20)" -.\" The following is from 2.6.28-rc4: Documentation/networking/ip-sysctl.txt +.\" The following is from Linux 2.6.28-rc4: Documentation/networking/ip-sysctl.txt Show a list of the congestion-control algorithms that are registered. The items in the list are separated by white space and @@ -364,7 +364,7 @@ More congestion-control algorithms may be available as modules, but not loaded. .TP .IR tcp_app_win " (integer; default: 31; since Linux 2.4)" -.\" Since 2.4.0-test7 +.\" Since Linux 2.4.0-test7 This variable defines how many bytes of the TCP window are reserved for buffering overhead. .IP @@ -372,7 +372,7 @@ A maximum of (\fIwindow/2^tcp_app_win\fP, mss) bytes in the window are reserved for the application buffer. A value of 0 implies that no amount is reserved. .\" -.\" The following is from 2.6.28-rc4: Documentation/networking/ip-sysctl.txt +.\" The following is from Linux 2.6.28-rc4: Documentation/networking/ip-sysctl.txt .TP .IR tcp_base_mss " (Integer; default: 512; since Linux 2.6.17)" The initial value of @@ -381,9 +381,9 @@ to be used by the packetization layer Path MTU discovery (MTU probing). If MTU probing is enabled, this is the initial MSS used by the connection. .\" -.\" The following is from 2.6.12: Documentation/networking/ip-sysctl.txt +.\" The following is from Linux 2.6.12: Documentation/networking/ip-sysctl.txt .TP -.IR tcp_bic " (Boolean; default: disabled; Linux 2.4.27/2.6.6 to 2.6.13)" +.IR tcp_bic " (Boolean; default: disabled; Linux 2.4.27/2.6.6 to Linux 2.6.13)" Enable BIC TCP congestion control algorithm. BIC-TCP is a sender-side-only change that ensures a linear RTT fairness under large windows while offering both scalability and @@ -395,21 +395,21 @@ increment ensures linear RTT fairness as well as good scalability. Under small congestion windows, binary search increase provides TCP friendliness. .\" -.\" The following is from 2.6.12: Documentation/networking/ip-sysctl.txt +.\" The following is from Linux 2.6.12: Documentation/networking/ip-sysctl.txt .TP -.IR tcp_bic_low_window " (integer; default: 14; Linux 2.4.27/2.6.6 to 2.6.13)" +.IR tcp_bic_low_window " (integer; default: 14; Linux 2.4.27/2.6.6 to Linux 2.6.13)" Set the threshold window (in packets) where BIC TCP starts to adjust the congestion window. Below this threshold BIC TCP behaves the same as the default TCP Reno. .\" -.\" The following is from 2.6.12: Documentation/networking/ip-sysctl.txt +.\" The following is from Linux 2.6.12: Documentation/networking/ip-sysctl.txt .TP -.IR tcp_bic_fast_convergence " (Boolean; default: enabled; Linux 2.4.27/2.6.6 to 2.6.13)" +.IR tcp_bic_fast_convergence " (Boolean; default: enabled; Linux 2.4.27/2.6.6 to Linux 2.6.13)" Force BIC TCP to more quickly respond to changes in congestion window. Allows two flows sharing the same connection to converge more rapidly. .TP .IR tcp_congestion_control " (String; default: see text; since Linux 2.4.13)" -.\" The following is from 2.6.28-rc4: Documentation/networking/ip-sysctl.txt +.\" The following is from Linux 2.6.28-rc4: Documentation/networking/ip-sysctl.txt Set the default congestion-control algorithm to be used for new connections. The algorithm "reno" is always available, but additional choices may be available depending on kernel configuration. @@ -423,7 +423,7 @@ and the kernel was configured with the option. .TP .IR tcp_dsack " (Boolean; default: enabled; since Linux 2.4)" -.\" Since 2.4.0-test7 +.\" Since Linux 2.4.0-test7 Enable RFC\ 2883 TCP Duplicate SACK support. .TP .IR tcp_fastopen " (Bitmask; default: 0x1; since Linux 3.7)" @@ -454,7 +454,7 @@ Set server side RFC\~7413 Fast Open key to generate Fast Open cookie when server side Fast Open support is enabled. .TP .IR tcp_ecn " (Integer; default: see below; since Linux 2.4)" -.\" Since 2.4.0-test7 +.\" Since Linux 2.4.0-test7 Enable RFC\ 3168 Explicit Congestion Notification. .IP This file can have one of the following values: @@ -492,21 +492,21 @@ normal SYN retransmission timeout will be resent with CWR and ECE cleared. .TP .IR tcp_fack " (Boolean; default: enabled; since Linux 2.2)" -.\" Since 2.1.92 +.\" Since Linux 2.1.92 Enable TCP Forward Acknowledgement support. .TP .IR tcp_fin_timeout " (integer; default: 60; since Linux 2.2)" -.\" Since 2.1.53 +.\" Since Linux 2.1.53 This specifies how many seconds to wait for a final FIN packet before the socket is forcibly closed. This is strictly a violation of the TCP specification, but required to prevent denial-of-service attacks. In Linux 2.2, the default value was 180. .\" -.\" The following is from 2.6.12: Documentation/networking/ip-sysctl.txt +.\" The following is from Linux 2.6.12: Documentation/networking/ip-sysctl.txt .TP .IR tcp_frto " (integer; default: see below; since Linux 2.4.21/2.6)" -.\" Since 2.4.21/2.5.43 +.\" Since Linux 2.4.21/2.5.43 Enable F-RTO, an enhanced recovery algorithm for TCP retransmission timeouts (RTOs). It is particularly beneficial in wireless environments @@ -572,17 +572,17 @@ are restored to the values prior to timeout. .RE .TP .IR tcp_keepalive_intvl " (integer; default: 75; since Linux 2.4)" -.\" Since 2.3.18 +.\" Since Linux 2.3.18 The number of seconds between TCP keep-alive probes. .TP .IR tcp_keepalive_probes " (integer; default: 9; since Linux 2.2)" -.\" Since 2.1.43 +.\" Since Linux 2.1.43 The maximum number of TCP keep-alive probes to send before giving up and killing the connection if no response is obtained from the other end. .TP .IR tcp_keepalive_time " (integer; default: 7200; since Linux 2.2)" -.\" Since 2.1.43 +.\" Since Linux 2.1.43 The number of seconds a connection needs to be idle before TCP begins sending out keep-alive probes. Keep-alives are sent only when the @@ -596,11 +596,11 @@ of 75 seconds apart) when keep-alive is enabled. Note that underlying connection tracking mechanisms and application timeouts may be much shorter. .\" -.\" The following is from 2.6.12: Documentation/networking/ip-sysctl.txt +.\" The following is from Linux 2.6.12: Documentation/networking/ip-sysctl.txt .TP .IR tcp_low_latency " (Boolean; default: disabled; since Linux 2.4.21/2.6; \ obsolete since Linux 4.14)" -.\" Since 2.4.21/2.5.60 +.\" Since Linux 2.4.21/2.5.60 If enabled, the TCP stack makes decisions that prefer lower latency as opposed to higher throughput. It this option is disabled, then higher throughput is preferred. @@ -611,7 +611,7 @@ Since Linux 4.14, this file still exists, but its value is ignored. .TP .IR tcp_max_orphans " (integer; default: see below; since Linux 2.4)" -.\" Since 2.3.41 +.\" Since Linux 2.3.41 The maximum number of orphaned (not attached to any user file handle) TCP sockets allowed in the system. When this number is exceeded, @@ -625,7 +625,7 @@ The default initial value is set equal to the kernel parameter NR_FILE. This initial default is adjusted depending on the memory in the system. .TP .IR tcp_max_syn_backlog " (integer; default: see below; since Linux 2.2)" -.\" Since 2.1.53 +.\" Since Linux 2.1.53 The maximum number of queued connection requests which have still not received an acknowledgement from the connecting client. If this number is exceeded, the kernel will begin @@ -635,7 +635,7 @@ The default value of 256 is increased to greater (>= 128\ MB), and reduced to 128 for those systems with very low memory (<= 32\ MB). .IP -Prior to Linux 2.6.20, +Before Linux 2.6.20, .\" commit 72a3effaf633bcae9034b7e176bdbd78d64a71db it was recommended that if this needed to be increased above 1024, the size of the SYNACK hash table @@ -657,7 +657,7 @@ In Linux 2.6.20, the fixed sized was removed in favor of dynamic sizing. .TP .IR tcp_max_tw_buckets " (integer; default: see below; since Linux 2.4)" -.\" Since 2.3.41 +.\" Since Linux 2.3.41 The maximum number of sockets in TIME_WAIT state allowed in the system. This limit exists only to prevent simple denial-of-service attacks. @@ -667,14 +667,14 @@ If this number is exceeded, the socket is closed and a warning is printed. .TP .IR tcp_moderate_rcvbuf " (Boolean; default: enabled; since Linux 2.4.17/2.6.7)" -.\" The following is from 2.6.28-rc4: Documentation/networking/ip-sysctl.txt +.\" The following is from Linux 2.6.28-rc4: Documentation/networking/ip-sysctl.txt If enabled, TCP performs receive buffer auto-tuning, attempting to automatically size the buffer (no greater than .IR tcp_rmem[2] ) to match the size required by the path for full throughput. .TP .IR tcp_mem " (since Linux 2.4)" -.\" Since 2.4.0-test7 +.\" Since Linux 2.4.0-test7 This is a vector of 3 integers: [low, pressure, high]. These bounds, measured in units of the system page size, are used by TCP to track its memory usage. @@ -705,7 +705,7 @@ This value overrides any other limits imposed by the kernel. .RE .TP .IR tcp_mtu_probing " (integer; default: 0; since Linux 2.6.17)" -.\" The following is from 2.6.28-rc4: Documentation/networking/ip-sysctl.txt +.\" The following is from Linux 2.6.28-rc4: Documentation/networking/ip-sysctl.txt This parameter controls TCP Packetization-Layer Path MTU Discovery. The following values may be assigned to the file: .RS @@ -722,7 +722,7 @@ Always enabled, use initial MSS of .RE .TP .IR tcp_no_metrics_save " (Boolean; default: disabled; since Linux 2.6.6)" -.\" The following is from 2.6.28-rc4: Documentation/networking/ip-sysctl.txt +.\" The following is from Linux 2.6.28-rc4: Documentation/networking/ip-sysctl.txt By default, TCP saves various connection metrics in the route cache when the connection closes, so that connections established in the near future can use these to set initial conditions. @@ -733,12 +733,12 @@ If is enabled, TCP will not cache metrics on closing connections. .TP .IR tcp_orphan_retries " (integer; default: 8; since Linux 2.4)" -.\" Since 2.3.41 +.\" Since Linux 2.3.41 The maximum number of attempts made to probe the other end of a connection which has been closed by our end. .TP .IR tcp_reordering " (integer; default: 3; since Linux 2.4)" -.\" Since 2.4.0-test7 +.\" Since Linux 2.4.0-test7 The maximum a packet can be reordered in a TCP packet stream without TCP assuming packet loss and going into slow start. It is not advisable to change this number. @@ -747,11 +747,11 @@ minimize unnecessary back off and retransmits provoked by reordering of packets on a connection. .TP .IR tcp_retrans_collapse " (Boolean; default: enabled; since Linux 2.2)" -.\" Since 2.1.96 +.\" Since Linux 2.1.96 Try to send full-sized packets during retransmit. .TP .IR tcp_retries1 " (integer; default: 3; since Linux 2.2)" -.\" Since 2.1.43 +.\" Since Linux 2.1.43 The number of times TCP will attempt to retransmit a packet on an established connection normally, without the extra effort of getting the network layers involved. @@ -761,7 +761,7 @@ update the route if possible before each new retransmit. The default is the RFC specified minimum of 3. .TP .IR tcp_retries2 " (integer; default: 15; since Linux 2.2)" -.\" Since 2.1.43 +.\" Since Linux 2.1.43 The maximum number of times a TCP packet is retransmitted in established state before giving up. The default value is 15, which corresponds to a duration of @@ -771,7 +771,7 @@ The RFC\ 1122 specified minimum limit of 100 seconds is typically deemed too short. .TP .IR tcp_rfc1337 " (Boolean; default: disabled; since Linux 2.2)" -.\" Since 2.1.90 +.\" Since Linux 2.1.90 Enable TCP behavior conformant with RFC\ 1337. When disabled, if a RST is received in TIME_WAIT state, we close @@ -779,7 +779,7 @@ the socket immediately without waiting for the end of the TIME_WAIT period. .TP .IR tcp_rmem " (since Linux 2.4)" -.\" Since 2.4.0-test7 +.\" Since Linux 2.4.0-test7 This is a vector of 3 integers: [min, default, max]. These parameters are used by TCP to regulate receive buffer sizes. TCP dynamically adjusts the size of the @@ -836,11 +836,11 @@ lowered to 87380 in low-memory systems). .RE .TP .IR tcp_sack " (Boolean; default: enabled; since Linux 2.2)" -.\" Since 2.1.36 +.\" Since Linux 2.1.36 Enable RFC\ 2018 TCP Selective Acknowledgements. .TP .IR tcp_slow_start_after_idle " (Boolean; default: enabled; since Linux 2.6.18)" -.\" The following is from 2.6.28-rc4: Documentation/networking/ip-sysctl.txt +.\" The following is from Linux 2.6.28-rc4: Documentation/networking/ip-sysctl.txt If enabled, provide RFC 2861 behavior and time out the congestion window after an idle period. An idle period is defined as the current RTO (retransmission timeout). @@ -848,7 +848,7 @@ If disabled, the congestion window will not be timed out after an idle period. .TP .IR tcp_stdurg " (Boolean; default: disabled; since Linux 2.2)" -.\" Since 2.1.44 +.\" Since Linux 2.1.44 If this option is enabled, then use the RFC\ 1122 interpretation of the TCP urgent-pointer field. .\" RFC 793 was ambiguous in its specification of the meaning of the @@ -862,7 +862,7 @@ the urgent pointer points to the first byte after the urgent data. Enabling this option may lead to interoperability problems. .TP .IR tcp_syn_retries " (integer; default: 6; since Linux 2.2)" -.\" Since 2.1.38 +.\" Since Linux 2.1.38 The maximum number of times initial SYNs for an active TCP connection attempt will be retransmitted. This value should not be higher than 255. @@ -875,13 +875,13 @@ the default value was 5, which corresponded to approximately 180 seconds. .TP .IR tcp_synack_retries " (integer; default: 5; since Linux 2.2)" -.\" Since 2.1.38 +.\" Since Linux 2.1.38 The maximum number of times a SYN/ACK segment for a passive TCP connection will be retransmitted. This number should not be higher than 255. .TP .IR tcp_syncookies " (integer; default: 1; since Linux 2.2)" -.\" Since 2.1.43 +.\" Since Linux 2.1.43 Enable TCP syncookies. The kernel must be compiled with .BR CONFIG_SYN_COOKIES . @@ -915,7 +915,7 @@ This can be useful for network testing. .RE .TP .IR tcp_timestamps " (integer; default: 1; since Linux 2.2)" -.\" Since 2.1.36 +.\" Since Linux 2.1.36 Set to one of the following values to enable or disable RFC\ 1323 TCP timestamps: .RS @@ -941,9 +941,9 @@ can be consumed by a single TCP Segmentation Offload (TSO) frame. The setting of this parameter is a tradeoff between burstiness and building larger TSO frames. .TP -.IR tcp_tw_recycle " (Boolean; default: disabled; Linux 2.4 to 4.11)" -.\" Since 2.3.15 -.\" removed in 4.12; commit 4396e46187ca5070219b81773c4e65088dac50cc +.IR tcp_tw_recycle " (Boolean; default: disabled; Linux 2.4 to Linux 4.11)" +.\" Since Linux 2.3.15 +.\" removed in Linux 4.12; commit 4396e46187ca5070219b81773c4e65088dac50cc Enable fast recycling of TIME_WAIT sockets. Enabling this option is not recommended as the remote IP may not use monotonically increasing @@ -951,18 +951,18 @@ timestamps (devices behind NAT, devices with per-connection timestamp offsets). See RFC 1323 (PAWS) and RFC 6191. .\" -.\" The following is from 2.6.12: Documentation/networking/ip-sysctl.txt +.\" The following is from Linux 2.6.12: Documentation/networking/ip-sysctl.txt .TP .IR tcp_tw_reuse " (Boolean; default: disabled; since Linux 2.4.19/2.6)" -.\" Since 2.4.19/2.5.43 +.\" Since Linux 2.4.19/2.5.43 Allow to reuse TIME_WAIT sockets for new connections when it is safe from protocol viewpoint. It should not be changed without advice/request of technical experts. .\" -.\" The following is from 2.6.12: Documentation/networking/ip-sysctl.txt +.\" The following is from Linux 2.6.12: Documentation/networking/ip-sysctl.txt .TP -.IR tcp_vegas_cong_avoid " (Boolean; default: disabled; Linux 2.2 to 2.6.13)" -.\" Since 2.1.8; removed in 2.6.13 +.IR tcp_vegas_cong_avoid " (Boolean; default: disabled; Linux 2.2 to Linux 2.6.13)" +.\" Since Linux 2.1.8; removed in Linux 2.6.13 Enable TCP Vegas congestion avoidance algorithm. TCP Vegas is a sender-side-only change to TCP that anticipates the onset of congestion by estimating the bandwidth. @@ -970,9 +970,9 @@ TCP Vegas adjusts the sending rate by modifying the congestion window. TCP Vegas should provide less packet loss, but it is not as aggressive as TCP Reno. .\" -.\" The following is from 2.6.12: Documentation/networking/ip-sysctl.txt +.\" The following is from Linux 2.6.12: Documentation/networking/ip-sysctl.txt .TP -.IR tcp_westwood " (Boolean; default: disabled; Linux 2.4.26/2.6.3 to 2.6.13)" +.IR tcp_westwood " (Boolean; default: disabled; Linux 2.4.26/2.6.3 to Linux 2.6.13)" Enable TCP Westwood+ congestion control algorithm. TCP Westwood+ is a sender-side-only modification of the TCP Reno protocol stack that optimizes the performance of TCP congestion control. @@ -985,7 +985,7 @@ TCP Westwood+ significantly increases fairness with respect to TCP Reno in wired networks and throughput over wireless links. .TP .IR tcp_window_scaling " (Boolean; default: enabled; since Linux 2.2)" -.\" Since 2.1.36 +.\" Since Linux 2.1.36 Enable RFC\ 1323 TCP window scaling. This feature allows the use of a large window (> 64\ kB) on a TCP connection, should the other end support it. @@ -999,7 +999,7 @@ is disabled, TCP will not negotiate the use of window scaling with the other end during connection setup. .TP .IR tcp_wmem " (since Linux 2.4)" -.\" Since 2.4.0-test7 +.\" Since Linux 2.4.0-test7 This is a vector of 3 integers: [min, default, max]. These parameters are used by TCP to regulate send buffer sizes. TCP dynamically adjusts the size of the send buffer from the @@ -1096,7 +1096,7 @@ can choose from any of the available congestion-control algorithms above). .TP .BR TCP_CORK " (since Linux 2.2)" -.\" precisely: since 2.1.127 +.\" precisely: since Linux 2.1.127 If set, don't send out partial frames. All queued partial frames are sent when the option is cleared again. This is useful for prepending headers before calling @@ -1112,7 +1112,7 @@ only since Linux 2.5.71. This option should not be used in code intended to be portable. .TP .BR TCP_DEFER_ACCEPT " (since Linux 2.4)" -.\" Precisely: since 2.3.38 +.\" Precisely: since Linux 2.3.38 .\" Useful references: .\" http://www.techrepublic.com/article/take-advantage-of-tcp-ip-options-to-optimize-data-transmission/ .\" http://unix.stackexchange.com/questions/94104/real-world-use-of-tcp-defer-accept @@ -1129,14 +1129,14 @@ The kernel returns a \fIstruct tcp_info\fP as defined in the file This option should not be used in code intended to be portable. .TP .BR TCP_KEEPCNT " (since Linux 2.4)" -.\" Precisely: since 2.3.18 +.\" Precisely: since Linux 2.3.18 The maximum number of keepalive probes TCP should send before dropping the connection. This option should not be used in code intended to be portable. .TP .BR TCP_KEEPIDLE " (since Linux 2.4)" -.\" Precisely: since 2.3.18 +.\" Precisely: since Linux 2.3.18 The time (in seconds) the connection needs to remain idle before TCP starts sending keepalive probes, if the socket option @@ -1145,12 +1145,12 @@ has been set on this socket. This option should not be used in code intended to be portable. .TP .BR TCP_KEEPINTVL " (since Linux 2.4)" -.\" Precisely: since 2.3.18 +.\" Precisely: since Linux 2.3.18 The time (in seconds) between individual keepalive probes. This option should not be used in code intended to be portable. .TP .BR TCP_LINGER2 " (since Linux 2.4)" -.\" Precisely: since 2.3.41 +.\" Precisely: since Linux 2.3.41 The lifetime of orphaned FIN_WAIT2 state sockets. This option can be used to override the system-wide setting in the file .I /proc/sys/net/ipv4/tcp_fin_timeout @@ -1204,7 +1204,7 @@ This option should not be used in code intended to be portable. .TP .BR TCP_SYNCNT " (since Linux 2.4)" -.\" Precisely: since 2.3.18 +.\" Precisely: since Linux 2.3.18 Set the number of SYN retransmits that TCP should send before aborting the attempt to connect. It cannot exceed 255. @@ -1257,7 +1257,7 @@ Further details on the user timeout feature can be found in RFC\ 793 and RFC\ 5482 ("TCP User Timeout Option"). .TP .BR TCP_WINDOW_CLAMP " (since Linux 2.4)" -.\" Precisely: since 2.3.41 +.\" Precisely: since Linux 2.3.41 Bound the size of the advertised window to this value. The kernel imposes a minimum size of SOCK_MIN_RCVBUF/2. This option should not be used in code intended to be @@ -1386,7 +1386,7 @@ It is possible to peek at out-of-band data using the .B MSG_PEEK flag. .PP -Since version 2.4, Linux supports the use of +Since Linux 2.4, Linux supports the use of .B MSG_TRUNC in the .I flags @@ -1522,9 +1522,9 @@ or the generic socket layer may also be returned for TCP. Support for Explicit Congestion Notification, zero-copy .BR sendfile (2), reordering support and some SACK extensions -(DSACK) were introduced in 2.4. +(DSACK) were introduced in Linux 2.4. Support for forward acknowledgement (FACK), TIME_WAIT recycling, -and per-connection keepalive socket options were introduced in 2.3. +and per-connection keepalive socket options were introduced in Linux 2.3. .SH BUGS Not all errors are documented. .PP diff --git a/man7/time.7 b/man7/time.7 index 358bc7f9e5..c10e0a0873 100644 --- a/man7/time.7 +++ b/man7/time.7 @@ -67,10 +67,10 @@ on kernels up to and including 2.4.x, HZ was 100, giving a jiffy value of 0.01 seconds; starting with 2.6.0, HZ was raised to 1000, giving a jiffy of 0.001 seconds. -Since kernel 2.6.13, the HZ value is a kernel +Since Linux 2.6.13, the HZ value is a kernel configuration parameter and can be 100, 250 (the default) or 1000, yielding a jiffies value of, respectively, 0.01, 0.004, or 0.001 seconds. -Since kernel 2.6.20, a further frequency is available: +Since Linux 2.6.20, a further frequency is available: 300, a number that divides evenly for the common video frame rates (PAL, 25 Hz; NTSC, 30 Hz). .PP diff --git a/man7/udp.7 b/man7/udp.7 index 130d16c949..5822bc551f 100644 --- a/man7/udp.7 +++ b/man7/udp.7 @@ -198,7 +198,7 @@ is accumulated into a single datagram that is transmitted when the option is disabled. This option should not be used in code intended to be portable. -.\" FIXME document UDP_ENCAP (new in kernel 2.5.67) +.\" FIXME document UDP_ENCAP (new in Linux 2.5.67) .\" From include/linux/udp.h: .\" UDP_ENCAP_ESPINUDP_NON_IKE draft-ietf-ipsec-nat-t-ike-00/01 .\" UDP_ENCAP_ESPINUDP draft-ietf-ipsec-udp-encaps-06 diff --git a/man7/unix.7 b/man7/unix.7 index f11a70ebc2..b290117fcc 100644 --- a/man7/unix.7 +++ b/man7/unix.7 @@ -519,9 +519,8 @@ to fail with the error .BR EINVAL . .B SCM_MAX_FD has the value 253 -(or 255 in kernels .\" commit bba14de98753cb6599a2dae0e520714b2153522d -before 2.6.38). +(or 255 before Linux 2.6.38). .TP .B SCM_CREDENTIALS Send or receive UNIX credentials. diff --git a/man7/user_namespaces.7 b/man7/user_namespaces.7 index fff6e2caab..b08e6a8f7d 100644 --- a/man7/user_namespaces.7 +++ b/man7/user_namespaces.7 @@ -47,7 +47,7 @@ with the .B CLONE_NEWUSER flag. .PP -The kernel imposes (since version 3.11) a limit of 32 nested levels of +The kernel imposes (since Linux 3.11) a limit of 32 nested levels of .\" commit 8742f229b635bf1c1c84a3dfe5e47c814c20b5c8 user namespaces. .\" FIXME Explain the rationale for this limit. (What is the rationale?) diff --git a/man7/vdso.7 b/man7/vdso.7 index 20e4bc063b..8f69f191ae 100644 --- a/man7/vdso.7 +++ b/man7/vdso.7 @@ -394,7 +394,7 @@ __kernel_sync_dicache_p5 LINUX_2.6.15 .ft P \} .PP -In kernel versions before Linux 5.6, +Before Linux 5.6, .\" commit 654abc69ef2e69712e6d4e8a6cb9292b97a4aa39 the .B CLOCK_REALTIME_COARSE @@ -434,7 +434,7 @@ __kernel_sync_dicache_p5 LINUX_2.6.15 .ft P \} .PP -In kernel versions before Linux 4.16, +Before Linux 4.16, .\" commit 5c929885f1bb4b77f85b1769c49405a0e0f154a1 the .B CLOCK_REALTIME_COARSE diff --git a/man8/ld.so.8 b/man8/ld.so.8 index 5f790323dc..e279be5fae 100644 --- a/man8/ld.so.8 +++ b/man8/ld.so.8 @@ -238,7 +238,7 @@ are delimited by colons or spaces. .B \-\-list List all dependencies and how they are resolved. .TP -.BR \-\-list\-tunables " (since 2.33)" +.BR \-\-list\-tunables " (since glibc 2.33)" Print the names and values of all tunables, along with the minimum and maximum allowed values. .TP @@ -588,7 +588,7 @@ is ignored in secure-execution mode. By default, when searching shared libraries to resolve a symbol reference, the dynamic linker will resolve to the first definition it finds. .IP -Old glibc versions (before 2.2), provided a different behavior: +Old glibc versions (before glibc 2.2), provided a different behavior: if the linker found a symbol that was weak, it would remember that symbol and keep searching in the remaining shared libraries. @@ -639,7 +639,7 @@ Since glibc 2.4, .B LD_ORIGIN_PATH is ignored in secure-execution mode. .TP -.BR LD_POINTER_GUARD " (glibc from 2.4 to 2.22)" +.BR LD_POINTER_GUARD " (from glibc 2.4 to glibc 2.22)" Set to 0 to disable pointer guarding. Any other value enables pointer guarding, which is also the default. Pointer guarding is a security mechanism whereby some pointers to code