Victor

Definitely not, but we still have much more favorable worker laws.

🖕 AI

lol yeah, now that you mentioned it, the order seems to be random or some totally unrelated metric to the charts. 🥴

Going back a little bit, you mentioned advantages to “segregating into vlans”?

Would you like to elaborate on some of those advantages?

😁 “Maaaybe”

TIL Arch is a footgun. 🤡 cope. 😉

But yeah, I agree, if package maintainers were astute there, a warning would’ve probably been good somehow. Not sure pacman supports pre-install warnings. Maybe? It does support warning about installing a renamed/moved package. But the naming would’ve had to be really weird for everyone involved if the warning would be clear in that case.

It would be a very out-of-scope feature for a Linux package manager to do a GPU hardware check and kernel module use check to compare whether you’re using the installed driver, and then somehow detect in the downloaded, about-to-be-installed binary that this will indeed remove support for your hardware.

It just seems very difficult to begin with, but especially not the responsibility of a general package manager as found on Linux.

On Windows, surely the Nvidia software should perform this detection and prevent the upgrade. That would be its responsibility. But it’s just not how it is done on Linux.

It’s not the package itself that “auto updates”. The package manager just updates all the packages that have updates available, that’s it.

But still, the system doesn’t really “break”, all you have to do is downgrade the package, then add a rule preventing it from being updated until Nvidia/Arch package maintainers add a new package that has only that legacy driver’# latest version, which won’t be upgraded again.

Windows doesnt drop to CLI and break if the graphics driver is missing.

Okay. Kind of a matter of definition of “breaking” but sure.

But also GPU driver updates are not forced on you just by updating the system.

Right. But on Linux they happen automatically when upgrading the rest of your system, is what I was saying.

Not worse than America yet though.

Actually we’re managing that on our own soon, I think. 🫣

This is why everyone needs protection from a work culture that burns through people.

You are all welcome to Europe for that. Come on over.

Ah okay, so it’s kinda just for aesthetic reasons mostly? I’ll take that explanation home any day 😄

You don’t have to updare your drivers though.

Not sure if you’re on Windows or Linux but, on Linux, we have to actively take explicit actions not to upgrade something when we are upgrading the rest of our system. It takes more or less significant effort to prevent upgrading a specific package, especially when it comes in a sneaky way like this that is hard to judge by the version number alone.

On Windows you’d be in a situation like “oh, I forgot to update the drivers for three years, well that was lucky.”

Not really a problem of Arch, but of the driver release model, then, IMO. You’d have this issue on Windows too if you just upgraded blindly, right? It’s Nvidia’s fault for not naming their drivers, or versioning/naming them in a way that indicates support for a set of architectures. Not just an incrementing number willy nilly.

Apparently? Title only mentions dropping the support on Linux. 🤷‍♂️

Is there a technical advantage to using a 192 network vs a 10 network like you described? I would’ve thought they’re just addresses, still IPv4 as well.

I tend to use hostnames where possible. Maybe that’s not viable for your situation?

At least you admit to being a troll.

Go back to Reddit. You don’t belong here.

So as to stop being a troll. Nobody thinks it’s funny. Most of us are older than 12 here.

Just stop the charade.

• moving task bar to the center

• control panel vs Settings app

I didn’t mind these. But it’s not important what I think as I don’t use Windows anymore.