User Tools

Site Tools


haas:spring2014:unix:projects:archive_handling

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
haas:spring2014:unix:projects:archive_handling [2014/02/04 08:31] – [Procedure] wedgehaas: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. 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> 
- 
-A quick way to check and see if you did everything right is to compute the MD5sum hash of the archive and see if it matches mine: 
- 
-<cli> 
-lab46:~$ md5sum myarchive.tar.gz 
-cc247da7f4d4c4d29e8cc4dda2b03f10  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. 
haas/spring2014/unix/projects/archive_handling.1391502668.txt.gz · Last modified: 2014/02/04 08:31 by wedge