Files and paths · Lesson 15 of 36 · 8 minutes

Scratch workspace

Create a temporary lab area inside home and clean one file safely.

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 scratch
Run mkdir -p lab/scratch.
Hint & worked example
Create a directory. -p also creates missing parent directories and accepts an existing directory.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
mkdir -p lab/scratch
```
Remember: Creating a folder does not change the current directory.
2
Create scratch file
Run touch lab/scratch/temp.txt.
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/scratch/temp.txt
```
Remember: touch is not a way to empty a file that already has content.
3
Remove scratch file
Run rm lab/scratch/temp.txt.
Hint & worked example
Remove the named file from the virtual workspace. The training root and system trees are guarded.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
rm lab/scratch/temp.txt
```
Remember: Simulator protections are not a promise that a real shell will protect the same target.

Understand the pattern

A bounded workspace lowers cleanup risk.

mkdir: Create a directory. -p also creates missing parent directories and accepts an existing directory.
Creating a folder does not change the current directory.
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.
rm: Remove the named file from the virtual workspace. The training root and system trees are guarded.
Simulator protections are not a promise that a real shell will protect the same target.

Worked example and expected result

$ mkdir -p lab/scratch

(no output; exit 0)

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

$ touch lab/scratch/temp.txt

(no output; exit 0)

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

$ rm lab/scratch/temp.txt

(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 “Scratch workspace”, which interpretation is safe?touch is not a way to empty a file that already has content.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 touch workflow from “Scratch workspace” 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: Delimited file fields 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