Run mkdir lab.
mkdir lab
Lesson 37 of 360
0/360 lessons
0/17 missions
Files and paths · 8 minutes
New learnerrank
0XP
0%complete
learner@clairos:/home/learner $
Unix ops lab: type a command, press Enter
Instructions
8 minutes
Click any instruction for the command details, the why, and the common mistake to avoid.
Run ln -s /home/learner/README.txt lab/readme-link.
ln -s /home/learner/README.txt lab/readme-link
Run stat lab/readme-link.
stat lab/readme-link
Save progress
Keep learning across sessions.
Create a free account to sync completed lessons, XP, streaks, course status, and your next lesson across sessions.
Checking account status...
Progress sync is idle.
0XP
New learnerrank
0day streak
0best streak
0daily streak
0lessons
0courses
0missions
0tasks
Noverified
Progress sync stores completion IDs, scores, streaks, badges, and game settings. Terminal contents, editor snippets, lab scratch, email, and real names are never published on leaderboards or share cards.
Lesson support
What to notice while you play.
Recognize symlink behavior in a safe setting.
Create a lab folder before making the link.
Symlinks appear often in Unix configuration and deployment layouts.
- Assuming a symlink is a full copy.
- Forgetting that link targets can break.
Reference
Commands in this lesson.
mkdir <name>
Create a folder.
ln -s <target> <link>
Create a simulated symbolic link.
stat <path>
Show lab file details.