======Part 3======

=====Entries=====

====November 3,2011====
Today we learned how to use xcommands which cause images to appear on other peoples screens by connecting to the server their virtual machine was hosted on. This lead to much trolling and spamming of random anims and images.  In addition we were given time to play with these commands and work on other projects.
====November 10th, 2011====
Today we worked on taking the raw HTML for the CCC course listings and used regular expressions to pick out the bits of HTML coding that we didn't want to make it easier to read as well as to clean up the format a bit.The end form of the command we used to do this was around two and a half lines on the whiteboard
====November 22nd,2011====
Today was a play and work on stuff day so we could get stuff done on our OPUS due to the upcoming break 
====November 29th, 2011====
Today we learned about EoCE, or the end of class experience, which is not a final exam, but a final experience of the class which is a totally and completely different thing than a final exam. Haas answered any questions we had about the EoCE before taking questions on everything else and giving us more play time while putting out small fires and burning children and such while discovering the interesting universe of Ryan VS. Dorkman.
=====unix Topics=====

====Foregrounding a process====
Foregrounding a process brings it back from being backgrounded and allows you to resume  using it. To Foreground a process you type the file name followed by fg.
====Backgrounding a process====
Backgrounding a process frees up the terminal and allows you to do other things. To background a process simply type the filename followed by the ampersand (&). In order to bring the process back you will need to use the foreground command
====Keyword 3====
Identification and definition of the chosen keyword. Substitute "keyword" with the actual keyword.

If you wish to aid your definition with a code sample, you can do so by using a wiki **code** block, an example follows:

<code c>
/*
 * Sample code block
 */
#include <stdio.h>

int main()
{
    return(0);
}
</code>

====Keyword 4====
Identification and definition of the chosen keyword. Substitute "keyword" with the actual keyword.

If you want to demonstrate something on the command-line, you can do so as follows:

<cli>
lab46:~$ cd src
lab46:~/src$ gcc -o hello hello.c
lab46:~/src$ ./hello
Hello, World!
lab46:~/src$ 
</cli>


====Keyword 5====
Identification and definition of the chosen keyword. Substitute "keyword" with the actual keyword.

If you wish to aid your definition with a code sample, you can do so by using a wiki **code** block, an example follows:

<code c>
/*
 * Sample code block
 */
#include <stdio.h>

int main()
{
    return(0);
}
</code>


====Keyword 6====
Identification and definition of the chosen keyword. Substitute "keyword" with the actual keyword.

If you want to demonstrate something on the command-line, you can do so as follows:

<cli>
lab46:~$ cd src
lab46:~/src$ gcc -o hello hello.c
lab46:~/src$ ./hello
Hello, World!
lab46:~/src$ 
</cli>


====Keyword 7====
Identification and definition of the chosen keyword. Substitute "keyword" with the actual keyword.

If you wish to aid your definition with a code sample, you can do so by using a wiki **code** block, an example follows:

<code c>
/*
 * Sample code block
 */
#include <stdio.h>

int main()
{
    return(0);
}
</code>

====Keyword 8====
Identification and definition of the chosen keyword. Substitute "keyword" with the actual keyword.

If you want to demonstrate something on the command-line, you can do so as follows:

<cli>
lab46:~$ cd src
lab46:~/src$ gcc -o hello hello.c
lab46:~/src$ ./hello
Hello, World!
lab46:~/src$ 
</cli>


====Keyword 9====
Identification and definition of the chosen keyword. Substitute "keyword" with the actual keyword.

If you wish to aid your definition with a code sample, you can do so by using a wiki **code** block, an example follows:

<code c>
/*
 * Sample code block
 */
#include <stdio.h>

int main()
{
    return(0);
}
</code>


====Keyword 10====
Identification and definition of the chosen keyword. Substitute "keyword" with the actual keyword.

If you want to demonstrate something on the command-line, you can do so as follows:

<cli>
lab46:~$ cd src
lab46:~/src$ gcc -o hello hello.c
lab46:~/src$ ./hello
Hello, World!
lab46:~/src$ 
</cli>


====Keyword 11====
Identification and definition of the chosen keyword. Substitute "keyword" with the actual keyword.

If you wish to aid your definition with a code sample, you can do so by using a wiki **code** block, an example follows:

<code c>
/*
 * Sample code block
 */
#include <stdio.h>

int main()
{
    return(0);
}
</code>


====Keyword 12====
Identification and definition of the chosen keyword. Substitute "keyword" with the actual keyword.

If you want to demonstrate something on the command-line, you can do so as follows:

<cli>
lab46:~$ cd src
lab46:~/src$ gcc -o hello hello.c
lab46:~/src$ ./hello
Hello, World!
lab46:~/src$ 
</cli>
=====unix Objective=====
====Objective====
State the course objective; define what that objective entails.

===Method===
State the method you will use for measuring successful academic/intellectual achievement of this objective.

===Measurement===
Follow your method and obtain a measurement. Document the results here.

===Analysis===
Reflect upon your results of the measurement to ascertain your achievement of the particular course objective.

  * How did you do?
  * Room for improvement?
  * Could the measurement process be enhanced to be more effective?
  * Do you think this enhancement would be efficient to employ?
  * Could the course objective be altered to be more applicable? How would you alter it?
=====Experiments=====
====Compression Script====

===Question===
can i write a script that allows me to compress files simply by typing their names?
===Resources===
Class, Opii

===Hypothesis===
I think it will succeed.

gzip, the command use to compress files should be able to work in conjunction with the Echo command to allow me to make a title entry bar for the files i want to compress.

===Experiment===
I'm going to write the script.

===Data===
the script was successful in compressing the files run through it.
<cli>
!/bin/bash


echo "enter filename: "
read word
word=$word
gzip $word

exit
</cli>
===Analysis===
My Hypothesis was correct and is possibly applicable. The only real shortcoming is how limited the script is.
===Conclusions===
if something as like zipping a file can be made put into a script to simplify it then it's possible to do so with more advanced commands.
====Regular expression====

===Question===
can i have a regular expression search through an entire directory?
===Resources===
Class, Opii

===Hypothesis===
I think it will succeed.

Using the cat and ls commands with grep and there's no reason you shouldn't be able to add
===Experiment===
I'm going to write the script.

===Data===
could not get the command to work
"ls usr |cat|grep '^[1]*$'|less|wc -l" only shows "0" regardless of the directory

===Analysis===
Something must be wrong with the command.
===Conclusions===
Data suggests that the command i'm using is incorrectly structured. While my commands is faulty i think the objective is plausible.