Files and paths · Lesson 1 of 36 · 10 minutes

Files

Create folders and files, then copy, move, and remove lab files carefully.

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 lab folder
Run mkdir -p lab to create a training folder.
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
```
Remember: Creating a folder does not change the current directory.
2
Create a note
Run touch lab/note.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/note.txt
```
Remember: touch is not a way to empty a file that already has content.
3
Copy the note
Run cp lab/note.txt lab/note-copy.txt.
Hint & worked example
Copy a file to a new location, leaving the original in place.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
cp lab/note.txt lab/note-copy.txt
```
Remember: Confirm the destination before replacing a file. This lab supports file copies, not every cp option.

Understand the pattern

Most terminal work is careful path and file manipulation.

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.
cp: Copy a file to a new location, leaving the original in place.
Confirm the destination before replacing a file. This lab supports file copies, not every cp option.

Worked example and expected result

$ mkdir -p lab

(no output; exit 0)

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

$ touch lab/note.txt

(no output; exit 0)

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

$ cp lab/note.txt lab/note-copy.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 “Files”, 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 “Files” 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: Copy and move 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