Run file README.txt.
file README.txt
Mission 311
File type inspection
Identify files, directories, links, and text before acting on them.
Files and pathsfilestat
Lesson 311 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 file lab.
file lab
Run stat README.txt.
stat README.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 identifying filesystem object types.
Start with file README.txt, inspect the result, then continue in order.
Identifying filesystem object types helps operators explain what they know before they change anything.
- Skipping the output that proves identifying filesystem object types.
- Changing several things before recording a baseline.
Reference
Commands in this lesson.
file <path>
Identify a simulated file, directory, link, or text format.
stat <path>
Show lab file details.