this post was submitted on 03 Feb 2024
1311 points (98.4% liked)

linuxmemes

21197 readers
140 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!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [โ€“] [email protected] 3 points 9 months ago (1 children)

    There are enty of books you can read. If you're really interested in learning I suggest you may start learning how to write bash.

    For the rest I really would say, that just try doing stuff. Try to set up a docker, or other stuff. Also you can go to already solved Problems and try to understand what the problem was and what they did to solve it.

    Also: Just start trying to support people. Google(or any other Search Engine of your liking) is very useful for this. Even if you just find out what exactly the problem is, that helps.

    [โ€“] [email protected] 5 points 9 months ago

    thanks. i have a laptop i deliberately installed debian on.. but that's about it lol

    i'll take you up on the support suggestion too.. i recently had to figure out why a unix server went down at work. luckily we had a set of scripts and commands archived from the manager that supported it before he left. all i did was just run them with a little bit of logic and context applied, but it forced me to poke around a bit and seeing what each command did. i was careful enough not to break anything but i found it quite interesting