6 ms·

Running this on our AWS sandbox ec2 instance after snapshotting it: freebsd-update fetch install && freebsd-update -r 10.2-RELEASE upgrade EDIT: Updat

Running this on our AWS sandbox ec2 instance after snapshotting it: freebsd-update fetch install && freebsd-update -r 10.2-RELEASE upgrade EDIT: Updates to 10.1-RELASE-p17 (currently) before upgrading

cperciva 11y ago
Quick reminder (not that you necessarily need it, but lots of people do forget this): It's usually a good idea to run freebsd-update fetch and install any updates (rebooting if necessary) before you try to upgrade to a new release. On occasion there have been problems in freebsd-update which need to be fixed. EDIT: Don't run 'freebsd-update fetch install && freebsd-update ... upgrade', since if the first command installs kernel updates you might need to reboot before downloading upgrades. (Ok, it's very unlikely. But it's theoretically possible that a kernel update would affect the upgrade-downloading process.)
- 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 ago
    Only 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 ago
      Sounds like userland is mostly perpetually backward-compatible. If so, that would be awesomesauce.
      - Sanddancer 11y ago
        Pretty 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.
bmir-alum-007 11y ago
FreeBSD ip-172-x-x-x 10.2-RELEASE FreeBSD 10.2-RELEASE #0 r286666: Wed Aug 12 19:31:38 UTC 2015 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC i386 Woohoo!

cperciva 11y ago

Quick reminder (not that you necessarily need it, but lots of people do forget this): It's usually a good idea to run freebsd-update fetch and install any updates (rebooting if necessary) before you try to upgrade to a new release. On occasion there have been problems in freebsd-update which need to be fixed. EDIT: Don't run 'freebsd-update fetch install && freebsd-update ... upgrade', since if the first command installs kernel updates you might need to reboot before downloading upgrades. (Ok, it's very unlikely. But it's theoretically possible that a kernel update would affect the upgrade-downloading process.)

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 ago
  Only 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 ago
    Sounds like userland is mostly perpetually backward-compatible. If so, that would be awesomesauce.
    - Sanddancer 11y ago
      Pretty 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.

bmir-alum-007 11y ago

FreeBSD ip-172-x-x-x 10.2-RELEASE FreeBSD 10.2-RELEASE #0 r286666: Wed Aug 12 19:31:38 UTC 2015 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC i386 Woohoo!