this post was submitted on 19 Aug 2025
1909 points (98.5% liked)

linuxmemes

28472 readers
1733 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • 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.
  • 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, no politics, no trolling or ragebaiting.
  • Don't come looking for advice, this is not the right community.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. 🇬🇧 Language/язык/Sprache
  • This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  •  

    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 remove France.

    founded 2 years ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] ragebutt@lemmy.dbzer0.com 92 points 3 months ago (8 children)

    I mean this is true and yes but in an age where documentation is increasingly terrible, the idea of a service manual for something you bought is basically a foreign concept, and half the shit you buy doesn’t come with a meaningful manual does it really apply the same way?

    Like sure, knowing the post error codes on my motherboard or linux stuff is possible because it’s documented. But the appliance example? That is increasingly false and those manuals are increasingly becoming 5 page idiot guides: “here is how to turn the system on and off, here is how to turn heat up/down, contact authorized vendor for issues” and if you don’t do that then you void your warranty. Any more robust documentation is locked to “authorized vendors” and costs $$$, if it even exists (and doesn’t just say “replace system when it stops working correctly)

    [–] Bazoogle@lemmy.world 26 points 3 months ago (7 children)

    I partly disagree with what you say. The subscription appliance garbage absolutely do lock advanced user manuals behind paywalls. But it isn't not rare (at least right now) to still find products with good user manuals. There are usually separate documents with one being a "quick setup" and another being a full "user manual". Avoid the worst offenders and you should be okay.

    [–] Krzd@lemmy.world 13 points 3 months ago (1 children)

    Eh. I own a few old tools with manuals, and they actually have diagrams of the inner workings together with part numbers, some even have electrical diagrams with resistor values etc. All of the newer tools have a tiny useless "visit this website for more information" and 50% of the time it's some bs about errors 1-10: restart device, 10-20 please contact a technician because opening the tool voids your warranty. I know dipshit, I don't care about warranty cause I need the tool now or tomorrow, not in 3 months when you tell me it's "unserviceable" or "uneconomical to repair" and I have to buy a new one.

    [–] Bazoogle@lemmy.world 4 points 3 months ago

    I agree with the fact that there are not thorough diagrams with part numbers and wirijg diagrams like there used to be. A part of it is the fault of the manufacturer, and a part of it is just the way things are made now. Circuit boards are not as simple as they once were to include comprehensive wiring diagrams. They could absolutely break the modules into different boards and label the boards with different part numbers, so rather than replacing a resistor you'd just have to replace that board. It's also not clear to me how many people actually have a comprehensive understanding of the item being sold.

    But there is the obvious fact that companies want you to buy another one and not repair it. It's often cheaper for them to not repair the product themselves, and just replace the entire unit. They dont keep a surplus of parts for repairs, nor do they want to spend the man power troubleshooting and fixing the issue. It's just cheaper to replace it entirely. If they themselves will just replace rather than repair why would they bother keeping detailed documentation. If anyone cared for the enviornment more than money, they'd probably do it. But we all know how that goes.

    I would also add that even previously they were prioritizing money. It was just cheaper for them to make it repairable, especially if they are going to offer some sort of warranty. It was also good for business since it made customers happy. I think at some point it became cheaper to do it the way we do now

    load more comments (5 replies)
    load more comments (5 replies)