Re: PAM and current

2002-02-04 Thread Dag-Erling Smorgrav

"M. Warner Losh" <[EMAIL PROTECTED]> writes:
> I just upgraded my laptop to -current to start working on some
> lingering newcard + acpi problems (like the panic on boot due to
> interrupt issues).  So I notice a new message on my console when I log
> in via xdm:
> 
> Feb  3 16:18:44 hammer : PAM unable to dlopen(/usr/lib/pam_opie.so)
> Feb  3 16:18:44 hammer : PAM [dlerror: /usr/lib/libopie.so.2: Undefined symbol 
>"__xuname"]
> Feb  3 16:18:44 hammer : PAM adding faulty module: /usr/lib/pam_opie.so
> Feb  3 16:18:44 hammer : PAM unable to dlopen(/usr/lib/pam_opieaccess.so)
> Feb  3 16:18:44 hammer : PAM [dlerror: /usr/lib/libopie.so.2: Undefined symbol 
>"__xuname"]
> Feb  3 16:18:44 hammer : PAM adding faulty module: /usr/lib/pam_opieaccess.so

Your xdm is linked against -STABLE libc, but the PAM modules expect a
-CURRENT libc.  Since PAM modules aren't versioned, there's no way to
keep -STABLE modules around for -STABLE apps; you have to rebuild all
PAM apps when upgrading from -STABLE to -CURRENT.

DES
-- 
Dag-Erling Smorgrav - [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



PAM and current

2002-02-03 Thread M. Warner Losh

I just upgraded my laptop to -current to start working on some
lingering newcard + acpi problems (like the panic on boot due to
interrupt issues).  So I notice a new message on my console when I log
in via xdm:

Feb  3 16:18:44 hammer : PAM unable to dlopen(/usr/lib/pam_opie.so)
Feb  3 16:18:44 hammer : PAM [dlerror: /usr/lib/libopie.so.2: Undefined symbol 
"__xuname"]
Feb  3 16:18:44 hammer : PAM adding faulty module: /usr/lib/pam_opie.so
Feb  3 16:18:44 hammer : PAM unable to dlopen(/usr/lib/pam_opieaccess.so)
Feb  3 16:18:44 hammer : PAM [dlerror: /usr/lib/libopie.so.2: Undefined symbol 
"__xuname"]
Feb  3 16:18:44 hammer : PAM adding faulty module: /usr/lib/pam_opieaccess.so

Ideas?  This is post mergemaster.

Warner

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message