Date: Sat, 1 Jun 2024 20:23:15 +0100 From: void <void@f-m.fm> To: freebsd-current@freebsd.org Subject: Re: May 2024 stabilization week Message-ID: <Zlt1I92bkg4D1g_R@int21h> In-Reply-To: <038DCC90-FBB1-4413-80D5-EDB0A0AF53BD@karels.net> References: <ZlQ9mKCGqVzWh24m@cell.glebi.us> <ZlVcbpyIxZIzjlNy@cell.glebi.us> <ZlhxrlrY6eWV9i6g@int21h> <8DCD6FBB-F913-4D79-8ED4-69D302C31505@karels.net> <ZlthzyV3c6cM2Tjd@int21h> <038DCC90-FBB1-4413-80D5-EDB0A0AF53BD@karels.net>
index | next in thread | previous in thread | raw e-mail
On Sat, Jun 01, 2024 at 03:13:23PM -0400, Mike Karels wrote:
>Sorry, this is a different instance of the problem that pkg had with
>its scripts. This is fallout from removal of security_daily_compat_var.
>The 900.tcpwrap script was modified for this in April. Did you run
>etcupdate?
yes - etcupdate -p after make installkernel and etcupdate -B after
make installworld; then make check-old then yes | make delete-old
then yes | make delete-old-libs then reboot.
Might be relevant:
1. arm64.aarch64
2. ufs only & MBR
3. ISTR the canonical way of source upgrading involves a reboot
after etcupdate -p to boot into the new kernel and then do the
installworld. i didn't do that.
--
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Zlt1I92bkg4D1g_R>