Permissions and users · Lesson 17 of 33 · 8 minutes

Script private mode

Set strict metadata on a script draft.

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
Create script
Run touch lab/private-script.sh.
Hint & worked example
Create an empty file when absent, or update timestamps without truncating an existing file.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
touch lab/private-script.sh
```
Remember: touch is not a way to empty a file that already has content.
2
Set private executable
Run chmod 700 lab/private-script.sh.
Hint & worked example
Change permissions using an octal mode or a symbolic adjustment. Each rwx bit belongs to owner, group, or other.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
chmod 700 lab/private-script.sh
```
Remember: Do not use 777 as a blanket fix. Grant the smallest access needed.
3
Inspect script
Run stat lab/private-script.sh.
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 lab/private-script.sh
```
Remember: Metadata and file contents answer different questions.

Understand the pattern

Junior operators build confidence by gathering evidence before changing systems.

touch: Create an empty file when absent, or update timestamps without truncating an existing file.
touch is not a way to empty a file that already has content.
chmod: Change permissions using an octal mode or a symbolic adjustment. Each rwx bit belongs to owner, group, or other.
Do not use 777 as a blanket fix. Grant the smallest access needed.
stat: Inspect a file or directory metadata record, including ownership, permissions, and size.
Metadata and file contents answer different questions.

Worked example and expected result

$ touch lab/private-script.sh

(no output; exit 0)

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

$ chmod 700 lab/private-script.sh

(no output; exit 0)

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

$ stat lab/private-script.sh

Path: /home/learner/lab/private-script.sh
Type: file
Mode: -rwx------
Owner: learner
Group: learners
Size: 0 bytes

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 “Script private mode”, which interpretation is safe?Do not use 777 as a blanket fix. Grant the smallest access needed.A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.

Apply it elsewhere

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

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Ownership audit 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