Re: New pam doesn't work with xdm 4.2
On Sun, 24 Feb 2002, David O'Brien wrote: > On Sun, Feb 24, 2002 at 10:15:44PM -0700, M. Warner Losh wrote: > > In message: <[EMAIL PROTECTED]> > > "David O'Brien" <[EMAIL PROTECTED]> writes: > > : On Sun, Feb 24, 2002 at 08:46:45PM -0700, M. Warner Losh wrote: > > : > You need a different version for -current than for -stable. Make sure > > : > you have the right version. > > : > > : I got the same problem with Xwrapper -- and it was compiled on this > > : 5-CURRENT w/in the past 6 months. > > > > xdm is the problem, not Xwrapper. > > I don't follow you. In my case it was Xwrapper -- I use ''startx''. I use startx, and used to use Xwrapper. Now I don't use Xwrapper, and use a setuid root X :-(. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New pam doesn't work with xdm 4.2
In message: <[EMAIL PROTECTED]> "David O'Brien" <[EMAIL PROTECTED]> writes: : On Sun, Feb 24, 2002 at 10:15:44PM -0700, M. Warner Losh wrote: : > In message: <[EMAIL PROTECTED]> : > "David O'Brien" <[EMAIL PROTECTED]> writes: : > : On Sun, Feb 24, 2002 at 08:46:45PM -0700, M. Warner Losh wrote: : > : > You need a different version for -current than for -stable. Make sure : > : > you have the right version. : > : : > : I got the same problem with Xwrapper -- and it was compiled on this : > : 5-CURRENT w/in the past 6 months. : > : > xdm is the problem, not Xwrapper. : : I don't follow you. In my case it was Xwrapper -- I use ''startx''. Ah, xdm was my problem Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New pam doesn't work with xdm 4.2
On Sun, Feb 24, 2002 at 10:15:44PM -0700, M. Warner Losh wrote: > In message: <[EMAIL PROTECTED]> > "David O'Brien" <[EMAIL PROTECTED]> writes: > : On Sun, Feb 24, 2002 at 08:46:45PM -0700, M. Warner Losh wrote: > : > You need a different version for -current than for -stable. Make sure > : > you have the right version. > : > : I got the same problem with Xwrapper -- and it was compiled on this > : 5-CURRENT w/in the past 6 months. > > xdm is the problem, not Xwrapper. I don't follow you. In my case it was Xwrapper -- I use ''startx''. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New pam doesn't work with xdm 4.2
In message: <[EMAIL PROTECTED]> "David O'Brien" <[EMAIL PROTECTED]> writes: : On Sun, Feb 24, 2002 at 08:46:45PM -0700, M. Warner Losh wrote: : > You need a different version for -current than for -stable. Make sure : > you have the right version. : : I got the same problem with Xwrapper -- and it was compiled on this : 5-CURRENT w/in the past 6 months. xdm is the problem, not Xwrapper. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New pam doesn't work with xdm 4.2
On Sun, Feb 24, 2002 at 08:46:45PM -0700, M. Warner Losh wrote: > You need a different version for -current than for -stable. Make sure > you have the right version. I got the same problem with Xwrapper -- and it was compiled on this 5-CURRENT w/in the past 6 months. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New pam doesn't work with xdm 4.2
In message: <[EMAIL PROTECTED]> Doug Barton <[EMAIL PROTECTED]> writes: : "M. Warner Losh" wrote: : > : > You need a different version for -current than for -stable. Make sure : > you have the right version. : : Version of what? There are no freebsd 5 binaries on xfree86.org's : website that I can see. I hope you're not saying that binary : compatability is broken by design in 5.0... I'm saying that PAM doesn't have versioning, so PAM modules are compatible between 4.x and 5.x. You must rebuild X under -current. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New pam doesn't work with xdm 4.2
"M. Warner Losh" wrote: > > You need a different version for -current than for -stable. Make sure > you have the right version. Version of what? There are no freebsd 5 binaries on xfree86.org's website that I can see. I hope you're not saying that binary compatability is broken by design in 5.0... -- "We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory." - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New pam doesn't work with xdm 4.2
You need a different version for -current than for -stable. Make sure you have the right version. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
New pam doesn't work with xdm 4.2
I installed XFree86 version 4.2 in binary format from the xfree86.org website. I just upgraded my -current installation to today's latest bits, and now I can't log in with xdm. This is the output to the console (minus date/host info for readability): PAM unable to dlopen(/usr/lib/pam_unix.so) PAM [dlerror: /usr/lib/pam_unix.so: Undefined symbol "setnetconfig"] PAM adding faulty module: /usr/lib/pam_unix.so PAM unable to dlopen(/usr/lib/pam_opie.so) PAM [dlerror: /usr/lib/libopie.so.2: Undefined symbol "__xuname"] PAM adding faulty module: /usr/lib/pam_opie.so PAM unable to dlopen(/usr/lib/pam_opieaccess.so) PAM [dlerror: /usr/lib/libopie.so.2: Undefined symbol "__xuname"] PAM adding faulty module: /usr/lib/pam_opieaccess.so This is my home workstation, so I can just use startx for now, but this should be fixed long term. Doug -- "We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory." - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
