Differences

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

--- haas:spring2014:unix:projects:archive_handling [2014/01/20 21:48] – [Procedure] wedge
+++ haas:spring2014:unix:projects:archive_handling [2014/02/04 19:36] (current) – wedge
@@ Line 44: / Line 44: @@
 =====Procedure=====
-COMING SOON
+In the UNIX Public Directory you will find a **projects/archive_handling** subdirectory.
-=====Execution=====
-Several operating behaviors are shown, namely, with and without command-line arguments and 1-, 2-, and 3-digit values.
-<cli>
+There you will find two existing archives:
-lab46:~/src/cprog/multby11$ ./multby11
-Enter value: 345
-x 11 = 3795
-lab46:~/src/cprog/multby11$
-</cli>
-The execution of the program is short and simple- obtain the input, do the processing, produce the output, and then terminate.
+  * archive1.zip
+  * archive2.tar.bz2
+You'll probably want to make a copy of these to some working directory in your home directory.
+Essentially, I want you to do the following:
+  - Figure out the format of each archive, and read up on the available tools for manipulating them
+  - Extract the contents of the two archives and study them (make sure you keep track of what is in which archive)
+  - Analyze the archive contents and find any corrupt or empty files. They are not needed.
+  - Arrange the remaining content by the following criteria:
+    * name the files smallest, small, big, biggest, and tack on the appropriate extension
+    * the smallest file will be whichever file represents the smallest/lightest of the four things (not file size but contextual content of what the file is describing)... similarly as appropriate with small, big, and biggest (the largest/heaviest of the four things)
+  - Create a new archive, called **myarchive.tar** containing only these size-themed files.
+    * do NOT store any paths in the archive, just put the files at base level
+  - Compress **myarchive.tar** on second highest (on the best, not fastest end of the spectrum) compression level in gzip to create the appropriately named **myarchive.tar.gz**
+    * also use the **-n** argument to aid in the verification step below
+  - Submit **myarchive.tar.gz** using the submit tool.
 =====Reflection=====
 Be sure to provide any commentary on your opus regarding realizations had and discoveries made during your pursuit of this project.
-  * Does this process work for four digit numbers?
+  * Why do you suppose tar works the way it does?
-  * How about five digit numbers?
+  * What might be some benefits of separating archival and compression functionality?
-  * Do you see a pattern for now this trick could be extended?
 =====Submission=====
 To successfully complete this project, the following criteria must be met:
-  * Code must compile cleanly (no warnings or errors)
+  * Submit a copy of your archive to me using the **submit** tool.
-  * Executed program must display a total of 1 or 2 lines (depending on presence of argument)
-  * Output must be correct, and match the form given in the sample output above.
-  * Code must be nicely and consistently indented (you may use the **indent** tool)
-  * Code must be commented
-    * have a properly filled-out comment banner at the top
-    * have at least 20% of your program consist of **<nowiki>//</nowiki>**-style descriptive comments
-  * Output Formatting (including spacing) of program must conform to the provided output (see above).
-  * Track/version the source code in a repository
-  * Submit a copy of your source code to me using the **submit** tool.
 To submit this program to me using the **submit** tool, run the following command at your lab46 prompt:

Lab46 Wiki

User Tools

Site Tools

Differences

Page Tools