notalaser

After seeing the astroturfing in this thread, I'm switching to Vivaldi or Chromium, not Tor Browser.

So put a big red scary "PRESS THIS BUTTON AND YOU'LL GET HACKED IN TEN MINUTES UNLESS YOUR COMPUTER DOES NOT CRASH BEFORE THAT" that turns telemetry off and let me press it.

What later days? Software mixing worked fine in ALSA in 2004-2005, and OSS emulation had been working reliably way before that. The first PulseAudio release was in 2004, and it wasn't adopted by Fedora until way, way later.

This has worked reliably in ALSA before it has worked reliably in PulseAudio (and, in fact, way before PulseAudio received any meaningful adoption, when Fedora enrolled everyone in PA's beta testing).

No, but they will affect most of the equipment connected to those generators.

That's the thing -- it's (no longer) easy at all. When accessing every other function requires guessing which hamburger menu it's hidden behind, it looks clean and easy to use, but it's not.

In the meantime, a bunch of us developers are desperately trying to figure out what the fsck broke this time, drinking our sorrows about this new life where we can't debug anything that happens at boot, and frantically setting up BSDs on our laptops at home, so that we can at least get a break from this mess when we're at home.

I (thankfully only) used to do Linux BSPs in a former life. In the last year or so of doing that, I think we spent about 15-20% of a project's time debugging systemd problems and working around it being too smart for its own good. 20% for the bloody init system sounds fine until you realize the rest of the time included stuff like writing or expanding device drivers.

Of course you are free to do whatever you want, it's the entitlement that pisses me off. Somehow, employees charging "too much" is not ok and totally not the companies' fault, whereas offering too little is great management. Then they wonder why there are six million jobs that they can't fill.

So... the business doesn't even generate enough revenue to afford hiring the kind of people who can keep it running well, or at least not as well as its owners would want it to be running?

Should workers be doing charity work now?

> But maybe the job isn't economically worth it at the higher salary?

As in, their business doesn't even generate enough revenue to afford hiring the kind of people who can keep it running?

> But, I'm kinda baffled why anyone would volunteer to provide free labor to one of the largest and most profitable companies in the world.

YES! MacOS users don't need to document macOS as a volunteer project, they need to demand Apple to give them their money's worth.

Honestly -- I have no idea, I only had to do it a few times, on Yocto and buildroot images, and in pretty restricted cases. It was pretty easy (basically udev has this file which matches a set of device selection rules with a set of actions, effectively saying "if I encounter a device of this type, I'm going to do these particular things"), but I googled my way through it.

I expect there are some distro-specific hoops to jump through, but I have no idea which ones -- I really don't like automounting, I keep it disabled even on KDE.

(Why? Old habits die hard, I guess?)

I don't know what they use, but there's always eudev, Gentoo's fork which works just fine, and offers pretty much everything that udev offers (except for the systemd dependency).

Yes. This is all handled via udev, udisks & co., XFCE, Gnome and KDE have nothing to do with it (other than having it work more or less out of the box).