![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/028151d2-3692-416d-a8eb-9d3d4cc18b41.png)
Here’s another one for you, my reading comprehension-challenged Internet friend.
macOS is actually UNIX 03 certified. It doesn’t get any more UNIX than that. 😉
Here’s another one for you, my reading comprehension-challenged Internet friend.
macOS is actually UNIX 03 certified. It doesn’t get any more UNIX than that. 😉
You might be right. In either case, the argument stands but thanks for the correction.
I wouldn’t want your help anyway, considering you think your reading comprehension is better than mine. 😆
You responded to “macOS is UNIX” with “it’s not open source”. I’m just illustrating how these 2 things are not correlated.
In any case, macOS is based on OpenBSD. Even the original BSD, which OpenBSD is based on, was not initially open source.
Everything you said was a straw man.
UNIX != open source.
In fact, most flavours have historically been commercial and proprietary.
The main “instability” I’ve found with testing
or sid
is just that because new packages are added quickly, sometimes you’ll have dependency clashes.
Pretty much every time the package manager will take care of keeping things sane and not upgrading a package that will cause any incompatibility.
The main issue is if at some point you decide to install something that has conflicting dependencies with something you already have installed. Those are usually solvable with a little aptitude
-fu as long as there are versions available to sort things out neatly.
A better first step to newer packages is probably stable
with backports
though.
Debian.
Proxmox (which is heavily Debian) if the use case is to host VMs and/or LXC containers. Debian on those.
Not much use to go Ubuntu or Mint, unless you have specific issues with Debian that don’t happen with those. Even then, it may be one apt install
away from a fix.
If you want to try out BSD, power to you. I wouldn’t experiment on a backup computer though, unless by backup you just mean you want to have the spare hardware and will format it with Debian if you ever need to make it your main computer anyway.
Otherwise, just run Debian!
Up until a few months ago, Vulkan was very unstable on BG3. It’s been fine for a while though. I haven’t made performance or smoothness comparisons though, I just default to Vulkan and it’s been fine.
Well what do you know… this was just released in beta! Haven’t had a chance to try it yet though.
https://store.steampowered.com/app/1021000/iVRy_Driver_for_SteamVR_PSVR2_Premium_Edition/
Doesn’t seem to have been an update in a while…
I don’t mind the order of path, arguments and options, but what the hell is the deal with long arguments with a single dash? i.e. -name
instead of —-name
I fairly constantly need to disable Bluetooth on my iPad so they work on my phone.
If you put the headphones in pairing mode, you can just re-pair with the phone without having to touch the iPad.
deleted by creator
They’re Meross, this one specifically.
https://shop.meross.com/products/meross-matter-plug-with-energy-monitor-mss315-uk
I got a couple of PM plugs with Matter support. I can’t pair them with HomeKit or Home Assistant. I spent about 5h troubleshooting this, inspecting network packets and whatnot and didn’t get any closer to having them working.
I’d rather things just had MQTT support. Happy with Zigbee though, as I can route those to MQTT as well.
Stability is no longer an advantage when you are cherry picking from Sid lol.
This makes no sense. When 95% of the system is based on Debian stable
, you get pretty much full stability of the base OS. All you need to pull in from the other releases is Mesa and related packages.
Perhaps the kernel as well, but I suspect they’re compiling their own with relevant parameters and features for the SD anyway, so not even that.
Why would they manually package them? Just grab the packages you need from testing
or sid
. This way you keep the solid Debian stable
base OS and still bring in the latest and greatest of the things that matter for gaming.
You don’t and likely never will get a fully open stack for those GPUs. Even the latest Radeon cards have a lot of closed-source binary blobs for firmware.
Where the line is drawn between the driver and the firmware blobs makes a massive difference though. Look at the recent case of AMD trying (and failing) to license HDMI 2.1+ for their open source drivers.
Linux is quite an oddball in the UNIX world, tbh. It’s the most popular these days, and the one I’m most familiar with, but most Linux OSs are a lot more GNU than they are UNIX.