Terminal basics · Lesson 31 of 34 · 8 minutes

Absolute and relative path report

Resolve relative names into full canonical paths.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

learner@clairos:~ $

↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Print the current directory
Run pwd.
Hint & worked example
Print the directory that relative paths currently resolve from.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
pwd
```
Remember: A relative path is interpreted from the working directory, not necessarily the home folder.
2
Resolve a relative file
Run realpath README.txt.
Hint & worked example
Resolve a path to its canonical location in the virtual filesystem.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
realpath README.txt
```
Remember: Resolving a path and reading its contents are separate operations.
3
Resolve a relative directory
Run realpath lab.
Hint & worked example
Resolve a path to its canonical location in the virtual filesystem.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
realpath lab
```
Remember: Resolving a path and reading its contents are separate operations.

Understand the pattern

Relating the current directory to canonical paths helps operators explain what they know before they change anything.

pwd: Print the directory that relative paths currently resolve from.
A relative path is interpreted from the working directory, not necessarily the home folder.
realpath: Resolve a path to its canonical location in the virtual filesystem.
Resolving a path and reading its contents are separate operations.

Worked example and expected result

$ pwd

/home/learner

Exit status: 0. The command completed successfully in the training fixture.

$ realpath README.txt

/home/learner/README.txt

Exit status: 0. The command completed successfully in the training fixture.

$ realpath lab

/home/learner/lab

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Repeat this workflow in the sandbox with a different scratch filename. Keep the system fixtures unchanged and compare the observed output with your expectation before moving on.

Explain it

In “Absolute and relative path report”, which interpretation is safe?Resolving a path and reading its contents are separate operations.A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.

Apply it elsewhere

Before adapting the realpath workflow from “Absolute and relative path report” to another server, what should you do?Paste the training paths unchanged into production.Skip output inspection whenever the command is familiar.Confirm the current directory, target identity, permissions, and the installed command behavior first.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Help before change Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

GNU Coreutils manual · GNU Bash manual