this post was submitted on 03 Aug 2024
65 points (92.2% liked)

Canada

7155 readers
224 users here now

What's going on Canada?



Communities


🍁 Meta


πŸ—ΊοΈ Provinces / Territories


πŸ™οΈ Cities / Regions


πŸ’ SportsHockey

Football (NFL)

  • List of All Teams: unknown

Football (CFL)

  • List of All Teams: unknown

Baseball

Basketball

Soccer


πŸ’» Universities


πŸ’΅ Finance / Shopping


πŸ—£οΈ Politics


🍁 Social & Culture


Rules

Reminder that the rules for lemmy.ca also apply here. See the sidebar on the homepage:

https://lemmy.ca


founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] pathief@lemmy.world 2 points 2 months ago* (last edited 2 months ago) (2 children)

The problem with that logic is that this failure was not caused by Microsoft, it was caused by ClownStrike. Their software works on Windows and Linux (not sure about Mac) and they fucked up the linux software a few weeks before the Microsoft incident.

Even if Linux had more market share in the affected endpoints they would still have been affected, just on different timelines I guess.

[–] cyberpunk007@lemmy.ca 4 points 2 months ago (1 children)

I'm not claiming it was Microsoft's fault. I blame crowd strike. But freebsd is not windows. A bad patch could have had a different result on a different system. They're different.

[–] pathief@lemmy.world 1 points 2 months ago* (last edited 2 months ago)

Yes, they are different but as you can see it wasn't smooth either: https://www.techspot.com/news/103899-crowdstrike-also-broke-debian-rocky-linux-earlier-year.html

I'm not sure how ClownStrike works on BSD, though .

[–] BCsven@lemmy.ca 1 points 2 months ago

The only difference might be some linux distros hold two kernels, so you have a backup boot. And some have immutable system like A/B android so if boot fails it auto rollsback to the old working state