I’ve done workstation maintenance in a previous job. Every part of the Linux centralized management was worse than Windows. We did it to support our coworker’s wishes, but SSSD constantly shits the bed, and having to code (config management) to write some pretty simple rules like default printers is super annoying compared to the Active Directory built ins.

Microsoft’s biggest strength is the Active Directory. Linux user and computer management is a huge PITA.

Yea. They were basically burning the tar like leftovers from fuel distillation and there was a lot of heavy tankers moving from East Asia to the US.

https://en.m.wikipedia.org/wiki/Heavy_fuel_oil

Nah, Sulfur compounds can lower albedo. That’s actually quite possibly what happened here and why we have sudden outlier acceleration.

https://www.livescience.com/planet-earth/climate-change/cutting-pollution-from-the-shipping-industry-accidentally-increased-global-warming-study-suggests

Yea, and the smothered burrito was California in the 1970s as well?

Not even close. Grand Rapids, Michigan in the 1960s wins out. https://www.foodrepublic.com/1433416/what-are-wet-burritos-difference/

While it may be true that getting rid of SUID binary is ideal, widening systemd’s security surface area is much more concerning to me than the sudo binary.

How would you deal with iowaits in a system like that? I can perfectly burn 100% of CPU time running a poll(), but that’s not useful work…

Tickless means it’s not based on the computer frequency and idle CPUs can stay idle rather than being annoyingly brought into high power mode ever 100 Hz, but it’s still firing interrupts based on scaling timed variables.

They’re now called “Dynticks”

SUSE wrote the vaguely more understandable write up that Linux foundation links to: https://www.suse.com/c/cpu-isolation-full-dynticks-part2/

BTW, the Linux RCU code is evil but interesting: https://www.p99conf.io/session/how-to-avoid-learning-the-linux-kernel-memory-model/

Disk Duplicator is a destroyer? Man, I used to image so many drives with DD back in my helpdesk days…

Hash the image, then assign hash ranges to servers that are part of the ring. You’d use RAFT to get consensus about who is responsible for which ranges. I’m largely just envisioning the Scylla gossip replacement as the underlying communications protocol.

Why? Use something like RAFT, elect the leader, have the leader run the AI tool, then exchange results, with each node running it’s own subset of image hashes.

That does mean you need a trust system, though.