Note that p1 is userland only, so your kernel will not show the -p1:
Code:root@fbsd-test:~ # freebsd-version -urk 14.3-RELEASE 14.3-RELEASE 14.3-RELEASE-p1
root@fbsd:/home/judd # freebsd-version -urk
14.3-RELEASE
14.3-RELEASE
14.3-RELEASE-p1
Last time I've tried freebsd-version, there wasn't a matter of order of flags, kru and urk were same, is it a bug?Note that p1 is userland only, so your kernel will not show the -p1:
Code:root@fbsd-test:~ # freebsd-version -urk 14.3-RELEASE 14.3-RELEASE 14.3-RELEASE-p1
The following options are available:
-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.
-j jail Print the version and patch level of the installed userland
in the given jail specified by jid or name. This option can
be specified multiple times.
If several of the above options are specified, freebsd-version will print
the installed kernel version first, then the running kernel version, next
the userland version, and finally the userland version of the specified
jails, on separate lines. If neither is specified, it will print the
userland version only.
The version string comes from /usr/src/sys/conf/newvers.sh and is "baked" in the kernel at compile time. That's why the version of the kernel and the version of the userland can differ after certain patch updates. As is the case now, p1 fixed a userland issue, no changes were made to the kernel. Therefor the kernel wasn't recompiled for something that's only cosmetic (no changes were made to the kernel, only the version string changed because of newvers.sh).When you build kernel from source everything is p1