Files and paths · Lesson 26 of 36 · 8 minutes

Symlink inventory

Create, read, and inspect links before relying on them.

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 site link
Run ln -s /srv/www/index.html lab/site-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 /srv/www/index.html lab/site-link
```
Remember: A relative symlink target is interpreted from the link directory.
2
Read target
Run readlink lab/site-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/site-link
```
Remember: A symlink contains a target path, not another copy of the target file.
3
Inspect link
Run stat lab/site-link.
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 lab/site-link
```
Remember: Metadata and file contents answer different questions.

Understand the pattern

Junior operators build confidence by gathering evidence before changing systems.

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.
stat: Inspect a file or directory metadata record, including ownership, permissions, and size.
Metadata and file contents answer different questions.

Worked example and expected result

$ ln -s /srv/www/index.html lab/site-link

(no output; exit 0)

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

$ readlink lab/site-link

/srv/www/index.html

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

$ stat lab/site-link

Path: /home/learner/lab/site-link
Type: link
Mode: lrwxrwxrwx
Owner: learner
Group: learners
Size: link -> /srv/www/index.html

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

Apply it elsewhere

Before adapting the readlink workflow from “Symlink inventory” 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: Glob safety preview 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