Slashdot Mirror


Culture Clash: SCO, OpenLinux, Linus And The GPL

hobsonchoice writes "SCO has issued a letter saying SCO Linux customers won't be sued. The same does not seem to apply if using a non-SCO distribution such as RedHat." LightSail points to the SCO letter itself, and raises an interesting point: "If they approve the use of 'their' IP in Linux in a single kernel, then the GPL holds that IP SCO allows to be used by a select few must be freely released to any and all. It appears that all Linux users everywhere were just given a license to continued use of Linux even if SCO would win their suit with IBM." And Haikuu writes "eWeek recently posted an interview conducted by e-mail exchange with Linus Torvalds regarding his recent move to the OSDL and the SCO suit."

710 comments

  1. SCO Letter by 56 · · Score: 4, Insightful

    They said they won't sue people using SCO Linux, not that it was ok with them for the code to be used. There's a difference. If I jaywalk and don't get charged, it's not that jaywalking is not illegal, it's that the law was not enforced. Big difference.

    1. Re:SCO Letter by BitterOak · · Score: 5, Interesting
      But if SCO sold them Linux, I don't see how they could sue anyway. Isn't selling someone something which implements your IP an implicit grant of permission to use it? If I buy the new Harry Potter book, for instance, can't I assume I have a license to read it?

      --
      If I can be modded down for being a troll, can I be modded up for being an orc, or a balrog?
    2. Re:SCO Letter by Cyborg · · Score: 3, Informative

      Maybe you should read the article though, that's not what it says... It says SCO Linux customers "are not liable", as in they aren't breaking the law. They're crossing the street on a crosswalk in a green light, not jaywalking. It seems to say more to me that they've got that license legally, not that they're breaking the law and just wont get sued for it.

      "SCO Group has assured its Linux customers that any company that's paying for Linux software and services from SCO Group is already paying for SCO's intellectual property."

      Who's got the skinny directly from SCO's website that the article mentions?

      --
      --Me
    3. Re:SCO Letter by pyrrho · · Score: 2, Insightful

      no, when SCO copied and distributed Linus' IP to them it did so under the GPL, GPLing it's own IP. If they want to say, "oops, didn't mean to do that" then they could recall their distro. To allow their distro puts them in violation of the GPL.

      They must be sued by key OSS copyright holders.

      --

      -pyrrho

    4. Re:SCO Letter by wfrp01 · · Score: 1

      They said they won't sue people using SCO Linux, not that it was ok with them for the code to be used.

      Which perhaps points to the real reason for this lawsuit. They want to challenge the GPL. Why not? They've got nothing to lose. Who would be surprised to see this pathetic group of vainglorious losers butter themselves up for yet another opportunity to crap all over everyone, including themselves? If they win, they'll be the only linux vendor with a legal drop in replacement for all the suddenly invalidated installations. Sure. And I'm an elf.

      Their argument will go something like "the GPL prevents us from protecting our IP, therefore the GPL is an invalid license" blah blah blah.

      --

      --Lawrence Lessig for Congress!
    5. Re:SCO Letter by Anonymous Coward · · Score: 0

      Once SCO is brutally defeated, I believe people will start crawling out of the wodwork with defamation lawsuits. I am surprised Darl McBride would put his future, and the futures of his wife and children at risk in such a silly adventure. Surely he must understand that they will be destroyed.

    6. Re:SCO Letter by Trogre · · Score: 4, Informative

      They said they won't sue people using SCO Linux, not that it was ok with them for the code to be used. There's a difference. If I jaywalk and don't get charged, it's not that jaywalking is not illegal, it's that the law was not enforced. Big difference.

      It would be, except that they're still distributing said product.

      --
      "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
    7. Re:SCO Letter by Anonymous Coward · · Score: 1, Insightful
      You're the only one here who gets it.

      SCO is distributing GPL code in violation of the GPL. They (a) are distributing GPL code in their distro and (b) are limiting who can use it (i.e., only their for-pay customers can use it). Clear violation. The violation doesn't entitle the rest of the world to use their distro. It merely makes SCO's distribution illegal and a violation of the GPL authors' copyrights. They (GPL authors) need to sue SCO.

    8. Re:SCO Letter by Anonymous Coward · · Score: 0

      "SCO Group has assured its Linux customers that any company that's paying for Linux software and services from SCO Group is already paying for SCO's intellectual property."

      Ok, if SCO customers got licensed the code under GPL, they have all the rights that GPL provides. Meaning, they have the right to distribute the code they were given. Anything else is harm (i would consider a change of licensing terms as harmed). I wish a SCO licensee would put up a web or ftp site where code from purchased SCO linux is made available.

      All legit and within their rights, especially after SCO issued this assurance letter to them.

    9. Re:SCO Letter by sleeper0 · · Score: 3, Insightful

      did anyone read the linux interview? I haven't read every SCO article that has come out but i found it surprising to read that linus was saying that RCU patents and copyrights are held by IBM (formerly sequent) considering it is the RCU code that they have been showing.

      Does anyone have a link to analysis of the RCU patents and copyrights? Up to this point everything i have seen has been very broad discussion about why people doubted SCO's claim was correct, but this seems like a smoking gun... SCO shows rcu code and rcu ip is shown to belong to sequent and bought by ibm? Would push me into placing a short position.

    10. Re:SCO Letter by Citizen+of+Earth · · Score: 1

      They want to challenge the GPL. Why not? They've got nothing to lose.

      I say that the real scam here is a pump-and-dump of thier stock, so if papers are filed tomorrow of 1,000 developers suing SCO for copyright infringement on all parts of the Linux kernel that they are not claiming ownership of, their stock goes through the floor. Encouraging counter suits is not a good strategy for them. They must keep their share price high until the owners unload their own stock. This means making bold and brash statements on a daily basis until then.

      If they win, they'll be the only linux vendor with a legal drop in replacement for all the suddenly invalidated installations. Sure.

      If they defeat the GPL, then they will also be defeating copyright law, so it won't matter who has copies of what; everything will be free!

    11. Re:SCO Letter by Anonymous Coward · · Score: 0

      I have read most of the articles on this story sin fin. As it's been said many times before, SCO believes all UNIX derivative works are their property, so the fact that IBM got RCU from Sequent doesn't matter. SCO is claiming to own everything, whereas Linus, IBM and pretty much the rest of the free world, understand that IBM holds the copyrights, not SCO's bitch ass.

    12. Re:SCO Letter by Stonent1 · · Score: 1

      But if SCO sold them Linux, I don't see how they could sue anyway. Isn't selling someone something which implements your IP an implicit grant of permission to use it? If I buy the new Harry Potter book, for instance, can't I assume I have a license to read it?

      Well I think that the fact that SCO is "selling" GPL'd linux WITH THEIR CODE IN IT, is an implicitly saying the code is GPL'd! If their code was not GPL'd then they can't call it Linux, it's Linux+SCO SystemV "enhancements". By sco knowingly distributing it, they have just lost their reason to claim that someone has pirated their code... That's like not proof reading a book and after you have sold it, you find out that some how someone slipped your home phone number into the book. Too late now!

    13. Re:SCO Letter by Surak · · Score: 4, Interesting

      Well, SCO has specifically referred to Unix patents.

      And according to the terms of the GNU General Public License, if you can't satisfy patent laws AND the terms of the GPL simulataneously you have no right to use the code at all.

      Does this mean that SCO, by telling their users it's alright, is violating GPL? I'm not a lawyer, but I know a bit about IP law. But this whole mess is confusing even me, especially since SCO keeps saying conflicting things.

      My head hurts now. I wonder if I can sue SCO for medical bills and psychological trauma? :)

    14. Re:SCO Letter by FreeMars · · Score: 1

      Their argument will go something like "the GPL prevents us from protecting our IP, therefore the GPL is an invalid license" blah blah blah.

      Fine. Then they can
      - negotiate a license with every author of each package they want to include, and
      - rewrite the functionality of each package they don't want to license.

      Even if they own the IP they can't use your code without your permission.

      --
      Email: slashdot3@FreeMars.org (Address will be abandoned when it gets spam.)
    15. Re:SCO Letter by Stonent1 · · Score: 1

      pump-and-dump of thier stock

      Levitz, Enron, WorldCom, Emclone (sp), now SCO. Note to SCO: I think the SEC should (to quote Axle Foley) "Crawl up your ass with a microscope."

    16. Re:SCO Letter by SydShamino · · Score: 1

      Hypothetical situation:

      Linus goes to SCO's site, tonight, and downloads Linux source. It is still freely available there after all, released by SCO under the GPL even though they claim they have IP in it.

      Tomorrow, Linus creates a new Linux trunk based on the "SCO" kernal, and starts developing Linux from there.

      Would that not absolve Linux of any IP claims, even if SCO did win something in court? Sure, they claim to have IP, but they knowingly gave it away under an open source license, months after they "knew" of the IP.

      --
      It doesn't hurt to be nice.
    17. Re:SCO Letter by Anonymous Coward · · Score: 1, Informative

      Hmmm -- if Canopy starts dumping their stock, the markets going to percieve the case is full of hot air, and the stock will collapse back down to .50 a share.

      These guys are far worse than pump-n-dumpers. They honestly believe they are going to get commercial licences from every linux install. The daily FUD is to scare IT managers into believing them.

    18. Re:SCO Letter by wfrp01 · · Score: 1

      If they defeat the GPL, then they will also be defeating copyright law, so it won't matter who has copies of what; everything will be free!

      I'd like to think so. But I can imagine otherwise. The argument could go something like "just as your right to free speech doesn't give you the right to shout 'fire' in a theatre, neither does copyright allow you to create licenses which are 'viral' yada yada." Which would be a bunch of horse pucky, but nevertheless certain people never fail to let one bad turn beget another.

      Plus if you can get a GPL challenge into the court room, you could subpoena Richard Stallman. Wouldn't that be fun? You could demonstrate the perversion of the GPL by making a public spectacle of its author! Sick, but how could anyone who reads /. be surprised? We see this kind of behaviour every day.

      --

      --Lawrence Lessig for Congress!
    19. Re:SCO Letter by ErikZ · · Score: 1, Insightful


      Isn't selling someone your product and then suing them for using it incredibly stupid?

      --
      Democrats or Republicans. They are both taking us to the same place and they are not afraid of us anymore.
    20. Re:SCO Letter by sleeper0 · · Score: 4, Informative

      Since no one came up with any better research i thought i would share this, which was the only substantial discussion i was able to find of RCU patent & copyright history:

      http://lwn.net/Articles/36164/

    21. Re:SCO Letter by Anonymous Coward · · Score: 0

      Some discussion (and a whole lot of crap) here

    22. Re:SCO Letter by wfrp01 · · Score: 1

      Even if they own the IP they can't use your code without your permission.

      Sure. But say for the sake of argument that the GPL were invalidated. What would people who had GPL'd code do? They'd basically either (1) keep it to themselves or (2) release it under a BSD style license. Any BSD code could be used by a commercial entity as they saw fit.

      I realize I don't have a fully fleshed out theory here, but as far as what SCO is up to, I don't think anyone does. Maybe they don't even know themselves.

      But in any case, it won't surprise me in the slightest, now that the OSS/Free Software movement has gotten so large, to see non-techie folks, like lawyers, repeat a lot of the same arguments we've been having for years, but in a different forum. Like "BSD is 'more free'" vs. "You're just an opportunist! Use the GPL!" vs. "No way you hippie communist!" etc. In the courts. Tomorrow at 11:00.

      If slick lawyers like Boies can continue duping the dunderheads at SCO into paying his legal fees, he'll keep concocting lawsuits. It's his job.

      --

      --Lawrence Lessig for Congress!
    23. Re:SCO Letter by L1ttl3p1gg3 · · Score: 1

      It would be, except that they're still distributing said product.

      But there is no kernel - with there distrobution... They have the source for everything - and a couple of kernel "addons" but no kernel source...I Wonder if the kernel source that is missing has there ever special code in it? If it did/does, could be worth doing a diff on the code from kernel.org with what ever there's are - and seeing what the difference really is (if anything)...

      --
      I've pissed someone off somewhere...
    24. Re:SCO Letter by GRW · · Score: 1

      >It would be, except that they're still distributing said product. The Linux kernel doesn't seem to be currently in the list of packages on that server.

    25. Re:SCO Letter by sholden · · Score: 2, Interesting

      There isn't in the location choosen for reasons I can't comprehend by the OP.

      However, over here:ftp://ftp.sco.com/pub/scolinux/server/4.0/upd ates/SRPMS are four files that claim to be "kernel-source" but strangely contain the string "nosrc" as well.

      This one in particular: kernel-source-2.4.19.SuSE-82.nosrc.rpm contains a file called patches.i386.tar.bz2 which in turn contains a file called 8975_NUMAQ.

      That seems to be a kernel patch dealing with something related to NUMA, and contains GPL references.

      Isn't NUMA one of the things, SCO has specifically mentioned as being part of the IP at issue?

    26. Re:SCO Letter by MrGrendel · · Score: 5, Informative
      They seem to have removed all of the kernels, at least in every place I looked. But they aren't nearly as clever as they think they are. From the file kernel-source-2.4.19.SuSE-106.nosrc.rpm (notice that they removed the source from the source rpm -- I confirmed that). But there are quite a few patches left. Inside patches.tar.bz is the file 020_rcu-poll. To quote...
      + * Read-Copy Update mechanism for mutual exclusion
      + *
      + * This program is free software; you can redistribute it and/or modify
      + * it under the terms of the GNU General Public License as published by
      and a little farther down is
      + * Copyright (c) International Business Machines Corp., 2001
      + *
      + * Author: Dipankar Sarma <dipankar@in.ibm.com>
      + *
      + * Based on the original work by Paul McKenney <paul.mckenney@us.ibm.com>
      + * and inputs from Andrea Arcangeli, Rusty Russell, Andi Kleen etc.

      What have you got to say for yourselves now, dumbasses? This may not contain the exact stuff that they're all worked up about (although it sounds like they want to claim RCU entirely), but it is a patch for source that does contain the offending material and therefore a derivative work.

    27. Re:SCO Letter by Anonymous Coward · · Score: 1, Interesting

      Call me crazy, but I've yet to hear this argument:

      Suppose SCO wins (ducks).

      Okay really -- suppose SCO wins and their claims are correct: Some of SCO's IP is in Linux. Big Friggin' Deal!!! That doesn't give them the right to start charging everyone for it. Correct me if I'm wrong, but MOST of Linux has been written by many, many people NOT employed by SCO. Those people surely could have a say in who uses THEIR hard work (IP) and I'm sure that those people are not too keen on SCO hijacking their tens (hundreds?, millions?) of thousands of hours of development.

      To wrap up...
      1 - SCO wins.
      2 - SCO decides to sell Linux, claiming that it's theirs.
      3 - SCO distributes their version of Linux which GUESS WHAT???, contains a WHOLE BUNCH of GPL'd code.
      4 - Hence, to distribute Linux (even AFTER a potential victory in court) straps SCO into accepting the GPL. There is really no way around it... they can't steal ALL of Linux because SOME of it belongs to them... The majority of it belongs to the thousands of people that wrote it, and these people, I'm sure, would not be very pleased to have their hard work stolen.

      (5) - Alternatively, they might just _try_ to kill Linux and sell whatever half-baked version of *nix they've got... I say _try_ because I don't believe that IP laws, piracy laws, etc. can stop the future of Linux. I know I'll still use it, even if I've got to download it from overseas and break all kinds of state and federal laws to do it.

      okay, i'm done ranting... off to get what little sleep I can tonight.

      In Peace.

    28. Re:SCO Letter by kwan3217 · · Score: 1

      Hmmm. I could not find anything looking like either an iso or a kernel rpm at this link. Maybe they already pulled it?

      --
      Lots of technical and environmental problems are solved by the application of vast amounts of nuclear power
    29. Re:SCO Letter by ottothecow · · Score: 1
      dont they have to provide the source if they EVER distributed it...so couldnt you call them up and say you want to see the source for [insert file name you want but they dont give]

      if they say no, they get slapped with a gpl lawsuit because they wont give the source

      --
      Bottles.
    30. Re:SCO Letter by Anonymous Coward · · Score: 0

      I am about to go cook a 'Red Baron's" single serving pizza in my toaster oven. After I consume said single serving pizza, I am going to call my prom queen girl friend (yes, she won it) and then fuck her poutie Puerta Rican mouth. MMMMMMMmmm MMMMMMMMMMMMMMMMMM!!!!!!!!!!!!!!!

    31. Re:SCO Letter by Crosis · · Score: 1
      If I buy the new Harry Potter book, for instance, can't I assume I have a license to read it?
      Not in New Zealand
    32. Re:SCO Letter by CCA · · Score: 3, Insightful

      What if I buy the new Harry Potter book, decide I have too much work to read it, sell it to my roommate, and later find out that someone stole my code, slapped a GPL on it, and printed it in the middle of the book? Have I just lost my intellectual property? Clearly I haven't - as SCO contends, you can't "accidentally" GPL your code. Couldn't I sue the people who stole it? Couldn't I be a nice friend and not sue the person I sold the book to? Which brings up another point. Have you read a lease? I don't know if this is common, but mine says the landlord's failure to enforce the terms of the lease on any other tenant does not, in any way, limit his rights to enforce them with me. I'm pretty sure thats how it works in civil cases. I can arbitrarily bring up civil cases, and ignore other cases that I might win, for no good reason. Of course, this isn't to say SCO has a good legal case. I have no idea if code was actually stolen or not. However, if code was stolen, its not as simple as "they aren't sueing X, which gives Y immunity".

    33. Re:SCO Letter by innocent_white_lamb · · Score: 1

      dont they have to provide the source if they EVER distributed it...so couldnt you call them up and say you want to see the source for [insert file name you want but they dont give]

      If you bought or otherwise "obtained" the package in question from SCO then yes.

      if they say no, they get slapped with a gpl lawsuit because they wont give the source

      If you're just Joe Schmoe they don't have to give you anything.

      --
      If you're a zombie and you know it, bite your friend!
    34. Re:SCO Letter by innocent_white_lamb · · Score: 1

      Linus goes to SCO's site, tonight, and downloads Linux source.

      Apparently the kernel source is no longer available on their site.

      they claim to have IP, but they knowingly gave it away under an open source license, months after they "knew" of the IP.

      Looks like they have just now stopped.

      --
      If you're a zombie and you know it, bite your friend!
    35. Re:SCO Letter by tanveer1979 · · Score: 1
      But if SCO sold them Linux, I don't see how they could sue anyway.

      A bit of a contradiction here. If SCO sells them Linux, and it is under GPL, how can they sue anybody becoz they GPL'd their IP. It seems that there is so much confusion in this case that in the end it wont matter who is right or who is wrong, all that will matter that who has better lawyers. I guess IBM is pretty strong on that front.

      However this battle will drag real long and in the end the user will be at loss and also its the SCO shareholder who stands to lose. The SCO share has really been jumping quite a bit and it is only a matter of time before the SEC jumps in. Welcome to 2003: The battle of the 'nixes
      --
      My Aurora : http://www.youtube.com/watch?v=o91ZsGwJYyg
      FB : https://www.facebook.com/TanveersPhotography
    36. Re:SCO Letter by MrGrendel · · Score: 3, Insightful
      Invalidating the GPL won't really help SCO at all. If the GPL becomes invalid, then everything reverts to standard copyright law, which means that know one has a legal right to distribute Linux at all, including SCO. They wouldn't be able to collect much licensing revenue because most commercial users would just migrate to *BSD. Suing over BSD would be much more difficult for them because their predecessors already settled a lawsuit involving that code (and essentially lost).

      I don't see any reason why the GPL would be invalidated, however. The GPL grants people rights that they do not have under normal copyright law, unlike most licenses that seek to remove rights. There are rules that the distributors have to follow in order to be granted the GPL rights, but it's hard to see how that could possibly be a problem. If it was invalidated, the court would be saying that the GPL grants people additional rights that are too restrictive. That's not logically coherent. And the GPL doesn't prevent anyone from asserting IP rights. By agreeing to follow the terms of the GPL, they are agreeing to not assert additional IP rights over that code. The agreement is the important part. Nobody is forced to distribute GPL'd code, it is done by choice. Any loss of IP rights on the part of SCO is because they chose to give them up.

    37. Re:SCO Letter by mcrbids · · Score: 1

      But if SCO sold them Linux, I don't see how they could sue anyway. Isn't selling someone something which implements your IP an implicit grant of permission to use it?

      Yes, and that's the point. The license was GPL and so your permission to use it under the attached GPL license means you have the right to grant others the right to use said IP.

      Valid or not, I've seen this point made in a number of forms.

      --
      I have no problem with your religion until you decide it's reason to deprive others of the truth.
    38. Re:SCO Letter by a_n_d_e_r_s · · Score: 1

      We're talking about SCO here !

      --
      Just saying it like it are.
    39. Re:SCO Letter by ocelotbob · · Score: 5, Informative

      The source is still on the server, only its location is obfuscated a bit. It seems to me that the move to remove the kernel is just an issue of trying to appear that they've been irreparably damaged. I'd offer to diff from the mainstream kernel myself, but I'm on my laptop which has a tiny, tiny amount of storage space.

      --

      Marxism is the opiate of dumbasses

    40. Re:SCO Letter by boots@work · · Score: 3, Insightful

      If you didn't know your code was in there while you were selling copies of the book, perhaps you'd have a claim to ask for all the copies back. Perhaps.

      But if you kept selling the book, in the full knowledge of what it contained, can you then renege on your contract with the purchasers and demand the books back? Hell no.

      This is the situation SCO are now in. Even after their initial allegations against IBM, they continued both selling copies of Linux, and offering it for free download from their web site.

      Clearly they were entering into a contract with those people, with the knowledge that Linux contains RCU, SMP, and whatever else. That contract is the GPL. SCO has no grounds to revoke their customers contracts.

      *If* (and this seems awfully unlikely) IBM breached their contract with SCO, then SCO can sue IBM. That doesn't make a whit of difference to people who got a GPL licence to the kernel from SCO.

    41. Re:SCO Letter by Eneff · · Score: 2, Insightful

      connect the dots...

      4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License.

      6. You may not impose any further
      restrictions on the recipients' exercise of the rights granted herein.

      7. (The biggie) If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you`may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.

      Ergo, if you knowingly redistribute, you must allow others to redistribute. It's been well-established that they still have the binaries up on their servers. There's your authorization to use their source.

    42. Re:SCO Letter by Rogerborg · · Score: 1

      How about you read the license rather than expecting to be spoon fed the answer?

      That said, I need the practice. Open wide! Here comes the choo choo train!

      3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:

      a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

      b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

      c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)

      Now, would you like me to wipe your arse for you?

      --
      If you were blocking sigs, you wouldn't have to read this.
    43. Re:SCO Letter by Qeantk · · Score: 1

      Mod parent up, please.

    44. Re:SCO Letter by Rogerborg · · Score: 2, Informative

      >according to the terms of the GNU General Public License, if you can't satisfy patent laws AND the terms of the GPL simulataneously you have no right to use the code at all.

      s/use/distribute/

      YA definitely NAL

      --
      If you were blocking sigs, you wouldn't have to read this.
    45. Re:SCO Letter by stiggle · · Score: 1

      But IBM is a customer of SCO as they use a license of their unix for Aix.

      Does that mean IBM is now free from legal action?

      hehehehehe

    46. Re:SCO Letter by Arioch+of+Chaos · · Score: 1
      If I buy the new Harry Potter book, for instance, can't I assume I have a license to read it?

      Not if it's an e-book ;-)

      --
      IAAAL - I am actually a lawyer ;-)
    47. Re:SCO Letter by minkwe · · Score: 1

      The SCO letter claims that buying Linux from them means buying a license to use their intellectual property. If one of those who bought Linux from SCO modified it and distributed it according to the license would they be sued? Is SCO now allowing them to make modifications and do what they want with those modifications (according to the GPL). If so then they have Licensed they IP under the GPL. If not then they are violating the GPL because of all the other code that they distributed with it that does not belong to them.

      They keep shooting themselves in the foot every now and then. Very soon they'll have no toes left.

      --
      "Fighting terrorists with millitary might is like killing a mosquitor on your Dad's forehead with a rifle."
    48. Re:SCO Letter by mpe · · Score: 1

      But if SCO sold them Linux, I don't see how they could sue anyway. Isn't selling someone something which implements your IP an implicit grant of permission to use it?

      With software apparently not...

      If I buy the new Harry Potter book, for instance, can't I assume I have a license to read it?

      A character introduced in HP&OoP would most likely claim that you don't :)

    49. Re:SCO Letter by Znork · · Score: 2, Insightful

      I dont think you can get anyone elses license terminated by getting your own license declared invalid. Even if the GPL became invalid for SCO, only their license would revert to copyright, which means everyone else could go on doing what they want.

      So, a successful challange against the GPL would just mean that anyone who wanted could go to court for the ability to lose their right to distribute GPL software. Great. They'd obtain the legal right to shoot themselves in the foot.

    50. Re:SCO Letter by mpe · · Score: 1

      The SCO letter claims that buying Linux from them means buying a license to use their intellectual property. If one of those who bought Linux from SCO modified it and distributed it according to the license would they be sued? Is SCO now allowing them to make modifications and do what they want with those modifications (according to the GPL). If so then they have Licensed they IP under the GPL. If not then they are violating the GPL because of all the other code that they distributed with it that does not belong to them.

      Which is basically copyright infringment, known as "software piracy". An interesting side effect of the GPL is that anyone who happens to recieve a pirated copy is perfectly in the clear so long as they themselves comply with the GPL.

    51. Re:SCO Letter by Surak · · Score: 4, Insightful

      Yeah, but in this case one of the people slapping the GPL the code in the middle of the Harry Potter book is Caldera, which today is none other than SCO itself.

      You can't go around claiming a bunch of people illegally stole your work when you're part of those group of people. It's called failure to mitigate your own damages.

      Same with your landlord. Your landlord's failure to enforce thet terms of the lease on others doesn't limit his rights to enforce them on you. But if you're lease terms say that you can't knock down walls in your apartment, and your landlord is swinging the sledgehammer with you, your landlord just lost his right to enforce that particular lease term on you.

      Now my point is this: the reason they can't sue X and grant immunity to Y -- because by distributing the code, they are, as specifically stated in the GPL since NOTHING ELSE gives them the right to distribute the code, agreeing to the terms of the GPL. Which means if their code is in there, by distributing to Y and holding them harmless, their case for sueing X has basically been totally destroyed.

    52. Re:SCO Letter by mpe · · Score: 1

      And according to the terms of the GNU General Public License, if you can't satisfy patent laws AND the terms of the GPL simulataneously you have no right to use the code at all.

      Rather you have no right to distribute (to third parties) the code under the GPL. Copyright law says that you need permission from the copyright holder to distribute at all. The GPL says that the copyright holder grants you conditional permission to distribute. Thus to distribute the code under the GPL you need simply follow the applicable conditions. If you can't (or don't want to) follow all the applicable conditions in the GPL then the only way you can distribute is by getting permission from the copyright holder(s).

    53. Re:SCO Letter by p3d0 · · Score: 1
      Right. And SCO's claim is that their code was released without their knowledge or permission, by someone who does not hold the copyright, so the GPL doesn't really enter into it.

      The interpretation that "the GPL holds that IP SCO allows to be used by a select few must be freely released to any and all" is simplistic at best, and I think it's specifically, explicitly incorrect. The GPL says that whomever you release binaries to should also get the source; I'm pretty sure it does not say that if you give someone the code, you have to give it to everyone.

      If someone is going to make a claim like that, they ought to quote the relevant clause from the GPL.

      --
      Patrick Doyle
      I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
    54. Re:SCO Letter by MortisUmbra · · Score: 1

      Well, you can't be selective about it is the point. If I have a patent of a copyright, it is my duty to defend my patent or copyright. I cn't pick and choose, I have to defend it from everyone, or risk losing it. I can think of serval federal review bodies who would LOVE to see SCO doing something like that, only taking potshots at OTHER people selling Linux but not their own.

      --

      "The saddest words of mice and men, are not those which were, but should have been."
    55. Re:SCO Letter by mpe · · Score: 1

      But say for the sake of argument that the GPL were invalidated.

      SCO getting the GPL invalidated would be a case of shooting themselves in the foot (with a cannon). Without the GPL they would have no right at all to distribute the code at all.

      What would people who had GPL'd code do? They'd basically either (1) keep it to themselves or (2) release it under a BSD style license.

      False dicotamy. The copyright holders of thc code could apply any licence they wanted to. Including one similar to the current GPL.

    56. Re:SCO Letter by jpmorgan · · Score: 1

      Um, no. To enter into a contract, both parties have to sign, and it has to be witnessed. If delivering a product were entering into a contract, then EULAs of all types would be well and truly legal.

    57. Re:SCO Letter by mpe · · Score: 1

      I don't see any reason why the GPL would be invalidated, however. The GPL grants people rights that they do not have under normal copyright law, unlike most licenses that seek to remove rights.

      The most important thing to remember is that the GPL is not an EULA it is a "Copyright Distribution Licence".

      And the GPL doesn't prevent anyone from asserting IP rights. By agreeing to follow the terms of the GPL, they are agreeing to not assert additional IP rights over that code. The agreement is the important part. Nobody is forced to distribute GPL'd code, it is done by choice.

      Effectivly the GPL says that you have permission, from the copyright holder, to distribute, a copyrighted work, subject to a set of conditions. Conceptually this isn't that different from the copyright holder saying "you may distribute if you pay me X amount of money."

    58. Re:SCO Letter by boots@work · · Score: 1

      Don't be silly.

      As any first-semester law student could tell you, a contract can be formed verbally, or implicitly by action. Contracts do not have to be written and certainly do not have to be witnessed.

      Do you really expect to have a written, signed and witnessed contract every time you purchase groceries?

      Having a contract in writing and witnessed helps avoid arguments later about exactly what was agreed to, but it is not required by law. (There may be exceptions for some kinds of contracts in some jurisdictions.)

      Go away troll.

    59. Re:SCO Letter by schon · · Score: 1

      SCO's claim is that their code was released without their knowledge or permission, by someone who does not hold the copyright, so the GPL doesn't really enter into it.

      Except that the GPL is the only thing that allows them to continue to distrubute Linux (which they're still doing.)

      There are some simple questions:
      Do they know "their" code is in a GPL'ed product?
      Are they still distributing this product?

      There is no doubt that the answer to both of these questions is YES.

      So, whether they put "their" code there, or someone else did is irrelevant. They are either agreeing to GPL it, or are in violation of copyright law. It's really that simple.

    60. Re:SCO Letter by Fishstick · · Score: 3, Funny

      I must not tell lies... OW!
      I must not tell lies... OW!
      I must not tell lies... OW!


      God she's a bitch.

      --

      There is much cruelty in the universe, John.
      Yeah, we seem to have the tour map.

    61. Re:SCO Letter by Exousia · · Score: 1

      The point is that SCO is giving tacit approval for these users of Linux to use it as it stands. That means that SCO is tacitly agreeing to the GPL. SCO does not have the right to say, "we are going to allow you to use the Linux kernel that we claim has our unauthorized IP in it, but we are not agreeing to the GPL." If they agree to the use of the disto, *any* distro, of Linux with SCO code in it, they agree to the GPL.

      --

      --Slashdot: News for Turds. Stuff that Splatters.
    62. Re:SCO Letter by sql*kitten · · Score: 1

      What have you got to say for yourselves now, dumbasses? This may not contain the exact stuff that they're all worked up about (although it sounds like they want to claim RCU entirely), but it is a patch for source that does contain the offending material and therefore a derivative work.

      I expect they will say that IBM didn't have the right to release it under the GPL (I don't have a copy of the file you refer to but I presume it is in reverse chronological order otherwise how could IBM copyright it after it was GPL'd). It seems to say that Paul McKenney - who has an IBM email address, but might have originally worked for Sequent - wrote some stuff, then Dipankar Sarma modified it in 2001, then later IBM GPL'd it.

    63. Re:SCO Letter by grahamm · · Score: 1

      RIAA and MPAA do not seem to think so? They object to the playing of DVDs in 'unlicenced' players and sell so called 'CDs' which do not play on Linux or other computer systems.

    64. Re:SCO Letter by swv3752 · · Score: 1

      Actually they had to agree to the GPL or else they themselves are in violation.

      --
      Just a Tuna in the Sea of Life
    65. Re:SCO Letter by p3d0 · · Score: 1
      There are some simple questions:
      Do they know "their" code is in a GPL'ed product?
      Are they still distributing this product?
      It still doesn't matter. I can modify GPL'ed code, and I can distribute it to a select group of people. So long as I give them the source code along with the binaries, it's all good.

      If you're claiming the GPL has some kind of "if you give it to someone, you must give it to everyone" clause, then please post it. I can't find it.

      --
      Patrick Doyle
      I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
    66. Re:SCO Letter by Zeriel · · Score: 1

      Delivering a product with the click-through agreement and license terms shown beforehand is presumed legal and the license is binding. Signatures and witnesses are not required, all that's required is a clear display of terms and an action. Having a notice that says "Here's the GPL, you can download if you agree" is exactly the same (legally) as the implied contract to buy something for the price on the sticker in the grocery store (when a retailer has a malfunction in their pricing/scanning systems that results in a higher price being charged than is listed on the sticker, they can be held liable for fraud and violation of contract). The act of offering is their "signature", and the act of paying/downloading is yours.

      EULAs that are shown after the product sale are presumed non-binding by the doctrine of first sale. See many previous posts by many people about closing a deal on your house and then finding a terms of use stapled to the front door after the fact.
      AFTER THE FACT. Those words are the key difference between a valid license contract and an invalid (mostly) EULA. Not signatures, not witnesses. Timing.

      --
      "America has done some terrible things. But I know that Americans don't cheer when innocents die." -Dave Barry
    67. Re:SCO Letter by lobsterGun · · Score: 1

      Even though IBM may have the patent on RCU tech, SCO could still have a copyright on an implementation of RCU. SCO would have to pay whatever license IBM specified on the RCU implementation, but that alone would not give IBM the right to use SCOs copyrighted source code without their permission.

    68. Re:SCO Letter by Catiline · · Score: 1
      The interpretation that "the GPL holds that IP SCO allows to be used by a select few must be freely released to any and all" is simplistic at best, and I think it's specifically, explicitly incorrect. ... If someone is going to make a claim like that, they ought to quote the relevant clause from the GPL.
      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.

      Clear enough for you?

    69. Re:SCO Letter by johnnyb · · Score: 3, Insightful

      Actually, the GPL is even more enforceable than that, because the end-user does NOT have to accept it, even to use the program. The end-user can simply ignore the GPL and use the program as if it had no license attached.

      In which case, normal copyright laws apply, which means you can't redistribute at all.

      The problem with most EULAs is that they restrict rights after purchase. The GPL is completely different in that it adds rights under specific conditions. If you don't meet those conditions, you never had those rights to begin with.

    70. Re:SCO Letter by Anonymous Coward · · Score: 0

      Except...SCO contends their license with IBM for the original Unix code prevents them from releasing any software that was developed from that code. They would argue that RCU was developed for AIX, and therefore cannot be publicly released.

    71. Re:SCO Letter by MrGrendel · · Score: 1

      They probably will come up will some sort of nonsense like that. But their defense against GPL violations when they sent out the 1500 letters in May was that the GPL only applies to code that has a properly attached copyright notice according to section 0. So the sections of "copied" code are not under the GPL, while everything else is. Of course, sections 3 and 7 close up that loop hole, but this is even more problematic for their defense. Even if IBM was contractually prohibited from distributing the RCU code, they still own the copyright. There is no way that SCO can claim that the copyright is somehow theirs because you can't transfer copyrights by contract. They have to be physically signed over after the fact (there is a short discussion of this somewhere on the FSF web site). So even if IBM violated a contract with SCO, the copyright notices for the RCU code are correct and SCO loses its only feeble defense.

    72. Re:SCO Letter by pfleming · · Score: 1

      No- they said they won't sue people who paid to use the SCO Linux code.

    73. Re:SCO Letter by p3d0 · · Score: 1
      Well, that's pretty good, but it's not the whole story. Some companies modify GPL'ed code for internal use, and the GPL allows that. If an employee were to redistribute that code outside the company, they could be in breach of their employment contract, and justifiably so.

      Likewise, is there any reason that SCO could not write up a contract with a customer requiring that the customer not redistribute the code? If so, why is this situation different from the employee's situation?

      --
      Patrick Doyle
      I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
    74. Re:SCO Letter by EvilBudMan · · Score: 1

      --But if SCO sold them Linux, I don't see how they could sue anyway.--

      This is the good ole USA where anyone can sue for anything. It doesn't mean that they can win but they can sue and take up lots of your time and money.

    75. Re:SCO Letter by usotsuki · · Score: 1

      And they, along with SCO, can go foo off. (Nice use of chiasm there BTW).

      Anything should work on any player.

      Any Linux should be free for all.

      And foo it all, if there's a problem, they should help us all move to BSD. (I'm staying put with Hed Rat, TYVM)

      -uso.

      --
      Dreams, dreams, don't doubt dreams, dreaming children's dreaming dreams. Sailor Moon SS
    76. Re:SCO Letter by nobody69 · · Score: 1

      To enter into a contract, both parties have to sign, and it has to be witnessed.

      That's not true. If you go into Your Friendly Neighborhood Pizza Joint and ask for a large with everything you have entered into a contract to pay for a large with everything, eventhough you didn't sign anything. You can't claim that you don't have to pay after the fact because you didn't sign a piece of paper, or even verbally say "I'll pay you $18 for the pizza". Or even if they put anchovies on it.

      --
      "Bugger this, I want a better world." - Jenny Sparks
    77. Re:SCO Letter by Stephen+Samuel · · Score: 1
      They said they won't sue people using SCO Linux, not that it was ok with them for the code to be used.

      No difference.. The GPL is essentially an agreement to not sue you for what would normally be a violation of copyright. A promise not to sue is (in legal circles) essentially a statement that it's OK.
      (IANAL)

      --
      Free Software: Like love, it grows best when given away.
    78. Re:SCO Letter by Anonymous Coward · · Score: 0

      ftp://ftp.caldera.com/pub/updates/OpenLinux/3.1.1/ Server/current/SRPMS/linux-2.4.13-21S.src.rpm

      Full Source and SCO's patches
      Released 9th May 2003

    79. Re:SCO Letter by Anonymous Coward · · Score: 0

      ftp://ftp.caldera.com/pub/updates/OpenLinux/3.1.1/ Server/current/SRPMS/linux-2.4.13-21S.src.rpm

      Full Source and SCO's patches
      Released 9th May 2003

    80. Re:SCO Letter by Twanfox · · Score: 1
      This is the situation SCO are now in. Even after their initial allegations against IBM, they continued both selling copies of Linux, and offering it for free download from their web site.
      So, if SCO is distributing for free the Linux OS, that means they wouldn't be getting paid for it. Would the people that are not paying service contracts, but aquired their software from SCO liable for damages?
    81. Re:SCO Letter by Catiline · · Score: 1
      Likewise, is there any reason that SCO could not write up a contract with a customer requiring that the customer not redistribute the code? If so, why is this situation different from the employee's situation?
      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.

      Once SCO gives the code to anyone who is not a part of SCO -- to wit, they distribute the code -- they are bound by the GPL and may not limit their customers' excercise of any GPL rights. That difference is simple: internal use by employees is not distrobution, so contract clauses between the employer and employee can prevent all distrobution; however, once the code has been released once, it is released for good.

    82. Re:SCO Letter by Dr.Zap · · Score: 1

      Well then, I guess I'll just have to install SCO linux on all my boxes, then upgrade them using Gentoo.

    83. Re:SCO Letter by p3d0 · · Score: 1
      Ok, I guess distribution within the entity that holds the copyright isn't actualy distribution at all.

      You win.

      --
      Patrick Doyle
      I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
    84. Re:SCO Letter by DavidTC · · Score: 1
      Getting viral licenses thrown out would be the last thing SCO wants, as they have a truly viral license, in that they are claiming ownership and control of everything that's ever been part of Unix, even if a third party put it in.

      Even the GPL doesn't do that kind of wackiness. You can stick something in a GPL product and still retain copyright and control of other versions of the code in other locations.

      SCO's claim is basically that their license is so viral, it's roughly akin to saying that if you purchase a copy of their book, and write a note in it, and then later you have a similiar note publish in a collection of short stories, they own the copyright on that entire collection.

      Which is about as viral as you can get.

      --
      If corporations are people, aren't stockholders guilty of slavery?
    85. Re:SCO Letter by Trogre · · Score: 1

      Sorry, not quite the right page.
      The kernel is here.

      --
      "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
    86. Re:SCO Letter by mink · · Score: 1

      I think you need to read up on patent/copyright/trademark law.

      Trademarks if not defended will be lost when infringed.
      Patents can be selectively enforced and not be lost.
      Copyright can AFAIk also be selectively enforced, but I dont think I have heard of this happening.

      --
      Well I've wrestled with reality for thirty five years doctor, and I'm happy to say I finally won out over it.
    87. Re:SCO Letter by Anonymous Coward · · Score: 0

      Nosrc RPMS are those SRPMS of which not all sources are present in the SRPM, some are to be downloaded from a ``well-known'' website. For more info., see this page

    88. Re:SCO Letter by ltmdweaver · · Score: 1

      Well not really a big difference, considering your point does not apply...

      traffic is not civil law... IP is.... Also in the case of IP, not enforcing (especially over time) is... in the eyes of the law dminishing the value of the IP... kind of hard to make that kind of case about the safety of jaywalking... ;-)

    89. Re:SCO Letter by 56 · · Score: 1
      Umn... you do realize that I used the traffic exaxmple as a way of discussing principle - I wasn't trying to make any sort of even remotely literal point.

      You would think that was obvious....

    90. Re:SCO Letter by civilizedINTENSITY · · Score: 1

      "They said they won't sue people using SCO Linux", and in fact that they would continue supporting them (even to the point of updates)...not that it was ok with them for the code to be used.

      "If I jaywalk and don't get charged, it's not that jaywalking is not illegal, it's that the law was not enforced." Yes, but the point is that having released (knowingly) under the GPL the code is now GPL-ed. Thus its more like after the Gov'nr grants a pardon the Supreme Court extends the pardon for everyone else convicted under a given law. After they've painted crosswalks its not jaywalking anymore!

  2. looks better with line breaks by Anonymous Coward · · Score: 3, Funny

    SCO will die
    Linux will always prosper
    so will IBM

  3. Re:really now by Klimaxor · · Score: 0, Flamebait

    ...that is the single most fucked up post i've ever read on..any site..period.
    i mean...wow..i'm sitting here at work, and it just blew my mind.

    --
    your sins into me, oh my beautiful one.
  4. Why doesn't someone by Anonymous Coward · · Score: 2, Funny

    Set up Scodot.org, and then all the SCO news can be there. That would make me happy.

  5. Is it worth it? by ShieldW0lf · · Score: 2, Funny

    I mean, should we switch?

    How much suffering would you have to endure before you'd use Caldera on all your servers to make it stop?

    --
    -1 Uncomfortable Truth
    1. Re:Is it worth it? by greentree · · Score: 1

      I suppose Hitler wasn't that bad of a fellow after all. His Nazi idea is starting to grow on me now. Hmmm

    2. Re:Is it worth it? by perp · · Score: 5, Funny

      How much suffering would you have to endure before you'd use Caldera on all your servers to make it stop?

      At this point, I think it would take me and my loved ones being flogged with bundles of stinging nettles that have been dipped in hot sauce and rolled in salt, while listening to Celine Dion sing that Titanic song accompanied by an orchestra of bagpipes. In Hell.

      --
      There are two kinds of sysadmins: paranoids and losers. I'm both kinds.
    3. Re:Is it worth it? by ShieldW0lf · · Score: 4, Funny

      Shit. They would have had me at Celine Dion...

      --
      -1 Uncomfortable Truth
    4. Re:Is it worth it? by Anonymous Coward · · Score: 0

      Until the GPL is upheld in a court of law, noone really knows if it is enforcable or not.

    5. Re: Is it worth it? by Black+Parrot · · Score: 1


      > At this point, I think it would take me and my loved ones being flogged with bundles of stinging nettles that have been dipped in hot sauce and rolled in salt, while listening to Celine Dion sing that Titanic song accompanied by an orchestra of bagpipes.

      Aye, matey, that would really spoil the bagpipe music.

      --
      Sheesh, evil *and* a jerk. -- Jade
    6. Re:Is it worth it? by Anonymous Coward · · Score: 0

      I was told that hell was a burning pit of fire and lava. This never really bothered me, I just thought of it how my parents always told me when they put alcohol on my sores: "It'll only burn for a second or so"
      They didn't say anything about Celine Dion. Fuck that, I'm going to church from now on!

    7. Re:Is it worth it? by fanatic · · Score: 1

      Caldera OpenLinux 2.2 was the first Linux distro I ever installed, May 1999.

      It was gone after a few weeks when I realized I had to manually fix things to get the 'at' command to work, and when it appeared that I would never be able make the innd installation work.

      Went to redhat 6.0 which wasn't glitch free, but the basics worked.

      (I'm very suspicious of anydistro that shows up with basic things not working. I ditched a Mandrake distro when it became clear that the email MTA wasn't going to work anytime soon (even local email didn't work). This was right after they ditched sendmail for postix, a good decision with a bad initial implementation.)

      Anyhow, there isn't enough suffering to make me use SCaldera. I seriously doubt there will ever be consequences for any Linux users because a) their suit is a contract dispute with IBM and I didn't sign a contract with SCO when I installed Redhat and b) their suit is a bunch of crap, based on the idea that since they own some ancient code, they own everything ever done since that was in any way related. Look for them to get laughed out of court the first time someone takes a serious look at their case.

      --
      "that's not encryption - it's a new perl script that I'm working on..." - from some Matrix parody
  6. Companies just don't get that GPL means business.. by Anonymous Coward · · Score: 5, Interesting

    It continues to seem that most companies simply don't believe that the GPL is a real license. It's as if they think that secretly free software authors "don't really mean it" when they explicitly define rights and restrictions in a license.

    It's almost as if the GPL is too "far out" and too liberal for anyone in corporate America to really believe it's real or take it seriously; they seem to think they can just pretend like it isn't there and the courts will wink and understand. As more and more cases end up in court (as the SCO case looks like it will), I wonder if we'll start to see a shift away from "those free software kids don't have a REAL license, this GPL thing is just a toy" to "these are dangerous commies that threaten our entire economy and for that reason the courts must ignore what they're doing and side with us!"

    Sort of like the end of segregation and the Vietnam war protests in the US, both things that much of the older generation simply couldn't understand beyond "those silly kids and their silly ideas" and later "those god damned subversive kids and their dangerous ideas..."

  7. Bad analogy by metalhed77 · · Score: 2, Interesting

    SCO can do as they wish with their IP of course, its that simple, truly.

    --
    Photos.
    1. Re:Bad analogy by 56 · · Score: 1

      The analogy is apt for what I was saying. It would not have been apt for what you were saying but, of course, I was not trying to prove your point.

    2. Re:Bad analogy by Gaetano · · Score: 4, Interesting

      Except they can't include code covered by their IP/Copyright or whatever with GPLed software (the linux kernel) without also releasing their code as GPL software. So even SCO customers don't really have a license for their linux distribution unless it was GPLed, which isn't what SCO wants.
      They actually can't do whatevery they want with their IP.

    3. Re:Bad analogy by Anonymous Coward · · Score: 0

      There must be some rules/laws in place where a company may choose to NOT sue their customers, no?

    4. Re:Bad analogy by Anonymous Coward · · Score: 0

      Oh yeah, to continue...

      SCO Linux customers haven't done anything illegal; they got their code from SCO, and obviously SCO can't infringe on SCO's IP rights. Hence, they don't get sued.

    5. Re:Bad analogy by Znork · · Score: 2, Insightful

      Actually, they can do whatever they want with their IP. They just cant do whatever they want with others IP. As Linux is GPL, SCO is either violating copyright law on a massive scale by distributing Linux together with SCO proprietary IP, or they have to release their IP under GPL. They're perfectly free to do either, only in one case they're open to massive fines that would make their IBM lawsuit seem modest plus jailtime for copyright violations (of other peoples copyrighted but GPL'ed code), and in the other they have to release their code under a GPL compatible license and cant sue anyone.

    6. Re:Bad analogy by mpe · · Score: 1

      Except they can't include code covered by their IP/Copyright or whatever with GPLed software (the linux kernel) without also releasing their code as GPL software.

      Actually they could, but in order to do so they would need to negotiate with the copyright holders of every relevent piece of GPL code. Following the GPL is the simplist option for anyone who wishes to distribute GPL (and derived) code. Since they have no need to identify, contact and negotiate with copyright holders.
      By placing their code under GPL these people have effectivly said "if you want to distribute my work, then you can do so according to these (and only these) conditions." If you want a different set of conditions then you must negotiate with the copyright holder.

    7. Re:Bad analogy by Anonymous Coward · · Score: 0

      Did you notice that SCO says in its letter:

      ``SCO will continue to honor all contractual obligations with existing customers including product updates, service, and support.''

      Isn't the GPL one of these "contractual obligations"?

  8. I wonder... by mikeophile · · Score: 2, Insightful

    How many people will be shorting SCO stock tomorrow morning?

    1. Re:I wonder... by Citizen+of+Earth · · Score: 0, Flamebait

      How many people will be shorting SCO stock tomorrow morning?

      Ha, I shorted 1000 shares today... well, as a fun virtual exercise.

    2. Re:I wonder... by anotherdotter · · Score: 1

      Did you buy a put option, or effectively borrow the stock and sell it etc...?

      As a lowly student, I can't afford to put up the margins my broker wants. I'd like to buy a put option, but I don't think people write them. Thanks.

    3. Re:I wonder... by Anonymous Coward · · Score: 0

      How many people know the SCO employees and thier families ?
      They shorted SCO before the news release!!!!

    4. Re: I wonder... by Black+Parrot · · Score: 1


      > How many people will be shorting SCO stock tomorrow morning?

      Holding on to SCOX may not be a vote of confidence in SCO's business plan; it may be a vote of no confidence in the US legal system.

      And there are plenty of folk out there who can afford to throw away a few thousand dollars on SCOX now on the extremely slim chance that it will be worth 10x a year or two from now.

      --
      Sheesh, evil *and* a jerk. -- Jade
  9. well by intermodal · · Score: 5, Insightful

    if they are allowing Caldera linux users to continue as it is, I'm fairly certain that as a GPL'ed product, if SCO determines they are going to release their linux kernel as a proprietary object with or without open source, they're opening themselves up to hundreds of lawsuits from kernel developers who haven't licensed that action.

    --
    In SOVIET RUSSIA... erm...NSA AMERICA, the Internet logs onto YOU!
    1. Re:well by MrWa · · Score: 2, Interesting
      if they are allowing Caldera linux users to continue as it is, I'm fairly certain that as a GPL'ed product, if SCO determines they are going to release their linux kernel as a proprietary object with or without open source, they're opening themselves up to hundreds of lawsuits from kernel developers who haven't licensed that action.

      But SCO's argument is that these very kernel hackers had no right to release that kernel work under the GPL to begin with - all derivative work from UNIX belongs to SCO. All SCO will be doing is reasserting their right (according to them) to all that work was done. Just as WASTE, apparently, was never actually released under the GPL...

      Imagine the trauma is SCO wins: not only will all that derivative work belong to them but there will be a boatload of pissed off kernel hackers that have given a lot of work away (ironically, considering that is what they have been doing all along, ne?)

    2. Re:well by intermodal · · Score: 1

      even if that's true, the kernel hackers still released their own code under the GPL. Any usage of the GPL code by Caldera-cum-SCO is a voilation of the terms of it's release, and SCO would be certainly liable.

      --
      In SOVIET RUSSIA... erm...NSA AMERICA, the Internet logs onto YOU!
    3. Re:well by 1lus10n · · Score: 1

      "Imagine the trauma is SCO wins: not only will all that derivative work belong to them "

      ALL derivative work will belong to them. that'd be BSD, OSX, Solaris, AIX etc ... not just Linux. and Believe me they wouldnt hesitate to sue the hell out of everyone if they win this suit.

      point is their lawyers arent as good as IBM's. IBM can just buy them. and they still haven't proven that they have a damn leg to stand on.

      --
      "Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe." --Albert Einstein
    4. Re:well by intermodal · · Score: 2, Insightful

      that's untrue. Even if they win, they'll only own SCO-licenese Unixes. Linux and BSD are not under the SCO license, and are not bound by IBM's agreements or anyone else's, for that matter, as far as that IP is concerned. Even if they do own AIX, any AIX code that made it into the GPL'ed Linux will prove to be SCO's, but will of course NOT be a SCO ownership of Linux. Seriously, the only people that can get hit for this are those responsible. Even Linus himself is not responsible for code that wasn't contributed by him as long as he cannot be proven to have known it was stolen from SCO. Let's face up to the facts...Linus is safe, and Linux cannot be appropriated as SCO regardless by this outcome.

      To reiterate what has been said before, the worst thing that can happen is that the Linux crew has to rewrite a few hundred lines of code or take out modules for a while that honestly don't affect most of us x86 Linux users until they can be rewritten.

      --
      In SOVIET RUSSIA... erm...NSA AMERICA, the Internet logs onto YOU!
    5. Re:well by intermodal · · Score: 2, Insightful

      Yes...the closest they can hope for is to slap the guy who submitted the code to the kernel, and to have it removed from future kernels. They may even be able to stop the distribution of these older kernels without the modules they claim to be theirs being removed.

      However (and its a big however), the Linux guys in charge (linus, alan cox, etc.) were unaware of the code's potentially dubious origins and therefore cannot be held accountable for anything but its removal and replacement. IBM's chance of losing in this is slim. Linus's chance of losing the kernel itself is beyond slim. Besides...the genie is out of the bottle. Even if they try to close the source it'll just get forked.

      --
      In SOVIET RUSSIA... erm...NSA AMERICA, the Internet logs onto YOU!
    6. Re:well by 1lus10n · · Score: 1

      that all depends on what exactly you mean by "if they win".

      if they win all of their claims then they will retain the rights to all derivative works. and if SCO code is indeed in Linux then they can claim linux is derivative.

      doesnt mean its right.
      doesnt mean i think it will happen
      it does however remain a possibility. and thats all i was trying to point out in response to the parent.

      --
      "Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe." --Albert Einstein
    7. Re:well by intermodal · · Score: 1

      it's still untrue. The kernel developers have no binding agreement with SCO, and last time I checked, Jim doesn't get Jane's belongings because she rented a house in good faith from Jack, who had such an agreement with Jim.

      --
      In SOVIET RUSSIA... erm...NSA AMERICA, the Internet logs onto YOU!
    8. Re:well by 1lus10n · · Score: 1

      yeah and ?

      i didnt say anybody besides IBM had any agreement with SCO. but SCO has filed claims that they own *ALL* derivative works. anything they can convince a court was built based on or with their IP. its that simple.

      --
      "Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe." --Albert Einstein
    9. Re:well by intermodal · · Score: 1

      i realize that, but there is no possible way it'll happen so it's pointless to speculate to that depth. SCO has no way of claiming that legitimately. The only chance in hell they have is to start from a ridiculously presumptuouos platform and go even further with it. There's no way that it'll work in court, especially with IBM's lawyers on it.

      --
      In SOVIET RUSSIA... erm...NSA AMERICA, the Internet logs onto YOU!
    10. Re:well by 1lus10n · · Score: 1

      right. and i have been saying that from day 1.

      and i wasnt stating the whole "derivative" thing as fact, simply speculating.
      and im going to continue to speculate since way to many people are playing "head in the sand, fingers in ears" games and denying the very real possibility that SCO will win.

      i dont want them to. but they very well might.

      --
      "Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe." --Albert Einstein
    11. Re:well by intermodal · · Score: 1

      yep. But meanwhile, as the kernel development teams become aware of what contains SCO code, the kernel will likely have all traces of it removed by the time the suit ends in 2007 or whenever, at which point if SCO wins it'll get appealed till SCO loses or till it goes to the supreme court. I'm confident that it won't get that far.

      --
      In SOVIET RUSSIA... erm...NSA AMERICA, the Internet logs onto YOU!
  10. Pronounciation? by Anonymous Coward · · Score: 0
    Dumb question... I want to sound fairly intelligent when I talk about this, so: Is it pronounced "S, C, O, Linux" or do I say it like a word: "SKOH Linux"?

    Posting AC for obvious reasons ;)

    1. Re:Pronounciation? by greentree · · Score: 1, Informative

      it is pronounced as one syllable.. as you guessed "SKOH".. SKO.. whichever.

    2. Re:Pronounciation? by alienhazard · · Score: 1

      who cares, its not like they deserve to have their name pronunced right. why not just pronounce it "hermaphroditic sea snail" like i do, its much more fun that way.

      btw, SCO is an acronym meaning Santa Cruz Operation, so i assume it would technically be S-C-0 and i think i did read somewhere that that is how its said .

      --
      > "I allege that SCO is full of it" -Linus
    3. Re:Pronounciation? by evenprime · · Score: 4, Interesting

      Is it pronounced "S, C, O, Linux" or do I say it like a word: "SKOH Linux"?

      I called their line the other day to see why they were still distributing linux, and their voice mail said "S-C-O". This surprised me, since my friends and I have been pronouncing it 'skoh' since the 1996 or 1997.

      --

      "Weapons should be hardy rather than decorative" - Miyamoto Musashi
      I think that goes for OS's too
    4. Re:Pronounciation? by Anonymous Coward · · Score: 0

      "So certain are you?" -Yoda

      Even the people at Caldera, when you'd talk to them at trade shows, would alternate between pronouncing it "Skoh" and "Ess See Oh."

      IBM is NOT pronounced "Ih-bum" by any knowledgeable person.

      I worked 10 years at NEC and would be annoyed when people would pronounce it "Neck."

      Not every pronunciation has to be shortened by default.

    5. Re:Pronounciation? by Anonymous Coward · · Score: 0


      I would say Ess Cee Oh...

      why?

      Because it is (or at least, used to be) an
      acronym for "Santa Cruz Operation".

    6. Re:Pronounciation? by Anonymous Coward · · Score: 0

      That's really odd, in 10+ years, I've always heard it pronounced "Sko".

      Might be like calling Digital Equipment "DEC" -- everyone did it except the employees.

    7. Re:Pronounciation? by mabinogi · · Score: 1

      An acronym would be "SCO" , not S C O, since an acronym is pronounceable as a word.

      perhaps you mean initials....

      --
      Advanced users are users too!
    8. Re:Pronounciation? by Anonymous Coward · · Score: 0

      Not to download they're not.

    9. Re:Pronounciation? by BELG · · Score: 2, Funny

      After recent events, I pronounce it as "SUCK'O".

    10. Re:Pronounciation? by LinuxGeek8 · · Score: 1

      Yes, I had the same experience. about 2 years ago I called their Dutch office, a friend of mine was working there, and the woman who answered the telephone also pronounced it as "S-C-O".
      Afaik it should be pronounced as "Skoh".

      --
      Well, don't worry about that. We can get you back before you leave. (Dr. Who)
    11. Re:Pronounciation? by Stephen+Samuel · · Score: 1
      I called their line the other day to see why they were still distributing linux, and their voice mail said "S-C-O".

      SCO what? You think I care how they pronounce it?

      --
      Free Software: Like love, it grows best when given away.
  11. viral nature of GPL. by stonebeat.org · · Score: 1

    I guess this is why some advocates of IP do not like like the viral nature of GPL.

    BTW not being being caught for evading the law is not same as applying the GPL to peice of source code.

    1. Re:viral nature of GPL. by MrLint · · Score: 2, Funny

      You mean SCO jumped into the GPL pool without their crack team of lawyers reading it first? Say it aint so.

    2. Re:viral nature of GPL. by Anonymous Coward · · Score: 0

      All licenses are viral, including MS EULAs. Get over it.

    3. Re: viral nature of GPL. by Black+Parrot · · Score: 1


      > You mean SCO jumped into the GPL pool without their crack team of lawyers reading it first? Say it aint so.

      Of course, "they" jumped in when they were still a software company instead of a lawsuit company. There has been a change of managment since then.

      --
      Sheesh, evil *and* a jerk. -- Jade
    4. Re:viral nature of GPL. by frozenray · · Score: 1

      > You mean SCO jumped into the GPL pool without their crack team of lawyers reading it first?

      The good news for SCO: they have a "crack" team of lawyers, indeed.

      The bad news: that's "crack" as in "the stuff you can buy from the dealers in the less reputable parts of town".

      --
      "There are already a million monkeys on a million typewriters, and Usenet is NOTHING like Shakespeare." - Blair Houghton
  12. Hopefully this means Linux is free and clear by LordBodak · · Score: 3, Insightful
    Linux is released under the GPL. SCO can't just say "oh, it's ok that you have it but it's not ok that others have it."

    However, it does seem logical that SCO could _choose_ not to prosecute SCO Linux users. But then, couldn't you argue that any Linux user that ever had a Caldera/SCO OpenLinux CD is a SCO Linux user?

    IANAL, but SCO barely had a leg to stand on legally and now it seems like they shot the foot on that leg :)

    --
    LordBodak's journal.
    1. Re:Hopefully this means Linux is free and clear by Anonymous Coward · · Score: 0

      Oh really? You look like an ANAL to me.

    2. Re:Hopefully this means Linux is free and clear by KrispyKringle · · Score: 4, Insightful
      You miss the point. This is not law. SCO is not contractually bound not to prosecute anyone who is a "SCO user," in the sense that you could find a loophole in that decision and avoid prosecution. The decision to prosecute or not is a personal, non-binding one. If they say, "Oh, well, I meant that they would not be prosecuted for use of SCO, not that I won't prosecute anyone who ever used SCO" (which is obviously what they do mean, anyway), you can't say, "Well, that's not what you said." If they want to sue you, they certainly can.

      Furthermore, many people are posting here that "SCO is approving the use of their code in Linux under the GPL! Nyah nyah!" Well, there's a far cry from not prosecuting certain individuals and approving the use. If you stole SCO's code but only had $50 in your bank account so they chose not to prosecute you, they could still prosecute RedHat for doing the same thing. By your logic, the failure to prosecute home users is a blanket approval, which it truly isn't. It's just a cost-benefit analysis; they have little to gain from suing home users.

      In certain IP cases, failure to enforce IP ownership does constitute a grant to public domain of that IP, but this is not a wholesale failure to prosecute, only a leave given to a few specific alleged violators. This is meaningless. Of course SCO won't sue SCO users; this is not in any way a legal flaw (and, no offense to all those armchair lawyers, but I'm sure SCO had their legal team review all actions they've taken prior to taking them, so I doubt you'll find any "loopholes").

    3. Re:Hopefully this means Linux is free and clear by LordBodak · · Score: 1
      You're quite correct in that.

      Of course there is one other thing that does lead to the idea the SCO will never see any money from Linux licenses. If SCO is correct that their IP is in Linux, as soon as the evidence comes out in the IBM trial, kernel developers are going to get to work reimplementing those parts of the kernel. Posibly by the time the case is over (but almost certainly before SCO could even begin going after users) there will be kernel releases without SCO code.

      --
      LordBodak's journal.
    4. Re:Hopefully this means Linux is free and clear by Chris+Brewer · · Score: 1

      "But then, couldn't you argue that any Linux user that ever had a Caldera/SCO OpenLinux CD is a SCO Linux user?"

      Whoo-hoo! I'm free and clear!

      I bought Caldera OpenLinux for Dummies a few years ago now. 2.2 kernel, kde 1.0... Those were the days.

      Of course I wouldn't touch it now, but I suppose I could un-rpm the kernel source and run the patches all the way up to 2.5.73, thereby absolving myself from sin... :)

      --
      Consultancy: If you're not part of the solution, there's money to be made in prolonging the problem
    5. Re:Hopefully this means Linux is free and clear by KrispyKringle · · Score: 2, Informative
      Absolutely right; thats why from a I-don't-give-a-shit-about-law-just-let-me-write-co de standpoint the whole thing is silly. Just say what code is copyright and let the kernel developers fix it.

      This pretty much clears it up from our end. Linux is (or will be) in the clear, which is pretty much all we probably care about. For IBM, however, this is not nearly the end of the story.

      If IBM did violate their contract with SCO (I know this is something we all don't want to talk about much), they did do something pretty shitty. I can't speak for coders everywhere, but I would whole-heartedly agree with SCO right now if someone stole something I'd written. So IBM could face a huge amount of damages, not to mention the possible revokation of their Unix licenses. So I suppose its slightly possible (I doubt this would happen; they'd probably just pay some outrageous new license fee) that this could be the death of AIX. Couple that with a pretty severe hit to the reputation of Linux (imagine trying to convince a suspicious CEO about the wisdom of a grassroots OS now) and you've got a pretty large Unix marketshare drop. Which probably adds up to boosts for Windows and, if Sun has their way (big if; the big problem with Sun is not the quality of their OS but the cost of their hardware), a big boost for Solaris.

      All of this is more corporate fallout than anything that applies to the hobbiest or home-users, but it makes the point that this whole thing does get rather complex.

    6. Re:Hopefully this means Linux is free and clear by DavidTC · · Score: 1

      Um, actually, under legal theory it would be pretty damn stupid to sue someone for using what you sold them. There's basically no way they'd be able to get away with that in court, at least not until they issued a recall and offered to pay for the product, and even then it's iffy.

      --
      If corporations are people, aren't stockholders guilty of slavery?
  13. The Gloves Come Off... by Anonymous Coward · · Score: 5, Insightful

    A couple thoughts spring to mind:

    1. What the HELL were you protesters thinking by putting your arms around this guy and turning it into a photo-op for him? I mean, the windows refund day fiasco was bad enough. But are we serious about protesting or not?

    2. The more I read, the more I think this is going to come to a legal test of the GPL.

    3. As someone has already pointed out, it's a fine line between granting a license and choosing to not enforce copyright violations from their own customers. It's assinine that they could even suggest their own customers are violating a copyright by using software which THEY sold to them, but it will make for a very interesting legal battle.

    4. Does anyone have any stories of how Linux customers of other distributions are being damaged? Of how other Linux-derived companies or employees are being harmed? I think it's time to create a mailing list somewhere of people who feel they are being harmed by SCO's actions.

    1. Re:The Gloves Come Off... by antiMStroll · · Score: 4, Interesting
      1. What the HELL were you protesters thinking by putting your arms around this guy and turning it into a photo-op for him?

      I got to thinking afterwards what a masterful stroke SCO pulled by joining the protestors. Entering the fray 'in the spirit of fun', and getting the opposite side to join in, including at one point convincing one of the protestors to carry pro-SCO signs, reduced the anti-SCO position to 'all in fun' as well. Not to be taken seriously. You can bet though, the message the SCO signs carried - linux = communism, GPL = theft, OSS = Kazaa - resonated with a few less-informed people.

      Pretending to extend the hand of friendship, SCO completely obliterated the anti-SCO message. Slick.

    2. Re:The Gloves Come Off... by KrispyKringle · · Score: 1
      "2. The more I read, the more I think this is going to come to a legal test of the GPL."

      I strongly doubt that. SCO is suing IBM under their alleged contract violation, not under any copyright or intellectual property violations. I don't feel like searching down the exact quote, but Darl MacBride said something like, "Intellectual property is for enforcing rights between strangers. Contract law is much stronger; contract law is for when you know the other party. In this case, we will be using contract law." Something like that; you get the idea.

    3. Re:The Gloves Come Off... by Anonymous Coward · · Score: 0

      Nonetheless, SCO is using the lawsuit to threaten ALL Linux users, not just IBM. And their claims of copyright infringement, though it may not be the charges of the lawsuit itself, over portions of Linux, is directly related to the GPL, as is the fact that they were distributing, and continue to distribute linux themselves.

      So the GPL is very relevant.

    4. Re:The Gloves Come Off... by Anonymous Coward · · Score: 0
      1. What the HELL were you protesters thinking by putting your arms around this guy and turning it into a photo-op for him? I mean, the windows refund day fiasco was bad enough. But are we serious about protesting or not?

      Wow, you slashdotters sure get worked up. I am one of the people in the picture. After our twenty minute converstion, he said that he had to leave so I asked him if we could take his pictures with him. I thought it would be a Kodak moment, and would actually be pretty funny.

      I realize how big of a threat this lawsuit is, that's why I was one one of the main organizers of the event. I really doubt that they are going to use that picture in their next set of brochures.

      We were serious about the protest, but also had some fun while we were at it. Take a chill pill buddy...

    5. Re:The Gloves Come Off... by KrispyKringle · · Score: 1

      No, it isn't. This will not become a test of the GPL. The GPL is not relevant to this case. Now, if someone else is suing someone else in relation to the GPL that I don't know about, please, feel free to mention it.

    6. Re:The Gloves Come Off... by bninja_penguin · · Score: 1

      Does anyone have any stories of how Linux customers of other distributions are being damaged?

      Not some other distro but SCO's godforsaken own OpenLinux thingy...I've said this before, and I'll say it again, "SCO, where's my goddamn $20.00 rebate you promised would get to me in 3 or 6 or 8 weeks? I'm pretty goddamn sure you didn't mean 4 years!

      Sco, just take the $20.00 and get some AIDS riddled crack whore, and have her do you like you want to do me!

      --
      For those who describe their systems as 'boxen', do you order multiple 'boxen' of corn flakes also?
    7. Re:The Gloves Come Off... by jmors · · Score: 1

      Class Actiuon Suit Anyone!? It would seem to me that a great deal of harm is being done, not only to linux companies and direct users of Linux in business applications but also to those of us who have evangelized,supported, and encouraged the use of open source and linux technology in the sometimes rather large corporations we work for. I myself am employed by a large telecommunications firm and have supported and encouraged the use and deployment of linux as an operating system in talks with Executives and Vice Presidents within my company. This is damaging not only to those of us who occassionally develop or work on parts of various open source projects but it is damaging our reputations and possibly, in some cases our likelyhood of raises and adequate compensation. I can even imagine in some corporations people could be fired for being the one who puched through the decision to switch to linux. I am definitely not a lawyer but wouldn't a class action lawsuit against SCO for the damage their unsubstantiated FUD campaign is doing be perfectly reasonable? Any Lawyers out there? I'll be one of the first to sign up as a co-defendant!

      --
      The Matrix is real... but I'm only visiting!
    8. Re:The Gloves Come Off... by Daniel+Phillips · · Score: 1

      You can bet though, the message the SCO signs carried - linux = communism, GPL = theft, OSS = Kazaa - resonated with a few less-informed people.

      But more importantly, is the effect re informed people. Those signs will surely come back to haunt SCO.

      --
      Have you got your LWN subscription yet?
    9. Re:The Gloves Come Off... by SlashDread · · Score: 1

      Well SCO did not make any friends in France...

      peace /Dread

  14. It's a numbers Question here by infonography · · Score: 5, Funny

    Of course SCO Linux users won't be sued. There are too few to make it worth while.

    --
    Sorry about the writing. Robot fingers, you know? Cliff Steele in DOOM PATROL #23
    1. Re:It's a numbers Question here by Anonymous Coward · · Score: 1, Funny

      Wait, SCO Linux still has users?

    2. Re:It's a numbers Question here by mandolin · · Score: 1

      Ya know, the prez of IBM ought to go purchase some old dusty copy of Caldera OpenLinux that someone forgot to pee on/burn/mutilate. (You know they're not exactly flying off the shelves right now.) Then IBM becomes a SCO Linux customer, and this whole freakin' lawsuit goes away.

    3. Re:It's a numbers Question here by DavidTC · · Score: 1
      Surely someone has it sitting around unused on a CD around there. Write a note explaining you're donating it and all rights associated with it to IBM, sign it, and mail it off to IBM's legal department in the original package.

      This whole thing just keeps getting more and more surreal, doesn't it? A milti-billion dollar lawsuit over something that SCO lets people get away with for 50 dollars.

      --
      If corporations are people, aren't stockholders guilty of slavery?
  15. SCO shoots both it's own feet.... by deanj · · Score: 5, Funny

    Man, just as soon as SCO shoots itself in both feet during the past couple of weeks, it finds a third foot, and shoots that.... ....oh wait... that's not a foot.... ....ouch....

    1. Re:SCO shoots both it's own feet.... by Jade+E.+2 · · Score: 1
      Man, just as soon as SCO shoots itself in both feet during the past couple of weeks, it finds a third foot, and shoots that.... ....oh wait... that's not a foot.... ....ouch....

      Come on man, that should have been obvious, nobody has feet that small.

    2. Re:SCO shoots both it's own feet.... by Anonymous Coward · · Score: 0

      Oh, man that's the funniest thin I've read all week!

  16. Re:really now by Anonymous Coward · · Score: 0

    For a good time, get other things blown at work.

  17. Nice Quote from Linus by jpetts · · Score: 5, Funny

    Interviewer: SCO alleges that you need to focus more on getting clarification as to where the code that goes in the Linux kernel comes from.
    Linus:I allege that SCO is full of it.

    --
    Call me old fashioned, but I like a dump to be as memorable as it is devastating - Bender
    1. Re:Nice Quote from Linus by Anonymous Coward · · Score: 0

      That is a great quote. Really, is there any more well spoken person in the field? He does exactly what he says and he says it so eloquently that you can't help but agree with what he says.

    2. Re:Nice Quote from Linus by mcgroarty · · Score: 1

      Eloquent nothing. Linus is direct, no bullshit or flowery talk.

  18. get it right... by squidinkcalligraphy · · Score: 2, Interesting

    So SCO lets its customers use it's hypothetical IP as part of the linux kernel. As said in the story, this would then release this code under the GPL. But this does NOT mean they now give the source away to all and sundry - only to their customers (who can then release it to anyone they choose).

    Of course this is all irrelevant as the source is out there and available regardless. Can't wait to see this play out in court.

    --
    "I think it would be a good idea" Gandhi, on Western Civilisation
    1. Re:get it right... by LiENUS · · Score: 1

      having purchased caldera's openlinux product manyayears back i hearby under the gpl release the source, have at it

    2. Re:get it right... by 1010011010 · · Score: 1


      So, pull the Caldera kernel-source.src.rpm fro mtheir distro, patch to make it the same as the kernel for $MYDISTRO, and there you go.

      --
      Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
    3. Re:get it right... by MsGeek · · Score: 1
      These guys already did: http://www.lycoris.com/ .

      They took Caldera's good points (and there were a few) and washed the SuCk-O out of it.

      I wonder what all this SCO bullshit will mean for the next major upgrade of Lycoris, Beryl. Maybe it will never happen. Another reason to curse the name of SCO. Now and forever. Amen.

      --
      Knowledge is power. Knowledge shared is power multiplied.
  19. SCO's customers lose either way by hgp · · Score: 2, Interesting
    Even if SCO chooses not to sue it's own customers (what an ingenious idea - don't sue you're own customers), what sort support are they going to be able to supply while pursuing a lawsuit against IBM. And after IBM counter-sues how much money will they be able to get off them because SCO has failed to fulfil it's support contract.

    -Like tears in rain, time to die.

    1. Re:SCO's customers lose either way by Anonymous Coward · · Score: 0

      [...] not to sue it's own customers [...] don't sue you're own customers [...] failed to fulfil it's support contract.

      Not to sue it is/has own customers? Do not sue you are own customers? Failed to fulfill it is/has support contract? You're talking bullshit.

    2. Re:SCO's customers lose either way by Anonymous Coward · · Score: 0

      Yes, let's judge everybody according to their ability to follow English punctuation rules. Surely anyone who has not mastered correct usage of homonyms, contractions, and possessive pronouns is a WASTE OF LIFE that should be ignored, like the hobo that they are. Hey look, I used "they" to refer a singular subject! This means that I have nothing valuable to say. Please ignore me. Clearly I am inferior to your exquisite manliness. You deserve to pass your genes to more beautiful women than I, with your bigger, gramatically correct penis, while I am stuck with ugly women who cannot punctuate the right way.

      Did you ever hear of this Greek dude named Socrates? Yeah, he couldn't speak English. He didn't even know the difference between "there" and "their"! This means that he is a kook and has useless ideas that all of us should ignore. And besides, he is like, really old.

  20. Obligatory Simpsons Quote by tpengster · · Score: 5, Funny
    SCO has issued a letter saying SCO Linux customers won't be sued.

    Sideshow Bob: The following neighbourhood residents will not be killed by me: Ned Flanders, Maude Flanders, Homer Simpson, Marge Simpson, Lisa Simpson, that little baby Simpson...that is all.

    [Homer runs up to Bart's room]

    Homer: Woo-hoo! Did you hear that Bart? Heh--oh...

  21. GPL doesn't help here!! by Anonymous Coward · · Score: 5, Interesting

    The anti-GPL crowd likes to talk about how the GPL has this power to "force" people to do things, like some kind of animated chainsaw that turns on its owner. Now the anti-SCO folks are using the same argument? Sorry folks, that's not how it works.

    The GPL is simply a means for a copyright holder to grant others the right to copy under certain circumstances. It can't "force" anyone to do anything.

    If the Linux kernel is a derivate work of SCO's (or more likely, certain PARTS of the kernel are derivative works), then SCO can simply claim that ALL copies of the Linux kernel are infringing copies, and ALL public distributions of the code are copyright violations.

    The GPL was placed on that code by someone who was not the copyright holder. That person would not have the right to license the code at all. So you'd have to just ignore the GPL, and treat the code the same as if you just downloaded the Windows 95 source code from somebody on Kazaa.

    SCO can also say, well, since we don't want you to have to go to all the trouble of deleting your OS, we'll sell you an end-user license and so forth, for $50. Otherwise we'll sue you. Aren't we nice and friendly? And we'll pick and choose who we want to sell licenses to, and who we want to give them to for free.

    They certainly wouldn't allow distribution by anyone under the GPL.

    The GPL simply falls by the wayside, since the copyright holder (SCO) NEVER INTENDED to distribute the code. It doesn't matter that they were already distributing it, they can argue that they were duped into distributing it because they didn't know what was in it.

    The GPL does not have any magical power to bestow freedom on anything it touches. Especially someone ELSE'S code.

    (This is assuming all the bullshit SCO is putting out is actually true.)

    1. Re:GPL doesn't help here!! by foonf · · Score: 5, Insightful

      There is something to this. However, if it were the case that some code included in the Linux kernel weren't distributable under the GPL, it would be illegal to distribute it at all. Why? Because all of the rest of the code, going back to the original bits written by Linux in 1991, is under the GPL. Combining that code with other code creates a derivative work of that code. Under the GPL's famous viral provisions, any derivative work of GPL'd software has to be distributable under the terms of the GPL (ie, you can add code which is GPL'd, or you can add code under another license that does not conflict with the GPL).

      So if there is violating code, SCO has no right to "bless" redistribution unless they agree to non-GPL licensing terms with EVERY SINGLE KERNEL DEVELOPER who contributed non-offending source. If they are implying that distribution of their linux kernel is legal, therefore, it implies that they are offering whatever portions they claim ownership of under the terms of the GPL. If not, they are infringing upon the copyrights of hundreds of kernel developers.

      --

      "(Man) tries to live his own life as if he were telling a story. But you have to choose: live or tell." --Sartre
    2. Re:GPL doesn't help here!! by bear_phillips · · Score: 4, Interesting

      Then Linus could send a letter to those people that SCO gave a license to and say "SCO gave you a license to 50 lines of code, but you can't use the other 30000 lines of code because SCO's codes is not GPL'd"

      The GPL does prevent SCO from deciding who can and can't use the linux kernel.

      --
      http://www.windmeadow.com/
    3. Re:GPL doesn't help here!! by Fros1y · · Score: 2, Interesting

      This misses the point though. Sure, SCO can send out emails to all of their customers and grant them the rights to use SCO-tainted linux code, assuming such code exists. When they do that though, and persecute others, they cease to be able to distribute other developers code contributed to the kernel.

      If they claim linux infringes on their IP, and that they must grant licenses for use to be valid, then they'll have to license *other* developers code to distribute it at all.

    4. Re:GPL doesn't help here!! by foonf · · Score: 4, Insightful

      errg.

      SCO has no right to "bless" redistribution

      Should be:

      SCO has no right to "bless" non-GPL redistribution

      The most sickening thing is that it sounds like SCO really doesn't want the (hypothetical) code removed. They want to convince a court that somehow IBM's AIX contract gives them ownership of anything that happens to have Unix code in it, and this overrides anyone else's copyrights, even if they wrote it, Linux as well s Dynix and AIX.

      If they really cared about their Linux customers, they would flag the (alleged) offending code immediately and, if not replace it themselves, at least alert the kernel developers, so that a legal fix could be released. The records are clear enough that it seems they ought to be able to win damages from whoever was responsible for adding it, even if the offending code had been removed from current kernels. If there is no real offending code, though, what they are doing makes perfect sense: the more extreme and ludicrous their claims are, the higher their stock price goes, and the higher their (still slim) chances of being bought out or getting a nice settlement, rather than being embarassed in court.

      --

      "(Man) tries to live his own life as if he were telling a story. But you have to choose: live or tell." --Sartre
    5. Re:GPL doesn't help here!! by Anonymous Coward · · Score: 0

      But then SCO loses its liscese to distribute Linux(tm) code, wich they still are. And then all of the SCO Linux(tm) users are using Pirated software. A derivative work still has copyright protection for the person that created it derived from the original. It must be lisensed from BOTH parties. SCO can lisese their (alleged) code to their customers, but the terms they are implicitly giving remove their lisese to distribute Linux(tm).

      Linux is a trademark of Linus Torvalds

    6. Re:GPL doesn't help here!! by Citizen+of+Earth · · Score: 1

      The most sickening thing is that it sounds like SCO really doesn't want the (hypothetical) code removed. They want to convince a court that somehow IBM's AIX contract gives them ownership of anything that happens to have Unix code in it, and this overrides anyone else's copyrights, even if they wrote it, Linux as well s Dynix and AIX.

      Me no lawyer, but it would seem to me that IBM contributed the code to Linux under the GPL license. In the slim chance that IBM was demonstrated not to have had the right to do that, then that granting should logically be undone with no 'infection' of the Linux kernel by SCO's nebulous 'all your OS' theory.

    7. Re:GPL doesn't help here!! by iabervon · · Score: 2, Interesting

      If SCO gives out a license to anyone, the license must be GPL-compatible; otherwise SCO is violating the terms of the GPL, which give them the only right they have to distribute Linux at all, and they are suddenly the world leader in software piracy, selling commercially a large number of pieces of software by even more copyright holders. If they're saying that 50 lines of code are worth $3 billion, they'd be in a position even MicroSoft couldn't bail them out of.

      If they do give their users a legimitate license to the code, their users can use other distributions if desired, and can pass this license on to anyone else.

      Of course, they could simply stop distributing anything licensed to them under the GPL. They've said they're not going to continue selling Linux, but they are still offering it (and updates) for download currently. They could claim that they were doped into distributing their code with GPL code, but it would be hard for them to claim that the still don't know, and the current situation is not viable for them with respect to the GPL.

    8. Re:GPL doesn't help here!! by Dalcius · · Score: 4, Interesting

      This is ridiculous.

      "If the Linux kernel is a derivate work of SCO's (or more likely, certain PARTS of the kernel are derivative works), then SCO can simply claim that ALL copies of the Linux kernel are infringing copies, and ALL public distributions of the code are copyright violations."

      The Linux Kernel is a work owned by many people; the copyrights belong to no one person. To declare that, "Well, since this code was added to the kernel, the entire kernel is now in violation and belongs to us" is ridiculous. SCO may sue for damages of the code used (IF it exists, which is sketchy at best), and then it will be removed (IF they ever explain what code that is -- if not, any judge with two brain cells is going to force them to or drop the suit). End of story.

      ---
      "The GPL simply falls by the wayside, since the copyright holder (SCO) NEVER INTENDED to distribute the code. It doesn't matter that they were already distributing it, they can argue that they were duped into distributing it because they didn't know what was in it."

      Another idiocy, except I can't put it past the courts to not blame SCO on this one. Still, the Linux code that SCO distributed still belongs to the copyright owners who have deemed that the code is not to be distributed unless all attached code is GPLed. SCO, willingly or not, either published their code under the GPL, or violated the IP of hundreds of developers.

      --
      ~Dalcius
      Rome wasn't burnt in a day.
    9. Re:GPL doesn't help here!! by Anonymous Coward · · Score: 0

      There's just one problem with this theory...

      If Linux is not a GPL'd product, but an unauthorzed derivation of SCO's IP, then what is the status of the Non-SCO IP that is included in SCO's linux distro?

      It would seem fairly evident under your argumnet that those rights would belong to the their creators, who would therefore be legally entitled to have them pulled from the work.

      As you said, the GPL does not have any magical power to bestow freedom on somebody else's code, that applies to SCO as well, the GPL deosn't entitle them to "liberate" any one else's code

      All this tactic does is shift them from being infringed, to infringing...

      SCO's customers may not have anything to fear from SCO, but SCO may not be the only one to fear..

    10. Re:GPL doesn't help here!! by Dalcius · · Score: 3, Interesting

      Another interesting point:

      Based on their original (albeit vague) allegations, how can SCO claim that they didn't know that they distributed their IP under the GPL when IBM can claim the same ignorance?

      --
      ~Dalcius
      Rome wasn't burnt in a day.
    11. Re:GPL doesn't help here!! by canadiangoose · · Score: 1
      They can't argue that they didn't know the code was in there. If they think Linus needs to pay attention to where he is getting code submissions from, don't you think that SCO should be responsible for verifying the origin of any code that they are distributing?

      Talk about the pot calling the kettle black.

      --
      Never eat more than you can lift -- Miss Piggy
    12. Re:GPL doesn't help here!! by jmv · · Score: 4, Insightful

      The question to SCO here is quite simple: "do you agree that the Linux distribution you released is placed on the GPL, letting the users modify/copy it at will?". If the answer is yes, then case closed (they just gave up their IP - if indeed SCO IP there was, which I doubt). If the answer is no, then SCO wasn't allowed to distribute Linux in the first place. This puts them in copyright violation over millions of lines of code (not GPL violation - they didn't agree to the GPL, so they're re-distributing under no valid license). Talk about "IP theves"!

    13. Re:GPL doesn't help here!! by nathanh · · Score: 1
      The GPL is simply a means for a copyright holder to grant others the right to copy under certain circumstances. It can't "force" anyone to do anything.

      Correct. The GPL can't force anybody to do anything. But if SCO doesn't agree to the GPL then they have no rights to distribute Linux at all. This includes all the drivers that SCO didn't write. The filesystems. The USB stack. Anything that is provably not SCO's. Even if SCO is right and some parts of the kernel are owned by SCO, this does not extend to *all* of Linux. For example, I have contributed to the kernel (just a handful of lines). If SCO doesn't agree to the GPL then I won't grant them the right to distribute my code. They are guilty of copyright infringement.

      Multiply this by 10s of 1000s of developers and SCO is cruising for a lawsuit the likes of which God has never seen.

    14. Re:GPL doesn't help here!! by eyez · · Score: 1
      The GPL simply falls by the wayside, since the copyright holder (SCO) NEVER INTENDED to distribute the code. It doesn't matter that they were already distributing it, they can argue that they were duped into distributing it because they didn't know what was in it.

      Duped?! From what I've read, SCO claims they've known about the violations for over a year. The fact that they didn't IMMEDIATELY stop distribution of the GPL'd code with their code in it made it so that they were KNOWINGLY AND WILLINGLY distributing their code in a GPL'd project. That claim is down the toilet.

      What SCO's trying to claim is that since they own some code that was added in to linux, They have an immunity from the terms of the GPL. That it somehow doesn't apply because they own a minor portion of the code in linux.

      It really just seems like they're trying to claim ownership of the Linux Kernel now.

      --
      get 0wned. irc.w30wnzj00.com
    15. Re:GPL doesn't help here!! by Anonymous Coward · · Score: 1, Insightful
      The GPL simply falls by the wayside, since the copyright holder (SCO) NEVER INTENDED to distribute the code. It doesn't matter that they were already distributing it, they can argue that they were duped into distributing it because they didn't know what was in it.

      Your Honor, I didn't know the gun was loaded

      I am sorry honey I didn't think I was fertile

      These lame excuses will not absolve you of responsibility for your actions.

      SCO sold a Linux distro. They did that intentionally. The gun was loaded. He was fertile.

      I have no idea why they did it and I do not see why I or anyone else (including a judge) should give a rat's petunia what their subjective beliefs about their actions were.

      They are in the software business, they know what source code is, they had (or had easy access to) the source code and they were in a better position than anyone else in the whole wide world to know if the code contained material that they thought was theirs. And yet, they INTENTIONALLY sold it under the GPL.

      Now, I do not know whether the GPL will prove to be legally binding in every aspect. But, even if every clause is not valid, it must at least operate as a waiver of copyright in the material subject to it.

      IMHO and IAAL, SCO has at the very least waived any infringement claim on code it sold under the GPL. I think they and their lawyers know that and that is why they sued IBM for breach of contract and why they did not start by suing Red Hat or Linus Torvalds.

      'nuff said

    16. Re:GPL doesn't help here!! by tlk+nnr · · Score: 1

      So if there is violating code, SCO has no right to "bless" redistribution unless they agree to non-GPL licensing terms with EVERY SINGLE KERNEL DEVELOPER who contributed non-offending source.

      I think blessing is possible:
      Party A distributes a GPL program and mentions that you need an additional license to actually run it. Party B sells the license.
      One example is LAME - souce is LGPL, but you need a patent license from Fraunhofer/Thompson to use it.
      SCO (==party B) could request a license fee from customers of Redhat (==party A) for running Linux. SCO would not violate the GPL in doing so - they are not distributing the Linux kernel, thus they are not bound by the GPL.
    17. Re:GPL doesn't help here!! by Anonymous Coward · · Score: 1, Interesting

      This is exactly what I wrote SCO last week. Back in 1999 I wrote a part of the USB functionallity which can now be found in Linux. It was developed independently from Linux and then integrated by some third party (not me) after I released it as GPL. SCO has distributed and used this code for years, but if the 2.4 kernel they use contains non-GPL code (as they claim), embedding my code into "their kernel" is an infrindgement of my copyright. It doesn't matter if they integrated my code, or somebody else already did before them. From my perspective, they use my GPL code in their non-GPL product and make lots of money with it. That makes them legally liable. SCO has been notified by me about this and I asked them to start licensing negotiations with me immediatly (obviously their use is not covered by the GPL, thus they need a dedicated license from me, covering all past and future use of my intellectual property). They have not responded so far, which is no surprise. I am currently looking for a lawyer and a sponsor to take them to court. I encourage all Linux copyright holders to do the same.

    18. Re:GPL doesn't help here!! by Error27 · · Score: 1

      >>you can't use the other 30000 lines of code because SCO's codes is not GPL'd

      The kernel is a hundred times larger than that. I haven't counted, but I've heard that 2.5 is almost up to 5 million lines of code. Every month kernel developers write or modify around 50,000 lines of code.

      SCO can take their 83 lines of code and put it where the sun don't shine.

    19. Re:GPL doesn't help here!! by Anonymous Coward · · Score: 0

      For a very long time, SCO has distrubuted code, Linux code, which contains a file called COPYING. This is the GNU General Public License. This means that SCO is granting permission to use it under the terms of the General Public License.

      I don't know how anyone could interpret it any other way. Well, I see it, but it's hard.

    20. Re:GPL doesn't help here!! by Anonymous Coward · · Score: 0

      Please read the GPL - if there is infringing (GPL-incompatible) code in the Linux kernel, the entire kernel cannot be distributed until the infringing code is removed.

      This doesn't give SCO ownership, but it certainly is a correct description of the consequences.

      For those too lazy to look it up themselves, the relevant portion of the GPL (and note that it applies to copyrights as well as to patents - but at the time of the writing, the accidental inclusion of GPL-incompatible code wasn't considered as a possibility):

      7. If, as a consequence of a court judgment or allegation of patent
      infringement or for any other reason (not limited to patent issues),
      conditions are imposed on you (whether by court order, agreement or
      otherwise) that contradict the conditions of this License, they do not
      excuse you from the conditions of this License. If you cannot
      distribute so as to satisfy simultaneously your obligations under this
      License and any other pertinent obligations, then as a consequence you
      may not distribute the Program at all. For example, if a patent
      license would not permit royalty-free redistribution of the Program by
      all those who receive copies directly or indirectly through you, then
      the only way you could satisfy both it and this License would be to
      refrain entirely from distribution of the Program.

    21. Re:GPL doesn't help here!! by geoff+lane · · Score: 1

      Sorry, SCO is screwed. If they, themselves, distribute a product that contains their trade secrets in plain sight, then there is NO legal way to get their secrets back. Neither can they sue others for using those secrets.

      Trade secrets depend on the holder keeping the secret. Going to a court and asking "We told everybody the formula for Coke by accident, will you now stop everybody from making it for themselves?" is likely to get the lawyers fined for wasting court time.

    22. Re:GPL doesn't help here!! by wagemonkey · · Score: 1
      You could try negotiating some deal with IBM to 'lend' you some legal help - or point you at a friendly lawyer. IBM seem to be solid over this case, but I'm sure even big blue would smile at SCO dying the death of a thousand cuts if they're sued over this stuff by the kernel devs.

      I was wondering how much money SCO have - they could be bankrupted just by the discovery phase of this case - I vaguely recall an IBM case where they wre required to produce all the documentation related the work of one employee - I think it was several tons of paperwork. I sometimes wonder if IBM gave lessons on paperwork to government - they basically buried the case in manuals until it went away, I wish I could remember the details. It may even have been the anti-trust trial, which died of old age.
      If SCO want all IBM employee email for the last three years then just print it out and deliver it in a few semis.

    23. Re:GPL doesn't help here!! by MadJo · · Score: 1

      If they really cared about their Linux customers, they would flag the (alleged) offending code immediately and, if not replace it themselves, at least alert the kernel developers, so that a legal fix could be released.
      Nice idea, and great solution, however, SCO won't gain anything with it. Why else would everyone who has given access to review the violating code need to sign a NDA?
      If SCO would flag the alleged offending code, they would in fact say that the NDA is void, and also that way every programmer working on the kernel can erase and replace the reason for the lawsuit SCO is now planning against IBM.

      I would like to see this solution, but I'm afraid it won't happen in the near future.

    24. Re:GPL doesn't help here!! by spotteddog · · Score: 1

      "The GPL simply falls by the wayside, since the copyright holder (SCO) NEVER INTENDED to distribute the code. It doesn't matter that they were already distributing it, they can argue that they were duped into distributing it because they didn't know what was in it."

      SCO can't claim they did not know what was in Linux and still hope to hold customer confidence - if they do they admit they sold customers a product (which they claim to produce portions of) without performing *any* due diligence with respect to the product.

      Essentially they would be saying, "here is a computer program, run it, we don't know what it does. Have a nice day."

      I think once SCO *sold* its first copy of Linux, and included the source code, they lost the ability to claim they did not intend to distribute the code.

      If they redistributed kernels patched with their IP - tough; they should have checked the source *before* **they** distributed it.

      --
      . there used to be a sig here.....
    25. Re:GPL doesn't help here!! by hobsonchoice · · Score: 1

      I don't know if this works for you, but maybe you can transfer your copyright to somebody who is interested in enforcing your rights (FSF?), or get a lawyer to take it on contigency.

      If I were you, I'd keep very good records of all your communications with SCO as well as a diary of any day to day events which may be relevant.

    26. Re:GPL doesn't help here!! by hobsonchoice · · Score: 1

      One other thing I forgot. If you are sending letters to SCO, I don't see why you couldn't keep IBM informed about it (ask your lawyer about this)

    27. Re:GPL doesn't help here!! by schon · · Score: 1

      The GPL simply falls by the wayside, since the copyright holder (SCO) NEVER INTENDED to distribute the code

      Perhaps, if SCO had actually ceased distributing Linux.

      The fact is, they are still distributing it, nearly three months after they found "their" code in the kernel.

      Care to explain to me how they "never intended" to distribute it, if it's still available?

      they can argue that they were duped into distributing it because they didn't know what was in it.

      But now they do know what's in it. Are they going to argue that they are being "duped" into continuing to distribute it?

    28. Re:GPL doesn't help here!! by hobsonchoice · · Score: 1

      With all due respect, if you think SCO is infringing your copyrights, it is likely to have little practical effect unless you enforce your copyrights in court.

      If you think SCO is infringing your copyrights, have you told them (and kept records of it)? Are you planning any legal action to enforce your copyrights? Have you hired a lawyer? Are IBM aware of your issue?

      I'm not bashing you, but if you take no action except complain here, from the outside world's perspective it'll just be one more disgruntled geek preaching to the choir.

    29. Re:GPL doesn't help here!! by Karrick · · Score: 1
      jmv's point is the kicker of all kickers...

      In redistribution of "SCO Linux" & "OpenLinux," SCO is required to yield IP claims of the whole of their respective distributions, including all improvements upon & contributions to, under terms of the GPL (GPL, Section 2c germain). Specifically, every bit of code used to create their distributions ("SCO Linux" & "OpenLinux") was required to be released under the GPL in order for SCO to legally distribute those distributions. Additionally, if in fact the above software distributions do contain the same IP that they now contest in court as stolen, then SCO's case for contention was invalidated by their very release of said code to the public under terms of the GPL. SCO's provision to their Linux business partners has no bearing on this case. The mere fact that they already yielded IP rights of the code to the GPL when they redistibuted the Linux kernel makes their case a moot point. You can not sue someone for taking something which you already gave them for free.

      The court's fact finding phase would reveal whether SCO's release of Linux distributions also contain the contested IP, and if so, mitigate their claims against the Linux community.

      Karrick S. McDermott

      --
      -=-=-=-=-=-=-=-=-=- "Ask not what your computer can do for you, but what *you* can do for your computer."
    30. Re:GPL doesn't help here!! by nathanh · · Score: 1

      There's no value in me complaining because I'm from a different country and have very little code in there. I was just using myself as an example of the legal issues involved here; it's not a simple case of SCO owning *all* of the Linux kernel. There are a number of copyright holders. People with more code and US citizenship can do the suing. I'll enjoy the spectacle from where I sit.

  22. RTFGPL by Citizen+of+Earth · · Score: 5, Interesting

    must be freely released to any and all. It appears that all Linux users everywhere were just given a license to continued use of Linux even if SCO would win their suit with IBM.

    That's not what it means. Nobody can unintentionally make their software GPL through 'infection'. Instead, it means that SCO has just formally violated the GPL and should now be sued for copyright infringement by anybody and everybody who owns copyrights to any part of the Linux kernel. In particular, Linus could generate lots of press by suing SCO for copyright infringement. He might get some good coin out of it too; $3.1-billion ought to do it.

    1. Re:RTFGPL by eyez · · Score: 1
      Instead, it means that SCO has just formally violated the GPL and should now be sued for copyright infringement by anybody and everybody who owns copyrights to any part of the Linux kernel.

      Even further, the GPL has a clause that says breaking the GPL is grounds for losing your license to the GPL; SCO doing this is enough to make it that, sure, those people won't get sued by SCO, but that SCO has now lost THEIR license to distribute the Linux Kernel-- Forever.

      And unlike the IBM->at&t unix contract, it the GPL plainly states in nice clear letters, that it *IS* revocable.

      --
      get 0wned. irc.w30wnzj00.com
    2. Re:RTFGPL by Rogerborg · · Score: 1

      > the GPL has a clause that says breaking the GPL is grounds for losing your license to the GPL;

      Quote that clause. It's not there. All the GPL version 2 talks about is ongoing conditions, not conditions in perpetuity, which is one of its big problems.

      --
      If you were blocking sigs, you wouldn't have to read this.
    3. Re:RTFGPL by Anonymous Coward · · Score: 0

      >Even further, the GPL has a clause that says breaking the GPL is
      >grounds for losing your license to the GPL; SCO doing this is enough
      >to make it that, sure, those people won't get sued by SCO, but that
      >SCO has now lost THEIR license to distribute the Linux Kernel--
      >Forever.
      >
      Not only to the Linux Kernel. This applies to GCC and it's assorted libs and everything else that's been placed under the GPL and similar licenses by the FSF and other people. For example SCO could be forbidden to make use of or ship *ANY* version of Mozilla

    4. Re:RTFGPL by spitzak · · Score: 1
      You have that wrong. Nowhere in the GPL does it say it is revocable or any such clause like that. I am curious what wording you see as saying this, please quote it.

      Most importantly: such a clause is illegal without a signed contract. This is the same reason most clauses in unsigned EULA's are probably unenforcable. Otherwise people could put code into the "public domain" (ie even more free than the GPL) and then "revoke" it many years later after it is in every product (open or closed).

      What they lose is the ability to redistribute the code as long as they make their current claims. Their claim that their customers are ok, while others (including those who copy the customers code) are not ok, this means their distribution is not GPL because copying is not allowed. Now unless SCO is claiming they wrote 100% of Linux, some portions of it they got from outside authors, who gave it to them under the terms of the GPL, which says that code may not be redistributed unless the GPL applies to the redistribution. By redistributing it and ignoring the rules, they are violating the copyright of all authors (other than themselves :-) ) of Linux. This is the copyright of literally thousands of people and organizations, including Linus and all other big-name kernel hackers, and IBM and nVidea and Oracle and many other companies.

      If SCO suddenly changed their plans, and either removed their code or released it GPL or public domain, they could then continue to distribute copies of Linux, without any violations of the GPL. It is not "revoked" in any way.

      They may still be liable for copyright violations for the previous releases of SCO Linux. However in the same vein if there really is stolen SCO code in Linux then the person who did that is also still liable for copyright violations, even though the code has been removed.

    5. Re:RTFGPL by Karrick · · Score: 1
      GPL, Section 4:

      4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

      emphasis mine...

      Karrick S. McDermott

      --
      -=-=-=-=-=-=-=-=-=- "Ask not what your computer can do for you, but what *you* can do for your computer."
    6. Re:RTFGPL by spitzak · · Score: 1
      I believe this is attempting to say you cannot redistribute an otherwise ok GPL version if you at the same time are violating the GPL on that code. If you stop infringing the GPL you are then free to distribute the code again. So this is a bit of extra punishment for violating the GPL. Ie if RedHat did something to violate the GPL on Linux, they would lose the rights to sell their copy of Linux, even though otherwise that copy of Linux is completely in the clear. However if RedHat then corrected their violation, I believe that they would get the rights to distribute Linux back. IANAL but this sounds a little bogus to me as one illegal action should not be able to make an otherwise legal action that is totally independent suddenly illegal.

      I also think your reading of this would violate RMS's and FSF's goals. According to your reading of this, one mistake by a company would prevent them from ever releasing their code GPL. So in my RedHat example they would never be allowed to distribute Linux ever again, thus shutting off a very productive and useful source of GPL code, and RedHat might as well go into the closed-source business. I seriously doubt this matches the FSF's intentions at all, so for that reason I don't think this revokation works as you think.

    7. Re:RTFGPL by Karrick · · Score: 1
      First of all, I think you and I basically agree on these several points. You merely asked for a quote of the text, and I provided it for the viewing pleasure of the eternally geeky...

      Second, I believe we both agree that the GPL is clearly a "per-Program" based license. In other words, by violating the GPL on one software item, a given company is forbidden from continuing to distribute that particular program. The company still may, however continue to distribute other GPL-governed software, contingent upon their ability to fully satisfy the conditions of the licenses in respect to those software items.

      Third, your most recent comments must be in response to someone else's prior text and not mine. Tracing back the chain, it is apparent that my contribution to this thread consists entirely of my quote of Section 4 of the GPL, and the phrase emphasis mine.

      Karrick S. McDermott

      --
      -=-=-=-=-=-=-=-=-=- "Ask not what your computer can do for you, but what *you* can do for your computer."
  23. here's a tip for SCO by ruebarb · · Score: 1

    fire your lawyers and PR people...

    whoever is giving you advice is getting paid by the hour, and doesn't care how stupid you look or how irrelevant your actions are...

    I can't believe this is even a professionally traded company. It feels like amateur hour around there.

    RB

    --

    ----------
    ah honey, we're all resplendent - Bill Mallonee
  24. IP != Copyright by DarkMan · · Score: 5, Informative
    From the header: If they approve the use of 'their' IP in Linux in a single kernel, then the GPL holds that IP SCO allows to be used by a select few must be freely released to any and all. It appears that all Linux users everywhere were just given a license to continued use of Linux even if SCO would win their suit with IBM.


    No, emphatically not.

    GPL applies to copyright'ed materials only. If SCO have other form of IP protection (such as patent, or, as they in fact claim, trade secret) the the GPL does not even interact with it. And see below.

    Further, it is possible for SCO to liscence their copyrighted code such that all thier customers may use it. That does not make it GPL'd.

    The GPL only applies upon redistribution - it is quite valid for me to link in code written under any sort of liscence to the Linux kernel. However, I may not freely redistribute it unless I can meet all the restrictions on it. From the GPl, section 7:

    If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all.


    Granted, it is talking principly in terms of patent liscencing, but that's inconsequential.

    As a case in point, conside the NVIDIA binary drivers. If you have an NVIDIA card, you have a liscence to use that copyrighted code. You do not have a liscence to re-distribute NVIDIA's code. Yet you may link the two systems together, just fine, provided you don't try to redistribute the combined work.

    Now, SCO redistributing binaries from their ftp site, _after_ they make claims about thier code being in Linux is a whole different kettle of fish. That's a different issue however.
    1. Re:IP != Copyright by Anonymous Coward · · Score: 0

      It comes down to this, did ANYONE buy SCO Linux in the two week window after they announced that they knew of these violations.

      If so, they hold legal GPL code ..they can distribute it .. and I hope they do (SCO will probably discourage them somehow).. if there are any ppl.

    2. Re:IP != Copyright by dh003i · · Score: 1

      Your right, IP doesn't equal copyright, but SCO has basically admitted that they distributed whatever code they could be talking about under the GPL. Thus, they have to allow individuals to freely distribute all the code they released when they released their own GPL'ed version of GNU/Linux ,and freely distribut any derivatives. This means that they can't make the kidn of claims they're trying to make.

      Either that, or they are in violation of the GPL, which means everyone who owns GPL'ed code in GNU/Linux can sue them. The damages against SCOX for each violation -- particularly the major ones -- could range in the billions, and would the totality of all of those violations would surely bankrupt them. Anyone inheriting their IP who attempts to do the same that they did would also be in violation of the GPL, thus also liable for billions.

    3. Re:IP != Copyright by bear_phillips · · Score: 1
      What about section 3b of the GPL

      # b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,



      Wouldn't that mean that code that SCO distributed in the last three years must be made available?

      --
      http://www.windmeadow.com/
    4. Re:IP != Copyright by Anonymous Coward · · Score: 0

      Nice idea, but when this gets to court in 2007, nobody is going to care about some 2 week window.

    5. Re:IP != Copyright by sholden · · Score: 1

      Only if they used the written offer option, as opposed to providing the source with the original binaries (and providing it for download at the time of downloading the binaries is good enough I seem to recall - ie. having linux-binaries.tgz and linux-source.tgz as two seperate downloads side by side is the same is if they were in one download (but saves those who don't want the source the bandwidth)).

    6. Re:IP != Copyright by Svartalf · · Score: 1

      If it's not Copyright, it's Trade Secret or Patents, yes. Problem is, SCO doesn't have any applicable patents to their name (key thing for them to do ANYTHING regarding patents...) and if it was a Trade Secret, having it put into the kernel just blew the Trade Secret status all to Hell.

      You can ask for subsequent royalties if it's Copyrighted.

      You can ask for past, present, and future royalties if it's a Patent.

      You can license a Trade Secret as long as it's one, but if someone "oopses", you can sue the person that screwed up, but you can't ask anyone else for licensing as it's no longer your IP.

      The best they can hope for is that they have a Copyright case here, because anything else is a foregone conclusion against them.

      --
      I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
    7. Re:IP != Copyright by Rogerborg · · Score: 1

      >Only if they used the written offer option, as opposed to providing the source with the original binaries (and providing it for download at the time of downloading the binaries is good enough I seem to recall

      Depends on the interpretation of "accompanying" ("Accompany it with the complete corresponding machine-readable source code"). I'd interpret that as meaning bundled into a single tar rather than just available (which is clause b). IANAL, and more importantly I haven't asked a lawyer to look at this specific clause of the GPL.

      --
      If you were blocking sigs, you wouldn't have to read this.
    8. Re:IP != Copyright by sholden · · Score: 1

      I'm going by what the FSF have stated is their interpretation. Which of course isn't binding in this case since they aren't the copyright holders let alone a court, but it seems good enough for me...

    9. Re:IP != Copyright by Rogerborg · · Score: 1

      Fair enough. I wonder if that's predicated on a good faith interpretation of the GPL though. That's pretty much the opposite of the way SCO view it.

      --
      If you were blocking sigs, you wouldn't have to read this.
  25. Silly SCO by MalleusEBHC · · Score: 3, Funny

    I guess we know where all the 2449 votes for "GP-who?" came from now.

  26. Not really by Anonymous Coward · · Score: 4, Informative

    "If they approve the use of 'their' IP in Linux in a single kernel, then the GPL holds that IP SCO allows to be used by a select few must be freely released to any and all. It appears that all Linux users everywhere were just given a license to continued use of Linux even if SCO would win their suit with IBM."

    Unfortunately, this may be false (IANAL etc.) because SCO can say that "credit" their liability. That is, if the court finds that their IP was stolen and all Linux users must pay $1000 to SCO, SCO can simply credit their own customers as having "paid up" as it were. Now the interesting issue is this .. the software was licensed under GPL. Will SCO be able to _change_ the license terms (if not any existing SCO linux customer can cut & paste and recontribute their code back to Linux). Especially after issuing this statement of saying they will ensure their customers are unharmed. I would consider being revoked and then given shitty license terms as harmed. Dont know about the courts.

    1. Re:Not really by AJWM · · Score: 1

      That is, if the court finds that their IP was stolen and all Linux users must pay $1000 to SCO, SCO can simply credit their own customers as having "paid up" as it were.

      And if this happens, SCO isn't living up to the terms of the GPL and is immediately in copyright violation on every copy of Linux it has distributed, since it distributed the other contributers' code without a valid (ie, GPL) license.

      Each and every copyright holder of Linux code distributed by SCO then launches an infringement suit against them -- ideally in as many different jurisdictions as possible (to keep their lawyers very busy).

      --
      -- Alastair
    2. Re:Not really by dmaxwell · · Score: 1

      SCO can go ahead and distribute the kernel that way. They can even weasel a judge into blessing it for them. There's only two problems: the 3 million or so lines of code they didn't write and the 300 or so hacked off developers who hold the copyrights on that.

      They already had a target pasted to their balls. Now they added flashing neon to it.

    3. Re:Not really by zangdesign · · Score: 0, Troll

      The primary agency to sue SCO would be the FSF, since Stallman wrote the GPL. I really doubt that Linux dev's would see a cent from this, but Stallman would be incredibly rich all of a sudden.

      Damn, I need a few more acronyms to make that totally incomprehensible.

      --
      To celebrate the occasion of my 1000th post, I will post no more forever on Slashdot. Goodbye.
    4. Re:Not really by Anonymous Coward · · Score: 0

      no. the FSF doesn't hold the rights to the linux kenel. the primary agency to sue SCO would be whoever released tghe code under the GPL (class action suit?)

    5. Re:Not really by spitzak · · Score: 1
      Wrong! The Linux copyright was not assigned to the FSF. Linus himself owns the copyright on large amounts of it, I believe.

      The FSF owns the copyright on GCC and many of the command-line utilities. But as RMS likes to point out, the kernel is seperate. And SCO seems uninterested in attacking anything other than the kernel.

  27. That hole just keeps getting deeper by Trogre · · Score: 1, Funny

    So what do you reckon SCO's chances are of making it to their own "SCOForum" (17-20 August)?

    --
    "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
  28. It will soon be pronounced ... by puckhead · · Score: 3, Funny

    Eye-Bee-Em Linux

    --
    Watching Cowboy Bebop in my jammies, eating a bowl of Shreddies.
    1. Re:It will soon be pronounced ... by pyrrho · · Score: 1

      No, it'll be pronounced Ibum/Linux

      GNU/BM would just be wrong.

      --

      -pyrrho

    2. Re:It will soon be pronounced ... by Thing+1 · · Score: 1
      Or how about:

      Eye-Bee-Em Unix

      --
      I feel fantastic, and I'm still alive.
    3. Re:It will soon be pronounced ... by orbitalia · · Score: 1

      Actually as it's GNU/Linux, I've done a quick grep on this whole comments page and ... Not one person has called it GNU/Linux, I hope rms isn't reading this *grin*.

    4. Re:It will soon be pronounced ... by usotsuki · · Score: 1

      Technically, I would have to call it "Linux (GNU userland)".

      BTW, any "Linux (BSD userland)" distros? :)

      -uso.

      --
      Dreams, dreams, don't doubt dreams, dreaming children's dreaming dreams. Sailor Moon SS
  29. Exactly what constitutes a SCO customer by hillct · · Score: 5, Interesting

    To 'hold harmless' is far different than a grant of license. Although the analogy in the parent is somewhat misleading, the point is absolutely valid. Eseentially, SCO is agreeing to exclude customers of it's own linux distribution from any future legal action.

    The big question is, what constitutes a SCO customer? Must I have purchased SCO services with my download of the SCO linux distro, or can I simply make use of their distro to avoid the threat of legal action? How much of the SCO distro must I use?

    Perhaps I should install a few packages on each of my Linux boxes, so as to avoid the the threat of lawsuits.
    As I re-read this, it appears the letter is only directed to current and ongoing SCO partners. This suggests that possibly, not only would I have had to have purchase SCO services but I would have to continue to pay for SCO service contracts indefinately into the future. Then again, IANAL, so perhaps I have misinterpreted the legal implications of this letter.

    --CTH

    --

    --Got Lists? | Top 95 Star Wars Line
    1. Re:Exactly what constitutes a SCO customer by topham · · Score: 1

      Actually, not in this case (IANAL). They have indicated that their customers won't be held accountable to SCO... but that makes the code in question (all of it) a violation of the license under which it was distributed. Which means the users have NO right to run the code.

      Which actually means SCO is encouraging copyright infringment.

      I'm just not sure the whole thing is convoluted enough that someone could win if they took them to court over that...

      SCO really should be encouraging their customers to switch to a Unix-variant that has no legal issues outstanding. I suspect their own customers would lynch them for that though.

    2. Re:Exactly what constitutes a SCO customer by dammitallgoodnamesgo · · Score: 1
      SCO really should be encouraging their customers to switch to a Unix-variant that has no legal issues outstanding.
      If you believe SCO, then right now that's only OSX, Sun, and NT (well, yeah, you know what I mean with that last one). Even then, if I were a customer, with SCO's history I'd be concentrating on the right now
    3. Re:Exactly what constitutes a SCO customer by rodgerd · · Score: 2, Informative

      That's funny, because SCO have actually states only Sun is definitely OK, and there are questions around Apple and Microsoft.

      Either SCO are about to become the richest and most powerful company in the industry, or they're about to have something unpleasant happen.

    4. Re:Exactly what constitutes a SCO customer by KrispyKringle · · Score: 1
      Er, I think they just mean that they won't sue people for using SCO Linux. Presumably, if you are using Caldera and RedHat, you could be liable for the RedHat. Anyway, this applies more towards large commercial users who have made support contracts with SCO; for them, its a means of reassurance. SCO isn't about to start suing home users of Linux. So don't worry about installing Caldera on your home computers. If you didn't get a letter from SCO before, you probably, just a guess, slipped under the radar on that one.

      Which is a definite relief; I know when they were looking over the list of who to send those letters to, it was like, "RedHat, Boeing, Cisco, and John Smith of 42 Evergreen Lane, for his two desktops running Debian."

    5. Re:Exactly what constitutes a SCO customer by MickLinux · · Score: 4, Interesting

      So you're saying that since, 4 years ago, I went to LinuxMall and purchased 4 versions of Linux, including Caldera's, then they won't sue me. Well, that's nice.

      Nonetheless, I still contend that they are attempting to steal the work and IP of thousands of developers. That is wrong. That is theft.

      Maybe the proper answer would be open-source, distributed lawsuits. Like, 10000 individual lawsuits against SCO, all at once, in every venue imaginable. Each of which can be resolved by them signing away all rights to all GNU software, and aside from that can only be resolved through them either fighting or losing case after case after case. I mean, if getting their lawyer to each venue costs only $500+10 hrs, but the lawyer is charging $50/hr [unheard of cheapo], then each time the lawyer has to show up, that's $1000. $1000 x $10,000 = $10 Million, times the number of times the lawyer has to show up.

      I've picked my numbers low. SCO's legal fees could easily run into the billions, just for fighting the lawsuits.

      Therefore, distributed attacking penguins could concievably work. Just arrange things so that if you win, or if SCO gives up all rights to GNU, it stops there, and they don't hit any other bumps. Be a gracious victor: the point is not to go to war, the point is to get out of the war intact as quickly as possible, and stay out where possible.

      --
      Correct Horse Battery Staple: 72 bits of entropy. Enter "Correct H" into google. When it generates the phrase, that's
    6. Re:Exactly what constitutes a SCO customer by croddy · · Score: 2, Funny
      echo Caldera Linux Release 1 > /etc/caldera-release

      all fixed!

    7. Re:Exactly what constitutes a SCO customer by kfg · · Score: 3, Insightful
      "To 'hold harmless' is far different than a grant of license."

      This is absolutely correct.

      However. . .SCO did grant license at original aquisition, and made that license the GPL. You can find it right in the distro. They remain bound by it themselves.

      This is the legal Scylla and Charybdis that SCO is attempting to navigate between. This is why they have to keep making new clarifications of their position every day. As they turn in one direction they begin to come too close to the danger on one side, then when they turn back they come too close to the danger on the other.

      I think there's a general consensus that if they keep it up sooner or later they're going to go down the hole or get smashed on the rocks, there is no clear route through, other than somebody sending out the Coast Guard to rescue them with a sweetheart buyout deal.

      KFG

    8. Re:Exactly what constitutes a SCO customer by DarenN · · Score: 1

      I'll take B) Have Something Unpleasant Happen for a dollar

      Seriously, though, SCO look like they're heading for the most almight kick in the coporate stones. And at this point, I'm starting to wonder what they think they're at. It's almost certain that any code in the kernel that SCO _might_ be able to claim is so minimal that claiming any loss would be laughable. I'm not even going to bother backing that up with links, because they're scattered all over the previous weeks.

      They seem to be adding to the hype and adding to the hype and eventually it's all going to implode.
      Well, at least it'll make brief entertainment after all the pissing off

      --
      Rational thought is the only true freedom
    9. Re:Exactly what constitutes a SCO customer by Salo2112 · · Score: 1

      If done, it would be the largest DDOS attack in the history of Linux. ;-)

    10. Re:Exactly what constitutes a SCO customer by Kyoya · · Score: 1

      "Therefore, distributed attacking penguins could concievably work. Just arrange things so that if you win, or if SCO gives up all rights to GNU, it stops there, and they don't hit any other bumps. Be a gracious victor: the point is not to go to war, the point is to get out of the war intact as quickly as possible, and stay out where possible.
      "

      Why do I see several thousand little pengiuns carrying a missle strapped to their back waddling their way across Utah with this line.

      In all seriousness I don't know how effective this would really be. In my estimation the US system would instinctively side with SCO in each of these cases. The mindset to be on the side of big business is ingrained in every politico's head.

      Now maybe if this were to be done in places were politicians still seem to understand they run things and not the guys in the Fortune 1000 companies.

      --
      To strive, to seek, but not to yield
    11. Re:Exactly what constitutes a SCO customer by Anonymous Coward · · Score: 0

      Thousands of lawsuits against SCO? There's a word for that: it's called "barratry."

      It's the same sort of tactic that SCO is employing, only on a larger scale. It's unethical and illegal.

    12. Re:Exactly what constitutes a SCO customer by DustMagnet · · Score: 1
      This is why they have to keep making new clarifications of their position every day. As they turn in one direction they begin to come too close to the danger on one side, then when they turn back they come too close to the danger on the other.

      This is the best description/analogy I've heard of for this whole mess. It makes you wonder if there goal is anything but pump and dump.

      The one thing they do seem to understand is that they need to keep this all as talk. Each legal action they take might brings them closer to the fall, so they are streching those out as far a possible.

      --
      'SBEMAIL!' is better than a goat!!
    13. Re:Exactly what constitutes a SCO customer by Stephen+Samuel · · Score: 1
      but that makes the code in question (all of it) a violation of the license under which it was distributed. Which means the users have NO right to run the code.

      Er, um no. This means that SCO is in violation of the license. Under the GPL the users continue to have the right to use and distribute the code in question.

      If SCO is claiming that they're distributing code that the GPL doesn't allow them to distribute, then it's only SCO who is violating the GPL.

      --
      Free Software: Like love, it grows best when given away.
    14. Re:Exactly what constitutes a SCO customer by usotsuki · · Score: 1

      *BSD?

      We know that's in the clear.

      (btw anyone know any BSD userlands for Linux?)

      -uso.

      --
      Dreams, dreams, don't doubt dreams, dreaming children's dreaming dreams. Sailor Moon SS
    15. Re:Exactly what constitutes a SCO customer by DavidTC · · Score: 1
      Um, it's not barratry if there's grounds for the case. Barratry is threatening cases with no legal merit, or filing them, and can't apply if you have good legal grounds.

      Both SCO's customers and any contributer to the kernel have perfectly valid reasons to sue SCO...the customers were lied to that they would be able to distribute the product under the terms of the GPL, and the contributers because SCO distributed their code without permission. (Which ironically gives the customers yet another thing to sue about...they are using code they have no permission to have, and are liable to be sued at any point in time by kernel contributers!)

      SCO can fix both problems with a recall of OpenLinux, but that would utterly bankrupt the company. (Which is not a valid reason, under law, not to do it.)

      --
      If corporations are people, aren't stockholders guilty of slavery?
    16. Re:Exactly what constitutes a SCO customer by topham · · Score: 1

      The GPL cannot grant a license to use code not covered by the GPL.

      Period.

      SCO claims, right or wrongly, that some of the code is NOT GPL, while the GPL requires that all of it be.

  30. It's sounds simple to me by klupo · · Score: 1

    "UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity."
    Dennis Ritchie.

    --
    "Talent does what it can; genius does what it must."
  31. Boycott SCO (eom) by Anonymous Coward · · Score: 0

    'nuff said.

    1. Re:Boycott SCO (eom) by Anonymous Coward · · Score: 1, Informative

      There are several calls for a boycott on the web.

      http://lwn.net/Articles/24757/
      http://www.carlu g.org/pipermail/carlug-discuss/200 3-March/001810.html
      http://lists.terrasoftsolutio ns.com/pipermail/yell owdog-general/2003-March/006325.html

  32. Re:Companies just don't get that GPL means busines by Citizen+of+Earth · · Score: 1
    couldn't understand beyond "those silly kids and their silly ideas" and later "those god damned subversive kids and their dangerous ideas..."

    ...then they laugh at you, then they fight you...

  33. Sick of SCO? by rosewood · · Score: 1

    I know that a lot of people are getting very sick of the SCO stories. Maybe they would consider a SCO catagory and thus a SCO filter.

    However, its not THAT bad. On top of that, this whole thing is just facinating. When the dust settles, whoever has been following this and knows some of the inside tracks could seriously write a killer book. The things going on in this case just blow my mind and today is yet another example.

    Just when I think I have heard it all...

    1. Re:Sick of SCO? by zuralin · · Score: 1

      OT but actually looking through the preferences they have a topic you can block labeled "Caldera", which just happens to have the same icon as all the SCO stories, and im pretty sure that's the "SCO filter" you're looking for.

  34. In Defense of SCO by Anonymous Coward · · Score: 4, Funny
    Every day I log onto Slashdot, and every day it's another story about how SCO is trying to destroy the Linux community. And comment after comment does nothing but attack SCO. I for one am getting tired of this. I think it's about time that somebody stood up and took stock of all that SCO has contributed to the world. So here, then, is my own personal account about how SCO has changed my life for the better.

    It was the winter of 1988, and I was a student at the University of California at Santa Cruz. One night, I went to the Wednesday juggling group, and I met this woman named Lynn. Lynn was in an on-again, off again relationship that at the moment was off again.

    Well, by the end of the evening, Lynn and I had a date to go hiking that weekend. We went out for a hike, and one thing led to another, and the next thing you knew we went back to my dorm and slept together.

    We continued on like this for a few weeks, merrily boinking away, and then I went away for spring break. When I returned, Lynn told me that she had gotten back together with her old boyfriend. It was no huge loss where I was concerned, and I was grateful for all the good times.

    Now how does this relate to SCO, you ask? Well, it turns out that Lynn worked for SCO. At the time, Santa Cruz had no technology companies to speak of. So it stands to reason that if it weren't for SCO, Lynn likely would have found work in some other town, and we would never have met.

    This is all a round-about way of saying that SCO got me laid. Which sort of pales in significance to who owns what lines of code or what licenses were or weren't handed out. Yet it seems the Slashdot crowd is obsessed with this technical minutia, and purposefully ignores all the great things that SCO has undoubtedly contributed to this world. Like getting me laid. So, people, please get it together and be a bit more objective about this great company.

    1. Re:In Defense of SCO by Anonymous Coward · · Score: 0

      I find your comment very strange.

    2. Re:In Defense of SCO by mcgroarty · · Score: 1
      Friend, you are living in the past.

      Today, all they would give you is goat.sco -- and I promise you that McBride doesn't like to be the woman. That's your job, my friend. A hello.jpg is YOU.

    3. Re:In Defense of SCO by Anonymous Coward · · Score: 2, Funny

      This is clearly a lie. No one who ever attended a "juggling group" ever got laid. Even in Santa Cruz.

    4. Re:In Defense of SCO by Anonymous Coward · · Score: 0

      Dude, you do know that Lynn used to be a guy, right!?

    5. Re:In Defense of SCO by Anonymous Coward · · Score: 1, Funny
      Oh no, you're screwed (no pun intended).
      • Did Lynn make you sign an NDA so you couldn't "sleep and tell"? Are you in violation now for revealing your experience?
      • I hope you didn't get her pregnant. She'd look at the kid, with 1/2 her DNA, and think of that kid as her own IP. She'd then find out the child also had 1/2 of your DNA, which she'd claim also as her IP by extension. Then she'd accuse you of stealing your kid's DNA and implanting it in your own body. Genetic testing and gene similarities would provide her the evidence to prove you stole your child's DNA.
    6. Re:In Defense of SCO by SoulDrift · · Score: 3, Funny

      It's a lucky thing that you and her didn't have any children... SCO might have tried to class them as derivative works.

      And then you'd be in a *whole* lot of trouble. ;-)

    7. Re:In Defense of SCO by raga · · Score: 1

      This is all a round-about way of saying that SCO got me laid.

      And now SCO is trying to get you screwed.

      cheers-raga

    8. Re:In Defense of SCO by Anonymous Coward · · Score: 0

      William, is that you ???

      Lynn

  35. Re:Companies just don't get that GPL means busines by Tim+Macinta · · Score: 4, Interesting

    Sure, it appears that they either don't understand or believe the GPL, but I doubt they are that dumb. I think what's going on is that they realize that they can't stop others from distributing Linux because they are still distributing it themselves (despite their claims otherwise), but they want to keep people from distributing it anyway, and spreading FUD like this is how they do it. Why do they want to keep people from using Linux if they would have a hard time legally enforcing it? They want to drive people from Linux to Unix because they believe that they can exert control over Unix. I believe that is their plan. They want to drive people away from what they can't control into the arms of the closest alternative, which they do plan to control.

  36. liable to whom by pyrrho · · Score: 2, Interesting

    they might not be liable for SCO IP, but what about all the GPL IP? SCO is ignoring the fact that the GPL does not apply if they ship royalty generating IP in their distro, so they cannot ship all that GPLed code. So their customers are now liable, instead, for GPL violations (although there may be obscure wiggle room for them based on the fact that it's really the act of copying that becomes prohibited, e.g. SCO is the violator).

    Linus, the FSF, and RMS should all SUE!

    --

    -pyrrho

    1. Re:liable to whom by danheskett · · Score: 1

      Linus, FSF, RMS sueing is bad, because in the long run it validates the idea that GPL is problematic legally.

      With proprietary systems from Sun or MS, there isn't this whole unpleasant nastiness (though there is loads of other nastiness, that's for sure). That'll be mercilessly pounced on if the other side countersues and it drags out for years or even decades. That was MS's rub for a long time (as well as Novell) - "our stuff isn't embroiled in day-to-day lawsuits".

    2. Re:liable to whom by Aussie · · Score: 2, Insightful
      Linus, FSF, RMS sueing is bad, because in the long run it validates the idea that GPL is problematic legally.

      Crap, suppose you buy a gun to protect your family and property. If someone throws a stick at your house would you shoot them ? How about if they try to kidnap your family and burn your house ? Would you shoot them then ?

      SCO is trying to kidnap our family and burn our property, it is time to use the most effective defense possible.


      Exceptional circumstances demand exceptional action.
    3. Re:liable to whom by 1lus10n · · Score: 1

      AIX = proprietary.

      and IBM is getting just as much shit about its AIX license as the whole linux thing ......

      the thing i find amusing in this is simple .... SCO claims linus doesnt "verify" his code. and exactly how the hell is he supposed to due that ? call up SCO and ask if is theirs ? wait for MONTHS for them to get back to him just so he can hear ..... "that code is ours we commited it yesterday. have a nice day." ? its not like their is some mythical place where all proprietary source code is kept so us OSS developers can double check that the code being sent to us isnt already patented/trademarked/copyrighted. and if there was we would get sued more, because companies could just say "he has access to code xyz. his product Can't be better than ours !! he mustv'e stolent the code !!! (TM SCO)"

      --
      "Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe." --Albert Einstein
    4. Re:liable to whom by JohnFluxx · · Score: 1

      damn your right - we should gang up and shoot all the employees!

      Oh, analogy right sorry - I'm bad at those

    5. Re:liable to whom by dipipanone · · Score: 1

      Linus, FSF, RMS sueing is bad, because in the long run it validates the idea that GPL is problematic legally.

      Well, any licence is problematic legally if you happen to violate it.

      My preferred option is *still* an amendment to the GPL that specifically excludes use by SCO and its customers. I'd love to hear SCO trying to explain to their customers how they can no longer use any of that communist Open Source software while they continue to use SCO products.

      OK, so I know that such a retroactive change, given the zillions of GPL contributors, would probably be impossible, but I can dream can't I?

    6. Re:liable to whom by Znork · · Score: 1

      So, if I obtain the sourcecode to Windows, add a few lines of code and sell it as my own really cool "Windows" I wont get sued by MS? Riiiight.

      That isnt a GPL issue, that's a copyright issue and it's the same if you try to distribute anyones software without the right to do so. It's exactly the same unpleasant nastiness wether it's proprietary or GPL.

      Of course, SCO's customers arent liable in any way for SCO's GPL violations. The GPL covers distribution, and unless those customers are distributing SCO's product they would not be in any trouble (if they were, they would have to be granted a GPL compatible license for SCO's code, or they would be infringing for the rest of the code tho). SCO themselves on the other hand would be forced to either distribute their code under GPL compatible terms or they would be infringing by distributing other peoples GPL code.

    7. Re:liable to whom by mpe · · Score: 1

      they might not be liable for SCO IP, but what about all the GPL IP? SCO is ignoring the fact that the GPL does not apply if they ship royalty generating IP in their distro, so they cannot ship all that GPLed code. So their customers are now liable, instead, for GPL violations.

      So long as SCO's customers don't violate the GPL they are in the clear. If SCO are distributing GPL code in violation of the GPL then they are guilty of copyright infringement.

    8. Re:liable to whom by laird · · Score: 1

      No, No, No. FSF suing doesn't show that the GPL is problematic, it shows that it is enforceable. Admittedly every GPL violater so far has backed down before the case has gone to trial, but if the GPL were enforced by a trial that would simple remove whatever perception that "the GPL is problematic legally" people opposed to the GPL have managed to project. I'd say that the fact that the GPL has never been challenged in court shows how effective it is...

      As for things being "embroiled in day-to-day lawsuits" you've been following the continual stream of lawsuits MS has been involved in, haven't you?

    9. Re:liable to whom by Stephen+Samuel · · Score: 1
      SCO made it clear that They want to own linux. Their spokesman said that Linux will no longer be free (if they have their way). I.e. they expect us to pay (them) for Linux.

      You can bet your bare ass that I'll be happy to support any attempt to drag them into and thru any court on this continent that'll flay their duplicitious ass.

      --
      Free Software: Like love, it grows best when given away.
    10. Re:liable to whom by pyrrho · · Score: 1

      yes, except that with royalty generating IP in linux the GPL doesn't apply. I would think they would have to stop using it, but if not literally, in effect, as they could not legally make a copy to, e.g., install on a new server.

      But anyway, I agree, it's SCO that is the clear violator and legitimate target for GPL based actions.

      --

      -pyrrho

  37. Wrong SCO by gotr00t · · Score: 3, Funny
    Actually, yes, that was the old SCO, the GOOD SCO. Then, they sold their UNIX assets to Caldera, and then Caldera called themselves SCO.

    So, the SCO back then was GOOD the SCO now is BAD

    Don't think that they're the same company cause they're not. It used to be about UNIX, now it's about using UNIX to sue people to earn profit.

    1. Re:Wrong SCO by master_twig · · Score: 1

      there SEEMS to be a tad FEW upperCASE letters in YOUR STATEMENT.

      I can just feel my mind thinking these words out really really loud.

      That sounds wierd, I'll shuttup now

    2. Re:Wrong SCO by MadCow42 · · Score: 1

      Exactly... as it happens, the management of the new SCO is coming close to getting laid too. Well, if you call getting reamed by IBM "laid", anyways.

      q:]

      --
      I used to have a sig, but I set it free and it never came back.
    3. Re:Wrong SCO by fanatic · · Score: 1

      Wrong poster. The old SCO sucked ass, too. Their product looked good wrt Windoze, but bad wrt real Unices. Their paid-for support sucked beig green donkey dicks.

      They were doomed from the instant Linux could boot.

      --
      "that's not encryption - it's a new perl script that I'm working on..." - from some Matrix parody
    4. Re:Wrong SCO by follower-fillet · · Score: 1

      > So, the SCO back then was GOOD the SCO now is BAD
      Ahh, so we're talking about high-speed SCO not full-speed SCO? :-)

    5. Re:Wrong SCO by mark-t · · Score: 1
      Exactly... as it happens, the management of the new SCO is coming close to getting laid too. Well, if you call getting reamed by IBM "laid", anyways.
      No... not laid. Screwed.
    6. Re:Wrong SCO by Anonymous Coward · · Score: 0

      As a Santa Cruzian, I would like to back up the "old SCO" argument and clear the name of the original Santa Cruz Operations from the current problems. We here at Santa Cruz are pretty pissed off.

      I've seen various mails going about the two LUGs (SLUGLUG and SMAUG) and the school of engineering at UCSC complaining about the asociation people make between the current SCO and the original Santa Cruz company.

      As anybody in Santa Cruz knows, our companies are organic, free-range, freedom loving, naked running, tofu eating, open minded, bi-curious, pierced, colorful, surfing, nature loving, drum circle dancing, clothing optional, GPL screaming hippies.

  38. SCO Trial by Billly+Gates · · Score: 3, Funny
    IBM Lawyer: The code in question is from AIX and not systemV. How can you claim ownership?

    McBride: My precious was birthday present YESS

    IBM Lawyer: What are you talking about?

    McBride: Its what has it got in my pocketses.

    IBM Lawyer: You do not even have the source code do you?

    McBride:Did we say so, precious? Cross it is, impatient, precious.

    IBM Lawyer: Your honor, since SCO can not even have the code they therefor have no ownership. I have the source code here and ....

    McBride: MY PRECIOUS! THEIF, theif IbM! We hates it FOREVER! My PRECIOUS!

  39. at war by pyrrho · · Score: 1

    General: "Corporal, the enemy is advancing, fire another round!"

    Corporal: "We can't sir."

    General: "Out of ammo?"

    Corporal: "no."

    General: "What is it then!?"

    Corporal: "We're out of feet."

    PS:

    General: "Well go for the knees--- ouch!"

    --

    -pyrrho

  40. Re:Companies just don't get that GPL means busines by Planesdragon · · Score: 2, Interesting

    ...then they laugh at you, then they fight you...

    And then you find out if you side has what it takes to win.

    Ghandi had the plight of the oppressed, the moral high ground, and the triple guilt of the Anglican White Empire.

    What does GNU have? Some sour grapes against software developers, and a license designed to turn copyright on its head.

    It's entirely possible that the concept of copyleft could be tossed out, as being an unfair infringement upon the innovation and artistic progress of others. It's also entirely possible that it'll be upheld lock stock and barrel.

    No one, AFAIK, has attempted to challenge the GPL and taken it to court. (If you know otherwise, please site case name and / or court.) Until that happens, it's a license that may have some or more parts of it removed.

    (For the GNUelots, the "entirely possible" would require a case getting to the Supreme Court.)

  41. Re:Companies just don't get that GPL means busines by Planesdragon · · Score: 1

    The GPL doesn't mean business. It means common ground and contractorship.

    The GPL, by design, will make it unprofitable to sell software sight unseen. If the GPL became dominant, software would be limited to an add-on provided by OEMs, contractors, and philantrophic coders.

    Before you call that a troll--if YOU could be paid $12000 (welfare) to stay home and code, with no boss and little-to-no prejudice against how you get the money, would you?

  42. SCO thinks the GPL is a joke by The_Dougster · · Score: 5, Interesting
    They seem to think that it is a bunch of malarky and they can walk all over it. Stallmann et. al. crafted the GPL so that they could write GNU's Not Unix from the very start. If you think that I would donate my free time writing programs so that SCO can steal them then you are sadly mistaken. Just like I don't help people at work who have problems with Windows even though I am an expert. If I were to donate my time helping somebody with Windows, then Bill Gates and Microsoft are essentially stealing my time for free. If somebody has problems I tell them to call the IT department or Microsoft Technical Support.

    Same deal with GNU software. I rely on the GPL to know that my code is going into the public pool. I do it as a hobby and I don't get paid for my time, so my one recompense is knowing that some jerks can't steal my hours of labor. I give them as a gift for all the world and that is good enough for me.

    When these "SCO" big-shots start attacking the GPL I take it personal, and so does anybody else who has written for Linux and GNU. I'm certainly not writing code to make SCO rich. They don't pay me, they don't like my "philosophy", well they can go piss up a rope because I'm getting tired of them walking all over the GPL like it somehow doesn't apply to them because they are "big-shots." Bullshit! They are a bunch of crack-heads if they think they can pull this swindle off. They got big balls, I'll give them that, but their big balls are gonna get kicked hard.

    --
    Clickety Click ...
    1. Re:SCO thinks the GPL is a joke by tshak · · Score: 3, Insightful

      so my one recompense is knowing that some jerks can't steal my hours of labor

      Well then you better reevaluate why you work for free - even if it's a hobby. Hypothetically speaking, Microsoft could very well be making money off of your labor. They could use your program, modify it for their own internal use, and never give anything for it while they reap the benefits of your software.

      --

      There is no longer anything that can be done with computers that is nontrivial and clearly legal. -- Paul Phillips
    2. Re:SCO thinks the GPL is a joke by The_Dougster · · Score: 4, Funny

      Yes but that gives me karma and takes away theirs... W00T!

      --
      Clickety Click ...
    3. Re:SCO thinks the GPL is a joke by rowanxmas · · Score: 0

      That was the best comeback ever!

    4. Re:SCO thinks the GPL is a joke by Aadain2001 · · Score: 1

      Then Microsoft would be in violation of the GPL. The GPL lets anybody on the face of the earth take something released under it and package it and sell it, but they are required to provide the source code for free to any and all who ask for it. That means that their "product" becomes only as valuable as the services they sell with it, which is fine by me since they would actually have to do something in order to make money. If Microsoft passed it off as their own and didn't release source code, well then they would be criminals wouldn't they.

      --
      Space for rent, inquire within
    5. Re:SCO thinks the GPL is a joke by Strudelkugel · · Score: 2, Insightful

      Just like I don't help people at work who have problems with Windows even though I am an expert.

      Which makes your co-workers think exactly what of Linux advocates...?

      --
      Imagine how much harder physics would be if electrons had feelings! -Feynman, maybe
    6. Re:SCO thinks the GPL is a joke by Anonymous Coward · · Score: 4, Informative

      Read parent again. Internal use means they don't give/sell/license the product to anyone, so they are not obligated to provide the code to anyone. Not a violation of the GPL.

    7. Re:SCO thinks the GPL is a joke by Malcontent · · Score: 2, Flamebait

      Does it really matter? Isn't the fact that MS is willing to support windows one of it's selling points?

      People buy windows because they can get support for it, why should they be pissed off if someone tells them to call Microsoft and get support for it?

      --

      War is necrophilia.

    8. Re:SCO thinks the GPL is a joke by tshak · · Score: 1, Redundant

      You're only right if MS distributed the code (which is what the GPL covers). However, I explictely mentioned internal use. For example, if MS used a modified version of CVS for it's source control, it would not have to give those modifications back to the community. Most importantly, they could have reaped all of the benefits of the work putting into CVS which could have saved them thousands of dollars.

      --

      There is no longer anything that can be done with computers that is nontrivial and clearly legal. -- Paul Phillips
    9. Re:SCO thinks the GPL is a joke by Strudelkugel · · Score: 2, Insightful

      Isn't the fact that MS is willing to support windows one of it's selling points?

      Depends on who you talk to. For the typical user, probably not. The practical effect of its ubiquity, though, is that there is probably someone around you can ask, or a book ("Dummies", etc) to look at.

      Does it really matter? ....why should they be pissed off if someone tells them to call Microsoft...

      I don't know if you have ever worked in an office environment, but let me tell you, it matters a lot. Imagine a co-worker is trying to figure out how to open a window (a real one!) and is puzzled by the locking mechanism. Someone comes along who knows everything there is to know about the windows in the building, but the one the co-worker is looking at is not one he would have used. The co-worker asks for assistance, but he says "Call facilities, that's what they are for." I guarantee that the co-worker will swear to never recommend whatever the preferred brand of the expert is, because they will associate it with his attitude. Believe me, attitude matters more than technology. That's why *nix lost the desktop in the first place.

      --
      Imagine how much harder physics would be if electrons had feelings! -Feynman, maybe
    10. Re:SCO thinks the GPL is a joke by Malcontent · · Score: 2, Insightful

      " guarantee that the co-worker will swear to never recommend whatever the preferred brand of the expert is, because they will associate it with his attitude. Believe me, attitude matters more than technology. That's why *nix lost the desktop in the first place."

      Once again so what? Do I really care if some clueless twit isn't using linux? I am happy they aren't using linux. They should stay as far away from linux as possible. Using linux will in all likelyhood make their little heads explode.

      There is no reason to make yourself a slave to other people's whims just because somebody *might* not use linux unless you get on your hands and knees and server them like a good little dog.

      Tell them call IT or MS, it's not your job and you have better things to do.

      --

      War is necrophilia.

    11. Re:SCO thinks the GPL is a joke by Anonymous Coward · · Score: 0

      It's called being a dick, dick. The fact that you and "the dougster" miss that point makes it exactly.

      help the (l)users out, maybe they will get comfortable with their machines enough to move to your OS of choice, since they will have respect for you - instead of thinking you're a dick - dick. It could be as simple as saying "Hit f1".

    12. Re:SCO thinks the GPL is a joke by The_Dougster · · Score: 1, Flamebait

      No, I tell them that I have been screwed by MS Operating systems for fifteen years, and that I won't propogate the situation any more. I give some smart-assed advice which is the the actual solution and walk away. They know me and they don't dis Linux because they don't know that it exists, and I don't tell them either. I just say I hate Windows and leave it up to them to find an alternative. I'm not an advocate anymore, been there, done that. I just let them flounder in their own ignorance.

      --
      Clickety Click ...
    13. Re:SCO thinks the GPL is a joke by Strudelkugel · · Score: 1

      Yeesh! Well, you are "Malcontent." Now that I think about it, I used to call IT because of network problems. Novell network that is...

      --
      Imagine how much harder physics would be if electrons had feelings! -Feynman, maybe
    14. Re:SCO thinks the GPL is a joke by Strudelkugel · · Score: 1

      I'm not an advocate anymore, been there, done that

      What were you advocating?

      --
      Imagine how much harder physics would be if electrons had feelings! -Feynman, maybe
    15. Re:SCO thinks the GPL is a joke by eryk · · Score: 2, Informative

      That's why *nix lost the desktop in the first place.
      What??? Did I miss a fight? Now, I am really disappointed... I though that the fight for desktop is about to begin.

    16. Re:SCO thinks the GPL is a joke by Anonymous Coward · · Score: 0

      "Just like I don't help people at work who have problems with Windows even though I am an expert. If I were to donate my time helping somebody with Windows, then Bill Gates and Microsoft are essentially stealing my time for free."

      Gee, and I thought the time one spent at work belonged to one's employer. Or perhaps you don't get paid at your job?

    17. Re:SCO thinks the GPL is a joke by Rogerborg · · Score: 1

      Well said. I spend enough time doing unpaid tech Windoze support for friends and family. I shudder to think how bad it would be if they ran lunix. Next time someone begs an install off of me, I'm telling them to buy a Mac, because:
      A: It's only got one button, and Mac presses it before it leaves the factory.
      B: I know jack shit about them, so I won't have to waste my life saying "click start, setting, control panel, system..." down a 'phone ten times a week.

      --
      If you were blocking sigs, you wouldn't have to read this.
    18. Re:SCO thinks the GPL is a joke by Znork · · Score: 1

      I dont do MS tech support for family and friends. I do do Linux tech support for them, and in fact it's not at all bad. For them, they're not logged in as root, and it 'just works' for their email and websurfing and spreadsheet/word processor needs. They can even let their (2-5 yearold) kids play with it, since I set up a simple script with an icon for the parents to use if the kid messes up their desktop. Just click the icon and it'll wipe and restore the home directory for the kid.

    19. Re:SCO thinks the GPL is a joke by Anonymous Coward · · Score: 0

      >When these "SCO" big-shots start attacking the GPL I take it personal,
      >and so does anybody else who has written for Linux and GNU. I'm
      >certainly not writing code to make SCO rich. They don't pay me, they
      >don't like my "philosophy", well they can go piss up a rope because I'm
      >getting tired of them walking all over the GPL like it somehow doesn't
      >apply to them because they are "big-shots." Bullshit! They are a bunch
      >of crack-heads if they think they can pull this swindle off. They got
      >big balls, I'll give them that, but their big balls are gonna get >kicked hard.
      >

      Why, what are you going to do about it?

      I keep hearing this stuff, and nothing keeps happening. Until someone takes action against SCO I can't take such comments seriously. Goddammit haven't you got the DMCA over there to prevent unauthorised distribution of copyright materials? Sue 'em, ffs! Send 'em a takedown notice! Or shut up and wait for the court case, like the rest of us.

    20. Re:SCO thinks the GPL is a joke by Anonymous Coward · · Score: 0

      Asswipe,

      Have you ever thought that his job might be something other than user support? I get the same sort of stuff - I'm an engineer, my job isn't supporting users - it's engineering work, instead. Sure, I'll go out of my way and help people with Linux/Unix problems, but Windows and Macs? They are on their own. But hey, you can go out of your way and help those sots, and maybe your work won't get done, and you will be the one that gets axed because you missed project deadlines.

    21. Re:SCO thinks the GPL is a joke by Anonymous Coward · · Score: 1, Funny

      They'd be better off using CVS instead of their god awful Visual Sourcesafe, thats for damn sure.

    22. Re:SCO thinks the GPL is a joke by gomiam · · Score: 2, Interesting

      Mmm... IBM tried this with Apache for their Websphere web server.
      They finally realized they were better off cooperating with the Apache developers (by pointing out bugs and sending patches) that trying to keep their modifications up-to-date with the main Apache tree.
      By the way, the enterprise I work currently in has chosen, for the time being, the same original path; I can only hope they will open their eyes soon and start returning code to the OpenH323 community (and yes, I have talked about it several times with them, but they are still somewhat clueless on this account).

    23. Re:SCO thinks the GPL is a joke by gomiam · · Score: 1
      I would mod you "Troll", but I agree with your last paragraph (looking at it again, perhaps I still would mod you "Troll").

      I usually connect to IRC-Hispano network (an spanish language IRC network) and have been doing so since 5 or 6 years ago. I have seen the #linux channel's helpfulness level go steadily down.

      <old grandpa stories mode on> It used to be that any question was met with either direct help, pointers or questions for more information. Currently there are, in fact, many more clueless (if not completely stupid) questions (on Saturday, someone asked to be sent, over DCC, "the Linux install disks", being in a cybercafe), but even usual newbie (no offense meant) questions are now ignored or, even worse, frowned upon.

      Yes, the channel is now a Linux users' meeting point rather than a hot-line, but manners should still be held. Anyway, there are still those who try to help anyone asking questions, so perhaps there is hope yet. </old grandpa stories mode on>

    24. Re:SCO thinks the GPL is a joke by mpe · · Score: 2, Informative

      Then Microsoft would be in violation of the GPL. The GPL lets anybody on the face of the earth take something released under it and package it and sell it, but they are required to provide the source code for free to any and all who ask for it.

      Actually no. The GPL obliges people to make available the source (of GPL covered code) only to third parties they have supplied it to. i.e. if you sell GPL code then the only people who can demand the source code from you are your customers. Also if GPL software is used entirely for "personal use", which a corporation can do just as easily as an individual, then it can also be modified in all sorts of ways.

      If Microsoft passed it off as their own and didn't release source code, well then they would be criminals wouldn't they.

      If Microsoft were to do this they would be enguaging in both fraud and copyright infringement.

    25. Re:SCO thinks the GPL is a joke by TopShelf · · Score: 0

      Wow, I bet you're really popular around the office. Don't be surprised if you miss out on the birthday cake next time...

      --
      Stop by my site where I write about ERP systems & more
    26. Re:SCO thinks the GPL is a joke by Aceticon · · Score: 1

      You just proved his point!

    27. Re:SCO thinks the GPL is a joke by kien · · Score: 2, Insightful
      Just like I don't help people at work who have problems with Windows even though I am an expert.

      Hehe, I've had this urge (I mean, it gets rediculous after you've had to remove the Lovegate virus from 20 co-workers' PCs) but I guess I value teamwork more than GNU/Linux advocacy or any antipathy towards Microsoft. I just can't say no when one of my friends or family needs some technical help.

      The somewhat surprising side-affect of this willingness to help my neighbor has been that they now value my opinion and they are increasingly curious about GNU/Linux because while I'm fixing their problem they frequently hear me muttering things like "why people pay for this crap when they can have something better for free boggles the mind".

      I guess for me, helping people is more fun and important than my own personal stance on software (and this from a bootable-card-carrying hippie communist member of the FSF!).

      --K.
      --
      Sig: Bad people happen. Try to avoid being one of them.
    28. Re:SCO thinks the GPL is a joke by Jim+Hall · · Score: 1

      They could use your program, modify it for their own internal use, and never give anything for it while they reap the benefits of your software.

      Yup, that's how the GPL works. If you modify then redeploy GPL'd software for internal use only (inside your company) you do not need to distribute the source code for that program to your end users. Reason: this is not considered distribution under the terms of the GNU GPL ... as a corporate entity, you are not {technically speaking} redistributing it to anyone, so there is no requirement to distribute source code.

      Also, "Free" has never meant "zero price". It means "Freedom". So it's also possible for an organization (like Microsoft) to give away or sell your GPL'd software (under the terms of the GNU GPL) and not pay you a dime.

      -jh

    29. Re:SCO thinks the GPL is a joke by Frnknstn · · Score: 1

      Actually no. The GPL obliges people to make available the source (of GPL covered code) only to third parties they have supplied it to

      According to my reading, the GPL obliges people to make available the source (of GPL covered code) to anybody to whom it has been supplied.

      If you sell a GPL program, the person who buys it can give it away to anybody at all, and that recipient is entitled to have the source code.

      --
      If it's in you sig, it's in your post.
    30. Re:SCO thinks the GPL is a joke by Anonymous Coward · · Score: 0
      "Sure, I'll go out of my way and help people with Linux/Unix problems, but Windows and Macs?"

      And why would you go out of your way to ignore windows and mac users when they need help? Are you just a plain old asshole or is there another reason?

    31. Re:SCO thinks the GPL is a joke by kalidasa · · Score: 2, Insightful

      Wait a minute:

      Believe me, attitude matters more than technology. That's why *nix lost the desktop in the first place

      When did *nix EVER have the desktop? I seem to remember this progression:

      CP/M

      Apple

      DOS

      MacOS

      Windows 3

      Windows 95/NT

      Windows 98/NT4

      Windows 98SE/2K

      Windows XP

      The only places Unix was widely used on the desktop were IRIX machines and NeXT boxen, the former in a niche market and the latter at the high end of the price spectrum (and so mostly in universities and other institutions). Most places that had "UNIX on the desktop" had terminals hooked up to a UNIX mini, and they were in close competition with the VT100s and the VAXen.

    32. Re:SCO thinks the GPL is a joke by siliconminded · · Score: 1

      That's wonderful of you. You're not a decent enough person to help someone at work you know personally, but you're willing to stand up and defend the hours of labor you gave "as a gift for all the world". Pompous ass.

    33. Re:SCO thinks the GPL is a joke by Rich0 · · Score: 2, Informative

      It also means that they cannot legally prevent an MS employee for posting said internal software onto the Internet for all to see. Maybe they aren't using anything worth posting...

      You can't force users to sign an NDA to use GPL software - the GPL states that ANYONE you give the software must be allowed to use it under the terms of the GPL - which means they too can redistribute it.

    34. Re:SCO thinks the GPL is a joke by Rich0 · · Score: 1

      Your scenario:

      Company A sells software to customer B.

      Customer B gives software freely to users C1-C100k.

      My understanding is that company A is responsible under the GPL to provide the source to customer B only. B is then responsible to give the source to C1-C100k. A should not have to incur huge distribution costs for distribution it does not perform.

      Even if somehow the GPL were found legally to require A to distribute the source to C1-100k it would still require B to do the same. A's legal defense would be to set up a web server that is bandwidth-capped at 1kbps and 1 user and have it distribute the software to anyone who asks. They could also send a source CD to B (or better still include it on their original distribution CD). They could then say that they set up a system in aticipation of the expected download demand (since they weren't expecting anyone to download the source anyway - it was already sent to everyone who has the software that they know about).

      The GPL was designed to protect those who write free software from having their work exploited. It was not designed to force anyone who wants to distribute free software to have 12 T3 lines and colocation.

    35. Re:SCO thinks the GPL is a joke by johnnyb · · Score: 2, Insightful

      Actually, when used within an organization, the organization is the user, not the individual. If an individual posts the modified code, they are violating the copyright of Microsoft.

      You see, the GPL doesn't take force unless there's redistribution. If the copyright holder (in this case, Microsoft), isn't distributing outside out itself, then the software isn't under the GPL, and therefore that individual does not have the authority to redistribute it, and can be sued.

    36. Re:SCO thinks the GPL is a joke by johnnyb · · Score: 1

      In addition, A can charge for the source. It has to be a "reasonable charge" but that doesn't mean they have to be responsible for the production costs.

    37. Re:SCO thinks the GPL is a joke by ichimunki · · Score: 1

      That interpretation hinges on the definition of the word "distribute" and is one of the grey areas in the GPL. My personal take is that an employee, acting as an agent of his/her employer during work hours is not the recipient of a distributed copy of the software and has no right to expect the source code to be forthcoming.

      However, if the employees are given the software to install on machines they own, or the software is given to independent contractors, then the GPL comes back into play. Interestingly, my take on this is pretty close to the FSF interpretation. Here's a quote for the lazy: No, in that case the organization is just making the copies for itself. As a consequence, a company or other organization can develop a modified version and install that version through its own facilities, without giving the staff permission to release that modified version to outsiders.However, when the organization transfers copies to other organizations or individuals, that is distribution. In particular, providing copies to contractors for use off-site is distribution. .

      Did I mention that the GPL FAQ should be required reading if you are going to try and comment on specifics of the GPL?

      --
      I do not have a signature
    38. Re:SCO thinks the GPL is a joke by johnnyb · · Score: 1

      In fact, they do this. It's called Microsoft Interix.

    39. Re:SCO thinks the GPL is a joke by Anonymous Coward · · Score: 0
      "And why would you go out of your way to ignore ... users when they need help? Are you just a plain old asshole or is there another reason?

      He said he uses Linux, not *BSD! Geeze, RTFP!

    40. Re:SCO thinks the GPL is a joke by The_K4 · · Score: 1

      like I don't help people at work who have problems with Windows even though I am an expert.

      So, if one of your Co-workers is have a problem (meaning a loss of productivity) and even if you KNOW how to fix the problem wuickly and easily you are going to make them use IT (which usually takes time) or MS Tech. Support. You would CHOOSE to hurt your company, talk about biting the hand that feeds you.

    41. Re:SCO thinks the GPL is a joke by Anonymous Coward · · Score: 0

      Re: Just like I don't help people at work who have problems with Windows even though I am an expert.

      Must be a real pleasure for people to work with
      you.

    42. Re:SCO thinks the GPL is a joke by usotsuki · · Score: 1

      *wave*

      I believe a lot of people forget that point of the GPL, that it is not about "no cost", which is why I don't like the term "free software".

      I hedge. I usually say "free/open software", but occasionally I qualify "free" with a foreign word that has the intended meaning (usually, in my case, the Japanese word "jiyÃ").

      -uso.

      --
      Dreams, dreams, don't doubt dreams, dreaming children's dreaming dreams. Sailor Moon SS
    43. Re:SCO thinks the GPL is a joke by usotsuki · · Score: 1

      Lunix? You tell them to run a Commodore C64 OS? :)

      -uso.

      --
      Dreams, dreams, don't doubt dreams, dreaming children's dreaming dreams. Sailor Moon SS
    44. Re:SCO thinks the GPL is a joke by sbillard · · Score: 1

      You are a prick. I'm glad I don't work with you. Damn jerk. GFY.

      I can see you there at your desk, picking your nose, refusing to help - even though you claim to have the answers
      I don't help people at work who have problems with Windows even though I am an expert

      Take your GPL and shove it up your ass sideways. You need a swift kick in the pants.

    45. Re:SCO thinks the GPL is a joke by belove · · Score: 1

      I think this really speaks at the heart of the matter, don't screw with the experts. Look at the BSD case and now Apple's case. UNIX is just too public to really have any single owner. I mean, UNIX is like the wheel in a way.

      This is a good case for all open source software. I was talking with some neighbors, and while not being industry experts, they understand that the SCO v IBM case is a joke.

      I think that if IP changes hands more than once, it should be made public. So many eyes seeing it pretty much makes it public anyway. Think about the BeOS sources and how many eyes have seen it by now. This court case is such a massive injustice already, that it exposes the weakness of the US just as the OJ trial did.

      When will enough be enough? We must work to stop this nightmare system. I think we need real political unrest NOW! If we're unable to rock the boat, Bush will remain in power, and these SCO guys could win. We already know that we do not want our President to be like Nixon, yet a guy very much like him is sitting in our office!

      Please, get in touch with your local Linux User Group. If none exists, start one yourself and get the ball rolling.

    46. Re:SCO thinks the GPL is a joke by fishbowl · · Score: 1

      "And why would you go out of your way to ignore windows and mac users when they need help?"

      You totally missed his point.

      I'm good with cars. I will help people with their cars when they have problems that fit my tools and my skills. When they have cars that need special (or just not metric!) tools, or when they have problems hat don't fit my skills.

      It doesn't mean I'm "ignoring" Dodges and Fords to work on VW's and MG's.

      --
      -fb Everything not expressly forbidden is now mandatory.
    47. Re:SCO thinks the GPL is a joke by gbjbaanb · · Score: 1

      well, I wasn't really trolling, more feeding the original.

      But my last point is the big deal. Although that attitude isn't solely confined to linux 'l33t' users, they seem to be the majority (or, those who think this way learn Linux and become part of the 'community' because it allows them to act that way. self fulfilling perhaps).

      I wonder, if Linux becomes mainstream, will these people start complaining that Linux has 'sold out'? So many times other underground/minority/elitist projects have gained wide-spread acceptance, that has happened.

    48. Re:SCO thinks the GPL is a joke by EJB · · Score: 1

      Of course it is a violation of the GPL. It is distribution. It is making copies. Only copies for personal use are "fair use", in other cases, you are not allowed to make those copies unless you have the permission from the copyright holder. This hypothetical company has that permission because it is written in the GPL. But the company only has that permission as long as they stick to the GPL.

      With your argument, any company would be allowed to make unlimited copies of MS Office as long as they don't "distribute it outside itself"

    49. Re:SCO thinks the GPL is a joke by Anonymous Coward · · Score: 0

      If somebody has problems I tell them to call the IT department or Microsoft Technical Support. Hmmm -- BOFH, anyone?

    50. Re:SCO thinks the GPL is a joke by TheCarp · · Score: 1
      Well being that I took 5 years of french I like to say "Software libre" but mostly only because I can pronounce an "re" without reversing it, and it conveys the meaning since English adopted a bunch of words with this root a long time ago.

      Probably the best English word, even if the connotations arn't always the best, is "Liberal Software", using liberal in the sense of "Freely permitted, not interfered with." (OED) even if it is a slightly archaic usage.

      Or perhaps, also from the OED:

      5. Of political opinions: Favourable to constitutional changes and legal or administrative reforms tending in the direction of freedom or democracy.


      Which seems to translate very appropriatly (even if most americans seem rather ignorant of what the term has traditionally meant).

      Its not so much that there is no better term in english than "free" by the standars of definition, its mostly a problem of connotation.

      -Steve
      --
      "I opened my eyes, and everything went dark again"
    51. Re:SCO thinks the GPL is a joke by TheCarp · · Score: 1
      I used to do windows support for a living... now I generally refuse to help windows users (of course I just recently aquired my first windows machine in 6 years, which will cease to run windows as soon as the dual mode IBM wireless card in the T40 is supported under linux :) )

      I learned a phrase then, and have learned it a few times since:

      No good deed goes unpunished


      Its sooo true. You help one guy with a windows problem, and someone else will have one for them, you help them, and you are garaunteed to be asked every question under the sun for the next 3 weeks by half the office.

      Now heres the thing... most companies hire IT support. As a unix sysadmin, I am not paid for my ability to do windows support. So fine helping you once is nothing, maybe helping someone else is nothing too... one offs. However, once you get started it can easily snowball... and in fact, with systems as ubiquietous and problem-prone as windows boxes... it always does.

      Now, I also used to fix HP laser printers... we have exactly 1 of these in the office. When asked, I happily look at it. I don't like supporting printers, and its not why I have my job, but as theres only 1 of them, and we have an issue that needs my attention maybe once in 6 months... theres no snowballing with this skill.

      -Steve
      --
      "I opened my eyes, and everything went dark again"
    52. Re:SCO thinks the GPL is a joke by johnnyb · · Score: 1

      "With your argument, any company would be allowed to make unlimited copies of MS Office as long as they don't "distribute it outside itself""

      Incorrect. If you look at the GPL, it says this explicitly, while the Microsoft EULA does not.

    53. Re:SCO thinks the GPL is a joke by Anonymous Coward · · Score: 0

      Seriously, do you really think they use Sourcesafe to store the 2Billion lines of code? Ya right - they built a custom solution internally with the help of an outside firm.

    54. Re:SCO thinks the GPL is a joke by smithmc · · Score: 1

      Once again so what? Do I really care if some clueless twit isn't using linux? I am happy they aren't using linux. They should stay as far away from linux as possible. Using linux will in all likelyhood make their little heads explode.

      It is exactly this sort of attitude that guarantees that Linux will never beat Windows on the desktop. Which, of course, I'm sure is just fine with certain members of the propellerhead crowd...

      --
      Downmodding is the refuge of the weak. Don't downmod, make a better argument!
    55. Re:SCO thinks the GPL is a joke by Frnknstn · · Score: 1

      B is then responsible to give the source to C1-C100k.

      True, but the point is moot, as this would mean that the source code (the Microsoft-altered code in this example) IS availible, as B would have to have given the source to C1-C100k, or provided a written offer to distribute the source. Your bandwidth-capped server idea is not legal under the GPL; If a user wants the source, it is your responsibility to get the source to him, with a charge no more that the cost of the transferance.

      A can charge for the source

      Yes, 'A' can, but the cost of the source may be no higher than cost of the binaries, and if you have the binaries, you are entitled to the source, with a charge no more that the cost of the transferance.

      --
      If it's in you sig, it's in your post.
    56. Re:SCO thinks the GPL is a joke by Fat+Casper · · Score: 1
      So, if one of your Co-workers is have a problem (meaning a loss of productivity) and even if you KNOW how to fix the problem wuickly and easily you are going to make them use IT (which usually takes time) or MS Tech. Support. You would CHOOSE to hurt your company, talk about biting the hand that feeds you.

      IT chose to hurt the company by deploying Windows. Donating Band-Aid tech support harms the company far worse by hiding from management the true cost of Windows. Should you turn in a completed help ticket so the pay for your time spent doing tech support instead of your real job comes out of IT's budget instead of your own department's?

      Doing Windows tech support (unless it is explicitly a part of your job) violates one of Murphy's Laws of combat, too: Don't reinforce failure. Failure tends to reinforce itself. You can use Windows all you want. I'm not going to help you do it, though.

      --
      I spent a year in Iraq looking for WMD and all I found was this lousy sig.
    57. Re:SCO thinks the GPL is a joke by buffy · · Score: 1

      Hmm...you're right, but the issue will get murkier if they distribute the program to contractors. Contractors are not a direct part of an organization--particularly if the contract is with another company, not just an individual. Either way, they are distributing it to another entity (in the business sense) and would fall under the terms of the GPL (per re-distribution.)

      Just my $0.02. And always, IANAL, so perhaps it's worth even less...

      -buf

    58. Re:SCO thinks the GPL is a joke by Malcontent · · Score: 1

      Yes and it was a stupid point made by a stupid person. Who the fuck cares.

      --

      War is necrophilia.

    59. Re:SCO thinks the GPL is a joke by Malcontent · · Score: 1

      "It is exactly this sort of attitude that guarantees that Linux will never beat Windows on the desktop"

      If you think that my attitude is the only thing preventing linux from beating windows on the desktop then you are quite possibly the stupidest person on the planet.

      --

      War is necrophilia.

    60. Re:SCO thinks the GPL is a joke by smithmc · · Score: 1

      If you think that my attitude is the only thing preventing linux from beating windows on the desktop then you are quite possibly the stupidest person on the planet.

      Gee, there you go again. You should work at a help desk, or maybe as a product evangelist. The world should not be denied the benefit of your people-skills.

      --
      Downmodding is the refuge of the weak. Don't downmod, make a better argument!
    61. Re:SCO thinks the GPL is a joke by Malcontent · · Score: 1

      "The world should not be denied the benefit of your people-skills."

      Once again you display your lack of inteligence by failing to keep to the topic of the discussion.

      Are you going to tell us a cute story of about your dog now?

      --

      War is necrophilia.

    62. Re:SCO thinks the GPL is a joke by gomiam · · Score: 1
      Ok, point taken, troll mod forgotten :-)

      On l33t l1nu>< u5er2: fortunately, they are not the biggest part of the community. Unfortunately, they are the noisiest. Fortunately, mostly no one pays them too much attention if there is a regular member around to un-unsettle them.

      Oh, in my experience, they are already crying out that Linux distros have sold out (say... Red Sucks and Suckse are terms that I have already heard more than once), excepting the pure ones like Debian or Gentoo (I like Debian myself, but I'm quite agnostic when working on UNIX/Linux otherwise).

      That's not much to care about, anyway. Whenever something sacred spreads there are always zealots that cry out. It is funny: they consider something good for it is not widely understood and suddenly change their minds when everybody gets a taste of it. I'm certain that there are a lot of psychology/sociology books written on this account :-)

      PS: sorry for my abusing quotes. My mind is loosing steam by the second at this time (0:50 in Spain)

  43. Yikes by Faust7 · · Score: 4, Funny

    Interviewer: ...where the code that goes in the Linux kernel comes from.

    Linus: I allege that SCO is full of it.

    Watch out, SCO is just nutty enough to take that the wrong way.

    1. Re:Yikes by Demerara · · Score: 1

      What Linus actually meant to say was:

      I allege that SCO is full of IT

      Clearly, something for which evidence might be hard to come by...

      --
      Backward%20compatibility%20is%20over-rated
  44. So does this mean... by Anonymous Coward · · Score: 1, Interesting

    that if I download a copy of Caldera Linux (someone can tell
    you the link to get it), then I won't have to worry about them suing me?
    Even if I don't actually use it? Or do I have to use it
    at least once then I can claim I have permission to use
    the kernel in another Linux OS I'm running?

    1. Re:So does this mean... by baloogan · · Score: 0

      Good idea!

      /me thinks.....

  45. Why stop with IBM? by princeofweasels · · Score: 1


    I think that they should sue their customers. Why stop while they're on a role. Really if they fire up another couple of billion dollar lawsuits against their biggest customers they're likely to get there stocks up into the teens. Then they could sue themselves (http://uptime.netcraft.com/up/graph/?host=www.sco .com) it might even go up as high as 20.

  46. Re:really now by antiMStroll · · Score: 1

    Which, of course, proves being drunk and typing with your feet doesn't work.

  47. BIll Gates must be smiling a million dollar smile by crivens · · Score: 0, Flamebait

    BIll Gates must be sitting back in his $5000 leather chair, with his feet up on his $10000 mahogany (oak, teak or whatever) desk, smiling a smile bigger than the cheshire cat and thanking his lucky stars that those stupid Linux developers adopted the GPL.

  48. Trademark/Copyright by stevezero · · Score: 3, Insightful

    One side of me says that if SCO doesn't enforce it's "rights" against everyone, including its own users, then there might be a danger of someone claiming that because SCO failed to defend their "rights" against everyone, there is a danger of making the "rights" null and void. After all, if you don't defend your rights vigorously, you have a danger to lose them.

    The other side, as I see it, is if someone paid money to SCO/Caldera/Whoever and accepted an EULA from SCO/Caldera/Whoever, then they have a license to use the code anyway....

    1. Re:Trademark/Copyright by BJH · · Score: 2, Interesting

      NO.
      Copyright doesn't work like that (for the thousandth time). If you have copyright on something, those rights last as long as copyright law allows. Not defending them doesn't harm your case in any way if you suddenly decide to start defending them.

    2. Re:Trademark/Copyright by DragonMagic · · Score: 2, Informative

      Incorrect.

      SCO does not own the trademark for UNIX, nor any other trademarks alleged to be infringed in this suit. Trademarks are the only IP that can be lost if not actively defended.

      Copyrights can be moderately defended and still kept. However, if you choose to widely ignore infringement for a lengthy period of time, your hopes of coming back to sue people for large amounts of damages will be laughed out of court. Especially if you continue to help give away those copyrights fully knowing that by doing so people would be infringing on your rights.

      Patents don't have to be actively protected. You can sue even when you have a week left of the patent for all the sales which came before using your patents. As long as the patent is still valid, you can have a fair chance at getting people to stop using your patent and/or collecting your fees for use of your patent.

      Here, though, SCO has only sued IBM for violating a contract, anticompetitive practices and illegally distributing trade secrets. Linux and the BSDs have not been sued for any IP problems.

      Until they do file suit, technically there's no reason to stop distributing the code, working on the code, or using the code. They also haven't shown what infringes their rights, so it's impossible for anyone to guess what could be the problem. Can't really stop allegedly infringing if no one else seems to know what the infringing code is!

      --

      Human nature is the same everywhere; the modes only are different. -- Earl of Chesterfield
    3. Re:Trademark/Copyright by bovinewasteproduct · · Score: 1

      Huh?

      About the only place this applies is to trademarks.

      The most that will usally happen is that the courts will rule that you can't get money out of someone if you've sat around too long.

      But selective copyright/patent enforcement? I can do that all day long. What was that in the news about Red Hat saying they would not enforce their patents? Same thing. They can go after the big players and leave the small fish alone and the courts won't say a word...

      BWP

  49. Interpreting the letter by hobsonchoice · · Score: 4, Interesting

    I think they are simply saying they don't want license fees and/or won't sue (not sure which - probably means same thing) existing SCO customers. I personally don't think the letter necessarily implies that SCO thinks that SCO Linux customers will be able to keep on distributing source, GPL style.

    One thing that I haven't figured out, is what about UnitedLinux? (which I believe SCO to be a member of). Is SCO Linux = a standardized UnitedLinux distro, or is it more complicated than that?? And if yes, or nearly, how do SCO think customers of their UnitedLinux partners should act??

    Another thing that isn't clear, is whether you will be able to become a SCO Linux customer (not saying I want to, just whether it will be possible) - i.e. what if you want to buy SCO Linux - could you? I realize they have stopped selling it for now, but will this continue?

  50. no-one, because by dh003i · · Score: 1

    shorting SCOX would imply that people would buy it again after the price plummets. Not likely, since this company, run by incompetent execs, is destined for bankruptcy.

    1. Re:no-one, because by mikeophile · · Score: 2, Informative
      There is no such implication in short-selling stock.

      When you short a stock, you are in effect borrowing shares from a shareholder and selling them. If the stock price goes up, you have to make up the difference to the shareholder you borrowed from. If the stock completely tanks, it's unlikely the shareholder will want the now worthless stock and you walk away with a nice profit.

    2. Re:no-one, because by Rogerborg · · Score: 1

      I think you miss the point. To sell stock you have to find someone willing to buy it. Any informed speculator will be avoiding SCO like the plague.

      Fortunately for SCO, informed speculators are pretty thin on the ground. There's always a chump ready to take the risk.

      --
      If you were blocking sigs, you wouldn't have to read this.
    3. Re:no-one, because by bankman · · Score: 1

      No, that's not what it implies. Short-selling means that you are selling something that you don't have with the intention to buy it (to satisfy delivery to your initial counterpart) at a later point. Of course, to make a profit, the transaction implies that you (the short-seller) hope to buy SCOX (in this case) at a discount (a price that is below the price of the intitial deal). This may not work, because the share price could rise as well as fall. It is a gamble that only works if the market generally agrees with your evaluation of the company/share. Supply will be greater than demand and the price falls.

      It does not imply that people would buy the shares again, since somebody _already_ bought them. If demand is lower than supply, you buy the shares at the lower price to only satisfy the past deal. One might think, that this increased demand could level the share price again, but your buyer is very likely to sell the shares as quickly as possible since he probably has the same kind of fundamental expectations about SCO as you, but was hoping to make a quick profit on current situation.

      What I find strangest about this situation instead is this: Why does the business press (eg. Business Week, Forbes) write rather favourably about SCO in this situation? Are they really that daft? Or do they know something I haven't picked up yet?

      --
      I feel so sig.
    4. Re:no-one, because by anotherdotter · · Score: 1
      I think you miss the point. To sell stock you have to find someone willing to buy it. Any informed speculator will be avoiding SCO like the plague.

      No, no, no. You are missing the point. When you short you borrow the stock today, and sell it today. YOU then buy back the stock later (hopefully at a dirt cheap price) so that you can give it back to the person you originaly borrowed the stock from.

  51. Re:haiku by j0nkatz · · Score: 0, Offtopic

    They will dye Linux will live lond and prosper?

    --
    Don't mod me, bro'!!!!
  52. Um... by Anonymous Coward · · Score: 0

    "The less I have to do with suits, the happier I am. That said, if I'm called as an expert witness, I'll go if only because I'd be curious about the process."

    I'm sure he'd also go if he was compelled by subpoena, too. Unless I'm misunderstanding how the process works, wouldn't he be compelled to testify if called upon by the courts? You can't just volunteer to testify, right?

  53. ... then they kill you. by Anonymous Coward · · Score: 0

    Just a little joke. We're on a long winning ride! It should be over in a cool century.

  54. stay away from sco by polished+look+2 · · Score: 3, Insightful

    SCO's "protest" images were not in good taste; portraying Torvalds as a puppet of IBM is a pretty cruel thing to do; equating hard work banging out code with piracy is a pretty cruel thing to do.

    1. Re:stay away from sco by Anonymous Coward · · Score: 1, Funny

      Here is my take on the whole thing....

      See SCO.
      See SCO lie.
      See stocks fly.
      Fly stocks, fly!
      See Gartner blow.
      SCO stocks grow!
      Grow stocks! Grow!
      See Novell.
      See Novell smack,
      Smack SCO! Smack!
      See IBM.
      See IBM laugh.
      SCO lawyers barf.
      SCO stocks cut in half.
      See SCO.
      See SCO whine.
      SCO says "It's mine!"
      See IBM.
      IBM puts foot down.
      SCO execs start to drown.
      Drown SCO, drown!

  55. dynamic IP by Graspee_Leemoor · · Score: 5, Funny

    Ha, I pity SCO with their static IP!

    I have dynamic IP.

    Yesterday I owned the rights to Wireless Toasters, and the day before it was me who invented a certain sort of plastic sheathing suitable for undersea cables, tomorrow it may be me who invented tcp/ip!

    Oh the excitement of dynamic IP...

    graspee

    1. Re:dynamic IP by Anonymous Coward · · Score: 0

      What are you talking about? Of course SCO has dynamic IP. Yesterday they sued over Linux IP, today they're suing over Unix IP.

  56. Re:BIll Gates must be smiling a million dollar smi by Anonymous Coward · · Score: 0

    WTF are you drooling about, moron?

  57. except... by pyrrho · · Score: 1

    The GPL specifically states that if you ship the code, the GPL applies, and that if you ship your proprietary IP it has to be available for a royalty free non-terminable licence.

    So SCO is clearly in violation of the GPL to be doing this.

    Further, since it's distributed under the GPL and they have confirmed this now, their IP can be redistributed, as the GPL allows, by their customers.

    I do not share you confidence in SCO's lawyers, so I'll call your SCO lawyers and rais you a pack of IBM lawyers.

    --

    -pyrrho

    1. Re:except... by KrispyKringle · · Score: 4, Insightful
      Pyrrho, did you even read what I was replying to? Not the argument that shipping Linux made their code GPL (this is a whole other issue which I've discussed in previous posts). I was talking about the argument that not prosecuting certain violations means that SCO cannot prosecute any violations, which is patently untrue, regardless of your post.

      I don't really feel like going in-depth on the other argument, but I will address it briefly. Basically, the argument goes, SCO accidentally GPL'ed their code. In order for this to apply, SCO would have to be the one who released the code under the GPL. This is incorrect; the alleged SCO code that was included when SCO released their own distro under the GPL was not released by SCO, it was being redistributed. The initial release, allegedly, was done by IBM, which is therefore invalid in that it was not released by the code owners.

      Also, this argument ignores the specifics of the SCO/IBM argument, which is not IP at all but, rather, about contractual violations; there are no "is this wrong" issues here; the only issue is whether it happened. If IBM did in fact release SCO code, it was certainly a contract violation.

      And I don't see what IBM's lawyers have to do with it; what I meant was that it is silly to assume that such a simple flaw exists in SCO's reasoning without even doing any legal research first. IBM's lawyers, to my knowledge, have never used either of the above mentioned arguments publicly, and I would be quite surprised if those arguments made it into the court case, seeing as it is about contract violation and not IP.

    2. Re:except... by pyrrho · · Score: 1

      I did read those posts.

      You make a good point about the IBM v. SCO nature not involving the GPL, I'm thinking about the fact that SCO has GPLed their code however.

      They distributed it under GPL.

      That can be inadvertent, so they immediately cease shipping linux. By indemnifying their customers, however, they have said to the court "make no mistake about it, we know we've shipped our code with GPL code, and please understand we are fine with that, we have told our customers this is fine." Right. Assuming their lawyers have read the GPL, their code is now GPLed.

      OR: they are in violation of the GPL and can be sued. It's not a part of the IBM case, but it could be, there is no reason that IBM, as a linux copyright holder cannot counter sue SCO now.

      Sorry if that wasn't clear. I agree the post you were replying too was the most wrong of all, implying that using SCO at anytime would indemnify you from getting sued, when clearly they mean "we won't sue you for using SCO IP that we sold you."

      --

      -pyrrho

    3. Re:except... by KrispyKringle · · Score: 1

      Heh, OK, the thought of IBM threatening to sue as a Linux copyright holder hadn't really occurred to me. It seems a bit far-fetched, still, to claim that they GPL'ed their code incidentally, but it does seem a bit more pertinent under that light.

    4. Re:except... by Rogerborg · · Score: 1

      > The GPL specifically states that if you ship the code, the GPL applies, and that if you ship your proprietary IP it has to be available for a royalty free non-terminable licence.

      Does it really? Care to quote the parts that say that?

      What it actually says is that the only thing that gives you the ongoing right to duplicate other people's IP is to ship with the GPL license attached. It doesn't say that you have to mean it, nor that you can't stop shipping (thereby stopping your own violation of other peoples' rights, and SCO are slowly getting there) and then renege on your GPL license and prosecute the duplication and distribution of your copyrighted code.

      Regarding patents, again all that the GPL says is that you can't distribute other people's copyrighted source at the same time as you're attaching patent claims. Once you stop shipping (which SCO will by the time this gets heard in court, I assume) you can go hog wild.

      The GPL does not require you to grant explicit licenses to your patents, either on an ongoing basis or in perpetuity. This is the big snafu in version 2, and one which is long overdue for change.

      If you disagree, quote the clauses. I say they're not there.

      --
      If you were blocking sigs, you wouldn't have to read this.
    5. Re:except... by pyrrho · · Score: 1

      What it actually says is that the only thing that gives you the ongoing right to duplicate other people's IP is to ship with the GPL license attached. It doesn't say that you have to mean it, nor that you can't stop shipping (thereby stopping your own violation of other peoples' rights, and SCO are slowly getting there) and then renege on your GPL license and prosecute the duplication and distribution of your copyrighted code.

      yes of course, I agree, you can not mean it, and then GPL doesn't apply. You have to stop and have a good story about accidently shipping it in the first place.

      The topic of this story was SCO further sanctioning the use of linux by their own customers. They know they have no license now by which to have given those customers Linux, but they are not recalling those distributions, they are actively promoting that their customers keep Linux, promising support, and standing behind what they have done.

      What they have done accidently or by design is ship their code under the GPL. So in other words, by sanctioning what they did, even if they stop further shipments, they have said loud and clear, "We DO mean it... our IP, under the GPL, merged with linux, boot up and be merry".

      It's as if there is a mind bubble and some people do not realize the other linux code is not public domain, that it's fully copyrighted material. Not just any hypothetical AT&T code in there, but all the other stuff, the other parts of the kernel that linus or whomever added.

      SCO must be sued by OSS copyright holders. Specifically those into which SCO code is currently merged.

      --

      -pyrrho

    6. Re:except... by mmurphy000 · · Score: 1

      "This is incorrect; the alleged SCO code that was included when SCO released their own distro under the GPL was not released by SCO, it was being redistributed. The initial release, allegedly, was done by IBM, which is therefore invalid in that it was not released by the code owners."

      Could you point out where in the GPL there is a distinction between "initial release" and "redistributed"?

      Or, to put it another way, how do we know that *Linux* is distributed under the GPL? After all, it could be that Linus never really intended for Linux to be under the GPL, that somebody nefarious put those GPL headers in while he wasn't looking, and he just put that code on FTP servers without realizing the GPL headers were in there.

      Heck, we don't even know if we're allowed to use Microsoft products. It could be that there's some rogue person in Redmond, writing EULAs and putting CDs in boxes, without anyone in Microsoft realizing it. They thought they were just a research firm.

      In all three cases (SCO shipping SCO code in Linux, Linus shipping Linux, Microsoft shipping product), we have a copyright holder expressly distributing their copyrighted material with a license attached. Two of the three claim they know what they're doing. One claimed they knew what they were doing at the time (why else issue SCOLinux press releases and put prices on SCOLinux and such?), and now claim they were duped.

      Courts, at least in the US, use reasonableness tests all the time in their judgements. Which is more reasonable:

      -- That copyright holders who distribute their copyright product with a license attached are bound by that license, regardless of how that license got there?

      -- That recipients of copyrighted works with licenses attach need to go back to the purported copyright holders and have them validate that they indeed did intend to distribute the material as so licensed? So, everytime somebody buys a Microsoft product at a store, they need to send a form for Microsoft to sign and notarize?

      IANAL, but IMHO, the "SCO didn't intend to ship the code under the license, therefore it doesn't apply to them" opens a can of worms that courts are unlikely to want opened. Hence, this is a test of shrinkwrapped licenses. If the courts specifically rule on whether the GPL applies in this case, it could have major impact on software distribution across the board.

    7. Re:except... by Rogerborg · · Score: 1

      I agree. SCO can and should be sued by the other rights owners, perhaps as a class action. What I am wondering is how a court will interpret their defence, which will be that the GPL gives them let and leave to do whatever the hell they like, as long as they follow the terms of the license, i.e. either refrain from duplicating the code, or duplicate it with a GPL license text attached...regardless of whether they ignoring this license and are prosecuting third parties for duplicating their copyrighted source.

      It sounds crazy, doesn't it? Claiming GPL protection from copyright violation while at the same time ignoring it to prosecute violation of your own GPL'd source. But these will be separate cases, heard by separate courts, each of them run by a judge who is determined to keep the arguments focussed on her case. This could get very messy indeed.

      --
      If you were blocking sigs, you wouldn't have to read this.
    8. Re:except... by Dr.+Manhattan · · Score: 1
      Basically, the argument goes, SCO accidentally GPL'ed their code. In order for this to apply, SCO would have to be the one who released the code under the GPL. This is incorrect; the alleged SCO code that was included when SCO released their own distro under the GPL was not released by SCO, it was being redistributed.

      But, once they became aware of the alleged violations, they didn't stop distributing the Linux source code themselves. They continue to distribute code that they do not have the copyright to.

      The only legal way that they can do so is if they accept the GPL. Otherwise, they are violating copyright, just as much as any 'music pirate'. At least one kernel developer has explicitly demanded that they stop distributing his code.

      So, which is it, in your view? Is SCO violating copyright law? Or have they accepted the GPL for the code they are distributing, i.e. the Linux kernel? I don't see how they can have it both ways...

      --
      PHEM - party like it's 1997-2003!
    9. Re:except... by KrispyKringle · · Score: 1

      My feeling in writing this was actually that the spirit of the law is broken by considering this a release; I hate to be a party pooper but if SCO did not intend to release their source code as GPL, it should not be GPL. That would be wrong, so to speak. Would it be illegal? I have faith that our courts would find it so, for a number of reasons. In order for a contract to apply (and thats all licenses are), both parties have to be knowing in the contract they have entered. If SCO did not know this contract was being applied to their source code, the whole thing gets iffy. This does not mean its cut-and-dry, for certain, but I find the argument less compelling than most on Slashdot seem to.

  58. How is the GPL Designed to turn copyright on it's by mindstrm · · Score: 4, Informative

    head? I'm sick of hearing this.

    It does NOTHING to take away ANYONE's rights under copyright.

    Free software authors, like ANY authors, have the right to choose how their works are licensed, and under what terms derivitave works can be made... and that choice includes saying "Anyone can use this as long as they abide by the GPL".

    You are always free to contact the copyright holder of any work available under the GPL and request licensing under different terms, you know. Think the author of a GPL work is perhaps a bunch of people? That depends on the project.. often copyrights are assigned to the project leader... and depending on how contributions are made, that may still be the case despite having lots of authors.

    I'm really unclear on what aspect of the GPL needs to be "challenged". If the GPL does not apply, then copyright law forbids the things people are doing with those works the authors placed under the GPL. It's not a use license, but if you don't accept it, the law is clear: you don't have the right to do certain things with that code.

    SO unless the argument is "THE gpl doesn't apply, so all works available under the GPL are actually in the public domain" there is no argument.

    IT doesn't have to be tested in court... copyright is already testd in court, and the authors of any GPL software are free to sue anyone who is not abiding by the license, and hence, has NO right to do what they are doing.

  59. Not *exactly* by autopr0n · · Score: 2, Interesting

    SCO has no right to distribute Linux whatsoever, since they know 'their' code is in Linux without giving up the rights to that code. However, as long as they are not distributing any GPL'd code, they are in the clear.

    Contrary to what a lot of people think, the worst that can happen to you if you violate the GPL is that you lose your rights to distribute the code, and you might have to pay a civil fine for the GPL infringement.

    But the point is moot anyway, since SCO isn't distributing anything right now, they are not GPLing anything.

    --
    autopr0n is like, down and stuff.
    1. Re:Not *exactly* by Anonymous Coward · · Score: 0



      I call bullshit, this sounds like a troll to me.

    2. Re:Not *exactly* by Rogerborg · · Score: 1

      Nearly. You can't "violate" the GPL, nor can you "infringe" it per se. You can only infringe copyright. Distributing under the GPL just means attaching a GPL license to the source. Note that the action of doing that (demonstrably) isn't the same as the intention of following it. You don't have to mean it, and the license is only as binding as the copyright owners force it to be.

      --
      If you were blocking sigs, you wouldn't have to read this.
    3. Re:Not *exactly* by Anonymous Coward · · Score: 0

      ftp://ftp.sco.com/pub/scolinux/server/4.0/updates/ SRPMS/kernel-source-2.4.19.SuSE-82.nosrc.rpm

  60. Yup. by mindstrm · · Score: 1

    And how should they get more clarifications.. I mean

    - Linus knows where HE got contributions from
    - Those people know where THEY got them from
    - The code is available for the WHOLE WORLD to see, and let Linus et-al know if something isn't right.

  61. The Silver Lining by rhizome · · Score: 5, Interesting

    Like a lot of people around here, I've been watching intently as I perceive something that seems to represent freedom to be under assault from a bunch of greedy and self-serving corp-lawyers. Taking a step back, I've begun seeing this as a good thing because this is exactly the kind of threat that the GPL has been begging for over the years: a battle for legitimacy. Did you think that testing the GPL was going to be a small potatoes deal? The way it's playing out is perfect: a single-minded company wants to pull itself out of a GPL-induced (I'd say, given their Caldera competence) downturn, and an opponent who can well afford the time, money, and expertise to fight this without weaseling out into a settlement. Well, I hope for that last part, but you know what I mean.

    Counterintuitively - and not a little bit idealistic about the legal system's ability to judge without outside influence - perhaps the thing to do is to root for SCO a little bit. Egg them on with false love! Give them a hand up the hubris ladder! Kneel down as they fawn over their petards! Make this the fight that covers many bases as possible so that these things we seem to share an attachment with are the stronger for it.

    --
    When I was a kid, we only had one Darth.
    1. Re:The Silver Lining by Anonymous Coward · · Score: 0

      Great, except that I think you and the original poster are too optimistic. I am for Linux... but I think SCO will win. :-(

      Maybe I have just seen too many people win millions in what should have been obviously frivolous lawsuits... :-(

    2. Re:The Silver Lining by MadJo · · Score: 1

      i agree with you to some extent. I agree that this case could well blow open the way to a society where GPL is accepted by even the big corporations.

      However, I will not root for SCO, because I think it's their only solution, when they don't have the ability to gain profit from their own business, to sue others who can.

      If SCO wins, where will it stop.

      In a NYT article which was posted here on /. recently (can't find it at the moment), one of the members of the SCO-board was quoted saying that it was not their intention of crippling Linux, but that the free days of Linux are over.
      And I personally strongly oppose to that.

    3. Re:The Silver Lining by Anonymous Coward · · Score: 0

      Riiight... SCO doesn't have nearly enough hubris right now. Egging them on would be like walking into the center of a mushroom cloud and lighting a match. :)

      Sure, I'd like to see a good test of the GPL. But I don't think this is it. If SCO can show that they stopped distributing the kernel when they found out about the supposed infringment, then the claim that they GPL'ed their own IP by continued distribution wouldn't wash. [I know, I know, the source is still available. They might try claiming it was an accident.]

      Also, there seem to be plenty of ways they could lose without actually touching the issue of the GPL. For example, a judge could rule that they failed to protect themselves by making the nature of the infringment clear to all relevant parties. At this point, a ruling that they weren't eligible for damages from IBM would probably sink the company, rendering the lawsuit obsolete.

    4. Re:The Silver Lining by rhizome · · Score: 1

      I'm not saying that this is the Holy Grail of GPL tests, or that SCOs claims have any merit. This is just a good opportunity to start getting some caselaw down on these issues. As I see it, there is quite an important issue here in that SCO seems to want to pull back from their GPL stance; to take their ball and go home (with a fat wallet). Perhaps this is all about arcane contract terms, but it's playing out like SCO wants to make IBM answer for Linux and the terms of the GPL. Is it possible to withdraw from the GPL? This is exactly the kind of horror that Microsoft brought up back in the original Halloween document. Well, maybe this can also be a case of making SCO answer for the predatory legal establishment and EULAs to some degree. Now, I'm getting a little far afield.

      The short answer is that I doubt there would ever be a "Mother of all GPL tests", but the more caselaw is down on the books and the more legal tests of *aspects* of the GPL that can be used in the future, the better.

      --
      When I was a kid, we only had one Darth.
  62. SCO are going to be stung... by wukie · · Score: 1

    SCO have stirred the international hornets nest. And soon a lot of angry people are going to start stinging SCO.

  63. Re:Companies just don't get that GPL means busines by fatboy · · Score: 1

    The GPL, by design, will make it unprofitable to sell software sight unseen. If the GPL became dominant, software would be limited to an add-on provided by OEMs, contractors, and philantrophic coders.

    People don't buy "software". People buy solutions to problems. This is way more money is made by contract programming than by selling boxes of software.

    Before you call that a troll--if YOU could be paid $12000 (welfare) to stay home and code, with no boss and little-to-no prejudice against how you get the money, would you?

    What do you mean by "welfare". I don't see contract programming as "welfare", even if it is done for the government. Welfare is a hand out, not the exchange of programming for money.

    --
    --fatboy
  64. Many Copyright Holders by pyrrho · · Score: 1

    You seem to forget, even if SCO is a copyright holder (doubtful at the moment), they are not the only copyright holder! If you lose Linux because the GPL doesn't hold --- SCO CAN'T GIVE IT BACK TO YOU.

    It's not clear to me if the customers can be sued, but SCO certainly can, they are knowingly and wontonly violating the license on other people's IP, which is what these kind of cases hinge on, the intentionality of it.

    --

    -pyrrho

  65. exactly --- utah by Anonymous Coward · · Score: 0

    now they don't get anyone laid! well, at least not before the marriage(s).

  66. If I where a kernel developer by codepunk · · Score: 1

    If I where a kernel developer or I had any knowledge that sco had ever sold and or distributed any code that I had developed I would be visiting the courthouse in the morning. It would be terribly easy to win a lawsuit against them for knowingly distributing and selling my IP while not abiding by the GPL license under which I distribute my code. SCO's supposed 80 lines of code does not make up for the millions of lines of other peoples IP they have illegally sold and distributed.

    --


    Got Code?
  67. Have you ever read the GPL? by autopr0n · · Score: 1

    Actually, not in this case (IANAL). They have indicated that their customers won't be held accountable to SCO... but that makes the code in question (all of it) a violation of the license under which it was distributed. Which means the users have NO right to run the code.

    One of the first things it says is that you don't need to agree to the license to run the code, only to distribute the code.

    Even microsoft can run GPL'd code.

    --
    autopr0n is like, down and stuff.
    1. Re:Have you ever read the GPL? by homer_ca · · Score: 1

      That's the whole point! If SCO/Caldera distributed GPL code, they can't discriminate between different groups who received that code from Caldera and they can't place further restrictions of the distribution of GPL code. i.e. not sue paying customers, but sue freeloaders who downloaded a free iso of Openlinux. What gets confusing is, can they sue Linux users who received the GPL code from another distributor? See article 6 of the GPL below. If a Redhat user received his kernel from Redhat, it seems like SCO has no obligations under article 6 to him because there is no distributor/recipient relationship. However, if a SCO user took SCO kernel source and diff'ed and patched it with vanilla Linus kernel source to undo all the Openlinux patches, he could then get "clean" kernel source that could be recompiled into any other distro.

      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.

    2. Re:Have you ever read the GPL? by topham · · Score: 1

      correct, no dispute from me there... except the code in question (according to SCO) is ILLEGAL.

      As such, neither SCO, nor GPL can grant permission for use.

      With a voided license your left with copyright law...

    3. Re:Have you ever read the GPL? by Stephen+Samuel · · Score: 1

      No big deal... I'll just email RedHat a copy of the SCO kernel that I downloaded from their site on June 18.. This is well after SCO was aware that it's impugned code was in there. I got it direct from SCO, they know what's in it, and the GPL says I have the right to redistribute it.

      --
      Free Software: Like love, it grows best when given away.
  68. SCO hiding facts? by Anonymous Coward · · Score: 3, Funny

    With each statement made by SCO, I become more and more confident that the Iraqi Information Minister is alive and well and it is HE who is truly behind all of this. Who else could possibly have such a complete grasp of the opposite of reality?

    Think about it - he disappears and the SCO FUD machine cranks up. Coincidence? I don't think so.

  69. I have a question... by dcavanaugh · · Score: 1

    As we all know, Orin, Fritz, and the usual suspects are interested in letting the copyright industry attack those who are accused of copyright violations.

    If they pass such a law, can we all go black hat on SCO based on their alleged GPL violations?

    1. Re:I have a question... by Cid+Highwind · · Score: 1

      You think that law would ever apply to individuals?

      Silly rabbit! Special rights are for multinational corporations!

      --
      0 1 - just my two bits
  70. Re:Why can't they realize... by Anonymous Coward · · Score: 0

    what's harry potthead?

  71. SCO vs. IBM vs. [INSERT YOUR NAME HERE] by oaf357 · · Score: 2, Interesting
    After reading the actual letter it seems like SCO is just trying to get its Linux customers to move over to UNIX. That was the biggest ball of sales and marketing (S&M as one fellow /.'er called it) I've ever seen in a letter to a customer.

    Linus didn't have to say a whole lot. The suit doesn't involve him yet and he's not obligated to remove any code from the kernel because A) no one has asked him to and B) the pending lawsuit seems to be the way SCO wants to handle this. Linus does give his opinion of the lawsuit though and I think he would like it if SCO just said, "You know what, we're morons. Sorry about the mess." But, SCO is too deep into this now.

    Just a reminder. I'm consolidating the "worthwhile" points of the lawsuit at the link in my sig. If anyone would like me to add something to that page or would like to contribute commentary on this subject please don't hesitate to contact me.

  72. Re:GPL doesn't help here, unless one reads it by civilizedINTENSITY · · Score: 1

    "The GPL was placed on that code by someone who was not the copyright holder." Impossible, under the GPL. Perhaps you meant "no liscense was attatched". Then everyone is in violation of copyright (since parts would still be under GPL, and the combined work would fail the GPL).

    Likewise its impossible for SCO to try to sell an end-user liscense, since the code in question is combined with GPL-ed code, and hence can't be distributed. Anyone who purchases such an end-user liscense would be buying the Golden Gate bridge based on SCO having a van on the bridge at the time.

    SCO may have never intended to distribute the code...LOL...but they are distributing now, even as I type this. They were "duped" into continuing distribute? Is that what you really mean? If they don't grant their IP under the GPL, then distribuing their distribution is a violation of the GPL. If they had shutdown their FTP servers when they quite selling, your position might have be viable, but they didn't and they haven't.

  73. That is different. by mindstrm · · Score: 3, Interesting

    The only reason NVIDIAs drivers are not covered by the GPL is because binary only kernel modules using existing kernel interfaces were expressly permitted from the beginning by Linus, as an EXCEPTION to the GPL. This means these drivers can be under any license NVIDIA wants. The only reason you can't distribute thsoe drivers with the OS is because NVIDIA says so, not ebcause of the GPL.

    Note - I'm trying to find the clause that allowed it, I'm sure I've seen it before, and it's common knowledge.. but I can't find it, anyone know where it is?

    The license on the linux Kernel itself is not just the GPL, it has an additional clause.

    You quoted Section 7 of the GPL.. let's look at more of it:

    "For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. "

    That's pretty self explanatory.. if SCO cannot distribute copies that allow ANYONE to redistribute in the same manner, they cannot distribute at all.. Therefore, they cannot just license their version of linux to their users only, and impose restrictions on others.

    1. Re:That is different. by Rogerborg · · Score: 1

      You can't find the clause because it's not there. Can you quote it? No, so please stop talking out of your arse lest the more exitable slashbots believe you rather than taking the time to read it themselves.

      --
      If you were blocking sigs, you wouldn't have to read this.
    2. Re:That is different. by spitzak · · Score: 1
      He's talking about the license for Linux, you moron, not the plain GPL.

      Look up the word "exception" in the dictionary. Now imagine an "exception to the GPL". Now why the hell do you think that text is in the GPL? By definition it is NOT in the GPL.

    3. Re:That is different. by DarkMan · · Score: 2, Interesting

      Sorry, I'm afraid that there is no exception clause. The lameness filter doesn't like in the diff output, so I've removed it. Each line of the diff output started with

      sdjp@fermi:/usr/src/linux-2.4.21$ curl http://www.gnu.org/licenses/gpl.txt | diff COPYING -
      [Curl output snipped for lameness filter reasons]
      [Begin diff output]
      1,16d0

      NOTE! This copyright does *not* cover user programs that use kernel
      services by normal system calls - this is merely considered normal use
      of the kernel, and does *not* fall under the heading of "derived work".
      Also note that the GPL below is copyrighted by the Free Software
      Foundation, but the instance of code that it refers to (the Linux
      kernel) is copyrighted by me and others who actually wrote it.

      Also note that the only valid version of the GPL as far as the kernel
      is concerned is _this_ particular version of the license (ie v2, not
      v2.2 or v3.x or whatever), unless explicitly otherwise stated.

      Linus Torvalds

      [Line of hypthens the lameness filter doesn't like]

      [End diff output]

      The only difference between the liscence on Linux and the GPL is noted there, and it does not mention binary drivers.

      So, either it's a breach of the Linux lisence to use them (because there is no exception clause), or no clause is required to use them legally.

      Also, note that these actions by SCO do not involve distribution. They claim that they found some of thier IP [0] was illegally placed in Linux. They have then seperatly given a group of people a non-transferrable liscence to use that IP. I cannot see how that caused GPL to apply.

      As I mentioned above, the fact that they distributed Linux puts them in a sticky situation. Note that it doesn't mean that they accepted the GPL - it means either they accepted the GPL, or were in breach of a software liscence.

    4. Re:That is different. by Rogerborg · · Score: 1

      And you can quote this, can you? Can you, you shrieking lickspittle? Go on, shut me up by quoting it. I'm waiting.

      --
      If you were blocking sigs, you wouldn't have to read this.
    5. Re:That is different. by Anonymous Coward · · Score: 0

      NOTE! This copyright does *not* cover user programs that use kernel
      services by normal system calls - this is merely considered normal use
      of the kernel, and does *not* fall under the heading of "derived work".
      Also note that the GPL below is copyrighted by the Free Software
      Foundation, but the instance of code that it refers to (the Linux
      kernel) is copyrighted by me and others who actually wrote it.

      Also note that the only valid version of the GPL as far as the kernel
      is concerned is _this_ particular version of the license (ie v2, not
      v2.2 or v3.x or whatever), unless explicitly otherwise stated.

      Linus Torvalds

      This is directly copied from my local 2.4.18 linux kernel
      source package from file /usr/src/linux/COPYING.
      Following that paragraph comes the stock GPL.

      Is that good enough? If not goto kernel.org and
      downlaod the kernel source yourself and have a look.
      If you want a link, how about using google groups
      with "linus exception gpl modules" and you will find
      more then enough chatter about this issue, which has
      obviously been quite well known all around.

    6. Re:That is different. by Anonymous Coward · · Score: 0

      This is interesting, and the upshot is that SCO can never, ever collect royalties on Linux.

      They cannot collect from any of the major distros, because none of them can distribute a SCO-encumbered kernel at all. They cannot distribute it themselves, unless they granted their customers unlimited, royalty-free redistribution rights consistent with the GPL. They can't do this because it undermines their ability to collect royalties.

    7. Re:That is different. by Rogerborg · · Score: 1

      Fair enough, thanks for that. It's not an exception to the GPL though, as the original poster claimed. It's an assertion of applicability. That the GPL requires this assertion highlights once again just what a badly written, over verbose, under specified mess it is. I'm sticking to my IP lawyer's advice, which is to let some other sucker be the one to pay to clarify the GPL in court. Step up to the plate, IBM.

      --
      If you were blocking sigs, you wouldn't have to read this.
  74. The most important line in the letter is... by MrGrendel · · Score: 3, Informative
    SCO will continue to honor all contractual obligations with existing customers including product updates, service, and support.

    In other words, they have every intention of continuing to distribute Linux to at least some of their current customers. They have not only violated the GPL in the past, but they are planning to violate it in the future.

    1. Re:The most important line in the letter is... by Anonymous Coward · · Score: 0

      Well then SCO should be sued for a trillion dollars .. hey .. they set the precedent for dr evil amounts ..

      dvnull

    2. Re:The most important line in the letter is... by dinog · · Score: 1
      Hmm... They supplied some of their customers with code under a GPL license. Doesn't this mean,to honor their contractual obligations, they have to allow their customer to redistribute the GPL'ed code ?

      Dean G.

  75. Another Good Linus Quote by Anonymous Coward · · Score: 3, Informative

    eweek: Has this legal matter affected in any way how you or any of the kernel developers are working on the current kernel?

    Linus: Not that I know of, although I do suspect a fair amount of time has been wasted just worrying about it.

  76. Hmmm... by Trolling4Dollars · · Score: 0

    Perhaps this really isn't about Linux at all? Maybe SCO is actually going for the GPL's throat. It would seem to make sense in light of the anti-protest signs where they tried to paint Linux and it's users with the broad brush of "communism" and "piracy". I know there is a lot of disgust with the GPL in the corporate world because it creates a truly level playing field which is something no good little capitalist wants. I've heard over and over on this board from several neocons that it's always better to have every unfair advantage over your competitors as possible. That's pretty much the complete opposite of what the GPL stands for. If they wind up winning AND proving that corporations can break the GPL and get away with it, then they will have gained the ultimate unfair advantage indeed.

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

      Overrated?!!! What fucker said THAT! I thought the posting by trolling was pretty on topic and insightful. How many people have posited that this whole SCO thing is an attack on the GPL? I would venture to say nil. You fuckers. I hate all Slashdot moderators because they can't moderate worth a fucking turd in the sewer. Stupid asshats.

  77. 20 years is a long time by symbolset · · Score: 4, Funny

    We look forward to helping you and your customers meet your business needs for the next twenty years. -- Optimist Darl

    --
    Help stamp out iliturcy.
  78. worst case... by autopr0n · · Score: 2, Insightful

    Is that linux developers simply 'roll back' to wherever Linux was before IBM first contributed, and start again from there. I doubt it would take much time to get back to where they where, especialy if programmers simply 'resubmitted' patches that they were sure they owned the rights to and had not been tainted by IBM.

    --
    autopr0n is like, down and stuff.
  79. Re:Companies just don't get that GPL means busines by Anonymous Coward · · Score: 0

    could you explain your reasoning further? and please go a little further than parroting the idiotic viral claim: if you use somebody's code you have to do it under the terms of the copyright holder. you are also free not to use that code or try to negotiate a different license. so how is this different from any other license?

  80. They know they can't get license fees for Linux... by TurnYourRadioOn · · Score: 2, Informative

    It's pretty clear.

    They realize how hopeless and preposterous it is, to get licensing fees from Linux users in general. Instead they try to get what they can by bullying people into using (paying for) "their" Linux.

    It suggests they're aware of how thin the ice is where they're standing...

  81. Damn It, somebody sue SCO by bwt · · Score: 1, Interesting

    I'm really getting tired of this crap. When are kernel developers going to sue SCO for violating the GPL? All of SCO's past profits from selling Linux are a direct result of their piracy. This is a big pot of gold -- why is nobody going after it?

  82. It's worse than that by Anonymous Coward · · Score: 2, Interesting

    If you're really pissed at The SCO Formerly Known As Caldera, and you've ever purchased one of their Linux distributions, sue them to get your $50 back. They claimed they were selling you code under a certain license, now they're retracting that claim. If they can get away with that at all, it shouldn't be without at least giving you your money back.

    Of course, it's not mainly about the money: it's about thousands of people dragging SCO to small claims court as their own personal way of saying, "Fuck you, too!"

    1. Re:It's worse than that by bovinewasteproduct · · Score: 1

      Yeah, and the only problem is that if you lose, you get to pay THEIR lawyers bills...

      Not fun..

      BWP

  83. Forget the GPL, make them put up or shut up! by Dr_Marvin_Monroe · · Score: 3, Interesting

    Don't ya think SCO should have'ta PROVE that there was copying taking place first?...I mean, why bother with the merits of the GPL and if it's enforceable here. The relevant issue is about illegal copying and supposed "obfuscation" of code to make it look "not copied." We have not even gotten to trial yet!....until the judge rules guilty, or I see the evidence myself, it's all a bunch of accusations to me. We are entitled to our innocence right up to the verdict, or even after the verdict if we can get a good PR firm.

    Slashdot should be helping to shape the language of this media hype event, we shouldn't even be debating this crap until the evidence is presented....we should be encouraging the press to do likewise....all press comments should be "we are within our rights, we obey the law, we are unconcerned, we'll see the bastards in court, business as usual..." That's precisely how IBM's handled the case so far..."we are right, we know it, we'll be seeing ya' in court."

    Even answering their charges only serves to shift the debate and allow them control over the media "language" of the case. With their weak case, they will attempt to shift the spotlight to anything BUT proving that copying took place, who did it, and the chain of custody along the way.

    The best answer is to deny, deny, deny....then claim that you can't recall, but you are sure that you didn't do it, 'cause you never break the law. That's how Bill G. does it...it seems to work pretty good....

  84. STOP THIEF!! SCO is ripping off SUSE! by pair-a-noyd · · Score: 2, Funny

    go to ftp.sco.com and browse around.
    (/pub/scolinux/ipfserver/4.0/SRPMS)
    They are distributing YAST.
    THIEF!!!

  85. read the damn thing before you talk about it by autopr0n · · Score: 1

    The GPL spesificaly say you don't need to agree to it to distribute the to use the stuff

    --
    autopr0n is like, down and stuff.
    1. Re:read the damn thing before you talk about it by Malcontent · · Score: 1

      If you don't agree to it then it reverts back to copyrights of the coders. If you don't agree to the GPL then you have to get all the authors persmissions.

      --

      War is necrophilia.

    2. Re:read the damn thing before you talk about it by dmaxwell · · Score: 1

      If you don't agree to it then it reverts back to copyrights of the coders. If you don't agree to the GPL then you have to get all the authors persmissions.

      Let's be clear about who has to do what. The GPL does not regulate usage; it regulates re-distribution. In regards to the Linux copyright holders, OpenLinux users are in the clear. Since SCO is trying to cloud the waters those users probably shouldn't try to re-distribute SCO's Linux but they are just fine on usage. There's no need for any SCO Linux users to rip out their mail-server say.

      SCO on the other hand does need the authors' permission to distribute the code on the new basis they are attempting to create. They have a snowball's chance in hell of getting it.

    3. Re:read the damn thing before you talk about it by bear_phillips · · Score: 1

      SCO DID distribute the stuff. Under your theory I can take any GPL'd program, add in my own code. Distribute the code then go back and say, "Oh my propriatary code accidentally got into the GPL'd code, I give a license to everyone who paid me money, but nuts to those other guys." SCO wants to have it both ways and the GPL says that you can't. SCO DID distribute GPL'd code so now it either has to abide by the GPL or not. SCO can't give a special license to its friends.

      --
      http://www.windmeadow.com/
    4. Re:read the damn thing before you talk about it by Rich0 · · Score: 1

      It does mean though that you could only install one copy for each one you received on CD. If you got a new computer you couldn't install linux on that one as well - as you are essentially redistributing it to yourself. Copyright law, after all, does restrict your right to copy. I doubt that the ??AA lobby would allow the courts to rule on this any other way...

  86. Paid for IP? by The+Monster · · Score: 1
    "SCO Group has assured its Linux customers that any company that's paying for Linux software and services from SCO Group is already paying for SCO's intellectual property."
    But what about the intellectual property of everyone else that contributed code to SCO/Caldera Linux? Since that IP was licenced under the GPL, SCO/Caldera has no right to use it unless they release it under the GPL as well. They sent out to their paying customers CDs that include the GPL text. Those customers have every reason to believe that those were the terms of the license granted to them, and (although IANAL, I know people who are, who have explained to me that) courts tend to interpret any 'gray areas' in a license that is not negotiated between parties (but just placed on goods or services 'take it or leave it') in the terms that grant the greatest rights to the customer. So, any customers who paid even $1 to SCO/Caldera and received Linux as part of the package, have had their copies of Linux released to them under the terms of the GPL, which grants those customers the right to redistribute the code royalty-free. I trust that at least one of them has already submitted a copy of the source code they got from SCO/Caldera back to the community.

    Even if SCO can somehow win against IBM, they really can't go after anyone else now that they've willingly released code to others under the GPL. Their argument is that they didn't know that the code they willingly released was theirs, but they knew they released it - they were quite willing to let their customers have the rights granted by the GPL over the code so long as they thought someone else owned the original IP, even though the GPL says they're licensing their IP royalty-free. I don't see any way they can navigate this legal minefield and not get a limb blown off.

    --

    [100% ISO 646 Compliant]
    SVM, ERGO MONSTRO.

    1. Re:Paid for IP? by TomV · · Score: 2, Interesting

      Since that IP was licenced under the GPL, SCO/Caldera has no right to use it unless they release it under the GPL as well.

      As far as I can gather, SCO's position seems to be, at its heart, that the old UNIX System V AT&T license (or rather, every single one of the numerous SysV licenses, AIX, Dynix, etc) was, to use a Ballmer-ism, 'viral', unstoppably so, in their view.

      They've been pretty clear that anything designed to work with any flavour of UNIX, by anyone in possession of any variant of the SysV licence, is in their opinion, automatically part of 'the UNIX intellectual property'. Therefore, for example, because Sequent developed their NUMA code whilst bound by a SysV license for Dynix, SCO's position seems to be that NUMA is automatically theirs.

      And from that position, it's easy to see how SCO would make the leap to claiming that there's no GPL issue with Linux, because ALL of the Linux code, due to the supposedly viral nature of the Sys V licenses, is theirs to start with, so not only would they claim the absolute right to distribute the Linux code as they please, they would also tend to the view that no one, not Torvalds, not Stallman, can claim any ownership of anything which interoperates with any system derived from any system with any ancestry which might have involved a viral SysV license. In SCO's view, if it works with UNIX, it's their property regardless of any other factors.

      Now clearly this looks like a lot of self-serving boholox, but i can believe that the old (convicted monopolist, remember) AT&T might very well have put some thoroughly draconian terms into their licenses, and, horrifyingly, if the sysV licenses do turn out to be viral, then SCO wins, hands down.

      tomV

    2. Re:Paid for IP? by hobsonchoice · · Score: 1

      I also believe that's one of their possible theories.

      However the huge hole in it, is that not all (majority of?) Linux contributors have signed Sys V licenses. In which case, they need an even more expansive definition of derivative than something than might be in the AT&T contract.

      The other question that arises, is where would this leave the OpenGroup. If SCO owns anything remotely UNIX-like, Open Group's UNIX role would be redundant. Novell sold some UNIX rights to SCO, and gave some to OpenGroup, so even if AT&T had the broadest rights, I don't think it automatically follows the rights have passed down intact from AT&T to USL to Novell to SCO, undiluted - at least in the Novell/SCO case, it doesn't seem to have been Novell's intent.

    3. Re:Paid for IP? by tjawatts · · Score: 1

      [quote]AT&T might very well have put some thoroughly draconian terms into their licenses, and, horrifyingly, if the sysV licenses do turn out to be viral, then SCO wins, hands down. [/quote] No they dont win hands down. IANAL but I believe the terms could be invalidated for being unreasonable, dont remember where I read that but I think it was from a lawyer. Tony

  87. Don't forget the "Just because we don't..." clause by magores · · Score: 3, Informative

    Okay. I'm nodda Loi-yer. But I've played one on TV. And this is one thing I have learned...

    In every contract I have written, signed, and/or approved there has been a clause that says something to the effect of...

    "Just because I decide not to enforce a particular section of this contract today, doesn't mean I don't have the right to call for enforcement tomorrow."

    I don't know all the details of the GPL, and I don't know all the details of any agreements that SCO has with other companies. But, at first glance, I rate it this way...

    "Any and all" > "Just because I decided to sue you and not him"

    Of course, as some have pointed out, If SCO can prove that their IP was given out, without their knowlege, then the "any and all" may be pre-empted.

    Then again... If the IP was given out, and SCO did know about it, but they chose not to enforce it at all for a given length of time, then their rights are forfeit BECAUSE they didn't enforce it.

    So.. Here's the question.... Did SCO own something, and not know what they owned, and who was using it, for a really long time?
    A) No. They didn't know, and they didn't enforce their rights. Therefore, SCO is dumb and they lose.
    B) Yes. They knew, but didn't enforce. SCO loses again

    No witty signature here. Nothing to see. Move along.

  88. Or... by Anonymous Coward · · Score: 1, Insightful

    You could end up like... what's his name?.... Dave from the LRP witcho bad-ass attitude.

  89. this is true... by intermodal · · Score: 1

    however, someone's sure to be a dumbass and turn it into a class-action, which is never worth it

    --
    In SOVIET RUSSIA... erm...NSA AMERICA, the Internet logs onto YOU!
  90. After the trial....... by bishopi · · Score: 1
    .....I see a scene not unlike THIS in SCO's future.

    Ian

  91. IP Pattents by HeX86 · · Score: 1

    I need to patent my ip before someone steals it: 127.0.0.1

  92. they have already distributed the software by 73939133 · · Score: 2, Insightful

    It really makes no difference at this point whether they declare that they won't sue their own Linux customers: they had already accepted their obligations under the GPL when they distributed their version of Linux in the first place. The only thing that it underlines (again) is how poor their understanding of their obligations under the GPL is.

  93. What if SCO wins by Anonymous Coward · · Score: 0

    What then? Do we just shut down our Unix and Linux boxes and go home? Frightening thought, isn't it? Think about the possibilities. Maybe someone (smarter than myself) should write a Friend of the court brief on the results of such a thing.

  94. an introduction to "New Logic" by foonf · · Score: 4, Insightful

    Here is the problem. You are basing your conclusions on "logic", or as it shall be known now, Old Logic. Old Logic is no longer in effect: we are now operating under New Logic, also known as SCO Logic. Here is how it works, taking the simple example first.

    Sequent has licensed Unix from AT&T. Sequent develops some nifty stuff like NUMA, RCU, etc. for large parallel computers. They then incorporate this into Unix. The result is now a derived work of Unix, and AT&T/successors have "sole relicensing rights" to that derived work. But here's where the New Logic comes in: Not only that version of Unix, but also the original implementations of those technologies themselves, are also derived works, and the Unix license grants them to AT&T, or their successor in holding the license, in this case SCO. You'd think that Sequent's copyrights (now held by IBM) would let them do whatever they want, but this is erroneous: The Unix license grants these rights to SCO, and IBM can distribute implementations of these technologies only according to the terms of the System V license. This is what SCO has claimed all along.

    Now lets apply this to Linux. IBM has incorporated implementations of these ideas, which can only be licensed through SCO even though IBM owns them, into Linux, under the GPL. Under Old Logic, even if we accept the above, IBM has simply broken the GPL, and the kernel without these parts still belongs to the original contributors, and can be licensed under the GPL. But as always, New Logic changes everything: Since Linux, with RCU and NUMA support, is now a derived work of System V Unix (even if it has been created illegally), SCO now has "sole right of relicense" to not only this derived work, but as with Sequent, all previous implementations, even those without the licensed code (just as it applies to implementations of RCU and NUMA before they were incorporated into Unix). And under the New Logic, Linus' copyright matters no more than Sequent's.

    --

    "(Man) tries to live his own life as if he were telling a story. But you have to choose: live or tell." --Sartre
    1. Re:an introduction to "New Logic" by molarmass192 · · Score: 4, Insightful

      The problem is that the term "derived work" is poorly defined. IANAL, but historically, a court will always pick the most narrow definition of such a vague definition to avoid setting unintended precedent. All IBM needs to do is convince the court that the proper definition is constrained to work derived directly from code in Sys V, and that's the end of that. NUMA, RCU, etc are nowhere to be found in the original code so these would be innovations, rather than a derivations. The dictionary is very clear about the distinction between these two. Now, I haven't seen the NUMA or RCU code but I doubt any of the original Sys V code is present anywhere in there.

      --

      Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws-Plato
    2. Re:an introduction to "New Logic" by surprise_audit · · Score: 1
      You'd think that Sequent's copyrights (now held by IBM) would let them do whatever they want, but this is erroneous: The Unix license grants these rights to SCO, and IBM can distribute implementations of these technologies only according to the terms of the System V license.

      I think you missed one little detail in there - when IBM acquired Sequent, they also acquired the RCU patent which then begs the question: how does the RCU patent relate to the "derived work" status SCO is claiming?

      That rustling noise you can hear is the sound of IBM's patent-enforcement platoon preparing for the first volley of lawsuits against SCO...

  95. Good SCO, bad SCO by Anonymous Coward · · Score: 0

    Good SCO... bad SCO... I'm the SCO with the lawyer.

    (oh man, that was really bad)

  96. GPL License Specifics by Anonymous Coward · · Score: 0

    The SCO seems to have fead its bait to a big fish, with the bait being their System V code release with somewhat misleading terms of use, and the fish being Linux. However, the fish may just be big enough to swallow SCO. This is why some analysts say that GPL will be tested.

    I have actually read through the GPL license and I am convinced that:
    1. If SCO releases Linux, it has to release it under GPL.
    2. If SCO releases Linux under GPL, then they have to make it available for download and anyone can get it for free.
    3. If SCO's version of linux contains the copyrighted System V code, than there is somewhat of a mess:

    SCO gets linux under GPL from the linux community. It contains the copyrighted System V code. SCO releases the code back to GPL as its Linux release. This is like GNU's Not Unix, or SCO's Controversial Obfuscation. In any matter, it seems we have a semidecidable problem on our hands, where SCO holds the halting switch. They will probably try to convince court that GPL's re-feedback effect makes GPL illegal because it allows copyrighted or patented code to become vertually impossible to remove from Linux.

    1. Re:GPL License Specifics by KenRH · · Score: 2, Informative
      2. If SCO releases Linux under GPL, then they have to make it available for download and anyone can get it for free.

      Actually not. If they make sure anyone who get a copy also get the source, by exsample only distributing the binaries on a CD with the source, their obligations under the GPL is done. On the other hand everyone who get such a CD can make the contend downloadable on their own, but then that person/company is responsible for making the source available to anyone who get the binaries.

      3. If SCO's version of linux contains the copyrighted System V code, than there is somewhat of a mess:

      Now that SCO "knows" the linux kernel contains their propiteary IP, they may only continue to distribute it if they put that IP under the GPL. If not they will be in breach of the GPL and the GPL is the only ting that allows them to distribute it in the first place.

  97. that is so appropriate... by pb · · Score: 1

    ...that I can even tie it back to a slashdot article from 1998! ...now SCO has indeed been corrupted by The One Ring, but Linux is still like Tom Bombadil.

    --
    pb Reply or e-mail; don't vaguely moderate.
  98. Re:The Gloves Come Off... -- correction by althalus · · Score: 1

    Actually, none of the protesters carried the sco signs. The person who stated that didn't know what they were talking about. The only people who carried the sco signs were sco employees. They kept following us wherever we went.

    Nobody liked having the sco folk with the signs, we just showed enough restraint to not do anything stupid.

  99. Impossible to collect royalties. by Nucleon500 · · Score: 2, Interesting
    Unless every single line of code in the kernel was stolen, SCO can't collect royalties. Assume for a minute that 15% is owned by SCO, and that the GPL doesn't apply to that 15%. (I do not believe this, but just for the sake of discussion...) Suppose SCO said you can only copy their code if you pay them. Because the remaining 85% is still GPL (and can't be distributed unless recipients can also freely distribute), but SCO's 15% can't be freely distributed, it's illegal to distribute the tainted kernel at all (because the recipient couldn't distribute the GPL code, because he doesn't know how to separate it from SCO's code) Even SCO couldn't distribute the kernel until they either distributed their 15% under the GPL, or seperated their 15% from the GPL'd 85%. And of course if they separate it, the community will instantly rewrite the 15%, and the GPL kernel will be whole again. In short, if even one line of the kernel is still under the GPL, SCO can't collect royalties without telling the world which code is theirs.

    IANAL. Also, I don't think any of SCO's code is actually in the kernel. I'm describing a safety net, possibly the last, but I don't think it will go nearly that far.

  100. Re:Companies just don't get that GPL means busines by Aadain2001 · · Score: 1
    ...but I doubt they are that dumb.
    I direct you to exihbit A: 2 terabytes of news articles from /. about SCO and their actions/remarks made since sueing IBM. The prosecution rests its case.
    --
    Space for rent, inquire within
  101. Good news; bad news by DaveAtFraud · · Score: 4, Insightful

    The bad news:

    Licensing lawsuits (or lawsuits in general) are rarely about right and wrong and are more about which side can afford better lawyers. Even an egregious violation of the GPL by SCO would still come down to this. To some extent, this is why companies don't take the GPL seriously. Under any other circumstances, who is going to cough up the big bucks to challenge some company's higly paid legal team?

    The good news:

    IBM can afford very good lawyers and has a huge economic incentive to fight SCO "to the death." IBM has been moving to a "services" based business model for some time and free, cross-platform operating systems and software fit into this plan nicely.

    The unknown:

    So far, IBM has publicly been asserting only that they have a valid license to use System V Unix as per their original license agreement. They have not asserted anything regarding the GPL with regard to either the code in question or SCO's use of GPLed software in SCO Linux. This whole mess could and probably will get settled without the GPL even being brought up in the courtroom.

    SCO's action of attempting to stop IBM from shipping AIX by revoking the license is fairly weak since it requires SCO to show that IBM *as a corporation* deliberately assisted Linux development by violating the SCO copyright on certain code. All IBM has to do is say "No we didn't. Prove it." (which they have) and SCO is faced with the task of finding e-mails or memos or whatever that directed some of IBM's kernel contributors to copy code. Barring finding such evidence, SCO would be stuck going after the individual contributors. In this matter, the question of whether or not some Linux code may be lifted from SCO's codebase only proves that their was a violation of the SCO copyright; not that IBM as a corporation is responsible for the copyright violation. More likely, all SCO will "discover" is a memo from IBM's legal department to one or more of the contributors involved stating that it is a copyright violation if you cut and paste but its not if you simply apply techniques learned to the Linux code. Hardly a smoking gun.

    SCO could sue the individual contributors involved in which case IBM would probably still foot the bill for their legal defense since IBM would just say they are standing by their employees in a business related matter and chances all SCO could get out of it even if they win is a retraction of the code (chage a few variable names and the indentation and comments and someone else can re-submit it) and maybe a few bucks since chances are we aren't talking milionaires here.

    My guess:

    This is primarily a FUD campaign on SCO's part to try to derail Linux. They don't have a good case but they sure are making a lot of noise to make up for it and IBM knows it. Unfortunately, there's no good legal way to say, "Put up or shut up!"

    --
    They that can give up essential liberty to obtain a little temporary safety deserve neither safety nor liberty.
    Ben
    1. Re:Good news; bad news by mcrbids · · Score: 2, Informative

      Unfortunately, there's no good legal way to say, "Put up or shut up!"

      Sure there is. It's called defamation.

      --
      I have no problem with your religion until you decide it's reason to deprive others of the truth.
    2. Re:Good news; bad news by Anonymous Coward · · Score: 0

      > SCO would be stuck going after the individual contributors...

      You are right. Copyright infringement does pierce the corporate vail. So SCO must first prove "IBM" acted with intent, then it can go after the individuals regardless. But that is copyright law, and this case is - so far - about contract issues.

      But, in better news, copyright is very much what busting the GPL is about. There are criminal penalties in copyright law, 1 year per, as I recall. Is SCO about to break the GPL willfully and with malice? Not very good news for SCO, and personally for all corporate leaders playing along.

    3. Re:Good news; bad news by EriDay · · Score: 1

      Licensing lawsuits (or lawsuits in general) are rarely about right and wrong and are more about which side can afford better lawyers.

      I disagree. If SCO can stay afloat, this will go to the supremes. In a decade (or 2), we'll all be citing SCO v IBM as justification for some corner of IP law.

    4. Re:Good news; bad news by Alsee · · Score: 1

      If SCO can stay afloat, this will go to the supremes. In a decade (or 2)

      LOL! Microsft would have to licence one hell of a lot of SCO IP to keep them afloat that long. In it's entire history SCO has never had a profitable quarter until this one, and that's only because Microsoft handed them a big wad of cash. SCO was just about to go under, and this lawsuit isn't going to help their business any. Except their business with Microsoft of course.

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
    5. Re:Good news; bad news by Anonymous Coward · · Score: 0

      This is primarily a FUD campaign on SCO's part to try to derail Linux. They don't have a good case but they sure are making a lot of noise to make up for it and IBM knows it. Unfortunately, there's no good legal way to say, "Put up or shut up!"

      Apparently, there is in Germany. I guess the "lone superpower" chooses not to protect their citizens, businesses, economy, and future well-being as well as some of the rest of the world does theirs. If this country is gonna be "of the lawyers, for the lawyers, and by the lawyers", then it's time for the rest of us to bail!

  102. Pot. Kettle. Black. by goldfndr · · Score: 1

    Linus isn't the only one capable of practicing "due diligence".

    --
    Copyrights, Patents, Trademarks: temporary loans from the Public Domain, not real property ("intellectual" or otherwise)
  103. Can users really be sued? by larryleung · · Score: 1

    Can users of products that contain unlicensed code or patents be sued directly? If so, this seems to cause a huge problem with *all* software, since anything I use could potentially have legal problems.

  104. Re:So many of us.... by The+Bungi · · Score: 1

    Finding Nemo?

  105. Re:BIll Gates must be smiling a million dollar smi by Mr.+Hankey · · Score: 1

    I don't see the connection. If SCO were to somehow have an actual case and win, they've mentioned that they are interested in going after the free BSDs after that. The license doesn't really interest them as much as their claim of owning the rights to every OS on the planet outside of Windows.

    --
    GPL: Free as in will
  106. Oh Damn by infonography · · Score: 1
    I just got an Email, SCO is suing me!

    Ha got them, I use Solaris on Ultrasparc. Good luck lamers.

    --
    Sorry about the writing. Robot fingers, you know? Cliff Steele in DOOM PATROL #23
  107. This is exactly why GNU exists, and what its about by The_Dougster · · Score: 4, Interesting
    Linus wrote the Linux kernel because he wanted to toy around with a Unix-ish system but he couldn't afford the AT&T license. I use GNU because I want the same thing, and no, as a home user, I do not want to have to license SCO Unixware. A _lot_ of hard work has gone into GNU and the Linux kernel just so that people like you and me can have the worlds best operating system to experiment with and learn from.

    I have indeed been a SCO sysadmin, and it is an ugly hard-core Unix with no frills, no hand-holding, and it ain't Linux. If you think that Linux isn't ready for the desktop then SCO Unix is about ten years behind Linux in this regard. Basically it sucks in every respect except that SCO will come in and hook up a bunch of consoles for you and will write you some lame app in Unibasic to run on your terminals. That was the old SCO, the new SCO probably doesn't get their hands dirty with such stuff like writing programs.

    Having run their OS, it was OK, nowhere near as good as GNU+Linux but it was OK, something like NetBSD with FVWM2 I suppose, except not as good. SCO reminded me of Ultrix on the university terminals about ten years ago.

    But Linus did a clean-room implementation of the Unix kernel, and Stallman's FSF wrote the rest of the GNU OS as a clean room implementation as well. This was so that you and me could piss around with a real Unix-like system at home without having the bankroll to install AT&T UNIX. I don't know what you know about how SCO operates, but they implement the High Priesthood almost as good as IBM does.

    When I was the SCO sysadmin, the management totally freaked out when they found out I had even touched the SCO box! But the mods I made (since I had learned using Linux) pleased them so they let me keep working with it. I replaced as much as I could with GNU so I was running SCO/GNU which was better than SCO. The little box was humming better than it ever did. I hacked the Unibasic code and implemented ANSI-BBS terminal support in addition to Wyse-30 "magic cookie codes" and Whoaa! We could use the "telnet" thing just as good as the Wyse-30's!!! Amazing! No more garbled screens ... don't have to walk over to the termial anymore!

    Linux exists as a learning tool. How else are you going to learn Unix as a home user? No it isn't ready for the desktop, and it may never. It is an old-school "big iron" OS and you ought to thank your lucky stars that you have it.

    --
    Clickety Click ...
  108. /. effect by Anonymous Coward · · Score: 0

    click here to contribute the the SCO /. effect for 23 June 2003 and help SCO spend their remaining cash faster thus stimulating the economy and creating jobs for our hurting IT sector!

    http://www.sco.com/cgi-bin/search.cgi?q=truth

  109. Re:BIll Gates must be smiling a million dollar smi by Anonymous Coward · · Score: 0

    I don't see the connection. If SCO were to somehow have an actual case and win, they've mentioned that they are interested in going after the free BSDs after that. The license doesn't really interest them as much as their claim of owning the rights to every OS on the planet outside of Windows.

    And what makes you think that Windows (or MacOS, or BeOS, or anything else for that matter) is immune from this insanity? McBride has stated that *ALL* operating systems are dirivitives of UNIX and therefore may be infringing on SCO IP.

  110. Re:Companies just don't get that GPL means busines by Malcontent · · Score: 1

    "It's almost as if the GPL is too "far out" and too liberal for anyone in corporate America to really believe it's real or take it seriously; they seem to think they can just pretend like it isn't there and the courts will wink and understand"

    They think that and they are right!

    Can you imagine this supreme court ever siding with a long haired hippie radical over some corporation?

    --

    War is necrophilia.

  111. IBM's Response by Quothz · · Score: 3, Informative

    I don't see this on this thread, but Lord knows it might be elsewhere. IBM has promised to take it to court here. Quothz -- Suffering from .sig anxiety.

  112. Re:Companies just don't get that GPL means busines by Malcontent · · Score: 1

    "It's entirely possible that the concept of copyleft could be tossed out, as being an unfair infringement upon the innovation and artistic progress of others. "

    You are talking about copyright. GPL gives you rights, it does not take them away.

    The authors copyright takes away your rights to artistic progress, GPL allows you to use the authors work under certain circumstances.

    --

    War is necrophilia.

  113. See sco run by Billly+Gates · · Score: 2, Funny
    See SCO.
    See SCO lie.
    See stocks fly.
    Fly stocks, fly!
    See Gartner blow.
    SCO stocks grow!
    Grow stocks! Grow!
    See Novell.
    See Novell smack,
    Smack SCO! Smack!
    See IBM.
    See IBM laugh.
    SCO lawyers barf.
    SCO stocks cut in half.
    See SCO.
    See SCO whine.
    SCO says "It's mine!"
    See IBM.
    IBM puts foot down.
    SCO execs start to drown.
    Drown SCO, drown!

  114. Re:BIll Gates must be smiling a million dollar smi by Mr.+Hankey · · Score: 1

    I believe he excluded Redmond, but still, that's my point exactly. It really has little to do with the GPL, more to do with greed on the part of some lawsuit-happy executives.

    --
    GPL: Free as in will
  115. WRONG, WRONG, WRONG!!! Re:GPL doesn't help here!! by Anonymous Coward · · Score: 0

    Where you're wrong is that the GPL, a license, would still control the distribution of all the copyrighted code that was not owned by SCO. And because of the viral nature of the GPL, SCO can't pick and choose. If they distribute linux they must do so according to the terms of the GPL license which prohibits the inclusion of code without the accompaniment of the source code. SCO would have to strip out the code which supposedly belongs to them and release it separately as a patch, with a different license. Therefore, if/when SCO distributes GPL'd software in violation of the GPL, what's really important is that they are actually infringing the copyright of the hundreds of different authors of GPL'd code because they don't have any other license to distribute that other persons copyrighted code. That opens SCO up to copyright infringement lawsuits by all of those authors. The GPL is a license. It does not wave the copyrights of GPL'd code. It's simply a license that gives rights to users detailing the ways in which they may/must use the code. Simply, if you redistribute GPL'd binaries, you must also include complete source code.

    There are a few things that are certain in this case.
    1) Copyrights are copyrights. If you are the author of code, you own that code and the copyright for that code immediately. Distributing your code according to a GPL license does not change that.
    2) SCO must adhere to the GPL for all the code that they do not have IP claims to. Which is most or all of the code. If they are unable to adhere to the GPL for the code they don't own, then it is illegal for them to distribute that code.

    As I see it, there is really only one scenario that would be really truly damaging to linux. And I think I'll keep that idea to myself rather than accidentally help any SCO lawyers that are lurking. But the most interesting question I wonder about is how much GPL'd code has SCO stolen and put into they're products without releasing that back into the wild? That's a flagrant violation of the GPL and opens SCO up to a class action lawsuit from all linux kernel developers. That would be very interesting.

  116. SCO Confirms They Can't Use Linux by SEWilco · · Score: 5, Interesting
    The /. summary has a link to the letter on the SCO web site.

    1. SCO confirms in this letter that SCO is selling Linux.
    2. The GPL sections 6 and 7 seem to restrict use of the GPL if they are affected by (their own) restrictions on GPL-protected tools.
    3. The IBM Public License terminates the license if patent litigation takes place.
    4. Item #2 in the letter says SCO is suspending sales of Linux.

    Well, what SCO Products might be affected by the GPL and IPL?

  117. OK, so can some one revoke SCO Linux license? by ArcticCelt · · Score: 1

    I agree with you, but the problem is that they already benefit from the work of people like you and they seams to not respect the GPL. Is it possible to revoke their use of Linux because they don't respect the GPL and ask them to destroy all their previous distribution of SCO Linux. (Then the next step is to sue them for 1 000 000 000$ and give this amount to different organizations of the open source movement. ;) )

    --

    Yahh, hiii haaaaa! -Major Kong, from Dr. Strangelove
    1. Re:OK, so can some one revoke SCO Linux license? by Anonymous Coward · · Score: 3, Interesting

      Each copyright holder can have their own go at SCO for breaking the grant to their work as specified under the GPL. Each and every God bless'ed one of them.

      Notice I did NOT say "licensed under the GPL". As you ALL know, the GPL is a grant. A grant, without which, SCO has NO RIGHT WHATSOEVER to make even a single copy of the work in question.

      Copyright law stipulates prescribed penalties when the infringment was, er, non-accidental and a specific level of damage cannot be set. I belive the number is/was $100K or $150K per infringement.

      GPLed works would probably fall in that catagory. The GPL is "good and true", as long as copyright is the law of this land, but dollar damages would be pretty hard to set.

      Law says... "per infringement". Each and every holder of a copyright within Linux would have the right to declare at least one infringment.

      In a way Linus theory on "distributed copyright holding" vs. the FSF's centralized approch may prove an advantage here. FSF can only sue once per infringement. The Linux case would quickly grow and the courts would have a hard time grappling with the possibility that a single act of "copying" could result in such massive statutory liability.

      Better step up soon, 'tho. I'd bet SCO can't pay you all. Something of a lottery, to be sure, but you never thought you'd ever be able to get paid $100K for contributing to Linux, did ya?

    2. Re:OK, so can some one revoke SCO Linux license? by Znork · · Score: 1

      "Per infringement" means "per copy you make". If they make and sell 1000 copies, they commit 1000 infringements.

    3. Re:OK, so can some one revoke SCO Linux license? by Anonymous Coward · · Score: 0

      interessting, I have had over the years fiftheen different linux versions. If this could become through, I'm willing to install a few dozens.

    4. Re:OK, so can some one revoke SCO Linux license? by hobsonchoice · · Score: 1

      > In a way Linus theory on "distributed copyright holding" vs. the FSF's centralized approch may prove an advantage here. FSF can only sue once per infringement

      That assumes Linux contributors (or for that matter FSF) would step up to the plate and sue for copyright violation [and win]. Right now, except for 1 guy sending email to SCO [what happened next?], as reported at theinquirer.net, nobody has sued yet.

    5. Re:OK, so can some one revoke SCO Linux license? by grahamm · · Score: 1

      Per copy you make of each individual copyrighted item. So if A owns to the copyright to X and B owns the copyright to Y, then creating a copy of something containing both X and Y infringes both A & B's copyright. So if 1000 copies are made, that is 1000 infringements of A's copyright and 1000 infringements of B's copyright = 2000 infringements.

    6. Re:OK, so can some one revoke SCO Linux license? by CyberGarp · · Score: 2, Interesting

      "Per infringement" means "per copy you make". If they make and sell 1000 copies, they commit 1000 infringements.

      So if each of the authors of the code in the kernel, took this letter as a piece of evidence, and the other statements and filed a class action lawsuit against SCO--each infringement would be also per author. Let's for fun say that there are 1000 authors of kernel code (I suspect more). That's 1000 copies X 1000 authors = 1 million infrigements. Now since the code is "free", the copyright violations come in at 100k a piece according to a previous IANAL. This puts damages at 100 billion dollars.

      Is this enough money to get a high powered team of lawyers drooling? They of course would be limited by the total cash value of SCO, but I would advocate that kernel developers band together and file a class action. They might just get paid...

      I see your 50 billion and up you 50.

      --

      I used to wonder what was so holy about a silent night, now I have a child.
    7. Re:OK, so can some one revoke SCO Linux license? by DavidTC · · Score: 1
      But wait, there's more!

      SCO is giving your property out with various files and stuff that says those people can give it out, also in violation of your wishes.

      A clever lawyer could argue that while SCO only sold x copies, there could in fact be an unknown number of copies made from the originals, because the people who purchased said copies were delibrately misinformed by SCO that they could hand them out like candy.

      In other words, not only are SCO copyright violators, but they are delibrately misleading others into being copyright violators, and telling them to misinform still others! SCO is obviously liable for all that copying.

      Not only should SCO have to pay damages, it should have to issue a recall, and it should have to try to track down every damn copy of a copy of a copy of the kernel made from SCO's distribution.

      --
      If corporations are people, aren't stockholders guilty of slavery?
  118. IBM used to sell Thinkpads preloaded with Caldera by weeboo0104 · · Score: 1

    ...Linux 2.4. They were the T21 and T22 models. Machine type 2647-L?? Anybody else remember these?

    They were selling them in 2000. I don't think those particular models were good sellers. I wonder if SCO is suing them as retaliation for dropping their particular distro and going with Red Hat and others on their server platforms.

    --
    It is easier to build strong children than to repair broken men. -Frederick Douglass
  119. SCO unixware 7 by pair-a-noyd · · Score: 0, Offtopic

    Welcome to SCO's UnixWare 7.1.3 download area
    file: ftp://ftp.sco.com/pub/unixware7/713/README

    Located in this directory are patches and supplements
    specific to SCO's UnixWare 7.1.3 product.

    Device Drivers for UnixWare 7.1.3 can be found
    at:

    ftp://ftp.sco.com/pub/unixware7/drivers

    Security patches for UnixWare 7.1.3 can be found at:

    http://www.sco.com/support/security/

    What's New
    ----------
    On 10-MAY-03: ./ptf9000c - xAPIC supplement for support of the
    IBM xSeries 440 and IBM xSeries 360

    ptf9000b - The xAPIC Supplement for IBM xSeries 440 has been
    removed and is superseded by ptf9000c

    On 06-MAY-03: ./uw713pk - This directory contains Maintenance Pack 2 for
    UnixWare 7.1.3

    On 30-APR-03: ./uw713up - This directory contains Update Pack 1 for UnixWare 7.1.3

    DRIVERS:
    -------

    ftp://ftp.sco.com/pub/unixware7/drivers/audio - Audio Drivers
    ftp://ftp.sco.com/pub/unixware7/drivers/g raphics - Graphics Drivers
    ftp://ftp.sco.com/pub/unixware7/drivers/n etwork - Network Drivers
    ftp://ftp.sco.com/pub/unixware7//drivers/ storage - Host Bus Adapters Drivers

    MAJOR SUPPLEMENTS:
    -----------------
    ./uw713pk - UnixWare 7.1.3 Maintenance Pack 2 (posted 06-MAY-03) ./uw713up - UnixWare 7.1.3 Update Pack 1 (posted 30-APR-03)

    Open Source packages
    --------------------
    ./opensrc - This directory contains open source packages
    that have been ported to run on native UnixWare
    and are provided with UnixWare 7.1.3. SCO provides
    these source files in compliance with the GPL License
    for these open source packages.


    PATCHES:
    -------
    Filenames size and sum Title ./ptf9000c - This directory contains the xAPIC Supplement for support of
    the IBM xSeries 440 and IBM xSeries 360

    For: UnixWare 7.1.3
    UnixWare 7.1.3 with UnixWare 7.1.3 Maintenance Pack 1

    Filenames:

    ptf9000c.Z 145401 (09385) pkgadd image
    ptf9000c.boot1.img 1474560 (46172) Boot Image Volume 1
    ptf9000c.boot2.img 1474560 (63300) Boot Image Volume 2
    ptf9000c.txt 3888 (12295) Documentation

  120. Re:Companies just don't get that GPL means busines by The_Dougster · · Score: 4, Insightful
    No, for a very long time all companies were scared to death of it. Linux has been the Pariah Dog of OS's for the last decade just because of this. No company would touch it for fear of viral licensing contamination. Personally, I understand the GPL and as an engineer, I leverage it!

    Consider, if I, at work, want to program a robot or something, I can totally use GPL code until the cows come home, and nobody or nothing can do anything about it. The GPL gives me this freedom. As long as I don't try to distribute my derived code, I'm totally legit! And since my company doesn't sell robots, nobody gives a crap as long as it works flawlessly. It is an in-house thing never to be sold or given away, and it does what it is supposed to do perfectly.

    That is how the GPL works for you. And don't try and say I'm ripping off the GPL because I'm not, this is perfectly within the License and my robot program is none of your business as long as I don't try and sell it to you.

    This is a powerfull license for engineers, I sincerely doubt that Visual Studio would give you these broad freedoms even if it was suitable for programming industrial equipment, which I will never know because my company will never pay the ridiculous licensing fees for something like that if a GPL alternative is viable.

    --
    Clickety Click ...
  121. Finding Nemo Seagulls by ashitaka · · Score: 1

    When watching this I could not helped but think that the seagulls had much in common with SCO.

    Mindless repetition of:

    "Mine! Mine! Mine! Mine!..."

    --
    If you don't want to repeat the past, stop living in it.
  122. Not the right reason by SuperKendall · · Score: 1

    No, in the case of bankruptcy the person shorting gets a 100% gain on the short.

    The real reason why most people won't be shorting is the off chance that SCO might win. In that case, the stock doubles or triples in seconds and so do your losses - until the margin call comes in and you are, what they call in the stock business, "screwed six ways from Sunday".

    Shorting a stock is for people with a lot of time to see what is going on and keep the finger on the trigger to pull out if need be. Who needs that kind of pressure when you can find a company that will go up instead, with no limit to profit and a 100% limit on your loss? LTBH is the way to go if you don't want an ulcer or to micromanage your portfolio.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  123. oh well by DigitalGlass · · Score: 1

    eh, i have karma to burn, i think at least...

    here is an idea....

    how about all the executive members of SCO just go shoot themselves! :-)

    im so sick of hearing the letters SCO.

  124. Interesting Development: Linux distributors okay by eric76 · · Score: 4, Informative

    SCO is now saying they have no intention of suing Linux distributors!

    From http://www.computerwire.info/brnews/6FF3308412856B 4D80256D4E005D45FA (Last time I pasted in a URL, it inserted a space. So if you can't connect, look for spaces)

    Linux distributors are safe from legal action by The SCO Group Inc, because the company does not want to destroy Linux, according to SCO's SVP and general manager of the SCOsource intellectual property enforcement division, Chris Sontag. ... "One of the reasons we haven't launched a suit against a Linux distributor is because of the GPL [open source General Public License]," Sontag told ComputerWire. "It would blow up the GPL and destroy Linux and we do not want to do that."

    However, they still appear to want "licensing fees"

    One solution may be a new kind of licensing mechanism for the SCO Unix code, he said, although there remain issues with the GPL that complicate how such a mechanism might be implemented. Sontag said SCO's effort was focused on identifying Linux intellectual property issues and possible mechanisms through which future problems could be prevented.

    Also, notice here that they are now saying the "infringing code" is from AIX and Dynix:

    "There is derivative code from AIX and Sequent Dynix [in Linux], there has also been contribution of derivative code from other licensees, and there has also been Unix System V code directly copied into Linux line by line," said Sontag.

    In other words, SCO now seems to be saying that the so-called infringements are from AIX and Dynix instead of System V.

    What they still aren't saying is those so-called infringements are of code written by Sequent and IBM, owned by Sequent and IBM, copyrighted by Sequent and IBM, and is theirs to do with as they wish.

    While AIX and Sequent Dynix are derivative works of System V, they have a long way to convince me that the IBM/Sequent modifications are derivative works of System V.

    It's a contract dispute with IBM based on definitions that have extremely interpreted to SCO's benefit and in ways that I suspect have rarely, if ever, been interpreted before.

    Also in the article:

    Asked if this meant that SCO was considering lawsuits against other Unix vendors Sontag was more reserved. "Potentially," he said.

    This brings up the obvious questions:

    1) Are they talking about other flavors of UNIX that have IBM/Sequent code? For that matter, are there other flavors of Linux have the IBM/Sequent code?

    or

    2) Have they found other so-called infringements apart from the IBM/Sequent code? Are they claiming, as it sometimes seems, that if System V and another UNIX has a few identical lines of code, there is necessarily an infringement regardless of the actual source of the code?

  125. Re:Companies just don't get that GPL means busines by God!+Awful+2 · · Score: 1

    "You are talking about copyright. GPL gives you rights, it does not take them away."

    Yes, and George Bush is a compassionate conservative, Miller Lite is the great taste that won't fill you up, etc.

    You're living proof of the old adage that if you repeat a slogan often enough, people will begin to accept it without using their critical thinking skills.

    This has been groupthink. Thanks for participating.

    -a

  126. Re:How is the GPL Designed to turn copyright on it by God!+Awful+2 · · Score: 2, Informative


    SO unless the argument is "THE gpl doesn't apply, so all works available under the GPL are actually in the public domain" there is no argument.

    I don't think that's implausible. It may depend on who has the biggest lobby group or whether the present economic climate continues. Did you know that in Red Hat's SEC filing, they list the possibility that the GPL will be found unenforcable as one of their biggest risks of doing business.

    -a

  127. SCO Linux and UnitedLinux by steveha · · Score: 2, Insightful

    Is SCO Linux = a standardized UnitedLinux distro, or is it more complicated than that??

    I wrote a review of SCO Linux 4.0 for Linux Journal magazine. I looked SCO Linux over quite carefully, and talked to SCO people about it.

    SCO Linux 4.0 is United Linux 1.0, with just these differences: SCO's system information tool is included, and Webmin is set up for you (YaST is still there, but SCO recommends and supports Webmin).

    SCO's system information tool is nice, but hardly essential (it's just a tool that puts together a file with information about your system such as kernel version, libc version, etc.) Webmin is nice, but you could easily install it yourself on a SuSE Linux system.

    SCO Linux is almost completely a standard UnitedLinux system.

    steveha

    --
    lf(1): it's like ls(1) but sorts filenames by extension, tersely
  128. "Bigshots"... by Bobke · · Score: 1

    but who got nothing to loose :(

  129. Re:SCOGIRL! by pair-a-noyd · · Score: 1

    That can't possibly be real...
    No way.

  130. Re:Companies just don't get that GPL means busines by Malcontent · · Score: 0

    You can attack me all you want but that does not make me wrong.

    Go ahead and dispute what I said if you can.

    --

    War is necrophilia.

  131. Re:Companies just don't get that GPL means busines by edb · · Score: 1

    The GPL is a real license, and it does not conflict with nor weaken copyright law. Licensing the use of Intellectual Property does not in any way weaken ownership of that IP. Perhaps it's time that this point is driven home by a court. If I don't own the IP (if I don't control the copyright, either by virtue of being the author or by having that right assigned to me by the author), then I usually can't transfer that IP to someone else legally unless I have specific permission of the real owner to do that. The GPL is both the permission for that transfer, and the obligation to do so.

    The GPL is not a transfer of copyright or IP ownership. Just as is true for releases of code to selected parties under more "traditional" licensing terms (like, for money ;-), the copyright still rests with the author of the code released under GPL. The GPL simply licenses a recipient of that code to use it, modify it, and do whatever with it, with the restriction that if they distribute something based on or derived from that licensed code, their distribution must be no more restrictive than the GPL-licensed code they are incorporating.

    If I release code into the community under the GPL, I still own it. I can license that very same code under different licensing terms to other people, as I choose. I can charge money for my code to some people, and give it for free to others.

    But if I have licensed my code under the GPL, then anyone who receives it under that GPL license can propogate it per the terms of the GPL. Indeed, the GPL requires them to propogate my original code along with their modifications to it. Someone who got it for free from me can give it for free to someone who might otherwise have paid me for it.

    The GPL might be scary to the corporate suits and lawyers, but it's really a lot simpler than they fear.

    Or maybe it's actually scarier...

    If SCO has released some code/IP under GPL, then by the terms of the GPL anyone who receives that code is obligated to pass on that code to anyone else who asks for it. Even if SCO charges money from someone else for that very same code.

    But then, IANALBIHPWTMMTL (I Am Not A Laywer, But I've Paid Wayyyy Too Much Money To Lawyers)

    --
    In theory, practice and theory are the same. In practice, they rarely are.
  132. ATTENTION: Parent Subject Is Misleading !! by Anonymous Coward · · Score: 0

    ... It makes it seem like they actually have customers.

    I'm starting to think that I wish this SCO bullshit would just suddenly go away. Is this really happening?

  133. SUE SCO! by mcrbids · · Score: 5, Interesting

    If you, like me, are running Linux *anywhere* (and I'm running it nearly *everywhere* I can) SUE THEM for $10,000 in your local small claims court. They won't show up, they won't defend themselves for such a small, nuisance suit, so they won't lose.

    But can you imagine the impact of 5,000 of these kinds of suits?

    I'd be willing to provide the hosting space for a site that instructs and coordinates this kind of effort.

    --
    I have no problem with your religion until you decide it's reason to deprive others of the truth.
    1. Re:SUE SCO! by Yekrats · · Score: 1

      I doubt you would be able to sue them in small claims court, unless they have an office in your state. I think that if you sue a company across state lines, you need a higher court.

      I'm not 100% sure about that, and I'm not a lawyer. But I think it's possible that 5000 people could do a "lawsuit crapflood" in SCO's home state. ;-)

      --
      Ceci n'est pas une pipe.
  134. Settle down people by spiritraveller · · Score: 1

    SCO knows it has no case against users of ANY Linux distro, much less the one that it is distributing itself. By distributing its version of Linux, SCO bound itself to the GPL, and any code that it released (including what it claims was stolen from UnixWare) is now released under the GPL...

    Their case against IBM is a contract case, NOT a copyright case.

    They have no case against Linux or any Linux users! It's all a PR game.

    "Sue our own customers?!?! Oh wait, no, we would never do that, we love our customers."

  135. Re:Companies just don't get that GPL means busines by God!+Awful+2 · · Score: 1, Insightful


    Go ahead and dispute what I said if you can.

    Stallman claims that the GPL gives you rights and does not take them away. Well, the fact is that the GPL permits you do do certain things and it prohibits you from doing other things. If you want to arbitrarily categorize some of these permissions as rights, that conveys a sense of absolute morality. And while I'm certain that Stallman believes in absolute morality, that's not an opinion that I have much respect for.

    -a

  136. cult? by geoff+lane · · Score: 1

    I wonder how many scientologists work at SCO. Their
    legal tactics are very reminiscent of the behaviour of that cult.

  137. Linux distributors by hayden · · Score: 1
    Rather than focus its legal efforts on the open source community and Linux distributors, SCO is working to identify the issues and come up with solutions in consultation with customers and other parties, said Sontag.
    Most likely scenario is:
    1. You tell the community what is copyright SCO and you want removed (proving that you own it along the way).
    2. The community removes said code.
    3. The community replaces said code with a reimplementation
    4. The community expresses it's love of SCO by going out of it's way to destroy the remaining SCO user base
    There's an optional final step where IBM buys the tattered remains of SCO at a fire sale.
    --
    Nerd: Derogatory term typically directed at anybody with a lower Slashdot ID than you.
    1. Re:Linux distributors by eric76 · · Score: 1

      SCO clearly doesn't want to identify the allegedly infringing code. I guess they'd prefer to have everyone pay them royalties.

      I'd bet that it hurts their case. They have a duty, I think, to ameliorate damages. They are doing nothing to ameliorate damages and everything to propagate damages.

      So one argument in the ulikely event that SCO should file suit against somene and prevail is that SCO could have limited the damages and since they have made every attempt to not limit the damages, they are entitle to none at all.

      As someone pointed out a few days ago, the judge who was appointed to hear the case did just that on another case. Then, one writer wrote a book and sent a copy to another writer along with a note asking him to look through it and let him know if he had any problems with the similarities to his book.

      After the writer went on to write another couple of books, the other writer filed suit against him for copyright infringement.

      The judge ruled that the second writer had plenty of opportunity to object. Since the second writer didn't take that opportunity to object, the judge either dismissed the case (with prejudice, I assume) or found for the defendant (I don't remember which).

      I think that SCO is going for broke. They have taken no action at all that would indicate that they want the infringements to stop.

      They are either going to win big or lose big, most probably the latter.

      For what it's worth, I don't see any need to remove the said code, at least in that which has already been reported. The code is clearly the property of IBM, not SCO and it is clearly not a derivative work of System V. SCO has no sayso over what IBM does with the code just because they added it to a derivative work of System V first.

      In the very unlikely event that SCO should win, it would likely be based on a contract breach finding that IBM did not have the right to distribute their code solely because of the contract. That is, the problem with the code distribution would be strictly between IBM and SCO. Noone else is involved. It's not stolen property in any form or fasion and there should be no requirement whatsoever for those of us using the code IBM distributed to pay any royalties to SCO.

      It would only be problematical if IBM improperly distributed code actually owned by SCO.

      Linus certainly recognizes this based on his reported comments in the press:

      As far as I can tell, SCO doesn't have any IP claims. Their lawsuit isn't about IP claims; it's about some contract dispute with IBM. The only IP issues they have brought up in a verifiable way has been the RCU [Read Copy Update, a way to access data structures that may be changing on multiple CPUs with less locking than normal] work that IBM did, and that SCO doesn't have any IP rights to that I can see: the patents are all IBM, and the code was written by (and thus copyrighted by) IBM too. Well, it was Sequent at the time, but they're all IBM now.
  138. This is the most hilarious thing... by Anonymous Coward · · Score: 0

    ... I've seen on slashdot in weeks. If there was a best of Slashdot and there was a humour category, the parent would get my vote.

  139. credibility by pyrrho · · Score: 1

    You have a point, but the fact is, business expect you to sue. If you use Sun or MS IP against their license, they WILL sue. And most businessmen are aware that actually, companies like Sun and Microsoft are constantly in litigation as plaintiffs and defendants, so I don't think you are right.

    In fact, I think if they don't sue over these violations, they will lose credibility and the GPL will be used like public domain. It must be enforced for a business person to take it seriously.

    --

    -pyrrho

    1. Re:credibility by danheskett · · Score: 1

      I think the greater risk here is that someone might use GPL software instead of an expensive alternative, but they won't if they fear they'll be told to cough up licensing, royalities, or other payments out of budget.

      GPL being destroyed is a bad thing, but only if people intend on using GPL'd software.

  140. For what? by aweraw · · Score: 1
    the authors of any GPL software are free to sue anyone who is not abiding by the license


    I've always wondered, if OSS developers decided they were going to sue someone for misappropriation of their code, what would they be sueing for??

    I mean, it's not like they've incurred any financial damages by their code being misused (unless you consider that they could have taken royalties or a licensing contract for use of the code)... can anyone tell me how an OSS developer would go about extracting money, and what damages they could claim from the code theives?
    --
    5468652047616D65
    1. Re:For what? by Znork · · Score: 1

      Damages would be the same as for copyright violations. Copyright violation is a crime, and it has pretty hefty fines, especially if done for profit. Plus of course jail time. What exact damages would go to the copyright holder in a potential civil suit would be over and above that, of course.

  141. this will never fly by Kludge · · Score: 5, Insightful

    Redhat can make the same claim that SCO is making about distributing Linux code. "We didn't know that code was in there." If not even SCO knew the code was in there when SCO was distributing Linux, how could Redhat be held liable?

    If they attempt to sue a Linux company or a linux user for using Linux, they will have to reveal in court, in public, all duplicated code in question. Once that happens (if this duplicated code actually exists), you can bet your $$ that code will be gone from Linux in less that 12 hours.

    1. Re:this will never fly by Phil+John · · Score: 1

      IANAL, but IIRC ignorance (in this case not knowing that there was copyrighted code in the product) is not a defence that will stand up well in court.

      SCHoes lawyers will probably argue that if you're going to release a product based on an open source codebase as opposed to developing a proprietary solution, you should still have to evaluate every single piece of code to make sure that it doesn't violate anyone's rights.

      Which of course is complete an utter crap, but there you go!

      The only problem I foresee with the removing code scenario is that every single linux install with the offending code will need to be patched...not a small task at all. :o(

      --
      I am NaN
    2. Re:this will never fly by InfoVore · · Score: 1
      ...they will have to reveal in court, in public, all duplicated code in question.

      Not by a long shot. Courts can and do have evidence presented 'under seal' to protect private/proprietary/sensitive information. If I were the SCO lawyers, that would be one of the first motions I put before the bench. They would stand a good chance of the motion being granted, too.

      There are very few "game over" scenarios in any court case. /.ers need to remember that. This is a dance, not a boxing match.

      Cheers,

      I.V.

      --
      "These laws they're passing won't even compile anymore, let alone execute." - anon
    3. Re:this will never fly by HiThere · · Score: 1

      First people will need to be convinced that it's SCO's code. Once that happens, you're right, it won't wait for the lawsuit to end. But I'm not sure that the same evidence that would convince a coder would convince a Judge ... so it's quite possible that even after the checking was done, and the code that the hackers considered questionable removed, that the court could decide very differently.

      This, of course, is assuming that there is anything for anyone to check... it's sounding less and less like that's going to be true.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
  142. Why would anyone take this seriously? by Anonymous Coward · · Score: 0

    He compares a bottom end Walmart computer with a Mac
    which is in the higher price range. He quotes Business
    Week's writer's prediction without giving us this writer's
    scorecard. I'm not going to bother going on, but how in
    the heck do people like this get jobs as journalists?

  143. crackrock by boots@work · · Score: 2, Funny
    From the letter


    In addition, new customer sales indicate that there is still no better option for rock-solid, dependable technology for their core businesses than our SCO UNIX solutions.


    Yeah, right. I hope SCO sober up before they go to court.
  144. What if... by zakezuke · · Score: 1

    What if I have a Caldara CD yet choose to run redhat?

    This is something i'm pondering... I got a free caldara cd at some point for some reason or another. I never thought much about it till this artical came up.

    Not that I actually run caldara, but in theory I was granted a free license at the time.

    --
    There is no sanctuary. There is no sanctuary. SHUT UP! There is no shut up. There is no shut up.
  145. Nnnnnnnggg... by clambake · · Score: 1

    Pshew, ok, got to say it...

    That is wrong. That is theft.

    It's Copyright Infringment, not theft!!!

    Oh wait, but maybe in this case it IS theft? Because they are stealing the RIGHTS, not the code? DAMN IT, Stop messing with my head! NNNNNnnnngggaaaaah!

    1. Re:Nnnnnnnggg... by rking · · Score: 1

      You were correct the first time, it isn't theft (though it is illegal). You can't 'steal' rights. The only way to appropriate a right is in accordance with the law; otherwise the law will always say that the person still has the rights, in which case they haven't been stolen although they may have been infringed upon.

    2. Re:Nnnnnnnggg... by DavidTC · · Score: 1
      I don't know what definations you use, but in my book you can certainly 'steal' something using the legal system, and this case is a perfect example. SCO is trying to steal the rights to every line of code that has ever touched System V Unix in any way, using the legal system and some dubious wording in contracts a decade old.

      This is, to put it bluntly, theft. If they succeed, it will be theft of 95% of the world's operating systems, there is no better way to describe it.

      Now, yes, to be 'theft' requires property to be taken 'unlawfully', so in a strictly legal sense, it's obviously not technically theft if done legally. But that's like saying framing someone for murder and them getting the death penalty isn't 'murder', because the legal system did it. It's certainly ethically murder, and using legally ambigious terms to steal an OS because someone once put something in it that they also put in your OS is ethically theft.

      That's not to be confused with what SCO is doing with GPL software, which is probably just copyright violation.

      --
      If corporations are people, aren't stockholders guilty of slavery?
  146. Linux vs. SCO: The Decision Matrix (How Linux will by Anonymous Coward · · Score: 4, Interesting

    ince the Linux vs. SCO dispute has become quite complex, I have taken the time to distil the various issues of contention into a format which lends itself to easier digestion, and have drawn possible likely outcomes for these issues raised by SCO. Sources for all claims made herein are supplied as footnotes.

    www.cybersource.com.au/users/conz/linux_vs_sco_mat rix.html

  147. Re:Companies just don't get that GPL means busines by KenRH · · Score: 1
    Well, the fact is that the GPL permits you do do certain things and it prohibits you from doing other things.

    Wrong!

    GPL permits you to do certain things provided you comply with certain conditions. Without the GPL, or some other license from the copyright holder, you could not do these at all!

  148. SCO is doomed either way now. by swbrown · · Score: 5, Interesting

    SCO continues to shoot itself in the foot with its public statements. let's review two sections of the GPL:

    "b) 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."

    "4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance."

    SCO could have claimed that since they did not know of the alleged code, that they have not granted rights to that piece of code by distributing it. however, they have stated that they knew months in advance of the lawsuit of the alleged code, and continued to sell and distribute their Linux distribution. They have also continued to distribute their Linux distribution via FTP, and now, they prove in this letter that they know they have distributed the alleged code to their customers, and are planning to hold them harmless instead of removing it from their distributions.

    So, we have two cases:

    1. That SCO has granted rights to the code in question under the GPL by knowingly distributing it. In this case, they have no case against anyone but the original infringer.

    2. That SCO has not granted rights to the code in question under the GPL. In this case, they have voided the license to distribute the kernel under the GPL, and have been knowingly stealing Linux, as they have no other rights to distribute it under. Their announced plan for the future is to continue stealing it for benefit of their customers. They could be sued by everyone who has contributed to the kernel for stealing their IP.

    So, SCO is simply doomed regardless of the validity of their case.

    However, if you've been reading the daily SCO articles and interviews, the whole stolen code thing is just misdirection and FUD. What they are really claiming is that anyone who has touched an invention to System V has not only given SCO rights to that invention, but has given up their own rights to that invention. This is simply madness, but this is their claim. This is their basis for claiming non-SCO technologies like IBM's JFS, and claiming that hundreds of thousands of lines of code in Linux are infringing. The sheer audacity of this claim, that they exclusively own 20 years worth of other people's inventions, is probably why they have avoided seeking a temporary injunction, because they would have to make this argument in court immediately, and it would never hold up. They want this to drag on as long as possible in hopes their slander and libel against Linux pays off on its own.

  149. Re:Companies just don't get that GPL means busines by unoengborg · · Score: 1

    I think the problem is more general than that.
    The understanding of licenses usually seams to be limited regardless of what rights and obligations they might give the licensee. People copy Microsoft software even though their EULA explicitly tells you not to. So how can we expect them to follow the rules of GPL. It's sad really, as it makes it very hard to be in the software business regardless if you sell your software for money or for code.

    --
    God is REAL! Unless explicitly declared INTEGER
  150. Some basic points of fact by Rogerborg · · Score: 3, Informative
    Just to clear up some of the bigger misconceptions out there.
    • "Distributing under the GPL" means exactly and only placing GPL license text in your source. The act of doing so isn't the same as meaning it.
    • You can't sue someone for "infringing the GPL". The GPL isn't a law. You sue someone for infringing your copyright. You can do that if anyone distributes your copyrighted and GPL licensed code regardless of whether they are retaining GPL licenses and attaching them to their modifications. The GPL just gives them their defence. But it's not a contract, and it grants no clear or unarguable protection.
    • If you sue people for violating your copyrights despite attaching GPL license text to your source, that does not clearly disallow you from using the GPL defence against me if I sue you for duplicating my copyrighted source. Confused? Read the GPL. The GPL self destructs if you "copy, modify, sublicense, or distribute the Program except as expressly provided under this License". Suing a third party for violating your copyright (after you've stopped distributing my copyrighted source) isn't covered.
    • There is no clause in the GPL that requires anyone to license their code in perpetuity. All it says is that if you distribute my code with a GPL license attached, I indicate that I agree not to sue you for performing that duplication. The instant that you stop duplicating my copyrighted source, I have no leverage over you.
    • The same applies in spades to patents. There is no clause in the GPL that requires you to grant licenses for your patents, either while distributing or in perpetuity. All it says is that if you pursue your patents while duplicating my copyrighted source, you have no right not to be sued. Again though, once the duplication stops, you can go hog wild pursuing your patent claims.

    We all need to take a deep breath and realise that there is a serious threat here. You may think that the GPL gives you unbreakable rights in perpetuity. You'd be wrong. Read it. Try and find the clauses. They aren't there.

    The problem that SCO has is that they may still be duplicating other people's copyrighted code. Doing so while prosecuting patent rights removes the protection that the GPL gives them from being sued, so get your suits in now. But heck, the GPL is only a gentleman's agreement anyway. It doesn't have the force of law, nor is it a contract. You can sue anyone for duplicating your code regardess of whether you attached a GPL license to it or not, arguing that it didn't form a contract, or that it's revokable because it doesn't grant rights in perpetuity.

    This isn't black and white. SCO have left themselves liable to being sued, but that doesn't mean that they invalidate their right to sue others for duplicating their copyrighted source. The only winners here will be the lawyers. And no, I'm not one, but I've paid enough to them to accept that the GPL is a huge mess (because it doesn't mandate unrevokable and in perpetuity) and that this was an inevitable situation sooner or later.

    --
    If you were blocking sigs, you wouldn't have to read this.
    1. Re:Some basic points of fact by spitzak · · Score: 2, Insightful
      This does not sound right.

      Imagine instead the code had a typical public-domain header ("you may use this code for any purpose, provided that..."). For our purposes this is exactly the same as the GPL, it is a block of text saying under what conditions you may violate the copyright on the code. You are claiming that this text is meaningless, and that if I released public-domain code, I could still sue somebody who makes a copy of that code.

      If what you are saying is true, then all code that does not involve a signed contract (ie public-domain, BSD, GPL, and all open source licenses, all code samples in books, and all commercial programming libraries) are suddenly unsafe to use.

      Personally I think this is hogwash, and I'm not sure what you are trying to say.

      Remember that the GPL is somewhere between copyright and public-domain. It cannot do anything that one or the other of those cannot do.

    2. Re:Some basic points of fact by Rogerborg · · Score: 1

      > Imagine instead the code had a typical public-domain header ("you may use this code for any purpose, provided that..."). You are claiming that this text is meaningless, and that if I released public-domain code, I could still sue somebody who makes a copy of that code.

      Absolutely. Whether you'd win or not depends on whether you explicitely specified "unrevokable and in perpetuity", on how you handle the cease-and-desist, and on how you argue the court case. You could send a cease and desist explicitely nullifying the license and reclaiming your rights. The license didn't form a contract, and you received nothing (directly) in return for granting rights to duplicate. The recipient has had a free ride. Why did they have an expectation that it would be in perpetuity? (you would argue)

      > If what you are saying is true, then all code that does not involve a signed contract (ie public-domain, BSD, GPL, and all open source licenses, all code samples in books, and all commercial programming libraries) are suddenly unsafe to use.

      Yes. They are unsafe to use, which is why my company runs every use of such code past a specialist IP lawyer, and we don't do that often. We do this because the company is set up to be sold, and the value of the company is the code base. Any code that we don't have full rights to is worthless to us.

      We actually entered into a discussion with a third party developer to see if we could pay him for a license for a GPL tool he had written. He declined, telling us that we were fine to use it as it was, and that he had no intention of revoking the license. He was confused by the suggestion that he could do this, and he hadn't even considered the possibility that at some point he might sell the rights to his copyrighted code to a third party who would try and revoke it and exploit the user base (yes, much as SCO have done).

      I'm not saying that SCO will win, just that it is exactly the situation that RMS has been warning about for years. Commercial companies that rely on implicitely licensed code should be watching this case very, very closely. Even if SCO screw the pooch, other observers will be taking notes. Think Microsoft. Think Microsoft buying out SCO entirely and then starting with the little fish rather than going after IBM. Think Microsoft buying out Red Hat and all their "defensive" patents.

      Ultimately, you get what you pay for. Specifically, you get what you can prove that you contracted to buy. Anything else is a loan.

      --
      If you were blocking sigs, you wouldn't have to read this.
  151. Re:Companies just don't get that GPL means busines by Pflipp · · Score: 1

    Yup, and so in response to their picket signs: now who are the crack-smoking, lawless hippies? (Not that that has ever been unclear...)

    --
    "We can confirm that Debian does *not* ship the version with the trojan horse. Our version predates it." [CA-2002-28]
  152. Where is Ransom Love? by Kamelion · · Score: 1

    With all the news I've read about SCO, one question keeps on comming to mind. Where is Ransom Love? If I'm not mistaken, Ransom got the idea behind Open Source and Linux. He was the orriginal CEO of Caldera, or at least was CEO from 1999 to some time in 2002.

    When he ran the company I held stock in SCO/Caldera. I ditched it after he stepped down and the company started becoming evil.

    Sigh. I'd sure like to here Ransom's take on all this.

  153. United Linux died ? by AlecV · · Score: 1

    http://www.unitedlinux.com

    "UnitedLinux, the industry consortium comprised of Conectiva, The SCO Group, SuSE Linux and Turbolinux"

  154. Think everyone is missing the point here... by Karem+Lore · · Score: 0
    I don't think this changes much to be truly honest...If you look at all the SCO postings on slashdot you will come across information regarding the fact that Microsoft, not even a month ago I think, bought the license to use SCO's code...

    To me, this is just SCO declaring publicly that it won't sue Microsoft (being the father of this FUD storm). I am sure that Microsoft and SCO lawyers have been cohooting together to form an alliance. What does M$ want with SCO code anyway? Is it going into Longhorn? If not, did M$ already use the code? In this case, did SCO quietly go to M$ and say "Look, we like you. License or we will be forced to protect our IP against you when we attack Big Blue. We can't justify attacking them and not you. Therefore, license our code, about a month later we will say we will not sue our current customers. Therefore you are safe, and we are free to continue banging Big Blue's door. How about that eh? Pay us enough for the lawyers though, ok?"


    Karem

    --
    When all is said and done, nothing changes...
  155. Re:Companies just don't get that GPL means busines by gotan · · Score: 1

    they seem to think they can just pretend like it [the GPL] isn't there and the courts will wink and understand

    The GPL is what gives them the right to redistribute Linux and create derivatives of it for distribution in the first place. If the court "winks" it away they face standard copyright which is far more restrictive. SCOs problem at the moment is, that since they themselves try to restrict what you may or may not do to their Linux (if they didn't you could simply take one copy of their Linux point at the GPL and make their case vanish in a puff of smoke) they are in violation of the GPL. To my understanding (IANAL, #include "stdDisclaimer") that means every developper who has a code-snippet in their distribution can sue them for copyright-violation (at least one already did).

    What they also fail to understand is that they can't charge royalties on Linux: If they try that the GPL doesn't apply any longer (the source-code has to be freely redistributable) and they again violate the copyrights of anyone who contributed code to that distribution. If they take off the GPL they no longer have the right to distribute the code or the binaries.

    So even if they get their case through they can only demand that their stuff be removed from Linux, but they can't have it all for themselves, since they don't have any rights to all the parts that are not from them. That's the nice thing about the GPL: even if you manage to "remove" it from a piece of code you fall back on standard copyright, so unless the code was yours to GPL in the first place you gain no rights to it.

    --
    "By the way if anyone here is in advertising or marketing... kill yourself." -- Bill Hicks
  156. GPL violation by Anonymous Coward · · Score: 0

    if sco attempts to distribute linux with an encumbrance against redistribution, then sco does not have a license to distribute. it's the same thing. YANA good L.

  157. Someone mod parent down to 3 or 4 with overrated by MickLinux · · Score: 3, Interesting

    In case you didn't notice, I posted the parent.

    Quite honestly, although I consider my post to be interesting, I don't consider it to be insightful.

    It may be inciteful, or not, but I'm not 100% sure it's good. I'm still of the opinion that the best wars are those that are never fought, and that wars have no winners, only losers.

    So though I consider this as a trial balloon to think about and consider, I *don't* automatically consider this a good thing. And I don't find any particular insight in this. Insight is "seeing within". This posting, though, was as obvious as a guy carrying a scarecrow into a herd of penguins. I mean, slashdot thinks in terms of distributed function, right?

    Now, insightful would have been if I had figured a way to finesse all of this, and completely drop off SCO's radar, and still leave SCO standing.

    Thing is, I still don't hate SCO or Microsoft, even with all their criminal behavior. There is some good in every organization, just as there is some good in every city, because you don't get the organization without human trust. I just don't like it when it breaks bad.

    Anyhow, someone mod this one down to 3 or 4. I wanted this balloon out there, but it's really not all that insightful.

    - MickLinux [and yes, it's really me].

    --
    Correct Horse Battery Staple: 72 bits of entropy. Enter "Correct H" into google. When it generates the phrase, that's
  158. An idea? by shades66 · · Score: 2, Interesting

    Why can't all the programmers that have contributed to the GPL now go after all SCO's customers saying that they are(/Maybe as in SCO's own threat they sent out to AIX/Linux users...) using a product which is in violation of the GPL because of the way SCO are operating and therefore they must pay X thousand $ per line of code per installation. If a great number of people do this then maybe SCO's own customers may complain that SCO stop this stupidity.

    Oh well. One day this madness will end and hopfully SCO will be 10 feet under the ground...

    --
    ---- There are 10 types of people in the world. Those that understand binary and those that don't
  159. Re:Companies just don't get that GPL means busines by PugMajere · · Score: 2, Insightful

    I'm 90% sure you're trolling, but what the hell..

    Copyright law, by default, assigns most rights related to a work to the author. The GPL only concerns itself with those rights. It relaxes the restrictions on those rights as long as certain rules are followed.

    The things the GPL prohibts you from doing would not be possible (legally) if the GPL didn't exist anyway - i.e, no rights were taken away by the GPL.

    The GPL is a grant to distribute a work, under certain conditions - nothing more. If you think you have that right absent any contract, you are sadly mistaken.

  160. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  161. why waste bandwidth for those SCO idiots? by jopet · · Score: 1

    a company that has nothing to offer but an overpaid legal department desperately trying to sell a few decade-old comments as "intellectual property" is causing noise all over the internet and in all media. Why waste time for that idiotic company instead of discussing companies that have to offer innovation and something useful? They are simply not worth the fuss.

  162. Microsoft's true aims by floyd-robinson · · Score: 1

    Has anybody tried to make sense of what is really going on, and for what purpose does SCO (an obviously sinking ship) try to scuttle Linux intellectual property? Here are interesting developments to think about: 1. Microsoft buys Apple stock. Microsoft ports MSOffice for the Mac. By developing apps for a Unix-like OS such as Apple, Microsoft developers can gain valuable programming experience for the Unix platform. 2. Microsoft develops Windows 2000 Server. Several important Unix security concepts gets implemented, like tighter file permissions and streamlined kernel operations. 3. Microsoft develops Windows XP. Much of the Unix concepts gets reimplemented in the desktop operating system. 4. Microsoft develops Windows 2003 Server. It is seen as a stop-gap release between Win2003 Server and WinXP while users wait for the ultimate OS in the works -- Longhorn. On a side but very interesting note, Win2003 Server is now more Unix-like. Configuration files are no longer housed in a cryptic registry but are simple text files. Services can be configured individually. A very interesting article on the net opines that Microsoft is becoming more and more like Unix. http://www.informationweek.com/story/showArticle.j html?articleID=10300922 Comments from the article: "...products, where they facilitate Unix-to-Windows interoperability. Services for Unix is comprised of commands, utilities and libraries drawn from BSD Unix, a Posix layer developed by Microsoft, and GNU utilities, among other elements, Miller says. And Windows Server 2003 comes with new Unix-based command-line administration tools." "But Microsoft needs to improve its Unix-interoperability pitch, a message that's coming from the top. "We must invest in better support for developers who want to move Unix applications to Windows, or extend Unix applications with additional functionality on Windows," CEO Steve Ballmer wrote in a state-of-the-company E-mail that went to all Microsoft employees on June 4. "We have made great strides on Services for Unix, and Unix class-library support on Windows. There is still more to be done to support Unix APIs and scripts on Windows." That push, more than anything else, may explain why Microsoft needed SCO's Unix code. And it's worth noting that Microsoft's Unix-interoperability strategy is essentially the same as its Linux-interoperability strategy. "We see Linux as yet another variant of Unix," Miller says. Services for Unix, he says, can be used to run Linux applications on Windows." 5. Microsoft buys a chunk of SCO and takes a look at SCO's codebase. In this manner, they leverage the theoretical knowledge gained from working with MacOS, BSD, and their own implementation of these concepts on Win2K, Win2003 Server, and WinXP. 6. Meanwhile, MS unsuccessfully tries to stem the tide of Linux migrations around the world, most especially with lucrative government agencies. In a bid to boost up this effort, MS funded SCO to raise serious doubts on Linux IP, target IBM, and spread FUD. So far, this campaign has been somewhat successful in making potential migrators think twice of Linux. 7. Meanwhile, MS core developers tries to emulate Unix, trying to make libraries and APIs compatible with everyone else. Why engineer an OS to become more and more Unix-like? Big question, any answers? If Microsoft finishes the compatibility problem, then they can complete the stage which they have been working for so long. --Embed (or steal) the greatest Linux kernel into their core OS.-- Since no one can take a peek at their source code, they can do this, then build "decoy wrappers" around it to mask its true core design. Microsoft suddenly has a powerful core. Why bother designing your own when you can steal the greatest kernel for free, as long as you don't get caught in the act of stealing? How can the underfunded FSF and OSI police this act? How can the rest of the open source community ensure that their work doesn't get plagiarized behind the scenes? The dark side is very dangerous indeed. Sound the alarm now!

    1. Re:Microsoft's true aims by floyd-robinson · · Score: 2, Interesting

      (Umm..Err..sorry, left out the tags...)

      Has anybody tried to make sense of what is really going on, and for what purpose does SCO (an obviously sinking ship) try to scuttle Linux intellectual property?

      Here are interesting developments to think about:

      1. Microsoft buys Apple stock. Microsoft ports MSOffice for the Mac. By developing apps for a Unix-like OS such as Apple, Microsoft developers can gain valuable programming experience for the Unix platform.

      2. Microsoft develops Windows 2000 Server. Several important Unix security concepts gets implemented, like tighter file permissions and streamlined kernel operations.

      3. Microsoft develops Windows XP. Much of the Unix concepts gets reimplemented in the desktop operating system.

      4. Microsoft develops Windows 2003 Server. It is seen as a stop-gap release between Win2003 Server and WinXP while users wait for the ultimate OS in the works -- Longhorn.

      On a side but very interesting note, Win2003 Server is now more Unix-like. Configuration files are no longer housed in a cryptic registry but are simple text files. Services can be configured individually.

      A very interesting article on the net opines that Microsoft is becoming more and more like Unix.

      Comments from the article:

      "...products, where they facilitate Unix-to-Windows interoperability. Services for Unix is comprised of commands, utilities and libraries drawn from BSD Unix, a Posix layer developed by Microsoft, and GNU utilities, among other elements, Miller says. And Windows Server 2003 comes with new Unix-based command-line administration tools."

      "But Microsoft needs to improve its Unix-interoperability pitch, a message that's coming from the top. "We must invest in better support for developers who want to move Unix applications to Windows, or extend Unix applications with additional functionality on Windows," CEO Steve Ballmer wrote in a state-of-the-company E-mail that went to all Microsoft employees on June 4.

      "We have made great strides on Services for Unix, and Unix class-library support on Windows. There is still more to be done to support Unix APIs and scripts on Windows."

      That push, more than anything else, may explain why Microsoft needed SCO's Unix code. And it's worth noting that Microsoft's Unix-interoperability strategy is essentially the same as its Linux-interoperability strategy. "We see Linux as yet another variant of Unix," Miller says. Services for Unix, he says, can be used to run Linux applications on Windows..."

      5. Microsoft buys a chunk of SCO and takes a look at SCO's codebase. In this manner, they leverage the theoretical knowledge gained from working with MacOS, BSD, and their own implementation of these concepts on Win2K, Win2003 Server, and WinXP.

      6. Meanwhile, MS unsuccessfully tries to stem the tide of Linux migrations around the world, most especially with lucrative government agencies. In a bid to boost up this effort, MS funded SCO to raise serious doubts on Linux IP, target IBM, and spread FUD. So far, this campaign has been somewhat successful in making potential migrators think twice of Linux.

      7. Meanwhile, MS core developers tries to emulate Unix, trying to make libraries and APIs compatible with everyone else.

      Why engineer an OS to become more and more Unix-like? Big question, any answers?

      If Microsoft finishes the compatibility problem, then they can complete the stage which they have been working for so long.

      Embed (or steal) the greatest Linux kernel into their core OS.

      Since no one can take a peek at their source code, they can do this, then build "decoy wrappers" around it to mask its true core design.

      Microsoft suddenly has a powerful core. Why bother designing your own when you can steal the greatest kernel for free, as long as you don't get cau

  163. SCO is doomed either way now but just in case by goatan · · Score: 1, Interesting
    There could be a way to keep Linux alive This suit is taking place between two American based companies and it is in American courts that it will (probably) be decided, but American law has no standing on the rest of the world. So the worst case scenario as far is I can see is that Linux wonâ(TM)t be developed or used in America, but will still exist unchanged in the rest of the world. A big pain in the arse in know for you over the pond but Iâ(TM)m sure a lot of Linux users would carry on regardless. Also I imagine that this would apply to non-US distributors as well as the developers.

    What are other peopleâ(TM)s views on the likely hood of Linux being in 2 worlds at the same time one where its free and open another where its IP?

    I wish SCO would pick on some one in the UK there are laws and fines against frivolous lawsuits here.

    This is all on the presumption that the judge is complete fool who sits on his elbows and nudges people out they way with his arse IANAL but I play one on /.

    --
    Saying Apple is better than MS is like saying Botulism is better than rabies.

    1. Re:SCO is doomed either way now but just in case by Anonymous Coward · · Score: 0

      I've thought for a long time that Linux would eventually come into a showdown with US corporate "culture". The value system behind Linux is fundamentally alien to the US, and much more in keeping with Europe. Linux will sweep the world and become the default target for OS development and the US will be stuck with comparatively backward proprietary alternatives.

      It'll be the Yank's loss...

  164. Re: your sig by BigBadBri · · Score: 1
    From 'religion.h':

    #ifdef _CHRISTIAN
    #ifndef _MANICHEAN
    #define GOD 0x11
    #endif
    #define GOD 0x10
    #endif
    #ifdef _ISLAM
    #define GOD 0x1
    #endif
    #ifdef _NIETZSCHE
    #define GOD L"Dead"
    #endif

    Note that compilation with _NIETZSCHE will break most implementations.

    --
    oh brave new world, that has such people in it!
  165. Not any more they don't heh heh by Anonymous Coward · · Score: 0

    Take a look at what Sontag is saying now:

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

    www.computerwire.info/brnews/6FF3308412856B4D802 56 D4E005D45FA

    He says they aren't going to go after any Linux distrubutors because of the GPL. Seems they finally are starting to read the fine print.

    1. Re:Not any more they don't heh heh by hobsonchoice · · Score: 1

      He doesn't say whether or not, they will go after Linux users

      Personally I'd be surprised if they didn't read the GPL years ago. I mean how could they distribute software under it, create a web site containing info about it, etc., if they didn't know what it contained.

  166. Re:Companies just don't get that GPL means busines by Anonymous Coward · · Score: 0

    You're a tool. This is simple. If I give you some code which is not licensed to you under any explicit licence, you have no rights whatsoever to that code under standard copyright laws. You cannot use it and you cannot redistribute it. Thats the law.

    So how can you claim that by providing you with the right to use and redistribute that code with the GPL adds further restrictions? All I've done is given you extra, limited rights to the use and distribution of my code that you wouldn't have under standard copyright laws.

    This is really fucking simple, and the next bellend I see arguing about the GPL when they clearly havn't even read the fucking thing, let alone used it on their own works, I'm going to hunt down and feed to a god damn plastic shredder.

  167. Re:This is exactly why GNU exists, and what its ab by BigBadBri · · Score: 2, Interesting
    The old SCO Openserver product was indeed a big ugly sucker of an OS.

    I once did a fresh install in a very tight timeframe, so tight in fact that I was unable to license the second processor, and missed the fact that the Rio card being used made a nice little 1MB memory hole at 15MB (the box had 128MB, but Openserver wasn't ever going to see it without a bootstring).

    Despite this, the box went online and serviced 140 users (all running Sage) without complaints for the whole of the following day, until I could get back in and fix the processor license and bootstring.

    I'd love to see an NT box (this was about 5-6 years ago) that could boot properly in 15MB, run on 1/2 its processors, and still support 140 users running a fairly disk-intensive app like Sage.

    Yep, Openserver was a BUFF, but it was robust and not too unfriendly.

    --
    oh brave new world, that has such people in it!
  168. Re:Companies just don't get that GPL means busines by Znork · · Score: 1

    There has been multiple challanges to the GPL, however, none has made it to court, because every company getting the call from the FSF has folded and complied on the recommendation from their lawyers.

    As far as I've heard, the FSF counsel is itching for a test case... there just dont seem to be any volunteers.

  169. Re:This is exactly why GNU exists, and what its ab by Eminor · · Score: 1

    No it isn't ready for the desktop, and it may never.

    It's the OS on my machine. I would say it makes a fairly good desktop.

  170. I wouldn't get myself so worried by The+Analog+Kid · · Score: 1

    SCO would be dead before any case like this would make it to court. All it is vaporware to make their stock look good, oh wait its now $5.68, well its not the $11.25 it once was.

  171. Re:Companies just don't get that GPL means busines by Urkki · · Score: 1
    If you want to arbitrarily categorize some of these permissions as rights,

    Well, I think the there's such thing as "copyright" defined in the law. And GPL gives you more rights than copyright law does. If you don't agree with GPL, then you are limited by the copyright law and whatever other IP-related laws apply.

    I don't see any kind of morality issue here (unless you think copyright law is immoral).

  172. Dude, I hate to tell you this... by EriDay · · Score: 1

    ...but I was the other guy, and I uh...well let's just say you've got a virial... uh licencing problem.

  173. Re:Companies just don't get that GPL means busines by dmaxwell · · Score: 4, Insightful

    Stallman claims that the GPL gives you rights and does not take them away. Well, the fact is that the GPL permits you do do certain things and it prohibits you from doing other things.

    Let's leave morality and Stallman out of this for a minute and just look at the license. Standard copyright law says you can't do anything without a license or sale of rights from the copyright holder. Well, not quite nothing. Excerpts can be quoted critically and the like but standard copyright law gives no usage or distribution privileges by default.

    So far, the GPL hasn't come into this at all. First off, the GPL grants unlimited usage rights. Well they specifically say any usage of the Program is permitted. You can even use Emacs to write "Stallman is a dirty hippy." and post it to Slashdot. It then goes on to grant unlimited distribution provided specific rules are adhered to. At no point has anything been taken from you that you didn't already have. Now you may detest the "specific rules" but that is another argument. The fact remains that the GPL permits far more than no license at all.

    And yes, the GPL can be construed as granting rights. I can do any number of things that a software author detests with his work as long as I follow the rules. I can fork the code, publically question its design, benchmark it and so forth. The author can't say crap as long as I follow the rules. The real world works that way. Go yell "Fire!" in a movie theatre if you would a real world demonstration of what rights are and are not. Rights, rules, and prohibitions aren't mutually exclusive except in the minds of certain obtuse philosphers who obviously didn't get out much.

  174. Hold your horses by Anonymous Coward · · Score: 0

    Saying you won't sue is not the same as giving away your rights. Only after a rather long period of time the company would lose the rights to sue because they neglected their obligation to enforce those rights.

    I'm amazed at how many people jump at conclusions all the time. There's a reason these things take so long to be resolved. It's because it's very complex.

    I'll shut up now. I think everyone should.

  175. Re:Companies just don't get that GPL means busines by mpe · · Score: 1

    It's entirely possible that the concept of copyleft could be tossed out, as being an unfair infringement upon the innovation and artistic progress of others.

    It's probably hard to do this without tossing a portion of current copyright law in the bargin. Effectivly you'd be impinging on the absolute rights of copyright holders to control distribution of their works.

  176. Re:Companies just don't get that GPL means busines by mpe · · Score: 1

    The GPL is a grant to distribute a work, under certain conditions - nothing more.

    In many cases the conditions are not even especially difficult or costly. The only obvious group of people who are likely to find the conditions difficult are those wedded to the propriatary "software is a product" idea.
    The conditions could just as easily be "pay me X per copy"...

  177. this was in SCO's site by C0vardeAn0nim0 · · Score: 2, Interesting

    in SCO's (actually caldera's) site they have a copy of a gartner arcticle that contains parts that are a litle detrimental to SCO

    http://www.caldera.com/scosource/gartner_warning .h tml

    some quotes:

    "The SCO Group's suit against IBM could be a way to make SCO a more attractive takeover target"

    "In Gartner's opinion, SCO's claim that IBM misappropriated trade secrets from AIX will be difficult to prove, because an enterprise OS consists of many components, including high-availability features, diagnostics, security, kernel hardening, scheduling and queue management."

    --
    What ? Me, worry ?
  178. How to win an IBM lawsuit by StringBlade · · Score: 1

    1. claim $3 billion in damages
    2. shoot feet out from under self
    3. ???
    4. PROFIT!!!

    --
    ...and that's the way the cookie crumbles.
  179. Re:Companies just don't get that GPL means busines by mpe · · Score: 1

    Consider, if I, at work, want to program a robot or something, I can totally use GPL code until the cows come home, and nobody or nothing can do anything about it. The GPL gives me this freedom. As long as I don't try to distribute my derived code, I'm totally legit! And since my company doesn't sell robots, nobody gives a crap as long as it works flawlessly. It is an in-house thing never to be sold or given away, and it does what it is supposed to do perfectly.

    If your company were to contract someone else to do the work all that contractor would have to do is give your company a copy of the source.

  180. Why don't we... by ganiman · · Score: 0

    HACK THE PLANET!!!

    Seriously, if SCO has a linux distro out there, then it must be released under the GPL, which means that the sourcecode is freely viewable, and the ANYONE can modify any way they see fit, so long as they provide the proper documentation along with the newly modified code, right? (Correct me if I'm wrong here, I haven't been reading my GPL nightly as the /. poll says) If SCO has a Linux distro out there, wouldn't they have used some of the great UNIX code that has taken more than 20 years to perfect?? And if they did, wouldn't that mean it is already free to the world and that is whole case is a bunch of bull??

    I don't think SCO has much of a case, except that they have been flooding the media with propaganda. I do believe that SCO believes they are right in this case, and that their ultimate goal is that they want to OWN Linux. They aren't stupid, they see that Linux (one day, maybe not soon, maybe not even in the distant future, but..) will one day be the most widely used OS.

    --
    geek n performer who performs morbid or disgusting acts, as biting off the head of a live chicken
    1. Re:Why don't we... by intrep1d · · Score: 1

      If SCO 'owned' Linux then it would lose most of its users. I think that is what SCO is missing. If they take control of it, then they kill it. No more 'OPEN' appeal to it. If they did end up winning the case for certain parts of the code, developers could just work that code out (no matter how deeply entwined it is) and build something better in those core parts. In my opinion we should all just switch to a BSD and be done with it. And if all the linux developers/users were behind the BSDs then we would already have a much easier desktop platform (sort of) to recruit people from... MacOSX.

      No matter the case, linux developers who have put their heart and soul into making a great OS, will never let it be owned by some old pathetic company. SCO has made good stuff (once upon a time) but now they are just a pain.
      --
      me

  181. my bad, was thinking of "selling short" by dh003i · · Score: 1

    Never mind. I was thinking of a different technique called "selling short", which is where you try to sell the stock at it's high point, and then buy it back at it's low-point. It's a risky market-timing strategy.

  182. SCO are Thieves by deathmolor · · Score: 1

    Pure and simple. They are trying to steal Linux. Linus with just a few comments lays it right on the line. He doesn't see any IP issues in the kernel at all.

    The GPL applies to SCO we need to remember that everything they are doing makes them nothing more then common thieves. Stealing time (aka money) right out of our hands.

    SCO can hide behind litigation for now but it is soon time for them to be known as the thieves they are.

  183. Knowledge required for a decision by Paul+Johnson · · Score: 1
    Legally (and practically) you have to know you are doing something before you can be said to have decided to do it.

    In this case, it seems likely that SCO will say that they were unaware of their own IP being in Linux, and hence had not made any decision to license it under the GPL even though they were distributing it. Once they became aware of it they stopped the distribution.

    The letter does not change this situation. SCO has contractual commitments to people who bought its Linux distribution. This leads to the odd (but perfectly consistent) situation where SCO's IP was aquired without a licence, but SCO is still legally required to support it because there is no way it can fail to support it without being in breach of contract.

    If I buy the new Harry Potter book, for instance, can't I assume I have a license to read it?

    Under normal circumstances yes. But if J K Rowling or her publishers sold you a PC that inadvertantly had a copy of the book on its hard drive then no, you would have no right to read it. This is a much closer analogy than just buying an ordinary book.

    Paul.

    --
    You are lost in a twisty maze of little standards, all different.
    1. Re:Knowledge required for a decision by Stephen+Samuel · · Score: 1
      In this case, it seems likely that SCO will say that they were unaware of their own IP being in Linux, and hence had not made any decision to license it under the GPL even though they were distributing it. Once they became aware of it they stopped the distribution.

      No, They have not stopped distribution. I downloaded a copy of the Linux source code last Wednesday, and it's still available. It's pretty clear that SCO knows that the code they claim is in Linux. They're still making money off of Linux (support contracts). They're still distributing it, and they've promised at least some of the people they're distributing it to that they won't be sued for using it.

      Either the code is available under the GPL, or SCO is violating the GPL.

      --
      Free Software: Like love, it grows best when given away.
    2. Re:Knowledge required for a decision by arkanes · · Score: 1
      See, I think that falls down. If someone sells you a box, and that box has a copy of Harry Potter in it, you get to keep the book. The burden of making sure that you're selling what you think you're selling is on the distributor. Likewise, if you order a book from Amazon, and they send you 2 copies (but bill you for one), you get to keep the extra copy. You don't need a license to read a book, so your example falls down there, too.

      Now, you can certainly make the claim that the work required to authenticate all the code in the Linux codebase is massive and that due dilligence doesn't require auditing everything - that'd be something for a court to decide, obviously - but you've got NO excuse for knowing infringment. If the Caldera linux distro that they are continuing to distribute and sell has any of the code they claim to own in it, then they've release that code under the GPL. Period. There's wiggle room with supporting previous releases. There's even wiggle room with the amount of time before they took the freely available images off thier website. But there certainly is no wiggle room with the continued distribution of Caldera Linux - the GPL is very clear. Any code you release under the GPL must either be clear of IP claims, or you must offer a license freely to anyone who recieves the code, under terms no more restrictive than the GPL itself. Period.

    3. Re:Knowledge required for a decision by BitterOak · · Score: 1
      Under normal circumstances yes. But if J K Rowling or her publishers sold you a PC that inadvertantly had a copy of the book on its hard drive then no, you would have no right to read it. This is a much closer analogy than just buying an ordinary book.

      If a random person sells me a computer with a pirated copy of the book on it, then I would probably not have a legal right to keep that copy. But if J.K. Rowling herself sells me such a computer accidently (and she is the copyright holder) then I don't see why I would be required to delete it. I haven't copied it; she has, and she's the copyrighrt holder. Can you cite any statutes or precedents to back up your assertion?

      --
      If I can be modded down for being a troll, can I be modded up for being an orc, or a balrog?
  184. Re:Companies just don't get that GPL means busines by mpe · · Score: 1

    The GPL is what gives them the right to redistribute Linux and create derivatives of it for distribution in the first place. If the court "winks" it away they face standard copyright which is far more restrictive.

    SCO needs permision from the copyright holders to distribute GPL covered code. The GPL gives that permission conditionally. SCO have no alternative permission from the copyright holders, therefore they cannot distribute the code at all.

    To my understanding (IANAL, #include "stdDisclaimer") that means every developper who has a code-snippet in their distribution can sue them for copyright-violation (at least one already did).

    Copyright law gives the copyright holder a lot of powers. They can sue SCO for copyright infringement; take out court orders to stop SCO distributing; offer SCO alternative licences; etc.

  185. I said it in March... by panda · · Score: 2, Interesting

    I'll say it again:

    SCO hired David Boies. They want to lose.

    They're just looking to get bought out, plain and simple.

    --
    Just be sure to wear the gold uniform when you beam down -- you know what happens when you wear the red one.
  186. Microsoft seems to respect it... by Anonymous Coward · · Score: 0

    They've been badmouthing it for some time now. I'm sure their lawyers have gone through the GPL with a fine-tooth comb and have not found a way to compromise it. I think the best MS can do is to support any knucklehead (SCO) who wants to try to take on the GPL hoping that negative press will be generated. The funny thing is, MS generates plenty of negative press against themselves, and they've managed to survive it very well. Why do they think an amorphous global entity like OSS would not be able to overcome negative press? I guess that's the best weapon they have in their hopeless fight.

  187. Just a bad train wreck.... by Anonymous Coward · · Score: 0

    This is just getting silly. Perhaps if we don't pay attention to it any more, it won't be able to feed off the energy we give it!

    Nothing to see here people, please move along...

  188. Re:Companies just don't get that GPL means busines by mpe · · Score: 1

    The GPL, by design, will make it unprofitable to sell software sight unseen.

    In many cases selling software isn't profitable anyway. If someone attempted to start up a proprietary software company odds on they'd go bankrupt...

    If the GPL became dominant, software would be limited to an add-on provided by OEMs, contractors, and philantrophic coders.

    So instead you sell time and expertise. The vast majority of software is part of custom systems. Indeed the idea of an "off the shelf solution" is in many real world situations an utter nonsense. Whilst the components may come off some "shelf" or other they still need modifying and fitting together in order to make a system which addresses the needs of the customer. The open source "shelf" has a few advantages over the proprietary "shelf". e.g. anyone can take from it and no complex restrictions on what you can do with the bits.
    A good analogy, IMHO, is to think of putting a software system together as being like constructing a building.

  189. Re:Companies just don't get that GPL means busines by mpe · · Score: 1

    People don't buy "software". People buy solutions to problems. This is way more money is made by contract programming than by selling boxes of software.

    As well as way more software written and adapted for custom systems. If anything writing software to be sold as a boxed product is a far more difficult and risky enterprise. Since you need to guess what the software needs to do. (Then hope people will actually want to buy it.) Whereas for a system contracted to meet specific requirments you already know what it needs to do.

  190. SCO vs. Linux Explained (Simply) by intrep1d · · Score: 1

    Interesting explanation. Next time someone asks you about the SCO / Linux debate link them here =)

    http://www.arie.org/doh/
    --
    me

  191. Long ago, in a galaxy far away... by gosand · · Score: 1
    Pretending to extend the hand of friendship, SCO completely obliterated the anti-SCO message. Slick.

    Gee, I wonder where I have heard this type of tactic before.

    Somehow, I picture Billy talking to Darl several months ago, saying "You do not know the power of the dark side. Join me, and we can rule the galaxy as father and son."

    --

    My beliefs do not require that you agree with them.

  192. It's implicit in the GPL itself. by OmniGeek · · Score: 1

    Per the GPL, you must include the source with the binaries when you distribute to a third party. Also per the GPL, the same rights you have under the GPL transfer to said third party, i.e. you CANNOT contractually prohibit them from further distribution of the binary (with source, natch) OR from distributing the source for whatever fee they choose, or for free.

    So: As long as at least ONE of the people you distributed the source to wishes to "give it to everyone", the deed is done, the cat out of the bag, the horse out of the barn. QED.

    --

    "My strength is as the strength of ten men, for I am wired to the eyeballs on espresso."
    1. Re:It's implicit in the GPL itself. by p3d0 · · Score: 1
      Ok, you have a point.

      So the question is whether they are still distributing it to customers. If they are not still distributing it, having stopped when they found out about the offending code, then I think they can tell their customers "go ahead and keep using it, but don't distribute it" and their legal position is still consistent with the GPL.

      --
      Patrick Doyle
      I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
  193. Re:Companies just don't get that GPL means busines by Anonymous Coward · · Score: 0

    Ghandi had the plight of the oppressed, the moral high ground, and the triple guilt of the Anglican White Empire.

    The first two meant nothing. The last meant everything.

    As I have pointed out many times here, had Japan won WWII, Ghandi would have said:

    "First they march you through hundreds of miles through the jungle, then they shoot you, then they disambowel you, then you lose."

  194. Re:Companies just don't get that GPL means busines by hburch · · Score: 1

    It then goes on to grant unlimited distribution provided specific rules are adhered to.

    I'm sorry, but that statement is hilarious. You are granted "unlimited" distribution "provided specific rules are adhered to". I do not dispute that the GPL grants more rights than you would have without it (it specifically says you do not have to accept it). However, it offers only "limited" distribution rights. In fact, your distribution rights are limited to licensing under the GPL.

    It is certainly true that the distribution rights are much greater than most commercial packages. That is, you have non-zero distribution rights (most EULAs claim to limit even resale of the "purchased license"). However, compared to the BSD license, the GPL is a straightjacket when it comes to distribution. This is, of course, the point of the GPL: GPL developers do not want their hard work put into a closed-source product. The GPL is designed to force open-source distribution of derivatives.

  195. Re:This is exactly why GNU exists, and what its ab by Anonymous Coward · · Score: 0

    Linux exists as a learning tool.

    IBM and other companies (RH, Suse, Mandrake, etc.) might disagree with you, and as someone who makes his living off from Linux support, I would too. Linux is not Âa learning toolÂ. ItÂs a real OS that has plenty of power to get the job done as well as any other Unix. If that werenÂt the case, Sun wouldnÂt be looking out the side of itÂs eyes at it.
  196. Re:Companies just don't get that GPL means busines by mpe · · Score: 1

    Licensing the use of Intellectual Property does not in any way weaken ownership of that IP. Perhaps it's time that this point is driven home by a court. If I don't own the IP (if I don't control the copyright, either by virtue of being the author or by having that right assigned to me by the author), then I usually can't transfer that IP to someone else legally unless I have specific permission of the real owner to do that. The GPL is both the permission for that transfer, and the obligation to do so.

    The GPL dosn't oblige you to do anything. Copyright law says you need permission, from the copyright holder, in order to distribute copies of copyrighted work(s). The GPL gives you such permission, subject to a set of conditions.

    The GPL is not a transfer of copyright or IP ownership. Just as is true for releases of code to selected parties under more "traditional" licensing terms (like, for money ;-), the copyright still rests with the author of the code released under GPL.

    e.g. it's perfectly possible for an author to licence a work to a publisher. Though with some kinds of works publishers want to hav copyright assigned to them...

    If SCO has released some code/IP under GPL, then by the terms of the GPL anyone who receives that code is obligated to pass on that code to anyone else who asks for it.

    Not quite, the obligation only applies to those people SCO has actually supplied the binaries to. Of course if they make the binaries available to anyone who wants them then they had better make the source just as easily available. If they only made the binaries available for sale then they'd be entitled to ask for a evidence that you were before supplying the sources.

  197. Culture clash? by Anonymous Coward · · Score: 0

    Rather a clash of civilizations. Between those that have it, and those that don't.

  198. Re:Companies just don't get that GPL means busines by Asprin · · Score: 1


    It's almost as if the GPL is too "far out" and too liberal for anyone in corporate America to really believe it's real...

    Perhaps you meant something else, but I have seen a few people on both sides of the GPL try to use modern political partisanship to describe the purpose and intent of GPL, and I want to torpedo that stinking-freighter-full-of-trash right here, right now. The GPL is no more liberal or conservative than anything other legal contract or license.

    To wit:

    If Bob writes a piece of software and decides to GPL it, he is making his own free-will decision about how he wants to exercise control over his creation. That's conservative compared to the liberal/socialist/communist (take your pick) approach would demand that government would take ownership of the code and collect taxes for using it.

    If AmazinglySuperSoft, Inc. sees his source and wants to use it, they have to consider that Bob's price tag as creator is that they have to GPL their derivative code, too. Don't like it? Fine, do the conservative thing and write your own code and don't use Bob's. Nobody can force you to do anything, and nobody's going to gripe about using alternatives, that would be liberalism.

    Just like with everything else in that cozy little place I like to call 'reality', everyone gets to make their own decisions here -- ultimately, that's the essence of idealistic conservatism in a nutshell.

    I do, however, agree with you entirely that these people are acting like ignorant bozos, but I think it has more to do with NOT READING THE FREAKING LICENSE[*] than the whole "liberal-conservative" thing. They're calling the GPL "communist" because it carries a stigma, not because it does anything even **remotely** communist. I think their real fear is that they've been commoditized by an entity thay can't buy out and with which they can't negotiate.



    obDisclaimer: Yep, I consider myself a conservative. No, I didn't write this to pick on liberals. I wanted to show that political partisanship has no place here by arguing the exact opposite of the prediliction that the GPL is a liberal document. I am sorry if you missed the point.



    [*] I mean, really, it isn't even that frickin' long, and the PREAMBLE tells you almost everything you really need to know in case the you have some sort of complex about having to look up the really big words like "verbatim".

    --
    "Lawyers are for sucks."
    - Doug McKenzie
  199. Re:The Gloves Come Off... and the first victim is. by SlashDread · · Score: 1

    SCO

    I work for a SCO shop. (Well we run SCO and sell stuff running on it)

    Suddenly our OpenServer =>> UnixWare update project is being re-evaluated in favour of...
    linux

    I love it, make more noise for Linux SCO, it a few moths key people (in a must-be-rocksteady server market) will think Linux is ok, because IBM says so.

    peace /Dread

  200. Re:Linux vs. SCO: The Decision Matrix (How Linux w by TheFrood · · Score: 1

    Damn, I was hoping it was that Dukes of Hazard thing again.

    TheFrood

    --
    If you say "I'll probably get modded down for this..." then I will mod you down.
  201. We must save COMDEX by Rev.+DeFiLEZ · · Score: 1

    HA!, Caldera gave me a copy of their linux at comdex for free, does that mean I am in the clear?

    and people thought comdex was just about the T-shirts!

  202. Endgame to overturn the GPL and steal Linux by timlewis_atlanta · · Score: 3, Insightful

    The next (unannounced) step is for SCO to challenge the GPL, or be challenged on it. This is what SCO want, and they think they can win. It's nothing to do with Microsoft.

    I've said this twice before on slashdot : SCO are aiming to steal Linux. If they win against IBM and subsequently successfully have the GPL overturned then they will be able to charge for use of Linux. Additionally, if they manage to keep the alleged source code violations sealed, then the community will not be in a position to rewrite the copied code. Linux would be dead to the open source world and would become a proprietary operating system owened by SCO. Click here for my original comment :
    http://slashdot.org/comments.pl?sid=64233&cid=5958 703

    In their letter SCO state "SCO will continue to honor all contractual obligations with existing customers including product updates, service, and support.". This action indicates they may very well be violating the GPL by offering Linux OS pathes etc. This invites someone to take them to court for violating the GPL, which is exactly what they want.

    So watch for two things:
    1. SCO moves to have all source code violations sealed in court.
    2. Another court case starts : Open Source Developers vs SCO, fighting over the validity of the GPL.

  203. Spelling mistake by timlewis_atlanta · · Score: 1

    Of course that should read "OS patches" not "OS pathes".

  204. Re:Companies just don't get that GPL means busines by Planesdragon · · Score: 1

    Effectivly you'd be impinging on the absolute rights of copyright holders to control distribution of their works.

    Like what the concept of copyleft could be construed to do.

    Mind you, I don't think that it's likely SCOTUS would toss out the concept, but it's possible. Especially given that no law I know of explicitly authorizes copyleft or copyleft-like concepts.

  205. It's not the GPL, silly! by k98sven · · Score: 2, Interesting

    It continues to seem that most companies simply don't believe that the GPL is a real license. It's as if they think that secretly free software authors "don't really mean it" when they explicitly define rights and restrictions in a license.

    Oh, the GPL is a real licence, and either they've all understood that, or they're just incompetent with respect to licensing issues. Remember that IBM, which has more IP lawyers than many (most?) western nations has carefully examined the thing.
    If there were any loopholes or room for doubt, IBM probably would've exploited them long ago.

    Rather, I think it's an issue of big guys believing that they can s--t all over the small guys. Sadly, this often makes good business sense. You can do whatever you want to people if they can't afford to sue you.

    If you're big enough to afford lots of defense lawyers (and perhaps a few campaign donations to the powers that be), you don't even have to worry about getting sued.

  206. Re:How is the GPL Designed to turn copyright on it by Planesdragon · · Score: 1, Informative

    You are always free to contact the copyright holder of any work available under the GPL and request licensing under different terms, you know.

    Only for single author projects. Any sizable GPL'd program has an innumerable ammount of unlisted authors--except for those who have had rights assigned to them by the FSF, and I doubt that the FSF would allow circumvention of their own license.

    I'm really unclear on what aspect of the GPL needs to be "challenged". If the GPL does not apply, then copyright law forbids the things people are doing with those works the authors placed under the GPL. It's not a use license, but if you don't accept it, the law is clear: you don't have the right to do certain things with that code.

    The basic concept of copyleft has yet to be held up or torn down by a court. It is entirely possibe that, if copyleft is found to be an unfair use of copyright law, the GPL will be re-interpreted as merely a waiver of liability and a release into the public domain.

    The GPL just covers so few instances--and for most of those that it does cover, the authors are either far too small to contest the GPL, or far too large to use GPL'd code.

  207. Ask slashdot? by nanojath · · Score: 1
    Probably too late for this to get noticed, but as an interested layman I was curious about informed opinion about this quote from the interview w/L. Torvalds in the later link:


    SCO alleges that you need to focus more on getting clarification as to where the code that goes in the Linux kernel comes from. Do you have any plans to change the current Linux development model?


    No. I allege that SCO is full of it, and that the Linux process is already the most transparent process in the whole industry. Let's face it, nobody else even comes close to being as good at showing the evolution and source of every single line of code out there.


    Informed opinion (yeah, I know - impossible to verify but...): is this true? It made sense to me when I read it but as a non-programmer, I've not participated in the actual development process. If this is a reasonable statement I think that it is an argument that needs more exposure, because it is strongly in favor of the open source development model.

    --

    It Is the Nature of Information to Transgress Artificial Boundaries

  208. Re:Companies just don't get that GPL means busines by aussersterne · · Score: 1

    My god, why must Americans put everything into Rebublican vs. Democrat boxes? From Miriam Webster:

    2 a : marked by generosity : OPENHANDED b : given or provided in a generous and openhanded way
    6 a : of, favoring, or based upon the principles of liberalism b capitalized : of or constituting a political party advocating or associated with the principles of political liberalism; especially : of or constituting a political party in the United Kingdom associated with ideals of individual especially economic freedom, greater individual participation in government, and constitutional, political, and administrative reforms designed to secure these objectives

    Both of these could fit the poster's context, including but not limited to, GPL, anti-segregation movements and vietnam protesting. Nowhere in MW's definitions for "liberal" do you find "Democrat Party, USA" or "communist."

    --
    STOP . AMERICA . NOW
  209. That ship has sailed by Anonymous Coward · · Score: 0
    As far as I can gather, SCO's position seems to be, at its heart, that the old UNIX System V AT&T license (or rather, every single one of the numerous SysV licenses, AIX, Dynix, etc) was, to use a Ballmer-ism, 'viral', unstoppably so, in their view.
    Then why did/does SCO/Caldera distribute Linux with GPL licensing on the CDs? My knowledge of Contract Law is limited to what I gleaned from Prof. Kingsfield's class on The Paper Chase, but I distinctly remember that the essence of a contract is the meeting of minds. In this case we have offer and acceptance. SCO/Caldera offered software under the GPL, and their customers accepted the offer.

    I want to see a class-action suit brought against SCO, on behalf of every single SCO/Caldera Linux customer, for fraud and breach of contract.

    Posting as AC from work, but it's obvious who I am
    SVM, ERGO MONSTRO

  210. Re:Companies just don't get that GPL means busines by johnnyb · · Score: 1

    In addition, if it's open, you have all of the benefits of packaged software.

    Plus, you get free bugfixes AND ENHANCEMENTS from others, an extended community support system,and a larger base of people familiar with the software. In fact, this is exactly why Cisco opened up their printing system - they wanted the benefits of free software. It was more beneficial to them to distribute the code freely (even though they were _paying_ developers to develop it) than it was to not do so.

    The mistake most people make is that they forget that in order to have new software, you have to have software producers. Just because one _specific_ _method_ of payment becomes no longer available (although I doubt that will happen, too), does not mean that software producers will not get paid. As long as there are

    a) people who need software

    and

    b) people who can write software but need money

    Software producers will be paid, it just might not be in the same fashion.

  211. Interesting Thought by Fujisawa+Sensei · · Score: 1

    Was the code in question ever included in a Linux distribution from SCO/Caldera?

    If so they just put their stamp of approval on the GPLing of their own stuff.

    --
    If someone is passing you on the right, you are an asshole for driving in the wrong lane.
    1. Re:Interesting Thought by perlchild · · Score: 1

      More like getting an uniformed court to say that any and all Linux violates their IP, and they can sue at will. I wonder if they said they would not sue CURRENT SCO clients... But keep a reserve to sue anyone who'd let a support contract with SCO terminate.

  212. The arrogance of SCO is truly astounding. by walterbyrd · · Score: 1

    SCO received $8.5 million in FUD money. That brings their book value to about $10 million. SCO has never been profitable and has no competitive products. Yet, this recently formed, essentially worthless, company seems to consider their own power to almost limitless.

    SCO apparently believes that they have absolute rights over all software technology developed in the last 30 years - if not more: SMP, NUMA, RCU, JFS, LVM, Linux, FreeBSD, NetBSD, OpenBSD, maybe even MacOS and MS-Windows.

    We poor pitiful peons can hope that the all-powerful Darl McBride will be kind enough to allow us to continue to use our present OS. We must recognize that is entirely up to him.

    Recently the all-powerful lord and master Darl, has deemed that we may continue the Caldera Linux for which we have already paid.

    I suppose we should all fall on knees, clasp our hands, bow our heads, and while sobbing uncontrollably, thank and praise our lord and god - the kind and powerful Darl. While trembling at his feet, we should bless the great and Darl for allowing us to use the Caldera Linux that we have paid for.

  213. Re:Companies just don't get that GPL means busines by johnnyb · · Score: 1

    The great thing about the GPL is that it gives you some leverage in regards to keeping your own source code. For example, if a company needs some custom work, you can say

    "Well, I can write the code myself in 2 months. Or, I could write the code in two weeks using open-source product A. The only restriction is that if we use product A we have to contribute our changes back to the community."

    Give them the price for 2 weeks vs 2 months, and I'm pretty sure I know which one they will choose. Now, I know that this isn't the exact implications of the GPL, but it is the practical ones, because of problems of upgrading patched software.

  214. Re:Companies just don't get that GPL means busines by ChaosDiscord · · Score: 1

    I agree with your general message (that the GPL does in fact grant rights. Specifically, it grants you rights that under vanilla copyright law you would not have). However, you have a small, but popular, misconception:

    Standard copyright law says you can't do anything without a license or sale of rights from the copyright holder. Well, not quite nothing. Excerpts can be quoted critically and the like but standard copyright law gives no usage or distribution privileges by default.

    You've got copyright slightly backward. When you purchase something protected by copyright, you outright own that one particular copy you just purchased. You are free to use it however you like. You can read it, watch it, disassemble it, sell it, loan it out, and give it away. You most certainly get usage privileges. You even get some distribution privileges, you can distribute the original copy (but not distribute additional copies).

    Copyright is about restricting certain rights to the copyright holder. The key elements are the right to distribute copies and the right to publically perform the work (Squint a little and public performance looks like distribution of a copy). To practice these restricted rights, sure, you'll need some sort of license or sale of rights. But if you want to do just about anything else, well, because you purchased that one copy, you're free to do so.

  215. Re:Companies just don't get that GPL means busines by Asprin · · Score: 1


    Neat-o, but the entities (Microsoft, SCO, etc.) that are attacking the GPL as liberal/socialist/communist are in the US, and **THEY**, not me, **THEY** are doing so in that context. I didn't make up the words, so if you have a gripe about semantics, talk to somebody else. I was trying to head off this argument because It - appears - to - be - an - issue, and it shouldn't be.

    I am sorry I failed.

    --
    "Lawyers are for sucks."
    - Doug McKenzie
  216. Re:Companies just don't get that GPL means busines by squiggleslash · · Score: 1
    It doesn't prohibit anything without seperate permission that you're not already prohibited from doing without seperate permission.

    That's why we talk about the GPL giving people rights they otherwise wouldn't have.

    You're locked in a cell, and we throw you a key and ask that you use it to unlock a door that would free you and everyone else. And instead of being grateful, you whine and bitch and moan that we're not giving you anything, that you're not free, because you're obliged to free everyone else at the same time.

    The GPL is viral and takes your rights away. Dubya is a compassionate conservative. Miller Lite is... you want me to stop? You've heard these tired, inaccurate, slogans before?

    --
    You are not alone. This is not normal. None of this is normal.
  217. Re:Companies just don't get that GPL means busines by LMCBoy · · Score: 1

    Well, the fact is that the GPL permits you do do certain things and it prohibits you from doing other things.

    No. The GPL does not restrict you from doing anything that you would not already be restricted from doing under standard copyright law. Cast in these terms, it is indeed true that the GPL itself grants you additional 'rights' while taking none away (since you never had arbitrary redistribution rights anyway).

    --
    Liberal (adj.): Free from bigotry; open to progress; tolerant of others.
  218. Landlords by pommiekiwifruit · · Score: 1
    Hah! My landlord leapt over the fence a few days before I was due to leave my flat and slashed away at the garden leaving branches all over the place. The inspector came around shortly after that and one of the things that caused my damages to precisely equal the amount of the deposit was untidy garden (the other was limescale). Of course when I moved in the garden was an overgrown mess and I had mowed the lawn and cleared most of the brambles (leaving a few for blackberries) and planted flowers etc.

    The point is they will do that if they think they can get away with it, and they usually can (in NZ on the other hand deposit money is held in trust by the govt.). He also delighted in telling me he would throw away the decades old carpet/furniture after I had just paid to have them shampooed (not that they were dirty, just old).

  219. Re:Companies just don't get that GPL means busines by God!+Awful+2 · · Score: 1

    Sorry, I don't do semantics.

    -a

  220. A serious contender? by josquin9 · · Score: 2, Funny

    Remember all those years when the big boys were all saying "linux will never be a serious operating system"?

    Couldn't Linus just say "Yep, you were all right. The whole thing was a joke. Linux was always intended to be a comical OS."

    At that point I think we could claim the whole system falls under the category of parody, and the copyright issues should just go away. Right?

  221. Duh. by Anonymous Coward · · Score: 0

    Here is the argument:

    IF there is no infringing code in Linux, SCO is guilty of malicious slander and libel.

    IF there IS infringing code in Linux, SCO has continued to distribute Linux distributions WITH THE CODE after becoming aware of it. So the "they can't have licensed it if they weren't aware of it" argument does not apply. They ARE aware and they continue to release a Linux build. Which means...

    They must either be distributing their Linux build under the terms of the GPL, in which case, they have in fact licensed the code for release and the code therefore becomes immediately NON-INFRINGING.

    OR

    They must be distributing their Linux build outside the terms of the GPL, in which case they are guilty of copyright infringement of every person who has contributed any code in the distribution SCO is distributing - in which case SCO is opening itself to a flood of lawsuits.

    Where does IBM come into play here?

    SCO claims that IBM is the one that inserted SCO's code into the Linux kernel.

    IF this is true, we can simply revert to the above... either SCO, by continuing to distribute Linux after becoming aware of potential problems, has released the offending code under the terms of the GPL - meaning IBM is now licensed to use it the same as anyone else and the SCO suit holds no water.

    OR

    IF there are any lines of code in the Linux distribution that SCO distributes - and SCO chooses not to distribute it under the GPL - that were contributed by IBM, SCO is now in equal violation of IBM's copyright as IBM is in violation of SCO's.

    Basically, any way you slice it, the naked fact that SCO continues to distribute Linux builds *after* (and that's the key word here) claiming that they have discovered infringing code has destroyed their case and made them the only party that, ultimately, can be liable for damages.

    Had SCO immediately stopped distributing Linux builds after claiming, "hey, we found stuff in here that belongs to us and shouldn't be in here!" their case would be a lot stronger. As has been pointed out before, they can't agree to release their stuff under the GPL if they didn't know it was in there. But now that they know it's in there, and they continue distributing it, means they must release it under the GPL or face the legal consequences. The fact that they did not pull their Linux distros immediately has, in essence, torpedoed their own case.

  222. Re:Companies just don't get that GPL means busines by God!+Awful+2 · · Score: 1

    Stallman has chosen to push the GPL as "as copyright + extra freedoms" rather than "public domain - extra restrictions". When you think of a program with no real owner, public domain comes to mind, but Stallman used copyright so he could add his extra restrictions. The perspective is flexible if you ask me. He's like a lawyer or a politician who can give you one things and sell it as another.

    -a

  223. Sco's real problem is that copyright != patent by Anonymous Coward · · Score: 0

    I can write a piece of code and it can look identical to someone elses code and I have not commited a copyright infringement IFF I have never seen their code. Patents prevent other people from independently developing the same thing; Copyrights DO NOT! For a copyright infringement to be proven exposure to the infringed material must be shown. If the person who is supposed to be infringing is the original creator of the material and sold the copyright to the material I think it would be even harder to prove copyright infringement; you would be argueing that after someone sells a work they cannot make any other works in that field.

  224. Obligatory "Simpsons" reference by zurkog · · Score: 2, Funny

    SCO has issued a letter saying SCO Linux customers won't be sued.

    SideSCO Bob [on P.A.]: The following linux users will ~not~ be sued by me: SCO/Linux. That is all.

    SCO User: Woohoo! Did ya hear, Linus!? Hey---Oh.

  225. Re:Companies just don't get that GPL means busines by dmaxwell · · Score: 1

    Stallman has chosen to push the GPL as "as copyright + extra freedoms" rather than "public domain - extra restrictions". When you think of a program with no real owner, public domain comes to mind, but Stallman used copyright so he could add his extra restrictions. The perspective is flexible if you ask me. He's like a lawyer or a politician who can give you one things and sell it as another.

    The license can be considered (and used) apart from Stallman. At this point, it is even used by people wh o significantly disagree with Stallman on many points and even use it to serve goals he doesn't agree with. Ask the Ghostscript people. Just because a work is GPLed doesn't mean Stallman or the FSF owns it. Secondly, GPL programs most certainly have "r eal owners". Since this is all about Stallman how do you explain Ghostscript, QT, or reiserfs? All of those are licensed in context dependant ways because they have "real owners". Most people who use the GPL actually do intend "copyright + extra freedo ms". GPL projects that have their code abused by corporations do indeed seem to feel they have ownership.

    If you don't care for the GPLed stuff then that's fine. Theres plenty of BSD stuff thats just as good or maybe even better. But you know what, ev en that stuff isn't public domain. BSD coders often get hacked off if their stuff is used without acknowledgement. Yes, Virginia the BSD license has a significant restriction on "total freedom": Don't plagiarize our work. You can use it but have to acknowledge you didn't write it. It has another significant restriction: "You don't get a warranty so if it breaks in half, you get to keep both halves." Of course if that isn't "Free" enough then you can let MS exercise it's freedom to license as it sees fit all over you.

    This "public domain - extra restrictions" is a red herring. If you expect to find a full OS and associated utilities in the PD then good luck to you. Even those "totally free" BSD guys disclaim liability and insist on acknowlegement. The moral of story is that there is no such thing as "total freedom". The GPL and even BSD, X, MIT licenses are ways of saying "You're right to throw a punch ends at my nose."Ë

  226. "New Logic" absurdity by David+Jao · · Score: 1
    [Under New Logic,] SCO now has "sole right of relicense" to not only this derived work, but as with Sequent, all previous implementations

    The problem with New Logic (and I hope and pray that the courts realize this) is that anything and everything in the world now belongs to SCO, even material written by others who have no contract or relationship at all with SCO.

    In other words, let's say I write a program called Linnux which IBM (illegally) incorporates into Unix. By New Logic, SCO now controls all versions, including past versions, of Linnux through their contract with IBM, even though

    1. IBM's action was illegal
    2. I have no contract with SCO and I never at any point granted any ownership rights to SCO
    The fact that my own work can fall under SCO licensing as a result of an illegal act by an unrelated third party is frightfully wrong.

    To put it another way: If IBM illegally included Harry Potter with AIX, does SCO suddenly own Harry Potter? That is what New Logic seems to imply.

  227. Re:Companies just don't get that GPL means busines by Maserati · · Score: 1

    Then write off the open source "contribution" as a charitable donation or some other tax scheme. Get someone from Finance to run the numbers.

    --
    Veteran, Bermuda Triangle Expeditionary Force, 1992-1951
  228. Excuse me Mr. Pot, but I'm black? by Anonymous Coward · · Score: 0

    "...they can argue that they were duped into distributing it because they didn't know what was in it."

    Which is really a case of the pot calling the kettle black. If you listen to Darl McBride, half the reason for this suit is to make the FSF and OSS people give their heads a shake and review the process by which code is accepted. SCO would like to see some sort of mechanism for applying due diligence to OSS code submissions.

    Another piece of advice SCO executives seem to be handing out left right and centre is for IT/IS people to perform their own due diligence reviews of code to be run in the enterprise.

    The recurring theme of course is that everyone else has to exercise due diligence, excepting of course SCO. SCO's belief that they could extract damages from Linux distributors seems to be a damning indictment of those distributors due diligence procedures.

    What about SCO's own due diligence? Shouldn't these high and lofty procedures have been applied to their own distro? Before it was shipped? That certainly would have prevented the whole "releasing the code themselves under the GPL" issue.

    The legal issues aren't clear to me, but a common sense interpretation of this mess runs like this:

    SCO says users and distributors of Linux may be liable for unlicensed SCO IP included in the software, unbeknownst to the user, distributor, and, until recently, SCO.

    SCO further maintains that the fact that none of these distributors and users were aware that this IP was present in the software they were using is besides the point, essentially ignorance of the content is not a defense.

    SCO has ignored the GPL, pretty conclusively too. But, if that comes up, we could expect them to try and hide behind the fact that they, as the copyright holder, did not GPL the code in question, and subsequent distribution of the code under the GPL was anulled by this original unlicensed inclusion.

    There may be some way to make that work in law, but in the real world we call it a double standard. Bottom line, SCO is pointing fingers and screaming foul because they failed at the same thing they claim every one else failed at, due diligence.

  229. The score as I see it: by Stephen+Samuel · · Score: 1
    • SCO says it's their code in the Linux Kernel
    • They say it's IBM's fault.
    • Not only that, but it's code written by IBM.
    • SCO says they have the right to control release because it was once attached to an SYSV system
    • They have also assured their (other) licensees that they stil own their code that they inserted into their versions of UNIX, it's just that SCO can stop them from distributing it.
    • They say that the GNU license on the code is invalid because the GPL states that it can only be placed by the copyright owner
    • But if IBM Still owns the code, and they're the ones who placed it, then the GPL is valid (It's just that SCO gets to sue IBM for releasing it withiout their say-so .. but subsequent users are still OK).
    • SCO is still distributing Caldera Linux -- including kernel source.
    • This means that they're distributing it under the GPL, with a GPL license on it and IBM (the owner of the code) has also explicitly released it... Seems like everybody in this loop has given their permission -- either explicit or implict.
    • If their license is really this nasty (and they're ambushing customers with things like this), I expect that a lot of other businesses are going to abandon their Unix license as soon as they can.
    • It's pretty unlikely that their long stretch claim to owing everything ever put into AIX is going to win.
    • Some people now think that they're going to try and (essentially) blackmail people into paying them for any copies of Linux that didn't come direct from Caldera/SCO (even if it came indirectly from them).
    • This whole mess places them in violation of the GPL and opens them up to some nasty copyright suits.
    • Until this started, SCO looked like it was about to go bankrupt
    • If this fails, not only will their old UNIX funding sources dry up, but nobody is going to want to buy Caldera, either. They could also end up with millions (billions) in legal bills.
    My reading of this is that they've started with a weak case, shot themselves in the foot, and are still claiming that they own the world. it really reminds me of Monty Python's infamous Black Night.

    If I knew when (not if) SCO's stock is going to tank, I'd issue a shell-sort order today.

    --
    Free Software: Like love, it grows best when given away.
  230. Hope this squabble kills Unix and strengthens Linu by Anonymous Coward · · Score: 0

    SCO has revoked the Unix license given to IBM. I hope IBM dumps Unix for good and goes with Linux!

  231. What they know that you don't know by worldcitizen · · Score: 1

    Last week on MSN money, a columnist mentioned how tired he was of getting calls from brokers "pushing" SCOX.

    This looks like "old" pump and dump. Some stock has news that look good (but in reality they aren't). A few brokers put on their salesman hats and try to get as many buyers as can be found. Meanwhile, the sharks are selling the pumped stock. Later, the stock drops, a bunch of people lose what they invested and Wall Street moves on to the next business. For example, SCOX management is selling. They had conveniently "programmed" sales (you wondered if programming means software to them? I think this other "programming" is what interests them...) Go to the business section at yahoo and check the insider trades. You'll see these "programmed" trades (note that other insiders do have programmed trades, that is, they sell similar amounts every set amount of time, but I couldn't find any previous similar "programmed" trades in SCOX records)

    Financial magazines many times just report what brokers are saying. If brokers are peddling a certain stock, they'll just echo those comments. Traditionally it is up to the readers to determine if the comments are on the money or not. On the other hand you're right that occasionally they actually guess correctly, for example, about a possible acquisition being negotiated.

    By the way, return on investment for shorting a stock that goes bankrupt tends to infinite (you pay close to $0 and get something in return, for more details just look at my other recent postings on SCOX)

    Disclaimer: I'm short SCOX (Pro: I'm putting my money where my mouth is. Con: now I have a vested interest in seeing SCOX shares drop like the .... they are)

    1. Re:What they know that you don't know by bankman · · Score: 1

      Well, while I agree with you on how financial magazines come up with their interpretations, I am having trouble finding the insider trades at SCOX that you mention: Check it out for yourself here.

      --
      I feel so sig.
  232. Will Novell sue SCO ? by dinog · · Score: 1
    It seems to me that if the code violations preceede SCOX's aquisition of Unix from Novell, that Novell may have reason to sue SCOX since SCOX bought Unix from them with money gained by selling Linux.

    That would amuse me to say the least. SCO fights the case, gets a determination of infringement, and then Novell sues them because the infringement started before SCOX aquired the rights to Unix, and thus Unix was bought by a Linux company using funds gained by violating the rights of the very code they purchased.

    How can SCO win this case ?

    Is there even a possible outcome that doesn't hurt SCO as much or more than it helps them ?

    Dean G.

  233. Re:Companies just don't get that GPL means busines by jorgen · · Score: 1
    The GPL is designed to force open-source distribution of derivatives

    The choice is really simple. Don't like the GPL terms? Then don't touch it with a 10 foot pole. Nobody is actually forcing you, unless you take the shortcut of using somebody elses GPLd work.

  234. Re:Companies just don't get that GPL means busines by JoeBuck · · Score: 1

    You misunderstand what RMS means when he says that the GPL only adds rights, it does not take any rights away. RMS is absolutely correct in a legal sense. That's because if he just wrote "Copyright FSF, all rights reserved", the default situation is that of copyright law, which says that no one but the copyright holder may make copies or derivative works. If you have a legal copy you can run it, make one backup, study how it works, and so forth. These are the kinds of things that shrinkwrap licenses sometimes restrict, but copyright law does not restrict.

  235. SCO WMD's by Anonymous Coward · · Score: 0

    Can we invade SCO to find WMD's or something?
    We did so good in Iraq, (the oil fields were invaded first) I really believe SCO has WMD's laying around that can be assembled and used in about a hour.

    Maybe that is why we cannot find any WMD's in Iraq, SCO has had them hidden in McBride's orifice all along.

    We should also see if Ben Laughing is there, or So-dum Who's-insane.

  236. but by phriedom · · Score: 1

    You think SCO wants to have the GPL challanged? But if the GPL is invalid, then SCO has no permission from the hundreds of copyright holders of Linux to distribute it. I cannot imagine any way for SCO to avoid charges of willfull copyright infringement from any of the many authors of Linux.

    And I think companies like Disney and the **AA's have paid for really very strict legislation against copyright infringment, which means that people like Linus have all the teeth here.

    --
    Don't moderate flamebait as Troll. Know the difference or you will be Meta-moderated.
  237. Re:Companies just don't get that GPL means busines by God!+Awful+2 · · Score: 1

    The GPL is viral and takes your rights away. You've heard these tired, inaccurate, slogans before?

    Well, no. I've only ever heard "The GPL is viral and anti-business."

    Anyway, if you ask me, the GPL is a public domain license that takes away rights, dressed up as a proprietary license that grants them.

    -a

  238. Re:Companies just don't get that GPL means busines by God!+Awful+2 · · Score: 1

    This is, of course, the point of the GPL: GPL developers do not want their hard work put into a closed-source product.

    And this is, of course, why some people hate the GPL. The closed source developers don't want their hard work converted into a GPL product.

    -a

  239. Re:Companies just don't get that GPL means busines by God!+Awful+2 · · Score: 1

    My objection to the GPL has nothing to do with it not being free enough. I just don't like the fact that it is anti-business because it creates unhealthy competition.

    As for BSD, I think the license is fine. Having to give credit is not anti-business and it doesn't create unhealthy competition. Unfortunately, the volume of BSD-licensed work out there pales in comparison to the amount of GPL stuff.

    If a group of people get together to develop an open source program, they have no real incentive to prefer the GPL license to the BSD one. Unless, of course, they are trying to dupe businesses into developing part of the code for them, against their personal interest. (Which is exactly what they are trying to do.)

    -a

  240. Re:Companies just don't get that GPL means busines by Malcontent · · Score: 1

    The only people who hate the GPL are people who want to steal other peoples code.

    --

    War is necrophilia.

  241. Re:Companies just don't get that GPL means busines by Malcontent · · Score: 1

    "If a group of people get together to develop an open source program, they have no real incentive to prefer the GPL license to the BSD one."

    They have a big reason. They don't want to become unpaid volunteers at a corporation. They don't want other people to take their code and make money selling it.

    Maybe to you that's not significant. So what if Bill Gates steals your code and makes another billion or two? Some people don't want that to happen.

    --

    War is necrophilia.

  242. Re:Companies just don't get that GPL means busines by Malcontent · · Score: 1

    "Anyway, if you ask me, the GPL is a public domain license that takes away rights, dressed up as a proprietary license that grants them."

    Quite possibly the stupidest thing ever written on slashdot.

    --

    War is necrophilia.

  243. The Real Culture Clash by some+old+guy · · Score: 1

    Way back when, at least in 81'/'82/'83, there was a really great biker/hippie bar up in the hills in Mountain View called Rizotti's Beer Garden. I was working as a neophyte IBM ironworker, swapping tape reels at a SF bank's data center, and some of us would spend some of our spare time at Rizotti's getting sluiced. I remember a few times listening to these incredible ubergeeks from places like Sun, HP, Xerox, Digital, and UC argue about acrcana like implementing PDP-11 over this new TCP/IP thing and so on.

    Being a 22-year-old nitwit who barely understood C, I had no idea that these guys would one day rule my world when XENIX hit the street a while later. But that was the culture back then. Much like the Linux community today.

    Now Unix is just a toy for MBA raiders and a football for lawyers. It's one of those "Paris was Yesterday" kind of things that reminds us that when intellect meets money, money wins. We're all whores by necessity. Some are just skankier than others.

    --
    Scruting the inscrutable for over 50 years.
  244. Re:Companies just don't get that GPL means busines by God!+Awful+2 · · Score: 1

    They have a big reason. They don't want to become unpaid volunteers at a corporation. They don't want other people to take their code and make money selling it.

    "Why should I release my code as open source? Because it doesn't cost you anything, and you have the benefit of knowing that others are finding your work useful."

    I can't count the number of times I've heard this argument espoused on /., but as soon as there's the hint of someone making money, people get all freaked out. What really bugs me is how the GPL advocates think it's ludicrous when people call them communists.

    -a

  245. Re:Companies just don't get that GPL means busines by God!+Awful+2 · · Score: 1

    The only people who hate the GPL are people who want to steal other peoples code.

    I don't know what hole you just crawled out of, but apparently you haven't been paying attention. Making unauthorized use of someone else's code is not stealing; it's a copyright violation -- no worse than copying music off Kazaa.

    -a

  246. Re:The Gloves Come Off... -- correction by Anonymous Coward · · Score: 0

    You still hugged the CEO.

  247. Re: maybe the GPL is irrelevant by timlewis_atlanta · · Score: 1

    You got me thinking again. It turns out that it might not matter if the GPL is or is not enforceable : if SCO win the IBM case on the basis of their claims that they own ALL derivative works and they get a ruling that the Linux kernel is a derivative work then it would mean that SCO would own the code even though it was written by other people.

    So the people who wrote the code and distributed it under the GPL would have actually distributed it illegally, as they would have been ruled to not own their own code. It follows that SCO wouldn't need the permission of the authors of the code, and the GPL wouldn't apply to the Linux kernel. Of course it would still apply to GNU software.

    Of course this whole situation is absurd. No sensible court would rule that the authors of software don't own the copyright. But sometimes courts reach complicated and strange decisions.

  248. Get real moron. by mindstrm · · Score: 1

    The whole point is a) it's been stated as common knowledge by many and b) I recall reading it at one point. And c) There are lot sof binary only drivers.

    Did you miss the part where I said I couldn't find it?

    I'm *sure* something was in there at one point.. there was a specific rule about binary drivers..

  249. Re:Companies just don't get that GPL means busines by Malcontent · · Score: 1

    In communism you work for the benefit of other people (the greater good). If you realease your code under a BSD or a public domain license you are practising communism.

    That's why GPL people get upset when you call them communists. They are charging for their product, the price is clearly stated and you are not under any obligation to buy it.

    GPL is capitalism public domain and BSD is communism.

    --

    War is necrophilia.

  250. Re:Companies just don't get that GPL means busines by God!+Awful+2 · · Score: 1

    GPL is capitalism public domain and BSD is communism.

    Bullshit. Just because you can come up with a flimsy analogy to equate the GPL licence with "charging for their product" doesn't make it capitalism.

    Capitalism is a specific economic system which attempts to maximize the wealth of society by a large number of small transactions in which each party acts in his own interest. However, capitalism is not an infallible system. It seeks local maxima, which may not be the true maxima. It can also have negative social and evironmental results.

    Communism is a system which seeks to avoid the problem of capitalism (the local maxima) in order to maximize the wealth of society even further. However, communism has many flaws because it requires people to act against their direct self interest. Also, communism espouses equality, which is not a stable state (and therefore it can't be a local maxima).

    The flaw in communism is the same as the flaw in the GPL, which is the tragedy of the commons. This doesn't really apply so much to the hobbyists (who could just as easily release their code as BSD), as the businesses who are forced into developing GPL'ed software against their collective self interest.

    To paraphrase a /. motto, people are going to steal your code no matter what you do, so you might as well release it as BSD and at least get credit for it.

    -a

  251. Re:Companies just don't get that GPL means busines by Malcontent · · Score: 1

    I will say it again.

    If you release your code into the public domain you are practising communism and advancing the cause of communism. Communism is working for the greater good. In communist countries your labor and efforts don't belong to you they belong to the "people". In other words in communism all your labor is in the public domain and for the benefit of the public.

    GPL may not be capitalism in the sense that you perceive capitalism but there is no denying that GPLed code comes with a price. The price is not money but it's a high price nevertheless. SO high that most companies won't pay it.

    "To paraphrase a /. motto, people are going to steal your code no matter what you do, so you might as well release it as BSD and at least get credit for it."

    That's just downright stupid. Do you leave your bike unlocked? DO you leave your house unlocked? Why make it easy or safe for people to steal your labor. That's communism.

    --

    War is necrophilia.

  252. Re:Companies just don't get that GPL means busines by God!+Awful+2 · · Score: 1

    If you release your code into the public domain you are practising communism and advancing the cause of communism. Communism is working for the greater good.

    I don't understand what you have against working for the greater good.

    I don't have a problem releasing my code into the public domain, assuming it isn't something I think I can sell. If someone else can make a buck off something I wrote then more power to them. (Although I would appreciate it if they had the courtesy to offer me a job.) I do, however, have a problem with releasing my code only to have it co-opted by a bunch of communists who are hell intent on destroying the software industry.

    That's why I disagree with your categorization of BSD/public domain as communism. Communism involves manifestos and propaganda and cults of personality. Communism is about destroying the capitalist establishment; something that public domain code doesn't do.

    GPL may not be capitalism in the sense that you perceive capitalism but there is no denying that GPLed code comes with a price.

    As I tried to explain before, capitalism is not just about buying goods for money; communist countries have money too. Capitalism is a specific economic system that has certain predictable behaviours (due to game theory). GPL'ed software does not exhibit these properties, but it does bear a strong resemblance to communism (again, in game theory terms).

    That's just downright stupid. Do you leave your bike unlocked? DO you leave your house unlocked? Why make it easy or safe for people to steal your labor. That's communism.

    As I said, I was only paraphrasing a common /. motto.

    -a

  253. Re:Companies just don't get that GPL means busines by Malcontent · · Score: 1

    "I don't understand what you have against working for the greater good."

    I don't have anything against it. I just call it what it is which is communism. If you are communist and want to advance the cause of communism then by all means release your code into the public domain.

    "As I said, I was only paraphrasing a common /. motto."

    I have enver heard that on ./ but what the fuck who cares.

    --

    War is necrophilia.

  254. Re:Companies just don't get that GPL means busines by God!+Awful+2 · · Score: 1

    I don't have anything against it. I just call it what it is which is communism. If you are communist and want to advance the cause of communism then by all means release your code into the public domain.

    Now you're not even being consistent with your last message, in which you deride communism.

    Aside from that, you didn't even bother to refute my point, which I assume to mean that you've lost the argument.

    I have enver heard that on ./ but what the fuck who cares.

    There's a million variations on the theme of "X is going to happen no matter what you do, so you might as well embrace it." I can't believe you've never heard them.

    -a

  255. Re:Companies just don't get that GPL means busines by Malcontent · · Score: 1

    "Now you're not even being consistent with your last message, in which you deride communism."

    I never derided communism. Go back and re-read my posts.

    "Aside from that, you didn't even bother to refute my point"

    You know ,you made so many scattered arguments that I have lost track of what you are saying. All I know is that you hate stallman, you hate the GPL and you are on some kind of a crusade to convince people to embrace communism by donating their labor to the public good.

    I don't have anything against communism. If you want to advocate a socialist/communist lifestyle that is your right. Maybe we would all be better off if everybody (including Bill Gates) just dumped all their code into the public pool but Bill Gates is not a communist and he would never ever share his products with the public. By the same token The folks at the FSF are not communists either and they also don't want to dump their code into the public pool.

    GPL is closer to your ideal then the proprietary code of MS and all other corporations so I really don't see why you would hate them so much while at the same time praising MS.

    Once again I have nothing against communism it's just that history shows that it does not work.

    It's great that you have communist ideals and want to share your work with the world. It's great that you want to relinquish ownership of your labors and let everybody have it for nothing. But it's not fair to force other people to share in your beliefs.

    Some people don't want to let anybody do whatever they want with their code.

    --

    War is necrophilia.

  256. Re:Companies just don't get that GPL means busines by God!+Awful+2 · · Score: 1

    I never derided communism. Go back and re-read my posts.

    I see what I see. I'm not going to argue with you about your state of mind.

    You know ,you made so many scattered arguments that I have lost track of what you are saying. All I know is that you hate stallman, you hate the GPL and you are on some kind of a crusade to convince people to embrace communism by donating their labor to the public good.

    Hate Stallman: tick
    Hate the GPL: tick
    Communist Crusade: huh?

    I don't know where you got that idea. I'll have you know that I am a professional software developer. I work on closed source programs and I expect to paid for my work. I don't work for free and I have never released a BSD-licensed program in my life. [It is quite possible that there are a few small freeware apps I wrote in high school or university floating around out there, but that's not really the point.]

    I believe in for-profit software. Capitalism is a good way to drive the economy and promote innovation. However, I acknowledge that once a technology advances to a certain level of maturity, it becomes a commodity. At that point, it does no real harm to have a free or cheap alternative.

    A BSD/public domain license on the commodity allows everyone to start on an equal footing. Now the innovators can add their custom feature and charge only for that feature, without having to amortize the cost of developing the entire platform. That's why I advocate the BSD/PD license, but only for people who were going to give away their code in the first place.

    To call me a communist is ridiculous. I don't believe in unadulterated capitalism either. What I do advocate is pragmatism. The GPL is a Machiavelian plot to bring down the entire software economy. Advocates claim that they are not against people making money, but then they come up with the flimsiest of business cases and sigh "too bad" when the companies go belly up within the year.

    Some people don't want to let anybody do whatever they want with their code.

    Yeah, but it's amazing how 90% of those people lose their ideals when it comes to the ownership of other peoples' music.

    -a

  257. Not quite by Anonymous Coward · · Score: 0
    "The only restriction is that if we use product A we have to contribute our changes back to the community."
    Not quite, only if said company was distributing the binaries for this custom program. Which it wouldn't so they wouldn't be obligated to fold any of your changes back into the community.
    1. Re:Not quite by johnnyb · · Score: 1

      Yes, but my version is the condensed version of "You could keep them to yourselves, but then if you get out of sync with the mainline tree you have then degenerated into a full-fledged software development project which will do nothing but increase your costs through the roof, so it's best just to contribute the changes back to the community."

      I think my original version is better for explaining to PHBs.

  258. Re:Companies just don't get that GPL means busines by Malcontent · · Score: 1

    "To call me a communist is ridiculous"

    To call you a communist is absolutely accurate. You advocate that people donate their labors to public for the benefit of the public for the advancement of the public good. This is exactly what communism is all about.

    As I stated before, the GPL is closer to captialism then public domain or BSD. GPL'ed code comes with restrictions and a price and is therefore is closer to proprietary/capitalism model.

    "What I do advocate is pragmatism. The GPL is a Machiavelian plot to bring down the entire software economy."

    Lying does not help your cause. You can spread all kinds of venom and hatred towards the GPL or stallamn or whaoever you want but it only makes you look more stupid because you are not able to convince other people of your point of view using logic. This kinds of obvious vitriolic lie was exactly the kind of propaganda used by other prominent communist and look how far it got them.

    "Yeah, but it's amazing how 90% of those people lose their ideals when it comes to the ownership of other peoples' music."

    Off topic and irrelevant.

    --

    War is necrophilia.

  259. What does it all mean? by kaycee77025 · · Score: 1

    First, everyone with a copy of OpenLinux will have it on e-bay. Second, Chinese software .... copiers will get a chance to pirate SCO software. Third, people like me will be going to used book and software stores shopping for recent SCO releases (openLinux 2.4 @ 14.95) What a country!

  260. Re:Companies just don't get that GPL means busines by God!+Awful+2 · · Score: 1


    To call you a communist is absolutely accurate. You advocate that people donate their labors to public for the benefit of the public for the advancement of the public good.

    This is ridiculous. As I already stated, I advocate selling software for profit. That is my #1 preference. However, if you do feel like giving your software away, I would rather you release it as BSD rather than GPL so you don't deny someone else the opportunity to make money off of it.

    As I stated before, the GPL is closer to captialism then public domain or BSD. GPL'ed code comes with restrictions and a price and is therefore is closer to proprietary/capitalism model.

    Metaphorically, one could say that GPL'ed software has a price. However, metaphorical arguments don't prove anything. Don't you have any more substantive arguments?

    By the same token The folks at the FSF are not communists either and they also don't want to dump their code into the public pool."

    Communists don't share the wealth with everyone. They only share with other communists.

    You can spread all kinds of venom and hatred towards the GPL or stallamn or whaoever you want but it only makes you look more stupid because you are not able to convince other people of your point of view using logic

    Hehe. My opinion at least has a basis in pragmatism. I dislike the GPL because I think it will be bad for the economy. Contrast that with your irrational outlook, which centres around the overwhelming fear that someone, somewhere is making money off your work (even though it does you no harm for them to do so).

    Forget logic; let's talk about common sense. Stallman says the GPL doesn't prevent you from making money from selling software; you can still charge a fee for the physical medium on which the software is stored. There's a perfect example of letting logic overrule common sense. Sure, it's technically possible to make money doing this, but the profits are so low as to be insignificant.

    "Yeah, but it's amazing how 90% of those people lose their ideals when it comes to the ownership of other peoples' music."

    Off topic and irrelevant.

    Hardly. Since it appears that the majority of GPL advocates on /. also support music piracy, it is clear to me that their opinions are based on convenience and egocentrism and not a coherent world view.

    -a

  261. Re:Companies just don't get that GPL means busines by Malcontent · · Score: 1

    "However, if you do feel like giving your software away, I would rather you release it as BSD rather than GPL so you don't deny someone else the opportunity to make money off of it."

    Once again GPL has a price. People who release code under the GPL are not "giving it away". The GPL is a EULA just like the code you sell has a EULA. There is no appreciable difference between the code you sell and the GPLed code.

    "Metaphorically, one could say that GPL'ed software has a price."

    No not metaphorically, it actually has a price. The price is not money but it's a price nevertheless. The price is so high that people like you (and Bill Gates) can not afford to pay it. It's a new kind of price for a new kind of economy.

    "I dislike the GPL because I think it will be bad for the economy. Contrast that with your irrational outlook, which centres around the overwhelming fear that someone, somewhere is making money off your work (even though it does you no harm for them to do so)."

    The GPL has nothing to do with money. I don't care who makes money with my code. I am happy when people make money with my code. I just don't want them to steal it. That's all. They can make all the money they want as long as they don't deny other people the same rights that I gave them (and other people gave me).

    "Since it appears that the majority of GPL advocates on /. also support music piracy,"

    Bullshit, offtopic and irrelevent.

    --

    War is necrophilia.

  262. Re:Companies just don't get that GPL means busines by God!+Awful+2 · · Score: 1

    I notice you are getting a lot of practice at arguing with what I say and not what I mean. Whenever possible, you choose to misinterpret my words and make a semantic argument rather than a logical one.

    "if you do feel like giving your software away..."
    Once again GPL has a price. People who release code under the GPL are not "giving it away".

    Your objection is 100% semantic and it has no bearing on my argument. If you wish, I'll rephrase my argument in legalese to compensate for your thought impediment:

    However, if you do feel like releasing your software under terms that allow redistribution of the source code without renumeration paid to the original author as cash or cash equivalents, I would rather you released it under a BSD license rather than GPL so that if someone else thinks they could make money from it, they aren't likely to be disuaded by the terms of the license.

    There is no appreciable difference between the code you sell and the GPLed code.

    I.e. in one area (they both have EULAs) they are almost identical. That doesn't stop them from being different in a million other ways.

    The price is not money but it's a price nevertheless.

    That's great, but it's still a metaphor because we were talking about capitalism, which is an actual economic system that was designed to deal with real money. The theory of capitalism was designed to deal with real money (or at the least, barter) so if you want to extend it less concrete types of "prices", you have to understand that not all of the same conclusions will necessarily apply.

    It's a new kind of price for a new kind of economy.

    At least in the short run.

    The GPL has nothing to do with money.

    Sure, if you want to be naive. I should also point out that guns have nothing to do with murder. You can have murder without guns and you can have guns without murder.

    [Of course the problem with statements such as the above in an argument is that half of America will agree with it.]

    I am happy when people make money with my code. I just don't want them to steal it.

    If you released the code as BSD, they could make money and they wouldn't be stealing. The real question is why you care that someone is reusing your code without permission. After all (as the old /. argument goes), copyright violation is not really theft because theft is when you deprive someone of property.

    The BSD license doesn't deprive you of your code. If someone extends your software without BSD'ing that, it doesn't even deprive other people of your code. It just gives them more options: they can have the original code for free, or they can have the improved software for a price.

    "Since it appears that the majority of GPL advocates on /. also support music piracy,"
    Bullshit, offtopic and irrelevent.

    Even Stallman supports music piracy. Interesting on how all of his proposed revenue models for music sharing take the power out of the hands of the copyright owners and hand it over to the government. It's all very (dare I say it) communistic.

    -a

  263. Re:Companies just don't get that GPL means busines by Malcontent · · Score: 1

    "However, if you do feel like releasing your software under terms that allow redistribution of the source code without renumeration paid to the original author as cash or cash equivalents, I would rather you released it under a BSD license rather than GPL so that if someone else thinks they could make money from it, they aren't likely to be disuaded by the terms of the license."

    It's apparent to me that your value system is very narrowly defined. You define value and worth (and cost and price) strictly in terms of cash. I guess that's what makes us different.

    "Sure, if you want to be naive. I should also point out that guns have nothing to do with murder. You can have murder without guns and you can have guns without murder."

    Absolutely. That is dead on. COngratulations, you now get it.

    "The real question is why you care that someone is reusing your code without permission."

    Because I am not a communist. I believe in ownership and property. Those things are the bedrock of capitalism.

    "The BSD license doesn't deprive you of your code. If someone extends your software without BSD'ing that, it doesn't even deprive other people of your code. It just gives them more options: they can have the original code for free, or they can have the improved software for a price."

    Right. Public domain will accomplish the same thing (there is very little difference between public domain and BSD). It's communism. I am not a communist, I don't believe in communism. I don't think that people should be forced or even encouraged to relquinsh their labors to others.

    "Even Stallman supports music piracy."

    He believes in fair use not piracy. I for one think it's immoral that a musician or their agents can punish you for singing a song.

    --

    War is necrophilia.

  264. Re:Companies just don't get that GPL means busines by God!+Awful+2 · · Score: 1


    It's apparent to me that your value system is very narrowly defined. You define value and worth (and cost and price) strictly in terms of cash. I guess that's what makes us different.

    It depends. When I'm talking about capitalism vs. communism, I use those terms in a monetary context. If you employ specific terminology without reference to the context in which you are using them, then you are apt to reach ridiculous conclusions.

    (BTW, it is still not true that my entire value system is based on money.)

    "Sure, if you want to be naive. I should also point out that guns have nothing to do with murder. You can have murder without guns and you can have guns without murder."

    Absolutely. That is dead on. COngratulations, you now get it.

    Actually, that was a test to see what kind of thinker you are and you proved my point. In an earlier posting, I said that you seemed to let logic overrule common sense. It's a common flaw of geeks -- they are good at Boolean logic, but they don't seem to understand fuzzy logic and statistics. The fact is, while not every gun will kill someone, there is strong evidence of a correlation between guns and murder, so to say that guns and murder are "unrelated" is simply willful ignorance.

    "The real question is why you care that someone is reusing your code without permission."

    Because I am not a communist. I believe in ownership and property. Those things are the bedrock of capitalism.

    But you don't believe in selling things for money, which, if anything, is the real bedrock of capitalism. The real question to me is *why* you believe in ownership and property. It strikes me that your beliefs are dogmatic and you might not understand *why* you believe in them.

    Right. Public domain will accomplish the same thing (there is very little difference between public domain and BSD). It's communism. I am not a communist, I don't believe in communism. I don't think that people should be forced or even encouraged to relquinsh their labors to others.

    So basically the only reason why you don't release your code under the public domain is because you don't want to be a communist. You don't have any real reason for not wanting to be a communist; it just has bad connotations or something. Face it: you are perfectly willing to relinquish your labours to others, but only on Stallman's terms. Meanwhile, I advocate selling software for a profit and *you* are calling *me* a communist?!?

    "Even Stallman supports music piracy."
    He believes in fair use not piracy. I for one think it's immoral that a musician or their agents can punish you for singing a song.

    Stallman believes in extending fair use by taking away the right of copyright owners to control how their property is distributed. Sounds like communism to me.

    -a

  265. Re:Companies just don't get that GPL means busines by Malcontent · · Score: 1

    "there is strong evidence of a correlation between guns and murder, so to say that guns and murder are "unrelated" is simply willful ignorance."

    You are seeing a causation where none exists. People murder with guns because guns are an effective tool for killing. Before guns people murdered with knives, arrows and swords. Guns are just a tool.

    "But you don't believe in selling things for money, which, if anything, is the real bedrock of capitalism. "

    I have said repeatedly that I have no objection to anybody selling anything. I really don't know where you are getting this stuff from. You can't just make shit up and then draw a conclusion from it.

    Not only do I believe in selling things for money, I also believe in an expanded definition of currency. In a rapidly evolving world we need to expand our ways of looking at wealth and currency. The GPL is but one way of refining currency. It's a way of converting labor to wealth that effectively allows you to compete with Bill Gates the richest man in the world. In the old economy BIll Gates gets to fuck you in ass while making your mother watch just for fun and because he owns the world. In the new economy (by exploring new kinds of currency and wealth) you can hope to compete with him.

    "Face it: you are perfectly willing to relinquish your labours to others"

    You are truly misinformed. When I release my code under the GPL I retain ownership of the code. I also retain a degree of control over what happens to that code forever.

    See my comment above why in some ways GPLing code is better then selling it. When you sell your code you are competing with Bill Gates. That's a fight you are going to lose because he is the richest, most powerful person on the planet. You are just wasting your money and time by fighting a 400 pound gorilla.

    It's better the enter a fight you at least have a chance of winning.

    --

    War is necrophilia.

  266. Re:Companies just don't get that GPL means busines by God!+Awful+2 · · Score: 1


    You are seeing a causation where none exists. People murder with guns because guns are an effective tool for killing. Before guns people murdered with knives, arrows and swords. Guns are just a tool.

    Right... and I suppose that if guns weren't easily available, we'd see a vast increase in the number of drive-by beheadings. It's exactly the fact that guns are such an effective tool for killing that makes the murder rate go up.

    After watching Bowling for Columbine, I researched the stats on murder vs. gun ownership (because I didn't trust Michael Moore to fact check them). What I found was not a correlation between murder and guns in general, but a correlation between murder and handguns specifically.

    "But you don't believe in selling things for money, which, if anything, is the real bedrock of capitalism. "

    I have said repeatedly that I have no objection to anybody selling anything. I really don't know where you are getting this stuff from. You can't just make shit up and then draw a conclusion from it.

    Alright... another rephrase to satisfy your nitpicking:

    But you don't believe in selling the things *you produce* for money, which, if anything, is the real bedrock of capitalism.

    Not only do I believe in selling things for money, I also believe in an expanded definition of currency. In a rapidly evolving world we need to expand our ways of looking at wealth and currency

    Source?

    It's a way of converting labor to wealth that effectively allows you to compete with Bill Gates the richest man in the world.

    I.e. If you can't make the blind people see, poke out everyone's eyes so they can all compete on the same level.

    You are truly misinformed. When I release my code under the GPL I retain ownership of the code.

    Nominally, yes.

    I also retain a degree of control over what happens to that code forever.

    If you give everyone else all the same rights you have then you no longer have control.

    When you sell your code you are competing with Bill Gates. That's a fight you are going to lose because he is the richest, most powerful person on the planet.

    My goal is not specifically to "beat" Bill Gates. My intent is to make enough money to live a comfortable life. There's enough room out there for more than one person out there to make money, although OSS has significantly reduced my chances.

    It's better the enter a fight you at least have a chance of winning.

    That is one of the lamest justifications for OSS I have heard, but I have to admit it explains a lot. You view competition as a game and you are willing to cut off your nose to spite your face.

    -a

  267. Re:Companies just don't get that GPL means busines by Malcontent · · Score: 1

    "But you don't believe in selling the things *you produce* for money, which, if anything, is the real bedrock of capitalism."

    Again that's not true. I sell some stuff I produce, I get paid for other things I produce, and I GPL some stuff I produce. It's all according to the marketplace. If I can compete and have a chance in hell of winning then I'll ask for money, If I have no chance to win then I'll GPL (which is winning!).

    "I.e. If you can't make the blind people see, poke out everyone's eyes so they can all compete on the same level."

    Bzzzzzt wrong again. I harm no one by releaseing my code under the GPL. I could have not released it at all, I could have simply retained the copyright. Nobody has to accept the GPL. If they want to use my code then can PAY ME. So you can pay me with the GPL or you can pay me with cash. Either way I want to get paid for my code.

    "My intent is to make enough money to live a comfortable life"

    I already make enough money to live a comfortable life. My employer compensates me generously for my labors.

    "There's enough room out there for more than one person out there to make money, although OSS has significantly reduced my chances."

    OSS only hurts you if you are too stupid to write your own code. If you are too lazy to write your own code, too stupid to ride on the backs of BSD coders and exploit their labors then you don't deserve to make money. Capitalism is not a handout, nobody owes you code, nobody owes yoy anything.

    "You view competition as a game and you are willing to cut off your nose to spite your face."

    I don't hurt myself at all by GPLing my code. I win. I get better code (other people help me) yet at the same time Bill Gates is too afraid to touch my code and ruin it for everybody.

    --

    War is necrophilia.

  268. Re:Companies just don't get that GPL means busines by God!+Awful+2 · · Score: 1


    I harm no one by releaseing my code under the GPL. I could have not released it at all, I could have simply retained the copyright.

    Quite untrue. You harm quite a lot of people. Admittedly, you only harm each of them a little bit, but if 100 other people think the same way you do and keep extending your code then the harm adds up.

    - You harm the entrepreneur who was planning to release a commercial version of the same thing.
    - You harm the 50 people he would have hired.
    - You harm the tens of thousands of software developers looking for jobs because their bargaining power is slightly reduced.

    Nobody has to accept the GPL. If they want to use my code then can PAY ME.

    Nobody is that desparate to use your code. Anything that one person develops alone can be easily replaced. What they would like to use is the code that has been collaboratively developed by hundreds or thousands of people.

    I already make enough money to live a comfortable life. My employer compensates me generously for my labors.

    Fine, so does mine. (Not as much as I was making a few years ago, but quite adequate.) But I am not arrogant enough to assume that will always be the case. Like a lot of people, I was laid off last year. Fortunately, I have some very specialized skills and I quickly found a new job. However, I feel sorry for all my friends who aren't so lucky. And what about the new grads? When I look at resumes, I see guys with 10+ years of coding experience applying for jobs as testers.

    OSS only hurts you if you are too stupid to write your own code.

    It's not a question of being too lazy to write your own code. These days, software projects are a lot bigger than they used to be, and it's impractical to re-invent the wheel. It used to be that you would license some third party libraries to provide the building blocks. But the existence of GPLed alternatives drives down your margins. You can't afford to buy the libraries, but you can't afford to use the GPLed onces either. It's a Hobson's choice.

    If you are too stupid to ride on the backs of BSD coders and exploit their labors then you don't deserve to make money.

    The problem is there is not enough BSD stuff out there to compensate for all the GPL stuff. Nowadays, more amateur projects (including a lot of university research) are being released under the GPL, perhaps because the GPL has better propaganda and it appeals to the communistic tendencies of elitist university students/professors who have had it easy all their life.

    Capitalism is not a handout, nobody owes you code, nobody owes yoy anything.

    Capitalism is not a perfect system; it requires government regulation. /. readers are always bitching about the monopolistic practices of Microsoft. I choose to complain about the monopolist practices of the FSF.

    -a

  269. Re:Companies just don't get that GPL means busines by Malcontent · · Score: 1

    Interesting. You don't want to write your own code, you can't find enough BSD code to steal from, you are not allowed to steal code from the GPL pool so you whine about why you can't make money because you are unable to compete with a bunch of people who code in their spare time.

    So instead of working harder and making better code you whine on and on about how the GPL is evil and is preventing you from making tons of money off of other peoples backs.

    You know what you don't deserve to make money. You are just a leech on society.

    --

    War is necrophilia.

  270. Re:Companies just don't get that GPL means busines by God!+Awful+2 · · Score: 1


    Interesting. You don't want to write your own code, you can't find enough BSD code to steal from, you are not allowed to steal code from the GPL pool so you whine about why you can't make money because you are unable to compete with a bunch of people who code in their spare time.

    If only it were so. If the only competition was from hobbyists then there wouldn't be a problem. Unfortunately, there are some misguided companies out there who fund OSS development and ruin it for everyone.

    So instead of working harder and making better code you whine on and on about how the GPL is evil and is preventing you from making tons of money off of other peoples backs.

    Well, yeah. I am kind of sick of always working harder. It used to be that startups expected you to work a lot of overtime, but they paid you well and they lured you in with tons of stock options. Now everyone is in startup mode. Thanks in large part to OSS, there's more and more players fighting for a bigger piece of a shrinking pie.

    You know what you don't deserve to make money. You are just a leech on society.

    Yeah... just because I advocate an economic system with a mathematical basis (as opposed to an economic system I read about in "Adam Smith for 3 year olds"), that makes me a leech on society.

    -a

  271. Re:Companies just don't get that GPL means busines by Malcontent · · Score: 1

    "If only it were so. If the only competition was from hobbyists then there wouldn't be a problem. Unfortunately, there are some misguided companies out there who fund OSS development and ruin it for everyone."

    If you can't stand the heat get out of the kitchen. If you are unable to compete get out of the business. That's capitalism.

    "Well, yeah. I am kind of sick of always working harder. It used to be that startups expected you to work a lot of overtime, but they paid you well and they lured you in with tons of stock options. Now everyone is in startup mode. Thanks in large part to OSS, there's more and more players fighting for a bigger piece of a shrinking pie."

    Move to a more socialist or communist country. That might make your anxiety go away.

    "
    Interesting. You don't want to write your own code, you can't find enough BSD code to steal from, you are not allowed to steal code from the GPL pool so you whine about why you can't make money because you are unable to compete with a bunch of people who code in their spare time.

    If only it were so. If the only competition was from hobbyists then there wouldn't be a problem. Unfortunately, there are some misguided companies out there who fund OSS development and ruin it for everyone.

    So instead of working harder and making better code you whine on and on about how the GPL is evil and is preventing you from making tons of money off of other peoples backs.

    Well, yeah. I am kind of sick of always working harder. It used to be that startups expected you to work a lot of overtime, but they paid you well and they lured you in with tons of stock options. Now everyone is in startup mode. Thanks in large part to OSS, there's more and more players fighting for a bigger piece of a shrinking pie.

    You know what you don't deserve to make money. You are just a leech on society.

    Yeah... just because I advocate an economic system with a mathematical basis (as opposed to an economic system I read about in "Adam Smith for 3 year olds"), that makes me a leech on society."

    WHat makes you a leech is that you want to be able to use other people's code without paying a price. You want to legalize stealing.

    --

    War is necrophilia.

  272. Re:Companies just don't get that GPL means busines by God!+Awful+2 · · Score: 1

    You know what pisses me off? People who have entirely dogmatic belief systems. Your adherence to capitalism is some kind of religious issue. You doggedly advocate various corolleries of capitalist systems, and yet you ignore the spirit of the idea. You don't understand how capitalism works (and when it doesn't).

    If you dogmatically assume that anything capitalist is good and anything socialist is bad then fine: Let's cut taxes, abolish the minimum wage, expand free trade, and dispense with social security and medicare. You and I can slog it out for 60 cents an hour along with the rest of the third world.

    I admit it. I don't want to work 80 hours a week to make less money than I did 5 years ago. What's the point of technology making our life easier if I have no free time? For some reason you want to abolish all the white colar jobs, or at least turn them into a living hell. Of course you don't state this as an actual goal, but your attitude is that if this happens then "so what, that's capitalism."

    Capitalism is a sound economic system, but like anything other system, it doesn't work if you to take it to extremes. You advocate a system that bears only superficial resemblance to capitalism. But because you can come up with some bullshit analogy that converts the GPL into capitalism ("a different kind of price for a new economy"), and you dogmatically assume that anything capitalistic is good, you are able to talk out your ass.

    -a

  273. Re:Companies just don't get that GPL means busines by Malcontent · · Score: 1

    Once again answer the main charge.

    you are constantly whining about how you are unable to compete with part time amateur coders. You are whining because you are not allowed to use other peoples labors for your own benefit and profit. You whine about how capitalims has made you poorer and more unhappy.

    Ok so what? I don't fucking care about your whiny ass. Move to canada, move to finland, move to any other country that will take you. Move to a country which practices a flavor of capitalism/socialism that makes you happy.

    Either that or just fucking kill yourself. If you are unable to cope then end it all. Just don't fucking bother me about it.

    It's clear you don't have the talent or the smarts to make it in this country. You are destined to become just another shmuck in this endless sea of shmucks. One day you will get old enough to collect social security and will ride around the country in a winnebago camping in walmart parking lots and buying cheap slave labor chinese goods.

    Really man look ahead, what kind of a life are you going to have in 10, 20, 30, 40, or 50 years. How many times are you going to marry and divorce? Are you going to make any difference at all?

    Just end it man, do the rest of us a favor.

    --

    War is necrophilia.

  274. Re:Companies just don't get that GPL means busines by God!+Awful+2 · · Score: 1

    Yo dude, do you work for the post office? Is that why you are so unsatisfied with your life that you have to work a second job for free. You OSS types are just are like papparazi in the way you ooh and ahh over your geek heros. Real capitalist invest their money on race horses or balooning around the world. They don't undermine their own industry in a desperate bid for fame.

    I, for one, don't care if I ever become famous. I just want to put in an honest days work and make enough money to play a round of golf every week. Thankfully, I already live in Canada, and not in your ridiculous country. That doesn't make me immune from the GPL, however, since lots of OSS projects are based here. You know, in a lot of industries, if a bunch of upstart punks tried to do someone else's work for free, they'd get their legs broken.

    -a

  275. Re:Companies just don't get that GPL means busines by Malcontent · · Score: 1

    If you live in canada then your basic needs are taken care of. You could be unemployed and won't starve.

    Really there is no need for you to whine and moan about the GPL.

    "You know, in a lot of industries, if a bunch of upstart punks tried to do someone else's work for free, they'd get their legs broken."

    Really? Which ones?

    --

    War is necrophilia.

  276. Re:Companies just don't get that GPL means busines by God!+Awful+2 · · Score: 1


    If you live in canada then your basic needs are taken care of. You could be unemployed and won't starve.

    Yeah. I could move back in with my parents... sounds great!

    Really there is no need for you to whine and moan about the GPL.

    Right... because a bare subsistence living sounds appealing to me. Really, you over-estimate the safety net that Canada provides. The economy here ain't doing so hot either. There isn't enough money to pay for everyone to be unemployed.

    "You know, in a lot of industries, if a bunch of upstart punks tried to do someone else's work for free, they'd get their legs broken."
    Really? Which ones?

    Mostly the ones where the teamsters have shady mob connections.

    -a

  277. Re:Companies just don't get that GPL means busines by Malcontent · · Score: 1

    "Right... because a bare subsistence living sounds appealing to me. Really, you over-estimate the safety net that Canada provides. The economy here ain't doing so hot either. There isn't enough money to pay for everyone to be unemployed."

    Look you can have subsidence living without working at all. Sounds great to me. All day to do whatever the fuck you want while the govt takes care of food and shelter. If you want more then that then get off your ass work. Bitching and moaning about the GPL ins't going to make you money.

    "Mostly the ones where the teamsters have shady mob connections."

    In the US assault is a crime. If you get caught you go to jail. We also have pretty good police that can trace genetic evidence and get the person responsible (not that they don't make mistakes mind you they do).

    If you are planning on breaking the legs of GPL programmers then be careful. You will most likely get caught and end up in jail. In the US jail is no fun.

    --

    War is necrophilia.

  278. Re:Companies just don't get that GPL means busines by God!+Awful+2 · · Score: 1

    Apparently, after I mentioned I was from Canada you latched on to that and assumed this is some kind of socialist paradise. In fact, you're not allowed to collect unemployment/welfare benefits unless you are actively looking for work. I'm not sure of all the details, since I've never been out of work long enough to collect, but for unemployment at least you have to document which jobs you have applied for.

    In the US assault is a crime. If you get caught you go to jail. We also have pretty good police that can trace genetic evidence and get the person responsible (not that they don't make mistakes mind you they do).

    Right. As opposed to Canada where assault is legal and our crimes are investigated by trained squirrels. Really, life here is not so different except for the fact that our government isn't run by religious fundamentalists and we aren't completely ignorant of the rest of the world.

    Of course I wasn't literally advocating breaking the legs of GPL programmers. I'm trying to illustrate a point. A lot of other industries have unions that are meant to look out for the collective interests of the workers. In a lot of ways, that's what makes us different from 3rd world countries, 19th century chimney sweeps, etc.

    The software industry has the exact opposite -- a trade organization that lobbies against the interests of the workers. It wouldn't bug me if the product was actually becoming obsolete, but last time I checked, software was still an important commodity. People on /. keep telling me I'm making buggy whips for some reason.

    -a

  279. Re:Companies just don't get that GPL means busines by Malcontent · · Score: 1

    You can start a union if you want. I bet most geeks won't join though.

    Of course starting a union is actual work so you might be all that interested.

    --

    War is necrophilia.

  280. Re:Companies just don't get that GPL means busines by God!+Awful+2 · · Score: 1


    You can start a union if you want. I bet most geeks won't join though.

    I don't want a union. I want a lobby group to buy some politicians and get the GPL ruled unenforceable.

    Of course starting a union is actual work so you might be all that interested.

    Fuck you. I love how just because I stated that I don't want to work 80 hours a week for the rest of my life, you call me a lazy leech on society. What do you feel is an appropriate work week, 100 hours? Are you a gnostic?

    -a