Files and paths · Lesson 31 of 36 · 8 minutes

Temporary workspaces

Create bounded temporary files and directories for disposable work.

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 a temporary file
Run mktemp lab/note.XXXXXX.
Hint & worked example
Create a uniquely named scratch location in the virtual filesystem.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
mktemp lab/note.XXXXXX
```
Remember: Do not guess a temporary filename when isolation matters.
2
Create a temporary directory
Run mktemp -d lab/work.XXXXXX.
Hint & worked example
Create a uniquely named scratch location in the virtual filesystem.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
mktemp -d lab/work.XXXXXX
```
Remember: Do not guess a temporary filename when isolation matters.
3
Inspect the temporary paths
Run ls -la lab.
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 lab
```
Remember: A listing is not proof that you can read or modify every listed file.

Understand the pattern

Using temporary paths instead of cluttering durable locations helps operators explain what they know before they change anything.

mktemp: Create a uniquely named scratch location in the virtual filesystem.
Do not guess a temporary filename when isolation matters.
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.

Worked example and expected result

$ mktemp lab/note.XXXXXX

/home/learner/lab/note.000001

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

$ mktemp -d lab/work.XXXXXX

/home/learner/lab/work.000001

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

$ ls -la lab

--rw------- learner learners     0 note.000001
ddrwxr-xr-x learner learners   dir work.000001

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 “Temporary workspaces”, which interpretation is safe?Do not guess a temporary filename when isolation matters.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 mktemp workflow from “Temporary workspaces” 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: Sorted inventory comparison 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