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.3 KiB
Knowledge Check: Users and Permissions Foundations
1. A colleague says "permission denied" and fixes it with chmod 777. What's wrong with
that fix?
Answer: 777 grants read, write, AND execute to the owner, group, AND everyone else — almost
always far more access than the actual problem required. It "fixes" the symptom while violating
least privilege, usually granting write access nobody asked for.
2. What does the permission 644 actually mean, broken down?
Answer: Owner: read+write (4+2=6). Group: read-only (4). Other: read-only (4). Nobody but the owner can modify the file; everyone can read it.
3. Why does sudo <command> exist instead of just logging in as root permanently?
Answer: It grants elevated privilege only for the one command that needs it, minimizing the time spent with full access — reducing the chance a mistake (or a compromised session) causes serious, wide damage.
4. State the least-privilege principle in your own words.
Answer: Grant exactly the access something needs to do its job, and nothing more.
Instructor Notes
Facilitation: Question 1 is worth discussing as a group — most students have seen chmod 777 somewhere online as "the fix," and unlearning that habit early matters.
Approximate timing: 5 minutes.