vallor
2017-02-03 13:01:00 UTC
// snip
use Windows is to update my Garmin. Otherwise, I'm in Linux doing
everything I need or want to do. Currently running Linux Mint 18.
I've been using Linux since 1992 though, installing the Manchester
Computing Center boot/root floppies. Hell, we didn't even have
TCP/IP in the beginning, had to run a Linux port of KA9Q NOS to be
able to log in to the thing remotely. Didn't have ethernet either,
had to use SLIP.
("And had walk to the campus barefoot in the snow, uphill, both
ways..." ;)
I swear that as I was reading this I was thinking about the barefoot
in the snow, uphill.... both ways. And then I read you wrote that and
it is even more funny. :)
let's see... 1992.... I believe at that time I had an Amiga 3000 which
had a 14.4k modem connected to a UNIX box which I subscribed to and I
was using the korn shell. Not well, either. I didn't know jack-shit
about the shell. But it was a shell account non the less.
In 1994 I got my hands on real UNIX for the first time from Novell. I
had UNIXWare which was UNIX System V release 4.2. It was merely part
of my NetWare training and so I paid enough attention to it to pass
but it was not the focus of the study; Netware was. NetWare 3.12 as a
matter of fact. Which was all text at that time.
Well, I went to work at the local 2-year college campus as a studentIf there is an app I need and it is not available on Linux, that's
not down time. If you think it is you have deeper issues than I
thought. I have a calculator on my desk. I can calculate without it.
It's just damn convenient to use the calculator. Is that downtime
according to you? If your answer is yes, then thanks for cluing me
in as to just how retarded your mind truly is.
I dual-boot to Windows 10 to play games. The only other reason tonot down time. If you think it is you have deeper issues than I
thought. I have a calculator on my desk. I can calculate without it.
It's just damn convenient to use the calculator. Is that downtime
according to you? If your answer is yes, then thanks for cluing me
in as to just how retarded your mind truly is.
use Windows is to update my Garmin. Otherwise, I'm in Linux doing
everything I need or want to do. Currently running Linux Mint 18.
I've been using Linux since 1992 though, installing the Manchester
Computing Center boot/root floppies. Hell, we didn't even have
TCP/IP in the beginning, had to run a Linux port of KA9Q NOS to be
able to log in to the thing remotely. Didn't have ethernet either,
had to use SLIP.
("And had walk to the campus barefoot in the snow, uphill, both
ways..." ;)
in the snow, uphill.... both ways. And then I read you wrote that and
it is even more funny. :)
let's see... 1992.... I believe at that time I had an Amiga 3000 which
had a 14.4k modem connected to a UNIX box which I subscribed to and I
was using the korn shell. Not well, either. I didn't know jack-shit
about the shell. But it was a shell account non the less.
In 1994 I got my hands on real UNIX for the first time from Novell. I
had UNIXWare which was UNIX System V release 4.2. It was merely part
of my NetWare training and so I paid enough attention to it to pass
but it was not the focus of the study; Netware was. NetWare 3.12 as a
matter of fact. Which was all text at that time.
worker in 1991, and immediately got immersed in our NetWare
environment. And it was right about then that the campus got its
Internet connection through CSUNet.
After a few semesters of college prep courses, I decided I was tired of
being "poor", so applied for a full-time position in Computing
Services, and got the job. Worked there until 1995.
As a student worker, I had actually had one semester that was 4 units
of work experience, and 3 units of "special studies in computer
science", for a total of 7 units, which counted as "full time". The
"special studies" was developing a student-access Linux server, so that
students could have shell access to the Net, email and (later) web
pages.
In 1993 my biz partner and I used our knowledge gained with this
process to start developing a local business, and in 1994, opened our
doors as a public-access Unix host. We were originally going to be a
"freenet", but it turned out cwru wanted something like $20K to license
the software and the name, so we called ourselves a "pa-net" (pay-net).
Our company's first Net connection was a 56K ADN frame relay
connection. We were getting our USENET via C-band satellite though,
which was an amazing service for that time.
While we were still a shell hosting provider, "The Internet Adapter"
came about. This was a program that could be run on a shell host that
would provide TCP/IP to the person dialed up, so they could run Trumpet
Winsock and run their Internet apps, such as a web browser. A lot of
people were using TIA, so we bought a site license and made it part of
our service. Then we bought a Livingston Portmaster to serve PPP to
customers, and that's when we became a modern ISP.
By that time we had a T1, and had moved out of the residence we were
running the service out of into an office downtown. Not much longer
after that, we got fiber pulled into the building from the CO (a few
blocks down the street), and our Net connection became SMDS over T3.
might know you, but there are slight differences in what he did and what
you did. I was about to say, are your initials AB? or TB?
Yeah, it is SD, so I'm not the droid you're looking for. ;)
Yeah, I had a friend who started a hosting business back then. Very
similar to what you did. He used BSDI and also rented space downtown in
San Francisco which was hooked up with a T1. He wasn't an ISP though. He
was a registrar and a host. I was very proud of him for following
through. He was always kind of a fuck-up, but he followed through on
this and gave it an honest go.
That was an interesting era. I had an account with slip.net and I
remember having a Netcom.com account. Was all happy to get an ISDN line
and sync up lotus notes at 10k. My friends were WOW'ed by that.
The 90's were an amazing time for the Internet's development. It wassimilar to what you did. He used BSDI and also rented space downtown in
San Francisco which was hooked up with a T1. He wasn't an ISP though. He
was a registrar and a host. I was very proud of him for following
through. He was always kind of a fuck-up, but he followed through on
this and gave it an honest go.
That was an interesting era. I had an account with slip.net and I
remember having a Netcom.com account. Was all happy to get an ISDN line
and sync up lotus notes at 10k. My friends were WOW'ed by that.
quite a gold rush, a "boom".
Some technologies from the time were ahead of their time, such as some
protocols used for Project Athena. (Zephr comes to mind.) It was also a
time of "coopitition" between many ISP's, because there was so much
untapped market that a lot of times you could help the next guy to
succeed, without it impacting your own sales.
For that T3 we had, we had had to bring in the fiber by paying for
special construction. But once that building was lit, the building
filled up with Internet companies, all of them trying to make it in the
"gold rush boom". Some succeeded, others failed. We were running 10-
Base-T connections to customers, which doesn't sound like a lot today,
but at the time that was scads of bandwidth.
Things were so basic back then and now the expectations are so high.
I remember when we got our USR X2 modem gear for 56kbit dialup. Then westarted selling ISDN service, then DSL. Scott Adams (creator of
"Dilbert") worked in the SBC ISDN labs, and I think I once read a lament
of his that they sat on the technology for too long.
You are probably familiar with ISDN "B" channels, two of which could be
ganged together for a 128Kbit connection -- but did you know that ISDN
also had a "D" channel for slower-rate data services? I don't think
anybody ended up using it, but it was an unmetered (and unbilled) 16kbit
channel that could be used to send packets to other ISDN subscribers. I
wonder if ISDN had been marketed earlier, what kinds of services would
have popped up on the "D" channels.
Of course, bandwidth is so cheap and plentiful nowadays that people are
getting 4K video from services over the Net. Back at the campus in the
early 90's, we were happy to be getting a weekly broadcast in the form of
a Sun .au file -- Internet Talk Radio Geek of the Week. And indeed, they
are still up on the net:
http://town.hall.org/radio/Geek/
Today, grabbing one of those files is barely a blip on the radar, but at
the time, it took several minutes to download a fresh show. There were
other folks on-campus interested in listening, but who didn't have sound
on their computers -- so we wired up a multimedia computer in the machine
room to the phone system, so that we could conference in anyone who
wanted to listen, and play the files at a set time.
Wiring the campus for Internet was its own challenge. We ran fiber to a
lot of buildings, but a lot of that was initially for Netware services.
Getting folks to sign off on putting drivers that would enable TCP/IP was
harder than it might sound at first, because lab directors were quite
interested in ensuring their systems were stable. If I'm not mistaken,
we ended up using a particular Crynwr packet driver that would interface
with ODI. I'm sure you remember the fun we had getting the right network
stack drivers loaded on DOS machines, requiring entries in CONFIG.SYS and
AUTOEXEC.BAT. (This was even more of a problem on our campus, because
some users had to be able to talk to the campus HP3000 mainframe, which
_didn't_ use TCP/IP for their purposes. They used a terminal program
called "Reflection".)
In fact, that got to be a problem later, when we wanted real-time access
to the class schedule to be on the Net. The way we worked around that
was this: the web server ran on a Linux box, which connected to the
library's HP9000, which had the capability to connect to the campus
mainframe (an HP3000) through its own peculiar terminal services. It
would make that connection, log in to the HP3000, then run a program to
spit out the data for the sections which was then html-entabulated by the
cgi-bin running on the Linux box. Talk about "middleware"!
Anyway, that's my "green screen war stories" for now. I'm adding
ba.internet to the newsgroups line because I think the old timers there
would get a kick out of talking about Internet before the dot.bomb crash
of 2001...
--
-v
-v