this post was submitted on 19 Jul 2024
742 points (98.1% liked)
linuxmemes
21378 readers
1361 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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
Hard to roll back when you're stuck in a boot loop
Not to mention the patch being applied was being applied at boot, so rollback > patch > crash; repeat
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
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
Not if you can boot from an old snapshot like BTRFS and ZFS can