Date: 05 May 2002 13:48:30 +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: <xzpk7qiyfw1.fsf@flood.ping.uio.no> In-Reply-To: <20020504230811.T1525-100000@master.gorean.org> References: <20020504230811.T1525-100000@master.gorean.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug Barton <DougB@FreeBSD.org> writes: > 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_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 Yep, these modules don't exist in -STABLE. You should keep your old /etc/pam.conf around for -STABLE programs. > 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 It seems libopie should have had its major bumped with libc, but didn't. But why on earth is xdm trying to use pam_opie? 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?xzpk7qiyfw1.fsf>