2907
Some trouble
(lemmy.world)
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 05 Jul 2023
2907 points (97.2% liked)
linuxmemes
21222 readers
98 users here now
Hint: :q!
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
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
sudoin 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
The ones that make me laugh uncontrollably are those Windows disk encryption issues for which the solution is…wait for it… run Linux from a LiveISO, fix the disk with Linux, then reinstall Windows. Because Windows is incapable of fixing its own issues that it itself caused.
As a former computer service technician, we used Ubuntu Live USB and DVDs (yes it was a long ago) a lot.
I remember something happened to my family's Windows computer once. A system file had gotten corrupted somehow so it could only boot into the repair utility, which, naturally, couldn't repair the file.
The solution I found on Google was to put in the installation disc (I think it was Windows 7?), run the disc at startup (by switching the boot order in the BIOS), and fix it using Command Prompt on the disc.
Windows' own diagnostic tool included with the OS couldn't fix the problem. Only the disc could. It was pretty fortunate we still had that thing. Until then, it had just been sitting there collecting dust.
Windows lacking tooling to fix issues caused by its own malfeasance was what made my switch to Linux permanent. I used a LiveCD to fix file system issues that Windows had no tools for unless I wanted to pay thousands for janky third-party tools. Once I did that and recovered most of my lost data, I thought long and hard and just said "fuck it, I'll use Linux".
None of my family will run Linux, however, on my recommendation. I can cope with Linux's ... selective set of user friends. They can't, and I'll be damned if I turn into free tech support.