• 4 Posts
  • 168 Comments
Joined 1 year ago
cake
Cake day: June 1st, 2023

help-circle


















  • While you’re not wrong there are still FreeBSD pain points particularly around wifi that remind me of 2007 when I first moved to Linux (and then FreeBSD). They’re working on it and have some funding put aside to pay developers to help remedy this. Laptops also are very likely to have odd and end edge cases, for instance my chromebook needs to pass audio over i2c which FreeBSD doesn’t support and even linux needs some hacky scripts to run through the commands to enable this (and the script needed an update because THIS particular model was slightly different from others by the same brand…). Linux in this regard moves much faster in getting support going and requires little to no pain especially in comparison. I love FreeBSD and use it everywhere I possilby can but there’s certainly things it’s just not easy/practical to use it for right now.


  • I use FreeBSD on a desktop as a server and for desktop usage with a touchscreen to run a virtual pipe organ that needs an obscene amount of resources to run. There’s a few things that I see as pros:

    1. Zfs on root/by default. Absolutely love zfs and not having to screw around with dkms/kernel issues etc to get it running is a huge plus imo

    2. Jails - I cannot stand docker. It’s opaque and I’m stuck trusting that whatever image I’m downloading is updated/secured and or running multiple extra containers to stack together. With jails I spent my time setting up the jail once (installing services etc), and using a jail manager (bastille) I can maintain what I think is better control of the internals and updates etc. the commands mirror the os as well which is nice

    3. Integrated world - the way bsd integrates the core system and separates out the packages means most security updates just need a service restart not a full reboot so uptime between OS patches can be months at a time. They’re also very conservative about changing how the core system functions so how I install/set up/maintain the system in 2007 is the same as today.

    4. The manual. Anything I need to know when adding services including edge use cases is in the manual on their website. Much cleaner written than the arch manual, and has a pdf download available if you aren’t going to always have the internet (and a terminal interfaced manual option to download).

    For my usage there’s not much I can think of for cons, but I will say laptops and particularly WiFi suffer currently. There’s funding and works in progress to fix this but still idk I’d use it on a laptop today without carefully checking support for the hardware like I would’ve with old school Linux. They’ve come a long way recently with edge cases for instance I’m currently running a windows vm with gpu pass thru using their bhyve vm manager, something that wasn’t supported a year ago, so I am optimistic the funding will help in the next few years on some of the laptop issues.