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.

Ink also runs when wet, so caveat emptor if you plan on your paper existing anywhere with water.

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…

Most of the bolted on services are rather shitty. ResolveD in particular is straight up hot garbage unless the only thing you are comparing it to is nscd. I like shipping all my logs to a centralized service and journald just gets in the way. It feels like they took upstart, bolted on some really crappy daemons,

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.