Wednesday, October 28, 2009

Day 17

Day 17: Network Concepts

My IP address while using the internet was…

IP Address:
152.33.62.173
Source:
whois.arin.net
Prefix:
152/8
Designation:
Administered by ARIN
Status:
LEGACY
OrgName: Elon University OrgID: ELONUAddress: 100 Campus DriveCity: ElonStateProv: NCPostalCode: 27244-2010Country: US

We used WhatismyIP.com and Whois.net to find out information about our IP address and information on other internet domain addresses.


On “WhoIs” I looked up facebook.com and got the following information…




Registrant:
Facebook, Inc
1601 S. California Ave
Palo Alto, CA 94304
US

Domain name: FACEBOOK.COM


Administrative Contact:
Admin, Domain domain@facebook.com
1601 S. California Ave
Palo Alto, CA 94304
US
+1.6505434800 Fax: +1.6505434800

Technical Contact:
Admin, Domain domain@facebook.com
1601 S. California Ave
Palo Alto, CA 94304
US
+1.6505434800 Fax: +1.6505434800



Registration Service Provider:
Lysand LLC
http://www.lysand.com/
This company may be contacted for domain login/passwords,
DNS/Nameserver changes, and general domain support questions.


Registrar of Record: TUCOWS, INC.
Record last updated on 20-May-2009.
Record expires on 30-Mar-2010.
Record created on 29-Mar-1997.

Registrar Domain Name Help Center:
http://domainhelp.tucows.com

Domain servers in listed order:
NS2.FACEBOOK.COM 204.74.67.132
DNS05.SF2P.TFBNW.NET
DNS04.SF2P.TFBNW.NET
NS1.FACEBOOK.COM 204.74.66.132

Monday, October 26, 2009

Day 16: Interactive Network Activity

-- What was the word you were sent, and what is its definition?-- What was the word you were trying to send, and what is its definition?-- How long does it take you to send your message using this method?-- Was it easier to send or receive a message using this method?-- What were some of the bottlenecks?-- How could you speed up this process or make it more efficient?

The word I was supposed to have received was “factotum,” which is defined by Wikipedia as a general servant or a person having many diverse activities or responsibilities. However, I did not receive my entire message (I only got 4 out of the eight letters) and did not receive or hear the numbers correctly when they were relayed to me, because I got a different first 4 letters than my sender.
The word I sent out was “gremials,” which is defined as being is a square or oblong cloth which a
bishop, according to the "Cæremoniale Episcoporum" and "Pontificale", should wear over his lap, when seated on the throne during the singing of the Kyrie, Gloria and Credo by the choir, during the distribution of blessed candles, palms or ashes, during the washing of feet in the Mass of the Lord's Supper, and also during the anointments in connection with Holy orders.
Using the method we initially used in class, relying messaging between each other was a tedious task, but for the most part people got their messages across. It did take the class close to an hour to relay our different 8-letter-word messages though. I also feel like the people who were louder and more inclined to speak up, were the ones who got the message out more clearly and faster than others.
For me, it was easier sending out messages rather than receiving them, because I could choose when I wanted to send them out, the content in which I was sending out and I was prepared for the task, as opposed to when you receive the message, you have to be ready to write it down, hear it clearly and then decode it.
Some issues or “bottlenecks” that the class ran into were collisions when people started to speak up all at once and there were also some issues with people not hearing their message clearly and having to figure out how to tell their sender the problem. We tried a few different methods of relaying messages through our network and in the end stuck with our original choice, of sending out messages at random.
I believe you could make this task more efficient by utilizing the circle method of allowing each computer/person to say their message and if they have no message send it on to the next person.

Wednesday, October 21, 2009

October 21: Networking thoughts...

Q: What are some creative ways to design a network to handle 1) addressing and 2) communication conflicts in a bus topology?
Addressing can be defined simply as a networks way of finding other computers. A way to help networks find other computers more smoothly and directly would be to name or label each of the computers attached to the network wire of the bus. This could be done a few different ways, either by using numbers, letters or a combination of both to help the network identify where each piece of information is going and to help organize the information when going through the wire.
Having a structured and labeled way of addressing or finding other computers will help to ensure better communication throughout the bus wire and helps to make things run together and more smoothly. Naming them gives the network and address or specific computer of where to send the information, instead of guessing or sending throughout to all. This labeling in beneficial in all sorts of other areas, not just in the computer networking world and helps to make communication run better and faster.

