Re:FreeBSD 14.5-Release
by ArchOversight on Tuesday September 08, 2026 @03:52PM
(#49616015)
14.x-RELEASE if you still need i386 support, 15.x-RELEASE if you are installing new and want the longest longevity.
Nobody is running i386 in production, I would think. It’s fun to imagine someone actually might be…
Re:FreeBSD 14.5-Release
by ArchOversight on Friday September 11, 2026 @12:12PM
(#49660845)
I know a ton of embedded shops that are running x86 (including some actual i386 still) in production, and will likely for years to come. That stuff was bullet proof, cheap and still runs today.
Some of these things have long lifetimes.
Re:FreeBSD 14.5-Release
by BoredomIsFun on Tuesday September 08, 2026 @03:08PM
(#49615223)
> Also, real businesses use -CURRENT, everybody knows that.
No, not really.
I have thousands of CDN servers that would disagree with you.
Re:FreeBSD 14.5-Release
by BoredomIsFun on Tuesday September 08, 2026 @03:39PM
(#49615811)
Netflix is just a single point. I'd never run current in production.
It may be more common than you think. The latest version of pfSense CE is on 16.0-CURRENT.
Re:FreeBSD 14.5-Release
by CursedSilicon on Tuesday September 08, 2026 @08:36PM
(#49619191)
PFsense gleefully ships vulnerable code to their own customers. They are an even worse data point
https://arstechnica.com/gadgets/2021/03/buffer-overruns-lice...
-CURRENT is great for cattle. For pets, I recommend -RELEASE.
A CDN *cache* server is a special case. Netflix cache appliances can accept the risk of running FreeBSD -CURRENT and upgrading half their fleet to the latest snapshot every ~2 weeks and we thank them for battle testing FreeBSD's active development branch in production. It really helps to reveal regressions (both correctness and performance) early in the subsystems and drivers that matter to their usecase.
Most users will neither be willing nor able to accept the trade-offs that Netflix chose.
Also, real businesses use -CURRENT, everybody knows that.