Calling a kernel mode driver a “simple text file” sure is interesting
Comment on Some bad code just broke a billion Windows machines
werefreeatlast@lemmy.world 1 month agoI don’t hear about billions of Linux or Mac computers going down all at the same time. I’m hearing that windows allows a simple text file change to bring down all of them at the same time.
MetaCubed@lemmy.world 1 month ago
werefreeatlast@lemmy.world 1 month ago
Even if you write assembly code straight out like a total hacker, it’s still a text file. Literally jump 0x12345 is text. And if it’s just a few kilobits long, then it’s a simple text file yes. Got anything else to ad? Specially if the file actually doesn’t work and the system made to run it “windows” is such shit that every copy of it got halted.
MetaCubed@lemmy.world 1 month ago
Yes and at the end of the day it’s all just binary getting dumped into a cache and processed by the CPU. The point is that the intent of the file matters and while they do both hold text, the intent, purpose, and handling of the kernel mode/ring 0 driver is much different than a “simple text file”
So different in fact, that as another user pointed out, it has happened to Linux too
brognak@lemm.ee 1 month ago
Weird, cus it literally happened a few months ago:
neowin.net/…/crowdstrike-broke-debian-and-rocky-l…
This was in no way a Windows problem, this was entirely a CrowdStrike problem. Claiming otherwise makes you look like an uninformed moron.
Entropywins@lemmy.world 1 month ago
They are most likely uninformed with a very strong opinion based on how they feel…while I’d like to call them a moron I’ve done this exact thing and like to think I’m not a moron.