![Avatar](/_next/image?url=%2Flemmy-icon-96x96.webp&w=3840&q=75)
qjkxbmwvz
Yeah, something this big is absolutely not one engineer’s fault. Even if that engineer maliciously pushed an update, it’s not their fault — it was a complete failure of the organization, and one person having the ability to wreck havoc like this is the failure.
And I actually have some amount of hope that, in this case, it is being recognized as such.
My Debian system was bricked when it “upgraded” to systemd.
Required attaching a monitor to a normally headless server to fix. (Turns out systemd treats fstab differently and can hang booting if USB drive isn’t attached.)
Steam, a 3rd party program, has nuked the home directory of users who didn’t really do anything wrong.
Programs have huge abilities to bork systems, be it Windows or Linux…
Probably coincidence? It sounds (???) like this is a pretty simple fix on Windows.
The number of times I have borked my Linux machines so they wouldn’t boot is, well, greater than zero for sure. Any operating system can be bricked to the point of requiring manual intervention by software with elevated privileges.
Wonder how many shell scripts written on that OS are still in use today…