Wednesday, September 23, 2009

Day 7: Lab 1 & 2

LAB 1:

After some very grueling and frustrating conversations discussing other options for using the punch, my group finally came up with an optional theory on how to use a punch to write out letters. Using the same 80-character capability, we converted the decimal to binary code to represent the letters of the alphabet. The numbers punched would be the same, but in order to type in letters, you would use the binary code system.

The binary code consisted of:

1

2

4

8

16

32

64

128

0

1

2

3

4

5

6

7

Each number represented in the binary code would correspond to a number found on the decimal punch card, which then would be turned on and off to represent the corresponding numerical value of the alphabet. For example, the letter “L” is the 12th letter in the alphabet. To represent this number with the binary code you would turn on the “4” and “8”, to show the letter “L”.

LAB 2:

The code in Lab 2 says, “Be sure to drink your ovaltine.”

Using the base that binary code “65=A”, my group was able to break down the code by strands of 8 and decode the message. Therefore the letter “B” would be binary code “66”, “C=67”, “D=68”, and so on. The 8-bit number “00100000” represents a space in between words. We used a binary code converter to check our answers and discover what the “0010000” 8-bit code represented.

The binary code above is similar to the theory my group thought up from the question above, when using the number of where the letter falls in the alphabet to represent it in binary code form.

Monday, September 21, 2009

Day 6: How to read a Punch Card

In class today we learned how to decipher and read a punch card. Although they look intimidating a first, there I am going to explain step by step an easy way to read them.

A punch card can be defined a piece of paper that displays digital information by using a series of holes and corresponding numbers to represent numbers and words. For a better description and summary of the history and invention of the punch, please follow this link on Wikipedia: http://en.wikipedia.org/wiki/Punched_card

To start out, there are 12 lines altogether on your card that will help you decipher the corresponding number or letter that was typed.

The first two lines are blank (12 & 11) which helps to establish what letter is being typed or special character, followed by the number 0-9.

Numbers correspond directly to their number that is punched, basically numbers are easy to recognize. The letters of the alphabet get a little bit trickier.

If a hole is punched on the 12th, along with an additional punch, that is referring to the first 9 letters of the alphabet. The 11th line corresponds with the second sets of 9 letters, and line 0 corresponds with the last set of 9.

For visual a good visual aid, follow this link http://www.cs.uiowa.edu/~jones/cards/codes.html.

ABCDEFGHI= 12TH line and corresponding number

JKLMNOPQR= 11TH line and corresponding number

STUVWXYZ= Line 0 and corresponding number

- Single punches= number

- 2 punches= letter

- 3 punches= special character

Wednesday, September 16, 2009

Triumph of the Nerds: Part 2

What is reverse engineering?
Reverse engineering can be described in short as making a replica of an already existing piece of software, which is either the same or faster than the one it is being compared to. In the documentary, Triumph of the Nerd, reverse engineering was used on IBM’s PC for competitors to figure out how to become a more integrated part of the computer market at the time. A group of 15+ ‘virgin to IBM code’ men came together to take part IBM’s ROM-BIOS to create a new, but similar version, which would enable them to make a PC that could read IBM’s other software.
According to www.npd-solutions.com, reverse engineering can be described as a process of better analyzing a system by:
Identify the system's components and their interrelationships
Create representations of the system in another form or a higher level of abstraction
Create the physical representation of that system
Is reverse engineering legal?
Many ethical and legal questions come to mind when talking about reverse engineering. Plagiarism and copying is often frowned upon in our society, yet technology and advancement would not move forward if people did not question, experiment, and build upon one another’s ideas.
The IBM’s ROM-BIOS was copyrighted, which is why the men of Compact were smart in hiring individuals that were not accustomed to IBM’s code when creating their replica version. So in that sense, things were done legally ‘by-the-book.’ On the other hand, some might argue it does not seem to be quite ethical. As mentioned before, things cannot move forward unless someone examines them differently. We also live in a world of free enterprise, where competition among businesses is what we strive for and reverse engineering is a way to keep up with demand and competition.

Monday, September 7, 2009

Day Two: Hardware

After today's talk about hardware and the basic inside of a computer one question I am still wondering about is how exactly the chips, wires, CPU, etc all come together to create what we see on the page. I understand the basic setup of the products, but do not fully understand how they work still to create the programs we have on our computers today.