Repairing a Download Pack is a practical Bash project for learners who know basic scripting. Help an event organizer recover missing or damaged resources while keeping correct files and personal notes intact. Your result is a usable local PDF and text pack, plus scripts you can run again with another supported pack.
Two Guided Labs first build an inventory from an independently trusted SHA256 manifest, then turn those findings into selective HTTP repairs. One independent Challenge changes the collection and the damaged or missing members. Each lab has its own prepared files and local source; no earlier lab's files are required.
What You Will Learn
After completing this course, you will be able to:
- classify every required member as matching, missing or mismatched by comparing its actual bytes with an independent reference;
- preserve filenames containing spaces and recognize a valid empty resource;
- download only the members that need repair using curl and correctly encoded request parameters;
- verify each temporary candidate before replacing its destination and clean only your own temporary files;
- preserve correct files and unrelated notes, including their bytes, mode, owner and modification time;
- repeat a completed repair without making download requests, then open and download the real local PDF and text resources.
Who This Course Is For
This course is for Bash learners who want to automate a useful file-recovery decision rather than download every file again.
Prerequisites: Complete Shell for Beginners or have equivalent experience with terminal paths, script arguments, conditions and loops. The Guided Labs explain SHA256, filename parsing, command exit statuses, curl, temporary candidates and the cleanup trap used here. Neither PowerShell nor the audio-preview project is required.
Learning environment: LabEx provides Linux in your browser with the required tools, original synthetic resources, the Workspace terminal and the Download Desk page. The source is a controlled local HTTP service. No external account or local software installation is needed. Interface labels and command output remain in English.
Frequently Asked Questions
Does a matching checksum prove who published a file?
No. You compare bytes with a manifest supplied independently and assumed trusted. The digest detects disagreement with that reference; it does not authenticate a publisher. Do not rebuild the reference from damaged files.
What happens if a download fails?
HTTP rejection, interrupted transfers and an incorrect body returned with HTTP 200 must not replace a destination. Publication is per file: an earlier verified repair may remain when a later member fails. This is not a whole-pack transaction or crash-recovery guarantee.
Will a second run download correct files again?
No. Matching files, including a legitimate empty member, are kept. A complete second run makes zero download requests and preserves the pack and personal notes.
