Differences

This shows you the differences between two versions of the page.

--- haas:spring2014:unix:projects:archive_handling [2014/02/04 10:23] – [Check compression] wedge
+++ haas:spring2014:unix:projects:archive_handling [2014/02/04 19:36] (current) – wedge
@@ Line 89: / Line 89: @@
 You should get some sort of confirmation indicating successful submission if all went according to plan. If not, check for typos and or locational mismatches.
-=====Verify=====
-<WRAP info>UPDATE: Turns out I forgot to consider the resulting timestamp of the final archive, so this verification process will **ONLY** work if you add the **-n** argument to **gzip** when you are doing the compression step (note you may be providing gzip with other arguments- you still want those too). With **-n**, timestamps are not included in the gzip header, which is what was causing the different MD5 sums. With this change, individual verification is now possible.</WRAP>
-To determine if you potentially did things correctly, the following steps can be followed:
-====Check compression====
-Did you compress the resulting archive in accordance with project specifications?
-<cli>
-lab46:~$ dd if=myarchive.tar.gz of=header.out bs=1 count=10 2>/dev/null; md5sum header.out; rm -f header.out
-a25a01ac9f94d4e42eeb0cde2e31f  header.out
-</cli>
-Verifying the rest of the archive via checksums is the difficult part, at first due to timestamps being stored, but also because user IDs are recorded in the tar file. This is problematic for a quick one-line approach.
-If you want, you can try using the **--owner=wedge** argument to tar when creating the archive. If that works, then you **MAY** get one of the following:
-<cli>
-lab46:~$ md5sum myarchive.tar.gz
-d0e41e19dc64a9b66a5f3cb44e529b96  myarchive.tar.gz
-lab46:~$
-</cli>
-That is MY md5sum of the archive, in accordance with the project requirements. If your archive's MD5 sum is **identical** to mine, then you can rest assured you did it right.
-It also seems many have interpret the file naming criteria differently than I had intended (for example, on file size vs. conceptual size of what the images contain). If you did this, you will not get the above checksum... you will like get this one:
-<cli>
-lab46:~$ md5sum myarchive.tar.gz
-a1eac6601e20f028ff158651359ec890  myarchive.tar.gz
-lab46:~$
-</cli>
-Ultimately, I will accept either.

Lab46 Wiki

User Tools

Site Tools

Differences

Page Tools