Ancestors

Toot

Written by Pete Orrall on 2024-12-17 at 01:00

Just updated my kickass laptop to #FreeBSD 14.2. The upgrade was smooth as per usual.

Downloading the updates took a while since this laptop has a 100mb NIC. This ancient system has a dual core Centrino and a couple GB of RAM. FreeBSD runs quite nicely on it.

Amusingly, however, neofetch still reports I am running 14.1 and uname -a reports the correct version. Hmmm. 🤔

=> View attached media

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

Descendants

Written by Pete Orrall on 2024-12-17 at 02:07

Apparently rebooting fixes the discrepancy between reported versions. Who'd have thunk? 🤦‍♂️

[#]FreeBSD has breathed new life into this ancient #laptop. Switched from #twm to #openbox and surfing the #web with #elinks.

Admittedly I did cheat and replace the 5,400 RPM hard drive with a 1TB SSD. I'm not masochistic enough for that, particularly when I had something exponentially better on hand. 😆

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

Written by greggyb on 2024-12-17 at 12:15

@peteorrall when you update versions, the kernel is still running the version that is in memory, i.e. the old version.

There's no way to restart the kernel process to use the bits on disk other than to restart the machine.

Similarly, if you upgrade a package and have a running process for that, the upgrade will not change the version of the currently executing process.

=> More informations about this toot | More toots from greggyb@mastodon.sdf.org

Written by Pete Orrall on 2024-12-17 at 13:50

@greggyb @subnetspider @evgandr @jeffpc

I updated from 14.1-RELEASE. Ran frebsd-update -r 14.1-RELEASE upgrade. It downloaded and installed patches. I was then presented with a message that the kernel was updated and a reboot was needed, and then I'd need to run freebsd-update install to continue with it.

I've updated FreeBSD systems before and the process was the same. Last night however was the 1st time using neofetch - so perhaps the reported kernel version discrepancy was always there?

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

Written by Josef 'Jeff' Sipek on 2024-12-17 at 14:03

@peteorrall @greggyb @subnetspider @evgandr Weird. I don’t know what neofetch does to get the version numbers 🤷‍♂️

=> More informations about this toot | More toots from jeffpc@mastodon.radio

Written by Graham Perrin on 2024-12-18 at 23:02

@peteorrall I guess, you followed the FreeBSD Handbook.

True?

The book lacks the advice to restart the OS.

Compare with release documentation,

https://www.freebsd.org/releases/14.2R/

[#]FreeBSD

=> More informations about this toot | More toots from grahamperrin@bsd.cafe

Written by Dianora (Diane Bruce) on 2024-12-29 at 15:09

@peteorrall I'm on a FreeBSD laptop right now. ;) Look at my pinned posts I also have a BSD instance.

=> More informations about this toot | More toots from Dianora@ottawa.place

Written by Josef 'Jeff' Sipek on 2024-12-17 at 13:37

@peteorrall In case this helps… ‘freebsd-version -kru’ is what I use to get the (1) installed kernel, (2) running kernel, (3) user space versions. If the first two don’t match, a reboot is in order. The kernel may not match user space if there was a user space-only patch.

=> More informations about this toot | More toots from jeffpc@mastodon.radio