Author: aurel32 Date: 2007-05-30 13:20:20 +0000 (Wed, 30 May 2007) New Revision: 2318
Modified: glibc-doc-reference/branches/glibc-2.6/debian/README.source glibc-doc-reference/branches/glibc-2.6/debian/changelog glibc-doc-reference/branches/glibc-2.6/debian/copyright glibc-doc-reference/branches/glibc-2.6/manual/Makefile glibc-doc-reference/branches/glibc-2.6/manual/argp.texi glibc-doc-reference/branches/glibc-2.6/manual/charset.texi glibc-doc-reference/branches/glibc-2.6/manual/conf.texi glibc-doc-reference/branches/glibc-2.6/manual/errno.texi glibc-doc-reference/branches/glibc-2.6/manual/filesys.texi glibc-doc-reference/branches/glibc-2.6/manual/lang.texi glibc-doc-reference/branches/glibc-2.6/manual/maint.texi glibc-doc-reference/branches/glibc-2.6/manual/memory.texi glibc-doc-reference/branches/glibc-2.6/manual/message.texi glibc-doc-reference/branches/glibc-2.6/manual/resource.texi glibc-doc-reference/branches/glibc-2.6/manual/search.texi glibc-doc-reference/branches/glibc-2.6/manual/signal.texi glibc-doc-reference/branches/glibc-2.6/manual/startup.texi glibc-doc-reference/branches/glibc-2.6/manual/stdio.texi glibc-doc-reference/branches/glibc-2.6/manual/string.texi glibc-doc-reference/branches/glibc-2.6/manual/sysinfo.texi glibc-doc-reference/branches/glibc-2.6/manual/syslog.texi glibc-doc-reference/branches/glibc-2.6/manual/time.texi Log: * New upstream version. Modified: glibc-doc-reference/branches/glibc-2.6/debian/README.source =================================================================== --- glibc-doc-reference/branches/glibc-2.6/debian/README.source 2007-05-30 13:16:34 UTC (rev 2317) +++ glibc-doc-reference/branches/glibc-2.6/debian/README.source 2007-05-30 13:20:20 UTC (rev 2318) @@ -1,6 +1,6 @@ glibc-doc-reference_<version>.orig.tar.gz contains the glibc-<version>/manual directory of upstream http://ftp.gnu.org/gnu/glibc/glibc-<version>.tar.bz2 It has been created with the following commands: - bzip2 -c -d glibc-2.5.tar.bz2 |\ - tarcust -x 'glibc-2.5/(?!manual).*' |\ - gzip -9 > glibc-doc-reference_2.5.orig.tar.gz + bzip2 -c -d glibc-2.6.tar.bz2 |\ + tarcust -x 'glibc-2.6/(?!manual).*' |\ + gzip -9 > glibc-doc-reference_2.6.orig.tar.gz Modified: glibc-doc-reference/branches/glibc-2.6/debian/changelog =================================================================== --- glibc-doc-reference/branches/glibc-2.6/debian/changelog 2007-05-30 13:16:34 UTC (rev 2317) +++ glibc-doc-reference/branches/glibc-2.6/debian/changelog 2007-05-30 13:20:20 UTC (rev 2318) @@ -1,3 +1,9 @@ +glibc-doc-reference (2.6-1) experimental; urgency=low + + * New upstream version. + + -- Aurelien Jarno <[EMAIL PROTECTED]> Wed, 30 May 2007 14:25:25 +0200 + glibc-doc-reference (2.5-2) unstable; urgency=low * Upload to unstable (closes: bug#418893). Modified: glibc-doc-reference/branches/glibc-2.6/debian/copyright =================================================================== --- glibc-doc-reference/branches/glibc-2.6/debian/copyright 2007-05-30 13:16:34 UTC (rev 2317) +++ glibc-doc-reference/branches/glibc-2.6/debian/copyright 2007-05-30 13:20:20 UTC (rev 2318) @@ -1,11 +1,11 @@ -This is the Debian prepackaged version of the GNU C Library Reference Manual version 2.5 +This is the Debian prepackaged version of the GNU C Library Reference Manual version 2.6 For licensing reasons, the GNU C Library Reference Manual cannot be distributed in Debian and has to be shipped in the non-free section. It has been repackaged by the GNU Libc Maintainers <[email protected]> from the following source: - <ftp://sources.redhat.com/pub/glibc/releases/glibc-2.5.tar.bz2> + <ftp://sources.redhat.com/pub/glibc/releases/glibc-2.6.tar.bz2> The following applies to the GNU C Library Reference Manual (libc.info): Modified: glibc-doc-reference/branches/glibc-2.6/manual/Makefile =================================================================== --- glibc-doc-reference/branches/glibc-2.6/manual/Makefile 2007-05-30 13:16:34 UTC (rev 2317) +++ glibc-doc-reference/branches/glibc-2.6/manual/Makefile 2007-05-30 13:20:20 UTC (rev 2318) @@ -58,7 +58,7 @@ pipe socket terminal syslog math arith time \ resource setjmp signal startup process job nss \ users sysinfo conf crypt debug) -add-chapters = $(wildcard $(foreach d, $(add-ons), ../$d/$d.texi)) +add-chapters = linuxthreads.texi appendices = lang.texi header.texi install.texi maint.texi contrib.texi \ freemanuals.texi Modified: glibc-doc-reference/branches/glibc-2.6/manual/argp.texi =================================================================== --- glibc-doc-reference/branches/glibc-2.6/manual/argp.texi 2007-05-30 13:16:34 UTC (rev 2317) +++ glibc-doc-reference/branches/glibc-2.6/manual/argp.texi 2007-05-30 13:20:20 UTC (rev 2318) @@ -832,7 +832,7 @@ @item ARGP_LONG_ONLY Use the gnu getopt `long-only' rules for parsing arguments. This allows long-options to be recognized with only a single @samp{-} -(i.e. @samp{-help}). This results in a less useful interface, and its +(i.e., @samp{-help}). This results in a less useful interface, and its use is discouraged as it conflicts with the way most GNU programs work as well as the GNU coding standards. Modified: glibc-doc-reference/branches/glibc-2.6/manual/charset.texi =================================================================== --- glibc-doc-reference/branches/glibc-2.6/manual/charset.texi 2007-05-30 13:16:34 UTC (rev 2317) +++ glibc-doc-reference/branches/glibc-2.6/manual/charset.texi 2007-05-30 13:20:20 UTC (rev 2318) @@ -207,7 +207,7 @@ than one byte, they are effected by byte-ordering. Thus, machines with different endianesses would see different values when accessing the same data. This byte ordering concern also applies for communication protocols -that are all byte-based and, thereforet require that the sender has to +that are all byte-based and therefore require that the sender has to decide about splitting the wide character in bytes. A last (but not least important) point is that wide characters often require more storage space than a customized byte-oriented character set. @@ -737,7 +737,7 @@ multibyte character, the number of bytes belonging to this multibyte character byte sequence is returned. -If the the first @var{n} bytes possibly form a valid multibyte +If the first @var{n} bytes possibly form a valid multibyte character but the character is incomplete, the return value is @code{(size_t) -2}. Otherwise the multibyte character sequence is invalid and the return value is @code{(size_t) -1}. @@ -2231,7 +2231,7 @@ same as the one required for UCS-4. This is done for performance reasons as one does not want to perform unnecessary byte-swapping operations if one is not interested in actually seeing the result in UCS-4. To avoid -trouble with endianess, the internal representation consistently is named +trouble with endianness, the internal representation consistently is named @code{INTERNAL} even on big-endian systems where the representations are identical. Modified: glibc-doc-reference/branches/glibc-2.6/manual/conf.texi =================================================================== --- glibc-doc-reference/branches/glibc-2.6/manual/conf.texi 2007-05-30 13:16:34 UTC (rev 2317) +++ glibc-doc-reference/branches/glibc-2.6/manual/conf.texi 2007-05-30 13:20:20 UTC (rev 2318) @@ -1455,11 +1455,6 @@ Inquire about the value of @code{_POSIX_PRIO_IO}. @comment unistd.h [EMAIL PROTECTED] POSIX.1g [EMAIL PROTECTED] _PC_SOCK_MAXBUF -Inquire about the value of @code{_POSIX_PIPE_BUF}. - [EMAIL PROTECTED] unistd.h @comment LFS @item _PC_FILESIZEBITS Inquire about the availability of large files on the filesystem. Modified: glibc-doc-reference/branches/glibc-2.6/manual/errno.texi =================================================================== --- glibc-doc-reference/branches/glibc-2.6/manual/errno.texi 2007-05-30 13:16:34 UTC (rev 2317) +++ glibc-doc-reference/branches/glibc-2.6/manual/errno.texi 2007-05-30 13:20:20 UTC (rev 2318) @@ -1434,7 +1434,7 @@ arguments required for the format can follow the @var{format} parameter. Just like @code{perror}, @code{error} also can report an error code in textual form. But unlike @code{perror} the error value is explicitly -passed to the function in the @var{errnum} parameter. This elimintates +passed to the function in the @var{errnum} parameter. This eliminates the problem mentioned above that the error reporting function must be called immediately after the function causing the error since otherwise @code{errno} might have a different value. @@ -1479,7 +1479,7 @@ If the global variable @code{error_one_per_line} is set to a non-zero value @code{error_at_line} will avoid printing consecutive messages for -the same file anem line. Repetition which are not directly following +the same file and line. Repetition which are not directly following each other are not caught. Just like @code{error} this function only returned if @var{status} is Modified: glibc-doc-reference/branches/glibc-2.6/manual/filesys.texi =================================================================== --- glibc-doc-reference/branches/glibc-2.6/manual/filesys.texi 2007-05-30 13:16:34 UTC (rev 2317) +++ glibc-doc-reference/branches/glibc-2.6/manual/filesys.texi 2007-05-30 13:20:20 UTC (rev 2318) @@ -131,7 +131,7 @@ @comment GNU @deftypefun {char *} get_current_dir_name (void) @vindex PWD -This @code{get_current_dir_name} function is bascially equivalent to +This @code{get_current_dir_name} function is basically equivalent to @[EMAIL PROTECTED] (NULL, 0)}}. The only difference is that the value of the @code{PWD} variable is returned if this value is correct. This is a subtle difference which is visible if the path described by the @@ -917,7 +917,7 @@ the return value of @code{ftw}. When the sources are compiled with @code{_FILE_OFFSET_BITS == 64} on a -32-bit system this function is in fact @code{ftw64}, i.e. the LFS +32-bit system this function is in fact @code{ftw64}, i.e., the LFS interface transparently replaces the old interface. @end deftypefun @@ -990,7 +990,7 @@ then that value is returned. When the sources are compiled with @code{_FILE_OFFSET_BITS == 64} on a -32-bit system this function is in fact @code{nftw64}, i.e. the LFS +32-bit system this function is in fact @code{nftw64}, i.e., the LFS interface transparently replaces the old interface. @end deftypefun @@ -1434,7 +1434,7 @@ One useful feature of @code{rename} is that the meaning of @var{newname} changes ``atomically'' from any previously existing file by that name to -its new meaning (i.e. the file that was called @var{oldname}). There is +its new meaning (i.e., the file that was called @var{oldname}). There is no instant at which @var{newname} is non-existent ``in between'' the old meaning and the new meaning. If there is a system crash during the operation, it is possible for both names to still exist; but @@ -3104,7 +3104,7 @@ This function is reentrant. When the sources are compiled with @code{_FILE_OFFSET_BITS == 64} on a -32-bit system this function is in fact @code{tmpfile64}, i.e. the LFS +32-bit system this function is in fact @code{tmpfile64}, i.e., the LFS interface transparently replaces the old interface. @end deftypefun Modified: glibc-doc-reference/branches/glibc-2.6/manual/lang.texi =================================================================== --- glibc-doc-reference/branches/glibc-2.6/manual/lang.texi 2007-05-30 13:16:34 UTC (rev 2317) +++ glibc-doc-reference/branches/glibc-2.6/manual/lang.texi 2007-05-30 13:20:20 UTC (rev 2318) @@ -1274,7 +1274,7 @@ @comment ISO @deftypefn {Macro} size_t offsetof (@var{type}, @var{member}) This expands to a integer constant expression that is the offset of the -structure member named @var{member} in a the structure type @var{type}. +structure member named @var{member} in the structure type @var{type}. For example, @code{offsetof (struct s, elem)} is the offset, in bytes, of the member @code{elem} in a @code{struct s}. Modified: glibc-doc-reference/branches/glibc-2.6/manual/maint.texi =================================================================== --- glibc-doc-reference/branches/glibc-2.6/manual/maint.texi 2007-05-30 13:16:34 UTC (rev 2317) +++ glibc-doc-reference/branches/glibc-2.6/manual/maint.texi 2007-05-30 13:20:20 UTC (rev 2318) @@ -156,7 +156,7 @@ to look for a system-dependent version of a file that's not in @file{generic}. This means that any system-dependent source file must have an analogue in @file{generic}, even if the routines defined by that -file are not implemented on other platforms. Second. the @file{generic} +file are not implemented on other platforms. Second, the @file{generic} version of a system-dependent file is used if the makefiles do not find a version specific to the system you're compiling for. Modified: glibc-doc-reference/branches/glibc-2.6/manual/memory.texi =================================================================== --- glibc-doc-reference/branches/glibc-2.6/manual/memory.texi 2007-05-30 13:16:34 UTC (rev 2317) +++ glibc-doc-reference/branches/glibc-2.6/manual/memory.texi 2007-05-30 13:20:20 UTC (rev 2318) @@ -31,7 +31,7 @@ There are a lot of different ways systems organize memory, but in a typical one, each process has one linear virtual address space, with addresses running from zero to some huge maximum. It need not be -contiguous; i.e. not all of these addresses actually can be used to +contiguous; i.e., not all of these addresses actually can be used to store data. The virtual memory is divided into pages (4 kilobytes is typical). @@ -1065,7 +1065,7 @@ @item int keepcost This is the size of the top-most releasable chunk that normally -borders the end of the heap (i.e. the high end of the virtual address +borders the end of the heap (i.e., the high end of the virtual address space's data segment). @end table @@ -2407,7 +2407,7 @@ @cindex paging You can tell the system to associate a particular virtual memory page -with a real page frame and keep it that way --- i.e. cause the page to +with a real page frame and keep it that way --- i.e., cause the page to be paged in if it isn't already and mark it so it will never be paged out and consequently will never cause a page fault. This is called @dfn{locking} a page. @@ -2467,7 +2467,7 @@ paging rule is: If a frame backs at least one locked page, don't page it out. -Memory locks do not stack. I.e. you can't lock a particular page twice +Memory locks do not stack. I.e., you can't lock a particular page twice so that it has to be unlocked twice before it is truly unlocked. It is either locked or it isn't. Modified: glibc-doc-reference/branches/glibc-2.6/manual/message.texi =================================================================== --- glibc-doc-reference/branches/glibc-2.6/manual/message.texi 2007-05-30 13:16:34 UTC (rev 2317) +++ glibc-doc-reference/branches/glibc-2.6/manual/message.texi 2007-05-30 13:20:20 UTC (rev 2318) @@ -1189,7 +1189,7 @@ with every language this is the only viable solution except for hardcoding the information in the code (which still would require the possibility of extensions to not prevent the use of new languages). The -details are explained in the GNU @code{gettext} manual. Here only a a +details are explained in the GNU @code{gettext} manual. Here only a bit of information is provided. The information about the plural form selection has to be stored in the @@ -1590,7 +1590,7 @@ them. The POSIX locale model uses the environment variables @code{LC_COLLATE}, [EMAIL PROTECTED], @code{LC_MESSAGES}, @code{LC_MONETARY}, @code{NUMERIC}, [EMAIL PROTECTED], @code{LC_MESSAGES}, @code{LC_MONETARY}, @code{LC_NUMERIC}, and @code{LC_TIME} to select the locale which is to be used. This way the user can influence lots of functions. As we mentioned above the @code{gettext} functions also take advantage of this. @@ -1810,8 +1810,8 @@ Other programs help to manage development cycle when new messages appear in the source files or when a new translation of the messages appear. -here it should only be noted that using all the tools in GNU gettext it -is possible to @emph{completely} automize the handling of message +Here it should only be noted that using all the tools in GNU gettext it +is possible to @emph{completely} automate the handling of message catalog. Beside marking the translatable string in the source code and generating the translations the developers do not have anything to do themselves. Modified: glibc-doc-reference/branches/glibc-2.6/manual/resource.texi =================================================================== --- glibc-doc-reference/branches/glibc-2.6/manual/resource.texi 2007-05-30 13:16:34 UTC (rev 2317) +++ glibc-doc-reference/branches/glibc-2.6/manual/resource.texi 2007-05-30 13:20:20 UTC (rev 2318) @@ -584,7 +584,7 @@ @cindex preemptive scheduling When two processes are in contention to use the CPU at any instant, the one with the higher absolute priority always gets it. This is true even if the -process with the lower priority is already using the CPU (i.e. the +process with the lower priority is already using the CPU (i.e., the scheduling is preemptive). Of course, we're only talking about processes that are running or ``ready to run,'' which means they are ready to execute instructions right now. When a process blocks to wait @@ -819,7 +819,7 @@ @item The calling process does not have @code{CAP_SYS_NICE} permission and its -owner is not the target process' owner. I.e. the effective uid of the +owner is not the target process' owner. I.e., the effective uid of the calling process is neither the effective nor the real uid of process @var{pid}. @c We need a cross reference to the capabilities section, when written. @@ -1185,7 +1185,7 @@ @item EPERM The call would set the nice value of a process which is owned by a different -user than the calling process (i.e. the target process' real or effective +user than the calling process (i.e., the target process' real or effective uid does not match the calling process' effective uid) and the calling process does not have @code{CAP_SYS_NICE} permission. @@ -1215,7 +1215,7 @@ @comment sys/resource.h @comment BSD @item PRIO_USER -All the processes owned by a particular user (i.e. whose real uid +All the processes owned by a particular user (i.e., whose real uid indicates the user). The argument @var{id} is a user ID (uid). @end vtable @@ -1272,7 +1272,7 @@ @item The access to certain resources (RAM, I/O ports) has different costs from different CPUs. This is the case in NUMA (Non-Uniform Memory -Architecture) machines. Preferrably memory should be accessed locally +Architecture) machines. Preferably memory should be accessed locally but this requirement is usually not visible to the scheduler. Therefore forcing a process or thread to the CPUs which have local access to the mostly used memory helps to significantly boost the Modified: glibc-doc-reference/branches/glibc-2.6/manual/search.texi =================================================================== --- glibc-doc-reference/branches/glibc-2.6/manual/search.texi 2007-05-30 13:16:34 UTC (rev 2317) +++ glibc-doc-reference/branches/glibc-2.6/manual/search.texi 2007-05-30 13:20:20 UTC (rev 2318) @@ -82,7 +82,7 @@ available @code{NULL} is returned. The mean runtime of this function is @[EMAIL PROTECTED]/2. This -function should only be used elements often get added to or deleted from +function should only be used if elements often get added to or deleted from the array in which case it might not be useful to sort the array before searching. @end deftypefun @@ -247,21 +247,21 @@ @node Hash Search Function @section The @code{hsearch} function. -The functions mentioned so far in this chapter are searching in a sorted +The functions mentioned so far in this chapter are for searching in a sorted or unsorted array. There are other methods to organize information which later should be searched. The costs of insert, delete and search differ. One possible implementation is using hashing tables. -The following functions are declared in the the header file @file{search.h}. +The following functions are declared in the header file @file{search.h}. @comment search.h @comment SVID @deftypefun int hcreate (size_t @var{nel}) The @code{hcreate} function creates a hashing table which can contain at least @var{nel} elements. There is no possibility to grow this table so -it is necessary to choose the value for @var{nel} wisely. The used -methods to implement this function might make it necessary to make the +it is necessary to choose the value for @var{nel} wisely. The method +used to implement this function might make it necessary to make the number of elements in the hashing table larger than the expected maximal -number of elements. Hashing tables usually work inefficient if they are +number of elements. Hashing tables usually work inefficiently if they are filled 80% or more. The constant access time guaranteed by hashing can only be achieved if few collisions exist. See Knuth's ``The Art of Computer Programming, Part 3: Searching and Sorting'' for more @@ -368,9 +368,9 @@ dynamically. It must be initialized with zero before calling this function. -The return value is non-zero if the operation were successful. if the -return value is zero something went wrong which probably means the -programs runs out of memory. +The return value is non-zero if the operation was successful. If the +return value is zero, something went wrong, which probably means the +programs ran out of memory. @end deftypefun @comment search.h Modified: glibc-doc-reference/branches/glibc-2.6/manual/signal.texi =================================================================== --- glibc-doc-reference/branches/glibc-2.6/manual/signal.texi 2007-05-30 13:16:34 UTC (rev 2317) +++ glibc-doc-reference/branches/glibc-2.6/manual/signal.texi 2007-05-30 13:20:20 UTC (rev 2318) @@ -2567,7 +2567,7 @@ Note that you must not use @code{sigprocmask} in multi-threaded processes, because each thread has its own signal mask and there is no single process signal mask. According to POSIX, the behavior of @code{sigprocmask} in a -multi-threaded process is ``unspeficied''. +multi-threaded process is ``unspecified''. Instead, use @code{pthread_sigmask}. @ifset linuxthreads @xref{Threads and Signal Handling}. Modified: glibc-doc-reference/branches/glibc-2.6/manual/startup.texi =================================================================== --- glibc-doc-reference/branches/glibc-2.6/manual/startup.texi 2007-05-30 13:16:34 UTC (rev 2317) +++ glibc-doc-reference/branches/glibc-2.6/manual/startup.texi 2007-05-30 13:20:20 UTC (rev 2318) @@ -830,7 +830,7 @@ Don't confuse a program's exit status with a process' termination status. There are lots of ways a process can terminate besides having it's program finish. In the event that the process termination @emph{is} caused by program -termination (i.e. @code{exit}), though, the program's exit status becomes +termination (i.e., @code{exit}), though, the program's exit status becomes part of the process' termination status. @node Cleanups on Exit Modified: glibc-doc-reference/branches/glibc-2.6/manual/stdio.texi =================================================================== --- glibc-doc-reference/branches/glibc-2.6/manual/stdio.texi 2007-05-30 13:16:34 UTC (rev 2317) +++ glibc-doc-reference/branches/glibc-2.6/manual/stdio.texi 2007-05-30 13:20:20 UTC (rev 2318) @@ -433,7 +433,7 @@ @cindex multi-threaded application Streams can be used in multi-threaded applications in the same way they are used in single-threaded applications. But the programmer must be -aware of a the possible complications. It is important to know about +aware of the possible complications. It is important to know about these also if the program one writes never use threads since the design and implementation of many stream functions is heavily influenced by the requirements added by multi-threaded programming. @@ -1992,7 +1992,7 @@ The @samp{%g} and @samp{%G} conversions print the argument in the style of @samp{%e} or @samp{%E} (respectively) if the exponent would be less than -4 or greater than or equal to the precision; otherwise they use -the @samp{%f} style. A precision of @code{0}, is taken as 1. is +the @samp{%f} style. A precision of @code{0}, is taken as 1. Trailing zeros are removed from the fractional portion of the result and a decimal-point character appears only if it is followed by a digit. @@ -2393,8 +2393,9 @@ allocates a string (as with @code{malloc}; @pxref{Unconstrained Allocation}) to hold the output, instead of putting the output in a buffer you allocate in advance. The @var{ptr} argument should be the -address of a @code{char *} object, and @code{asprintf} stores a pointer -to the newly allocated string at that location. +address of a @code{char *} object, and a successful call to [EMAIL PROTECTED] stores a pointer to the newly allocated string at that +location. The return value is the number of characters allocated for the buffer, or less than zero if an error occurred. Usually this means that the buffer Modified: glibc-doc-reference/branches/glibc-2.6/manual/string.texi =================================================================== --- glibc-doc-reference/branches/glibc-2.6/manual/string.texi 2007-05-30 13:16:34 UTC (rev 2317) +++ glibc-doc-reference/branches/glibc-2.6/manual/string.texi 2007-05-30 13:20:20 UTC (rev 2318) @@ -1187,8 +1187,8 @@ @comment ISO @deftypefun int strncmp (const char [EMAIL PROTECTED], const char [EMAIL PROTECTED], size_t @var{size}) This function is the similar to @code{strcmp}, except that no more than [EMAIL PROTECTED] wide characters are compared. In other words, if the two -strings are the same in their first @var{size} wide characters, the [EMAIL PROTECTED] characters are compared. In other words, if the two +strings are the same in their first @var{size} characters, the return value is zero. @end deftypefun @@ -1966,11 +1966,6 @@ using a multibyte character encoding (abstract) character consisting of more than one byte are not treated as an entity. Each byte is treated separately. The function is not locale-dependent. - -Note that ``character'' is here used in the sense of byte. In a string -using a multibyte character encoding (abstract) character consisting of -more than one byte are not treated as an entity. Each byte is treated -separately. The function is not locale-dependent. @end deftypefun @comment wchar.h Modified: glibc-doc-reference/branches/glibc-2.6/manual/sysinfo.texi =================================================================== --- glibc-doc-reference/branches/glibc-2.6/manual/sysinfo.texi 2007-05-30 13:16:34 UTC (rev 2317) +++ glibc-doc-reference/branches/glibc-2.6/manual/sysinfo.texi 2007-05-30 13:20:20 UTC (rev 2318) @@ -872,7 +872,7 @@ @item MS_SYNCHRONOUS This bit on specifies that all writes to the filesystem while it is -mounted shall be synchronous; i.e. data shall be synced before each +mounted shall be synchronous; i.e., data shall be synced before each write completes rather than held in the buffer cache. @item MS_MANDLOCK Modified: glibc-doc-reference/branches/glibc-2.6/manual/syslog.texi =================================================================== --- glibc-doc-reference/branches/glibc-2.6/manual/syslog.texi 2007-05-30 13:16:34 UTC (rev 2317) +++ glibc-doc-reference/branches/glibc-2.6/manual/syslog.texi 2007-05-30 13:20:20 UTC (rev 2318) @@ -370,7 +370,7 @@ Results are undefined if the priority code is anything else. -If the process does not presently have a Syslog connection open (i.e. +If the process does not presently have a Syslog connection open (i.e., it did not call @code{openlog}), @code{syslog} implicitly opens the connection the same as @code{openlog} would, with the following defaults for information that would otherwise be included in an @code{openlog} Modified: glibc-doc-reference/branches/glibc-2.6/manual/time.texi =================================================================== --- glibc-doc-reference/branches/glibc-2.6/manual/time.texi 2007-05-30 13:16:34 UTC (rev 2317) +++ glibc-doc-reference/branches/glibc-2.6/manual/time.texi 2007-05-30 13:20:20 UTC (rev 2318) @@ -193,7 +193,7 @@ arbitrary event. On the GNU system, that event is the creation of the process. While arbitrary in general, the event is always the same event for any particular process, so you can always measure how much time on -the CPU a particular computation takes by examinining the process' CPU +the CPU a particular computation takes by examining the process' CPU time before and after the computation. @cindex CPU time @cindex clock ticks @@ -447,7 +447,7 @@ @comment time.h @comment SVID, XPG @deftypefun int stime (time_t [EMAIL PROTECTED]) [EMAIL PROTECTED] sets the system clock, i.e. it tells the system that the [EMAIL PROTECTED] sets the system clock, i.e., it tells the system that the current calendar time is @var{newtime}, where @code{newtime} is interpreted as described in the above definition of @code{time_t}. @@ -1470,7 +1470,7 @@ @node Low-Level Time String Parsing @subsubsection Interpret string according to given format -he first function is rather low-level. It is nevertheless frequently +The first function is rather low-level. It is nevertheless frequently used in software since it is better known. Its interface and implementation are heavily influenced by the @code{getdate} function, which is defined and implemented in terms of calls to @code{strptime}. @@ -1790,7 +1790,7 @@ the format string the return value points right after the last consumed input character. If the whole input string is consumed the return value points to the @code{NULL} byte at the end of the string. If an error -occurs, i.e. @code{strptime} fails to match all of the format string, +occurs, i.e., @code{strptime} fails to match all of the format string, the function returns @code{NULL}. @end deftypefun -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
