4 ms·
I would still have built rsync.net on FreeBSD because of how familiar I was with it and how much I had personally (and institutionally) invested in it from John
by rsync 5y ago
I would still have built rsync.net on FreeBSD because of how familiar I was with it and how much I had personally (and institutionally) invested in it from JohnCompanies.
Since ZFS is now so core to what we do, it was a very natural evolution.
I have zero experience with Dragonfly BSD.
I love that FreeBSD is still a very simple UNIX without complications like systemd. I was recently tinkering with a raspberry pi and had to work out wifi connectivity and had to interface with ... what is that weird wifi subsystem that linux uses ? Supplicant ? Wow.
I just want to pipeline commands and edit config files. I don't care that it's inefficient or doesn't scale. It has scaled just fine for me.
- dijit 5y agoI believe wpa_supplicant is still needed for wifi access on freebsd (or, it was in 2017 when I was last using freebsd on my laptop). OpenBSD has better integrations with ifconfig and wpa though, it’s possible they are ported over now, but wifi config is the same as in Linux (or had been for quite a significant amount of time) on freebsd. Completely agree about the opaque and incidental complexity of the systemd ecosystem though, I’m glad people love it but it’s not for me.