[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...
bch 3 days 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 3 days ago
andai 2 days 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 2 days ago
You're one of today's lucky 10,000! [0]
3eb7988a1663 3 days 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__ 3 days ago
Bluestein 3 days ago
izabera 3 days ago
Bluestein 3 days ago
BSDobelix 3 days 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 ;)
Bluestein 3 days ago
BSDobelix 3 days 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.
Bluestein 3 days ago
a2ff6eeb0 3 days ago
skydhash 3 days 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 2 days ago
Use your best build hardware to build for your test hardware.
prmoustache 2 days ago
spauldo 2 days 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 2 days ago
spauldo 2 days ago
vermaden 2 days ago
Details:
- https://vermaden.wordpress.com/2020/10/14/oldschool-gaming-o...
galleywest200 3 days 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 2 days ago
yjftsjthsd-h 2 days ago
laidoffamazon 2 days ago
IcePic 2 days ago
So even if you can divine that a binary windows driver sometimes writes a 5 into that register at certain times, you will have a far harder time figuring out how and when it is needed to actually do that, and the source you get will be super hard for anyone else to understand if its all magic numbers getting written into "random" locations, compared to say, "wificard.driver.radio_enable = ACTIVATE_RADIO;" even if it compiles into writing 5 to offset $0562. Such reverse-engineered sources are super hard to keep working in the long run, when someone rewrites how and when IRQs are delivered to devices or whatever major is happening in the kernels so this leads to drivers no longer working even if they did have a short period of use.
snvzz 2 days ago
- A standard driver API with some traction.
- Drivers running in userspace.
It would not be the problem it is.
fithisux 6 hours ago
sbseitz 2 days ago