Linux Files and Permissions for Makers
Learn paths, owners, groups, modes, and parent directory traversal before changing chmod or chown.
Ladder steps
Each step should prove one idea before the project asks for the next one.
Examples to inspect
Use examples to read signals, not as blind recipes.
Walk path permissions
namei -l /srv/www/site/current/index.html
Expected signal: Each directory and file shows mode, owner, and group
Check owner and mode
stat -c '%A %U:%G %n' index.html
Expected signal: A compact permission and owner line
Check service process user
ps -o user,comm -C nginx
Expected signal: The account running nginx workers
Common traps
- Using chmod -R 777.
- Changing ownership without knowing the service user.
- Fixing the file while the parent directory still blocks traversal.
Practice task
Build a test directory where only the parent execute bit is wrong. Use namei -l to identify the break.
Next steps
- Use LinuxOneLiners permission-denied repair path.
- Learn Nginx static root checks.
- Practice service-user debugging.
Practice ladder
- Near-Copy Rebuild: Recreate one example, decision path, or worked explanation from Linux Files and Permissions for Makers. Keep most givens the same, then apply, explain, and check while naming each cue you used. Use the lesson's example block when it helps.
- One-Change Transfer: Change exactly one condition, number, input, symptom, material, or constraint from the near-copy case. Then apply, explain, and check again and explain what changed.
- Mixed Review Set: Interleave this topic with one prerequisite or adjacent idea. Write three short prompts: one recall, one application, and one comparison.
- Find And Fix The Error: Invent a plausible wrong answer, unsafe step, invalid assumption, or bad classification. Mark the first point where it goes wrong, then correct it using the lesson's check.
Flashcard preview
What does namei -l prove?
It walks each path component and shows whether a parent directory blocks traversal.
What does the 'Read the whole path' step prove?
A failure can come from any parent directory, not just the final file. Check: namei -l shows every component.
What does the 'Check owner and group' step prove?
The file owner and group determine which permission bits apply. Check: stat shows owner, group, mode, and name.
What does the 'Match the service user' step prove?
A web server or service may not run as your login user. Check: systemctl show -p User can reveal service user config.
What does the 'Avoid recursive fixes' step prove?
Recursive chmod or chown can damage unrelated files. Check: Change only the proven broken component.
When would you use `namei -l /srv/www/site/current/index.html`?
Use it to walk path permissions. Expected signal: Each directory and file shows mode, owner, and group
Downloadable study pack
Export the same ladder as a plain Markdown note or Anki-compatible TSV. Commands and code blocks stay plain so they work in local notes.
Related paths
Study pack check passed. Notes, cards, examples, and practice tasks are meant to keep the ladder useful outside the page.
Continue learning this topic
Use this page as part of a project path, not as a one-off article. Save the note, review the cards, try the practice task, then choose the next ladder based on what your project exposes.
Study assets
Project context
- Deploy a Static Site on a VPS
- Browse Software and Linux
- Next ladder clue: Use LinuxOneLiners permission-denied repair path.
Related references
Buy me a coffee for more maker ladders
TopicLadder is free to read. Support helps turn rough project paths into useful notes, cards, videos, and practice tasks.