Gentoo Archives: gentoo-commits

From: "Diego Petteno (flameeyes)" <flameeyes@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/base/pam: upgrade-0.99.xml
Date: Sun, 24 Feb 2008 20:28:11
Message-Id: E1JTNS9-00086N-LM@stork.gentoo.org
1 flameeyes 08/02/24 20:28:05
2
3 Modified: upgrade-0.99.xml
4 Log:
5 Update the PAM guide, try to be more explicit on which changes need to
6 be applied to what.
7
8 Revision Changes Path
9 1.12 xml/htdocs/proj/en/base/pam/upgrade-0.99.xml
10
11 file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/base/pam/upgrade-0.99.xml?rev=1.12&view=markup
12 plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/base/pam/upgrade-0.99.xml?rev=1.12&content-type=text/plain
13 diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/base/pam/upgrade-0.99.xml?r1=1.11&r2=1.12
14
15 Index: upgrade-0.99.xml
16 ===================================================================
17 RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/base/pam/upgrade-0.99.xml,v
18 retrieving revision 1.11
19 retrieving revision 1.12
20 diff -u -r1.11 -r1.12
21 --- upgrade-0.99.xml 22 Nov 2007 21:24:40 -0000 1.11
22 +++ upgrade-0.99.xml 24 Feb 2008 20:28:05 -0000 1.12
23 @@ -1,6 +1,6 @@
24 <?xml version="1.0" encoding="UTF-8"?>
25 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
26 -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/base/pam/upgrade-0.99.xml,v 1.11 2007/11/22 21:24:40 flameeyes Exp $ -->
27 +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/base/pam/upgrade-0.99.xml,v 1.12 2008/02/24 20:28:05 flameeyes Exp $ -->
28
29 <guide link="/proj/en/base/pam/upgrade-0.99.xml" lang="en">
30 <title>Linux-PAM 0.99 upgrade guide</title>
31 @@ -18,8 +18,8 @@
32 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
33 <license/>
34
35 -<version>1.7</version>
36 -<date>2007-11-22</date>
37 +<version>1.2</version>
38 +<date>2008-02-24</date>
39
40 <chapter>
41 <title>Upgrade guide</title>
42 @@ -79,10 +79,21 @@
43 </impo>
44
45 <p>
46 -All the changes described have to be applied to each file in the
47 -<path>/etc/pam.d/</path> directory (the PAM configuration files). Please make
48 -sure you remove eventual backup files (<path>*~</path>) before trying to update
49 -<c>sys-libs/pam</c>, or the emerge process will fail as a safety measure.
50 +What users have to do for most of the cases is either to install a new package
51 +(because the module was migrated out of the main <c>sys-libs/pam</c> ebuild), or
52 +to change the configuration so that it does not use the modules that were
53 +dropped. If you made changes to the PAM service configuration files, you should
54 +be able to handle all the changes. For those who never changed a configuration
55 +file, there is only one change that needs to be done, documented in the <uri
56 +link="#pam_stack">pam_stack and the include directive</uri> section.
57 +</p>
58 +
59 +<p>
60 +The changes need to be applied to each and every file in the
61 +<path>/etc/pam.d/</path> directory (the PAM services configuration
62 +files). Please make sure you remove eventual backup files (<path>*~</path>)
63 +before trying to update <c>sys-libs/pam</c>, or the emerge process will fail as
64 +a safety measure.
65 </p>
66
67 <p>
68 @@ -96,6 +107,15 @@
69 <c>app-portage/portage-utils</c>.
70 </p>
71
72 +<impo>
73 +The safety check will also check the comment lines, which means that you also
74 +need to remove the comments that refers to the removed modules. This is meant as
75 +an extra safety so that users don't uncomment lines that will disallow them from
76 +logging in on their system. If you want to keep the comment in there as
77 +documentation, you're invited to split up the modules' names (for instance in
78 +<path>pam _stack.so</path>).
79 +</impo>
80 +
81 <pre caption="using qfile -o to check for orphan files">
82 # <i>qfile -o /etc/pam.d/*</i>
83 /etc/pam.d/sshd
84 @@ -213,7 +233,7 @@
85
86 </body>
87 </section>
88 -<section>
89 +<section id="pam_stack">
90 <title>pam_stack and the include directive</title>
91 <body>
92
93
94
95
96 --
97 gentoo-commits@l.g.o mailing list