Read a shell prompt, move through directories, inspect paths, and verify location before running commands that change files.

What you will be able to do

Explain the five core decisions involved in navigate the linux command line.
Choose the narrow Linux command or method that matches a stated operational need.
Interpret command output as evidence before deciding whether to change system state.
Apply an observe, act, verify, and recover workflow to a realistic Linux task.

Build the Operating Model

Read a shell prompt, move through directories, inspect paths, and verify location before running commands that change files.

Reliable Linux work separates observation, decision, action, and verification. That order keeps a command from becoming a guess and makes each result useful for the next decision.

Begin in a disposable lab or a recoverable environment. Record the active user, working directory, target, and baseline output before any command that can change system state.

Prompt and command

The prompt marks a shell ready for input, while the typed command requests one specific operation. This distinction helps identify the smallest relevant part of the system before a change is attempted.

Read the prompt context, type one command, and inspect its output before entering the next command. Keep the command, target, and visible result together so another person can reproduce the reasoning.

The safety boundary is clear: do not copy a prompt symbol as input. You should be able to verify this result: one command and its visible result.

Working directory

A running shell process has a current working directory that anchors relative path names. This distinction helps identify the smallest relevant part of the system before a change is attempted.

Run `pwd`, compare the printed path with your intended location, and correct the location before changing files. Keep the command, target, and visible result together so another person can reproduce the reasoning.

The safety boundary is clear: verify location before destructive commands. You should be able to verify this result: an absolute path for the current location.

Directory movement

The `cd` shell builtin changes the current directory used to resolve later relative paths. This distinction helps identify the smallest relevant part of the system before a change is attempted.

Move with `cd <path>`, then use `pwd` so the new location is confirmed rather than assumed. Keep the command, target, and visible result together so another person can reproduce the reasoning.

The safety boundary is clear: quote path names that contain spaces. You should be able to verify this result: a confirmed new working directory.

Path forms

An absolute path starts at the root directory, while a relative path starts at the working directory. This distinction helps identify the smallest relevant part of the system before a change is attempted.

Choose an absolute path when location must be unambiguous and a relative path when the current context is intentional. Keep the command, target, and visible result together so another person can reproduce the reasoning.

The safety boundary is clear: do not confuse root with the home directory. You should be able to verify this result: a path resolved from the intended starting point.

Directory listing

The `ls` command lists directory entries, and options can reveal hidden names or detailed metadata. This distinction helps identify the smallest relevant part of the system before a change is attempted.

Start with `ls`, add `-a` for hidden entries, and add `-l` when permissions and ownership matter. Keep the command, target, and visible result together so another person can reproduce the reasoning.

The safety boundary is clear: a listing does not change the working directory. You should be able to verify this result: entries and selected metadata for a directory.

Apply One Controlled Change

Start from the read-only commands that reveal identity, scope, and current state. Write the expected result before entering a modifying command, including which files, processes, accounts, or connections may be affected.

Make one narrow change and stop. If the output reports an error or an unexpected target, preserve that evidence and return to inspection instead of adding unrelated commands.

Repeat the original observation after the action. A successful command status is useful, but the real completion signal is the intended state plus the absence of an unintended side effect.

Complete the Evidence Loop

A good terminal record answers four questions: what was observed, why one action was selected, exactly what changed, and how the result was verified. A screenshot without command context answers fewer questions than saved text output.

Test both the expected success and one safe failure condition. This confirms that the procedure recognizes a wrong path, missing permission, invalid input, stopped service, or unavailable endpoint instead of silently continuing.

Finish by restoring the lab baseline when the task was experimental. For an operational change, record the final state and the reversal step so later work begins from a known boundary.

Recap Before Practice and Prove

The first decision concerns prompt and command. Read the prompt context, type one command, and inspect its output before entering the next command.

The second decision concerns working directory. Run `pwd`, compare the printed path with your intended location, and correct the location before changing files.

The third decision concerns directory movement. Move with `cd <path>`, then use `pwd` so the new location is confirmed rather than assumed.

The fourth decision concerns path forms. Choose an absolute path when location must be unambiguous and a relative path when the current context is intentional.

The final decision concerns directory listing. Start with `ls`, add `-a` for hidden entries, and add `-l` when permissions and ownership matter. Keep the final output as the baseline for the next task.

Navigate the Linux Command Line