Update.

1999-01-24  Ulrich Drepper  <drepper@cygnus.com>

	* ctype/ctype.c (toupper): Correct variable names from lat change.
	(tolower): Likewise.

6 files changed, 30 insertions, 25 deletions

diff --git a/ChangeLog b/ChangeLog
index 7baae4fce5..0d922f7314 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+1999-01-24  Ulrich Drepper  <drepper@cygnus.com>
+
+	* ctype/ctype.c (toupper): Correct variable names from lat change.
+	(tolower): Likewise.
+
 1999-01-23  Ulrich Drepper  <drepper@cygnus.com>
 
 	* sunrpc/rpc_main.c (open_output): Allow better translation of
diff --git a/FAQ.in b/FAQ.in
index 788c50e2e8..db5bd1d373 100644
--- a/FAQ.in
+++ b/FAQ.in
@@ -172,14 +172,14 @@ new kernel features when using old kernel headers for compiling the GNU C
 library.
 
 {ZW} Even if you are using a 2.0 kernel on your machine, we recommend you
-compile GNU libc with 2.1 kernel headers.  That way you won't have to
-recompile libc if you ever upgrade to kernel 2.1 or 2.2.  To tell libc which
+compile GNU libc with 2.2 kernel headers.  That way you won't have to
+recompile libc if you ever upgrade to kernel 2.2.  To tell libc which
 headers to use, give configure the --with-headers switch
-(e.g. --with-headers=/usr/src/linux-2.1.107/include).
+(e.g. --with-headers=/usr/src/linux-2.2.0/include).
 
-Note that you must configure the 2.1 kernel if you do this, otherwise libc
+Note that you must configure the 2.2 kernel if you do this, otherwise libc
 will be unable to find <linux/version.h>.  Just change the current directory
-to the root of the 2.1 tree and do `make include/linux/version.h'.
+to the root of the 2.2 tree and do `make include/linux/version.h'.
 
 ??	The compiler hangs while building iconvdata modules.  What's
 	wrong?
@@ -308,8 +308,8 @@ There are some failures which are not directly related to the GNU libc:
   checks have been used so that you can't build with it.
 - The kernel might have bugs.  For example on Linux/Alpha 2.0.34 the
   floating point handling has quite a number of bugs and therefore most of
-  the test cases in the math subdirectory will fail.  The current Linux 2.1
-  development kernels have fixes for the floating point support on Alpha.
+  the test cases in the math subdirectory will fail.  Linux 2.2 has
+  fixes for the floating point support on Alpha.
 
 ??	What is symbol versioning good for?  Do I need it?
 
@@ -783,7 +783,7 @@ really screwed up.
 in the kernel and work-arounds are not suitable.  Besides, some parts of the
 kernel are too buggy when it comes to using threads.
 
-If you need nscd, you have to use a 2.1 kernel.
+If you need nscd, you have to use at least a 2.1 kernel.
 
 Note that I have at this point no information about any other platform.
 
@@ -1182,7 +1182,7 @@ define it this way and therefore programs must be adopted.
 ??	Why has <netinet/ip_fw.h> disappeared?
 
 {AJ} The corresponding Linux kernel data structures and constants are
-totally different in Linux 2.0 and Linux 2.1.  This situation has to be
+totally different in Linux 2.0 and Linux 2.2.  This situation has to be
 taken care in user programs using the firewall structures and therefore
 those programs (ipfw is AFAIK the only one) should deal with this problem
 themselves.
diff --git a/NEWS b/NEWS
index ac563679b2..d857c0490b 100644
--- a/NEWS
+++ b/NEWS
@@ -1,6 +1,6 @@
-GNU C Library NEWS -- history of user-visible changes.  1998-03-04
+GNU C Library NEWS -- history of user-visible changes.  1999-01-24
 
-Copyright (C) 1992, 93, 94, 95, 96, 97, 98 Free Software Foundation, Inc.
+Copyright (C) 1992, 93, 94, 95, 96, 97, 98, 99 Free Software Foundation, Inc.
 See the end for copying conditions.
 
 Please send GNU C library bug reports using the `glibcbug' script to
@@ -47,7 +47,7 @@ Version 2.1
 
 * Mark Kettenis implemented the utmpx interface and an utmp daemon.
 
-* Ulrich Drepper added character conversion functions.
+* Ulrich Drepper added character set conversion functions (iconv).
 
 * Optimized string functions have been added.
 
diff --git a/ctype/ctype.c b/ctype/ctype.c
index 1c684026fe..ce6d7097f0 100644
--- a/ctype/ctype.c
+++ b/ctype/ctype.c
@@ -39,11 +39,11 @@ func (isxdigit, _ISxdigit)
 int
 tolower (int c)
 {
-  return __c >= -128 && __c < 256 ? __tolower (__c) : __c;
+  return c >= -128 && c < 256 ? __tolower (c) : c;
 }
 
 int
 toupper (int c)
 {
-  return __c >= -128 && __c < 256 ? __toupper (__c) : __c;
+  return c >= -128 && c < 256 ? __toupper (c) : c;
 }
diff --git a/manual/install.texi b/manual/install.texi
index 0bc0be3ef3..694c1d69fa 100644
--- a/manual/install.texi
+++ b/manual/install.texi
@@ -251,10 +251,10 @@ One auxiliary program, @file{/usr/libexec/pt_chown}, is installed setuid
 sets the permissions on a pseudoterminal so it can be used by the
 calling process.  This means programs like @code{xterm} and
 @code{screen} do not have to be setuid to get a pty.  (There may be
-other reasons why they need privileges.)  If you are using a 2.1 Linux
-kernel with the @code{devptsfs} or @code{devfs} filesystems providing
-pty slaves, you don't need this program; otherwise you do.  The source
-for @file{pt_chown} is in @file{login/programs/pt_chown.c}.
+other reasons why they need privileges.)  If you are using a 2.1 or
+newer Linux kernel with the @code{devptsfs} or @code{devfs} filesystems
+providing pty slaves, you don't need this program; otherwise you do.
+The source for @file{pt_chown} is in @file{login/programs/pt_chown.c}.
 
 @node Tools for Compilation
 @appendixsec Recommended Tools for Compilation
diff --git a/manual/process.texi b/manual/process.texi
index 46aeff6009..14421b592f 100644
--- a/manual/process.texi
+++ b/manual/process.texi
@@ -243,15 +243,15 @@ signals and signal actions from the parent process.)
 @comment unistd.h
 @comment BSD
 @deftypefun pid_t vfork (void)
-The @code{vfork} function is similar to @code{fork} but on systems it
-is more efficient; however, there are restrictions you must follow to
+The @code{vfork} function is similar to @code{fork} but on some systems
+it is more efficient; however, there are restrictions you must follow to
 use it safely.
 
-While @code{fork} makes a complete copy of the calling process's
-address space and allows both the parent and child to execute
-independently, @code{vfork} does not make this copy.  Instead, the
-child process created with @code{vfork} shares its parent's address
-space until it calls exits or one of the @code{exec} functions.  In the
+While @code{fork} makes a complete copy of the calling process's address
+space and allows both the parent and child to execute independently,
+@code{vfork} does not make this copy.  Instead, the child process
+created with @code{vfork} shares its parent's address space until it
+calls @code{_exit} or one of the @code{exec} functions.  In the
 meantime, the parent process suspends execution.
 
 You must be very careful not to allow the child process created with