diff options
| -rw-r--r-- | Changes | 68 |
1 files changed, 34 insertions, 34 deletions
@@ -167,24 +167,24 @@ mbind.2 changed the "policy" parameter to "mode" throughout the descriptions in an attempt to promote the concept that the memory policy is a tuple consisting of a mode and optional set of nodes. - + rewrite portions of description for clarification. - + clarify interaction of policy with mmap()'d files and shared memory regions, including SHM_HUGE regions. - + defined how "empty set of nodes" specified and what this means for MPOL_PREFERRED. - + mention what happens if local/target node contains no free memory. - + clarify semantics of multiple nodes to BIND policy. Note: subject to change. We'll fix the man pages when/if this happens. added all errors currently returned by sys call. - + added mmap(2), shmget(2), shmat(2) to See Also list. mmap.2 @@ -192,7 +192,7 @@ mprotect.2 Fran�ois Diakhate Add text noting that PROT_WRITE may (and on x86 does) imply PROT_READ. - See Debian bug 441387. + See Debian bug 441387. nfsservctl.2 Aleksandr Koltsoff @@ -219,7 +219,7 @@ reboot.2 sched_setaffinity.2 Samuel Thibault Note what thread is affected if 'pid' is specified - as 0, or as the value returned by getpid(). + as 0, or as the value returned by getpid(). sched_setscheduler.2 Carsten Emde @@ -269,7 +269,7 @@ stat.2 swapon.2 Michael Prokop EINVAL also occurs if target path is on tmpfs or similar. - See Debian bug 435885. + See Debian bug 435885. sync.2 mtk @@ -306,7 +306,7 @@ ffsl.3 fts.3 mtk Removed statement that fts functions are expected to appear - soon in POSIX; it's years old and has not yet come to pass. + soon in POSIX; it's years old and has not yet come to pass. ftw.3 mtk / Geoff Clare @@ -319,11 +319,11 @@ getdate.3 getaddrinfo.3 mtk / Geoff Clare Fixes/improvements for example program. - + gethostbyaddr.3 Mats Wichmann Add documentation for gethostbyaddr_r(). - Plus a few other small fixes. + Plus a few other small fixes. gethostbyname.3 mtk @@ -374,7 +374,7 @@ log1p.3 longjmp.3 Paul Brook / mtk After a call to longjmp(), the values of modified, non-volatile - variables in the function that called setjmp() are unspecified. + variables in the function that called setjmp() are unspecified. makecontext.3 Aleksandr Koltsoff @@ -430,7 +430,7 @@ proc.5 Improve description of num_threads field under /proc/PID/stat. Maxime Vaudequin Fix path error (s%proc/sys%proc/sys/kernel%) in mentions of - /proc/sys/ostype, /proc/sys/osrelease and proc/sys/version. + /proc/sys/ostype, /proc/sys/osrelease and proc/sys/version. Maxime Vaudequin I noticed things to correct and to clarify in subsection "/proc/filesystems" of proc.5: @@ -440,28 +440,28 @@ proc.5 - add an explanation for FS marked with "nodev" - s/mount(1)/mount(8)/, also corrected in section "SEE ALSO" - clarify usage by mount: the current wording may lead to - think /proc/filesystems is always used by mount when no FS - is specified. So, usage of "may" which IMHO is more - appropriate + additional explanations + think /proc/filesystems is always used by mount when no FS + is specified. So, usage of "may" which IMHO is more + appropriate + additional explanations In mount(8) we can see: If no -t option is given, or if the auto type is - specified, mount will try to guess the desired type. - If mount was compiled with the blkid library, the - guessing is done by this library. Otherwise, mount - guesses itself by probing the superblock; if that - does not turn up anything that looks familiar, - mount will try to read the file /etc/filesystems, - or, if that does not exist, /proc/filesystems. - All of the filesystem types listed there will be - tried, except for those that are labeled "nodev" - (e.g., devpts, proc and nfs). If /etc/filesystems - ends in a line with a single * only, mount will - read /proc/filesystems afterwards. + specified, mount will try to guess the desired type. + If mount was compiled with the blkid library, the + guessing is done by this library. Otherwise, mount + guesses itself by probing the superblock; if that + does not turn up anything that looks familiar, + mount will try to read the file /etc/filesystems, + or, if that does not exist, /proc/filesystems. + All of the filesystem types listed there will be + tried, except for those that are labeled "nodev" + (e.g., devpts, proc and nfs). If /etc/filesystems + ends in a line with a single * only, mount will + read /proc/filesystems afterwards. Samuel Thibault Since linux 2.6.11, /proc/stat has an eighth value for cpu - lines: stolen time, which is the time spent in other operating - systems when running in a virtualized environment. + lines: stolen time, which is the time spent in other operating + systems when running in a virtualized environment. arp.7 Updated BUGS text referring to jiffies; refer to time.7 instead. @@ -476,7 +476,7 @@ hier.7 - missing period for /media and /mnt - /mnt description is not totally correct, it is true for some distributions but in others /mnt is used as a temporary FS - mount point, as it is specified by FHS: + mount point, as it is specified by FHS: http://www.pathname.com/fhs/pub/fhs-2.3.html# MNTMOUNTPOINTFORATEMPORARILYMOUNT - s/X-Windows/X-Window/ (3 occurrences) @@ -497,8 +497,8 @@ pthreads.7 socket.7 mtk, after a note by Andi Kleen Clarify that SO_SNDTIMEO and SO_RCVTIMEO only have effect for - socket I/O calls; not for multiplexing system calls like - select() and poll(). + socket I/O calls; not for multiplexing system calls like + select() and poll(). time.7 mtk |