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]>
36 lines
1.5 KiB
Markdown
36 lines
1.5 KiB
Markdown
# Guided Exercise: Predict Before You Look
|
|
|
|
Before you run the real inspection commands in the Lab, commit to a guess — this is what makes
|
|
the real numbers meaningful instead of just scrolling past them.
|
|
|
|
## Your task
|
|
|
|
On paper or in a scratch file, write down your best GUESS for:
|
|
|
|
1. How many CPU cores does this machine have?
|
|
2. How much total RAM, roughly, in GB?
|
|
3. How much free disk space is on the root filesystem?
|
|
|
|
Then think through: which of these three would you expect a "student Lab" environment to be
|
|
MOST constrained on, and why? (Hint: think about what happens if 50 students are each running
|
|
their own Lab on one shared physical machine at the same time.)
|
|
|
|
## A worked shape to check yourself against
|
|
|
|
There's no single right numeric answer here — the point is the habit of predicting first. A
|
|
reasonable answer to the "most constrained" question: memory and CPU are typically the tightest
|
|
shared resource on a multi-tenant host, since every additional Lab needs its own slice of both,
|
|
while disk is comparatively cheap to over-provision.
|
|
|
|
## Instructor Notes
|
|
|
|
**Facilitation:** Have students commit to a number verbally or on a shared doc BEFORE anyone
|
|
runs the real commands — the value is in noticing the gap between guess and reality, not in
|
|
getting it right.
|
|
|
|
**Approximate timing:** 5 minutes.
|
|
|
|
**Optional extension:** ask what would happen to their guess if this were a "real" laptop
|
|
they personally own vs. a shared cloud server — good primer for later resource-limit
|
|
discussions (ROOT 06's resource requests/limits, ROOT 09's resource governance).
|