Bug 233806 - Incorrect patchlevel number (p5) after freebsd-update
Summary: Incorrect patchlevel number (p5) after freebsd-update
Status: Closed Works As Intended
Alias: None
Product: Base System
Classification: Unclassified
Component: misc (show other bugs)
Version: 11.2-RELEASE
Hardware: amd64 Any
: --- Affects Many People
Assignee: freebsd-bugs mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-05 17:21 UTC by Alex Christensen
Modified: 2018-12-05 18:07 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Christensen 2018-12-05 17:21:42 UTC
After update (with freebsd-update) to 11.2-RELEASE-p6, command "uname -r" reports version 11.2-RELEASE-p5:

root@www:/ # freebsd-update fetch
src component not installed, skipped
Looking up update.FreeBSD.org mirrors... 2 mirrors found.
Fetching metadata signature for 11.2-RELEASE from update1.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.

No updates needed to update system to 11.2-RELEASE-p6.
root@www:/ # uname -r
11.2-RELEASE-p5
root@www:/ #

I rebooted the server, but it did not help - p5
Comment 1 Larry Rosenman freebsd_committer 2018-12-05 17:52:39 UTC
Probably -p6 was just a *USERLAND* change, and not a *KERNEL* change.

Kernel changes will change uname, USERLAND changes won't

what does:
freebsd-version -ku 
show?
Comment 2 Alex Christensen 2018-12-05 17:58:41 UTC
(In reply to Larry Rosenman from comment #1)

root@www:/ # freebsd-version -ku
11.2-RELEASE-p5
11.2-RELEASE-p6
root@www:/ # uname -a
FreeBSD www.[censored].ru 11.2-RELEASE-p5 FreeBSD 11.2-RELEASE-p5 #0: Tue Nov 27 09:33:52 UTC 2018     root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
root@www:/ #
Comment 3 Larry Rosenman freebsd_committer 2018-12-05 18:00:26 UTC
so that proves my point.

The uname /freebsd-version -k value is the kernel,
freebsd-version -u is the userland version.

They do *NOT* have to be the same. There is no bug here.
Comment 4 Alex Christensen 2018-12-05 18:05:56 UTC
(In reply to Larry Rosenman from comment #3)

Thank you!