Live data from Hacker News

Why I run FreeBSD for my home servers (2024)

aumont.fr

151–160 of 251 posts

Re: Why I run FreeBSD for my home servers (2024)

#151

Alpine, Void, Devuan or Artix all would have allowed author to use Linux while addressing his points of concern. I don't think the BSD's have real advantages anymore since so much core performance stuff is in Linux first. When most of the software is available on all these platforms, it mostly comes down to user preference.

[deleted]

Re: Why I run FreeBSD for my home servers (2024)

#152
post #106
post #93

Earlier quoted context omitted.

ZFS is a first class part of FreeBSD. you can use it on linux, but it will always have some rough edges. How rough it open to question though, for some it works well.

Used ZFS on Debian in production for 8 years, yet to experience rough edges but always interested to learn.

My experience with ZFS (over 10 years ago now) was awful. Still have a bad taste in my mouth though no doubt it's much improved today.

Re: Why I run FreeBSD for my home servers (2024)

#153
post #13

The main complain of the author seems to be that linux use systemd. In my experience, systemd is far better and more reliable than anything else, especially if you need complex logic (ex: when this and that happen, start doing this, except when such and such are present) Most of the problems I've seen come from trying to duplicate systemd functions: in the author example, why bother with rsyslog or network-manager? I…

I went back to Devuan and sysvinit for a peace of mind. Systemd works until it does not. The final straw for me were randomly missing NFS mounts after booting to multiuser. I was not able to find the fix, and the good folks on debian forums, while acknowledging the problem, could not help either.

Re: Why I run FreeBSD for my home servers (2024)

#154
post #128
post #43

Earlier quoted context omitted.

Ubuntu can have zfs with an install of a package. BSD’s inability to utilize docker ecosystem had me decided to stick with Ubuntu for a decade, unless things change and BSD gets clear advantages over Linux.

Ubuntu ships an outdated version that misses a lot of bugfixes. They don't seem to be interested in either backporting fixes or shipping the current stable version. Every other day some Ubuntu user hits the ZFS GitHub issues with a problem that was fixed years ago.

After hitting this in production, I will never choose Ubuntu again.

On top of the things you mentioned, it’s basically impossible to produce a working playbook that switches from Ubuntu’s garbage package to the upstream ones - systemd wedges badly about 25% of the time, and force disables the zfs units. None of the documented systemd overrides worked.

I’m enjoying devuan and openbsd at home.

Re: Why I run FreeBSD for my home servers (2024)

#155
post #115

Earlier quoted context omitted.

To me arch linux is the middle ground between a too-much-complexity "fat" distribution like ubuntu or debian and a-minimal-but-eclectic-freebsd. the arch wiki is VERY comprehensive, linux has a huge community, and arch forced you to understand much just by stepping through the installation process.

arch (or any rolling release) on a home server doesn't sound like a good idea?

Pacman has always been kind to me. Portage, on the other hand, crippled my beloved X60 after a full system upgrade even though I was only a few weeks behind. I don't recall the precise issue but if memory serves it was some sort of circular version dependency that I was unable to resolve. I was a 19-year-old l00nix nublet so I'm sure it was my fault but I've never had so much trouble with a distro package manager as I did with Gentoo's.

Re: Why I run FreeBSD for my home servers (2024)

#156

I use FreeBSD for my home server and I have for years. For me, the biggest reason is just the stability from a user perspective. I don't mean system stability, although it has been rock solid, I mean the stability in terms of administration - the tools don't change frequently. `ifconfig` just works, like it has worked for 20 years. On my linux servers, it's all swallowed into `ip addr` now. I don't mind that, I certa…

> like it has worked for 20 years

.. almost forty years

Re: Why I run FreeBSD for my home servers (2024)

#157

I started reading but stopped as soon as it was a systemd rant. systemd, while not for everyone is a good for most people .

Very well put. I can see how if you learnt Linux before systemd, it may feel like a regression in some ways, but for anyone learning Linux after systemd it's somewhat impenetrable to use anything else. Systemd successfully "productised" and canonicalised what appears to have only really been a bunch of loose conventions beforehand (e.g. sysvinit, not sure I've never seen scripts from different authors work completely the same).

Re: Why I run FreeBSD for my home servers (2024)

#158

I notice FreeBSD admins tend to follow a 'pets not cattle' approach, carefully nurturing individual systems. Linux admins like myself typically prefer the 'cattle not pets' mindset—using infrastructure-as-code where if a server dies, no problem, just spin up another one. Leverage containers. Statelessness. I don't want to spend time meticulously configuring things beyond the core infrastructure my services run on. I…

BSD is for those core infrastructure that you want to meticulously configure. If the system is cattle who cares what OS is underneath

Re: Why I run FreeBSD for my home servers (2024)

#159
post #115

Earlier quoted context omitted.

To me arch linux is the middle ground between a too-much-complexity "fat" distribution like ubuntu or debian and a-minimal-but-eclectic-freebsd. the arch wiki is VERY comprehensive, linux has a huge community, and arch forced you to understand much just by stepping through the installation process.

arch (or any rolling release) on a home server doesn't sound like a good idea?

[deleted]

Re: Why I run FreeBSD for my home servers (2024)

#160
post #86

Earlier quoted context omitted.

I have "reversed engineered" dockerfiles in order to avoid containers. Any software should be installable without docker, it just takes more knowledge and time. Also sometimes it doesn't, there is a binary (like with go and rust and .net) or other times the long route is pip or apt and some conf fiddling. Databases are the worse part maybe but once you get it is more control for you and what you want to do with your…

that is absolutely fascinating. why do you want to avoid containers?

Most straitforward reason is not having multiple database server and reuse one Pgsql or Mariadb for several instances of same app.
Post reply on HN