Linux Command Line Tasks Without Surprises

The safest terminal command is one you can explain before you run it. Work out what a command will read, what it will change, and whether you can reverse the change.

Inspect before editing

Use pwd to confirm where you are and ls -la to see what is present. For a search or replacement, print matching lines before changing files. Quote paths with spaces, and try the command on a disposable copy when you are unsure.

Read the flags

Flags can change a harmless-looking command into a destructive one. Check --help or the manual page before using -r, -f, or a command piped into a shell. Generated commands are starting points, not permission to run them as root without inspection.

Related tools

• chmod Calculator — Convert between octal and symbolic Unix file permissions.
• Cron Next Runs — Preview the next scheduled runs of a cron expression in local time or UTC.
• Crontab Generator — Build a cron expression and read it back in plain language.
• find Command Builder — Assemble a find command with name, type, size, age and depth tests, then choose to print, delete or exec on each match.
• Git Cheatsheet — A quick reference of the Git commands I keep forgetting.
• grep Pattern Builder — Build a grep command with the right regex style, recursion, includes and context lines, then copy it.
• Dev Ops — Describe a Linux problem and get safe commands, flag explanations, a risk level and the next troubleshooting steps — all in the browser.
• sed Replacement Builder — Build a sed command to replace text, delete matching lines or print only matches, with in-place editing and backups.
• xargs Builder — Build and explain an xargs command — null input, batch size, parallelism and a replace string, with a note on each flag.