There's the Installing Linux on a dead badger HOWTO, but NetBSD actually runs everywhere for realsies. It's also lovely to work with and has the nicest man pages imho.
> Default partitioning: /root goes in the spinal cord and brain stem, /swap and /soul go on the left hemisphere of the brain, and /usr, /var, and /home go on the right. If you're working with a badger with damage to one of those areas, you can repartition one or the other brain hemisphere, but as noted in Step 2, using a brain-damaged badger is not recommended and may interfere with successful installation.
How usable are the BSDs as a GUI daily driver? Like 99% of Linux applications work out of the box or more like 50%?
With new CVEs being discovered in ancient bedrock code on the daily, it seems prudent to switch to a NetBSD/OpenBSD/Qubes system for the next few years until some vulnerabilities might get smoothed over.
NetBSD 11 with Firefox 151 from pkgsrc on a custom CTWM is a usable daily driver for Emacs daemon mode GUI/TUI and console tmux simultaneous use. Remote in from a Windows or macOS desktop.
I use FreeBSD on all my machines for everything sinc about 11 years GUI is I3/X11/AMD-Card everything works, but please test it yourself, it's like with linux, you just know what's not/is working if you use it daily for all your edge-cases (maybe your scanner, maybe your barcode-scanner your Bluetooth-Stuff your wireless etcetc)
Overall i really love FreeBSD for everything computing (Pi/Laptop/Workstation/Servers).
And the community is great...wanna make a port/src-patch?...just send it to the bug-tracker, no rituals needed ;)
they get accepted or rejected, updating ports/packets would be a wonderful AI job, check newest version, update port, poudriere the thing, test it, make patch, send to bugtracker.
Maybe the AI can even check "funny" upstream commits like it happens with npm/crate and block that stuff.
But FreeBSD ports is incredible up to date so there should be no flood of patches anyhow.
Indeed. This might be naive but it would be grand if projects could have their own models and compute with which to perform these and other tasks, each trained as per the project's ethos/needs.-
This is way too expensive. Models are an inherently centralizing technology, and there's no future for niche projects that don't make up a big part of the major providers training sets.
It has a working X11 with DRM from linux as base so everything graphical will work mostly fine. The issue is more around the OS and some subsystems. OpenBSD is still using the Giant Lock model, so SMP can be an issue. Linux has more independent subsystems so heavy processing is unlikely to impact usb audio (which is an issue I have with my oldish laptop). Another issue is the input subsystem (wscons framework) which is not as sophisticated as Linux Input subsystem. In general, linux subsystems are more sophisticated/complex than their OpenBSD counterpart, but the latter work well enough.
There are some linuxisms in some applications (the recent moves to wayland/systemd,...) but they're mostly easy to port.
Depends on what you need. Software compatibility is mostly good, as long as it doesn't have a dependency on systemd or some other Linux-specific feature. Driver support varies, but FreeBSD in particular is pretty decent there.
FreeBSD has a Linux compatibility feature that lets you run native Linux binaries. I've never used it so I can't say how good it is, though - all the stuff I use runs fine natively.
The major BSDs have decent package management and sizeable repositories, with the option to build software (and customize compile-time options) using the ports or pkgsrc systems. You can also rebuild and customize the kernel and base system (aka "make world") but that's strictly optional these days.
I seem to remember there was some GNOME stuff that had a hard systemd dependency and wouldn't run on the BSDs. That was a while back though and I don't run GNOME so I don't know whatever happened there or what the status is.
bch | 15 hours ago
[0] https://www.microsoft.com/en-us/download/details.aspx?id=524...
[1] https://wiki.netbsd.org/ports/emips/
[2] https://www.microsoft.com/en-us/research/publication/an-onli...
tosti | 14 hours ago
andai | 4 hours ago
Installing Linux on a dead badger
https://strangehorizons.com/wordpress/non-fiction/articles/i...
> Default partitioning: /root goes in the spinal cord and brain stem, /swap and /soul go on the left hemisphere of the brain, and /usr, /var, and /home go on the right. If you're working with a badger with damage to one of those areas, you can repartition one or the other brain hemisphere, but as noted in Step 2, using a brain-damaged badger is not recommended and may interfere with successful installation.
bch | 4 hours ago
You're one of today's lucky 10,000! [0]
[0] https://xkcd.com/1053/
3eb7988a1663 | 15 hours ago
With new CVEs being discovered in ancient bedrock code on the daily, it seems prudent to switch to a NetBSD/OpenBSD/Qubes system for the next few years until some vulnerabilities might get smoothed over.
__patchbit__ | 14 hours ago
[OP] Bluestein | 14 hours ago
- https://www.ctwm.org/index.html
izabera | 14 hours ago
[OP] Bluestein | 14 hours ago
BSDobelix | 13 hours ago
Overall i really love FreeBSD for everything computing (Pi/Laptop/Workstation/Servers).
And the community is great...wanna make a port/src-patch?...just send it to the bug-tracker, no rituals needed ;)
[OP] Bluestein | 13 hours ago
BSDobelix | 13 hours ago
Maybe the AI can even check "funny" upstream commits like it happens with npm/crate and block that stuff.
But FreeBSD ports is incredible up to date so there should be no flood of patches anyhow.
[OP] Bluestein | 12 hours ago
a2ff6eeb0 | 12 hours ago
skydhash | 13 hours ago
It has a working X11 with DRM from linux as base so everything graphical will work mostly fine. The issue is more around the OS and some subsystems. OpenBSD is still using the Giant Lock model, so SMP can be an issue. Linux has more independent subsystems so heavy processing is unlikely to impact usb audio (which is an issue I have with my oldish laptop). Another issue is the input subsystem (wscons framework) which is not as sophisticated as Linux Input subsystem. In general, linux subsystems are more sophisticated/complex than their OpenBSD counterpart, but the latter work well enough.
There are some linuxisms in some applications (the recent moves to wayland/systemd,...) but they're mostly easy to port.
idatum | 10 hours ago
Use your best build hardware to build for your test hardware.
prmoustache | 6 hours ago
spauldo | 5 hours ago
FreeBSD has a Linux compatibility feature that lets you run native Linux binaries. I've never used it so I can't say how good it is, though - all the stuff I use runs fine natively.
The major BSDs have decent package management and sizeable repositories, with the option to build software (and customize compile-time options) using the ports or pkgsrc systems. You can also rebuild and customize the kernel and base system (aka "make world") but that's strictly optional these days.
I seem to remember there was some GNOME stuff that had a hard systemd dependency and wouldn't run on the BSDs. That was a while back though and I don't run GNOME so I don't know whatever happened there or what the status is.
andai | 4 hours ago
galleywest200 | 12 hours ago
You can opt to build it yourself and exclude anything that is not 2-clause BSD licensed, as some drivers and such are if I recall correctly.
laidoffamazon | 10 hours ago
yjftsjthsd-h | 9 hours ago
laidoffamazon | 5 hours ago
sbseitz | 8 hours ago