======Part 1====== =====Entries===== so many keys and commands to take in. command promts. ====september 17, 2011==== Ive learned the vi text editor realy is the Best text editor on the planet. entering text is inspiring. may need more practice ====9/21/2011==== This is a sample format for a dated entry. Please substitute the actual date for "Month Day, Year", and duplicate the level 4 heading to make additional entries. - ===September 24, 2011==== played with commands. Found out how to move files around =====Topics===== ====Shell==== The shell is the traditional user interface If you wish to aid your definition with a code sample, you can do so by using a wiki **code** block, an example follows: ====Root==== main, center, top, start directory. If you want to demonstrate something on the command-line, you can do so as follows: lab46:~$ cd / ====directory==== A file system structure. same as the file folder, which is a visual aid for non-unix users. If you wish to aid your definition with a code sample, you can do so by using a wiki **code** block, an example follows: ====Pipe==== a set of processes chained by their standard streams, so that the output of each process (stdout) feeds directly as input (stdin) to the next one. If you want to demonstrate something on the command-line, you can do so as follows: | ====cal==== calender- displays time, date, country codes. ====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: lab46:~$ cd src lab46:~/src$ gcc -o hello hello.c lab46:~/src$ ./hello Hello, World! lab46:~/src$ ====tee==== The tee utility is one of my personal favorites and is very simple. The command is intended to be used in a pipe to capture the standard output of another command and display it on the screen, as well as copy it to a file. In the following example, the directory listing is displayed on the screen, and also copied to the file dir.txt. Using cat to type out the dir.txt file shows that it contains the same information that was displayed on the screen. $ ls -l|tee dir.txt total 141 -rwxrwxrwx 1 mjb group 16850 Apr 12 16:13 SMALL01.DOC -rwxrwxrwx 1 mjb group 14881 Apr 12 20:51 SMALL02.DOC -rwxrwxrwx 1 mjb group 17758 Jun 13 01:29 Small03.doc -rwxrwxrwa 1 mjb group 12791 Jul 12 22:44 Small04.doc -rwxrwxrwx 1 mjb group 4232 Jun 12 00:03 Smallxx.doc drwxrwxrwx 1 mjb group 0 Jul 12 21:25 docs -rwxrwxrwx 1 mjb group 261 Jun 13 01:08 hello.cbl -rwxrwxrwx 1 mjb group 184 Jun 13 00:59 hello.txt -rwxrwxrwa 1 mjb group 343 Jul 12 21:32 mver -rwxrwxrwa 1 mjb group 83 Jul 12 19:52 sh_histo -rwxrwxrwx 1 mjb group 455 Apr 12 18:10 simpmenu -rwxrwxrwx 1 mjb group 600 Apr 12 18:39 simpmenu.txt -rwxrwxrwa 1 mjb group 17 Jul 12 22:24 sleepy -rwxrwxrwx 1 mjb group 189 Jun 13 01:13 smallfry.txt $ cat dir.txt total 141 -rwxrwxrwx 1 mjb group 16850 Apr 12 16:13 SMALL01.DOC -rwxrwxrwx 1 mjb group 14881 Apr 12 20:51 SMALL02.DOC -rwxrwxrwx 1 mjb group 17758 Jun 13 01:29 Small03.doc -rwxrwxrwa 1 mjb group 12791 Jul 12 22:44 Small04.doc -rwxrwxrwx 1 mjb group 4232 Jun 12 00:03 Smallxx.doc drwxrwxrwx 1 mjb group 0 Jul 12 21:25 docs -rwxrwxrwx 1 mjb group 261 Jun 13 01:08 hello.cbl -rwxrwxrwx 1 mjb group 184 Jun 13 00:59 hello.txt -rwxrwxrwa 1 mjb group 343 Jul 12 21:32 mver -rwxrwxrwa 1 mjb group 83 Jul 12 19:52 sh_histo -rwxrwxrwx 1 mjb group 455 Apr 12 18:10 simpmenu -rwxrwxrwx 1 mjb group 600 Apr 12 18:39 simpmenu.txt -rwxrwxrwa 1 mjb group 17 Jul 12 22:24 sleepy -rwxrwxrwx 1 mjb group 189 Jun 13 01:13 smallfry.txt $ ====gcc==== GNU Compiler Collection, formerly the "GNU C Compiler" ====USER==== person who uses Unix in some way. ====GUI==== Graphical User Interface- programs used by devices in order to provide human interface with the computer. I (I.E. keyboard,screen,mouse,trackball ====sudo,su ==== (Substitute userid) aka su - command allows you to change to another userid. (Substitute userid and do somthing) aka sudo- allows the single use of a command under the auspices of another user ====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: lab46:~$ cd src lab46:~/src$ gcc -o hello hello.c lab46:~/src$ ./hello Hello, World! lab46:~/src$ =====Objectives===== ====Objective 1==== 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===== Can i copy the game directory and past it in my closet. ====Experiment 1==== ===Question=== Can the game directory be copied and pasted into the a closer directory, such as, my closet? ===Resources=== Collect information and resources (such as URLs of web resources), and comment on knowledge obtained that you think will provide useful background information to aid in performing the experiment. The following commands are needed. $ man cp $ man ls $ pwd $ ls $ cp $ cd ===Hypothesis=== I belive that you can move or copy the game directory to another of your chosing. in turn bring an easy and quick solution to over exploitation of the cd command. While shorting the time it takes to play a simple game. Based on what you've read with respect to your original posed question, what do you think will be the result of your experiment (ie an educated guess based on the facts known). This is done before actually performing the experiment. State your rationale. ===Experiment=== resarch the paths from the root directory to the gams dir. and vise versa for the user shell . How are you going to test your hypothesis? What is the structure of your experiment? ===Data=== Perform your experiment, and collect/document the results here. ===Analysis=== Based on the data collected: * was your hypothesis correct? * was your hypothesis not applicable? * is there more going on than you originally thought? (shortcomings in hypothesis) * what shortcomings might there be in your experiment? * what shortcomings might there be in your data? ===Conclusions=== What can you ascertain based on the experiment performed and data collected? Document your findings here; make a statement as to any discoveries you've made. ====Experiment 2==== ===Question=== can you use a asterisk in a full command line in vi. ===Resources=== Collect information and resources (such as URLs of web resources), and comment on knowledge obtained that you think will provide useful background information to aid in performing the experiment. ===Hypothesis=== Based on what you've read with respect to your original posed question, what do you think will be the result of your experiment (ie an educated guess based on the facts known). This is done before actually performing the experiment. State your rationale. ===Experiment=== How are you going to test your hypothesis? What is the structure of your experiment? ===Data=== Perform your experiment, and collect/document the results here. ===Analysis=== Based on the data collected: * was your hypothesis correct? * was your hypothesis not applicable? * is there more going on than you originally thought? (shortcomings in hypothesis) * what shortcomings might there be in your experiment? * what shortcomings might there be in your data? ===Conclusions== the experiment shows that the lab46 vurtule set up can not run the ifconfeg ====Experiment 3==== ===Question=== What is the question you'd like to pose for experimentation? State it here. ===Resources=== Collect information and resources (such as URLs of web resources), and comment on knowledge obtained that you think will provide useful background information to aid in performing the experiment. ===Hypothesis=== Based on what you've read with respect to your original posed question, what do you think will be the result of your experiment (ie an educated guess based on the facts known). This is done before actually performing the experiment. State your rationale. ===Experiment=== How are you going to test your hypothesis? What is the structure of your experiment? ===Data=== Perform your experiment, and collect/document the results here. ===Analysis=== Based on the data collected: * was your hypothesis correct? * was your hypothesis not applicable? * is there more going on than you originally thought? (shortcomings in hypothesis) * what shortcomings might there be in your experiment? * what shortcomings might there be in your data? ===Conclusions=== What can you ascertain based on the experiment performed and data collected? Document your findings here; make a statement as to any discoveries you've made.