commit man-pages for openSUSE:Factory
![](https://seccdn.libravatar.org/avatar/e2145bc5cf53dda95c308a3c75e8fef3.jpg?s=120&d=mm&r=g)
Hello community,
here is the log from the commit of package man-pages for openSUSE:Factory checked in at 2013-05-27 11:52:02
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/man-pages (Old)
and /work/SRC/openSUSE:Factory/.man-pages.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "man-pages"
Changes:
--------
--- /work/SRC/openSUSE:Factory/man-pages/man-pages.changes 2013-03-25 20:40:50.000000000 +0100
+++ /work/SRC/openSUSE:Factory/.man-pages.new/man-pages.changes 2013-05-27 11:52:04.000000000 +0200
@@ -1,0 +2,191 @@
+Thu May 2 10:14:33 CEST 2013 - pgajdos@suse.cz
+
+- update to version 3.51
+ * Newly documented interfaces in existing pages
+ sched_rr_get_interval.2
+ Document /proc/sys/kernel/sched_rr_timeslice_ms
+ proc.5
+ Document /proc/[pid]/map_files directory
+ This directory was added in Linux v3.3 and provides info about
+ files being mmap-ed in a way very similar to how /proc/[pid]/fd
+ works.
+ v2: Added examples of how links look like and noted dependency
+ on kernel config option CONFIG_CHECKPOINT_RESTORE.
+ Document /proc/sys/kernel/shm_rmid_forced
+ capabilities.7
+ Document /proc/sys/kernel/cap_last_cap
+ * Global changes
+ * Various pages
+ Global fix: fix placement of word "only"
+ * Various pages
+ License headers: consistent format
+ * Various pages
+ Global fix: s/since kernel/since Linux/
+ * Various System V IPC pages in Section 2
+ Add "System V" to .TH line and text
+ Make it clear that these pages relate to System V IPC,
+ not POSIX IPC.
+ * Changes to individual pages
+ access.2
+ Clarify RETURN VALUE for F_OK
+ See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705293
+ alarm.2
+ Correct the description of behavior when 'seconds' is 0
+ clone.2
+ Add prototype for syscall to SYNOPSIS
+ And further clarify the distinction between the system call
+ and the wrapper function in the introductory text.
+ Update feature test macro requirements
+ The requirements quietly changed changed in glibc 2.14
+ See also http://www.sourceware.org/bugzilla/show_bug.cgi?id=4749
+ Clarify differences between clone2() syscall and wrapper function
+ Note those architectures where the sys_clone argument order differs
+ Add short subsection noting that blackfin, m68k, and sparc are different
+ Move clone2() text to subsection in description
+ The description of ia64 clone2() should follow the discussion
+ of the raw system call interface.
+ Change subhead for ia64 discussion
+ getcpu.2
+ Recommend that 'tcache' should be specified as NULL nowadays
+ io_cancel.2
+ Improve description
+ io_destroy.2
+ Improve description
+ The description was rather vague, citing a "list of I/O contexts"
+ and stating that it "can" cancel outstanding requests. This
+ update makes things more concrete so that the reader knows exactly
+ what's going on.
+ io_getevents.2
+ The 'timeout' argument is not updated
+ I looked back through the kernel code, and the timeout was
+ never updated in any case. I've submitted a patch upstream
+ to change the comment above io_getevents.
+ io_setup.2
+ Clarify nr_events
+ nr_events is technically the number of completion events that can
+ be stored in the completion ring. The wording of the man page:
+ "capable of receiving at least nr_events" seems dubious to me,
+ only because I worry that folks might interpret that to mean
+ 'nr_events' total, instead of 'nr_events' concurrently.
+ Further, I've added information on where to find the per-user
+ limit on 'nr_events', /proc/sys/fs/aio-max-nr. Let me know if
+ you think that is not relevant.
+ listxattr.2
+ Explain use of 'size' argument
+ lseek.2
+ _GNU_SOURCE must be defined to get SEEK_DATE and SEEK_HOLE definitions
+ See http://sourceware.org/bugzilla/show_bug.cgi?id=15312
+ mmap.2
+ Add pointers to relevant /proc files described in proc(5)
+ posix_fadvise.2
+ pread.2
+ readahead.2
+ sync_file_range.2
+ truncate.2
+ Refer to syscall(2) for ABI semantics on certain 32-bit architectures
+ Also: in sync_file_range.2 and posix_fadvise.2 remove description
+ of conventional calling signature as flawed, and in
+ posix_fadvise.2, de-emphasize focus on ARM, and rather phrase
+ as a more general discussion of certain architectures.
+ readdir.2
+ readdir(2) doesn't exist on x86-64
+ semop.2
+ Clarify the discussion of 'semadj'
+ shmctl.2
+ Refer to proc(5) for description of /proc/sys/kernel/shm_rmid_forced
+ syscall.2
+ Add notes that caution users when passing arguments to syscall()
+ For example, passing 'long long' on ARM-32 requires special
+ treatment.
+ Document the exact calling convention for architecture system calls
+ Add PA-RISC details under calling conventions
+ Refine discussion of ARM and other ABIs
+ syscalls.2
+ Update kernel version number at start of list
+ umask.2
+ SEE ALSO: add acl(5)
+ unshare.2
+ Update feature test macro requirements
+ The requirements quietly changed changed in glibc 2.14
+ See also http://www.sourceware.org/bugzilla/show_bug.cgi?id=4749
+ fopencookie.3
+ Correct definition of cookie_io_functions_t
+ pthread_setname_np.3
+ The thread argument is passed in by value
+ readir.3
+ seekdir.3
+ telldir.3
+ Eliminate the implication that these functions deal with "offsets"
+ The directory position dealt with by the readdir() and
+ friends is not a simple file offset in modern file systems.
+ Typically, it is some kind of cookie value. Add text and
+ make other changes to these pages to eliminate the
+ implication that this is an offset, and warn the reader
+ that directory positions should be treated strictly as
+ opaque values.
+ In the process, rename the 'offset' argument of seekdir(3)
+ to 'loc', and add some text to readdir(3) to note that
+ the 'd_off' field is the same value returned by telldir(3)
+ at the current directory position.
+ See also https://lwn.net/Articles/544298/
+ scalb.3
+ Fix prototypes for scalbf() and scalbl()
+ sched_getcpu.3
+ Update feature test macro requirements
+ The requirements quietly changed changed in glibc 2.14
+ See also http://www.sourceware.org/bugzilla/show_bug.cgi?id=4749
+ ualarm.3
+ Add note on the behavior when 'usecs' is zero
+ POSIX.1-2001 does not specify the behavior in this case
+ and no other system that I checked documented the behavior.
+ Probably, most or all systems do what Linux does in this
+ case: cancel any pending alarm, just as alarm(0) does.
+ Add that info in NOTES.
+ elf.5
+ Add byte positions for all EI_xxx fields
+ When describing e_ident, most of the EI_xxx defines mention the
+ exact byte number. This is useful when manually hacking an ELF
+ with a hex editor. However, the last few fields don't do this,
+ which means you have to count things up yourself.
+ Add a single word to each so you don't have to do that.
+ proc.5
+ Refer to sched_rr_get_interval(2) for info on sched_rr_timeslice_ms
+ Since Linux 3.9, /proc/sys/kernel/sched_rr_timeslice_ms can
+ be used to change the SCHED_RR quantum.
+ SEE ALSO: Add sysctl(8)
+ Simplify the example of printing out environ
+ The binutils package contains a very handy utility to
+ print out null-byte delimited strings from a file. This
+ can replace a rather complex expression with cat(1)
+ provided as an example for printing out /proc/[pid]/environ.
+ Update /proc/PID/maps example
+ Update to 64-bit example that includes "[heap]", "[stack],
+ and "[vdso]"
+ Formatting fixes for /proc/PID/maps
+ Document the "pathname" field of /proc/PID/maps
+ Add reference to capabilities(7) for /proc/sys/kernel/cap_last_cap
+ /proc/PID/maps: add a reference to mmap(2)
+ ip.7
+ Document IP_MULTICAST_ALL
+ This commit adds documentation for the IP_MULTICAST_ALL socket
+ option.
+ The option was added to the Linux kernel in 2.6.31:
+ Author Nivedita Singhvi
participants (1)
-
root@hilbert.suse.de