How (and why) to Ramble on your goat sideways
#2981
Boost Pope
iTrader: (8)
Join Date: Sep 2005
Location: Chicago. (The less-murder part.)
Posts: 33,020
Total Cats: 6,588
Yeah, and the scary part is, all that test illustrates is that I'd maxed out the 100 megabit ethernet connection of the particular PC that I happened to be sitting at. The actual pipe out to the backbone proper has got to be many orders of magnitude faster than that.
(Remember when a T1 was considered the ultimate in hot-**** connectivity? This is seventy times faster, and it's just some random PC in an office somewhere.)
Hell, I remember when I was living in the dorm at UF in 1995, and we had run a couple of a 4800 baud serial lines up to the rooms from a termserver we found in the basement that was connected to the campus ring. That was just the awesomest **** imaginable, since it was a direct, always-on connection to the mainframe with no modem involved.
Oh, how times change.
(Remember when a T1 was considered the ultimate in hot-**** connectivity? This is seventy times faster, and it's just some random PC in an office somewhere.)
Hell, I remember when I was living in the dorm at UF in 1995, and we had run a couple of a 4800 baud serial lines up to the rooms from a termserver we found in the basement that was connected to the campus ring. That was just the awesomest **** imaginable, since it was a direct, always-on connection to the mainframe with no modem involved.
Oh, how times change.
#2984
Boost Pope
iTrader: (8)
Join Date: Sep 2005
Location: Chicago. (The less-murder part.)
Posts: 33,020
Total Cats: 6,588
Well, I also owned a then-new 14.4 modem, however the 4800 baud ports were greatly advantageous. At first, we merely pulled one to each dorm room, and everybody used whatever terminal software they had to access a shell connection. (One guy had an actual DEC VT-220 terminal on his desk.) Since the connection was very reliable and always on, it didn't matter if downloads took longer, you could simply the queue them up and let them run overnight.
Remember, back then, internet access was a two-step process. You dialed up a server and were presented with a shell, and then ran your applications such as Pine or Lynx on the server itself, doing everything in 80x25 text mode. So if you wanted to download a file from Usenet, first you downloaded it from the internet to the server, and then you'd use Kermit or Xmodem to download it from the server to your actual PC.
Later, we consolidated all the ports into a single room, and hooked them up to Mauricio's computer, which was running Linux (which, at that time, was brand-new.) We then pulled RG-58 coax through the ceiling to all the rooms, and bought ourselves 10 megabit ethernet cards (which, back then, were both very expensive and fairly rare) and networked all the PCs on the floor together. We compiled a copy of TIA and left it running on the VAX at all times, directed to the ports which were tied to Mo's Linux machine, which in turn used SLIP to create a tunneled TCP/IP connection. By that point, most of us had upgraded to Windows 3.1 or Win 95, so we used Winsock to connect our machines to Mo's server, and Viola! We had TCP/IP connections right on our desktop, with a total bandwidth of up to 28,800 baud, depending on who else was using the connection!
(This was a hell of a cool thing in 1995.)
The ethernet network also had another use. The first of the multiplayer FPS games such as Doom II and Rise of the Triad had just come out, so using Novell IPX/SPX, we were able to run multiplayer deathmatch games, which frequently went on until sunrise.
Remember, back then, internet access was a two-step process. You dialed up a server and were presented with a shell, and then ran your applications such as Pine or Lynx on the server itself, doing everything in 80x25 text mode. So if you wanted to download a file from Usenet, first you downloaded it from the internet to the server, and then you'd use Kermit or Xmodem to download it from the server to your actual PC.
Later, we consolidated all the ports into a single room, and hooked them up to Mauricio's computer, which was running Linux (which, at that time, was brand-new.) We then pulled RG-58 coax through the ceiling to all the rooms, and bought ourselves 10 megabit ethernet cards (which, back then, were both very expensive and fairly rare) and networked all the PCs on the floor together. We compiled a copy of TIA and left it running on the VAX at all times, directed to the ports which were tied to Mo's Linux machine, which in turn used SLIP to create a tunneled TCP/IP connection. By that point, most of us had upgraded to Windows 3.1 or Win 95, so we used Winsock to connect our machines to Mo's server, and Viola! We had TCP/IP connections right on our desktop, with a total bandwidth of up to 28,800 baud, depending on who else was using the connection!
(This was a hell of a cool thing in 1995.)
The ethernet network also had another use. The first of the multiplayer FPS games such as Doom II and Rise of the Triad had just come out, so using Novell IPX/SPX, we were able to run multiplayer deathmatch games, which frequently went on until sunrise.
#2991
Elite Member
iTrader: (10)
Join Date: Jun 2006
Location: Athens, Greece
Posts: 5,976
Total Cats: 355
Then the scripted connections came and we all rejoiced.
The KDE and kppp arrived and we rejoiced even more.
#2992
Boost Pope
iTrader: (8)
Join Date: Sep 2005
Location: Chicago. (The less-murder part.)
Posts: 33,020
Total Cats: 6,588
I had to do a little research to support my assertion here, but the use of "Random" in this context is well-established, and predates my own existence on the earth by at least a decade.
J. Random Hacker:
[very common] A mythical figure like the Unknown Soldier; the archetypal hacker nerd. This term is one of the oldest in the jargon, apparently going back to MIT in the 1960s. See random, Suzie COBOL. This may originally have been inspired by ‘J. Fred Muggs’, a show-biz chimpanzee whose name was a household word back in the early days of TMRC, and was probably influenced by ‘J. Presper Eckert’ (one of the co-inventors of the electronic computer.)
Source: The New Hacker's Dictionary (J. Random Hacker)
and[very common] A mythical figure like the Unknown Soldier; the archetypal hacker nerd. This term is one of the oldest in the jargon, apparently going back to MIT in the 1960s. See random, Suzie COBOL. This may originally have been inspired by ‘J. Fred Muggs’, a show-biz chimpanzee whose name was a household word back in the early days of TMRC, and was probably influenced by ‘J. Presper Eckert’ (one of the co-inventors of the electronic computer.)
Source: The New Hacker's Dictionary (J. Random Hacker)
some random X: adj.
Used to indicate a member of class X, with the implication that Xs are interchangeable. “I think some random cracker tripped over the guest timeout last night.” See also J. Random.
Source: The New Hacker's Dictionary (some random X)
Used to indicate a member of class X, with the implication that Xs are interchangeable. “I think some random cracker tripped over the guest timeout last night.” See also J. Random.
Source: The New Hacker's Dictionary (some random X)
#2995
Motor Swap FAIL
This would suck so bad, how could some one be this dumb? Lol, the guys laugh is actually just as funny!
http://www.streetfire.net/video/moto...il_2048702.htm
http://www.streetfire.net/video/moto...il_2048702.htm