Do not mention old Linux kernel versions in installation documentation.

diff --git a/ChangeLog b/ChangeLog
index 4254c90..5aef24f 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,10 @@
+2012-05-23  Joseph Myers  <joseph@codesourcery.com>
+
+       * manual/install.texi (Running make install): Do not mention Linux
+       kernel version for which pt_chown is not needed.
+       (Linux): Do not mention problems with nscd with 2.0 kernels.
+       * INSTALL: Regenerated.
+
 2012-05-23  Andreas Jaeger  <aj@suse.de>
 
        * sysdeps/unix/sysv/linux/powerpc/bits/mman.h

diff --git a/INSTALL b/INSTALL
index 5b9b8d2..d4fabe9 100644 (file)
--- a/INSTALL
+++ b/INSTALL
@@ -244,9 +244,9 @@ well.
 permissions on a pseudoterminal so it can be used by the calling
 process.  This means programs like `xterm' and `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 or newer Linux kernel with the
-`devptsfs' or `devfs' filesystems providing pty slaves, you don't need
-this program; otherwise you do.  The source for `pt_chown' is in
+privileges.)  If you are using a Linux kernel with the `devptsfs' or
+`devfs' filesystems providing pty slaves, you don't need this program;
+otherwise you do.  The source for `pt_chown' is in
 `login/programs/pt_chown.c'.
 
    After installation you might want to configure the timezone and
@@ -377,11 +377,6 @@ C Library with `--prefix=/usr'.  If you set some other prefix or allow
 it to default to `/usr/local', then all the components are installed
 there.
 
-   You cannot use `nscd' with 2.0 kernels, due to bugs in the
-kernel-side thread support.  `nscd' happens to hit these bugs
-particularly hard, but you might have problems with any threaded
-program.
-
 Reporting Bugs
 ==============
 

diff --git a/manual/install.texi b/manual/install.texi
index 0abb57e..5aca058 100644 (file)
--- a/manual/install.texi
+++ b/manual/install.texi
@@ -275,8 +275,8 @@ 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 or
-newer Linux kernel with the @code{devptsfs} or @code{devfs} filesystems
+other reasons why they need privileges.)  If you are using a
+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}.
 
@@ -428,11 +428,6 @@ if you configure @theglibc{} with @samp{--prefix=/usr}.  If you set some other
 prefix or allow it to default to @file{/usr/local}, then all the
 components are installed there.
 
-You cannot use @code{nscd} with 2.0 kernels, due to bugs in the
-kernel-side thread support.  @code{nscd} happens to hit these bugs
-particularly hard, but you might have problems with any threaded
-program.
-
 @node Reporting Bugs
 @appendixsec Reporting Bugs
 @cindex reporting bugs