freebsd-version -k
says 13.0 RELEASE, uname -r
the same. Is it just me or some release mistake?I'm pretty sure you accidentally used the 13.0-RELEASE images. Because there's no way a 13.1-RELEASE would install 13.0.I have downloaded 13.1 amd64 memstick image, burned to USB disk, checked its sha512 sum, it matched so I've installed it. Afterwards a surprise,freebsd-version -k
says 13.0 RELEASE,uname -r
the same. Is it just me or some release mistake?
dd
'd the Rasperry Pi image to my SD card and FreeBSD 13.1 started out of the box.Anybody else have an easy go of it?
… i forgot to start ntpd so my system time wasn't correct. …
… Is it just me …
bectl list -c creation
The relnotes indicate that the freebsd-update utility can be used to do the upgrade. Why didn't you use that means? Is it unreliable?Exported my zfs pools, downloaded, burned to USB, booted, installed like usual, imported my zfs pools, updated, and configured. 10 minutes later my services were up and running without any pain at all.
… Is it unreliable?
Nah. I just don’t need cruft lying around after the upgrade from prior releases. Upgrading in place is fine, but I like recreatable installs where I know the dependencies are the current media plus packages.The relnotes indicate that the freebsd-update utility can be used to do the upgrade. Why didn't you use that means? Is it unreliable?
No, sorry. But since the Raspberry Pi 400 doesn't have a real time clock, it could have been any date.Can you recall how far out?
- pkg upgrade segfaults multiple times saying (null) has no equivalent package or something.
- pkg upgrade breaks in the middle, e.g. when upgrading freebsd-doc complaining it cannot replace some of the files and just quits.
… HTML format build has been disabled until separate localized-only build will work again without requiring the en_US build.