Slashdot Mirror


Linus on GPL3 In Forbes

musicon writes "In an interview via e-mail with Forbes, Torvalds discusses GPLv3, digital rights management and sharks with laser beams. From the article: 'I'm sure changes will be made [to GPLv3]. The fact that the FSF and I have some fundamentally different views of what the GPLv2 was all about makes me worry that we won't find a good agreement on the next version.'"

37 of 316 comments (clear)

  1. oh man! by nb+caffeine · · Score: 5, Funny

    sudo apt-get install sharks-with-lasers_kernel_module

    --

    "Something's wrong with you...and I hope we never do meet again." - Deftones When Girls Telephone Boys
  2. I, for one... by UseTheSource · · Score: 3, Funny

    Welcome our laser beam-wearing shark overlords!

    --
    "Ein Volk, ein Reich, ein Führer." -Adolf Hitler
    "We are one Nation, we are one People." -The One 'leader'
  3. Couple of things here... by Kaellenn · · Score: 5, Interesting

    First off, please forgive my ignorance, but is it really *that* important for Linus to decide to move Linux from the GPLv2 to the GPLv3? Just because version 3 of the license becomes available does not automatically invalidate the version 2 license does it? Why is this such a hot button issue?

    For the most part, I completely agree with Torvalds on his points--and I can't say I'm at all surprised to see Stallman and the FSF take this direction with version 3. Simply put: they are "zealots" for lack of a better term. For them, free software is less about open source and open development and more about a form of political agenda.

    Now I'm not trying to bash Stallman or the FSF, they have made some wonderful contributions to the community. But let's call a spade a spade here and look at what GPLv3 is about: attempting to hide attempts to restrict developers under the guise of being an update to the world's most popular open source license. For all of the FSF's talk against bad copyright policy and software restrictions, this license introduces their own set as if to say, "we don't like their way; so you should definitely do it our way instead."

    Too much politics and agenda and not enough open source development.

    1. Re:Couple of things here... by GigsVT · · Score: 4, Interesting

      Is it even possible to relicense Linux under GPLv3?

      Did Linus get copyright assignments from every contributor? If not, then there's no way it can ever be really GPLv3, not legally.

      Even if the contributors put the "or later" clause, that would still give end users the option for using Version 2.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    2. Re:Couple of things here... by kfg · · Score: 5, Insightful

      For them, free software is less about open source and open development and more about a form of political agenda.

      Dude, copyright and patents are a political agenda by identity.

      KFG

    3. Re:Couple of things here... by GigsVT · · Score: 3, Informative

      You can't do that. With the "or later" clause, the end user gets to decide which license they will use.

      Unless you actually own the copyright you can't modify the license, so you can't take away the end user's right to choose GPLv2.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    4. Re:Couple of things here... by Akoma+The+Immortal · · Score: 3, Insightful

      "Zealots" again. Why cant you just use another word to qualify Stallman actions? Like CONSISTENT with his beliefs, STEADY in his view of Free Software.

      RMS did not change his views on developping software to empower users. The world of Open Source Software did and is in great danger of falling in the same trap again. This time DRM/DMCA and patents are the trap set by the corporations to gain control of OtherPeople IP (TM).

      RMS does not force you to abide by his rules. You can use whatever license you want and he wont have a say about it. Give the same respect to him.

      RMS does not call the proprietary leaders as "zealots", just "Hard Working Capitalist Businessmen Who Like to Ride the Curtains Of Other People IP (TM)". Shit he isn't even calling them or you anything.

      Respect is the fondation for all civil discussion.

      Regards,

      --
      assert(expired(knowldege)); core dump
    5. Re:Couple of things here... by Mr+Z · · Score: 3, Informative

      It's actually pretty simple. Portions of code licensed as "GPL v2 or later" can be incorporated into a GPL v2 program or a GPL v3 program. Portions of code licensed as GPL v2 only can only be incorporated with GPL v2 programs (or other licenses compatible with GPL v2, of which I believe there are precious few). GPL v3 is not strictly compatible with GPL v2, because it "adds additional restrictions." When you integrate GPL v2-or-later code into a GPL v3 program, the result is GPL v3.

      This is sorta like how BSD-minus-advertising-clause is "compatible" with GPL, in that such BSD code can be integrated into a GPL v2 program without violating the BSD license. The result is a GPL v2 program, though. You can't take GPL v2 code and integrate it into a BSD-licensed program and end up with something BSD-licensed, because of the requirements GPL places on requiring source with redistribution. Relicensing as BSD removes that requirement and thus violates the license on the GPL v2 code.

      As a user, the only impact of the "GPL v2 or later" clause is that I can pick which ever one suits my fancy. As it stands, GPL v3 places more restrictions on what I can do with the code than GPL v2, so as a user I'll probably pick GPL v2. If GPL v4 were to come along and say "Do whatever you like, you may as well consider this code public domain," then I as a user could go hog wild with it.

      As far as migrating the Linux kernel or any other GPL v2 app to GPL v3.... If the license on a bit of code is "GPL v2 or later," then it's trivial to make future versions "GPL v3 only." You can't "take back" the GPL v2-or-later versions, but you can make future versions GPL v3, removing the support for GPL v2. In Linux, portions of the kernel are GPL v2-or-later, so those portions can become parts of GPL v3 apps easily. The bulk of the kernel is GPL v2-only (w/ binary kernel module exception). So to bring the kernel into GPL v3 land, Linus would have to talk nearly everyone into either relicensing the kernel as GPL v2-or-later or GPL v3.

      --Joe
  4. Somewhat Dupe ... by karvind · · Score: 5, Informative
    Our earlier slashdot stories unless he explains more ..

    Torvalds Explains Dislike For GPLv3

    Linus Says No GPLv3 for the Linux Kernel

  5. Re: From my vantage point by XanC · · Score: 5, Insightful
    From my vantage point (and I may well be missing something important), it looks like the anti-GPL3 sentiment comes from a misinterpretation about encryption keys. If that's clarified, either in people's heads or the wording or both, I don't see any real negatives.

    I see a GPL that prevents companies from using DRM (which wasn't around for v2) to get around GPL requirements. Basically those same requirements that we liked from v2.

  6. Sweet! Zealot B.S. for the 7,000th time by Mateo_LeFou · · Score: 5, Insightful
    GPLv3 is closing loopholes, see the TiVo example, by which people could use other people's work and ignore their obligations under the license, i.e. by making the code modifiable but making modified versions of the code unrunnable.

    If Linus is fine with TiVo's method of coopting the kernel and making it for all practical purposes unmodifiable, that's his business. But lots of other people have contributed code to free software and are not.

    PS: this is how I understand it so far. My opinion is subject to revision

    --
    My turnips listen for the soft cry of your love
    1. Re:Sweet! Zealot B.S. for the 7,000th time by jimicus · · Score: 3, Interesting

      In the case of the first, there's no point in TiVo releasing code complete with any modifications. You can't use it anyway.

      There's been a similar thread discussing companies working around the GPL recently on my local LUG mailing list. In this case, discussion concerns a piece of hardware which uses GPL'd code but requires a hacked GCC to compile.

      The theory is:

      "The code says:

      int do_something(void) {
      #DO_SOMETHING
      }

      The compiler is hacked to insert the real code when it sees #DO_SOMETHING. The company which distributes the compiled source code doesn't distribute a compiler, so is not obliged to release the source code for the compiler itself, thus providing an end-run around the GPL."

      How true this is, I don't know. It's speculation. Please don't mod me up just because you think this makes sense!

      Essentially, GPLv3 adds a "Don't take the piss" clause. AIUI, the problem is putting this in legal parlance.

  7. Most popular OSS? by woobieman29 · · Score: 3, Interesting
    From TFA: "Torvalds' opinion matters because his program is by far the most popular open source program in the world."

    I'm not sure....would maybe Firefox have more overall users? Seems that it's on 80-90% of Linux boxes, plus an ever growing number of Windows machines and other OS's as well.

    --
    \/\/oobie
  8. I was thinking gcc. by cduffy · · Score: 5, Insightful

    Firefox is only on workstations -- headless servers typically won't have a web browser; my company's certainly don't. I was thinking gcc would be a better candidate: Not only is it installed on a strong majority of Linux-based systems, but also on a large number of traditional Unix systems elsewhere.

  9. GNU/Linux kernel? by amightywind · · Score: 5, Interesting

    I wonder if Linus even has the real authority to unilaterly switch to an alternative license. I don't think so. By his own admission he is not a deep thinker about the philosophical (he says polical) part of the job. Many of his colleagues are. Any change would have to be accepted by the core kernel developers. If not a fork is all but inevitable (GNU/Linux anyone?). My guess is he will talk like this from time to time but will be under pressure to maintain the status quo.

    --
    an ill wind that blows no good
  10. Crap, another question ...I have a lot to learn by Mateo_LeFou · · Score: 5, Informative
    GPLv3 code "crimps the style of mad scientists everywhere by also putting restrictions on the use of the source code. You cannot install it on your hardware (laser-equipped shark or otherwise) without also making sure that others can install another version"

    If I understand it right, and I prolly don't, you can install any modified version whatsoever on your sharks. Your obligations re: making keys available etc. do not kick in until you distribute the modified version. i.e. if you're a shark salesman rather than a mad scientist.

    Is that right?

    --
    My turnips listen for the soft cry of your love
  11. Ignore him. by Spy+der+Mann · · Score: 3, Insightful

    Linus isn't an activist. He's just a programmer. Sure, he made a wonderful kernel, but it's the GPL that made his kernel popular and freely-downloadable.

    In any case, does it really matter if he redistributes his kernel under GPL2 or 3? It's not like it's the end of the world or anything. I think this is plainly media hype.

  12. This just in GPLv4 = Sea bass by drrck · · Score: 5, Funny

    Due to the public outcry GPLv4 will no longer include sharks with laser beams. They have been replaced with Sea Bass. Extremely ill-tempered sea bass.

  13. I agree with RMS on patents but disagree on DRM by FlorianMueller · · Score: 4, Interesting
    For a long time it seemed to me that a distinction between Free Software and Open Source was hair-splitting: the key open source programs were Free Software at the same time. Now there are two trends that suggest a distinction may be increasingly necssary:

    • Oracle et al. try to acquire open-source projects by buying up the companies behind them.
    • IBM and like-minded large players try to effectively control open source based on their huge patent portfolios. Companies like Nokia sometimes say it pretty directly that they believe patents enable them to potentially open-source some code while still retaining ownership.

    Looking at those disconcerting trends, I very much support the GPL v3's approach to software patents. But when it comes to DRM, I think the FSF goes too far and addresses an issue for philosophical reasons that isn't worth it. DRM is a lot more legitimate per se than software patents are. Categorically opposing DRM may be perceived as downright anti-commercial by a number of people, and it's a move that I fear will only hurt the FSF and the GPL without changing anything about the fact that DRM is here to stay.

  14. Re:They didn't say you have to use GPLv3! by vertinox · · Score: 3, Insightful

    For all of the FSF's talk against bad copyright policy and software restrictions, this license introduces their own set as if to say, "we don't like their way; so you should definitely do it our way instead."

    RMS and the FSF aren't saying saying "All your old GPLv2's are invalid and now you must upgrade to our new GPLv3!!!"

    They are giving developers the options to restrict what others from restricting the next guy down the line from doing something with their work.

    You don't have to use GPLv3 if you don't want to.

    If someone else releases their work with a GPLv3 license and it bothers you...

    Then tough. The original author has the right to release it under any license he wants be it BSD, closed source, or GPL.

    If Linus doesn't want to use GLPv3 then it is his right. He can keep v2 forever. The GPL license doesn't belong to RMS. He just made up the wording of the contract that others can use to release software with.

    No one is being forced to anything they don't want to...

    Well other than the people who are being restricted from adding DRM and various freedom restricting to other people's work released in GPLv3.

    Well if you really want that DRM so bad... Then make your own program from scratch. Don't use someone elses open source code whose express wish is to not have his work used in ways he did not mean it to.

    GPLv3 gives the original author this ability.

    --
    "I am the king of the Romans, and am superior to rules of grammar!"
    -Sigismund, Holy Roman Emperor (1368-1437)
  15. Zealotry can be good by amightywind · · Score: 4, Insightful

    Simply put: they are "zealots" for lack of a better term. For them, free software is less about open source and open development and more about a form of political agenda.

    Stallman repeatedly states that software freedom is his goal, and not its widespread adoption by "practical minded" corporations. He has nothing against corporations if they do not interfere with his primary goal. That make's him a zealot, I guess. I call it clear thinking. Time and again he has been proven correct in the face of criticism.

    --
    an ill wind that blows no good
  16. Fallen hero or lone wolf? by Spy+der+Mann · · Score: 3, Interesting

    You cannot install it on your hardware (laser-equipped shark or otherwise) without also making sure that others can install another version. And that's my gripe.

    Call me a fanatic, but open source isn't worth crap if it can't be redistributed. This is _THE_ principle of open source, that anyone can make AND RUN their own version. There are business-ready licenses out there, but the GPL was made to perpetuate the programmers' and users' freedom.

    I think Linus needs a reality check. Perhaps a few months of working for Microsoft will make him realize his mistakes. There ARE evil people, evil corporations trying to take over the world, just look at the patent business.

    I'm kinda disappointed after reading this, I always had seen Linus as a hero, and thought he was as enthusiastic about open source as many of us were. Sad to see he's just yet another programmer who went corporate, like Steve Jobs. He just happened to cooperate with the open source movement.

    Oh well. We should be thankful he's still cooperating, and consider him an ally rather than a leader.

  17. MOD PARENT UP by Anonymous Coward · · Score: 3, Insightful

    Yes! I'm confused as to how Linus gets this part wrong. Mad scientists (or the military, or Microsoft, etc.) can use modified GPLv3 code however they want. However, if they try to distribute the code to the public (they sell software, or hardware with software on it), then they have to make it possible for the recipients to:

    1. See the code.
    2. Modify the code.
    3. Run the modified code.

    Private shark zoos are not subject to any restriction. Shark salesmen, however, would be required to make the source available, so that you could modify the way your shark-laser system works.

    The TiVo example is a better one. If I buy a TiVo, and it uses GPL code, then I should be able to modify that code and run the modified code on that hardware. Their modifications are functionally useless to me (to the world) if I cannot run the modified code on the hardware. Yes, in theory I could build my own TiVo from scratch... but that's not practical. So why should GPL programmers license their code that way?

  18. GPLv3 is not anti DRM. by Stalyn · · Score: 3, Insightful

    GPLv3 is anti-evil-DRM in which the GPL would be circumvented by DRM methods. Such as providing you with the source code by unable to compile/run it because of DRM. Yet GPLv3 as I understand it does not say you can not include DRM in your software, you are free to do so.

    I just find Linus too trusting of business. You would think he would have learned his lesson with BitKeeper but in the end I think he blames Andrew Tridgell instead of BitMover. Even RMS may be too distrusting of business, but isn't it better to be safer than sorry?

    --
    The best education consists in immunizing people against systematic attempts at education. - Paul Feyerabend
  19. Bitkeeper anyone? by John+Jamieson · · Score: 4, Insightful

    Why the facination with Mr. T's thoughts on the GPL? He really isn't that big of a believer in Open Source. It just happened to be the vehicle that propelled him to fame. IT IS HIS RIGHT TO NOT REALLY CARE ABOUT OPEN SOURCE!

    But what is this thing that /. seems to have about pretending there is this big NEW rift in the open source movement with Stalmans GPL v3? There is no rift, you have Stallman who is a believer, and Linus, who couldn't really give a crap as long as he can keep working unencumbered. That is why he chose bitkeeper, again, that is his right, as long as he does not pose as an Opensource poster boy(I don't think he usually does).

  20. Re: From my vantage point by dgatwood · · Score: 4, Insightful
    Not a misinterpretation, a legitimate difference of opinion. RMS wants to make sure that GPLed software can be recompiled by the end user and replaced with an altered version, which is why that was put in the license. By contrast, Linus wants TiVo to continue using the Linux kernel, and TiVo doesn't want to allow users to create custom kernels and still have a usable TiVo, as the ability to do so would potentially allow users to easily break their DRM scheme.

    No, one of the fundamental GPL v3 changes is, by intentional design, antithetical to the continued proliferation of Linux in certain types of embedded devices, including TiVo-like devices, set top boxes, etc. Thus, there is and always will be a fundamental tension between RMS's notion of ideal freedom and the Linux community's goal of "Linux everywhere".

    This isn't something that can be changed by a simple wording change. IMHO, GPL v3 is basically DOA as far as the kernel is concerned; you can pretty much be guaranteed that if Linus did try to push GPL v3 into the kernel, all the embedded Linux developers would fork, and that fork would result in some really ugly politics and a very dramatic decline in the number of Linux (v3) kernel developers.

    --

    Check out my sci-fi/humor trilogy at PatriotsBooks.

  21. Commercial vs. Proprietary by mengel · · Score: 4, Insightful
    You're falling for the classic confusion here (which the FSF "purists" are trying to correct) that doing commercial software somehow requires being proprietary.

    The FSF folks would be ecstatic to have busnesses actually embrace the open source model, be commercial, and sell lots and lots of support, installation, and maintenance for software that is still modifiable by the end customer.

    People keep trying to paint the FSF folks as anti-commercial, or anti-business. They are most assuredly not. They are trying to educate companies and the public about a better way to do software, whether as a business or not.

    And neither companies nor people should adopt FSF principals out of altruism. They should adopt them because they realize that once customers understand what the free software rights really do for them, they will begin to demand them by not doing business with companies that don't grant them. Just as you wouldn't buy a car from a dealer if you could only ever get it fixed at that dealership (for whatever rates they choose to charge), you will stop buying software that can only be modified by that software company. It doesn't mean you won't go to the dealer for some or all repairs, it just means you don't want to be forced to.

    Of course, pushing the car analogy, this only really happens when you become aware of local car repair companies. And this is where companies like IBM can really help -- by offering the "Jiffy Lube" of free software -- a national, well known chain of software maintenance, configuration, and repair for open source.

    --
    - "History shows again and again how nature points out the folly of men" -- Blue Oyster Cult, 'Godzilla'
  22. GPL v3 makes compliance verifiable by quentin_quayle · · Score: 5, Informative

    Suppose a vendor creates a distro, Blue Hat. It's designed for platform P but P is made to require binaries signed by Blue Hat, it won't run anything else. Now Blue Hat releases a body of source code and claims to have complied with GPL v.2.

    Now has Blue Hat complied with GPL v.2? No one outside Blue Hat can know. The only way to verify that some source corresponds to the binary you're running is to compile it and run the result. If you can't do that without a key, and Blue Hat won't give you a suitable key, they could violate GPL with impunity.

    It doesn't require that BH give up their ultimate private key, just one sufficient to sign source. This is all that GPL 3 requires in regard to DRM and keys.

  23. On the wrong side of the battle by RLiegh · · Score: 4, Interesting

    Morally, Linus is on the wrong side of the DRM battle, since he supports it (and is willing to be used as a PR pawn by Forbes), however Pragmatically, he's on the right side of the battle, since DRM is ineveitable and perhaps by doing their bidding, the robber barons^W^W business world will allow him to continue living^w coding.

    Stallman may be right morally, but so was John The Baptist; and look at what happened to him.

  24. Re: From my vantage point by Mr+Z · · Score: 3, Insightful

    Just to throw my two cents in, that's exactly how I read it as well.

    The thing is, if we really do get "Linux everywhere," enough people are going to want to start hacking that it'll create an economic incentive to cater to the hackers. Witness the Linux variant of the WRT54G.

    IMHO, DRM will only die by collapsing under its own weight, and by heightening consumers' awareness of the issues. Fighting DRM head on by denying access to its underlying technologies (when, as Linus states, those technologies themselves aren't inherently evil) isn't going to work.

    --Joe
  25. tainted by GrumpyOldMan · · Score: 3, Funny

    $ dmesg
    sharks-with-lasers: module license 'mad scientist' taints kernel.

  26. Linus RMS by MrCopilot · · Score: 4, Insightful
    Linus "I'm pretty happy with the GPLv2, and I just don't have the motivation or inclination to start talking to lawyers. I'm a programmer. I worry about kernel bugs."

    RMS "Pragmatically speaking, thinking about greater long-term goals will strengthen your will to resist this pressure. If you focus your mind on the freedom and community that you can build by staying firm, you will find the strength to do it. ``Stand for something, or you will fall for nothing.''

    Pretty much sums it up. I'm sure RMS doesn't like talking to lawyers either, he just has Beliefs and convictions that force him to. (No offense Mr MOGLEN)

    I will adopt GPL v3 as soon as finalized. I have much more faith in the "Ramblings" of RMS than the casual "Who Cares" of Linus. Great as the kernel might be. Without the Convictions of Stallman and GPLv2, Most of us would still be Running Proprietary OS's and paying for several different Compilers and toolsuites and Graphical toolkits, ad infinitum. We have those choices now because Stallman sat down with a few lawyers despite his distaste for authority. There is something to be said about beating the big guys with their own stick, Software Licenses

    Note to Article Author: I believe GCC is a little more popular (at least in terms of users) than Linux or Firefox. And that was written by?

    Ramble on RMS

    --
    OSGGFG - Open Source Gamers Guide to Free Games
  27. Has Linus misread the DRM provisions in GPL3? by Trestran · · Score: 3, Informative
    Maybe someone can explain this to me, but I'm not sure if GPL3 is saying what Linus says (or thinks) it's saying.

    I watched some of the explanations on GPL3 given by RMS and Moglen here, and they seemed fairly adamant about the fact that GPL3 did not forbid the use of DRM-ish encryption/authentication in code that falls under it, just that any keys necesary for running it need to be given to the user.

    Same deal for Trusted Computing-esque machines; it's perfectly fine to make a machine that uses keys to restrict usage of the machine maker's code that falls under GPL3, as long as they give the keys to the end-user. It's even fine to make a seperate key for each and every machine, only give it's unique key to one single end user tied to his or her machine. Just as long as the end-user gets those keys:
    RMS: Now, if each machine has a different signature key, they only have to give your signature key to you. Your machine's signature key. They have to give it to you, they don't have to publish it, they don't have to give it to anyone else. They can even promise you that they won't give it to anyone else, but they have to give it to you.
    Or as the GPL3 licence puts it:
    Complete Corresponding Source Code also includes any encryption or authorization codes necessary to install and/or execute the source code of the work, perhaps modified by you, in the recommended or principal context of use, such that its functioning in all circumstances is identical to that of the work, except as altered by your modifications. It also includes any decryption codes necessary to access or unseal the work's output. Notwithstanding this, a code need not be included in cases where use of the work normally implies the user already has it.

    Complete Corresponding Source Code need not include anything that users can regenerate automatically from other parts of the Complete Corresponding Source Code.
    Reading through the DRM clause it mentions "no permission is given to distribute covered works that illegally invade users' privacy" which is already "illegal", so you wouldn't be allowed to do it anyway, and "[no permission is given] for modes of distribution that deny users that run covered works the full exercise of the legal rights granted by this License" which you wouldn't be allowed to do anyway, without breaking the licence.

    Or is this dispute about some other part of the new licence?
  28. Gross out by FishandChips · · Score: 3, Insightful

    If Torvalds declared he was simply walking away from it all, one really couldn't blame him considering the sometimes disgusting criticism levelled at him. And what has he done, apart from helping to give the world a free operating system, inspiring the open source movement and saying simply "Please treat me with the freedoms and respect I extend to you"?

    Mr Torvalds is just one guy, an engineer with an optimistic, congenial outlook on life, not a professinal advocate or evangelist with a foundation or six behind him full of law professors. Have Lessig and Moglen condemned some of the personal criticism levelled at Torvalds or would that be too much like hard work?

    Yet as a hard-working regular guy Torvalds has a better grasp of daily realities than many of his critics. Tightening up on software patents is a good idea, but rejecting DRM as the devil's work is a poor idea, perhaps simply immature. As the underdog in this affair he gets my support every time. If a better, revised GPLv3 emerges, one that two people or more can actually understand and agree upon, which is more than can be said for the present draft, then Torvalds will deserve our gratitude for sticking up for what he believes despite the hyena-like behaviour of some in the open source world.

    --
    Las qué passoun
    tournoun pas maï
  29. Mr. T's thoughts on the GPL by SoTuA · · Score: 4, Funny
    Why the facination with Mr. T's thoughts on the GPL?
    I pity the fool... who doesn't provide source with the binaries.
  30. Torvalds should stick to technical matters. by jbn-o · · Score: 3, Insightful

    I wonder if Linus even has the real authority to unilaterly switch to an alternative license.

    He doesn't. The Linux kernel hasn't been under his exclusive copyright for most of its existence. Not even his fork is under his copyright alone because he doesn't collect copyright assignments from contributors to his fork. This seems to me to be right in line with the general lack of foresight and considerable confusion about software freedom I've come to associate with him (see his use of Bitkeeper and his objection to Andrew Tridgell's work on a Bitkeeper repo pulling program for other examples).

    By his own admission he is not a deep thinker about the philosophical (he says polical) part of the job.

    All the more reason why Forbes should have interviewed people who are deep thinkers about issues relevant to the GPL: RMS, Eben Moglen, or someone from the FSF who could have spoken with more insight and a clear understanding of what the license is meant to achieve. Interviewing Torvalds about licensing is usually fruitless because he gets another chance to demonstrate how much he doesn't understand the goals of the license and how much he doesn't agree with what he doesn't understand.

    He claims that use of GPL-covered programs is restricted by the first draft of GPLv3: "You cannot install it on your hardware (laser-equipped shark or otherwise) without also making sure that others can install another version.". That is a good thing because that's critical to software freedom. His criticism is confusing: he professes to want to be allowed to fix things, yet he criticizes along the lines of preventing people from stopping users to be able to fix things. He also doesn't seem to understand that others might want to tinker things he doesn't want to tinker with (a dishwasher or a DVR). Heaven forbid anyone wants to change the length of a wash, rinse, or dry cycle or a DVR that only deletes recorded programs when the user says to do so.

    He views the GPLv2 as a contract: "However, I don't think that's part of my GPLv2 contract." and Eben Moglen made it quite clear in his detailed discussion of GPLv3 that the GPL has not been and will not be a contract. There's even a section in the draft GPLv3 called "Not a Contract". I'd rather take Moglen's legal advice than Torvalds', particularly when it comes to interpreting the GPL.

    It's also hard to take Torvalds' complaints seriously because he refuses to become a part of the year-long revision process, even by submitting comments to the GPLv3 FSF site.

    If not a fork is all but inevitable (GNU/Linux anyone?). My guess is he will talk like this from time to time but will be under pressure to maintain the status quo.

    GNU/Linux isn't a fork, it's the GNU operating system featuring the Linux kernel. This is distinct from the GNU operating system featuring a kernel from one of the BSD systems, or the official GNU operating system which runs with the HURD.

  31. Re:See the crusaders march by frank_adrian314159 · · Score: 4, Insightful
    Do employees get the source code for their payroll system if it runs on Linux?

    Why not? It's the data and binaries in the payroll system that need to be secure, not the source code.

    --
    That is all.