Discussion
Loading...
Post
@iodomi it's my first choice for most workloads. You can have a look here: https://it-notes.dragas.net/categories/freebsd/
And especially here: https://it-notes.dragas.net/2024/10/03/i-solve-problems-eurobsdcon/
@stefano great, thanks :D
@iodomi I've been using FreeBSD on servers since FreeBSD 4.something. It... just works. I've got a couple of machines that were upgraded in place from 9 to 14 (9 was release in 2012, 14 is still supported). The base system config has barely changed in that time.
All third-party things (i.e. the things that the server exists to run) are all updated regularly and available in packages.
Podman is somewhat immature, but mostly works for container things. There are things like @BastilleBSD for managing jails, but they have largely missed the benefits of modern container orchestration and it feels more like just managing a bunch of machines.
@david_chisnall sounds like very stable experience, thanks for sharing!
@iodomi The nice thing I've found about FreeBSD is that I only need to learn new stuff when I want to do something new.
Moving from from-source builds of packages required me to learn to use pkg, but the old way still works. Using ZFS for snapshots and backups meant learning some new things, but UFS and GEOM are still there if I don't want to (or I can use the minimal feature set of ZFS and pretend it's UFS).
The way that I learned to configure the network 20+ years ago is still the way I configure a network. I learned a few new things for IPv6 autoconfiguration. The firewall rules I wrote in pf back then still work. Along the way, pf grew some new features and I need to learn something if I want to use them, but if I don't, things remain the same.