On 5 May 2002, Dag-Erling Smorgrav wrote:
> Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes:
> > Doug Barton <[EMAIL PROTECTED]> writes:
> > > Then I'm back to my original point. I think that breaking binary
> > > compatibility for all 4.x pam applications is a very bad idea.
> > It was already broken. There's nothing you can do about it.
>
> Hmm, let me amend this: it's broken for you because you have a pre-
> OpenPAM libpam + modules that was built on 5.0. You wouldn't see this
> if you'd upgraded straight from 4.x, because OpenPAM uses versioned
> modules and doesn't clobber your old 4.x modules. I asked David to
> put libpam and the PAM modules in COMPAT4X, but never heard back from
> him.
Ok, I put the following in /usr/lib/compat, from my releng_4 box:
libc.so.4
libc_r.a
libc_r.so.4
libpam.a
libpam.so.1
libpam_ssh.a
And tried the following from the same box in both /usr/lib and
/usr/lib/compat:
pam_cleartext_pass_ok.so
pam_deny.so
pam_opie.so
pam_permit.so
pam_radius.so
pam_skey.so
pam_ssh.so
pam_tacplus.so
pam_unix.so
Still the same errors:
unable to dlopen(/usr/lib/pam_nologin.so)
[dlerror: Cannot open "/usr/lib/pam_nologin.so"]
adding faulty module: /usr/lib/pam_nologin.so
unable to dlopen(/usr/lib/pam_opie.so)
[dlerror: /usr/lib/libopie.so.2: Undefined symbol "__xuname"]
adding faulty module: /usr/lib/pam_opie.so
unable to dlopen(/usr/lib/pam_opieaccess.so)
[dlerror: Cannot open "/usr/lib/pam_opieaccess.so"]
adding faulty module: /usr/lib/pam_opieaccess.so
unable to dlopen(/usr/lib/pam_lastlog.so)
[dlerror: Cannot open "/usr/lib/pam_lastlog.so"]
adding faulty module: /usr/lib/pam_lastlog.so
--
"We have known freedom's price. We have shown freedom's power.
And in this great conflict, ... we will see freedom's victory."
- George W. Bush, President of the United States
State of the Union, January 28, 2002
Do YOU Yahoo!?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
