5 ms·
Ah thanks. It happens this box was updated from 10.1 -p16 to -p17 recently. Generally, on most OSes/apps, smaller upgrade deltas = less breakage. Afterwards,
by bmir-alum-007 11y ago
Ah thanks. It happens this box was updated from 10.1 -p16 to -p17 recently. Generally, on most OSes/apps, smaller upgrade deltas = less breakage.
Afterwards, folks may want to rebuild outdated ports to avoid stale shared libs from the previous release using something like:
(cd /usr/ports && make update && portmaster -a)
# or: -aBg saves new packages for re/installation on other boxes
Finally, check ports for any unpatched security issues (should be 0):
pkg audit -F
EDIT: only rebuild outdated ports
- feld 11y agoOnly for some kernel modules because a few occasionally have an issue but generally they're not supposed to. Otherwise FreeBSD is backwards compatible. You can run FreeBSD 2.0 binaries and libraries just fine if you want. There's some on the official FreeBSD cluster, I think. In case you didn't know, the official FreeBSD packages for 10.1 and 10.2 will continue to be built on 10.1 -- the oldest supported release in the 10.x train.
- bmir-alum-007 11y agoSounds like userland is mostly perpetually backward-compatible. If so, that would be awesomesauce.
- Sanddancer 11y agoPretty close. Compatibility back to FreeBSD 4 is a port package away, and there's a kernel module to support a.out binaries if you really need to run those 20+ year old programs. Some of the older syscalls don't have 32 bit wrappers, though, so you may not get full support for absolutely positively everything without emulation, but pretty damn close.