Permissions and users · Lesson 24 of 33 · 8 minutes

Shared directory risk

Inspect shared directories before trusting their contents.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

learner@clairos:~ $

↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Inspect shared temp
Run stat /tmp.
Hint & worked example
Inspect a file or directory metadata record, including ownership, permissions, and size.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
stat /tmp
```
Remember: Metadata and file contents answer different questions.
2
List shared temp
Run ls -la /tmp.
Hint & worked example
List directory entries; -a includes hidden names and -l adds ownership and permission detail.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
ls -la /tmp
```
Remember: A listing is not proof that you can read or modify every listed file.
3
Verify temp directory
Run test -d /tmp.
Hint & worked example
Evaluate a file or string condition through its exit status rather than printed output.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
test -d /tmp
```
Remember: A successful test usually prints nothing; inspect $? or chain a command.

Understand the pattern

Junior operators build confidence by gathering evidence before changing systems.

stat: Inspect a file or directory metadata record, including ownership, permissions, and size.
Metadata and file contents answer different questions.
ls: List directory entries; -a includes hidden names and -l adds ownership and permission detail.
A listing is not proof that you can read or modify every listed file.
test: Evaluate a file or string condition through its exit status rather than printed output.
A successful test usually prints nothing; inspect $? or chain a command.

Worked example and expected result

$ stat /tmp

Path: /tmp
Type: dir
Mode: drwxrwxrwx
Owner: root
Group: root
Size: 0 items

Exit status: 0. The command completed successfully in the training fixture.

$ ls -la /tmp

(no output; exit 0)

Exit status: 0. The command completed successfully in the training fixture.

$ test -d /tmp

(no output; exit 0)

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Repeat this workflow in the sandbox with a different scratch filename. Keep the system fixtures unchanged and compare the observed output with your expectation before moving on.

Explain it

In “Shared directory risk”, which interpretation is safe?A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.A listing is not proof that you can read or modify every listed file.

Apply it elsewhere

Before adapting the ls workflow from “Shared directory risk” to another server, what should you do?Skip output inspection whenever the command is familiar.Confirm the current directory, target identity, permissions, and the installed command behavior first.Paste the training paths unchanged into production.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Sudoers readonly review Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

GNU Coreutils manual · GNU Bash manual