3 ms·

Yeah, but which one? Also, real businesses use -CURRENT, everybody knows that.

by justin66 26d ago

ArchOversight 26d ago
14.x-RELEASE if you still need i386 support, 15.x-RELEASE if you are installing new and want the longest longevity.
- justin66 25d ago
  Nobody is running i386 in production, I would think. It’s fun to imagine someone actually might be…
  - ArchOversight 23d ago
    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.
BoredomIsFun 26d ago
> Also, real businesses use -CURRENT, everybody knows that. No, not really.
- drewg123 26d ago
  I have thousands of CDN servers that would disagree with you. https://people.freebsd.org/~gallatin/talks/OpenFest2023.pdf https://people.freebsd.org/~gallatin/talks/OpenFest2023.pdf
  - BoredomIsFun 26d ago
    Netflix is just a single point. I'd never run current in production.
    - icedchai 26d ago
      It may be more common than you think. The latest version of pfSense CE is on 16.0-CURRENT.
      - CursedSilicon 26d ago
        PFsense gleefully ships vulnerable code to their own customers. They are an even worse data point https://arstechnica.com/gadgets/2021/03/buffer-overruns-license-violations-and-bad-code-freebsd-13s-close-call/ https://arstechnica.com/gadgets/2021/03/buffer-overruns-lice...
  - cperciva 26d ago
    -CURRENT is great for cattle. For pets, I recommend -RELEASE.
  - crest 25d ago
    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.

Yeah, but which one? Also, real businesses use -CURRENT, everybody knows that.

ArchOversight 26d ago

14.x-RELEASE if you still need i386 support, 15.x-RELEASE if you are installing new and want the longest longevity.

justin66 25d ago
Nobody is running i386 in production, I would think. It’s fun to imagine someone actually might be…
- ArchOversight 23d ago
  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.

BoredomIsFun 26d ago

> Also, real businesses use -CURRENT, everybody knows that. No, not really.

drewg123 26d ago
I have thousands of CDN servers that would disagree with you. https://people.freebsd.org/~gallatin/talks/OpenFest2023.pdf https://people.freebsd.org/~gallatin/talks/OpenFest2023.pdf
- BoredomIsFun 26d ago
  Netflix is just a single point. I'd never run current in production.
  - icedchai 26d ago
    It may be more common than you think. The latest version of pfSense CE is on 16.0-CURRENT.
    - CursedSilicon 26d ago
      PFsense gleefully ships vulnerable code to their own customers. They are an even worse data point https://arstechnica.com/gadgets/2021/03/buffer-overruns-license-violations-and-bad-code-freebsd-13s-close-call/ https://arstechnica.com/gadgets/2021/03/buffer-overruns-lice...
- cperciva 26d ago
  -CURRENT is great for cattle. For pets, I recommend -RELEASE.
- crest 25d ago
  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.