Files and paths · Lesson 2 of 36 · 8 minutes

Copy and move

Duplicate and rename project files while checking paths before and after.

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
Copy a project file
Run mkdir -p lab, then cp projects/hello.txt lab/hello-copy.txt.
Hint & worked example
Create a directory. -p also creates missing parent directories and accepts an existing directory. 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.
```
mkdir -p lab
cp projects/hello.txt lab/hello-copy.txt
```
Remember: Creating a folder does not change the current directory. Confirm the destination before replacing a file. This lab supports file copies, not every cp option.
2
Rename the copy
Run mv lab/hello-copy.txt lab/renamed.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/hello-copy.txt lab/renamed.txt
```
Remember: A successful move should be verified at both the destination and the old path.
3
Verify the rename
Run cat lab/renamed.txt.
Hint & worked example
Read one or more files to standard output without editing their contents.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
cat lab/renamed.txt
```
Remember: Reading a source file should precede changing it; avoid printing real secrets.

Understand the pattern

Copy and move mistakes are easy to prevent with a quick ls or cat.

mkdir: Create a directory. -p also creates missing parent directories and accepts an existing directory.
Creating a folder does not change the current directory.
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.
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.
cat: Read one or more files to standard output without editing their contents.
Reading a source file should precede changing it; avoid printing real secrets.

Worked example and expected result

$ mkdir -p lab

(no output; exit 0)

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

$ cp projects/hello.txt lab/hello-copy.txt

(no output; exit 0)

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

$ mv lab/hello-copy.txt lab/renamed.txt

(no output; exit 0)

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

$ cat lab/renamed.txt

Hello from a fake project file.

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 “Copy and move”, which interpretation is safe?A successful move should be verified at both the destination and the old path.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 mv workflow from “Copy and move” 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: Safe deletion 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