this post was submitted on 19 Jul 2024
742 points (98.1% liked)

linuxmemes

20707 readers
416 users here now

I use Arch btw

Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
poopsmith@lemmy.world
zephyr@lemmy.world
742
Congratulations all. (lemmy.world)
submitted 2 months ago by BonesOfTheMoon@lemmy.world to c/linuxmemes@lemmy.world
30 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] turbowafflz@lemmy.world 10 points 2 months ago (1 children)

Does windows not have any reliable filesystem snapshot capabilities? Because as soon as I learned about this whole thing my first thought was just that it would be easy to fix just rollback to the snapshot before the update

[–] scholar@lemmy.world 3 points 2 months ago (2 children)

Hard to roll back when you're stuck in a boot loop

[–] Routhinator@startrek.website 1 points 2 months ago (1 children)

Not to mention the patch being applied was being applied at boot, so rollback > patch > crash; repeat

[–] turbowafflz@lemmy.world 1 points 2 months ago (1 children)

Wait did they not stop serving the broken release to clients even after they realized the problem? I guess I wouldn't be surprised but wow that's worse than I expected

[–] scholar@lemmy.world 1 points 1 month ago

The fault was a driver, so if the faulty driver loaded at boot the machine would bsod again. If the machine got network before the driver loaded there was a chance that it could download and install the fixed driver

[–] turbowafflz@lemmy.world 1 points 2 months ago

Not if you can boot from an old snapshot like BTRFS and ZFS can