On this day I seen that all thing in computers work on similar bases to each-other. And that even tho some thing it would seem have nothing in common they do on some level. Like USB protocol and TFTP RFC 1350

USB protocol then RFC 1350 Token Packet then RRQ/WRQ

The two are still different but the token and the RRQ/WRQ do about the same thing and the format of both is similar. The token sets up read/send and control transfer. The RRQ/WRQ this sets the read/write and send the info on how to read the file. Both are one of the first thing sent both say what they are in the first part (Pid , 2 bytes). And both end with a zero value. And both have a way of passing the file ether by Name in RFC or by Address(amusing that a devise is a file to).

The little similarity in just the first pack are very commend even with other things that have to send data. But with the USB having to send data over a serial bus that it would have less in-common with TFTP.

Forking is cloning. So cloning makes a double that is close to the same as the original with some copies of the stuff it has. So it clones the parent to make children or a child. I thank this was outlawed. So now that there's a bunch of clone kids they can be sent out to do the Parents bidding and after there done the kids just die. Then the parent come's and collects there kid's by waiting. In most of the world this is not allowed and there's some sort of prison time involved.

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.

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.

This sorting algorithm takes two elements compares them and if you are sort it from less to most then it will move the lower element to the front of the pair and the higher to the back.

This is how the sort works.

Are images that get posted on the internet that then get changed by people on the net to be funny. Or there just made up.

Nyan cat: http://nyan.cat/

Leek spinning: http://leekspin.com/

Philosoraptor: http://fuckyeahphilosoraptor.tumblr.com/

And many many more are out there now waiting to be seen.

LVM = Logical Volume Manager or Management.

This is a disk drive manage it also dose other storage devices, mostly for big drives. Some operating systems have LVM built in to them like Debian, Ubuntu, Gentoo, that can make a boot-able filesystem on the logical volume.

Root logical volume one

    Physical area 1 & 3

Var logical volume two

    Physical area 2

Home logical volume three

    Physical area 4

It the protocol used for USB. With a USB being a serial bus it mean's that the data need to be put in to packets for sending and receiving. So USB has a protocol that it uses for this.

This is a Token Packet

This is a Start of Frame packet

This is a Data packet

The CRC is only computed over the data field it doesn't include the PID.

There are more packet than this there is the Handshake packet and a Ping packet.

A model, sample, test, process, that act's a thing to learn from or to replicate.

In this there where Prototypes A - C where set up. What there after is how to make C.

None of these Prototype came out with the right answer.

Prototype A - C can still be used as a learning tool to get to C

Prototype D answered the question on how to get C. In this demonstration we start with a Test that Fails. Then another Test sampling Prototype A this Fails as well. From A and B its learned that C can't be achieved in this manner. Then Prototype C has a Sampling of A and B that is another Test. This is then model a little different to get Prototype D that works. From there the process is replicate to make more C.

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:

/*
 * Sample code block
 */
#include <stdio.h>
 
int main()
{
    return(0);
}

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$ 

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:

/*
 * Sample code block
 */
#include <stdio.h>
 
int main()
{
    return(0);
}

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$ 

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:

/*
 * Sample code block
 */
#include <stdio.h>
 
int main()
{
    return(0);
}

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$ 

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:

/*
 * Sample code block
 */
#include <stdio.h>
 
int main()
{
    return(0);
}

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$ 

Will eat your brains. Not really there just processes that did not die with the rest. There are two kinds of zombies.

State the course objective; define what that objective entails.

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

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

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?

State the course objective; define what that objective entails. I am taking the time to find out more about Debain and what its like to run my own server using samba. So I'm reading up on all the stuff it asks well loading up.

State the method you will use for measuring successful academic/intellectual achievement of this objective. The measure that I have set forth is that I will have a working server that I can use and I will understand what is going on and what all that stuff is that its asking for. I know all the general parts of what is going on but the other things like what LVM is and what it dose for a Linux system. Mostly I just want the server working and to know what all that little stuff is and what it's doing.

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

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?

State the course objective; define what that objective entails. I am hoping that this months objective is to get a program that can run on different computers as one. So hoping.

State the method you will use for measuring successful academic/intellectual achievement of this objective. That I write a program that can be run on multiple systems. Even if it can't I just want to know how its done and how close I can get.

Follow your method and obtain a measurement. Document the results here. That I have a running program that is forked so that it can run on different systems.

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?

What is the question you'd like to pose for experimentation? State it here.

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.

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.

How are you going to test your hypothesis? What is the structure of your experiment?

Perform your experiment, and collect/document the results here.

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?

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.

What is the question you'd like to pose for experimentation? State it here.

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.

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.

How are you going to test your hypothesis? What is the structure of your experiment?

Perform your experiment, and collect/document the results here.

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?

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.

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:

Whose existing experiment are you going to retest? Prove the URL, note the author, and restate their question.

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.

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?

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?

Publish the data you have gained from your performing of the experiment here.

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?

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