This is one of those comments that causes Arch to get the reputation that it does. You aren’t wrong and you probably don’t intend to be off-putting but here we are.
This is one of those comments that causes Arch to get the reputation that it does. You aren’t wrong and you probably don’t intend to be off-putting but here we are.
Red Hat and Debian both backport security fixes but don’t backport things like laptop device support. It can take a year or more for versions of those distros to gain the kind of functionality that is looking for.
This is an excellent answer. My eli5 addition is this:
It depends on your distro. Distros that do more hand holding and more compatibility without additional operator involvement will be more likely to backport or use a stable kernel with backports like these. Examples: Ubuntu/Fedora/Mint. Distros that focus on system stability will take much longer to integrate backports like these, ex: Debian. And masochists will tell you to do it yourself, ex: lfs, arch.
You couldn’t pay me to use this…
Here is the rest of the story: the people who chose the subdomain chose .ml because they want it to mean marx-lenin… that’s why it means that for them.
Generally you are right. In this specific instance it was chosen for the fascism.
This took a major hit just a few years ago when the UK officially backed out.
You are making just such a weird argument and it sounds like you are retroactively trying to salvage a bad position because you made a mistake.
If you care strongly about audio quality. A built-in doesn’t have any quality guarantees… why then does usb vs hat matter?
If quality is your concern why bring up price in the first part? It is blatantly obvious that cheap parts *might" equate to cheap quality. This is blatantly obvious.
Obviously there will be USB solutions that are equal or better solutions than prebuilt rpi dac hats since the primary dac hats are exceptionally niche.
This response just sounds like you got caught out in your mistake/bad argument. Why be a dick about it?
Unfortunately your is a known bug. If the delete doesn’t get federated properly there isn’t a way to redo it.
Have LTS kernels started backporting non security fixes like this? To be fair I haven’t looked at this in over a decade but this kind of patch wouldn’t have been backported then.