Recommended Free Tools
Five commands often taught early in Linux are cd, ls, cp, mv and rm. They remain useful, but someone who now manages files in a graphical file manager, works from a project directory, or automates repeated tasks may type them less often. This is an illustrative list, not a claim that every Linux user—or this article’s author—learned the same five commands or stopped using them.
Which five commands are we talking about?
These commands cover basic navigation and file handling. One technical distinction matters: cd is a Bash shell builtin, while ls, cp, mv, and rm are documented GNU utilities. “Linux command” is convenient shorthand, but familiar commands do not all work in exactly the same way or belong to the same technical category. GNU-specific behavior can also differ from other implementations.
As an Amazon Associate I earn from qualifying purchases.
| Command | What it does | Why someone might type it less | What remains worth learning |
|---|---|---|---|
cd |
Changes the current directory in the shell. | Starting work in a terminal already opened at the relevant folder, or handling files in a graphical application. | Relative paths, the current working directory, and how a shell’s location affects commands. |
ls |
Lists directory contents. | Using a file manager, editor sidebar, or another tool that already displays the project files. | How to inspect a directory and recognize hidden files, names, and paths; exact options depend on the implementation. |
cp |
Copies files or directories. | Copying through a graphical interface, or using a repeatable script or application workflow. | Source and destination order, recursive-copy options where needed, and the risk of copying to the wrong place. |
mv |
Moves or renames files or directories. | Dragging files in a file manager, renaming in an editor, or letting a tool organize generated output. | That a move can change a file’s location or name, and that destinations and existing files deserve attention. |
rm |
Removes files or directories. | Deleting through a graphical interface that offers a review or recovery path, or avoiding manual cleanup through automation. | That removal may be difficult or impossible to undo; verify the target before executing. |
GNU’s documentation describes these file operations and the broader Coreutils manual documents utilities such as ls and cat. Bash documents shell syntax and builtins, including cd. Consult the documentation for the system and implementation you use: GNU Coreutils basic operations, GNU Coreutils manual, and the Bash manual.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesWhy might these commands fade from everyday use?
Learning a command and typing it every day are different things. A command can teach a durable idea even when another interface becomes more convenient for a particular task. The reasons below are possible workflow changes, not measured trends or claims about how often Linux users run these commands.
#1 Best Overall
A graphical workflow handles the same action
A file manager can show folders, move or rename items, and provide a visual way to select files. An editor can expose project files in a sidebar. In those workflows, cd and ls may be unnecessary for locating a file, while cp, mv, and rm may be replaced by interface actions. The trade-off is that visual selection does not remove the need to understand which file or folder is being changed.
The terminal starts in the right place
Some applications open a terminal at a project directory, or a person may keep a shell session there. That reduces the need to navigate with cd. It does not make paths irrelevant: a relative path is interpreted from the shell’s current directory, so knowing where that directory is still matters.
Rank #2
A repeated operation becomes a script or application task
For a repeatable task, automation may perform a sequence of file operations instead of requiring each command to be entered by hand. A tool may also create or organize files itself. This shifts attention from remembering individual commands to checking what the automation will target and what it will change.
Free tools Windows power users keep installed
One-click scans. No signup required.
What should you keep from learning them?
Even if you rarely type a command, its underlying concepts help you understand tutorials, error messages, scripts, and terminal instructions. The useful foundation is not memorizing a long list of options; it is understanding the current location, the path being addressed, the source and destination of a file operation, and the consequences of a deletion.
Rank #3
- For navigation: know how to identify the current directory and interpret an absolute path versus a relative one.
- For listing: recognize that a directory listing is an inspection step, and that files not shown by a tool’s default view may still exist.
- For copying and moving: identify which path is the source and which is the destination before running a command.
- For deletion: slow down and inspect the exact target. A typo or misunderstood path can affect the wrong files.
- For portability: check the manual for the implementation installed on your system rather than assuming every option is universal.
How to practice without risking important files
- Make a disposable practice folder. Create it in a location you can identify easily, and put only test files inside.
- Check your location and inspect the folder. Use
pwdto print the current working directory, then uselsto list its contents. These commands help confirm what a relative path will refer to. - Practice a copy and a rename or move with test files. Read the command’s help or manual first. GNU Coreutils documents the behavior of
cpandmvin its basic operations reference. - Inspect a deletion target before removing it. Read the full path and command, including any options, before pressing Enter. Do not assume that a terminal deletion will behave like moving a file to a graphical trash folder.
- Look up unfamiliar syntax. Use the installed manual page or the documentation for the relevant shell or utility. For GNU utilities, the Coreutils manual is a reference; for Bash shell behavior, consult the Bash manual.
The command name alone is not a complete instruction. Options, arguments, paths, and the environment determine what happens, so learn to read the whole command before running it—especially when it changes or removes files.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Does learning these commands still make sense?
Yes, if you use a Linux terminal or want to understand instructions and scripts that assume one. These five provide a compact introduction to navigation and common file operations, but they are not a universal list of the first commands everyone should learn. What matters most is matching practice to your tasks and understanding the effect of each operation, rather than measuring progress by how often you type a particular command.
Quick Recap
Best Value
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
