NetBSD seems to be thriving of late: as the Linux world goes pro-AI, some of the AI-averse are turning to this explicitly AI-free project.
The NetBSD project’s Mastodon feed reports that it received a record 120 donations last month, and it has far exceeded its target:
“We received $120,282 USD in total. Naturally, this has completely filled up our donations target bar which was set at $50,000. Time to fund some projects!”
It’s a welcome contrast to the usual stories of under-funded FOSS projects, and it follows a visible uptick in people asking about NetBSD in the FOSS Unix groups we read, ever since Emperor Penguin Torvalds said that Linux was not an anti-AI project back in July, and the following month, the Debian project polled its developers on AI use, and they chose to permit AI-generated contributions.



Has anyone used a *BSD lately? Genuine question. I have tried one of them in the past and it wasn’t really something that you can use as a daily driver. Have they improved? If so, I wouldn’t mind taking another dive.
I was daily-driving NetBSD 11 on my desktop for a month or so. I’ve used it in the past on a laptop for a year or two as well, but that isn’t “lately.” A lot of the other comments do mention it feels like “old Linux,” which I agree with. It has some serious quirks.
I left it behind, though, because of a crash. I had everything set up with XFCE on NetBSD’s X server using the nouveau driver, and it was rather flaky on a pretty old GT 710 card. So X would just crash every now and then. One day though, the system locked up entirely under pretty mild load. That meant it was time to power cycle because everything was unresponsive.
After power-cycling, the filesystem was corrupted. Worse, NetBSD’s utilities said that it was unrecoverable. I have not seen an unrecoverable filesystem in years! Some NetBSD regulars online explained the issue, said I should have turned on journaling (it has it but wasn’t enabled?!?), and told me it was time to restore from backups. My point is that the filesystem is comically old-fashioned and unreliable. I follow a few people online who pointed out that this experience is pretty common.
I switched to gentoo (which also has a strong anti-AI policy, though I don’t know how it will work with AI slop in the kernel) after this experience because I can’t be dealing with corrupted filesystems regularly.
I like NetBSD, I really do. But filesystem corruption seems to be a regular occurrence.
File corruption is a planet-sized no no for me. Lmao.
I use FreeBSD daily and have projects planned for OpenBSD and NetBSD.
For desktop you can do everything Linux can, minus gaming. No proton or equivalent. Some driver gaps occasionally and some things extra steps.
For server, has its own systems and quirks. No docker though. Other ways to do everything else.
NetBSD will get you running a unix system on anything. Im planning to use it on my Dreamcast. Im really hyped to find new uses.
OpenBSD is really secure in architecture, people use it on routers. I like it for older 32 bit support (netbsd works too if you need bluetooth).
FreeBSD for a NAS or server is just chef’s kiss. Solid desktop and improving hypervisor.
Damn, it’s actually missing things that I basically can’t live without. lol. Gaming and docker. I use both a lot
This is my experience over the past 10+ years of dabbling with the BSDs; also see my website for example installations of OpenBSD and FreeBSD (currently working on a NetBSD article).
OpenBSD is the easiest to learn from scratch, and its installer is simple and takes less than 10 minutes even on older hardware. It has by far the best documentation of the three big BSDs. Out of the box it’s extremely barebones (a feature, not a bug, and shared by all three major BSDs). If you select to run X11 during installation you get FVWM2, not the prettiest but functional. You can get to a nice Xfce or even GNOME (if that’s your thing) desktop using packages in the repository. If you have AMD and/or Intel GPUs, you’ll have accelerated video, and compositing if your desktop/wm has that feature. There’s also xcompmgr and picom available. If you have an Nvidia GPU, OpenBSD won’t work with it. Overall, it’s very usable as a modern desktop workstation, with the caveat that it’s slower than the other BSDs in everyday use. This is partly due to security mitigations being turned up to 11 which can be dialed back down, and partly due to the developers prioritizing security and correctness over raw performance. Still, it’s good enough for a daily driver for many folks. Also LibreWolf is now in ports thanks to the much appreciated efforts of Leah Rowe (of LibreBoot fame).
FreeBSD is far more performant than the others, especially on the desktop, and has the largest development community behind it. It also has somewhat broader hardware support than the others, though OpenBSD actually has better Wi-Fi drivers for some cards. FreeBSD isn’t quite as easy to get up to a functioning desktop, but they are working on a “desktop installer” script to make it easier. Still, nothing a seasoned Linux veteran can’t handle with a little help from the docs. It’s blazing fast on the desktop, has good KDE Plasma support now, and has the fastest and most robust file system in ZFS. Still, bear in mind that to this day most FreeBSD devs don’t dogfood the OS (they do their development on macOS or Linux workstations rather than FreeBSD natively).
I’m not as familiar with NetBSD, only having dabbled with it on a Raspberry Pi and a couple of older PCs in the past few years (and my Sega Dreamcast in the early 2000s), but so far it seems to be kind of a middle ground between the other two. Performance is right in the middle, easier to install (with a CTWM desktop by default) than FreeBSD, and hardware support is kind of all over the place. A bonus is the broad spectrum of platform support; you have the usual AMD64/ARM/ARM64 giants, but also tons of smaller, older, and more esoteric platforms. My only real gripe is no LibreWolf; we’re stuck with a rolling release of Firefox that is a bit buggy at times. I believe it has the smallest development team of the three as well as the least amount of funding, but as the article said they have had a boost in interest and funding since coming out as anti-“AI” and I hope that affords them the resources needed to advance the project in all areas.
EDIT: too many thinking bears
I tried FreeBSD couple weeks ago. I was disappointed. Lots of good stuff but coming from Arch the documentation is… ugh. I tried installing it on my old, very common laptop that has run every Linux I’ve ever thrown at it. After a half hour of troubleshooting the WIFI I found a comment at the bottom of an old forum thread stating my wifi chipset which is very common is simply not supported. Then I installed it in a VM. Installing KDE was weird, the packages were simply not in the repos. Then again, at the bottom of a forum thread, I found someone explaining that KDE packages regularly disappear from the repos, that it’s “normal”. And yes, 3 days later, finally the KDE packages reappeared and I could install it.
Edit: just an example. I installed librewolf just now. This is what it says when you install it:
Everything’s always a problem. Death by 1000 paper cuts. It really feels like Linux from 15-20 years ago. I’ve been spoiled by modern Linux for too long. But again, there’s really awesome stuff. Jails, ports and the Linux compatibility layer are pretty awesome. Also there are utilities to make things easier. I installed KDE with desktop-installer for instance to make it easier.
So, my last experiences with FreeBSD were the opposite of this, cleaner than any Linux I’ve tried, and easier than NetBSD and OpenBSD. But! I also simply like the FreeBSD way of solving problems and looking for solutions, it feels much like modding games in my childhood in atmosphere somehow. People sometimes like what seems natural.
FreeBSD ports system and the way to configure sound I also liked very much.
Your screenshot is something I’d use as an illustration of why I like it, just one screen of text with a lot of very terse and useful information. If knowing that something doesn’t work under FreeBSD is its problem in your opinion, then that’s just wrong, that’s not something FreeBSD developers and users can change except with a lot of effort that’s needed in many places at the same time.
I know, I complained about bad documentation and then immediately shared a screenshot of excellent communication… My point was that critical information is found at the bottom of old forum threads, then I got sidetracked and showed a screenshot of complexity, which doesn’t mean bad documentation.
It’s usually found in the FreeBSD handbook. Sorry, but no. With BSDs RTFM is actually the kindest kind of advice. TFM is well-structured, well-written and full.
(If the question is not about rare hardware support or running development snapshots, that kind of thing.)
Oooofff. I’d lose it coming from cachyOS. I’m kind of spoiled.
I do. I have an OpenBSD vps that provides the ingress and proxying for my selfhosted stuff, and vanilla FreeBSD running my NAS and a few self-hosted services. I have an old usff as a desktop for messing around that has bounced around operating systems including the above.
A laptop is the hardest use case for them, but doable if you dont mind it feeling like Linux a decade or more ago. I actually preferred Linux a decade ago, so its fine with me. Ill probably switch my personal thinkpad to one of them again when I have time.
That’s what gets me. I used to like tinkering and fixing things 10 years ago when I first switched to Linux full-time, but not anymore. Now I’m one of those boring dudes who just wants their shit to work so I can get real stuff done. And Linux right now does just that for me. I hardly ever have issues with my Linux run PC. I really want BSD to get better. I like more options.
Where Linux requires solving problems many times, BSDs usually require solving them once or twice, things rarely change where that’s not necessary.
But timely updates are still important, or you’ll have to reinstall everything outside of the base system due to accumulated differences not being resolvable by package managers.
Same problem as with many Linux distributions.
That is my experience as a server or network appliance, but its hard to beat all the work that has gone into linux hardware driver development over the years with operating systems running with a fraction of the userbase. At least with boot environments, its possible to avoid ever breaking things once you get it working.
deleted by creator
I gave it a try in a VM , because I do that kinda thing for fun.
I couldn’t figure out the DE install, but I really didn’t try nor do any research.
Compared to my experience with arch or fedora, it’s not something to half ass on a whim.
FreeBSD is actually quite easy when you know Arch from before the introduction of systemd. It also has a massive documentation.
Well, my experience with arch is sloppin’ it with archinstall :
archinstall is great. it beats any graphical installers.
Well damn then.
It was pretty easy for me to run KDE on freebsd following these steps. I’m running it in a VM, mostly just to become familiar with it, so there’s probably a lot I don’t have to fuss with.
It’s basically just install sddm and KDE then enable them in sysrc.
That really doesn’t look too bad. I might just spin up a VM and fuss with it for a bit
@cenzorrll@piefed.ca is probably right. Again, my expression isn’t “it’s impossible” it’s “you need to pay attention to achieve it”.
I just slop a random distro into a VM once in a while for the lulz. The only thing it indicates is “how idiot proof is installing this OS?”.
The result of the experiment is that FreeBSD is not idiot proof. I got it to install, but I didn’t get to install a DE (LXQT) from the bare bones install. I probably can , I just need to actually pay some attention and read some guides.
The other thing is that I’m installing it into an already weak machine, so putting fancier DEs like GNOME or KDE aren’t going to work out too good.
LXQT is “official” for FreeBSD
https://lxqt-project.org/
https://wiki.freebsd.org/LXQt
Yeah, I daily drive a BSD, it’s definitely not for everyone. Software compatibility and some file system quirks are probably going to be the biggest hurdles. Oh well, maybe someday macOS will be able to compete with Linux.
:/ that’s actually pretty frustrating to hear for me. I really want them to get better so I can use it on a laptop.
Oh sorry, that was just a joke about macOS having BSD heritage. I don’t have experience with modern *BSDs
I actually tried NetBSD recently with everything default, and it was surprisingly usable. Comparing to my current installation of Void, I found it not so daily-driveable though, at least without learning bunch of new stuff.
My router at home is a virtualized OPNsense machine, which is based on FreeBSD
https://en.wikipedia.org/wiki/Comparison_of_BSD_operating_systems
There are dozens of us!
deleted by creator
You must be a genius or just have the patience of a mountain, or I may be too far behind with my knowledge about it. Man, I really don’t have the energy for tinkering, but I might mess with it on my laptop some time in the near future. Which BSD has the best hardware compatibility and is easy to install a desktop on? Because when I tried it back in 1776, it didn’t even recognize my Wi-Fi card.
deleted by creator
I’m no expert but I’m under the impression that WiFi compatibility has been an issue because of a lack of available drivers. For a long time, some common broadcom and realtek chips required that the windows driver be used for Linux via a “wrapper”.
" Didn’t recognize my WiFi card" was a common problem.
Oh yeah, I’m not blaming BSD at all, I think it’s just these manufacturers don’t even think of BSD when they make a device. That same laptop was fine with Linux. So yeah, it’s not a BSD fault. No drivers and we can’t do anything about a manufacturer who refuses to support a certain os
Ah, this is giving me flashbacks to running Linux on a Sony Vaio in 2008
Wasn’t that because the hardware was shit? Making the cpu do most of the work?
https://en.wikipedia.org/wiki/Softmodem