

Some countries have pretty strict laws about not promoting Nazi ideology - by pushing that notifications it would probably be breaking that law.
Some countries have pretty strict laws about not promoting Nazi ideology - by pushing that notifications it would probably be breaking that law.
Stolen? It was forked as is allowed by the MIT license. With GPL as well there is no „you cannot fork” rule, you can do exactly the same thing. The author misunderstood that „you have to push the changes to upstream”, which is not in any of those licenses.
Open the disks, take the platters out, you can smash them. Or, if you’ve been naughty, you can borrow a belt sander and sand them down to naught.
Counter-counter point: people don’t get a Mac or windows laptop to learn about osx or windows. They generally want to run software or at least browser to do what they need to do.
Uh, memory metrics in Linux are a pain. The only tool that reports most cached as available is htop. free, top and a lot of other software (like node_exporter) will report that a lot of cached memory is not available.
To OP: don’t worry, a lot of Linux tools are smart enough to give back memory if memory pressure rises.
Microsoft is big tech, and GitHub is owned by y Microsoft.
…and then you learn that packageX v1 is not maintained anymore and relies through a deep set of dependencies on a seriously vulnerable package (in a version which is also not maintained anymore).
Sorry, I had a pretty eventful December :)
My take is that it’s already your systems feature, rather than admins responsibility. If you treat departments like customers, you’d find a good way to spread the costs. If something is just a „common infrastructure”, you will always find something that makes costs that doesn’t have an easy way to track who triggered that - because you don’t pass enough information with it.
Not sure what is hard in it - you need consistent tagging, and that by itself gives you a lot of mileage in cost explorer.
This is not an unusual comment section on Phoronix, to put it mildly.
No, it has not „always been fine” - I’ve worked with people who disabled auto updates on their dev machines just to keep a specific kernel & driver version working together. Circa 2016 :)