Technology

59534 readers

3195 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

389

Some bad code just broke a billion Windows machines (www.youtube.com)

submitted 4 months ago by TimeSquirrel@kbin.melroy.org to c/technology@lemmy.world

120 comments fedilink hide all child comments

Cybersecurity firm Crowdstrike pushed an update that caused millions of Windows computers to enter recovery mode, triggering the blue screen of death. Learn ...

you are viewing a single comment's thread
view the rest of the comments

[–] MetaCubed@lemmy.world 0 points 4 months ago (1 children)

Calling a kernel mode driver a "simple text file" sure is interesting

[–] werefreeatlast@lemmy.world 0 points 4 months ago (1 children)

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 points 4 months 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