Why I run FreeBSD for my home servers (2024)

(aumont.fr)

190 points psxuaw | 1 comments | 31 Mar 25 12:59 UTC | HN request time: 0.206s | source

Show context

nine_k ◴[31 Mar 25 16:28 UTC] No.43536856[source]▶

If systemd is the reason, there are several good distros without systemd (I run Void Linux in particular).

If "kubesomething" is the reason, there's no requirement to use it. I think most people don't run it on their home servers.

If containers are the reason, then again, they are not a requirement. But they are pretty similar to BSD's jails. I don't think they are particularly complex.

FreeBSD has a number of strong suits: ZFS, a different kernel and network stack, a cohesive system from a small(ish) team of authors, the handbook, etc. But the usual Linux hobgoblins listed above are a red herring here, to my mind.

replies(5): >>43536992 #>>43541101 #>>43541384 #>>43541789 #>>43543787 #

znpy ◴[01 Apr 25 07:19 UTC] No.43543787[source]▶

>>43536856 #

> If systemd is the reason, there are several good distros without systemd (I run Void Linux in particular).

There are people in the FreeBSD camp that actually do advocate for something like systemd in FreeBSD. See "The Tragedy of systemd": https://www.youtube.com/watch?v=o_AIw9bGogo

replies(2): >>43544255 #>>43549306 #

1. toast0 ◴[01 Apr 25 17:21 UTC] No.43549306[source]▶

>>43543787 #

Something like systemd might be useful. There are some aspects of systemd that make sense and are useful.

There's other stuff like eliminating boot interactivity, so you can't hit ctrl-c or any other keys to cancel waiting for dhcp on network ports that aren't plugged in, that really bother me.

I also don't think a FreeBSD init/system supervision system would go and re-implement dns, ntp, and whatever else, including redoing security mistakes from decades ago.

↑