7 tricks to make learning the Linux command line easier


The Linux command line can seem impenetrable, with arcane instructions and a focus on text interfaces. Fortunately, there are plenty of resources and tools to help you get started.

Customize your terminal to fit your needs

Make the terminal feel like home

The first thing you should do is make your learning environment as comfortable as possible. You don’t want to spend too much time tweaking every last setting, but getting the basics right can make everything that follows a little bit smoother.

The settings will vary depending on your distro, but things to look out for include:

  • Light/dark mode: pick whichever you’re most comfortable reading text in.
  • Font: you’ll want to use something monospaced with clear differences between similar characters e.g. “0” (zero) and “O” (uppercase “oh”).
  • Whether to open new terminals in tabs or windows.
Ubuntu terminal preferences showing settings for text and background color.

You’ll also want to know how to use keyboard shortcuts since 99% of your work on the command line will involve typing. Don’t be afraid to open several terminal windows (or tabs) to run commands simultaneously and organize your tasks.

Ubuntu terminal preferences showing keyboard shortcuts for common operations.

Customize your shell to your liking

Legibility is key

Once you’ve customized your terminal app, you should make a couple of small changes to your shell. This is typically bash, although you can change it to an alternative shell, like fish or zsh.

One of the best quick upgrades you can make is to customize your prompt, the text your shell displays at the beginning of each line. The default is quite useful, but you can make it more useful for learning Linux. I like to use this setup:

export PS1="\n[\$PWD] \$ "

This will remove things like your username and host, which you probably won’t care about when starting. It also displays the full path of your current directory rather than just its name, making it easier to see your current location at a glance:

A Linux terminal showing a custom prompt containing the full path of the current directory.

You can make this setting permanent by adding it to your .bashrc (or similar) file. That file is also a great place to set up aliases, which act like shortcuts for commands. If you find it difficult to remember a command’s name, or its most useful default options, set up an alias, e.g.

alias list='ls -l'

Learn all about commands with man (and alternatives)

man pages are your best friend

Each command you’ll need to learn has built-in documentation that you can read using the man tool. These “man pages” explain what a command does, different modes of operation, what files it requires, etc.

The Linux man page for the rmdir command showing various options and other details.

The man pages are comprehensive, but they can be a bit overwhelming, especially when you’re getting to know the system. Fortunately, there are alternatives.

Each command will usually support a -h or –help option, which explains how to use it in a simpler form:

The Linux pwd command with the --help option showing brief usage information.

The tldr tool condenses long man pages into more manageable summaries. Here’s a comparison of a classic man page on the left alongside the tldr equivalent on the right:

A Linux man page alongside a tldr equivalent which is much briefer, with clear examples.

tldr shows minimal information, following it up with clear examples for the most common uses of each command. You can install it using your system’s package manager. If you just want to try tldr out, its web interface is excellent:

The Linux tldr web interface showing formatted help for the mkdir command.

Find the commands you need with apropos

Teach yourself to fish

Linux commands often have short, abbreviated names for historical reasons. It can be tricky to remember your “chown” from your “sudo.”

First, try exploring the directories listed in your PATH variable. These will contain programs you can run on the command line. Run:

echo $PATH

That shows a set of directories with colon (:) characters between them. Then run:

ls dirname

This will show the contents of one of these directories. And files that appear are executable commands you can run:

Linux commands showing the contents of the PATH variable and commands in the /bin directory.

If you’re still having trouble identifying a command, try apropos, a search tool for man pages. Use it when you’re looking for a specific command, but you’re not sure what it’s called. Just run:

apropos keyword

That will search for a keyword and see relevant man pages.

Output from the Linux apropos command showing other commands related to the keyword "pdf."

Consult these excellent and approachable resources

Don’t go it alone!

For further reading, there are plenty of online resources you can consult for free. Find a reliable source that caters to your level of experience and work through everything it has to offer.

The Linux command line for beginners guides you from the very beginning, covering all the basics you’ll need when setting out. It’s aimed at Ubuntu users, but if you can open a terminal, you’ll be able to follow everything.

A page from the "Linux command line for beginners" site explaining how to open a terminal in Ubuntu.

Linux Journey: Command Line provides a short overview of the most important commands, with associated exercises and interactive quiz questions.

Linux command line for you and me has everything for absolute beginners to more advanced users, so work through it from beginning to end if you’re aiming to be an expert. It’s also highly usable as a reference source.

This Linux Tutorial from Ryans Tutorials explains the core concepts with plenty of interesting asides, tips, and insight. It features many diverse examples which help to explain how the command line works.

