PAM problem

Kevin Oberman oberman at es.net
Thu Feb 22 23:31:32 UTC 2007


> Date: Thu, 22 Feb 2007 17:33:28 +0200
> From: Marinos Ilias <marinosi at ceid.upatras.gr>
> Sender: owner-freebsd-current at freebsd.org
> 
> Thank you Oliver.
> 
> I did reinstall all my ports too, but I could not understand why this
> problem occured.I still cannot.I reinstalled sudo and now it works
> fine , just like my other installed ports.

Wow, that was a long line.

-current is, by definition not -stable. APIs and ABIs changes rather
frequently and that breaks things that were built for the ABIs in older
versions of FreeBSD. Before v7 moves to the sedate life of -stable,
there will be compatibility shims and a V6 compatibility port built to
keep old binaries working, but that is a lot of work and simply does not
happen until the ABIs are frozen for 7.0-Release.

This means that you will spend a lot more time rebuilding ports when you
run -current. It is not for the faint of heart or those who don't have
the time to build ports rather more often then they are used to.

If you are asking specifically about sudo, I have no idea which libraries
caused the failure, but it is not unexpected that most ports can do this
from time to time.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman at es.net			Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 224 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20070222/191ff493/attachment.pgp


More information about the freebsd-current mailing list