Solved freebsd update bin

Hello.
How to fix it?
uname -rms
FreeBSD 13.1-RELEASE-p2 amd64
Further.
# freebsd-update fetch
# freebsd-update install
src component not installed, skipped
Installing updates...Scanning //usr/share/certs/blacklisted for certificates...
Scanning //usr/share/certs/trusted for certificates...
Scanning //usr/local/share/certs for certificates...
done.
Reboot server, look.
uname -rms
FreeBSD 13.1-RELEASE-p3 amd64

freebsd-version
13.1-RELEASE-p5
I start again.
# freebsd-update fetch
src component not installed, skipped
Looking up update.FreeBSD.org mirrors... none found.
Fetching metadata signature for 13.1-RELEASE from update.FreeBSD.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.

No updates needed to update system to 13.1-RELEASE-p5.
# freebsd-update install
src component not installed, skipped
No updates are available to install.
Run '/usr/sbin/freebsd-update fetch' first.
 
fix what?
freebsd-version -kru to show versions of the installed kernel, the running kernel and userland
If there there no updates to the kernel but there were to userland then you will see the kernel at say -p3 and the userland at say -p5.
I think there were multiple threads asking about this and the last couple of binary updates were against userland not kernel.
 
fix what?
freebsd-version -kru to show versions of the installed kernel, the running kernel and userland
If there there no updates to the kernel but there were to userland then you will see the kernel at say -p3 and the userland at say -p5.
I think there were multiple threads asking about this and the last couple of binary updates were against userland not kernel.
# freebsd-version -kru
13.1-RELEASE-p3
13.1-RELEASE-p3
13.1-RELEASE-p5
Not understood.
Why different data?
uname -rms
FreeBSD 13.1-RELEASE-p3 amd64
freebsd-version
13.1-RELEASE-p5
 
20221129:
13.1-RELEASE-p5 FreeBSD-SA-22:15.ping
FreeBSD-EN-22:28.heimdal

Stack overflow in ping [SA-22:15.ping]

Regression in Heimdal KDC [EN-22:28.heimdal]
Then what about these vulnerabilities?
In p5!
 
How difficult everything is.
It would be much easier if there was a single version of space as an update from /usr/src/
Understood.
# freebsd-version -kru
13.1-RELEASE-p3 - loaded new kernel
13.1-RELEASE-p3 - install new kernel
13.1-RELEASE-p5 - install new update world.
 
bagas, there is a single version. But the version string for a kernel can only be set at build time. So, if the kernel wasn't rebuilt (because there was no need to do so as no code changed), it will keep showing the old version. If you'd build your own custom kernel after the update to -p5, the kernel version would show -p5 as well.

Probably the documentation should be improved, the major source of confusion seems to be uname. The manpage should make explicit that this tool will only show the kernel version and that this version doesn't need to be up-to-date with the currently installed freebsd version.
 
freebsd-version also seems be be causing confusion.
It shouldn't. By default, it prints the userland version, which is the relevant information most of the time. The manpage also documents the fact that the kernel might have an older version.
It would be much better if there was only one answer.
By default, there is only one. But being able to know the versions of both the installed and the running kernel is helpful, for example to know whether you must reboot.
 
  • Like
Reactions: mer
I agree it shouldn’t be causing confusion and once you know what freebsd-version is telling you it makes sense. And there’s no point building and shipping and installing a kernel where nothing has changed apart from a version number.

It feels like at least 5-10 non-issues on the forums recently with confusion about kernel version versus userland version.

I don’t know what the answer is but it seems to be something that is causing confusion.
 
I don’t know what the answer is but it seems to be something that is causing confusion.
And that's where I say: I think it's uname, at least for those who do read manpages. uname is the canonic (unix) tool to know the system version, so especially if you don't know FreeBSD deeply yet, it's probably the first thing you try. And the uname(1) manpage doesn't make it explicit enough that it is the version obtained from the running kernel, neither does it mention that the kernel isn't updated with every patch release (like the freebsd-version(1) manpage does).
 
And that's where I say: I think it's uname, at least for those who do read manpages. uname is the canonic (unix) tool to know the system version, so especially if you don't know FreeBSD deeply yet, it's probably the first thing you try. And the uname(1) manpage doesn't make it explicit enough that it is the version obtained from the running kernel, neither does it mention that the kernel isn't updated with every patch release (like the freebsd-version(1) manpage does).
It's how it should be for me. Uname is a generic posix tool, freebsd-version is not.
Seems more like a thing for the freebsd-update manpage. In any case, it is indicated in the handbook.
ℹ️ NOTE
Usually, the user needs to be prepared to reboot the system. To know if the system requires a reboot due to a kernel update, execute the commands freebsd-version -k and uname -r. Reboot the system if the outputs differ.
 
CuatroTorres Say you don't read every single word of the handbook upfront (almost nobody does) and after an upgrade and checking uname (because, yes, it is the "standard" tool you already know from other systems), you're confused. We can't help people who just don't read any docs of course, but say you're not one of them, which document are you most likely to read? Probably uname(1), don't you think? That's why I think it should be improved on that topic...
 
On second thought, including a note in uname does not alter the use of the command. However, the update is not trivial and you need to go to the handbook.
 
man <whatever> is the first thing in my muscle memory, followed by "hey duck duck go, what do you know about whatever".

But of course that's because it's been a while since I've had a need to look at the handbook, but often duck duck go gives me links to the handbook :)
 
Everyone seems to run into this at some point (and it looks like a new person does every few days). Once you understand freebsd-version -kru though, you're good to go.

It does serve a good purpose, as opposed to having a single version: you clearly know when you need to reboot the server, vs restart specific services, vs do nothing at all.

- running and kernel differ = reboot machine
- running and kernel are same, some sshd files changed in world = reboot sshd
- running and kernel are same, nothing related to services changed = don't do anything
 
  • Like
Reactions: mer
Back
Top