Not sure what you're on about, most package managers have a literal database of most package manager installed files. Debian and derivatives have dpkg --verify or debsums to verify the files, arch has paccheck, I'm sure other distros have something similar. And fixing them is just a matter of reinstalling the package, which you can do from a chroot if the system won't boot.
Or you can just run your system on a checksumming FS like btrfs which will instantly tell you when a file goes bad.
You'd figure that would take about 5 seconds for the world to win, but weirdly, it was kinda close.
I was just introducing someone to Rodney last night because some actor in a show we saw looked a bit like him. Then I wake up and see this here. Life sure has funny coincidences sometimes.
Shame he didn't have a scandal on that stage. They would have stopped taking about it within the day.
Someone found a way to weaponise bikeshedding.
it's a mechanism / not a computer,
It's an analog clockwork computer.
there is no mystery, just clickbait as usual.
There's plenty of mysteries about it, hence why it's still a topic of study despite being discovered 120 years ago.
Surprisingly, the inspiration for the paper came from a YouTuber who has been attempting to physically recreate the ancient mechanism.
I was just re-watching clickspring's videos about this yesterday.
You can catch a glimpse of what the websites were like using the web archive. A good starting point would be a popular web directory, like for example the Google directory from 2004.
Everyone just confirming aliteral's point.
I've been in love with the concept of ansible since I discovered it almost a decade ago, but I still hate how verbose it is, and how cumbersome the yaml based DSL is. You can have a role that basically does the job of 3 lines of bash and it'll need 3 yaml files in 4 directories.
About 3 years ago I wrote a big ansible playbook that would fully configure my home server, desktop and laptop from a minimal arch install. Then I used said playbook for my laptop and server.
I just got a new laptop and went to look at the playbook but realised it probably needs to be updated in a few places. I got feelings of dread thinking about reading all that yaml and updating it.
So instead I'm just gonna rewrite everything in simple python with a few helper functions. The few roles I rewrote are already so much cleaner and shorter. Should be way faster and more user friendly and maintainable.
I'll keep ansible for actual deployments.