this post was submitted on 11 Aug 2024
211 points (83.7% liked)
linuxmemes
21263 readers
656 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!
founded 1 year ago
MODERATORS
Upvoted because your experience is valid, but I will say that mercifully so far, I haven't had this issue personally. Instead, rather, my Windows 10 installation is basically broken because MS pushed an update that requires it to enlarge the recovery partition, but because there's another OS past the recovery partition, it can't. So whenever I use it now, I need to wait for it to try updating itself, recognize that it failed, and then undo the updates and boot again (the entire process takes 10+ minutes). I only use this partition for emergencies where something critical absolutely won't work on Linux, but it's still hilarious to me that this happened shortly after I abandoned ship.