On Mon, 7 Oct 2002, suken woo wrote:
> >>xdm broken on current when login . i knew this is the pam module
> >>problem,but how could i fix it?
> >
> >Chances are, you built your X11 with an old -CURRENT system, and since
> >then the ABI for the PAM stuff has changed in -CURRENT, so your old X11 n
--- Begin Message ---
Robert Watson wrote:
>On Mon, 7 Oct 2002, suken woo wrote:
>
>
>
>>xdm broken on current when login . i knew this is the pam module
>>problem,but how could i fix it?
>>
>>
>
>Chances are, you built your X11 with an old -CURRENT system, and since
>then the ABI for th
Robert Watson wrote:
>On Mon, 7 Oct 2002, suken woo wrote:
>
>
ok, here's i get the messages
Oct 7 00:38:18 wsk -:0 : unable to dlopen(/usr/lib/pam_nologin.so)
Oct 7 00:38:18 wsk -:0 : [dlerror: /usr/lib/pam_nologin.so:
Undefined symbol "_openpam_log"]
Oct 7 00:38:18 wsk -
On Mon, 7 Oct 2002, suken woo wrote:
> xdm broken on current when login . i knew this is the pam module
> problem,but how could i fix it?
Chances are, you built your X11 with an old -CURRENT system, and since
then the ABI for the PAM stuff has changed in -CURRENT, so your old X11 no
longer talk
>Date: Mon, 07 Oct 2002 12:48:33 +0800
>From: suken woo <[EMAIL PROTECTED]>
>xdm broken on current when login .
It isn't for me, and I've been tracking -CURRENT daily for some time.
>i knew this is the pam module
>problem,but how could i fix it?
Well, absent any clues as to why you think it
hello folks:
xdm broken on current when login . i knew this is the pam module
problem,but how could i fix it?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
