Slashdot Mirror


Torvalds Critiques of GPLv3 and FSF Refuted

j00bar writes "After Linus Torvalds' impassioned critiques of the second draft of GPLv3 and the community process the FSF has organized, Newsforge's Bruce Byfield discovered in conversations with the members of the GPLv3 committees that the committee members disagree; they believe not only has the FSF been responsive to the committees' feedback but also that the second draft includes some modifications in response to Torvalds' earlier criticisms." NewsForge and Slashdot are both owned by OSTG.

548 comments

  1. I can see both sides by Lord+Kano · · Score: 5, Insightful

    The FSF intends to use the GPL as a means to prevent people from doing certain "bad" things with free software. I get that and I support the idea. Linus seems to have chosen the GPL for practical reasons. He didn't want the code that he and so many others poured their hearts and souls into to be stolen and closed like the Cedega situation.

    I suspect that Linus just wants to make his software while the FSF wants to change the world.

    LK

    --
    "Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano
    1. Re:I can see both sides by Anonymous Coward · · Score: 5, Insightful

      "He didn't want the code that he and so many others poured their hearts and souls into to be stolen and closed like the Cedega situation."

      The thing is, changes in the GPL (mainly those dealing with DRM) are absolutely necessary if you don't want code to be "stolen and closed." It's not some theoretical, idealistic thing. It's an extremely practical consideration.

      If you write a program and release it under the GPL, and if it's permissible to make derivative versions that will no longer run when modified (due to DRM in hardware), then I can take and build upon your code and never give the improvements back. You may be able to see the source, but you can't use my changes because your future alterations will no longer execute on the hardware you own. I can also sell hardware including your code, and even though the GPL intends that my customers should thus have the right to modify the code -- they can't.

      Allowing commingling of DRM and GPLed code is a huge loophole. It essentially allows someone to make a proprietary branch of your code. From then on, you can still look, but you can't touch.

      As for patents, that's another very similar situation. By claiming patents on my modifications to your GPLed code, I can make my own proprietary branch of your code. You can no longer build upon my changes, because to do so would be a patent infringement... but I can freely take yours.

    2. Re:I can see both sides by dbIII · · Score: 2, Interesting
      The FSF intends to use the GPL as a means to prevent people from doing certain "bad" things with free software
      There are two things to think of that are important about this - first,it will also stop things that are not "bad" by the FSF definition, second - the FSF didn't write the software and does not own the copyright on it or have any obligation owed to them by the authors - attempted name changes or not.

      It is up to the FSF to convince the authors that any new licences are a good idea - the implication that the authors haver to do what the FSF says at all - especially when it is only a draft version of the new licence - is an odd way of looking at things. Effectively to get linux th use a different licence the FSF has to convince Linus, nearly every other kernel developer and all the groups that package distributions that it is a good idea, and even since a superficial look at the new draft licence turns up some problems there is more work to be done. Going out of your way to hurt companies that already comply with the GPL and add to the devlopment of free (as in look it up in the dictionary not make up your own meanings) software but have signed binaries on their hardware may be seen as "collatoral damage" by the thoughtless - but surely the FSF and other contributors can do better than that?

    3. Re:I can see both sides by DrJimbo · · Score: 5, Insightful
      Lord Kano said:
      I suspect that Linus just wants to make his software while the FSF wants to change the world.
      The FSF wants to change the world so that people like Linus will continue to be free to create and modify their free and open source software.

      Without the DRM provisions in the GPLv3 that Linus is complaining about, we could eventually face a situation where it is literally impossible to develop FOSS for the latest generation of computers. Worse, those computers could be running the GPLv2 software we wrote even though we have lost all of our rights to further modify it and we've lost the right to even choose what software we run on our own computers.

      --
      We don't see the world as it is, we see it as we are.
      -- Anais Nin
    4. Re:I can see both sides by init100 · · Score: 5, Insightful

      You may be able to see the source, but you can't use my changes because your future alterations will no longer execute on the hardware you own.

      The way Linus sees it is from the "developer" viewpoint. The code is still free from this viewpoint, since all modifications are published. You can modify it and run it on a DRM-free machine. The FSF rather thinks of the "end users" viewpoint, where modifying the code and running the modified code on the same machine is paramount.

      For myself, I understand Linus view, but I tend to go along with the FSF view. Being unable to modify free software on a hardware device and run it on the same device violates the spirit of free software. The vendor could build upon the mountain of free code, saving a lot of money in the process (i.e. not reinventing the wheel), but does not grant any of these freedoms to their customers.

      So to sum it up, I'd say they can write their own OS, or license a commercial one, if they don't want to give their customers the same freedoms they have.

    5. Re:I can see both sides by Pecisk · · Score: 1

      Problem is there that FSF actually wants to prevent BAD business practices (like bullying customers with DRM and patent stuff), but GPLv3 is definetly not a right way to do it.

      I can see both sides too and Linus have lof of it's points right (DRM is *legitive* way of protecting something, now what, we could not have crypt software in GPLv3? Crypt software in combining with hardware - I see lot of real legal use).

      If you don't like DRM - don't buy products with it (Music CD and DVDs). If you don't like software patents, campange and make it real for change like Europeans do. Make people aware about those serious issues, but not with THIS licence. That is the only real way to deal with it.

      --
      user@ubuntubox:~$ stfu This server is going down for shutdown NOW!
    6. Re:I can see both sides by Ohreally_factor · · Score: 0, Troll

      we could eventually face a situation where it is literally impossible to develop FOSS for the latest generation of computers

      Care to explain how this scenario is actually supposed to play out? And does your example require that the hardware makers conspire against OSS?

      I no longer trust the FSF. I know a power play when I see one, and this isn't about freedom and fairness. They want to dictate how people use software. It's no longer about distribution.

      You want a social revolution? Then let it happen, let it play out. If you want to push it forward, go develop something. If you're not a coder, go write or create something and release it under a CC license. The Revolution that the FSF is selling is top down, Stalinist/Leninist. I much prefer Linus's way, which reminds me more of a different Lennon.

      --
      It's not offtopic, dumbass. It's orthogonal.
    7. Re:I can see both sides by Znork · · Score: 2, Insightful

      "It is up to the FSF to convince the authors that any new licences are a good idea"

      Partly. Most programs under the GPL retain the GPL v.2 or later options, meaning redistributors and authors of derivative works can update the license to the newer version at their discretion. This is by design, so that the FSF can update the GPL, should loopholes appear or technology change the situation and allow code to be updated to more recent versions, _even when authors are out of touch or dead or otherwise_.

      The Linux kernel version of the GPL, however, does not retain that clause, rendering it stuck permanently in v2 land; and as the kernel, unlike FSF driven projects, doesnt require copyright reassignment, it would be more or less impossible to accomplish a change.

      Which means that a) the linux kernel is vulnerable to changes in law and technology that may render the v2 GPL ineffective and b) what Torvalds thinks is really has little bearing on the issue.

      "look at the new draft licence turns up some problems"

      I see no problems. The new version closes several holes; to get affected by them you'd have to have been willfully abusing those loopholes, violating the intent and spirit of the GPL. It's not as if the FSF's views are a well kept secret, so any due diligence would have made it obvious that such loopholes would be closed down.

    8. Re:I can see both sides by Ohreally_factor · · Score: 1, Interesting

      Being unable to modify free software on a hardware device and run it on the same device violates the spirit of free software. The vendor could build upon the mountain of free code, saving a lot of money in the process (i.e. not reinventing the wheel), but does not grant any of these freedoms to their customers.

      But the vendor must still publish the source of any changes he makes to the code. So the vendor is giving back. If you don't like that a vendor's device is locking you out, don't buy it. Is that so hard? Do you think you can avoid buying something you don't want on your own, or do you need the FSF to protect you from your own bad buying decisions?

      Meanwhile, for whatever reason, I want to buy this hypothetical vendor's device. Maybe I have a certain application where I want a TPM set up. Because the FSF wants to protect me from myself, I no longer have the choice to buy a machine that will run OSS.

      That's the sort of world we'd have if the GPLv3 became the dominant license. Yuck.

      --
      It's not offtopic, dumbass. It's orthogonal.
    9. Re:I can see both sides by temcat · · Score: 2, Interesting

      I'm afraid that soon DRM will be implemented everywhere at a low level so you'll have to completely refrain from buying any devices that can run user code, because neither of them will let you run what you choose.

    10. Re:I can see both sides by NMerriam · · Score: 1

      It doesn't require a conspiracy to change hardware, just economies of scale. If someday both Windows and the Mac OS require hardware with TPM/DRM at the boot level, then that's what 99% of the hardware available will have built-in. other options will be more expensive due to their niche status (and I'm sure Linux will be really popular when it requires a more expensive computer to run than Windows does!).

      If you find such a situation impossible to believe, just compare the price of a winmodem to a real modem and imagine the whole computer were built with the same marketing principles.

      --
      Recursive: Adj. See Recursive.
    11. Re:I can see both sides by dbIII · · Score: 1
      The FSF can update the GPL ... even when authors are out of touch
      Are you saying the FSF can switch the work of an author to a different licence when the authors are opposed to the new licence and this is a good thing? If you don't turn the copyright over to the FSF this is not possible - and I've always believed the author should retain the copyright of the work to stop exactly this sort of sillyness happening.
      what Torvalds thinks is really has little bearing on the issue
      If the views of the author do not have any bearing on the issue then something is seriously wrong with the copyright system that allows it to happen - whether it is a very good licence with some new clauses that mess thing up or some other thing.
    12. Re:I can see both sides by Ohreally_factor · · Score: 0, Troll

      And you base this fear on what?

      DRM is a boogie man that RMS is using to scare you and get you juiced up.

      --
      It's not offtopic, dumbass. It's orthogonal.
    13. Re:I can see both sides by sumdumass · · Score: 0

      The Xbox can run linux, Dlink routers can run linux, playstations and ipods can run linux, robots can run linux, Sun workstations can run linux, almost everything can run linux.

      My point isn't that you can buy one of these instead of a workstation, my point us that non of these at one point in time was ever supposed to run linux and now they can. DRM or not, you will be able to run linux (or whatever you want). The whole DRM thing has a trusted and non trusted enviroment. At worst case scenario, you won't be able to run certain propriatary apps when running nonDRMed stuff. big deal, sounds like your don't want to run them anyways.

      I too think this GPLv3 is going in a bad way. and i have other reasons then just this for thinking this way.

    14. Re:I can see both sides by Ohreally_factor · · Score: 1

      So, you're basically saying that there won't be hardware available for a reasonable price, because OSS can't compete with Windows or Mac OS on it's own merits. You don't think it will be possible to order a general purpose computer with TPM/DRM disabled? Do you really think that non-locked computers are going to just disappear?

      Here's the thing about the GPLv3. It's taking away more freedom from both the developer and the user. It will prevent the developer from developing for whatever hardware he wants and it will limit OSS users choice. And this is being done in the name of Freedom. But whose freedom? The two most concerned parties just lost some freedom. Society's freedom? What is that exactly? Does Society's Freedom equate with The Power of the Collective?

      --
      It's not offtopic, dumbass. It's orthogonal.
    15. Re:I can see both sides by cortana · · Score: 1
      If you don't like DRM - don't buy products with it (Music CD and DVDs).
      What am I to do once all computers come with these 'defective by design' chips? When I am no longer able to access my bank account, or government services, because my computer will be unable to validate itself to the remote servers? When it becomes illegal to manufacture, import, or operate hardware without Trusted Computing features?
    16. Re:I can see both sides by Pecisk · · Score: 2, Interesting

      So you think licence is right way to fight it? That GPLv3 will push hardware manifacturers, RIAA, MPAA and rest of parasyte crowd say "ohhh, our bad, let's move back to old, good way of earning money?"

      Sorry, but in reality, it requires political fight, because our opponents have took it to political level - they don't want to market to deside that DRM is bad, they want law that protects DRM. They don't want to market to deside how much value is in code or product, no, for that they go to politics and buy new, shiny patent law.

      Change THAT system. Licence won't help us. Change customer's attitude. Organise boycots. Don't buy Macs. Don't buy ATI or Nvidia video cards. Seriously. Vote with your wallet. Vote with your attitude. Inform rest of the crowd.

      Stallman could have listen to Linus and allowed clearly several uses of DRM with GPLv3 licence. I think everyone would be happy. Yep, maybe it would be a little bit more difficult to understand, but anyway...

      I am not against Stallman, or for Linus. Both they have some right points and some false. Linus is a little bit flamer - but he has been always, for example, he trashed GNOME, which I use - but at least he some right to do it. And at least he give some serious points from developer's side.

      And yes, Stallman rocks as ethical leader or politican, because he sees bigger picture. What he needs is to be more constructive and learn new ways to achieve his goals.

      --
      user@ubuntubox:~$ stfu This server is going down for shutdown NOW!
    17. Re:I can see both sides by Anonymous Coward · · Score: 0

      If you haven't been living under a rock for the last couple of years, you must have noticed that there is a strong movement towards making every PC a DRM-locked machine. At least certain hardware features (like HD video output) will be unaccessible to software which didn't go through some kind of certification. What good is your right to use the modified software on DRM-free machines when you can't buy them anymore?

    18. Re:I can see both sides by Knuckles · · Score: 1

      Are you saying the FSF can switch the work of an author to a different licence when the authors are opposed to the new licence and this is a good thing?

      He's saying that if the copyright holder licensed it "under v2 or later, at the user's discretion", then the user* (surprise!) has the option to license "under v2 or later". It is a good thing because by choosing this method the copyright holder has said that it is a good thing.

      * "User" = anyone bound by the license, i.e. anyone who is redistributing

      If the views of the author do not have any bearing on the issue

      The views of the author do have bearing. It's just that Linus is not the only author or copyright holder of code in the Linux kernel, and the kernel is distributed under GPL v2 and NOT "or later". In fact, Linus only has copyrights to a small part of the code. Therefore all (or at least a overwhelmingly big majority of) copyright holders would have to agree to a license change. This will not happen. Therefore Linus's opinion about a license change is pretty irrelevant.

      --
      "When I first heard Daydream Nation it quite frankly scared the living shit out of me." -- Matthew Stearns
    19. Re:I can see both sides by killjoe · · Score: 1

      Xbox can run linux but only if you break the law. That's the thing. In order to get linux to run on the xbox you are risking jail time.

      --
      evil is as evil does
    20. Re:I can see both sides by quintesse · · Score: 2

      Sure, and how many XBoxes can you buy that run Linux? The fact that somebody _can_, at some time, hack around the DRM and install Linux does not mean that it is a viable alternative. We are lucky that we can actually watch DVDs on Linux, not because some guy figured out how to decode the data but the fact that his work isn't considered illegal (yet) in a lot of places. But still, most distros don't include the necessary code just to be on the safe side. Thing is that I don't think that Linux will be a popular and viable OS in the future if people have to _knowingly_ break the law just to make it do the most basic of things: run it.

    21. Re:I can see both sides by cortana · · Score: 1
      So you think licence is right way to fight it?
      It is an important part of the fight. Isn't the phrase 'combined arms'?

      Buy a Tivo. Ask the manufacturer for the source code (as is your right, granted by the GPL) and you will recieve it. But now try to modify it--you can't, because the Tivo's DRM takes away the freedom granted to you by the authors of the code to run modified code. This is what the DRM clauses of the GPLv3 aim to prevent.

      Change [the corrupt political/legislative] system. Licence won't help us. Change customer's attitude. Organise boycots. Don't buy Macs. Don't buy ATI or Nvidia video cards. Seriously. Vote with your wallet. Vote with your attitude. Inform rest of the crowd.
      The license will help us. These days I think the license is the only thing that can help us. I boycott a lot of products, and to be perfectly honest it makes no difference in the real world.

      Stallman could have listen to Linus and allowed clearly several uses of DRM with GPLv3 licence.
      What do you call the clarifications and changes made to the DRM clauses between the first and second drafts of the GPL?

      Only Linus and the Slashbots who follow him seem to be spouting these claims. It is becoming harder and harder to attribute his comments to incompetence, rather than active malice.

      From TFA, "Torvalds' comments should probably be read in the context of his statement that his particular concerns, notably the mention of DRM, have not been addressed. Yet, in fact, they have been. In an interview with NewsForge, Eben Moglen, who heads the revision process, specifically mentioned that some changes in the second draft were specifically made in response to Torvalds' concerns..."
    22. Re:I can see both sides by Ohreally_factor · · Score: 1, Flamebait

      You know what's really funny? The vast majority of us on slashdot rightfully get up in arms when politicians play the terrorist card to take away our civil liberties. But we don't see it when one of our own does it to us. Instead we are ready to give up freedoms now because if we don't, then at some vague point in the future, DRM is going to lock us out of our computers.

      --
      It's not offtopic, dumbass. It's orthogonal.
    23. Re:I can see both sides by jellomizer · · Score: 1

      FSF is doing the same thing that a lot of other groups are doing. Mixing to many political Ideas into their organization. This is what I think is the biggest mistake that organizations make. It happens all over the place. Pro-Life groups promoting the War Against Iraq, Pro-Choise groups promoting More Taxes for the Rich. Environmental Groups promoting legalized drugs, Religious reform groups promoting the death penalty. These groups are all loosing focus and are basically becoming Democrats Shills or Republican Shills. While the reason these groups add these ideas is so they get more political interests and their words get heard more and get more people in higher position to get their word across. But the down side is while their word is better broadcasted less people are following it because while they agree with some points others they may oppose. So Say I am a Pro-Life, Environmentalist, who opposes the death penalty, But support the war in Iraq (Not actually my true position on these but a centered answer). So it will be difficult to fund or join any group because they all have parts which I oppose.if I join any group will be considered an outcast for my heretical beliefs. The same with GPL 3. It is expanding an Idea to add more charged items to the list While I am sure most people who support GPL don't care for DRM but a good amount do. So this will cause more people to shift away from GPL just for being to restrictive.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    24. Re:I can see both sides by spuzzzzzzz · · Score: 2, Insightful
      Here's the thing about the GPLv3. It's taking away more freedom from both the developer and the user. It will prevent the developer from developing for whatever hardware he wants

      Please explain to me how the existence of the GPLv3 will prevent developers from licensing their software under the GPLv2.
      --

      Don't you hate meta-sigs?
    25. Re:I can see both sides by replicant108 · · Score: 2, Informative

      He didn't want the code that he and so many others poured their hearts and souls into to be stolen and closed like the Cedega situation.

      And that is exactly why the GPL is being updated.

      Make no mistake - RMS may be driven by ethics, but the GPL is a practical solution to a practical problem.

    26. Re:I can see both sides by MichaelSmith · · Score: 1
      The Xbox can run linux

      The 360 can't yet, and the work required to get it running may run (if measured) into the millions of dollars.

    27. Re:I can see both sides by Ohreally_factor · · Score: 1

      You've got a good point. I better wipe the froth off of my mouth before someone thinks I'm rabid.

      --
      It's not offtopic, dumbass. It's orthogonal.
    28. Re:I can see both sides by Anonymous Coward · · Score: 0
    29. Re:I can see both sides by 5937 · · Score: 1

      "If you don't like that a vendor's device is locking you out, don't buy it. Is that so hard?"

      Can be as hard as not using ms-office.

      Also by allowing to run modified code they allow they allow customers to hire people for added features.
      Extends job-market for OSS-programmers, ie the people who wrote the stuff in the first place.
      That kind of advertising is taken away with DRM.

    30. Re:I can see both sides by 5937 · · Score: 1

      "Do you really think that non-locked computers are going to just disappear?"

      Non-windows-preloaded did.

    31. Re:I can see both sides by Rogerborg · · Score: 1

      Fair enough, but a bunch of developers who adopted the boilerplate "version 2 or later" license are going to get scorched. Their fault, mind.

      --
      If you were blocking sigs, you wouldn't have to read this.
    32. Re:I can see both sides by Ohreally_factor · · Score: 1

      That's never been true. It has always been possible to purchase a computer without having windows pre-loaded. Where do you people come up with this stuff?

      --
      It's not offtopic, dumbass. It's orthogonal.
    33. Re:I can see both sides by 5937 · · Score: 1

      By looking at mainstream-shops. The shops and prices where our users buy hardware.

    34. Re:I can see both sides by Anonymous Coward · · Score: 0

      And I can take your changes, which are required to be released, and modify them to remove the DRM portions.

      I may not ever be able to use closed hardware that relies on DRM, but that's the same as other closed hardware situations today.

      The Stallman / FSF positions are impractical. They go beyond 'freedom' into the realm of anti-commercial.

    35. Re:I can see both sides by Rutulian · · Score: 5, Insightful

      The way Linus sees it is from the "developer" viewpoint. The code is still free from this viewpoint, since all modifications are published. You can modify it and run it on a DRM-free machine.

      That's the short-sightedness of Linus' argument (the same short-sightedness that let him get trapped by the Bitkeeper fiasco). There are DRM-free machines now, but that doesn't mean there will be in the future. If the media companies have their way, every desktop computer will have a TPM chip in it, and if you want to view things like HD-content, it has to be enabled and running. So a company can take a project, like say mplayer, make a version that plays their video format, decrypting the stream via the TPM hardware, and then sign the binary and then sell it. Congratulations, a company has just saved themselves a couple of years of development time to make a video player to help sell their video files, and you can't modify it at all. If you modify it, it reverts to just plain old mplayer without the ability to use the code that was added. That defeats the purpose of the GPL. Linus really needs to wake up here. Yes, proprietary software has a right to exist, but pretending a company won't take advantage of free software to reduce their development costs (without giving anything back, if they can) is stupid. The GPL allows commercial use of free software as long as you give a fair share back to the community. It is not some fiendish scheme to force all software to be free as some people would say. The GPL as it is has worked fine for the last decade, but now it needs to change or it will no longer serve its purpose.

    36. Re:I can see both sides by Ohreally_factor · · Score: 1

      Oh, brother. You can't ever admit when you're wrong, can you.

      --
      It's not offtopic, dumbass. It's orthogonal.
    37. Re:I can see both sides by Rutulian · · Score: 3, Insightful

      But the vendor must still publish the source of any changes he makes to the code. So the vendor is giving back.

      No, it's not. The device driver code for an obscure chip on, say, a wireless router is completely useless if I can't run the code on said hardware. Think about the Linksys WRT54G. It was just running a linux kernel modified to run on the router with a set of minimal networking utilities. When the source was released, people were able to add all sorts of stuff: better firewalls, servers, ssh utilities, more efficient and capable routing.... They wouldn't have been able to do any of this stuff if Linksys had tossed in a TPM chip and made it so only their signed modified linux would run. The changes they made were also useless without the hardware (yay, so now we know how to run linux on a Linksys router, to bad we can't actually do it).

      So, yes, a consumer could just go buy a different wireless router, but that's not the point. The point is that Linksys would have been using GPL'd software to reduce their development costs without giving a useful share back to the community. Developers who don't mind that sort of thing use the BSD license. Developers who do use the GPL. For the GPL to continue to be relevant, it has to be modified to close loopholes that didn't exist 10 years ago.

    38. Re:I can see both sides by swillden · · Score: 1

      Fair enough, but a bunch of developers who adopted the boilerplate "version 2 or later" license are going to get scorched.

      "Scorched" is a bit strong. Those developers are perfectly free to continue using v2+. Someone who exercises the '+' option and produces modifications that are licensed under v3 (or v3+) may find themselves asked to change it back to v2+, or even just v2, before their work will be incorporated into the main trunk.

      The only way they'll get "scorched" is if someone forks their code, release the fork under v3 and improves the fork so much that the new fork becomes the dominant version of the code.

      This all, of course, presumes that the developers don't like the anti-DRM provisions of v3. Many do. I do, for example. I see the points on both sides, but on balance I think this is a desirable restriction. Free Software is big enough and valuable enough these days to be able to effect some changes in the computing landscape, and I think hindering the deployment of DRM-locked machines that deliberately limit what code will run on them is worth doing. I think Free Software has gotten big enough that this restriction won't significantly hinder the development of F/LOSS, which is the only thing that might concern me about the anti-DRM provisions of v3.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    39. Re:I can see both sides by anandrajan · · Score: 0

      That's the short-sightedness of Linus' argument (the same short-sightedness that let him get trapped by the Bitkeeper fiasco). There are DRM-free machines now, but that doesn't mean there will be in the future.

      Perhaps what you see as short-sightedness is actually an even longer sightedness. Perhaps, Linus looking into his crystal ball, sees a future where a subset of freedom loving consumers are forced to become open (non-DRMed) hardware developers and compete with all the closed (via DRM) consumer electronics hardware - just as the earlier case where linux, BSDs, free/open DOS had to rise up to compete with closed source Unix, VMS, DOS/Windows and MacOS.

      --
      Anand Rangarajan anand@cise.ufl.edu
    40. Re:I can see both sides by maxume · · Score: 1

      So everybody but the 'drm cartel' are useless, stupid, wet noodles? If there are people who want to buy drm free hardware, there will be drm free hardware.

      There might be a tough period where congress makes a stupid law, but stupid laws can be repealed.

      --
      Nerd rage is the funniest rage.
    41. Re:I can see both sides by Kihaji · · Score: 1

      So, you seem to think that the purchase dollars of the entire consumer market is going to be less effective than a license that hardware and software developers can just ignore and still reach 90+% of their market? The only thing that the GPL3 will succeed in doing with their new direction of now controlling how people are able to run software, not just distribute it, is killing itself.

    42. Re:I can see both sides by WilliamSChips · · Score: 1

      The DRM provisions in GPL3 won't prevent you from making open-source DRM applications. The fact that the app would then become useless will. The DRM provisions in GPL3 are for this and this only: To prevent $EVIL_GUY from using DRM to prevent you from using GPL code that you modified. That sounds reasonable enough for me. You already gave up the "freedom" to make a modification of someone else's GPL code proprietary. Why should you have the "freedom" to say it's GPL but only allow changes you like?

      --
      Please, for the good of Humanity, vote Obama.
    43. Re:I can see both sides by madcow_bg · · Score: 1

      Au contrair, my friend.
      It has already started. The worst thing of DRM is not itself, but the DMCA. Now it is illegal to break the DRM, even if you want to get into posession of your own computer.

      Remember http://politics.slashdot.org/article.pl?sid=06/06/ 04/177234 and the 1000 slashdot articles on that matter.

      The point is, it is already taking effect. If software companies want to use GPLv3 code they will have to contribute back, and that is the end of it. That is fair, and IMHO is not that bad for a company. If it was, no company would be supporting OSS. We don't see that much pressure from IBM, Novel, Oracle, etc.

    44. Re:I can see both sides by mickwd · · Score: 1

      You might care to notice that this guy has posted 22 times so far on this one subject (see his posting history).

      He also uses the sig "Boo!! I'm the DRM Boogieman!! If you don't do as RMS says, I'll take away your freedom!!".

      And his posts on this subject have included the following:

      This is a paranoid fantasy put into your head by RMS and others to further their own agenda.

      I just don't get how you people can impugn his integrity and at the same time, not question the integrity of RMS, well known for his demagoguery.

      Oh, brother. You can't ever admit when you're wrong, can you.

      RMS wants to protect the user from himself. The user cannot be trusted not to purchase a product with malicious features, so the GPLv3 must remove the choice from the user. This is what I mean by Big Brother. This is what you are supporting. The individual is not to be trusted, so the collective must make decisions for him. I'm sorry, but I don't want to live in the world you have planned for us.

      What it sounds like is that you want to "protect" the user from closed hardware. What's it feel like, being Big Brother?

      It took me a few hours to figure it out, but the article and its posting here, as well as a large number of posters are part of a campaign to discredit Linus for having the audacity to dissent with RMS and the FSF. Look at the timing. Look at the volume. Try browsing at a lower threshold, and see how much dissent is being modded down.

      The ends invariably justify the means with you types. Anyway, thank you for revealing the true colors of the FSF goon squad.

      You know what's really funny? The vast majority of us on slashdot rightfully get up in arms when politicians play the terrorist card to take away our civil liberties. But we don't see it when one of our own does it to us. Instead we are ready to give up freedoms now because if we don't, then at some vague point in the future, DRM is going to lock us out of our computers.

      I see the FSF priests are out in full force this morning.

      Here's the thing about the GPLv3. It's taking away more freedom from both the developer and the user. It will prevent the developer from developing for whatever hardware he wants and it will limit OSS users choice. And this is being done in the name of Freedom. But whose freedom? The two most concerned parties just lost some freedom. Society's freedom? What is that exactly? Does Society's Freedom equate with The Power of the Collective?

      DRM is a boogie man that RMS is using to scare you and get you juiced up.


    45. Re:I can see both sides by Overly+Critical+Guy · · Score: 1

      How come when people talk about piracy on Slashdot, it's not theft, but when there's source code involved, it's always referred to as "stolen?"

      --
      "Sufferin' succotash."
    46. Re:I can see both sides by mrchaotica · · Score: 1
      He didn't want the code that he and so many others poured their hearts and souls into to be stolen and closed like the Cedega situation.

      Tell me, then: what, exactly, is the essential difference between Cedega and TiVo? They both disallow modifying and using the code!

      There is no reason whatsoever why one should be prohibited but not the other.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    47. Re:I can see both sides by Overly+Critical+Guy · · Score: 1
      at some vague point in the future, DRM is going to lock us out of our computers.


      I've been hearing this alarmist propaganda for years. Guess what, if DRM "locks" us out of our computers, the process of the free market means demand will rise for computers that don't lock us out, which simply means someone will supply them and consumers will buy those instead. Not as dramatic as the Orwellian dreamscape you're imagining, I know.

      I'm so sick of emotional rhetoric. The sky is not falling all the time.
      --
      "Sufferin' succotash."
    48. Re:I can see both sides by mrchaotica · · Score: 1

      What freedoms, exactly, does the GPL v.3 force us to give up? Because I've looked and looked and looked, and I can't find any!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    49. Re:I can see both sides by jZnat · · Score: 1

      Because they're always different people talking about it. One group will refer to closed code as "stolen", while another group will refer to copyright infringement as such.

      --
      'Yes, firefox is indeed greater than women. Can women block pops up for you? No. Can Firefox show you naked women? Yes.'
    50. Re:I can see both sides by mrchaotica · · Score: 1

      Okay, but why bother when the GPL v.3 could prevent all the hardware from going DRM in the first place?!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    51. Re:I can see both sides by mrchaotica · · Score: 1
      first,it will also stop things that are not "bad" by the FSF definition

      Name one.

      the FSF didn't write the software and does not own the copyright on it or have any obligation owed to them by the authors

      Right, so wtf does Linus care about a license that he's not using anyway?! The Linux Kernel is not "v.2 or later", so it's not going to become v.3 regardless of what v.3 looks like!

      There's absolutely no reason for Linus to have a such inflamed opinion on all this, when it doesn't even concern him!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    52. Re:I can see both sides by Rutulian · · Score: 1

      I have no problem with closed hardware, or software. The problem comes when closed hardware (or software) companies use open source software to save on development time and then don't give back to the community. Sorry, letting me look at code I can't run may be following the letter of the license, but it doesn't follow the spirit. Companies, being amoral entities, only care about the letter, though, which is why the license needs to be modified to close loopholes.

    53. Re:I can see both sides by mrchaotica · · Score: 1
      Are you saying the FSF can switch the work of an author to a different licence when the authors are opposed to the new licence and this is a good thing?

      No. The copyright holder always has and always will have the right to license the original version any way he wants, be that GPL v.2, v.3, BSD, or the bend-over-and-drop-your-pants license. All the clause in the GPL does -- a clause which the original author willingly consented to when he decided to use the GPL, mind you -- is cause the program to also be licensed under future versions of the GPL.

      Here's an example: you release "foo, version 1" under the GPL v.2 including the "or later" clause. I get a copy and make some changes, and release "foo-modified, version 2" under the "GPL v.3 or later" license. Anyone who gets my version of the program must abide by v.3, but anyone who gets your version can still use v.2.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    54. Re:I can see both sides by Anonymous Coward · · Score: 0

      Companies want to use DRM because they think it will increase their profits by preventing piracy and also hindering competitors from entering their market. Companies want to use free software because they think it will increase their profits by reducing time to market and decreasing their costs of development.

      A company that does both is having its cake and eating it too. Or, more correctly, having its cake and eating someone else's too. DRM supporters have even used their economic clout to get the DMCA enacted, which removes traditional fair use rights and acts as a bar to both consumers and competitors alike.

      It is only reasonable that free software supporters use their economic power to prevent an outcome that gives them no benefit and actually disadvantages them. What's sauce for the goose is sauce for the gander. RMS's position is clearly correct and Torvalds' position is clearly wrong.

    55. Re:I can see both sides by mrchaotica · · Score: 1
      So, you're basically saying that there won't be hardware available for a reasonable price, because OSS can't compete with Windows or Mac OS on it's own merits.

      No, he's saying that there won't be hardware available for a reasonable price because OSS won't be allowed to compete on its own merits, but will instead be marginalized by the DRM cartel (including the RIAA, MPAA, Microsoft, and Apple) using the DMCA (which as nothing to do with "merit") to legally prohibit non-DRM hardware from being used.

      That's why the "market solution" won't work!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    56. Re:I can see both sides by mrchaotica · · Score: 1
      a bunch of developers who adopted the boilerplate "version 2 or later" license are going to get scorched.

      No they aren't, because they want this to happen! If they didn't, they wouldn't have included the "or later" clause to begin with. QED.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    57. Re:I can see both sides by mrchaotica · · Score: 1
      So you think licence is right way to fight it?

      It DOESN'T MATTER, because the license is not the "wrong" way to fight it!

      Unless you can prove that the GPL v.3 would hurt the cause, then you have no argument whatsover for opposing it!
      Change THAT system. Licence won't help us. Change customer's attitude. Organise boycots. Don't buy Macs. Don't buy ATI or Nvidia video cards. Seriously. Vote with your wallet. Vote with your attitude. Inform rest of the crowd.

      Yes, we should do that. But that doesn't mean we shouldn't use the GPL v.3 also!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    58. Re:I can see both sides by mrchaotica · · Score: 1
      FSF is doing the same thing that a lot of other groups are doing. Mixing to [sic] many political Ideas into their organization.

      Don't you get it? The FSF has always been political! And Linus bought into that political ideology when he chose to use the GPL for his kernel!

      The same with GPL 3. It is expanding an Idea to add more charged items to the list While I am sure most people who support GPL don't care for DRM but a good amount do. So this will cause more people to shift away from GPL just for being to restrictive.

      The GPL v.3 doesn't "expand" a damn thing. It provides exactly the same freedom it always has, which is for the user to control his own property. If you can't modify the source code, you don't have freedom. The GPL fixes that. If you can modify the source code but your hardware refuses to run it, you still don't have freedom. The GPL v.3 fixes that.

      What's so fucking hard to understand?!?!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    59. Re:I can see both sides by anandrajan · · Score: 1

      Okay, but why bother when the GPL v.3 could prevent all the hardware from going DRM in the first place?!

      Because I don't want to curtail other people's (read device manufacturers') freedom to try and curtail my freedom :-)

      --
      Anand Rangarajan anand@cise.ufl.edu
    60. Re:I can see both sides by dwandy · · Score: 2
      Perhaps what you see as short-sightedness is actually an even longer sightedness. Perhaps, Linus looking into his crystal ball, sees a future where a subset of freedom loving consumers are forced to become open (non-DRMed) hardware developers and compete with all the closed (via DRM) consumer electronics hardware
      I've looked into this. and yes I think that maybe one day open hardware is going to exist. but not in any kind of near to mid term. the problem is money. A CPU fab costs intel in the billions to make. Open source software can be run on a used sub-$100 desktop computer.

      In the mean time, if orgs like RIAA, MPAA, WIPO et al have their way, all hardware is going to require some kind of TPM.

      If I had to place my life's savings on which one will happen first (freedom hardware, or all intel/amd systems including some form of hardware TPM, I'd place my money on the TPM.

      Worse than that, sure if it exists, Windows will implement it. Will linux? doesn't have to, and I suspect it won't. But that won't stop the Intellectual Monopoly holders from making it law ... effectively making non-TPM compliant versions of Linux illegal.

      this is not the boogieman.
      This is the capitalist, and I for one do not welcome the new capitalist overlord.

      --
      If you think imaginary property and real property are the same, when does your house become public domain?
    61. Re:I can see both sides by jrobinson5 · · Score: 2, Informative

      Oh really?

      Yes, there are lots of ways to do it that are illegal, but you state the only way an Xbox can run Linux is if you break the law. This is just FUD.

    62. Re:I can see both sides by jrobinson5 · · Score: 1

      Windows doesn't come with DVD software either. You have to get it from the hardware manufacturer or a third party such as WinDVD. Not that you stated otherwise, just thought you should know.

      "Thing is that I don't think that Linux will be a popular and viable OS in the future if people have to _knowingly_ break the law just to make it do the most basic of things: run it."

      Umm, no. Last time I checked, it's still legal to run linux without the ability to play DVD's. Still, I really do think that someone big like Red Hat, Novell, Ubuntu Foundation, IBM, etc. should just pay the half million or whatever to the people who own DVD and then give it away free, similar to what that one Linux media player app (can't remember the name) did with MP3's.

    63. Re:I can see both sides by anandrajan · · Score: 1

      Worse than that, sure if it exists, Windows will implement it. Will linux? doesn't have to, and I suspect it won't. But that won't stop the Intellectual Monopoly holders from making it law ... effectively making non-TPM compliant versions of Linux illegal.

      Fair enough. But, we only have ourselves to blame if we let that happen and so from this perspective I can definitely see the validity in the pro-active nature of GPL v3. However, it still feels heavy-handed and "socialist" and not very creative. Isn't there a more creative way of solving this problem?

      --
      Anand Rangarajan anand@cise.ufl.edu
    64. Re:I can see both sides by Anonymous Coward · · Score: 0

      There are DRM-free machines now, but that doesn't mean there will be in the future. If the media companies have their way, every desktop computer will have a TPM chip in it, and if you want to view things like HD-content, it has to be enabled and running.

      Sounds like fear-mongering to me. Is this really the FSF's argument; fear of the evil media? That's it?

    65. Re:I can see both sides by Pfhorrest · · Score: 1

      Please explain to me how the existence of the GPLv3 will prevent developers from licensing their software under the GPLv2.

      Please explain to me how someone copying my code and using it in a closed-source project makes my original project less free. The issue here (with "v2 or later" licensed projects at least, where a project may be forked and re-licensed under v3) is the same.

      If you want to free your code, then really free it - just declare it public domain. Sure, someone could take a copy of that and do something with it you don't want, including adding some changes and compiling a binary and selling that binary and then burning their copy of the code with the changes before anyone can see it. So? YOUR CODE IS STILL FREELY AVAILABLE. They didn't do anything to your code. You made it free, and someone else copying it, peppering some of their code own in and doing whatever they want with it doesn't make your original code any less free.

      The whole point of the GPL is to control what people may or may not do with your code - to take away certain freedoms "for the greater good". GPLv3 is just taking that even further, as the GP said. And if your solution to these concerns is basically "what's the problem, your project is still GPLv2 licensed even if someone makes a GPLv3 fork", then by that same line of reasoning... what's the problem with non-copyleft licenses, your code is still public domain, even if someone else makes a closed source fork.

      --
      -Forrest Cameranesi, Geek of all Trades
      "I am Sam. Sam I am. I do not like trolls, flames, or spam."
    66. Re:I can see both sides by Anonymous Coward · · Score: 1, Insightful

      That's the short-sightedness of Linus' argument (the same short-sightedness that let him get trapped by the Bitkeeper fiasco).

      And you're demonstrating the blind spot that keeps idealists from understanding pragmatic people like Linus.

      Yes, Bitkeeper was a mess. However Linus has publically said, multiple times, that it was worth it. Specifically, his increased productivity while he used it more than paid for the time it took to migrate to something else. And his experience with it helped him understand what he really wanted that wasn't being provided by other tools out there.

      If this is the consequence of shortsightedness, then I wish more people were shortsighted like this!

    67. Re:I can see both sides by init100 · · Score: 1

      Congratulations, a company has just saved themselves a couple of years of development time to make a video player to help sell their video files, and you can't modify it at all. If you modify it, it reverts to just plain old mplayer without the ability to use the code that was added. That defeats the purpose of the GPL.

      You sum up what I think here pretty well.

    68. Re:I can see both sides by quintesse · · Score: 1

      "Last time I checked, it's still legal to run linux"

      Of course it is, we were talking about what _could_ happen in the future and looking at the writing on the wall that future might not be too far off.

      Just looking at the kinds of security features they are builing into the next-gen DVDs where even your display hardware will check if you actually have the rights to display the contents of the disc! For this your display needs to support DRM and it will check if it gets it information from trusted source, yes your Gfx card will need to support DRM which of course needs a driver that supports DRM as well. But that driver can only be trusted if it runs on an OS that supports DRM. Even simulation of an OS won't be possible with the Trusted Platform being implemented.

      So hacking around all those limitations will be a difficult job if only because you will have to do it on several levels instead of just one as with current DVDs (the encryption) for example. But with more and more laws appearing around the world forbidding those kinds of work arounds there might come a time where you will be breaking several laws just by displaying a BluRay movie on your Linux machine.

      And remember this is not about just paying a license to be able to use some decoder, this is about your freedom to do with your computer and the information on it as you see fit. If you pay for an MP3 license you have bought the rights to listen to your MP3-encoded music, but at the same time you are free to just convert it to just about any other format you would want. There are no shackles. With DRM this changes, you might be able to pay off the industry so you are allowed to watch their movies but that's the only thing you will be able to do with it, they decide when, how and how many times you can watch your movie. A Linux system that allows those kind of limits just wouldn't be Linux anymore.

    69. Re:I can see both sides by Peaker · · Score: 1
      the process of the free market means demand will rise for computers that don't lock us out,

      Just like the process of the free market gave rise to:
      • Open standards (Microsoft Office)
      • Open APIs (Direct X, Windows, etc)
      • Great Music and competition (RIAA, MPAA)

      The free market has really proven itself, especially in the computing world.

      I am sure many more such great examples exist, showing how the free market always guarantees that our freedom, just like quality is always top priority of the companies.

      We can continue to entrust our freedom with it, and all will be well.
    70. Re:I can see both sides by mrchaotica · · Score: 1

      But you're not curtailing the device manufacturers' freedom to make DRM. You're simply not helping them to do so, by not letting them use your Free code.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    71. Re:I can see both sides by Peaker · · Score: 1
      At worst case scenario, you won't be able to run certain propriatary apps when running nonDRMed stuff. big deal, sounds like your don't want to run them anyways.

      No, the worst case scenario is that you are locked out of:
      • Reading others' documents
      • Government services
      • Media distribution, as well as copying your own media

      Actually that's just the "lock out" worst case. There are much worse scenarios:
      • Government retroactively changing documents in a 1984-like fashion.
      • Bosses mailing orders that are deleted or modified retroactively giving no evidence of the source later.

        Of course you are only affected by the second if you choose not to be locked out. We can already see that the vast majority of the population chooses not be locked out over freedom, and could easily allow the government to start encrypting their data and services locking you out. The whole internet would be divided into its majority, and the "locked out" long-forgotten Linux users.
    72. Re:I can see both sides by Peaker · · Score: 1

      Eh...

      What freedoms are we giving up now with the GPLv3?

    73. Re:I can see both sides by dbIII · · Score: 1
      Name one.
      You won't be able to force your linux based router to only accept signed binaries for updates and so will potentially be highly vunerable to script kiddies - and the same goes for binary repositories for yum etc. It is a very major drawback and was refered to in the article the earlier story was linked to (but not this one unfortunately).

      There's absolutely no reason for Linus to have a such inflamed opinion on all this
      It is a reaction to an earlier discussion. People such as RMS are repeatedly insisting he had to put his support behind the new licence and he had to change to the new licence in linux (even though it isn't finished yet), and then threatened to go around him if he doesn't comply - as would have been seen in earlier articles. It boils down to the fact the he doesn't like the licence and it is not their project.
    74. Re:I can see both sides by Anonymous Coward · · Score: 0
      You won't be able to force your linux based router to only accept signed binaries for updates and so will potentially be highly vunerable to script kiddies - and the same goes for binary repositories for yum etc.

      Sure you will, you build and sign the binaries yourself. Unless the aim of the hardware vendors is to lock consumers out of their equipment, this isn't an issue.

    75. Re:I can see both sides by colmore · · Score: 1

      You clearly have yet to be locked out of the basic utility of some media you've rightfully purchased. DRM is no boogeyman, it's already getting in peoples way, and there are bills in congress right now that would vastly decrease the ability to use a computer as a general purpose reprogrammable machine, rather than a fancy DVD player / console.

      I don't think you make a very good analogy really. DRM is the invasion of rights, where as government policy in response to terrorism is the invasion of rights. The GPL, very unlike acts of congress, doesn't take rights away from anyone without their consent. People who create software are free to use whatever (legally valid) license they wish. The GPL won't come down like a hammer upon all free software users; anyone unhappy with the situation is free to branch from a GPL2 licensed version.

      Business runs free software, and if it becomes impossible to run linux on DRM'd hardware, hardware producers will resist forcing DRM on their customers. On the other hand, if 95% of people out there are able to run their business just fine on DRM'd hardware then we will be saddled with DRM, and amateurs and hackers everywhere will suffer.

      There are multi-billion dollar interests that stand to gain a lot from DRM, so to deny that it's a danger is to be willfully ignorant of the way or society functions. As Linux (frequently running on arrays of consumer hardware) now also support multi-billion dollar interests, keeping free software on the other side of the DRM divide will mean there is an equally powerful group of interests resisting DRM.

      --
      In Capitalist America, bank robs you!
    76. Re:I can see both sides by Anonymous Coward · · Score: 0
      The way Linus sees it is from the "developer" viewpoint. The code is still free from this viewpoint, since all modifications are published. You can modify it and run it on a DRM-free machine. The FSF rather thinks of the "end users" viewpoint, where modifying the code and running the modified code on the same machine is paramount.


      Linus isn't the only developer. When it comes to the GPL there really is no "developer" and "user". The GPL gives the "user" the right to also be the "developer". I am both a user and a developer as I often change the software source that I use to work the way I want it on my Linux systems.

      Linus chose the GPLv2 because he thought it was the best license out there to encourage participation in development and to ensure the code stayed open. He still feels that way. There are a lot of us "developers" who believe now that the GPLv2 is lacking because of the Tivoization. I for one do not want code that *I* have written to be locked up in a device where changes can't be made and run on that device by the user. I will certainly choose to use the GPLv3 for any new code that I write.

      The funny part is, Linus doesn't have to relicense the kernel under the new version of the GPL and in fact this would be nearly impossible to do because there are thousands of copyright holders to the source in the kernel and some of them are no longer with us. The kernel will almost certainly remain under the GPLv2. So, if Linus prefers to continue using the GPLv2 for his work then by all means, continue using it. For a lot of us we prefer to use GPLv3. It's really that simple.

      Why does there have to be this dramatic "us" against "them" type of breakdown all the time?

      -Void
    77. Re:I can see both sides by sumdumass · · Score: 1

      Ok, if the government locks people out of documents, then new government officials will be elected and it will be reversed. In california, were i think it is most likley to happen, a position on the ballot can be put in place with just a few signitures compared to the people registered to vote. and guarenteeing this doesn't happen. This will keep a demand for DRM free services.

      Now something that is one of the bigest reasons always brought up by why people won't switch to linux is that they have 10 years of software invested in windows that will become useless in linux. This is so popular that apple has decided to use it as a selling point were you can still boot to windows on a mac. They also puport that they have files that simply cannot be read in linux. How well will DRM in the fasion you describe last when everyone finds out they cannot run thier office 98, word 2000, games from the 90's or early 2000's. There will be an upraor over this. It is likley that DRM in this fashion will only exist on apliances like the XBOX, Ipod or internet enabled toasters. Can you imagine the reaction millions of people will have when they buy a new computer and everything including old quickbooks files or office documents are ruined for general us or thier computer runs slow and they cannot surf the interweb? How about when the fast computers slow to a crawl when they try to see if it will work. Dell and HP are going to have one hell of a consumer complaint/tech support issue and probably a lawsuite if they don't market thier new "trusted PCs" as apliances that won't run anything the consumers already own.

      Now, as for bosses mailing orders and it then disapearing. Well, thats already illegal if two conditions are in play. First is if the company is traded,publicly or privatly. Second is if they fall under the laws relating to finacial institutions or medical instituations(hippa). All it will take is some disgruntled employee to make an acusation and the software enabling it will be removed by enforcment of the laws. There are probably some other situation were email retention and viewing are required by law (like ISP data retention). I know of companies who have andlost contract disputes and liability claims in court because they couln't produce a valid emabil trail.

      And for governments changing documents? you mean they won't just put whiteout across the screen? Or a black bar that can be removed by changing the font colors? How long with the public let this happen, especialy when there will be a record that the document was changed to a different revision number? Refere to first point about ballot resolutions and elected officials. The feds won't lock themselve out of interaction with Main, or California because they insist on using propriatary DRMed formats. Also we have an accessebility laws that wold probably preclude them from using software like this.

    78. Re:I can see both sides by Ohreally_factor · · Score: 1

      GPLv3 prohibits users from using signed binaries on hardware that the FSF deems "bad". Specifically, the user cannot create software with signed binaries for use on Trusted Computing hardware. Apparently the FSF doesn't think users are capable of deciding for themselves what hardware is best for some applications, so it wants to stop them from making a "bad" decision.

      It's so worried about closing the "Tivo loophole", which is really inconsequential, that it's willing to foreclose on all the potential good uses of signed binaries on trusted computing hardware.

      --
      It's not offtopic, dumbass. It's orthogonal.
    79. Re:I can see both sides by sumdumass · · Score: 1

      I dunno, This GPLv3 will make it technicly illegal for someone to write a program making the DRMed IPOD work in linux along with DRMed Itunes and distribute it under the GPLv3 or it would make it illegal to distribute GPLv3 software to work with computers that have it installed.

      If GPLv4 comes a reality, I doubt most people will run thier code from it. It will also probably cause almost all the major projects to branch and FOSS will likley die a slow death. But that seems to be what some people want.

    80. Re:I can see both sides by dbIII · · Score: 1
      Sure you will, you build and sign the binaries yourself
      But so can the script kiddies if the hardware will accept binaries from anywhere. Unfortuantely the discussion is being driven by someone who considers "free" computing to be able to log on to any machine he likes (look up the attitude of RMS on passwords) - we don't have to follow every idea he has, only the good ones.
    81. Re:I can see both sides by Zaiff+Urgulbunger · · Score: 2

      Is it legal (or even possible yet) to run Linux on an xbox360? I ask since the security on the latter console appears more "robust" than the first xbox, and consequently, is surely more likely to involve a DCMA violation?

    82. Re:I can see both sides by theLOUDroom · · Score: 1

      GPLv3 prohibits users from using signed binaries on hardware that the FSF deems "bad".

      That's bullshit.

      It not at all about what the hardware is but rather WHO HOLDS THE KEYS. The GPL is about preventing code-signing from making the freedoms protected by the GPL irrelevant.

      This isn't some pie-in-the-sky thing. Companys are actively working on making this happen.

      What is being done we is in the true spirit of the GPL. "I have produced this work for society to use, I ask in return that any addional work be available as well."
      Having the code but having to way to run it is pointless. It's counter to the spirit and intent of the GPL.

      --
      Life is too short to proofread.
    83. Re:I can see both sides by orasio · · Score: 1

      First: piracy is robbery in high seas. So, it _is_ theft.

      Copyright infringement is not theft, because you are taking stuff, and the original owner can still use the copyrighted stuff. Theft involves the victim losing the stuff that was stolen.

      In the case of Cedega, it wasn't theft either, but it was a ripoff, because they promised to give stuff back to the community, and they didn't.

    84. Re:I can see both sides by dfghjk · · Score: 1

      "I for one do not want code that *I* have written to be locked up in a device where changes can't be made and run on that device by the user."

      It's not the code that's locked up, it's the device. The code you've contributed is still freely available to be used, modified, redistributed, etc. The device, however, is not covered by the GPL (v2) and your belief that you are entitled to modify its function is misguided. The license for the software doesn't extend to the hardware that's sold to you.

      Somehow users have come to believe that devices with GPL'ed firmware are somehow offering them the inherent right to modify the product. That isn't so. RMS wants to change this by extending the reach of the GPL beyond the scope of the software that is licensed.

      If you want to be able to modify a product you purchase make sure you have the right to beforehand. It's totally justifiable that programmers will reject the additional limitations that v3 brings.

    85. Re:I can see both sides by foom · · Score: 1

      This is a ridiculous argument. You don't need to have DRM to make a device safe from tampering. Make the hardware require a physical button to be held down in order to write to the firmware.

      If you, for some reason, want to add signed binaries to the mix, then just require a physical button to be held down in order to write to the set of authorized keys.

      GPL3 is satisfied and script kiddies can't overwrite the software on your device.

      Everyone's happy, The End.

    86. Re:I can see both sides by WilliamSChips · · Score: 1

      Bullshit. There merely has to be an option to ignore the signing and let yourself get pwned(IMHO you deserve to get pwned for using binaries but that's a different issue).

      --
      Please, for the good of Humanity, vote Obama.
    87. Re:I can see both sides by mrchaotica · · Score: 1
      You won't be able to force your linux based router to only accept signed binaries for updates and so will potentially be highly vunerable to script kiddies

      That's bullshit and you know it.

      First of all, it's entirely possible and indeed easy to secure a Linux-based router (such as my Linksys) against script kiddies simply by setting the admin password, and disconnecting it from the network before updating it (except for the connection to the computer with the patch, of course). Moreover, there's no reason the device couldn't include a switch to lock it to only accept signed binaries, as long as you could unlock it and/or change what "signature" it allows.

      People such as RMS are repeatedly insisting he had to put his support behind the new licence and he had to change to the new licence in linux (even though it isn't finished yet)...

      Show me a verbatim quote by RMS where he said this, because I think you're lying.

      ...and then threatened to go around him if he doesn't comply

      That doesn't even make any sense -- the Free Software Foundation doesn't need to "go around" Linus; he ultimately has no say whatsoever in the GPL v.3 anyway! Except for public opinion, Linus has zero leverage over the FSF regarding the GPL v.3, and (again, except for public opinion) the FSF has zero leverage over Linus regarding the Kernel's licensing. So aside from wanting to make an ass out of himself and/or shill for the companies that sign his paycheck, I see no reason for Linus to be getting upset. And I don't accept "it's not [the FSF's] project" as a reason, because I haven't seen any evidence other than your unsupported assertion that anyone from the FSF has complained recently about the Kernel's licensing!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    88. Re:I can see both sides by mrchaotica · · Score: 1
      Specifically, the user cannot create software with signed binaries for use on Trusted Computing hardware.

      You've got that exactly backwards. The GPL v.3 is designed to ensure that the user can sign binaries for use on Trusted Computing hardware! This is as opposed to the default, where the user is forced to rely on the grace of the manufacturer to sign binaries for him.

      Apparently the FSF doesn't think users are capable of deciding for themselves what hardware is best for some applications, so it wants to stop them from making a "bad" decision.

      The user can still decide to buy whatever hardware he wants, and [try to] run GPL software on it to his heart's content. All it prevents is manufacturers taking advantage of GPL software without allowing the users all the freedoms the GPL is supposed to protect.

      Now, really -- have you got a real example for me? 'Cause you've still failed to name one.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    89. Re:I can see both sides by jasonjacks0n · · Score: 1
      The way Linus sees it is from the "developer" viewpoint. The code is still free from this viewpoint, since all modifications are published. You can modify it and run it on a DRM-free machine. The FSF rather thinks of the "end users" viewpoint, where modifying the code and running the modified code on the same machine is paramount.

      Yeah, it took me a while to understand Linus's point of view, but eventually after reading all of his recent Groklaw posts, I arrived at the same understanding you did. Basically Linus thinks of the code as completely distinct from the hardware, and as such GPLv2 provides as much protection to the software as he cares for. Which does makes perfect sense, as far as it goes..

      The FSF's stance, on the other hand, is basically that, in the case of something like a TiVo (which I own and love, BTW), the hardware and software work together to provide a single device. From the user's point of view, anyway. Basically, because the TiVo hardware is so reliant on its software to work, you could conceptually think of the entire thing *almost* as a "derivative work" of the GPLed software it contains. So the FSF is basically trying to set up a situation where the software on such a device is protected with roughly the same strength as an LGPLv2ed library: the "client code" (or in this case, hardware) can be as proprietary as it likes, but must allow the "library" (the GPLed software it runs) to be swapped out freely by the user.

      Both as a user, and as a developer who occasionally releases GPLed code, I tend to prefer the latter point of view. As a TiVo owner, I dislike the fact that TiVo benefited from the Linux kernel, but refuses to pass that benefit on to me.

      And the provisions in GPLv3 are definitely in the spirit of the original GPL's intent. They're trying to fix an oversight, not expand the GPL's reach. I mean, when I learned about the TiVo's signed binaries (after purchasing one), I thought of them as a hack around the intent of the GPL, so it's not surprising to me that the FSF is trying to close that loophole. They're not actually trying to expand the GPL, just prevent it from being trampled.

      It's a hard problem to solve, and I actually do think Linus has a valid point; GPLv3 as it stands might eliminate some valid, desirable uses of GPLed software. But I think the bigger potential problem is that, with a TPM chip in every consumer device, if the GPL doesn't explicitly protect us from TiVoization, we'll de-facto lose the ability to modify GPLed software on our machines. It'll be legal, but technically not viable. It would be better if, as Linus believes, market forces would fix that problem, but to me that seems unlikely..

      --
      This space intentionally left blank.
    90. Re:I can see both sides by CodeBuster · · Score: 1

      If orgs like RIAA, MPAA, WIPO et al have their way, all hardware is going to require some kind of TPM.

      This is exactly what they did with Macrovision and VCRs. They lobbied heavily for legislation that made it illegal to sell VCRs without Macrovision chips or at least it was very difficult to obtain a "professional" model without the Macrovision in many first world countries (most people who gave a crap simply bought black market filtering hardware or built it themselves instead). They could very easily make the licensing fees for the legally required TPM chips high enough to squeeze out those pesky open source developers who create software that decrypts their bogus encryption schemes and allows people to skip past the advertisements. You are bang on with your analysis.

    91. Re:I can see both sides by CodeBuster · · Score: 1

      Sounds like fear-mongering to me

      They (MPAA, RIAA, et al) did it before with Macrovision and VCRs so it is not too far fetched to believe that they will try similar schemes again in the future. Remember when they were trying to lobby for a "cop chip" to somehow magically detect whether an arbitrary stream passing through a DAC was actually an infringement of a copyrighted work? Fortunately for all of the electrical and computer engineers out there even THEY (MPAA, RIAA, et al) realized how futile and stupid that approach was (probably after some engineers explained it to the execs in a way that even a second grader could understand). However, The strategy of the legally required control/scrambling chip is one that is near and dear to the hearts of the content companies and they will definitely try again in the future provided that they can get a solution that is not completely brain dead.

    92. Re:I can see both sides by Schraegstrichpunkt · · Score: 1
      I suspect that Linus just wants to make his software while the FSF wants to change the world.

      Linus likes to pretend that legal issues and malevolent entities don't exist. The FSF knows better.

    93. Re:I can see both sides by init100 · · Score: 1

      This GPLv3 will make it technicly illegal for someone to write a program making the DRMed IPOD work in linux along with DRMed Itunes and distribute it under the GPLv3

      This kind of defeats the purpose of distributing a program under the GPL, since such a program would necessarily have to hinder modifications of the code. So why use GPL for such a program at all?

      or it would make it illegal to distribute GPLv3 software to work with computers that have it installed.

      Can you expand on why you think this is the case? The DRM provisions in GPLv3 are only there to prevent someone from taking away your right to modify GPLv3 code by making it impossible to run modified versions.

    94. Re:I can see both sides by Schraegstrichpunkt · · Score: 1
      GPLv3 prohibits users from using signed binaries on hardware that the FSF deems "bad". Specifically, the user cannot create software with signed binaries for use on Trusted Computing hardware. Apparently the FSF doesn't think users are capable of deciding for themselves what hardware is best for some applications, so it wants to stop them from making a "bad" decision.

      Really? Where?

      The GPLv3 drafts tell distributors that if they distribute my code, they need to distribute everything necessary to ensure that the recipients have the ability to exercise the four freedoms that the FSF associates with free software, and to ensure that the recipients know that they can do these things. Otherwise, I can sue those distributors for copyright infringement.

    95. Re:I can see both sides by init100 · · Score: 1

      If there are people who want to buy drm free hardware, there will be drm free hardware.

      What if 1% want to buy DRM-free hardware, and the remaining 99% just accept that DRM is a new fact of life? Don't you think there will be very few choices, if any at all, for those 1% that don't want DRM hardware?

    96. Re:I can see both sides by Eivind · · Score: 1

      Out of curiosity, which law, precisely, would that be ?

    97. Re:I can see both sides by init100 · · Score: 1

      Because I don't want to curtail other people's (read device manufacturers') freedom to try and curtail my freedom

      They can try to curtail people's freedom all they want, but (with the GPLv3) they sure cannot use my code to help them do it.

    98. Re:I can see both sides by killjoe · · Score: 1

      Look if you think that one statement from the german office of MS is the actual MS policy worldwide then go ahead. Until MS actually produces a press release I will believe otherwise.

      --
      evil is as evil does
    99. Re:I can see both sides by init100 · · Score: 1

      Somehow users have come to believe that devices with GPL'ed firmware are somehow offering them the inherent right to modify the product. That isn't so. RMS wants to change this by extending the reach of the GPL beyond the scope of the software that is licensed.

      In other words, you are saying that it should be fine for hardware companies to use your GPL-licensed code, saving a lot of development cost, but prevent their customers from modifying it and run it on the same device? This violates the spirit of free software, in that the device manufacturer does not pass on its freedoms granted by the GPL to their customers. And if I license my code under the GPL, I choose this license exactly to give the users those freedoms, and I would not want some device manufacturer to use my code but not pass on their freedoms granted by the GPL.

      In my view, the DRM provisions in the GPLv3 exist to close a loophole in the GPLv2, not to extend the reach of the license. It is there to protect my intention of user freedoms when I release software licensed under the GPL. If I did not care about those freedoms, I would use another license, like the BSD license. And if I wanted the modifications released, but did not care about the users, I could still use the GPLv2.

    100. Re:I can see both sides by init100 · · Score: 1

      disconnecting it from the network before updating it

      Why not just restrict router updates to come from the internal network, possibly even eliminating the possibility to upgrade over WLAN? Then you should not have to disconnect the router from the internet during the upgrade.

    101. Re:I can see both sides by init100 · · Score: 1

      But so can the script kiddies if the hardware will accept binaries from anywhere.

      Why would any reasonable router accept firmware upgrades from the outside network. It could simply restrict updates to coming through the internal network (possibly even restricting it to the wired network).

    102. Re:I can see both sides by gayleard · · Score: 1

      IMHO, if Linus and RMS disagree, Linus is almost certain to be right.

    103. Re:I can see both sides by init100 · · Score: 1

      Where I live, the only way of buying a desktop PC without Windows is by buying the parts and assembling it yourself. And then you are not buying a computer, you are buying computer parts.

    104. Re:I can see both sides by init100 · · Score: 1

      DRM is *legitive* way of protecting something, now what, we could not have crypt software in GPLv3? Crypt software in combining with hardware - I see lot of real legal use

      DRM uses encryption in many cases, but encryption is NOT DRM. With non-DRM encryption systems (even with crypto hardware) the computer owner determines the restrictions for accessing data, and is used to prevent third parties from accessing your private data on your computer. DRM is about making the computer disobey the computer owner and instead obey some third party, like the media companies or the hardware manufacturer.

      The DRM provisions are there to prevent TIVOization, which means that hardware vendors build upon free software, saving a lot of money compared to developing it themselves, but restrict their customers from using modified versions of this software, by making the hardware only accept certain "trusted" versions of the software. This is a violation of the GPL spirit, i.e. that users have the same rights and powers as the developers, and this is the reason these DRM clauses in the GPLv3 were added.

      So the answer to your question is: Yes, we can have GPLv3-licensed encryption software without any problems with regard to the DRM clauses.

    105. Re:I can see both sides by tinkerghost · · Score: 1

      Can I point out that NO developer will ever run a locked down DRM box for development? Doing so would require resigning for every recompile of any module - do you really think that marketing/ITsecurity would give every developer the signing software?
      It's not going to happen. I don't like GPL v3's take on DRM, mostly because it's not DRM that inspired it, it was a trusted computing issue with TIVO. The Tivo hardware was hardwired(or flashed) to only run the OS it came with, and not tweaked versions of it. The reason behind that was in fact a DRM issue, by only running certified versions of the software, TIVO could go to **AA and say, "look, DRM is in place & secure, so stop suing me." Now, you may agree or disagree with that, but Tivo did exactly what they were required to do, they made changes to the code & returned those changes to the community. Could you further change the code and run it on a Tivo? No, but the changes to the code were available and you could incorperate those changes into your own project - and to me that has always been the core of the FOSS community. I am free to learn from your stuff & use it, just like you can use mine.
      The problem I have with GPL v3 is that I can see reasons to use trusted computing - banking, military, and medical records - by deliberatly voiding the core of trusted computing (being able to control/identify exactly what code is running), you exclude the possibility of using any GPLv3 code in those applications. In other words, by artificially forcing freedom, I see GPLv3 actually restricting it. I think that's been Linus' point also.

    106. Re:I can see both sides by Anonymous Coward · · Score: 0

      Like when Linux wrote his license for the kernel, and RMS wrote his for his GNU utilities? You probably don't even remember Linus' license, but RMS' license is called the GPL, version 2 of which is the license used for the Linux kernel.

    107. Re:I can see both sides by tinkerghost · · Score: 1
      And if I wanted the modifications released, but did not care about the users, I could still use the GPLv2.
      Not nessesarily, if the libraries are released under GPLv3, then you may have a hard time releasing code that links to them under GPLv2.
    108. Re:I can see both sides by dfghjk · · Score: 1

      "In other words, you are saying that it should be fine for hardware companies to use your GPL-licensed code, saving a lot of development cost, but prevent their customers from modifying it and run it on the same device?"

      Yes. They are free to modify the code but the hardware is not subject to the GPL.

      "This violates the spirit of free software, in that the device manufacturer does not pass on its freedoms granted by the GPL to their customers."

      No it does not. The freedom to modify the code remains intact. You may use the code in any way you wish, including creating a competing product.

      "And if I license my code under the GPL, I choose this license exactly to give the users those freedoms, and I would not want some device manufacturer to use my code but not pass on their freedoms granted by the GPL."

      You are incorrect to assume they've done otherwise. You want to project the limitations of the software license onto other parts of the product not associated with it.

      "In my view, the DRM provisions in the GPLv3 exist to close a loophole in the GPLv2, not to extend the reach of the license."

      You may prefer to view it as a loophole, but closing it involves extending the reach of the license. No hardware manufacturer is EVER obligated to sell products capable of running any arbitrary GPL'ed code. Name one manufacturer that advertised that the used Linux in order to enable their customers to modify the products function? A Linksys router? They made changes to their product to discourage it.

      "It is there to protect my intention of user freedoms when I release software licensed under the GPL. If I did not care about those freedoms, I would use another license, like the BSD license. And if I wanted the modifications released, but did not care about the users, I could still use the GPLv2."

      And included in your intentions is any hardware that is bundled with the GPL'ed software even though abolutely no GPL'ed work went into that design or construction of that hardware.

      You're free to release any work you contribute under any license of your choice, but there's no reason to pretend that your new license isn't more restrictive in the name of freedom than previous ones.

      I think that ppl should be free to modify their OS to their heart's content. I also think that copyright holders should also be free to deny those users access to their content, just as those "freedom lovers" use their copyright to strongarm others and extend the reach of their license. Cuts both ways, and if you want to champion extra restrictions to a license that makes future software undesirable then more power to you.

    109. Re:I can see both sides by init100 · · Score: 1

      You want to project the limitations of the software license onto other parts of the product not associated with it.

      And if the hardware won't function without my software, why can't I do that? Either use my software according to my rules, or write your own software.

      A Linksys router? They made changes to their product to discourage it.

      Then, why did they make a special Linux version, the WRT54GL, after they changed the WRT54G to VxWorks?

      And included in your intentions is any hardware that is bundled with the GPL'ed software even though abolutely no GPL'ed work went into that design or construction of that hardware.

      I don't care about the design of your hardware except that it may not be used to limit the rights of users of my software. If you don't like it, write your own software and smell the increased costs.

      I also think that copyright holders should also be free to deny those users access to their content

      Deny all you want, but don't expect my computer to obey you. Either it plays and allows everything (no DRM on media), or it don't allow anything at all (DRM on media, but no DRM in my computer). I won't allow my computer to selectively allow certain actions and deny others based on your decisions. If this means that I cannot buy your songs or your movies, it's your loss. I'll live without them.

    110. Re:I can see both sides by dfghjk · · Score: 1

      "And if the hardware won't function without my software, why can't I do that? Either use my software according to my rules, or write your own software."

      Of course you can do that. What you can't do is license your software such that it allows me to use it then complain when I do. The GPLv2 is just that.

      "Then, why did they make a special Linux version, the WRT54GL, after they changed the WRT54G to VxWorks?"

      I forgot about that, and it appears to be a rare example of a product intended to allow mods. I use the VxWorks one. I prefer a device that works without requiring mods.

      "I don't care about the design of your hardware except that it may not be used to limit the rights of users of my software."

      Then don't buy it and don't license your software to me. The GPLv2 license grants me that right so you should choose something else. Your GPL'ed work did not contribute to my hardware design and it does not govern the use of that work.

      "Deny all you want, but don't expect my computer to obey you. Either it plays and allows everything (no DRM on media), or it don't allow anything at all (DRM on media, but no DRM in my computer). I won't allow my computer to selectively allow certain actions and deny others based on your decisions. If this means that I cannot buy your songs or your movies, it's your loss. I'll live without them."

      I think you're getting emotional. I'm not a content provider, I'm just openminded. You seem to feel that it is your right to make decisions regarding your computing platform (it is) and the software you author (also true), but also how others use software licensed to them (you aren't) and how commercial entities will do business with you (ain't so). Everyone else's freedom to choose is intact as well, and maybe it's time you understand that. Your rights don't include violating the rights of others.

      I am not an advocate of drm but I totally understand why it exists. Just as you doggedly defend your right to dictate how software you author gets used, contect creators wish to do the same. Your tool is the GPL which you and the FSF would like to sharpen now that it's not enough. Content providers will use drm whether you like it or not. They have no other business model.

      Frankly, I want the battle to play out between Fair Use and DRM and I want DRM to lose. I want the business model to change and I want technology to benefit the users. What I don't want is for the free software community to turn the guns on itself by making its licenses increasing restrictive.

      Vendors use GPL'ed software in proprietary products because it offers some advantage they don't otherwise have and rarely is hackability their goal. If GPL'ed software becomes universally unavailable, the result will be fewer products at a slower pace with higher prices. Non-GPL'ed free software could very well rush in to fill the gap. Make the GPL sufficiently unattractive to use and it will get dropped and replaced. Linux, for example, isn't so good that it's irreplacable.

      Our need to out computing platforms open is essential but so is the need to maintain incentives for creativity. These issues are colliding headon and radical positions such as yours are not helpful, so take your extreme positions if you like and prepare to be marginalized.

    111. Re:I can see both sides by init100 · · Score: 1

      also how others use software licensed to them (you aren't)

      You mean software licensed to third parties by other third parties with none of my code involved? Where did I write that?

      how commercial entities will do business with you (ain't so)

      If I don't accept how they want to do business with me, I have no obligation to do business with them. So in essence, I do have the right to make decisions about how they do business with me, at least indirectly.

      Everyone else's freedom to choose is intact as well, and maybe it's time you understand that. Your rights don't include violating the rights of others.

      Now where did I say that?

      Content providers will use drm whether you like it or not.

      And they are free to do so, except using my code. In addition, they cannot expect me to buy their DRM:ed offerings (although I won't pirate it either).

      Vendors use GPL'ed software in proprietary products because it offers some advantage they don't otherwise have and rarely is hackability their goal.

      Such as the advantage of reduced costs. This certainly gives them two options, lower prices or raised profit margin (or a combination of the two). But I don't see why programmers releasing GPL software have any responsibility to fund the development for vendors that don't want to pass on the GPL spirit to their customers.

      so is the need to maintain incentives for creativity

      Such as retaining the ability to profiteer from other peoples' work, but not comply fully with their wishes?

    112. Re:I can see both sides by dfghjk · · Score: 1

      "You mean software licensed to third parties by other third parties with none of my code involved? Where did I write that?"

      You take offense when a company uses GPL'ed code, complies with the license, but doesn't unlock it's hardware. That's what I mean by "how others use software licensed to them"

      "If I don't accept how they want to do business with me, I have no obligation to do business with them..."

      Yes, but that's the extent of it. I'll remind you that you also said "Deny all you want, but don't expect my computer to obey you." What did you mean by "obey"?

      "Now where did I say that?"

      Once again, you said it here: "Deny all you want, but don't expect my computer to obey you."

      "And they are free to do so, except using my code. In addition, they cannot expect me to buy their DRM:ed offerings (although I won't pirate it either)."

      Perhaps, depending on your license. Depending on the circumstances, GPLv2 and DRM aren't mutually exclusive. As far as pirating, that's good to hear. Seems like you were implying otherwise.

      "Such as the advantage of reduced costs. This certainly gives them two options, lower prices or raised profit margin (or a combination of the two). But I don't see why programmers releasing GPL software have any responsibility to fund the development for vendors that don't want to pass on the GPL spirit to their customers."

      Certainly one of the big incentives is cost, especially when a product may otherwise not even be viable.

      Programmers don't release GPL out of any responsibility to anyone. They do it for fun, for glory, for education, for principle. Some do it for pay, but no programmer sets out to volunteer his work so that others may profit, and in no way can the efforts of these programmers be considered "funding".

      Now, regarding "the GPL spirit", there is no such thing. There is the license itself and nothing else. What matters is how that license is interpreted by those involved (which may include judges and juries if it gets to that point). The "spirit" of the GPL is subject to the whims of RMS and will change as his personal politics change. If you release code under a license then don't get mad when you find out your license doesn't pack the punch you thought it did.

      So far, the GPL hasn't even been tested so we have only the opinions of the FSF and attorneys who have commented to tell us what it actually means. I personally have trouble believing that the inclusion of header files constitutes linking, for example, since a header is simply documentation on how to use an interface. I would be excited to hear how a challenge to that played out.

      "Such as retaining the ability to profiteer from other peoples' work, but not comply fully with their wishes?"

      Their wishes are reflected in their license. If their license allows certain use then who's to say a company doesn't comply?

      It's clear that RMS realizes that GPLv2 doesn't extend as far as he wants it to. There wouldn't be a GPLv3 if that wasn't the case. For those that agree with RMS's politics, they should embrace and evangelize GPLv3. Not all agree (Linus included) and the more radical and restrictive RMS gets with his policies the more marginalized he will become. Linus wants Linux (and free software in general) to remain relevant. Some programmers take it much further than that and don't agree with even the GPLv2 restrictions.

      Believe it or not, some programmers don't mind their work being integrated into commercial products, just as some content creators freely release works into the public domain. GPL'ed works compete with these projects as well.

    113. Re:I can see both sides by init100 · · Score: 1

      I'll remind you that you also said "Deny all you want, but don't expect my computer to obey you." What did you mean by "obey"?

      Simply that if it's in my power, my computer will not be DRM-crippled, which means that I'm in charge of my computer, not "them". Of course, that means I won't be able to buy their DRM-crippled products, but that's fine with me.

      GPLv2 and DRM aren't mutually exclusive.

      At the moment, no, but that problem is being addressed. I'll switch to GPLv3 for all my GPL code releases when the license is finished (unless problem turns up with it).

      As far as pirating, that's good to hear. Seems like you were implying otherwise.

      I only meant that my computer won't obey their demands (because of a lack of DRM). The lack of DRM also means that I won't be able to play their content, but I'm fine with that. I refuse to pay money for intentionally crippled hardware. The irony is that DRM only hurts their legitimate customers, who will be locked into specific systems by the DRM. The pirates will get it anyway, with DRM stripped, which in essence means a better product. But I don't support copyright infringement, how could I do that and at the same time enforce the GPL (which depends on copyright)?

      Now, regarding "the GPL spirit", there is no such thing.

      Okay, let's say the free software spirit instead. Ask the FSF. They would probably disagree with your claim of no GPL spirit.

      If you release code under a license then don't get mad when you find out your license doesn't pack the punch you thought it did.

      This is a fairly recent problem, and is therefore being addressed by the FSF and the community (by way of the drafting and comments process). I never thought the current version packed the punch to prevent DRM from removing user freedom, I'm simply happy to see it addressed.

      Believe it or not, some programmers don't mind their work being integrated into commercial products

      Neither do I under certain circumstances. GPL is for code that I write for free on my spare time. BSD is for code written at my current place of work, since I work at a publicly funded university. Taxpayers (including corporations) already payed for my work, so they should be able to use it any way they want. I could even write proprietary software if I would get paid, provided it wouldn't be for Microsoft or similar companies (I wouln't want to help such companies get any further than they already have).

    114. Re:I can see both sides by dfghjk · · Score: 1

      "...BSD is for code written at my current place of work, since I work at a publicly funded university. Taxpayers (including corporations) already payed for my work, so they should be able to use it any way they want..."

      ah, and I completely agree with that. Some would say that such code should be GPL'ed but I don't agree. A BSD-like license is the right answer.

      "Okay, let's say the free software spirit instead. Ask the FSF. They would probably disagree with your claim of no GPL spirit."

      Haha, I'm sure you're right and I doubt I'd convince RMS otherwise. My comment regarded how a license would be interpreted. What the author(s) intended msy be different.

      Otherwise, I completely agree with you. I don't believe, assuming GPLv3 achieves its goals, that it will be universally adopted. I feel you are free to license your work as you like but i'm not sure v3 will be better for the community than v2.

    115. Re:I can see both sides by 5937 · · Score: 1

      Your brother can't? Is that typical for your family? :)

  2. Managing requirements by MichaelSmith · · Score: 1

    There is a lot of waffle in the article about listening to people but nobody had presented a simple table showing the requirements for GPLv3 in different drafts. This is the sort of thing you do to design commercial software and I would expect that the same approach would make the GPL more transparent.

    If they want to give Torvalds's input a low priority then show that somehow. Otherwise show where his input has gone.

    I don't want to take sides in the Linus v RMS thing here, I am just a bit sick of people having to reinvent the argument each and every time.

    1. Re:Managing requirements by Anonymous Coward · · Score: 1, Informative

      There is a lot of waffle in the article about listening to people but nobody had presented a simple table showing the requirements for GPLv3 in different drafts.

      What about this one?

    2. Re:Managing requirements by Ohreally_factor · · Score: 1

      A lot of hand waving. This "article" is really an editorial, not news. Linus himself has said that the section on DRM is not what bothers him, but other parts of the license that are actually engineered to interfere with DRM. The problem is that it will interfere with a lot of legitimate uses.

      I don't see any real refutation of Linus's points in the article. It reads more like a personal attack, or at least an unsubstantiated one.

      --
      It's not offtopic, dumbass. It's orthogonal.
  3. Isn't Linux beside the point here? by JanneM · · Score: 4, Insightful

    I'm sure lots of people will correct me if I'm wrong, but isn't the Linux kernel - and thus Torvald's views - rather unimportant here?

    The entire kernel, and all contributions from hundreds or thousands of people, are explicitly licensed as GPL version 2. Even if the kernel people were rabidly enthusiastic about GPL v3, they'd have a very, very difficult time changing the license in any case; as a practical matter it'd probably be impossible. So what Torvalds, in the guise of kernel maintainer, thiks of the license is not really relevant since the licence, no matter what it looks like, would never be used by the kernel in any case.

    Torvalds views as an OSS developer are of course relevant - but as one voice among the hundreds of other leading developers in various projects. And as has been pointed out, if he really wanted to be constructive he'd have joined in the debate itself, rather than just sniping at it via the media.

    --
    Trust the Computer. The Computer is your friend.
    1. Re:Isn't Linux beside the point here? by jpardey · · Score: 1

      But who owns the copyright to each bit of code? I haven't looked at the source, but I assume the copyright would be granted to whatever body oversees linux. It would be a nightmare to maintain otherwise.

      --
      I have freaks! I did something right...
    2. Re:Isn't Linux beside the point here? by LLuthor · · Score: 2, Informative

      Nope.

      I still own copyright on the little pieces of the kernel that I wrote.
      The only rights anyone else has are those granted by the GPL 2.

      Changing the kernel license is impossible. Many contributions have been made by people who are now unreachable, dead, or simply disagree with a license change.

      --
      LL
    3. Re:Isn't Linux beside the point here? by headkase · · Score: 1

      Um, there is no body that has oversight for the Linux kernel. As a public service announcement for you, most of what people call "Linux" is actually the Linux kernel plus the GNU Free Unix base and a windowing layer. There is no maintaner because the because the various licences that cover these code bases (including the gpl v2) are permissive. You are allowed to use the code as long as you list in your own documentation where the code came from and who it is copyrighted to. Usually, there are conditions in a particular license where derivative code must be released under the same license. Some licences such as the gpl require you to publish your source code while others such as the bsd license doesn't require this and also allows commercial use without any payment.

      --
      Shh.
    4. Re:Isn't Linux beside the point here? by flooey · · Score: 1

      But who owns the copyright to each bit of code?

      Whoever wrote that particular bit of code. That's one of the amazing things about the way the GPL is written, it takes what would normally be a complete mess and makes it workable. And not only that, but by having each coder retain copyright to what they wrote, you also create a huge body of people who have standing to sue were someone to violate the GPL.

    5. Re:Isn't Linux beside the point here? by dbIII · · Score: 1
      most of what people call "Linux" is actually the Linux kernel plus the GNU Free Unix base and a windowing layer
      Hence the silly name change suggestion of LiGnuX - later revised to the irrelevant gnu/linux. Call it Ubuntu, Fedora, Gentoo or whatever instead if that is what you are talking about - I'm sick of newbies flaming me when I don't call the kernel gnu/linux becuase they think it is a gnu project and RMS wrote most of it.

      I for one have a nvidia binary kernel module loaded which would never have been allowed if RMS ran the project or had any meaningful involvement in it - and I'm fairly sure the new version of the GPL would prohibit that sort of thing.

    6. Re:Isn't Linux beside the point here? by cas2000 · · Score: 1
      The entire kernel, and all contributions from hundreds or thousands of people, are explicitly licensed as GPL version 2. Even if the kernel people were rabidly enthusiastic about GPL v3, they'd have a very, very difficult time changing the license in any case; as a practical matter it'd probably be impossible. So what Torvalds, in the guise of kernel maintainer, thiks of the license is not really relevant since the licence, no matter what it looks like, would never be used by the kernel in any case.


      that's true for the kernel as a whole, but i'm not sure that it's true for particular parts of the kernel. GPLv2 and GPLv3 will be compatible licenses, so i can't see any reason why the author of a particular part of the kernel can't license their work under GPLv3. if it's a crucially important part of the kernel (i.e. too big to be rewritten and replaced) then, for all practical purposes, anyone using the kernel has to comply with the terms of both GPLv2 and GPLv3.

      personally, i don't see what Linus' problem is. i would have thought that prohibiting the misappropriation of GPL code via sneaky DRM mechanisms would be a good thing - after all, the point of GPL is "once free, always free". subverting that by by using DRM to make sure that no "unauthorised" version of the code can be installed is not a desirable outcome.

    7. Re:Isn't Linux beside the point here? by init100 · · Score: 1

      I assume the copyright would be granted to whatever body oversees linux. It would be a nightmare to maintain otherwise.

      As other people have already pointed out, every developer owns the copyright to the piece of code they wrote. The is one advantage of this not yet mentioned in this thread: By retaining the copyright to the code you wrote, you can prevent Linus (or the suggested oversight body) changing the license to a proprietary one, locking the code up along with your contributions. Not that I see this happen too soon, but it is still a kind of insurance against this happening in the future.

      I'd refuse contributing my spare time to a project that requests me to transfer the copyright of the code I wrote.

    8. Re:Isn't Linux beside the point here? by mesterha · · Score: 1
      The is one advantage of this not yet mentioned in this thread: By retaining the copyright to the code you wrote, you can prevent Linus (or the suggested oversight body) changing the license to a proprietary one, locking the code up along with your contributions.

      As understand the GPL license, even the copyright owner can not change the license. If you could change the license then this would be a big problem for anyone who depended on GPL software. At any time your software could become illegal. Instead, what the copyright owner can do is release his software under multiple licenses. Therefore, if some owns the copyright they can effectively create a proprietary fork but anyone can take up the old GPL software and continue developing it.

      --

      Chris Mesterharm
    9. Re:Isn't Linux beside the point here? by AuMatar · · Score: 1

      If the code is already released, it can't be relicensed to GPLv3 only. If, for example, the guy who wrote the scheduler was to release the scheduler under GPLv3, he could do so. The license would not change the code to GPL3 only, it would make it GPLv OR GPLv3 (whichever the person using the code wishes to use). So no, that won't work as a backdoor way to make Linux GPL3. Although it would be nice if individual contributors made things available as GPLv3 as well, so future OS writers can use the code in future OSes.

      --
      I still have more fans than freaks. WTF is wrong with you people?
    10. Re:Isn't Linux beside the point here? by init100 · · Score: 1

      As understand the GPL license, even the copyright owner can not change the license.

      This is certainly true for the current version, but for upcoming versions the copyright owner can change the license. So users of GPL software does not have to worry that their software suddenly becomes illegal.

      But still, if I would refrain from contributing to projects that requested copyright transfers, because they might take my code proprietary in the future. If I wanted to allow that, I would use a BSD (or similar) license instead.

    11. Re:Isn't Linux beside the point here? by Ohreally_factor · · Score: 1

      Please explain to me how GPL code can be misappropriated by sneaky DRM mechanisms. And please make the distinction between misappropriation and "using it in a way with which I don't agree".

      --
      It's not offtopic, dumbass. It's orthogonal.
    12. Re:Isn't Linux beside the point here? by TheRaven64 · · Score: 2, Informative
      As understand the GPL license, even the copyright owner can not change the license.

      Not quite true. The GPL does not (and cannot) reduce the rights of the copyright owner. The only thing that can do that is assignment of the copyright to another entity.

      The GPL can not be unilaterally revoked. This means that code, once licensed under the GPL, remains under the GPL. The copyright owner is still free to release it under other licenses, however. If they do, then users of the code may have the choice as to which license they accept. An example of this is MySQL; you may either use the GPL (and abide by its conditions) or buy a proprietary license with fewer constraints.

      --
      I am TheRaven on Soylent News
    13. Re:Isn't Linux beside the point here? by WalksOnDirt · · Score: 1
      GPLv2 and GPLv3 will be compatible licenses...

      The GPLv2 license with the later versions clause is of course compatible with GPLv3, but other than that I don't think so. GPLv3 adds more restrictions, which is prohibited by v2; and if GPLv3 is made compatible with the v2 only license it would be pointless.
      --
      a,e,i,o,u and sometimes w and y (at be if of up cwm by)
    14. Re:Isn't Linux beside the point here? by cortana · · Score: 1
      GPLv2 and GPLv3 will be compatible licenses
      They will be? The GPLv3 contains many additional restrictions over those permitted by GPLv2 which would seem to make them incompatible.
    15. Re:Isn't Linux beside the point here? by cortana · · Score: 1

      If I, as a user, cannot make use of the source code I recieved under the GPL (see: Tivo) then the license has been subverted. This is the issue that the DRM clauses in GPLv3 want to solve.

      Unfortunately most of the rest of the world seems determined to bury its head in the sand on this issue. :(

    16. Re:Isn't Linux beside the point here? by mesterha · · Score: 1

      This is certainly true for the current version, but for upcoming versions the copyright owner can change the license. So users of GPL software does not have to worry that their software suddenly becomes illegal.

      But still, if I would refrain from contributing to projects that requested copyright transfers, because they might take my code proprietary in the future. If I wanted to allow that, I would use a BSD (or similar) license instead.

      I guess I'm not being clear because of the hour, but my point was that under the current version your software cannot become illegal even if you transfer the copyright. If the new owner releases a proprietary version, the old version is still under the GPL, and you can use and build on that old version.

      Perhaps I misunderstood your original point, but the copyright owner can only lock up the code if he has the copyright on all the code and none of the code was ever released under the GPL. Therefore, if you want to protect your contribution then you just need to release your contributions under the GPL before you give up the copyright. From then on your contribution will always be available.

      In addition, you should only contribute to a software project with a license that always guarantees you access to the code, since your contribution might not be worth much without access to the rest of the code. I assume this is part of what it means to be a GPL compatible license.

      However, maybe you just don't like the fact that someone can "lock up" a version of your contribution and profit off your labor. In that case, you should keep the copyright.

      --

      Chris Mesterharm
    17. Re:Isn't Linux beside the point here? by quintesse · · Score: 1

      Well, as far as I know the ownership of a lot (all?) of the GNU code has been signed over to the FSF just so they can better protect the work of all the individuals involved.

      I don't know which works better or if there is even any real difference, just pointing out that there are alternatives in the management of the ownership using the same GPL.

    18. Re:Isn't Linux beside the point here? by Ohreally_factor · · Score: 1

      Can you explain how exactly it's been subverted? You've got the code. If you wanted to play with a hardware, maybe you shouldn't have bought a TIVO. Am I correct in understanding that you want to be protected from buying the wrong hardware?

      --
      It's not offtopic, dumbass. It's orthogonal.
    19. Re:Isn't Linux beside the point here? by mesterha · · Score: 1
      Not quite true. The GPL does not (and cannot) reduce the rights of the copyright owner. The only thing that can do that is assignment of the copyright to another entity.

      Well I guess it depends on how one defines rights. For example, before licensing under the GPL, the copyright owner can stop anyone from publishing his code. Afterwords, anyone who receives the code from the owner can publish the code.

      The GPL can not be unilaterally revoked. This means that code, once licensed under the GPL, remains under the GPL. The copyright owner is still free to release it under other licenses, however. If they do, then users of the code may have the choice as to which license they accept. An example of this is MySQL; you may either use the GPL (and abide by its conditions) or buy a proprietary license with fewer constraints.

      Yes, this was my point. I guess it was confusing when I said the owner can not change the license. By this I mean he can not change the license to, for example, effectively revoke the GPL license. He can still distribute his code under a different license. I assume this is the "right" of the copyright owner to which you refer.

      --

      Chris Mesterharm
    20. Re:Isn't Linux beside the point here? by Anonymous Coward · · Score: 1, Informative

      Am I correct in understanding that you want to be protected from buying the wrong hardware?

      No. I'm just telling Tivo that they can't use code I've written if they're going to prevent others from others modifying it and using it. They can pass on the same rights that I give to them or they can write their own code.

      I'm not really interested in your sophistry about how they can modify it, it just won't work and that makes everything okay. You can write the code that let's them do that and I'll be relatively happy.

    21. Re:Isn't Linux beside the point here? by init100 · · Score: 1

      my point was that under the current version your software cannot become illegal even if you transfer the copyright. If the new owner releases a proprietary version, the old version is still under the GPL, and you can use and build on that old version.

      You are right. In my opinion, I would not want future versions of code containing my GPL-licensed contributions to be taken proprietary, and that's why I resist copyright transfer (for spare-time code).

      my point was that under the current version your software cannot become illegal even if you transfer the copyright.

      It would be available yes, but it would also be included in a proprietary product, which I would not want for code released under the GPL. This is what retaining of copyright protects me against.

      my point was that under the current version your software cannot become illegal even if you transfer the copyright.

      Exactly.

      Note that I'm not really a GPL zealot, I just don't want code written in my spare time to be taken proprietary. If I would be hired to write proprietary code, that is another matter, since I get a piece of the pie. A third way is releasing code with a BSD license, which I do at my current employer, since I work in a publicly funded university. Taxpayers (including businesses) already payed for my work, so they should be allowed to do what they want with it, including using it in a proprietary product.

    22. Re:Isn't Linux beside the point here? by cortana · · Score: 1
      See http://www.gnu.org/philosophy/free-sw.html:

      Free software is a matter of the users' freedom to run, copy, distribute, study, change and improve the software. More precisely, it refers to four kinds of freedom, for the users of the software:

      • The freedom to run the program, for any purpose (freedom 0).
      • The freedom to study how the program works, and adapt it to your needs (freedom 1). Access to the source code is a precondition for this.
      • The freedom to redistribute copies so you can help your neighbor (freedom 2).
      • The freedom to improve the program, and release your improvements to the public, so that the whole community benefits (freedom 3). Access to the source code is a precondition for this.
      The fact that I have not, and will never, buy a Tivo does not change the fact that Tivo are preventing end users from excercising freedoms 1 and 3, as intended by the owners of the code they build upon.
    23. Re:Isn't Linux beside the point here? by Ohreally_factor · · Score: 1

      I'm not getting how Tivo is preventing you from adapting the source code, if they're providing you with it. They give you the source code, then improve it all you want. Knock yourself out. Build some Tivo-like hardware and install it on that. Maybe you want Tivo to open source their hardware designs? Is that going to be in the GPLv4?

      I'm just not seeing how either freedoms 1 or 3 are being interfered with. What it sounds like is that you want to "protect" the user from closed hardware. What's it feel like, being Big Brother?

      --
      It's not offtopic, dumbass. It's orthogonal.
    24. Re:Isn't Linux beside the point here? by cortana · · Score: 1
      I'm not getting how Tivo is preventing you from adapting the source code, if they're providing you with it. They give you the source code, then improve it all you want. Knock yourself out. Build some Tivo-like hardware and install it on that.

      You are ignoring the parts of freedom 1 that I highlighted for your attention. I will quote it again:

      The freedom to study how the program works, and adapt it to your needs (freedom 1). Access to the source code is a precondition for this.

      Access to the source code in and of itself does not guarantee the ability to adapt the device to the user's needs! From the man himself:

      You see, the Tivo is designed so that it won't run your changed versions, it refuses to even start and thus, nominally, Freedom number 1, the freedom to change the source code so that it will do what you want, nominally the users have that freedom but really the user does not have that freedom. You can change the source code so that it would do what you want, but then it won't do anything.

      So this is called Tivoisation and this is what we're trying to prevent. But why are we so concerned with this? Well, why would anybody do Tivoisation? What is the motive? The reason is because they're putting malicious features into the code and they don't want the users to fix these deliberate problems. The Tivo has two kinds of nasty features.

      [descriptions of spyware and DRM]

      Now, I disagree with those features, I think they're unethical. Well, as long as people continue to have the full, the real enjoyment of Freedom number 1, I don't need to worry about those malicious features because people will take them out, they will fix them, but once the software is tivoised, the users can't fix it.

      The rest of your post is beneath a response. Good day.
    25. Re:Isn't Linux beside the point here? by Anonymous Coward · · Score: 1, Insightful

      Like you say, Torvalds has the same right to snipe as anyone. But I don't see Linus demanding disproportionate consideration, I think it's us blowing Linus' comments out of proportion.

    26. Re:Isn't Linux beside the point here? by Ohreally_factor · · Score: 1

      You've made a leap from adapting the program to your needs to adapting the device to your needs. Again, why not just insert a clause in the GPL that will force a hardware maker to open source the designs?

      The quote you selected is quite revealing. RMS wants to protect the user from himself. The user cannot be trusted not to purchase a product with malicious features, so the GPLv3 must remove the choice from the user. This is what I mean by Big Brother. This is what you are supporting. The individual is not to be trusted, so the collective must make decisions for him. I'm sorry, but I don't want to live in the world you have planned for us.

      --
      It's not offtopic, dumbass. It's orthogonal.
    27. Re:Isn't Linux beside the point here? by CTachyon · · Score: 1

      I for one have a nvidia binary kernel module loaded which would never have been allowed if RMS ran the project or had any meaningful involvement in it - and I'm fairly sure the new version of the GPL would prohibit that sort of thing.

      Actually, the GPLv2 prohibits it, too. It's quite against the letter of the current GPL to distribute nVidia's binary-blob driver with the Linux kernel, as the nVidia driver is clearly a derived work of the Linux kernel (i.e. you need kernel source code to compile the wrapper that turns the binary blob into a driver -- the finished driver doesn't make any sense without a Linux kernel to go with it, so the kernel plus driver equals a derived work). This is why the handful of distros that currently distribute binary blobs are moving away from them, and the smart ones require you to compile the blobs into drivers yourself (albeit with automated wrappers around the process). It's only by the good graces and/or ignorance of various Linux copyright holders that nobody's been sued over it yet.

      --
      Range Voting: preference intensity matters
    28. Re:Isn't Linux beside the point here? by CTachyon · · Score: 1

      You've got the gist of it, but I just want to clarify for other readers.

      The way it works, from a copyright holder's perspective, goes something like the following. By releasing your work under the GPL, you have irrevocably given the permissions listed therein to anyone who receives a copy. As the copyright holder, you can go back and relicense it (whether more or less restrictive), but people will always be able to keep distributing the GPLed copies, since the GPL cannot be revoked.

      (Something like this happened with Secure Shell, except the old SSH license was BSD-like. Any free software license will, ipso facto, be irrevocable due to the distribution model, and the GPL is not in any way unique in that regard. That's why Sun doesn't let you redistribute Java after you download it.)

      Beyond that, a catch is that the exact wording of the GPL is itself copyrighted by the FSF, and the terms on redistributing the GPL itself read: "Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed." This means that, if you want a license that works like the GPL but isn't the actual FSF GPL, you (a) have to write it from scratch yourself (or pay your lawyer to do it) to avoid creating a derivative work that violates the license on the GPL, and (b) you can't call it "GPL", since it would be fraud to misrepresent your own custom license as the genuine FSF GPL (although, technically, the FSF doesn't explicitly own a trademark on the name "GNU General Public License").

      If you need to, you can get around this by using a disjunction of licenses ("You may distribute this software under ANY of these licenses"). If you really, really need to, some programs have been distributed under a conjunction of licenses ("You may distribute this software only if you meet the terms of ALL of these licenses"), which ended up the case with the OpenSSL license (which is a bit of a trainwreck due to hysterical raisins). And, in very rare cases, you can ask the FSF for permission to modify the GPL (see the Affero license).

      --
      Range Voting: preference intensity matters
    29. Re:Isn't Linux beside the point here? by mrchaotica · · Score: 1
      the nVidia driver is clearly a derived work of the Linux kernel (i.e. you need kernel source code to compile the wrapper that turns the binary blob into a driver -- the finished driver doesn't make any sense without a Linux kernel to go with it, so the kernel plus driver equals a derived work).

      As I understand it, the binary part of the nVidia driver is actually largely the same codebase as nVidia's Windows drivers. The wrapper is GPL. Therefore, the entire package barely squeaks by as not violating the GPL.

      I don't like it either, but that's the way it is.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    30. Re:Isn't Linux beside the point here? by honkycat · · Score: 1

      I've got to say, I agree with the other guy. You have access to everything that Tivo has done to the source code. The fact that it won't run on their hardware is unfortunate, but they haven't taken anything away from you. You are still free to take the source and port it back to any other hardware you like. Yeah that sucks, but it's a hardware problem, not a software problem.

    31. Re:Isn't Linux beside the point here? by honkycat · · Score: 1

      You ignored his very apt observation that you are still free to find another source for the hardware that will run the Tivo software and run it on that. There's nothing particularly unique about the Tivo hardware -- you can build it yourself for a few hundred bucks and be free to run anything you want on it. Complete with Tivo's additions since they give you the source.

    32. Re:Isn't Linux beside the point here? by mrchaotica · · Score: 1
      And please make the distinction between misappropriation and "using it in a way with which I don't agree".

      That's what "misappropriation" means, dumbass!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    33. Re:Isn't Linux beside the point here? by mrchaotica · · Score: 1
      the GPLv3 must remove the choice from the user.

      Let's see if you can answer this question, without any bullshit: What choice did the GPL v.3 remove from the user?

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    34. Re:Isn't Linux beside the point here? by Bryan+Ischo · · Score: 1

      I agree with the guy that you don't agree with. In fact I think you are entirely missing the point of the GPL, in several different ways:

      1. You're missing the point of the spirit of the GPL, which are the restrictions which it is trying to place on the redistributors of its software. The GPL is a license which allows a developer to ensure that the software that they have written and released always be useable in a certain way by end-users; which includes always being modifiable by those end-users. You are taking a much too narrow view on the meaning of the word "modifiable". It doesn't matter if I can modify the software but can't run it. That's not modifiable. Modifiable in the GPL sense means being able to modify it and use the modified version on the same platform that the original version ran on - which is a much more meaningful definition of modifiable.

      2. You're missing the point of software licenses altogether: you seem to suggest that they're somehow meant to serve the end-users. They're not. A software license is a way for the developer of the software to choose how their code is to be used. They've done the work of creating the code, and they're willing to give it away for free - as long as they get some guarantees about how it's going to be used, so that they don't feel grossly exploited. A company which uses a piece of GPL'd software and applies DRM mechanisms to ensure that it can never be modified (by the useful definition of modified that I just gave in point 1) is *EXPLOITING* the GPL. And the developer has every right to try to stop that. The GPLv3 gives them the ability to do that. It's the developer's choice entirely to decide to use the GPLv3 or not. And if they use it, you have very little right to complain that they're not releasing their code under a "free" enough (i.e. "exploitable" enough) license. It's their code, they can release it however they want.

      Now of course, just as the developer has every right to put whatever restrictions they want on the source code they release (and many developers find the spirit of the GPLv2 to their liking, and many will find the GPLv3 even better), it is also your right to decide not to use that software because you don't like the license. The greater community will through the collective tension between end-users' desire to get what they want, and GPL developers' desire not to be ripped off, decide which license will win out. So far the GPL has been a huge win obviously, it is hugely successful and appreciated by developers and many end-users alike. And the GPLv3 will be the same.

    35. Re:Isn't Linux beside the point here? by Bryan+Ischo · · Score: 1

      What you are saying is obviously false. If it were that easy to reproduce the TiVo hardware, and run TiVo's additions to the GPL'd software that it uses on it, then someone would have done it already.

      Once again, you're completely missing the point. The developer gets to choose how their code is going to be used. The developer may not want to release their source code so that some hardware manufacturer can lock users into a certain version of the software using DRM mechanisms. The developer may not want the end users of the software to have to spend hundreds of dollars to develop a compatible hardware platform for the source code to run on, rather than using the hardware that they already bought for the express purpose of running the modified version of the GPL'd software in question. The developer will then choose to license their software under GPLv3.

      The developer may also not care about these issues, in which case they can use the GPLv2.

      It's really very, very simple:

      1. Developer writes some great code that they want to share with the world.
      2. Developer decides that if they're going to release the code for free for anyone to use, that they want to ensure that all end-users always have the freedom to modify the code, use the modified version, and re-distribute it.
      3. Developer releases the code under GPL because it guarantees exactly what the developer wants.
      4. Company decides to use the GPL'd software in its product, and uses DRM mechanisms to ensure that modified versions of the GPL'd software can't be run on it.
      5. Developer realizes that this violates their intention when they released the code under copyright with GPL restrictions: the end-user can't modify the code and use the modified version. At least, not in a meaningful way (yes, they can buy new hardware or spend extra effort to port the code to some new platform or something like that, but that's not what the developer intended that the user would have to do, and from the user's perspective, it sure doesn't feel like they can modify and use the modified software, since they can't even use it on the platform which it was written to run on!).
      6. If developer used GPLv3 they can sue the company for copyright infringement and force the company to respect the license. If the developer used GPLv2 then too bad for them, they didn't protect their code as well as they thought they did because the GPLv2 doesn't address this issue.

      Thus we see the value of the GPLv3. It allows developers to protect their code from exploit in a way that they care about. If they don't care about that, they use GPLv2.

    36. Re:Isn't Linux beside the point here? by dbIII · · Score: 1
      Therefore, the entire package barely squeaks by as not violating the GPL.

      I don't like it either, but that's the way it is.

      So obviously it is time to penalise those nasty linux people and nasty nvidia people and stop this sort of thing happening again by changing the licence? As said above - linux is not a gnu project, so it does NOT have to follow the whim of RMS in his fight against DRM and even commercial GPL software (eg. emacs fork).
    37. Re:Isn't Linux beside the point here? by mrchaotica · · Score: 1

      What are you talking about? I'm pretty sure that Linus's objections to the GPL v.3 have nothing whatsoever to do with nVidia, and I haven't heard of any changes that would affect that kind of thing at all. The changes are designed to stop the likes of TiVo.

      So yeah, you should calm down because you're ranting incoherently.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    38. Re:Isn't Linux beside the point here? by honkycat · · Score: 1

      I wouldn't say it's so obviously false. I haven't looked at the software on a Tivo, but I bet the actual changes to GPL software are not that significant. More likely, they have their own proprietary apps that run on top that do all the stuff you'd really want to duplicate.

      I understand what you're saying about the value, but I don't feel it is a level of control that is justified. There's nothing anywhere in the GPL that requires the new authors make it easy to use their changes. Just having the code available is enough to disclose what they are doing, and in my mind, that's enough. There's no need that they even distribute the hardware freely (as in widely) in the first place.

      Anyway, as you say, the existing version of the license will continue to exist and to be used widely. Good. I can see the value in the v3 additions to some, but it's not something I would opt for. What's unfortunate for those who feel the way I do is that it means it's likely there will not be further developments on DRM-less versions of the license. Oh well.

    39. Re:Isn't Linux beside the point here? by Ohreally_factor · · Score: 1

      It removes the choice of the user to use signed binaries. It removes the choice of the user to use Trusted Computing hardware, i.e., any hardware that the user wants. It's based on the idea that the user can't make these decisions for himself and must be protected from "bad" decisions, i.e., decisions that the FSF doesn't agree with.

      (I must say that I'm disappointed that you of all people would mark me as a foe. I never would have thought that you couldn't handle a difference of opinion. Oh well. We learn a lot about each other in internecine strife.)

      --
      It's not offtopic, dumbass. It's orthogonal.
    40. Re:Isn't Linux beside the point here? by dbIII · · Score: 1

      Please read the posts above to get some context - especially the guy who was talking about how binary kernel modules should not be allowed if an outside group doesn't like them.

    41. Re:Isn't Linux beside the point here? by newhoggy · · Score: 1

      I don't see why GPLv2 and GPLv3 code can't co-exist in the same project. Linus can require that all future contributions to the kernel are GPLv3. Eventually the parts of the kernel that remain GPLv2 will be in the minority and can be systematically replaced.

    42. Re:Isn't Linux beside the point here? by WilliamSChips · · Score: 1

      By definition, future versions of GPL are GPL-compatible.

      --
      Please, for the good of Humanity, vote Obama.
    43. Re:Isn't Linux beside the point here? by mrchaotica · · Score: 1

      Hmm... I noticed a guy who was surprised that the kernel copyright holders haven't objected to it, but I haven't found anything about what you just said. Got a quote?

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    44. Re:Isn't Linux beside the point here? by mrchaotica · · Score: 1
      It removes the choice of the user to use signed binaries.

      No it doesn't. In fact, the GPL v.3 itself is what would allow the user to choose to run signed binaries (as opposed to being forced to do so).

      It removes the choice of the user to use Trusted Computing hardware, i.e., any hardware that the user wants.

      No it doesn't. The user can put GPL v.3 software on anything he wants, whether it's "Trusted" or not. I myself intend to buy a Thinkpad (which, unfortunately, has a TPM) in the next few months, and run GPL software on it. I have no doubt that eventually some of that software will be GPL v.3, and that it will continue to run just fine.

      All the new license will prevent is distributors (as opposed to users) being allowed to incorporate GPL v.3 software into their product without giving their users all of the Four Freedoms. This is exactly the same thing that the GPL v.2 does; it's just that v.2 has a loophole for two particular situations (DRM and web services).

      It's based on the idea that the user can't make these decisions for himself and must be protected from "bad" decisions, i.e., decisions that the FSF doesn't agree with.

      No it isn't. It's based on the idea that if people want to profit by using GPL software, then they should give back to the community that they're taking from. "Giving back" means guaranteeing their users the Four Freedoms, not necessarily just releasing source code.

      (I must say that I'm disappointed that you of all people would mark me as a foe. I never would have thought that you couldn't handle a difference of opinion. Oh well. We learn a lot about each other in internecine strife.)

      I can deal with a difference of opinion; I marked you as a foe because you appear to be willfully spreading FUD (as I just pointed out).

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    45. Re:Isn't Linux beside the point here? by CTachyon · · Score: 1

      Sort of. The binary blob constitutes nVidia's shared driver codebase between Windows and Linux. It exposes some intermediate functionality, which the wrapper layer thunks to. However, the binary blob itself doesn't constitute a driver, for any OS. The wrapper code for the Linux driver, however, falls under the GPL's rule because it legally counts as a derivative work of the Linux kernel. Since a derivative work plus something else is still a derivative work, the final compiled driver is still under the GPL's rule, even though most of the functionality is contained in the proprietary binary blob. And, while there's nothing wrong with doing that as an individual on your own computer (the GPL is a copyright license), you can't distribute the resulting mess legally.

      --
      Range Voting: preference intensity matters
    46. Re:Isn't Linux beside the point here? by init100 · · Score: 1

      What's unfortunate for those who feel the way I do is that it means it's likely there will not be further developments on DRM-less versions of the license.

      Then you can use the GPLv2 as a foundation and make the additions (bar DRM) you want to have. You might even use those parts of GPLv3 that you like and ignore the others. The only thing you cannot do is call your new license "GNU GPL" (or possibly GPL).

    47. Re:Isn't Linux beside the point here? by honkycat · · Score: 1

      That's true, though the GPL has the advantage of having been written and pored over by lawyers and being guaranteed GPL-compatible.

  4. Re:Sure to happen by CRCulver · · Score: 3, Insightful

    One indeed has to wonder what's going on with Torvalds. It's one thing to feel that Stallman is a kook and the Free Software ideal is often overly zealous. I admire Stallman and his movement, but I acknowledge that many people consider it all an embrassment. However, it's another thing entirely to actively cheer on the introduction of DRM, which Torvalds has been doing now for a couple of years. Doesn't Linus realize that with strict hardware controls enforcing what may and may not be run, one's freedom to tinker may disappear? You'd think that someone who invented an operating system "just for fun" would want other people to be able to experience the magic of doing whatever they likes with their computer.

  5. Oh Horrors! by RunningGeek84 · · Score: 1

    Mentioning RMS and Linus Torvalds in the same post; this is going to start a flame war ...

  6. Linus by Enderandrew · · Score: 4, Interesting

    I am very grateful for the contributions Linus has made to the world. But he can be an ass from time to time.

    And when he said that nothing much changed between the second and third drafts, he was not only being flippant, but ignorant. Many of the changes were in direct response to criticisms he made.

    GPLv3 will happen regardless of whether or not it is accepted for the Linux kernel. I'm not sure they need to make Linus happy. I think the GPL crew needs to make the license best suit their needs.

    Regardless, I don't think Linus will back down and accept it any time in the future. He has been very clear that the kernel is to be licensed under GPLv2 and GPLv2 exclusively.

    --
    http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    1. Re:Linus by Anonymous Coward · · Score: 5, Insightful

      I'll go you one further, and I hope Linus gets to read this. His behavior regarding this new draft is starting to cost him significant respect, and he's also hurting both the free software camp, and his own open source group, while providing Rovian press material for some real class A crooks. Linus is a great developer, but he needs to show a little moderation, and a little more respect for Richard Stallman. Call him what you will, but Stallman's vision regarding the GPL to this point has been beyond genius. And if it was not for Stallman's vision and tenacious courage (with Eben Moglen's help) in the face of just about every kind of demeaning criticsm and ploy one could imagine, Linus would still be in Finland, himself eating herring every day and trying to get Windows to stop crashing.

      Stallman's license has stymied a large nest of very nasty people for 20 years, people who would steal Linus blind if it weren't for Stallman and his vision. And given Stallman's record, dedication, and results, if he sees issues with patents and DRM, if I were Linus, I'd listen first, and then ask respectful questions via professional channels.

      Based on the past 20 years, and the benefits that will accrue to all of us due to his work, Richard Stallman is deserving of a Nobel prize nomination. Linus is just a developer and project manager, and he should show Stallman commensurate respect.

      jwwjr

    2. Re:Linus by Helldesk+Hound · · Score: 2, Insightful

      > Regardless, I don't think Linus will back down and accept it any time in
      > the future. He has been very clear that the kernel is to be licensed under
      > GPLv2 and GPLv2 exclusively.

      However, if the compiler that they use to compile the binary versions of the Kernel is licenced under the GPL v3, then wouldn't the Kernel also need to be licenced under the GPL v3?

      Surely GNU/Linux is an ecosystem, and the Kernel is but one part of that ecosystem that would not be able to function without all the rest of the system - at least sufficient to produce an interactive system that people would be able to use.

    3. Re:Linus by houghi · · Score: 2, Insightful
      GPLv3 will happen regardless of whether or not it is accepted for the Linux kernel.


      Sure it will happen. You could also write a GPLv4 or any other license. On my SUSE there are some 20+ different licences. The question is not wether or not you can make a new license, but wether or not people will start using it.

      I could make a "houghi license" and I am sure nobody will use it, not even me. Now if nobody is going to use it, why make it?
      --
      Don't fight for your country, if your country does not fight for you.
    4. Re:Linus by init100 · · Score: 1

      He has been very clear that the kernel is to be licensed under GPLv2 and GPLv2 exclusively.

      I wonder what would happen if the authors of some important part of the kernel suddenly change the license for their contributions to GPLv3. It is certainly in their power to do so (unless they transferred copyrights). This might effectively change the license of the entire kernel, since use of said part would require adherence to the new GPLv3 restrictions.

    5. Re:Linus by Kaktrot · · Score: 2, Informative

      I don't think anything would happen, really. The pieces that are in the Linux kernel would still be licensed under the GPLv2. They have the option of giving the code away under v3, but that doesn't change the exact copy that is already in use in the kernel.

      --
      BSD: The most efficient way of subsidizing the enemy.
    6. Re:Linus by Enderandrew · · Score: 1

      Nope. The license covers the program itself, not things you create with the program.

      Just because an office suite might be under the GPL, that does not mean documents created by it are under the GPL.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    7. Re:Linus by init100 · · Score: 1

      that doesn't change the exact copy that is already in use in the kernel.

      I think you are right. If someone changed the license, it would not affect the current version, only upcoming versions. And then someone might simply deny the inclusion of the new GPLv3-licensed code into the Linux kernel, to make sure that the kernel as a whole stays GPLv2.

    8. Re:Linus by Enderandrew · · Score: 1

      You seem to suggest that if Linus isn't using this, then there is no point to the license. Given the number of committees that worked on this, and their connection to major software projects, their involvement all but guarantees that many major software projects will use the new GPL license.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    9. Re:Linus by Enderandrew · · Score: 1

      I haven't read over GPLv3, but past versions of the GPL support multiple licenses, and general flexibility in that regard. I've even heard that the GPLv3 allows you to specify which restrictions you want to use, and which not to use.

      Just because one part of the kernel shifts to GPLv3, I don't think that requires the entire kernel to migrate to the new license.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    10. Re:Linus by portmapper · · Score: 1

      > However, if the compiler that they use to compile the binary versions of the Kernel is licenced under the GPL v3,
      > then wouldn't the Kernel also need to be licenced under the GPL v3?

      It's true that GPL is viral, but it does not infect output from programs ;-)

    11. Re:Linus by Ohreally_factor · · Score: 1

      Dude!! I'll use it!
      ---------------
      The above comment is released under the houghi license, whatever that is. =)

      --
      It's not offtopic, dumbass. It's orthogonal.
    12. Re:Linus by Helldesk+Hound · · Score: 1

      > Just because an office suite might be under the GPL, that does not
      > mean documents created by it are under the GPL.

      True - agreed.

      But what if the "output" of your program was something that statically linked to a library?

    13. Re:Linus by ultranova · · Score: 1

      I wonder what would happen if the authors of some important part of the kernel suddenly change the license for their contributions to GPLv3. It is certainly in their power to do so (unless they transferred copyrights). This might effectively change the license of the entire kernel, since use of said part would require adherence to the new GPLv3 restrictions.

      GPL is non-revocable. This means that if you licensed out some code under GPL v2, it will forever stay licensed under GPL v2. You may, of course, also license the same code under GPL v3, but users may still stick to GPL v2 if they want to. Or you could license any new versions under GPL v3, but the users can take the old version and start developing for it themselves under GPL v2 - a process known as forking, which happened to XFree86.

      I am not a lawyer and this is not legal advice.

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    14. Re:Linus by baadger · · Score: 1

      > It's true that GPL is viral, but it does not infect output from programs ;-)

      not until GPL v4 :P

    15. Re:Linus by Anonymous Coward · · Score: 0

      Linus would still be in Finland, himself eating herring every day

      Please rid the world of one condescending racist asshole by killing yourself. Thanks!

    16. Re:Linus by Anonymous Coward · · Score: 0

      I am Finnish and there is nothing wrong with herring...

    17. Re:Linus by Anonymous Coward · · Score: 0

      AHAHAHAHAHA. As if Linus Torvalds care about having your respect. Who are you anyway?

    18. Re:Linus by maxume · · Score: 1

      This will never happen. They will simply stick with their own fork of gpl2 licensed gcc. This goes for anything else too. Or maybe *BSD would get more popular among linux kernal developers.

      --
      Nerd rage is the funniest rage.
    19. Re:Linus by caseih · · Score: 1

      However, if the compiler that they use to compile the binary versions of the Kernel is licenced under the GPL v3, then wouldn't the Kernel also need to be licenced under the GPL v3?


      Umm, no. The output of GCC has never been under any license; only the code of the compiler suite itself. If GPLv3 changes this, then no wonder Linus is so opposed to it. I doubt that, even under the GPLv3, GCC's output will be under any license.

    20. Re:Linus by mrchaotica · · Score: 1
      However, if the compiler that they use to compile the binary versions of the Kernel is licenced under the GPL v3, then wouldn't the Kernel also need to be licenced under the GPL v3?

      Damn it, for the fifteen-billionth time, NO!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    21. Re:Linus by mrchaotica · · Score: 1

      First of all, some people -- like me, for instance -- want the GPL v.3 and will use it.

      Second, and more importantly, there's a huge body of code out there (that's not the Linux kernel) that's licensed as "GPL v.2 or later," which will become licensable by the terms of the GPL v.3 automatically.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  7. How much did M$ pay you to 'write' that? by Travoltus · · Score: 0, Redundant

    And it's 'Gnu Public License', thank you very much.

    --
    --- Grow a pair, liberals... stop letting the Republicans bully you!
    1. Re:How much did M$ pay you to 'write' that? by chicagotypewriter · · Score: 1

      "GNU GENERAL PUBLIC LICENSE" - taken from the first line at http://www.gnu.org/licenses/gpl.txt
      thank you very much

  8. Re:The GPL needs to go by Anonymous Coward · · Score: 0

    egg troll? Is that you??

  9. yeah but guess who owns the future? by Quadraginta · · Score: 1, Insightful

    Absolutely right. But so far it's been Linus who's done the most to actually change the world. Proving once again the superiority of actually getting working technology out the door, versus spending a decade or so fine-tuning your philosophy about how to begin working on the great technology that you will eventually design when you have the philosophy just perfect (if everyone hasn't succumbed to old age first).

    I've had enough troubles in my own career directly traceable to wanting to Get Things Right at the expense of Getting Things Done to appreciate this particular point with some sensitivity, not to say bitterness. Feh.

    1. Re:yeah but guess who owns the future? by Mornelithe · · Score: 5, Insightful

      Yes, yes. Quite right. Hardly anybody uses gcc, or glibc, or gdb, or emacs, or bash, or...

      Damn those FSF nuts for never writing any software that's good enough for use. After all, everyone knows that all you need is a bare kernel to get things done.

      --

      I've come for the woman, and your head.

    2. Re:yeah but guess who owns the future? by Kaktrot · · Score: 1

      You can make the argument that Linus created the single most important piece of the whole, I suppose. I'm not sure I agree. In any case, the kernel is still a small thing compared to everything the GNU project did. Linus is brilliant, of course, but somehow I think that things might be going a bit smoother now if maybe the GNU kernel project hadn't been such a clusterfuck.

      --
      BSD: The most efficient way of subsidizing the enemy.
    3. Re:yeah but guess who owns the future? by cryptoluddite · · Score: 1

      Hurd is a failure because Linux exists. Without Linux, the same developers working on it would be working on Hurd (or a fork of hurd). Torvolds was in the right place at the right time, and did a competent job of capitalizing on it. In this respect he is like Bill Gates, with people saying how if it hadn't been for Microsoft we'd still be using DOS. I think this kind of argument, that it could never have turned out as well without , is pretty absurd.

    4. Re:yeah but guess who owns the future? by Quadraginta · · Score: 4, Interesting

      Well, yes, good point. A very good point.

      But...I dunno. Until Linux came along, these things seemed a bit on the fringe to me, except for Emacs, which predates the FSF anyway. I installed GCC and GDB once or twice in the early 90s, but it never did as good a job as the compiler and debugger you always got along with your proprietary Unix, which you got along with your workstation. (The $1000 license fee being peanuts compared to the $40,000 hardware anyway.)

      So at least in my experience -- and I admit I was a scientific programmer, a user, and not a systems programmer or applications developer -- the GNU tools were pretty much just curiosities until Linux made it possible to run Unix on your PC. Now that was a Great Thing. All the elegance, stability, security and network-savviness of the work computer now available at home. Very nice. And the GNU tools made that possible, yes. But the free kernel was the keystone to that arch, I think. Linux could have squeaked by with few less GNU tools (albeit not without GCC), but I think all the GNU tools would have remained curiosities without the free kernel. As soon as a great free Unix existed, a lot of people jumped in to add what was still missing, like a fancy desktop instead of plain old X and fvwm, drivers, or package managers instead of a giant tarball and a 64kb README. But would people have ever jumped in to create the kernel, knowing the various GNU system applications already existed? Well, they didn't -- not until Linus. Maybe it had to wait until hardware prices came down, so if it hadn't been Linus it would've been someone else anyway. But maybe it's also harder for people to get excited when they see a bunch of pieces lying around, so that if maybe you built the central piece you could assemble everything into a coherent whole. Maybe it's easier to get excited when you can see a working model, even if it's crude and belches smoke everywhere, and could use some serious extra tinkering to work better. It's from that point of view that I think Linux has inspired and will inspire more people to do OSS work, or use it, than GNU. Maybe Linus is Shakespeare stealing Roger Bacon's plays -- but it's nevertheless Shakespeare who gets remembered in the history books.

      Also, what I recall (vaguely) is that between '85 and '95 or so, the GNU kernel was always coming along Real Soon Now, but seemed stuck because they wanted to Get It Right. Let's just pass lightly over the gcc/egcs wierdness, which is maybe harder to understand than the Pope's nuanced position on masturbation among priests. I think substantial dithering got short-circuited by Linus, and by the people fired up about Linux,

      Now, I'm not saying RMS or the FSF's work isn't highly valuable. The value of their work isn't what I'm talking about at all. What I'm saying is that I think the future belongs more to people like Linus -- that they will have more lasting influence -- because, as the OP said, they seems more focussed on getting stuff out the door, and the FSF (and RMS in particular) seem more focussed on making sure it's the right stuff, built with the right moral philosophy, isn't going to exploit the masses or give you karma, et cetera. In all my working experience, folks who spend substantial amounts of energy on the aesthetics of their product rather than on its bare ugly function get chewed up by the real world sooner or later. Jobs and NeXT, Betamax vs. VHS, Multics, DEC's Alpha chip -- tragedies like that come to mind. The perfect is often the enemy of the good, as they say.

    5. Re:yeah but guess who owns the future? by Ohreally_factor · · Score: 3, Insightful

      I don't think it's so much that Linus eschews changing the world. I think that he has an eminently more practical way of doing it. For one thing, he's not hung up on converting people through either religious fervor or through convincing them his way is best (if there's a difference). As he's said, he's not trying to shove anything down anyone's throat. Instead, he shows by example how it's supposed to work, and why open source development is a better way of software development, whatever your motives are. I think it's great that he's not "at war" with proprietary software and proprietary software makers. They aren't relevant to him one way or the other. They can either follow his way now or follow it later. Linus in confident in his methods. He doesn't need to fight anyone. (He's probably confident in his manhood as well.)

      And I think this was the most damn part of his indictment of the FSF. That they're hate and fear based, and when you let hate and fear dictate your principals, you end up hurting yourself and those you want to help. A good example of this is the whole issue of specific code tied to hardware. The FSF wants so badly to hurt DRM that they are willing to hurt legitimate uses. The funny part is that DRM is going to turn out to be a non-issue. DRM is not going to be relevant for long, with no action from the FSF*.

      Really, though, the ones that are going to wind up getting hurt are the FSF themselves. It will be a lot easier to rewrite the userland than it will be to rewrtire the kernel. Or so I'm told.

      Some people will take up GPLv3, but I think the majority will continue to use the GPLv2. The GPLv3 people will risk getting left behind.

      *Here's why DRM will fail on it's own: at this point in history, when a cartel of copyright holders are trying to wall off culture and charge admission, we have unprecedented new tools for the creation, marketing, and distribution of culture. The more that these culture holding companies try to control culture and withhold it, the more new culture will rush in to take its place. The more new culture developed, the less overall value for the walled off culture. There is no scarcity of culture and there will not be a scarcity of culture. On the contrary, music, literature, and art are set to explode. The power of the culture holding companies is already broken. Now it's just the long unwinding of their monopolies.

      --
      It's not offtopic, dumbass. It's orthogonal.
    6. Re:yeah but guess who owns the future? by joto · · Score: 2, Insightful

      Hurd is a failure because Linux exists. Without Linux, the same developers working on it would be working on Hurd (or a fork of hurd).

      I seriously doubt that. Hurd development was slow before linux existed, and it remains slow after linux came to life. Now it's 15 years since linux was first created, and linux is at this stage the centerpiece of an entire industry of software products and services. Meanwhile, lots of other operating systems have been written from scratch, and I can probably list dozens that are (a) more usable than hurd, (b) younger than both hurd and linux, and (c) still written by volunteers.

      Hurd development is not slow because of a lack of developers, it is slow because of bad architectural decisions, a severe case of second system effect, mach instability, failure to follow a "worse is better"-philosophy, and so on. Adding more developers to this kind of project can in many cases slow it down even further (read: "the mythical man-month").

      Torvolds was in the right place at the right time, and did a competent job of capitalizing on it.

      His name is Torvalds, not Torvolds. His place was minix enthusiasts, and yes, it probably was the correct place to find developers for a new free unix kernel. I'm quite sure I would disagree that he did a competent job of capitalizing on it, Torvalds remained a poor student for a pretty long time.

      In this respect he is like Bill Gates, with people saying how if it hadn't been for Microsoft we'd still be using DOS.

      Uh, Microsoft was the company that brought us DOS in the first place (although they didn't write it, they bought the right to it, and sold it to us consumers). And no, Torvalds is not filthy rich, like Bill Gates.

      I think this kind of argument, that it could never have turned out as well without <insert person here>, is pretty absurd.

      Maybe you find it absurd, but sometimes it's just the truth. The right man in the right place can and do make an important difference at times. You can argue that without Linus, someone else would soon have written a free 386 unix-clone. And you would probably be right, but what happened afterwards, the unique community, and so on, is largely a result of Linus being who he is, it would happened differently with another person at the center.

    7. Re:yeah but guess who owns the future? by ultranova · · Score: 5, Insightful

      All the elegance, stability, security and network-savviness of the work computer now available at home. Very nice. And the GNU tools made that possible, yes. But the free kernel was the keystone to that arch, I think. Linux could have squeaked by with few less GNU tools (albeit not without GCC), but I think all the GNU tools would have remained curiosities without the free kernel.

      The GNU project was trying to create a free version of Unix - the GNU system - and was going about it in a systematic fashion, one tool at the time. The kernel was left until last, and Linux simply happened to come at the right moment, when most of the system was already up and running but the kernel wasn't.

      As it happens, the GNU project does have a working kernel of their own, HURD. HURD never really took off, mainly because Linux got the snowball effect going - it got some users, some of whom began co-developing it, making it better, which in turn gained it more users and more developers and so on. Linux has almost all the developers, so HURD has almost none.

      But thinking that Linux is the true success story and the GNU project just a less important side path is absurd. It's the GNU project that made Linux possible, not the other way around.

      What I'm saying is that I think the future belongs more to people like Linus -- that they will have more lasting influence -- because, as the OP said, they seems more focussed on getting stuff out the door, and the FSF (and RMS in particular) seem more focussed on making sure it's the right stuff, built with the right moral philosophy, isn't going to exploit the masses or give you karma, et cetera.

      You think that Linux - a single operating system kernel - is going to have more lasting influence than the whole free software movement, of which the Linux kernel is just a part of ? Especially when what allowed Linux to grow in the first place was the development model made possible by the GPL ?

      I beg to differ.

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    8. Re:yeah but guess who owns the future? by TheRaven64 · · Score: 4, Insightful
      But the free kernel was the keystone to that arch, I think. Linux could have squeaked by with few less GNU tools (albeit not without GCC), but I think all the GNU tools would have remained curiosities without the free kernel

      There already was a free kernel. It was called BSD, and it ran on VAX and a few other things. Due to an SCO-like lawsuit, the first x86 port was delayed by a few months, and it wasn't really ready until 1992. By this time, you could build a complete Free Software system on x86 without Linux.

      These days, there are at least three Free direct descendants of the BSD kernel in active development. One is even supported by the Debian project; you can swap out the Linux kernel and install a FreeBSD kernel under Debian, and not notice the difference. Even Linux binaries work, since it has a system call translation layer (with a negligible performance hit.

      The GNU project created more than just a compiler, a shell, and a few bits of userspace. I would not be at all surprised if you are running an order of magnitude (or more) more GNU code than Linux. If you're running GNOME, then you certainly are (you know what the G stands for, I presume).

      Trying to build a Free Software system without Linux is trivial; I have three machines that I use regularly without a single line of proprietary code on them, and none of them runs Linux. Trying to build Free Software system without any GNU code is almost impossible.

      --
      I am TheRaven on Soylent News
    9. Re:yeah but guess who owns the future? by Jah-Wren+Ryel · · Score: 1
      As soon as a great free Unix existed, a lot of people jumped in to add what was still missing,
      BSD4.4 (the first release fully free of USL code) was released at roughly the same time as linux went 1.0.

      However, despite having a "more free" license than Linux, and often technically better implementations, the entire *BSD family has yet to garner a tenth of the vitality that Linux has. Can I prove that Linux's popularity over the BSD camp's is due to the GPL -- nope, but it is one very strong differentiator and Linus himself said, "Making Linux GPL'd was definitely the best thing I ever did."

      they seems more focussed on getting stuff out the door, and the FSF (and RMS in particular) seem more focussed on making sure it's the right stuff, built with the right moral philosophy,

      Yet, the history of computing is absolutely stuffed with products that "got out the door" to serve a short-term need and then died. In fact, with a few notable, monopolistic exceptions, that's practically the story of the entire industry.

      The FSF's contribution is not about code for things like gcc or emacs or hurd, it's about defining a social framework that complements human nature in order to encourage sharing by preventing any company from using another company's own work against them to gain an advantage.

      Linus does engineering that organizes electrons -- the FSF does engineering that organizes nuerons. Excellence on one side can compensate for some deficiencies on the other, but a major blunder is probably fatal no matter what - e.g. all of the examples like vhs vs betamax that you've already mentioned plus thousands more.
      --
      When information is power, privacy is freedom.
    10. Re:yeah but guess who owns the future? by Anonymous Coward · · Score: 1, Interesting

      Here's why DRM will fail on it's own: at this point in history, when a cartel of copyright holders are trying to wall off culture and charge admission, we have unprecedented new tools for the creation, marketing, and distribution of culture.

      Here's why this is wrong: DRM is not about music and video any longer. It was, but technology companies have realised that DRM is "digital"... it doesn't just refer to music and video. DRM hardware (such as these trusted computing systems, like the Intel Apple Macs) allows them to specify the exact piece of code that is allowed to run, if and allowed to run, whether it is allowed to access as piece of data. It is control beyond their wildest dreams.

      DRM is not about the MPAA/RIAA these days... they are just puppets. It is the Microsoft/Intel/IBM/HP/Apple's of the world -- they will control the hardware/software and they will broker access to your machine, and run their software secretly, and stop you from changing anything or doing anything of which they do not approve.

      Controlling music/video (and selling it to you) is just the cream on the top of the pudding for them. It's about time geeks realised this.

    11. Re:yeah but guess who owns the future? by killjoe · · Score: 0

      The GPL destroyed the SCO lawsuit. GPL3 will have the same kind of power to defend free software from the corporations that want to kill it.

      There is a reason why there are so many astro turfers here pissing on the GPL, RMS, and the FSF every time the topic comes up. They are deadly afraid of it.

      That's good for all of us.

      --
      evil is as evil does
    12. Re:yeah but guess who owns the future? by nacturation · · Score: 2, Funny

      That they're hate and fear based, and when you let hate and fear dictate your principals, you end up hurting yourself and those you want to help.

      And we all know that this leads directly to the dark side.

      --
      Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
    13. Re:yeah but guess who owns the future? by thsths · · Score: 2, Interesting

      I do use emacs, or rather xemacs, but the project is a good as dead, and certainly not the future.
      I use glibc, and I would like to use it even more, but the port to Solaris is dead.
      I use gdb, and I would like to use it even more, but the support for SPARC64 is very flaky.
      I use gcc, and I would like to use it even more, but it does not compile to common virtual machines (Perl, Parrot, Java or CIL).
      bash is nice, certainly compared to the bourne shell, but it has been like this for more then 10 years.

      So while a lot of GNU tools are useful, even the very best ones leave at lot do be desired. And don't tell me to just write a patch, because it is not that easy. The missing support of virtual machines for example is a political decision of RMS, and much the same can probably be said about the Solaris port of glibc. The missing support of anti-aliased fonts in emacs is just a symptom that the project is dead.

    14. Re:yeah but guess who owns the future? by Anonymous Coward · · Score: 0

      Thanks for the official history. Suggest you desist from contradicting those that were actually there at the time Sonny.

    15. Re:yeah but guess who owns the future? by mpcooke3 · · Score: 1

      There are many people focussed on getting stuff out the door including Apple and Microsoft, of course MS has not been so good at it lately :) but they have shipped a lot of software over the years.

      I use GNU/linux because of the rights i am given to use and modify the whole platform. If linux is not protected from DRM abuses and my ability to modify and use my system the way i want is restricted then I will move to another platform when it comes along.

      I'll even start testing a buggy Hurd kernel if I have to.

      There are questions as to whether the current GPL is "good enough", I don't know all the nitty gritty about the DRM issues but I suspect RMS is right. If he is, then eventually we'll need a GPLv3 Kernel or a kernel released under a similar license. By then we could have wasted a lot of time as people have their rights slowly erroded by the DRM restrictions and one by one give up on Linux. This could result in a lot of wasted time in continued development on a dead end linux kernel.

      I'm a software developer, I'm used to looking at worst case scenarios.

    16. Re:yeah but guess who owns the future? by Ohreally_factor · · Score: 2, Insightful

      It did, did it? I guess IBM needn't have hired any lawyers, then. Looks like the just wasted money.

      The GPL didn't destroy SCO, although it certainly played a part in events and may still play a part. First and foremost, SCO destroyed itself, because (as many guessed and as it now seems clear) they never had a case to begin with. All they had was a scheme (or three).

      --
      It's not offtopic, dumbass. It's orthogonal.
    17. Re:yeah but guess who owns the future? by iphitus · · Score: 0

      A bare kernel and emacs.

    18. Re:yeah but guess who owns the future? by replicant108 · · Score: 1

      But the free kernel was the keystone to that arch

      Actually, the GPL is the keystone.

    19. Re:yeah but guess who owns the future? by CaptainCheese · · Score: 1

      I wasn't paying attention to the whole thing til mid-1994, but based on the records I believe that it was more of an emergent concept rather than a breakthrough.

      The FSF saw the need a decade before, and was working to fill it. Stallman was the visionary, and Torvalds a lucky hacker with good timing.

      In hindsight, if the FSF could have done their Hurd development more openly and released flawed code earlier, or even hacked together an interim monolithic kernel then Linus might have just been a contributor to that. Or if Linus had taken Andrew Tanenbaums' criticisms of the monolithic model more seriously, he might have got stuck in the same problems as the FSF and never even reached a workable public alpha.

      But Linus Torvalds was in the right place at the right time, and he did have the bare-bones of a kernel that slotted into place with the FSF tools to make an OS (kinda stealing the glory from RMS and the FSF,) but even if he hadn't done so, and FSF's Hurd contributors had continued with their interminably slow and not-very-public (the irony) debug, someone else would have provided the kernel.

      --
      -- .sigs are a waste of data...turn them off...
    20. Re:yeah but guess who owns the future? by mav[LAG] · · Score: 1
      IBM hired lawyers because SCO's claims were mainly about contracts. It also calculated - very accurately as it turns out - that the SCO case was an ideal opportunity to create a legal precedent where the GPL could be shown to be ironclad.

      I agree with the GP; SCO has bumped its head against the GPL at every turn:
      • Original claim: misappropriation of trade secrets. Dropped after it was pointed out that SCO continued to distribute the code under the GPL.
      • Modified claim: copyright infringement. Thrown out.
      • Lawsuits against DC and Autozone went nowhere for the same reason.
      • SCO's claims that the GPL is unconstitutional: smacked down.


      --
      --- Hot Shot City is particularly good.
    21. Re:yeah but guess who owns the future? by Lorkki · · Score: 1
      As it happens, the GNU project does have a working kernel of their own, HURD. HURD never really took off, mainly because Linux got the snowball effect going - it got some users, some of whom began co-developing it, making it better, which in turn gained it more users and more developers and so on.

      As I understand it, at the time when Linux was released it was a working kernel, whereas HURD was more of a vague promise. You don't win users in a hacker culture by asking them to join you in formulating the ideal solution, you need to have something which (kind of) works and is good enough to be improved upon.

      You think that Linux - a single operating system kernel - is going to have more lasting influence than the whole free software movement, of which the Linux kernel is just a part of ?

      In the absence of Linux, perhaps BSD would've caught on and GNU gone the way of obscurity. Perhaps someone might've gone and implemented HURD's alleged original idea of adapting the BSD kernel as a base for the GNU system. Who knows, any number of things might have happened, but it's hardly appropriate to underestimate the part of Linux and its momentum in making GNU vastly more popular (in turn aiding the development of GNU tools, and so on).

    22. Re:yeah but guess who owns the future? by thsths · · Score: 1, Flamebait

      > The GNU project was trying to create a free version of Unix - the GNU system - and was going about it in a systematic fashion, one tool at the time.

      One tool at a time is by no means systematic. Doing it in the right order would be systematic. Except that the GNU project had an Image Manipulation Program and a desktop environment before the kernel would support 2GB of hard disk space. To me that does not look very systematic.

      > You think that Linux - a single operating system kernel - is going to have more lasting influence than the whole free software movement, of which the Linux kernel is just a part of ?

      Fortunately, GNU and FSF are not the whole free software movement. There is BSD, there is KDE, there is Mozilla, there is OpenOffice, and there are also countless smaller projects. Freedome is also about choice, but choice is something that RMS seems to reserve to himself.

    23. Re:yeah but guess who owns the future? by Rogerborg · · Score: 1

      PC centralism aside, commercial toolchains targetting the Linux kernel are enough for many embedded applications. Even on a GUI PC, it'd be far easier to replace the FSF layers than those above and below them.

      --
      If you were blocking sigs, you wouldn't have to read this.
    24. Re:yeah but guess who owns the future? by Rogerborg · · Score: 1

      Actually, it isn't.

      Well. Your turn.

      --
      If you were blocking sigs, you wouldn't have to read this.
    25. Re:yeah but guess who owns the future? by Rogerborg · · Score: 1

      Pish, tosh. Any license would have sufficed. The germane point is that SCO released and continue to release their "trade secrets / methods and concepts" to a public audience. True, they did that because of the GPL, but that's a priori.

      --
      If you were blocking sigs, you wouldn't have to read this.
    26. Re:yeah but guess who owns the future? by Anonymous Coward · · Score: 0

      "(He's probably confident in his manhood as well.)"

      A stupid, personal and irrelevant little dig unworthy of any of the personalities being discussed here.

    27. Re:yeah but guess who owns the future? by m874t232 · · Score: 1

      But...I dunno. Until Linux came along, these things seemed a bit on the fringe to me, except for Emacs, which predates the FSF anyway.

      GNU software was running on just about every UNIX workstation, was widely used with embedded systems, and was what made NeXTStep possible.

      What I'm saying is that I think the future belongs more to people like Linus -- that they will have more lasting influence

      The success of Linus is very much like the success of Gates: both succeeded by releasing inferior technology early and then patching it up. That's not just the future, it's always been that way. It's a great strategy to get rich and/or famous, it's just that your users pay the price.

      But I don't think Linus will have much lasting influence; the Linux kernel is already having serious problems with maintenance and release, and I think Linus is not capable of delivering the next generation kernel that we need. The irony is that any successor operating system to Linux will probably still be called "Linux" even though it will have no software by Linus in it.

    28. Re:yeah but guess who owns the future? by topham · · Score: 1


      how did the gnu make nextstep possible?

      The core of Next is mach/bsd; neither of which are gnu.

      The majority of unix tools are available as either bsd, or gnu variants.

    29. Re:yeah but guess who owns the future? by Anonymous Coward · · Score: 0

      Lots of words, no message. Seems like you have read some book, but never really been part of the movement. Thus your knowledge is lacking. No offense, but you're confused.

    30. Re:yeah but guess who owns the future? by anothy · · Score: 5, Insightful
      The GNU project was trying to create a free version of Unix - the GNU system - and was going about it in a systematic fashion, one tool at the time. The kernel was left until last, and Linux simply happened to come at the right moment, when most of the system was already up and running but the kernel wasn't.
      where's my "-1 Wrong" modifier? saying GNU was trying to create a free Unix is simply laughable. you know what it stands for, right? HURD was never intended to be unix, it was intended to be something else entirely. the GNU toolset was developed on Unix because that was the best development environment available, and happened to also be the most similar to GNU's vision for HURD. the fact that the GNU tools look vaguely unix-like (at best; --some-really-long-option, for example, is decidedly un-unixy) is almost more of a coincidence. they were explicitly not trying to create a free Unix.
      As it happens, the GNU project does have a working kernel of their own, HURD. HURD never really took off, mainly because Linux got the snowball effect going - it got some users, some of whom began co-developing it, making it better, which in turn gained it more users and more developers and so on. Linux has almost all the developers, so HURD has almost none.
      HURD never took off due to the lack of a clearly articulated vision, lack of leadership, and the fact that Linux filled most of the true goals of the contributors: "gimme something free i can use that mostly works". sure, Linux getting all the flash in the media and schools biases people towards working on that over other kernels, but HURD can't put all their failings on Linux's shoulders. the various BSD's - hell, even Plan 9 - manage to progress further and more quickly than HURD does, despite HURD being the pet project of GNU's nominal head.
      But thinking that Linux is the true success story and the GNU project just a less important side path is absurd. It's the GNU project that made Linux possible, not the other way around.
      really? can you document that? to me, it sounds like speculation. i disagree, and think it's the other way around: without a useful core, the tools would've remained just a curiosity. by contrast, by 1994 (at the latest; possibly as early as 1991), Linux could've just used the BSD user-land stuff (and, IMHO, we'd all have been better off). Linux didn't make GNU possible, that's true - but it made it relevant.
      You think that Linux - a single operating system kernel - is going to have more lasting influence than the whole free software movement, of which the Linux kernel is just a part of ?
      that's not what the parent said. he said the future belongs to people like Linus more than people like RMS. that's true. even within the GNU world there's these differences in outlook and the results become apparent.
      Especially when what allowed Linux to grow in the first place was the development model made possible by the GPL ?
      stop drinking GNU's cool-aid. what allowed Linux to grow initially was the open space for a free unix-like system on the most common cheap hardware. initially, the "development model" was Linus hacking on things. then it was a bunch of people hacking on things, and Linus putting the bits together. the development model was not new, and was not invented by GNU.
      --

      i speak for myself and those who like what i say.
    31. Re:yeah but guess who owns the future? by anothy · · Score: 3, Insightful
      Trying to build Free Software system without any GNU code is almost impossible.
      that's only true depending on how you define "Free Software". given that you're using the capital F and S, you seem to imply GNU's definition of "Free", as embodied in the GPL. in which case, sure, you can't build a system which is based on GNU's philosophy without a good chunk of GNU's code. but is that surprising? it's practically a tautology.

      not everybody cares about GNU's philosophy, and they certainly didn't invent the idea of open source or free (little-f) software. using the broader definition of "free software", you can do exactly what you're asking with BSDs with not too much work at all, and there's plenty of free (even OSI-approved) systems out there which contain no GPL code at all (see Plan 9 for an example). you have a very narrow view of the world is all.
      --

      i speak for myself and those who like what i say.
    32. Re:yeah but guess who owns the future? by Millenniumman · · Score: 1

      BSD is more popular than Linux. Mac OS X is based off of it, and I believe Microsoft uses some BSD code. Apple releases most of their modifications.

      You might not consider it a victory because those are proprietary operating systems, but they wrote good software which a lot of people found useful.

      The main BSDs aren't as popular as Linux because they don't have buzzword status and none are focused on an easy to use Desktop OS.

      In the FSF's ideal world, there is no proprietary software. In such a world, programmers wouldn't be able to make money (Some might, but good Desktop software shouldn't require enough support to pay for its development). My favorite software is mostly from very small software companies that wouldn't exist if they had to be open source.

      We'd only have a fraction of the software we have, and most of it would be for people who know Linux very well, not the novices that use 90% of computers.

      Proprietary software serves consumers, because it needs them to survive. OSS serves computer enthusiasts, because it needs them to survive.

      As for Microsoft not serving consumers as well as it could, that is only due to lack of competition.

      --
      Stupidity is like nuclear power, it can be used for good or evil. And you don't want to get any on you.
    33. Re:yeah but guess who owns the future? by Anonymous Coward · · Score: 1, Funny

      The GNU project was trying to create a free version of Unix - the GNU system - and was going about it in a systematic fashion, one tool at the time. The kernel was left until last, and Linux simply happened to come at the right moment, when most of the system was already up and running but the kernel wasn't.

      The Dodge Neon that's in my driveway is almost ready to start racing in Formula 1, I just need to get a bigger engine in it

    34. Re:yeah but guess who owns the future? by Anonymous Coward · · Score: 0

      "And I think this was the most damn part of his indictment of the FSF. That they're hate and fear based, and when you let hate and fear dictate your principals, you end up hurting yourself and those you want to help."

      If 'fear and hate' are the motivating forces behind the FSF it should be a trivial matter to support that contention. Cite away. I doubt you can since the argument you employ is a total canard. DRM isn't equivalent to Proprietary software, it's a subset, one in every aspect antethical to the FSF's principles from Day 1. You do know what the first 'F' in FSF stands for, right? Both senses?

      You're reasoning is as common as dirt these days and can be stated in an line: 'Principle doesn't matter, only utility.' For some it does.

    35. Re:yeah but guess who owns the future? by Aim+Here · · Score: 1

      You're wrong with the BSDs on two counts:

      A) Insofar as they're free software in the 'wider' sense, they're Free Software in the FSF sense. What bizarre definitions of 'Free Software' and 'free software' are you using that makes them different. 'Free Software' as defined by the FSF includes a wide swathe of licenses. Nearly as many as the OSI-definition, and more than the DFSG definition.
      Of course, FreeBSD supports some binary-only drivers (are those 'free software' in your sense?), but the FSF would likely endorse almost everything about OpenBSD. In fact, they gave Theo an award for services to Free Software not so long ago.

      B) Without GNU licensed code, BSD's are hugely crippled. For one reason: glibc. Not to mention they don't have gcc either, which is another big handicap. Delete your GNU licensed libraries from your favourite BSD and see how far you can go...

    36. Re:yeah but guess who owns the future? by mattyrobinson69 · · Score: 1

      Freebsd, apart* from the gnu compiler collection, of course.

      *also, I always install bash on freebsd, which is gnu, iirc.

    37. Re:yeah but guess who owns the future? by Infernal+Device · · Score: 1

      You think that Linux - a single operating system kernel - is going to have more lasting influence than the whole free software movement, of which the Linux kernel is just a part of ?

      When people speak of Linux, do they say GNU/Linux or just Linux?

      Yeah, I know - it's not really a competition ... except when it is. The FSF needs to work on gaining the mindshare that Linux has gotten. It's easy for Linux, people actually get something tangible - the FSF, not so much. The GPL presents a set of concepts, but I think we're moving to an age of goal-oriented people who are less concerned about the whys and wherefores.

      --
      "My God...it's full of trolls!"
    38. Re:yeah but guess who owns the future? by anothy · · Score: 1

      nope.

      A) You're confusing Open Source with Free Software, and probably also with "GPL-compatible". BSD licenses are not Free Software because they do not "preserve freedom" (sic) in the way GPL does. i think i agree that it's a stupid distinction, but the FSF has fought hard to promote a given definition of "Free Software", and as a trademark-like name, it's got different meaning from "free software", using the common english definitions of those words.
      besides, if you use the broader definition (which i'm certainly not going to try to talk you out of, since i think it's the better one), the point in the grandparent post is even less defensible. i was trying to be charitable.

      B) BSDs do not generally use glibc. there have been individual projects to do so, but they are not the default configuration (and the projects never get very far). gcc is used regularly, it's true, but it's not the only option. replacing that would probably require the most work, but only in the sense of finding the suitable replacement. i'm not sure which compilers have been used with which kernels, but there's plenty of other free compilers out there which will work. BSDs, unlike Linux, don't rely on the gcc "extensions" to C.
      also, even if that were true (it isn't), it still doesn't help the point i was replying to: there's plenty of other systems which are free (and Free, to the extent there's a difference) which incorporate 0 lines of GNU code.

      --

      i speak for myself and those who like what i say.
    39. Re:yeah but guess who owns the future? by TheRaven64 · · Score: 1
      Without GNU licensed code, BSD's are hugely crippled. For one reason: glibc

      None of the BSDs use glibc; they all have their own libc. Glibc, for example, does not contain strlcat, which originated in OpenBSD's libc.

      Anyone who considers BSDs (and I run Free and OpenBSD myself, not Linux) to be GNU free, however, would do well to look in the gnu directories of the source trees. After you've installed third party software (ports) you are almost certain to end up with a considerable amount of GNU code (gtk, for example).

      --
      I am TheRaven on Soylent News
    40. Re:yeah but guess who owns the future? by Overly+Critical+Guy · · Score: 1

      Well, I use BSD, so...thanks for the compiler, GNU.

      --
      "Sufferin' succotash."
    41. Re:yeah but guess who owns the future? by Overly+Critical+Guy · · Score: 1
      GNU software was running on just about every UNIX workstation, was widely used with embedded systems, and was what made NeXTStep possible.


      NeXTStep ran on Mach and used much BSD code.

      The success of Linus is very much like the success of Gates: both succeeded by releasing inferior technology early and then patching it up.


      At least Linus released something. HURD still isn't officially released and ready for production systems, and I suspect it never will be.
      --
      "Sufferin' succotash."
    42. Re:yeah but guess who owns the future? by awol · · Score: 1

      Whether Linus is more practical or not is irrelevant. There is a real risk that there is a fight coming. The fight I fear is the lining up of all the big media DRM fanboys on one side and those of us that want ot be free on the other. RMS may have killed an Archduke by trying to replace proprietary Unix with the GNU project and trying to unite all the users. Or perhaps Linus made the gun and the Archduke still lives, his death due soon when TC is the only way to buy new hardware and all the end users start to accelerate the death of big media. I am not suggesting that anyone is going to die, but there is a serious risk that much of what we do now (and take for granted) will become illegal. THAT is the problem. It is deeply ironic that countries like China, India and perhaps the South Americans and Africans may become the saviour of those of us in the West that belive in being free to manage our data as we see fit, by manufacturing "free hardware" for their own use. Which, in the most dystopian vision I have, becomes illegal to import into my country, or illegal to connect to the "pipes" of the Internets 3.X...

      FSF cares about this. I am ambivilant about whether Linus cares. He's done enough, none of us (well very few) are in any position to criticise. But the FSF cares about this and THAT matters, they have no real power but are vocal, have some cash, and are a bit like a hydra, so they are very tough to shut up. GPL v3 is them preparing the ground for the fight (on one front) there are other fronts (free hardware etc) but those are different discussions.

      As a final point, and at the risk of invoking Godwinson's Law, being exclusively pragmatic and moaning about the overkill of GPLv3 is a bit like being grateful that the trains are running on time while society is going to shit.

      --
      "The first thing to do when you find yourself in a hole is stop digging."
    43. Re:yeah but guess who owns the future? by UserGoogol · · Score: 1

      Actually, the FSF explicitly considers the BSD License to be a free software license.

      I believe the distinction is that a free software license is merely one which does not infringe on the freedoms they list here. Actively ensuring the freedoms of the end-user is the GPL's niche to be sure, (through tricks like copyleft) but they do not consider that stuff to be neccesary in order for software to be free.

      --
      "Never attribute to malice that which can be adequately explained by stupidity." -- Hanlon's Razor
    44. Re:yeah but guess who owns the future? by Aim+Here · · Score: 1

      I stand corrected on point 2 (I was misled by a visit to the OpenBSD site and not finding non-GNUed compilers or libraries.

      However, the FSF definition of 'Free Software' most definitely includes non-copyleft licenses, and on that score you're utterly dead wrong. Go to fsf.org and check up.

    45. Re:yeah but guess who owns the future? by Lord+Kano · · Score: 4, Insightful

      But thinking that Linux is the true success story and the GNU project just a less important side path is absurd. It's the GNU project that made Linux possible, not the other way around.

      GNU is what made Linux possible. Linux is what made GNU successful.

      They need each other. They're both necessary and important. Why quibble over which one is more necessary and important?

      LK

      --
      "Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano
    46. Re:yeah but guess who owns the future? by Nicolay77 · · Score: 1

      I do agree with you.

      The real resource is developers, not simply lines of code with a particular license. If the GCC project didn't existed then a BSDCC would have born and would have used probably the very same developers. Lines of code with any license but without developers are dead projects.

      But GCC was there first and got the momentum. However what makes it useful is the developer community attached to it. If there were a better and faster compiler (almost any other compiler is faster) with a BSD license, it would surely gain enough developers to stop this compiler dependency.

      However probably the only way to develop a fast and good C++ compiler fast enough is doing it in Lisp, and there seems to be too many purists both in lisp and in C++ camps.

      But lisp is just the right language to make compilers and other code-transformation tools.

      --
      We are Turing O-Machines. The Oracle is out there.
    47. Re:yeah but guess who owns the future? by Millenniumman · · Score: 1

      I suspect that HURD will be used by Windows Vista.

      --
      Stupidity is like nuclear power, it can be used for good or evil. And you don't want to get any on you.
    48. Re:yeah but guess who owns the future? by bensch128 · · Score: 1

      Chicken and the egg paradox?

    49. Re:yeah but guess who owns the future? by Millenniumman · · Score: 1

      GPL3 will have the same kind of power to defend free software from the corporations that want to kill it.

      The final battle, with a literal interpretation of the above statement:

      *RMS is overseeing the final moments of the Battle of Redmond, when Balmer appears*
      Balmer : Die you communist scum! *throws chair at RMS*
      RMS: Haha, I have the GPL *holds up a paper copy of the GPL*
      *the chair bounces off of the license, and goes back at Balmer*

      --
      Stupidity is like nuclear power, it can be used for good or evil. And you don't want to get any on you.
    50. Re:yeah but guess who owns the future? by larry+bagina · · Score: 1
      the only gnu-related piece of nextstep was gcc, modified to support objective c. IIRC, Steve Jobs & co didn't want to release their modifications on the grounds that it was only a front-end to gcc and thus exempt from the GPL. Stallman complained and eventually prevailed.

      Had they known the full implications, NeXT might have used a different compiler.

      --
      Do you even lift?

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

    51. Re:yeah but guess who owns the future? by topham · · Score: 1


      They did use a different compiler. They actually licensed the original Objective-C compiler. Without knowing the full details I expect they switch to gcc only because it supported more processors.

      As well, it is quite likely the only reason why they wanted to only give binary modules back was because of the prior licensing arrangement they had regarding Objective-C. I'm sure it took them a lot of effort internally to determine if they even could release the source code.

    52. Re:yeah but guess who owns the future? by killjoe · · Score: 1

      One quote from the german arm of MS does not establish a blanket policy. Sorry.

      --
      evil is as evil does
    53. Re:yeah but guess who owns the future? by Jah-Wren+Ryel · · Score: 1

      BSD is more popular than Linux. Mac OS X is based off of it,

      Depends on what you mean by "based" - OSX is Mach with a BSD personality.

      You might not consider it a victory because those are proprietary operating systems, but they wrote good software which a lot of people found useful.

      But how many programmers madke money from it? That seems to be your own metric, and Apple has already reduced the size of that group to some subset of its own OS developers.

      In the FSF's ideal world, there is no proprietary software. In such a world, programmers wouldn't be able to make money.

      FALSE. That you believe the only way to make money from software development is by selling support just means you haven't been paying attention.

      --
      When information is power, privacy is freedom.
    54. Re:yeah but guess who owns the future? by Anonymous Coward · · Score: 0

      and there you have just proven his point. There were other free kernels available...no one cared until linux came along.

    55. Re:yeah but guess who owns the future? by Millenniumman · · Score: 1

      OS X does use Mach in its kernel, but BSD is also very important.

      My metric is how many people find it useful. Making someone money is useful. Increasing someone's productivity is useful.

      How does a software developer make money if not by charging for software or support, and if he gives all his software and code away? There might be some market for customizing software for a business, but it isn't huge. And lets say this developer makes a normal application(rather than libraries), an RSS reader, web browser, text editor, etc.

      --
      Stupidity is like nuclear power, it can be used for good or evil. And you don't want to get any on you.
    56. Re:yeah but guess who owns the future? by Jah-Wren+Ryel · · Score: 1

      My metric is how many people find it useful. Making someone money is useful. Increasing someone's productivity is useful.

      Ok, so your metric changes to suit your point. I won't play that game.

      There might be some market for customizing software for a business, but it isn't huge.

      Bingo. But poor understanding of the market. Depending on the year and who does the measurement, more dollars are spent on in-house corporate customization than are spent on shrink-wrap. Think about that for a second - shrink-wrap employs a programmer once and his employer sells the results of his work over and over again. Customization employs a programmer for each dollar spent. Even if customization was just a tenth of the market dollars, it would still employ more people than the shrink-wrap biz.

      --
      When information is power, privacy is freedom.
    57. Re:yeah but guess who owns the future? by bfields · · Score: 1

      "given that you're using the capital F and S, you seem to imply GNU's definition of "Free", as embodied in the GPL. in which case, sure, you can't build a system which is based on GNU's philosophy without a good chunk of GNU's code. but is that surprising? it's practically a tautology." Uh, no, you're confused about the FSF's definition of "free". Go read their web pages sometime. Despite an obvious preference for the GPL, they most definitely consider BSD-licensed software to be free.

    58. Re:yeah but guess who owns the future? by bfields · · Score: 1

      "BSD licenses are not Free Software because they do not "preserve freedom" (sic) in the way GPL does. i think i agree that it's a stupid distinction, but the FSF has fought hard to promote a given definition of "Free Software""

      Who told you this???

      Here is the FSF's definition of "free software". There's no such "preserve freedom" clause.

      They also have a list of free software licenses free software licenses. Note that BSD is included. (It is non-copyleft, but free.)

      They certainly *do* prefer the GPL, in general (though not necessarily everywhere), but they definitely do not do that by claiming that non-GPL'd software is not free software.

    59. Re:yeah but guess who owns the future? by Vol_Firefighter · · Score: 1

      Wrong GNU operating system was going to be a unix-like operating system.

    60. Re:yeah but guess who owns the future? by AJWM · · Score: 1

      In this respect he is like Bill Gates, with people saying how if it hadn't been for Microsoft we'd still be using DOS.

      Alas, the truth of it is that it hadn't been for Microsoft, we'd probably have been using something Unix-like a lot sooner. (Although arguably Digital Research could have ended up doing the same thing that MSFT did. Both DR-DOS and MS-DOS (nee QDOS) were natural successors to the 8-bit CP/M.)

      The fact is that in the timeframe that IBM introduced the x86-based PC, there were many other platforms, from M68K-based (and other 16 and 32 bit chip) systems running real AT&T Unix derivatives, to high-end 8-bit 6809 systems running the Unix-like OS-9, and even a couple of Unix derivatives or workalikes for IBM's own PC. (Even Microsoft was in that game then, with Xenix.)

      --
      -- Alastair
    61. Re:yeah but guess who owns the future? by Anonymous Coward · · Score: 0

      "Linus who's done most to actually change the world." Linus' kernel contribution was tremendously important to the world of free software. However, the spirit of free development does not stem from him at all, and you completely ignore the choice to use the FSF licenses and man hours of thousands of developer teams which recide at Sourceforge, Freshmeat, Savannah and so on. I say Bravo, FSF, Bravo, Linus AND Bravo, all free software developers - I applaud you all!

    62. Re:yeah but guess who owns the future? by ClosedSource · · Score: 0

      I think you might be right if you'd said "if it hadn't been for IBM, we'd probably have been using something Unix-like a lot sooner." The 8088 (the term "X86" was coined much, much later) that IBM chose for the PC didn't have any privilege levels so it's not possible (even today) to run a stable and secure Unix OS on it. In addition because of the 8088's 64K memory segmentation, it's much more difficult to write a large program for it.

      That's not to say that you couldn't write a Unix-like OS for it, but the security and stablity of such an OS would be far less than Windows NT/2000/XP.

    63. Re:yeah but guess who owns the future? by Anonymous Coward · · Score: 0

      --they were explicitly not trying to create a free Unix.

      Erm --- the initial announcement goes:
      GNU will be able to run Unix programs, but will not be identical
      to Unix. We will make all improvements that are convenient, based
      on our experience with other operating systems.

      Sounds to me like they were trying to create a free Unix-compatible operating system (but better by drawing from past experience). So yes technically not a carbon-copy but a copmatible system.

      --Linux could've just used the BSD user-land stuff (...)
      Why didn't it, I wonder? If the decision was made on technical merit could it be that GNU had the best user-land stuff at the time?

      --the future belongs to people like Linus more than people like RMS.
      That statement makes no sense. What you possibly mean is that Linus has been a more succesfull software developer/project manager than RMS. True, RMS has always been hard to work with.

      --stop drinking GNU's cool-aid. what allowed Linux to grow initially was the open space for a free unix-like...
      Hahahaha! BSD had been around for longer and was more mature than "Linux" ... companies invested huge amounts of money on the Linux kernel exactly because it was under the GNU GPL which ensured a level playing field. Do you think IBM would have invested as heavily on the kernel if it knew that its investment could find their way (under say BSD terms) in the Windows operating system? If so, then I have some plots on the moon for sale if you are interested....

    64. Re:yeah but guess who owns the future? by Schraegstrichpunkt · · Score: 1
      BSD licenses are not Free Software because they do not "preserve freedom" (sic) in the way GPL does.

      Wrong. They're not "copyleft" licenses, but they are free software. RTFW.

      the FSF has fought hard to promote a given definition of "Free Software", and as a trademark-like name, it's got different meaning from "free software", using the common english definitions of those words.

      Wrong again. Go look at the FSF's website. None of their core philosophy documents capitalize "Free Software" the way you do, except when the it's followed by "Foundation".

      besides, if you use the broader definition (which i'm certainly not going to try to talk you out of, since i think it's the better one), the point in the grandparent post is even less defensible. i was trying to be charitable.

      Your opinion is overrated. Read the fscking document:/p>

      Free software is a matter of the users' freedom to run, copy, distribute, study, change and improve the software. More precisely, it refers to four kinds of freedom, for the users of the software:

      • The freedom to run the program, for any purpose (freedom 0).
      • The freedom to study how the program works, and adapt it to your needs (freedom 1). Access to the source code is a precondition for this.
      • The freedom to redistribute copies so you can help your neighbor (freedom 2).
      • The freedom to improve the program, and release your improvements to the public, so that the whole community benefits (freedom 3). Access to the source code is a precondition for this.

      A program is free software if users have all of these freedoms.

      It's not really that difficult to understand.

    65. Re:yeah but guess who owns the future? by Schraegstrichpunkt · · Score: 1
      In the FSF's ideal world, there is no proprietary software. In such a world, programmers wouldn't be able to make money

      You are an idiot. Not merely because you believe the above, but because you *still* believe the above, even though it's been so widely debunked that you should really know better by now.

      The vast majority of programmers make money writing custom software. Lots of it is free software. Lots of it isn't.

    66. Re:yeah but guess who owns the future? by Schraegstrichpunkt · · Score: 1
      I'll even start testing a buggy Hurd kernel if I have to.

      Minix 3 is more promising. It's BSD-licenced, but we could always create a GPLv3 work if we wanted to. (And to those of you who would complain about that, how is it any worse than creating a proprietary fork?)

      Actually, there's enough "GPL 2 or later" code in Linux that somebody could probably just start a GPLv3 fork of Linux. Heck, even lots of code Linus wrote (before he put his revisionist "clarification" into COPYING) is licensed under any version of the GPL as per section 9 of GPLv2.

    67. Re:yeah but guess who owns the future? by Schraegstrichpunkt · · Score: 1

      Bah. s/work/fork/

    68. Re:yeah but guess who owns the future? by Schraegstrichpunkt · · Score: 1

      The FSF is taking their sweet time with HURD, which includes doing one or two rewrites, because Linux exists. The FSF probably figures that there's no point in building a system that's technically inferior to Linux, since then nobody will bother adopting it anyway.

      If Linux didn't exist (and a legally-unencumbered BSD didn't either), the HURD would probably be usable by now.

    69. Re:yeah but guess who owns the future? by cswiger2005 · · Score: 1
      B) Without GNU licensed code, BSD's are hugely crippled. For one reason: glibc. Not to mention they don't have gcc either, which is another big handicap. Delete your GNU licensed libraries from your favourite BSD and see how far you can go...

      Oddly enough, FreeBSD, NetBSD, OpenBSD, Darwin/MacOS X, and so forth use their own libc which is not glibc. The GPL-licensed library which is most commonly used on the BSD platforms is probably libreadline.

      --
      "The human race's favorite method for being in control of the facts is to ignore them." -Celia Green
    70. Re:yeah but guess who owns the future? by anothy · · Score: 1
      sigh. okay, i guess in order:
      • the fact that they intended HURD to be able to run unix programs does not make it Unix; hell, it doesn't even make it unix-like. Plan 9 can run unix programs; with the right intermediaries, Windows can run unix programs. are either of these systems unix systems? of course not. it's about the system design, and GNU had something very different from Unix in mind for HURD.
      • i can't really speak directly to linus' motivations for using the GNU stuff instead of the BSD stuff, but i imagine the cloud cast by the AT&T lawsuit was a significant factor; it certainly was for others around the same time, including some of the big iron and commercial unix vendors. that hesitation cost BSD a lot of traction and gave linux and GNU a chance to catch up. but it's downright silly to claim that GNU's toolset in 1991 was as complete or as correct as BSD's at the same time.
      • the statement wasn't mine, i was just reacting to an intentional mis-characterization of an ancestor post. but regardless, it certainly does make sense (regardless of correctness): the claim is that people like Linus will have more of an impact on and more control over the future than people like RMS.
      • please read before responding to things. note, in particular, the "initially" in the text you've quoted. IBM and others didn't start investing in Linux for nearly a decade after the initial announcement; that doesn't qualify as "initially". so your speculation on IBM's decision making may well be correct (who's to say they just wouldn't create an internal fork?), but is totally irrelevant regardless.
      oh, and stop being an ass.
      --

      i speak for myself and those who like what i say.
    71. Re:yeah but guess who owns the future? by anothy · · Score: 1

      no, it wasn't. see your sibling for a slightly more detailed response, but basically they wanted it to be able to run unix programs (in some undefined way), but did not intend for it to be a unix system. i'm not sure "unix-like" is defined enough to be useful in discussion.

      --

      i speak for myself and those who like what i say.
    72. Re:yeah but guess who owns the future? by AJWM · · Score: 1

      The 8088 (the term "X86" was coined much, much later)

      Yes, the IBM PC was 8088, but that was just Intel's 8-bit bus version of its existant 8086 processor. Either way, IBM started the x86 line of PCs.

      didn't have any privilege levels so it's not possible (even today) to run a stable and secure Unix OS on it

      True but irrelevant. It's not possible to run any kind of stable and secure OS on it, but it is possible to run a system that's a Unix "lookalike" system in that it has the same user tools, shell, etc. Indeed, IBM itself sold PC/IX, a Unix clone for the PC.

      In addition because of the 8088's 64K memory segmentation, it's much more difficult to write a large program for it.

      True but also irrelevant. "More difficult" != "impossible", and Unix grew up on 16-bit processors with an inherent 64K address limitation. (I ran a Unix system for a couple of years on a PDP-11/20 with 128K RAM and 10MB disk.)

      That's not to say that you couldn't write a Unix-like OS for it, but the security and stablity of such an OS would be far less than Windows NT/2000/XP.

      I'd like to see you try to run any of Windows NT/200/XP on an 8088-based IBM PC!

      --
      -- Alastair
    73. Re:yeah but guess who owns the future? by m874t232 · · Score: 1

      At least Linus released something. HURD still isn't officially released and ready for production systems, and I suspect it never will be.

      You're right: it may never be. But that's not because Linus is better than the people working on the Hurd, it's because Linux has attracted all the third party contributions and very few people are left to contribute to the Hurd.

      Linus is a capable open source project leader and developer, but he is no better many other kernel developers; the reason he succeeded where others failed was that he had just the right product at just the right time and attracted all the contributions with his project.

      But, in the end, we'd probably be better off if the community had waited a year or two for the first release of the Hurd or the first free BSD release. Still, one shouldn't complain too much: unlike DOS, Linux has grown and matured fairly well.

    74. Re:yeah but guess who owns the future? by m874t232 · · Score: 1

      In addition to the obvious contribution to NeXTStep--gcc--GNU was also widely responsible for the fact that a UNIX-based workstation was a choice at all. If GNU hadn't paved the way and made a lot of improvements to the UNIX userland environment, UNIX workstations wouldn't have been as big a success as they were in the 80's.

    75. Re:yeah but guess who owns the future? by ClosedSource · · Score: 0

      "Yes, the IBM PC was 8088, but that was just Intel's 8-bit bus version of its existant 8086 processor. Either way, IBM started the x86 line of PCs."

      Yes, the 8088 was 8-bit bus version of the 8086, but no, it is not an X86 processor.

      "I'd like to see you try to run any of Windows NT/200/XP on an 8088-based IBM PC!"

      I don't know why you'd like me to try it since I already explained why it couldn't be done.

      The point of my post was that even if a Unix "lookalike" OS could be written for the 8088, it wouldn't have the key attributes that an OS like Linux has and the responsible party would be IBM, not MS. If your point was that if not for MS we would have been using an unstable and insecure Unix-like OS than I can see your point.

    76. Re:yeah but guess who owns the future? by civilizedINTENSITY · · Score: 1
      I use gcc, and I would like to use it even more, but it does not compile to common virtual machines (Perl, Parrot, Java or CIL).
      GCC, the GNU Compiler Collection
      The GNU Compiler Collection includes front ends for C, C++, Objective-C, Fortran, Java, and Ada, as well as libraries for these languages (libstdc++, libgcj,...).
      The GNU Compiler for the JavaTM Programming Language
      GCJ is a portable, optimizing, ahead-of-time compiler for the Java Programming Language. It can compile Java source code to Java bytecode (class files) or directly to native machine code, and Java bytecode to native machine code.
  10. Re:The GPL needs to go by Anonymous Coward · · Score: 0

    From one Anonymous Coward to another, your post is total and complete troll bullshit. There is no requirement in the GPL that forces anyone to publish changes that were made for internal use, as in by a corporation for internal applications. Only if the software is to be redistributed, are changes required to be published. It is really the best deal in the history of software.

    jwwjr

  11. Translation of Torvalds' attack by njdj · · Score: 1, Interesting

    Torvalds complained that the FSF didn't listen to people's comments.

    What he really meant was, "The FSF listened to everybody's comments, instead of just doing what I told them to do."

    The experience of being a benevolent dictator in one area has given him the idea that he should be a benevolent dictator in other areas.

    1. Re:Translation of Torvalds' attack by dbIII · · Score: 1
      What he really meant was, "The FSF listened to everybody's comments, instead of just doing what I told them to do."
      I think you have it backwards - remember who it is that insists on a name change another persons project to "advertise" the gnu project and bring attention to the FSF.

      It is up to the FSF to convice others that changing to a different licence is a good thing - instead of some overbearing person insisting that people have to change because they said so. If I was Linus my polite response would be to tell me when it's finished and I'll tell you if I like it enough to change licences. There is still some way to go.

    2. Re:Translation of Torvalds' attack by Anonymous Coward · · Score: 0

      Wow, such a skewed interpretation is marked "insightful." Only on Slashdot...

    3. Re:Translation of Torvalds' attack by init100 · · Score: 2, Informative

      remember who it is that insists on a name change another persons project to "advertise" the gnu project

      Are you referring to the term GNU/Linux? In this case, you are wrong. Stallman does not insist on Linus to change the name of Linux, he just insists on using the term GNU/Linux when referring to a working (GNU/)Linux system, which contains a lot more than the Linux kernel. I understand his argument, and in principle I agree, but using the term GNU/Linux in practice is unduly complex.

    4. Re:Translation of Torvalds' attack by AuMatar · · Score: 1

      Except noone is asking Linus to change the kernel license- it would be pretty much impossible, since copyright belongs to the individual contributors. You'd have to convince thousands of individual devs, some of whom are dead, to agree to it. The FSF has never asked Linus to change license, this is Linux blasting it on his own. Which wouldn't be a bad thing if they were throught out criticisms, but his criticisms have no basis in reality. Many of them are just flat out wrong- the license doesn't require what he says it does.

      --
      I still have more fans than freaks. WTF is wrong with you people?
    5. Re:Translation of Torvalds' attack by dbIII · · Score: 1
      Are you referring to the term GNU/Linux? In this case, you are wrong
      Go talk to someone who was reading the linux news groups back when RMS suggested the LiGnuX name - he was very open about it being to promote gnu and he repeated the same thing when he came back with the prefix idea sometime later. It has created confusion and very large numbers of people now believe that the views of RMS should be considered with the linux project over and above many of the leading contributors - they think it is a gnu project!
    6. Re:Translation of Torvalds' attack by TheRaven64 · · Score: 1
      remember who it is that insists on a name change another persons project to "advertise" the gnu project and bring attention to the FSF

      No, actually. I do remember a lot of people trying to rename the work of the GNU project, the XFree86 team, and many others as 'Linux,' however, even though Linux is a tiny portion of the system. Before you try FSF bashing again try this experiment:

      Try creating a free software desktop, server, or other system, without using any GNU software. Then try the same thing without Linux. You will find the second task a whole lot easier than the first; you can even run Debian without Linux, and I very much doubt 99% of 'Linux' users would be able to tell the difference.

      --
      I am TheRaven on Soylent News
    7. Re:Translation of Torvalds' attack by init100 · · Score: 1

      back when RMS suggested the LiGnuX name

      Do you mean that he actually requested a name change for the kernel? I would understand the suggestion "LiGnuX" for the entire system, just like GNU/Linux, but IMAO he had no business requesting a name change for the kernel.

    8. Re:Translation of Torvalds' attack by dbIII · · Score: 1
      No, actually. I do remember a lot of people trying to rename the work of the GNU project, the XFree86 team, and many others as 'Linux,'
      Those people are obviously entirely ignorant of what is on their disk and may even be the sort of people that call the entire machine in its case a "hard disk" or "CPU". There are other people who call the entire software distribution things like "slackware", "ubuntu" or whatever - but no-one who really has a clue is going to call gcc, emacs or whatever "linux". This whole stupid attitude of "we are doing it to them but we'll say they are doing it to us" must be filtering down from war propaganda or something - so please, calm down, pay attention and adjust your attitude with information from more than one source.
  12. Article is one-sided by vdboor · · Score: 2, Insightful

    I've read TFA, but noticed most arguments against Linus' option are made by members of the Open Source / Free Software communities. It would be more interesting to hear the feedback from commercial party's who're involved with Linux as well (e.g. Novell, HP, Oracle, Trolltech). This doesn't exactly put any weight under the arguments of the article.

    I believe Linus is more open towards commercial development then most FLOSS community members are. This makes it understandable why he is so against enforcing freedom through everyones throats. Linus has always been the more practical type.

    --
    The best way to accelerate a windows server is by 9.81 m/s2 ;-)
    1. Re:Article is one-sided by DrJimbo · · Score: 4, Insightful
      vdboor said:
      I believe Linus is more open towards commercial development then most FLOSS community members are. This makes it understandable why he is so against enforcing freedom through everyones throats. Linus has always been the more practical type.
      I've heard over and over again that Linus is taking the practical and/or pragmatic side of this debate. Poppycock! He is not being practical, he is being very short sighted in a way that could come back and bite all of us in the hat someday.

      The DRM provisions in the GPLv3 that Linus is complaining about are there to help ensure that FOSS developers like Linus will not be locked out from developing software on future generations of computers.

      Furthermore, if we are locked out from developing FOSS on those computers, we can take some comfort in the fact that it will be illegal to run GPLv3 code on them.

      --
      We don't see the world as it is, we see it as we are.
      -- Anais Nin
    2. Re:Article is one-sided by Ohreally_factor · · Score: 2, Interesting

      This is the second time you've proposed that without the GPLv3, OSS developers will be locked out from developing a whole generations of computers. Could you please explain this scenario for me? Is there going to be a conspiracy of hardware makers that are going to lock out OSS development?

      --
      It's not offtopic, dumbass. It's orthogonal.
    3. Re:Article is one-sided by Anonymous Coward · · Score: 0
      This is the second time you've proposed that without the GPLv3, OSS developers will be locked out from developing a whole generations of computers. Could you please explain this scenario for me?

      Why? It's not going to happen, GPLv3 will prevent it.
    4. Re:Article is one-sided by jimicus · · Score: 2, Informative

      Doesn't need to be.

      All Trusted Computing provides is a means to verify remotely what software is running on a given system. Cisco have already developed routers which can be set up to only route traffic from something running "approved" software.

          http://www.sfgate.com/cgi-bin/article.cgi?file=/ch ronicle/archive/2003/11/19/BUGP6351V31.DTL

      If they only way for your software to be "approved" is that it's the version your vendor shipped & signed, then it matters not whether or not you can modify what they shipped and install it yourself - as soon as you do that, the router will drop any packets from your PC and internet access will stop working.

      Maybe that's an extreme example - I can't see many ISPs cutting off most of their customers overnight. But I can see banks requiring a "trusted" setup for online banking, government departments requiring a "trusted" setup for interaction (and if the UK is anything to go by, the online systems will sooner or later replace the existing ones so you can't just post them your tax forms). Add this all up and if you think running Linux on a desktop can be awkward and painful now, imagine what it would be like in that vision of the future.

    5. Re:Article is one-sided by g2devi · · Score: 2, Insightful

      > He is not being practical, he is being very short sighted in a way that could come back and bite all of us in the hat someday.

      While I agree that it is short sighted, I think it's short sighted for different reasons.

      I don't think that GPL3 proponents in the Linux development community have any problem with the Linux kernel being licensed under GPL 2. The problem is that it's GPL 2 only, so it can never be changed in the future by future maintainers of Linux without a complete rewrite. If there's a serious problem with the GPL 2 or the rest of the world moves to GPL 3 and the Linux kernel can no longer share code with the rest of the world, Linux is SOL. Like it or not, Linux is now bigger than Linus.

      There is a simple solution that would immediately silence the debate. If individual files in the Linux kernel could be tagged as "GPL 2 or later" and have that license maintained (the same way the license of BSD files in the kernel are maintained), the Linux kernel would be GPL2, however, it would be possible to gradually move Linux completely to the "GPL 2 or later" as various portions of the Linux kernel get rewritten. People who currently want their modules to remain "GPL 2 only" could do so. People who wanted their modules to be "GPL 2 or later" could do so.

      If after 10 years, Linux is still 99% "GPL 2 only", the issue is pretty much dead. Developers want the GPL 2 only license and Linus is currently just defending the obvious. If however, 99% of the kernel is "GPL 2 or later" then Linus's current decision to have the kernel be "GPL2 only" is not with the Linux community.

      In either case, the conflict is artificial.

    6. Re:Article is one-sided by Kobayashi+Maru · · Score: 2, Informative

      This is the second time you've proposed that without the GPLv3, OSS developers will be locked out from developing a whole generations of computers. Could you please explain this scenario for me? Is there going to be a conspiracy of hardware makers that are going to lock out OSS development?


      I imagine it means we could find ourselves in a situation where the Playstation 4 or XBOX 3 actually runs Linux. But while the code is "open," licensed under the GPLv2, all the cryptographic nonsense and DRM closes it back down again. Granted we'll have the source to look for attack vectors, but until a weakness is found, we'll still have to go to Microsoft or Sony for a "developer license." Which really just means paying large sums of money so they will use their private keys to generate a "valid" crypotgraphic signature for your binary.

      Now because these are game systems, they'll attract the attention of the best hackers in the world. Having the source code, even GPLv2, would be a tremendous boost to the modding scene. Imagine instead that this is your toaster, or your Buick, or your no-name cell phone -- something only you and a small number of other people are interested in. Because the source is available under the GPLv2, you can find the exact line that is creating the bug you want to fix, but because none of you know how to hack the encryption checking, you're powerless to do anything about it.

      This is, I think, what the GPLv3 is trying to prevent.
    7. Re:Article is one-sided by maxume · · Score: 1

      Unfortunately(or something), gpl3 can't prevent Sony from using the mountain of existing gpl2 code in such a way.

      So really, all gpl3 does is offer developers that are in it for the idiology a place to put new work.

      --
      Nerd rage is the funniest rage.
    8. Re:Article is one-sided by labratuk · · Score: 1

      I think you've got to take your ideas a step further and imagine that the Playstation 4 or XBOX 3 not only run linux, but become very popular as general purpose communications & media devices, usurping the role of the general purpose PC. They run word processors, email, IM, DRM video on demand, DRM music managers, simple video editors, simple photo managers. They're cheap to mass produce. Eventually general purpose PCs dramatically rise in price due to smaller market of people who have need of them.

      So anybody who wants to be remotely technical is stuck with paying high prices for machines which can run their software when they have a perfectly good cheap powerful machine in the living room, only it's crippled to only run 'trusted' software.

      --
      Malike Bamiyi wanted my assistance.
    9. Re:Article is one-sided by LocalH · · Score: 1
      In my opinion, the GPLv3 goes too far, into a realm where the software developers shouldn't have any rights whatsoever. Here's what Linus said and I agree 100%:

      I literally feel that we do not--as software developers--have the moral right to enforce our rules on hardware manufacturers. We are not crusaders, trying to force people to bow to our superior God. We are trying to show others that cooperation and openness works better.


      And:

      Side note: the reason GPLv2 is so successful at fighting the root problem of using copyright to fight restrictive copyrights is that it makes "interesting material" available under a license that forbids further restricting it.

              I would suggest that anybody who wants to fight DRM practices seriously look at the equivalent angle. If you create interesting content, you can forbid that content ever be encrypted or limited.

              In other words, I personally think that the anti-DRM clause is much more sensible in the context of the Creative Commons licenses, than it is in software licenses. If you create valuable and useful content that other people want to be able to use (catchy tunes, funny animation, good icons), I would suggest you protect that content by saying that it cannot be used in any content-protection schemes.

              Afaik, all the Creative Commons licenses already require that you can't use technological measures to restrict the rights you give with the CC licenses. The "Share Alike" license in particular requires all work based on it also to be shared alike--that is, it has the "GPL feel" to it.

              If enough interesting content is licensed that way, DRM eventually becomes marginalized. Yes, it takes decades, but that's really no different at all from how the GPL works. The GPL has taken decades, and it hasn't "marginalized" commercial proprietary software yet, but it's gotten to the point where fewer people at least worry about it.

              As long as you expect Disney to feed your brain and just sit there on your couch, Disney & Co. will always be able to control the content you see. DRM is the smallest part of it--the crap we see and hear every day (regardless of any protection) is a much bigger issue.

              The GPL already requires source code (that is, non-protected content). So the GPL already does have an anti-DRM clause as far as the software is concerned. If you want to fight DRM on non-software fronts, you need to create non-software content, and fight it there.

              I realize that programmers are bad at content creation. So many programmers feel that they can't fight DRM that way. Tough. Spread the word instead. Don't try to fight DRM the wrong way.
      --
      FC Closer
    10. Re:Article is one-sided by DrJimbo · · Score: 1
      LocalH said:
      In my opinion, the GPLv3 goes too far, into a realm where the software developers shouldn't have any rights whatsoever. Here's what Linus said and I agree 100%:
      I literally feel that we do not--as software developers--have the moral right to enforce our rules on hardware manufacturers. We are not crusaders, trying to force people to bow to our superior God. We are trying to show others that cooperation and openness works better.
      And:
      Side note: the reason GPLv2 is so successful at fighting the root problem of using copyright to fight restrictive copyrights is that it makes "interesting material" available under a license that forbids further restricting it.
      Linus misunderstands the DRM clauses in the latest version of the GPLv3. By quoting him like this you are merely propagating that misunderstanding without adding anything new to the discussion.

      The whole point of the (now clarified) DRM clauses in the GPLv3 was not to:
      enforce our rules on hardware manufacturers
      as Linus claims (and you echo) it was instead to do exactly what Linus wants:
      to makes "interesting material" available under a license that forbids further restricting it.
      Encryption/decryption technology can be and is being used to restrict access to GPLv2 code. Depending on which side of the debate you are on this is called either "trusted" or "treacherous" computing. The technology now exists for "DRM" to be applied to all of the code that runs on a computer. The manufacturers have it in their power to make the next generation of computers such that they have total control over what software we are allowed to run on our own computers. If you change even one bit, the software will no longer run.

      That is one hell of a restriction. In fact, if it ever happens that the leading generation of computers all have treacherous computing installed then Linus and every other FOSS developer will be out of business (on those machines) because they won't run modified software. User based development will become impossible.

      This fight isn't about Tivos and dvd players as much as it is about preserving our right and ability to continue to develop FOSS on our own computers.

      Preventing the people that wrote the software from performing any future modifications (on the latest generation of computers) is one HELL of a restriction. I've got no problem with telling manufacturers that they can't do that with my software.

      --
      We don't see the world as it is, we see it as we are.
      -- Anais Nin
    11. Re:Article is one-sided by DrJimbo · · Score: 1
      Just do a simple Google(treacherous computing). The first result is an essay RMS wrote about five years ago called: Can you trust your computer?. In this essay RMS describes the scenario very clearly. He says:
      There are proposals already for US laws that would require all computers to support treacherous computing, and to prohibit connecting old computers to the Internet. The CBDTPA (we call it the Consume But Don't Try Programming Act) is one of them. But even if they don't legally force you to switch to treacherous computing, the pressure to accept it may be enormous. Today people often use Word format for communication, although this causes several sorts of problems (see "We Can Put an End to Word Attachments"). If only a treacherous computing machine can read the latest Word documents, many people will switch to it, if they view the situation only in terms of individual action (take it or leave it). To oppose treacherous computing, we must join together and confront the situation as a collective choice.
      The main question in the discussion here seems to be fueled by varying estimates of the amount of market penetration treacherous computing will be able to obtain. If treacherous computing gets 100% market penetration then FOSS is totally locked out from future development (on the latest hardware). So what level of penetration is acceptable to you? 1%? 10%? 50%? 90%?

      There are plenty of corporations that see it is in their own best interest to have 100% infiltration of treacherous computing. But treacherous computing works very much against the best interests of the FOSS community and even users in general. The eventual penetration of treacherous computing will be determined by the balance of forces for it and against it. The longer we wait to fight treacherous computing the deeper its final market penetration will become. If we are never able to band together to fight it then the forces that want treacherous computing will eventually win, market penetration will near 100%, and FOSS will die.

      --
      We don't see the world as it is, we see it as we are.
      -- Anais Nin
    12. Re:Article is one-sided by pnambic · · Score: 1

      > The DRM provisions in the GPLv3 that Linus is complaining about are there to help ensure that FOSS developers like Linus will not be locked out from developing software on future generations of computers.

      How exactly, by which mechanism, does licensing software under the GPLv3 prevent crippled machines taking over the market to the point where it's prohibitively expensive to buy a non-crippled computer? Note that I don't believe that that will happen, but if it were to happen, how would the GPLv3 save us (apart from prohibiting users to run their software on their machines, just like Tivo is doing right now)?

      I honestly don't get it. Are we expecting Microsoft to switch to GPLv3 any time soon?

    13. Re:Article is one-sided by init100 · · Score: 1

      How exactly, by which mechanism, does licensing software under the GPLv3 prevent crippled machines taking over the market to the point where it's prohibitively expensive to buy a non-crippled computer?

      It won't. However, at least the GPLv3 would prevent the vendors of such crippled machines using the software we wrote against us. They can write their own software, but they would not be able to build upon the mountain of (GPLv3-licensed) free code to further this goal.

  13. GNU project non-existent? by Anonymous Coward · · Score: 4, Insightful

    Wow, the GNU utilities you use every day, the compiler, and many other things the GNU project started were completely ignored in your post.

    1. Re:GNU project non-existent? by wenzi · · Score: 1

      We use a lot of utilities. They were not all written by Stallman, and not GNU by the way.

      We use Cron, written by Paul Vixie, everyday also.

      What is your point ?

      --
      -- I doubt, therefore I might be.
    2. Re:GNU project non-existent? by Anonymous Coward · · Score: 3, Informative

      Nowhere did I say "all" utilities. The "GNU utilities" refers to things such as the entire coreutils package.

      My point doesn't need all utilities to be written by the FSF, of course. The parent merely implied that the FSF didn't do *any* coding toward his software freedom in ignorance. My pointing of *some* contradicts a statement that there were none at all.

      If you missed these connections, I apologize and stress that I will point out the doubly (and more) obvious in future posts. I should have known better than to point out the singly obvious when there are so many ways to miss the obvious!

    3. Re:GNU project non-existent? by Richard_at_work · · Score: 3, Insightful

      I can replace all the GNU utilities in a Linux system with functionally similair tools from other projects - however, the GNU kernel is practically unusable. Its simply a matter of convenience that the GNU tools are used, but I guess that should be acknowledged as well.

    4. Re:GNU project non-existent? by Anonymous Coward · · Score: 0
      I can replace all the GNU utilities in a Linux system with functionally similair tools from other projects - however, the GNU kernel is practically unusable. Its simply a matter of convenience that the GNU tools are used, but I guess that should be acknowledged as well.

      I wouldn't recommend HURD but you can certainly use other kernels than Linux, both with and without the GNU tools. So its just a matter of "convenience" that Linux is used, but I guess that should be acknowledged.

    5. Re:GNU project non-existent? by Mprx · · Score: 1

      The GNU kernel is practically unusable because there is no longer any strong incentive to improve it. We already have a good Free kernel, there's no great need for another. If Linux was never started then the HURD would certainly be much better by now.

    6. Re:GNU project non-existent? by Ohreally_factor · · Score: 2, Insightful
      If Linux was never started then the HURD would certainly be much better by now.

      The Dead Body That Claims It Isn't: I'm not dead.
      The Dead Collector: 'Ere, he says he's not dead.
      Large Man with Dead Body: Yes he is.
      The Dead Body That Claims It Isn't: I'm not.
      The Dead Collector: He isn't.
      Large Man with Dead Body: Well, he will be soon, he's very ill.
      The Dead Body That Claims It Isn't: I'm getting better.
      --
      It's not offtopic, dumbass. It's orthogonal.
    7. Re:GNU project non-existent? by Scarblac · · Score: 3, Insightful

      Show it. Show us a completely usable system, running a Linux kernel and no GNU stuff. I don't think it can be done.

      On the other hand, Debian with a BSD kernel and Debian with a Hurd kernel are both available.

      --
      I believe posters are recognized by their sig. So I made one.
    8. Re:GNU project non-existent? by Anonymous Coward · · Score: 1, Insightful

      No, you can't. There is no "functionally similar tool" to GCC which is Free Software, other than GCC itself.

    9. Re:GNU project non-existent? by tgcid · · Score: 2, Informative

      Afaik, the BSDs largely have their own set of utilies, so it should be possible to run the Linux kernel + BSD programs. The greatest (and hardest to replace) contribution of the GNU programs is GCC. Currently, Theo da Raadt (of OpenBSD) has proposed writing a faster (in compile-time not run-time), more secure/strict compiler.

    10. Re:GNU project non-existent? by Anonymous Coward · · Score: 0

      LOL

    11. Re:GNU project non-existent? by labratuk · · Score: 2, Insightful

      Good luck replacing gcc. Even the BSDs use gcc.

      And no, icc cannot reliably compile a runnable kernel.

      --
      Malike Bamiyi wanted my assistance.
    12. Re:GNU project non-existent? by gmack · · Score: 1

      If Linux was never started then the HURD would certainly be much better by now.

      Actually the HURD kernel has been "almost done" since before the Linux kernel was even started so it's failure has nothing at all to do with having to compete for resources with the Linux kernel.

    13. Re:GNU project non-existent? by Overly+Critical+Guy · · Score: 1

      If you're a BSD user, there are only things like the gcc compiler, which can be replaced. GNU utilities are used as a matter of convenience.

      --
      "Sufferin' succotash."
    14. Re:GNU project non-existent? by Overly+Critical+Guy · · Score: 1

      The BSDs use their own utilities. They often use gcc, but that can be replaced. You could bring over BSD utilities or other alternatives and use that with a Linux kernel.

      This mythical idea that the GNU utilities are the irreplaceable bedrock of all UNIXes needs to go away.

      --
      "Sufferin' succotash."
    15. Re:GNU project non-existent? by Overly+Critical+Guy · · Score: 1

      If the only GNU utility being used is a compiler (and, yes, there are alternatives), I think the point has been proven.

      --
      "Sufferin' succotash."
    16. Re:GNU project non-existent? by mrchaotica · · Score: 1

      First of all, the problems with HURD most likely stem from the fact that the FSF requires copyright assignment for code contributions while Linus allows contributors to keep their copyright.

      Ironically, however, this has led directly to the current problems with the Linux kernel wrt. GPL v.3, which creates a new "strong incentive" to improve HURD (since, obviously, it's going to go GPL v.3-only as soon as the license is done).

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    17. Re:GNU project non-existent? by pjrc · · Score: 1
      I can replace all the GNU utilities in a Linux system with functionally similair tools from other projects

      Ok, now try to compile them from source!!

    18. Re:GNU project non-existent? by compass46 · · Score: 1

      "Currently, Theo da Raadt (of OpenBSD) has proposed writing a faster (in compile-time not run-time), more secure/strict compiler."

      This idea recently came up on one of the OpenBSD lists and was shot down by some of the OBSD developers.

    19. Re:GNU project non-existent? by a.d.trick · · Score: 1

      Ever though of the GCC? Sure there are other C compilers, but none as widely used and supported on various architectures as that one. Also what about Emacs? I've never really used the beast myself but I know there are many geeks who would weep and wail if that disappeared.

    20. Re:GNU project non-existent? by the+Atomic+Rabbit · · Score: 1
      They often use gcc, but that can be replaced.

      By what? (*rolls eyes*)

    21. Re:GNU project non-existent? by larry+bagina · · Score: 1

      proprietary closed source compilers (intel, sun, irix, etc). The linux kernel can "sort of" be compiled with icc (but only since they added support for some non-standard gcc extensions). The linux kernel depends on non-standard gcc extensions, and for the longest time, even depended on specific versions of gcc. The *BSD kernels will compile (and run!) with multiple compilers.

      --
      Do you even lift?

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

    22. Re:GNU project non-existent? by Anonymous Coward · · Score: 0

      Ironically, however, this has led directly to the current problems with the Linux kernel wrt. GPL v.3

      What problem would that be? If you are refering to the inability to change the licence, then it isn't really a problem since it is what Linus intended when he made it specifically GPL v2 only instead of GPL v2 or later.

    23. Re:GNU project non-existent? by WilliamSChips · · Score: 1

      Because they're quite good.

      --
      Please, for the good of Humanity, vote Obama.
    24. Re:GNU project non-existent? by AJWM · · Score: 1

      Hear hear. While I love the GNU utilities (mostly), the basic set -- especially going back a few years -- amounts to what any C programmer with some knowledge of Unix data structures could crank out in short order. Even before "The GNU Manifesto", Kernighan & Plauger's "Software Tools" (1976) showed how to build up a small suite of Unix-like utilities for almost any reasonable OS, and the Berkeley stuff started coming out not long after that.

      Yes, there are some GNU tools that are rather harder to duplicate (the already mentioned GCC, stuff like lex and yacc (er, flex and bison), etc), but the coreutils have been independently reimplemented many times, and even "Software Tools" covered the rudiments of writing compilers and parser generators.

      --
      -- Alastair
    25. Re:GNU project non-existent? by unix_core · · Score: 4, Funny
      "Theo da Raadt (of OpenBSD) has proposed writing a faster (in compile-time not run-time), more secure/strict compiler."

      Well, I've proposed releasing Windows Vista under the GPL.

    26. Re:GNU project non-existent? by mrchaotica · · Score: 1

      You're absolutely right. Sorry, let me rephrase that to "the current problems I, and others like me, percieve exist."

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    27. Re:GNU project non-existent? by ClosedSource · · Score: 1

      "the GNU utilities you use every day"

      Aren't you making a big assumption here? Plenty of developers have never used the GNU utilities and never will.

    28. Re:GNU project non-existent? by bcmm · · Score: 1

      Gentoo offers both Linux and BSD kernels, and both GNU and BSD utilities (i.e. cd, rm, ls, etc.). Last time I checked, not all combinations are supposed to work yet, but the devs are aiming for such support eventually. There have been options like using BSD's telnet for a while, but a couple of months ago they introduced a package to replace the GNU userland with FreeBSD stuff. Presumably, the GNU compiler toolchain (which is a seperate package from the utilities) will still be required.

      So, pretty soon Gentoo will support BSD utilities on a Linux kernel, not as a manually configured hack, but as an install option for the OS.

      --
      # cat /dev/mem | strings | grep -i llama
      Damn, my RAM is full of llamas.
    29. Re:GNU project non-existent? by cswiger2005 · · Score: 1

      Generally by a platform-specific compiler, such as Intel's icc, Sun's SPARC-specific acc, and so forth. It's worth noting that the BSD's make an effort to support using other compilers because it improves the portability of the code and may generate different warnings.

      Going further back in time, BSD 4.3-reno came with the PCC compiler...

      --
      "The human race's favorite method for being in control of the facts is to ignore them." -Celia Green
    30. Re:GNU project non-existent? by cswiger2005 · · Score: 1

      You're wrong, see PCC:

      http://en.wikipedia.org/wiki/Portable_C_Compiler ...which apparently is under a BSD license.

      --
      "The human race's favorite method for being in control of the facts is to ignore them." -Celia Green
    31. Re:GNU project non-existent? by cswiger2005 · · Score: 1

      > And no, icc cannot reliably compile a runnable kernel.

      Actually, people got icc to build the FreeBSD kernel back in 2003, albeit with some known issues back then which have since been resolved, from what I've heard on the mailing lists. See http://kerneltrap.org/node/974:

      Compile FreeBSD with Intels C compiler (icc)

      URL: http://www.leidinger.net/FreeBSD/

      Contact: Alexander Leidinger [email blocked]

      Since I ported icc to FreeBSD I wanted to build FreeBSD with icc. Now
      with icc 7.1 (and some patches) it is possible. There are still some
      bugs, e.g. NFS doesn't work with an icc compiled kernel, IP seems to
      be fragile, and some advanced optimizations trigger an ICE (Intel is
      working on it). At the moment I'm waiting for our admins to install
      icc on the FreeBSD cluster (we got a commercial license from Intel, so
      we are allowed to distribute binaries which are compiled with icc),
      after that I will try to convince some people with more knowledge of
      the IP and NFS parts of the kernel to debug the remaining problems.
      When the icc compiled kernel seems to work mostly bugfree the userland
      will get the porting focus. Interested people may try to do a build of
      the ports tree with icc independently from the status of the porting
      of the userland... if this happens at the FreeBSD cluster, we would
      also be allowed to distribute the binaries.

      Benefits include: another set of compiler errors (debugging help),
      more portable source, and code which is better optimized for a P4 (gcc
      has some drawbacks in this area)

      --
      "The human race's favorite method for being in control of the facts is to ignore them." -Celia Green
    32. Re:GNU project non-existent? by labratuk · · Score: 1

      Ok, that's great, but I was really implying a linux kernel, seeing as the parent was talking about building a linux system without GNU.

      --
      Malike Bamiyi wanted my assistance.
    33. Re:GNU project non-existent? by cswiger2005 · · Score: 1

      It's not exactly news that the Linux kernel contains GCC-specific idioms.
      Do you regard this as a feature or evidence of poor portability?

      Besides, if you want to talk about Linux as an entire OS, others have pointed out that Gentoo is actively working to integrate installing either a Linux kernel with a more BSD-derived userland, or installing a FreeBSD kernel with a Linux/glibc userland. In which case, the ability to compile a working kernel using icc or other compilers is entirely relevant to "Linux as OS".

      --
      "The human race's favorite method for being in control of the facts is to ignore them." -Celia Green
  14. Re:Sure to happen by Lehk228 · · Score: 1

    a well implemented DRM/TC system will not require code signing or other forms of verified binaries, rather blocks of memory will be restricted in what code can do with them, to work with a protected set of data you would create a thread that would handle that data and only certain actions could be taken. to allow backups of data the data or any derivitive of it could be exported in an encrypted block back to "normal" space and depending on rules encoded in the original data it could be openable by a limited (or unlimited) set of other devices and classes of devices.

    an audio stream could be exported to encrpted compressed audo for loading on any one of many portable audio players with a TC chip.

    programming around these rules would take some getting used to but it would allow complete source and binary freedome by separating the rules applied to the data and the applicaitons handling it. this also removes the possibility of an insecure or secretly malicious application compromising a set of protected data.

    --
    Snowden and Manning are heroes.
  15. So we want evil to win because good is dumb? by Anonymous Coward · · Score: 0

    > I suspect that Linus just wants to make his software while the FSF wants to change the world.

    One problem I have with *not* trying to "change the world" is that unrestricted computers may not be possible in all legal venues if certain parties have their way. And, honestly, that issue is *much* more important to me than simply having technically superior software. What good is having a superior computer if you can no longer do what you want with it? And yet Linus has repeatedly opined that the hardware seller has some kind of right to lock me down? I'd kick the hardware maker in the balls before I'd take that kind of crap from them. You won't catch me with a TiVO.

    Also, it's ironic that one of Linus' objections to the DRM clauses were that they might forbid useful future technology, when he's so against giving Linux the opportunity to be relicensed under newer versions of the GPL. Given that the licensee gets to choose which license they wish to accept from among those allowed by the copyright holder(s), I wonder if he isn't working against the system instead of with it? After all, if the DRM clause really did forbid the use of Linux or other software in useful ways, the GPL could be modified in later published versions to allow for those uses...

  16. Linus.. by Anonymous Coward · · Score: 0

    Linus is a dumb focktard, why should anyone listen to him anyway? He trolls on every project if he doesn't agree with it.

    1. Re:Linus.. by slack_prad · · Score: 1

      He's not dumb, but he trolls, alright

      --
      Sent from my desktop computer
  17. The answer... by dosius · · Score: 4, Insightful

    The answer if you can't handle Linux being bound to GPL2 when the rest of the world goes GPL3, is to drop Linux for a GPL3-compatible system. Don't get me wrong, I like Linux, but maybe this will cause a lot of movement from Linux, not to Hurd - Hurd is still shit - but to FreeBSD, which is the next best thing to Linux and the license ought to be compatible with any version of the GPL.

    And besides. In this "GPL vs Proprietary! White vs Black!" debate that's been going on past 15-aught years, I've sided with NetBSD.

    -uso.

    --
    What you hear in the ear, preach from the rooftop Matthew 10.27b
    1. Re:The answer... by Kaktrot · · Score: 1
      I think this is a fantastic idea! GNU should fork FreeBSD into GNU-BSD! Then they wouldn't have to worry about what Linus thinks. If the rest of the kernel developers are any indication, Linus would probably be one of the very few who would be upset by it, and one of the best operating systems would be protected from commercial hijacking.

      *Guiness guys* Brilliant! I know that's not what you had in mind, but I'm inspired now.

      --
      BSD: The most efficient way of subsidizing the enemy.
    2. Re:The answer... by RLiegh · · Score: 1
      I think this is a fantastic idea! GNU should fork FreeBSD into GNU-BSD!
      You mean into something like this?
    3. Re:The answer... by chance2105 · · Score: 1

      To drop the Linux kernel, which has at least GPLv2 protections, for a BSD which has _none_ of those protections for developers and end users is silly.

      GPLv2 vs GPLv3 might be a debate, but the GPLv2 got us where we are today.

  18. Who cares what Linus thinks about the GPLv3? by Korgan · · Score: 3, Informative

    Maybe I'm being ignorant here, but if anyone actually reads the version of the GPL that is used by and distributed with the Linux kernel, it does not allow you to use a later version. The Linux kernel is, and always will be, GPLv2. That was a conscious decision by Linus and the other developers.

    Because of that, who really cares what Linus has to say about the GPLv3? He's made it pretty clear he doesn't like it, but the only work that he's producing that anyone cares about is Linux. And the Linux kernel will never be anything other than GPLv2. Even if they /WANTED/ to change it, too many people that have contributed in the past under the GPLv2 license are either dead or simply not accessible to get their permission to change to the newer license. The logistics of keeping track of which part is GPLv2 and which might become GPLv3 just makes it simply "too hard."

    Personally, I don't give a damn if Linus likes GPLv3 or not. Its not about Linus, its about everyone in the Free software community as a whole. Individuals can go shoot their feet off instead of their mouth. Its about whats best for the majority, not just Linux or just Gnome or just GCC or just whatever...
    [/rant]

    1. Re:Who cares what Linus thinks about the GPLv3? by Just+Some+Guy · · Score: 1
      The logistics of keeping track of which part is GPLv2 and which might become GPLv3 just makes it simply "too hard."

      Are you sure? Under Subversion, you can run "svn blame somefile.c" to see who wrote each and every line of that file. If you made a database of users and whether it's OK with each, and assuming that whatever they've decided to store Linux in this month supports similar functionality, it should be relatively easy to see when every contributor to a file had signed up and to then "convert" that file. Repeat until finished, or until the missing pieces are small enough to be removed or rewritten.

      --
      Dewey, what part of this looks like authorities should be involved?
    2. Re:Who cares what Linus thinks about the GPLv3? by Korgan · · Score: 1

      The point is moot however, given that the Linux kernel will never be anything but GPLv2. Torvalds, Morton and crew just wouldn't accept new GPLv3 code unless it was dual licensed at the very least.

      Secondly, any code that is a derivative of existing could would have to remain GPLv2 anyway simply because of the terms of the current license. It specifically rules out future versions of the GPL. Therefore only new code that is not derived from existing kernel code would be able to go this path.

      Even discounting all of this, the fact still remains that Torvalds opinion of the GPLv3 is purely negative and he has offered nothing constructive yet. Sure, point out the problems, but also offer solutions that might resolve those problems. As someone who is lead of one of the largest and most popular Open Source coding projects out there, you'd figure he'd know this already. He expects it of people commenting on, or contributing to, the Linux kernel.

      I still maintain that I don't care what Linus Torvalds thinks of the GPLv3 given his main project, the only project of his anyone outside of Linux kernel development gives a stuff about, will never ever be GPLv3 simply because the existing license does not allow it. The legal logistics, even above the technical abilities of SVN, are simply too difficult for it to be possible until such time as the copyright has expired on a lot of code. So about another 65-75 years or so under current US law.

  19. if only the corporations were more willing... by Anonymous Coward · · Score: 0

    to help the free software / open source community without a direct personal interest.

    Corporations are by definition not benevolent, they are stockholdocratic.

    I care not a wit what the corporations think about the process. The community are my brethren, not the corporations.

  20. Re:The GPL needs to go by Sterling+Christensen · · Score: 1

    The GPL doesn't do that.

    As I understand it (I'm not a lawyer), the GPL dictates the terms/conditions by which you may COPY the work. Meaning: if you publish your modified kernel (as a binary or whatever) the GPL kicks in and requires you to publish source code too. If your modifications stay internal, private, on-site (i.e. no COPYING occurs) you're at no obligation whatsoever.

  21. Re:The GPL needs to go by Anonymous Coward · · Score: 0

    this is all so wrong that it isnt even funny. Where are the mods? If this comment doesn't deserve a -1 WRONG tag I don't know what does. Please mod it down to stupidtrollland, where it came from.

  22. Re:The GPL needs to go by slack_prad · · Score: 1
    ...any products compiled with GPL'd tools - such as gcc - would also have to its source code released.
    WHAT?! is this true? Can someone clarify?
    --
    Sent from my desktop computer
  23. What's ERS' Opinion? by Anonymous Coward · · Score: 0

    ERS has been pretty silent about the whole thing, and it was him what started the OPEN-SOURCE software?

    He's probably too busy working on his good programs, fethcmail is still been extend...

  24. Re:The GPL needs to go by Punboy · · Score: 2

    Ok, well since you know nothing about Linux (even though you claim to have worked with it), I'll let you in on a few secrets.

    Ext2 is ancient. Don't use it. Instead use a journalled filesystem such as Ext3 and ReiserFS, the latter being my favorite for production environment. Both ext2 and ext3 filesystems can be easily defragged with e2defrag. Although, Ext3 and ReiserFS both have technologies to prevent major defragmentation.

    Token ring? Please. Nobody really makes good tokenring equipment anymore (if they ever did in the first place), and nobody cares to. Use ethernet, its cheaper, faster, more reliable, and has far more products available. But in any case, Linux has supported tokenring for a very long time. Don't believe me? Google it.

    As far as your lawyers' analysis of the GPL, they are completely wrong. You don't have to release any sourcecode that's compiled with GCC just because GCC is GPL'd. Neither do you have to release any modifications you make to the linux kernel. This is the wonder of the GPL version 2. If you want to sell your modifications, fine. Do so. Sell it, distribute it for free, whatever. Just cite the source. But, only the modifications. If you are going to release the modifications already builtin, you have to provide the original source prior to modification. Simple.

    You totally made up most of your argument, you've probably never worked in the IT field a day in your life, at least not with Linux. Stop acting like you're an engineer/lawyer/whatever. You are not.

    --
    If you like what I've said here, and want to read more, go to http://www.krillrblog.com
  25. nothing to see, move along by maxpublic · · Score: 0, Redundant

    I don't really see the problem here. It's not as if any of the folks in question (Torvalds, FSF, EFF, whatever) have any sort of actual authority to force the adoption of any particular licensing scheme. They can recommend a licensing scheme until they turn blue in the face, but that's all that they can do and all they'll ever be able to do.

    So what if one set of folks chant mantras over the greatness of v3, while another group do the same over v2? Neither group can enforce an agenda on anyone else, so if you don't prefer v3 or v2 (or vice versa) then fuck what the opposition thinks. Choose whatever license makes your little developer heart go pitter-patter and move along, doggie.

    My guess here is that the very lack of real authority is what gets the fanatics panties in a twist. They can't *force* everyone around them to adopt v3 or v2, so they get royally pissed when others won't automatically adopt The One True and Right Way(TM) with cheerful abandon. If anything this should make the non-fanatics happy, as the situation provides *us* with the right to make that choice, rather than some bunch of arrogant fuckers who prides themselves over being our intellectual or moral 'superiors'.

    Max

    --
    My god carries a hammer. Your god died nailed to a tree. Any questions?
    1. Re:nothing to see, move along by Ohreally_factor · · Score: 2, Insightful

      Actually, I think it's good to have this debate, maybe even healthy. You're right, if someone's mind is made up, there's little chance that an argument of slashdot will change it. But not everyone has made up their mind, nor is everyone clear on the issues. The "article" itself is not a real help: it's really more of an editorial from one of the opposing camps.

      There is a danger, however. How great this danger is is anyone's guess. It might be fairly minor. Here's how I see it:

      If the OSS development community really does get divided by this, we're going to see a lot of forking going on, if members of any project disagree on changing to GPLv3. If someone who has written some code wants to keep his code under GPLv2, those that want to move to GPLv3 can remove his code and rewrite it. He can get together with other GPLv2 hold outs, pool their code and rewrite the missing bits. If this comes to pass, I see an exponential rise in the amount of duplicated effort.

      It's a possible scenario. I don't know for certain whether it will be widespread or even if it's really a bad thing. Another thing I am not clear on: people are saying that GPLv3 and GPLv2 are "compatible". How will a v2 and a v3 fork be able to merge at a later date? Can the v2 fork take the v3 code and keep the v2 license?

      --
      It's not offtopic, dumbass. It's orthogonal.
    2. Re:nothing to see, move along by SwashbucklingCowboy · · Score: 1
      It's not as if any of the folks in question (Torvalds, FSF, EFF, whatever) have any sort of actual authority to force the adoption of any particular licensing scheme.

      Linus can stop adoption of GPL v3 as he's written part of Linux. A piece of software's author (owner) controls how it's licensed.

      The FSF certainly can (and according to RMS will) force the adoption of GPL v3 on all of the code controlled by the FSF. That's a reasonably significant part of the code in a Linux distro.

    3. Re:nothing to see, move along by LocalH · · Score: 1
      The FSF certainly can (and according to RMS will) force the adoption of GPL v3 on all of the code controlled by the FSF. That's a reasonably significant part of the code in a Linux distro.

      Only on new releases. Even on software that includes the "or any later version" clause, I can still distribute it under the original license it was released under.
      --
      FC Closer
    4. Re:nothing to see, move along by jasonjacks0n · · Score: 1
      f the OSS development community really does get divided by this, we're going to see a lot of forking going on, if members of any project disagree on changing to GPLv3.

      Yeah, I think a lot of people are worried about this; it's a big part of why the discussion is so heated, I think..

      I mean, the FOSS licenses and their interactions are already too complicated: GPL/LGPL vs. BSD is understandable, but then there's the Apache license, Perl's artistic license, the MPL, Sun's CDDL, the PHP License, and tons more .. it gets hard to even keep track of the acronyms, much less what licenses can be mixed and so on. And now there might be a huge split between GPLv2 people and GPLv3 people? Yuck. :-/

      But it seems inevitable. Certainly Linux will remain under GPLv2, because it's not practically possible to change it, even if Linus could be convinced. And RMS will clearly move all GNU code that the FSF controls to GPLv3.

      It's a possible scenario. I don't know for certain whether it will be widespread or even if it's really a bad thing. Another thing I am not clear on: people are saying that GPLv3 and GPLv2 are "compatible". How will a v2 and a v3 fork be able to merge at a later date? Can the v2 fork take the v3 code and keep the v2 license?

      As far as I can see, for that to be possible, the GPLv3-licensed code would need to include a special provision that it could be used under a previous version of the GPL. Sort of the like the built-in provision for future license versions, but in reverse. That basically throws away the benefits of using GPLv3 at all, though, so I don't see it happening much.

      --
      This space intentionally left blank.
  26. Of course not by Sterling+Christensen · · Score: 1

    The FSF says GCC's output doesn't have to be GPL:
    http://www.gnu.org/licenses/gpl-faq.html#GPLOutput

    glibc is *L*GPL, but that's different. It requires modifications to glibc itself to be published, but allows the program using glibc to be closed source.

    (I'm not a lawyer, this is not legal advice)

    1. Re:Of course not by tgcid · · Score: 1

      From the page you linked: Can I use GPL-covered editors such as GNU Emacs to develop non-free programs? Can I use GPL-covered tools such as GCC to compile them? Yes, because the copyright on the editors and tools does not cover the code you write. Using them does not place any restrictions, legally, on the license you use for your code. Some programs copy parts of themselves into the output for technical reasons--for example, Bison copies a standard parser program into its output file. In such cases, the copied text in the output is covered by the same license that covers it in the source code. Meanwhile, the part of the output which is derived from the program's input inherits the copyright status of the input. As it happens, Bison can also be used to develop non-free programs. This is because we decided to explicitly permit the use of the Bison standard parser program in Bison output files without restriction. We made the decision because there were other tools comparable to Bison which already permitted use for non-free programs.

  27. Re:The GPL needs to go by Anonymous Coward · · Score: 0

    sup my nigga

  28. Parent blatently incorrect by Workaphobia · · Score: 2

    At first I thought it odd that a well written (that is, grammatically correct), lengthy post should be modded -1 Troll, but by the time I finished reading your post it became clear that you are either grossly misinformed or deliberately spreading lies about the license. I believe it is the latter, since I doubt that any commercial legal department could interpret the GPL so poorly, when most slashdot readers are aware of these simple facts:

    A: You are *NOT* under any obligation whatsoever to release your source code to anyone else so long as you do not distribute your modified binaries. If you do distribute your binaries, the GPL aims to make certain that the recipient also has access to the source code corresponding to it.

    B: Programs compiled under GCC are not GPL'd. In fact, the output of any GPL program is never automatically covered by the GPL unless a significant portion of the output originated from said program. Also, the gcc libraries are LGPL'd, not GPL'd, so this concern doesn't even apply.

    But you already knew that, didn't you.

    --
    Evidently, the key to understanding recursion is to begin by understanding recursion. The rest is easy.
  29. Wow, you missed the whole point of the DRM clause. by Anonymous Coward · · Score: 1, Insightful

    the bsd license includes even fewer freedom-protecting clauses than gplv2, so why would people who wante a freedom-protection clause in gplv3 defect to bsd licenses?

    They'd have to relicense the bsd stuff (since it's missing the freedom-protecting gplv2 clause of no extra limitations) as gplv3, but it wouldn't be a bsd project anymore, it'd be something else.

  30. Re:Wow, you missed the whole point of the DRM clau by Anonymous Coward · · Score: 0

    Freedom to? Users? The BSD license allows freedom to developers. I'm a developer, and perfer bsd licensed code. I'll give code if the client asks, and charge more. People have mouths to feed you know. There is no point in freedom to users, I perfer freedom to developers, and will send patches to the used project if I somehow improve the code.

    Thanks for not thinking

  31. You just fed a troll (n/t) by Anonymous Coward · · Score: 0

    n/t

  32. Re:Wow, you missed the whole point of the DRM clau by Anonymous Coward · · Score: 0

    Now I understand why *BSD only has at most 8 or 9 users in the entire world. You guys have fun, though, don't let us users stop ya. lol

  33. MOD PARENT UP by cryptoluddite · · Score: 3, Interesting

    The problem I have with Linux re: GPL 3 is that he's just being ignorant. He has some beef about people having to give out their own personal private keys that has been shot down by any number of people that actually know what they are talking about legally (PJ, Eben, etc). Just casually reading the license and Linus' comments, he just isn't making any sense.

    My best bet is that Linus doesn't actually want to understand the GPL v3. Linux is eminently practical, and the practical thing to do to increase Linux usage, fix bugs, and add new features is to make Linux corporate friendly. A *lot* of contributions come from the likes of IBM, Red Hat, Sun, Novell, and other companies. I bet the prospect of these companies pulling out their support is a major consideration (whether intentional or not).

    1. Re:MOD PARENT UP by marcosdumay · · Score: 1

      Let's call it what it is: Linus is spreading FUD. He may not realise that, but that doesn't change the fact.

      He also insist on ignoring that the more "corporate friendly" BSD has far less support from the corporations than the not friendly Linux.

  34. It is a (the?) Free Software license by hooykaas · · Score: 1

    So it makes sense that the Free Software communities are most heavily involved and it seems perfectly logical and acceptable that the process is lobsided to those communities.

    In fact if one looked at the persons in the 4 committee, one would see many representatives of commercial companies. I found these list quite impressive (even though I can't estimate how actively everyone is involved, and what kind of influence they have). That we don't hear them in the article might be that in such corporations talking to the "press" is often more controlled.

  35. Re:Wow, you missed the whole point of the DRM clau by dosius · · Score: 1

    The thing is you can convert BSD license to GPL license. There's nothing stopping you from doing that.

    -uso.

    --
    What you hear in the ear, preach from the rooftop Matthew 10.27b
  36. Re:The GPL needs to go by Godji · · Score: 3, Funny

    Furthermore, after reviewing this GPL our lawyers advised us that any
    products compiled with GPL'ed tools - such as gcc - would also have to
    its source code released. This was simply unacceptable.


    You sure have some really dumb lawyers. How much do you pay them?

  37. Re:The GPL needs to go by arkhan_jg · · Score: 2, Informative

    This troll is posted in every GPL discussion, and most linux discussions. Ignore it, it's complete crap intended merely to provoke responses.

    --
    Remember kids, it's all fun and games until someone commits wholesale galactic genocide.
  38. It's about the right to 'Fix' problems yourself by Anonymous Coward · · Score: 1, Insightful
    Sorry, but Linus is simply late to the game, and therefore misses the point of what the FSF is all about.

    The FSF starts based on the premises that if you have a problem (something does not work the way you want it to) you have the right to fix it yourself, not rely on some third party to 'fix' it or not, as they choose.

    If you buy a bit of hardware that uses GPL code, but will not allow you to 'fix' a problem yourself (because your fix will not run on the hardware they have restricted to run only their own version of GPL code), then you have lost the right to 'fix' your own problems.

    Destroys the whole point of it using GPL code, doesn't it? At least for the end user - but it is sort of nice for those that then profit from GPL code used this way.

    The FSF has this one right - just as RMS was right when he wanted to fix a print driver and was not allowed to - and so started the whole GPL/GNU Copyleft thing.

    This is as simple as the FSF fights the war, so others can actually produce code that will be of actual open use to all.

    Linus produces some of that code - he should be a bit grateful.

    As I am grateful to Linus for writing his bit and releasing it under the GPL - making it possible for me to use.

    I just value the freedom RMS and crew have created for me - and protected for me, and that they continue to protect for me. Including the code Linus (and so many others) wrote and released under the GPL.

    Locking GPL code into hardware, never to be changed is a Bad Thing.

    BTW, I don't expect anyone to have to agree with me - it's just a post of my strongly held opinions - no more no less.

    This is only A/C because I used some mod points in this thread, and this is the only way to post without undoing those - and I have no more mod points so it's not gaming the system so I can mod this up (I doubt it will be anyway).

    NewToNix.

    1. Re:It's about the right to 'Fix' problems yourself by NewToNix · · Score: 1
      Well so I just learned a bit more about / code - it warns you that your mods are lost when you try to post - even after you have no more points to use. Which is OK - that seems to be the deal.

      But it does not warn you that it's going to do the same thing after you use the A/C button and preview.

      So I can say I wasn't warned - but that's OK, I learned something.

      sorry to those people I modded up that just lost my effort to make their views heard.

      Not bitching here, just apologizing for my lack of knowledge - and a slight error, I think, in the /code.

      Ah well, it was my first try at A/C posting - and my last... a learning experience.

      NewToNix

  39. Re:Sure to happen by Ohreally_factor · · Score: 1, Interesting

    This may be me going out on a limb but maybe Linus knows he personally will be allowed to tinker no matter what gets implimented. Remember that hes not immune to being corrupted by money too.

    Your way past out on a limb. I think you've fallen deeply into your own crevice.

    On what basis can you make such an allegation? Someone disagrees with you, so they must be corrupt? What the fuck is wrong with you?

    --
    It's not offtopic, dumbass. It's orthogonal.
  40. No point in doing that by _jameshales · · Score: 1

    There's no point taking something and placing restrictions on it, if people can still use the freer version. Changing its license would be pointless unless someone was planning on making major modifications and improvements to the BSD software, and then maintaining it.

  41. Has Linus sold out? (was: Re:I can see both sides by quentin_quayle · · Score: 4, Insightful

    First a minor point which keeps getting overlooked. With DRM hardware, you cannot verify GPL compliance. The only way to verify that a set of source code purporting to represent the binary that is running, is really the binary that is running, is to compile from that source and run the new binary. Any hardware that requires signed binaries prevents this unless signature capability is given to anyone who wants it. Thus without GPLv3, there cannot be public verification that any vendor of supposedly-GPL software for "trusted" hardware really is complying with the GPL. So another way to characterize the anti-DRM provision would be to call it verifiability.

    Now, DrJimbo in parent post:

    "Without the DRM provisions in the GPLv3 that Linus is complaining about, we could eventually face a situation where it is literally impossible to develop FOSS for the latest generation of computers. Worse, those computers could be running the GPLv2 software we wrote even though we have lost all of our rights to further modify it and we've lost the right to even choose what software we run on our own computers."

    Right, exactly - And this is what Torvalds consistently refuses to address. He snipes at GPLv3 with invective and complaints about the process (and if he really was the poster in the Groklaw thread, about the definition of source code), etc.. But on the hardware issue he just flippiantly declares that if you don't like the inability to run modified GPL code on the same device, get some other device.

    This obviously ignores the "trusted computing" initiative that is intended to make all PCs slave devices, and is progressing like an onrushing freight train while DRM apologists quibble on the tracks and say "let's wait and see what it really turns out to be" or "how it is used" - then of course it will be too late.

    This makes me wonder of a darker possibility which I do not like to think of ,but it fits the facts: Has Linus sold out? This is suggested by another poster below and in this post at the Newsforge thread:

    "You need to understand why Torvalds opposes this. Torvalds sits behind a wall of IBM/HP (and other companies) lawyers. They pay his wages and defend him from the SCOs of the world. In return, he spouts their views... and in this case, these technology companies want this hardware in every PC very very badly. To get the level of control over the user that they want, they must be able to use a "trusted" kernel (the kernel/bios/boot loader are critical components in a trusted system).
    "Basically, Torvalds has turned into a mouthpiece for technology companies. "

    Otherwise why does Linus fail to address the real and appropriate concerns about TC hardware becoming exclusively available?

  42. Re:The GPL needs to go by Ohreally_factor · · Score: 1

    YHBT.

    However, GPLv3 seems to be changing control to beyond mere distribution. That is at the heart of this debate.

    --
    It's not offtopic, dumbass. It's orthogonal.
  43. TCM is coming, we need GPLv3 before then by Anonymous Coward · · Score: 1, Insightful

    Care to explain how this scenario is actually supposed to play out?

    Easy: TCM is coming, unstoppably.

    And once TCM is on everyone's PC, your *effective* freedom to change the code on your own computer goes out the window, because if you change it then your box will be flagged as untrusted and your downloads from many sites and playbacks of media will begin to fail.

    So, manufacturers will be benefitting from GPL'd code, and providing sources, and you will still be able to modify anything you like, but to no avail because as soon as you do so, your computer will start to act "broken".

    And that's why we need GPLv3. GPLv2 is fairly adequate at this point in time, except where DRM undermines it like in the case of the TiVO, but the way things are going that will become the norm everywhere, and will make a total mockery of the intentions of the GPL. Being able to recompile the sources but not use them is obviously a travesty.

    If you still don't understand the issue then God help you.

    1. Re:TCM is coming, we need GPLv3 before then by sumdumass · · Score: 1

      On this DRMed world, how qill software engineers and programers continue to work?

      I mean microsoft isn't going to push for technoligy that stops anyone from making software for thier operating system. Intel, via, biostar, asus or any other hardware manufacturer isn't likley to start selling appliances instead of computer mainboards. There will be a way to sign your own code against this DRM. It may require some OSS coder to produce a TCM module or something though.

    2. Re:TCM is coming, we need GPLv3 before then by Anonymous Coward · · Score: 0
      It may require you either pay thousands of dollars for keys to the kingdom or you can no longer even connect to the internet because your ISP detects you are running untrusted code. Neither is acceptable.

      Consumers are not asking for DRM or TCPA, there is no point to the technology unless enforcement is ubiquitous.

    3. Re:TCM is coming, we need GPLv3 before then by dfghjk · · Score: 1

      "And once TCM is on everyone's PC, your *effective* freedom to change the code on your own computer goes out the window, because if you change it then your box will be flagged as untrusted and your downloads from many sites and playbacks of media will begin to fail."

      Your freedom to change the code still exists, as does the freedom of the copyright holders to deny you access to their product if they so wish. You've been brainwashed into thinking they have an obligation to serve you---perhaps even free of charge.

      You may consider this "new computing product" not very desirable but, as they say in free software land, you're always free to create your own. It goes both ways.

  44. I think Linus is right by Stephan+Gitz · · Score: 1

    I think that Linus is right and there is no problem with DRM because we have a marketplace. Yes, there will be Vendors that use GPL-Soft and forbid changed and therefore unsignd binarys to execute on there Hardware. Maybe you can call that Vendors Leeches, but sometimes there are good reasons for this behavior that benefit the Custumer. Think on Mission-Critical Hardware that should NEVER execute hacked binarys - in your best interest.

    And yes, there will DRM-crippled Hardware where you would like to change the software, but you are free to not buy that Hardware if it not fit your needs. If the big Vendors use only "crippled" Hardware and there are enough People that want Hardware that allow to execute unsigned binarys, than there will uprise a new vendor that grow big really fast. Most Hardware is no Magic in this times and many Companys exist that sell you the ASICs you need for your Hardware. Buy a CPU, some DSPs, some RAM and some Interfaces and put it together. If all Hardware is crippled and you are the only on that dont cripple the Hardware, your sales will skyrocket.

    Don't underestimate the community. In times where many people realize the power and benefits of Homebrew Software, Vendors that forbit Homebrew will slowly die if there is not a REALLY good reason to forbid changes. Sony seems to realize that with the PS3 and allow Homebrew to sell more Hardware. If you can select between a XBox360 that don't allow you execute Homebrew and a PS3 that allow you execute Homebrew, what Hardware will a Homebrew-Fan buy?

    1. Re:I think Linus is right by Anonymous Coward · · Score: 0
      Are you on drugs? No, the marketplace will not decide because the market will be rigged. TCPA crippled hardware will be sold unmarked to prey on consumer ignorance and it will be sold at a huge loss to maintain market apathy.

      Homebrew developers are a tiny percentage of the global computing device market. Far from embracing and welcoming community contribution, many corporates would prefer if we didn't exist, which we wont the TCPA scenario plays out. For a time we may be able to obtain functional hardware, until TCPA becomes so entrenched that there's a push for legislation to make it mandatory.

      Think on Mission-Critical Hardware that should NEVER execute hacked binarys - in your best interest.

      The hardware manufacturer says hacked code, I say custom kernel with custom modules, the expensive legislation says "criminalized"!

    2. Re:I think Linus is right by cortana · · Score: 1
      I think that Linus is right and there is no problem with DRM because we have a marketplace. Yes, there will be Vendors that use GPL-Soft and forbid changed and therefore unsignd binarys to execute on there Hardware. Maybe you can call that Vendors Leeches, but sometimes there are good reasons for this behavior that benefit the Custumer. Think on Mission-Critical Hardware that should NEVER execute hacked binarys - in your best interest.
      Fine, except it won't stop at that.

      Monopoly holders such as Microsoft and the *IAA will lobby for laws making the manufacture, import, sale or use of hardware without Trusted Computing chips illegal.
    3. Re:I think Linus is right by Stephan+Gitz · · Score: 2, Informative
      Are you on drugs? No, the marketplace will not decide because the market will be rigged. TCPA crippled hardware will be sold unmarked to prey on consumer ignorance and it will be sold at a huge loss to maintain market apathy.

      You seems not to realize that TCPA should not be used kill all OpenSource on all devices with TCPA-Hardware.
      OSS and DRM-Software will coexist on normal Hardware without the Problems that someone told you. They will NEVER forbid you to run own code on a PC. The Cell-Chip is one of the first CPUs that designed with Hardware-Security in mind. With the Cell-Chip you kann run a SELFMODIFID Linux and on top of it you run a DRM-Software that will get an encrypted chanel from the Processor. Please read some more about TCPA and how it Works:
      http://www-128.ibm.com/developerworks/power/librar y/pa-cellsecurity/

      There is no need to forbid you to execute your own binarys to give DRM-Software all features there need. The Problem lies only in the Embedded-Market, where Vendors can decide that there should only run the own binarys one the Hardware. But as i explained, if all gread Vendors forbit you to execute your own code, then there will rise another Vendors that will allow it to you.

      Homebrew developers are a tiny percentage of the global computing device market.

      The Homebrew-Community are developers AND users and together there will be enough on the global market that there will be Enterprices that meets the demands of the Homebrew-Community.

      Far from embracing and welcoming community contribution, many corporates would prefer if we didn't exist,

      Thats right, but prefer something will mean nothing.

      which we wont the TCPA scenario plays out.

      Thats Wrong. TCPA will NEVER take your posibility to run your own code on Standard-Hardware.

      For a time we may be able to obtain functional hardware, until TCPA becomes so entrenched that there's a push for legislation to make it mandatory.

      It is no Problem when they will make it manatory for Hardware, because you will have no Problem to execute DRM-Soft and OSS at the same time on the same PC. And there will never a Bill that force you to put your own Work in the DRM-Cage.
    4. Re:I think Linus is right by Anonymous Coward · · Score: 0

      Feature creep! Running your own code TCPA free is great when you can no longer even connect to the internet. Keep drinking the kool-aid.

    5. Re:I think Linus is right by Stephan+Gitz · · Score: 1
      Monopoly holders such as Microsoft and the *IAA will lobby for laws making the manufacture, import, sale or use of hardware without Trusted Computing chips illegal.
      There is NO PROBLEM for OOS if ALL Hardware have "Trusted Computing" chips, because there is no problem to execute OSS without harm for the DRM-Soft on the same Hardware. So they can lobby a law that all Hardware must have Trusted Computing without the possibility to copy DRM-Content, but you can't lobby a law that all Software must DRM-cribbled. It is like you can make a law that all streets must have mandatory attributes, but you can't make a law that only Cars from Ford and GM can use the street.
    6. Re:I think Linus is right by Stephan+Gitz · · Score: 1
      Monopoly holders such as Microsoft and the *IAA will lobby for laws making the manufacture, import, sale or use of hardware without Trusted Computing chips illegal.
      I think that softwarepatents are the only real threat for OpenSource-Software.

      by the way: I am using 99% OpenSource @Home and administrate a 100% Linux-Lab at work. But after i informed me many hours about Trusted Computing, i am sure that it CAN't be used to kill OpenSource.
    7. Re:I think Linus is right by cortana · · Score: 1
      There is NO PROBLEM for OOS if ALL Hardware have "Trusted Computing" chips, because there is no problem to execute OSS without harm for the DRM-Soft on the same Hardware.

      It is a problem once my bank says, "for your security, you must have a Trusted Computing verified system to access your bank account online". It is a problem once my government says the same thing.

      So they can lobby a law that all Hardware must have Trusted Computing without the possibility to copy DRM-Content

      Which is a bad thing since it completely obliterates uses which, until now, were protected by the doctrines of fair use, fair dealing, and by the fact that in the non-digital world, utilisation and modification of a work does not require it to be copied.

      but you can't lobby a law that all Software must DRM-cribbled.

      There is no need to do so when the market grants extrodinaty leverage to a small number of producers, who can simply agree to all declare simultaneously that their consumers must use Trusted Computing verified hardware.

      It is like you can make a law that all streets must have mandatory attributes, but you can't make a law that only Cars from Ford and GM can use the street.

      If the utilisation of Trusted Computing hardware requires the licensing of a patent then you can indeed make just such a law.

    8. Re:I think Linus is right by cortana · · Score: 2, Insightful

      But you are ignoring a very real way in which it (or, at least general DRM) is being used to kill open source: Tivo's abuse of the works it builds upon and distributes which are licensed under the GPL.

      This is a moot argument anyway. In twenty years time, the web will have indeed reduced whatever OS we use into a poorly-debugged set of device drivers. Try applying the Four Freedoms to Google or other web applications that you use.

    9. Re:I think Linus is right by Stephan+Gitz · · Score: 1
      Feature creep! Running your own code TCPA free is great when you can no longer even connect to the internet.
      If you can't connect to the Internet, please pay your bill or let an expert help you. But it will NEVER happen that your ISP will check if your Hardware runs 100% DRM-Soft. And also most Content-Creators have no wish to check if you have also OSS running. Many Content-Providers will make DRM-Hardware and Software mandtory to use there Content, but if you want there Content, you can run DRM-Software on TOP auf your OpenSource-OS that get a "secure" environment for there Content from your Hardware. Without kicking the Ilusion of Democracy and establish a Diktatorship there will be NO WAY that you can't get in the Internet because you use OpenSource.
    10. Re:I think Linus is right by Anonymous Coward · · Score: 0
      it will NEVER happen that your ISP will check if your Hardware runs 100% DRM-Soft.

      100%? I'll not be using any 'DRM-Soft' or any TCPA enabled platform. TCPA will be a requirement for many online services and it can already be used to resrict network access, who the fuck are you to say that these features will "NEVER" be mandated for ISP's?

      Without kicking the Ilusion of Democracy and establish a Diktatorship there will be NO WAY that you can't get in the Internet because you use OpenSource.

      If you lived in either the US or the UK, you'd know that there's no interest in maintaining the illusion of democracy anymore. We can at least agree that democracy was an illusion, unlike TCPA. The capacity of TCPA to grant technology companies dominion over the worlds digital information is not something you dismiss as a result of reading their propaganda.

    11. Re:I think Linus is right by Stephan+Gitz · · Score: 1
      It is a problem once my bank says, "for your security, you must have a Trusted Computing verified system to access your bank account online". It is a problem once my government says the same thing.
      You obvious don't know how TCPA works. There is no Problem if your Bank say you need TCPA-Features to use there service. There is no need that ALL Software that you run in that Moment need to be signed. Only the Software for the Banking needs to be signed. So you can run Linux and on top of it the signed BankingSoftware. TCPA will NOT kill OpenSource. You will not forced to run a 100% signed System to used DRM-caged-services.

      So they can lobby a law that all Hardware must have Trusted Computing without the possibility to copy DRM-Content

      Which is a bad thing since it completely obliterates uses which, until now, were protected by the doctrines of fair use, fair dealing, and by the fact that in the non-digital world, utilisation and modification of a work does not require it to be copied.
      Yes, it is a bad thing that big Industries try to take away fair use, fair dealing and things like that from our culture, but i agree with Linus that the GPL is not the place to fight this development.
    12. Re:I think Linus is right by Stephan+Gitz · · Score: 1
      But you are ignoring a very real way in which it (or, at least general DRM) is being used to kill open source: Tivo's abuse of the works it builds upon and distributes which are licensed under the GPL.

      No, Tivo don't kill OpenSource. You can download the complete Source with all there Changes from there Website: http://www.tivo.com/linux/linux.asp

      Yes, i think it sucks that you can't use the Tivo-Hardware with modificated Software, but everyone can take the Source and build similar Hardware and Services to compete with Tivo. So Tivo don't kill OpenSource. A Question: You have the choice between Tivo that don't allow Homebrew and a similar Service that allow you Homebrew. What Service will get more Customers over time?
    13. Re:I think Linus is right by cortana · · Score: 1

      Indeed, I should have said Free Software, not Open Source.

      As to your question: other factors will determine it. The market fails to protect the rights of consumers in this case because there are not enough consumers who are aware that they have these rights and/or care to make use of them.

    14. Re:I think Linus is right by Anonymous Coward · · Score: 0
      You obvious don't know how TCPA works. There is no Problem if your Bank say you need TCPA-Features to use there service. There is no need that ALL Software that you run in that Moment need to be signed. Only the Software for the Banking needs to be signed.

      You obviously don't understand that freedom doesn't entail being forced to run signed binaries.


      So you can run Linux and on top of it the signed BankingSoftware. TCPA will NOT kill OpenSource. You will not forced to run a 100% signed System to used

      I will not be running any signed software on my systems. What don't you understand?

    15. Re:I think Linus is right by Stephan+Gitz · · Score: 1
      Indeed, I should have said Free Software, not Open Source.
      That don't change anything.

      As to your question: other factors will determine it. The market fails to protect the rights of consumers in this case because there are not enough consumers who are aware that they have these rights and/or care to make use of them.
      I don't agree with you. I think the Market that realize that Homebrew and a big Community arround a Produkt is something to want, is allready big enough. I am amazed how many People have a WRT54G(S) because of the community. I am amanzed how many have a modded Xbox or a modded PSP. I am amanzed how many People are pissed off about Mobiles with crappy Firmware, and ask about Linux-Mobiles. The Community is already bigger than many ever feared/hoped.

      I disagree with you when you say we must save stupid people from buying crappy hardware. If the GPL is a place to stop other People from doing stupit things, i have some paragraphs that we can include to.
      In one Paragraph we can stop all fascist, racist and warmonger using GPL-Soft because they use it for stupid things that i don't want.
      In another Paragraph we can add that all Users from GPL-Soft must accept Freigeld because our Money we use today has a bug that drives many in poverty and view in richness - till Civil War

      See also:
      A Critical Analysis of Traditional Money and the Financial Innovation "Neutral Money"
      A Market Economy without Capitalism
    16. Re:I think Linus is right by Stephan+Gitz · · Score: 1
      You obviously don't understand that freedom doesn't entail being forced to run signed binaries.
      You have the freedom to let all Hardware in the shelves that want you to force to use signed binarys. I will never buy Hardware like Tivo from Enterprices that don't want me in there community.
      I will not be running any signed software on my systems. What don't you understand?

      I understand this and thats OK! But why will you force other to do the same? I for one run Ubuntu and Debian and all my binarys are signed. And i would use signed Bankingsoftware to.
    17. Re:I think Linus is right by Anonymous Coward · · Score: 0
      That don't change anything.

      For God's sake, it's doesn't you bloody moron.

    18. Re:I think Linus is right by pinky0x51 · · Score: 1

      >Yes, there will be Vendors that use GPL-Soft and forbid changed and therefore unsignd binarys to execute on there Hardware.

      And because the idea of GPL is that nobody should have the power to forbid you this things GPLv3 will close this hole.

      >but sometimes there are good reasons for this behavior that benefit the Custumer. Think on Mission-Critical Hardware that should NEVER execute hacked binarys - in your best interest.

      This will be possible with GPLv3.
      You are free to use trusted computing hardware and DRM in your office to run only software signed by you. But you (the owner, the big boss of the company) must have the freedom to run modified versions if some business processes have changed. And i think it's also in his interest to controls his own IT infrastructure.
      The GPLv3 doesn't allow that the manufacture of the "trusted computing hardware" sells you the hardware with the software and now you are not able to adapt the software to your new business processes even if the license of the software say that you can do it.

      That's the same mistake like Linus does with his voting-machine-example. The state (call it state A) will be able to use DRM voting machines with DRM technology to ensure that on all voting-machines runs the right software. But if state A sells his voting-machine to another state (call it state B) he have to give state B all he needs to control his voting-machine like state A did.

      The freedom of you as a user is never restricted it just ensures that everyone who gets this machines too will have the same freedom.

      --
      Support Free Software! Join FSFE's Fellowship: http://fellowship.fsfe.org
    19. Re:I think Linus is right by Stephan+Gitz · · Score: 1
      Yes, there will be Vendors that use GPL-Soft and forbid changed and therefore unsignd binarys to execute on there Hardware.

      And because the idea of GPL is that nobody should have the power to forbid you this things GPLv3 will close this hole.

      But should we fight this fight with the GPL? We see with Tivo that a) Enterprises lock there Hardware b) the same Enterprises bring the Software forward because the GPLv2 force them to published their changes of the code. Maybe it is in the short term better to force Hardwarevendors not to lock their Hardware, but will it be better in the long term?
      I don't think so. The Hardwarevendors that want lock there Hardware will simply use BSD and the GPL-Software will evolve slower. But when the GPL don't forbid to lock the Hardware, the Vendors help to evolve the GPL-Software although you can't use your own binary on their Hardware. But remember, no one will force you to buy their Hardware and they alienate their Community.

      And i think it's also in his interest to controls his own IT infrastructure.

      I think this too, and therefore i think that there is no need for the DRM-Part in the GPL. Let the stupid Vendors lock their Hardware while they need to give Softwarechanges to the Community. As you say: there is an intrest to control the own Infrastructure. If the established Vendors lock the Hardware while using GPL-Soft, there will be new StartUps that grep the same Code that the established Vendors use, but put it in Hardware that give the Customer the ability to Control the Code. I belief that in the long Term the Customers will require the ability to Control the Hardware, because of the benefits that the Community will give them. If the established Hardwarevendors don't give you Hardware that you can control, there will be space for new Vendors that can grep the same Software and put it in Customer-friendly-Hardware.
    20. Re:I think Linus is right by pinky0x51 · · Score: 1

      >But should we fight this fight with the GPL?

      I think it's not the question if we shoud "fight" something.
      It's a more a question about what is the idea and the aim of the GPL. And the idea and the aim of the GPL is to give all users all 4 freedoms. To protect this idea and this aim we need a DRM clause in GPLv3 because that's the only way GPLv3 will be able to practice it's idea and aim in the age of DRM and DMCA. What 20 years ago was the copyleft clause to protect the idea and the aim of the GPL is today the DRM clause.

      >Maybe it is in the short term better to force Hardwarevendors not to lock their Hardware, but will it be better in the long term?

      Maintaining users freedom is always better in the long term.

      >But when the GPL don't forbid to lock the Hardware, the Vendors help to evolve the GPL-Software although you can't use your own binary on their Hardware.

      What is the advantage if i can read the source but doesn't have the freedom to control my software and my device?

      Maybe you see it more from the view of an engineer. You want to see the code and want to tinker with it, even if you can tinker just on a piece of paper because their is no device which will run your new version.
      But the view of GPL is the view from the user which life depends more and more on technical devices and software. The GPL wants that this user have always the full control over this part of his life. That's not a academical question from the view of an engineer but a rather practical question which needs practical answers. And a answer like "Buy a PC make use of your freedom to modify the software and than by another PC on which you can hopefully run the code because your first PC will deny your freedom to run your version of the software" isn't really a practical answer.

      >But remember, no one will force you to buy their Hardware

      Who will guarantee that i will always have a choice? What device could i buy to run my modified Tivio Software? What option will i have if all PC's come with TPM and DRM.

      Even if your are right and their will always be one vendor with alternative hardware. Will this hardware be able to do the same job like the other hardware? Will this hardware really run all the different software which is installed on the locked devices? Will i be able to use this hardware together with my "un-trusted" software to participate the the digital culture, make bank transfers, etc.?

      Even if all this answers are positive, but i don't believe that you can give me this positive answers for the complete future. This doesn't explain why a license designed to give users freedom and protect users freedom should maintain holes through which other can remove this freedom? I think such a license would be a lie to all people who choose the GPL with the trust that the GPL is a license which gives and protect freedom.

      --
      Support Free Software! Join FSFE's Fellowship: http://fellowship.fsfe.org
    21. Re:I think Linus is right by Blakey+Rat · · Score: 1

      And then they'll make a law that the police can torture anybody who gets pulled over for speeding! Then they'll make a law that all video games must be about either Strawberry Shortcake or Barney the Purple Dinosaur! Then they'll pass a law that only Vespa scooters can use freeways!

      Seriously, how about we design a GPL for the real world instead of your paranoid fantasies?

      Then again, this site is full of people who think RFID tags, glorified bar-codes, are going to let the government track their underwear when they go through metal detectors.

    22. Re:I think Linus is right by init100 · · Score: 1

      I for one run Ubuntu and Debian and all my binarys are signed. And i would use signed Bankingsoftware to.

      Those are not the same types of signatures. The Unbuntu/Debian/whatever package signatures do not require hardware to operate, because they only exist to protect you from getting rogue packages. You decide what repositories to use. A signed banking application would exist to assert to the bank that you are not running unapproved software. In this case, you are left out of the loop, the bank is in charge here. And if the bank does not provide a Linux version, say hello to Windows,

      Of course you could change to another bank, if there exists a bank that support your system.

    23. Re:I think Linus is right by init100 · · Score: 1

      You will not forced to run a 100% signed System to used DRM-caged-services.

      How can the DRM-caged service trust your system if there is no chain of trust from the hardware to the banking application. How can the service know that your untrusted kernel does not subvert the trusted application? This is why unbroken chains of trust are required for "trusted computing". Your kernel needs to be signed (not by you, say goodbye to running modified kernels), your operating system libraries need to be signed (OS libraries are used by applications to interface with the kernel) and the application need to be signed. Only then can the DRM-service owner trust your system to enforce his will (and not yours).

    24. Re:I think Linus is right by init100 · · Score: 1

      If the GPL is a place to stop other People from doing stupit things

      The GPLv3 isn't there to stop people doing stupid things. Exhibit A: It does not stop people from buying hardware with proprietary software, which Mr Stallman certainly thinks is stupid. No, the added restrictions in the GPLv3 are there to stop vendors from subverting the license. If I write a piece of software and release it under the GPL, I want everyone to have the freedoms granted by the GPL, even if they didn't get the software directly from me. I don't want anyone to benefit from my software while at the same time removing the freedoms I granted to the world when I released said software under the GPL.

      If someone want to only allow signed/trusted binaries to run on their hardware, fine. I'm not going to stop them from writing their own code. But they are not allowed to use my code to further this goal. I want all users of my software to have the freedoms granted by the GPL, including those who get it preloaded on an appliance. If the vendor wants to save money by using my code, fine, but then they have to grant their users all the freedoms granted by the GPL. This includes replacing the preloaded software with modified software, and still be able to run it properly.

    25. Re:I think Linus is right by init100 · · Score: 1

      you can run DRM-Software on TOP auf your OpenSource-OS that get a "secure" environment for there Content from your Hardware.

      This is incorrect. Applications do not interface with hardware directly, it does so through the operating system libraries, which interface with the kernel, which interface with the hardware. Each of these components have to be signed to create a chain of trust, so that the DRM software can be certain that the DRM is not subverted by the system kernel or OS libraries.

      So you might be able to run free software applications on a "trusted system", but you cannot use untrusted OS libraries or untrusted kernels if you want (or have to) use some "trusted" application. And when you cannot modify the operating system below the applications, you are no longer really running a free software system.

    26. Re:I think Linus is right by Stephan+Gitz · · Score: 1
      Your kernel needs to be signed (not by you, say goodbye to running modified kernels), your operating system libraries need to be signed (OS libraries are used by applications to interface with the kernel) and the application need to be signed.

      Sorry, this is wrong. TCPA lies in the HARDWARE and Prozesses can get an encryptet environment from the TCPA-Hardware. You can run your own modified Kernel with your own modified Desktopenvironment and on top of this you can execute a signed Programm that get a "secure" enviroment from the Hardware.

      Please inform you how TCPA works:
      http://www-128.ibm.com/developerworks/power/librar y/pa-cellsecurity/
    27. Re:I think Linus is right by init100 · · Score: 1

      TCPA lies in the HARDWARE and Prozesses can get an encryptet environment from the TCPA-Hardware.

      In every current desktop OS, applications never interface directly to the hardware, they do this through the OS libraries and the system kernel. Why would applications suddenly start interfacing directly with hardware now?

      Security hardware would need drivers, just like any other hardware. This is to hide the details of how the hardware works from the application programmer. And then we have the different CPU privilege levels required by different classes of instructions. For applications to interface directly with hardware, the CPU instructions to do this would need to work even in the least privileged CPU mode. Otherwise, access to security hardware would require involvement of the kernel, which would need to be trusted in this case. And since applications never interface with the kernel directly, the OS libraries would need to be trusted too.

      Please inform you how TCPA works:

      I could not find a single word about how applications are going to interface with the hardware. The article discussed the concept, but details about how this would work were conveniently left out.

    28. Re:I think Linus is right by Stephan+Gitz · · Score: 1
      In every current desktop OS, applications never interface directly to the hardware, they do this through the OS libraries and the system kernel. Why would applications suddenly start interfacing directly with hardware now? Security hardware would need drivers, just like any other hardware. ... Otherwise, access to security hardware would require involvement of the kernel, which would need to be trusted in this case.
      Again: Please inform you how TCPA works.
      Yes, the Kernel needs an interface to communicate with the TCPA-Features of the Hardware, but the Kernel don't need to be signed. The DRM-Application can test if it talk to the Processor, or to a imposter because of the key in the TCPA-Modul that is signed from the Hardwarevendor. Yes, the DRM-Application speaks with the OS-Interfaces and the OS-Interfaces talk to the TCPA-Module, but there is an encrypted End-to-End-Tunnel from the the Hardware to the DRM-Software. The DRM-Software can see that the public key from the TCPA-Module is signed from the Hardwarevendor, and the initial data from the application will be encryptet with this public key and therefore the Data can only decryptet by the private-key that lies in the Hardware. In this secure Chanel they generate a AES-Session-Key to encrypt the Data for the following Session. The only kernel you can build, is a Kernel that can copy the ENcryptet Data in some Datafiles, but every Datastream will encryptet with an new Session-Key, and so you can work a couple million years to decrypt a single session.

      You can only make a Kernel that can get the Mediastreams UNencrypted outside the Processor, if you have the signing-key from the Hardwarevendor, and you can bet that this key lies on a networkless PC behind steel-reinforced doors.

      TCPA will not kill Open-Source-Software and even on your 100% selfbuild Linux-from-Scratch you will be able to run DRM-Software that enables you to watch the newest Hollywood-Blockbuster - if you wish. The "only" thing that TCPA will bring, is that the big player from the Content-Industrie will put all their Content in encrypted bottles that you can only open with DRM-Software and TCPA-Hardware. This can be seen as a social problem, but it has nothing to do with render you unable to run your own software on a TCPA-Hardware. The social problem with DRM and TCPA can only be solved by law, or if the Community build enough open content.
  45. Re:Sure to happen by Ohreally_factor · · Score: 0, Offtopic

    I see the FSF priests are out in full force this morning. The guy who makes unsubstantiated accusations that Linux has sold out gets passed over, but I get modded as a troll.

    --
    It's not offtopic, dumbass. It's orthogonal.
  46. Re:Sure to happen by Pecisk · · Score: 0

    Maybe he just suggests to vote with your wallet? Don't buy DRMed computers, media, hardware, etc. And be control of your...emmmm...you got something?

    DRM is reality, like it or not. You can vote against it actually *buying* computers with no DRM and inform people around you who are not very tech-savvy about subject do the same. Simple.

    Stallman simply does the right thing in wrong way, period. I agree with idea, always had, bad not with methods. GPLv3 is actually not a right way of doing it.

    --
    user@ubuntubox:~$ stfu This server is going down for shutdown NOW!
  47. Alas, I have no mod points by NickFortune · · Score: 1, Funny
    it's nevertheless Shakespeare who gets remembered in the history books.

    Don't you mean BACON/Shakespear?

    Sorry, couldn't resist :)

    With that out of the way, I thought that was nicely put. I was an applications and systems coder, and that was exactly my experience.

    --
    Don't let THEM immanentize the Eschaton!
  48. Forget RMS and L****s. License how you want by ishmalius · · Score: 2, Insightful
    I personally have no concern about what one weird guy or the other thinks. I will use whichever license fits into my intentions for my code. I personally almost like the idea of anti-DRM. Why? If I am generous enough to let you use my code, then it would be unfair for you to use my code to be selfish to others. Simple as that. But beyond that, I really don't care. All I really want is the basic tenet of GPL: if I give it to you and you use it, then you should be willing to do the same for others.

    Remember, GPL does not take rights away. It starts with the premise that you have no right at all to use my code. It then gives you generous rights under easy conditions. Not bad, really. If a person thinks that GPL is too onerous, then he does not need to use it. Remember, it's my code.

  49. what? by sentientbrendan · · Score: 1

    >Without the DRM provisions in the GPLv3 that Linus is complaining about,
    >we could eventually face a situation where it is literally impossible to
    >develop FOSS for the latest generation of computers.

    How does that follow? Think clearly. If OSS doesn't work with DRM, it's not like that forces anyone to not use DRM. It just causes people to choose software under a different licence. Realistically, if someone wants to only run signed software, they can always go with proprietary software.

    In general, my impression of the FSF is that they are idealists and are either unconcerned or unable to deal with the practical realities of the software business. Thankfully, we have people like Linus Tolvalds who *are* concerned with making OSS that people in the real world will be able to use.

    1. Re:what? by mrchaotica · · Score: 1
      How does that follow? Think clearly. If OSS doesn't work with DRM, it's not like that forces anyone to not use DRM. It just causes people to choose software under a different licence. Realistically, if someone wants to only run signed software, they can always go with proprietary software.

      STOP WITH THE FUCKING FALSE DICHOTOMY!

      The object is not, and never was, to "force" anyone not to use DRM. The object has always been simply to not help them to use DRM by refusing to let them abuse the privilage of using Free code!

      Maybe the GPL v.3 will stop the tide of DRM, and maybe it won't. But those of us who actually care about our freedom at least don't want to contribute to our own opresssion!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    2. Re:what? by DrJimbo · · Score: 1
      sentientbrendan said:
      If OSS doesn't work with DRM, it's not like that forces anyone to not use DRM. It just causes people to choose software under a different licence. Realistically, if someone wants to only run signed software, they can always go with proprietary software.
      Let me explain. First of all, the proposed GPLv3 will not prohibit people from using DRM. If people only want to run signed software there is nothing in the GPLv3 that would prevent this as long as it is the computer owner, not the manufacturer who makes this choice.

      You are correct in that no FOSS license can force manufacturers to do or not do anything. If manufacturers choose to only make treacherous computers (where they have total control over what software we are allowed to run on our own computers) there is nothing we can put into our licenses that will stop them directly.

      The most we can do is make it illegal for them to use our software in these treacherous computers. If there is a substantial body of useful software that is licensed under the GPLv3 by the time treacherous computers are ready to hit the marketplace then manufacturers will at least have some incentive to continue to make non-treacherous computers.

      You can make a grid of all the possibilities: GPLv2 vs. GPLv3 and various degrees of treacherous computing market penetration. Even though the DRM provisions in the GPLv3 are not a magic bullet that will force manufacturers to not sell treacherous computers, I see no case where it benefits the FOSS community to choose the GPLv2 over the GPLv3.

      I don't understand why any FOSS developer would want our software to run on machines that we can own but not control. Once all computers become treacherous computers, FOSS is dead. I agree with you that our choice of license cannot directly stop them but this is not a good reason to make it easier for them. If they want to take away my ability to choose what software runs on my computer and if they want to prevent me from modifying the software that runs on my computer then I'm going to make it as difficult as possible for them to do this. Why make it easier for them?

      --
      We don't see the world as it is, we see it as we are.
      -- Anais Nin
    3. Re:what? by init100 · · Score: 1

      But those of us who actually care about our freedom at least don't want to contribute to our own opresssion!

      Well said! I couldn't have put it better myself.

  50. Re:Wow, you missed the whole point of the DRM clau by the_womble · · Score: 2

    So you make money by re-selling other people's code with a little bit of work done on it? I am sure it works well for you, but how well does it work for the people whose code you are using? How do they make money?

  51. Linus did not get a fair interview by hansreiser · · Score: 1

    While I suspect I disagree with Linus on this topic, I think the journalist did not do a good job of portraying Linus's views in a way that best brings out his argument and that argument's strongpoints. Though of course, if I know that Linus did not get a fair opportunity to project his arguments at their best, then maybe I know that I don't know whether I would agree with Linus.....

  52. Re:The GPL needs to go by RenoRelife · · Score: 0

    I read this in shock and awe. I guess you could say I was dumbstruck by a dumb*uck.

  53. Re:Wow, you missed the whole point of the DRM clau by nacturation · · Score: 2, Informative

    I am sure it works well for you, but how well does it work for the people whose code you are using? How do they make money?

    They've chosen to not make money from the code by releasing it under the license they have. If their goal were to make money from the code, odds are they wouldn't have open sourced it.

    --
    Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
  54. The situation by Mendy · · Score: 4, Insightful

    ...that I can see justifying the extra clauses in V3 is one where all the major computer manufacturers decide that their computers will only run those operating systems that are certified with them. Businesses might not object to this (if it was sold as having "security benefits") and so there wouldn't be enough of a market for people who wanted to run their own versions to justify a new "GPL Friendly" hardware company, at least not with the resources that Intel/AMD have at their disposal. The problem with attempting to use the GPL to rememdy this problem is that if the hardware manufactuer is building a check into the hardware but shipping the hardware without the software then the GPL probably doesn't apply to them. It might apply to any OEM shipping Linux with the hardware but I'm sure they'd get round the legal problems by making a click-through that put the responsibility for the combining of the two on to the end user.

    For the other lesser cases where there isn't such a barrier to entry I don't see that there's a problem. If someone makes a DVD player that is unmodifyable and publishes the source of it's operating system then if there's a market for a modfiyable one a competitor can simply take the published source and build a competing product. There can also be some legitimate reasons to prevent people from modifying software - "If the work communicates with an online service, it must be possible for modified versions to communicate with the same online service in the same way such that the service cannot distinguish." - sounds to me like it would be impossible to make a GPL'd game that did any kind of hacked client prevention.

    I think a likely outcome of all this is that any hardware manufacturer who would be likely to fall foul of these clauses will simply switch to using a non-GPL operating system, commercial or BSD and consequently Linux will miss out on contributions to infrastruture such as embedded cpu support that it might otherwise have recieved. The MPAA (or whoever it is who controls it) may also choose not to grant licences to hardware manufactuers who produce devices can run modified code that they fear could be used to circumvent their DRM.

  55. Re:Has Linus sold out? (was: Re:I can see both sid by Ohreally_factor · · Score: 1, Interesting

    Man! The knives are out! Is there anything to which you won't stoop? Character assassination because a respected member of the community disagrees with you? The ends invariably justify the means with you types. Anyway, thank you for revealing the true colors of the FSF goon squad.

    --
    It's not offtopic, dumbass. It's orthogonal.
  56. Re:Sure to happen by Anonymous Coward · · Score: 0
    I see the FSF priests are out in full force this morning. The guy who makes unsubstantiated accusations that Linux has sold out gets passed over, but I get modded as a troll.

    Don't let that stop you making unsubstantiated accusations about the moderation or claiming innocence whilst you're agenda and bias are perfectly obvious. I'm proud to be a troll, you appear to be in denial!

  57. Flame war indeed. by Ohreally_factor · · Score: 1

    It took me a few hours to figure it out, but the article and its posting here, as well as a large number of posters are part of a campaign to discredit Linus for having the audacity to dissent with RMS and the FSF. Look at the timing. Look at the volume.

    Try browsing at a lower threshold, and see how much dissent is being modded down.

    --
    It's not offtopic, dumbass. It's orthogonal.
    1. Re:Flame war indeed. by arose · · Score: 1

      I have one question: troll or paranoid? P.S: Remeber bitkeeper!

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
  58. "vote with your wallet" doesn't work by H4x0r+Jim+Duggan · · Score: 3, Informative

    Issues such as DRM cannot be tackled by consumer choices in the market. There are two reasons.

    First, the market is not granular enough. The consumer will never be given the choice of DRM'd CDs vs. DRMless CDs. The options are decided by marketing teams, and they will give consumers choices such as DRM'd CDs or nothing.

    Secondly, like a mutual-loss based price war between two companies where the rich one waits for the poorer one to run out of funds, in this battle, if the consumers ever lose, there is no way back. Once DRM is pervasive, consumers no longer have any way to leverage the DRMers. If an ISP wants people to accept worse service, they have to offer something (such as a lower price) constantly. If a company wants consumers to accept DRM, they just have to get consumers to accept this once and to purchase DRM'd hardware (and they do this by leveraging a tangental market, such as the content industry), and then there is no way for the consumer to roll this back.

    1. Re:"vote with your wallet" doesn't work by Millenniumman · · Score: 1

      The consumer does have the choice of DRMed CDs and DRMless CDs right now. And they could go without CDs if they cared enough about DRM.

      If people stop buying the product, it will hurt the company. So what if they buy DRMed hardware once? They can still get DRMless hardware.

      If DRM isn't stopped by consumer choice, it will be because most people don't care.

      --
      Stupidity is like nuclear power, it can be used for good or evil. And you don't want to get any on you.
    2. Re:"vote with your wallet" doesn't work by mrchaotica · · Score: 1
      They can still get DRMless hardware.

      Yes, for now, but that choice is being removed as we speak.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    3. Re:"vote with your wallet" doesn't work by kevlarman · · Score: 1

      the problem is that most people don't understand the issue of DRM. let's say that you got all the GNU/Linux,BSD, and Mac users along with every single programmer in the US (i'm being as generous as i can here) to stop buying DRM'ed music, the music industry probably wouldn't even notice, or worse they would blame it on internet piracy and point to it as the reason that they _have_ to put DRM on their music. try explaining to joe shmoe how evil DRM is after that.

      --
      A mouse is a device used to point to the xterm you want to type in
    4. Re:"vote with your wallet" doesn't work by sheldon · · Score: 1
      First, the market is not granular enough. The consumer will never be given the choice of DRM'd CDs vs. DRMless CDs. The options are decided by marketing teams, and they will give consumers choices such as DRM'd CDs or nothing.


      Obviously written by someone who does not know where the word DIVX originated from.
    5. Re:"vote with your wallet" doesn't work by Millenniumman · · Score: 1

      That doesn't mean "vote with your wallet" doesn't work. It means that most of the "voters" will support DRM out of apathy.

      --
      Stupidity is like nuclear power, it can be used for good or evil. And you don't want to get any on you.
    6. Re:"vote with your wallet" doesn't work by aichpvee · · Score: 1

      "If an ISP wants people to accept worse service, they have to offer something (such as a lower price) constantly."

      Not so, comcast has a monopoly here and DSL speed and pricing are both poor. All they have to do to make people accept worse service is lower the quality of the service and keep the pricing better than 1.5mbps and south of 80$/month.

      --
      The Farewell Tour II
  59. Multimedia by 5937 · · Score: 1

    "At worst case scenario, you won't be able to run certain propriatary apps when running nonDRMed stuff. big deal, sounds like your don't want to run them anyways."

    Having multimedia or not makes or breaks a desktop today.

  60. Re:Has Linus sold out? (was: Re:I can see both sid by quentin_quayle · · Score: 1

    My post is not an attack on Linus, it is only raising a question. I just want to know why he avoids one crucial issue.

    "you types" and "true colors of the FSF goon squad"? That is the stuff of trolls. I agree with RMS/FSF on this one issue, but not everything, and I don't think my post shows any evidence of fanaticism.

    BTW, if you interpret my post as an attack then you are implicitly agreeing that a world of all-DRM hardware would be a bad outcome. Otherwise you would not take it as imputing a negative quality when I ask whether LT favors that outcome.

    It is a legitimate question. Does Torvalds really think there is no likelihood of the TC scheme making general-purpose programmable PCs hard to obtain or use? This seems to be his premise but it is refuted by the abundant facts and he has not made any argument for it. Or does he think that is an OK scenario? Either way I just want to know which side he is on, and so do others.

  61. how this is related by H4x0r+Jim+Duggan · · Score: 1

    Linus said that the whole public consultation process was a sham and that he heard that FSF ignored all the input from the discussion committees. He even said that this annoyed him more than the DRM stuff. I think it was on ZDNet.

    So this article shows what the discussion committees actually think, instead of what Linus says he heard they think.

    I'm not saying he misreported this intentionally. Maybe some people with an agenda sought him out and casually mentioned their frustration to him at the water cooler. I don't know.

    1. Re:how this is related by Ohreally_factor · · Score: 1

      This story broke on Groklaw, because someone posting as Linus was outlining his supposed objections to the GPLv3. It turned out that it really was Linus. Other reports came after, when reporters asked him to confirm his words.

      His main objection was to the provisions that prevent the use of signed binaries. He said that the section outlining DRM was a red herring. And he also expressed frustration at what he saw as a railroaded process. Overall, he outlined his philosophical differences with the FSF.

      So, to claim that his criticisms have been refuted is a half truth at best. More like a third truth.

      --
      It's not offtopic, dumbass. It's orthogonal.
  62. Certificates by 5937 · · Score: 1

    "There will be a way to sign your own code against this DRM."

    Today with the web, for a good certificate you have to pay a money.
    Else your webpage lacks some functionality.
    Now getting a good certificate for software is a lot more work, all this testing at $os-vendor..
    $bigcorp can pay, $me can not.

  63. What if any is his affiliation with Transmeta now? by D4C5CE · · Score: 2, Insightful
    it's another thing entirely to actively cheer on the introduction of DRM, which Torvalds has been doing now for a couple of years. Doesn't Linus realize that with strict hardware controls enforcing what may and may not be run, one's freedom to tinker may disappear?
    Was he free to criticize platforms locked into Digital Restrictions Management while working for a company that helps build them (most recently FlexGo for Microsoft BTW) ?

    Does he still have relevant ties to (t)his (former?) employer during/after "a leave-of-absense [sic]" ?

    These are questions that any serious reporting on his stance needs to ask and answer - before questioning the merits of GPLv3 (that would make perfect sense for Linux anyway) just because the FSF cannot get Linus Torvalds to fully and openly agree with it (yet).

  64. Re:Sure to happen by tomhudson · · Score: 1, Insightful

    The ONLY thing that will prevent the proliferation of DRM is the consumer not buying it.

    As long as there is a demand for non-drm hardware, manufacturers WILL make it, because they can make money off it.

    Linus has stated that this is a 20-year battle, not something that can be resolved in a day. Its not going to change just because of the GPLv3 - that only affects software. The problem is hardware, not software. Vote with your wallet, and if a significant number of people do, then non-drm hardware remains available.

    You have only yourself to blame if you own an iPod, or pay to download drm'd music. You've already voted with your $$$, saying "I'll buy drm'd shite"

    Fucktards. You can't have it both ways. You can't go and say "oh, drm is BAD" and then get all weak-kneed and gooey-eyed because you want your drm'd music. All you iPod-toting freaks have whored yourselves out, and real cheap too ... 99 cents.

    Its like the guy who sees a pretty woman:

    Man: Would you sleep with me for a million dollars?
    Woman: Wow, sure!
    Man: How about for a buck?
    Woman: What kind of woman do you think I am?
    Man: We've already established that with the first question. Now we're just haggling over price.

    If its bad, boycott it at the consumer level. Vote with your wallet. THAT will fix the problem. (Hint: Ask Sony about how well their r00tkit program went).

    Same with Windows. Don't want vendor lockin at the OS level? Don't support Microsoft or Apple, because they're pushing for it. The hardware vendors don't give a damn one way or another ... they'll make anything the market wants.

    But don't go around throwing rocks at Linus for pointing out that all you iPod-toting Windows weenies are emperors without clothes, and that the GPLv3 doesn't get to the root of the problem, which is the choices that YOU as a consumer make.

  65. Re:Has Linus sold out? (was: Re:I can see both sid by Rogerborg · · Score: 1, Insightful

    How can someone who has never bought in sell out?

    The apparent belief that GPL3 will somehow prevent crippled hardware from becoming the only thing available is ludicrous. Linux is and will continue to be GPL2, and there's no compelling reason to open hardware to accomodate any other software. Moglen's nastygrams don't provide enough of a disincentive to just steal Free software, if it comes to that.

    As I see it, it's not Torvalds who needs to justify his position, it's you. You won't, of course, because you're so deep in cognitive dissonance that you can't acknowledge that the FSF is still drawing up battle plans when it's already lost the war. When the first beta of a Windows version that requires TC hardware is released, you may try to sue for peace, but by then it will be far too late.

    --
    If you were blocking sigs, you wouldn't have to read this.
  66. Re:Has Linus sold out? (was: Re:I can see both sid by Rogerborg · · Score: 1

    If you insist on a childish framing of the issue into "sides", then Linus defines his own side. Are you with him or not?

    --
    If you were blocking sigs, you wouldn't have to read this.
  67. no, his main objection wasn't DRM by H4x0r+Jim+Duggan · · Score: 1

    Nope. I've done my homework on this one.

    Linus's statement, which this article shows to be incorrect, was: "The real problem was always the re-definition of source code. Actually, I take that back. The real problem was and is that there are lots of people who disagreed with the FSF on issues (mine was the definition of source code, while I know that some commercial entities felt that the patent language was totally unsupportable). And the FSF took that input, and then totally ignored it."

    1. Re:no, his main objection wasn't DRM by Ohreally_factor · · Score: 1

      Here is his entire statement, from which you merely took a part:

      DRM "Misunderstood"
      Authored by: Anonymous on Thursday, July 27 2006 @ 07:11 PM EDT
      ----------
      I'm pretty sure I didn't misunderstand anything at all.

      A lot of people are confused by the DRM issue, and the problem comes mostly from the organization of the first GPLv3 draft itself. It had a section on DRM, and that section is totally irrelevant and has almost no semantic content.

      (In the new draft, the DRM section has been renamed to talk about users' rights instead, but it's still the same case - that section isn't actually the interesting one).

      The real anti-DRM thing is the new and bogus language in section 1 - the definition of "source code". That is the true change in both the previous and the current draft, and that's my personal beef.

      The fact that they had a separate (and largely boring) section called "DRM" was never the issue, and was (and is) a total red herring. The real problem was always the re-definition of source code.

      Actually, I take that back. The real problem was and is that there are lots of people who disagreed with the FSF on issues (mine was the definition of source code, while I know that some commercial entities felt that the patent language was totally unsupportable). And the FSF took that input, and then totally ignored it.

      So as far as I can tell, the whole GPLv3 "process" has been a sham from the very beginning. Eben and Richard talk about "discussion drafts", but it's not "discussion" if you don't actually care what the other side says. And Richard most definitely doesn't care (Eben probably does, but has no actual say in the end result).

      So forget about this whole "community input" thing. Input has been given, and then duly ignored.

      Oh, well. At least that's how I've seen it, and maybe that explains my disillusionment with the GPLv3.

      Linus

      His second posting:

      DRM "Misunderstood"
      Authored by: Anonymous on Thursday, July 27 2006 @ 08:18 PM EDT
      ==============
      I tried to explain my own disagreement with the GPLv3 in a number of emails to the linux kernel, but obviously haven't been uniformly successful.

      And yes (responding both to you, and to another poster), I realize that input has been taken on the drafts, but all the changes I've seen have been about largely stylistic issues - wording changes, things like that. I don't think any input on any really fundamental disagreement has been really on the table.

      Now, I also realize that that is probably exactly what the FSF was going for. Rms had a vision for what he wanted the GPLv3 to say, and it says that, and then they are open to modifying details. Fair enough, and I'm not fighting the GPLv3 changes per se. I'm just telling people why they are bad changes for me, and why I think they are bad changes for most other projects too.

      I'll try to explain it once more, usign the analogy that seems to have been the most effective so far with some people. To me, the GPLv2 has always been about "quid pro quo", ie I want people to pay me back in kind. There are other issues (and many of them I think end up being the reasons why it has been so successful), but that "quid pro quo" is why I started using the GPL, and I think it's a very fundamental thing. It's also - to me - very fair. I give source code out, you can repay in kind.

      Now, the difference between "quid pro quo" and the FSF stance is that in many ways, the reason for the GPL as far as the FSF is concerned was never "fairness". It was all about a higher calling, and about something that the FSF thinks is much bigger - "freedom".

      And I disagree. I think that "freedom" is fine, but we're not exactly talking about slavery here. Trying to make it look like we're the Abraham Lincoln of our generation just makes us look stupid and stuck up. I'd much rather talk about "fairness" and about issues like just being a much better process for generating better code, and having fun while doing so.

      And the th

      --
      It's not offtopic, dumbass. It's orthogonal.
  68. linus, shame on you. by tsoflash · · Score: 1

    Richard Stallman and team built the guts of the os's know as linux over a period of 22 YEARS. Linus built a kernel, like every Computer Science major must. Linus puts it out on the net - others combine it with Stallman's project (Stallman was working on a more difficult memory manager architecture) and then comes a working GNU - Unix like OS - (now known as Linux) that Stallman and his teams had been working on for years. Let's face it. Linus received the credit instead of Richard Stallman for a gargantuan effort. Not to debase linus efforts, but that guy is taking credit for a lot of other peoples work. Richard Stallman - Free Software foundation - http://www.gnu.org/ Linus Torvalds - A Kernel - needs $$$

    1. Re:linus, shame on you. by Anonymous Coward · · Score: 0

      YOU ARE TEH FUNNAY!

    2. Re:linus, shame on you. by Anonymous Coward · · Score: 0

      You're a dope.

  69. A spelling troll appears! by Anonymous Coward · · Score: 0

    What do you do next?

    kiss
    touch
    ->put it in

  70. Refuted? by nwbvt · · Score: 2, Informative

    Thats some pretty strong language, and isn't at all appropriate for this discussion as it primarily involves opinions rather than facts. Linus disagrees with the direction GPLv3 is taking, which is his right to do. To 'refute' those comments, you would basically have to prove he has no problem with GPLv3.

    Who the hell wrote this article, Richard Stallman?

    --
    Mathematics is made of 50 percent formulas, 50 percent proofs, and 50 percent imagination.
    1. Re:refuted? by thegnu · · Score: 1

      seems like you mean rebutted.

      I categorically refute everything you have to say.

      --
      Please stop stalking me, bro.
  71. wrong by m874t232 · · Score: 2, Interesting

    But so far it's been Linus who's done the most to actually change the world.

    No, he has not. All Linus did was write a kernel. If he hadn't done so, there were half a dozen alternatives about to become available. Most likely, if Linus had been run over by a truck, we'd be running the BSD kernel now, or some Mach derivative.

    Proving once again the superiority of actually getting working technology out the door, versus spending a decade or so fine-tuning your philosophy about how to begin working on the great technology that you will eventually design when you have the philosophy just perfect (if everyone hasn't succumbed to old age first).

    That charge is totally unfair. GNU released plenty of software long before the Linux kernel was created. And the reason development on the microkernel went slowly was not because of any "fine tuning of philosophy", it was because porting and cleaning up a large, existing microkernel codebase and giving it POSIX APIs was a big project that needed to be completed in one big development effort and required the PC industry to start delivering hardware capable of running it. Linus instead delivered a flaky and incomplete kernel that became popular because it ran on PCs right away, but that required many years to beat into shape.

    I've had enough troubles in my own career directly traceable to wanting to Get Things Right at the expense of Getting Things Done to appreciate this particular point with some sensitivity, not to say bitterness. Feh.

    You're right: getting code out the door, even if it is inferior quality, is clearly generally good for companies and developers. It's not good for users or the community. What happened with Linux vs. Mach was somewhat analogous to what happend with DOS vs. UNIX: the quick and dirty hack won, and users ended up paying the price. Fortunately, because Linux at least copied proven UNIX APIs, the Linux cleanup avoided most of the pain that have accompanied analogous evolutions at Microsoft and Apple.

  72. Re:Has Linus sold out? (was: Re:I can see both sid by Ohreally_factor · · Score: 2, Interesting

    He's written pretty extensively on this issue. He does not see the threat of totalitarian Trusted Computing happening. I happen to agree. This is a paranoid fantasy put into your head by RMS and others to further their own agenda.

    You're calling me a troll? You're the one suggesting that Linus has sold out. I'm not even a big Linus fan, but I'm aware of his contributions and I have respect for the man. And it amazes me that you could even ask that question about him. It's really astonishing. How can you maintain it's an "honest question"? At best, it's a stupid and reckless question. At worst, it's a calculated smear. I just don't get how you people can impugn his integrity and at the same time, not question the integrity of RMS, well known for his demagoguery.

    Let me ask you this: In your mind, are there no good uses for trusted computing? Are there never circumstances where trusted computing could be applied without evil effect? Or is all trusted computing inherently evil and must be stamped out?

    --
    It's not offtopic, dumbass. It's orthogonal.
  73. refuted? by bitt3n · · Score: 1

    seems like you mean rebutted.

  74. Re:Sure to happen by squiggleslash · · Score: 4, Insightful

    Right, because we're going to get a choice.

    Like we did with DVDs. We can buy the DRM free hardware and DRM free DVDs of our favorite movies, or we can buy the DRM'd versions of both. Except we can't. Because in the vast majority of cases, the content we want is only available in a DRM'd form.

    With the greatest of respect, the argument that this can be dealt with by "consumers" is utter and complete crap. The choices that need to be available for consumers to deal with this issue are non-existant. In order for DRM to be dealt with, it has to be dealt with at every level. This means consumers avoiding it where possible. It means Free Software authors chosing licenses that ensure DRM proponents can't leverage the work of the Free Software community when building their content prisons. It means constant advocacy. It means lobbying politicians against DMCA like laws and in favour of liberalizations.

    No one single system is going to prevent DRM from taking hold. We already have one source of media, movies, now completely locked up by DRM schemes and where the only workarounds are illegal. This will spread. It will get worse. The laws are getting worse. Consumers are getting less choices. Companies like TiVo are benefiting from the same communities they're undermining, using GNU and Linux to create their products while simultaneously undermining the freedom of their users. For anyone to claim that this can be dealt with using one single simple solution "Duh, let market forces fix it! Consumers rulez, they are always informed enough to make the right choices and will always have the choices to begin with" is being desperately naive.

    And, personally, I cannot see how DRM is consistant with Free Software. The GPL is not the BSD license. It does take pro-active steps to ensure the software so-licensed remains Free. Allowing DRM would be a bug in the GPL, it's not something that can be allowed, because it amounts to a loophole. By all means, argue against these kinds of things being added to the BSD license, but there absolutely must be provisions against DRM in the GPL, otherwise the GPL ceases to have any meaning.

    --
    You are not alone. This is not normal. None of this is normal.
  75. Re:Has Linus sold out? (was: Re:I can see both sid by Anonymous Coward · · Score: 0
    The only way to verify that a set of source code purporting to represent the binary that is running, is really the binary that is running, is to compile from that source and run the new binary.

    You'll have to trust the compiler, then. Which means you'll have to ... umm ... wow ...

  76. Freedom to choose by Ben+Rigas · · Score: 2, Insightful

    I can see this from both points of view, but ultimately Linus has the freedom to choose what he wants to do. If you don't like his choice, don't use Linux anymore! If you are really a developer/user who cares that much about GPL v3, then go work on HURD.

    Isn't it hypocritcal to advocate freedom, while at the same time attempting to take Linus' freedom to choose away from him? You are welcome to disagree with him, but you should respect his right to choose.

    1. Re:Freedom to choose by Aim+Here · · Score: 1

      Who's attampting to 'take Linus' freedom to choose away from him?'. People are disagreeing with him.

      Criticism isn't censorship, silly. If it is, you've just censored us!

    2. Re:Freedom to choose by Ben+Rigas · · Score: 1

      I guess I didn't say it quite right in my original comment, nobody can take his freedom to choose away. It's more a matter of respecting his choices.

      There's nothing at all wrong with disagreeing with him. I just mean that if you do disagree, then why not be more constructive and build up something like HURD? Being excited about v3 and supporting projects that also support it will go much further in the long run, rather than beating up on Linus now.

  77. Re:Forget RMS and L****s. License how you want by maxume · · Score: 1

    The basic tenet of the gpl is 'If I give it to you and you use it, then you *must* be willing to do the same for others'. BSD is share-please, GPL is share-dammit.

    --
    Nerd rage is the funniest rage.
  78. Re:The GPL needs to go by Anonymous Coward · · Score: 0

    I'm not sure why the Grandparent a troll, our lawyers said the same thing.

    That doesn't mean they are RIGHT, but it is true that lawyers can somehow mistake the situation into that.

    I disagree with his "never suggest linux" diatribe, but if I didn't understand the situation, and just listened to our lawyers, i'd probably hold the same view too.

  79. But does it help? by pnambic · · Score: 5, Insightful

    As far as I can see it, DRM technology poses three distinct major threats to developers' and users' freedoms:

    1. locked digital media
    This is where the GPLv3 works, sort of. You cannot take a GPLv3ed media player, add some DRM component, and distribute the result while keeping the key that unlocks the media secret. That's fair. Unfortunately, there is a large range of non-GPLed media players available. In the end, FOSS users will still have to resort to hacks, but they're not worse off in that respect than they are now, and at least the code they worked on won't be used to prevent them from doing what they want.

    2. locked FOSS-using devices (the Tivo scenario)
    I think the FSF, and software developers advocating GPLv3, are seriously overstepping their bounds here. Basically, they're telling hardware developers that in order to use FOSS, not only do they need to give freely what they freely received (which is just reasonable), but they also have to make THEIR OWN product convertable to any use their customers see fit. This immediately excludes building devices that need to assure overall system integrity (from fair network gaming through to voting machines) and also excludes a number of fairly reasonable business models (hardware has a significantly non-zero duplication cost, unlike software, and the money has to come from somewhere). Alternatively, they can choose to make their machines physically tamper-proof (which defeats the intent of the license, makes the license unverifiable, and the product unrepairable in case of software problems). The net result will simply be that hardware developers will stop considering the use of FOSS, which will lead to them getting what they want anyway, FOSS code getting less exposure and less fixes, and end users receiving an arguably less technologically sound product at a higher price.

    3. locked general-purpose computers
    The GPLv3 can't do squat about thread 3. If such devices do indeed appear, they will simply not be running FOSS. Ever. Because even if a vendor would like to offer an OS based on some hypothetical GPLv3ed kernel, the license wouldn't allow it.

    So, looking at the above, I can't help but think that Linus is right here. I have the utmost respect for RMS and the members of the various committees, I'm even a paid-up and (CD-)card-carrying member of the FSF (#2342), but so far they have failed in providing a satisfactory solution to the problems ahead.

    Please prove me wrong.

    1. Re:But does it help? by Xtifr · · Score: 1

      > "1. locked digital media
      > This is where the GPLv3 works
      "

      Sort of. If someone wants to include a DRM'd player on an otherwise free system (including GPLv3), there's no problem. That's simply bundling. But yes, they would have to write the media-player component from scratch if they wanted it to have DRM. The rest of the system could be GPLv3 (or LGPLv3) though.

      > "2. locked FOSS-using devices (the Tivo scenario)
      > I think the FSF, and software developers advocating GPLv3, are seriously overstepping their bounds here. Basically, they're telling hardware developers that in order to use FOSS, not only do they need to give freely what they freely received (which is just reasonable), but they also have to make THEIR OWN product convertable to any use their customers see fit.
      "

      No they are NOT overstepping their bounds. The whole point of the GPL is and always has been to ensure that someone who receives the code has the same rights and freedoms as the person who provided it (not counting any additional rights reserved to the actual copyright holders). The FSF is simply telling hardware developers that they don't have any special additional rights to control the software (not their software, remember) simply because they are working in hardware rather than software. This simply puts the hardware developers on the same footing that software developers (such as me) have been on with respect to GPL'd software all along.

      The point of the GPL has always been to ensure an equal footing for everyone, rather than have separate classes of "developers" and "users". Everyone is potentially a developer. The TiVo model undermines that by making TiVo a privileged developer. The GPLv3 is merely closing a loophole that was never supposed to be there in the first place.

      > "The net result will simply be that hardware developers will stop considering the use of FOSS"

      Yes, and that's fine. Although I will correct that to say "SOME hardware developers". And that's no different from the fact that some software developers will not consider using FLOSS for similar reasons. The fact is that if hardware developers can't make money out of selling hardware, there's something wrong with them! Your arguments for hardware developers using non-free software make MORE sense for software developers than hardware developers. And yet, somehow, software developers seem perfectly able to use and make money off of FLOSS. Why are hardware developers so special? Why do they deserve their own privileged class with respect to FLOSS users/developers?

      Why should these hardware developers get special benefits from the hard work of an international community of software developers dedicated to the principle of sharing? Why should hardware developers, and hardware developers alone, be able to ignore the principles of sharing that everyone else is subject to? Why should hardware developers be able to sell me a copy of my code--code I wrote and licensed under the GPL--without allowing me to enhance/fix it, when I specifically released it under a license that was intended to prevent that?

      It seems to me that Linus (and you) are identifying too much with the hardware developers and forgetting the perspective of software developers! Let alone end users. Software developers have been learning to come to terms with the GPL for years (in my case, close to two decades). We've figured out how to go on making money even in an environment of freedom. Why are hardware developers so special that they don't need to go through the same process? And face the same alternatives (develop your own software from scratch, with all the extra work and insecurity that implies, if you don't want to share or play nice).

      Arguments about "more people will develop for/with free software if we simply don't insist that it be free" have always been stupid and always will be. (Although they are raised on a regular basis.) This is not, and neve

    2. Re:But does it help? by ghettoimp · · Score: 2, Insightful

      "This immediately excludes building devices that need to assure overall system integrity (from fair network gaming through to voting machines)"

      I don't see why it would prevent you from developing voting machines based on GPL'd code. I mean, who cares if Joe Hacker can see and make their own versions of the voting software, as long as he can't install it on the voting machines on election day. This is a social problem of having safeguards and procedures, not a question of open or closed sources.

    3. Re:But does it help? by pnambic · · Score: 1

      > I mean, who cares if Joe Hacker can see and make their own versions of the voting software, as long as he can't install it on the voting machines on election day. This is a social problem of having safeguards and procedures, not a question of open or closed sources.

      I don't worry about Joe Hacker the outsider, I worry about the people who legitimately have access to the voting machines. If they can install modified software on the machines without the machine ceasing to function, the integrity of the machine can be breached. The GPLv3 explicitly prohibits the manufacturer of the machine to make sure that that doesn't happen, in effect making a voting machine using GPLv3 software uncertifiable.

      Not to mention medical devices. Or devices that handle payment transactions, like this one (unfortunately in German only). Do we, as the Free Software community, go on record stating, "well, for this sort of thing, Free Software is just not the solution"?

    4. Re:But does it help? by dondelelcaro · · Score: 1
      2. locked FOSS-using devices (the Tivo scenario)
      I think the FSF, and software developers advocating GPLv3, are seriously overstepping their bounds here. Basically, they're telling hardware developers that in order to use FOSS, not only do they need to give freely what they freely received (which is just reasonable), but they also have to make THEIR OWN product convertable to any use their customers see fit.
      Didn't their customer purchase the product? Why shouldn't I as a consumer be able to modify a product that I've purchased to implement whatever fixes or features I want the product to run?
      This immediately excludes building devices that need to assure overall system integrity (from fair network gaming through to voting machines)
      This is actually not true (or at least, not the intention.) Being able to verify that you're running a specific binary on the machine is quite reasonable, however the end user has to be able to disable this if they want to run their own software (possibly disabling their extended warranty or whatever.) In the cases where the GPLv3 disallows verification when the user agrees with it, the current draft is buggy.
      Alternatively, they can choose to make their machines physically tamper-proof (which defeats the intent of the license, makes the license unverifiable, and the product unrepairable in case of software problems).
      It's basically impossible to do this; in the cases where it actually matters, the proper method is to make the hardware device tamper evident, not tamper proof. [Think voting software; where if you wanted to have a DRM or TPM device, you set the jumper to enable it; then seal the box with a voter and voting official verifiable seal and/or lock on the case.]
      The net result will simply be that hardware developers will stop considering the use of FOSS, which will lead to them getting what they want anyway, FOSS code getting less exposure and less fixes, and end users receiving an arguably less technologically sound product at a higher price.
      Assuring user freedom is far more important to the FLOSS community than companies who do not buy into the basic philosophy of FLOSS being able to lower their development costs by using it. In the long run, if companies are not interested in contributing to the movement, that's fine. Interested volunteers who already do the work will continue on doing the work.
      --
      http://www.donarmstrong.com
    5. Re:But does it help? by pnambic · · Score: 1
      > Why are hardware developers so special? Why do they deserve their own privileged class with respect to FLOSS users/developers?

      Simple. Economics. It is not cheap to supply hardware to your customers, and for many applications, customers are unwilling to pay the actual cost of the hardware. Think game consoles, cell phones, Tivo and friends.

      > It seems to me that Linus (and you) are identifying too much with the hardware developers and forgetting the perspective of software developers! Let alone end users.

      End users wishing to buy a general purpose computer that can act as a PVR should buy just that. As for the freedom to fix what you bought, that's not guaranteed by the GPLv3. Even the FSF sort-of admits this, in the context of regulatory compliance:

      But if there really are regulations which forbid software on certain devices from being modified once it's installed, it's still possible to use software licensed under the GPL -- simply burn the software into a ROM. Then nobody can upgrade it without replacing the ROM. Of course, device manufacturers will protest that this prevents them from upgrading it themselves. This shows that their true desires are not to comply with FDA rules, but to get special rights that nobody else has.

      Does that sound like a logical argument to you? Is this really about users' freedoms?

      > Arguments about "more people will develop for/with free software if we simply don't insist that it be free" have always been stupid and always will be.

      Fully agreed. However, the world in which RMS (and I) would like to live in is one in which for any reasonable task you want to do, there's a Libre option. We're not getting closer by excluding certain applications by default.

      There is one other interesting point that just happened to cross my mind. Imagine google was built on a GPLv3 foundation. If the original authors added the appropriate clause, they'd have to make their source code downloadable. That's fair. However, if I downloaded said code and modified it to suit my tastes, should they then be required to run my version on google.com, so that I can use the code in the same context from which I received it?

      BTW, just for the record, I'm not a hardware manufacturer, nor do I work for one. I'm an independent software developer building FOSS-based billing/accounting/CRM/etc. systems (for food) and music production software (for fun).
    6. Re:But does it help? by pnambic · · Score: 1

      > Didn't their customer purchase the product? Why shouldn't I as a consumer be able to modify a product that I've purchased to implement whatever fixes or features I want the product to run?

      Would it advance the overall level of freedom if the customer were unable to purchase the product in question, but instead had to rent it from the manufacturer, signing a contract that would make him subject to a heavy fine for replacing the software? Would that be compliant with the GPLv3?

      Or to look at this from a slightly different angle, how about putting the software in an SMD ROM chip with a blob of glue on top? That is compliant with the GPLv3 (see the link I posted in another response on this thread). Whose freedoms does that protect?

    7. Re:But does it help? by dondelelcaro · · Score: 1
      Would it advance the overall level of freedom if the customer were unable to purchase the product in question, but instead had to rent it from the manufacturer, signing a contract that would make him subject to a heavy fine for replacing the software? Would that be compliant with the GPLv3?

      If you don't own the hardware or you decide to limit the rights that you have by signing contracts, there is little the GPL can do to help you. At most it can restrict its use in such environments; it doesn't do so currently because this is at odds with Freedom 0.

      Or to look at this from a slightly different angle, how about putting the software in an SMD ROM chip with a blob of glue on top? That is compliant with the GPLv3 (see the link I posted in another response on this thread). Whose freedoms does that protect?

      There are definetly use cases where people can use GPLed works in such a way that users are unable to exercise the freedoms that the GPL tries to guarantee. It's clearly not a perfect license. The current draft of v3 goes farther to try to protect those freedoms, but even it is unable to do so completely.

      At some level the licence has to strike a balance between protecting the freedom of users to modify GPLed works and the freedom of distributors to deploy GPLed works in any way that they want. The GPL has always been about this compromise, and the section on DRM and TPM is attempting to finely adjust this balance by allowing "legitimate" uses of DRM while disallowing uses which curtail user freedom.

      If you think the license has the balance wrong, comment on it at http://gplv3.fsf.org. I've personally spent dozens of hours agonizing over this very issue (I'm on Committee D, in case it wasn't clear.) You can see what else I've written on it (and the draft of what I supplied to the FSF for the first draft) here: http://svn.donarmstrong.com/don/trunk/projects/gpl v3/issues/drm_allowing_authentication/.

      --
      http://www.donarmstrong.com
    8. Re:But does it help? by pnambic · · Score: 2, Interesting
      > If you think the license has the balance wrong, comment on it at http://gplv3.fsf.org./

      My basic objections - in soundbite form, as unfortunately encouraged by the interface - seem to have been submitted already; I'll still mail the text below to the comment system, in the hope that a human being might encounter it somewhere in there. ;)

      > [...] (I'm on Committee D, in case it wasn't clear.) You can see what else I've written on it [...]here: http://svn.donarmstrong.com/don/trunk/projects/gpl v3/issues/drm_allowing_authentication/.

      That was a very interesting read indeed, and confirms that Linus was and still is wrong about the process. I still think he's right about the result so far, though. Here's what I'll submit to the e-Mail comment system in a few minutes, both "for the record" of this thread, and as a shameless attempt to exploit the attention of a committee member, if it does get dropped:

      I feel deeply uncomfortable with the following section, specifically with the *marked* sentences:

      Terms and Conditions, section 1, paragraph 4

      The Corresponding Source also includes any encryption or authorization keys necessary to install and/or execute modified versions from source code in the recommended or principal context of use, such that they can implement all the same functionality in the same range of circumstances. (For instance, if the work is a DVD player and can play certain DVDs, it must be possible for modified versions to play those DVDs. *If the work communicates with an online service, it must be possible for modified versions to communicate with the same online service in the same way such that the service cannot distinguish.*) A key need not be included in cases where use of the work normally implies the user already has the key and can read and copy it, as in privacy applications where users generate their own keys. *However, the fact that a key is generated based on the object code of the work or is present in hardware that limits its use does not alter the requirement to include it in the Corresponding Source.*

      This specifically allows modified versions to hide the fact that they are modified. Thereby it creates two technical problems:

      • it makes it impossible to verify and certify distributed systems consisting in whole or in part of (derived works of) Free Software.
      • it makes it impossible to verify the integrity of a distribution package consisting of Free Software and hardware and/or non-free software, e.g. to determine eligibility for support or warranties.

      These seem to me to exclude Free Software from a substantial set of reasonable and legitimate applications in existence today or foreseeable for the future.

      Additionally, it seems to be in conflict with the following provision:

      Terms and Conditions, section 5, paragraph 2

      a) The modified work must carry prominent notices stating that you changed the work and the date of any change.

      In particular, the section quoted earlier seems to amend this with, "unless the notice would be machine-readable, in which case the modified work may choose not to carry such a notice". This serves as a strong deterrent to authors of original works to free those works if they customarily provide them e.g. as part of a hardware package on which they in turn provide a warranty.

      Lastly, this whole issue seems to open up a veritable can of worms with regards to the definition of "derived work" vs. "aggregate". In the case of Tivo for example, the distribution package consists of a computer with some proprietary hardware on which some free software and some proprietary software is installed, all of which works properly only in connection with an online service. Now for some reasons, the proprietary software part is s

    9. Re:But does it help? by martin-boundary · · Score: 1
      I don't worry about Joe Hacker the outsider, I worry about the people who legitimately have access to the voting machines.
      Then you shouldn't be arguing for or against a system which applies to every user/developer, but instead you should be arguing for or against a system which specifically addresses the people who legitimately have access.

      There's nothing wrong with imposing restrictions and oversights specifically on a subgroup of people who have access to voting machines. This can be done as part of voting laws, through video surveillance, whatever. It has nothing to do with the GPL if it's not about _all_ users and _all_ developers.

    10. Re:But does it help? by dodobh · · Score: 2, Insightful

      And in all these cases, the end user is losing out on being able to use the hardware/software as (s)he pleases. This is precisely what the FSF is trying to prevent.

      --
      I can throw myself at the ground, and miss.
    11. Re:But does it help? by init100 · · Score: 2, Insightful

      Does that sound like a logical argument to you? Is this really about users' freedoms?

      You can't upgrade to your modified version, but they (the vendor) can't either. This is more equal that "they can, but you can't".

    12. Re:But does it help? by init100 · · Score: 1

      However, if I downloaded said code and modified it to suit my tastes, should they then be required to run my version on google.com, so that I can use the code in the same context from which I received it?

      No, but google.com is their hardware, not yours. But if I buy a hardware gadget, that is my hardware, not the vendor's (unless I sign a contract with them that says otherwise). It is my hardware regardless of whether their business model is selling underpriced products and overpricing on additions (printer cartridges for underpriced printers, games for underpriced game consoles, etc) to compensate.

    13. Re:But does it help? by pnambic · · Score: 1
      Yes, but everyone is worse off in that situation. I find the logic behind this deeply repulsive. As I wrote elsewhere in this thread (and sent to the FSF as well):

      In essence, it states:
      • any degree of freedom is acceptable if everyone has the same freedom.
      • users should be concerned with freedom first, maintainability, security, and upgradeability second
      • hardware developers looking to make sure that they know what they sell - to be able to support it, for example, not to bask in the glory of having more freedom than their users - should use proprietary software or make everyone's life more difficult
      • the concerns of software developers who worry about tivoization of their work are unimportant if the "tivoizer" locks the code down hard enough.
      Of these statements, only the second could maybe have been construed as an FSF position earlier. The rest is just plain idiotic, no matter what side you're on.
    14. Re:But does it help? by pnambic · · Score: 1

      Yes, but, to reiterate the title of my first comment, does it help? I think the language currently in section 1, paragraph 4 is throwing the baby out with the bathwater, while getting the bathwater all over the floor in the process. You do realize that the FSF's response to hardware manufacturers claiming to need control over installed software is, "Well, put it in ROM, then, that way noone will be able to upgrade, and you're in compliance again", right?

    15. Re:But does it help? by dch24 · · Score: 1

      > 1. locked digital media This is where the GPLv3 works

      Sort of. If someone wants to include a DRM'd player on an otherwise free system (including GPLv3), there's no problem.


      Agreed. It appears this will be the first major battlefield for TPM. The media center PC (Mac Mini, XBox) in the future will have a TPM chip to make DRM unbreakable. Microsoft is already moving in this direction. GPLv3 will prevent the TiVo scenario, keeping FOSS code out of locked TPM software stacks.

      But will that stop TPM in the media center PC? I doubt it. The battle will be won by GPLv3 because of the security holes in any closed-source system. HD-DVD and BluRay will be cracked. Windows will have its security holes. And so there will always be a percentage of the market who need systems with GPLv3 software enough to hold the rest of the industry at bay.

      > 2. locked FOSS-using devices (the Tivo scenario)

      > I think the FSF are overstepping their bounds. They're telling hardware developers that they have to make THEIR OWN product convertable to any use their customers see fit.

      The FSF is simply telling hardware developers that they don't have any special additional rights to control the software (not their software, remember) simply because they are working in hardware rather than software.

      Everyone is potentially a developer.


      Agreed. This is the second battle, when we are years into the media center PC, the TPM + DRM lockdown, and the DMCA will still be there. The businesses who have a decided to make their money by manipulating customers' choices (this is not advertising) will continue to try to push for a monopoly (100%) TPM. This means they will try to drive FOSS out of computing.

      Microsoft is a good example of how this happens after the first lockdown. Microsoft first achieved OS domination and vendor lock-in. Then they started leveraging their marketshare to drive the competitors out of business. It will be the same way in this battle.

      They have no interest in anyone being able to develop. But GPLv3 preserves the ability to develop any kind of new invention (software or hardware) using equipment you have purchased. It's all a part of fair use, and the GPL has been about distributing source code along with binaries so that fair use covers the source code. The other alternative is reverse engineering. I'd say GPL is just the more efficient method of the two, since both are possible, even with the most elaborate TPM schemes. It's an arms race, and a pointless one, I believe. Especially pointless now that the FOSS community is so strong and capable.

      > 3. locked general-purpose computers

      > The net result will simply be that hardware developers will stop considering the use of FOSS


      There will always be hardware vendors who sell closed-source products. The FOSS projects have never been threatened by closed-source products. Would emacs disappear even if everone switched to vi? No, because old source code always ends up archived somewhere. Old binaries are sometimes archived too, but since they're old, they usually don't work. FOSS is not threatened by the success of other projects.

      It is the closed-source shops that are threatened by open source. They will do whatever they can to stop open, community-based development, but it won't do any good in the end.

      I think stage three of this battle will not be locked general-purpose computers. I do think that we will see them, but I think that will be part of stage one, above. And I think the GPLv3 (and even the GPLv2) will be around to keep stage one from complete penetration. FOSS will not die in stage one.

      Stage three will take a long time to implement, but the ultimate goal is to reduce the internet back to cable TV, what we had before 1990. Efforts toward a tiered internet may not succeed in the near future. But these large companies are not going away, and they will be lobbying your governments very pe

    16. Re:But does it help? by dodobh · · Score: 1

      Put it in ROM (or equivalent flashable hardware). Works fine.
      There is a reason why open specifications work.

      --
      I can throw myself at the ground, and miss.
  80. Re:Sure to happen by Overly+Critical+Guy · · Score: 1

    Linus is reasonable enough to recognize that creators have the right to protect their content from rampant thievery. I've been listening to Slashdot's alarmist anti-DRM arguments for years and have yet to see their mythical Orwellian power structure materialize.

    --
    "Sufferin' succotash."
  81. so you agree with me by H4x0r+Jim+Duggan · · Score: 1

    Well, thanks for that copy'n'paste. You don't seem to disagree that the part I quoted was the relevent part, so I guess you agree with me.

    1. Re:so you agree with me by Ohreally_factor · · Score: 1

      No, I don't agree with you.

      There has not been a solid refutation of Linus's criticisms, despite your claim that the "main" criticism has been answered. I'm not satisfied. No real examples were given of Linus's (or anyone else's) problems with the draft being addressed. They "addressed" his concerns about the DRM section? Linus makes it clear that those were never the real concerns. Do they say anything about signed binaries? No. Not addressed. Do they say anything about the redefinition of source code? No. Not addressed. Do they say anything about the redefinition of distribution (my concern, not sure about Linus)? No. Not addressed. They spoke only in generalities.

      Also let's look at the interviewees. The guy from Gnome? Axe to grind. He's gone on record before as calling Linus irrelevant, because Linus dared to criticize the Gnome project. Judging by that excuse for an article and the posts I see here on slashdot (some of which are accusing Linus of selling out!), it's hard not to conclude that a smear campaign has started.

      By the way, have you ever studied the history of socialist movements and revolutions that have been subverted into totalitarian regimes? If you have, you'll see where the FSF is getting their playbook.

      --
      It's not offtopic, dumbass. It's orthogonal.
  82. Re:Has Linus sold out? (was: Re:I can see both sid by Anonymous Coward · · Score: 0

    If there's no threat from DRM lockdown, then what is the problem with license terms preventing that? Or in other words, if the license says you have to give out a signing key to let modified software run on the hardware, but nobody is going to use these signed binary checks they where's the problem?

    I think the reality is that Linus' position is that hardware will include signed-binary checks but will not be abused to prevent running modified software (primarily because you will always be able to buy hardware you can run the modified software on). Power is always abused, that's why we have checks and balances and laws. You never give any entity unilateral controls like DRM-lockdown.

  83. GPLv2 a stupid idea by bussdriver · · Score: 1

    By allowing GPL to have a version 2, they opened us all up to the idea GPL can be revised.

    If GPL v2 was NEVER allowed to happen, a new license would be required.

    Creating conflicting definitions of GPL every x years is going to undermine the GPL. MS could have MS-GPL and call it GPLv4 but nobody would accept that...who knows, in 10 years MS could be directly involved in GPLv4.

  84. Re:Has Linus sold out? (was: Re:I can see both sid by Ohreally_factor · · Score: 1

    If there's no threat from DRM lockdown, then what is the problem with license terms preventing that?

    Because it is preventing valid uses of signed binaries. Do you not think there might ever be a valid "good" use of signed binaries?

    --
    It's not offtopic, dumbass. It's orthogonal.
  85. Re:Has Linus sold out? (was: Re:I can see both sid by marcosdumay · · Score: 1

    Or he is emotionaly oposed to FSF (what is quite more possible). His arguments dont make sense, but that doesn't implies that he is sold out.

  86. Re:Has Linus sold out? (was: Re:I can see both sid by Anonymous Coward · · Score: 1, Insightful

    When has IBM objected to the GPL v3 in that way?

    That said, from what I've read that was officially from Torvalds, he seems to think that the hardware makers should be allowed to control what runs on the devices they sell. I totally, utterly and completely disagree with that. Once I buy it, it's mine, and I have no intention whatsoever of going along with any scheme that allows the device makers to pretend otherwise.

  87. Re:Has Linus sold out? (was: Re:I can see both sid by mrchaotica · · Score: 1
    Linux is and will continue to be GPL2, and there's no compelling reason to open hardware to accomodate any other software.

    Then why is Linus protesting against GPL v.3 so much?! It won't affect him; why does he care?

    As I see it, it's not Torvalds who needs to justify his position, it's you. You won't, of course, because you're so deep in cognitive dissonance that you can't acknowledge that the FSF is still drawing up battle plans when it's already lost the war. When the first beta of a Windows version that requires TC hardware is released, you may try to sue for peace, but by then it will be far too late.

    First of all, you have no idea what you're talking about regarding "a Windows version taht requires TC hardware." GPL code, version 2 or version 3, will have no problem running on the TC machine you're referring to. It's only the reverse situation -- TC hardware that requires signed code -- that GPL code (version 3 or version 2, if it was compiled by the user) won't run on.

    Second, what kind of fatalistic, self-defeating, cowardly dumbass are you?! Let me guess, you'd just sit in a burning building because "oh well, it's already too late" and let the fire get you. Or you'd just let yourself bleed to death after getting a paper cut because "oh well, it's too much bother to go find a band-aid."

    We have not "already lost," but negative assholes like you sure as Hell aren't helping!

    --

    "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  88. Re:Wow, you missed the whole point of the DRM clau by Jack9 · · Score: 2, Informative

    If their goal were to make money from the code, odds are they wouldn't have open sourced it

    Your view is typical of the Open Source fanboys. Open Source code is not a vow of poverty, it's a belief in a philosophy of community strength. This is not at odds with capitalism. Once you understand that, you might have an idea of why Torvalds' criticisms have validity.

    --

    Often wrong but never in doubt.
    I am Jack9.
    Everyone knows me.
  89. Why is this being discussed? by LocalH · · Score: 1

    Who cares? If Linus says the kernel is not going to be GPLv3, then what does it matter what others say? It means the kernel's not going to be GPLv3.

    --
    FC Closer
  90. tagging for legal disclaimer by Ifni · · Score: 1

    NewsForge and Slashdot are both owned by OSTG.

    Maybe this could just become a tag: newsforgeandslashdotownedbyostg.
    Or even shorter: nfandsdownedbyostg.
    Or even: ownedbyostg.
    Or just: ostg.

    It just seems such a commonly used footer could make great use of the tagging system.

    --

    Oh, was that my outside voice?

  91. You are completely ignorant and wrong. by Anonymous Coward · · Score: 0

    None of the GNU tools mattered at all. The linux kernel could have just used the BSD userland. In fact, Linus even said more than once that had he known about BSD, he wouldn't have even started linux. And without linux, the GNU crapware would be completely ignored, with the exception of emacs, and possibly gcc.

  92. A non-GNU Linux system by SpaceLifeForm · · Score: 1

    Not only can it be done, it is not terribly difficult to
    do so. Try the Linux kernel with uClibc and Busybox.
    Toss in dropbear and TinyCC and you are well on your
    way to a usable system sans GNU userland tools.

    --
    You are being MICROattacked, from various angles, in a SOFT manner.
  93. Re:Has Linus sold out? (was: Re:I can see both sid by dwandy · · Score: 1
    Let me ask you this: In your mind, are there no good uses for trusted computing? Are there never circumstances where trusted computing could be applied without evil effect? Or is all trusted computing inherently evil and must be stamped out?
    yes. "Trusted Computing" is evil, and must be stamped out. The 'trust' in the phrase is that you must trust someone else to decide what your hardware can and can not do, and it will be a question of your hardware doesn't trust you. At this point, the General Computing Machine will be dead.
    Explain to me why I should let Sony decide what my computer is going to do?

    This will be acceptable when it's acceptable for my car manufacturer to tell me which roads I can drive on
    ...when it's acceptable for my telephone company to tell me which numbers I can dial
    ...when it's acceptable for my TV manufacturer to tell me which channels I can watch
    ...when it's acceptable for my stove to tell me I what I can and can't cook, and what time I can cook at
    ...when it's acceptable for my couch to say I can't sit on it just now....

    My personally owned objects are to serve me. At my discretion. Not some corporation.

    If you like your "freedom" to be at the mercy of Thomas Hesse, that's your problem. I'm not interested.

    Lastly, there's nothing beneficial that can be accomplished in hardware (ref:TPM) that can't be done in software and thereby be at the control of the user instead of at the control of software and media vendors.

    --
    If you think imaginary property and real property are the same, when does your house become public domain?
  94. You are seriously delusional. by Anonymous Coward · · Score: 0

    You can just as easily swap out the GNU userland tools (and the assortment of random non-GNU tools that people like you always ignore) for a (MUCH nicer) BSD userland. Grab tendra for you compliler and away you go.

  95. GNU/BSD by Xtifr · · Score: 1

    I know you meant the comment about "go work on HURD" to be ironic, but the fact is that there is a not-so-experimental project that actually will allow me to dump Linus's stupid kernel without giving up all the meaty GNU goodness I love, and I am seriously considering a switch to GNU/BSD in the not-too-distant future. For a number of reasons.

    Anyway, this isn't about taking away Linus' freedom to chose the license for his own software. He already did that, long ago, and GPLv3 is not it. Even if he wanted to, he'd have a very hard time switching Linux to GPLv3 at this point. But he's out there playing politician, trying to influence other people's license choices, and that makes him fair game for debate. (Especially when he says stupid things or misinterprets the plain terms of a license he isn't even using.) Or are you trying to say that only Linus is allowed to try to influence people?

  96. Re:Sure to happen by lgw · · Score: 2, Interesting

    DRM and TCPA are user hostile technologies, support can and will be ripped out of Open Source code. There is no argument here, I will not running DRM or TCPA compliant code, period.

    I've been seeing senseless rants like this increasingly on Slashdot. It's like some superstition. All Trusted Computing does is give ownership of a computer to whoever owns the master keys.

    If you have the master keys (as you would, on a box you built yourself) then Trusted Computing means you *really* own your computer. You can prevent rootkit installation, and guarentee access to content no matter how DRM-encrusted. If someone else has the master key, why would you pay money for something you don't own?

    --
    Socialism: a lie told by totalitarians and believed by fools.
  97. Re:Sure to happen by lgw · · Score: 1

    to work with a protected set of data you would create a thread that would handle that data and only certain actions could be taken

    This model has been debunked in the security world (though people still use it). A thread that has access to content protected by DRM can simply leak the data to a thread that doesn't have any use restrictions, and the best any system can do is limit the bandwidth of the leak.

    --
    Socialism: a lie told by totalitarians and believed by fools.
  98. Re:Wow, you missed the whole point of the DRM clau by nacturation · · Score: 1

    Your view is typical of the Open Source fanboys. Open Source code is not a vow of poverty, it's a belief in a philosophy of community strength. This is not at odds with capitalism.

    Where did I ever say that it's a vow of poverty or that it's at odds wth capitalism? In your rush to put words into my mouth, it appears you missed the most important part of my post. I stated "If their goal were to make money from the code...".

    And as far as "Open Source code is... a belief in a philosophy of community strength", I'd recommend you examine your own fanboyism there. Releasing your code under an Open Source compatible license is a license choice, nothing more. Whether or not this license choice resulted from your subscription to some higher cause is a completely different issue.

    --
    Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
  99. good grief by Quadraginta · · Score: 1

    Lots of words, no message.

    It's not always about delivering a message, okay? I'm relating interesting personal experience, not preaching a sermon. It's food for thought, not an attempt to tell people what to think.

    Seems like you have read some book

    Don't be insulting. Why would I waste time reading books about software development? My heavy reading is J. Chem. Phys. and Phys. Rev.. My light reading runs to Dorothy Sayers and Patrick O'Brian. So where did what I know come from? Well, I wrote my first code 28 years ago this September, an implementation of Conway's "Life" in 8080 machine code. I've never hacked an OS, but in the last two decades I've written megabytes of serious scientific application code on everything from VMS and CMS to Multics to half a dozen varieties of proprietary Unices, plus of course Linux itself.

    but never really been part of the movement.

    I said I wasn't a systems hacker. I was a user, and a pretty high-level geeky informed one at that. I didn't use my computers for editing Word documents and photoshopping Dan Quayle's head onto an elephant seal's body. I wrote big programs to solve nonlinear integral equations, run molecular dynamics simulations, evaluate many-dimensional phase-space integrals, et cetera and so forth. I squeezed every speck of raw scalar performance I could out of the hardware, and the hardware I worked on started off costing a cool million (in 1980 dollars).

    Thus your knowledge is lacking.

    About what? About the Right Way to program operating systems? Guilty as charged. I'm a user, not a kernel hacker. But, unless you're an utter pure theorist, a monk in an ashram, than any reasonable kernel hacker has got to care about my point of view. I mean, what are you writing operating systems for? Just to boot up and look pretty? So Brittany T. Nager can log onto her Facebook account and check out cute college guys? Surely you write operating system to be seriously and heavily used -- to do good work for scientists and engineers, for people who really need the power of the latest hardware governed by a rock-solid, powerful OS that you don't just reboot every day, or when it freezes up, whichever comes first. Well, that's me. That's why I think my "userland" perspective during the development of the free Unix is a bit relevant.

    No offense, but you're confused.

    About what? You're saying I don't remember correctly what it was like doing serious programming in the Late Workstation to Early Linux transition era? Because I had a stroke or something? Feh.

    Or are you saying I don't "correctly" interpret my experience? Well maybe I don't, but, if so, that should be a serious warning to kernel hackers and software-movement prophets: alas, often the vast army of users who in the end determine whether your software is successful or a museum exhibit are not going to "interpret" their experience with your work the way you think they should. They're not going to act like supplicants in your temple, asking to be shown The Way. They're going to act like homeowners calling around to find someone to clean the pool. If using your work means putting up with a lot of hard to understand delays, restrictions, obfuscations or other inconveniences -- well, they won't. Even if those things are all intended to serve A Good Purpose That Someday You Will Understand.

  100. Re:Has Linus sold out? (was: Re:I can see both sid by foom · · Score: 1

    Actually it does not prevent good uses of signed binaries. The "good" kind of binary signing is the kind where you, the end user, are in control of the restrictions. It is perfectly acceptable under the GPLv3's terms if your computing device refuses to run binaries that aren't properly signed, as long as you, the user, can either disable that behavior, or add your own trusted keys.

  101. several gcc replacements by r00t · · Score: 1, Informative

    tcc -- much faster than gcc, though little optimization
    icc -- from Intel
    ??? -- something from IBM for Power chips

    1. Re:several gcc replacements by Anonymous Coward · · Score: 0

      Can tcc is reliable anough produce a commercial/enterprise grade full linux distribution? If not, the comparison with gcc is pointless. Icc is non-free software.

  102. Re:Has Linus sold out? (was: Re:I can see both sid by Rob+Kaper · · Score: 1

    Any hardware that requires signed binaries prevents this unless signature capability is given to anyone who wants it.

    And that will happen. Even in a DRM-only world, every single software company in the world must remain able to easily give all developer machines and laptops the ability to generate binaries and to run them locally for testing. Not a single company will accept a dependency on third party certification for an urgent, crucial bugfix at 3am in the night. None of the parties behind DRM would benefit from a complete collapse of the ICT sector, so everyone will be able to sign.

  103. GNOME isn't GNU by r00t · · Score: 1

    GNOME was written by some FSF fans at Red Hat, and the "G" fit the acronym better than an "R". The GNU label also nicely distracted attention from Red Hat, allowing other Linux vendors to package the desktop. No other vendor is going to ship a Red Hat branded desktop!

    The compiler and C library aren't much better. The FSF wrote toy versions long ago. Since then, Red Hat and Cygnus (since purchased by Red Hat) have done most of the work. The FSF is just a way to make things look more vendor-neutral than reality.

    Heck, I have a project that the FSF tried to get joined up. It seems the FSF has some sort of marketing group that goes around to various software projects trying to get the GNU name added. WTF? Anybody else get approached like that? (obviously, I told them in detail exactly how they could go to Hell for trying to rewrite history by renaming everything)

  104. Re:Has Linus sold out? (was: Re:I can see both sid by squiggleslash · · Score: 1

    I think Linus is more like half the geeks on Slashdot, slightly embarassed by the whole idea of politics and wanting desperately to appear "reasonable" to the point of making a point of criticising the FSF and similar political groups when he can.

    Nothing about his criticisms of the DRM provision of GPL3 make any sense, it's certainly inconsistant - you're either in favour of people being able to do what they wish with their own copies code to the point of supporting the GPL or you're not. If you don't care, why the fuck are you using it at all? I mean, why has Torvalds chosen the GPL over, say, the BSD license?

    This is the second time he's come out against the principles he signed up for when he chose the GPL for Linux. The first time was the BitKeeper fiasco, where even after BitKeeper's authors prove they were completely untrustworthy, he condemned the very developers that have been a part of making Linux successful instead of admitting his decision to entrust a Free Software project to a proprietary source manager might just have been both inappropriate and, actually, not very "pragmatic".

    Sometimes, when you have 99% of a group describing the other 1% as "zealots", and doing so over and over again, loudly, as if they feel the need they have to prove something, you need to listen to the so-called zealots. They're very often the few people who actually know what they're talking about.

    In the mean time, it's time Linus put his money where his mouth is. If he really believes it's immoral to place restrictions on what restrictions third parties can be put on his software, then he needs to re-release Linux under the BSD or X11 licenses. The GPL2 is a half-way house that places restrictions on companies that rerelease binaries but do nothing to limit the use of those binaries, but places few restrictions on organizations that release source code that can never be modified and compiled into anything usable thanks to a signing process that ties particular binaries to the hardware they need to run on. It's time to be clear in what's wanted.

    --
    You are not alone. This is not normal. None of this is normal.
  105. Re:Has Linus sold out? (was: Re:I can see both sid by Ohreally_factor · · Score: 1

    Which means that anyone else with local access, or perhaps even remote access can either disable that behavior or add their own trusted keys.

    --
    It's not offtopic, dumbass. It's orthogonal.
  106. Re:Has Linus sold out? (was: Re:I can see both sid by Ohreally_factor · · Score: 1

    God forbid you should ever be in a hospital being kept alive on machines running open source software licensed under GPLv3, and someone who "likes to tinker" loaded up their "improved" version of the software without proper authorization or QA. (Don't you think that would be a valid use of signed binaries?)

    That's just one example of a use of OSS where signed binaries and trusted computing would be a good thing. There are plenty other uses of signed binaries that would be very good things. Anyplace where someone's life is on the line. Anyplace where an unsigned binary has the potential to wreak havoc. I'd hazard to say that there are more positive good uses than there are negative bad uses.

    You're just buying into the FSF propaganda of paranoia. It's time you started asking why the FSF wants you paranoid. How do they benefit from instilling fear into you. What sort of compromise are they trying to sell you to escape their unlikely worst case scenario of totalitarian trusted computing.

    Just like those developers who went for the the GPLv2 plus edition, you're being sold a pig in a poke.

    I'm curious as to how exactly you expect Sony to dictate what you do with your computer. As near as I can tell, Sony doesn't have a monopoly on hardware yet, and probably never will. If you think Sony is out to control your computer, can't avoid that by just not buying Sony products? Or do you need a software license in case you accidentally buy Sony? You cannot trust yourself, so you need the FSF to protect you from yourself and your own decisions?

    It's stunning how people are so unwilling to take responsibility for themselves that they'll surrender to a Big Brother figure who promises to protect them from the evils of the world.

    It's astonishing how much this GPLv3 circus reminds me of Animal Farm.

    --
    It's not offtopic, dumbass. It's orthogonal.
  107. Re:Has Linus sold out? (was: Re:I can see both sid by Anonymous Coward · · Score: 0

    Yup. Read up on Ken Thompson's Reflections on Trusting Trust.

  108. GNOME is GNU by Anonymous Coward · · Score: 0

    You are misinformed. GNOME is a GNU project.

    It has many sponsors: FSF, Debian, Sun Microsystems, Red Hat, HP, Novell, Nokia, Intel, IBM and more.

    GNOME gets code contributions from Red Hat, yes. Your point?

  109. Re:The GPL needs to go by Anonymous Coward · · Score: 0

    Considering the way the GPL is going now and the way the FSF loves to be vague in their definitions & meanings(to the extent of what ever outcome bennifits them the most), that bit in the cut & paste troll becomming true wouldn't surprise me...

  110. Re:Sure to happen by packeteer · · Score: 2, Insightful

    I didn't say he WAS corrupted. I just wanted to remind everyone than nobody is immune from corruption, nobody. Look at the evidence however. I know its not a lot to work with but it seems like Linus is supporting things that many of us think are bad. That does not make him outright bad for linux or anything like that. I am just saying that we cant just assume he is perfect in every way and we can leave it in his hands.

    Someone disagrees with you, so they must be a troll? What the fuck is wrong with you?

    --
    unzip; strip; touch; finger; mount; fsck; more; yes; unmount; sleep
  111. Re:Wow, you missed the whole point of the DRM clau by Jack9 · · Score: 1

    I stated "If their goal were to make money from the code...".

    That's only the first wrong.

    Open Source just exposes the logic. Nothing more. There's inherent value in large collections of OS code outside of the logic. I can't understand why you would believe that releasing code OS prevents you from making money off of it.

    Hence I said:
    Open Source code is not a vow of poverty,
    This is not at odds with capitalism. (this was a bit obtuse, but same logic)

    You state:
    Releasing your code under an Open Source compatible license is a license choice, nothing more.

    That's your second wrong.

    Your license choice is always based on an informed decision. You astutely say that there's an implicit "Reason" to chose a license. There's lots of reasons, they amalgamate into a belief in a higher or LOWER cause, even if it's as terrestrial as the company's bottom line. That's why you dont roll dice to decide your license. Since you simply call my reasoning (why one might choose an OS license) fallacious, with no real logic or evidence to the contrary, I'll just ignore your "rah rah I'm right, you're wrong!" stance out of respect. We each misspeak every day.

    I did not miss the point. I think you are stating falsehoods as arguments why GPL3 is sane.
    Defending a legal agreement is always easier than attacking it when there's only a philosophical incentive to attack it. That's just business and the core of Torvald's problem with it.

    --

    Often wrong but never in doubt.
    I am Jack9.
    Everyone knows me.
  112. Re:Sure to happen by tomhudson · · Score: 1

    You have the choice not to buy those dvds. Nobody is forcing you to. So you go without. Big deal. If enough people did it, the producers would say "fuck that shit". Why? Because you're hurting them where it huts most.

    "The choices that need to be available for consumers to deal with this issue are non-existant."

    Really? You mean to tell me that the mobo I bought in February has drm on it? I don't think so, Clyde. Ditto my monitors, my video card, etc. No drm to be found. I'd have to go out of my way to find a mobo that has palladium (trusted computing platform) ... I'd have to break into some lab somewhere and STEAL it. Why? Because nobody' selling that shit yet. No consumer demand.

    "We already have one source of media, movies, now completely locked up by DRM schemes and where the only workarounds are illegal"

    ... really? Gee, I guess my el cheapo region-free dvd player is a figment of my imagination. And the last time I looked, it was quite happy to play non-drm'd content.

    As far as the laws are concerned, all bad laws do is get people to ignore them, and disrespect their proponents. We're seeing a pushback against these stupid attacks on fair use. It won't happen overnight, but it will happen, the same as other stupidities like laws against gays and lesbians, or criminalizing soft drugs, or "my country right or wrong".

  113. GNOME is not GNU by r00t · · Score: 1

    You're not paying attention.

    Any group can slap a GNU label on their project. The FSF actively encourages this. The FSF even approached me with the request that I slap a GNU label on my own project. (they contribute NOTHING, but wanted the label anyway)

    Slapping a GNU label on the project in no way makes the project really truly GNU. It's a flag of convenience for vendor neutrality, and it's a way for Stallman to claim he did everything.

    GNOME is no more GNU than OpenBSD is.

  114. Re:Sure to happen by tomhudson · · Score: 1

    "Companies like TiVo are benefiting from the same communities they're undermining, using GNU and Linux to create their products while simultaneously undermining the freedom of their users"

    How has Tivo prevented you from using any GPL'd code on other hardware? Have they made the bits disappear? Made them proprietary? Changed the license? No. So you can't run modified binaries on Tivo ... nothing stopping you or someone else from using the same code to compete in the marketplace by offering a superior hardware product.

    And there's no law that says you have a constitutional right to own a Tivo.

    If you're so opposed to their practices, just don't buy one. Enough people do, someone (they're called "competitors") will see a marketing opportunity.

  115. Re:Sure to happen by Lehk228 · · Score: 1

    that thread is not able to send data out of the protected space except as indicated in the original protected block permissions. the permissions could specify that analog unprotected signal outputs such as VGA and sound are acceptable, or may only allow them at certain configurations or not at all, instead only allowing secured interfaces such as HDMI.

    --
    Snowden and Manning are heroes.
  116. Re:Has Linus sold out? (was: Re:I can see both sid by Blakey+Rat · · Score: 1

    "Trusted Computing" already exists in the form of video game consoles, and I never really seen the Slashdot FSF followers saying anything against those.

  117. Re:Wow, you missed the whole point of the DRM clau by nacturation · · Score: 1

    Open Source just exposes the logic. Nothing more. There's inherent value in large collections of OS code outside of the logic. I can't understand why you would believe that releasing code OS prevents you from making money off of it.

    I think we may be arguing two different points. My point is actually quite simple: I'm saying that choosing to release their code for free (as in beer) means that they choose not to make money from the code distribution. That -- and only that -- is my point. It's a bit of a tautology, but recall the original quote (not yours) to which I replied:

    "I am sure it works well for you, but how well does it work for the people whose code you are using? How do they make money?"

    Obviously those who release their code for free (as in beer) don't expect to make money from the act of others downloading the code. They make their money in other ways, or not at all, and realize that others can use their work to make money too. The reason I replied to the post I did was to address the implied statement that it's somehow wrong to make money off of others' code.

    Since you simply call my reasoning (why one might choose an OS license) fallacious, with no real logic or evidence to the contrary...

    I didn't think much was needed. You stated that "Open Source code is... a belief in a philosophy of community strength" and if you review your post you'll see this was the entire point of your comment. You didn't state "why one might choose an OS license", you stated "Open Source code = a belief in a philosophy of community strength".

    I stated that the choice of license is a completely separate issue from any beliefs and you're right to call me on that -- sometimes, the two are highly related. But to state that choose open source is one particular belief is inaccurate.

    There's lots of reasons, they amalgamate into a belief in a higher or LOWER cause, even if it's as terrestrial as the company's bottom line.

    This is different from your original statement I quoted above. You can see why I called your reasoning fallacious as you are now contradicting it yourself. But you're right... a company might release their code because they think it'll bring them millions in venture capital funding and those in the company are only out to make a buck, not giving a rat's ass about any kind of community that may or may not even look at the code.

    I think you are stating falsehoods as arguments why GPL3 is sane.

    You're attributing beliefs to me which I don't hold. I never mentioned GPL3 in any of my posts (save this one) yet you state I'm arguing in favor of the sanity of GPL3? How did you reach this conclusion?

    --
    Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
  118. Re:Has Linus sold out? (was: Re:I can see both sid by foom · · Score: 1

    Sorry, that doesn't follow *at all*.

    The _owner_ has to be able to add trusted keys, other people do not. There are any number of possibilities for authenticating that the "change trusted keys" request is not from a hacker. Most common would likely be a physical component ("flip a switch on the motherboard", "hold down reset button for 20 seconds", etc). You could also require a password known only by the owner, verified by trusted boot loader code. Or anything else you feel appropriate.

  119. A matter of personal choice by Requiem18th · · Score: 2, Insightful

    I write free software because I want my users to be able change their software. If my users can't change my code how is it good for me? It is my personal choice not to subsidise DRM device producers. Do you have a problem with that?

    --
    But... the future refused to change.
  120. Re:Has Linus sold out? (was: Re:I can see both sid by WilliamSChips · · Score: 1

    Unless I'm greatly misunderstanding GPLv3, all this restriction will do is prevent requiring a signed-binaries requirement. This will not prevent you or the hospital from saying "only allow signed binaries from X, Y, or Z on my computer" but it will prevent malicious guy M from saying "You can only install binaries signed by me which by the way are modified in the style of Trusting Trust to prevent you from using anything but binaries signed by me and there's no way to verify because the only way to figure that out is with another OS and the bootloader won't let you do that because it's my special GPLv2 Router which can only run binaries of OSes signed by me and if you even try to do any of this I'll sue you under the DMCA because I'm Mr. M and only signed binaries will protect you from the evil h4xx0rs and I'm right and RMS is wrong, GPLv2 good GPLv3 bad GPLv2 good GPLv3 bad"

    --
    Please, for the good of Humanity, vote Obama.
  121. Linus is a troll, yes, by WilliamSChips · · Score: 1

    but he is smart.

    --
    Please, for the good of Humanity, vote Obama.
  122. refutation doesn't matter by eliot1785 · · Score: 2, Insightful

    They might have refuted Linus's criticism, but his criticism is still there. The reality is that this little feud between Linus and FSF matters less as a logical debate and more as a practical issue. If Linus is unhappy with GPLv3 and decides not to adopt it for the Linux kernel, that will be a major blow for GPLv3 no matter how you cut it, because it will have a domino effect in which it is not adopted as a new standard.

    It may be that the other GNU project tools like gcc are indispensible parts of the Linux operating system. I don't know enough to know for sure. But the Linux kernel is also an indispensible part, and if you start having the operating system split between GPLv2 and GPLv3, new projects will justified in following the Linux kernel's lead and sticking with GPLv2.

    Another issue here that may not be fully appreciated is that many people already think that GPLv2 already goes too far. By going even farther, GPLv3 is going to turn off even more people to the GPL project. It may be that the goals it establishes are justified. But if even Linus Torvalds is turned off by this, I wonder what corporate users of Linux will say...?

    Also - one theory I'd like to just throw out there is the possibility that while current replacements for many of the GNU tools may be lacking, if they adopt GPLv3 and corporate customers like Google and Sun don't like them because of restrictions on usage, they may spearhead the development of replacements.

    Likewise, any GPL version that places clear requirements on web applications developed using programs under that version (e.g. you must GPL those web applications) will never see adoption by Google etc. Assuming this is where FSF is going, the GPL will ultimately destroy itself by becoming too extreme.

    1. Re:refutation doesn't matter by eliot1785 · · Score: 1

      I also wanted to say that the main thing that FSF needs to do is address the fears of basic programmers, especially those in startup companies, who have little legal knowledge and are frankly a bit scared by the whole GPL thing. People on Slashdot always complain when somebody comes on here and posts a comment that demonstrates their lack of understanding of the GPL and its limitations, but that should be a sign that there remains a huge lack of understanding out there.

      What is *really* lacking from the GPLv3 (and also GPLv2) is a clear description of the circumstances under which you *do* retain proprietary rights to your own work, and control over the license. While not legally necessary, inclusion of such a description would go a long way toward mollifying the fears of people who are worried about losing the ability to profit from their own work. In a nutshell, the primary barrier toward greater enthusiasm for the GPL is the (accurate) perception that FSF and the GPL do not have a profit- or business-friendly attitude.

      This will not happen because the FSF does not want to encourage people to have any sort of control over their own intellectual property. Whatever control is retained under the GPL (e.g. the ability to keep source secret if you don't distribute it, the ability to retain a copyright on your work even if you cannot enforce it) is granted grudgingly, and usually by omission of an explicit restriction, rather than willingly. That attitude is a major turnoff to a lot of people.

  123. Still... by kuitang · · Score: 1

    Well, there the ack (Amsterdam Compiler Kit) and tcc. The problem is that glibc has waaaaaaay too many extensions and most open-source code uses them liberally. And jed is a nice alternative to emacs, just as soon as they have an X11 display I'll be happy.

    --
    Don't believe in miracles -- rely on them.
  124. The developers changing things for the licence? by dbIII · · Score: 1
    then just require a physical button to be held down
    You are entirely missing the point here - the licence is there for the benefit of the developers and the end users - not just the new FSF agenda. Re-read what you wrote above and you will understand that would be just making it more difficult for those groups that already comply with the existing licence. Older hardware without the button would be stuck at the last version with the existing licence - which doesn't help the end user or the developer.

    Also consider that the device may not be a simple desktop computer that is in front of you but something in an entirely different location where you can not easily press the button.

    I see these clauses as being an inappropriate blunt instrument. In an effort to stop DRM you want to make some systems of authentication completely unusable and effectively do the same thing as posting the shadow password file on the net? I don't think you want to do that, and the person who does want to do that - Richard Stallman, has very strong views on passwords which probably make him think authentication is irrelevant. I think the instrument should be a bit less blunt or it may be a case of pushing for legislative change to stop DRM instead of a new rushed licence pushed onto the unwilling.

    1. Re:The developers changing things for the licence? by init100 · · Score: 1

      new rushed licence pushed onto the unwilling.

      I cannot see the GPLv3 being pushed on anybody. It is a new version, free to be used by anyone that want to use it. The only ones that might see it as a push are those that currently abuse the DRM (and/or patent) loopholes. They will have the license "pushed down their throats" in the way that certain "must have" projects might change their license from "GPLv2 or later" to "GPLv3 or later" for new versions. They then have to decide whether to strip out the DRM, fork the last version of the GPLv2 licensed code or write or license a proprietary or at least a non-GPLv3-licensed replacement.

    2. Re:The developers changing things for the licence? by dbIII · · Score: 1

      Look back to the start of this thing a few weeks back - the whole point was people such as RMS were insisting that Linus had to change to the new licence whether he liked it or not.

    3. Re:The developers changing things for the licence? by foom · · Score: 1
      the licence is there for the benefit of the developers and the end users - not just the new FSF agenda
      The license will only apply to code which the developers of that code apply it to. The FSF will apply it to all their code, and I expect many developers will similarly apply it to all their code. Some may not.

      Re-read what you wrote above and you will understand that would be just making it more difficult for those groups that already comply with the existing licence.
      I have little sympathy with makers of devices using GPLd software that do not allow me to modify the software. It is against the spirit of the current license, and will be against the letter of the next.

      Older hardware without the button would be stuck at the last version with the existing licence - which doesn't help the end user or the developer.
      If there's no way to replace the signing key on that hardware, the signing key is the same for every device, and the hardware developer doesn't want to give out the common key to all hardware owners, then, yes, they can't put GPLv3 software on that piece of hardware. Otherwise, they could tell the owner the signing key for their device.

      In an effort to stop DRM you want to make some systems of authentication completely unusable and effectively do the same thing as posting the shadow password file on the net?
      You still seem to be under some misguided idea that you can't use signed binaries with GPLv3. Again, you can. There just has to be some way for the owner to get or replace the signing key. This makes no systems of authentication unusable except the authentication of a device being unmodified by the owner, to the device maker.

      Nor does it do anything like posting a shadow password file to the net. I don't even know where you're getting that from...

    4. Re:The developers changing things for the licence? by init100 · · Score: 1

      the whole point was people such as RMS were insisting that Linus had to change to the new licence whether he liked it or not.

      RMS can insist all he want about the license for Linux. It is simply not in his power to decide. I still don't see this as the new license being "pushed down anyone's throat", which usually involves force or at least coercion, which this is not. RMS is certainly trying to influence Linus toward changing the license, which he is free to do, but Linus is also free no ignore him.

      And by the way it would be very hard to change the license version even if Linus agreed, because of the "GPLv2 only" clause in the Linux license.

  125. Re:Has Linus sold out? (was: Re:I can see both sid by dwandy · · Score: 1
    so your choices are:
    You are a troll like everyone else has indicated. You now drop to -5 in my personal viewing.
    You back up what you've stated with something intelligent. I listen (may not agree) but I do listen.

    Pick one.

    --
    If you think imaginary property and real property are the same, when does your house become public domain?
  126. Re:Wow, you missed the whole point of the DRM clau by Jack9 · · Score: 1

    Obviously those who release their code for free (as in beer) don't expect to make money from the act of others downloading the code.

    Unsurprisingly, this is how some companies/people are currently making money off of OS code. Redhat makes money off the distribution of code. Distribution for free allows greater adoption which allows for the need to quicker adoption in time-critical cases (premium digital channels for delivery is yet another way to make money off download-distribution while still being OS). This one of the many ways the community strength, reinforces itself ... only obvious after reaching a threshold of success of course.
    I will attempt to guess that

    There's lots of reasons, they amalgamate into a belief in a higher or LOWER cause, even if it's as terrestrial as the company's bottom line.

    Abstract reasoning for choosing a license.

    Open Source just exposes the logic. Nothing more.

    A statement describing the total net-effect of a practical reality.

    There is no license entitled "Open Source", but there is a movement/belief, so my statements don't "feel" like I contradicted myself.

    I am sorry, GPL3 is not the original topic of your discourse. My bad.

    --

    Often wrong but never in doubt.
    I am Jack9.
    Everyone knows me.
  127. mailme@plainsmedia.com by Anonymous Coward · · Score: 0

    mailme@plainsmedia.com

    checking for spiders

  128. Re:Sure to happen by Schraegstrichpunkt · · Score: 1

    Please. Ever heard of covert channels?

  129. Re:Wow, you missed the whole point of the DRM clau by nacturation · · Score: 1

    Distribution for free allows greater adoption...

    Yes, there are a lot of secondary or network effects which result from allowing others to download your source at no cost. Someone might dabble with the code and contribute something back. And of course, it's also possible under various licenses to charge a modest sum for the act of downloading the code. However, as a primary means an open source licenses aren't chosen in order to profit from the download of the code in and of itself. The profit comes as a by-product. As you say, Open Source just exposes the logic, nothing more -- it doesn't produce nor does it guarantee profit.

    There is no license entitled "Open Source", but there is a movement/belief...

    Various movements/beliefs use Open Source, but not all Open Source implies a movement/belief. In the late 1980s, I released some code for a software package I created into the public domain. I certainly didn't do that as part of a movement, nor did I do so because of any particular beliefs. I did so for various *reasons*, but to call those reasons beliefs would be too much of a stretch.

    --
    Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
  130. Re:Has Linus sold out? (was: Re:I can see both sid by init100 · · Score: 1

    I think the parent meant owner of the computer instead of end user.

  131. Re:Has Linus sold out? (was: Re:I can see both sid by init100 · · Score: 1

    Once I buy it, it's mine, and I have no intention whatsoever of going along with any scheme that allows the device makers to pretend otherwise.

    Not only that, but they sure should not use my GPL-licensed code, developed in my spare time, to further such an agenda. If they want to do this, then they have the option of staying away from GPL(v3) code.

  132. You DON'T UNDERSTAND the function by CarpetShark · · Score: 1

    The "function" of these tools is not to get you a free program to run on your computer. It's to get you and everyone else a FREE (as in freedom) platform, that they can all use and innovate on equally. Only copyleft-licensed software does that.

  133. Linux is what is is, because it's GPL'd by CarpetShark · · Score: 1

    Linux wouldn't be what it is today, except that it choose to use the GPL, and people came on board and contributed because of the guarantees that the GPL provides. If Linus hadn't taken that route, we'd all be working on HURD or something instead.

    Linus is good with Linux, but he's too practical to lead with visionary ideas. The GPL (maybe moreso, GPLv3) *is* a visionary idea, and it will be inspiring people centuries after Linux has been forgotten.

  134. That's the funny thing though by everphilski · · Score: 1

    the free software foundation is making a software license that restricts freedoms. Cracks me up.

    1. Re:That's the funny thing though by init100 · · Score: 1

      the free software foundation is making a software license that restricts freedoms. Cracks me up.

      They only restrict the freedom to take someone else's GPL-licensed code and adding restrictions further down the line, like e.g. preventing modified versions to run using DRM hardware (which subverts the license and essentially removes the freedom to run modified code).

  135. Should not crack you up. by Anonymous Coward · · Score: 0

    There are obviously varios qualities of freedoms. There are bad and good freedoms. No one should have the freedom to kill everyone he does not like, for example.

  136. Re:Sure to happen by Identifiable+Coward · · Score: 2, Interesting
    If you have the master keys (as you would, on a box you built yourself) then Trusted Computing means you *really* own your computer. You can prevent rootkit installation, and guarentee access to content no matter how DRM-encrusted. If someone else has the master key, why would you pay money for something you don't own?

    If, as you suggest, we shall be in control of the "master" keys then I fail to see how it would help the content industry.

    If, as I suspect, someone else shall be in control of the "master" keys then I can see perfectly clearly how it would help the content industry.

    As the idea of TC and DRM are being pushed by the content industry I think it would seem logical to assume that my suspicions are in fact correct.
  137. Re:Sure to happen by Identifiable+Coward · · Score: 1
    All you iPod-toting freaks have whored yourselves out, and real cheap too ... 99 cents.
    Ignoring the peurile insults do you actually think that everyone who owns an iPod uses iTunes? Now, who is being an idiot?

    Not quite sure how that got modded +2 Insightful either.
  138. Re:Sure to happen by tomhudson · · Score: 1

    Buying an iPod is supporting a business (Apple) that is doing its best to be THE drm content provider. So, don't be so quick with the "who's the idiot" bit. If you're against drm, don't buy Apple products that support drm.

  139. Re:Sure to happen by lgw · · Score: 1

    Dell really isn't in the business of helping the "content industry", nor really are processor or chipset manufacturers. Compare the revenues of Dell or Intel with e.g. the entire RIAA, and you'll see the "content industry" isn't going to be pushing the hardware vendors around.

    I know some of the people working on the Trusted Computing standards, and they work for big hardware vendors, not for "content industry" companies. There's a huge market for Trusted Computing that has absolutely nothing to do with DRM. Sure, the "content industry" is *also* pushing it, but so what?

    On the other hand, you can bet that future generations of gaming consoles will be very locked down and basically unmoddable, as that industry is very different from general purpose computing. Doesn't seem like much of a problem.

    --
    Socialism: a lie told by totalitarians and believed by fools.
  140. Re:Sure to happen by lgw · · Score: 1

    If I own the hardware I have access to anything I want to. If the data I want exists unencrypted at *any* point in any equipment I own, I can get that data. It's only a matter of cost and motivation. The technologies to extract the data from the processor, memory, or any bus on the system are all available off the shelf as test equipment - pricey, but available.

    --
    Socialism: a lie told by totalitarians and believed by fools.