Linux Terminal Commands

Linux terminal commands: A practical reference to everyday shell commands for navigating a Linux system, inspecting files and finding command help. This guide explains what each command does, its syntax, practical examples, useful options, and common mistakes. Commands are shown for typical installations; flags can vary across operating-system and tool versions.

Before you start

Open a terminal appropriate for the operating system shown in the examples. Check that the required tool is installed and that you are running it with the permissions needed for your task. Replace sample names, paths, hostnames and IDs with values from your own environment.

Syntax at a glance

Square brackets usually indicate optional arguments, while uppercase words such as FILE, HOST and PACKAGE are placeholders that you replace. Keep quotes around paths or text that contains spaces. Commands should be tested on a safe sample before being used in production.

Quick command reference

Command syntax and examples explained

1. pwd

Purpose: Print the current working directory.

Syntax

pwd

Example

pwd

Options and notes: No extra option needed.

Use this first when you are unsure which folder a relative path refers to.

2. ls -lah

Purpose: List files, including hidden files, with readable sizes.

Syntax

ls -lah

Example

ls -lah /var/www

Options and notes: -a includes dotfiles; -l shows details; -h uses human-readable sizes.

The output includes permissions, owner, size and modification time.

3. cd

Purpose: Change the current directory.

Syntax

cd DIRECTORY

Example

cd /var/www/html

Options and notes: cd .. moves up; cd ~ returns to the home directory.

Quote paths containing spaces, for example cd "My Projects".

4. whoami

Purpose: Show the effective current username.

Syntax

whoami

Example

whoami

Options and notes: Usually no options are needed.

This helps confirm which user account will own files created by later commands.

5. man

Purpose: Open the manual page for a command.

Syntax

man COMMAND

Example

man find

Options and notes: Press q to quit; /word searches within the manual.

Manual pages document flags, defaults and examples for installed tools.

Common mistakes and troubleshooting

• Command not found: confirm the tool is installed and available on your PATH; open a new terminal after changing PATH.
• Permission denied: verify the current account, file permissions and target path. Use administrator/root privileges only when genuinely required.
• Unexpected output: check the command version, quoting, current directory and exact arguments. Consult the local help or manual for options supported by your build.
• Destructive operations: preview the target and keep a backup before deleting data, rewriting history, flashing a partition or changing system configuration.

Safety tips

Review every command before running it, especially commands that delete files, change permissions, flash firmware, alter a database or expose a network service. For network scanning and remote administration, work only on devices and systems you own or are authorized to test. Keep credentials, private keys, access tokens and log files private.

Frequently asked questions

Do these commands work on every system?

Not always. Some commands are specific to Windows, Linux, Android, a particular package manager or an installed tool version. Use the syntax shown for your platform and check local help when a flag is unavailable.

Can I copy and run every example exactly?

Use the examples as templates. Replace placeholders such as filenames, package IDs, hostnames and paths with your own values, and verify the effect before executing a command that changes data or system state.

Conclusion

Use this reference as a starting point, then confirm flags in the tool’s official help or manual for your installed version. A clear understanding of syntax, options and side effects makes command-line work more reliable.