======Part 3======
=====Entries=====
==== April 3, 2012====
Burnout-
- power source burnout
- started project for extended mini screen
- opus maybe
==== April 5, 2012====
More work -less play
- still hung up on project
- using sever at home with no screen ( the uklmimate no gui )
- using putty in order to sometimes see what is processing.
==== April 10, 2012====
-trying to keep springbreak out of my mind
- looked up some linux facts
====Entry 12: April Day, 2012====
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.
As an aid, feel free to use the following questions to help you generate content for your entries:
* What action or concept of significance, as related to the course, did you experience on this date?
* Why was this significant?
* What concepts are you dealing with that may not make perfect sense?
* What challenges are you facing with respect to the course?
Remember that 4 is just the minimum number of entries. Feel free to have more.
{{page>hpc0part3&nofooter}}
{{page>unixpart3&nofooter}}
=====Experiments=====
====log in scpirt====
===Question===
can one create their own xorg.config file
===Resources===
-knowledge of Linux file system and or way to quick reference
===Hypothesis===
I believe that one can create a way to direct an graphic relay t a additional screen by the creation of a xorg.conf file with in the /etc/X11/ directory.
===Experiment===
-cd into /etc/X11/
-command: vim /etc/X11/xorg.conf
-with no file present and having a new file born a new i filled the blank space with a template text found on source site
===Data===
##################Original Video Setting ###################
section "Device"
Identifier "configured Video Device"
EndSection
Section "Monitor"
Identifier "configured Monitor"
EndSection
Section "screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "configured Video Device"
SubSection "Display"
Depth 24
Modes "1280x800"
EndSubSection
EndSection
#####################################################
Section "ServerLayout"
Identifier "server Layout"
Screen 0 "Default Screen" 0 0
Screen 1 "DisplayLinksScreen" Leftof "default Screen"
EndSection
#####################################################
Section "Files"
ModulePath "/usr/lib/xorg/modules"
ModulePath "/usr/local/lib/xorg/modules"
EndSection
###########DisplayLink Stuff#########################
Section "Device"
Identifier "DisplayLinkDevice"
Driver "displaylink"
Option "fbdev" "/dev/fb0"
EndSection
Section "Monitor"
Identifier "displayLinkMonitor"
EndSection
Section "screen"
Identifier "DisplayLinkScreen"
Device "DisplayLinkDevice"
Monitor "DisplayLinkMonitor"
SubSection "Display"
Depth 24
Modes "1280x1024"
EndSubsection
EndSection
~
~
~
~
~
===Analysis===
-something went wrong.
-the gui of the m,achain is inoperatable.
- startx module is unresponsive when implemented
- My presumption was wrong and i see the importance to how a config file can change the activity of the Linux machine.
===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 8====
===Question===
Can one make their own Xorg.conf file and have it work
===Resources===
instructor-Haas
www.google.com
www.mulchman.org
===Hypothesis===
By craeting a text file in vim text editor i can have a a second screen mounted and operating on nmy school linux box.
===Experiment/Data===
followed the instructions on the Mulchman.org web site to acquire the appropiate files and drivers.
- had a problem with the make command form the start
- Found that additional pakages and headers were needed to finshed the project. (thx Haas)
- many hold ups have keeped this project form compleation
===Analysis===
Based on the data collected:
* Needs headers for XF86
*learned more than i knew before and yet i feel i must know more
===Conclusions===
THE OCEAN IS BIG- BRIAN and so is the world of linux
====Retest 3====
Perform the following steps:
===State Experiment===
Whose existing experiment are you going to retest? Provide the URL, note the author, and restate their question.
===Resources===
Evaluate their resources and commentary. Answer the following questions:
* Do you feel the given resources are adequate in providing sufficient background information?
* Are there additional resources you've found that you can add to the resources list?
* Does the original experimenter appear to have obtained a necessary fundamental understanding of the concepts leading up to their stated experiment?
* If you find a deviation in opinion, state why you think this might exist.
===Hypothesis===
State their experiment's hypothesis. Answer the following questions:
* Do you feel their hypothesis is adequate in capturing the essence of what they're trying to discover?
* What improvements could you make to their hypothesis, if any?
===Experiment===
Follow the steps given to recreate the original experiment. Answer the following questions:
* Are the instructions correct in successfully achieving the results?
* Is there room for improvement in the experiment instructions/description? What suggestions would you make?
* Would you make any alterations to the structure of the experiment to yield better results? What, and why?
===Data===
Publish the data you have gained from your performing of the experiment here.
===Analysis===
Answer the following:
* Does the data seem in-line with the published data from the original author?
* Can you explain any deviations?
* How about any sources of error?
* Is the stated hypothesis adequate?
===Conclusions===
Answer the following:
* What conclusions can you make based on performing the experiment?
* Do you feel the experiment was adequate in obtaining a further understanding of a concept?
* Does the original author appear to have gotten some value out of performing the experiment?
* Any suggestions or observations that could improve this particular process (in general, or specifically you, or specifically for the original author).