Networking · Lesson 21 of 26 · 8 minutes

SCP transfer plan

Plan a copy command without opening a network connection.

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
Dry-run copy
Run scp README.txt lab:/tmp/README.txt.
Hint & worked example
Practice a fixed simulated copy workflow without network transfer.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
scp README.txt lab:/tmp/README.txt
```
Remember: Direction, destination, and host identity matter before copying real files.
2
Read source
Run cat README.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 README.txt
```
Remember: Reading a source file should precede changing it; avoid printing real secrets.
3
Hash source
Run sha256sum README.txt.
Hint & worked example
Compare content digests to detect byte changes, not to establish who authored the file.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
sha256sum README.txt
```
Remember: A checksum detects changes only relative to a trusted expected digest.

Understand the pattern

Junior operators build confidence by gathering evidence before changing systems.

scp: Practice a fixed simulated copy workflow without network transfer.
Direction, destination, and host identity matter before copying real files.
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.
sha256sum: Compare content digests to detect byte changes, not to establish who authored the file.
A checksum detects changes only relative to a trusted expected digest.

Worked example and expected result

$ scp README.txt lab:/tmp/README.txt

dry-run only: would copy README.txt to lab:/tmp/README.txt; no network connection was made.

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

$ cat README.txt

Welcome to Clairos Learn. This is a simulated filesystem for practicing terminal and server basics. Nothing here is connected to your real computer.

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

$ sha256sum README.txt

a76968d5df26cfd59ecd7d080f8283d65e91ec7366d233b4b98233877aa154c6  /home/learner/README.txt

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 “SCP transfer plan”, which interpretation is safe?A successful first check guarantees that every dependent service is healthy.Reading a source file should precede changing it; avoid printing real secrets.A command appearing in history proves it completed successfully.

Apply it elsewhere

Before adapting the cat workflow from “SCP transfer plan” 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: Interface evidence capture 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