A project for CSCS1730 UNIX/Linux Fundamentals by Dominic Spaccio during the spring of 2014.

This project was begun on 6FEB14 and is anticipated to take several days of on and off dedication.

To unravel the mysterious puzzle box. The purpose is to get a better understanding of how someone can intentionally or unintentionally confuse an operator through simple mishandling of filename extensions. I hope to help other students unravel the puzzle box while learning how to manage their anger.

In order to successfully accomplish/perform this project, the listed resources need to be consulted/achieved:

• read the man page for the command FILE
• read the man page for the command GZIP
• read the man page for the command TAR
• read the man page for the command ZIP
• read the man page for the command UUENCODE
• make available a six-pack (this is a min. req.) of your favorite beer

The intention of this project is to help students master the use of some very simple commands in the UNIX environment.

Upon approval, you'll want to fill this section out with more detailed background information. DO NOT JUST PROVIDE A LINK.

Providing any links to original source material, such as from a project page, is a good idea.

You'll want to give a general overview of what is going to be accomplished (for example, if your project is about installing a web server, do a little write-up on web servers. What is it, why do we need one, how does it work, etc.)

Give a general overview of your anticipated implementation of the project. Address any areas where you are making upfront assumptions or curtailing potential detail. State the focus you will be taking in implementation.

State and justify the attributes you'd like to receive upon successful approval and completion of this project.

• Patience: first and foremost if this doesn't help you acquire some you either have a ton already or you are immune to agitation.
• Desire to drink: when you reach the glorious ending of this puzzle box inside you'll find a coupon. This coupon is good for a variety six-pack of… you guessed it, beer. Good for the first three students who unravel my puzzle box, provided you can show me a proper ID validating you are of age to legally purchase alcohol.

The actual steps taken to accomplish the project. Include images, code snippets, command-line excerpts; whatever is useful for intuitively communicating important information for accomplishing the project.

Upon completion of the project, if there is an applicable collection of created code, place a copy of your finished code within <code> </code> blocks here.

/*
 * hello.c - A sample "Hello, World!" program
 * 
 * written by NAME for COURSE on DATE
 *
 * compile with:
 *   gcc -o hello hello.c
 *
 * execute with:
 *   ./hello
 */
 
#include <stdio.h>
 
int main()
{
    printf("Hello, World!\n");    // Output message to STDOUT
    return(0);
}

Again, if there is associated code with the project, and you haven't already indicated how to run it, provide a sample run of your code:

lab46:~/src/cprog$ ./hello
Hello, World!
lab46:~/src/cprog$ 

Comments/thoughts generated through performing the project, observations made, analysis rendered, conclusions wrought. What did you learn from doing this project?

In performing this project, the following resources were referenced:

• URL1
• URL2
• URL3 (provides useful information on topic)
• URL4

Generally, state where you got informative and useful information to help you accomplish this project when you originally worked on it (from Google, other wiki documents on the Lab46 wiki, etc.)