Re: Where is 1600018?

From: Kevin Oberman <rkoberman_at_gmail.com>
Date: Fri, 01 May 2026 21:08:58 UTC
On Fri, May 1, 2026 at 1:34 PM Herbert J. Skuhra <herbert@gojira.at> wrote:

> On Fri, 01 May 2026 20:04:57 +0200, Kevin Oberman wrote:
> >
> > With the late security notices I decided to update my CURRENT system.
> > Updated /ust/src with 'git pull' and rebuilt everything. The kernel
> version
> > still shows as 1600017.
> > FreeBSD ptavv 16.0-CURRENT FreeBSD 16.0-CURRENT #99
> > main-n285595-0ed292531e04: Fri May  1 07:28:07 PDT 2026
> > root@ptavv:/usr/obj/usr/src/amd64.amd64/sys/GENERIC
> > amd64 1600017
> >
> > Why am I not getting 1600018? Do I need to turn off meta-mode and build
> > the kernel again?
>
> If the git revision (0ed292531e04) matches with your checkout then
> it's too old. The bump in sys/sys/param.h happened about 4 hours later
> (1569e2334ab5).
>
> $ uname -KU
> 1600018 1600018
>
>
Still not sure about some link to meta-mode but almost certainly a race
condition. Ever since the kmod ports came into existence, I have updated my
only "built from sources system" when 'pkg version' showed that they had
the version number bumped. It's always worked until this time. It looks
like I pulled the updated source after the commit, but before it was fully
propagated to whichever the pull loaded the version I built.

Sorry for the noise.
-- 
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683