Files and paths · Lesson 6 of 36 · 8 minutes

Symbolic links

Create and inspect a simulated symbolic link.

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 lab
Run mkdir -p lab.
Hint & worked example
Create a directory. -p also creates missing parent directories and accepts an existing directory.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
mkdir -p lab
```
Remember: Creating a folder does not change the current directory.
2
Create link
Run ln -s /home/learner/README.txt lab/readme-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-link
```
Remember: A relative symlink target is interpreted from the link directory.
3
Inspect link
Run stat lab/readme-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/readme-link
```
Remember: Metadata and file contents answer different questions.

Understand the pattern

Symlinks appear often in Unix configuration and deployment layouts.

mkdir: Create a directory. -p also creates missing parent directories and accepts an existing directory.
Creating a folder does not change the current directory.
ln: Create a symbolic link in the lab with ln -s.
A relative symlink target is interpreted from the link directory.
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

$ mkdir -p lab

(no output; exit 0)

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

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

(no output; exit 0)

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

$ stat lab/readme-link

Path: /home/learner/lab/readme-link
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 “Symbolic links”, 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 relative symlink target is interpreted from the link directory.

Apply it elsewhere

Before adapting the ln workflow from “Symbolic links” 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 basics 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