Run whoami.
whoami
Mission 358
Permission regression triage
Establish identity and metadata before applying a narrow repair.
Troubleshootingwhoamitouchchmodstat
Lesson 358 of 360
0/360 lessons
0/17 missions
Troubleshooting · 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 touch lab/permission-regression.txt.
touch lab/permission-regression.txt
Run chmod 640 lab/permission-regression.txt.
chmod 640 lab/permission-regression.txt
Run stat lab/permission-regression.txt.
stat lab/permission-regression.txt
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.
Build repeatable confidence with diagnosing a permission regression from identity and mode evidence.
Start with whoami, inspect the result, then continue in order.
Diagnosing a permission regression from identity and mode evidence helps operators explain what they know before they change anything.
- Skipping the output that proves diagnosing a permission regression from identity and mode evidence.
- Changing several things before recording a baseline.
Reference
Commands in this lesson.
touch <file>
Create an empty file.
chmod <mode> <path>
Change a simulated numeric permission mode.
stat <path>
Show lab file details.
whoami|id|groups
Inspect the learner account.