Slashdot Mirror


GPL in Court - Good or Bad?

Irvu asks: "The Register has a lengthy opinion piece today about IBM's lawsuit, and the GPL. Barring a settlement this case will see the first test of the GPL in a court of law. Previously the GPL has functioned as a social contract with the implicit (albeit untested) force of law behind it. Any ruling now could radically alter the free-software/open-source landscape for good or ill. Andrew Orlowski dwells on these possible ills in his piece. What does Slashdot think? Is this test a good or bad thing? Do you have faith in the justice system (or IBM's Lawyers) to draw the right conclusions? And, how do you see any outcome affecting you?"

413 comments

  1. Either way it's a good thing by mjmalone · · Score: 5, Insightful

    A legal test of the GPL is a good thing no matter how it turns out. If the court case fails that just means that revisions need to be made, it would go against the philosophy of the open source community NOT to test the license. I don't know how much of a landmark case this is, it is kind of a gray area, not straight infringement.

    1. Re:Either way it's a good thing by Anonymous Coward · · Score: 5, Insightful

      I agree that the GPL should be tested, but given the nature of how law works in the US, I'm darned glad it's IBM's lawyers defending it.

    2. Re:Either way it's a good thing by Nucleon500 · · Score: 5, Interesting
      I don't think it's a grey area at all. The SCO case is almost exactly the kind of thing the GPL is supposed to prevent. (The difference is that SCO is trying to close the code "legally," not by embracing and extending.) It's crystal clear that SCO is attempting to infringe the copyright of thousands of developers. I'm glad that the test case is so clear-cut.

      It's important to remember that while this may become the first test in court (except the MySQL case), both RedHat's and IBM's lawyers are comfortable with it. And the other companies that have faced GPL issues have respected it; they didn't think they could fight it. SCO's leaders, a few armchair lawyers, and Microsofties are the only ones I've heard who don't think it'll be enforceable.

    3. Re:Either way it's a good thing by minusthink · · Score: 5, Funny

      "A legal test of the GPL is a good thing no matter how it turns out"

      I agree, as long I'm not paying for it.

      --
      "when life gets complicated, I like to take a nap in a tree and wait for dinner" - Hobbes.
    4. Re:Either way it's a good thing by TopShelf · · Score: 1

      Exactly - while IBM isn't doing this out of the goodness of their own heart, the Linux crowd should be ecstatic that Big Blue is on its side (for at least the moment).

      --
      Stop by my site where I write about ERP systems & more
    5. Re:Either way it's a good thing by Sancho · · Score: 1

      It should be interesting at least. I see no reason that the GPL should be invalid but other software licenses would be. Any lawyers have any insight into this?

    6. Re:Either way it's a good thing by MuParadigm · · Score: 5, Interesting


      Having read the article, I disagree with the author's comment that the GPL is a "social contract." I've read it, I'm sure a number of you have too. It's not a long document. I'd post it here, but I don't want to look like a Karma-Ho.

      Anyway, it *is* a document with teeth. Let's say you're an author, and a publishing company wants to publish your book. You have the copyrights. They cannot publish it without your permission. So you sell them the right to publish it for an advance of $40,000 and maybe a buck a book for every copy sold after the advance is paid off.

      Now, in the case of the GPL, instead of paying with cash or a portion of the profits from distribution, you pay by agreeing to certain terms and taking certain actions. For instance, if you distribute the software, you must include a copy of the GPL and a copy of the source code. If you modify the software and then distribute it, then you must do the same thing. That's your payement. It is required. If you don't take those actions (make the payment) then you can be sued for copyright violation. Outside of those conditions, you can do with it what you want for your own personal use and not worry about it.

      There isn't anything "nebulous" about the GPL, despite Blake Stowell's FUD. And it's not a social contract; it's a contract, pure, and simple, and legally enforcable.

      I can't wait to see this get tested in court. SCO will get their asses laughed out of court.

      Judge: Let me get this straight. You say code that you own was relesed under GPL by another company.

      SCO: Yes, that's right.

      Judge: And then you released it under GPL yourself -- but not really because you didn't know the code was in there.

      SCO: Yes, your honor. That's correct.

      Judge: You never read the code, even though it was freely available, and you were publishing and distributing it.

      SCO: That's right, your honor.

      Judge: (snickers) Get the fuck out of here. All claims resolved in IBM's favor.

    7. Re:Either way it's a good thing by gcalvin · · Score: 3, Interesting

      I'm usually not a "conspiracy theory" type, but my gut tells me that Microsoft is behind this, and that the whole idea is for SCO to lose. This gives Microsoft a poster boy for the fight against the Evil, Viral, IP-Corrupting GPL. "Look at poor SCO," they'll say. "They tried to work with the Open Source crowd, but those evil commies stole their IP and tricked them into giving it away, and as a result, they were destroyed." It doesn't matter that it's not true -- it'll look true enough to people.

    8. Re:Either way it's a good thing by Ybrog · · Score: 2, Funny

      Actually, I believe the correct reply is "I have no recollection of that."

      --

      bleh

    9. Re:Either way it's a good thing by shaitand · · Score: 4, Informative

      I think it say something that nobody has dared to challenge it thus far, and that IBM's lawyers considered it solid enough to allow IBM to use it prior to this. This is no fragile piece of ground, this is rock solid and I've never heard a lawyer say otherwise.

    10. Re:Either way it's a good thing by Anonymous Coward · · Score: 5, Insightful

      There isn't anything "nebulous" about the GPL

      Unfortunately, there are some nebulous areas in the license. Not in the basic concept, I agree.

      But once the GPL starts talking about "linkage", and trying to claim that Application A linked with GPL'd Library L means A has to be GPLed, while App A linked with GPL'd Operating System O does not, it's on thoroughly nebulous ground. The concept of "linkage" just isn't that clear cut, especially in the modern day with dynamically linked libraries, or in embedded systems where the OS is more often than not statically linked with the "application". This nebulousity is entirely self-inflicted by the GPL; it's not "FUD" spread by some evildoer. Had the GPL never tried to make this distinction in the first place, it wouldn't be a problem.

      While the obligations under the GPL are straightforward enough, it's not always clear when those obligations apply. Safest thing to do is assume that if you're anywhere near GPL'd code, then your code needs to be GPL'd as well. Over-broad, but it's the only way to be sure. The lack of clarity in the license one reason why the FSF has to maintain pages and pages of FAQs about the GPL, and perhaps one reason they're working on yet another version of the GPL.

      Making the license more complicated naturally increases the chances for bugs and unforeseen interactions and side effects. One of the nice things about the BSD license is that it's so bloody simple.

      Just because you find the intent of a work admirable doesn't mean you must assume the work is therefore perfect. The GPL shouldn't be treated as Holy Writ and viciously preserved against all "attack" from evil FUDsters. It should be improved where required.

    11. Re:Either way it's a good thing by oolon · · Score: 1

      The thing I find amusing is that the complaint about GPL has aways been its "viral" natural, but here we have SCO claiming the UNIX code has exactly this nature and worse cos with UNIX SCO believes you cannot donate your own code twice.

      James

    12. Re:Either way it's a good thing by fireboy1919 · · Score: 1

      The lack of clarity in the license one reason why the FSF has to maintain pages and pages of FAQs about the GPL, and perhaps one reason they're working on yet another version of the GPL.

      Something where you could be sure that linking is allowed, for instance? I suppose you could say their working on that, if by "working" you mean "have had available and in use for a long time."

      It's called the LGPL, and its a wonderful thing when you're writing libraries that you want everyone to use and freely improve upon.

      --
      Mod me down and I will become more powerful than you can possibly imagine!
    13. Re:Either way it's a good thing by bwt · · Score: 2, Interesting


      I think it's even more simple than that. MS goes behind the scenes and maybe drops $20 million to send SCO off to battle knowing full well they will be crushed. If the net effect is that Linux is slowed down by say 1 fiscal quarter, then they probably make their $20 million back several times over.

    14. Re:Either way it's a good thing by rnd() · · Score: 1

      Microsoft may not respect GPL'ed software as a business competetor, but I think you're wrong in asserting that Microsoft would steal GPL'ed code, or anything along those lines.

      --

      Amazing magic tricks

    15. Re:Either way it's a good thing by Xabraxas · · Score: 3, Interesting
      I think you're wrong in asserting that Microsoft would steal GPL'ed code, or anything along those lines.

      Why do you think that? There is no evidence that they did steal code but I don't think it's entirely out of the realm of possibility. It is much easier to steal open code and close it than it is to steal closed code and open it, for all to see. Besides Microsoft's track record isn't so good concerning illegal business practices. I am in no way suggesting it is fact, but it is entirely possible.

      --
      Time makes more converts than reason
    16. Re:Either way it's a good thing by iabervon · · Score: 1

      It's actually perfectly reasonable that they didn't find the code in the kernel before they released it. Nobody reads the whole kernel source, and they were in the middle of a lot of upheaval (plus the whole dot-com bubble); part of the advantage of open source is that the license allows you to redistribute stuff you didn't write and you don't have to read through the whole thing, either. If you did, no distribution would get anywhere.

      The issue is that they didn't stop distributing the kernel when they discovered code they suspected of being theirs in it. At that point, they could determine that somewhere in the licensing chain, someone had incorporated code they did not own, and the license on the work as a whole was not valid. But SCO continued to distribute the code, an action which could only be legal if either they accepted the validity of the license they received or if they decided to license the code in question under the GPL. Attacking the validity of the GPL doesn't help their case any, because nothing else gives them the right to distribute Linux. Nobody (else) seriously believes that the GPL relinquishes the copyright holder's rights.

    17. Re:Either way it's a good thing by aldousd666 · · Score: 1
      Yeah, and microsofties now have to eat their own hats, (albiet for different reasons -- I always swore I'd never use 'albeit' in conversation, let alone on slashdot) A relatively old article in Fortune details some of their problems.

      If these are the kind of people that the GPL has opposed to it, they're just saying that stuff because they're drowning in it themselves.

      --
      Speak for yourself.
    18. Re:Either way it's a good thing by EvanED · · Score: 1

      This is true, but the consequences of it being found out would be *tremendous*... they stick it in the Windows kernel and someone finds out, theoretically anyway the entire kernel would become open source. Same with office, etc. Suddenly MS has lost half its market 'cause people would legally spread it for free.

      Even with something like anticompetitive practices, the penalty is not set down, and as we've seen almost none was actually applied. The GPL mandates the (what MS would see are) penalties to be handed out, and there's no negoiating. You used the code? It's open source. No "well, what do you deserve" thinking by the judge.

    19. Re:Either way it's a good thing by Anonymous Coward · · Score: 0

      It will be damn good: when the GPL is declared unenforceable there will be a nice bunch of public domain utilities and software packages and the World economy will be pumping again.

    20. Re:Either way it's a good thing by GigsVT · · Score: 3, Insightful

      But once the GPL starts talking about "linkage", and trying to claim that Application A linked with GPL'd Library L means A has to be GPLed, while App A linked with GPL'd Operating System O does not,

      What are you referring to? How do you "link to an operating system"?

      The concept of "linkage" just isn't that clear cut

      Sure it is.

      it's not always clear when those obligations apply.

      No, it's very clear. When you distribute GPL'd code, you must abide by the GPL. If you distribute no GPL'd code, then the GPL doesn't apply to you.

      Safest thing to do is assume that if you're anywhere near GPL'd code, then your code needs to be GPL'd as well.

      Total FUD. It's completely safe to use GPL'd tools to create any kind of software you want, so long as you don't distribute any GPL'd code.

      Most of the FAQs actually explain copyright law, rather than grey areas in the GPL.

      There is at least one grey area, such as using a completely server-side modified GPL'd app on the web, that is one thing they are working on for version 3. Linking really isn't one of those grey areas.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    21. Re:Either way it's a good thing by IM6100 · · Score: 2, Interesting

      Has anybody pondered how IBM might benefit if the GPL fails in court? It isn't a clearcut truth that they would be hurt one way or the other, however the GPL is defined in court. IBM isn't a party using the Linux kernal in a way that they couldn't afford to make royalty payments if necessary. It's a lot of other people who face a dimmer future than IBM with that possibility.

      The GPL could end up nullified in such a way that the Linux kernal became sort of a free-for-all public domain piece of code. In that case, IBM wouldn't lose, nor would they lose if the GPL as it's interpreted by most people is upheld. It could be a win-win situation for IBM.

      Just some idle thoughts. Flame away.

      --
      A Good Intro to NetBS
    22. Re:Either way it's a good thing by Anonymous Coward · · Score: 0

      I agree completely. The GPL was specificly designed as a legal tool. It wasn't created in isolation, because the FSF and RMS consulted several lawyers for the drafting of it and made sure that it would stand as a legal contract.

      It's just as valid as anything Microsoft or any other software liscencing sceme is. If GPL is invalid then so is that little slip of paper saying "by opening this package you are agreeing to.." blah, blah, blah

      As far as just a "social contract", all contracts are social, as far as the fact that they are legal agreements to a certian type of human behavior,which sociaty is defined as nothing but a collection of human behaviors in a large scale of interactions. If you realy want to understand the social side of things, then you have to read the FSF and the GNU projects documentation, reasoning, and opinions on the matter.

    23. Re:Either way it's a good thing by IM6100 · · Score: 1

      Any time severe and clear-cut penalties are defined into a law or a contract, that just means that it would be worth billions of dollars to defeat it, if the threat of it going into force became a possibility.

      But we're wandered so far off into hypothetical that it's ridicuous. Microsoft doesn't need any of the GPL code out there. They can and do write their own code. They're far too egotistical an outfit to just suck in code from outside and use it. They learned the perils of doing that when they were forced to come up with a replacement for the Stacker code and put out a whole new version of DOS (DOS 6.22) because they'd made the mistake of cloning Stack's kludge (yes, it was a kludge, and I told anybody who used Stacker that it sucked).

      --
      A Good Intro to NetBS
    24. Re:Either way it's a good thing by IM6100 · · Score: 2, Insightful
      Let's say you're an author, and a publishing company wants to publish your book. You have the copyrights. They cannot publish it without your permission. So you sell them the right to publish it for an advance of $40,000 and maybe a buck a book for every copy sold after the advance is paid off.

      Now, in the case of the GPL, instead of paying with cash or a portion of the profits from distribution, you pay by agreeing to certain terms and taking certain actions.


      The big difference in the comparision you made above is that the author and owner of the copyright for the book have made an explicit contract signed in ink with the publisher. The GPL is an implicit contract. Anybody who happens along and acquires a copy of the GPL'd code is supposedly bound by this 'contract.' It's a heck of a lot like an EULA in that regard, and nobody here takes binding EULA's seriously. Why should we take the GPL seriously either?
      --
      A Good Intro to NetBS
    25. Re:Either way it's a good thing by runderwo · · Score: 4, Insightful
      The GPL is an implicit contract. Anybody who happens along and acquires a copy of the GPL'd code is supposedly bound by this 'contract.'
      Wrong. Notice that it is typically contained in a file called 'COPYING'. The GPL only applies when you redistribute the software.
      It's a heck of a lot like an EULA in that regard, and nobody here takes binding EULA's seriously. Why should we take the GPL seriously either?
      It's not like a EULA at all. A distribution license like the GPL is not invoked until you distribute the software to someone else. A EULA is a contract that is invoked when you install a piece of software (or sometimes, when you open the box).

      The GPL guarantees you to have no restrictions on your use of the software. Above and beyond that, it grants you certain distribution rights that you would not have otherwise under copyright law. If you reject the terms of the GPL, you may not distribute the software, but you can still use it for whatever purpose you want. A EULA, on the other hand, is designed to disallow you to even make use of the software if you do not accept its terms.

      See the difference now?

    26. Re:Either way it's a good thing by Anonymous Coward · · Score: 1, Interesting

      > Most of the FAQs actually explain copyright law, rather than grey areas in the GPL.

      And that's the problem -- the GPL's handling of software dependancies is entirely based on the concept of "derived works" under copyright law. And what exactly is a derived work is a complete gray area for software -- unlike music recordings or books where there are industry standards for using other people's work.

      Because this is such a gray area, there's been an enormous amount of supposition and lore injected by RMS and other GPL partisans. A court of law could easily come up with a radically different interpretation.

      > Linking really isn't one of those grey areas.

      Look pal, the GPL doesn't mention "linking" at all, which means that you are in full Gray Area terrority right now.

      The FSF uses "linking" as a sort of technical metaphor to make it easier for the partisans in the trenches to understand the derived works issue. But when pressed, they'll happily tell you to call a lawyer, who will tell you that it's not smart to cross some advocacy group with a chip on their shoulder, no matter if their position is legally sound or not.

      Furthermore, the FSF's stance on linking is out of step with the rest of the software industry (who happily links to MS Windows libraries without copyright worries) and isn't even internally consistant. So it's very difficult to call the issue cut-and-dried.

    27. Re:Either way it's a good thing by IM6100 · · Score: 1

      So. Okay, we've established that a contract is necessary to redistribute the software.

      Where is this contract? How many people have signed it? And how come I've never, ever, heard anybody testify or even casually mention having signed this contract?

      Unless there's a contract, signed in pen and ink somewhere, or at least a formalized agreement that witnesses will testify in court was made.... there isn't a contract. Contracts are not implicit things.

      --
      A Good Intro to NetBS
    28. Re:Either way it's a good thing by jbolden · · Score: 1

      Furthermore, the FSF's stance on linking is out of step with the rest of the software industry (who happily links to MS Windows libraries without copyright worries)

      In the case of Microsoft the copyright holder grants permission for that sort of linking. Microsoft's linking policies are quite generous. There really isn't a comparison.

    29. Re:Either way it's a good thing by jbolden · · Score: 2, Insightful

      If you didn't sign the contract then you had no right to copy the software at all. The default in US law is any form of copying is prohibited unless either

      a) The law specifically exempts it
      b) It is obviously implicitly permitted (like copying software from your harddrive into ram)
      c) The license explicitly permits it

      Don't agree to the GPL and you'd have to show you copies based on a,b or c.

    30. Re:Either way it's a good thing by Nucleon500 · · Score: 1

      That isn't what I meant; sorry if I said it. I'm saying that the people who adore Microsoft, Microsofties, are the ones who jump at the opportunity to assert that the GPL hasn't been tested in court, as though that makes it unenforcable. They seem to say this because they don't like the GPL, and want to disuade it's use. Which is just fine, but I don't think their assertion is truthful. Whether they'd violate the GPL is another matter, though after SCO, nothing surprises me anymore. They don't mind funding GPL-violating companies, though.

    31. Re:Either way it's a good thing by Xabraxas · · Score: 2, Informative
      The GPL mandates the (what MS would see are) penalties to be handed out, and there's no negoiating. You used the code? It's open source. No "well, what do you deserve" thinking by the judge.

      That's not true. If they fail to meet the agreement (GPL) then they are in violation of copyright. They can be sued for monetary damages, up to $150,000 per copy. The GPL is a license not a contract.

      --
      Time makes more converts than reason
    32. Re:Either way it's a good thing by shaitand · · Score: 1

      Can't say for sure, but I do tend to concur with the other response you got concerning the default, the gpl relaxes copyright law, and without the license the default would be regular copyright and not public domain.

      However I'm fairly sure that the stanford law professor who wrote the gpl is likely to be good with text book law, and from my understanding the gpl is a pretty text book license, founded on as solid law as exists.

    33. Re:Either way it's a good thing by Xabraxas · · Score: 1, Insightful
      They're far too egotistical an outfit to just suck in code from outside and use it.

      FreeBSD anyone?

      --
      Time makes more converts than reason
    34. Re:Either way it's a good thing by Anonymous+Shepard · · Score: 2, Interesting

      What would happen if American courts would judge the GPL invalid and European courts would uphold it? Does anyone have an idea?

      --
      I have a life. I really do. I've just chosen to ignore it.
    35. Re:Either way it's a good thing by Anonymous Coward · · Score: 0

      You got a reference? I looked through my MS docs and didn't find any explicit permission to link to Windows libraries (although MS obviously encourages it).

      Their developer licences cover redistribution, just like the GPl.

    36. Re:Either way it's a good thing by neonmagic · · Score: 3, Interesting

      All i'm going to say is - why should a US court decision reflect or change the way the rest of the world looks at the GPL or SCOs 'invalid' claims?

      The US courts are known for weird decisions that defy all logic (Microsoft vs DOJ anyone?). The problem is that a positive court decision for SCO will railroad other international governments and legal systems to adopt the 'US' way of doing things. This is a VERY bad thing. Why should US law influence the legal system in Australia?

      As to the GPL - it is clearly laid out. SCO cannot simply argue they didn't read the GPL, understand it, or mean to distribute a Linux (or open source) distribution under those terms. They knew very well.

      I know i'd be ignoring all results for IP based on a US court decision, until decisions were made fairly and logically by a Australian Court of law. US law is completely only valid within the US, or territories part of the US.

      What needs to be done now is for everyone who uses Linux to complain to their local court systems - unfair trading complaints and misrepresentation. Subpoena SCO to provide evidence based on licensing claims. etc Linux is used in just about every country in the world - if you can shut down SCOs case because they are refusing to provide evidence but want people to buy licenses with evidence (i.e unfair trading and misrepresentation) then you have won half the case. Quite elementary dear Watson...

      Dave W Pastern

      --
      Slashdot can go and get fucked.
    37. Re:Either way it's a good thing by rnd() · · Score: 1

      I see. I like Microsoft software and Open Source software.

      --

      Amazing magic tricks

    38. Re:Either way it's a good thing by waterbear · · Score: 1

      A legal test of the GPL is a good thing no matter how it turns out.

      This interesting thought is being currently put to the test in another and less formal way, in Germany. Legal expert Prof Spindler (link to Infoworld report) recently provided a legal opinion (in German - very long) saying that GPL is invalid in Germany (mainly it seems because of excessive disclaimers of liability).

      Spindler provided this opinion for VSI, a lobby group for closed source. It might conceivably be suspected that the legal objections could have been inadvertently exaggerated, or simple possible fixes overlooked. If the objections are confirmed as legally solid by independent opinion, maybe their effect could be taken away by relatively brief or simple amendment to GPL, e.g. making a specific saving for overriding statute/case law if a lack of saving for that law would otherwise invalidate the applicability of the GPL. (But I don't know enough about German law to make any more specific suggestions).

      This kind of thing may be a test of how the GPL can adapt in practice, given the large bodies of code that have been GPL'd under the existing version.

    39. Re:Either way it's a good thing by buck-yar · · Score: 1

      All i'm going to say is - why should a US court decision reflect or change the way the rest of the world looks at the GPL or SCOs 'invalid' claims?

      International law is US law, at least according to Ruth Ginsberg.

      "Our island or lone ranger mentality is beginning to change," Ginsburg says.

      Consider this. Two citations from other countries laws-- First race upheld in the admissions process, and more recently during the texas sodomy case.

      Can anyone see any problems with this?

    40. Re:Either way it's a good thing by rking · · Score: 1

      So. Okay, we've established that a contract is necessary to redistribute the software.

      No it isn't. Copyright law forbids you from copying and distributing the copies unless you have PERMISSION from the copyright holder. You do not need a contract, you need permission. The GPL gives you permission to copy and distribute the software in certain circumstances. If you do not meet the conditions it lays down then you do not have that permission. If you have some other permission from the copyright holders then you're covered by that. Otherwise you can't lawfully copy and distribute the software.

      Unless there's a contract, signed in pen and ink somewhere, or at least a formalized agreement that witnesses will testify in court was made.... there isn't a contract. Contracts are not implicit things.

      Incorrect. GPL does not rely on contract law to be valid, however your statement that contracts cannot be implicit is not true. Your suggestion that they have to be signed in pen or witnessed suggests no familiarity with contract law at all. Every time you walk into a shop and buy something you are entering into a contract with the seller. No signing required, no witnesses required.

    41. Re:Either way it's a good thing by clarkcox3 · · Score: 1
      The GPL could end up nullified in such a way that the Linux kernal became sort of a free-for-all public domain piece of code.

      No, if the GPL were nullified, then normal copyright law would take over, and all code under the GPL would revert to being normal, copyrighted source code. Then no one would have a right to use it until the original authors said so. So, even if the GPL were completely nullified, the authors of such code would need to re-release it under some other open source license (maybe an updated/revised GPL)

      --
      There are no tiger attacks in my area and it's all because this rock I'm holding keeps the tigers away.
    42. Re:Either way it's a good thing by jbolden · · Score: 1

      1) The fact that their products do it casuslly. You void any rights you have if imply non enforcement.

      2) The following comments The Microsoft licensing model does not contain licensing provisions that require an OEM, and potentially its licensees, to disclose the source code for its intellectual property in a widespread fashion to open source participants. An OEM building a server appliance with Windows 2000 Server operating systems and the SAK has the assurance the software code and added value it develops remain the OEM's intellectual property....Some forms of code linking and commingling may or may not trigger legal obligations under the GPL.

      I.E. they explicitly contrast their license with the GPL. I couldn't find their license on their website.

      Finally as for redistribution vs. simple linking the law doesn't recognize linking for your own use as anything other than fair use. Microsoft only has to grant you permission to redistribute they can't not grant permission to link for your own use.

    43. Re:Either way it's a good thing by hummassa · · Score: 1

      I agree even more, since it's IBM paying for it.

      --
      It's better to be the foot on the boot than the face on the pavement. ~~ tkx Kadin2048
    44. Re:Either way it's a good thing by poot_rootbeer · · Score: 1

      the whole idea is for SCO to lose.

      If that's true, there's going to be a mob of SCO shareholders with torches and pitchforks and personal lawyers, out for SCO executives' blood. Intentionally losing a multi-million dollar lawsuit is not exactly in the corporation's best interest.

      It doesn't matter that it's not true -- it'll look true enough to people.

      It'll only look true to people who have no idea who SCO is, and therefore wouldn't feel sorry for SCO if they fell to the Open Source Movement.

      Even Farkers know that SCO is the bad guy here.

    45. Re:Either way it's a good thing by Anonymous Coward · · Score: 0

      The main issues as The Register pointed it out is not whether the GPL can withstand a legal assault. The point is that it should be taken as much more than just a mere legal document, but more as a social contract (which should be obvious from RMSs' stand on the subject). The legalese of the document can be contested and as it is pointed out, it is the "legalistic" way of thinking that is apparently present in the USA, that is responsible for forming this social contract in form of the legal document.

      While it can be beneficial for the GPL to be legaly tested, it could also be its deprimand, as it migth come out seen as purely legal document with holes that can be exploited and used, not unlike holes in other laws and legaly binding agreements. In a sense a GLP can be directly comapared to copy right (not copyright -- noe is legal agreement, the other is social agreement). Copy right is social agreement between me, the author, having some say about what can and can not be done with my work, and you, the society, that has some say about what is expected from me to be recognized as an author (I could be best novelist the world has ever known, but I have to give other the right to talk about my novels, critisize them, even burn them if the don't like them, but on the other hand I expect to be fairly compensated for what I have given in such public manner. GPL is also a social agreement between me, the author, producing the work that is expressed in the form of computer program, and you, the society, that wants to use this work I have produced, maybe in the ways I haven't envisioned. On one side, I can have the recognition and ability to learn from society that scrutinizes each line that I have wrote, possibly adding some of their own, on the other side is the society that has the right to see, modify and redistribute, each and every part of my work, as long as it preserves my rights that I have decided to keep. These rights are not classical rights of some material value, but they are rather the rights of moral and social value, that enable me to grow intelectualy in my profession as well as in my personality (yes, I might even grow a huge ego to go with that).

      It would be best for GPL to be understood as a social agreement. As a kind of document that would not be judged merely on its legal arguments, but rather on the argument of the goals it intends to achieve. Unlike outlaws like Thomas Jefferson, RMS (but please, don't take the comparison too strictly) is still among us, and he is (sometimes truly annoyingly) vocal about the social goals it wants to achieve in this world. GPL is merely attempt at legal representation of these wishes. This is where the argument wraps back into itself. GPL wouldn't be needed, if it could be expressed in a way similar to expressions like copy right. Unfortunately to be recognized as a valid social contract in the USA it must be expressed as a legaly binding agreement (or law, but that would be too far fetching). When GPL is expressed as a legaly binding agreement, it can be judged solely on its legal merits. When GPL is judged merely on its legal merits, it no longer has the social component that was the one creating it. This is the argument as I undrestood it, and I see it as a valid argument.

      Social agreements can be bound and defined in courtrooms, but they also need open and thinking judges. These judges might not be too hard to find, but the arguments presented in the case will not be the arguments of social contracts, they will be the arguments of legal definitions and intentions. In this it might come out that IBM might even win in the courtroom, but GPL might still loose more that can be imagined at this point in time.

      This time is probably the most critical time in the development of the humanity. For the first time in histroy, private entities have the pover to monitor, control, and affect complete countries, sometimes almost complete continets. This is the time when governments openly deal with these power houses in order to obtain more and better

    46. Re:Either way it's a good thing by MntlChaos · · Score: 1

      150k per copy. M$ makes up to $200 per EU copy of desktop windoze, 149800 loss per copy of windoze sold. OUCH. 300k copies uses up their entire cash reserve!

    47. Re:Either way it's a good thing by Anonymous Coward · · Score: 0

      > the law doesn't recognize linking for your own use as anything other than fair use ... [MS] can't not grant permission to link for your own use

      I guess my point is that fair use may significantly weaken the normal (FSF) interpretation of what constitutes a derived work and when the GPL must be satisfied.

    48. Re:Either way it's a good thing by HiThere · · Score: 1

      They're obviously "sort of" behind this. They've even essentially admitted it. The question is, "What's their role?"

      What they've admitted to is basically "We saw this guy who wanted to attack our enemies, so we gave him a bunch of supplies." (I.e., bought a license without being asked or required to.)

      What is suspected is that MS put SCO execs up to this in the first place, and perhaps made some sub rosa deals that haven't come to light yet.

      Neither of these is exactly illegal. Unethical, perhaps, but that's no surprise. (And I even know some people who would say "That's just sharp business tactics.", and see nothing unethical about it, though I sure do.)

      That they've done anything more is dubious. I haven't seen any evidence indicating that they have. (True, I wouldn't expect to. But one shouldn't go around accusing entities of crimes without having reasonable evidence.)

      I have more trouble with SCOs executives. And, for that matter, with the FTC. And the Attorney General. I don't know why they haven't been charged with insider trading, e.g. Or even fraud. Or extortion. Or even, perhaps, racketeering. (It's an unreasonable charge, but it's more reasonable than in a lot of the instances where it is used.) So if there's a conspiracy, then it needs to be a broad spread one. More probable is just a bunch of people who like selective enforcement of the laws.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    49. Re:Either way it's a good thing by mpe · · Score: 2, Insightful

      The problem is that a positive court decision for SCO will railroad other international governments and legal systems to adopt the 'US' way of doing things.

      Invalidating the GPL would hardly be "positive" for SCO since it would mean that they could easily be sued into oblivion for copyright violations.

    50. Re:Either way it's a good thing by mpe · · Score: 1

      Has anybody pondered how IBM might benefit if the GPL fails in court? It isn't a clearcut truth that they would be hurt one way or the other, however the GPL is defined in court. IBM isn't a party using the Linux kernal in a way that they couldn't afford to make royalty payments if necessary.

      Assuming all the copyright holders would accept whatever IBM offered.

      The GPL could end up nullified in such a way that the Linux kernal became sort of a free-for-all public domain piece of code.

      Plenty of people would be very upset were anything to be placed in the public domain by court order. Especially those who have spent lots of money buying longer and more draconian copyright laws. If a court can simply strip copyrights from their holder(s) then all this lobbying and bribary has been for nothing.

    51. Re:Either way it's a good thing by Ric+Zero · · Score: 1

      Could you provide a pointer to the MySQL case, or an explanation. I noticed their license is not a normal GPL.

    52. Re:Either way it's a good thing by mpe · · Score: 1

      And that's the problem -- the GPL's handling of software dependancies is entirely based on the concept of "derived works" under copyright law. And what exactly is a derived work is a complete gray area for software -- unlike music recordings or books where there are industry standards for using other people's work.

      Thus what needs testing is copyright law. In the final analysis the relevent standard is that given in statute or case law. Rather than some "industry standards". Compilation recordings and anthologies have been around a lot longer than software.

      Furthermore, the FSF's stance on linking is out of step with the rest of the software industry (who happily links to MS Windows libraries without copyright worries)

      The FSF and Microsoft do not comprise the entire "software industry". It is also not hard to find situations where Windows software requires specific Microsoft DLLs to be present but only distributes some kind of Microsoft patch or service pack. Even where this includes lots of things not needed by the application.

    53. Re:Either way it's a good thing by dsojourner · · Score: 1

      IBM vs Microsoft's interests (even though it's not their case) ... I'm not sure I'd bet at this point.

    54. Re:Either way it's a good thing by mpe · · Score: 1

      The big difference in the comparision you made above is that the author and owner of the copyright for the book have made an explicit contract signed in ink with the publisher. The GPL is an implicit contract. Anybody who happens along and acquires a copy of the GPL'd code is supposedly bound by this 'contract.'

      What binds them is statute law, specifically copyright. This says that you need permission from the copyright holder in order to distribute a copy (modified or not) of a copyrighted work to a third party. Copyright law, as it now exists, grants copyright holders the ability to create a licence for the distribution of their works. The GPL is simply a form of licence which goes "Permission is granted subject to the following conditions...".

      It's a heck of a lot like an EULA in that regard, and nobody here takes binding EULA's seriously.

      An EULA is a completly different entity. It perports to cover use of a piece of software, not its redistribution.

    55. Re:Either way it's a good thing by Tetsujin28 · · Score: 1

      Not to mention QDOS...

      --
      - - - -
      The real Tetsujin 28 is a giant robot.
    56. Re:Either way it's a good thing by GigsVT · · Score: 1

      I.E. they explicitly contrast their license with the GPL.

      In any case, it's a good thing. Not everything MS says about the GPL is FUD.

      The GPL is, in fact, designed to prevent use of GPL'd libraries and software that involves tight integration (i.e. linked) with non-free software. This isn't a side-effect or some secret conspiracy, it's the purpose of the GPL, to provide exclusive advantages to the free software community that aren't available to non-free developers.

      The FSF is really honest about this too. The only FUD is that MS presents it as if it was some dirty secret of the open source community.

      The only side-effect is really the unfortunate use of GPL incompatible licenses by developers with good intentions. This is another reason the FAQs run kinda long, because there are so many licenses out there, and not all of them are able to be combined with GPL code.

      To respond to you post more directly, I think you grossly misunderstand what fair use is all about. It's a very limited provision of copyright law, in short, allowing use of limited sections of a copyrighted work for research, acedemics, news reporting, education, and things of that sort. It's doubtful that any linking would fall under fair use, but I don't think it's ever come up in court.

      On the other hand, your conclusions are right, but for the wrong reason. :)

      The GPL does not kick in unless you distribute GPL code or resulting binaries in some way. So for your own use, you are free to do what you like with GPL code. You just can't distribute it without worrying about compliance with the GPL.

      On the other other hand, MS EULAs do indeed put conditions on your mere use of their products. MS doesn't have to give you permission to do non-distribution things with their code, same as any license, but the EULA may place additional restrictions on the non-distribution use of their products. They must make a loophole in their EULA if it prohibits something that would be allowed by "default" under copyright law, and they want you to be able to do it. Think of it as a deny-all firewall with exceptions, compared with an allow-all firewall with exceptions.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    57. Re:Either way it's a good thing by GigsVT · · Score: 1

      The GPL guarantees you to have no restrictions on your use of the software

      The FSF does need to be very careful with one thing they are considering for GPL v3, the use of GPL'd web software.

      Reading RMS's writing, he is leaning toward considering the case where a program transmits HTML or whatnot over HTTP as redistribution.

      It's not unprecedented, since the program (often a script) generally copies parts of itself into the output, as a matter of course (think PHP).

      This would mean one would have to be very careful using GPL'd software for this use.

      This has the potential to be a very sticky subject.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    58. Re:Either way it's a good thing by jbolden · · Score: 1

      Linking code you own to other code you own for your own use involves making a copy for personal use. That's the fair use clause (right to make personal copies) that would apply

    59. Re:Either way it's a good thing by Boiled+Frog · · Score: 1

      Who would sue them? Linus?

      What would the damages be for distributing a free operating system?

  2. The GPL doesn't mean as much as people think by HiKarma · · Score: 4, Interesting

    I've always had doubts about the enforceability of the GPL in court.

    It seems to me it would be possible to release a proprietary program
    which takes a GPL'd source program, patches it and links it with
    independent binaries to make a new proprietary program. One could
    sell this program which does the patching, and the libraries, and
    provide the GPL code under GPL terms while keeping the modifications
    proprietary, as long as the modified code is never distributed.
    I would be concerned with any claim that the modifying program is itself
    a derivative work, though the mySQL folks make similar risky claims.

    However, I don't see this coming up in the IBM lawsuit. What might
    be tested there is just what it means to agree to a licence implicitly.
    We don't want that to be too strong. We don't want to add a lot of
    strength to those thousands of programs and web pages that say, "Use of
    this program indicates acceptance of these terms." Only deliberately
    agreeing to a contract should bind you to a contract.

    If you violate the GPL, you are not guilty of violating a contract,
    you are at most liable for infringing copyright. Which can result
    in a suit to stop you from doing the infringing, and for actual damages
    (hard to enumerate with free code) and statutory damages for the packages
    that properly registered their copyright (now you're talking.)

    In the latter case (the statutory damages) and with the injunction, you
    can then put pressure on somebody using your GPLd code to get out of
    the violation judgement by following the GPL. And indeed, the GPL says
    that if you follow the GPL, you are inherently not violating the copyright.

    However, the GPL itself can't make another person's code covered by
    the GPL. The fact that another person's non-GPL distributing of
    code is a copyright violation can be a tool to help you win a copyright
    suit, and that victory, or the threat of it, can make you put the screws
    to the defendant to do -- well, anything. Including giving you cash, or
    releasing their code under the GPL. It's actually up to you, the real
    owner of the GPLd code. If the FSF is the owner of GPLd code, it would
    probably use its power to force the new code to be released under the
    GPL, but that is its own philosophical decision. This is not inherent in
    the GPL.

    All the GPL says is, "If you modify and copy this code, and you release
    your modified program under the terms of the GPL, you're not infringing
    the copyright on it." It does not say, as some people think it does,
    that if you modify the code and copy it, your new work is under the GPL.

    1. Re:The GPL doesn't mean as much as people think by Anonymous Coward · · Score: 0

      Re-read the GPL. In particular, the definition of 'source' as the 'preferred form for making modifications'. That covers your patching program, since under those circumstances, said program would be the preferred form for making modifications.

    2. Re:The GPL doesn't mean as much as people think by leandrod · · Score: 4, Insightful
      > it would be possible to release a proprietary program which takes a GPL'd source program, patches it and links it with independent binaries to make a new proprietary program

      How practical would that be? Probably not enough to make a dent at the original program community, as any patches if useful would probably be small enough to be quickly replicated, and would be a pain to follow up with new versions.

      Now, suppose these patches contain the implementation of an essencial patent... well, this are just like binary modules for the kernel and codecs for mplayer; they exist, but they tend to become roadkill to further development, as most patents are interesting but liable to workarounds.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    3. Re:The GPL doesn't mean as much as people think by dackroyd · · Score: 1
      It seems to me it would be possible to release a proprietary program
      which takes a GPL'd source program, patches it and links it with independent binaries to make a new proprietary program
      Isn't that called a compiler. I know a friend who has one.
      It does not say, as some people think it does, that if you modify the code and copy it, your new work is under the GPL.

      If it isn't under the GPL then you have no right to use the code - as it's only by complying with the GPL that you are given the right to use the source code.
      btw That is why SCO is truly fuxored either they're lying and none of the Linux code is 'owned' by them or if they do 'own' some of the code then they've violated lots of Linux writers code by distributing their own version of Linux that isn't covered by the GPL (as they still claim ownership of their propriatary code.)
      --
      "Free software as in beer, copy protection as in racket" - Telsa Gwynne
    4. Re:The GPL doesn't mean as much as people think by Anonymous Coward · · Score: 3, Interesting


      It seems to me it would be possible to release a proprietary program which takes a GPL'd source program, patches it and links it with independent binaries to make a new proprietary program. One could sell this program which does the patching, and the libraries, and provide the GPL code under GPL terms while keeping the modifications
      proprietary, as long as the modified code is never distributed. I would be concerned with any claim that the modifying program is itself a derivative work, though the mySQL folks make similar risky claims.


      See Worlds of Wonder, Inc. v. Vector Intercontinental, Inc., 1986 WL 15608, N.D. Ohio, 1986. for an interesting comparison:

      1) W.O.W. had ownership of a valid copyright on its product, Teddy Ruxpin, as an audio-visual work.
      2) The audio-visual copyright encompasses all works created when a two-track tape is played in Teddy Ruxpin, one track directing its motors in synchronization with the other track playing stories and songs.
      3) Vector and Suma contributorily infringed this copyright by producing, adverstising, offering for sale, and selling a two-track tape which directly infringed the copyright when played in Teddy Ruxpin. There was infringement in that the tape directed the motors of Teddy Ruxpin and in synchronization played songs and stories, but it was of derivative work because the Vector tapes contained songs and stories different from those in the W.O.W. tapes.
      4) The Vector tapes do not have a substantial non-infringing use. The motor command track has no use other than to direct the motors of Teddy Ruxpin in synchronization with the playing of songs and stories on the audio track; and, there is little likelihood of market success based on the audio track alone.

      It does not say, as some people think it does,
      that if you modify the code and copy it, your new work is under the GPL.


      It says:
      Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.

    5. Re:The GPL doesn't mean as much as people think by HiKarma · · Score: 1

      You need to go further here. What I'm talking about can be viewed like a black box. It takes a tarball of GPL source code (which is distributed in full accordance with the GPL.) The black box is, among other things, a compiler (or a tool that invokes an existing compiler) to turn that source code not into the usual .o files, but into modified ones, as per your proprietary modifications.

      You do not distribute the modified GPL program, and as such, almost none of the terms of the GPL apply to you.

    6. Re:The GPL doesn't mean as much as people think by HiKarma · · Score: 5, Interesting

      That's the point. There is a lot of contention over clauses that say that "merely by doing something, you indicate your acceptance of an agreement."

      Most /.ers have been among those opposing such rules, by the way, in shrinkwrap contracts, and contracts on web sites that say that by using the web site you are bound to its terms.

      A typical clause of high contention have been those that say that you can't reverse engineer the program, for example.

      The reality is using and copying something can't bind you to arbitrary terms. Nobody seriously thinks they can. Copying any future articles of mine, by the way indicates acceptance of the terms on my web site, which include that you must pay me ONE MILLION DOLLARS for each article.

      The debate is over what you can bind people to with such contracts. Some court cases have gone one way, others have gone other ways.

      I would be amazed if a court were to say, "You put GCC in with your operating system, thus your entire OS must now be released under the GPL." I would be absolutely astounded.

      What a court might say is, "You violated the copyright of GCC when you bundled it in your proprietary OS, and therefor the remedies of copyright law are available to the FSF."

      Those remedies are:

      a) Actual damages -- how much the FSF lost because you did this. (likely to be hard to make large.)

      b) Injunctive relief -- remove GCC from your OS now, do what you can to remove it from copies you already released.

      c) Statutory damages -- at the court's discretion if GCC had its coypright registered with the LoC before the suit, these can be quite hefty financial damages.

      Now A won't scare anybody, but B and C could indeed force the OS vendor to do quite a bit, not because of the GPL or the court ordered relief, but to settle the copyright suit.

    7. Re:The GPL doesn't mean as much as people think by matth88 · · Score: 3, Insightful

      HiKarma makes some good points about possible GPL loopholes that might need to be addressed in a future version of the GPL, but I disagree that the GPL doesn't mean as much as people think, in fact, it means much much more.

      The *fact* that SCO has violated the GPL is the surest defense against the silly claims they are now making. The point of the GPL is that free software *remains* free, and that no organization (i.e. SCO) can use the embrace-extend-extinguish tactics that we've seen from Redmond.

      Love it or hate it, the GPL (assuming the courts agree) is an extremely potent instrument that will be very difficult to circumvent in any practical way. The "program to modify GPL code" you suggest could only be used by end users (since further distribution would be against the GPL, however the changes themselves happened), and would not work in the real world.

      In any event, if the GPL is tested and falls short, it will be revised and all our favorite projects will be relicensed under the new terms, and soon enough the old-GPL-releases will be obsolete. And Free Software lives on.

    8. Re:The GPL doesn't mean as much as people think by E_elven · · Score: 4, Informative

      >There is a lot of contention over clauses that say that "merely by doing something, you indicate your acceptance of an agreement."

      And that is where the problem lies. In general when speaking of such clauses, they are taking a right *away* from you. The GPL, however, is *granting* rights. You are under no duress that you must use the program, and you could not use it anyway if that clause were not in place. If the code in question were not GPL'd, the end-user would have no rights to it -they could use it if given to them by the copyright holder, but they could not distribute it further (whether they culd resell it after they wouldn't use it anymore should be covered under fair use, of course) in any shape. That's the all-important distinction; the GPL *grants* rights.

      --
      Marxist evolution is just N generations away!
    9. Re:The GPL doesn't mean as much as people think by Anonymous Coward · · Score: 1, Informative

      Well, there is a huge difference between the GPL and the average EULA: the GPL allows you to do things you wouldn't normally be allowed to do, such as give verbatim copies to your friends.

      The other EULAs make up arbitrary restrictions as they feel like, and hope that most will stick in court. Many of these restrictions take away rights that you would otherwise have (for instance they restrict the way you USE of the software, which expressly permitted by basic copyright law).

      Yes, the terms are on the GPL are "arbitrary", but they can be ignored, in which case you don't get to copy the software, which is an exclusive right of the copyright holder.

      I think any smart judge would see the difference. Considering how careful the FSF has been, even in the way they word things in their writings, I find it almost impossible to believe that a judge wouldn't find that someone violating the GPL is in fact violating copyright law.

    10. Re:The GPL doesn't mean as much as people think by grnbrg · · Score: 4, Interesting
      An example (taken from memory):

      The LAME mp3 encoder.

      The LAME mp3 encoder was, for a long time, officially distributed not in binary form or in source form, but as a patch against the reference code published by Fraunhofer.

      Due to patent encumberance and licencing restrictions, distribution of modified source or binaries was not permitted. But since the patches were 100% work of the LAME authors, they could distribute in this format. The fact that they were useless unless applied to the code distributed under a very restrictive license was irrelevant.

      A similar argument could be made for a (closed source) application that accepted as an argument a specific tarball (which could even be included in the package -- the GPL makes it freely distributable!) and output an application different from what is in the tarball.

      Sauce for the goose and all that....

      --
      grnbrg

    11. Re:The GPL doesn't mean as much as people think by Nucleon500 · · Score: 1
      You're making it too complicated. What you seem to be asking is, "Is it OK to make a non-GPL patch against a GPL program?" I think this boils down to a question of who made a derivative work, the patch author or the patch applier (in your case, the user). This isn't really a GPL issue, it's a question about what constitutes creating a derivative work, which is currently ill-defined for software.

      I would argue that if you create a patch against a program, you have derived from it. If you have a GPL program A, and you make a derivative A+B, and you then seperate B and distribute it, and expect users to recreate A+B, then for all intents and purposes, you've distributed A+B.

    12. Re:The GPL doesn't mean as much as people think by HiKarma · · Score: 3, Insightful

      Smart judges are not supposed to see the difference. The law must be applied consistently, and not nicely for things we like and badly for things we don't. Copyright law says you can't make copies. It doesn't say you can be bound to a contract if you do, only that you are infringing copyright. A judge shouldn't change that just because the contract you are alleged to have agreed with does nice things.

    13. Re:The GPL doesn't mean as much as people think by CoughDropAddict · · Score: 1

      Most /.ers have been among those opposing such rules, by the way, in shrinkwrap contracts, and contracts on web sites that say that by using the web site you are bound to its terms.

      That's because most of the time, they attempt to impose conditions on actions that are already legal to perform. The GPL grants rights to perform actions that would otherwise be illegal, but these grants are conditional on obeying the terms of the license.

      Those remedies are: [...]

      I think "injunctive" is what matters most. It is the right to demand compliance. What company wants to ship a product that they will have to recall/re-engineer if someone discovers the truth? What will happen to that company's reputation when someone does?

      The main barrier is the cost of litigation. But in all cases so far, bad PR was enough to convince the companies that it is in their best interest to comply.

    14. Re:The GPL doesn't mean as much as people think by arkanes · · Score: 2, Insightful
      Smart judges are very aware of the difference between "we will allow you to do this thing that you normally cannot legally do, as long as you follow these guidelines" and "you can't do these things because we said so".

      Copyright law certainly DOES permit the author of the work to allow redistribution. Such a thing is called a redistribution license. They're pretty common in the world of IP. Read up on it sometime.

    15. Re:The GPL doesn't mean as much as people think by arkanes · · Score: 1

      You are correct, to a degree that this is possible. The limit there is whether or not your work is a derived work of the original GPLed product that you're patching. The FSF says it is, but it'd really take a court case to decide. In fact, what you describe is very close to how binary-only kernel modules work.

    16. Re:The GPL doesn't mean as much as people think by arkanes · · Score: 1
      I'm going to reply to my own post because I've re-read some of the context of your original post and I want to clarify. You're certainly permitted to put a notice in all your Slashdot posts stating that reproducing them entails acceptance of the terms on your website (provide a link) and that I'll pay you ONE MILLION DOLLARS for reproducing them.

      Now, your license terms can't do anything to me so long as I copy your articles within the limits of fair use - selective quoting in my replies, for example. If, on the other hand, I decide to make a book out of Slashdot comments, you'll be perfectly entitled to come after me for copyright infringment.

      Basically, the GPL is an open offer for licensing, just as your .sig license would be. If a company finds it's terms disagreeable, they have the option of contacting the author for other terms, or using it anyway in violation of the law. It's possible that the court decision for such a violation would include compliance with the original license.

      Now, as for EULAs. An EULA is the equivilent of a .sig that says "by reading this post you agree to pay me ONE MILLION DOLLARS". See the difference here? In the first case, you're making an open offer to license rights that aren't normally granted, either in return for ONE MILLION DOLLARS or with certain conditions. In the second case, you're attempting to make an informal contract without consideration.

    17. Re:The GPL doesn't mean as much as people think by rmohr02 · · Score: 1
      Quoth the poster:
      We don't want to add a lot of
      strength to those thousands of programs and web pages that say, "Use of
      this program indicates acceptance of these terms." Only deliberately
      agreeing to a contract should bind you to a contract.
      Quoth the GPL:
      You are not required to accept this License, since you have not
      signed it. However, nothing else grants you permission to modify or
      distribute the Program or its derivative works.... (Section 5)
      Quoting the GPL in a /. Comment: -1 Karmawhore.
    18. Re:The GPL doesn't mean as much as people think by russotto · · Score: 1

      The Teddy Ruxpin case twists copyright law so badly out of joint I'd hate to see it cited anywhere else and thus given more value. 1) Teddy Ruxpin isn't an audiovisual work, any more than a player piano or a VCR is. It's an instrument. A Teddy Ruxpin tape might be an embodiment of an audiovisual work (with Teddy as the playing device, substituing for the VCR+TV), but Teddy ain't. 2) A copyright is on one work; creation of a derivative work may infringe that work's copyright but the original copyright doesn't cover those works. 3) The ridiculousness of 3) follows from the ridiculous of 1 and 2. Playing a non-Teddy-related tape in Teddy doesn't create a derivative audiovisual work. It moves a toy bear around. It may move it around in a derivative fashion (if Vector had copied portions of the W.O.W tapes), but otherwise it isn't a derivative work. 4) There's no direct infringement, therefore no contributory infringement, therefore other uses of the Vector tapes are irrelevant.

    19. Re:The GPL doesn't mean as much as people think by bigsteve@dstc · · Score: 2, Interesting
      How practical would that be? Probably not enough to make a dent at the original program community, as any patches if useful would probably be small enough to be quickly replicated ...
      On the contrary, the patches would probably be either large or hard to reproduce without knowledge entailed in patents / trade secrets. Otherwise why bother?

      The viability of this approach would depend on the intrinsic "added value" of the patches, versus the costs to both the software vendor and the end customer. Bear in mind that the software vendor would typically require the end customer to hold the patches as trade secret and/or forbid any reverse engineering.

      In addition, anyone who distributes proprietary patches to GPL'ed software must be prepared for the possibility of legal action against them. And they must also be prepared to go after people who violate their patents / trade-secrets. At the end of the day, it will be the courts who decide if this approach is a violation of the GPL.

    20. Re:The GPL doesn't mean as much as people think by bitmason · · Score: 1

      Ironically, a lot of SCO's case will also boil down to how broadly derivative works extend. Here's a link to an analysis of SCO's case as being primarily about how broadly a derivative works claim can extend: http://www.illuminata.com/cgi-local/pub1.cgi?docid =scoderived

    21. Re:The GPL doesn't mean as much as people think by leandrod · · Score: 1
      > On the contrary, the patches would probably be either large or hard to reproduce

      Yes, and it will be very hard to keep the patches against an ever-changing codebase. Not impossible, but unlikely.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    22. Re:The GPL doesn't mean as much as people think by Software · · Score: 2, Interesting
      You're mostly correct, except for this part:
      You are under no duress that you must use the program, and you could not use it anyway if that clause were not in place.
      This is not correct. You can use a GPL'd program, but you may not redistribute it. To quote section 0 (in part):
      The act of running the Program is not restricted.
      You don't have to agree to the GPL, but you have no rights to copy the program unless you do agree.
    23. Re:The GPL doesn't mean as much as people think by gbjbaanb · · Score: 0, Redundant

      "you can't do these things because we said so" - doesn't the GPL say that I must make any derivative work GPL (or at least 'freely distributable'). How come that restriction on what I could legally do with my code is ignored in discussions about the GPL?

      The GPL is flawed - if you want code to be free, you should release it under a licence that says 'this is free. do what you want with it', and leave whoever uses it to make their choices with their code. Nice, simple, easy. Adds to the world of free software without making any restrictions whatsoever.

    24. Re:The GPL doesn't mean as much as people think by RALE007 · · Score: 3, Insightful
      Bundling GCC with a proprietary OS does not violate the GPL, let alone would anyone even suggest the OS should be GPL'd.

      At most the company bundling GCC with an OS would have to make the _GCC source_ available to anyone who wants it. That's it. If the OS maker used GCC code, added their own improvements, and released the new compiler (bundled with an OS, on cd's, or even off it's website for free) the company would have to make the source code for their _new complier_ freely available to anyone who wants it under the terms of the GPL.

      The licensing of bundled pieces of software have nothing to do with one another. Bundling OSS and proprietary software together doesn't mean the GPL will "infect" the proprietary. Now if you take portions of GPL'd code and incorporate it in your OS, the OS is supposed to be GPL'd. If you don't want to GPL your OS, don't incorporate GPL'd code into it! Write your own.

      --
      Beware blue cats moving at .99c
    25. Re:The GPL doesn't mean as much as people think by God!+Awful+2 · · Score: 1


      Isn't that called a compiler. I know a friend who has one.

      no.

      -a

    26. Re:The GPL doesn't mean as much as people think by HiKarma · · Score: 1

      GCC may be a bad example. Consider instead a GPLd library (not LGPL, real GPL) statically linked with a program.

      Some think that doing so puts the program under the GPL, that you can be compelled to release the source of that program.

      I doubt that. I think what you're doing is violating the copyright of the library. When you are sued for doing so, you could avoid the suit by releasing the program under GPL, or settle it by doing so, but you can't be _forced_ to release it under GPL.

      At most, you can be forced to stop using the library, pay any money lost to the author of the library, and possibly pay statutory damages.

      Again, the statutories give teeth to the GPL if the copyright is properly registered before the suit. But to be strict, you can't force the GPL on the enclosing program.

      I believe this would be the same if I took a GPL program, heavily modified it and improved it and sold it in a proprietary manner. They could not force me to publish my changes. They could make me pay damages so high I might decide I would rather publish, but the choice to pay or publish would remain mine.

    27. Re:The GPL doesn't mean as much as people think by arkanes · · Score: 3, Insightful

      It's very simple. Because you can't legally modify and then re-distribute someone elses work. Period. You can have all kinds of arguments about what defines free, and what kind of freedom we want, but those are idealogical arguments, and not legal ones. In the absence of permission from the author (usually, but not always, in the form of a license), you cannot re-distribute copyrighted works, or create & distribute derivitive works. Period.

    28. Re:The GPL doesn't mean as much as people think by grofty · · Score: 1

      So as SCO claims the work as theirs, the source of the code they used has had its copyright infringed. Boy, is AT&T gonna make a killing by suing SCO for damages of the amount they get from any lawsuits, settlements, licenses and the versions of Linux they sold as a distributor. I think I may call my broker and buy some of that "T" stock now.....

    29. Re:The GPL doesn't mean as much as people think by Xabraxas · · Score: 1
      The viability of this approach would depend on the intrinsic "added value" of the patches, versus the costs to both the software vendor and the end customer.

      Kinda reminds me of when people applied all kinds of patches to minix to get a more usable system. Eventually people just didn't want to do it anymore and Linux was born.

      --
      Time makes more converts than reason
    30. Re:The GPL doesn't mean as much as people think by dmaxwell · · Score: 1

      I believe this would be the same if I took a GPL program, heavily modified it and improved it and sold it in a proprietary manner. They could not force me to publish my changes. They could make me pay damages so high I might decide I would rather publish, but the choice to pay or publish would remain mine.

      Of particular interest in litigation would be any profit the proprietized GPLed program made. Whether the copyright owner would have made money or not isn't the issue. The issue would be that you profited from use of his property. Anybody know how gains from such use are handled by courts?

      And yes, you're correct. The outcome of misappropiating GPLed software isn't necessarily that the whole work becomes GPLed. It is an option when settling with a copyright holder. That many GPL violators have taken that option doesn't make it a foregone conclusion. I think when it comes down to it, violators find it cheaper to comply with the GPL rather than writing the copyright holder(s) a large check for a different license or fighting it in court and paying their lawyer and the copyright holder.

    31. Re:The GPL doesn't mean as much as people think by onenil · · Score: 1

      The most common place I've seen this type of clause used is on websites... "Use of this website is subject to our terms and conditions".

      I would argue that your use of my website is not a given right, unless you agree to my terms and conditions. Where is it defined that connecting to a website and using any of its functions is any more of a given right than that of logging on to an anonymous FTP server, downloading a piece of code that has a similar clause attached to it, modifying it, and publishing it?

      Afterall, I'm granting you the right to use the application (website) that I've provided in the first place, I can take that away by disallowing your IP block, setting a cookie on your browser, or just taking the site offline. You are under no duress to use the website either.

      Using your same argument, I woudl actually suggest that the GPL is taking away rights from the use of the source code you download with it. You have a whole heap of text files that you can do practically anything with, but once you read the GPL, suddenly you don't have the rights to do a couple of the things you could before you read it. Without the GPL attached, you are allowed to do a lot more with the code you've got.

    32. Re:The GPL doesn't mean as much as people think by HiKarma · · Score: 1

      Among the remedies are actual damages. So yes, if the party sold the program for money, some or all of that money could be awarded to the plaintiff (the owner of the GPLd program.) Combined with money they lost, which might be zero for many programs that are not sold.

      If you gave away the program but, in violation of the GPL, didn't give away the source, the figuring of actual damages would be challenging! Courts care much more about money than principles of free software.

      As for the settling, it is indeed an option to settle by following the GPL. But the truth is that statement might mislead you. Anything the copyright holder will accept is an option when settling. You can settle by standing on your head and going boop-boop if that is acceptable to the copyright holder.

      As such, the terms of the GPL don't really enter into it. The GPL is not, I believe, a "here's what happens to you if you use GPL code" licence. It's a "here's what won't happen to you if you follow the GPL" licence. What won't happen is you won't be sued.

      The GPL is called a viral licence because it seems to bind further people down the chain to its terms. It doesn't. It just tells people down the chain they won't be violating copyright if they follow the terms. It misleadingly suggests that's the only way to avoid getting sued.

      In fact, many authors of GPL programs offer their programs under other licences too, including commercial ones.

    33. Re:The GPL doesn't mean as much as people think by cyril3 · · Score: 1
      Only deliberately agreeing to a contract should bind you to a contract.

      Should maybe but that has not been law for a long time. A finding like that would probably be beyond the ability of any judge at this point. It would destroy lots of very good and useful law that suggests that acceptance of a contract is implied by acting in accordance with the contract. It works both ways and to throw it out because occasionally it works against the 'weaker' party to a contract ignores the times it has acted as a shield against 'stronger" parties looking to void contracts that they have gone along with till it suited them.

      The argument about accepting EULA's as contracts will go on (and on and on) but a desire to avoid them is not a good reason to support changing good law.

      Personally I have always considered the GPL to be heavily reliant on acceptance of terms being implied by actions. No one signs anything with the GPL. How else do you evidence accepatnce.

    34. Re:The GPL doesn't mean as much as people think by IM6100 · · Score: 1

      Minux is a pedagogical Operating System intended to be used for educational purposes. There was no intent by the original author for it to be extended and bloated into the kind of project the Linux kernal has become.

      The people who 'gave up' on Minix and moved over to work on Linux did so because a project that better met their needs became available. Not because Minix 'failed' in some way.

      --
      A Good Intro to NetBS
    35. Re:The GPL doesn't mean as much as people think by IM6100 · · Score: 1

      Quoth the GPL:

      You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works....


      Okay. So where does the person who wants to accept the License sign? Until there's a place to sign the contract, there isn't a contract. Without a signed contract, there isn't any way to enforce said contract.

      This paradox is more important than most people are willing to accept.

      --
      A Good Intro to NetBS
    36. Re:The GPL doesn't mean as much as people think by bnenning · · Score: 2, Informative
      Okay. So where does the person who wants to accept the License sign? Until there's a place to sign the contract, there isn't a contract.


      The GPL isn't a "contract". It's a unilateral grant of permission to perform acts normally prohibited by copyright law. It's the exact opposite of most commercial EULAs, which are (IMO invalid) attempts to unilaterally remove your pre-existing rights in exchage for nothing.


      Without a signed contract, there isn't any way to enforce said contract.


      The GPL doesn't need to be enforced. Only copyright law does. If I modify and sell your GPLed software without providing source, you sue me not for "violating the GPL" but for copyright infringement. My only defense would be the GPL, but since I didn't abide by its conditions I won't be able to invoke it.

      --
      How to solve most of our problems: 1.Lots of nuclear plants. 2.Cure aging.
    37. Re:The GPL doesn't mean as much as people think by mvdw · · Score: 1

      It's a shame that the post of yours in the whole thread that is the clearest outline of your position is so far down the thread. Until I read this one, i wasn't really sure where you were standing, but this puts your position in a clear place.

    38. Re:The GPL doesn't mean as much as people think by jbolden · · Score: 1

      I could see a court arguing that by linking to GPLed code you voided your claim to copyright protection for those things not covered by the GPL. While its unlikely they would force a company to release source they might very well void their protections under the law which pretty much amount to the same thing

    39. Re:The GPL doesn't mean as much as people think by HiKarma · · Score: 1

      Oh, indeed there are implicit ways of being bound to a contract. But we're talking about parties who don't follow allong with the GPL way. We're talking people who take the code, modify it and just release the binaries of their new work.

      They aren't following the GPL in any way. They are plain and simple violating the copyright.

      People violate copyrights all the time, of course. I venture that some /. users may have violated the copyrights of RIAA members, and distributed songs in violation of copyright. Possibly. Are you open to the idea that if those songs had a licence on them which said, "The only legal means to distribute this song is by accepting the terms of this licence, which requires you to do XYZ"

      If you were then caught distributing such a song on Kazaa, would you want the law to be able to bind you to the terms on it? Is the GPL only OK because software is text and the software distros have a file in them called "LISENSE" or "read.me" that you might be expected to read, and music doesn't have a means to do that?

      Truth is you make copies all the time. Every time you visit a web site you read it by copying it with an HTTP fetch to local buffers, and then it is copied again to render it and display it. Most of those pages come with policy statements saying "use of this web site is subject to various conditions. By using the site you agree to them."

      They give you the site free. Are you bound?

    40. Re:The GPL doesn't mean as much as people think by jbolden · · Score: 1

      The problem with SCO's case is that factually they are wrong. Where they claim "derived" the aren't going to be able to show the chain of derivation. I.E. they can't prove the facts they need to show. SCO is simply too weak a case to prove much of anything.

    41. Re:The GPL doesn't mean as much as people think by Xabraxas · · Score: 1
      The people who 'gave up' on Minix and moved over to work on Linux did so because a project that better met their needs became available. Not because Minix 'failed' in some way.

      Hmmm. I don't recall ever saying Minix 'failed' so why did you put that in quotations? Minix did everything it was supposed to do. Other people wanted it to do more so they patched it. That became too tedious so they, namely Linus, created something else. I don't see the argument here.

      --
      Time makes more converts than reason
    42. Re:The GPL doesn't mean as much as people think by screenrc · · Score: 1
      Nice thread.


      But why is this different to cut & paste and
      code extentions by hand, compared to doing
      it automatially via a program ?


      The important issue here is if the 'black box'
      or the act of modifing, is itself derived work.
      If the program itself is derived work then you cannot
      distribute it as proprietory. Note, we are not
      talking about the output of the 'black box'
      (which is obviously derived work), I am only
      questioning whether the 'black box' program is derived
      work. Hard to tell.

    43. Re:The GPL doesn't mean as much as people think by Xabraxas · · Score: 1
      There was no intent by the original author for it to be extended and bloated into the kind of project the Linux kernal has become.

      While it is clear that Minix was only intended for computer science classes that doesn't take away from the fact that it didn't do what people wanted it to do without significant patches. That wasn't cutting anymore. You can read about this anywhere. The choice was "bloated" Linux

      or

      Featureless Minix?

      The choice was obvious.

      --
      Time makes more converts than reason
    44. Re:The GPL doesn't mean as much as people think by tricorn · · Score: 1
      If you gave away the program but, in violation of the GPL, didn't give away the source, the figuring of actual damages would be challenging!

      Damages might be the fair market value of the source code not released, which leads to an interesting situation. Since, by definition, a fair market value would be a price that the defendant would agree to sell it for (as one half of the equation), a fair solution would be for the court to require the defendant to name a price, and the plaintiff to be able to choose to take the money or the source code (and then release or keep as desired). Sort of like having one person cut the cake, and the other person choose which half to take.

    45. Re:The GPL doesn't mean as much as people think by tricorn · · Score: 1

      If I give you detailed directions on how to buy a copy of a (copyrighted) picture, and how to modify that picture in order to achieve some amusing effect (say, putting devil horns on Bill Gates), are my directions to you a derivative work of that photograph? I don't think so, but the FSF's reasoning would say it is. Do you have reason to think that a court would rule one way or the other?

    46. Re:The GPL doesn't mean as much as people think by HiKarma · · Score: 1

      This would be a whole new way of looking at it.

      Actual damages are the money lost by the copyright holder. My understanding is that because non-monetary things are so hard to quantify, that's what the statutory damages are there for.

      Outside the USA, laws give much stronger accord to the "moral rights" -- right of control over what's done with your art. The US tradition is much more financial.

      The question of how much money you lost because somebody else gave away binaries without source... Well, there's no saying a court couldn't try to figure it out but we won't get far predicting how they will do it.

    47. Re:The GPL doesn't mean as much as people think by Pofy · · Score: 1

      >A finding like that would probably be beyond the
      >ability of any judge at this point. It would
      >destroy lots of very good and useful law that
      >suggests that acceptance of a contract is
      >implied by acting in accordance with the
      >contract.

      Out of curiosity, does such a law actually exists? And if so, which country do you talk about? When I studied contract law (admitadly in a small course that touched many areas of laws but none really thoroughly) there were specific "rules" for how to enter a contract but no mention of what you just said.

    48. Re:The GPL doesn't mean as much as people think by bigsteve@dstc · · Score: 1
      In other words, the intrinsic value of the Minix patches was not high enough to make the approach viable in the long term. (Remember that Minix was never more than "hobby" computing.)

      But suppose that the patches incorporated patented technology that made database queries run 10 times faster. I expect that some companies would be willing to pay a lot of money for something like that, and would be prepared to put up with the long term inconvenience of patching.

    49. Re:The GPL doesn't mean as much as people think by dipipanone · · Score: 1

      The GPL is flawed - if you want code to be free, you should release it under a licence that says 'this is free. do what you want with it', and leave whoever uses it to make their choices with their code.

      Such licenses exist. If you wish to release *your* code under such a license, you're perfectly free to do so.

      Coders who wish to ensure that those people who derive benefit from their code are obligated to give something back in return, on the other hand, should use the GPL. That doesn't make it flawed, that makes it fit for the purpose it was designed for.

      If those aren't your purposes, use the license you prefer.

    50. Re:The GPL doesn't mean as much as people think by SQLz · · Score: 1

      Its trial by jury.

    51. Re:The GPL doesn't mean as much as people think by leandrod · · Score: 1
      > suppose that the patches incorporated patented technology that made database queries run 10 times faster

      In this case it would be much simpler to just use BSD. Not so important.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    52. Re:The GPL doesn't mean as much as people think by bigsteve@dstc · · Score: 1
      In this case it would be much simpler to just use BSD. Not so important.
      I didn't say that this hypothetical patch was a patch to the Linux kernel. Suppose that it was a patch to the MySQL codebase.

      The details of a hypothetical example are not particularly important. My point is that there are highly plausible examples where proprietary patches could have sufficiently high intrisic value to make the patching approach attractive ... if you ignore the moral issues, and the potential cost of litigation.

    53. Re:The GPL doesn't mean as much as people think by leandrod · · Score: 1
      > Suppose that it was a patch to the MySQL codebase.

      Then use PostgreSQL.

      > The details of a hypothetical example are not particularly important.

      Agreed. In general, there is always a piece of non-copylefted software one can hoard. Going for the GNU GPL stuff just makes no sense.

      Now suppose the world had turned GNU GPL and all free licenses were copyleft. Even so, the cost of maintaining the patches, and the fact that you can usually work around stuff would be enough to discourage people.

      Anyway, what is required from the GNU GPL is that it be good enough. Perfection is not attainable in this fallen world. Ultimately the scenario you paint is relevant if one presupposes a valuable patent; this is quite out of the scope for the GNU GPL, and must be dealt with political action to change the patent law.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    54. Re:The GPL doesn't mean as much as people think by anthony_dipierro · · Score: 1

      It seems to me it would be possible to release a proprietary program which takes a GPL'd source program, patches it and links it with independent binaries to make a new proprietary program. One could sell this program which does the patching, and the libraries, and provide the GPL code under GPL terms while keeping the modifications proprietary, as long as the modified code is never distributed.

      I don't think that would work. By applying the patch you'd be guilty of copyright infringment, therefore by selling the patch you'd be guilty of contributory and/or vicarious copyright infringement.

    55. Re:The GPL doesn't mean as much as people think by anthony_dipierro · · Score: 1

      In general when speaking of such clauses, they are taking a right *away* from you.

      No. A contract can't just take rights *away* from you. There must be consideration on both sides. In all binding EULAs you are granted certain rights in exchange for meeting certain conditions. The GPL is no exception.

    56. Re:The GPL doesn't mean as much as people think by anthony_dipierro · · Score: 1

      Well, there is a huge difference between the GPL and the average EULA: the GPL allows you to do things you wouldn't normally be allowed to do, such as give verbatim copies to your friends.

      But so does every EULA. For instance, the Windows EULA allows you to "store or install a copy of the SOFTWARE PRODUCT on a storage device, such as a network server, used only to install or run the SOFTWARE PRODUCT on your other COMPUTERS over an internal network" if you acquire a separate license for each concurrently used copy.

      The other EULAs make up arbitrary restrictions as they feel like, and hope that most will stick in court.

      I'm not sure what's arbitrary about their restrictions. Why is the restriction not to reverse engineer arbitrary but the restriction to distribute source code not?

      Many of these restrictions take away rights that you would otherwise have (for instance they restrict the way you USE of the software, which expressly permitted by basic copyright law).

      As does the GPL. It takes away the right to resell a binary copy without including the source code.

      Yes, the terms are on the GPL are "arbitrary", but they can be ignored, in which case you don't get to copy the software, which is an exclusive right of the copyright holder.

      Same with any EULA. Until you do something which requires a license, why would the license apply? Just because the license says it applies? That's nonsense, and a judge will see it as such.

      Considering how careful the FSF has been, even in the way they word things in their writings, I find it almost impossible to believe that a judge wouldn't find that someone violating the GPL is in fact violating copyright law.

      Depends on the action. If the action was fair use, or first sale, or some other right which the person already had, then they likely wouldn't be found guilty of copyright infringement. For instance, if I legally acquired RedHat CDs which didn't include source code and resold them, I'd be violating the GPL, but probably wouldn't be found to be violating copyright law.

    57. Re:The GPL doesn't mean as much as people think by HiKarma · · Score: 1

      This is a day old /. thread, so nobody is left reading, but how do you get that by applying a patch you are in violation of copyright? If you were, it would indeed be contributory infringement, but where do you get the former from?

      The GPL does not restrict what you, an end-user, do with a piece of GPL code you have on your machine. You are free to do with it as you wish, create derivative works, etc. as long as you don't distribute them.

    58. Re:The GPL doesn't mean as much as people think by anthony_dipierro · · Score: 1

      This is a day old /. thread, so nobody is left reading, but how do you get that by applying a patch you are in violation of copyright?

      By applying a patch you are creating a derivative work.

      The GPL does not restrict what you, an end-user, do with a piece of GPL code you have on your machine.

      The GPL doesn't, but copyright law does. You are not allowed to create derivative works without permission of the copyright holder, and the GPL only gives that permission when you include the source.

      You are free to do with it as you wish, create derivative works, etc. as long as you don't distribute them.

      The GPL does not say that.

    59. Re:The GPL doesn't mean as much as people think by HiKarma · · Score: 1

      Yes it does. Section 2. Full right to modify the program. Only if you distribute any modified program must you put it under the GPL.

      That's the tricky part -- what it really says is if you distribute any program derived from the program.

      It is an interesting question, is a patch a derivative work? That needs some more research.
      The telling recent case is the cleanflicks case.

      If it is, it would imply that you can't publish a bug fix to a program without the consent of the original author.

    60. Re:The GPL doesn't mean as much as people think by MrResistor · · Score: 1

      The amount lost by the copyright holder is easy to figure out: it's based on what the infringer was charging for it. The copyright holder doesn't have to have had any intention at all to ever sell the thing. This makes perfect sense, since the whole problem is the infringer profiting from something he has no rights to.

      --
      Under capitalism man exploits man. Under communism it's the other way around.
    61. Re:The GPL doesn't mean as much as people think by MrResistor · · Score: 1

      So, explain how exactly staticly linking a library is fundamentally different from just copy/pasting it into your source file.

      The GPL allows you to copy/paste if you want to, but with the requirement that the resulting program is also under the GPL. That's as it should be: it's clearly a derived work. Static linking is effectively the same thing.

      --
      Under capitalism man exploits man. Under communism it's the other way around.
    62. Re:The GPL doesn't mean as much as people think by anthony_dipierro · · Score: 1

      Section 2. Full right to modify the program.

      Not exactly. "You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change."

      Also, "You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License." But if the patch is copyrighted, and the resulting work is not freely distributable, then you can't license the derivative work under the GPL.

      It is an interesting question, is a patch a derivative work?

      I remember reading a Supreme Court case which decided that a derivative work necessarily contains some part of the original work (including theme, storyline, etc. as parts of the original work). I believe this was decided in a court case involving Galoob, but I might have the cases mixed up. I'm too lazy to look it up on google right now.

    63. Re:The GPL doesn't mean as much as people think by cyril3 · · Score: 1
      Not "a" law but law as in case law.

      In Australia at least there are cases supporting existance of a valid contract where the offer was basically "If I hear no more about him I shall consider the horse mine at 30 15s 0d". (Felthouse v Bindley

      And there are the ticket cases.

      From http://law.anu.edu.au/colin/Layout/Off_Ac_h.htm Traditionally the so-called "ticket cases", that is, cases in which there is a written document which is not signed by either party, have been analysed as follows: the person who provides the ticket makes an offer by proffering the ticket. The other person (the passenger in this case) then either accepts the ticket (and therefore the terms contained therein) or decides not to accept. The theory is that the person at least has some time to peruse the terms and then makes a decision whether to accept them. In practice, of course, no-one peruses the terms and no-one rejects the ticket. Instead they just put the ticket in their pocket. We will see later that in some ticket cases there is a possible argument that the person proffering the ticket must give reasonable notice of the terms in the ticket. But this is usually achieved by simply proffering the ticket.

      It's Australian but I presumed most common law jurisdictions wiould come to similar conclusions to allow normal business activities to go ahead.

    64. Re:The GPL doesn't mean as much as people think by cyril3 · · Score: 1
      Copyright is not a contract issue but licences are. By acquiring a CD I accept the note on almost every CD I've seen that says "Unauthorized copying blah blah is strictly prohibited." That is a licence. So yes if i were then caught distributing such a song on Kazaa, I would expect the law to be able to bind me to the terms on it. The GPL licence is a bit longer than the CD one because you can do more with software and it is a more complex issue.

      Truth is you make copies all the time.

      And those copies are all authorized by copyright law specifically to allow computers to operate.

      They give you the site free. Are you bound? Yes. Now don't tell me that hidden away in the really small print in white typeface is a promise to give them my next born child and now I'm bound to do that because I looked at their site.

      As an aside, while writing the first point above about every cd, i happened to pick up my copy (purchased legal and all) of the Sleepy Jackson CD which is proudly stamped with Copy Controlled in various places and notes that the disc incorporates Copy Control technology that prevents the consumer from making digital copies. Nowhere is there a copyright mark or the above mentioned Thou Shalt Not label. The only thing that looks ownerish is the (L.Steele.Control) after each song title which I assume is the Composer.Publisher

      So I made an analog copy.

  3. Good or Bad? by Hayzeus · · Score: 4, Insightful

    How about inevitable?

    1. Re:Good or Bad? by PolR · · Score: 1

      Totally agree. What is the good of having the GPL if it is not used in court in situations like this? Think of it as a test run to check the bugs. How can that be avoided?

  4. Sooner is Better by mhotas · · Score: 5, Insightful

    The sooner we know if the GPL holds water, the better. A lot of people are counting on it to protect their work. How big a disaster would it be if a loophole were found 5 years from now?

    1. Re:Sooner is Better by Anomander · · Score: 4, Interesting

      Why? If GPL fails your code will automatically revert to normal copyright wich AFAIK requires your permission to use it in any circumstance.

      The GPL is means to make your code more avaliable to the community, not for protection.

      The danger of GPL failing would be to keep any project distributed under the GPL together. All the contributors must then agree on a new copyright scheme and that is probably a showstopper...

    2. Re:Sooner is Better by truthgun · · Score: 2, Informative

      I agree. The question is not if this is good or bad, it is necessary. If it holds up that's great but if it doesn't then the GPL has to be redone.

      The problem with holes is not when they're found but how long they are there for ppl to exploit.

      --
      Sattinger's Law: It works better if you plug it in.
    3. Re:Sooner is Better by dafoomie · · Score: 1

      The GPL is means to make your code more avaliable to the community, not for protection.
      Actually, it does both. It encourages you to make your code available to the community by protecting your work, and you from your work. If I write a program and want to give it away, I can place it in the public domain. However, other people could take my work, modify it, sell it, and not "give back" to the community from which it came. I may also be liable for any damage done by the program if it malfunctions. The GPL ensures that you can give it away to the community without worry of those two situations.

    4. Re:Sooner is Better by IM6100 · · Score: 1

      If the GPL is declared null and void, then all those pieces of GPL'd code revert back to regular copyright. However, this means that the 'commons' that people have contributed to ceases to exist. Instead of a big project called the Linux kernal all under a common license, we've got 35,000 different code fragments, all of which have different copyrights and owners, and all of which can and will be interpreted seperately if people are taken to court for how they use said fragments.

      --
      A Good Intro to NetBS
    5. Re:Sooner is Better by shfted! · · Score: 1

      Don't forget -- if the code was once released under the GPL, one clause specifically states that you are allowed to distribute it under it later version. Thus, a simple amendment to the GPL would need to be made, a version (2.1?) released, and all GPL'ed projects could then be rereleased as though nothing happened.

      --
      He who laughs last is stuck in a time dilation bubble.
    6. Re:Sooner is Better by Pofy · · Score: 1

      >Why? If GPL fails your code will automatically
      >revert to normal copyright wich AFAIK requires
      >your permission to use it in any circumstance.

      I always thought of thr GPL as a such a permision. You normally can't distribute works or derivate works of someone without a permision. The GPL gives you (limitied, in that you must include the source) permision to do so. So, how can a permision "fail" and be said to not be valid? It is only when one try to make GPL into some sort of contract or license that it gets bad since there really is no agreement in the sense contract law requires. But if one look at it as a blanket permision given to anyone that wants so, to create derivative work and distribute it with the source, I see no problem and no way to not "uphold" it in a court or whatever.

  5. International Continuation by Anonymous Coward · · Score: 0

    Even if IBM wins in court, I think we will see the GPL and its spirit continue internationally for quite a while. The U.S. justice system will shoot the whole country in the foot if it rules against the main license used in all open-source software.

  6. OJ by ttyp0 · · Score: 2, Redundant
    Any faith I had in the legal system was lost on the O.J. Trial. I'm placing my bets on who's pockets are deeper (IBM). Remember, the law isn't about what's right or wrong.

    Anti SCO T-Shirt. $1 donated to OSI Fund on each shirt.

    1. Re:OJ by SnatMandu · · Score: 0, Troll

      The legal system would have done just fine if the LAPD wasn't rife with racist guys who tried to frame an already guilty man

    2. Re:OJ by Xerithane · · Score: 1

      Any faith I had in the legal system was lost on the O.J. Trial. I'm placing my bets on who's pockets are deeper (IBM). Remember, the law isn't about what's right or wrong.

      Civil or Criminal? OJ was found guilty in the civil hearing, and thus is broke ass.

      --
      Dacels Jewelers can't be trusted.
    3. Re:OJ by Anonymous Coward · · Score: 0
      Any faith I had in the legal system was lost on the O.J. Trial.
      You trusted the police? Don't you read newspapers?
    4. Re:OJ by Anonymous Coward · · Score: 0

      What's OSI doing about SCO? For that matter, what does OSI do about anything?

      Why not donate to RedHat's anti-SCO legal fund?

    5. Re:OJ by Anonymous Coward · · Score: 0

      Ya, he's so broke he has to go out golfing in Florida everyday while the rest of us non-murderers have to fucking work all day...

    6. Re:OJ by dr_dank · · Score: 2, Funny

      Any faith I had in the legal system was lost on the O.J. Trial.

      If things pan out the same, I can't wait for SCO to lead the police on the Bronco chase.

      --
      Where does the school board find them and why do they keep sending them to ME?
    7. Re:OJ by wass · · Score: 2, Insightful
      The main problem of the OJ trial was finding a jury worthy to determine the guilt of a celebrity. It was a positive feedback loop, when the difficulty arose to find an unbiased jury that didn't know about OJ or the crimes, the news agencies reported it, thus severely reducing the lot of potential jurors, etc.

      Ultimately, only handful of people very out of step of current events could be chosen for the jury. IIRC, there was a similar problem for the Ollie North trials, but not nearly as bad. Goes to show that sports celebrities are more widely known than political entities.

      Anyway, I don't know how business suits relate to juries, if they have them or not. But the problems inherent in the OJ case hopefully shouldn't present themselves here. You should be more concerned with the problems from the MSFT antitrust case. Where the company lied in court, was found guilty, and still got off the hook.

      I think Robert Frost summed it up best when he said "A jury consists of twelve persons chosen to decide who has the better lawyer."

      --

      make world, not war

    8. Re:OJ by Coventry · · Score: 5, Interesting

      If it took the well-publicized OJ trial to shake your faith, then you weren't paying much attention. It's been f-ed up for awhile.

      Heres a post-OJ example:
      I used to work for company X, which was owned by company Y. Company X laid me off. The very next day I get contacted by a big honcho (lets call him A) at X (and Y, CTO for both) to do some contracting work on an unfinished project for Y. I agree and get to work. I work, and I work, and I rack up hours, all billable via the agreement I had with A. I fix all the bugs, I deliver the system.
      And then Y doesn't pay. ...and doesn't pay. ...and leaves me in the lurch.
      I find out the software I'd written is about to be taken from its single location and rolled out nationaly by Y, and I get pissed and start bugging the hell out of my contact at Y (person B). Person B tells me that A was never allowed to authorize work for Y, and puts me in contact with a different honcha, person C. Person C claims they are evaluating my software and comparing it against other off-the-shelf systems. I make it very clear to C that this matters not: I agreed to do work for a specific price per hour, and they are using the fruits of my labor. He shrugs it off and says he is not bound by the agreements A made.
      Over the next two months, I get the runaround, and then finally C offers to pay less than 1/4rd of the bill as 'a fair liscensing fee based upon our research'. By this time, I had debt upto my eyeballs, but I still had some sense of reason and pride. I made it clear to C that I, not they, get to set liscensing fees for any product I decide to sell, and also stress that liscense was never an issue: I did contract work for them modifying an existing piece of software and fixing bugs, and I expected to get paid. C said the 1/4th was the best he could do. I said I'd go talk to a lawyer.

      Here's where the legal system steps in, the above was backstory.
      I go talk to a lawyer. With my documentation in hand, he said I have a very strong case - should it ever go to court. But he sugests we do some research and try other tactics (letter from his law firm, etc) first, because of a (to me) glaring problem with how these sort of civil cases go: No matter how big the organization in the wrong is, or how obviously in the wrong they are, it is soley upto the judges discretion as to wether the party in the wrong has to pay legal fees for the complaining party (should the complaining party win). Added to this fact, was that in the conservative city I live in, judges rarely make defendants pay for the complaining party's fees.
      This upset me quite a bit.
      Then the research into the company came down - just googling stuff I and the lawyer did. Y was run by lawyers and ex lawyers, and no suit brought against them ever made it out of court - they dragged their feet for years on anything they could, and used heavy-handed tactics and threats of countersuits whenever possible to stop suits dead in their tracks by scaring off the person or company making the complaint.

      So, here I am, almost a year later, still out TONS of $$ (>20k), and I can't afford to pursue the matter. For every letter they write in response to something my lawyer would send, I'd be out 100-250$ (assuimng it was a short letter my lawyer coudl respond to quickly). If I were to take the case to court, depositions alone could bankrupt me. I entered into a binding agreement with an officer of company Y, and I can't collect squat from it.
      Meanwhile, company Y is doing well. They have over 100000 users nationwide using the software I fixed and improved for them.

      What it comes down to is this (as the prosecution found out the hard way in the OJ trial): the legal system protects those who have money. If you have tons of money (for lawyers), you can get away with almost anything, or at least make it so painful, expensive and drawn-out for anyone to come after you that it isn't worth it.

      Back to the story at hand though: IBM has very deep pockets. But SCO is going to spend eery penny it has on lawyers, and can draw this out for quite awhile. Realisticaly, we wont have an answer to the is-the-gpl-enforcable question for Years.

      --
      man is machine
    9. Re:OJ by Xerithane · · Score: 1

      Ya, he's so broke he has to go out golfing in Florida everyday while the rest of us non-murderers have to fucking work all day...

      Nonsense. Plenty of murderers still have to work.

      --
      Dacels Jewelers can't be trusted.
  7. A good side, a bad one by leandrod · · Score: 5, Insightful

    Good:
    Once for all this "not yet tested in court" FUD will go away, and future violators might be deterred.

    Bad:
    Media circus. 'nough said.

    Worst:
    A bad result might make thousands of talented people loose faith in justice. This is actually good, as would be any acts of civil disobedience in consequence. The actual evil has been done in the last several decades in the slow, generalised erosion of morals... final defeat would be ugly, even the civil disobedience struggle itself would be honourable but containing scenes of unthinkable ugliness, stupidity and cruelty.

    --
    Leandro Guimarães Faria Corcete DUTRA
    DA, DBA, SysAdmin, Data Modeller
    GNU Project, Debian GNU/Lin
    1. Re:A good side, a bad one by Anonymous Coward · · Score: 0

      don't worry, once they learn that a little girl is about to loose faith in democracy, the system will correct itself.

    2. Re:A good side, a bad one by leandrod · · Score: 1
      > once they learn that a little girl is about to loose faith in democracy, the system will correct itself

      Moderators, please, +1 Funny.

      Now seriously, I mentioned justice, not democracy. They don't necessarily come together, nor is one necessarily caused by the other.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    3. Re:A good side, a bad one by leandrod · · Score: 1

      How on Earth can this be rated +1 Funny?!?

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    4. Re:A good side, a bad one by poot_rootbeer · · Score: 1

      Bad:
      Media circus. 'nough said.


      Don't worry, the media doesn't care (outside of Wired and TechTV, at least).

      Worst:
      A bad result might make thousands of talented people loose faith in justice.


      And spelling!

      The actual evil has been done in the last several decades in the slow, generalised erosion of morals... final defeat would be ugly, even the civil disobedience struggle itself would be honourable but containing scenes of unthinkable ugliness, stupidity and cruelty.

      I don't know what you're talking about. People and governments have always been as mean and evil as they are today. We're not heading towards End Times, and even if we were the final omen would not be the courts striking down the GPL.

      Are you by any chance wearing a Che Guevara T-shirt right now?

    5. Re:A good side, a bad one by leandrod · · Score: 1
      > media doesn't care

      We have our own media circus: ZDNet, CNet and friends... not to mention a hoard of news sites.

      > I don't know what you're talking about

      The Bible calls that "a conscience seared with hot iron".

      > People and governments have always been as mean and evil as they are today

      About people, agreed, at least at the depth of our hearts. But there have always been a kind of salutary hypocrisy: La Rochefoucauld's "hypocrisy is the tribute that vice pays to virtue" comes to mind. This acknowledgement of virtue is sorely missing, and confounds even supposedly conservative judges to judge based solely on economical basis and to give free rein to power. These are not the times were antitrust or public domain are given any serious consideration, and we are poorer for that.

      > the final omen would not be the courts striking down the GPL

      Rome wasn't built in a day. Nor destroyed.

      > wearing a Che Guevara T-shirt right now?

      I'm a culturally conservative, doctrinally orthodox, economically liberal (in the European sense) Baptist.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
  8. SCO's case is too weak by jbolden · · Score: 5, Interesting

    The problem with this case is that SCO's case is too weak for it to work as a test of the GPL. SCO is not going to be able to prove an original violation. Without a provable claim the case will stop. Its like a wrongful death suit where the prosecution doesn't have any evidence that the supposed victem is in fact dead.

    1. Re:SCO's case is too weak by EpsCylonB · · Score: 2, Insightful

      I think it is too easy to underestimate SCO at this point. They must at least think they have something otherwise they wouldn't have come this far. Certianly the biggest mistake the open source communtiy could make is to not take them seriously.

    2. Re:SCO's case is too weak by jbolden · · Score: 2, Insightful

      I read their original case and several filings after this. There is no evidence that they are on to something. I think there original bet was that IBM would rather buy them then allow for this confusion, publicity... IBM decided that SCO was a great place to make a stand. So no I don't think they have a case and yes I think the open source community shouldn't take them seriously.

      Serious companies complaining about a copyright or patent violation would be very anxious to see this violation corrected.

    3. Re:SCO's case is too weak by PetWolverine · · Score: 1

      Certianly the biggest mistake the open source communtiy could make is to not take them seriously.

      I disagree. I think it is certainly the biggest mistake the open source community could make to take SCO seriously. The primary motivation for SCO's lawsuit is to drive up the stock price. Every post that takes that suit seriously in any way does exactly that. That will reward the executives, and piss the rest of us off further.

      --
      I found the meaning of life the other day, but I had write-only access.
    4. Re:SCO's case is too weak by Xabraxas · · Score: 1
      Serious companies complaining about a copyright or patent violation would be very anxious to see this violation corrected.

      Very true. By their account SCO is losing money every time a copy of Linux is used. With the growing popularity of Linux one would think they would like to end this as quickly as possible. Perhaps they are hoping to drag it in hopes that as time goes on and more people adopt Linux, they will have more people to sue or demand licensing from if they win. Either way it looks shady.

      --
      Time makes more converts than reason
  9. good / bad? by Anonymous Coward · · Score: 0

    more like inevitable .. good or bad depends on
    how it goes, but it had to happen .. hopefully
    clear heads will prevail and a good precedent
    will be set ..

  10. A good thing by Salo2112 · · Score: 1, Redundant

    This may be the vetting linux needs to have complete acceptence.

    1. Re:A good thing by Anonymous Coward · · Score: 0

      Did you mean:

      This may be the vetting which the linux kernel needs in order to be accepted universally.

    2. Re:A good thing by Salo2112 · · Score: 1

      That will work, too. :-)

  11. I would trust IBM... by cliffy2000 · · Score: 1

    After all, they're bigger than U.S. Steel!

    (The Godfather Part II reference... and it actually makes sense, if you've seen the movie.)

    1. Re:I would trust IBM... by Anonymous Coward · · Score: 0

      I'm affraid you are praying to the wrong God.
      Wal-Mart! It's bigger then Microsoft and it sells Linux boxes!
      After all this world is run by large corporations, isn't it?

  12. Its Good that IBM is helping by linuxislandsucks · · Score: 1

    Its good that IBM is helping put their won legal views of the GPL in a court setting as they would not have signed up orginally to do any opnesource code without a thorough review of GPL by their onw legal staff..

    and as you may know IBM's legal staff is the best in the business even beter than SUN and MS's own legal dream teams

    --
    Don't Tread on OpenSource
    1. Re:Its Good that IBM is helping by IM6100 · · Score: 1

      However, 'big' isn't always 'better' in a court case. The American public has been conditioned for years to belive that the 'big company' is wrong, and the smaller company deserves their sympathy. That point has been driven into our heads for years and years of popular culture.

      In an IBM=Goliath, SCO=David framing of the issue, the GPL guys don't come out ahead if their champion is IBM.

      It's really awful, in some ways, seeing so many people cheer on IBM and praise them for their bigness. It's almost like big-company-coercion is okay, and the 800 pound gorilla is alright as long as it's our 800 pound gorilla. That's wrong. It goes against the grain, and it'll bite people who back it in the end.

      --
      A Good Intro to NetBS
  13. justice system by h4x0r-3l337 · · Score: 5, Interesting
    Do you have faith in the justice system (or IBM's Lawyers) to draw the right conclusions?

    IBM's lawyers are not out to defend the GPL, they are out to defend IBM. The two are not necessarily compatible. And in the end, whether or not IBM's lawyers "draw the right conclusions" (taken to mean they interpret and defend the GPL the way your average slashdot reader would like them to) is rather irrelevant. What matters is the judge's ruling. That brings us to the justice system... Given the choices that have been made in recent years, one could argue that there currently is no justice system. This started with the election of the president by the supreme court, and continued with the systematic suspension of basic rights guaranteed under the constitution.

    1. Re:justice system by BiggerIsBetter · · Score: 1

      Keep in mind that any rulings on the GPL have potential to affect ANY software licence. The software side of IBM has a huge amount riding on that. Granted, there may be concessions and arguments that suit IBM more than the OSS community, but still, if their case rests on the GPL being valid you can be damn sure they'll defend it to the best of their ability.

      --
      Forget thrust, drag, lift and weight. Airplanes fly because of money.
    2. Re:justice system by heinousjay · · Score: 1

      ...one could argue that there currently is no justice system. This started with the election of the president by the supreme court...

      Jeezuz Fuggin Christ. I wouldn't vote for George Bush if he promised me his daughters would spend the rest of their attractive lives manipulating my private areas in extremely pleasurable ways, but you have to give this shit a rest sometime. Three long years have passed. Focus on the future, and maybe you'll be able to do something that makes you happier. Keep rehashing the past, and you'll just be bitter and shitheaded.

      --
      Slashdot - where whining about luck is the new way to make the world you want.
    3. Re:justice system by the_greywolf · · Score: 1

      did you forget about the rubber bullets?

      that was before the supreme court had to clean up the mess in florida.

      --
      grey wolf
      LET FORTRAN DIE!
    4. Re:justice system by dmaxwell · · Score: 1

      IBM's lawyers are not out to defend the GPL, they are out to defend IBM.

      True but IBM truely are composed of litigious bastards. IBM had litigation down to a science before Daryl was even in diapers. Now these profession lawyering bastards seem to feel that GPL would make a fine clue-by-four to administer an old fashioned country ass-whipping to McBride and Sontag. I find that at least a little heartening.

    5. Re:justice system by Anonymous Coward · · Score: 0

      I am sorry, but the stuff about the president being elected by the supreme court IS COMPLETE BULLSHIT.

      They recounted the fucking ballets 2 or 3 times and each time it came out in Bush's favor. Every fucking time. EVERY FUCKING TIME.

      The US supreme court just said that it's up to Florida to solve it's own fucking problems, not the US fedral government. It's up to florida's legislator to elect the president not the fucking popular vote, however that's is what they use to decide 98% of the time.

      I can't beleive that some people who beleive they are so smart can't understand that they've been tricked. There are plenty of presidents who were elected with less then 50% of the vote.. Abraham Lincoln for example, or Bill Clinton himself.

      IF YOU DON'T UNDERSTAND THAT IT'S THE STATE'S LEGISLATION JOB'S TO ELECT THE PRESIDENT NOT THE POPULAR VOTE (all though it is usually decided that way). THEN YOU ARE A FUCKING IDIOT AND HAVE NO CLUE HOW OR WHY THE FOUNDING FATHERS DECIDED TO DO IT THIS WAY.

      You elect the legislative branch thru popular vote(house of representatives numbered by population, senate is numbered by state), the states elect the president, the judical branch is appointed. See, this is suppose to provide a balance. A set of rules set up for checks and balances so that one group can't terrorise the other.

      It was the legistature of Florida who cast the deciding vote. The US supreme court just voted to stay out of it. Nimrod.

    6. Re:justice system by Anonymous Coward · · Score: 0

      You're not very bright, are you?

    7. Re:justice system by poot_rootbeer · · Score: 1

      Given the choices that have been made in recent years, one could argue that there currently is no justice system.

      Only if one's only sources for news about what's happening in the judicial system are Slashdot and cable news stations.

      Justice IS actually served, a thousand times over every day, in courtrooms everywhere. You don't hear about those cases though because it's only news when justice IS NOT served.

      The system mostly works, and error conditions are normally trapped when they do occur.

    8. Re:justice system by Anonymous Coward · · Score: 0

      Oh, PLEASE! The Supreme Court HAD to step in when the Florida Supreme Court (for political reasons) started rewriting the Florida Constitution on the fly, and disregarding state LAWS which said elections had to be completed by a certain date, including all challenges and recounts. At that point, it was legal and appropriate for SCOTUS to step in and slap down a rogue state Sup. Ct. which was unconstitutionally arrogating to itself legislative powers, violating constitutional checks and balances... Your complaint is such a bogus liberal red herring that has acquired seeming legitimacy through sheer repetition, but won't stand up to logical, reasonable reflection.

    9. Re:justice system by leandrod · · Score: 1
      > The system mostly works

      Yes, but depending on your beliefs some decisions can be quite troubling in that they set a trend. My worries are much older, even if I'm not a citizen of the US: they come from Roe vs Wade and, later, the method patents.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
  14. GPL is stronger than other software "licenses" by echo · · Score: 5, Informative

    Read this article to understand why.

    http://moglen.law.columbia.edu/publications/lu-12. html

    1. Re:GPL is stronger than other software "licenses" by Troll_Kamikaze · · Score: 1

      Analysis brought to you by the eminently unbiased Eben Moglen.

  15. It's not a test of the GPL by turg · · Score: 4, Insightful

    It's not really a test of the GPL. It's a test of the validity of SCO's claims -- does SCO own what they say they do, and did IBM do what SCO says IBM did?

    The fact that SCO themselves distributed Linux under the GPL is one piece of evidence against SCO, there's nothing about the case that would cause the validity of the GPL to be a major issue. Or am I missing something?

    Are the claims of either side based on the (non-)validity of the GPL in any way?

    --
    <sig>Guvf vf abg n frperg zrffntr
    1. Re:It's not a test of the GPL by stubear · · Score: 1

      "The fact that SCO themselves distributed Linux under the GPL is one piece of evidence against SCO,..."

      This is only true if SCO released a version of Linux with the offending source code included. If their version of Linux does not contain the same source code that they claim was illegally included by IBM then the source code is still protected by whatever agreement IBM and SCO originally had. THE GPL cannot force SCO to open anything other than what they released under this license.

    2. Re:It's not a test of the GPL by sflory · · Score: 2, Interesting

      For the most part no. Now that IBM is claiming that SCO is in violation of the GPL. The validity of the GPL is very much in question. It is not a central issue currently, but things could change depending on how much IBM's counter suit depends on the gpl.

      For example if IBM can find proof that SCO knew that IBM had put parts of their AIX code in linux. While SCO was at the same time shipping that same code under linux. Then the validity of the GPL become very important.

      --
      IANALBIPOOGL (I am not a Lawyer, but I play one on GrokLaw.)
    3. Re:It's not a test of the GPL by roystgnr · · Score: 1

      The fact that SCO themselves distributed Linux under the GPL is one piece of evidence against SCO, there's nothing about the case that would cause the validity of the GPL to be a major issue. Or am I missing something?

      You're missing the countersuits. IIRC copyright infringement was one of IBM's claims against SCO.

    4. Re:It's not a test of the GPL by leandrod · · Score: 2, Insightful
      > It's not really a test of the GPL.

      Not yet, but unless IBM abandons at least its claim about SCO infringing the GNU GPL, or SCO bucks, stop redistributing and negotiate a license with all interested owner of distributed code, then it might come to a test case. Which obviously isn't necessary, as per Moglen's famous paper on the GNU GPL enforceability...

      > Are the claims of either side based on the (non-)validity of the GPL

      Yes. When IBM pointed finger at SCO infringing distribution of Linux, SCO tried to defend its illegal, immoral act by saying the GNU GPL is a vague license. Well, if so SCO shouldn't being redistributing any GNU GPL'd code, as it wouldn't be clear they have the rights to do so.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    5. Re:It's not a test of the GPL by red+floyd · · Score: 1

      Didn't they claim that the entire 2.4 kernel was in violation?

      The source to the 2.4.13 kernel is here.

      --
      The only reason we have the rights we have is that people just like us died to gain those rights. -- Cheerio Boy
  16. I license that cannot be enforced... by Anonymous Coward · · Score: 2, Insightful

    ...is a license to steal. The GPL needs legal validation, and I'm all for it happening in this case.

    If the judge determines that the license is not legally binding because of X, we just modify X in the GPL 3.0. If the judge determines that SCO does have IP rights over Y in the Linux kernel, then Y is removed in Linux 2.6. Even the worst result I can imagine is just a temporary setback for Linux.

    But to be perfectly frank, there's no chance in hell SCO will be able to prove their IP claims. A judge could invalidate the GPL on some technicality I don't know about, tho.

  17. Once more, with feeling this time... by Empiric · · Score: 4, Insightful

    It's important to understand where the "force of law" exists, fundamentally, in relation to the GPL. The force of law which the GPL utilizes, at base, is the force of copyright.

    In respect to SCO, given that they are redistributing the IP of others (i.e. the many, many coders who contributed to Linux), their only viable statements at this point are "We are, in fact, complying with the GPL" or "We are guilty of criminal copyright infringement"--not "The GPL sucks/is-legally-invalid/is-bad-for-business." Either they are complying with the GPL's conditions for duplicating copyrighted material, or they are guilty of criminal copyright infringement right now. Yes, right now.

    Given this, the focus should arguably be on how the GPL can be enhanced to continue to provide a framework of conditions for the redistribution of Open Source which benefits everyone, rather than how the court might "test" its contents, or whether the GPL text passes some subjective opinion as to whether it's legally "neat-and-tidy".

    --
    ~ Whence do you come, slayer of men, or where are you going, conqueror of space?
    1. Re:Once more, with feeling this time... by Anonymous Coward · · Score: 0

      Either they are complying with the GPL's conditions for duplicating copyrighted material, or they are guilty of criminal copyright infringement right now,

      Since they are still providing source from their FTP site, they are not yet in violation. Maybe. What do I know?

    2. Re:Once more, with feeling this time... by Empiric · · Score: 2, Insightful

      Yes, this is an interesting fact to note. I wouldn't be surprised if SCO's own lawyers have realized the consequences of redistributing without complying with the GPL, and that's the underlying reason they're still making it available via FTP.

      So, I wouldn't be surprised to see SCO continuing to talk out of both sides of their mouth, one half attacking the GPL and the other stating their compliance with it.

      --
      ~ Whence do you come, slayer of men, or where are you going, conqueror of space?
  18. GPL will have very little to do with the case by MyNameIsFred · · Score: 4, Insightful
    From the articles that I have seen, I don't believe GPL will play any significant role in the case. The issues are whether IBM broke its contract with SCO by creating a "derivative work" and whether SCO source code was improperly copied into source code that IBM released. The fact that the source code is under GPL is only marginally important. The same issues would be raised if the source IBM released was under BSD, MIT or any other license. I seriously doubt whether the validity of the GPL license will even be raised.

    I know some will say that the fact that SCO continues to provide Linux source code means that GPL is involved. But once again, that issue would be valid if the released source code were BSD, MIT, ... license.

    1. Re:GPL will have very little to do with the case by Erik_the_Awful · · Score: 0

      You are probably right for the reasons you mention as well as the likely hood that IBM and SCO will settle out of court. There is just a small chance that IBM will press their counter-suit. In that case, we may yet hear a judgement on the legal enforcability of the GPL. I'm keeping my fingers crossed.

    2. Re:GPL will have very little to do with the case by MrGrendel · · Score: 2, Informative

      The GPL forms the basis for many of IBM's counterclaims. That fact alone will cause SCO to raise questions about the validity of the GPL in court if the case ever makes it that far. There are a number of terms in the GPL that are not present in BSD style licenses, such as the restriction on sublicensing. SCO's many violations of the GPL opened the door for several of IBM's claims. The GPL will also play a huge role in the Redhat case

    3. Re:GPL will have very little to do with the case by leandrod · · Score: 2, Informative
      > some will say that the fact that SCO continues to provide Linux source code means that GPL is involved. But once again, that issue would be valid if the released source code were BSD

      Actually not. The (reformed) BSD license and friends do allow anyone to do anything but stripe out the copyrights notice. So if Linux was BSD-licensed, SCO could have gotten away with its reasoning, and IBM wouldn't have been able to point SCO's distribution of Linux as hypocritical and infringing.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    4. Re:GPL will have very little to do with the case by drinkypoo · · Score: 1

      On the other hand it would still result in SCO releasing the code to the general public, so I fail to see how this does not result in invalidating their claims. Maybe I'm missing something but the reason it's so good that SCO is distributing linux is that they're distributing the code in question (assuming it exists) and therefore they themselves have put it under the GPL. If they put it under the BSD license, the result would be exactly the same. Hypocritical would be if they took code out of GPL'd Linux and put it into SCO Unix, which has not been shown or even suggested, at least as far as I've noticed. I have seen allegations that SCO put Unix code into Linux, which is where the hypocrisy really mounts if it's true. Regardless, whether the source is in a BSD-licensed kernel, or a GPL-licensed kernel, the result of distributing it is the same: The copyright holder gives up all rights to that branch of the code except that it is now attached to a certain license, and therefore its inclusion in the kernel would be blessed.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    5. Re:GPL will have very little to do with the case by leandrod · · Score: 1
      > whether the source is in a BSD-licensed kernel, or a GPL-licensed kernel, the result of distributing it is the same

      Not quite... only the GNU GPL asserts the code must be unencumbered.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    6. Re:GPL will have very little to do with the case by drinkypoo · · Score: 1

      That would seem to only make a difference if SCO had patents which apply to the code, which they do not; They are held by others. SCO has only licensed the code, not the patents. Any patents belong to Novell or IBM.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  19. Something more important than testing the GPL by fr0z · · Score: 2, Interesting

    This lawsuit reeks of the USL vs BSDI lawsuit years ago. What's more important than testing the GPL (as someone has said, if it doesn't work then we can always re-write it), is that we keep raising the profile of Linux and OSS in general to non-geek friends and co-workers. That way we can help Linux avoid BSDs fate after their lawsuit was settled. But please do it in an even, unbiased manner, if not you'll freak people out...

    --
    Never underestimate the predictability of human stupidity...
  20. ...which will lead to... by Anonymous Coward · · Score: 0

    See you all in the OS/2 forums!

    j/k

  21. Is it just me... by mikeophile · · Score: 2, Funny

    Or did anyone else think that the ad for the O'Reilly book User Obliteration was part of the article on the Register?

    1. Re:Is it just me... by Anonymous Coward · · Score: 1, Informative

      O'Really.

    2. Re:Is it just me... by Theranthrope · · Score: 0
      That's O'Really.

      The thing is, I wish the real O'Reilly would print Pratical UNIX Terrorism. I would pay good money for that book, just for the bragging rights of simply owning it.

  22. Isn't a Copyright a Contract? by btakita · · Score: 1

    I thought a Copyright binds the parties to the use the IP.

    If someone agrees to use GPL code, aren't they agreeing to abide by it, or do they have to sign a document?

    1. Re:Isn't a Copyright a Contract? by HiKarma · · Score: 5, Informative

      Copyright law does essentially one thing. It gives the copyright holder exclusive right to make copies, and thus to get a court to punish and stop those who make copies of something without permission.

      The punishments are specific. Injunctions (stop copying!) Actual damages (pay me for what I lost because you copied it.) Statutory damages.

      In extreme cases (wilful infringement that really pissed off the court) statutory damages can be up to $150,000 per copy. That's a lot of leverage which can get you to make people obey the GPL.

      But copyright itself does not list among remedies, "Make them release their code under the GPL."

    2. Re:Isn't a Copyright a Contract? by Webmonger · · Score: 4, Informative

      The Holy GPL sayeth:
      "You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works."

      If you distribute GPLed code you either
      a) have accepted the GPL implicitly
      b) are violating the copyright on the GPLed work

    3. Re:Isn't a Copyright a Contract? by kien · · Score: 3, Interesting
      But copyright itself does not list among remedies, "Make them release their code under the GPL."
      Of course it doesn't because licensing violations are covered by contract (tort?) law, right?

      I think people tend to forget that the basic premise of the GPL is to point out how ridiculous and counter-productive it is to attempt to secrete source code for profit. The GPL might be called "copyleft", but its enforcement has little to do copyright law. The genius of the GPL is that it uses contract law to hack copyright law.

      But.....of course.....IANAL. :)

      --K.
      --
      Sig: Bad people happen. Try to avoid being one of them.
    4. Re:Isn't a Copyright a Contract? by HiKarma · · Score: 5, Interesting

      The GPL attempts to do this. It is a court test that would find out if it has done this.

      Many would dispute GPL's clause that since you can only copy the program under GPL terms, anybody who copies the program is agreeing to GPL terms. That is not correct. If you copy a GPL program in a way not permitted in the GPL, you are violating the copyright. That's it. That's all. You are not agreeing to a contract. The GPL wants you to think that you are, and the statutory penalties for violating copyrights are high enough that you might later wish to agree to the contract to settle, but you can't be made to agree to a contract because you copied something.

      At least I certainly hope so. Courts might rule either way, but I think we would not want them to rule in favor of the GPL, because of all the other ways such implicit contracts are used (no reverse engineering, must donate firstborn son, etc.)

    5. Re:Isn't a Copyright a Contract? by silas_moeckel · · Score: 3, Interesting

      I think it would be clearer to think of it like this.

      GPL gives you the right to sell, provide for download and otherwise make copies abilible of a work.

      As long as you dont distribute GPL has NOTHING to do with you at all as your not vialating copyright and you got your copy legaly.

      GPL is a contract that you accept when you distribute not when you receive a copy.

      --
      No sir I dont like it.
    6. Re:Isn't a Copyright a Contract? by HiKarma · · Score: 1

      Correct, except add to that
      c) Are exercising fair use rights
      d) Have some other licence to the part of the code you used, or it is in the public domain.

      But the main point is I don't think there is much conflict between (a) and (b). B wins. You are violating the copyright.

      To suggest you have "accepted the GPL implicitly" would imply that, for example, somebody else could take your code and distribute it as though it were under GPL. Or somebody could sue you not to demand remedy for infringement, but for breach of licence contract. I doubt the latter.

    7. Re:Isn't a Copyright a Contract? by kien · · Score: 1
      If you copy a GPL program in a way not permitted in the GPL, you are violating the copyright. That's it. That's all. You are not agreeing to a contract.

      I don't understand how a programmer, having viewed the source code of a program and thus implicitly read the GPL said program was released under, could fail to understand that they are agreeing to the contract. Perhaps that's one test for the courts. I hope someone brings up the EULAs used by Microsoft and various ISPs while arguing this point.

      The GPL wants you to think that you are, and the statutory penalties for violating copyrights are high enough that you might later wish to agree to the contract to settle, but you can't be made to agree to a contract because you copied something.

      Methinks a double-standard that favors those who can afford litigation is implied. I'd love to run your assertion by lawyers from the entertainment industry.

      At least I certainly hope so. Courts might rule either way, but I think we would not want them to rule in favor of the GPL, because of all the other ways such implicit contracts are used (no reverse engineering, must donate firstborn son, etc.)

      I'm with you...I hope they rule against software licenses, EULAs, the DMCA, eternal copyright, etc. etc. And if the GPL proves to be the vehicle to topple the myth of "intellectual property", I for one would say that it served its purpose.

      --K.
      --
      Sig: Bad people happen. Try to avoid being one of them.
    8. Re:Isn't a Copyright a Contract? by Webmonger · · Score: 1

      No, you aren't necessarily violating copyright. As long as you follow the GPL, you're not violating copyright.

      C and D are true, though distributing the whole work will never be "fair use".

      Remember that even people who distribute binaries based on unmodified source are required to provide access to the source they used. I stand by A and B.

      If someone acquires your derived-from-GPL source and distributes it, you can sue them, but the original author will sue you for copyright infringement.

    9. Re:Isn't a Copyright a Contract? by firewood · · Score: 1
      Many would dispute GPL's clause that since you can only copy the program under GPL terms, anybody who copies the program is agreeing to GPL terms. That is not correct. If you copy a GPL program in a way not permitted in the GPL, you are violating the copyright. That's it. That's all. You are not agreeing to a contract. The GPL wants you to think that you are, and the statutory penalties for violating copyrights are high enough

      One dangerous possibility is for a court to find that indeed someone did violate the GPL by distributing modified executables; but that the remedy for this violation of the copyright law does not include forcing them to comply with the GPL; and that the monatary damages for not complying in the case of GPL'd code is zero, because the copyright holders are freely distributing the source code to anonymous parties without requiring any monatary consideration, and because the copyright holders themselves did not file with the copyright office.

    10. Re:Isn't a Copyright a Contract? by HiKarma · · Score: 1

      That is indeed what could happen to a work where the copyright was not properly registered. However, on top of that would be the injunction to stop using it, which would be a serious penalty if the subject program depends highly on the code.

      If however it's a pluggable module -- I take out the GPL library and plug in a commercial one -- then indeed the violator may not feel much pain, though any lawsuit is a lot of pain, really.

    11. Re:Isn't a Copyright a Contract? by dipipanone · · Score: 1

      If you copy a GPL program in a way not permitted in the GPL, you are violating the copyright. That's it. That's all. You are not agreeing to a contract.

      Are you sure? From reading the GPL, it looks to me that there's a very clear contract involved. The license grants the user the right to modify and distribute the code, in return for certain obligations on their part, ie, their agreement to distribute the source of any amendments.

      Now IANAL, but that very definitely looks like a contract to me. You're granted the right to use that license under certain conditions. Breach those conditions and you've violated the terms of your license. How is that *not* a contract dispute?

    12. Re:Isn't a Copyright a Contract? by leandrod · · Score: 1
      > GPL is a contract

      It is not a contract, but a license. It asks nothing of you, it just states the rights you have. Violate the conditions, and the situation returns to the default, which under copy right law is no rights to copy...

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    13. Re:Isn't a Copyright a Contract? by leandrod · · Score: 1
      > the remedy for this violation of the copyright law does not include forcing them to comply with the GPL

      In this case, there would be no right to distribute. In SCO's case, they would be enforced from distributing Linux. They would have to ask nicely for the persecuting copyright holders to allow them doing so.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    14. Re:Isn't a Copyright a Contract? by leandrod · · Score: 1
      > How is that *not* a contract dispute?

      In a contract both parties agree on something. Make a sign in the bus stop; the bus driver agrees on stopping, you agree on taking the bus or at least saying 'sorry, wrong line'.

      The GNU GPL is just a grant of rights. Under copy right law you have no rights to copy, so the copy right holder grants you these rights if you abide by these conditions. Violate them, you loose the rights. It's that simple.

      It's kinda like with murder. You had no contract with humankind or the government granting you the right to live. But kill someone, and your right is revoked. There is still a lengthy process to determine if it was murder, and there might be atenuant circumstances, but murderers in principle forfeit their right to live.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    15. Re:Isn't a Copyright a Contract? by leandrod · · Score: 1
      > You are not agreeing to a contract. The GPL wants you to think that you are

      The GNU GPL wants nothing, because it's not a person.

      Now, there is nothing I can see in the GNU GPL to the effect that its drafters wanted to make it stick as a contract. It is a grant of rights, AKA as a license, nothing more. It is the EULAs of life that want to be contracts; that's why it is not EUL(icense), but EULA(greement).

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    16. Re:Isn't a Copyright a Contract? by firewood · · Score: 1
      > the remedy for this violation of the copyright law does not include forcing them to comply with the GPL


      In this case, there would be no right to distribute.

      Unless publicly and freely distributing code to anonymous parties without a written contract or a requirement for monetary consideration was consider by the court as legally equivalent to putting the source code in the public domain. I don't know if there is legal precedent about doing something that looks and feels like placing material in the public domain, and then trying to selectively enforce the loss of distribution rights using copyright law. (But IANAL).

    17. Re:Isn't a Copyright a Contract? by leandrod · · Score: 1
      > Unless publicly and freely distributing code to anonymous parties without a written contract or a requirement for monetary consideration was consider by the court as legally equivalent to putting the source code in the public domain.

      What would be the precedent? Books are in the library for anyone to take, but no one can make a copy.

      Anyway the code is there to take, but the GNU GPL accompanies each package stating the conditions to redistribute.

      Your imagination is running too fast...

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    18. Re:Isn't a Copyright a Contract? by Anonymous Coward · · Score: 0

      If you copy a GPL program in a way not permitted in the GPL, you are violating the copyright. That's it. That's all. You are not agreeing to a contract.

      Your Honor, when I was distributing this program I wasn't agreeing to the terms of the GPL. I was just willfully infringing on the author's copyright. So instead of being forced to open my source code and continue my business I want to be sentenced to stop doing business instantly and pay damages for willful copyright infringement.

    19. Re:Isn't a Copyright a Contract? by MrResistor · · Score: 1

      That isn't a flaw in the GPL, it's a flaw in copyright law in general.

      However, there is plenty of precedent in regards to this sort of situation already. Click through and shrink wrap EULAs have been upheld in court, and they actually take away rights you would otherwise have. The GPL uses the exact same mechanism (implied agreement) but is much stronger, legally, because it gives rights rather than taking them away.

      You can argue it all you want, but you'll just end up stuck in an endless loop. It comes down to this: you have to agree to the GPL when copying GPLed software because nothing else gives you the right to do so. Your arguement that they can just choose to break the law instead is a straw man. Every license ever conceived, for copyright or otherwise, is "vulnerable" to people deciding to break the law instead.

      --
      Under capitalism man exploits man. Under communism it's the other way around.
  23. SCO implications by Anonymous Coward · · Score: 0

    I am not a lawyer, but -- now that someone *has* indeed paid their extortion money, SCO is now officially guilty of fraud, no?

    I mean, can't every single developer of Linux who has contributed code now sue SCO for a portion of that "extortion money" / and/or sue them for illegally charging for something that is supposed to be free?

    In other words, now that there has been an exchange of money, isn't the "john" as guilty now as the "prostitute"?

    Sale of stolen goods and all that nonsense? I mean, lets say for a minute that it is Microsoft that just paid to license linux.

    By the legal system as I understand it, the recipient of the stolen goods is also liable. If you buy an illegal DVD on the street in Chinatown, can't you also be busted by the cops just as much as the seller?

    So, this could be a double edged sword, even for those that want to appease their PHB's by forking over the money for the license, no?

    1. Re:SCO implications by Erik_the_Awful · · Score: 1, Interesting

      I don't think "extortion money" is the term the lawyers would use, but your point about EVERY Linux contributor now sueing SCO for the violation of the GPL and the theft of IP is facinating. Indeed, SCO has effectivly co-opted Intellectual Property that belongs to a large community. The Free Software Foundation and other such orginazations would be the most likly entities to represent the Linux community at large in such an endevor. Still, I think such an action may be wasted effort. I read IBM's counter suit in part today. My bet is IBM is going to pound SCO into the ground every time this issue comes before a judge. Don't get in a pissing fight with a skunk. At least this time the skunk is on our side :> -EtA

    2. Re:SCO implications by Xabraxas · · Score: 1
      If you buy an illegal DVD on the street in Chinatown, can't you also be busted by the cops just as much as the seller?

      Nope. You can't generally get in trouble even if you are a pawn shop selling stolen merchandise. Pawn shops have to fill out reports about what they have bought and send them to area police departments. They use these records to cross reference with reports of theft. If they get a match they can go and confiscate any merchandise left but that's it. They would have to prove that the pawn shop was actively employing theives or knowingly accepting stolen merchandise which is a very hard charge to prove. I'm dealing with a case like this right now so I've learned a lot about how this sort of thing works.

      --
      Time makes more converts than reason
  24. Parks by Usquebaugh · · Score: 3, Interesting

    I really liked the difference in parks US vis UK. Being a Brit in the US I totally agree.

    The US is only now entering the phase were people understand the law is just a tool used by the monied people to keep their money. I would do the same if I had money.

    Breaking the law is not a big deal, breaking certain laws can be a very big deal, but in general do as you would like others to do to you. Or do good things for the good of all.

    1. Re:Parks by snStarter · · Score: 1

      And just what part of the United States have you been "enjoying" these parks? Or are you parked in front of a computer screen all day in, say, San Francisco?

      Have you toured? Lived in different parts of the country? Or are you stuck in a metro area and think you have seen the entire country?

  25. i'll consider stopping ripping off other people :p by Anonymous Coward · · Score: 0

    well, if the gpl wins i may just consider stopping distributing my "own" binary-only proprietary version of slashcode (renamed of course) and not continute to make millions of dollars

  26. Courts rule software can be modified/redistributed by jamienk · · Score: 4, Funny

    August 11, 2003
    AP Wire
    In a surprise 6-3 decision today, the US Supreme Court has ruled that the GNU Public Lisense is not enforcable and that programmers, users, and sellers do not need copyright holders' permission in order to modify, copy, or redistribute any machine- or human- readable code.

    With IP law thus crippled, Free Software advocates expressed shock and confusion about how to proceed. "Now that I can just legally use a copy of NT with a cracked serial," Linux creator Linux Torvalds moaned in Washington, DC, "There doesn't seem much point..."

  27. severability by MattW · · Score: 1

    I would love to hear the answer from a lawyer. Let's say the requirements of the GPL are, for one reason or another, held unlawful. Would that mean that anyone using GPL code would lose the benefit of the agreement? It seems preposterous that in the era of insane shrink-wrap license agreements, where you have to commit your pets and small children to research by aliens in order to use a calculator program, that something as simple as the GPL could be shot down. But if it were, would that leave code licensed so far under the GPL as freeware, or as code without any license that it would become illegal to copy?

    1. Re:severability by Anonymous Coward · · Score: 0

      No, the copyright owners still own the copyright. They would simply not be permitted to allow people to copy their work (subject to the requirements set out in the GPL).

    2. Re:severability by Tsu+Dho+Nimh · · Score: 1
      If the GPL were shot down, the default is copyright law. The GPL grants right in addition to the right inherent in acquiring a copyrighted object ... the right to modify and distribute, with certain restrictions such as making source code available.

      If you fail to follow the terms, and distribute without allowing othres the right to do the same, you lose the GPL protection and are immediately in violation of copyright ... and every individual who has a line of code in that distro can claim infringement.

    3. Re:severability by IM6100 · · Score: 1

      People who distribute the code and follow the provisions of the GPL didn't sign an explicit contract. Either did the people who distribute the code without following the provisions of the GPL.

      So where's this enforcable contract that everbody is espousing? We're to believe that people can and will selectively be allowed to enforce an implicit contract binding other people? Sounds a lot like the toothless EULA licenses that everybody hates and ridicules.

      --
      A Good Intro to NetBS
  28. yup by Anonymous Coward · · Score: 0

    only a madman would mod that down.

  29. Without precedent, it means nothing by drinkypoo · · Score: 4, Insightful

    As such, it's fantastic that the people behind the test of the GPL are IBM. Besides being a three letter acronym themselves, and thus inherently well-suited to understand the GPL's plight, they also have so much money and so many lawyers that it seems inconceivable that they could possibly fail to make the GPL all it could be.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    1. Re:Without precedent, it means nothing by Anonymous Coward · · Score: 0, Insightful

      Or subvert it to their own purposes at the expanse of those that cannot defend themselves.

      Your imagining of IBM as some saintly god of Open Source may be entirely too rose tinted for reality.

  30. Has any licence been tested? by Calgary · · Score: 1

    Has any licence been tested in court? Perhaps some commercial enterprise has threatened to sue or something, which may have resulted in a settlement, but has a court ever decided one way or another on *any* software licence?

    Of course there's the problem with implicitly accepting a licence by opening a box or clicking a button. How vaild is that considering that real world contracts require signatures by both parties (in different coloured ink?) ?

    What about the explicit denial of warrenty? Tort law (I believe) covers your Pinto's gas tank (and Firestone tires), but what about engine management software or the code in avionics systems? Can a licence wash the responsibility for due care and dilegence away?

    If the GPL proves unenforcable, how will commercial licences be affected?

  31. Re:No by tarquin_fim_bim · · Score: 1

    "It has no legal support."

    Things only need legal support if they are inherently without the law on their side.

  32. Old SCO Also Donated Code to Linux by Picass0 · · Score: 5, Interesting

    From Groklaw

    http://radio.weblogs.com/0120124/


    Old SCO Also Donated Code to Linux

    Well, knock me over with a feather. It turns out that old SCO, The Santa Cruz Operation, also donated code to Linux. There is an article dated June 12, 2000, that tells us all about their Linux distribution and their plans, which included scaling it to the enterprise, as marketroids like to call it:

    "While SCO may be rolling out its Linux distribution long after Red Hat and Caldera hit the market with theirs, SCO is no open source Johnny-come-lately. The company offers support services to Caldera and TurboLinux customers. In addition, the company's Tarantella middleware supports Linux, as will Monterey, the Intel-based version of Unix that SCO is building with IBM.

    "SCO is expected to announce 32- and 64-bit versions of Linux for Intel-based servers, which will be available in the fourth quarter of this year. In early 2001, SCO plans to deliver a 32-bit Internet Infrastructure Edition that will come bundled with a Web server and other IP applications. The company is also working on a 64-bit edition for service providers, including ISPs and application service providers, which will feature special billing and management tools.

    "The company is also expected to explore the following areas:

    "--Building the Linux clustering capacity to be in line with SCO's NonStop Clusters technology, which scales to 12 or more boxes with advanced reliability for data and applications. Current Linux clustering technology is generally limited to two or four nodes.
    --Beefing up Linux's symmetric multiprocessing capabilities. Currently the number of CPUs per Linux server is usually limited to eight; UnixWare can run on servers with up to 32 CPUs.
    -- Managing multiple Linux servers as well as applications from a single console as if they were a single system.
    -- Improving security and the ability of Linux to handle applications such as e-mail, including instant messaging.
    -- Adding online support services and documentation."


    Wait a sec. Isn't that what paragraph 85 of SCO's original complaint was talking about, and didn't they say that without IBM entering the picture, Linux could never have scaled? The complaint said:

    "For example, Linux is currently capable of coordinating the simultaneous performance of 4 computer processors. UNIX, on the other hand, commonly links 16 processors and can successfully link up to 32 processors for simultaneous operation."

    That wasn't accurate, but it does give me an idea. Maybe New SCO needs to sue Old SCO and leave the rest of us in peace.

    One year earlier, in 1999, a press release from Old SCO described itself like this:

    "We have over twenty years of experience with UNIX, Intel, and Open Source technologies. In fact, we believe that SCO has the largest staff of Open Source experts of any commercial software vendor.

    "As a founding sponsor of Linux International, SCO is a strong proponent of the Open Source movement, citing it as a driving force for innovation. Over the years, SCO has contributed source code to the movement, and currently offers a free Open License Software Supplement CD that includes many Open Source technologies. SCO UnixWare 7 operating system, the fastest growing UNIX server operating system for the past two years, supports Linux applications as part of its development platform."


    All the Tarantella-Linux press releases from June 1999 to February 2000 are here.All Tarantella press releases from June of '99 to July of 2000 are

    1. Re:Old SCO Also Donated Code to Linux by Risto · · Score: 1

      I remember all this too!!

      I feel like it's "1984" and history is being re-written by SCO

  33. Will SCO last long enough? by TheFrood · · Score: 2, Interesting

    The court date for the SCO-IBM suit is currently set for April 2005. Is it really reasonable to believe that SCO will be a functioning entity at that point? Their management team is dumping stock like mad, and should have long since divested themselves of any stock in the company. So who will be left to go to trial with IBM?

    TheFrood

    --
    If you say "I'll probably get modded down for this..." then I will mod you down.
    1. Re:Will SCO last long enough? by Erik_the_Awful · · Score: 0

      Good point. Maybe the FSF can sue SCO as well, pierce their "corporate veil" and go after SCO's officers. This is unlikely, but it 'shore would be cool. -EtA

    2. Re:Will SCO last long enough? by ReelOddeeo · · Score: 2, Informative

      IBM carefully selected four patents. In their complaint, on each patent count, they list which SCO products infringe each of IBM's patents.

      I admit ignorance of SCO's complete product line. But it seemed to me that thse four pagents are carefully chosen such that all of SCO's current or likely products will infringe at least one of the patents.

      If IBM gets a preliminary injunction, then this will cut off all revenue to SCO!. Of course, there is something else that I would like to cut off of each of the executives, but I would settle for them each getting a comfortable jail cell with Buba.

      Why only four patents? So that IBM doesn't come off in front of the judge as trying to abuse the legal system. If IBM countered with 2000 patents, it would seem very clear that IBM is just gaming the system.

      IBM also, just like Red Hat, asks for SCO to be made to stop their license extortion. With this in place, then SCO will have no money comming in.

      Patent lawsuits are expensive to defend. If I understand correctly, you must either (1) proove that you don't infringe, or (2) proove the patent is invalid. Either one takes lots of expensive patent research, sometimes on very old patents.

      So we come back to the question: Will SCO last long enough?

      --

      Those who would give up liberty in exchange for security and DRM should switch to Microsoft Palladium!
  34. How would a court rule against it? by jamienk · · Score: 4, Insightful

    * Could a court revolk my GPL-given right to modify GNUCash?

    * Could a court grant the right to Novel to sell a modified, binary-only version of Reiser v 4?

    How, exactly, could the GPL be ruled against? There may be small, fringe issues, but overall, the GPL rests on the exclusive rights to modify and copy given to IP owners of their works. When a copyrighted work is GPL'ed, the owner gives me extra rights. It is difficult to see how a court could forbid me from allowing you to sell or give away some PHP code that I wrote.

    1. Re:How would a court rule against it? by merdark · · Score: 1

      * Could a court revolk my GPL-given right to modify GNUCash?

      Yes. What GPL given right? You speak of the GPL as if it is GOD or something. It is not. If the courts say the GPL is worthless. Well, it's worthless.

      * Could a court grant the right to Novel to sell a modified, binary-only version of Reiser v 4?

      Sure. Are you ok? I'm starting to be conserned for your health here. You do understand that the courts MAKE the laws right?

    2. Re:How would a court rule against it? by sflory · · Score: 1

      A court could rule that the GPL is non binding. Or rule in such a way that you would not have legal recourse to prevent close sourced versions.

      --
      IANALBIPOOGL (I am not a Lawyer, but I play one on GrokLaw.)
    3. Re:How would a court rule against it? by RedWizzard · · Score: 1
      * Could a court revolk my GPL-given right to modify GNUCash?

      Yes. What GPL given right? You speak of the GPL as if it is GOD or something. It is not. If the courts say the GPL is worthless. Well, it's worthless.

      Correct. If a court ruled that the GPL was invalid with respect to GNUCash you would lose the right to distribute changes (you could still make and use changes privately, unless the court ordered the destruction of the source code you have). To continue to distribute changes you would require the permission of the copyright holder.
      * Could a court grant the right to Novel to sell a modified, binary-only version of Reiser v 4?

      Sure. Are you ok? I'm starting to be conserned for your health here. You do understand that the courts MAKE the laws right?

      Possible but exceedingly unlikely. Anything Novell derived from Reiser FS would contain considerable code copyrighted by Hans Reiser's company. If the GPL does not apply then Novell would need an agreement with that company to distribute that product. A court could order such an agreement but it would be a very unusual situation. More likely the court would rule that Novell cannot distribute anything based on Reiser FS and leave it to Novell and Reiser to negotiate any licensing agreement they desire.
    4. Re:How would a court rule against it? by rmohr02 · · Score: 2, Insightful

      The court could possibly find some part of the GPL illegal (I don't have any idea what, and I think if they did MS would have had to buy the judge), but then, since the GPL requires all of its terms to be followed, or none of them, the work you created would fall back to normal copyright, in which nobody can reproduce it without your express consent. This was previously given under the GPL, with restrictions. It seems that you could logically place the same restrictions on a case-by-case basis anyway, so there is no logical case against the GPL.

    5. Re:How would a court rule against it? by jamienk · · Score: 1

      When I write code and give it to you under the terms of the GPL, I am giving you permission to modify and redistribute my code (with certain restrictions) in ways my copyright wouldn't allow you to do. A court saying that I'm not allowed to do that is sort of like a court saying I'm not allowed to let you use my frying pan -- sure, you have no God-given right to use the pan, it's MINE after all, but it would be difficult for a court to forbid me from giving you that permission.

      And more: if a court orders that Novel, for example, can use MY code in ways that I expressly forbid (and I hold the copyright), then it stands that I can use their code, or yours, in ways that you don't want me to (and which your copyright gives you the exclusive rights to).

      The GPL simply formalizes the permissions that I give you for my intellectual property that, by default, you wouldn't otherwise have.

    6. Re:How would a court rule against it? by jamienk · · Score: 1
      To continue to distribute changes you would require the permission of the copyright holder.
      But wouldn't this permission take the form of an agreement very simmilar to the GPL? After all, that's what GNUCash's authors wanted the terms to be...
      More likely the court would rule that Novell cannot distribute anything based on Reiser FS and leave it to Novell and Reiser to negotiate any licensing agreement they desire.
      Of course, again, Hans Reiser would want the agreement to have the same terms as the GPL...
    7. Re:How would a court rule against it? by RedWizzard · · Score: 1
      But wouldn't this permission take the form of an agreement very simmilar to the GPL? After all, that's what GNUCash's authors wanted the terms to be...
      Sure, but a specific license agreement negotiated and signed by the parties involved will likely be looked on with a lot more favour by the courts (I'm assuming here that the courts have already taken a negative view on the legality of the GPL). The conditions and term may be exactly the same as the GPL but because the two parties are named specifically it will have more weight. Note that in the GNUCash case this is probably impossible to achieve since it will probably be impossible to contact all the copyright holders. Reiser FS may or may not suffer from the same issue.
    8. Re:How would a court rule against it? by merdark · · Score: 1

      "When I write code and give it to you under the terms of the GPL, I am giving you permission to modify and redistribute my code (with certain restrictions) in ways my copyright wouldn't allow you to do."

      Sure, but if GNUCash is ruled to have illegal code in it and the courts decide that no one can use it, than you can no longer contribute to it or use it. You're welcome to go make another GNUCash of course.

      "And more: if a court orders that Novel, for example, can use MY code in ways that I expressly forbid (and I hold the copyright), then it stands that I can use their code, or yours, in ways that you don't want me to (and which your copyright gives you the exclusive rights to)."

      If a court orders you to give up your code to Novel, then Novel gets your code. That doesn't give you the right to go break the law either. Think of this, someone sues you for, say, insulting them. You don't think you did anything wrong. But the courts decide you must pay up. That's it, you pay up, and you have no rights to go take someone elses money just becuase you feel your money was wrongly taken.

      You don't seem to understand, the courts can order whatever they like.

  35. GPL code is copyrighted code by Anonymous Coward · · Score: 0

    Because GPL code is copyrighted, the owners of the copyrights have the final say in how the code can be used. The only change I could envision is that securing permission to use GPL code might become somewhat more formal (e.g. like the "one click license").

    1. Re:GPL code is copyrighted code by Pofy · · Score: 2, Informative

      >Because GPL code is copyrighted, the owners of
      >the copyrights have the final say in how the
      >code can be used.

      No, copyright does not give you the right to tell how something is USED. It gives you an exclusive right (with some exceptions) to make copies, derivative work, public performnace and such. That is is. It does not cover general use of a work, even though many software, music and film providers wants to make you believe otherwise.

  36. Too Late by Anonymous Coward · · Score: 0

    5 years from now?

    Shit man, if this thing doesn't hold up in court I'd like to know 10 years ago!

    If every corporate pirate can just swoop in and steal my code I might as well have been using a BSD the whole time instead.

    Linux is nice and all but let's face it the only thing it's got going for it is the GPL.

  37. This is the guy. by niko9 · · Score: 1

    I would love to see this guy defend the GPL.

    It would be memorable for generations of geeks to come.

  38. maybe an error by initnull · · Score: 0

    Sure the gpl should be tested in court but i dont think it is the best case to test it.

  39. SCO Blew its Chance by Shadow+Wrought · · Score: 2, Insightful
    The GPL, if I remember correctly, allows for companies to break its covenants if they inadvertantly released their code through it. SCO blew their chance on this bit when they failed to shut down their Linux sales. Its hard to argue that you are "unaware" of something once you have filed suit!

    My reading of the GPL leads me to believe that it will be ruled enforceable. It is a well thought out contract that was crafted with instances like this in mind. Well maybe not SCO's Jerry Springer impersonations, but the general siuation nonetheless;-)

    --
    If brevity is the soul of wit, then how does one explain Twitter?
    1. Re:SCO Blew its Chance by ReelOddeeo · · Score: 1

      How can SCO claim that it did not know what it was distributing? For eight years? They would look pretty stupid in front of the judge.

      IBM can of course argue that SCO either knew what they were shipping or should have known.

      --

      Those who would give up liberty in exchange for security and DRM should switch to Microsoft Palladium!
  40. Judicial Activism by Anonymous Coward · · Score: 2, Interesting

    The attitude presented behind this posting is an example of the growing trend of Judicial Activism. In essence, due to our current flawed process we read too much into historical cases and the cases themselves begin to define law - which is not the job of the judicial branch of government. This growing trend will increasingly effect our laws and our society by unelected leaders. Please read Ron Paul's take on this matter in a column of his called "Federal Courts and the Imaginary Constitution".

    too_lazy_to_create_an_account

  41. Personally, by Sevn · · Score: 2, Informative

    I think this is a good thing. It was going to happen sooner or later. At least it's happening with a monsterous litigious bastard like IBM in the drivers seat. This is a wet-dream best case scenerio in the happening. I mean, damn. I'm going to have a friggin party. Money talks. Period. SCO could even win their pathetic lawsuit, and still get buried by the IBM patents they are infringing on. SCO is history no matter what. Gone. So long. Thank you for playing. So their only hope is to keep getting a story every single business day to drum up support for their ludicrous licensing scam, and hope more idiots bite.

    --
    For every annoying gentoo user, are three even more annoying anti-gentoo crybabies. Take Yosh from #Gimp for example.
  42. Let's find out if you're correct by Anonymous Coward · · Score: 0

    Please provide some links ;)

    1. Re:Let's find out if you're correct by Anonymous Coward · · Score: 0

      What a pretty girl!

      Fine looking body too!

      Oh Nice panties...

      Someone's looking horny...

      Oh that feels good I bet...

      Ooo, Kinky!

      Damn, what a dirty slut!

      Have a lolli...

      Yummy!

      That's a bit I rounded up quickly on google, I can't just be browsing around the net with a massive boner popping up in my shorts with folks wandering about the apartment you know...look for the blacks on blondes photo set if you can though it's fantastic...actually it looks like she likes to get boned by huge blacks dongs frequently cuase there are more sets like that!

  43. Choices, choices... by SagSaw · · Score: 3, Interesting

    Basically, I see three possible outcomes of any "test" of the GPL:

    A. The court rules that the GPL is a valid agreement/contract between the copyright holders and a licencee permitting the licencee to re-distribute the copyrighted work under certain conditions. Everything continues along as normal.

    B. The court rules that the GPL is not a licence agreement and that the GPL does not grant any rights in addition to copyright law. GPL3 is created by the FSF to fix any issues and automatically supercedes GPL2. Everything continues as normal after a slight delay.

    C. The court rules that some part of the GPL is not valid. Depending on which part, some licencees may gain rights not intended by the copyright holder. GPL3 is drafted to plug the hole and everything continues as normal, except that licenced as GPL2 can now be used in an unintended and/or undesired manner.

    Warning, the following assumes that SCO-owned code improperly made it into the linux kernel, an assumption which is far from proven true.
    SCO is in deep shit. They continued to offer the linux kernel under the GPL even after they were made aware that some of their copyrighted material made is way into the kernel through improper channels. It's going to be hard to convince a sane judge that they should be allowed to "take back" code that they previously licenced under the GPL. If, however, they can convince the judge that the GPL is invalid in some way, it might nullify any rights granted by the GPL. This would let SCO say "we never released the code under a valid licence, so no rights to use our code were ever granted." The kernel folks would also have a hard time releasing the kernel under another licence (a hastily drafted GPL3, for example) since they don't know which parts of the kernel are theirs and which are SCO's.

    --
    Come test your mettle in the world of Alter Aeon!
  44. Conservative Courts Reticent to Break Contracts by tjstork · · Score: 3, Interesting

    The big thing in favor of the GPL is that it is a private contract between two parties and anything the court does to disrupt that relationship is going to invite precendence for all of business, for any contract.

    It's possible that a challenge to the GPL might get thrown out because it is a binding contract... or maybe they will decide that the GPL is not a contract for some reason. But, if they do, those reasons would have to be very narrowly defined or they would invalidate other contracts. Given that the propensity of the courts these days is to favor privacy of contracts and commercial relationships, I would be shocked if the courts actually ruled against GPL.

    A bit of background. In the US system, the judiciary branch is charged with "interpreting the laws". Largely, if Congress drolls out some stupid bill, as they usually do, it falls on the courts to try and put a "sane spin on it." For this reason, the courts are not elected positions, they are appointed, and, the people once appointed are in for life. Usually the ruling political party puts in people of its philosophy, but there have been some famous goofs - like Bush - Souter.

    Usually a court case does not make it to the supreme court unless it has some sort of constitutional issue associated with it. How a GPL case might make it to the SCOTUS is interesting indeed. Would it fall under free speech? Would it fall under Commerce? Would it fall under Intellectual Property? Would it fall under the bill of rights about the exclusion of business...

    --
    This is my sig.
    1. Re:Conservative Courts Reticent to Break Contracts by IM6100 · · Score: 1

      How is the GPL a contract?

      Who signed on which dotted line? Were there witnesses at the signing?

      --
      A Good Intro to NetBS
  45. Re:Protect your work by Anonymous Coward · · Score: 0, Informative

    How exactly is your work protected, by something that requires you to show the mechanism?

    If you want to protect "your" work, obfuscate your proprietary source code and distribute only binaries.

  46. And only /. editors have unlimited mod points by Anonymous Coward · · Score: 0

    Methinks it's not a coincidence.

  47. No, we've needed clearer case history by SuperBanana · · Score: 3, Interesting
    Do you have faith in the justice system (or IBM's Lawyers) to draw the right conclusions?

    No- but that's irrelevant. SCO could pull a legal rabbit out of its hat, and win, and it could all end up being 100% kosher. MAYBE there is some blatantly copied code.

    The HUGE problem is that this would set a case precedence of sorts. Ie, everyone would think "the GPL is worthless." WORSE, people will violate it even more freely than they do now- and we know, from Linksys and others, that they do, wholesale. Imagine how much cut+pasting happens, or how many derivative works there are, etc...

    Copyright holders have had many, many years to establish case history in far better cases than this- ones where people have violated the GPL, there's plenty of evidence, etc. It's a failing of the open-source model; because no SINGLE individual feels the need(or has the resources, perhaps) to challenge a violation, we ALL loose. This is sorta why the FSF exists.

    Notice I said "copyright holders" at the start of the last paragraph, and not "The FSF". If you read their mission statement, you'll notice that they very clearly point out that they can't do JACK on their own if they don't own the copyright; the ball is in the court of those whose IP SCO is laying claim to. If you approach the FSF and ask for help, they'll help- but they can't just charge into court and yell "WE ARE HERE TO DEFEND THE PENGUIN'S HONOR!"

    1. Re:No, we've needed clearer case history by Anonymous Coward · · Score: 0

      >No- but that's irrelevant. SCO could pull a >legal rabbit out of its hat, and win, and it
      > could all end up being 100% kosher.

      Rabbit? Kosher?
      You must be joking, ask any rabbi - rabbits are as non kosher, as, say penguins. :-)

  48. License vs. Lawyers by Anonymous Coward · · Score: 0

    Well it isn't MS, they would not want it secret, and they get what they want with the Unix License.

    It could be SUN, they tried to keep the last deal hidden.

    The reality is probably that someone with very few Linux machines decided it would cost less to buy the licenses than it would cost to ask the lawyers.

    A full priced license is only $1400 once, the lawyers want $150 just to pick up the phone...

  49. All contracts are subject to court tests... by Anonymous Coward · · Score: 0

    if any of the contractual parties wish to take that route.

    The GPL, as a contract between two or more consenting parties, is binding like any other contract unless part or all of it is nullified by a court decision, and then possible only in that court's jurisdiction. The same is true with Microsoft's contracts, IBM's contracts, etc...

    The sooner the GPL is tested, the better. Under the current circumstances, having IBM in the ring fighting for you is a huge asset and advantage. IF IBM's legal department cannot defend the GPL against SCO's attacks then no one can.

  50. Copyright is NOT a contract, it is the law by 47PHA60 · · Score: 5, Insightful

    A contract is an agreement entered into by two or more parties. A copyright license is not a contract. Copyright is stronger than any contract in US law, and copyright and the terms under which use of copyrighted material is granted are well tested in US courts.

    If I write code, or a poem, or a novel, I own the copyright, EVEN IF NOBODY agrees to my terms of distribution. Nobody has signed a contract with me to use or distribute it, but the copyright is still mine, and I can dictate terms of use for my work as long as it's in effect.

    The GPL states this very clearly; I have italicized the part that I believe relates solely to copyright vs contract:

    "5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it."

    Nothing in copyright law gives you any rights over the software, except the terms dictated by the copyright holder (in this case, the terms of the GPL). If I write a novel and drop the manuscript, and you find it, you have no right to publish it, because the copyright is not yours. Under copyright, law, you have ABSOLUTELY NO RIGHTS to a work EXCEPT those granted by the copyright holder.

    The term "intellectual property," was invented by by people like those running SCO, because they want you and me to confuse an expression of an idea, which is under copyright, with the idea itself, which is not. Code is an expression, the algorithm or method is an idea. If SCO, MS, and others can obfuscate the fact that "intellectual property" does not exist in US law, they can make you think that expressing an idea with your own code (also called reverse engineering) is illegal. The only place in US law that ideas protected is patents, and there is much controversy about that.

    All this means that if the GPL is found to be invalid, then all software licenses will follow, because copyright is the only thing that gives them their power.

    1. Re:Copyright is NOT a contract, it is the law by HiKarma · · Score: 1

      "5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it."

      Here's where the GPL is stating the law incorrectly. First of all, fair use rights allow you to modify and distribute the program regardless of the copyright licence, so the GPL should not say that "nothing else grants you permission." In addition, the claimed GPLd work may be in the public domain or covered by another licence, and so again such a statement is false.

      Next, I believe they are wrong in saying that if you copy the program you are accepting the terms of the GPL. If you copy the program, you are violating copyright, not accepting the gpl.

    2. Re:Copyright is NOT a contract, it is the law by Anonymous Coward · · Score: 0

      >Here's where the GPL is stating the law incorrectly. First of all,
      >fair use rights allow you to modify and distribute the program
      >regardless of the copyright licence, so the GPL should not say that
      >"nothing else grants you permission.

      Wrong. This is exactly where the idiots runing Napster got into trouble. They thought they could screw around with copyright law too. You have no "fair rights use" to abuse GPL code or anything else placed under copyright. END OF ARGUMENT.

    3. Re:Copyright is NOT a contract, it is the law by rmohr02 · · Score: 1
      Here's where the GPL is stating the law incorrectly. First of all, fair use rights allow you to modify and distribute the program regardless of the copyright licence, so the GPL should not say that "nothing else grants you permission." In addition, the claimed GPLd work may be in the public domain or covered by another licence, and so again such a statement is false.
      Fair use gives you the right to make backups for personal use and to allow friends and family to use the software, but that is all (it certainly does not allow you to redistribute a modified version of the program). Some of the code in the GPL'd product may be in the public domain or through another license, but you will have to find that code through alternate means, as the modifications made to that code and the other code unrelated to that code is only available under the GPL (assuming the project you're getting the code from is authorized to use the third-party code under the GPL).

      Next, I believe they are wrong in saying that if you copy the program you are accepting the terms of the GPL. If you copy the program, you are violating copyright, not accepting the gpl.
      You have an option--you can violate copyright, or adhere to the terms of the GPL (unless you are making a backup, which is allowed under fair use).
    4. Re:Copyright is NOT a contract, it is the law by HiKarma · · Score: 1

      Fair use rights are much more vague than that. THey are of course not a blanket right to do anything, but they are also not simply to make backups. (They are not, by the way, to give copies to friends sand family. USEing the software does not infringe copyright unless you copy it.)

      Fair use rights, for example, would include the right to write a review of a GPLd program, by taking it and adding all sorts of comments to it about how it works or why it sucks. You could then legally sell that review, and your review and new comments would NOT be covered by the GPL. Others could not redistribute them without your permission.

      Fair use rights would allow a teacher to modify a GPLd program to illustrate an educational point in computer science, and to distribute that program to all his students, but the modified program would NOT be subject to the GPL.

      Thus, the GPL should not say nothing else grants you permission. Ok, to get strict, fair use is copying without permission, so fair use rights don't "grant you permission" -- they make your non-permitted copying not a copyright violation.

      But that's a minor quibble. The GPL, properly written, would say that you retain your fair use rights regardless of the GPL, and that the code may have other licences which could grant you permission.

      People incorporate public domain code into their programs all the time, and sometimes they GPL the programs. However, the public domain portion is still public domain, and I don't have to go out and find another public domain copy, not strictly, though I might want to check it to be sure I am safe.

      And as to the last sentence, you've almost got it. The GPL assures you that if you follow the GPL rules in any distribution of the software, you will not be violating the copyright. That is what it does. It does not bind you to follow those rules, it just says if you do follow them you won't be sued

    5. Re:Copyright is NOT a contract, it is the law by danoatvulaw · · Score: 1

      Here's where the GPL is stating the law incorrectly. First of all, fair use rights allow you to modify and distribute the program regardless of the copyright license, so the GPL should not say that "nothing else grants you permission." In addition, the claimed GPLd work may be in the public domain or covered by another licence, and so again such a statement is false.

      First of all, if you want to get the law correct, fair use is not your "right" as much as you seem to believe... fair use is a defense to what otherwise would be considered copyright infringement. You must affirmatively prove that your use qualifies as fair, you cannot simply say "well, i can do whatever I want, claim fair use and you prove me wrong." see 17 USC 107 Secondly, the rest of that paragraph is utter garbage and serves no purpose other than flaimbait.

    6. Re:Copyright is NOT a contract, it is the law by HiKarma · · Score: 1

      Actually, that's exactly how it works. You do what you want, and claim fair use, and they then must sue you to stop you and, in the suit, prove you wrong about that.

      Now I agree though that it's not that simple. In that once in court the burden will be on you to show the fair use. Their standard of proof is low, only as high as you set it with your own case as to why it's fair use.

      It is common to talk about fair use rights, even though statutorily fair use is as you say a defense against a claim of infringement.

      That's because fair use is there to stop the copyright act from violating the 1st amendment. It is declared, as the first amendment is interpreted, that you have a very strong right to criticise, and that no law may abridge it. The fair use doctrine is, in part, an affirmation of those rights, and so it is not inappropriate to call them fair use rights.

      As for the rest, I am not sure why you think it's flamebait, I intend it as reasoned argument. I'm not interested in debate where people sit and call the other's postings utter garbage, however, so no need to reply if that's your style!

    7. Re:Copyright is NOT a contract, it is the law by Anonymous Coward · · Score: 0

      Thus, the GPL should not say nothing else grants you permission. Ok, to get strict, fair use is copying without permission, so fair use rights don't "grant you permission" -- they make your non-permitted copying not a copyright violation.

      You are making the very common mistake of interpreting the GPL in terms of US copyright law. The GPL is intentionally vague/general to cover the different legal systems all over the world. For example: In most European countries there is definitely no blanket permission for teachers to copy material to their students, and Europe doesn't generally separate authorship from copyright (you never have to register a copyright to get statuatory damages).

      Several very intelligent law scholars have helped writing the GPL - the descriptions you are quoting are there to state the intent of the license. I have no idea about the US, but in a lot of other countries the court will take this into account: You won't have much chance of claiming ignorance or fair use if you intentionally violated the intent of the license and cannot *prove* you were right.

      If we use your teacher example: Do you really think a court would accept if a teacher bought one copy of WindowsXP and then copied it to all his students?

    8. Re:Copyright is NOT a contract, it is the law by Pofy · · Score: 1

      >...but the copyright is still mine, and I can
      >dictate terms of use for my work as long as it's
      >in effect.

      and

      >Under copyright, law, you have ABSOLUTELY NO
      >RIGHTS to a work EXCEPT those granted by the
      >copyright holder.

      This is not correct. Copyright laws do NOT dictate use. Copyright laws hanld only a few specific things, such as copying, distribution (of additional works usually), public performance and such. Actual USE is not at all covered.

      It is very important also to realise the difference between the actual "item", like the boom, or software program, and the "content" of it. The copyright governs the content. As such, I can own a book, and it is mine, yet I might not hodl the copyright to the content. There is NOTHING in the copyright laws that prevents me from using the book or program I might own. And there is no need for any special permision from the copyright owner to use it. You do need permision from the copyright owner if you want to make copies to give away for example or if you want to read a book for the public somewhere and so on.

      So no, it is not correct to say "you have absolutely no right", the correct way would be to say that one has ALL the rights, except a few, specified in copyright laws, that are exclusive to the copyright owner. And note, there are several exceptions to the exclusiveness as well.

    9. Re:Copyright is NOT a contract, it is the law by Pofy · · Score: 1

      >Fair use rights are much more vague than that.
      >THey are of course not a blanket right to do
      >anything, but they are also not simply to make
      >backups. (They are not, by the way, to give
      >copies to friends sand family. USEing the
      >software does not infringe copyright unless you
      >copy it.)

      As allready said, you are arguing, it appears, by assuming your own countries law applies everywhere. In Sweden for example, the equivalency to "fair use", although it is actually part of the actual copyright laws, gives you permision to make copies for "private use". This private use DO include copies to family and close friends. So, yes, here it is allowed to copy a music CD you own and give the copy to a friend of yours. This copying for private use does not apply to computer software though.

    10. Re:Copyright is NOT a contract, it is the law by HiKarma · · Score: 1

      Actually, I'm talking about U.S. law here, the law where the GPL was drafted, not my own country's law.

    11. Re:Copyright is NOT a contract, it is the law by Pofy · · Score: 1

      Just because the GPL was drafted in US, does not mean US law govern it. If you want to apply the GPL in some country, that county's laws apply to it. FOrtunately copyright laws are quite similar in most countries, but differences DO exist.

    12. Re:Copyright is NOT a contract, it is the law by rmohr02 · · Score: 1
      People incorporate public domain code into their programs all the time, and sometimes they GPL the programs. However, the public domain portion is still public domain, and I don't have to go out and find another public domain copy, not strictly, though I might want to check it to be sure I am safe.
      Yes--especially since the person incorporating the code may have made one or two minor changes.

      And by "modify and redistribute" in the grand parent, I was thinking making changes and selling them. You are correct--fair use applies mostly to private and educational use, and the GPL does not take away fair use. It is unnecessary for the GPL to state that it does not take away fair use, because laws already state that.
    13. Re:Copyright is NOT a contract, it is the law by 47PHA60 · · Score: 1

      I can modify and distribute copyrighted material under "fair use?" That would be news to most musicians, programmers, and authors. I think that parody is the only type of distribution that I have seen protected this way. Can you cite a US precedent or law that permits this?

    14. Re:Copyright is NOT a contract, it is the law by 47PHA60 · · Score: 1

      What you are saying makes sense, but in practical terms, copying, distribution, and performance precede use. That is the spirit behind copyright.

      You're saying that if I write a program on my computer, not intended for distribution, you can copy and use it, and I have no remedy under the law. Is use of a computer program defined as "public performance," or is it more like reading a book?

      For all practical purposes, you have no right to my code except those that I grant.

      As for your examples, I think you do need permission from the copyright holder if you want to copy books and give them away. Start copying programs, CDs and books and give them away on a website, and we'll see how long that lasts.

    15. Re:Copyright is NOT a contract, it is the law by Pofy · · Score: 1

      Actually, by use I mean how I "use" the specific copy I own. When it comes to a book it mean I can read it were ever I want, I can burn it up, toss it out of the window, give it away to someone else, sell it to someone else, tear the pages out of the book one by one (and rearanging them in whatever order I want) and so on. For computer programs it means the same thing and so on. People tend to believe that copyright prevents USE (as in ordinary use of items you own, expamples of which I gave) and is not allowed unless given special permision. Often claiming that you actually need a EULA for example to be allowed to "use" your computer program and so on.

      I agree that copying, and more evidently public performance is also a sort of use and that may have been confusing. SOrry about that.

      So yes, in those "uses" copyright laws give the copyright owner exclusive rights, you must get permision, but such uses are ver limited and thus a general statement that "you have no right to use it without permision" is not correct in most cases.

      >You're saying that if I write a program on my
      >computer, not intended for distribution, you can
      >copy and use it, and I have no remedy under the
      >law. Is use of a computer program defined
      >as "public performance," or is it more like
      >reading a book?

      So, no, you can't copy it since it is not allowed by copyright law. However, actually running (and using) the program would NOT be prevented by the copyright law (I could possibly commit other crimes in doing so, like breaking into your house to get to the computer though).

      Similary, if someone writes a poem on a piece of paper it would not be illegal or prevented by copyright laws for anyone to read it. No special permision is needed. At times, this seems contrary to what typical content providers wants you to believe. That is, they want you to believe that unless you aquire a special license you are not allowed to listen to some music or run a computer program. That is not so.

      >For all practical purposes, you have no right to
      >my code except those that I grant.

      Again, I have ALL rights, except those that copyright law restirct in granting you an exclusive right to it, and the only such rights regard copying, public performance and a few other such cases. ALL other "rights" are simply not handled or prevented by copyright laws and thus allowed although it might at times be hard to do it without breaking other laws, such as having to break into your house to use a program only in existance in your home computer. However, the actual use of the program would not be illegal in anyway.

      >As for your examples, I think you do need
      >permission from the copyright holder if you want
      >to copy books and give them away. Start copying
      >programs, CDs and books and give them away on a
      >website, and we'll see how long that lasts.

      I can't see any example in the text you commented were I said you are allowed to make copies without permision, especially not by doing it over the web. Actually, I said that copying is one of the few "uses" that IS restricted by copyright laws (although in Sweden, the copyright laws for example do give you the right to make copies and give to close friends and family without needing any permision). Perhaps you refere to some other post of mine here with those examples, otherwise you lost me there.

    16. Re:Copyright is NOT a contract, it is the law by 47PHA60 · · Score: 1

      My fault, I misread and saw a "not" where there was none. You did say that permission is needed for copying to distribute. Sorry.

    17. Re:Copyright is NOT a contract, it is the law by poot_rootbeer · · Score: 1

      Copyright is stronger than any contract in US law

      If this is true, how come musicians routinely sign contracts with record companies in which it is stipulated that they assign the copyright for their music over to the record company?

      Copyright law does allow the creator of a work to assign copyright to another party, but couldn't artists argue that a contract that compelled them to do so is unlawful?

    18. Re:Copyright is NOT a contract, it is the law by Pofy · · Score: 1

      No problem, I was a bit confused.

    19. Re:Copyright is NOT a contract, it is the law by HiKarma · · Score: 1

      This (now-old) thread was about a lawsuit involving IBM and Caldera, two U.S. companies, over U.S. contracts and U.S. law. That's the relevant law here.

    20. Re:Copyright is NOT a contract, it is the law by HiKarma · · Score: 1

      Legally, it is not necessary for the GPL to state it doesn't take away fair use, but would you not agree that ethically, it should not give the illusion that it does, when it says that nothign else lets you copy the program.

    21. Re:Copyright is NOT a contract, it is the law by rmohr02 · · Score: 1

      If it was only for the United States it should, but fair use differs from country to country.

  51. We have already lost ground, time to fight back! by alexander.morgan · · Score: 1

    If SCO survives this scam intact and the executives running this con are not held personally accountable, then the Open Source community will have lost regardless of the outcome. Any time somebody chooses a proprietary solution, because they are afraid of a phantom, the Open Source community looses. And with those people turning to other solutions, consulting jobs, careers, recognition for having built or contributed to a great product, etc., all of those things are damaged. My take is, that SCO has already caused tens of millions of dollars damage, a toll that could rise into the hundreds of millions even if IBM and the Open Source community prevail.

    Therefore, it is essential that the community strikes back:

    -- The FSF should establish a legal fund and sue to protect the reputation and joint property of contributors to GPL based products. Since it should be possible to portray the action of SCO as fraudulent and frivolous, it should therefore also be possible to pierce the SCO corporate shield and go after the executives and directors directly.

    -- All of us should petition local, state level, and federal law enforcement agencies to investigate SCO for fraud, extortion, etc. (we need a lawyer to spell out exactly what it is the government should do). SCO is claiming ownership of an entire city, when at best they own a dusty parking lot. I cannot imagine a company could get away with this sort of a thing if real estate was involved. How is intellectual property any different? The goal must be to hold the con artists in charge of this circus accountable--personally accountable!

    -- Petition the Justice Department to investigate Microsoft's payment to SCO, to determine if it was intended to generate Open Source/Linux FUD in an attempt to illegally damage the competition. I know, good luck with W in charge of things );

    That would be a good start, as it would show would be con artists that the Nigerian Bank Scam might be a better opportunity after all...

  52. Social contract was broken according to SCO by geekee · · Score: 2, Insightful

    I would use the SCO case as a litmus test for the GPL. The GPL's legal basis is in copyright. The GPL itself forbids anyone to submit code for which they do not own the copyright. If SCO's claim is true, the code in question should not be under GPL, by GPL's own standard. Therefore, even if SCO wins, it doesn't mean there was anything wrong with the GPL. It simply means that you can't always take someone's word at face value when you enter into a contract with him, which is a problem for any sort of contract, not just GPL.

    --
    Vote for Pedro
  53. Which is it? by The+Bungi · · Score: 1
    [...]the GPL has functioned as a social contract with the implicit (albeit untested) force of law behind it [...] Do you have faith in the justice system (or IBM's Lawyers) to draw the right conclusions?

    If you don't have faith in the legal system to uphold your license, then why have a license "with the implicit force of law behind it" in the first place? Indeed, why have a license at all? You can't have your cake and eat it, too.

  54. Why Not? by Ranger+Rick · · Score: 2, Insightful

    If there's any case that is heavily weighted on our side, it's this one.

    What would you prefer, that the GPL remain in legal limbo while people keep testing the edges without drawing enough attention to bring it to a full-on legal battle? At least we'll know one way or the other whether it's enforcable. Beats finding out 5 years from now when there's more open-source software out there.

    --

    WWJD? JWRTFM!!!

  55. You call that lengthy... by Anonymous Coward · · Score: 0

    Do you read much?

  56. Unknowingly distributing copyright infringments by captredballs · · Score: 2, Insightful

    What if (and this is a big "if", just for the exercise) SCO's copyrights were infringed upon and it unwittingly distributed those infringments via the Linux kernel. Does that mean that their copyrights are automatically invalidated and GPL-ized? No, of course not.

    If the court perceives this as a possibility (ie, SCO says they didn't know "their" code was contributed to linux and accidentally GPL'd it via distrubution), then the court may rule against the GPL, setting a negative precedent.

    I'm concerned that something like this could happen when the bullets (or rather, mountains and mountains of paper) start flying. If IBM can't prove that Caldera knowingly contributed the code in question to Linux, then it seems to me that the GPL need not be brought into the argument. I'd rather they left it alone and stuck to their contract infringements and fraud allegations.

    --

    I suppose I'm not too threatening, presently, but wait till I start Nautilus
    1. Re:Unknowingly distributing copyright infringments by adrianbaugh · · Score: 1

      What if (and this is a big "if", just for the exercise) SCO's copyrights were infringed upon and it unwittingly distributed those infringments via the Linux kernel. Does that mean that their copyrights are automatically invalidated and GPL-ized? No, of course not. If the court perceives this as a possibility (ie, SCO says they didn't know "their" code was contributed to linux and accidentally GPL'd it via distrubution), then the court may rule against the GPL, setting a negative precedent. The court may, at worst, rule that SCO acted unwittingly and its code doesn't have to be released under the GPL, in which case it will be removed from the kernel. They might be able to distribute binary-only modules in the same way as nVidia do for their graphics cards, but there would be big complications with that if any of the code in question has been patched by 3rd parties since SCO submitted it to Linus. However, while all this would be a bad outcome it seems it wouldn't be a ruling against the GPL itself, merely against whether SCO has the right to alter the license to something they've already been distributing. FWIW, my opinion would be that no, of course they shouldn't have the right to do that. If the IP meant so much to them they should have been more careful with it in the first place. It reminds me of when I was a kid and sold a toy AT-AT in a car boot sale for 5, and then went round whining for a couple of days when I realised I could have got more for it, it's just childish.

      --
      "'I pass the test,' she said. 'I will diminish, and go into the West, and remain Galadriel.'"
      - JRR Tolkien.
    2. Re:Unknowingly distributing copyright infringments by captredballs · · Score: 1


      I'm not sure I agree. "IF" SCO really did "own" it and didn't mean to publish it under that license, but an employee contributed it, then SCO should be able to ask that it is removed and placed under a license of their choosing. Anything else would be mean that copyright infringment circumvents copyright protection.

      --

      I suppose I'm not too threatening, presently, but wait till I start Nautilus
    3. Re:Unknowingly distributing copyright infringments by Tsu+Dho+Nimh · · Score: 1
      What if (and this is a big "if", just for the exercise) SCO's copyrights were infringed upon and it unwittingly distributed those infringments via the Linux kernel. Does that mean that their copyrights are automatically invalidated and GPL-ized? No, of course not.

      There is a legal process to follow if you discover that your works have been infringed upon. It involves filing a complaint in the appropriate court, and the complaint HAS TO SPECIFY exactly what part of work "A" is infringed upon by work "B". That is something SCO has not yet done. And a judge will not accept "they have some of our stuff in their stuff, trust me" as proof. I've been thorugh one infringement case and it was very meticulous: we showed our copyright, we showed our material in toto, and with the parts that appeared nearly verbatim in their material highlighted ... they countered by trying to claim that thye had accidentally produced the same maerial as ours ... down to my Canadian spelling quirks and three examples I made up. They lost.

      US copyright law also specifies that this complaint must be begun within three years of the discovery of the infringement. SCO has pissed away over a year of it, if Darl is to be believed.

    4. Re:Unknowingly distributing copyright infringments by goldfndr · · Score: 1
      I think you're oversimplifying it.

      From my reading, adrianbaugh agrees with your POV if it is that simple. What adrianbaugh also points out is that it might not be that simple: the code SCO wants "removed" might not be in the form that SCO "owns" - it might have been modified by some other authors that still might or might not have rights to the modifications of "SCO's" code. SCO would only be able to distribute their stuff as they made it, probably without the other authors' fixes/enhancements.

      And of course adrianbaugh also pointed out that, when SCO is claiming that Linus didn't do due diligence on checking sources' ability to contribute their particular contributions, they are probably even guiltier of not keeping a reign on their own employees in a world of transparency. I don't think you disagree with that particular section but I have a fondness for repeating it.

      --
      Copyrights, Patents, Trademarks: temporary loans from the Public Domain, not real property ("intellectual" or otherwise)
  57. Widepread Civil Disobediance in the U.S. by Nova+Express · · Score: 4, Insightful

    One underlying assumption of this article, that the United States has no experience with widespread civil disobediance, is simply wrong.

    I can think of at least two widespread laws that are regularly broken in America: Speeding laws (probably broken by the vast majority of driving adu;ts at one time or another), and marijuana prohabition laws (probably broken by tens of millions of people at the very least). And let's not forget historical examples such as alcohol prohabition. The author's selective ignorance of this matter (together with suggesting that a "Pacifica" successionist movement is "widespread") make anything he says rather suspect.

    Besides, the real solution to bad laws is not just ignoring them; doing that only gives a chance for the ruling party to selectively enforce those laws against its enemies. The problem is to repeal bad and unnecessary laws. We need far fewer laws, but have those fewer laws better enforced.

    --
    Lawrence Person (lawrencepersonh@gmailh.com (remove all "h"s to mail)

    http://www.lawrenceperson.com/

  58. More important by zakezuke · · Score: 2, Interesting

    What I feel is more important then the GPL in the SCO/IBM case whether or not SCO can freely distribute code either by free ftp or actual sales, then choose to charge licenses after the code is distributed.

    The implications of this are far reaching esp for typical software where money is exchanged. To me, it's like Toyota asking me for extra money for driving my old 1979 360,000 miles when they expected me as a consumer to buy a diffrent car after only 100,000 miles.

    --
    There is no sanctuary. There is no sanctuary. SHUT UP! There is no shut up. There is no shut up.
  59. CA, OR, and HI should secede by Anonymous Coward · · Score: 0

    "There's a strong and growing secessionist movement in the United States, and when I last met the great Robert Anton Wilson (just before Christmas) I asked him which constitutional system he'd choose for 'Pacifica', which is Bob's name for the new breakaway Union of California, Oregon and Hawaii."

    Well, he told me, "We've got one already. We could go back to the Constitution without any interpretation of what the Constitution says: free speech, and freedom of religion. Everything that has been destroyed in the last two hundred years that was intended by the original Constitution. We can start from that. "

    I don't believe the founding fathers had any inclination for welfare, social security, anti-trust legislation, a tax code rewards and punishes based on your choices in life, or any number of other liberal policies that that are taken for granted today. The truth is CA OR, and HI, don't like the constitution, and are trying to turn the US into a socialist state, completely against the US constitution. If they want to secede and start their own socialist paradise like the USSR, N. Korea, Cuba, etc., good riddance. I'd leave CA that day.

  60. Re:Protect your work by commodoresloat · · Score: 1
    If you want to protect "your" work, obfuscate your proprietary source code and distribute only binaries.

    A.k.a. "security through obscurity."

  61. Better now then later... by incom · · Score: 2, Interesting

    The sooner it is tested, the better. If there is anything legally wrong with the GPL then wouldn't you rather know as early as possible, then close your eyes and hide in ignorance , only to open them when something bad happens later?

    --
    True genius is grasping a situation like a peice of fruit, and peircing it just right so that it drains dry.
  62. Not really a test of GPL by ratfynk · · Score: 3, Informative

    If SCO code did get into Linux by someone other than SCO itself then the GPL will not be tested. If SCO itself put the code into Linux then they will most likely be given the right to have the offending code removed from distros other than SCO Linux. This however is most likely not the case otherwise the kernel code would have a history time line that would state exactly when and who was responsible, and if this did happen I think the good computer journalists would have found out about it already, and let the cat out of the bag. Either way I have the feeling that the judge in the case will skirt the GPL issue all together. I feel that either way Linux will lose big time. The money being thrown at making Linux seem to be illegal is too large and has under the counter sponsorship from the big guys except perhaps IBM.

    --
    OH THE SHAME I fell off the wagon and use sigs again!
  63. Depends how it fails by gidds · · Score: 1
    If GPL fails your code will automatically revert to normal copyright

    Sounds like a dangerous assumption. Yes, if the whole thing is declared null and void, then it 'fails safe'. But what if only one or two provisions were declared null and void? Or what if they're valid but don't mean exactly what people think, or otherwise allow some loophole?

    I don't think we can make any 'fail-safe' assumptions.

    (Of course, to my uninformed and untrained eye, it looks unlikely to fail. But we must make ourselves available for all eventualities.)

    --

    Ceterum censeo subscriptionem esse delendam.

  64. Agreed.. by hndrcks · · Score: 4, Interesting

    Thank you for stating what I thought when I read this earier today.

    The difference between Europe and the US is not about laws or respect for laws. Prohibition, and city parking are more current examples - Thoreau and the Whiskey Rebellion are examples from our country's earlier history. Rather, the difference is social norms vs. the social contract. Americans have a tradition of championing 'freedom' and 'individuality', but we still all drive our SUVs to McDonalds. Europeans seem to be much more in tune with social contracts and spend less time concerned with social norms. I think that was the point Mr. Orlowski was trying to make.

    --
    Everyone will start to cheer when you put on your sailin' shoes.
  65. Faith in the justice system... by jmors · · Score: 5, Insightful

    Personally I have alomost no faith in the justice system to do the right thing merely for the sake of "doing the right thing". If they do the right thing it will only be because the side defending the right thing has more money (IBM) so justice may prevail but certainly not because of our justice system. Can there really be any doubt in where the decisions made in our justice system come from? Big corporations, the RIAA, Disney, Oil Companies. As an added hurdle this case will be about technology issues, another huge stumbling block for our judicial system, our legislators, pretty much the majority of those in government office. Please don't get me wrong, I still believe that the United States is one of the greatest countries on earth in which to live, but unless we recognize the erosion of our rights, of our privacy, of our freedoms and stand up and do something about it, it will not remain so forever. I for one do not want to have to explain to my grandchildren why the only people with the law on their side are those with the money and power to buy it! Sorry for my rant...

    --
    The Matrix is real... but I'm only visiting!
    1. Re:Faith in the justice system... by Cyno · · Score: 1

      I agree and I think our judges don't understand the power they hold. If justice were truely blind then all laws would be required to be in compliance with the constitution, or immediately tossed out. The DMCA, for example, would not exist today. Or anything that takes away our freedom to possess objects, because possession hurts noone and is not a crime. In fact our constitution and our founders stated very clearly that we all must have the right to possess weapons. WMDs? It doesn't say, it just says we all have the right. Now, today, we seem to be shrugging this off like it was written by some loony who didn't understand our way of life.

      That's because our way of life has changed. It is now the republican way of life, where everyone is free as long as they don't do drugs or write certain types of software or..

    2. Re:Faith in the justice system... by poot_rootbeer · · Score: 1

      Can there really be any doubt in where the decisions made in our justice system come from? Big corporations, the RIAA, Disney, Oil Companies.

      Why do you say that?

      I don't mean "what incidents suggest to you this might be the case", but rather "what proof do you have that this IS the case".

    3. Re:Faith in the justice system... by HiThere · · Score: 1

      That's what it was designed for. Our system traces back to British law, and the original British lawyers were knights who were sworn to fight to defend their clients. (You may, perhaps, have heard the phrase "God send the right!")

      The legal system is basically designed so that nobody with enough power will get angry enough about things to attempt to overthrow the government. That's it's basic purpose. Everything else is an add-on. Trial by jury was a way to allow the knights to get out of having to mix it up physically (and for a long time, the loosing side had the right to offer a challenge is he found it unacceptable), because mixing it up physically is both a gamble and expensive. Also, it helped ensure community support, which meant that there wouldn't be a mob of peasants storming the castle or ambushing the tax collectors.

      The system was designed for the benefit of the powerful, with only enough sops thrown to the hoi polloi to keep them quiet. But as the number of layers on the pyramid gets higher, more and more people find themselves relatively disempowered. OTOH, if you're half way up, just think of how many have it even worse. Ever wonder why a black teenager doesn't trust the cops? He's got very good reasons. They never (almost never?) act for his benefit. They often act for yours. If your car is stolen, the police will help you. (It was almost certainly stolen by someone with relatively less power, since nobody else would bother.)

      The social interactions are complicated, but don't expect that they ever matched some ideal. It's just that the peasants don't write the history books. But they vastly out numbered the educated yeomanry. And they vastly outnumbered the nobles. And they vastly outnumbered the king. The Magna Charta happened when a bunch of Barons got really pissed off with the king for stepping on their "traditional rights". Read it and see how much the common folk were granted. They were given just enough to keep them quiet, and so that they would (at that point) support the nobles against the king.

      This is where the justice system comes from, and this is it's basic purpose. When you get more from it, be pleased. Don't *expect* more.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    4. Re:Faith in the justice system... by jak163 · · Score: 1

      You are positing a golden age in which up till now law was not on the side of those with money. In fact this has gone back and forth, but money has always been central to American law from the Constitution forward. Cf Morton Horwitz, The Transformation of American Law. The high point of the right to contract and the tilting of the law in favor of corporations came in the 1880s with the Santa Clara decision which said that corporations were individuals under the 14th amendment, so that their property could not be affected by public law without due process. This was then changed during the Progressive period due to theorists such as Oliver Wendell Homes and juduges like Harlan and Brandeis. Things swung back in the 20s, and then of course during the New Deal they went far in the direction of abridging the right to contract. What we are seeing now is a return to new Gilded Age and absolute right to contract.

  66. Knock knock. by Heisenbug · · Score: 2, Funny

    - Who's there?

    - OJ.

    - OJ who?

    - *You* can be on the jury!

  67. The limitation of the GPL by mark-t · · Score: 0, Redundant
    The GPL does not and cannot apply to any derivative work that does not itself contain any code that was GPL'd. Because the GPL gets its strength from copyright, it cannot control what another author does with their own material when no GPL'd content exists in their product, even if it was somehow "derived" from a GPL'd work.

    If that were not true, you may as well be talking about copyrighting actual ideas or concepts, which SCO may think it has a claim to, but certainly doesn't have any validity in our copyright system.

    Interestingly enough, this also means that "GPL tainting" is entirely a myth. You can learn as much stuff as you want from a GPL'd program, but it doesn't mean you can't apply that knowledge to be used in another closed-source program that you yourself write later. Mild cosmetic similarities between the source code of a closed-source program and a GPL'd work could be reasonably considered a result of the limitation that there are often only so many known reasonable ways to implement given algorithms.

    As long as the GPL's concept of "derivative work" only extends to works that still contain some amount of GPL'd code, I would believe and hope that the GPL itself will fare well in court.

  68. One man's activism is another man's justice by DesScorp · · Score: 2, Insightful

    Judicial Activism is one of those terms that has become horribly abused. Basically, if your side loses in court, you scream "judicial activism". When SCOTUS ruled that abortion is a right, conservatives screamed it. When they similarly ruled on conservative-favored issues (drug testing for athletes, etc), liberals screamed the same thing.

    --
    Life is hard, and the world is cruel
    1. Re:One man's activism is another man's justice by Anonymous Coward · · Score: 0

      Horribly abused? If you throw it into the context of the left-right debate, I understand your point. But you have completely ignored the issue of if it is correct or not. Creating law is not to happen in the courts, it is not part of the judicial system. They are to strike laws down or uphold them, not to legislate with a 'decision' on how to view the law. Do we follow the constitution or not? It might be abused by some but that doesn't make it any less important or real. I would encourage everyone to view past the smoke and mirrors of left-right.

  69. EBen Moglen is a sucky name by Anonymous Coward · · Score: 0

    Eben moglen is a sucky name, doesn't he know wealthy elites in the ruling class (like law professors at elitist schools like Columbia) are supposed to take power names not stick with the sucky ass name their parents gave them?

    Who would you side with in a case: Eben Moglen vs. Johnny Teknolojik?

    Or

    Eben Moglen vs. Brad Trustlots?

    Even CEOs of Linux companies know if you are going to be part of the elite ruling class you can't have a work a day joe dork name, just ask Ransom Love!

  70. Re:hapless troll -1 by Idealius · · Score: 0, Offtopic

    Honestly, I'm a C/C++ programmer, and used Windows since the 2.0 days, I'm proficient in DOS, and I currently have a distro of Linux installed on my PC and would say I'm fairly proficient with it, too. The reason why I've never tried FreeBSD?

    The name.

    "BSD" sounds horrible, throw "Free" on it and I'm just confused. Anyway, that's just IMO.

  71. not the supreme court's fault by Heisenbug · · Score: 1

    I'm tired of the Supreme Court gag ... what happened in 2000 was that our election came down within the margin of error of the voting process (flawed as that was). Bush won by statistically zero in Florida, and Gore won by a statistical value of zilch nationally.

    So what happened? Instead of descending into civil war, the coin toss was made by the courts and we moved on. The outcome of the election was handled roughly as fairly as it could have been.

    If you want to be mad at the system, don't blame the Supreme Court -- blame the two party system that handed us two candidates so bland that the average voter stayed home. That wasn't an accident -- it's a deliberate policy of both party machines to select a safe, predictable and manageable candidate. If we had run Bradley vs McCain instead of Bush vs Gore, do you really think the election would have been decided by the courts? I doubt it -- because then voters would have cared enough to vote. And frankly, either of them would have been better than our actual choices.

    Yes, the election was stolen -- but it happened long before the Supreme Court got involved, and the longer it takes us to notice the longer it's going to go on that way.

    1. Re:not the supreme court's fault by Sabalon · · Score: 1

      Personally, aside from the apathetic voters, I blame stupid people in Florida. a) can't figure out a simple butterfly ballot...piece of cake. Or the fact the sample ones were different than the final ones - how stupid are you that you go in to vote for hole #1, hole #4, hole #8.

      And I've always been insulted that they created the electoral college because they thought that the masses were too dumb to elect a president...now I think they may be onto something.

  72. GPL does not need to be tested by digitaltraveller · · Score: 4, Insightful

    The speculation as to whether or not it holds up in court is IMHO a moot issue.
    The GPL as written is a type of clever legal kung-fu that only a true hacker like RMS could come up with.

    Here is a key passage:

    5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.


    If the GPL was struck down, it would be the equivalent of striking down _ALL_ software licenses. In that case you could expect to see Microsoft's lawyers filing an amicus brief supporting the FSF.

    The speculation that you can circumvent the GPL by writing "intermediate software" is a notion that only an engineer could have.

    An analog is like claiming that you can build a robot, send the robot to break into someone's home, and get away with it because "The robot did it."

    Regular people (like judges) find this sort of argument very irritating. Instead they tend to focus on the intent of what a law/contract might achieve rather then the exact wording.

    In criminal cases it's called mens rea. If I send Paulie Walnuts to break Artie Bucco's legs because he hasn't paid me money, can I get away with it because I used Paulie's intermediate 'wetware'?

    In most situations you would be laughed out of court with this argument. Look at Napster.

    1. Re:GPL does not need to be tested by Mike+Hawk · · Score: 1

      Just to be clear on what you are saying here because it flies in the face of the common slashdot perception about licenses...

      If this point 5 of the GPL is allowed to stand regarding License (contract) acceptance, it would also mean all those other software licenses that you passively (or actively) accept also will be legal and binding. Modifying or distributing code is a much more passive act, with respect to contract participation, that actively clicking a button that says "Yes, I accept the terms and conditions of this contract."

      Strangely, the converse does not really hold true. If this clause of the GPL does not hold up, it doesn't necessarily mean all the EULA's of the world are struck down since those actually require more active input to get past and use the software. Also the logic the author chose to build into point 5 is flawed. As with any other instance of copyright, a potential user has 3 choices: 1. Not use the copyrighted work, 2. Use the copyrighted work according the license, 3. Use the copyrighted work beyond the boundaries of the license without permission. A license cannot retroactively deny choice 3. Its still a choice, albeit illegal. This is what copyright law is for, but one can't use that law to deduce as point 5 does that one has entered into a contract. The potential ramifications of that are astounding.

      Lets be careful what we wish for here slashdotters. We need to decide if we are for passive software license acceptance, or against it. I vote against.

  73. What about the DMCA? by mangu · · Score: 2, Interesting
    it would be possible to release a proprietary program which takes a GPL'd source program, patches it and links it with independent binaries to make a new proprietary program


    Wouldn't that program have the sole purpose of allowing you to violate copy protection?

    1. Re:What about the DMCA? by HiKarma · · Score: 2, Insightful

      Not as I currently read the GPL, which mostly talks about restrictions on you redistributing your modified GPLed program.

      I can take a GPL program and modify it to my heart's content on my machine, and keep the source secret, if I don't give the program to others. So far that's been the clear message from most GPL authorities.

      The loophole might be that I can also tell you how to take the GPL program and modify it the same, and neither you nor I distribute the modified program. In fact, I "tell" you how to do it by selling you a program that does it.

      That the GPL doesn't forbid, not directly. The one claim they could try would be to claim (as the mysql company does) that the program that does the modifying is a derivative work. That's a murky, less tested area.

  74. SCO shot themselves in the foot by SQLz · · Score: 3, Funny

    Man, I knew this would happen. IBM is quoting all of Darl's crazy feverish rantings in their counter suit.

    If anything, this case is going to make the GPL stronger because there is no way we can loose.

  75. Bully on IBM! by jtotheh · · Score: 1
    First of all
    I hereby do repeat and reallege the averments in paragraphs 1 through 91,
    with the same force and effect as though they were set forth fully herein.
    IBM is really fighting the good fight, it's interesting to see FUD used as a legal term in a real legal document....Hope it is handled by a wise judge.
  76. Absolutely... by Kjella · · Score: 1

    Even if SCO has IP in the Linux kernel, they are still distributing it under the GPL.

    2b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.

    6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.

    SCO is clearly trying to violate both these counts, by now charging for the "work" containing their source code, and to limit the rights to redistribute it explicitly granted to you under the GPL when you download it from SCO. Even if there is SCO IP in the kernel, it does not allow SCO to break the licence agreement with the thousands of third-party contributors. Just because someone stole my car, I can't blow up the highways...

    Kjella

    --
    Live today, because you never know what tomorrow brings
  77. answer one question by Trailer+Trash · · Score: 1

    Those of you who are sweating over whether the GPL will hold up need to answer one question: What legal right does SCO have to distribute the copyrighted works of Linus Torvalds et al? The answer: none.

    The GPL simply says that the copyright holder will grant you the right to redistribute as long as you follow a few simple rules.

    Copyright law is alive and well. The same law that gives the RIAA $150K/incident protects us. Don't worry, the GPL is irrelevant.

    Michael

  78. Re:Courts rule software can be modified/redistribu by redwulf__19 · · Score: 0

    Please provide a link to where go got this information. I have searched the AP wire and found no such info. Of course we all know who you "the original Poster" really is. Take it easy Bill, You have your billions Retire.

    --
    If it came from Microsoft, Flush it!
  79. Legal vs. Moral by imhotep1 · · Score: 1

    This posts meanders a bit, but I eventually get to a point, bare with me...

    I read a comment by an American astronaut (or perhaps it was a European astronaut, I forget) who had gone into space with both the European Space Agency and NASA. When asked to compare the two, he said that in Europe, they have a lot of rules, but enforces them loosely. In NASA, they much less rules, but enforced them much more strictly.

    I once had a German language teacher who explained to the class that there were social and moral differences between Americans and Europeans that were deeper than mere cultural or language differences. He said that in America, there was a strong sense that if you didn't get caught, you never did anything wrong, and that in Europe, that same logic didn't exist.

    While both of these I believe to be strong characterizations, there is a ring of truth to both of them. On the whole, Americans are a regimented and ordered society that believe if someone gives an order then it must be the correct course of action.

    One unfortunate side effect of this 'moral logic' is that it favors those who break the rules. If I can break the accepted rules, and get away with it, then not only will I have broken the rules, but now others will find it acceptable and follow me. With each transgression the dam gains another leak.

    Europeans tend to lack this 'follow the leaders' mentality not out of moral superiority, but out of the experiencing a thousand years of corrupt leaders. We Americans have only had 200 years, and we have only really been culturally aware of it since Nixon.

    Developers tend to not fall into this mental trap. We have a much more single minded approace to knowledge, and approach that is shared with most scholastic professionals, that of a single shared knowledge base, and that knowledge is free. No one objects to Microsoft selling Windows for profit, but developers get a little angry when someone figures out some new API call, and Microsoft get's angry and tells them they can't share that information.

    Businessmen, however, do tend follow this pattern. Rockefeller and Hearst (and some might add Gates,) violated many moral ideals to attain market dominance, and became economic (and in many respects, social and political,) gods.

    In the long run, the survival of the open source software movement relies not on the GPL, or on Linus Torvalds, but on forstering in the general public the basic idea that regardless of law, court rulings, or public announcements by famous businessmen, sharing of information is a right. Cooperation is a right. Free exchange of ideas is a right. Perhaps not an absolute right (I don't have the right to copy someone elses work verbatim and give it to you, if I haven't been given explicit rights to do so,) but an irrevokable right non-the-less.

    In America, the politicians, businessmen, and media are fond of the term capitalism, extoling how it is the foundation of American society. Anything else is communism, and therefore, bad. I won't go about arguing economics here, as it is well outside the scope of my now very overly long point, but I will say that there is now need for a fear of intelectual communism, especially if it is elective. This is what the GPL is, elective intelectual communism. This is what bothers SCO, and Microsoft. This is what bugs the anti-GPL crowds. This is why Europeans look at Americans and wonder, "What's wrong with those people," because they have long since learned that it doesn't matter what the governement says, it's still OK to share with your neighbors.

    1. Re:Legal vs. Moral by nickos · · Score: 1

      On the whole, Americans are a regimented and ordered society that believe if someone gives an order then it must be the correct course of action. ... Europeans tend to lack this 'follow the leaders' mentality not out of moral superiority, but out of the experiencing a thousand years of corrupt leaders. We Americans have only had 200 years, and we have only really been culturally aware of it since Nixon.

      This is spot on. To give a recent example of this phenomenon, look at the treatment of Bush and Blair by their respective domestic media over their justification for the Iraqi war. In the States no-one questions Bush for fear of looking unpatriotic, while in the UK the press lays into Blair for allegedly lying to the country to justify a pre-emptive strike.

      Similarly, actors like Martin Sheen receive hate mail over their opposition to the American governments position, while in Europe celebrities are not attacked for their political views.

      There's a much more articulate account of this behaviour here

  80. For what its worth by rssrss · · Score: 5, Informative

    IAAL, but I am not a copyright guru. I think that there are some misconceptions floating around that I should comment on.

    No court conducts a general review and commentary on any document (law, contract, what have you) that is part of a case before it. The court will review those portions of the document that are relevant to the case in front of it and will neither review nor comment on other portions that are not at issue in that case.

    In this case the issue that IBM raised is whether SCO lost its right to prevent third parties from copying, distributing, modifying, or running Linux by releasing Linux under the GPL. The court can and will answer this question without worrying about whether any other clause of the GPL, say the limitation of damages clause, is valid in another context.

    Now I do not know if every clause of the GPL is valid or if it will work in the way that St. Stallman wants it to work in every conceivable situation. But, if software licenses mean anything, then at the very least IBM's claim (if I have correctly understood and described it above) ought to be sustained. Other portions of the GPL may not work, but I do not think that they at issue in this case.

    --
    In the land of the blind, the one-eyed man is king.
  81. SCO bandits have deep pockets too by plierhead · · Score: 2, Informative
    The dudes at SCO now have pretty deep pockets personally though...Check out what these SCO banditos are pulling in by selling their pumped up stock!

    BROUGHTON, REGINALD C.: Declared Holdings
    SCO GROUP INC
    Senior Vice President

    NasdaqSC:SCOX (historical quotes, profile, other insiders)

    2003-08-05 120,000 Direct Insider & restricted shareholder transactions reported over the last two years
    Date Shares Stock Transaction ADVERTISEMENT

    • 2003-08-05 5,000 SCOX Automatic Sale at $12.56 - $12.57 per share. (Proceeds of about $63,000)
    • 2003-07-30 5,000 SCOX Automatic Sale at $12.80 - $12.81 per share. (Proceeds of about $64,000)
    • 2003-07-22 20,000 SCOX Automatic Sale at $12.91 - $13.2 per share. (Proceeds of about $261,000)
    • 2003-07-17 15,000 SCOX Planned Sale (Estimated proceeds of $195,000)
    • 2003-07-08 5,000 SCOX Automatic Sale at $10.90 - $10.95 per share. (Proceeds of about $55,000)
    • 2003-07-08 5,000 SCOX Planned Sale (Estimated proceeds of $56,450)
    • 2003-06-25 5,000 SCOX Automatic Sale at $10 per share. (Proceeds of $50,000)
    • 2003-06-20 5,000 SCOX Sale at $11.08 - $11.1 per share. (Proceeds of about $55,000)
    • 2003-06-20 5,000 SCOX Planned Sale (Estimated proceeds of $53,750)

    Nice work if you can get it !

    --

    [x] auto-moderate all posts by this user as insightful

  82. GPL *will* affect SCO money grab by SamNmaX · · Score: 1

    Though GPL will likely not affect this case, it will affect SCO's attempts to extort licensing fees for their "binary" licence (assuming of course there is at least some truth to their code being in linux). If they can collect such a fee, then the GPL is essentially useless as people could get away with adding proprietary code to a GPL'ed project and then demand money (and perhaps any other restrictions the company wishes) to use it.

    From what I understand of the GPL, any source code that had these addition restrictions would be GPL (and/or copyright) infringement against the GPL'd code as code that could not be used freely can't be mixed with that code. While some sort of "binary" licence from SCO might protect you from legal actions from SCO, it does not make the program fully legal.

  83. Re:THIS is good by Anonymous Coward · · Score: 0

    OMG who is the fucking homo who modded this down!?!?!?!?!

  84. BSD License w/ advertising clause almost tested by mec · · Score: 3, Informative

    That was part of the USL - BSDI lawsuits.

    The Regents of the University of California copyrighted their code.

    The Regents licensed their code under the BSD license (obviously) including the advertising clause.

    USL, a company related to AT&T, sued the University of California for distributing their proprietary code.

    UC sued back, on the grounds that AT&T was distributing files developed at UC without honoring UC's license.

    Ray Noorda of USL swiftly settled the suit after that, essentially abandoning almost all the original claims. The BSD license did not get tested by a judge, as far as I know.

    Ray Noorda gets around. He went on to found the Canopy Group.

  85. Re:REQ: Daniella Rush Photo Sets by Anonymous Coward · · Score: 0

    I bet if Ava was about to sit on your dick and fuck you stupid, you wouldnt say no ;)

  86. I wish to point out........ by Allnighterking · · Score: 4, Informative

    That this isn't the first test of the GPL!!!!! Mysql recently won their suite concerning illegal usage of Mysql code in a competitors non GPL'd product. It took nearly 2 years but they won hands down. THAT was the first test. That is the case that made the GPL viable. Take a look here.

    Linux Magazine and search for the section, "Jurist Judges GPL as Just"

    The point here is that in his opinion the judge establish legal precident for the GPL and it's validity as a "contract". I'm no lawyer but I do know that the SCO bulldink might be the most current test... but it's not the first.

    --

    I'm sorry, I'm to tired to be witty at the moment so this message will have to do.

    1. Re:I wish to point out........ by PingXao · · Score: 1

      MySQL AB didn't "win" anything. The parties agreed to settle out-of-court. There is a world of difference between a case that is settled out-of-court and one that progresses through a trial and where a verdict is rendered at the end. Furthermore, the opinion of the judge re. the GPL, while a good thing, establishes no precedent whatsoever. A case that is decided at the end by verdict does not automatically establish a legal precedent. A case must be appealed and the decision upheld (or reversed!) for a judicial precedent to be established.

      Even if the MySQL suit had gone all the way through to a verdict, it still would not be considered to be a legal precedent unless the loser appealed and the higher court ruled that the applicable parts of the GPL were valid and enforceable.

  87. Re:REQ: Daniella Rush Photo Sets by Anonymous Coward · · Score: 0

    Oh she is quite fine! I'd like to see her slob a knob or something but she never gets down and dirty for the camera you know!

  88. Yes, but... by Anonymous Coward · · Score: 0

    I could sign myself over to you as your slave, but it would be unconstitutional.

    Since the U.S. is currently a nation of, by and for the corporations for which it stands, please explain why the courts couldn't rule that the GPL is an invalid sport of nature with no standing in current Commerce statutes and has no use/meaning in a capitalist society?

    Isn't enough to be a well-worded contract -- the heart of the matter seems to be whether it the type of contract the judiciary will honor.

  89. Re:OJ - The RIAA Option by Anonymous Coward · · Score: 0

    Suggestion: File RIAA type subpoenas against the company and their customers. It's a journey to the dark side, but will start to get around their customer base.

  90. win-win by geekoid · · Score: 1

    Either, EULAs and copyright code are valid, therefore SCO will lose, or they are not, In which they may win, but it is a strike against EULAs.

    --
    The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  91. Offtopic: How to get paid as a contractor by rossifer · · Score: 1

    When entering into a new contract relationship, insist on clear deliverables and terms of payment: allow frequent invoice submission frequency, short terms (no more than net30), learn what their accounts payable pipeline is (regular invoice approval/check cutting schedule) and then follow each of the first invoices until the check is in your hand and in your account.

    Follow the invoices like a bloodhound. If asked (or even pre-emptively), make it clear that you will not be working (or billing) the hours that you're managing billing and then do it in front of them. The instant one of your invoices leaves the regular billing cycle to actually get close to net30, get ready to leave. When one breaks net30, stop working until the invoice is paid in full.

    I've never had a bum payee, though a few have tried. The real secret to success is to have an initial invoice to them after a week of work and a second in the pipeline by the time the first is paid. In most cases, there won't be enough work that they can afford to stiff you yet, no matter how much they may like to. In addition, the attitude about the early invoices results in a "squeaky wheel" treatment.

    Finally, the secret to success with this strategy is to work very hard and very well on the tasks that need doing. If you're a pain in the ass about your billing and you're not much of a self-starter, you're in trouble and you'll be looking for another client fairly quickly (without a reference). If you're a productivity monster and you let them know that you absolutely insist on being paid on time, you'll get paid and you'll get the reference when the job is done.

    Regards,
    Ross

    1. Re:Offtopic: How to get paid as a contractor by Coventry · · Score: 2, Informative

      These are all fine ideas, and ones I now use regularly in my business - I don't think I mentioned that despite the BS I went through I ended up deciding to be my own boss.

      I think in my case, the bigest things I could of done differently were to have opened my eyes over two things:

      1) Company Y had already proven itself, by how it shut down and sold off my employeer X, to be a ruthless and rude entity.

      2) Person A had a bad reputation outside the tech departments of X and Y for being an ass, and being untrustworthy.

      With #1, I had blinders on and saw the oppourtunity for making money. With #2, I had my blinders on and thought my previous experiences with person A entitled him to 'friend' status.
      In both instances I was dead wrong, and If I'd of taken a step back I'd of given the whole thing more thought ahead of time.

      sometimes some perspective is all we need, and I've found that keeping your perspective and seeing the whole, big picture can be an important part of keeping a biz afloat.

      For example: I recently met with a client who had grand ideas, and wanted all sorts of things done. I wrote a proposal and sent it to them, a short proposal, very informal. considering the features involved, this could be a huge project, so why didn't I write a detailed proposal and send over a work order? Because the (potential) client is a startup, and has money problems. I know that If I spend too much time on proposals for them and they go under I've lost potential business I could of been landing. The (potential) client is bothered by the informal proposal - even though it was informal it has a price range in it. We keep in contact and if they want my services they'll either try to haggle or cut some features. Or, they'll come back 6 months down the line and say 'we're ready to do this now' - which happens more often then you'd believe.

      If only perspective came in a can.

      --
      man is machine
    2. Re:Offtopic: How to get paid as a contractor by Anonymous Coward · · Score: 0

      If they renegged on thier end of the contract (the development) can't you claim ownership (copyright) of the product because the payment was never recieved, and charge them for each infringing use? just a thought

    3. Re:Offtopic: How to get paid as a contractor by PetWolverine · · Score: 1

      Or, they'll come back 6 months down the line and say 'we're ready to do this now' - which happens more often then you'd believe.

      Damn! I'm about to do that!

      It's actually just for a fast SDSL for a startup, but it's the same situation. I had to ask for a price quote. I talked to a salesman, and he even gave me some sort of deal. I relayed the price to my client, and he basically said he expects to be ready for it in about 6 months.

      I think I can believe that happening a lot.

      --
      I found the meaning of life the other day, but I had write-only access.
    4. Re:Offtopic: How to get paid as a contractor by Coventry · · Score: 1

      Yes, I could. But to charge them each infringment would still require going through a lawyer to try to negotiate (they don't respond to my calls/letters otherwise), which incurs legal fees, which rapidly skyrocket out of control.

      Oddly enough, the Best thing I ever found for possible use against them was the DMCA - it has a provision in it stating that removal of a copy-protection feature without permission is criminal, and can lead to civil damages. It also expands on that provision so that every infringing use of the product that has had the feature removed can be treated as an additional infringement, criminal and finable.
      Why was this applicable? - Because I made a backdoor. When things first started to get funky, I put in a special username and password combination - 50+ characters each, so almost impossible to crack - that if ever used would cause the software to delete itself. It was specifically designed to only affect the software, not the data, so their 100k user records in the email system would still be there. My software would be gone, but email and the user data would continue as normal. However, when I mentioned to them (late in the game, after they had rolled the software 'live' in multiple locations and were trying to pay me 1/4th the bill) that this existed and that if they don't pay it would go bye-bye, they hired someone to track it down and remove it. By removing this backdoor - a copyright mechanism I had put in place to protect myself - they violated the DMCA. Lovely, eh?

      --
      man is machine
  92. GPL is not an EULA by Anonymous Coward · · Score: 0

    The GPL explicitly makes no restrictions on your USE of the code. Thus the "U" in "EULA" doesn't apply. The GPL is a "DL" -- Distributor's License. No agreement is necessary either; but nothing except that GPL gives you the right to distribute it.

  93. Product of the 1970's eh? by Anonymous Coward · · Score: 0

    I can think of at least two widespread laws that are regularly broken in America: Speeding laws (probably broken by the vast majority of driving adu;ts at one time or another), and marijuana prohabition laws (probably broken by tens of millions of people at the very least).

    The first immortalized by the CB radio (and Fuzzbuster) craze... talk about organized anarchy (oxymoron too) deliberately intended to thwart the 55 MPH enforcement. Even the theme of the Smokey and the Bandit movie.

    The second was immortalized by Cheech and Chong's various movies, comedy acts and antics.

    Ahh, the 1970's.

  94. Better yet... by goldfndr · · Score: 1
    The implications of this are far reaching esp for typical software where money is exchanged. To me, it's like Toyota asking me for extra money for driving my old 1979 360,000 miles when they expected me as a consumer to buy a diffrent car after only 100,000 miles.
    A better analogy is Toyota asking you for more money after they discovered that the dealer threw in "free" rare trinkets that their margins didn't cover. You, Matt, might pity Toyota, but perhaps not.
    --
    Copyrights, Patents, Trademarks: temporary loans from the Public Domain, not real property ("intellectual" or otherwise)
    1. Re:Better yet... by zakezuke · · Score: 1

      Rare trinkets, perhaps... I imagine it's possible that the combo of mold and cracking of the factory vinyl might resemble a Jackson Pollock.

      --
      There is no sanctuary. There is no sanctuary. SHUT UP! There is no shut up. There is no shut up.
  95. Actually, SCO's argument seems to be by roystgnr · · Score: 1

    that because the GPL is too "vague", the coders who published under it have effectively (albeit accidentally) released their work into the public domain. Right...

    Of course, if you suggest that perhaps SCO's deliberately publishing their own code on a public FTP server with an attached license allows people to take advantage of that license, then they'll be the first ones to swear that you can't "accidentally" give your copyrighted material a less restrictive license than you would like. They want to have their kernel cake and eat it too.

  96. Uh... we don't know civil disobedience? by Wannabe+Code+Monkey · · Score: 1

    From article:

    It's almost redundant to point out that resisting the setbacks that might result from a ruling involve civil disobedience on quite a wide scale - every sysadmin will fiind himself a potential criminal, and this is a horrifying concept for such a young nation as the United States. But maybe the US can catch a clue from the rest of us, and conclude that not only is the law an ass, but that selective civil disobedience is a walk in the park.

    What kind of crap is this? Am I completely insane or is he saying that civil disobedience is something foreign to the US, and that it's greatly followed in the UK?

    So then I suppose the person who invented civil disobedience, Henry David Thoreau, wasn't an American. I suppose he didn't write an essay titled Civil Disobedience (originally titled Resistance to Civil Government).

    And I suppose it wasn't Ghandi who used civil disobedience against the British.

    And there was never anyone named Martin Luther King in the US.

    And there were certainly no protests of a civil disobedience nature against the Vietnam War or anything.

    For a very short history and some of the ideals of civil disobedience head here.

    --
    We always knew Comcast was corrupt, here's the proof: http://tech.slashdot.org/comments.pl?sid=1909890&cid=34545432
  97. Mod parent up - but why "Insightful" by x3ro · · Score: 1

    How could anyone miss the irony? Surely "Funny" would be more appropriate :S

    --
    [ UNSIGNED NOT NULL ]
    1. Re:Mod parent up - but why "Insightful" by drinkypoo · · Score: 1

      The irony is all the more piquant because of its sincerity. The GPL is just a method for fighting the system from within.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  98. What if GPL3 is incompatible with GPL2? by goldfndr · · Score: 1

    Actually, it could be worse. (B) and (C) as you have them assume that GPL3 is compatible with GPL2. If not, there will be a lot of consultation with authors persuading them to re-release under GPL3.

    --
    Copyrights, Patents, Trademarks: temporary loans from the Public Domain, not real property ("intellectual" or otherwise)
    1. Re:What if GPL3 is incompatible with GPL2? by SagSaw · · Score: 1

      I believe the GPL2 give the licencee the right to accept any future GPL licence in place of GPL2, so unless that particular part of the GPL2 were found to be invalid, the author has no say in GPL2 vs GPL3.

      As always, though, IANAL.

      --
      Come test your mettle in the world of Alter Aeon!
  99. Leave the country; put code on freenet. by Anonymous Coward · · Score: 0

    If you are not bound to a spouse or children, leave the country.

    Even if you are, if they can accept starting a new life elsewhere, leave the country.

    I think you will find that it is surprisingly easy to disappear, that is, if as of now you are not a wanted man; that would complicate things.

    Before you go, place the code on freenet.

    Of course there would probably be legal issues involved here, and so I can not recommend or endorse your doing this, but certainly it is quite likely that if you were to attempt to do this, that you would be successful.

    In your case, you live in a country which does not provide for justice to be done for you, a country in which the more time you spend pursuing justice, the further you are from obtaining it.

    How can anyone not sympathize?

  100. Bad joke. by Anonymous Coward · · Score: 0

    Why couldn't it have been the "Heuristic Algorithm License"? Much more appropriate.

    inside 2001 pun. Apologies. Had to be done.

  101. Friend A vs. Friend B by Anonymous Coward · · Score: 0

    What would happen if someone sued a friend knowing they could win just so the rueling could be used against a deep pocketed defendant?

  102. Microsoft and GPL enforcement by jbolden · · Score: 1

    Microsofties are the only ones I've heard who don't think it'll be enforceable.

    I don't know of any time Microsoft has ever asserted that the GPL would not be enforcable. In fact many of their anti GPL claims are based on how truly enforcable the GPL is -- i.e. a company that casually uses GPL code accidentally mixes in their propietery product could end up having their product GPLed. Many have argued that claim is too strong, but regardless it isn't a claim that the GPL is not enforcable.

  103. Re:The GPL is a contract by Rich+Gibson · · Score: 3, Insightful

    There is a fundamental difference between crapola click thru agreements on web pages and software and the GPL.

    The click through agreements are attempting to impose additional restrictions on your rightful activities.

    Installing software which you have purchased is your right. The click through is attempting to impose additional restrictions on what you may do.

    The difference is that the GPL provides you with the right to redistribute someone else's property. The price exacted for that distribution is to comply with the terms of the GPL.

    This is straight contract land. Offer, acceptence, consideration. There is no confusion. No ambiguity.

    Unlike the click through license, the GPL does not come into play until you attempt to do something that would be prohibited in the abscence of the GPL (or other license): redistribute the code.

    Click throughs and lame web Terms of Service controls your use of intellectual property. The GPL controls your distribution of intellectual propery.

    Big difference.

  104. GPL is a license, not a contract. by jbn-o · · Score: 1
    There isn't anything "nebulous" about the GPL, despite Blake Stowell's FUD. And it's not a social contract; it's a contract, pure, and simple, and legally enforcable. [...]
    Now, in the case of the GPL, instead of paying with cash or a portion of the profits from distribution, you pay by agreeing to certain terms and taking certain actions.

    Eben Moglen would disagree with you in that the GNU GPL is a contract--it's a license. The licensee is given permission to copy, modify, and make derivative works and otherwise you have whatever copyright law allows for by default.

    There is not necessarily payment being made by the licensee, there need not be agreement with the terms of the license (you might find the terms attached to distributing derivative works to be too onerous, for instance). The licensee either behaves according to the terms of the GPL or they only get what copyright law allows for.

    It's this careful crafting of the GPL, leveraging only the powers that are granted to copyright holders, that makes the GPL very likely to survive any court scrutiny. It's also what makes other licenses seem relatively poorly worded (like those licenses that try to place terms on running a program, a power not granted to copyright holders).

    1. Re:GPL is a license, not a contract. by MuParadigm · · Score: 1

      You're right that it's a license, not a contract. I read Moglen's LU essay on the differences about an hour after I wrote that and thought "D'oh".

      However most of the points I make are still correct, including the use of the term licensee, since there is no implicit acceptance of the license until the software is distributed. Therefore, the analogy of "paying" for the right to distribute the GPL'd software by following its terms is still good.

      And, of course, I agree with you on the crafting of the GPL and that it will hold up in court for that reason.

  105. Re:The GPL is a contract by HiKarma · · Score: 2, Interesting

    Shrinkwrap contracts are worse, but this is still too much power to give to copyright. Now, I can see a claim if you can prove that somebody did this knowing full well what the GPL means, but even lawyers debate exactly what the GPL means.

    Consider this. I publish an item and in the licence I say, "You may not copy this unless you give me one million dollars!" And you copy it. Do you now owe me a million dollars? No, you owe me what I can extract for copyright infringment. Even though you "agreed" to the terms I put there, just like the GPL.

    Let's make it worse. Say you know about my licence but decide your use is a fair use. Example, publishing the crucial part of Gerald Ford's book where he reveals why he pardoned Nixon. Very famous case.

    Turns out the court says, "no, it's not a fair use." So now we go back to the regime you claim, which says I knew about the terms and I published it, so now I am bound by them. Can I have my million?

    Nope. Copyright law only has so much power. The only power it has is to make you pay for copyright infringment. Not to bind you to an arbitrary contract.

  106. Copyright license revocation doesn't force PD. by jbn-o · · Score: 4, Insightful
    The GPL could end up nullified in such a way that the Linux kernal became sort of a free-for-all public domain piece of code. In that case, IBM wouldn't lose, nor would they lose if the GPL as it's interpreted by most people is upheld. It could be a win-win situation for IBM.

    I think that's highly unlikely. I think it's highly unlikely the GNU GPL will be found to be somehow invalid because I think the GPL is amazingly carefully prepared and worded so it only leverages what copyright law allows. My experience is that courts generally favor the copyright holder and interpret licenses such that the copyright holder's concerns are sustained.

    But if the GPL were hypothetically invalid, I think a court would be bound to say that the would-be GPL licensee defaults to whatever copyright allows for. I can't find an example that supports the notion of a work forcibly entering the public domain because of an invalid license. I think they would be non-distributable, non-modifyable, and no derivative works would be allowed to be prepared. Copyright holders would have to relicense the works in a way that is consistent with the court's problems.

  107. Fairness is possible by Baldrson · · Score: 1

    ...due to the fact that the media has not weighed in heavily on one side or the other.

  108. What is going to be a test of the GPL by Teancum · · Score: 1

    I would have to agree, the basic philosophy of the GPL is not going to be tested in the SCO vs. IBM lawsuit. The whole thing is going to go down to license issues other than the GPL (for example, IBM's AIX and its own additions to that codebase) and a number of patent issues.

    What is going to start to raise the GPL issues is when those buying the SCO license start to discover that there are hundreds of people they also have to pay, since the GPL has been violated they have to obtain a seperate license from each and every copyright holder. In some cases, this is going to be hard to even track down, and this is where court cases can end up taking decades to resolve. Yes, decades. This is a Pandora's Box of legal worms that SCO doesn't even know what is going on, and the affected companies will have to deal will long after SCO goes belly up.

    This should also be a huge wakeup call for project maintainers for GPL'd projects, to absolutely make sure that copyright for any submitted sections of code is totally cleared. I realize that this is not quite as easy as it would appear, but it is something that must be done. The free software/open source software community must come up with industry standards to remove source code that has conflicting copyright concerns.

    For his part, Linus Torvald had plenty of reason to believe that IBM had cleared their portions of the kernel for copyright violations, and that is perhaps the #1 reason why he isn't directly named as a defendant. Other project maintainers might not be so lucky.

  109. About SUVs by Teancum · · Score: 1

    I would have to say that your argument about the SUVs going to McDonalds is a really good example of how Americans try to circumvent the law to their own advantage.

    In the 1970s and earlier in America it would have been driving the Station Wagon with the kids to the local McDonalds instead. The problem here was that environmental and fuel economy laws were enacted that forced the auto industry to try and improve fuel effency by governmental decree. The tranditional 4 door with swing back hatch Station Wagon was classified as a passenger automobile, and had to go through the much tougher restrictions and higher standards.

    Eventually, through these regulations, the Station Wagon was sent into obsolescense, partly because the auto makers couldn't meet the legal requirements for fuel economy if they kept making them.

    These legal restrictions didn't apply to trucks, which had different standards to allow for commercial transportation needs. If you look at the vehicle title for an SUV, you will see that it is classified as a truck, just like a flower delivery van. The SUV is essentially an end-run around a silly law, which also has unintended consequences. Some people really do need a bigger vehicle than a 2-door coup with a 0.5 m^3 trunk storage.

    This reminds me about another silly law (that has since been repealed) that only allowed quartz halogen lights on garbage trucks. A company was trying to sell them to consumers a few years ago, and you had to sign an agreement with the company that at some point in the future you would convert your vehicle into a garbage truck. They even had a picture of a Cadallac with a garbage compactor on the back to prove it "could" be done.

    My main experience of living somewhere other than the United States is living in South America, where they have a tradition of governments changing every generation or so. And I don't mean a new party going into power, I mean somebody trashing whatever constitution was in effect and writing a new one, and throwing out all of the old laws, releasing the prisoners only to lock up the murderers and rapists in a few weeks (if they can catch them), and total civil instability.

    This has lead to a near total distrust of the government and has some very subtle effects on everyday life as well.

    One really good example was a classic eight-sided "Stop" sign. When I was in Brazil, I saw these in many places, but people hardly ever actually stopped in front of the sign. When I asked a local resident what the purpose of them was for, they said that it was a marker for where an accident occured a few years earlier. Or at least that was the punchline of a joke regarding those signs.

    If you tried to run through a Stop sign in the United States, one of two things would happen: 1) A small town cop would throw the book at you and you would have to deal with a bunch of grief trying to get out of the ticket (at least by paying the fine...don't you even think about trying to bribe the officer) or 2) You would get side swipped by a car going across the intersection in the other direction. Even while living in Brazil I never understood how they avoided this second problem, but the drivers there always seemed to avoid the problems.

    I will say that cultural differences with the United States vs. other countries, while subtle, are significant and tough to deal with for the unprepared. I am not proud of the lawsuit happy nature of America, but this is something that unfortunately is here to stay. I considered going to law school myself as a career path, but I felt there were too many lawyers in America as it was and didn't want to add to the problem.

  110. Strong prove that sco added the code !! by Anonymous Coward · · Score: 0

    Read de article in http://www.nwfusion.com/newsletters/linux/2000/080 7linux1.html

    Before the acquisition announcement, SCO had made some Linux-related noise of its own. Earlier this year, the company announced complete compatibility between Linux and its SCO OpenServer and UnixWare operating systems, as well as Linux compatibility for its Tarantella middleware product. The company also furthered its Linux push by creating a Linux professional services group. Most recently, there were reports that SCO had even been working on a Linux distribution of its own. That project probably won't see the light of day now, but any of the planned features SCO had intended for the new Linux distribution - clustering, SMP and remote server management improvements - will probably be integrated into the next version of OpenLinux.

    For enterprise users, the most important aspect of the deal could end up being technology development. When SCO acquired the rights to Unix years ago, it charged heavy royalties for the use of the operating system, as well as for developer licenses to use and modify the Unix source code. With Caldera in control of SCO's Unix, and with its pledge to provide "open access" to its Unix and Linux technologies, the open source community may finally get an outside-in look at commercial Unix source code. Caldera's plan is to "blend" the two technologies to deliver its unified OIP system for enterprises. Could this blurring of the line that separates Linux and Unix eventually make the two systems into one powerful open-source operating system? (How would you pronounce Lunix?) We'll have to wait and see.

  111. It is point 6 in the counterclaims. by leuk_he · · Score: 1

    If you read the counterclaim of IBM


    SIXTH COUNTERCLAIM
    Breach of the GNU General Public License ...
    76. SCO has taken source code made available by IBM under the GPL, included that code in SCO's Linux products, and distributed significant portions of those products under the GPL. By so doing, SCO accepted the terms of the GPL (pursuant to GPL 5)
    .....

    77. The GPL prohibits SCO from asserting certain proprietary rights over, or attempting to restrict further distribution of any source code Distributed by SCO under the terms of the GPL.
    ....

    79. As a result of SCO's breaches of the GPL, countless developers and users of Linux, including IBM, have suffered and will continue to suffer damages and other irreparable injury. IBM is ntitled to an award of damages in an amount to be determined at trial and to an injunction prohibiting SCO from its continuing and threatened breaches of the GPL.


    Hmm, interestiong, you can not ask licensence money for GPL software, but you can sue for irreparable damage, even for software you dont own. isnt this exactly the thing SCO is doing?

    Cant they just ask licence money for the linux kernel since the GPL licence was revoked (they did misconduct according to the gpl)

    1. Re:It is point 6 in the counterclaims. by dmaxwell · · Score: 1

      Hmm, interestiong, you can not ask licensence money for GPL software, but you can sue for irreparable damage, even for software you dont own. isnt this exactly the thing SCO is doing

      Er..no. The operative phrases are: SCO has taken source code made available by IBM under the GPL and an injunction prohibiting SCO from its continuing and threatened breaches of the GPL.

      IBM is doing nothing more than asserting the rights the GPL gives them. SCO is trying to claim the work of all the kernel developers under terms they didn't authorize. It's the GPL that's giving IBM the power to countersue for copyright violation. Its supposed to work this way.

      And while you can't ask for license money, one can certainly sell GPLed code or at least develop it in the first place for a commission.

    2. Re:It is point 6 in the counterclaims. by leuk_he · · Score: 1

      IBM is doing nothing more than asserting the rights the GPL gives them.

      They sue for damage, not for copyright violation. Or is this legal talk confusing me?

    3. Re:It is point 6 in the counterclaims. by dmaxwell · · Score: 1

      IBM is asserting that SCO's copyright violation is causing them damage. They're separate but related. The GPL lays out how to comply with licensed code. The particular way that SCO is breaching the license is causing IBM damages (threatening their customers, extorting them for licenses the GPL says they can't sell, etc.). The GPL doesn't mandate the penalty for damages but it can open the door to claim them.

  112. It has nothing to do with the GPL by Vryl · · Score: 1

    If the GPL comes into it at all, it will be regarding whether or not SCO/Caldera had already published the so-called infringing code.

    The GPL itself is watertight. It rests on the solid body of copyright code, and if you don't accept the GPL, you must believe that you have no right to copy the code, as the GPL grants you rights you would not normally have.

    Indeed the GPL states: "5. You are not required to accept this License, since you have not signed it."

    Most assuredly, these cases are NOT about the GPL. They are about contract infringement, or patent law, or trade-secret protection.

    I cannot take (say) Microsoft Windows, strip out the Microsoft Copyright notice and EULA and replace it with the GPL. I will be sued nearly out of existence if I tried to distribute such a thing. This has nothing to do with the validity or otherwise of the GPL, as I never had copyright on the code in question in the first place. I cannot release it under any licence except that of Microsofts.

    At no point in any of this will the validity of the GPL come into question. The only question is that of ownership of the original copyright.

  113. UK vs US Legal system by ekatz · · Score: 1

    The author wrote: "It's almost redundant to point out that resisting the setbacks that might result from a ruling involve civil disobedience on quite a wide scale - every sysadmin will fiind himself a potential criminal, and this is a horrifying concept for such a young nation as the United States. But maybe the US can catch a clue from the rest of us, and conclude that not only is the law an ass, but that selective civil disobedience is a walk in the park. We do it every day" The problem is that there is no litigant with a vested interest in making your life miserable in the park. If SCO wins this case, they will pursue users and force the legal system to be an accomplice to their greed.

  114. They don't care about the GPL by Anonymous Coward · · Score: 0
    (Posting anonymously.)

    I have reported GPL violations to RMS, and he simply asked me to go to the program authors. Specifically, the codebase for Indiatimes Messenger contained some GPL'ed code from Everybuddy (now Ayttm). I reported this to the authors of Everybuddy, but they didn't seem to care beyond a point. After that, I've seen so many license violations, GPL and otherwise.

    Thus, in practice, the GPL is not a strong instrument. Personally, I've come to believe that either I'll go for a closed-source license for my programs, or I'll go for something like BSD.

  115. You missed the worst by Anonymous Coward · · Score: 0

    Thousands of telented people decided to take revenge. I wounder how many skilled computer crackers are working full time on the linux project who will have nothing to do.

    Time to do nothing can let free the worst evil on networks.

    Now this could be 10 times worse than any thing you can think of most virus writers are unskilled at programing so they are not great writers so if some truely skilled people write virus you will see more mult platform virus more mult attack point virus and more hell.

  116. GPL will definately not be tested! by 4eek · · Score: 1

    I have been trying to follow this case in the last few weeks so as to understand what SCO's case is all about. I don't think most readers have really bothered to find out why SCO is suing IBM and Linux companies. SCO's problem with IBM is that, SCO owns UNIX code which they have licensed to IBM. IBM improved on the original code and distributes a UNIX derivertive under the name AIX. Then came Linux and IBM started contibuting code to Linux which is GPLed. SCO claims that IBM took part of the original UNIX code (AIX code) and put it in Linux, which is GPLed. SCO recons that everything that IBM has put in Linux ought not to have been there as they were contibuting closed scource material owned by SCO!

    SCO now thinks that they can solve the problem (they can't stop GPLed stuff from being further distibuted because its out there already) by getting linux owners and companies to pay them for the code that IBM introduced into Linux. Thats all there is to it!

    The GPL will NOT be tested! It cannot be tested, it will only be a tool for SCOs case

    --
    Every problem has a better solution when you start thinking it differently than the normal way.[Steve Wozniak]
  117. Hmmm.... Have you read the claims? by Anonymous+Froward · · Score: 1

    I've always had doubts about the enforceability of the GPL in court.

    Have you read the actual IBM's claims? It seems to me that you're discussing non-existing issue. Here's a relevant part of the claim:

    IBM is entitled to an award of damages in an amount to be determined at trial and to an injunction prohibiting SCO from its continuing and threatened breaches of the GPL.

    You see, nobody (except some /. crowd) is claiming that the court should force SCO to give away all of their code (if any) under the GPL. All IBM wants is "award of damages" and "injunction". What they're saying is that IBM is one of the contributors of GPL-ed code, and SCO has redistributed all these GPL-ed codes without respecting the GPL, and thus IBM has certain right to claim as one of the copyright holders.

    As a matter of fact, I think it's the beauty of the GPL that you don't have to worry about such things as the "enforcability of the GPL in court". It doesn't matter if it is enforcable or not. The GPL is to allow something that is otherwise prohibited, and when something nasty happens, the punishment-part is taken care by the normal copyright law (or some other existing law, whatever it is).

  118. Copyright is supposed to protect music too... by turnstyle · · Score: 1
    Is there a reason to think that 'copyright' or 'social contract' should protect GPL code, but not music?

    It seems to me that the general disregard for copyright as applied to music serves only to weaken copyright as applied to GPL.

    --
    Here's what I do: Bitty Browser & Andromeda
  119. SCO, GPL and the interesting twists here by pcause · · Score: 1

    This case presents some interesting spin on copyright law and licenses of copyrighted material. There are two interesting Copyright/license issues here. I'll give my view and any comments I make should not be taken to imply that I agree with either party on the facts or merits of the case. First, let's look at the SCO side.

    SCO appears to own the copyright and intellectual property rights to the UNIX system source code. UNIX source has always only been made available under a license that protects the source code and the trade secrets contained within the code. Your license does not allow you to use any of the code in other products unless that product is subject to the same license. Sort of GNU'ish, isn't it?

    SCO says IBM took some of its source code and put it in Linux. If IBM did this, then it violated its ;incense and owes SCO whatever damages the Courts set. Further, as I understand the law, any product that contains this source must be withdrawn from the market immediately. The products can not be used until the offending code is removed and replaced. That means that folks who are running Linux systems would have to shut them down as soon as they are notified or know that they are using a product containing the code.

    I believe that a problem in replacing the code is that the people doing it have to find a way to replace it without using the knowledge they have to essentially copy the code. It may be difficult to do this, but it can be done. Further, SCO may have the right to examine any replacement code and potentially hold up release until they and possibly a Court agree that the replacement code is free of any of their source. This all takes time, and in the meantime, no LINUX use.

    The second issue relates to SCO shipping Linux under the GPL with the offending code. One of the more interesting things about this case is that the GPL is essentially an equivalent license to the UNIX license. Whereas the UNIX license asks for cash for using the code, the GPL asks for your source code additions as compensation. Both licenses rely on the same basic copyright law to protect the code that is being licensed. Both licenses are binding not just on the licensee, but also require the licensee to only license any product built using any of the code under the same terms as the original code. Pretty interesting symmetry.

    Now comes the interesting part. If IBM violated the UNIX license and placed code from UNIX in Linux, it did not have the right to agree to the license terms for the code in question. The question then becomes one similar to this: if someone steals something from your house and you wind up in possession of the item, which is disguised, without realizing it and then give it away, do you lose title to it, even if you would never have given it away if you knew?

    1. Re:SCO, GPL and the interesting twists here by Queuetue · · Score: 1
      This is an important point, so read clearly.

      SCO says IBM took some of its source code and put it in Linux.

      No. SCO claims that IBM took some code that was written by a company IBM bought and copied it into AIX. They later also copied it into Linux.

      SCO claims that, by copying it into AIX (A UNIX derivative) first, it has magically become a derivative work of UNIX itself. This is obviously a unique interpretation of "derivative work."

      SCO does not lay claim upon the code itself, though - only where and how it may be used.
  120. Re:Courts rule software can be modified/redistribu by Anonymous Coward · · Score: 0

    Does this mean Scalia, Rehnquist, and Thmoas voted to uphold the GPL? OMG!!

  121. Good, and here's why by Rogerborg · · Score: 2, Insightful

    Because GPL licensed code is habitually ripped off by commercial companies, through evil or plain old ignorance. I've seen it both ways, and I've seen it at every company I've worked at.

    You, dear reader, might not have seen it, but that doesn't mean that I haven't, or that it doesn't happen.

    GPL needs a huge public case to bring it to the attention of both developers and pointy haired idiots. It must be made clear that the GPL can't be retrospectively revoked (that it doesn't specify "irrevocable and in perpetuity" beggars belief), but that once violated, you are commiting copyright violation (or "theft" in newspeak) every time you duplicate. This needs to be made clear in no uncertain terms, with a fat headline grabbing fine, not just another quiet non-disclosed settlement by that pussweed Moglen.

    The GPL is so badly understood even by people that use and comment on it every day (yes, you, dear reader), that this is a long overdue public test of it. If it ain't broke, let's say so. If it's broke, let's find that out and fix it.

    --
    If you were blocking sigs, you wouldn't have to read this.
  122. It had to come sometime -- and this is as good a.. by Monofilament · · Score: 1

    time as ever.

    Reasons why timing is good:
    1. IBM a mega-corporation is using it in their defense case (among other things they have). But they still reference it as one of the key's to their case. Thus they have some belief in it, whatever that might be.

    2. If it is never tested in a real court of Law.. then well its worthless. There is no precedent for it and if people realize nobody wants to use it in court, then its just as worthless as all those EULA's everybody just blindly clicks through.

    So here's hoping the make the good fight and the GPL comes out on top.

    But you can't back down when a big fight comes just because you have a fear of the system striking it down. If you never come to the table THEY'VE ALREADY WON.

    thats all

    --


    Who makes you Sig?
  123. The Andrew Orlowski agenda and the GPL by theolein · · Score: 1

    Note: This is not a positive note about him or his posts, so if you love the guy please forgive me.

    I don't know whether the GPL will be properly tested under the current circumstances, as it seems that the US legal system is one where your chances of winning are dependant on so many factors that have no real bearing on the core case, such as lawyer quality and quantity, the attitude of the judge and their mood and a jury who is more often than not in no way qualified to give opinion on highly technical matters such as these.

    I do however think Andrew Orlowski is an opinionated man with a personal view of what is right and wrong in this world. There's nothing wrong with that but I noticed quite a while ago that his personal opinion was anything but positive towards things that didn't fit in his opinion and he never seems to even attempt to qualify his statements. His op-ed pieces often take the position that HE is right. Point.

    I first took notice of him when he was the Reg's resident Mac writer, and he never failed to write scathing attacks on everything Mac and Apple related, be it horrific reviews of the ibook when it came out or sarcastic criticism of Steve Jobs business plan. While it can be refreshing to not have someone who is a mac zealot reviewing Apple stuff, I would point out that both the ibook and Apple's business plans have been success stories in a generaly bleak IT sector. His comments on OSX would have made you think it was 1996 again and Apple was going to die "any day now".

    This piece on the marvels of people in the UK ignoring the law as opposed to people in the states being a bunch of sheep is as ridiculous. He has a point in that traditionally in old world countries the power of the individual has been minimal leading to individuals ignoring it, but he so conveniently ignores the fact that the GPL needs to be seen as legally legitimate, no matter where it is implemented, for it to be taken seriously by businesses.

    And that applies to the UK, the US and just about anywhere else where businesses enforce their licences through the legal system.

  124. GPL in court by ajs318 · · Score: 3, Insightful
    I think the law is on the side of IBM and the GPL. Look at the facts.

    The Law of the Land:
    • Copyright law says basically that you need permission from the author to make copies of software and the like, except in certain limited circumstances which may vary from one jurisdiction to another.
    • If the law of the land says that you have a right to do something, then nothing and nobody can take that right away from you. Ever. Even if you sign a piece of paper saying you have given up that right, in the eyes of the law you still have that right. This is what that catch-all phrase "Your statutory rights are not affected" means.
    • Civil law gives you remedies, as a copyright holder, if someone performs unauthorised acts in relation to your work. The courts may decide on the nature and magnitude of such remedies. In general, whistling a tune in the street is likely to attract substantially smaller damages than broadcasting an unreleased movie.
    The GPL:
    • The GPL gives you the necessary permission to make and distribute copies of the work, in addition to any statutory rights you may have, if and only if you comply with certain restrictions. For instance, if you modify the work, you must not restrict distribution of your modified version, save that you may keep it entirely to yourself.
    • If you fail to comply with the conditions of the GPL, then your special permission to copy, modify and distribute is withdrawn. Copyright law is what bars you from making copies, not the GPL.
    There's nothing complicated in there; it is all quite straightforward. SCO has released code under the GPL, thereby granting a licence to others to copy it. That licence cannot now be withdrawn.

    I've said it before and I'll say it again. When you want to do something critical with Free Software - such as running a system where people will get hurt or killed if it fails - reading the source code is due diligence. Don't want to read it yourself? Don't know how and can't be bothered to learn? Then pay someone to read it for you. That's the way people make money out of Free Software. What SCO was doing was critical in a different way, because SCO was trying to keep proprietary code separate from GPL code. Nobody's life was in danger, but SCO mucked up anyway by not checking for things they didn't want in the code before releasing it.
    --
    Je fume. Tu fumes. Nous fûmes!
    1. Re:GPL in court by rssrss · · Score: 1

      "If the law of the land says that you have a right to do something, then nothing and nobody can take that right away from you. Ever. Even if you sign a piece of paper saying you have given up that right, in the eyes of the law you still have that right. This is what that catch-all phrase "Your statutory rights are not affected" means."

      IAAL and I can not make any sense out of this statement. Any right may be waived.

      The most sacrosanct of our rights under the United States Constitution, such as the requirement for a search warrant may be waived. Waivers of constitutional rights must be "knowing," "intentional," and "voluntary." But they are not invalid.

      Waivers of other statutory rights may or may not be valid depending on time, circumstance, and procedure. There is no law that makes all waivers invalid. Furthermore I do not believe that there is anything in the copyright law (17 USC) that limits the ability of any copyright owner to waive rights under that law.

      Bottom line. A copyright owner may waive copyrights by any action (or omission) that is sufficent to waive any ordinary property right, including written instrument, oral contract or conduct.

      --
      In the land of the blind, the one-eyed man is king.
    2. Re:GPL in court by ajs318 · · Score: 1

      Under British law, certain rights cannot be waived and consent cannot be given for certain actions. Look at the Unfair Contract Terms Act 1977. This is why we have that phrase on purchase guarantees and various contracts: to cover one party's behind. If they forgot to mention something, then it might appear that they were trying to limit your rights. That would come under the general heading of interfering with the process of law, and is punishable as seriously as it sounds like it might be.

      Of course, there might be different rules in force in less civilised nations :-)

      --
      Je fume. Tu fumes. Nous fûmes!
  125. A loss for GPL would by praedor · · Score: 1

    also be a loss for propriatory/closed source licenses too would it not? A loss in court couldn't simply be a loss for GPL and GPL alone, it would have to have broader implications.


    Click-thru licenses also haven't been tested in court and, as I understand the situation, the software powers that be are quite happy about this as a court challenge may well invalidate (and rightly so) these licenses.


    What would the wider implications be beyond GPL (for closed source) if the GPL loses in court?

    --
    In Bushworld, they struggle to keep church and state separate in Iraq as they increasingly merge the two in America.
  126. The GPL is pointless... by CrimsonTemplar · · Score: 1

    ...if it doesn't have a leg to stand on. I think that either way this case goes it will, in the long run, be beneficial to the OSS movement. I also think that IBM and the GPL will win out if this case goes to trial. Once the GPL is upheld in a court of law I have a feeling Linux and OSS will gain a great deal of credibility and more people will be open to using it.

  127. Calling Richard Stallman to stand as witness by ngyahloon · · Score: 1

    Since the idea of GPL was conceived by Richard Stallman, will he be called to stand as a witness to explain some of the notions presented in the GPL? It'll be wild if he does:)

    --
    Carpe Diem: Seize The Day!
  128. Thoughts in the GPL as Law... by GearheadX · · Score: 1

    The GPL has to be tested.

    It's a simple fact.

    A law that's on the books, but never applied isn't a real law, it's just words on a page. You have to actually get the words out, hold them up to the person standing against them, and impliment them.

  129. I'm not worried about a Judge... by shadoelord · · Score: 1
    A judge atleast has an education.

    If you've read the IBM filing, there is a line:
    "JURY TRIAL DEMANDED"

    A jury doesn't nessisarly represent the more intellegent in society.

    Jim Bob Bumble-Fsck with a GED and a drunken slur had better not be on the juror's list.

    --
    this is my sig, there are many like it, but this one is mine.
  130. Microsoft and Open Source/GPL by DrDebug · · Score: 1

    Somewhere, somehow, Microsoft must be behind SCO. Idealisticly for sure. Financially? Maybe. After all, you have to have some PRETTY DEEP POCKETS to butt heads with the IBM legal team. And that costs MONEY. Does SCO have it? I doubt it. But Microsoft has money out the wahzoo.

    The best thing that could happen for Microsoft is if SCO wins. But I am thinking that they would settle for a long, protracted battle (measured in years) so that they could (continue to) spread FUD. Perhaps they can even get an injunction against the GPL until a ruling is made (again, years later).

    The worst that could happen to Microsoft is if the judge squishes SCO like a bug because they filed a frivolous lawsuit. But that is not likely to happen.

    Remember, Microsoft isn't just an 800 lb financial gorilla, getting what it wants; it also has a solid litigation team. Bill Gate's dad was an attorney, and I am sure he taught Bill a few lessons there.

    So, overall, I smell Microsoft in this picture somewhere. A conspiracy, perhaps?

  131. Absolutely... by BlabberMouth · · Score: 1

    A ruling that finds the GPL or its parts unenforceable will also tell us why those parts are unenforceable and provide a guideline for revision. I would definitely find it ideologically appalling if the courts declined to enforce the GPL while consistently enforcing much more onerous and apparently legally tenuous shrink wrap licenses. The windows XP license is ok but the GPL isn't?

  132. Copyright Registration by economy · · Score: 1

    Are you sure copyright needs to be registered for imposition of statutory damages? You might be right, but I don't recall that being the key. I thought the key was being able to establish intent to infringe, willful and wanton, stuff like that. I don't even know where my IP Nutshell is anymore...