Take a deep dive with manuals from the Linux documentation project

Get the official guidance you need

The LDP is a long-standing initiative to create free, quality documentation on everything to do with Linux. As such, it offers a wealth of obscure, illuminating material, not all of which is useful for beginners.

However, there are still some excellent sources of information, if you’re willing to overlook the old-school presentation.

GNU/Linux Command-Line Tools Summary covers all sorts of built-in commands and how to use the command line. It also shows examples on how to run many of them.

Bash Guide for Beginners explains the specifics of the bash shell, how it handles your commands, and how you can write your own scripts.


Continue learning with some help from How-To Geek

We have a wide selection of Linux articles, for beginners and more advanced users. Several of them are already linked in this article, but here are some others that you’ll find …



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


I reluctantly upgraded from my Pixel 4a in late 2024, which means I spent four years clinging to a phone that still felt like a phone. Part of that was the size. The Pixel 4a was small enough to use without performing thumb yoga, a disappearing luxury now that flagships have settled into pocket-tablet territory. That’s an argument for another day.

The uglier issue is what happened after I moved on. In January 2025, Google pushed an automatic Android 13 update to Pixel 4a phones. Google’s own support page says the update reduced available battery capacity and affected charging performance on some impacted devices. Reddit users were less polite. One r/Pixel4a post said the battery suddenly had “around 40% of its former capacity” after the patch.

For poor ol’ 4a, that was basically the death knell.

When an update becomes the problem

A dying battery is normal. A four-year-old phone needing service isn’t exactly a scandal. Batteries age, screens fail, ports loosen, and gravity remains undefeated.

This felt different. The phone didn’t simply get old in someone’s pocket. Its usable life changed after a company-controlled patch, and the owner was left to deal with the result. The Verge reported that the update was tied to overheating-risk mitigation and reduced charging capacity by more than 50% on affected units. Battery safety is real. It still doesn’t erase the experience of waking up to a phone that suddenly can’t survive the day.

That’s what update death looks like. Software doesn’t just support aging hardware anymore. It can also decide when that hardware becomes miserable to keep using.

When every patch feels haunted

My wife, who’s rocking an S24 Ultra, has a different version of the same dread. She keeps running into Reddit threads about Samsung Galaxy phones and the dreaded green line, that bright vertical scar that makes a screen look like it has been reassigned to a cyberpunk prop department. One r/S23 user wrote that a green line appeared on a carefully maintained phone after about a year and a half, then said Samsung service quoted a screen replacement because the warranty was over. Another Samsung Community post claimed a green-line issue appeared after an August update, with the display allegedly working perfectly before it.

Reddit isn’t a forensic lab with avatars. A green line can come from boring hardware failure, not corporate villainy with a release calendar. Still, the anxiety is real. People don’t only worry that an update will move a button or ruin a camera setting. They worry it might be the thing that nudges a working device from “old” to “not worth repairing.”

Modern gadgets are never fully handed over. They keep phoning home. They keep asking for patches. They keep depending on decisions made long after the receipt has faded. Ownership now comes with a quiet asterisk.

The graveyard got software updates

Planned obsolescence used to sound like tinfoil-hat consumer paranoia, which was convenient for everyone selling the new thing. Then regulators started writing it down in boring official language. In 2018, Italy’s competition authority fined Samsung and Apple after finding that software and firmware updates caused serious malfunctions, reduced performance, and sped up replacement of older phones. Samsung was fined €5 million, while Apple was fined €10 million.

Apple’s battery-throttling mess made the suspicion harder to laugh off. In the US, Apple agreed to a settlement of up to $500 million over claims that it slowed older iPhones, while a separate multistate settlement required Apple to pay $113 million over alleged misrepresentations around iPhone batteries and performance throttling. Consumers weren’t hallucinating the pattern. The receipts were scattered across court filings, regulatory decisions, and phones that suddenly felt older than they had the day before.

Europe seems less willing to accept “trust us” as a product-lifetime policy. New EU rules for smartphones and tablets started applying on June 20, 2025, covering durability, repairability, battery life, and software updates. New labels put some of that lifespan math in front of shoppers before checkout.

The post-warranty graveyard used to be easy to recognize: cracked screens, swollen batteries, and charging ports full of pocket lint. Now the graveyard has paperwork, compatibility warnings, and software that slowly stops cooperating. The gadget can still turn on. It can still look fine on a desk. Then one day the company changes what “usable” means, and the thing you paid for starts practicing being trash.



Source link