Relevant BUGIDs:

[linux-pam] / doc / pam_source.sgml

diff --git a/doc/pam_source.sgml b/doc/pam_source.sgml
index 2ea9a7c9c97fa33bd19a51a2502232fe4dbd563b..bc091ed66b7f2252c2a748e1799b31b4100c12e3 100644 (file)
--- a/doc/pam_source.sgml
+++ b/doc/pam_source.sgml
@@ -268,7 +268,7 @@ that this enables.
       be used, including RADIUS, NIS, NCP (which means that Novell
       password databases can be used).
 
-   o  pppd has a PAMified version (available from RedHat)  Now it is
+   o  pppd has a PAMified version (available from Red Hat)  Now it is
       possible to use a series of databases to authenticate ppp users.
       In addition to the normal Linux-based password databases (such
       as /etc/passwd and /etc/shadow), you can use PAM modules to 
@@ -967,20 +967,6 @@ From here you can go back and get a real configuration
 going, hopefully after you've tested it first on a machine
 you don't care about screwing up.  :/
 
-Some pointers (to make everything "right" with Red Hat...):
-
-    Install the newest pam, pamconfig, and pwdb from the
-    redhat current directory, and do it all on the same
-    command line with rpm...
-
-        rpm -Uvh [maybe --force too] pam-* pamconfig-* pwdb-*
-
-    Then make sure you install (or reinstall) the newest
-    version of libc, util-linux, wuftp, and NetKit. For
-    kicks you might try installing the newest versions of
-    the affected x apps, like xlock, but I haven't gotten
-    those to work at all yet.
-
 </verb>
 
 <sect1>Avoid having a weak `other' configuration