this post was submitted on 20 Sep 2023
1175 points (98.7% liked)

Linux

48329 readers
639 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] duncesplayed@lemmy.one 6 points 1 year ago (2 children)

One smart thing I think Microsoft did was try to give every error message a code. Googling for "gpoopapp E0013" is often easier and gets more precise results than having to type in "gpoopapp The file /home/bitchslayer69420/.config/share/whatever.yaml could not be opened: File not found"

[–] DrQuint@lemm.ee 31 points 1 year ago* (last edited 1 year ago)

Unfortunately, the SEO hellscape means every single windows error just yield a "Try to install our patcher tool" article.

How about both?

[–] Strit@lemmy.linuxuserspace.show 21 points 1 year ago (1 children)

But in the latter case you don't have to google. You already know what the problem is. The file it's looking for is missing. So I'd rather have that kind of message than just an error code.

[–] duncesplayed@lemmy.one 2 points 1 year ago* (last edited 1 year ago)

You definitely have to ~~go to the Arch wiki~~Google in some cases. Knowing what the problem is and knowing how to fix it are sometimes seemingly unrelated. E.g., "Could not open foo.yaml: File not found" could actually mean "Some non-obvious file in the tarball was not set executable, which screwed up this one script that ran another script but couldn't run some other script which didn't give an error message, which made another script think the file had already been copied". If you can find someone out there who ran into exactly the same problem, you can find a solution to it, but if none of the words in your error message are completely unique, it can be very hard to find someone with the same problem.