Slashdot Mirror


30 Years of Ethernet

Babylon Rocker writes "An interview with one of the inventors of Ethernet." Metcalfe talks about the history of Ethernet as well as what he's been up to for the last couple years. (Not surprisingly, he's now a VC ;)

206 comments

  1. fp! by ciroknight · · Score: 1, Offtopic

    w00t!!, now for the serious side.. Ethernet is awesome, but I'm already tired of it. I can't wait to sit back and see what happens with 802.11(alphanumeric character) 30 years down the line.

    --
    "Victory means exit strategy, and it's important for the President to explain to us what the exit strategy is." G.W.Bush
  2. Maybe I'm Dumb by n8 · · Score: 1, Insightful

    What's VC stand for?

    I read the article and still don't quite get it

    1. Re:Maybe I'm Dumb by symbols · · Score: 1

      Not a venture capitalist.

    2. Re:Maybe I'm Dumb by gwernol · · Score: 5, Informative

      What's VC stand for?

      Venture Capitalist. People and institutions invest large sums of money into the funds run by his partnership. He then decides how to invest that money in other companies - usually high tech. startups. Its risky but potentially high reward, depending on how successful the companies he invests in become.

      --
      Sailing over the event horizon
    3. Re:Maybe I'm Dumb by GMontag · · Score: 4, Funny

      Apparently the old adage "A fool and his money are soon venture capital" does not apply here :-)

    4. Re:Maybe I'm Dumb by Beowulf_Boy · · Score: 5, Funny

      VietCong

    5. Re:Maybe I'm Dumb by Roelof · · Score: 2, Funny

      Ventriloquist Cheater

    6. Re:Maybe I'm Dumb by identity0 · · Score: 1

      "Charlie in the wire! Charlie in the wire! Get the machinegun, we-oh, never mind, it's only Bob."

    7. Re:Maybe I'm Dumb by silicon1 · · Score: 1

      ya I thought he was a vietcong or something.

    8. Re:Maybe I'm Dumb by Stonent1 · · Score: 1

      What's VC stand for?

      Victor Charlie? (Viet Cong)
      Perhaps not.

    9. Re:Maybe I'm Dumb by fm6 · · Score: 1
      VietCong. Metcalfe fought on the other side during the VietNam war. Why he's never been arrested is beyond me.

      Other definitions appear on the net, but none of them make any sense!

    10. Re:Maybe I'm Dumb by ozzee · · Score: 3, Funny
      What's VC stand for?

      vulture capitalist

    11. Re:Maybe I'm Dumb by bakes · · Score: 1

      I've also heard a VC referred to as a 'Vulture Capitalist'.

      --
      Ho! Haha! Guard! Turn! Parry! Dodge! Spin! Ha! Thrust!
    12. Re:Maybe I'm Dumb by fyonn · · Score: 1

      I've always preferred "a fool and his money are soon partying"

      dave

  3. 30 years of internet... by Znonymous+Coward · · Score: 3, Funny

    Does anyone have BitTorrent for the past 30 years of the internet? I really need it. Thanks!

    --

    Karma: The shiznight, mostly because I am the Drizzle.

    1. Re:30 years of internet... by b1t+r0t · · Score: 1

      I finished it already. You can have my copy. It's only slightly dogeared on the corners.

      --

      --
      "Open source is good." - Steve Jobs
      "Open source is evil." - Microsoft
    2. Re:30 years of internet... by Anonymous Coward · · Score: 0
      Does anyone have BitTorrent for the past 30 years of the internet? I really need it. Thanks!

      Um, yeah, but some of the pages are kinda stuck together.

    3. Re:30 years of internet... by c4Ff3In3+4ddiC+ · · Score: 1

      Nice sig...

      And now, ladies and gentlemen! It's time to pass the lameness filter!

      --
      *twitch*
  4. Yay! by methangel · · Score: 2, Funny

    Happy Birthday Ethernet!! Hurray for Ethernet! May it live long and prosper, and my bandwidth never end.

  5. Bigmouth by Eric+Seppanen · · Score: 5, Informative

    Metcalfe has a habit of saying stupid things, I wonder why people keep listening to him. One great invention thirty years ago, paired with a huge ego, does not an oracle make.

    --
    314-15-9265
    1. Re:Bigmouth by Overly+Critical+Guy · · Score: 1, Insightful

      You have places like Slashdot to thank for continuing to give the guy any credence.

      --
      "Sufferin' succotash."
    2. Re:Bigmouth by Anonymous Coward · · Score: 1, Interesting
      Wow. That was stupid, allright. At the time, what he said about Linux was obviously wrong, and stupid. In hindsight, it REALLY looks dumb.

      On the other hand, look at what he said about Windows:

      W2K is software also from the distant past -- VAX/VMS for Windows. But it will overpower Linux. NT, now approaching 23x6 availability, is already overpowering Linux.
      Snip out the parts about Linux, and you get
      W2K is software also from the distant past -- VAX/VMS for Windows. NT, now approaching 23x6 availability, ...
      This was unkind to Windows, but not totally untrue. I like ``VAX/VMS for Windows''.
    3. Re:Bigmouth by GMontag · · Score: 0, Redundant

      When did he start calling himself Al Gore?

    4. Re:Bigmouth by OtisSnerd · · Score: 5, Funny
      One great invention thirty years ago, paired with a huge ego, does not an oracle make.

      Tell that to Larry Ellison.

      ---

      This sig intentionally left blank.

    5. Re:Bigmouth by TheSunborn · · Score: 1

      Well, he has not been proven wrong yet.

    6. Re:Bigmouth by Zork+the+Almighty · · Score: 1, Funny

      Don't you know ? The Internet invented Al Gore.

      --

      In Soviet America the banks rob you!
    7. Re:Bigmouth by rdewald · · Score: 3, Insightful

      You're right, he did say some stupid things and he totally doesn't get Open Source.

      He's brilliant, though. A very bright light. He didn't let the fact that no one could imagine the possibilities of Ethernet limit the scope of it's ultimate possibilities. Indeed, as discussed in this article, datagrams are "regarded" by Ethernet as equals. This is a fundamental principle and it is important.

      Maybe that kind of clarity limits his ability to appreciate the more value-laden social contract of Open Source. That's okay with me. The tent is big enough for Bon Metclfe as far as I am concerned. No matter how utterly I disagree with him on things for which we are all allowed opinions, I'm glad we all agree on how to deliver packets.

      --
      The best way to do is to be.
    8. Re:Bigmouth by Anonymous Coward · · Score: 0

      In Soviet Russia, the Internet invents YOU!

    9. Re:Bigmouth by Caligari · · Score: 5, Funny
      Damn straight. Anyone who makes such non-sensical, inflammatory comments as:

      "Stallman and Torvalds would have us return to the time when software was so new that one person working alone could change the world over the weekend. But modern software, [...] is more complicated than that."

      Should be ignored at all cost.

      --
      The moving cursor writes, and having written, blinks on.
    10. Re:Bigmouth by Anonymous Coward · · Score: 1, Insightful

      Linux is based on thirty year old technology, and it hasn't replaced Windows. He's right. You know it.

    11. Re:Bigmouth by EverDense · · Score: 1, Funny

      "they flip the collective finger at Bill Gates, the software Romanoff whom they'd like to trap in a basement somewhere."

      Surely Romanoff was not THAT BAD.

      --
      http://jesus.everdense.com/
    12. Re:Bigmouth by vegetablespork · · Score: 3, Funny

      No kidding. This is one of my favorites, in which he predicts the death of flat-rate pricing for Internet access. Which would, of course, mean the end of popular interest in the Internet. "The information's on your web site? That's nice, but I pay by the kilobit. Mail me a copy, please. Thank you."

      --

      Call (206) 338-5780 COLLECT for information about a genuine BA, BS, MA, MS, MBA, or Ph.D.

    13. Re:Bigmouth by SN74S181 · · Score: 1

      While Larry Ellision invented the concept of vaporware software marketing, that wasn't 30 years ago.

    14. Re:Bigmouth by Anonymous Coward · · Score: 0

      Maybe it's just my old browser, but clicking on the "Print Article" link goes into an infinite loop between www.infoworld.com, archive.infoworld.com, and staging.infoworld.com

      Whee! I think I'll let this run for a few hours.

    15. Re:Bigmouth by mike_sucks · · Score: 1

      That would have been better as: "In Soviet Russia, Al Gore invents YOU!"

      --
      -- "So, what's the deal with Auntie Gerschwitz et all?"
    16. Re:Bigmouth by Anonymous Coward · · Score: 0

      Tell that to Sean Fanning.

    17. Re:Bigmouth by ProfessionalCookie · · Score: 2, Funny

      Al Gore says all kinds of stupid things all the time...but he still invented the internet!!!

      (ducks & lowcrawls for cover)

    18. Re:Bigmouth by vistic · · Score: 3, Insightful
      "He's brilliant, though. A very bright light."

      But... the light that burns twice as bright burns half as long!

      How sad... :(
    19. Re:Bigmouth by Anonymous Coward · · Score: 0

      I'm on the board of Narad, which is trying to deliver 100 (megabytes per second) through the cable TV system. That's not 100 kilobytes, but 100 megabytes. Sometimes we call that true broadband, as opposed to what they're now selling.

      100 megabytes per second... so like 800 Mbps... a bit faster than an OC-12.

      WOW! were do I sign up? do I have to pay for S&H
      on the $100Mbillion CPE?

    20. Re:Bigmouth by mcrbids · · Score: 4, Interesting

      An interesting quote from your linked to story:

      Why do I think Linux won't kill Windows? Two reasons. The Open Source Movement's ideology is utopian balderdash. And Linux is 30-year-old technology.

      Name a single networking infrastructure used more commonly than the 30-year-old ethernet!

      Why does this seem ironic to me?

      --
      I have no problem with your religion until you decide it's reason to deprive others of the truth.
    21. Re:Bigmouth by JohnFluxx · · Score: 1

      Well how on earth do you disprove "X will collapse" ? Since if X hasn't collapsed yet, it still might even further in the future..

    22. Re:Bigmouth by JohnFluxx · · Score: 1

      I rather liked "At least they're not bombing Redmond. Not yet anyway."

    23. Re:Bigmouth by fyonn · · Score: 1

      in this particular interview, I'd say that the interviewer wasn't particularly clued up.

      bob talks about his "ethernet business model" and goes on to say:

      It's based on de jure standards with proprietary implementations of those de jure standards, and it is unlike open source in that competitors don't give their intellectual property away. The competition is fierce, but there is a market ethic that products will be interoperable. And the standard evolves rapidly based on market engagement in such a way to value the installed base. There is a heavy value placed on sustaining and maintaining the installed base. That's the Ethernet business model.

      which is fair enough, whether people beleive him or not is another matter but I think he's making a valid point. then the interview asks:

      So does that have to do specifically with businesses that work with Ethernet technologies?

      what? was he even listening to bob? it reminds me of "handsome dan" interviewing wayne an garth about waynestock... "yeah, uhuh, yeah, right. groovey" etcetc.

      dave

    24. Re:Bigmouth by Shimbo · · Score: 1

      You're right, he did say some stupid things and he totally doesn't get Open Source.

      So, Windows 2000 didn't steamroller Linux out of existance. Still, who looks more foolish: Metcalfe for saying that, or the well-known Open Source proponent who predicted that W2K would never ship?

      Metcalfe has a good point: that open source is only essential when manufacturers don't play by the rules. Metcalfe's Law, which predicts that the winners are those who promote interoperability is important in understanding the success of Ethernet and the Internet as a whole.

    25. Re:Bigmouth by evilviper · · Score: 1

      I hate to tell you, but saying that RMS is naieve and lost in a dream world is NOT a stupid thing to say.

      He is VERY correct that a world with nothing but Free Software (as RMS advocates) is ridiculous, and just about all programmers will agree with me. It's not unconcievable that Open Source apps will be popular, but I don't believe Metcalfe was claiming that, I believe he was saying that there still need to be commercial software companies, and I agree completely. If he can be faulted for one thing, it's mixing up the terms Linux and Open Source for "Free Software", and for over-dramatizing the issue.

      A poster on this thread wished to help you by posting an article about how the internet should be metered, rather than flat-rate. It is quite true as a matter of fact. BlueLight internet service provided the statistic that 2% of users eat up 50% of the resources. With that in mind, it's not inconcievable that 98% of users would WANT to be billed only for the resources they use (within a certain range, let's say), because it would result in their performance being better, their ISP providing better service, and their prices being FAR lower.

      In fact, this same argument applies to federal health-care plans... I don't want to pay several times as much money for health care for the sake of a few individuals who are abusing the system. I could use the same argument against auto insurance... etc.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  6. TCP/IP by ciroknight · · Score: 2, Interesting

    Wait... if Ethernet has been around 30 years, that makes TCP/IP PRETTY DAMN OLD!!!!! Anyone up for re-inventing the wheel??? Maybe someone can make a protocol in which practically any piece of information can be traded, with a special way to commit a special pipeline to different medias (such as movie/music downloads getting a compressed, special set of ports used just for that purpose..).
    Next thing you know, the teleco's will be bringing up charges against us for inventing a better internet... when will this end!?!
    OR OR Or......... Maybe I'm delusional...

    --
    "Victory means exit strategy, and it's important for the President to explain to us what the exit strategy is." G.W.Bush
    1. Re:TCP/IP by Baron_911 · · Score: 1

      Yeah, it should be goin out of style like those damn COBOL programmers...

      --
      Polaroid. See what develops!!
    2. Re:TCP/IP by redcane · · Score: 2, Insightful

      TCP/IP doesn't have to be as old as ethernet. It's not the only protocol you can run on ethernet. Although I beleive TCP/IP is quite some years old.

    3. Re:TCP/IP by UserGoogol · · Score: 1

      I think it might be younger. I think the internet switched to TCP/IP around 1983.

      I'm tempted to reinvent the wheel, but first I have to fully grok "torque."

      --
      "Never attribute to malice that which can be adequately explained by stupidity." -- Hanlon's Razor
    4. Re:TCP/IP by ciroknight · · Score: 1

      didn't say it was as old, just that it's older than me ;)
      and yeah, you can use different protocols on the internet.. but who does? yeah UDP has some following, but not NEARLY as much as tcp/ip. fact is just that it's good, I'm just askin if anyone's given any though at the new TCP/IP, a better one, expanded beyond the original's specs, that can do more for us.

      --
      "Victory means exit strategy, and it's important for the President to explain to us what the exit strategy is." G.W.Bush
    5. Re:TCP/IP by Ark42 · · Score: 1

      You realize that UDP is really UDP/IP. By other protocols over ethernet, people probably mean IPX or vines and such.

    6. Re:TCP/IP by spaceyhackerlady · · Score: 4, Interesting
      I think it might be younger. I think the internet switched to TCP/IP around 1983.

      One indicator of this is that the relevant RFCs (791 and 793) are dated in 1981. At the time there were all kinds of long-haul data links, and lots of short-haul stuff too. I remember the University where I was an undergrad developing their own network to connect terminals to mainframes. Then they added X.25 capability so you could talk to people in other places (and boy was it expensive!). Then they hooked it up to the Internet. Then they ditched it completely, but not before several hacks to hook those new-fangled PCs up to it. At the time I considered myself fortunate to have a 9600 baud SLIP link.

      It's clear from the earliest RFCs that people really didn't know what computer networking was going to look like, and were making it up as they went along. People were certainly networking computers prior to the final form of TCP/IP; just that the present implementation of TCP/IP gelled the same year MTV went on the air.

      ...laura

    7. Re:TCP/IP by Anonymous Coward · · Score: 3, Insightful

      Ah you whippersnappers. Xerox used a proprietary data frame called LLC. Later recycled as Microsoft NETBui's transport frame. Used to have to pay 100 bucks per pc to run tcp on ethernet. It wasn't obvious that IP was the one protocol to rule them all until about 1995-96. And the real killer app in this direction was Windows 95s decent IP stack which killed Novells IPX slowly.

    8. Re:TCP/IP by bluGill · · Score: 2, Interesting

      I've seen several different protocols that can be used over IP in actual use. Most were only used for specific applications. Generally bulk mainframe data transfers. TCP and UDP supply just about everything you could want though. The other protocols I mentioned could be implimented over UDP just as easially if anyone cared to. (Not TCP though, slow start and a few other network nice things are specificly not wanted - they assume the network bandwidth is fot one application)

    9. Re:TCP/IP by Istealmymusic · · Score: 1
      The other protocols I mentioned could be implimented over UDP just as easially if anyone cared to.
      This is unnecessary. You can make your own transport layer protocol and send it over IP with no problems -- ICMP is just that.
      --
      "The lesson to be learned is not to take the comments on slashdot too literally." --Vinnie Falco, BearShare
    10. Re:TCP/IP by rootofevil · · Score: 1

      nah - leave reinventing the wheel to microsoft. and stealing the spokes, and the tire, and the axel.

      --
      turn up the jukebox and tell me a lie
    11. Re:TCP/IP by nuintari · · Score: 1

      Your pairing them off inncorrectly. its not tcp/ip and udp and they are totally unrelated. ip contains both tcp and udp, both are members of the same family, and both are very important. Anything that needs to be done fast, like multiplayer games, uses udp over ip extensively.

      So, you don't have this camp of people who swear by tcp over udp all the time, because anyone who writes stuff to run over ip knows that some stuff demands one or the other, its not a preference issue as you seem to believe.

      --

      --Nuintari

      slashdot : where an opinion can be wrong.

    12. Re:TCP/IP by Alien+Being · · Score: 1

      Are you sure you don't mean XNS?

    13. Re:TCP/IP by Muad'Dave · · Score: 2, Informative

      Uh, UDP is a member of the TCP/IP suite of protocols (ethernet protocol number 0800). So is ICMP. ARP (number 0806), however, is not. As far as protocols _over ethernet_, see this list of assigned protocol numbers over ethernet.

      Protocols within TCP/IP are assigned numbers as well. See this list of IPv4 protocol numbers for more info. TCP packets are tagged as IP protocol 6, UDP are protocol 17, ICMP are protocol 1, etc. They are all ethernet protocol 0800, however.

      Clear as mud?

      --
      Tiller's Rule: Never use a word in written form that you've only heard and never read. You will end up looking foolish.
    14. Re:TCP/IP by bluGill · · Score: 1

      Re-read my post. I said that I've seen protocols implimented over IP, at the same layer as UDP, TCP, or ICMP, but not using any of them. Then I went on to point out that they could have been implimented over UDP.

  7. VP by PtM2300 · · Score: 1, Funny

    VP=venture capitalist

  8. 30 Years of frustration by Malicious · · Score: 4, Funny

    Wow, it's been 30 years already, and i *still* haven't managed to get my mitts on a set of RJ45 crimpers...

    --
    01101001001000000110000101101101001000000110001001 10000101110100011011010110000101101110
    1. Re:30 Years of frustration by Anonymous Coward · · Score: 2, Funny

      RJ45? It's been 30 years and I still haven't managed to get myself the proper wires to set up a vampire tap.

    2. Re:30 Years of frustration by Ark42 · · Score: 1

      Has RJ45/cat5 really been around 30 years? I remember thinnet being very widely used not THAT long ago..

    3. Re:30 Years of frustration by fm6 · · Score: 1
      It's funny. My nephew wanted to network his house. I've never done anything like that but I knew what was involved. So I naively said, "OK, let's go down to CompUSA, get some Cat5, some rj45 connectors, and a crimper." CompUSA had the cable and the connectors, but no crimpers! We went down the street to a Radio Shack, which had crimpers and cable, but the cable wasn't pre-packaged, and the clerks were clueless as to how to sell it. They had connectors too, but they were absurdly expensive.

      Is there an IQ ceiling on electronics retailing or what?

    4. Re:30 Years of frustration by Juanvaldes · · Score: 2, Informative

      Is there an IQ ceiling on electronics retailing or what?
      Yes. I've had clerks at Frys walk out of the isle that has what I was looking for and tell me he thought it was across the store.

    5. Re:30 Years of frustration by bluGill · · Score: 4, Informative

      RJ-45 wasn't used for ethernet 30 years ago. Back then it was 10base5 (for 500 meters max cable length), or thicknet. A thick cable (that I have never seen) running thorugh the ceiling, and a AUI cable running from your computer to a tranciever in the cable. AUI is that 15 pin connector (like a pc joystick connector, but a slide holds the cable on not screws or luck) on the back of many older computers. Mostly if you see it there is a 10baseT tranciever connected to it today.

      Sometime latter "thinnet" came out, or 10base2 (200 meter cable), which was a much thinner cable, and much cheaper. It is still cheaper than twisted pair for small instalations. Though almost everyone is using twisted pair because it is easier and more reliable.

      I don't know exactly when 10BaseT with the rj-45 connectors came onto the scene, but it started catching on in the early 90s.

    6. Re:30 Years of frustration by fm6 · · Score: 0

      Hey, let's distinguish between stupidity and catatonia!

    7. Re:30 Years of frustration by b1t+r0t · · Score: 4, Informative

      You forgot the best part of 10base5... the vampire taps! In order to hook up to thicknet, you have to stick a vampire tap into the coax cable, and that was hooked up through the appropriate interface box to the AUI connector.

      --

      --
      "Open source is good." - Steve Jobs
      "Open source is evil." - Microsoft
    8. Re:30 Years of frustration by Marillion · · Score: 1

      I remember seeing a room where two THICK cables, thick as your thumbs, came together at a brick sized boxed that proudly proclaimed itself as a bridge. The left was simply labled "South Campus." The right was "North Campus."
      The connector (I forget the name, but think of BNC on steroids) was applied to the cable in two parts the first part pierced the solid sheath so the second part so make contact with the inner core.
      Ahhh
      You know, Nastalgia just isn't what it used to be.

      --
      This is a boring sig
    9. Re:30 Years of frustration by Dr+Caleb · · Score: 3, Funny
      30 years with an Ethernet and I still haven't caught my Ether Bunny.

      Thit

      --
      "History doesn't repeat itself, but it does rhyme." Mark Twain
    10. Re:30 Years of frustration by sogoodsofarsowhat · · Score: 1

      Its was refered to as 'Frozen Garden Hose'. Mainly due to their similar flexibility :)

      --
      . I love the sound of burning women and screaming rubber....
    11. Re:30 Years of frustration by hatmouse · · Score: 1

      I still have my cable boring tools and step ladder, maybe I should clean the garage.

    12. Re:30 Years of frustration by Anonymous Coward · · Score: 0

      I used to work at Radioshack. I'm Cisco certified, and I wouldn't have a clue how to sell the cat5 cable or even if we had it. Really, RS lackies nowadays are only a shell of what they once were. You don't even have to know how to spell 'electronics' to work there now.

      Go to school kids, or you'll end up hawking cell phones at RS.

    13. Re:30 Years of frustration by Anonymous Coward · · Score: 0

      'thinnet' may be cheaper, but it sucked then and sucks now.

      I used to have to troubleshoot those all the time, and finding which connector was flaky was a pain in the rear, especially if they used the amp drop-tap stuff.

      Just like a set of Christmas tree lights, one machine has the ability to take the entire loop out.

      Better than arcnet though; at least you didn't have dip switches for setting MAC addresses, along with all of the above problems :-)

    14. Re:30 Years of frustration by hirschma · · Score: 1

      Wow, people actually remember this stuff...

      Vampire taps were actually a newer development. The original Xerox equipment required you to DRILL into the 10base5 cable. The vampire taps eventually just pierced the "frozen yellow hose" when you clamped them on. That was a huge improvement.

      Thinnet, or "cheapernet", did in fact suck. Although I disagree on the reliability and usefulness of AMP drop taps - those were great for the time, and allowed a network to stay up through disconnects.

      Then 10baseT came out around '91/'92, I think, and the switches followed. The first switches allowed 1 MAC address per port (the brand was Kalpana), so 48 port and 96 port switches were common.

      Finally, the second gen switches ('93?) allowed multiple MACs per port, allowing you to really use them for backbones... but we had to use FDDI for 100mb to servers...oh the memories.

      jonathan

    15. Re:30 Years of frustration by Alioth · · Score: 1

      "Yellow Peril" was another nickname.

    16. Re:30 Years of frustration by Muad'Dave · · Score: 3, Insightful
      Do you remember:
      • Running that huge 15-conductor AUI cable up into the ceiling and across the room to get to the coaxial cable (up to 50m!)?
      • The 1 meter marks that limited how many taps you could get on the piece of coax that traversed your office?
      • Drilling (yes, drilling!) a friggin' hole in the coax, getting little bits of shield shorting it out, causing the whole segment to die?
      • Those manly N connectors?
      • Swooping on left-over bits of coax to use for you ham station (it was 50 ohm cable, after all!)
      • The relief you felt when 10Base-2 came out (thinnet, using RG-58 and BNC connectors).
      • The uber-relief you felt when 10Base-T came out.

      Those were the days!

      --
      Tiller's Rule: Never use a word in written form that you've only heard and never read. You will end up looking foolish.
  9. What VC stands for by jamie · · Score: 2, Informative
    From the article:

    You're now working as a venture capitalist.

    My business is technology innovation, and my fourth career in that business is as a VC.

  10. Congrats, folks... by Anonymous Coward · · Score: 0

    You guys just slashdotted C|Net.

  11. Good Wired Article by R33MSpec · · Score: 5, Interesting

    An interesting but old article on wired about Metcalfe here: The Legend of Bob Metcalfe

  12. a VC? by Anonymous Coward · · Score: 1, Funny

    He joined the Vietcong? That's pretty suprising!

    Well they do say vietnam is a beautiful country now that American invaders aren't trying ton bomb into the stone age and kill everyone who doesn't dig bigmacs...

  13. The world without Ethernet by axxackall · · Score: 0
    I wonder what would be the world without Ethernet? Would Internet begin and survive just on UUCP/SLIP/PPP?

    Basically, how much really should we thank the guy?

    --

    Less is more !
    1. Re:The world without Ethernet by InterruptDescriptorT · · Score: 1, Insightful

      Would you rather be stuck with Token Ring?

      I mean, IBM is a great innovator to be sure. But token ring, IMHO, was one of their great misses. Running at 4 or 16 Mbit, it was certainly speedy for its day, but the protocol to implement it is hellish, not to mention the extra hardware to make it work. It's really much more involved than the plug-'n-play 10baseT that we've all gotten used to with the dominance of Ethernet.

      I'm sure you've heard the joke--Why are you all on the floor? Someone pulled out the network cable and we're looking for the token. Anyway network topology that relies on peers to propagate a piece of information to its neighbour is doomed to failure.

      --
      Karma: Excellent Birds (mostly as a result of listening to Laurie Anderson)
    2. Re:The world without Ethernet by Anonymous Coward · · Score: 0

      2 words:

      token ring

    3. Re:The world without Ethernet by Anonymous Coward · · Score: 0

      Running at 4 or 16 Mbit

      Wasnt there a 100 Mbit token ring that runs on fiber? I assume there would be the Gb+ speeds now if token ring hadn't died off.

      but the protocol to implement it is hellish

      Hellish? if (have_token) { send_packet; }

      not to mention the extra hardware to make it work.

      Extra hardware? You mean like a nic?

      really much more involved than the plug-'n-play 10baseT that we've all gotten used to with the dominance of Ethernet.

      No, it really wasn't.

    4. Re:The world without Ethernet by cygnus · · Score: 1
      Anyway network topology that relies on peers to propagate a piece of information to its neighbour is doomed to failure.
      yeah, like Limewire, Gnutella, Kazaa, etc. etc. ;-)
      --
      Just raise the taxes on crack.
    5. Re:The world without Ethernet by euxneks · · Score: 1

      Anyway network topology that relies on peers to propagate a piece of information to its neighbour is doomed to failure

      That's not what the RIAA would have you believe!

      --
      in girum imus nocte et consumimur igni
    6. Re:The world without Ethernet by Anonymous Coward · · Score: 0

      Keep your mouth shut and your ears open. You don't know what you are talking about.

    7. Re:The world without Ethernet by Istealmymusic · · Score: 1
      How convenient of you to omit the most pungent statement of the grandparent:
      I'm sure you've heard the joke--Why are you all on the floor? Someone pulled out the network cable and we're looking for the token. Anyway network topology that relies on peers to propagate a piece of information to its neighbour is doomed to failure.
      This is why is a failure. Not because of its speeds (4 Mbps, 6 Mbps, 100 Mbps).
      Hellish? if (have_token) { send_packet; }
      This is not all required to implement Token Ring. You conveniently omitted the token passing.
      --
      "The lesson to be learned is not to take the comments on slashdot too literally." --Vinnie Falco, BearShare
    8. Re:The world without Ethernet by GlassHeart · · Score: 1
      extra hardware to make [token ring] work

      Sorry, what extra hardware are you referring to?

      It's really much more involved than the plug-'n-play 10baseT that we've all gotten used to with the dominance of Ethernet.

      10BaseT also required extra hardware, in the form of a hub or switch. Unswitched ethernet is also susceptible to many similar problems, such as a single broken or malicious node that won't stop transmitting. Older readers may remember how expensive ethernet switches were, which is why some sites were forced to deal with the nightmare that is 10Base2.

    9. Re:The world without Ethernet by tmasssey · · Score: 5, Informative
      You're kidding me, right?

      Before 1993 or so and the advent of Switched Ethernet, Ethernet would melt down under the weight of its own traffic. 40% traffic for Ethernet is an emergency situation. I've seen TR networks hum along with 80-90% utilization and the users barely know.

      Token Ring has built-in QoS. It has several levels of error monitors. These are things that are kind of added by switches, but are not a fundamental part of the topology. And if you don't have a *good* switch, you don't even have that.

      Of course, in the early 90's Ethernet cards were under $100 and Token Ring cards were $400. *That's* why Ethernet won. Not speed: TR was doing 16MBit when Ethernet could only do 10, and remember, I can acually *get* 16Mbit from TR, instead of 4Mbit with Ethernet. Today, with good switches, I don't miss TR too much. But before switches...

      Maybe that's why many, many very large organizations were using TR even into the early '90's. Try running 300 computers on unswiched 10Mbit Ethernet (the best Ethernet had then)...

    10. Re:The world without Ethernet by PS-SCUD · · Score: 1

      "Would you rather be stuck with Token Ring?"

      Ya, just look at what happened to Frodo!

      --


      "Much work is lost, for the lack of a little more." -Edward H. Harriman
    11. Re:The world without Ethernet by b1t+r0t · · Score: 1
      Token passing... is that anything like passing gas?

      Admittedly, as Token Ring was dying, people were finally making the Token Ring equivalent of an Ethernet switch, with each port a ring unto itself, but by then it was way too late.

      As for the speeds, I've only ever heard of 4 and 16 Mbps. I'm sure that there are optical protocols that pass tokens, but they're not Token Ring [tm].

      --

      --
      "Open source is good." - Steve Jobs
      "Open source is evil." - Microsoft
    12. Re:The world without Ethernet by Anonymous Coward · · Score: 0

      That's tolkien, silly weasel.

    13. Re:The world without Ethernet by Warphammer · · Score: 1

      Token passing in TR was pretty basic. The token travelled the electrical ring and each node passed it through. If the node had a packet waiting for transmit, it listened for the bit (actually a pair of Manchester encoding violations, IIRC) that indicated the current packet was a token and converted the violations into valid bits, essentially stripping the token and turning it into a data frame. Now there were other complexities like having a master station and error recovery, but the basics were pretty simple.

    14. Re:The world without Ethernet by Ungrounded+Lightning · · Score: 2, Informative

      I wonder what would be the world without Ethernet? Would Internet begin and survive just on UUCP/SLIP/PPP?

      Would you rather be stuck with Token Ring?

      I mean, IBM is a great innovator to be sure. But token ring, IMHO, was one of their great misses.


      There's token rings and there's token rings. Saying "Token Ring" when you mean "IBM's Token Ring" is like saying "DOS" when you mean "Microsoft's Disk Operating System".

      My guess is that, in the absense of the invention of Ethernet's listen/transmit/back off on collision model, we'd have bootstrapped up from Datapoint's ARCnet.

      Like IBM's protocol, ARCnet is also a token ring. But unlike IBM, ARCnet's transport layer is broadcast. So it combines the self-healing characteristics of Ethernet with the delivery-time and latency guarantees of token rings.

      ARCnet did have a downside - limited number of addresses on a segment. But there are ways around that. (My favorite is my own variant which I call "bumblenet", involving an aborted binary search for the next station to get the token.)

      But for radio, Ethernet-like low-level protocols have a distinct advantage over token rings: They suffer less from the "hidden transmitter" issue - where some devices can hear each other and others can't.

      Ethernet-like protocols get their packet through if the transmitter and receiver can hear each other and nobody else within their earshot is talking. So a pair of stations on THIS side of the hill can swap a packet at the same time a pair of stations on the OTHER side are swapping one, without explicitly negotiating about it over relays through other stations - or even knowning about stations on the other side of the hill.

      Token rings can work around a hill - even if you have a sparse chain of stations where each can only hear two neighbors. But there's a lot more effort involved. They only get simple when either everybody hears everybody else or everybody talks to exactly two neighbors in a closed ring.

      --
      Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
    15. Re:The world without Ethernet by duffbeer703 · · Score: 1

      Whopptie-doo.

      Beta was better than VHS, MicroChannel was better than ISA.

      The problem with token ring was that it was a proprietary technology hocked by IBM. If you aren't a large government or corporate entity, IBM doesn't give a shit about you.

      --
      Conformity is the jailer of freedom and enemy of growth. -JFK
    16. Re:The world without Ethernet by Anonymous Coward · · Score: 0

      Irrelevant.

      The discussion is not that token ring is better so it should be used instead of ethernet. The discussion is whether or not token ring was a mistake of a technology.

      Pay attention.

    17. Re:The world without Ethernet by nuintari · · Score: 1

      You really don't believe the entire internet runs on one giant ethernet network do you?

      This is why I hate being a network junky, anyone who owns a ethernet hub and some cable and plays counterstrike over their home network believes they are a networking genius because they know all there is to know about the one and only networking protocal.

      So no, don't thank him to much, without ethernet, we'd just use something else for cheap, efficient LAN's, vaccums tend to be filled.

      --

      --Nuintari

      slashdot : where an opinion can be wrong.

    18. Re:The world without Ethernet by Muad'Dave · · Score: 1

      Issues of load-based meltdown aside, token ring has one property that ethernet does not - token ring is deterministic with regard to delivery time. When you're writing B-52H simulator code, you _really_ want your frames to get there on time, every time. (where a few milliseconds late means glitchy flight).

      --
      Tiller's Rule: Never use a word in written form that you've only heard and never read. You will end up looking foolish.
    19. Re:The world without Ethernet by John+Harrison · · Score: 1
      Maybe that's why many, many very large organizations were using TR even into the early '90's.

      My home office is going to remove the token ring network next month.

    20. Re:The world without Ethernet by tmasssey · · Score: 1
      We *still* have clients using TR! Most of them are just waiting for the devices (usually embedded into expensive pieces of equipment) to die before they rip out that last bit of TR. One of them still has their 1000-computer network running TR, with an ATM backbone and connections to servers (155Mb and up!).

      They've even tried migrating to Ethernet. They will switch a division from time to time, but they've found that Ethernet actually costs them more: they have to buy new Ethernet switches compared to the cost of continuing with TR (which for them is near zero, with an inventory of 100Mb cards and CAU's already purchased), and it buys them pretty much nothing. So until there's an actual reason to, they're staying TR...

  14. Stupid is as stupid does by fm6 · · Score: 1, Insightful

    If you're a "free software" true believer, I guess that column must irritate. But I don't see anything stupid about it. Care to get specific?

    1. Re:Stupid is as stupid does by Anonymous Coward · · Score: 2, Insightful

      Um. The fact that it was completely wrong.

      Today of course we have the benefit of hindsight, but his predictions made are wrong. Win2k did not kill linux and in fact the linux server market share increased since.

      Duh.

    2. Re:Stupid is as stupid does by fm6 · · Score: 1

      Well, if we don't have to give specifics about anything, let me just proclaim that everything I say is totally correct and I never am wrong about anything! I win all arguments, forever!

    3. Re:Stupid is as stupid does by kovarg · · Score: 1

      Had he written the same thing on Slashdot it would have simply been marked as flamebait and forgotten about.

      --
      blame me!
    4. Re:Stupid is as stupid does by fm6 · · Score: 1

      Oh, you speak for all of Slashdot, do you? How nice!

    5. Re:Stupid is as stupid does by SN74S181 · · Score: 1

      Win 2k badly wounded Linux, though. It shook out most of the people who had practical uses for Windows and left behind just the zealots and malcontents.

    6. Re:Stupid is as stupid does by Anonymous Coward · · Score: 0

      Um what? Linux hasn't taken over the consumer desktop, but we're not talking about that market. Metcalf was talking about Win2k, the server OS. In fact, Linux has been exploding in that market and 2K's growth has been stagnant. So the only "zealots and malcontents" are those still running Win2K.

      Win2k didn't wound shit.

    7. Re:Stupid is as stupid does by Anonymous Coward · · Score: 0

      Sorry, but you are incorrect. Win2K didn't "wound" anyone except Microsoft. They over-promised and under-delivered. The result of course is that Linux is now quickly becoming the de-facto server platform for just about everything at most heavy-duty compute shops, while Windows is stagnating in the low-to-mid level file and print server market. With the new SCO-Microsoft partnership and the revelations of a Microsoft slush-fund to undercut new Linux opportunities, it is becoming increasingly clear that Microsoft has realized too late that it is fighting a losing battle and has no time to regroup. When SCO is ground into dust, I fully expect Microsoft to begin announcing software for Linux. They will certainly do it slowly and will certainly make it seem like Linux is their "last resort" for only those customers who absolutely insist, but it'll happen. I called Mecalfe a moron back in 99 when he called it "open sores", and I stick by my prediction that he will look like even more of a moron within the next couple of years as Linux levels Microsoft.

    8. Re:Stupid is as stupid does by Pharmboy · · Score: 1

      When SCO is ground into dust, I fully expect Microsoft to begin announcing software for Linux.

      I have always expected MS to create a desktop for Linux. Perhaps a few years off, but I can see several advantages to doing this.

      1. MS has more experience with the GUI than anyone else. As much as we bitch about it, the MS desktop is still easier for the masses to use than anything other than OS X. The masses like the MS desktop, and don't care about what is underneath it. 98% of the public is not a kernel hacker, and has no desire to become one.

      2. If Linux DID begin to expand into the desktop area, MS would still keep the GUI marketshare, and would probably be able to charge the same as they do for the entire OS. Or close.

      3. Security and Money. MS would not be as responsible for the security, since the kernel of the OS is open source. This would allow them to focus on applications and the desktop, which is more profitable. I can see their applications REQUIRING "Windows for Linux" to operate, so their revenue stream is not effected. There is nothing to prevent them from using a proprietary DRM ontop of Linux to manage their own software and licensing.

      4. If Linux DID catch on even more, they could switch to BSD as a kernel, and not open up the source. This would be consistant with Embrace, Extend, and Extinguish, with the end result being a MS GUI ontop of a proprietary or closed source kernel. This would be like the IBM model in reverse.

      5. They could even consider continuing using the Linux OSS kernel, so other people will do their work for free, although I think the BSD route is more likely in the long run, since they could effectively TAKE the code, and not release any changes to it. Linus has already said that he is open to DRM in the kernel, to boot.

      I don't expect that the above is necessarily PROBABLE, but it is entirely possible. I know this: I am a capitalist, and if I owned MS, I would be looking into the above as a possibility purely from a market share preservation move. I would also make sure that my 'real' Windows ran better, so people would get the impression that the NT kernel was better. Thier stockholders are not interested in MS's reputation as an innovator as much as a profit maker.

      --
      Tequila: It's not just for breakfast anymore!
  15. Photons vs Electrons by Anonymous Coward · · Score: 4, Insightful

    According to Metcalfe, Ethernet is competing with SONET and Fibre Channel, although he claims that ethernet is winning due to its "internet-compatibility," among other things. To me, this seems like steps in the wrong direction. If fibre optics do not integrate well with the present structure of the internet, then we should be changing the structure, not sticking to the old concept of ethernet. When ethernet was invented, it took advantage of technology available 30 years ago. Since then, we have only been improving on the implementation. Despite the fact that SONET and Fibre Channel are the current "Godzillas," THEY are the ones with the novel technology, and avoiding them would not be in the best interest of advancing technology.

    1. Re:Photons vs Electrons by jrstewart · · Score: 1

      Uhhh... You can run ethernet over fibre. It works quite well.

      The problem with Fibre Channel is that the storage people are having to recreate all of networking, and make all of the early networking mistakes all over again. Painful. That and it's expensive.

      I can't speak to SONET but if it's the disaster that ATM is/was then there's not a lot to learn there. Maybe some QoS stuff and a lot of bad examples.

      For the record ATM and Fibre Channel both commonly run over copper as well as fibre. The physical medium for all of these things makes a lot less difference than you seem to think.

    2. Re:Photons vs Electrons by WolfWithoutAClause · · Score: 2, Interesting
      I've never done any fibre channel, but SONET is very not novel, and in fact it is a dying dinosaur. The only reason it is so widespread is tradition, and the ethernet has caught up bigtime; and is much, much cheaper.

      If I was a telephone company I would be looking at buying only VOIP equipment and run it on private LANs with plenty of bandwidth. No SONET at all.

      --

      -WolfWithoutAClause

      "Gravity is only a theory, not a fact!"
    3. Re:Photons vs Electrons by silas_moeckel · · Score: 1

      OK first off Ethernet works great over fiber actualy in the last two revision fiber was first (1 gig and 10gigE I'm not sure on 100mb) Fiber Channel does nothing new realy it's just another packtied network that happen to run are some pretty high speeds and support packetized SCSI and network (mostly IP) it's nice it has dynamic addressing and a lot of support for bonding channels together. Sonet realy is what you want to use for going the distance it supports very large packets something ethernet has big issuea with. You can use ethernet but it's just not that easy there are a lot of issues like delayed collisions. Ethernet has the LAN locked up it just works well enough and has been expanding at a fast enough clip. It's being expanded into the MAN where it's just so much less expansive to switch than it is to route.

      I think when it realy comes down to it you can get a gigabit port on a big switch (lets say a 4k from cisco) for under 100 bucks a port easily while your paying sever thousand for the same ammount of bandwith for sonet and fiberchannel sometimes thats an addon to gigabit class switches but realy how long with it last with iSCSI comming up in the ranks.

      --
      No sir I dont like it.
    4. Re:Photons vs Electrons by Anonymous Coward · · Score: 1, Insightful

      ATM a disaster? you must be joking. With MPLS, IP is just now catching up to the QoS features inherent in ATM. So the companies that invested in huge ATM networks are laughing.

      Of course, switched Gig Eth over fiber is also a fine technology. Thanks Mr. Metcalfe.

    5. Re:Photons vs Electrons by connorbd · · Score: 2, Insightful

      Not that I actually know what I'm talking about, but I thought ATM was quite successful in certain niches? IIRC my DSL connection is basically ATM mingled with an analog signal... (Now ATM as an end-user networking architecture -- that has been a resounding failure. But I was under the impression that The Phone Company (TM) uses it quite a bit.)

    6. Re:Photons vs Electrons by jrstewart · · Score: 1

      Oh, ATM's used quite a bit. It just sucks. Let's take DSL for example. DSL modems encapsulate ethernet frames in ATM cells. The ATM cell size is 48 data bytes (plus a header, 8 bytes IIRC).

      Take the shortest common datagram, at TCP ACK. That's typically 20 bytes of IP header + 20 bytes of TCP header with no options or data bytes. Put that in an ethernet frame. It's padded to 64 data bytes (minimum frame length), plus 16 byte header plus 2 byte trailer (CRC). That's 82 bytes.

      So for a packet with no data you have 2 ATM cells which are fixed at 48 bytes long. Plus cell headers that's 112 bytes for a 40 byte packet of no data.

      ATM gear is quite expensive since it supports QoS and reliable delivery at the cell level. Ironically when running TCP/IP over ATM (with or without an ethernet encapsulation or emulation layer) this all goes wasted since TCP/IP will do that for you anyway. And for applications which don't need those guarantees it essentially means added latency and reduced bandwidth for no value.

      Now the small uniform cell size does have some benefits, especially in a streaming mode like voice traffic.

  16. Huh? by Dachannien · · Score: 3, Funny

    What, no gratuitous Al Gore comments? ;)

    1. Re:Huh? by Xeth · · Score: 1
      What, no gratuitous Al Gore comments? ;)

      I believe that's redundant.

      --
      If your theory is different from practice, then your theory is wrong.
    2. Re:Huh? by GMontag · · Score: 0, Offtopic

      This does not count as gratuitous?

  17. Xerox, Broadband by fm6 · · Score: 4, Interesting
    Two interesting bits of trivia. First, note that Xerox, which did all the early R&D for Ethernet, is mentioned only in passing. As with the GUI revolution and OOP, Xerox did all the pioneering, but dropped the ball when it came to actually profitting from it.

    Second, Metcalfe defines "broadband" to mean "high bitrate" rather than "uses a broad frequency band". Nitpickers like me have been quibbling over this change in definitions, but if someone like Metcalfe has gone over, it's time to let it drop!

    1. Re:Xerox, Broadband by xargs2 · · Score: 1
      This looks like a good thread to add some nitpicking...

      Ethernet is also not a protocol, like everyone is reffering to it as.

      [2.1] What is Ethernet?

      Ethernet is the IEEE 802.3 series standard, based on the CSMA/CD access method that provides two or more stations to share a common cabling system. This access method, Carrier Sense Multiple Access with Collision Detection, is the basis for Ethernet systems which range from speeds of 1 Mb/s through 1000 Mb/s. The design goals for Ethernet were to create a simply defined topology that made efficient use of shared resources, was easy to reconfigure and maintain, provided compatibility across many manufacturers and systems, while keeping the cost low.

      http://www.faqs.org/faqs/LANs/ethernet-faq/index.h tml

  18. But...but... by A_Non_Moose · · Score: 4, Funny

    "The technology is 30 years old...who'd want to use it?"

    Wasn't that one of Microsoft's arguments against Linux at one time?

    And, I *KNEW* I was a geek when this kept me laughing for 30+ minutes...laughing so hard I had tears rolling down my eyes and my sides hurt:

    Ethernet: A device used to catch the Ether-bunny.

    {snerk...hahahahaha}

    --
    Have you read the moderator guidelines? Well, have you, PUNK? (and I want a Karma: Gnarly option)
    1. Re:But...but... by T-Ranger · · Score: 1

      Im not sure that MS said that, though it sounds like something that they would say.. Im sure however that Metcalfe used that type of argument against linux/unix...

  19. Seems appropriate... by Mondoz · · Score: 2, Interesting

    Okay, not originally said about ethernet... "How can one little insulated wire bring so much happiness??"

    --
    /sig
  20. never been in Silicon Valley during dotCom era? by lingqi · · Score: 4, Informative

    If you have, you would absolutely, certainly have the initials VC engarined in your mind. These are the overlords that controls your life and owns your soul.

    Especially toward the end when all of them were changing from benevolent take-all-you-want piggybanks* to bloodsucking vampires that fires off one coworkers after next with glee**.

    *note1: actually, from the beginning it was more like the inverse of beggars: they often *BEGGED* you to take their money if you just had the stupidest business plan involving the word "internet" and "e-commerce."

    **note2: okay, I have to admit they didn't want to see the company they have vested interest fail, but toward the end, most VCs took control of their companies directly, and had no quarrals about tossing people out like used rags.

    For all the geeks out there - the whole dot-com -> dot-bomb thing taught me one big lesson: unless you make it to upper management or start out on your own (really on your own, i.e. your own capital), you are just a (disposable) pawn in this game.

    --

    My life in the land of the rising sun.

  21. As said by Homer Simpson... by Anonymous Coward · · Score: 0

    in refrence to stealing cable TV.. :)

  22. Not Photons vs Electrons by Webmonger · · Score: 3, Insightful

    It's not a choice of photons vs electrons. Ethernet can use optical fibre too.

    And I'm glad it's not up to you which technology we use, because the actual tech is only one part of the overall usefulness of a technology. For example, a $100 network card that can do 1gbit/s is more useful to me than a $1000 network card that can do 100 gbit/s. Because I can afford (and justify) the $100 card.

    Price matters. Open standards matter. Would we have Ethereal and tcpdump and all the billions of useful network tools that are out there if we were using proprietary standards for networking? I don't think so. Would people get owned due to network stack (or network protocol design) bugs? Seems quite possible.

    Try looking a little farther out.

  23. The "gigalapse" that wasn't by Anonymous Coward · · Score: 4, Interesting

    Bob Metcalfe once predicted that the internet would 'gigalapse' due to IP namespace exhaustion and sheer load. It didn't happen.

    Bob has made a career out of making an ass of himself with idiotic predictions coupled with a humongous ego. He fancied himself quite clever when he called the free software/open source movement "the open sores movement." Har har! You may have a career with ZDNET yet, Bob.

    Hey Bob we thank you for ethernet, but you're still a jerk.

  24. My favorite thing about Ethernet by sbwoodside · · Score: 4, Funny

    is CSMA/CD . What a brilliant MAC. You just start shouting, check to see if anyone else was shouting, and if they were, wait a random amount of time and start shouting again. It's so simple and stupid that no one would ever think it works.

    simon

    1. Re:My favorite thing about Ethernet by Pivot · · Score: 2, Funny

      I think those who are trying to automate the steering of cars should try this. Just drive on and when you hit something, you turn.

    2. Re:My favorite thing about Ethernet by evilviper · · Score: 0
      You just start shouting, check to see if anyone else was shouting, and if they were, wait a random amount of time and start shouting again.

      That's not true... Ethernet doesn't send if it detects another current transmission.

      More accurately, if it doesn't hear someone shouting, it shouts, and if it detects that someone else decided to shout at the same time, it waits, and shouts again.
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    3. Re:My favorite thing about Ethernet by sbwoodside · · Score: 1

      well, you're nitpicking. What I said was true, it jsut wasn't the whole truth. there's more to it than what you said too.

      simon

  25. Ethernet Scalability by jwang · · Score: 0

    I wouldn't argue against Ethernet for photons vs. electroncs (see other posts in this thread) but I do have a problem with Ethernet's scalability. The lack of determinism CAN and IS a problem in huge networks.

    I'm currently at MIT, and the network in my dorm was put in back when the dorm was first built in the 80s. It's 10-base-T and wholly inadequate for modern use. Random exponential backup is fine for situations where the ether isn't used heavily. It's pretty stupid flow control - if you sense a collision, wait some random period of time and try again. However, when you have a lot of stations transmitting, you get a lot of collisions... fast.

    The typical figure for saturation of a medium is around 70% usage. For Ethernet, however, it's more like 38%. As you add stations, it becomes more and more difficult to transmit before you go through your 15 retries and throw out the packet.

    When you combine this with TCP's assumptions, you run into some pretty perverse situations. TCP expects a network with 0 packet loss - the ACKs have to get back to the sender within some amount of time or it'll retransmit. When you get huge Ethernet networks with lots of activity, the exponential backup keeps delaying packet delivery until all communications slow to a crawl.

    For me, this means having to tolerate 30% packet loss and transfers of around 10 KB/sec through a 10 Mbit network with something like 600 hosts.

    The cure to all these problems has been revisions to Ethernet - switches establish an Ethernet link with two hosts between the switch and each port on the switch. It's a workaround to a stupid decision in the Ethernet protocol that's now firmly established and won't ever be changed because of its acceptance.

    1. Re:Ethernet Scalability by adri · · Score: 2, Informative

      Actually, TCP doesn't expect 0% packet loss at all. It expects an unreliable data path.

      The problem here, as you subsequently covered, is that ethernet backs off and handles its own retransmission. This screws with the TCP timers.

      If you could turn off the ethernet retransmission then TCP would still work just fine.

      But yes, unswitched ethernet sucked when you had many stations trying to move large amounts of data. Token ring (and ATM!) _did_ handle load better but was much more costly.

      (My DEC friends commonly refer to Ethernet as "cheapernet" with a little curled tongue action.. eww.)

    2. Re:Ethernet Scalability by Anonymous Coward · · Score: 1, Insightful

      TCP expects a network with 0 packet loss

      I can't believe you just said that. Um, the whole reason that TCP exists is to provide reliable services on an unreliable network (that is, > 0 packet loss).

      I also can't believe they are letting idiots like YOU into MIT now...

    3. Re:Ethernet Scalability by jwang · · Score: 1

      Thanks for clearing that up. I *think* what I meant to say is that if there's only one route to the gateway, then TCP gets fubared if the data path is unreliable. Of course, this would be the case with any protocol - what TCP was designed to fix is to choose an alternative path given that they exist. With Ethernet and TCP, though, when you have a heavily used link, it's particularly bad because of the retransmission delays you pointed out.

    4. Re:Ethernet Scalability by adri · · Score: 1

      Eep!

      TCP doesn't care about alternate data paths. Thats an IP routing issue.

      You could, in theory, implement TCP directly on top of some other protocol quite happily.. including directly on top of ethernet.

      Its all in the timers..

  26. He still doesn't "get" open source. by nathanh · · Score: 4, Interesting

    He makes this rather ignorant comment:

    ... it is unlike open source in that competitors don't give their intellectual property away.

    Open source contributors who use the GPL never "give their intellectual property away". Copyrights are very strongly defended; the recent FSF vs OpenTV story is sufficient proof of this. Trademarks are very strongly defended: Linus and RedHat have both defended trademarks. Patents are a sticky mess but even then the GPL doesn't demand that you give up patents; only that you don't use them to restrict or impede licensing. The open source movement is not so stupid as to "give away" code. Strong ownership of intellectual property is at the very core of open source.

    The subtle but important distinction is that open source developers want to share their intellectual property. The philosophy is "you may use my IP if I can use yours". This is not giving anything away; it's building a community of cooperation. There is an exchange of value between two parties even though the exchange is not monetary.

    I suppose it's possible to argue that BSD zealots are giving their intellectual property away. Yet another reason to avoid the BSD license.

    1. Re:He still doesn't "get" open source. by Anonymous Coward · · Score: 1, Insightful

      Get a clue, the code is not what's "intellectual property", it's the spec, the ideas , the design and the comments detailing corner cases, and those aren't protected by copyright. Someone smart can re-develop the code without infringing the copyright. Such copying takes some brain, similar to cheating in school, only the smart kids can get away with it.

      With GPL you give your IP away but force anyone who wants to reuse it in non-GPL products to re-implement it. BSD seems to take the pragmatic approach that once the cat is out of the bag, you may just as well take the whole thing and you are incited but not forced to contribute back.

    2. Re:He still doesn't "get" open source. by nathanh · · Score: 1
      Get a clue, the code is not what's "intellectual property

      All of it is intellectual property. Even the latitude and longitude markings on a map are IP. My point was that open-source developers do not give away their IP. They do retain ownership and they do defend their property. Just because you can point to examples of IP that aren't defended by law doesn't mean you have invalidated what I said. All you've done is argued on a tangent.

      ... it's the spec, the ideas , the design and the comments detailing corner cases, and those aren't protected by copyright.

      Design and comments are covered by intellectual property laws.

      Someone smart can re-develop the code without infringing the copyright.

      Huh? So your argument basically boils down to "somebody smart can reimplement it, therefore open-source developers give their intellectual property away". Are you nuts? Did Apple "give their intellectual property away" when Microsoft implemented the desktop interface? Did Opera "give their intellectual property away" when Konqueror implemented tabbed browsing. What a nonsense. Get a clue, yourself.

  27. Seems like 60 years ... by hndrcks · · Score: 1

    ...since I had to fsck with terminating resistors (10base2), vampire taps (10base5) or that crappy stiff ArcNet cable. I still have working setups of each packed away in my basement.

    --
    Everyone will start to cheer when you put on your sailin' shoes.
  28. No, YOU'VE got to be kidding ME by macdaddy · · Score: 4, Informative
    Before 1993 or so and the advent of Switched Ethernet, Ethernet would melt down under the weight of its own traffic. 40% traffic for Ethernet is an emergency situation.

    No, you're kidding me, right?

    I can't believe this FUD is still out there after 30 years. Contrary to popular and mis-guided belief, an Ethernet will NOT saturate itself at 37% utilization. Period. Anyone that honestly believes that should give the token ring and ATM salesdroids and spin doctors a great big pat on the back because that's exactly what it is: sales doubletalk and spin from vendors of competing technologies. For christ's sake, this myth was laid to rest in September of 1988 . This FUD relies on over-simplifications of assumptions in the theory and inadequacies in the testing procedures.

    I can't believe you'd honestly bring it up. Anyone with even a marginal amount of actual networking experience knows this to be FUD. Next time think before you speak about something you know nothing about.

    1. Re:No, YOU'VE got to be kidding ME by Anonymous Coward · · Score: 0

      Umm, sorry bud but it is YOU who is full of shit. The article you yourself quoted even says that such high utilization on ethernet is "theoretically" possible, and discussed how to implement hardware to get that kind of performance. While token ring had the real ability to saturate connections, no practical ethernet hardware was able to come even close.

    2. Re:No, YOU'VE got to be kidding ME by nuintari · · Score: 1

      YOU'VE never been the CWRU then have you? Where the flat topology \16 network was a nightmare for anyone on the ethernet segment. It was all ATM over fiber until a few years ago, but if you wanted more pc's in your room than their were available fiber jacks, you had to transieve it down to ethernet, and attach a hub....

      Then you realized why almost no one ever did this: 65%+ packet loss, all the time. The constant cry of a couple thousand machines on one giant flat network, screaming out ala ethernet fashion, it made life a living hell. Software switching on the routers to filter out some ethernet broadcast traffic helped, but it was never fixed until they ditched the old implmentation, and switched out all the buildings with switched gigabit ethernet.

      Ethernet has its problems, they all do. Whatever.

      --

      --Nuintari

      slashdot : where an opinion can be wrong.

    3. Re:No, YOU'VE got to be kidding ME by Shimbo · · Score: 1

      Umm, sorry bud but it is YOU who is full of shit. The article you yourself quoted even says that such high utilization on ethernet is "theoretically" possible, and discussed how to implement hardware to get that kind of performance. While token ring had the real ability to saturate connections, no practical ethernet hardware was able to come even close.

      That's nonsense, I'm afraid. Since when was it a problem with a network technology that it had *so much* bandwidth that the systems couldn't pump the data out that fast?

    4. Re:No, YOU'VE got to be kidding ME by macdaddy · · Score: 2
      The problem you experienced wasn't because this mythical limit to Ethernet. It's because you had too damned many nodes in a single collision domain. The Ethernet myth was made on the over-simplified interpretations of the assumptions made by Metcalfe's and Boggs's in the early testing of the "experimental" Ethernet (3Mbit Ethernet) and was part of the original Ethernet whitepaper. These tests assumed the maximum number of nodes simultaneously sending the maximum frame size and talking at the theoretical maximum line speed. These nodes were assumed to be connected together with the absolute maxiumum allowable lengths of cable, genereating the longest allowable round-trip response time. Did I mention that this myth started with a pre-standard Ethernet spec? In lay terms, this myth was based on bad interpretations of a lot of worst-case assumptions on a pre-standard form of what we call Ethernet.

      ATM is the worst piece of shit imagineable to put in a LAN. LANE has got to be one of the all-time worst fuckups in networking history. You can't beat stuffing a 1518-byte frame into a 53-byte ATM cell. It's even worse than that. The ATM cell's payload is only 48 bytes. Ooooohhh.... That's got to hurt. There's a reason why ATM is no longer used in LAN environments (or isn't in new installations and is rapidly being removed from old installations). It's great for WANs. It's horrible for LANs.

      The network you describe above is a larger version of what I spent the last 2.75 years trying to get fixed at my now former place of employment (/20 and a /22). Broadcasts storms caused eratic network failure and was undoubtedly contributing to piss-poor performance of the LAN. We too had ATM in our core (from long before I started there). They had migrated to switched Ethernet for most of the distribution and access layers. Unfortunately the hubs in the back room found their way back out onto the LAN to add a port here or replace a failed switch there. That certainly didn't help matters. That campus had two netblocks, even though it wasn't by true definition a routed LAN. We had a router on a stick essentially. Did I mention that it was a 2501? Yes, that's right. The 2500 series only have Ethernet interfaces capable of 10half. Oh, and I can't forget one sysadm's insatiable desire to put an old hub between the 2501 and the rest of the LAN so he could sniff? When it was finally recognized that collisions on the hub were a problem the solution cooked up by the sysadms was to buy a $70 NetGear 10/100 hub, so we coudl generate collisions faster. It didn't help the matters any that nodes were assigned IPs by user type, not physical location. This made any attempts to renumber the campus futile without the full support of the management. It would have been far less load on the router if we'd use either DHCP to add a static route to the both netblocks on all the machine or manually enter them. The ATM core, while technically running at 622Mps, was actually limited to 155Mbps by the fact that the ATM nic on in the chassis on either end of the 3 primary links were 155Mbps nics, not 622Mbps. This was also old Fore hardware. I didn't dare touch it for fear that it would break. I performed an upgrade on an ATM module in a new switch. The switch was 14 firmware revisions behind at the time. Unfortunately that broke LANE. The possible fixes was to upgrade all the ATM hardware to LANE-2 capable hardware or downgrade that switch. Any guesses on which I did? Oh hell, I almost forgot to mention. About 80% of the buildings were connected to the backbone via FDDI. Well, I shouldn't say they were connected to the backbone. I should say they were connected to their neighboring buildings. Eventually two of those were connected to one of two POPs. Of course it gets worse. Some of these buildings didn't have a single entry point for the network on the FDDI ring. A number of buildings ran the same FDDI network through every switch in the building, literally. It ran in one floor, all the way u

    5. Re:No, YOU'VE got to be kidding ME by nuintari · · Score: 1

      Never said it was the ethernet myth that caused it, but bad deployments of ethernet, or in CWRU's case, fast deployments to fix a lack of foresight on the part of their fiber laying ATM nut admin a few years back, led to an example of where ethernet does not work whatsoever.

      ATM can be decent for a lan, if you can afford to maintain it, but what college that just spent a boatload building a huge fiber network can afford to run multiple fiber faceplates to each dorm room? That, and ethernet is cheaper, by a landslide, and nearly as fast. Its also just the smarter choice for the last mile, save the atm for the backbone, where it rocks at what it does.

      I wouldn't say its infinitely scalable, becuse nothing is. Ethernet is poorly suited for WAN's, and even large enough(and I stress enough) lan's can get saturated. Its scalable to the point that is nessesary considering the network admin knows when to divide one huge lan into smaller, more efficient pieces and connect them with some other practicle method.

      But hubs should be illegal at this point.

      --

      --Nuintari

      slashdot : where an opinion can be wrong.

  29. metcalfe by Anonymous Coward · · Score: 0

    Metcalfe is a total elitist and he doesnt even know it.

  30. Or should we say .... by Smallpond · · Score: 1

    " Linux is based on thirty year old technology, and it hasn't replaced Windows. He's right. You know it."

    Windows is based on 30-year old technology and hasn't replaced Unix. In fact, the dominant form of computing 30 years ago was the mainframe. Windows hasn't even replaced that.

    1. Re:Or should we say .... by Anonymous Coward · · Score: 0

      But of course, saying that Windows is old doesn't have the same "stickin it to the Linux users!" feel, so the blowhards don't say it.

  31. Broken Ring .... by bizitch · · Score: 1

    It's fun to to go down memory lane sometimes - remember ....

    "OMFG! The Network is Beaconing! The Network is Beaconing!"

    Ahhh the good old days .... you know when one old piece of shit Broken Ring NIC that decides to take a header- could bring a Fortune 500 company to its knees ....

    Frankly - ArcNet was better!

    --
    ---- "Logoff! That cookie shit makes me nervous!" - A. Soprano
  32. heh, whatever by DashEvil · · Score: 1

    Linux sucks because it's 30-year old technology even though it's first public release was in 1991 and it doesn't have any ties to any of the heriditary unicies. (Making an assumption about the SCO claim, of course). Well, gee, brilliant. Knock down something simply because it's old. Let me tell you something folks, stop using wheels, old technology, innovate. Cars? 100 year old technology, innovate, come up with something radicly new! Let's face it, either this guy is sleeping with aliens, or he's a hypocrite. Go him!

    --
    -If God wanted people to be better than me, he would have made them that way.
  33. Don't Forget David Boggs by n9fzx · · Score: 3, Informative
    David was the other half of the Metcalfe-Boggs "team" that made Ethernet a reality. Dave is an honest-to-nuts Friend of the Electron electrical engineer, who had to crack the problem of making CSMA/CD work in the Real World; in particular, how do your hear a transmitter 500 meters away when you're sitting right next to your own?

    Boggs invented the first (of many) hardware circuit techniques to do collision detection, and other elements of transceiver design. If Dave hadn't picked up a soldering iron, we'd probably be doing DATAKIT or some other telco hack.

    --
    ...-.-
  34. Ethernet is not Aloha, Damnit! by Detritus · · Score: 1
    Please do not propagate misinformation about Ethernet.

    See:

    Measured Capacity of an Ethernet: Myths and Reality, David R. Boggs, Jeffrey C. Mogul, Christopher A. Kent .

    Ethernet is CSMA/CD, not CSMA. The collision detection mechanism arbitrates access to the medium, it is not there for flow control. Collisions are not bad.

    --
    Mea navis aericumbens anguillis abundat
  35. Another Nit to Pick! by fm6 · · Score: 1
    I shouldn't spoil a perfectly good joke, but I just realized that twisted-pair Ethernet, which is what everybody uses today, is only about 12 years old. Thirty years ago, you would have been looking for something to drive a spike into a CATV cable, which is how early Ethernet was implemented.

    Oh hey, found a Commmunications of the ACM article by Metcalf and Boggs about their early work on Ethernet. Good read.

  36. Right back at ya! by fm6 · · Score: 1
    Ethernet isn't a standard. It's a technology described by a set of 802.3 series standards.

    I wonder how long we can keep this up?

    1. Re:Right back at ya! by xargs2 · · Score: 1

      Hehe... You're quite right, that FAQ even has problems.

  37. Also... by ceeam · · Score: 1

    A Pentium processor is 10 somewhere around these days (don't remember exactly ;)

  38. Re:Photons vs Electrons : EoS ! by ballpoint · · Score: 1
    A technology that is on the rise is called Ethernet over SONET (EoS). Standards have been establish to carry 10, 100 and 1Gig ethernet packets in SONET envelopes using a technique called Virtual Concatenation.

    This way carriers will soon be offering ethernet access, without having to abandon their ample investments in SONET.

    Expect to hear about this technology a lot in the coming years.

    Read more here.

    Enter EoS in the searchbox at the upper left.

    --
    Flourescent (adj): smelling like ground wheat.
  39. Re:Don't Forget David Boggs-Jeopardy question. by Anonymous Coward · · Score: 1, Interesting

    Kind of like the Jobs-Wozniak team. One gets the glory while the other languishes in realitive obscurity. Were's the Wozniak reality-distortion field?

  40. Re:Don't Forget David Boggs-Jeopardy question. by Gordonjcp · · Score: 1

    It's that smokey haze that hovers around him...

  41. Re:first by Anonymous Coward · · Score: 0

    Who, Trinity?

  42. The really funny part by duck_prime · · Score: 1
    Well they do say vietnam is a beautiful country now that American invaders aren't trying ton bomb into the stone age and kill everyone who doesn't dig bigmacs...
    The really funny part is that the Vietnamese are now a bunch of money-grubbing Big-Mac-chomping Marlboro-smoking capitalistas thinly disguised as communists.

    God, I love this world.
  43. Big Mouth, Loud Voice by rootrot · · Score: 1

    Bob may well hold passionate and horribly misplaced beliefs, but he is open to arguement and, on occassion, can even change his mind. He also was/is the driving force behind Pop!Tech, an annual brain candy event where the questions around "what does all this tech mean" are addressed. Most people seem to miss that Bob is a provocateur...he *enjoys* annoying the crap out of people and forcing them to defend their often dogmatically (and poorly understood) positions. Mind you, this is not to say that Bob does not also hold some opinions dogmatically...but at least he can defend *why* he hold them. Personally, I like a man (or woman) who takes such pleasure in forcing others to think and defend their positions...in trying to respond to his taunts, deepen the understanding of their own positions, is this a bad thing?. Then again, maybe it is easier just to say that he's a bigmouth...perhaps you can force him to drink the hemlock.
    rootrot
    --
    The reasonable man adapts himself to the world: the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man.
    -George Bernard Shaw

  44. To nitpick your analogy... by John+Penix · · Score: 1

    It would be: Try to drive to your destination, and if you hit someone, go home and try to drive there again. (-:

    --
    Someone named an OS for me.
  45. Thick and twisted by fm6 · · Score: 1
    A thick cable (that I have never seen)...
    Actually you have. Thicknet cable was just CATV-grade coaxial cable. I don't know how similar this is to the coaxial jumpers that comes with a VCR. I seem to recall it was harder to bend. In this 1976 paper, Metcalfe and colleague explain that they used this stuff because it was readily available. But even then they foresaw the use of twisted pair.
    1. Re:Thick and twisted by bluGill · · Score: 1

      I know it is nearly identical to CATV cable. Not exactly though, and I've never personally seen the real thing. (Or at least if I have seen it I didn't know what it was)

    2. Re:Thick and twisted by fm6 · · Score: 1

      Maybe commercial ethernet cable was different. But in that paper I pointed to, they described their experimental ethernet as using off-the-shelf CATV cable.

  46. Interesting quote by Icekold · · Score: 1

    "And the reason that Ethernet won was that Ethernet was an open standard with many competing companies providing it."

    Now if only more compnaies would take heed...

  47. Interoperability is good by Jonner · · Score: 1

    And who tends to promote interoperability more than Free Software and Open Source authors?

  48. Open Source != Free Software by Jonner · · Score: 1

    Some people don't care about the difference, but Bob demonstrated his ignorance by stating that RMS is an "open-source software guru," when Richard doesn't even agree with Open Source. Bob failed to notice that there are idealogical, business, and pleasure (Linus did it just for fun) reasons for Free/Open Source software. In general, Bob's attitude seems to be that the bottom line is all that matters, which is silly, IMHO.

  49. Ignorant by Jonner · · Score: 2, Insightful

    You're not delusional as much as ignorant. First, IPv6 has existed for a number of years. It is not a reinvention, but a an evolution of IP to make it more scalable. Second, the value of IP and the Internet is that they are generic, not burdened by application specific details. There's a reason for the protocol stack: to keep application details at the top.

  50. Good point by Jonner · · Score: 1

    I didn't know what VC meant until I read the article (which I did before reading comments). Of course, maybe /. posts should be written in such a way that those who haven't read the article look dumb. That would make it easier to weed out a lot of clueless posts.