CrowdStrike incident happened too soon. Could have made serious money...
qjkxbmwvz
joined 2 years ago
"...today is opposite day."
This was my biggest complaint about an abroad stint in the Netherlands
all the peanut butter* was JIF style/huge ingredient list. Agree completely
only acceptable ingredients are peanuts and salt.
The beer wasn't all my style, but I could certainly appreciate it.
*"pindakaas" literally "peanut cheese," I think because "butter" is reserved for dairy products.
Neat read!
Colloquially, I'd use it to mean "requires physical access to fix."
protected
Um, about that...
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.
Can you program some keyboard-presenting device to automate this? Still requires plugging in something of course...what a mess.
As much as it pains me to say it, it's not really Microsoft at fault here, it's CrowdStrike.
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...
Wonder how many shell scripts written on that OS are still in use today...
Oh for their cloud services absolutely, you're right.