if the avg enduser has to temper in a commandline, your program is ass.
this post was submitted on 06 May 2025
114 points (96.7% liked)
Linux
56329 readers
699 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 6 years ago
MODERATORS
Knowing the commands
Well, it's easy... just be born in the early 80s and grow up with home micros!
2 things got me comfortable on command line: 1) A great cheat sheet (one from Ubuntu: https://ubuntu.com/download/server/thank-you); 2) Practice all the commands from the cheat list regularly. Last page is something for Pro version, but first 2 pages are great for a begginer. There is a typo at a command (or it was in a past cheat sheet): "Sudo change " instead of "sudo chage ". It helped me most to get comfortable with terminal. Enjoy!
Virtual environment? Taking notes of what they did?
Anyway, tell them it's okay you experiment and mess things up. Show them how to backup their important work. Then walk them through inevitably having to reinstall their distro.
They'll learn that you can just keep moving forward, fixing and learning as you go.
C:[Enter]
###
in my experience, practice, practice, and more practice. but "just git gud m8" isn't really helpful advice. if you don't have half a decade on hand, i can make a few more practical recommendations.
a shell that can do argument autocomplete is your best friend. personally, i use zsh + ohmyzsh + fzf + fzf-tab, but i'm sure there are other configs, and i've heard ohmyzsh is a bit of a nightmare, though i haven't had too many issues.
so let's say you're running the one rsync command this month, and you forgot the args, just tab-tab and you can search through the arguments with fzf.
I want a dropdown terminal la guake and yuake. Both options don't work on my Fedora. Because of this, I almost never use the terminal.
- making it ✨pretty✨
- using it a bunch
- man pages
- arch wiki
Practice.
The need to do it plus the realization that you can script anything based on it.
Drivers. Using recovery mode. Administration. Wanting to describe what to do rather then manually do it. Wild cards are really powerful and so is find and xargs. The text processing commands are useful too.
The other thing is having started computing in the 1970s. Everything was command line back then. GUI systems only become universal in about 1995.
Doing hackthebox or other CTF challenges, Using CLI software, writing bash scripts.