Ancestors

Toot

Written by Mathew Kane on 2024-11-19 at 03:45

Doing my first version upgrade with #FreeBSD. Gotta say, coming from the #Debian world of just issuing a few commands and hitting enter and not really thinking about it, to actually having to select a new point release does feel somewhat backward. And I wouldn't have even known that there was a new point release to upgrade to if there wasn't a "kernel mismatch" while trying to upgrade my packages.

=> More informations about this toot | More toots from berkough@mastodon.social

Descendants

Written by Eugene :emacs: :freebsd: on 2024-11-19 at 06:16

@berkough whoa, interesting, which package complained about "kernel mismatch"?

In terms of #freebsd you upgrading not to the new version of OS, but upgrading/patching the base system. So freebsd-update needs to know the version number from you, to understand which set of patches to download. Maybe you want to update just the minor version from older but supported release. Maybe you want the complete new features and bugs and updating to the new major version.

https://vermaden.wordpress.com/2023/01/22/keep-freebsd-desktop-updated/

=> More informations about this toot | More toots from evgandr@mas.to

Written by Eugene :emacs: :freebsd: on 2024-11-19 at 06:20

@berkough and, as I understand the BSD system, you shouldn't get "kernel mismatch error" while you stay on some not too old release version and use appropriate repositories and packages. Maybe there is a bug in some package, which was missed by someone maintainer of that package?

[#]freebsd

=> More informations about this toot | More toots from evgandr@mas.to

Written by not Evander Sinque on 2024-11-19 at 06:39

@berkough @evgandr that normally happens when you're on 13.2 while packages are built with 13.3 which usually is changed after 13.2 is eol.

=> More informations about this toot | More toots from FiLiS@mastodon.social

Written by Mathew Kane on 2024-11-23 at 05:27

@FiLiS @evgandr Yeah, I was upgrading from 14.0 to 14.1. It went really well. I actually don't mind the FreeBSD philosophy on a lot of things. This is my first time using it on a server though. I've always liked true Unix, but Linux always seemed to be the easiest to deploy in the past, now I have a great project box to play around with and learn FreeBSD.

=> More informations about this toot | More toots from berkough@mastodon.social

Written by David Chisnall (Now with 50% more sarcasm!) on 2024-11-19 at 08:22

@evgandr @berkough The package repo is built agains the oldest supported release in each stable branch. This version is encoded in packages. The pkg tool compares this against the version that a kernel reports. Newer point releases are backwards compatible, but they may add new things. If a point release introduces a new syscall, for example, then something built on it may use that syscall and fail on an older release.

If you are running a jail with an older (major) release, you can configure the kernel to report an older version in that jail.

I completely agree that it’s annoying that FreeBSD’s freebsd-update tool requires you to know which version you’re upgrading to. It’s one of a very long list of things I dislike about that tool. The PkgBase project is working to remove it and use pkg for the base system as well as for ports. It publishes official packages for 14, but they’re experimental. For 15, I hope it will be the default and we will be able to all forget it ever existed.

=> More informations about this toot | More toots from david_chisnall@infosec.exchange