Corning Community College
CSCS1730 UNIX/Linux Fundamentals
Reference technical documentation to locate and operate particular tools to aid you in accomplishing a task. Collaboratively construct an informative document to detail how one can prepare to start upon this process.
To successfully accomplish/perform this project, the listed resources/experiences need to be consulted/achieved:
As part of this activity is to test your ability to navigate around the filesystem and manipulate files on your own, there is no grabit configured for this project.
You will want to go here to edit and fill in the various sections of the document:
It would be especially useful to review the manual pages or any documentation on the following resources:
On your development system, I want you to do the following:
* Do NOT number your steps. Just place the command-line incantations utilized, one after the other.
One of the tests I will perform for output compliance of your code will involve comparing your program's output against a range of input values, to see if they all output in conformance with project specifications.
I will make use of a checksum to verify exactness.
You will need to run this from your dac0 project directory, where your individual a-h files are located.
You can check your project by typing in the following at the prompt (on lab46):
lab46:~/src/SEMESTER/unix/dac0$ filechk unix dac0
If all aligns, you will see this:
==========unix/dac0 whole file comparison========================================= For the file: a you want: cca000c9cb8a5c134bed61154a7907ba you have: cca000c9cb8a5c134bed61154a7907ba MATCH For the file: b you want: c8136ca761229bad59497021a8f425af you have: c8136ca761229bad59497021a8f425af MATCH For the file: c you want: d6db0da4b084fff4b255ae7a4e95ed62 you have: d6db0da4b084fff4b255ae7a4e95ed62 MATCH For the file: d you want: dadd5272203fa77b80f26cf355e6e833 you have: dadd5272203fa77b80f26cf355e6e833 MATCH For the file: e you want: af095aeaaf55a8a3b351a921baebc9e7 you have: af095aeaaf55a8a3b351a921baebc9e7 MATCH For the file: f you want: 84d0fd81532fac6c743c8054f76f0270 you have: 84d0fd81532fac6c743c8054f76f0270 MATCH For the file: g you want: c36a56a9ab8190e4d007bd16e377639a you have: c36a56a9ab8190e4d007bd16e377639a MATCH For the file: h you want: 226c53b09f112cf7323cd5263302ea95 you have: 226c53b09f112cf7323cd5263302ea95 MATCH
If something is off, your checksum will not match the dac0 checksum, and verification will instead say “MISMATCH”, like follows (note that a mismatched checksum can be anything, and likely not what is seen in this example):
==========unix/dac0 whole file comparison========================================= For the file: a you want: cca000c9cb8a5c134bed61154a7907ba you have: cca000c9cb8a5c134bed61154a7907ba MATCH For the file: b you want: d8136ca761229bad59497021a8f425af you have: c8136ca761229bad59497021a8f425af MISMATCH For the file: c you want: d6db0da4b084fff4b255ae7a4e95ed62 you have: d6db0da4b084fff4b255ae7a4e95ed62 MATCH For the file: d you want: dadd5272203fa77b80f26cf355e6e833 you have: dadd5272203fa77b80f26cf355e6e833 MATCH For the file: e you want: af095aeaaf55a8a3b351a921baebc9e7 you have: af095aeaaf55a8a3b351a921baebc9e7 MATCH For the file: f you want: 84d0fd81532fac6c743c8054f76f0270 you have: 84d0fd81532fac6c743c8054f76f0270 MATCH For the file: g you want: d36a56a9ab8190e4d007bd16e377639a you have: c36a56a9ab8190e4d007bd16e377639a MISMATCH For the file: h you want: 226c53b09f112cf7323cd5263302ea95 you have: 226c53b09f112cf7323cd5263302ea95 MATCH
To be successful in this project, the following criteria (or their equivalent) must be met:
Let's say you have completed work on the project, and are ready to submit, you would do the following:
lab46:~/src/SEMESTER/DESIG/PROJECT$ submit DESIG PROJECT file1 file2 file3 ... fileN
A less abstract instantiation of the above (to help you transition):
lab46:~/src/SEMESTER/unix/dac0$ submit unix dac0 result.tar.gz dac0.steps Submitting unix project "dac0": -> result.tar.gz(OK) -> dac0.steps(OK) SUCCESSFULLY SUBMITTED
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.
I'll be evaluating the project based on the following criteria:
26:dac0:final tally of results (26/26) *:dac0:archive submitted [2/2] *:dac0:archive has correct name of result.tar.gz [2/2] *:dac0:archive is max compressed with gzip [2/2] *:dac0:archive is a tar archive [2/2] *:dac0:archive extracts into current directory [2/2] *:dac0:archive contains 8 english readable files [2/2] *:dac0:archived files are named a-h [2/2] *:dac0:archived files named in order of size [2/2] *:dac0:instructions submitted in text file [2/2] *:dac0:instructions in file named dac0.steps [2/2] *:dac0:dac0.steps contains list of instructions for accomplishing task [2/2] *:dac0:dac0.steps instructions are accurate and correct [2/2] *:dac0:dac0.steps any extra information after hash mark [2/2]