From e7a175390efb0af63fc5985818bf5d921b2d7440 Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Tue, 12 Aug 2008 10:26:53 +0000 Subject: [PATCH] Removed tabs --- Changes | 170 ++++++++++++++++++++++++++++---------------------------- 1 file changed, 85 insertions(+), 85 deletions(-) diff --git a/Changes b/Changes index c97b28ef8..bb8c85a40 100644 --- a/Changes +++ b/Changes @@ -37,18 +37,18 @@ New and rewritten pages clock_getcpuclockid.3 mtk New page documenting the clock_getcpuclockid() library function, - available since glibc 2.2. + available since glibc 2.2. numactl.2 Christoph Lameter, various edits and improvements by mtk Documentation of the move_pages() system call. This page was formerly part of the numactl package, but really - belongs in man-pages (since it describes a kernel interface). + belongs in man-pages (since it describes a kernel interface). udplite.7 Gerrit Renker - Document the Linux implementation of the UDP-Lite protocol, - new in Linux 2.6.20. + Document the Linux implementation of the UDP-Lite protocol, + new in Linux 2.6.20. Newly documented interfaces in existing pages @@ -58,9 +58,9 @@ proc.5 Christoph Lameter, minor edits and improvements by mtk Documentation of the /proc/PID/numa_maps file. This material was formerly the numa_maps.5 page in the numactl - package, but really belongs in man-pages (since it describes - a kernel interface). - + package, but really belongs in man-pages (since it describes + a kernel interface). + Global changes -------------- @@ -91,9 +91,9 @@ unix.7 x25.7 mtk s/PF_/AF_/ for socket family constants. Reasons: the AF_ and - PF_ constants have always had the same values; there never has - been a protocol family that had more than one address family, - and POSIX.1-2001 only specifies the AF_* constants. + PF_ constants have always had the same values; there never has + been a protocol family that had more than one address family, + and POSIX.1-2001 only specifies the AF_* constants. Typographical or grammatical errors have been corrected in several @@ -106,21 +106,21 @@ Changes to individual pages execve.2 mtk The floating-point environment is reset to the default - during an execve(). + during an execve(). getitimer.2 mtk CONFORMING TO: POSIX.1-2008 marks getitimer() and setitimer() - obsolete. + obsolete. get_mempolicy.2 Lee Schermerhorn Misc cleanup of get_mempolicy(2): - + mention that any mode flags will be saved with mode. - I don't bother to document mode flags here because we - already have a pointer to set_mempolicy(2) for more info - on memory policy. mode flags are discussed there. - + remove some old, obsolete [IMO] NOTES and 'roff comments. + + mention that any mode flags will be saved with mode. + I don't bother to document mode flags here because we + already have a pointer to set_mempolicy(2) for more info + on memory policy. mode flags are discussed there. + + remove some old, obsolete [IMO] NOTES and 'roff comments. Lee Schermerhorn Update the get_mempolicy(2) man page to add in the description of the MPOL_F_MEMS_ALLOWED flag, added in 2.6.23. @@ -131,50 +131,50 @@ get_mempolicy.2 mbind.2 Lee Schermerhorn Fix error conditions, now that the kernel silently ignores - nodes outside the task's cpuset, as long as one valid node - remains. + nodes outside the task's cpuset, as long as one valid node + remains. - Now that cpuset man page exists, we can refer to it. Remove - stale comment regarding lack thereof. + Now that cpuset man page exists, we can refer to it. Remove + stale comment regarding lack thereof. Lee Schermerhorn Add brief discussion of mode flags. Lee Schermerhorn - Attempt to clarify discussion of MPOL_DEFAULT. + Attempt to clarify discussion of MPOL_DEFAULT. mtk Fix URI reference for libnuma. mprotect.2 mtk / Maxin John Remove EFAULT from errors. Under ENOMEM error, note that - EFAULT was the error produced in some cases for kernels before - 2.4.19. - + EFAULT was the error produced in some cases for kernels before + 2.4.19. + msgctl.2 mtk, after a note from Filippo Santovito In the ipc_perm structure definition, some fields were - incorrectly named: s/key/__key/ and s/seq/__seq/. + incorrectly named: s/key/__key/ and s/seq/__seq/. set_mempolicy.2 Lee Schermerhorn Fix up the error return for nodemask containing nodes disallowed by - the process' current cpuset. Disallowed nodes are now silently ignored, - as long as the nodemask contains at least one node that is on-line, - allowed by the process' cpuset and has memory. + the process' current cpuset. Disallowed nodes are now silently ignored, + as long as the nodemask contains at least one node that is on-line, + allowed by the process' cpuset and has memory. - Now that we have a cpuset man page, we can refer to cpusets directly - in the man page text. + Now that we have a cpuset man page, we can refer to cpusets directly + in the man page text. Lee Schermerhorn Another attempt to rationalize description of MPOL_DEFAULT. - Since ~2.6.25, the system default memory policy is "local allocation". - MPOL_DEFAULT itself is a request to remove any non-default policy and - "fall back" to the surrounding context. Try to say that without delving - into implementation details. + Since ~2.6.25, the system default memory policy is "local allocation". + MPOL_DEFAULT itself is a request to remove any non-default policy and + "fall back" to the surrounding context. Try to say that without delving + into implementation details. Lee Schermerhorn - Add discussion of mempolicy mode flags to set_mempolicy(2). - This adds another reason for EINVAL. + Add discussion of mempolicy mode flags to set_mempolicy(2). + This adds another reason for EINVAL. setpgid.2 mtk @@ -183,23 +183,23 @@ setpgid.2 semctl.2 mtk, after a note from Filippo Santovito In the ipc_perm structure definition, some fields were - incorrectly named: s/key/__key/ and s/seq/__seq/. + incorrectly named: s/key/__key/ and s/seq/__seq/. shmctl.2 Filippo Santovito / mtk In the ipc_perm structure definition, some fields were - incorrectly named: s/key/__key/ and s/seq/__seq/. + incorrectly named: s/key/__key/ and s/seq/__seq/. utime.2 mtk CONFORMING TO: POSIX.1-2008 marks utime() obsolete. - CONFORMING TO: POSIX.1-2008 removes the POSIX.1-2001 LEGACY - marking of utimes(), so mention of this point has been - removed from the page. + CONFORMING TO: POSIX.1-2008 removes the POSIX.1-2001 LEGACY + marking of utimes(), so mention of this point has been + removed from the page. vfork.2 mtk - CONFORMING TO: POSIX.1-2008 removes the specification of vfork(). + CONFORMING TO: POSIX.1-2008 removes the specification of vfork(). atan2.3 Fabian Kreutz @@ -207,21 +207,21 @@ atan2.3 bcmp.3 mtk - CONFORMING TO: POSIX.1-2008 removes the specification of bcmp(). + CONFORMING TO: POSIX.1-2008 removes the specification of bcmp(). bsd_signal.3 mtk CONFORMING TO: POSIX.1-2008 removes the specification ofcw - bsd_signal(). + bsd_signal(). bzero.3 mtk - CONFORMING TO: POSIX.1-2008 removes the specification of bzero(). + CONFORMING TO: POSIX.1-2008 removes the specification of bzero(). cexp2.3 mtk AVAILABILITY: These functions are still not in glibc - as at version 2.8. + as at version 2.8. clock_getres.3 mtk @@ -230,12 +230,12 @@ clock_getres.3 clog2.3 mtk AVAILABILITY: These functions are still not in glibc - as at version 2.8. + as at version 2.8. ctime.3 mtk POSIX.1-2008 marks asctime(), asctime_r(), ctime(), and ctime_r() - as obsolete. + as obsolete. dprintf.3 mtk @@ -244,11 +244,11 @@ dprintf.3 ecvt.3 mtk CONFORMING TO: POSIX.1-2008 removes the specifications of - ecvt() and fcvt(). + ecvt() and fcvt(). ftime.3 mtk - CONFORMING TO: POSIX.1-2008 removes the specification of ftime(). + CONFORMING TO: POSIX.1-2008 removes the specification of ftime(). ftw.3 mtk @@ -261,25 +261,25 @@ gcvt.3 getcwd.3 Reuben Thomas / mtk Clarify description of getcwd() for buf==NULL case; - CONFORMING TO: According to POSIX.1, the behavior of getcwd() + CONFORMING TO: According to POSIX.1, the behavior of getcwd() is unspecified for the buf==NULL case. mtk Add an introductory paragraph giving an overview of what these - functions do. - Fix error in description of getwd(): it does not truncate the + functions do. + Fix error in description of getwd(): it does not truncate the pathname; rather, it gives an error if the pathname exceeds - PATH_MAX bytes. + PATH_MAX bytes. Rewrote RETURN VALUE section. Add EINVAL ENAMETOOLONG errors for getwd(). - Various other clarifications and wording fixes. - CONFORMING TO: POSIX.1-2001 does not define any errors for - getwd(). + Various other clarifications and wording fixes. + CONFORMING TO: POSIX.1-2001 does not define any errors for + getwd(). CONFORMING TO: POSIX.1-2008 removes the specification of getwd(). gethostbyname.3 mtk CONFORMING TO: POSIX.1-2008 removes the specifications of - gethostbyname(), gethostbyaddr(), and h_errno. + gethostbyname(), gethostbyaddr(), and h_errno. gets.3 mtk @@ -294,7 +294,7 @@ iconv_open.3 index.3 mtk CONFORMING TO: POSIX.1-2008 removes the specifications of - index() and rindex(). + index() and rindex(). isalpha.3 mtk @@ -303,7 +303,7 @@ isalpha.3 makecontext.3 mtk CONFORMING TO: POSIX.1-2008 removes the specifications of - makecontext() and swapcontext(). + makecontext() and swapcontext(). memchr.3 mtk @@ -320,7 +320,7 @@ mktemp.3 nextafter.3 mtk BUGS: In glibc 2.5 and earlier these functions do not raise an - FE_UNDERFLOW exception on underflow. + FE_UNDERFLOW exception on underflow. opendir.3 mtk @@ -337,11 +337,11 @@ siginterrupt.3 sigset.3 mtk CONFORMING TO: POSIX.1-2008 marks sighold(), sigignore(), - sigpause(), sigrelse(), and sigset() as obsolete. + sigpause(), sigrelse(), and sigset() as obsolete. strchr.3 mtk - VERSIONS: strchrnul() since glibc 2.1.1. + VERSIONS: strchrnul() since glibc 2.1.1. tempnam.3 mtk @@ -370,9 +370,9 @@ usleep.3 standards.7 mtk Updated details for POSIX.1-2008, and noted that if - POSIX.1-2001 is listed in the CONFORMING TO section of a man - page, then the read can assume that the interface is also - specified in POSIX.1-2008, unless otherwise noted. + POSIX.1-2001 is listed in the CONFORMING TO section of a man + page, then the read can assume that the interface is also + specified in POSIX.1-2008, unless otherwise noted. time.7 mtk @@ -439,53 +439,53 @@ tgamma.3 trunc.3 mtk Added VERSIONS section noting that these functions first - appeared in glibc in version 2.1. + appeared in glibc in version 2.1. cosh.3 mtk BUGS: In glibc 2.3.4 and earlier, an FE_OVERFLOW exception is not - raised when an overflow occurs. + raised when an overflow occurs. fenv.3 mtk / Fabian Kreuz Provide more detail in the description of rounding modes. - Add text describing FLT_ROUNDS (formerly in fma.3). + Add text describing FLT_ROUNDS (formerly in fma.3). Add BUGS section pointing out the FLT_ROUNDS does not reflect - changes by fesetround(). + changes by fesetround(). fma.3 mtk Remove text about FLT_ROUNDS, replacing with a cross-reference - to fenv(3). + to fenv(3). fpclassify.3 mtk CONFORMING TO: Note that the standards provide a weaker guarantee - for the return value of isinf(). + for the return value of isinf(). log.3 mtk BUGS: In glibc 2.5 and earlier, log(nan("")) produces a bogus - FE_INVALID exception. + FE_INVALID exception. lround.3 mtk - Add reference to fenv(3) for discussion of current rounding mode. + Add reference to fenv(3) for discussion of current rounding mode. pow.3 mtk BUGS: described buggy NaN return when x is negative and y is large. - See also: http://sources.redhat.com/bugzilla/show_bug.cgi?id=3866. - BUGS: Note the bogus FE_INVALID exception that occurred in glibc - 2.3.2 and earlier on overflow and underflow. + See also: http://sources.redhat.com/bugzilla/show_bug.cgi?id=3866. + BUGS: Note the bogus FE_INVALID exception that occurred in glibc + 2.3.2 and earlier on overflow and underflow. remainder.3 mtk - Add reference to fenv(3) for discussion of current rounding mode. + Add reference to fenv(3) for discussion of current rounding mode. round.3 mtk - Add reference to fenv(3) for discussion of current rounding mode. + Add reference to fenv(3) for discussion of current rounding mode. scalb.3 mtk @@ -493,16 +493,16 @@ scalb.3 tgamma.3 mtk - BUGS: In glibc 2.3.3, tgamma(+-0) produced a domain error - instead of a pole error. + BUGS: In glibc 2.3.3, tgamma(+-0) produced a domain error + instead of a pole error. y0.3 mtk In glibc 2.3.2 and earlier, these functions do not raise an - FE_INVALID exception for a domain error. + FE_INVALID exception for a domain error. math_error.7 mtk Rewrite introductory paragraph. - Point out that a NaN is commonly returned by functions that report - a domain error. + Point out that a NaN is commonly returned by functions that report + a domain error.