this post was submitted on 11 Nov 2023
1014 points (97.3% liked)

linuxmemes

21453 readers
935 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 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 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 44 points 1 year ago (2 children)

    Realistically you don't have to if you're not constantly tinkering, but if you're changing a lot of low-level stuff without knowing what you're doing, you have the ability to break things. If you don't know how to fix them, then it's easier to just reformat. Basically it's a skill issue lol.

    [–] eletes 7 points 1 year ago (5 children)

    I've broke things often and had to reinstall a lot because I didn't know what I was doing. Still kinda don't know, but do y'all recommend anyways to learn the knowledge?

    Like I could probably read through man pages but I want something that shows how everything builds on each other to fill any gaps I'm missing

    [–] [email protected] 8 points 1 year ago (1 children)

    The Arch Linux Wiki is an incredible resource, even if you're running another distro. Most of it is pretty universal (other than specific commands like the package manager), and it explains how everything functions and fits together. If I'm troubleshooting, it's always my first stop.

    [–] [email protected] 3 points 1 year ago

    That and the Gentoo handbook are two of the best resources for learning things about how Linux works

    [–] [email protected] 7 points 1 year ago* (last edited 1 year ago)

    Just keep breaking stuff! It means your learning and trying new things, for the most part. Eventually you'll just break stuff less and less or know what to look for when something breaks. On that note do try to struggle with something a little bit before rolling back or reinstalling.

    [–] [email protected] 1 points 1 year ago

    I would recommend reading the manuals yes. Their are many manuals and not all are equal. The man pages can feel a bit strange as they list everything the software can do. To learn I found the archwiki to be better. (Also info manuals but many people are weirded out by the controls used to read these.)

    Also don't blame yourself for reinstalling if you mess up. It's normal especially if you need the computer to actually work in a timely fashion

    [–] [email protected] 1 points 1 year ago

    Depends on what you're breaking I guess. If it's DE stuff, kernel stuff, etc. Usually I just find a good YouTube tutorial if I want to learn something new and don't know what I'm doing.

    [–] [email protected] 1 points 1 year ago

    Getting comfortable with manpages and regex will get you pretty far, this is a really great resource for beginners (available for free as .pdf):

    https://linuxcommand.org/tlcl.php

    [–] [email protected] 2 points 1 year ago

    Yep tinkering with the system is probably the main issue (for that NixOS is awesome btw.). But even when you're not constantly tinkering. System-State accumulates over time, bugs are also apparent in (upgrading of) distros, and the maintainers of a distro cannot realistically handle every upgrade time-point x -> y, so stuff will likely break after some time.

    But even when I have fixed all the issues in my previous at some time broken distros, at some point it just feels good to have a freshly installed system without all that dirty accumulated state (NixOS + impermanence and you'll have that every reboot :P, see also this)