if the avg enduser has to temper in a commandline, your program is ass.
this post was submitted on 06 May 2025
110 points (95.8% liked)
Linux
53979 readers
1263 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
As someone who started with nothing but command line - Timex Sinclair, Apple IIe, DOS, I can’t even relate to the concept of being scared of command line.
Play around in a virtual machine so you don't have to worry about messing anything up. Start with the basics such as navigating through directories and creating, editing, and moving files. If you break something, just restore a snapshot.
The way I usually start teaching using the console to my (very much non-tech) students is set up a safe container and then let them type whatever, invariably generating a lot of error messages. Then I challenge them to generate different error messages, "gotta catch em all" style. Then we talk about the error messages and what they might mean. After this exercise they usually get the basic idea of command -- response, what to look out for and how to compose valid commands.
That's clever
Or just use Time Shift or a similar tool. I broke my first linux install like a dozen times, and I learned so much about how my computer operates in the process.
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.
Clear instructions on how to do a clearly defined, specific task, in a failsoft manner, faster and easier, which helps them in a project they are doing now.
Step 1: Use a youtube tutorial for the basic commands. Don't worry, you'll forget about them soon enough. But doing them once, helps with muscle memory. Step 2: When in need to do something, copy/paste from Q&A/forums various commands that they suggest for your problem. Your basic knowledge from step1 will come back as you do that.
After a few days, you'll be understanding what's going on and how the whole thing works in an abstract level.
I would recommand to never copy paste but retype so you have the commands on your finger memory.
Also don't be afraid to --help everything. It give more option for commands you know quicker than the man.
Practice.
I’m trying to make it a regular thing but my problem is I like to get my hands dirty by working on projects. The snag is that I get stuck a lot due to not knowing basics. My personality gets in the way = get dirty and learn fast(not necessarily shortcuts). Maybe I haven’t found that right source to learn that not too beginner and not too intermediate. Maybe a cool cluster of small projects to setup your computer then environment to setting up projects to do your everyday life takes to what you really want to learn.
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.