Slashdot Mirror


Happy Birthday, Linus

Glyn Moody writes "Today is the birthday of Linus. Just under 19 years ago, on the first day the shops in Helsinki were open after the holidays, Linus rushed out and spent all his Christmas and birthday money on his first PC: a DX33 80386, with 4 Megs of RAM, no co-processor, and a 40 Megabyte hard disc. Today, the kernel he wrote on that system powers 90% of the fastest supercomputers, and is starting to find its way into more and more smartphones — not to mention everything in between. What would the world look like had he spent his money on something else?"

17 of 376 comments (clear)

  1. A case of the pundays by suso · · Score: 5, Informative

    How would the world look different? It would be a whole GNU world.

    BTW, Linus is 40 today, there seems to be no mention of that anywhere.

    1. Re:A case of the pundays by knewter · · Score: 4, Informative

      I would counter that, while it inevitably would have happened at some point, it's not a given that the resulting OS would have been GPLed, and subsequently things could've turned out very differently. Happy Birthday, Linus!

      --
      -knewter
    2. Re:A case of the pundays by SanityInAnarchy · · Score: 4, Insightful

      It's just that more people are willing to contribute, when they feel that fruits of their labor can't be just "taken" as freely as BSD license allows.

      Bullshit, and there are plenty of very popular projects which would demonstrate the contrary -- sqlite, for example, has no license. That's because it's entirely public domain.

      To take another random example: Ruby on Rails. The license deliberately is not GPL, or even LGPL (which might have worked), but rather MIT. This means I could technically "take" it -- remember, it's not stealing, and it's not even copyright infringement here -- and build my own proprietary product.

      It also means that unless I relish maintaining my own separate fork of Rails, I'll be sending patches upstream whenever I do something cool. Even monkeypatches are much easier to send in as formal patches than to maintain.

      I used to think as you do, but the choice here is between the potential audience of every commercial product versus a few GNU zealots who will actually refuse to contribute to a project because they don't like the license.

      I can see people contributing to Linux instead of BSD if they prefer GPL, and if there are no other factors. But if Linux didn't exist, would you really refuse to contribute to BSD?

      Yesterday, I sent a patch to a project hosted by Google. They wanted me to sign an agreement essentially giving them copyright and a patent grant (without removing those rights from me) -- and this isn't Google being evil, it's common for projects to request copyright for contributions. I wasn't exactly happy about it, but it again comes down to the same choice -- are the terms of that agreement so bad that I'm going to refuse to contribute at all, or worse, fork the entire project? Probably not, especially for the small patches I have in mind.

      And by the way: If you believe in the GPL, and you pirate anything (movies, music, games...), you're a hypocrite. A term common among those who have a problem with current copyright law is, "It's not theft, it's copyright infringement," implying that it's not as bad. I've occasionally heard people say that if there was no copyright, there'd be no need for the GPL, but I don't buy that -- if you really believe that, why not use BSD or MIT?

      --
      Don't thank God, thank a doctor!
  2. Debian GNU/kFreeBSD by tepples · · Score: 5, Interesting

    What would the world look like had he spent his money on something else?

    Not much different, as the people who built Linux distributions would instead have ported GNU to the kernel of FreeBSD.

    1. Re:Debian GNU/kFreeBSD by eln · · Score: 5, Interesting

      There's also at least a small chance that many of the kernel hackers who work on Linux today would have been working on the Hurd kernel. As it happened, the release of Linux essentially killed Hurd, although it's technically still around.

    2. Re:Debian GNU/kFreeBSD by onefriedrice · · Score: 4, Insightful

      I know people like to think that the GPL played a significant role in the success of Linux, but in the face of so many examples of successful non-GPL free software such as apache and postfix, perhaps that assertion should be accompanied by a reasoned argument. Since no single software license is clearly a common denominator for successful free software, I wouldn't assume that the GPL is the driving force behind the success of Linux unless somebody makes a convincing argument in support of that claim. As it is now, although the assertion is often repeated, it seems to be based on mere assumption.

      --
      This author takes full ownership and responsibility for the unpopular opinions outlined above.
    3. Re:Debian GNU/kFreeBSD by chrb · · Score: 5, Informative

      Just because of the permissive license?

      Partly - commercial BSD derivatives and the BSD networking stack ending up in Windows 95 put off some developers - who wants to see their work being co-opted by Microsoft and other corporations in closed source products? Some people no doubt, but not the majority. Another effect of the licensing was that BSD splintered into different, slightly incompatible commercial forks. The GPL protected Linux from that fate - the free distributions were shipping more-or-less exactly the same kernel code as the commercial distributions - the general perception was that with Linux free didn't mean "less", it just meant "no telephone support". In BSD land, "free" (to many) meant "not as good as what Sun and IBM are selling".

      Another factor was that BSD was seen by some Europeans as being controlled by some American labs and American universities. This made it seem less approachable - and harder to get your code into. Linus, in contrast, welcomed good patches with open arms. Linus was highly enthusiastic about people developing code for his kernel. The same enthusiasm for outsiders was not visible within the BSD community.

      Yet another factor was the number of Linux distributions that sprung up. Competition is good - Debian, Slackware, Red Hat, etc. were all competing to make the best Linux distribution, and there were numerous other distributions trying to push them from the top. In contrast, BSD was more centrally controlled, and whilst there was some competition between distributions, there wasn't a great amount. Plus the licensing made forks more likely - with GPL and Linux, if someone wrote a good patch, it was highly likely that patch would end up in all Linux distributions fairly rapidly. The same could not be said of BSD and its various commercial forks.

    4. Re:Debian GNU/kFreeBSD by Rob+Riggs · · Score: 5, Interesting

      That's only partly true. In '94 BSD was even or ahead of Linux in terms of features. The reason Linux ended up "the winner" is because there was a stark difference between the two communities in welcoming newbies into the fold. #unix was the place to go on IRC for abuse. In stark contrast, the folks on #linux were very patient and helpful.

      I had both 386BSD and Slackware downloaded to floppy. I ended up running Linux because I was welcomed by the Linux community. Not so much with the BSD crowd. A little kindness is all it took to make Linux the world's most popular Unix OS.

      --
      the growth in cynicism and rebellion has not been without cause
  3. We will never know by prefec2 · · Score: 4, Insightful

    Maybe without Linux we would use Minix or Hurd today. While Linus caused an crystallization point for hundreds of developers he did not write the thing alone. these people were already there. More or less waiting for something like this to happen. Most of them were already part of the Minix mailing list. So most likely Linux was already waiting to happen then. From my own time as an undergraduate. all the good programmers wanted to write an OS. And when it Linux came into existence everyone said cool. I take it and I do something with it. The same happened later with the browser as well. And if X11 would have had a better programming interface there would have been more different browsers out there. Still. Thanks to Linus for starting it.

  4. Re:DX or SX? by Stonent1 · · Score: 4, Informative

    The 386SX was a 32 bit processor internally but had a 16 bit data bus. The 386DX was a straight 32bit processor all the way through. There was a third flawed varient that had a problem switching between real and protected mode that could lock up the system. Those chips would be stamped that they were only certified for 16 bit apps. The ones that tested good had a double sigma stamp on them. Neither the 386sx nor 386dx had math coprocessors. The 486 however was a different story. The 486DX had a coprocessor but the 486SX did not.

  5. Most Americans might by Kupfernigk · · Score: 4, Insightful

    Some North Americans really do overestimate the penetration of their own popular culture. Globally, most people wouldn't think of anyone at all. On Slashdot - Mr. Torvalds.

    --
    From scarped cliff or quarried stone she cries "A thousand types are gone, I care for nothing, no not one."
  6. No coprocessor... by TrisexualPuppy · · Score: 4, Informative

    The point about Linus's machine having no coprocessor is actually true. This made development a little iffy since floating point math had to be done in software. The i386DX actually did not have an FPU, and the coprocessor was the i387 which was not all that popular but was compatible with both the DX and SX models. It was not until the introduction of the i486 that the SX had no coprocessor and the DX had a built-in coprocessor.

    Interesting read.

    1. Re:No coprocessor... by Godji · · Score: 4, Funny

      I''ll go for a wild guess here, but I bet you're still 10 years younger :)

    2. Re:No coprocessor... by dotgain · · Score: 5, Funny
      That's the first time I've ever heard this, but I'll believe it. Nothing, I repeat nothing, will ever surprise me about the evolution of x86 any more.

      If you were to tell me that Little Endianness was simply the result of someone putting something on an overhead projector the wrong way, I'd believe you (because it seems like an extremely fucking stupid idea otherwise: "2 ^ 16 equals five-hundred-thirty-six, sixty-five thousand"

      If you were to tell me that the Pentium was really 64-bit, but the fabricators never hooked up the address pins because they never got the memo, I'd believe you.

      No doubt, x86 is the cheapest, fastest and most prevalent CPU in computers today, and probably always will be, but fuck me if it doesn't look like the biggest kluge in the world.

  7. Re:over 40 by rolfwind · · Score: 5, Insightful

    Is he going to invent anything else? Or after 40 do you just give up on life?

    http://en.wikipedia.org/wiki/Linus_Torvalds#Authority_on_Linux
    "About 2% of the Linux kernel as of 2006 was written by Torvalds himself.[13] Since Linux has had thousands of contributors, such a percentage represents a significant personal contribution to the overall amount of code. Torvalds remains the ultimate authority on what new code is incorporated into the standard Linux kernel.[18]"

    Do you know how much output that is?! Also, consider for a minute, that Linux isn't like the lightbulb, invent once and the work is done. How far would linux have gone if work quit in 1991, 1995, 2000? It's a work-in-progress.

    The world is littered with half-assed and half-finished projects, particularly software. It's far better that Linus brings and continues one project to excellence than do a dozen mediocre projects that quite never get there.

    Maybe you should go out and invent something. If it had 1/100 of the impact Linux has, you'll the world for the better significantly.

  8. Re:over 40 by jo42 · · Score: 5, Funny

    Everyone knows "42" is the real milestone.

  9. Re:over 40 by Antique+Geekmeister · · Score: 5, Insightful

    Linus invented 'git' much more recently, in 2005. If you haven't reviewed it for source control, and compared it to Subversion at Subversion's expense, I urge you to do so. It is lighter weight, _far_ faster, allows remote development far more easily, and actually pays attention to security with its far better handling of SSH keys and its built-in GPG signatures for software tags.

    I can also attest that you only give up on life at 40 if your first 40 years weren't worth living. And in that case, your age probably wasn't the problem.