Date: Tue, 8 Aug 2023 17:45:46 +0200 From: Michael Grimm <trashcan@ellael.org> To: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org> Cc: freebsd-current@freebsd.org Subject: [SOLVED] 14-CURRENT | alternatives for defunct /usr/lib/pam_opie.so? Message-ID: <5CD088DD-701D-49CC-8DAD-5E827D03EF87@ellael.org> In-Reply-To: <86350th7pa.fsf@ltc.des.no> References: <613E7476-6553-4A74-BF33-EF95D95F25A9@ellael.org> <86350th7pa.fsf@ltc.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling Sm=C3=B8rgrav <des@FreeBSD.org> wrote: > Michael Grimm <trashcan@ellael.org> writes: >> I'm currently in the process to prepare for upcoming 14-STABLE. Thus, >> I upgraded one of my sytems from 13-STABLE to 14-CURRENT. >=20 > Did you run etcupdate? I was just about to report that I somehow managed to "solve" this issue = with pam_opie, but not knowing how. Yep, I did run etcupdate, but not before reporting my issue. This = morning I did reinstall world, kernel and all my ports and ran etcupdate = on host and in all my ports. Removing security/opie afterwards and = everything is fine now. Sorry for the noise, I should have known better! Regards and thanks to all, Michael=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5CD088DD-701D-49CC-8DAD-5E827D03EF87>