this post was submitted on 07 Mar 2024
1416 points (93.0% liked)
linuxmemes
21280 readers
1116 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 2 years ago
MODERATORS
That's the thing right? I'm very much a non-tech person. But Linux error messages are nice and informative to the point that, even if I don't personally know what the fuck they are saying --
-- I can just copy them to my browser search bar. Oh look, someone else had the same issue. And someone who knew what they were talking about presented a solution. Nice, now I can get back to work!
And even when I am forced to troubleshoot on my own, the error messages and terminal logs often give enough of a clue that I can trial-and-error my way into making shit work.
What... you don't like the smiley face and QR code that leads you to a dead link on a rando microsoft website? You sure you need more information other than "Critical Process Died"?
The memory dump it does is useless... like anyone is ever gonna take a look at that memory dump. Disable it, it just wastes disk space.
The first time I saw a sadface bsod I legitimately said out-loud "Are you JOKING?"