- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
You must log in or # to comment.
The mistake was pushing it on Friday morning like a bunch of amateurs, they’re supposed to push it out scheduled on Friday at 5:03PM so you have enough time to get to your car and off the parking lot
Exactly hahaaha!!
Was about 3pm here /cries in Australian
We regularly get screwed over during business hours by things being pushed out overnight in the US/UK
AFAIK it was a Thursday night push for people in US mountain time / pacific time. But, that ends up being Friday early morning in Europe and Friday mid-day in Asia.
Y2K would have been CRTs. But it’s not like kids will know that.
Hey we had flat screens back then, they just took up the whole floor space and it took 2 people to move those projection TVs
Laptops also had LCDs. Just don’t move your mouse too fast or the screen can’t keep up and it’ll disappear
You’re thinking of passive matrix displays. Those were the cheaper option but active matrix screens did exist.
They did, but you had to pay a pretty penny to have one of those
Maybe even split-flap displays, or printed advertisements
As someone stuck in DTW, I feel the pain.
Down to win?
Bro do you even lingo? It’s obviously Down To Wedgie, that’s why he’s in pain
No, no, no. It’s clearly a city since the photo is flight info boards. Clearly he means Dallas Tort Worth, it’s a little tiny place unlike its bigger brother DFW.
Surprised to hear someone mention Dallas Tort Worth ever since The Incident.
Of course mate, and unlike its sibling, it Doesn’t Fuck Walruses
You sure it’s not DownTon Wrappy?
Is this the Denver airport?
Yeah
Ironically it was more of a hassle than y2k ended up being lol
Y2K24
Also, half the team must be on summer vacation
What happened?
An update to a cybersecurity software suite called CrowdStrike caused Windows machines to BSOD. CrowdStrike was big and monopolistic enough that it took out servees at large organizations worldwide.
How was this not tested by Microsoft in a virtual environment with a large set of test conditions before it was released? Does this not happen?
I don’t expect that Microsoft checks CrowdStrike’s software before CrowdStrike pushes their updates.
So this wasn’t a windows update? Got it
Real men test in prod
Everyone has a test environment but only a few separate prod
And here I am having to deal with 4 environments.
Should have used Linux!
Should have not trusted a third party to install proprietary code into the kernel. It’s not a Windows issue directly, they have a Linux version too, but anything that allows third parties to put proprietary code into your kernel and automatically update it without your approval is untrustworthy.
Counterpoint: Windows bad.
I can’t disagree with you there.
They have a Linux version, but this happened only to the Windows one… Coincidence?!
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.
The simple fix: turn it off and on up to 15 times
The simple fix 2: delete system32
It’s not like they haven’t caused Linux outages in the past.
Yes, coincidence.
The cause is a malfunction of the Crowdstrike monitoring solution, which employees use to spy at anything ever done on company hardware. They do have a Linux version and it has been reported to cause kernel panics (not
sure ifduring this incident).But yes, Windows on public information displays is dumb.
it was because crowdstrike themselves notified that this specific instance did not affect their linux nor osx distributions of security, and was windows specific.
This in particular is a Crowdstrike issue. They suck as much as windows. Crowdstrike has had issues on Linux before:
Crowdstrike - freezing RockyLinux After 9.4 upgrade:: https://forums.rockylinux.org/t/crowdstrike-freezing-rockylinux-after-9-4-upgrade/14041
Kernel panic observed after booting 5.14.0-427.13.1.el9_4.x86_64 by falcon-sensor process:
https://access.redhat.com/solutions/7068083Debian user experience: https://news.ycombinator.com/item?id=41005936
Another windows story: https://www.thestack.technology/crowdstrike-bug-maxes-out-100-of-cpu-requires-windows-reboots/
