From owner-freebsd-current Sat May 4 19:36:46 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id AA08137B404; Sat, 4 May 2002 19:36:43 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 95900535E; Sun, 5 May 2002 04:36:42 +0200 (CEST) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Doug Barton Cc: John Baldwin , Subject: Re: xdm broken on current References: <20020504192730.V873-100000@master.gorean.org> From: Dag-Erling Smorgrav Date: 05 May 2002 04:36:41 +0200 In-Reply-To: Message-ID: Lines: 16 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dag-Erling Smorgrav writes: > Doug Barton 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