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]>
40 lines
1.5 KiB
Markdown
40 lines
1.5 KiB
Markdown
# Guided Exercise: Plan a Directory Structure on Paper First
|
|
|
|
Before you build anything in the Lab, plan it — this is the same discipline you'll use later
|
|
when planning a Kubernetes namespace layout or a Git repository structure.
|
|
|
|
## Your task
|
|
|
|
You're setting up a small project called `weather-app`. On paper, sketch a directory tree
|
|
containing:
|
|
|
|
- A place for source code
|
|
- A place for documentation
|
|
- A place for tests
|
|
- A single hidden configuration file at the project's root
|
|
|
|
Write out the exact `mkdir` and file-creation commands you'd use, including whether each path
|
|
you write is absolute or relative.
|
|
|
|
## A worked shape to check yourself against
|
|
|
|
```
|
|
mkdir -p weather-app/src weather-app/docs weather-app/tests
|
|
echo "ready" > weather-app/.config
|
|
```
|
|
|
|
(Or with an absolute path: `mkdir -p /srv/weather-app/src ...`.) The `-p` flag matters here —
|
|
without it, `mkdir` refuses to create `weather-app/src` if `weather-app` doesn't already exist.
|
|
|
|
## Instructor Notes
|
|
|
|
**Facilitation:** Have students commit to their command in writing before revealing the worked
|
|
answer — the value is in noticing what `-p` actually buys them, not just copying a correct
|
|
command.
|
|
|
|
**Approximate timing:** 8-10 minutes live discussion; 5 minutes self-paced.
|
|
|
|
**Common mistake to watch for:** forgetting `mkdir -p` and getting a "No such file or
|
|
directory" error when creating a nested path in one command — a good moment to connect back to
|
|
Module 2's exit-code lesson (that error IS a non-zero exit code).
|