ced4568andClaude Sonnet 5
15b616274b
Adds all 6 ROOT 01 modules (how computers run software, the shell, filesystem navigation, files & text, processes, users & permissions foundations), each with a real lesson, demonstration/guided exercise, knowledge check where warranted, a hands-on Lab, and a reflection — 35 activities, 29 new content files. Adds 6 new hands-on Linux scenarios (linux-inspect-hardware, linux-shell-basics, linux-filesystem-navigation, linux-files-and-text, linux-process-management, linux-permissions-foundations) plus 2 MCQ scenarios, using the existing generic scenario/ validation engine (docs/ROOT_FOUNDATIONS_LAB_STRATEGY.md §1) — every one tested end-to-end via the real scenario setup/validate API, including negative tests confirming they correctly FAIL when not actually solved (e.g. the process-management scenario fails while the target process is still running; the permissions scenario is tested against a real `su - labuser` denial). Wires rootnode-linux-foundations-assessment (2 required + 4 random-draw scenarios) using the existing Phase 3B assessment engine. Adds a real, server-side ROOT 01->02->03->04->05 course prerequisite chain (courses.prerequisites) — verified live on two students: one who completed ROOT 01 sees ROOT 02 unlock; a fresh student sees ROOT 02 correctly locked while 03/04/05 stay vacuously satisfied (their own prerequisite courses are still empty). ROOT 06+ and the Capstone are unaffected. Co-Authored-By: Claude Sonnet 5 <[email protected]>
1.1 KiB
Reflection: Exit Codes Are Everywhere After This
Reflection questions
- Before this module, did you know commands returned a machine-readable success/failure signal at all? What did you assume happened instead?
- Where do you think exit codes might matter later in ROOT_ — in a script, a CI pipeline, or a container?
Real Ops takeaway
Every automated system you'll ever build or operate checks exit codes, not error messages.
A script deciding whether to continue, a CI pipeline deciding whether to deploy, and (much
later) a container orchestrator deciding whether a process is healthy, all reduce to the exact
same question this module taught you to answer by hand: did this exit 0 or not? Getting
comfortable checking $? now means none of those later systems will feel like magic.
This module is complete. Continue to the next module.
Instructor Notes
Discussion questions for a live classroom: question 2 previews Docker/Kubernetes health checks well before students get there — useful to name explicitly without going deep yet.
Approximate timing: 5-8 minutes live discussion; 5 minutes self-paced writing.