======Part 1====== =====Entries===== ====September 2, 2011==== Working with pointer and link list. Fun fun. The wonderful pointers that make the link list of happy and not so happy. 8-) -> 8-O -> :-( -> :-) -> =) -> :-/ -> :-\ -> :-? -> :-D -> :-P -> :-O -> :-X -> :-| -> ;-) -> ^_^ -> LOL This is the starter of the pointing that will lead to more pointing and then even more pointing. Then when all is pointing we pop it. LOL ====Month Day, Year==== 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. ====Month Day, Year==== 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. ====Month Day, Year==== 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. ======Topics Data====== =====Version Control (checkout, commit, update, add, log)===== Version Control is where you pick a time to save it to the system the system keep this version with the date and time that it was made in a list of other versions of the same program. like version1 version2.6 version3 and so on. There are version Control like SVN. This kind of Version Control System can be used by groups to work on collaborating projects. With this type of version control you have to add the file then commit it to the repository then its in the system. checkout- commit- update- add- log- lab46:~$ cd src lab46:~/src$ gcc -o hello hello.c lab46:~/src$ ./hello Hello, World! lab46:~/src$ /* A small program to save different copes of the same program at different * points so that if changers are made the user can go back to before * the changer where made. */ #include int main() { return(0); } =====Pointers (address of, assignment, dereferencing)===== Pointers work by having the address that they point to the thing that your working with. A is a pointer to B, B points to NULL, C points to A. ^ letter ^ Address ^ Address being pointing to ^ | A | 0001 | 0010 | | B | 0010 | NULL | | C | 0011 | 0001 | ==arrays, pointer arithmetic== ==pointers to pointers== A pointer may point to another pointer that could point to another pointer. ^ Pointer ^ Whats being pointed at ^ address ^ | A | 0011 |0001| | B | 0100 |0010| | C | 0010 |0011| | D | 0001 |0100| Here A points to C, C points to B, B points to D, D points to A. ==null pointers== Pointing to Null. ==void pointers== Pointers with no data type. ==function pointers== lab46:~$ cd src lab46:~/src$ gcc -o hello hello.c lab46:~/src$ ./hello Hello, World! lab46:~/src$ /* * * */ #include int main() { return(0); } =====Static allocation vs. Dynamic allocation===== ^Static Allocation^VS^Dynamic Allocation^ | | | | ==Memory allocation (malloc(), new)== Memory allocation is making a space to store the new data in. ==Memory De-allocation (free(), delete)== Memory De-allocation is freeing up the space that was used to store data in. /* * Sample code block */ #include int main() { return(0); } =====Structures===== A structure is a group of variable in a single container. ==structure pointer== lab46:~$ cd src lab46:~/src$ gcc -o hello hello.c lab46:~/src$ ./hello Hello, World! lab46:~/src$ ======Topics Sys Prog====== =====UNIX Systems Programming===== Unix system programming is the coolest thing ever if you have no idea what it is your in the wrong place. Not really. Yeah its cool and stuff but there is a lot to Systems programming. In this case we are limited to Unix, this is really good for if having to chose I would chose Unix or Linux. To start there is understanding the operating system, files, network, programs, commands, signals, shell, kernel, user space, multiple user system and a lot more. ==User space== This space is just for the user and all of there junk and the programs/applications. ==Kernel, Kernel space== Kernel space is it's own happy place that is where the Kernel lives. It lives in between the applications and the CPU (memory, device). There's a lot of traffic that goo's thru the Kernel to get to some form of hardware. |Software| <-> |Kernel| <-> |Hardware| =====Users, Files, and the Manual===== Users are people that uses. Files are folders. Manual is a Document that describes how something works. So users use manual to find out how to make a file and then uses the documentation in the manual to fill the file. ==File Access (open, read, write, lseek, close)== Opening a file means that you have the ability to see what is in the file. fp = fopen(FileName, Mode); This will open the file the mode says what you want to do. Reading a file means that you can see the data of the file that you opened. Setting the mode to r will let you read from the file. Ones the file is open you can also read the file using printf. Writing to a file means that you can edit it. Setting the mode to w will let you write to the file. Ones the file is open you can also write to the file using scanf. Closing a file means that its no longer open to be used. lseek allows the file to be add to at the end, append. ==File descriptors== ==Buffering== ==System Calls== =====Directories and File Properties===== ==File Types and File Properties== ==Bit Sets and Bit Masks== ==User IDs, Group IDs== ======Topics HPC 1====== =====Bourne Shell (sh shell)===== This is a default shell for Unix. Its the most simple shell for Unix systems. Its the sh shell. It was made to replace the original shell made by Thompson. /bin/sh =====Maintenance===== Is to fix or correct, clean, keeping up-dated. Software maintenance is fixings bug's that where found after release, and up-dating the software so that it can work with new software that came out. Maintenance is needed for lots of reasons, its main goal is to keep the something working as it should. =====logging===== Logging is the presses of cutting down tree's for use. Or it could mean the presses of logging activity or events. When a computer keeps a log it some important data in a file or a file of important data. ^ Log ^^^^ ^ Date ^ Time ^ Event ^ Change ^ | 10/23/11 | 10:30 am | UP | 10° | | 10/23/11 | 12:45 am | DN | 15° | | 10/23/11 | 03:25 pm | UP | 23° | | 10/23/11 | 04:50 pm | DN | 25° | | 10/24/11 | 11:20 am | UP | 11° | This is a log of Temperature change it only logs when the temperature changes in a different direction. =====Accessibility===== To be able to have the ability and the access to use something. In Computing Accessibility it's about the computer being able to give someone access to the system and then the program giving the ability the the user to do something. ^ Some thing to Read ^^ | If not look harder. | Can you see what is in the Box? =====Upgrades===== Upgrading is the process that should bring the ability of some thing to a more advanced level. =====backups===== A file that is saved else where or is saved before a test is run or compiled. =====documentation===== Documentation is a manual or a webpage that describe what it is and what it can do, and how it works. =====resource usability===== =====Remote Administration===== This is where the computer is controlled from a location other then physically controlling it or getting data from it. This requires the use of a network and some times the internet. =====on-site administration===== =====security - internal===== =====log analysis===== Making sense of computer generated logs. Like understanding what a log of info is saying. Take temp log. This is a log of the daily temps. ^ Time ^ Temp ^ | 12:01 | 32 | | 1:01 | 29 | | 2:01 | 26 | | 3:01 | 24 | | 4:01 | 21 | | 5:01 | 22 | | 6:01 | 23 | | 7:01 | 28 | This log is saying that its colds at about 4am in the morning. And that temp drops from 12:01 to 4:01 then rises at 5:01 to 7:01. ======Data 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? ======HPC1 Objective====== ===Objective=== State the course objective; define what that objective entails. My objective is to get the documentation done for the wall how to. Other objectives are to find out more about samba. ===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? ======Sysprog 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===== ====Experiment 1==== ===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. ====Experiment 2==== ===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. ====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. ====Retest==== If you're doing an experiment instead of a retest, delete this section. If you've opted to test the experiment of someone else, delete the experiment section and steps above; perform the following steps: ===State Experiment=== Whose existing experiment are you going to retest? Prove 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).

Can you read me?