1 |
On Wednesday 30 January 2008, maxim wexler wrote: |
2 |
> --- Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
3 |
> > Well, the docs page on the upgrade to pam-0.99 is |
4 |
> > complete, I updated |
5 |
> > severala machines no problem with it. So you must |
6 |
> > have muffed the |
7 |
> > instructions. Next time, read the whole page. |
8 |
> |
9 |
> While I was waiting I went back to the page and |
10 |
> decided I should probably emerge pam_chroot. |
11 |
> pam_userdb didn't seem to involve me so I left it |
12 |
> alone. Other than that I couldn't see what else |
13 |
> applied to my case except for the suggestion that |
14 |
> some, unamed, file should be edited. I notice that |
15 |
> since I apparently overleapt the main pam hurdle |
16 |
> /etc/pam.d has a new system-auth file in it. Must be |
17 |
> on the right track cause it didn't complain about |
18 |
> pam-0.99 when pam_chroot was emerged. |
19 |
|
20 |
FWIW, I have a stock standard workstation system pam-wise. I hanged no |
21 |
files from the default, it all works and upgrades were seamless. Here's |
22 |
the pam modules I have: |
23 |
|
24 |
nazgul / # eix ^pam | grep sys-auth |
25 |
* sys-auth/pam-afs-session |
26 |
* sys-auth/pam_abl |
27 |
* sys-auth/pam_bioapi |
28 |
* sys-auth/pam_chroot |
29 |
* sys-auth/pam_dotfile |
30 |
* sys-auth/pam_keyring |
31 |
* sys-auth/pam_krb5 |
32 |
* sys-auth/pam_ldap |
33 |
* sys-auth/pam_mktemp |
34 |
* sys-auth/pam_mount |
35 |
* sys-auth/pam_mysql |
36 |
* sys-auth/pam_p11 |
37 |
* sys-auth/pam_passwdqc |
38 |
* sys-auth/pam_pkcs11 |
39 |
* sys-auth/pam_pwdfile |
40 |
* sys-auth/pam_require |
41 |
* sys-auth/pam_sha512 |
42 |
* sys-auth/pam_skey |
43 |
* sys-auth/pam_smb |
44 |
* sys-auth/pam_ssh |
45 |
* sys-auth/pam_ssh_agent |
46 |
* sys-auth/pam_usb |
47 |
* sys-auth/pam_userdb |
48 |
* sys-auth/pam_blue [1] |
49 |
* sys-auth/pam_pgsql [1] |
50 |
* sys-auth/pam_sotp [1] |
51 |
|
52 |
and my /etc/pam.d/ |
53 |
|
54 |
nazgul / # ls -al /etc/pam.d |
55 |
total 146 |
56 |
drwxr-xr-x 2 root root 1072 2008-01-18 21:49 . |
57 |
drwxr-xr-x 92 root root 5464 2008-01-29 23:56 .. |
58 |
-rw-r--r-- 1 root root 152 2007-11-09 19:03 chage |
59 |
-rw-r--r-- 1 root root 152 2007-11-09 19:03 chfn |
60 |
-rw-r--r-- 1 root root 103 2007-11-09 19:03 chgpasswd |
61 |
-rw-r--r-- 1 root root 152 2007-11-09 19:03 chpasswd |
62 |
-rw-r--r-- 1 root root 152 2007-11-09 19:03 chsh |
63 |
-rw-r--r-- 1 root root 123 2007-11-02 12:59 cron |
64 |
-rw-r--r-- 1 root root 113 2008-01-18 21:42 cups |
65 |
-rw-r--r-- 1 root root 106 2007-11-05 15:21 cvs |
66 |
-rw-r--r-- 1 root root 223 2008-01-07 23:05 entrance |
67 |
-rw-r--r-- 1 root root 152 2007-11-09 19:03 groupadd |
68 |
-rw-r--r-- 1 root root 152 2007-11-09 19:03 groupdel |
69 |
-rw-r--r-- 1 root root 103 2007-11-09 19:03 groupmems |
70 |
-rw-r--r-- 1 root root 152 2007-11-09 19:03 groupmod |
71 |
-rw-r--r-- 1 root root 362 2007-11-02 12:57 imap |
72 |
lrwxrwxrwx 1 root root 15 2007-11-02 12:57 imap4 -> /etc/pam.d/imap |
73 |
lrwxrwxrwx 1 root root 15 2007-11-02 12:57 imap4s -> /etc/pam.d/imap |
74 |
lrwxrwxrwx 1 root root 15 2007-11-02 12:57 imaps -> /etc/pam.d/imap |
75 |
-rw-r--r-- 1 root root 197 2007-11-05 07:17 kde |
76 |
-rw-r--r-- 1 root root 196 2007-11-05 07:17 kde-np |
77 |
-rw-r--r-- 1 root root 563 2007-11-09 19:03 login |
78 |
-rw-r--r-- 1 root root 152 2007-11-09 19:03 newusers |
79 |
-rw-r--r-- 1 root root 139 2007-11-14 11:58 other |
80 |
-rw-r--r-- 1 root root 104 2007-11-09 19:03 passwd |
81 |
-rw-r--r-- 1 root root 362 2007-11-02 12:57 pop |
82 |
lrwxrwxrwx 1 root root 14 2007-11-02 12:57 pop3 -> /etc/pam.d/pop |
83 |
lrwxrwxrwx 1 root root 14 2007-11-02 12:57 pop3s -> /etc/pam.d/pop |
84 |
lrwxrwxrwx 1 root root 14 2007-11-02 12:57 pops -> /etc/pam.d/pop |
85 |
-rw-r--r-- 1 root root 183 2007-11-02 12:58 ppp |
86 |
-rw-r--r-- 1 root root 397 2008-01-18 21:48 samba |
87 |
-rw-r--r-- 1 root root 160 2008-01-18 21:30 saslauthd |
88 |
-rw-r--r-- 1 root root 84 2007-11-05 18:32 screen |
89 |
-rw-r--r-- 1 root root 152 2007-11-09 19:03 shadow |
90 |
-rw-r--r-- 1 root root 205 2008-01-18 21:21 sshd |
91 |
-rw-r--r-- 1 root root 1059 2007-11-09 19:03 su |
92 |
-rw-r--r-- 1 root root 172 2008-01-18 21:25 sudo |
93 |
-rw-r--r-- 1 root root 447 2007-11-14 11:58 system-auth |
94 |
-rw-r--r-- 1 root root 152 2007-11-09 19:03 useradd |
95 |
-rw-r--r-- 1 root root 152 2007-11-09 19:03 userdel |
96 |
-rw-r--r-- 1 root root 152 2007-11-09 19:03 usermod |
97 |
-rw-r--r-- 1 root root 218 2008-01-16 09:24 vmware-guestd |
98 |
-rw-r--r-- 1 root root 125 2008-01-14 21:38 xserver |
99 |
|
100 |
|
101 |
WorksForMe <shrug> |
102 |
|
103 |
> Then I made |
104 |
> detour and updated a bunch of /etc files that had |
105 |
> popped up after having started the massive update. I |
106 |
> must have missed modprobe cause when I booted again a |
107 |
> boot warning flashed by, "warning modprobe.conf not |
108 |
> generated". Then it got to login where I was again not |
109 |
> allowed access. Does that have something to do with |
110 |
> modprobe.conf? PAM? Both? |
111 |
|
112 |
Not related that I can see. modprobe.conf not being updated is a |
113 |
separate issue, solved by running modules-update in an existing root |
114 |
shell |
115 |
|
116 |
> > Meanwhile, boot off a LiveCD or some other medium. |
117 |
> > or maintenance mode, |
118 |
> > chroot into gentoo and find all packages that depend |
119 |
> > on pam: |
120 |
> > |
121 |
> > equery depends pam |
122 |
> |
123 |
> AttributeError: Package instance has no attribute |
124 |
> 'get_postmerge_deps' |
125 |
> |
126 |
> > or maybe |
127 |
> > euse -i pam |
128 |
> |
129 |
> no matching entries found |
130 |
> |
131 |
> As for modprobe, I just chrooted again and ran |
132 |
> update-modules. I forgot to add -v on the first pass, |
133 |
> so I did it again with -v and it's telling me |
134 |
> |
135 |
> *Skipping /etc/modules.conf generation(prerequisites |
136 |
> not satisfied |
137 |
> *Skipping /etc/modprobe.conf generation (file is newer |
138 |
> than dependencies) |
139 |
> * The dir '/lib/modules/2.6.15-gentoo-r5/modules.dep' |
140 |
> does not exist, skipping call to depmod |
141 |
> |
142 |
> So this is wierd: according to ls -l |
143 |
> /etc/modprobe.conf was just written. |
144 |
|
145 |
The mtime does not mean that the file was not written. |
146 |
|
147 |
I'd be more worried why you don't have |
148 |
a /lib/modules/2.6.15-gentoo-r5/modules.dep. |
149 |
|
150 |
Look into your /etc/modules.d/ and modprobe.conf and see what's there. |
151 |
|
152 |
> Or is it because the PC is in a chrooted environment |
153 |
> and uses a different set of modules? |
154 |
|
155 |
No, chroot uses the running kernel. It's not a virtualised environment. |
156 |
|
157 |
Maxim, I've been watching your posts for a while now, and most times |
158 |
it's because you made some blunder that is quite elementary and that |
159 |
you really should know. Your problem seems to be a lack of |
160 |
understanding of how Unix works. |
161 |
|
162 |
You really really need to start reading documentation. Your gentoo life |
163 |
will go much easier when you do. |
164 |
|
165 |
|
166 |
-- |
167 |
Alan McKinnon |
168 |
alan dot mckinnon at gmail dot com |
169 |
-- |
170 |
gentoo-user@l.g.o mailing list |