A project for Unix by Jason Mendoza in 2ought13 this project was begun on 4/7/2013 and is anticipated to take about a week….tops.

The purpose of this project is to open my mind like a flower in the morning and get through the hard outer candy shell of unix based systems and experience the creamy center and hopefully pull myself out of the screaming baby level of Linux knowledge

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

• resource1
• resource2
• resource3
• experience1
• experience2
• etc.

State the idea or purpose of the project. What are you attempting to pursue?

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.

• attribute1: why you feel your pursuit of this project will gain you this attribute
• attribute2: why you feel your pursuit of this project will gain you this attribute
• etc…

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);
}

PATH=/home/jmendoza/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games:/us

MAIL=/home/jmendoza/Maildir

SHELL=/bin/bash

TERM=xterm

USER=jmendoza

such as it is, the current alias for ls is 'ls –color=auto'

I beleive the variable is the when things are colorized.

The man page states that you can set things to be colorized always, auto or never

NOOO unaliased ls took away all of my glorious colors from the ls-mo-tron!! WHY JEEBUS!?!! WHY!

EOF
lab46:~$ echo $var1

lab46:~$ var1="UNIX SHELL"
lab46:~$ echo $var1
UNIX SHELL
lab46:~$ 

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.)