Imagine not running Pi-Hole with unbound on your homelab SFF PC for an independent DNS server with domain filtering. Shit's documented so plainly even a chimp could set it up. However, if running the NTP server requires a hardware atomic clock expansion card then yeah no fucking wonder most people don't self-host that shit. Setting it up to rely on something like DCF-77 would be even more complicated.
I also suspect the long game. as mentioned redhat makes more money if shit doesn't work, but if they're the ones in charge of what gets implemented and can push it, it becomes the de facto standard. it's basically how microsoft has been operating for decades and became the company it is today.
Theory-first analysis: Bespoke package manager, NIH symptoms. Might work great. IDK. Another interesting data point to watch, given how Xorg features in its Technologies list ( https://getsol.us/solus/technologies/ ). Interesting dependency-focused build system. Solbuild seems neat. They write a lot of code in Go. Budgie is written in Vala, the weird GTKObject-based language.
FreeBSD has the linuxulator which is cool. Also has Nvidia drivers. If those aren't your main concerns, OpenBSD is probably better.
European typing detected.
Playing around with it in a VM it does let me run the apps I use regularly and generally looks slick, I think I'll try installing it and see how it goes.
Theo De Raat is also Canadian, so you're only part of five eyes instead of getting assraped by the NSA directly if that matters.
>implying he didn't knew already
>starts to list an entire electronic project just to get local NTP running
OpenBSD is more focused on security, so you're gonna have to do things like enable simultaneous multi-threading (off by default) to get a reasonable desktop experience. All BSDs have good documentation though so it'll probably just be a matter of Reading The Friendly Manual.
I can't see why you'd need your own atomic clock for it, though. Why not just use WWVB as the source for the NTP server? (It also has its own NTP server but if you're doing it locally presumably you have some specific reason for not wanting to use that.)
Wrong again, child. Enjoy GNOME prison.
It's our superpower, normie.
I wouldn't say that would be one of my criticisms of wayland. You can do as much customization as you could on x11. My criticism would be it doesn't have the ecosystem x11 does still. Not really too surprising since its only now that people are actually starting to move over. And because it doesn't have the ecosystem still, you end up running into things you can't do with it people were able to with x11.
If your hardware works with openbsd. Probably pick openbsd.
If Wayland weren't run by the same FDE retards it'd have more support.
This is potentially a big footgun depending on whether your packages can handle back-and-forward compatibility of config data. Watch the versions closely.
Most reasonable post-systemd inits do this. S6 and runit do, at least. The problem is the entrenchment of systemd, that it's designed by idiots who are hostile to multiple use cases. It's better to dogfood the alternatives. I love systemd-nspawn though. It could be an isolated program, no need for pid 1 stuff.
