this post was submitted on 27 Oct 2023
1835 points (98.4% liked)

linuxmemes

21631 readers
45 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 2 years ago
    MODERATORS
    [email protected]
    [email protected]
    [email protected]
    1835
    Solid advice (lemmy.world)
    submitted 1 year ago by [email protected] to c/[email protected]
    177 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 8 points 1 year ago

    I've been on Linux for about a year and a half. So just passing the newbie phase I guess.

    My advice is to dive right in. Don't know what that file does? Delete it. Punch in cd /; rm -rf, try to us ethe find command, think you understand the find command. Then avoid the find command like your creepy uncle. Open up vim, have no idea what vim is, and restart your computer because there's a snowballs chance in hell of figuring it out once you're already in vim. Fuck the install of your first distro beyond recognition, download a new one and do it again. That last one isn't advice, it's going to happen so you might as well embrace it.

    Just try shit. Say: I wonder how I.... And then figure it out. Look into what all the symbols on the bash scripts do. Be curious and brave and remember that as long as you back up the important shit you may fuck something badly enough that it's not worth fixing but a reinstall doesn't take very long and it gives you a chance to try another distro anyway.

    I'm telling you when the terminal "clicks" it's such a good feeling. When you write a short bash script that works the first time without looking for help it feels GOOD. But nothing as good as peeling back layer after layer of abstraction and seeing there right in front of you all the shit Microsoft keeps from you. Sure most of an s trace is total fucking jibberish and probably always will be because I don't have myself enough to learn C but just look at all the stuff my computer does! Boy, look at it go.

    Bottom Line is that you can read all the books and how to guides in the world but none of them will do more to carry you forward into the perplexing and frustrating world of computers like a wild-eyed sense of curiosity and a bottle full of Xanax