NSFnet — 20 Years of Internet Obscurity and Insight

coondoggie writes "The National Science Foundation (NSF) reissued the words that started the Internet revolution 20 years ago today: 'The NSFnet Backbone has reached a state where we would like to more officially let operational traffic on.' That was the email sent to users of the NSF's fledgling NSFnet to announce that the network's backbone had been upgraded to a 'blazing T-1 speed.' NSFnet was created by NSF a few years earlier in an attempt to create a computer network similar to the Department of Defense's ARPANET. When the original six-node, 56 kilobits-per-second NSFnet backbone went into operation in 1986, NSF made the decision to allow any academic, governmental or commercial entity to hook up to this network of networks. Within a few weeks of going online, traffic on the new network began doubling every few weeks. The network's backbone of core 56 kilobits-per-second connections were considered fast, but they were not fast enough to satisfy the demands of all the new users who were coming online, according to the NSF."

Comments

I was at one of the earliest Internet sites...

[MichaelCrawford]

... the California Institute of Technology, in Pasadena. But I was working for an astronomer; our Vaxes ran VMS, which didn't support the Internet Protocol.

My friends who worked for the Physics department got to use the Internet though, because they ran Unix. They had all the source to it too - my friends' jobs was hacking on it.

One of their jobs was making troff output to graphics printers; the original troff only worked with phototypesetters, which were amazing optical devices that got their letterforms from images on filmstrips. The typesetter would load the film for the font you wanted, say to switch from bold to italic, then use the optics to scale the image onto photo paper at the right point size.

There was a huge debate in the astronomy department as to whether we should get on the Internet; it was thought that the expense of porting all of our data analysis software to Unix wouldn't be worth it. It was all written in FORTRAN!

I later transferred to UC Santa Cruz. I think they were on the Internet when I started in 1985, but it may have only been UUCP - Unix to Unix Copy Program, suitable for email and Usenet but not remote login. It worked great for file transfer too, if you knew the bang path from one end to the other. You might have to wait several days for your file to show up, but it generally arrived OK.

Later when I was a sysadmin at Octel Communications, I wrote a shell script called getrfc that would use UUCP to fetch the desired RFC from the IETF file server. My users thought it was the best thing since sliced bread.

Anyway, I knew for sure that at some point UCSC's only connection to the Internet backbone was a 56k leased line to the SF Bay Area, probably to Stanford. This was a campus of thirteen thousand students - which gave out free Unix accounts for the asking! - and thousands of staff and faculty, all connected to the rest of the world via the equivalent of a single 56k dialup connection. But it seemed to work really well!

It happened that I went back to school at UCSC this summer to sharpen my Computer Science skills (my degree is in physics, so my programming is all self-taught). It blew my mind that I could register for classes via a web page from my home in Silicon Valley - the web didn't even exist when I was an undergrad.

I was also quite surprised to find power outlets on each of the desks in the lecture hall. For laptops you know.

I remember being in high school, and my father telling me that someday there would be such a thing as a laptop. I found it hard to imagine.

Kids These Days. You don't know how good you've got it!