Files and paths · Lesson 34 of 36 · 8 minutes

Symlink chain audit

Create a link, inspect its stored target, and resolve the final path.

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
Create the audit link
Run ln -s /home/learner/README.txt lab/readme-audit-link.
Hint & worked example
Create a symbolic link in the lab with ln -s.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
ln -s /home/learner/README.txt lab/readme-audit-link
```
Remember: A relative symlink target is interpreted from the link directory.
2
Read the stored target
Run readlink lab/readme-audit-link.
Hint & worked example
Inspect a symbolic-link target; use resolution options deliberately.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
readlink lab/readme-audit-link
```
Remember: A symlink contains a target path, not another copy of the target file.
3
Resolve the final path
Run realpath lab/readme-audit-link.
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/readme-audit-link
```
Remember: Resolving a path and reading its contents are separate operations.

Understand the pattern

Auditing symbolic-link targets helps operators explain what they know before they change anything.

ln: Create a symbolic link in the lab with ln -s.
A relative symlink target is interpreted from the link directory.
readlink: Inspect a symbolic-link target; use resolution options deliberately.
A symlink contains a target path, not another copy of the target file.
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

$ ln -s /home/learner/README.txt lab/readme-audit-link

(no output; exit 0)

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

$ readlink lab/readme-audit-link

/home/learner/README.txt

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

$ realpath lab/readme-audit-link

/home/learner/README.txt

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 “Symlink chain audit”, which interpretation is safe?A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.A symlink contains a target path, not another copy of the target file.

Apply it elsewhere

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

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Archive manifest workflow 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