Files and paths · Lesson 12 of 36 · 7 minutes

Path normalization

Use dot and dot-dot safely without leaving the simulated filesystem.

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
Stat dot path
Run stat ./README.txt.
Hint & worked example
Inspect a file or directory metadata record, including ownership, permissions, and size.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
stat ./README.txt
```
Remember: Metadata and file contents answer different questions.
2
Stat dot-dot path
Run stat notes/../README.txt.
Hint & worked example
Inspect a file or directory metadata record, including ownership, permissions, and size.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
stat notes/../README.txt
```
Remember: Metadata and file contents answer different questions.
3
Enter notes
Run cd notes.
Hint & worked example
Change the shell working directory; .. selects the parent and ~ identifies your home.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
cd notes
```
Remember: Changing directories changes how later relative paths resolve.

Understand the pattern

Path normalization helps spot traversal mistakes.

stat: Inspect a file or directory metadata record, including ownership, permissions, and size.
Metadata and file contents answer different questions.
cd: Change the shell working directory; .. selects the parent and ~ identifies your home.
Changing directories changes how later relative paths resolve.

Worked example and expected result

$ stat ./README.txt

Path: /home/learner/README.txt
Type: file
Mode: -rw-r--r--
Owner: learner
Group: learners
Size: 148 bytes

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

$ stat notes/../README.txt

Path: /home/learner/README.txt
Type: file
Mode: -rw-r--r--
Owner: learner
Group: learners
Size: 148 bytes

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

$ cd notes

(no output; exit 0)

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 “Path normalization”, which interpretation is safe?A successful first check guarantees that every dependent service is healthy.Metadata and file contents answer different questions.A command appearing in history proves it completed successfully.

Apply it elsewhere

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

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Script metadata 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