389
Some bad code just broke a billion Windows machines
(www.youtube.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 20 Jul 2024
389 points (94.7% liked)
Technology
59374 readers
3249 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
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.
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