Changeset 5c6a906


Ignore:
Timestamp:
01/23/2014 09:49:25 AM (8 years ago)
Author:
Pierre Labastie <pieere@…>
Branches:
10.0, 10.1, 11.0, 7.10, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, ken/refactor-virt, krejzi/svn, lazarus, nosym, perl-modules, qt5new, systemd-11177, systemd-13485, trunk, xry111/git-date, xry111/git-date-for-trunk, xry111/git-date-test
Children:
af5d034
Parents:
514e1487
Message:

Add information about updating or reinstalling PAM, to avoid removing
important configuration files

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@12621 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:
1 edited

Legend:

Unmodified
Added
Removed
  • postlfs/security/linux-pam.xml

    r514e1487 r5c6a906  
    146146
    147147    <para>
    148       To test the results, a configuration file must be created. This file
    149       will be removed after the tests have completed. Ensure there are no errors
    150       produced by the tests before continuing the installation. First create the
    151       configuration file by issuing the following commands as the
    152       <systemitem class="username">root</systemitem> user:
     148      To test the results, a suitable <filename>/etc/pam.d/other</filename>
     149      configuration file must exist.
     150    </para>
     151
     152    <caution>
     153      <title>Reinstallation or upgrade of Linux PAM</title>
     154      <para>
     155        If you have a system with Linux PAM installed and working, be careful
     156        when modifying the files in
     157        <filename class="directory">/etc/pam.d</filename>, since your system
     158        may become totally unusable. If you want to run the tests, you do not
     159        need to create another <filename>/etc/pam.d/other</filename> file. The
     160        installed one can be used for that purpose.
     161      </para>
     162
     163      <para>
     164         You should also be aware that <command>make install</command>
     165         overwrites the configuration files in
     166         <filename class="directory">/etc/security</filename> as well as
     167         <filename>/etc/environment</filename. In case you
     168         have modified those files, be sure to backup them.
     169      </para>
     170    </caution>
     171
     172    <para>
     173      For a first installation, create the configuration file by issuing the
     174      following commands as the <systemitem class="username">root</systemitem>
     175      user:
    153176    </para>
    154177
     
    164187    <para>
    165188      Now run the tests by issuing <command>make check</command>.
    166     </para>
    167 
    168     <para>
    169       Remove the configuration file created earlier by issuing the
    170       following command as the
     189      Ensure there are no errors produced by the tests before continuing the
     190      installation.
     191    </para>
     192
     193    <para>
     194      Only in case of a first installation, remove the configuration file
     195      created earlier by issuing the following command as the
    171196      <systemitem class="username">root</systemitem> user:
    172197    </para>
Note: See TracChangeset for help on using the changeset viewer.