Run diff data/config-a.conf data/config-b.conf.
diff data/config-a.conf data/config-b.conf
Mission 350
Script change review
Compare configuration snapshots and record a review marker.
Shell scriptingdiffgreptee
Lesson 350 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 listen data/config-b.conf.
grep listen data/config-b.conf
Run printf script-change-reviewed | tee lab/script-change.txt.
printf script-change-reviewed | tee lab/script-change.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 reviewing change evidence before script-driven deployment.
Start with diff data/config-a.conf data/config-b.conf, inspect the result, then continue in order.
Reviewing change evidence before script-driven deployment helps operators explain what they know before they change anything.
- Skipping the output that proves reviewing change evidence before script-driven deployment.
- Changing several things before recording a baseline.
Reference
Commands in this lesson.
grep [-i] <text> <file>
Find literal text inside a file.
tee <file>
Write piped text to a lab file and keep it on screen.
diff <left> <right>
Compare two lab text files.