Files and paths · Lesson 35 of 36 · 8 minutes

Archive manifest workflow

Create an archive, list its members, and hash the artifact.

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 small archive
Run tar -cf lab/readme-backup.tar README.txt.
Hint & worked example
Practice archive inventory, creation, and extraction in a simulated archive format.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
tar -cf lab/readme-backup.tar README.txt
```
Remember: These training archives are virtual data structures, not downloadable production tar files.
2
List archive members
Run tar -tf lab/readme-backup.tar.
Hint & worked example
Practice archive inventory, creation, and extraction in a simulated archive format.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
tar -tf lab/readme-backup.tar
```
Remember: These training archives are virtual data structures, not downloadable production tar files.
3
Hash the archive
Run sha256sum lab/readme-backup.tar.
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 lab/readme-backup.tar
```
Remember: A checksum detects changes only relative to a trusted expected digest.

Understand the pattern

Verifying archive membership before trusting a backup helps operators explain what they know before they change anything.

tar: Practice archive inventory, creation, and extraction in a simulated archive format.
These training archives are virtual data structures, not downloadable production tar files.
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

$ tar -cf lab/readme-backup.tar README.txt

created archive /home/learner/lab/readme-backup.tar

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

$ tar -tf lab/readme-backup.tar

README.txt

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

$ sha256sum lab/readme-backup.tar

1249d1cbe1d47795e8f30e5ae5c1e694d0ec772b50a0ed9d0f4a3b5ee451f8ab  /home/learner/lab/readme-backup.tar

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 “Archive manifest workflow”, which interpretation is safe?These training archives are virtual data structures, not downloadable production tar files.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 tar workflow from “Archive manifest workflow” 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: Files and paths bridge 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