Linux command-line survival guide

The command line becomes safer when you always know the current directory, preview targets, quote paths, read help, and prefer reversible operations. Commands compose through files, streams, pipes, and exit codes.

At a glance

Question	Practical answer
When is it useful?	Before moving logs, pwd confirms location, find previews exact files, a dry run checks the pattern, and the final command reports a non-zero exit code on failure.
What should you do?	In a temporary directory, practice pwd, ls, cd, mkdir, cp, mv, less, rg, find, head, tail, and checking $?; never practice deletion on valuable data.
How do you know it worked?	You can predict every target before changing it, paths with spaces work, and a deliberate failure produces an exit code your script can detect.
Common failure	Avoid broad globs, unresolved variables, and recursive destructive commands until the exact target list is printed and verified.

flowchart LR
  A[Question] --> B[Linux command-line survival guide]
  B --> C[Small example]
  C --> D[Evidence]

The important idea is not to stop at a definition: connect the concept to a small example and observable evidence.

Worked example

Before moving logs, pwd confirms location, find previews exact files, a dry run checks the pattern, and the final command reports a non-zero exit code on failure.

Before acting, write the success signal. Change one condition at a time, observe the result, and record assumptions. For Linux command-line survival guide, this separates what you know from what you are merely guessing.

Practice in 20–30 minutes

Goal: In a temporary directory, practice pwd, ls, cd, mkdir, cp, mv, less, rg, find, head, tail, and checking $?; never practice deletion on valuable data.

1. Record the starting state and your prediction.
2. Implement the smallest version without adding unnecessary tools.
3. Change exactly one input or constraint and repeat.
4. Save a command, screenshot, output, or checklist as evidence.

Expected result: You can predict every target before changing it, paths with spaces work, and a deliberate failure produces an exit code your script can detect.

What can go wrong

Avoid broad globs, unresolved variables, and recursive destructive commands until the exact target list is printed and verified.

When the result differs from your prediction, do not change many things at once. Check inputs, versions, environment, permissions, and logs, then repeat from the smallest example.

Definition of done

• I can explain the concept in my own words.
• I completed the small example and kept evidence.
• I know one failure mode and how to check it.
• Someone else can repeat the work without guessing missing steps.

Go deeper

Use the linked resource or repository at the end of the page when you need a full implementation. Check current versions before applying commands to a real project.