From owner-freebsd-arch Sun Jun 23 12:52: 9 2002 Delivered-To: freebsd-arch@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id AADFE37B415; Sun, 23 Jun 2002 12:51:53 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 0F5B85361; Sun, 23 Jun 2002 21:51:51 +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: Alfred Perlstein , Will Andrews , David O'Brien , Makoto Matsushita , arch@FreeBSD.org Subject: Re: Installing XFree86 package via sysinstall: need X wrapper or not? References: <20020621135806Z.matusita@jp.FreeBSD.org> <20020621134520.G68827@dragon.nuxi.com> <20020621223209.GP76002@squall.waterspout.com> <20020622200545.GS76002@squall.waterspout.com> <20020622204229.GG53232@elvis.mu.org> <3D152EAA.DB201738@FreeBSD.org> <3D162074.A636B067@FreeBSD.org> From: Dag-Erling Smorgrav Date: 23 Jun 2002 21:51:50 +0200 In-Reply-To: <3D162074.A636B067@FreeBSD.org> Message-ID: Lines: 31 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-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Doug Barton writes: > Dag-Erling Smorgrav wrote: > > Doug Barton writes: > > > Or users for whom xdm isn't possible because the pam libraries in > > > -current are buggered. > > I can't recall receiving a bug report from you. > Then you have a really bad memory. :) You're one of the ones that told > me that it was "necessary" to break binay compat with 4.x for silly reason> so I was SOL with the X 4.2 I downloaded from Xfree's web > site. Now, recompiling isn't even an option because X won't compile on > -current... yippee! I'm afraid you're the one with a bad memory, then - I distinctly remember explaining to you *why* you were having problems with xdm and PAM. To summarize, you were running a version of X built on -STABLE on a version of -CURRENT where the -STABLE PAM library and modules had been clobbered with a version that wouldn't coexist with -STABLE's libc. This problem has existed on -CURRENT since long before I started working on PAM, and part of my work has been to implement PAM module versioning so this problem wouldn't occur in the future. The long-term fix to allow people to upgrade painlessly from -STABLE to -CURRENT is to include -STABLE's PAM library and modules in compat4x. I've asked David to do this several times, with no success. If you still claim that "the pam libraries in -current are buggered", you're going to have to back it up with solid evidence. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message