User Tools

Site Tools


haas:spring2017:unix:projects:pbx0

Differences

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

Link to this comparison view

Next revision
Previous revision
haas:spring2017:unix:projects:pbx0 [2016/09/09 17:50] – external edit 127.0.0.1haas:spring2017:unix:projects:pbx0 [2017/02/12 17:44] (current) – [Submission] wedge
Line 54: Line 54:
 Refer to the **file**(**1**) manual page or your references for more information. Refer to the **file**(**1**) manual page or your references for more information.
  
-=====Practice=====+=====Project=====
 For this project, files are located in the **pbx0/** subdirectory of the UNIX Public Directory. For this project, files are located in the **pbx0/** subdirectory of the UNIX Public Directory.
  
-^    ^|Do the followingand discuss the results in your Journal:| +There is a directory by the name of your userwhich contains a file. Please copy this into some custom project folder in your home directory.
-| ^  a.|Copy **file.txt** into your home directory.+
-|:::^  b.|Using **file**(**1**), what type of file does this appear to be?| +
-|:::^  c.|View the contents of this file using **cat**(**1**). Is it what it appears to be?| +
-|:::^  d.|Using **gzip**(**1**), compress this file with default compression. What does **file**(**1**) say?| +
-|:::^  e.|Uncompress the file, and recompress using arguments for fastest (not highest) compression. What does **file**(**1**) report now?|+
  
-As in many puzzlesone's visual comprehension of the scenario plays a vital role. Where something doesn't necessarily meet the eyeor is not behaving as you would expect- just try reading any messages or output. Sometimes the clues are right under your nose.+Using your debuggingobservationand analytical skills, unravel the puzzle until you have an ordered, plain text, english readable file (called **results**) with directions on how to submit the project.
  
-=====Procedure=====+In many puzzles, one's visual comprehension of the scenario plays a vital role. Where something doesn't necessarily meet the eye, or is not behaving as you would expect- just try reading any messages or output. Sometimes the clues are right under your nose.
  
-Try your hand at the following activitywhere things are not necessarily as they should be:+As is the case many investigationsjust observing how things behave can lead to recognition of an object's true state, or the recognition of a pattern, which can be used to solve the task at hand.
  
-  Locate the file **riddle.html** and copy it into your home directory.+=====Verification===== 
 +The **results** file, when correctly unscrambled and assembled, can be verified by generating its **md5sum** hash.
  
-Being a file that ends in **.html**, and knowing that HTML is typically a plain ASCII text format, you might try opening it in a text editor (or simply using the **cat**(**1**)) utility.+This hash should match the hash stored inside the **MANIFEST** file located in the project directory (in the public directory). 
 +=====Submission===== 
 +In addition to the files produced during the completion of this projectI would also like for you to create detailed step-by-step text file called **pbx0steps** which includes the valid command-lines that will document for me the steps you took from project commencement through completion. You will submit this file at the end in accordance with the instructions.
  
-Does it appear to be text readable file?+To successfully complete this project, you must follow the directions located in a readable file at the conclusion of this project. Until you encounter it, you are not yet finished (hint).
  
-  * Use the **file**(**1**utility to determine the actual file type. +You should get some sort of confirmation indicating successful submission (actually, twoif all went according to planIf notcheck for typos and or locational mismatches.
-  * Based on the output of filereact as appropriate to unravel this puzzle in order to find some plain text directions that will instruct you how to finish this project.+
  
-As is the case many investigations, just observing how things behave can lead to recognition of an object's true state, or the recognition of a pattern, which can be used to solve the task at hand.+I'll be looking for the following:
  
-=====Submission===== +<code> 
-To successfully complete this project, you must follow the directions located in a readable file at the conclusion of this project. Until you encounter it, you are not yet finished (hint). +52:pbx0:final tally of results (52/52
- +*:pbx0:submitted results file via submit tool [7/7] 
-You should get some sort of confirmation indicating successful submission (actually, two) if all went according to plan. If not, check for typos and or locational mismatches.+*:pbx0:submitted pbx0steps file via submit tool [8/8] 
 +*:pbx0:results md5sum matches project MANIFEST [5/5] 
 +*:pbx0:results is correctly unscrambled and assembled [5/5] 
 +*:pbx0:pbx0steps contains valid list of instructions [12/12] 
 +*:pbx0:pbx0steps any extra information after hash mark [5/5] 
 +*:pbx0:emailed results via instructions [5/5] 
 +*:pbx0:matching subject line as per instructions [5/5] 
 +</code>
haas/spring2017/unix/projects/pbx0.1473443433.txt.gz · Last modified: 2017/01/29 21:28 (external edit)