Run printf status=ready | tee lab/status.env.
printf status=ready | tee lab/status.env
Mission 348
Predictable output contract
Create machine-readable status lines and verify their shape.
Shell scriptingprintfteegrep
Lesson 348 of 360
0/360 lessons
0/17 missions
Shell scripting · 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 grep status lab/status.env.
grep status lab/status.env
Run cat lab/status.env.
cat lab/status.env
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 producing predictable script-style status output.
Start with printf status=ready | tee lab/status.env, inspect the result, then continue in order.
Producing predictable script-style status output helps operators explain what they know before they change anything.
- Skipping the output that proves producing predictable script-style status output.
- Changing several things before recording a baseline.
Reference
Commands in this lesson.
printf <text>
Print formatted training text.
grep [-i] <text> <file>
Find literal text inside a file.
tee <file>
Write piped text to a lab file and keep it on screen.