Skip site navigation (1)Skip section navigation (2)
Date:      23 Jun 2002 21:51:50 +0200
From:      Dag-Erling Smorgrav <des@ofug.org>
To:        Doug Barton <DougB@FreeBSD.org>
Cc:        Alfred Perlstein <bright@mu.org>, Will Andrews <will@csociety.org>, David O'Brien <obrien@FreeBSD.org>, Makoto Matsushita <matusita@jp.FreeBSD.org>, arch@FreeBSD.org
Subject:   Re: Installing XFree86 package via sysinstall: need X wrapper or not?
Message-ID:  <xzp6609zsbt.fsf@flood.ping.uio.no>
In-Reply-To: <3D162074.A636B067@FreeBSD.org>
References:  <20020621135806Z.matusita@jp.FreeBSD.org> <20020621134520.G68827@dragon.nuxi.com> <20020621223209.GP76002@squall.waterspout.com> <xzp4rfv3bbb.fsf@flood.ping.uio.no> <20020622200545.GS76002@squall.waterspout.com> <20020622204229.GG53232@elvis.mu.org> <xzpheju21z0.fsf@flood.ping.uio.no> <3D152EAA.DB201738@FreeBSD.org> <xzp660a16x9.fsf@flood.ping.uio.no> <3D162074.A636B067@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Doug Barton <DougB@FreeBSD.org> writes:
> Dag-Erling Smorgrav wrote:
> > Doug Barton <DougB@FreeBSD.org> 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 <some
> 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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzp6609zsbt.fsf>