Terminal basics · Lesson 17 of 34 · 8 minutes

Link targets

Create and inspect a symbolic link target.

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 link
Run ln -s /home/learner/README.txt lab/readme-target.
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-target
```
Remember: A relative symlink target is interpreted from the link directory.
2
Read link target
Run readlink lab/readme-target.
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-target
```
Remember: A symlink contains a target path, not another copy of the target file.
3
Inspect link metadata
Run stat lab/readme-target.
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/readme-target
```
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 /home/learner/README.txt lab/readme-target

(no output; exit 0)

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

$ readlink lab/readme-target

/home/learner/README.txt

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

$ stat lab/readme-target

Path: /home/learner/lab/readme-target
Type: link
Mode: lrwxrwxrwx
Owner: learner
Group: learners
Size: 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 “Link targets”, 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 “Link targets” 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: Existence checks 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