Files and paths · Lesson 10 of 36 · 8 minutes

Rename workflow

Create a report draft and rename it 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 reports
Run mkdir -p lab/reports.
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/reports
```
Remember: Creating a folder does not change the current directory.
2
Create draft
Run touch lab/reports/draft.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/reports/draft.txt
```
Remember: touch is not a way to empty a file that already has content.
3
Rename final
Run mv lab/reports/draft.txt lab/reports/final.txt.
Hint & worked example
Move or rename a file; the old path no longer names it afterward.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
mv lab/reports/draft.txt lab/reports/final.txt
```
Remember: A successful move should be verified at both the destination and the old path.

Understand the pattern

Admin notes and generated reports often need organized paths.

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.
mv: Move or rename a file; the old path no longer names it afterward.
A successful move should be verified at both the destination and the old path.

Worked example and expected result

$ mkdir -p lab/reports

(no output; exit 0)

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

$ touch lab/reports/draft.txt

(no output; exit 0)

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

$ mv lab/reports/draft.txt lab/reports/final.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 “Rename workflow”, which interpretation is safe?A successful first check guarantees that every dependent service is healthy.touch is not a way to empty a file that already has content.A command appearing in history proves it completed successfully.

Apply it elsewhere

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

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Wildcard safety 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