Date: 05 May 2002 04:36:41 +0200 From: Dag-Erling Smorgrav <des@ofug.org> To: Doug Barton <DougB@FreeBSD.org> Cc: John Baldwin <jhb@FreeBSD.org>, <current@FreeBSD.org> Subject: Re: xdm broken on current Message-ID: <xzpr8krxqva.fsf@flood.ping.uio.no> In-Reply-To: <xzpvga3xr4d.fsf@flood.ping.uio.no> References: <20020504192730.V873-100000@master.gorean.org> <xzpvga3xr4d.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling Smorgrav <des@ofug.org> writes: > Doug Barton <DougB@FreeBSD.org> 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. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpr8krxqva.fsf>