4 ms·

As a long term FreeBSD user who was bitten by recent (8 up to 11) source update issues I would have loved a disclaimer upfront: "we broke it again" or "we final

by jlg23 8y ago

As a long term FreeBSD user who was bitten by recent (8 up to 11) source update issues I would have loved a disclaimer upfront: "we broke it again" or "we finally got back to normal"....

siffland 8y ago
Support for FreeBSD 8 ended sometime in 2015, FreeBSD 11 did not come out until mid 2016 and if it was a recent update i can see why the huge jump could cause update issues. The answer to what caused your issue was most likely in the UPDATING file in the source directory. I have been using FreeBSD since 3.x in 1999 and have only been bitten by source updates when I failed to follow procedure and read the UPDATING file. Anyway source update from 11.2 to 12 worked for me fine.
jandrese 8y ago
Going from 8 to 11 you would probably be best off by backing up your data (do this anyway) and making a fresh 11 install. Reinstalling apps is super easy with pkg. I've never seen an OS updater that is happy to jump 3 major versions at once, especially since the old one has fallen off of even legacy support.
- jlg23 8y ago
  I am not talking about 8 to 11 in one go. With 8.x I experienced the first literally broken source update and a few came after that. I've switched from Linux to FreeBSD in 1999 because I was fed up with chunky/broken binary updates. One used to be able to compile 3 versions ahead on a running system and boot into a working, clean setup. I am lazy, of course I tried (and succeeded most of the time). But since 8 even the standard practice of migrating one major version at a time as well as updates from latest n.x to m.0 was broken for people who did not drink the "pkg and freebsd-update!" kool-aid. My allergies to that are raid controllers not supported by GENERIC kernel and a general preference to include into software only what I need - make.conf makes that really easy and maintenance is a breeze simply because we're not hit by as many security issues.
GalacticDomin8r 8y ago
8 straight to 11 is not a supported process at any point in the FreeBSD timeline. The canonical path is something like(this is documented somewhere): 8.0 > 8.4 > 9.0 > 9.3 > 10.0 > 10.4 > 11.0 > 11.2 Although I've had decent luck jumping straight from X-STABLE branches.
- jlg23 8y ago
  > 8.0 > 8.4 > 9.0 > 9.3 > 10.0 > 10.4 > 11.0 > 11.2 Yes, something like this. For 11.x I had to go to a specific patch level first (IIRC due to LLVM version bump).

by jlg23 8y ago

As a long term FreeBSD user who was bitten by recent (8 up to 11) source update issues I would have loved a disclaimer upfront: "we broke it again" or "we finally got back to normal"....

siffland 8y ago

Support for FreeBSD 8 ended sometime in 2015, FreeBSD 11 did not come out until mid 2016 and if it was a recent update i can see why the huge jump could cause update issues. The answer to what caused your issue was most likely in the UPDATING file in the source directory. I have been using FreeBSD since 3.x in 1999 and have only been bitten by source updates when I failed to follow procedure and read the UPDATING file. Anyway source update from 11.2 to 12 worked for me fine.

jandrese 8y ago

Going from 8 to 11 you would probably be best off by backing up your data (do this anyway) and making a fresh 11 install. Reinstalling apps is super easy with pkg. I've never seen an OS updater that is happy to jump 3 major versions at once, especially since the old one has fallen off of even legacy support.

jlg23 8y ago
I am not talking about 8 to 11 in one go. With 8.x I experienced the first literally broken source update and a few came after that. I've switched from Linux to FreeBSD in 1999 because I was fed up with chunky/broken binary updates. One used to be able to compile 3 versions ahead on a running system and boot into a working, clean setup. I am lazy, of course I tried (and succeeded most of the time). But since 8 even the standard practice of migrating one major version at a time as well as updates from latest n.x to m.0 was broken for people who did not drink the "pkg and freebsd-update!" kool-aid. My allergies to that are raid controllers not supported by GENERIC kernel and a general preference to include into software only what I need - make.conf makes that really easy and maintenance is a breeze simply because we're not hit by as many security issues.

GalacticDomin8r 8y ago

8 straight to 11 is not a supported process at any point in the FreeBSD timeline. The canonical path is something like(this is documented somewhere): 8.0 > 8.4 > 9.0 > 9.3 > 10.0 > 10.4 > 11.0 > 11.2 Although I've had decent luck jumping straight from X-STABLE branches.

jlg23 8y ago
> 8.0 > 8.4 > 9.0 > 9.3 > 10.0 > 10.4 > 11.0 > 11.2 Yes, something like this. For 11.x I had to go to a specific patch level first (IIRC due to LLVM version bump).