ced4568andClaude Sonnet 5
e007bcf000
Adds all 6 ROOT 02 modules (Linux system administration, storage & filesystems, the Networking Mental Model, Linux network inspection, DNS & HTTP, Linux troubleshooting) — 37 activities, each with a real lesson, demonstration/guided exercise, knowledge check, hands-on Lab, and reflection. The Networking Mental Model module (M3) gets deliberately extra depth per its "critical module" designation, with no lab by design — conceptual mastery via knowledge check and guided exercise, matching root-05-m00's own precedent. Adds 6 new hands-on Linux/networking scenarios plus 2 MCQs: linux-service-inspection (inspects the platform's own real nginx without touching it — a genuinely safe, real service-inspection target that avoids ever risking the Lab's own connectivity), linux-service-lifecycle (start/ verify/stop a fully controllable service), linux-storage-inspection, linux-network-inspection (ip/ss/getent/curl, each framed as answering one specific diagnostic question), linux-dns-http-diagnosis (a genuine DNS-resolves-but-wrong-port failure, diagnosed and fixed), and linux-troubleshooting-framework (a real missing-config-file failure, resolved via the RootNode Observe/Evidence/Hypothesis/Test/Repair/Validate/Prevent framework). All tested end-to-end via the real scenario-validation API, including negative tests confirming they fail when unsolved. Wires rootnode-linux-networking-assessment (2 required + 4 random-draw scenarios) using the existing Phase 3B assessment engine. Co-Authored-By: Claude Sonnet 5 <[email protected]>
1.3 KiB
Reflection: You Now Have a Repeatable Checklist
Reflection questions
- Before this module, if someone said "check whether the service is healthy," what would you have actually done? How does that compare to the five-question checklist now?
- You started and stopped a service you fully controlled this module. What's different about doing the same thing to a service you DIDN'T start, on a machine you don't fully understand yet?
Real Ops takeaway
The five-question checklist works on ANY unfamiliar Linux system, not just this Lab. Running process, listening port, config location, logs, and current state — this is genuinely how experienced engineers approach a machine they've never touched before. You'll use this exact checklist again in ROOT 04 when a container "doesn't seem to be working," and again in Kubernetes when a Pod isn't behaving as expected — the tools change, the checklist doesn't.
This module is complete. Continue to the next module.
Instructor Notes
Discussion questions for a live classroom: question 2 is worth real discussion time — the honest answer is "you should be more careful and inspect more before acting," a good early seed for the least-privilege/caution habits ROOT 09 formalizes much later.
Approximate timing: 5-8 minutes live discussion; 5 minutes self-paced writing.