I am a Linux beginner/amateur and I have sort of had enough of copy and pasting commands I find on the internet without having a good understanding of how they actually work.

I guess my end goal is to be able to comfortably install and use arch Linux with my own customization’s and be able to fix it when things go wrong.

What tips/ideas do you have for getting better at navigating the terminal, and getting a better understanding of how the os works. What is a good roadmap to follow? And how did you, advanced Linux user, get to the stage your at now?

Edit: my current distro is bazzite just in case you were interested and thanks for all the replies you are all really helpful.

    • pineapple@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 months ago

      I thought rolling releases were still pretty stable to things really break that often?

      • TheFadingOne@feddit.org
        link
        fedilink
        arrow-up
        4
        arrow-down
        1
        ·
        edit-2
        2 months ago

        They can be really stable. I think your milage severely varies on how much you know what you’re doing and how careful you are in respect to certain things.

        Personally I’ve been using Arch for 5 years and I haven’t really had any problems with things breaking on updates.

  • blob42@lemmy.ml
    link
    fedilink
    arrow-up
    17
    arrow-down
    1
    ·
    2 months ago

    start from man man and learn to use man pages. Get used to lookup man pages for any topic before checking on the internet

    • ouch@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      2 months ago

      Learning to read manpages is honestly the best advice. They are pretty dense in information, so maybe that’s why some people go to great lengths to run circles around them looking for inferior sources of information.

    • stinkape@lemm.ee
      link
      fedilink
      English
      arrow-up
      10
      ·
      2 months ago

      This is it. You’re likely not going to get away from needing help from time to time. Instead of focusing on trying to know everything, focus on knowing where to find what you need. It’ll click from there with time.

  • phantomwise@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 months ago

    Using tldr to learn commands. It gives you the information you are probably looking for in the man page but it’s not buried among lines and lines and lines of arcane stuff and it’s formatted in a readable way with helpful examples. Saved my sanity more than once.

    I’m not saying “don’t read the man pages”, they are great way to get a deeper understanding of commands. But when you are just wondering what a command does and how it’s commonly used, then a two lines summary + example is much more helpful than an essay going in minute details over everything.

    Since it takes a lot less time than hunting the same info in the man page, you can run it before every command you are not familiar with, without too much hassle. Then if you want more info you can check the man page.

      • pineapple@lemmy.mlOP
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 months ago

        Wait I did this to my main drive everything went black is this suposed to happen? will it start working again?

        • Blisterexe@lemmy.zip
          link
          fedilink
          arrow-up
          1
          ·
          2 months ago

          in case you aren’t joking, rm -rf / (albiet with a warning now) will delete allll the files on your system, so everything going black is the expected result.

          rm is remove, the - is to indicate that you want to pass arguments, and r&f are recursive (delete stuff in the folders in this folder) and force (don’t ask for confirmation). The slash afterwards designates the root folder, the folder with everything in it.

          So “rm -rf /” means “remove, recursively and forcefully, everything in the / directory”

  • BaumGeist@lemmy.ml
    link
    fedilink
    arrow-up
    3
    ·
    2 months ago

    I will be using your example of Arch as a great stepping off point, because honestly imo the best way to learn is by having a project to work on

    1. RTFM - Read The Fucking Manual. Read the docs, read the code comments if need be. In the case of installing an OS, use the installation guide as a starting point; Arch’s is on their wiki, and links to several other sections that go more in-depth about what each step does and why it does it.

    2. DuckDuck it - if you don’t understand what something is or why you’re doing it, search it. If you understand it completely, search it anyway and check the docs because no you don’t, you just don’t know how little you know. If you know why we do something and what function it fulfills, but not how… Then you’re a power user.

    Using your example of commands from the internet, break the command down into as many parts as you can, and figure out what each part does. If there’s punctuation marks, don’t assume you know what those are doing. man [command's name] is your friend.

    1. Do all of the above as often as possible, no matter how slow it makes progress feel. Learning these things the proper way now will save you from days, weeks and months of troubleshooting in the future. I mean it, literally at every step of the process.

    2. secondary sources are invaluable, but for this it might help to get into the best way to self-educate. The only gospel are the docs and/or manual that were written by the code/OS maintainers - primary sources - everything else is opinion.

    Here’s a source i agree with on the best way to self-educate, but keep in mind even Artem is still just a secondary source.

    That being said, here’s a few secondary sources that helped me understand how OSes work and why:

    nand2tetris: build an operating system starting with logic gates and working your way up from there. It has a offshoot site that’s slowly being rolled out, that implements it all in a gamified interface: nandgame

    os-tutorial: build an OS from scratch

    Linux From Scratch: Learn everything about Linux by building your own distro from the kernel up.

    Unfortunately everything that taught about the behind-the-scenes aspects of OSes in general—and Linux in specific—were either projects like the above, or just seeing what came up in a DuckDuckGo, Youtube, forum, or wiki etc. search. Below are just resources that teach you about the “power user” level of knowledge, not “super user” but not your average user either.

    Fireships’ 100+ Linux Things you Need to Know: it’s not particularly good on its own, but it does introduce a lot of concepts and vocab for you to then look up elsewhere

    freeCodeCamp.org offers a lot of courses that will go over using Linux. None go too in-depth on the fundamentals of Operating Systems, but they will still introduce most of what you need to know for day-to-day use. I don’t want to link them all, but just search for linux freecodecamp on youtube and find one that piques your interest. The longer, the more in-depth—you don’t have to watch it all in one sitting.

    1. And of course, when all else fails: just ask. Participate in the community, don’t be afraid of looking stupid. The only people that get no respect are the ones who refuse to accept others’ help because they know better than those they’re asking to help them. (ignore the gatekeepers who want to project their own need for an identity onto you)
  • secret300@lemmy.sdf.org
    link
    fedilink
    arrow-up
    6
    ·
    2 months ago

    To be honest I’ve been using Linux for years and I still paste commands all the time. The only difference is that now when I am trouble shooting I know what command I need just not the options and how to use it

  • unrealapex@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    2 months ago

    I’d recommend reading man pages. They’re a great way to understand the programs that are on your system. The Arch Wiki and the Gentoo Wiki both provide additional information that may be of use to you.

  • Fubarberry@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 months ago

    I learned a lot by using a less common distro (solus). When I would have a problem, the solutions I could find on forums or arch wiki wouldn’t apply to my distro directly, and I would have to look into the solution for long enough to understand what needed to change in order for the solution to work.

    You can probably do this on any distro, just by not using commands you find online until you understand what they’re doing and why that might fix your problem. Arch wiki is a great resource for any distro, even though it won’t always be accurate for the distro you’re on.

  • JTskulk@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    2 months ago

    Read and do! If it’s just a toy you play with sometimes, you might find learning harder. I find that making it your daily driver will motivate you to improve and fix things and in doing that you’ll learn.

  • stebator@lemmy.world
    link
    fedilink
    arrow-up
    6
    arrow-down
    1
    ·
    2 months ago

    If you are beginner in Linux, try beginner-friendly Arch-based distro: EndeavourOS, CachyOS, Manjaro

    You can learn Arch without too much hassle while using one of them

    • N0x0n@lemmy.ml
      link
      fedilink
      arrow-up
      5
      ·
      2 months ago

      EndeavourOS is great ! While it’s easier to install than Arch (I guess?) and give you tools to maintain your system, it’s still in need of daily maintenance to keep your system healthy and operational.

      You learn things but at slower pace and with less headache as a beginner. I’m very thankful EOS exists and give you a glimpse on how to configure/maintain and evolve with the Arch ecosystem !