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?"

47 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 BESTouff · · Score: 2, Insightful
      As the saying goes, Linux was an idea whose time had come. If it weren't for Linus, someone else would have invented another similar OS, or one of the existing (Hurd, BSD, Minix) would have been used. All the people, the culture, the computers and the communication medium were there, ready to give birth to such a thing.

      Still, Linus has been a great leader, and a tasteful (for some) architect. Thanks a lt for that !

    2. 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
    3. Re:A case of the pundays by phaggood · · Score: 2, Insightful

      Hurd was a mess (i think it was at its second or third rewrite at the time, trying for the last fad in kernel design)

      Hurd is the DNF of OS's?

    4. 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!
    5. Re:A case of the pundays by SanityInAnarchy · · Score: 3, Insightful

      GPL is more than just about copyright. It's about giving back.

      No, giving back is about giving back.

      GPL is about forcing you to give back, through copyright -- or it's about restricting people who refuse to give back from using it. It was created to counter the perceived (and very likely real) threat of people building a giant proprietary product out of what was once free, and everyone inevitably upgrading to the shiny new proprietary version, leaving everyone without the ability to change their own code.

      But free software, as a concept, doesn't require the GPL. Nor does free software, as a movement, rely on the GPL at this stage.

      how is having a problem with one part of a law mean you have a problem with the whole law.

      Copyright is a way of expressing what you want done with copies of your intellectual property.

      If you have a problem with copyright, or with the idea of intellectual property, I can certainly see a case for that -- and I'd love free-as-in-beer and DRM-free movies. I can certainly see piracy inevitably crushing those who cling to draconian DRM.

      But to then turn around and suggest the GPL?

      Think about your reaction when you see a gpl-violations story, versus an MPAA story. When it's the RIAA or MPAA, everyone (myself included) is quick to call them the MAFIAA and to defend piracy as "copyright infringement, not theft", and even suggest that there are no moral issues with it.

      But when it's a GPL violation, suddenly copyright matters and everyone is morally outraged.

      They both rely on the exact same part of the law -- they both rely on the assumption that just because you wrote something, you should be able to control what people do with it.

      Actually, I'll play devil's advocate for a moment -- if you consider it as a social issue, rather than a legal one, the GPL is about forcing people to share. If you think sharing is good, then you probably see the GPL as a way to encourage more sharing than would happen otherwise -- and there would probably be even more sharing with no copyright, so you'd gladly give up the GPL if it meant copyright law is gone forever. This is probably why such licenses are referred to as "copyleft".

      --
      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 Pharmboy · · Score: 2, Insightful

      While it would run in similar POSIX way, there is enough difference in the BSD and GNU/Linux license, that Free software would be very different. Don't underestimate the power of the philosophy behind the software.

      --
      Tequila: It's not just for breakfast anymore!
    3. Re:Debian GNU/kFreeBSD by Anonymous Coward · · Score: 2, Interesting

      If Bill Jolitz hadn't dropped off the face of the Earth for a year and perhaps even when he wasn't incommunicado if he had been more receptive to help from other people who wanted to pitch in we might be running a lot more 386BSD.

      Instead he ceded the high ground (IMO) to Torvalds.

    4. Re:Debian GNU/kFreeBSD by dkf · · Score: 3, Informative

      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.

      I doubt it would have happened. The Hurd hackers wanted to do fundamental OS research, and everyone else wanted a "Unix" kernel that they could just use and hack around with, and which didn't cost a lot.

      I can remember that the biggest factor in our little group of hackers moving to Linux (from 386BSD) was that it had working shared libraries. OK, they sucked in many (many!) ways, but it still meant that you didn't need to have loads of copies of libc in memory or on disk at once. On the small machines of the time, that was a massive saving.

      --
      "Little does he know, but there is no 'I' in 'Idiot'!"
    5. Re:Debian GNU/kFreeBSD by icebraining · · Score: 2, Informative

      Because BSD was being disputed in court:

      The lawsuit slowed development of the free-software descendants of BSD for nearly two years while their legal status was in question, and as a result systems based on the Linux kernel, which did not have such legal ambiguity, gained greater support. Although not released until 1992, development of 386BSD predated that of Linux. Linus Torvalds has said that if 386BSD had been available at the time, he probably would not have created Linux.

      BSD 4.4 was only released in '94, due to the lawsuit, and Linux had already gained popularity.

    6. 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.
    7. Re:Debian GNU/kFreeBSD by Pharmboy · · Score: 2, Interesting

      Of course the GNU/GPL is part of the success of Linux. On one extreme, there are those who believe GPL is more than a license, it is religion itself and RMS is their prophet. If the license didn't matter, many of the people writing software only for the GNU/GPL now might have working on BSD instead. Not every programmer is license agnostic. That doesn't mean that Free software (as a whole) would necessarily be behind the current state, but there are many people who are are a part of the "Linux only" scene *solely* because they believe in the idea of the GPL. For some, "free" isn't good enough, it must be "free, with the obligation it stays free". Some of those people just so happen to be pretty good programmers.

      --
      Tequila: It's not just for breakfast anymore!
    8. 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.

    9. Re:Debian GNU/kFreeBSD by LOLLinux · · Score: 2, Insightful

      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?

      Only GNU zealots? The people behind the original BSD, and the modern day ones, were/are perfectly fine with commercial companies using their code in their closed-source products.

    10. 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. What would the world look like? by UdoKeir · · Score: 2, Funny
    1. Re:What would the world look like? by EsJay · · Score: 2, Funny

      That's easy: http://www.guidebookgallery.org/screenshots/win31

      Does anyone else get queasy looking at Windows 3.1?

  4. Re:surley OSP by Anonymous Coward · · Score: 2, Funny

    Yeah, but it would have that crappy Finnish porn.

  5. this is what happened by Device666 · · Score: 3, Funny

    If linux wouldn't bought a computer, this year would be probably the year GNU\Hurd would be finished. Gnome KDE etc would probably not exist.

  6. 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.

  7. Alternate Reality? by The+Redster! · · Score: 2, Funny

    2010 will be the year of Solaris on the Desktop!

  8. Doesn't qualify for one-name status by sunderland56 · · Score: 3, Informative

    Mr. Torvalds may be well known, but when you use just the single name "Linus", most people think of the blanket-carrying kid in Peanuts.

    1. Re:Doesn't qualify for one-name status by larry+bagina · · Score: 2, Informative

      Linus (Peanuts): Sounds like "Vaginas"
      Linus (Torvalds): Sounds like "Penis"

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

  9. Re:no co-proc? by jgardia · · Score: 2, Informative

    386SX -> no math coprocessor, 16bit data bus 386DX -> no math coprocessor, 32bit data bus 486SX -> no math coprocessor, 32bit data bus 486DX -> math coprocessor, 32bit data bus

  10. Birthday money by Megaweapon · · Score: 3, Funny

    Perhaps better spent on a $699 license from SCO. /sarc

    --
    I'm sure "SlashdotMedia" will improve on all the wonders that Dice Holdings blessed us all with
  11. 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.

  12. Re:386dx, no coprocessor? by gregarican · · Score: 2, Insightful

    Nope that distinction didn't find its place until the Intel 80486 line of CPU's. Back during the 80386 days it was only differntiating between 16 and 32 bit handling --> http://encyclopedia.thefreedictionary.com/386+DX.

  13. 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."
  14. Re:surley OSP by Anonymous Coward · · Score: 2, Funny

    Yeah, but it would have that crappy Finnish porn.

    You don't care for Tom of Finland? To each his own.

  15. 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 Anonymous Coward · · Score: 3, Informative

      The 486 SX was just a 486 that they could not guarantee that the coprocessor would work so it was switched off.

    2. Re:No coprocessor... by teslar · · Score: 2, Insightful

      The point about Linus's machine having no coprocessor is actually true

      Nineteen years ago or so, I also got my hands on my first PC, pretty much same specs but with the coprocessor. My programming achievements at the time were pretty much limited to batch files. Linus wrote an OS on smaller hardware. Kinda makes me feel like I wasn't really using the full potential available to me :)

      Of course, I was 10 years younger at the time :)

    3. 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 :)

    4. 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.

    5. Re:No coprocessor... by ls671 · · Score: 2, Informative

      > The 486 SX was just a 486 that they could not guarantee that the coprocessor would work so it was switched off.

      Exactly, I thought mostly every /. reader knew that but reading the comments and replies makes me feel a little old... ;-)

      In short SX and DX where made at once, then on the testing stage, if the co-processor failed, they sold it as a SX, if it worked well, they sold it as a DX.

      Note that this principle is still applied today, I wrote about it previously to explain why overclocking sometimes work and sometimes don't:

      http://slashdot.org/comments.pl?sid=1246015&cid=28105441&art_pos=5

      --
      Everything I write is lies, read between the lines.
  16. Re:Alternate timeline... by sznupi · · Score: 3, Insightful

    Actually, Amiga would have been also a very valid choice back then, at least in Europe. I wonder if Linus ever said why he went with a PC.

    --
    One that hath name thou can not otter
  17. Re:As long as we're asking what if's... by Sir_Lewk · · Score: 2, Insightful

    What if Columbus was wrong? At a certian point, such speculation becomes meaningless ;)

    --
    "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
  18. Grattis på födelsedagen! by CaptainOfSpray · · Score: 3, Interesting

    Ja må han leva uti hundrade år!

    OK, I'm showing off - I lived in Sweden 18 years, became fluent in Swedish, and I'm guessing (from his name) that Linus is mother tongue Swedish rather than Finnish.
    But we're raising a glass and shouting "Skål" and "Gippis" and so on...

    --
    "Cock Up Your Beaver" does not mean what you think. This sig is intended to clog filters and annoy do-gooders
    1. Re:Grattis på födelsedagen! by ja · · Score: 3, Funny

      ... och sedan ska han skjutas, i en skottkärra fram!

      --

      send + more == money? ...
  19. Re:get real by LOLLinux · · Score: 2, Insightful

    Open source would be a lot better off with a few less egomaniacs like Linus and a few more - dare I say it? - RMS's.

    RMS not an egomaniac? lolwut? The whole GNU/Linux or GNU+Linux thing is nothing but pure egomania on RMS's part.

  20. 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.

  21. Re:over 40 by mrjohnson · · Score: 2, Interesting

    What about git? It's slowly taking over distributed source control...

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

    Everyone knows "42" is the real milestone.

  23. 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.

  24. Re:over 40 by Godji · · Score: 3, Insightful

    Oh, and by the way, Git.