Why are there occasional discrepancies in what is reported as the
running version?

After a recent upgrade I get 13.4-RELEASE-p1 as response to uname -a
but 13.4-RELEASE-p2 as response to freebsd-version .

When the upgrade completed I was told -p1 was installed,
when I ran freebsd-update fetch I was told no updates
were available or needed to run -p2.

Do some patches only register with some programs and not others?

-=-=-
The World Trade Center towers MUST rise again,
at least as tall as before...or terror has triumphed.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Louis Epstein <le@lekno.ws> wrote:

Why are there occasional discrepancies in what is reported as the
running version?

After a recent upgrade I get 13.4-RELEASE-p1 as response to uname -a
but 13.4-RELEASE-p2 as response to freebsd-version .

When the upgrade completed I was told -p1 was installed,

This repeats at every login

when I ran freebsd-update fetch I was told no updates
were available or needed to run -p2.

Do some patches only register with some programs and not others?

-=-=-
The World Trade Center towers MUST rise again,
at least as tall as before...or terror has triumphed.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Louis Epstein <le@lekno.ws> writes:

Louis Epstein <le@lekno.ws> wrote:

Why are there occasional discrepancies in what is reported as the
running version?

After a recent upgrade I get 13.4-RELEASE-p1 as response to uname -a
but 13.4-RELEASE-p2 as response to freebsd-version .

When the upgrade completed I was told -p1 was installed,

This repeats at every login

Is this not just the normal thing where -p2
didn't need to update the kernel?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Jan 5, 2025 at 2:24:21 AM CST, "Jesse Rehmer" <jesse.rehmer@blueworldhosting.com> wrote:

On Jan 2, 2025 at 9:54:37 PM CST, "Lowell Gilbert" <lgusenet@be-well.ilk.org>
wrote:

Louis Epstein <le@lekno.ws> writes:

Louis Epstein <le@lekno.ws> wrote:

Why are there occasional discrepancies in what is reported as the
running version?

After a recent upgrade I get 13.4-RELEASE-p1 as response to uname -a
but 13.4-RELEASE-p2 as response to freebsd-version .

When the upgrade completed I was told -p1 was installed,

This repeats at every login

Is this not just the normal thing where -p2
didn't need to update the kernel?

Most likely. I recommend using "freebsd-version -kru" to get the list of versions, from the manpage:

-k Print the version and patch level of the installed kernel.
Unlike uname(1), if a new kernel has been installed but the
system has not yet rebooted, freebsd-version will print the
version and patch level of the new kernel.

-r Print the version and patch level of the running kernel.
Unlike uname(1), this is unaffected by environment variables.

-u Print the version and patch level of the installed userland.
These are hardcoded into freebsd-version during the build.

There are some patch releases that do not update the kernel, or only the userland tools are updated. This causes confusion from time to time and this comes up on the FreeBSD forums often.

And I can confirm on my 13.4 system I see the following:

# freebsd-version -kru
13.4-RELEASE-p1
13.4-RELEASE-p1
13.4-RELEASE-p2

This is normal. In the p2 patch release the kernel was not updated.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Jan 2, 2025 at 9:54:37 PM CST, "Lowell Gilbert" <lgusenet@be-well.ilk.org> wrote:

Louis Epstein <le@lekno.ws> writes:

Louis Epstein <le@lekno.ws> wrote:

Why are there occasional discrepancies in what is reported as the
running version?

After a recent upgrade I get 13.4-RELEASE-p1 as response to uname -a
but 13.4-RELEASE-p2 as response to freebsd-version .

When the upgrade completed I was told -p1 was installed,

This repeats at every login

Is this not just the normal thing where -p2
didn't need to update the kernel?

Most likely. I recommend using "freebsd-version -kru" to get the list of versions, from the manpage:

-k Print the version and patch level of the installed kernel.
Unlike uname(1), if a new kernel has been installed but the
system has not yet rebooted, freebsd-version will print the
version and patch level of the new kernel.

-r Print the version and patch level of the running kernel.
Unlike uname(1), this is unaffected by environment variables.

-u Print the version and patch level of the installed userland.
These are hardcoded into freebsd-version during the build.

There are some patch releases that do not update the kernel, or only the userland tools are updated. This causes confusion from time to time and this comes up on the FreeBSD forums often.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)