Slashdot Mirror


SCO Awarded UNIX Copyright Regs, McBride Interview

Prizm writes "It seems that SCO is continuing to build up its case for world domination, as today it was awarded U.S. copyright registrations for UNIX System V source code by the U.S. Copyright Office. Shares are up 20%, Novell is nowhere to be found, and SCO is releasing binary, run-only Linux licensing. You can read all about it over in their press release." C|Net is also running an interview with McBride.

1,388 comments

  1. In other news... by kw · · Score: 5, Funny

    SCO awarded patent on breathable air technology, stock in Nature down 50%

    1. Re:In other news... by capnjack41 · · Score: 5, Insightful

      Faith in humanity down 44%

    2. Re:In other news... by SolitaryMan · · Score: 1

      Some people are writing code, others getting money and fame for this code :((

      --
      May Peace Prevail On Earth
    3. Re:In other news... by eupheric · · Score: 4, Funny

      It's a good thing i sold my faith in humanity short a while ago.

    4. Re:In other news... by darkov · · Score: 4, Funny

      I dunno about you, but I'm living in fear of SCO copyrighting my turds, then suing me when I go to the toilet for illegally distributing their intellectual property.

    5. Re:In other news... by Directrix1 · · Score: 3, Informative

      Here, is where I think SCOs major flaw in their argument is, the GPL circa Jan 28, 1999 explicitly states in its preamble:
      To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.

      For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

      Refer to way back machine: http://web.archive.org/web/19990128195748/www.gnu. org/copyleft/gpl.html

      And seeing as how SCO has been distributing Linux which had their code in the kernel. They have thusly, knowingly or not, distributed their rights, to the GPLd code in question, to the public. Because, of the statement above. Or if you want to hear it straight from GNU's statement:
      ...
      Moreover, there are straightforward legal reasons why SCO's assertions concerning claims against the kernel or other free software are likely to fail. As to its trade secret claims, which are the only claims actually made in the lawsuit against IBM, there remains the simple fact that SCO has for years distributed copies of the kernel, Linux, as part of GNU/Linux free software systems. Those systems were distributed by SCO in full compliance with GPL, and therefore included complete source code. So SCO itself has continuously published, as part of its regular business, the material which it claims includes its trade secrets. There is simply no legal basis on which SCO can claim trade secret liability in others for material it widely and commercially published itself under a license that specifically permitted unrestricted copying and distribution.
      ...

      --
      Occam's razor is the blind faith in the natural selection of least resistance and in universal oversimplification. -- EF
    6. Re:In other news... by Anonymous Coward · · Score: 0

      Ok guys, I own the copywrite on the letter "a". Even though the letter a happens to be in your sentances and part of the alphabet I require that all of you mail me 10 cents for every time you used this letter in your posting here. If you don't pay me I'll call a republican lawyer and sue every last one of you!!

    7. Re:In other news... by Anonymous Coward · · Score: 0

      You could always simply return their intellectual property to them in a timely fassion, in that event ;)

      I mean, if they asked for it...

    8. Re:In other news... by Anonymous Coward · · Score: 0

      fucking mormons

    9. Re:In other news... by mattite · · Score: 1

      No need to worry about that. I'm sure there's plenty of previous "art".

    10. Re:In other news... by MuParadigm · · Score: 2, Interesting

      Introduction:

      This is a bit long.

      Most of the arguments here against SCO have been about how it violates the GPL, or otherwise come from an Open Source point of view. I thought it might be a good idea to look at the contracts and court filings themselves, ignoring the other issues, just to see if SCO has *any* contractual claims that can be held.

      My conclusion is that the only claims they have any right to make are in regard to copyright, and that given Unix's tangled development history as well as its historical and continuing use in educational settings, they would have a very difficult time proving that as well.

      Disclaimer: I am not a lawyer. Everything that follow is my own opinion. And it is my biased opinion that SCO is full of shit. However, when this first started, I was willing to give SCO the benefit of the doubt, and my opinion has been mosttly influenced by my reading of the complaints and contracts SCO itself has posted on its web site at http://www.sco.com/ibmlawsuit.

      Argument:

      A) I've assumed ever since Novell backed down from its copyright claims that SCO does own the copyrights. However, it's kind of immaterial, unless (and until, I'm guessing) SCO amends its complaint to include copyright infringement. SCO's other claims regarding trade secrets and "Unix methods and concepts" don't seem to have any contractual basis.

      B) Novell claims to own the SYS V patents and SCO has not disputed that claim. Therefore, I assume Novell owns the patents.

      C) The trademarks for Unix, and its specification, are owned by The Open Group. (I wonder if there is any legal way The Open Group could terminate SCO's rights to the trademarks for Unix and Unixware? Now *that* would really kill SCO's stock price.)

      D) ATT sold IBM a license for a "SOFTWARE PRODUCT" consisting entirely of source code and Sys V documentation. There are no clauses in any of the contracts cited in SCO's complaint regarding "UNIX methods and concepts". SCO's claim to own the rights to "Unix methods and concepts" therefore doesn't hold water contractually, at least as applied to IBM.

      E) ATT had very unusual contracts for SYS V, in that it required the licensee to grant ATT ownership of all derived work. However, and this is extremely important, IBM's side agreement with ATT, XFER-00015B, explicitly states that IBM owns all derivative work produced "by or for it" from the "SOFTWARE PRODUCTS", except for the portions of SOFTWARE PRODUCTS included in the derivative works. I. E., you can modify the work and own it, but don't claim to own anything we copyrighted.

      ATT also specifically references section 2.01 of the license SOFT-00015, the clause that grants it right to derivative work, therby stating that section 2 of XFER-00015B overrides it.

      F) SCO's assertion (in paragraph 105 of the amended complaint) that it owns the derivative work of IBM is therefore in bad faith. This is, in particular, really egregious, and I expect they will at least get a reprimand from the court for this part of the complaint. The case may even be thrown out on this basis since most of SCO's complaints crumble without this assertion, though maybe I'm just being hopeful.

      I'm not sure why IBM hasn't brought this up in its responses yet. I think they're probably waiting to do so until the case is presented in a "proper venue" rather than in a Utah state or Utah federal court.

      G) SCO's trade secret claims are also pretty bogus since the code is likely on the internet and has been used in educational settings for the past 20-35 years. See the judgement denying ATT's temporary injunction request against BSD for further elucidation (sorry, I don't have the URL handy but I know it's somewhere here on Slashdot).

      H) Okay, here is a little bit of bad news: SCO's claims to own RCU and NUMA *may* have some *contractual* basis. Sequent signed contracts with ATT similiar to IBM's, however, Sequent didn't have any side agreement giving them ownership of their derivative works. As n

    11. Re:In other news... by einhverfr · · Score: 1

      Faith in humanity down 44%

      Faith in SCO down 150%....

      Try this link:

      http://www.sco.com/unitedlinux/

      They are still selling Linux under the GPL!

      --

      LedgerSMB: Open source Accounting/ERP
  2. The scary thing by TopShelf · · Score: 5, Insightful

    Does anybody have info as to how expensive this Linux licensing is going to be? It's quite possible that many companies may just pay the fee instead of going through the time, effort, cost and liability of doing otherwise. It's sad to see SCO actually get rewarded for how they're conducting themselves...

    --
    Stop by my site where I write about ERP systems & more
    1. Re:The scary thing by garcia · · Score: 2, Interesting

      unfortunatly, no matter how we feel about this, they are doing it legally.

      If they own the copyrights to SysV code then they can enforce them as they see fit.

      If they can prove that Linux infringes upon those copyrights, then they will be able to charge for its use.

      And please don't say copyright law is crap, we all know it, but it doesn't make it any less valid/enforcable.

    2. Re:The scary thing by pheared · · Score: 1

      Pricing of the run-time, binary UnixWare license will be announced in the coming weeks to customers and resellers. For more information, contact your local SCO sales representative or contact SCO at (800) 726-8649 or on the Web at www.sco.com.

      I agree though, some people will just fall for this. Sucks to be them I guess.

    3. Re:The scary thing by The+Fanta+Menace · · Score: 5, Interesting

      How can they force people to pay for the bits that don't belong to them? Assuming any do at all, that is.

      --
      -- Even if a god did exist, why the fsck should I worship it?
    4. Re:The scary thing by gilesjuk · · Score: 1

      Won't it just be easier (if there's any grounds for their action) to zap the offending code from the kernel or are they going to prevent this by not actually telling anyone where it is?

    5. Re:The scary thing by Anonymous Coward · · Score: 1, Insightful

      they can only force us to pay for what we have in the kernel. So if you are using SMP (which they claim they own the rights to) then they can charge you to use that.

      I assume an immediately new kernel would be released and everyone would move to a completely "clean" kernel.

      I can't understand why that hasn't happened already, but what do I know?

    6. Re:The scary thing by Anonymous Coward · · Score: 0
      Does anybody have info as to how expensive this Linux licensing is going to be?

      Pricing of the run-time, binary UnixWare license will be announced in the coming weeks to customers and resellers. How do I know that? I read the damn release before posting, that's how. Or are you asking if anyone here is privy to secret SCO plans that they want to divulge for karma?

    7. Re:The scary thing by TopShelf · · Score: 3, Insightful

      I'm not saying they don't have the right to enforce their copyright, but you have to admit that the way they're doing business these days, such as sending threatening letters to the Fortune 1000 and smearing OS leaders and practices, is generating plenty of illwill out there. I can't see them doing well in the long-term as a result of the last few months...

      --
      Stop by my site where I write about ERP systems & more
    8. Re:The scary thing by Surak · · Score: 5, Informative

      If they own the copyrights to SysV code then they can enforce them as they see fit.

      If they can prove that Linux infringes upon those copyrights, then they will be able to charge for its use.


      Wrong answer. *They* themselves distributed a Linux kernel, complete with source up until a week or so after they filed the suit, IIRC. If it was infringeing then, then they have relased whatever code might be in there under the terms of the GNU General Public License.

      Since the Linux kernel wouldn't by any means be comprised of 100% of their code, that makes any Linux kernel that contains their code a derivative work. Which means that they MUST distribute the source to remain in compliance with license.

      In other words, SCO, by releasing a binary-only Linux, is violating the terms of the GNU General Public License, and hence, they are breaking the law.

    9. Re:The scary thing by garcia · · Score: 0

      this is all irrelevant. They applied for a copyright and were given it. That means that ALL SysV code is owned by them.

      If Linux is using SysV code (which apparently it is) then they can enforce licensing of that.

      Their actions against the community means NOTHING. Smear campaigns, "extortion", whatever, does NOT matter.

      They own copyrights, they enforce them, we pay.

    10. Re:The scary thing by twistedcubic · · Score: 4, Insightful


      unfortunatly, no matter how we feel about this, they are doing it legally.

      Umm, no. They can't distribute other people's copyrighted code, and this includes Linux. If someone inserted unauthorized code in Windows, would the copyright holder get to own Windows???? The only way SCO can distribute Linux is under the GPL.

    11. Re:The scary thing by dissy · · Score: 5, Insightful

      > If they own the copyrights to SysV code then they can enforce them as they see
      > fit.

      True, but...

      > If they can prove that Linux infringes upon those copyrights, then they will be
      > able to charge for its use.

      Linux can not possibly infringe. It was made from scratch.

      This is like saying "Well, the makers of the Terminator movie have a copyright on that movie, so they can sue anyone that makes any story that even resembles a plot where robots take over the world."

      That isnt how copyright works, even in copyrights current fucked up state.

      Ford can not sue Chevy for designing 'a car'
      Intel cant sue apple for making 'a computer'

      Copyrights are very specific. Linux is NOT SysV in any way/shape/form. Linux was made from scratch.

      The only possibly questionabe action is that IBM added code to Linux that they shouldnt have. They broke a contract. The fight is between IBM and SCO.

      The _ONLY_ right SCO has using copyright of code is to demand you do not distribute it.
      With Linux, this can EASILY be done by removing the code and replacing it.

      That is the extent of the effect this could have over Linux.
      Any and all damages caused are directly and soley IBMs fault, and they alone will pay for it if found guilty.

    12. Re:The scary thing by GammaTau · · Score: 4, Insightful

      If they can prove that Linux infringes upon those copyrights, then they will be able to charge for its use.

      Yeah, if party A can prove that party B is infringing the rights of the party A, then the party B is in trouble. So far there's no trouble because there is no evidence.

      Please stop helping the SCO FUD machine. They have not shown any evidence nor are they planning to.

    13. Re:The scary thing by DevilM · · Score: 4, Interesting

      You are not entirely correct. As have others have shown, they are still distributing a Linux kernel via FTP.

    14. Re:The scary thing by ebh · · Score: 3, Interesting

      Here's their current price list. I don't know if their "insurance policy" binary licenses will be priced the same. I suspect they'll be lower, because they're trying to get as many sux0rs to buy into their protection racket as possible.

      As a manager, I'd be more likely to bet $200 (for, say, a single-page hold-harmless letter masquerading as a 0-user 0-CPU 0GB UW "license") than I would be to bet $2400 (the current cost of a 25-user dual-CPU 4GB UW7.1.3 license plus media).

    15. Re:The scary thing by garcia · · Score: 2, Insightful

      They obviously believe that they can defeat the GPL in court.

    16. Re:The scary thing by fwr · · Score: 3, Informative

      As far as I'm aware, the US Government does not do copyright searches like they do patent searches. I sincerely doubt that the copyright office did a comparison between Novell's copyrighted material and SCO's and determined that SCO's was significantly different to award the claim. I believe they probably grant any copyright (practically, if you tried to copyright a Harry Potter book or some other well-known text then it would proably not go unnoticed) and let the copyright holders battle it out in court.

      Just because they were granted a copyright does not mean that it is a valid copyright.

    17. Re:The scary thing by Ioldanach · · Score: 4, Informative
      unfortunatly, no matter how we feel about this, they are doing it legally.

      If they own the copyrights to SysV code then they can enforce them as they see fit.

      If they can prove that Linux infringes upon those copyrights, then they will be able to charge for its use.

      And please don't say copyright law is crap, we all know it, but it doesn't make it any less valid/enforcable.

      No, if they encumber the linux codebase with their own license, then the GPL becomes void and no longer can be used to distribute Linux. At that point, the distribution of every piece of linux that they don't explicitly own becomes prohibited, completely, because Linux falls back to copyright law which indicates that the contributors of the other pieces still own them and have not licensed them to any distribution but GPL. Therefore, if they tell people they need to pay to run linux, linux becomes un-runnable.

      In fact, if they actually make anyone pay to run linux, then they can be sued by the contributor of every other piece of code for copyright violation. After all, they distributed the rest of the code without a valid license to do so.

    18. Re:The scary thing by alatesystems · · Score: 1, Informative
      No, that's stupid. I keep hearing this over and over. That was the Santa Cruz Operation, not the new SCO. The new SCO has never released a version of linux, period.

      From their site:

      SCO History Caldera, Inc. was founded in 1994 by Ransom Love and Bryan Sparks. In 1998, Caldera Systems, Inc. was created to develop Linux-based business solutions. In 2001, Caldera Systems, Inc. acquired the assets of the Server Software Division and Professional Services Division of The Santa Cruz Operation, Inc. (SCO), forming a new company, Caldera International, Inc. In 2002, Caldera changed its name to The SCO Group (Nasdaq: SCOX).
      Source: Company Profile
    19. Re:The scary thing by Xerithane · · Score: 5, Interesting

      In other words, SCO, by releasing a binary-only Linux, is violating the terms of the GNU General Public License, and hence, they are breaking the law.


      Not breaking the law, they are in breach of contract. Who is going to take them to court to fight it? Nobody. However, this issue will be pressed by the IBM law team, and quite probably will have a favorable outcome on this point.

      However, unless the members at SCO had authority (ostensible, I believe) to release the kernel source than it is not binding that SCO released it knowingly and willingly. Just like if I release proprietary source at my job, it would not be binding unless I had authority to do it. I think that it is a given that whomever released the packages at SCO did have the proper authority to do it, so I don't think any of this paragraph actually matters.

      --
      Dacels Jewelers can't be trusted.
    20. Re:The scary thing by garcia · · Score: 1

      again, our personal beliefs about the copyright system are IRRELEVANT.

      If they are granted a copyright and they choose to enforce it, it's up to the people being sued for non-compliance to prove that SCO is wrong.

      Are the 5% of NORMAL computer users going to pony up the $1500 licensing fee to continue legally using it, I highly doubt it.

    21. Re:The scary thing by JWW · · Score: 4, Interesting

      What I like about all this is that they own the copyrights to the CODE, but are choosing to license the BINARY implementation.

      Convinent that, it will be awfully hard for Linux users to find the offending CODE in all those 0's and 1's.

      Also if the code SCO owns is in the Linux kernel, and they sell it, aren't they required to distribute it under the GPL for free?

      This is mindblowingly evil and an absolute anethma to everything open source stands for.

      I can only hope to have a chance to soon view a press conference where IBM announces its takeover of SCO, and fires everyone who still "works" there. The only bad thing about this is how much money McBride will make on the deal.

    22. Re:The scary thing by jbottero · · Score: 1

      I assume an immediately new kernel would be released and everyone would move to a completely "clean" kernel.

      I can't understand why that hasn't happened already, but what do I know?


      Well, hopefully the smart guys on the Kernel team are thinking about this already, not running in circles under some dilusion that the issue will not come up.

      I mean, why even wait? Chop SCO's head off now and just change any "questionable" code... There has been much talk of this "IF" SCO prevails, just do it "NOW".

    23. Re:The scary thing by Anonymous Coward · · Score: 0
      *They* themselves distributed a Linux kernel, complete with source up until a week or so after they filed the suit, IIRC. If it was infringeing then, then they have relased whatever code might be in there under the terms of the GNU General Public License.

      Doubtful, since SCO didn't put the code in the kernel, they weren't responsible for it being there.

      You can argue GPL 'stole' it from them unknowingly, just don't expect a federal judge to be convinced of your argument, especially since "linux" itself makes no attempts whatsoever to prevent stolen IP from being submitted into the kernel in the first place.

    24. Re:The scary thing by Surak · · Score: 4, Informative

      How? I've changed my stance on this somewhat.

      The GPL doesn't take away any rights whatsoever. It only grants rights, and places conditions on those rights.

      If I give you the binary and source code to a program I wrote, and it contains a copryright notice, you have NO RIGHT to distribute or disclose that source NOR it's binary to third parties. Period. The GPL gives you the right to do that, ONLY ON THE CONDITION that you also distribute the source code and make it available.

      It's not defeatable at all. Unless they accept the GPL, they have NO RIGHT to distribute the program. At all. Not because it's GPL, but because it is copyrighted and fully protected by United States Copyright Act of 1976, the Software Act of 1980, and various international treaties including the Berne Convention. Failure to abide by the terms of the GPL is called breach of contract. Pure and simple.

    25. Re:The scary thing by Anonymous Coward · · Score: 0

      *They* themselves distributed a Linux kernel, complete with source up until a week or so after they filed the suit

      Not quite.

      They themselves distributed a Linux kernel, complete with the source, and continue to do so.

    26. Re:The scary thing by JWW · · Score: 2, Interesting

      It hasn't happened because no one really knows what code is bad and SCO won't tell you unless you sign an NDA.

      If you're a kernel developer signing the NDA probably prohibts you from actualy going about removing the code as that would "disclose" what code is in question.

      I think I'm actaully beginning to hate SCO more than Saddam Hussein!

    27. Re:The scary thing by TheBaker · · Score: 1

      is that they can now invoke DMCA...And after looking at what the RIAA has gotten away with....

    28. Re:The scary thing by idlethought · · Score: 2, Informative

      Nope.. If SCO code was in Linux then shipping Linux would be illegal, and SCO cannot make it legal.

      If a company ships Linux 'knowing' that SCO have rights to portions of it, then they are breaching the copyright because the kernel they no longer have the right to distribute under the GPL.

      Since SCO still haven't indicated what is in the kernel and have won no court cases proving that the code is in the kernel, and have previously shipped the code under the GPL knowing it was in there, and are now effectively inciting piracy - it will all probably fizzle out when they go belly up and IBM buys up the rights.

    29. Re:The scary thing by Creepy+Crawler · · Score: 1

      >>>And please don't say copyright law is crap, we all know it,

      Only as long as it's not GPL infringement. Then its the end of the world.

      hint: GPL is a COPYRIGHT license, not a eula.

      --
    30. Re:The scary thing by u-235-sentinel · · Score: 1

      Personally I'm waiting for SCO to cough up the code in question and allow us to get rid of it.

      We don't need no stinking SCO code in our kernel. Once it's replaced I don't think they can say much about it.

      Probably why they have been so weird in their handling of all this. They don't want the code removed and want more customers so to speak.

      Once we discover the code it's gone. And SCO can take a flying leap.

      --
      Has Comcast disconnected your Internet account? Same here. You can read about it at http://comcastissue.blogspot.com
    31. Re:The scary thing by KeyserDK · · Score: 1

      It may be legal in US. But corporate laws are stricter in EU. At least it wasn't legal to claim what they did in germany without backing it up.

      --
      still reading?
    32. Re:The scary thing by Surak · · Score: 4, Interesting

      Hmm...then what's this this doing on their FTP server? Hmm?

    33. Re:The scary thing by b29651 · · Score: 1

      No they want a guardianship type appointment so they can control the releases .with enough IP copyrights this might be possible with courts of today

    34. Re:The scary thing by Anonymous Coward · · Score: 0

      Mod this troll down. Not only does he have no clue what he is talking about but he is confusing copyrights and patents. If I write a book and one chapter of the book is copied from Harry Potter word-for-word then I am infringing on the copyright. It doesn't matter whether I cut-and-paste the section, OCR'd it or hand typed it. It is still infrigement.

      And if Ford held a patent on a car then Chevy could not build it. Fortunately any patents on automobiles expired decades before any of us were born.

    35. Re:The scary thing by Surak · · Score: 2, Informative

      Breach of contract is breaking the law. Not criminal law, but civil law. And with the authority question, you're getting into agency issues. The problem is when the source is STILL sitting on their VERY PUBLIC FTP server, it's hard to say that the people in charge didn't know about it.

    36. Re:The scary thing by Trigun · · Score: 5, Insightful

      The biggest problem with the Kernel guys redoing it, is now they can be considered 'tainted'. Hell, because of the widespread distribution of the kernel source, everyone can be considered tainted. It is now impossible to do a clean-room implementation. The innovations which SCO own (not created) could be considered inspiration to the new implementation, and therefore any new implementation would be considered a derivative work.
      We have to shoot everyone and start over to have a true untainted implementation.

      Or we could bury SCO.

    37. Re:The scary thing by Surak · · Score: 1, Informative

      Oh yeah, let's not forget that by not following the GPL, they are violating *copyright* law as well, which has recently been criminalized. So strike what I just said about not being a violation of criminal law.

    38. Re:The scary thing by cdrudge · · Score: 1

      The old SCO joined up with Caldera transfering the unix side of the business to Caldera and spinning off Taranella and it's business. Candera released OpenLinux. Caldera then went back to the name The SCO Group. For a while it was still legally Caldera, but was d/b/a The SCO Group. It has since officially changed names to The SCO Group. So I think that legally they have released OpenLinux as the same corporation that they were. Changing names won't change that fact.

    39. Re:The scary thing by Anonymous Coward · · Score: 0
      Unless they accept the GPL, they have NO RIGHT to distribute the program.

      Again, who said they were? This is only a form of insurance for businesses whose linux plans are substaintial enough that they want protection from future litigation, and is not some new version of 'SCO Linux' that you now have to pay for. How hard is that to understand? Terribly, according to some of these posters.

    40. Re:The scary thing by frane · · Score: 1

      From the article, "SCO announced that Linux contained SCO's UNIX System V source code and that Linux was an unauthorized derivative of UNIX..." Whether Linux was made from scratch or not, SCO is claiming that it was an unauthorized derivative. I don't know how the legal definition of derivative will play into this, but clearly SCO thinks that they have some control over who makes Unix-like operating systems.

    41. Re:The scary thing by Martigan80 · · Score: 1

      then they have relased whatever code might be in there under the terms of the GNU General Public License.

      My question then would be; Does the American courts recognize the GPL? I mean it great and people have to follow it in theory, but how strong will the GPL hold up in court? How many are familiar with it? Better yet how many can be bought off on it?

      --
      This SIG pulled due to lack of funding. (This damn war is costing too much!)
    42. Re:The scary thing by Anonymous Coward · · Score: 0
      The biggest problem with the Kernel guys redoing it, is now they can be considered 'tainted'. Hell, because of the widespread distribution of the kernel source, everyone can be considered tainted. It is now impossible to do a clean-room implementation. The innovations which SCO own (not created) could be considered inspiration to the new implementation, and therefore any new implementation would be considered a derivative work.

      Yes, true, and should SCO win they may even get the courts to injunct whoever does attempt to remove it from ever working on Linux again.

    43. Re:The scary thing by morleron · · Score: 2, Informative

      I really don't think that SCO's ownership of copyrights will have much of an effect on Linux. Once we know what, if any, sections of code are in violation of SCO copyrights then we re-write the code to eliminate the infringement. This will have the added benefit of putting SCO in a position in which they will not benefit from their actions. Don't let SCO's bluster scare anyone into making any premature moves with regard whether or not to use Linux, keep using it, etc. With the speed the Open Source/Free SOftware community can react I would expect any needed code changes to happen quickly.

      Just my $.02,
      Ron

      --
      Impeach Barack Obama for violating the Constitutional requirement to be a "natural born" citizen to hold the office of P
    44. Re:The scary thing by the+gnat · · Score: 2

      If they are granted a copyright and they choose to enforce it, it's up to the people being sued for non-compliance to prove that SCO is wrong.

      Okay, bring it on. The burden of proof is currently on SCO. If they decide to sue, the violating code will have to be shown in court, and it will no longer be public. Unfortunately, some companies will undoubtedly decide to cough up licensing fees rather than challenge the claim. But it takes a hell of a lot of balls to ask people to pay you to license code they won't even tell about, and threaten them with a lawsuit unless they stop using infringing code that hasn't been identified.

      Anyway, they still haven't been honest or clear about whether the infringing code was developed by AT&T/SCO, or whether it was developed by IBM. There's a huge difference - basically, if only the latter applies, copyright is irrelevant. SCO is being deliberately vague because they hope to sucker CTOs who don't understand enough IP law, or are too cheap to force a showdown.

    45. Re:The scary thing by Anonymous Coward · · Score: 0

      Doubtful, since SCO didn't put the code in the kernel, they weren't responsible for it being there.

      No, but they are responsible for distributing it - which they are still doing.

      If SCO had stopped distributing the kernel when they had found out about it, then you might have a point. However, THEY ARE STILL DISTRIBUTING IT.

      Here's a simple test:

      Does SCO know that the license for the kernel is GPL?

      Does SCO know that "their" code is in the kernel?

      Is SCO distributing that code right now?

      The answer to all three questions is "YES"

      The bottom line is: THEY are distributing "THEIR" code as part of an GPL'ed product RIGHT NOW. How "their" code got there is irrelevant. The ONLY thing that grants them the right to distribute the kernel is the GPL, and they must therefore obey it's terms. The fact that they continue to distribute it means that they are distributing it under the GPL.

    46. Re:The scary thing by Dastardly · · Score: 4, Interesting

      Does anybody have info as to how expensive this Linux licensing is going to be? It's quite possible that many companies may just pay the fee instead of going through the time, effort, cost and liability of doing otherwise. It's sad to see SCO actually get rewarded for how they're conducting themselves...

      Paying the fee actually opens companies to liability from Linux developers. Because now they have received a copy of Linux code in violation of the GPL because whoever they got their Linux from could not have given it to them. Since, they did not receive the code in accordance with the GPL, they have no license for the code whatsoever and standard copyright law applies giving them no rights with regards to Linux.

      So, Linux developers can sue, and win, because by paying the fee to SCO they acknowledge that they have kowingly received Linux in violation of the GPL, and have no license to do anything with said software. Are developers likely to sue linux customers... No, they will do everything they can not to, but it may come down to that to at least prevent SCO from hijacking Linux.

      IANAL
      Dastardly

    47. Re:The scary thing by arose · · Score: 1

      They can't enforce a bloody fuck. How mony of the kernel developers are going along with it? It takes ONE major kernel contributor and a little funds tu make this licensing sheme go dodo.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    48. Re:The scary thing by BJH · · Score: 1

      You've made quite a few comments along these lines. However:

      they are doing it legally
      If they can prove that Linux infringes upon those copyrights

      How do you reconcile these two statements? They have proved nothing yet. NOTHING. But you seem to have a direct connection to God that tells you that their licensing of Linux is legal.

      Until they prove that there is copyrighted code, that they own under current copyright law, in the Linux kernel, their licensing scheme is a hair away from fraud. And if it comes out in court that they've been acting in bad faith, you can bet any companies that licensed Linux from them will be releasing the lawyers to sue them for fraud.

    49. Re:The scary thing by schon · · Score: 1

      Unless they accept the GPL, they have NO RIGHT to distribute the program.

      Again, who said they were?


      Well, HOW ABOUT THEIR FTP SITE, FOR ONE?

      How hard is this to understand? Terribly, according to you.

    50. Re:The scary thing by axxackall · · Score: 3, Insightful

      *New* SCO didn't buy any Unix copyright either, it was *old* SCO who bought it. But anyway, all merge and aquisition actions inherit all belongs of old entities unless it's says differently.

      --

      Less is more !
    51. Re:The scary thing by wfberg · · Score: 2, Informative


      Again, who said they were? This is only a form of insurance for businesses whose linux plans are substaintial enough that they want protection from future litigation, and is not some new version of 'SCO Linux' that you now have to pay for. How hard is that to understand? Terribly, according to some of these posters.

      In other words; a protection racket. Racketeering is illegal, you might know. As is barratry.

      SCO has, and are, distributing linux, which means they have accepted the GPL, and so they cannot sue people for using linux, at least up until the version that they distribute, whatever code it may contain. So a "license" from them protects you from.. barratry!

      I call RICO.

      --
      SCO employee? Check out the bounty
    52. Re:The scary thing by JessLeah · · Score: 1

      To most people, if it isn't on the Web site, it doesn't exist. It would be VERY easy to make the case that FTP is only for "hackers" and/or "highly technical individuals". Hell, SCO could even argue that those who use FTP to obtain software from them that they removed from their Web site were "hacking", and that they "should have known that this software was no longer for public download or use without appropriate licensing and payment." They could throw out some nice, Judge-convincing BS like "We only made these files available via the 'FTP' program, which is only for highly advanced technical individuals such as corporate IT managers, for the convenience of our paying customers. It was not intended for download by unlicensed individuals, and in fact doing so constitutes hacking as per the terms of the DMCA..." And the Judge would buy it hook, line and sinker, since it rings true of the Good Ol' American style of corporate IP-speak.

    53. Re:The scary thing by stoney27 · · Score: 3, Informative

      I would assume that you did not watch the 21min interview with McBride. He put the problems into three buckets, first was the line by line infringements, then there was the derived works problems and then finally the "re-implementation" of System V ideas. He concentrated on the first two since the last one would be the hardest to prove.

      He talked a lot about the SMP code in the 2.4 kernel, a lot. And basically said that if we went after the smaller guys, IE "Red Hat" it would shutdown Linux all together. Which would have the effect of killing most of that OS sector and any chance of them collecting any money if they win.

      Also it sounds like they will be making more of there case known in mid-August

      --

      It is said that a child learns wisdom from the parent,
      but the truly wise parent learns joy from the child
    54. Re:The scary thing by Dastardly · · Score: 1

      Also if the code SCO owns is in the Linux kernel, and they sell it, aren't they required to distribute it under the GPL for free?

      Under the GPL, yes. Free, no. Of course the first person to get the code can redistribute it at any price they want under the GPL.

      Dastardly

    55. Re:The scary thing by BJH · · Score: 3, Informative

      If Linux is using SysV code (which apparently it is)

      Where the hell did this come from? And why is it 'apparent'? There has been NO evidence released publically to indicate that any SystemV code is in Linux. ZERO.

      So stop spreading crap until a few more facts come out.

    56. Re:The scary thing by Rogerborg · · Score: 0

      They're not in breach of contract. The GPL is a license, not a contract. If they don't adhere to the terms of that license, they're (arguably) in breach of copyright. I say "arguably" because it will be up to the rights owners to show that, but it won't exactly be difficuly.

      Let's keep our terms straight.

      --
      If you were blocking sigs, you wouldn't have to read this.
    57. Re:The scary thing by plague3106 · · Score: 1

      No, i'm just going to continue using it.

    58. Re:The scary thing by Rogerborg · · Score: 1

      Doesn't really matter. The GPL is the only thing that gives them rights to duplicate the copyrighted source owned by other contributors. If the GPL doesn't "hold up", then they are in breach of copyright. Nothing else gives them the rights to duplicate. It's that simple.

      --
      If you were blocking sigs, you wouldn't have to read this.
    59. Re:The scary thing by Anonymous Coward · · Score: 0

      How many times do I have to say it? If you distribute any part of a GPL program, in any form, you are accepting the terms of the GPL. Period. If you violate those terms, you have breached your contract with the copyright holder, and you have committed a copyright violation as well, possible a criminal one. How hard is *that* to understand?

    60. Re:The scary thing by BJH · · Score: 2, Informative

      it's up to the people being sued for non-compliance to prove that SCO is wrong

      Absolutely incorrect. The burden of proof lies on SCO, not on the Linux community.

      And speaking of lies, do you mind not spreading bullshit? Your posts under this article are all groundless until more evidence comes out.

    61. Re:The scary thing by Xerithane · · Score: 1

      Oh yeah, let's not forget that by not following the GPL, they are violating *copyright* law as well, which has recently been criminalized. So strike what I just said about not being a violation of criminal law.

      Well, there isn't really such thing as breaking civil law. Civil laws are statutes set to protect those who take action against other parties that wrong them. I still understand what you are saying, so it's neither here-nor-there. Just a little semantics issue...

      Unfortunately there are only certain cases where violating copyright law will fall under criminal activities. Knowingly redistributing something while violating a license doesn't hit that, yet. I really wish that there was some sort of encryption scheme that went into the kernel, even if it was exceptionally trivial so that it fell under copyright-protection circumvention.

      That would make it especially odd.

      --
      Dacels Jewelers can't be trusted.
    62. Re:The scary thing by Dastardly · · Score: 1

      Again, who said they were? This is only a form of insurance for businesses whose linux plans are substaintial enough that they want protection from future litigation, and is not some new version of 'SCO Linux' that you now have to pay for. How hard is that to understand? Terribly, according to some of these posters.

      Pretty stupid insurance considering that by purchasing it the business purchasing it acknowledges they received Linux in violation of the GPL, and therefore everything falls back to standard copyright law in which the purchaser has no rights whatsoever. So, the purchaser now has a license to use SCO's code, and no license for the rest of Linux.

      IANAL
      Dastardly

    63. Re:The scary thing by Anonymous Coward · · Score: 0
      To most people, if it isn't on the Web site, it doesn't exist.

      Exactly, which it isn't, only several statements that they have suspended their Linux ventures indefinitely.

      Just because slashdot found a back door or hacked into their FTP servers does not mean SCO is still legally distributing it, especially not intentially.

    64. Re:The scary thing by SpaceLifeForm · · Score: 1
      Just because the source code is distributed, does not mean that everyone is tainted. In order to be tainted, you would have had to read (and *understand*) the source code, and very few do that unless they have a specific area of code they are interested in or having a problem with.

      Your possible argument (any implementation could be considered a derivative), logically can lead to the conclusion that if someone is sentient, anyone else having a logical thought is infringing!

      Things (at least in the U.S.) may be getting that screwed up, but there is still hope.

      When the phrase "All your thoughts are belong to us" becomes law, we *will* have a revolution.

      --
      You are being MICROattacked, from various angles, in a SOFT manner.
    65. Re:The scary thing by afidel · · Score: 1

      Yes but in copyright law there has to be a sufficiently large violation to warrent enforcement. So far they have shown only one function that was aparantly copied and they have not shown proof that the function in question even origionated in SysV (It could well have origionated in project Monterey in which case IBM probably has at least some ownership over it). All we know so far is that the code in question is pretty trivial and not some huge architectural construct that was copied wholesale. When they get to discovery and we find out how much code was actually copied THEN we can have an informed discussion on the issue, until then we are just blowing hot wind into SCO's PR sails.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    66. Re:The scary thing by afidel · · Score: 1

      If they "defeat" the GPL then their liscense to others code reverts to copyright law and then they have NO rights to it because no one would give SCO rights to their work at this point.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    67. Re:The scary thing by jazman_777 · · Score: 1
      Well, hopefully the smart guys on the Kernel team are thinking about this already, not running in circles under some dilusion that the issue will not come up.

      Imagine SCO going after Bitkeeper. Message to Kernel team: "You are 0wn3d!"

      --
      Slashdot: Failed Car Analogies. Amateur Lawyering. Anecdote Battles.
    68. Re:The scary thing by Trigun · · Score: 1

      I know that it sounds strange, but this entire case sounds even stranger.

      There could have been several resolutions to this case, but SCO has essentially blockaded all avenues of compromise. I could see them saying that the kernel hackers can't recode the kernel because they have seen SCO's version and will obviously infringe on it.

      Any time SCO wants money, it just sues or makes everyone buy a license in perpetua.

    69. Re:The scary thing by u-235-sentinel · · Score: 2, Insightful

      "The only way SCO can distribute Linux is under the GPL."

      Ahh yes but would anybody use it after all this B.S.?

      Whenever someone asks if I'm worried about a lawsuit I tell them not really. If SCO can demonstrate ANYTHING other than bullshit then I'll be happy to remove the code in question and continue using Linux. You know it will be just fine without their code. Hell... isn't this one of the reasons the source code is available? To get rid of stuff we don't want (or add it).

      SCO can sue me all they want. They won't get a dime (nor lawyer fees). But if they want to send a cease and desist then I'll be happy to remove their code. Just tell me where :-)

      --
      Has Comcast disconnected your Internet account? Same here. You can read about it at http://comcastissue.blogspot.com
    70. Re:The scary thing by Archie+Steel · · Score: 1

      Yep. Downloaded it just to make sure...Don't they realize they're digging their own grave, still allowing the Kernel to be downloaded?

      --

      Reminder: find a new sig
    71. Re:The scary thing by Anonymous Coward · · Score: 0

      Do you have permission from SCO to use their FTP servers? Here is what is says on their official website:

      The sale of this SCO Linux product to new customers is currently suspended due to intellectual property (IP) issues associated with the Linux operating system. Accordingly, SCO has announced the suspension of its own Linux activities until the issues surrounding Linux IP and the attendant risks are better understood and properly resolved

      http://www.sco.com/products/scolinuxserver/

    72. Re:The scary thing by Anonymous Coward · · Score: 1, Insightful

      5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.

      That's a pretty flaky clause.

    73. Re:The scary thing by CorwinOfAmber · · Score: 2, Insightful
      The biggest problem with the Kernel guys redoing it, is now they can be considered 'tainted'.

      I don't think this matters. Copyright law prevents you from making a copy, but it does not prevent you from "writing it in your own words", just like when you turned in book reports in school.

      --
      My future's determined by Thieves, thugs, and vermin -- The Offspring
    74. Re:The scary thing by Darth_Burrito · · Score: 1

      McBride was asked about this directly in the interview. His response was a little hazy but basically, he pointed to two arguments.

      First he said something about the GPL providing an out, in which I believe he was referencing section 7. This section is about patent/copyright infringement and about how if you can not distribute under the terms of the gpl, then you simply can't distribute. He seemed to be under the impression that SCO was no longer distributing (but I thought they were?)

      Second, McBride claimed that federal copyright law (no idea where) specified that you could not accidentally give away your copyright. It is pretty easy to envision a scenario of SCO ip seeping into linux via a third party without SCO knowing, resulting in it's accidental distribution by SCO. Of course, if this clause to copyright does exist, I'd be curious to find out who holds the burden of proof. Considering the scope of the allegations McBride made against Linux and the fact that they distributed their own version of Linux for so many years, it would seem unlikely that the level of infringement SCO indicates would have gone unnoticed for so long (right up until the moment when the company is circling the drain).

    75. Re:The scary thing by Xerithane · · Score: 3, Interesting
      They're not in breach of contract. The GPL is a license, not a contract. If they don't adhere to the terms of that license, they're (arguably) in breach of copyright. I say "arguably" because it will be up to the rights owners to show that, but it won't exactly be difficuly.

      Yes, they are in breach of contract. Licenses are contracts. There are two ways to go after a license violation. IP infringment (copyright), or contract law. Depending upon the circumstances, it's easier to do either. Typically, with software, it is easier to go after copyright infringement but you can still do both. It depends upon the license. If it's a signed license, it's easy. Otherwise it gets into this:
      Resolving the issue of enforceability of a "shrink-wrap" license, the court essentially decides the dilemma: was it a contract of sale in which an offer and acceptance were made at the store; or was it a licensing contract in which an offer was made at the store and acceptance was made sometimes later by an incident of use of the software.


      You see the common thread there, "contract" -- in the terms of "Licensing Contract".

      Let's keep our terms straight.

      Yes, lets.

      --
      Dacels Jewelers can't be trusted.
    76. Re:The scary thing by NoUse · · Score: 1

      ftp.sco.com isn't really a backdoor. More like a frontdoor. Plus the src rpm they have there no longer contains any actual source, but it did long after they filed the lawsuit.

    77. Re:The scary thing by Darth_Burrito · · Score: 1

      In the interview, McBride mumbled something about what sounded like a public show and tell session August 17th or 18th. Of course then again, he also said that if anyone wanted to come in and check themselves they were welcome to do so :) Field trip anyone?

    78. Re:The scary thing by Anonymous Coward · · Score: 0

      why doesn't someone just shoot the git

    79. Re:The scary thing by Anonymous+DWord · · Score: 1

      It would be VERY easy to make the case that FTP is only for "hackers" and/or "highly technical individuals".

      Go ahead then. We're all reasonably intelligent here. Shouldn't take you very long to make the case.

      --
      "If he thinks he can hide and run from the United States and our allies, he's sorely mistaken." Bush on bin Laden
    80. Re:The scary thing by kylemonger · · Score: 2, Funny
      I think I'm actaully beginning to hate SCO more than Saddam Hussein!

      I wonder if Ari Fleischer's Single Bullet Doctrine is applicable here. :)

    81. Re:The scary thing by Darth_Burrito · · Score: 1

      In the interview, McBride claimed their were hundreds of thousands of tainted lines and he implied rather directly, that simply excising these portions of code might not be practical or satisfactory. His suggestion involved going back to a 2.2 kernel since most if not all of the identified infringements were made in 2.4.

    82. Re:The scary thing by Speare · · Score: 2, Insightful

      I think the appropriate analogy here is that a retailer (think Wal*Mart) took down an advertising poster on their front door, but didn't remove the products from the shelf. The "shelf" is not for "highly technical users." No retailer could claim to have recalled an unsafe product without actually removing the product from those shelves or locking the entire building from public access. Removing the advertisements is not enough.

      --
      [ .sig file not found ]
    83. Re:The scary thing by moonbender · · Score: 2, Interesting

      Yeah, because "This is a private FTP server, you are not allowed to access anything on this site!" style disclaimers on public FTPs are working just brilliant as a legal defense for Warez sites. If you're running a non-protected, DNS'ed, anonymous FTP server, which you also link to on your web site[1], you'd better be ready to be liable for its contents. It's not like they'd start claiming their box got owned and somebody places those files there, distro style.

      Heck, they don't have a DON'T DOWNLOAD disclaimer of any sort on the FTP itself - and the web disclaimer is far from explicit: they say they've suspended their activities, well obviously that's not true!

      Note that I don't have a clue whether this is actually relevant for the case in point, I'm just saying they are in fact distributing those files.

      [1] I assume they do that, though not necessarily to that folder.

      --
      Switch back to Slashdot's D1 system.
    84. Re:The scary thing by number6x · · Score: 1

      This would upset decades of precedent set in IP cases that have come before. Both AT&T and Microsoft have put stolen intelectual property in their operating systems. Microsoft Windows TCP/IP stack contained stolen intelectual property from Berkeley Systems, and AT&T SysIV and SysV unix contained stolen IP from Berekely Systems.

      In both these previous cases the theiving companies (At&T and Microsoft) were responsible for the theft, and they indemnified their customers from any financial liability.

      BSD never went after the users. SCO wants to change this by trying to charge Linux users a license fee. If they set this new precedent, BSD would then have a case for going after all Windows at SysV users.

      SCO's customers will all be liable for using the stolen code AT&T put in Unix before SCO bought UNIX! I hope BSD is willing to charge enough to make it hurt. Then BSD could use the new SCO precedent to go after users of Windows versions that had stolen IP in it, and make much more money. BSD could be huge!

      SCO may inherit the copyrights to UNIX, but UNIX is already tainted with too much stolen IP.

      Precedent has already been set in software and many other industries. If IBM put stolen intelectual property into Linux (highly unlikely), then IBM would be liable but linux users would not be liable.

      Consider a hypothetical situation. If Ford stole some patented idea from Mazda and put it in a european designed Ford Focus*, Ford would be liable but all the Focus drivers would not have to send a check to Mazda too! Ford would take the hit and indemnify its customers. Ford Focus drivers would not be liable to Mazda.

      Or consider a real life case. Sears stole the patented idea for the famous Craftsman adjustable wrench. Sears lost in court after years battling the original patent owner, Sears paid up. No owner of a Sears Craftsman adjustable wrench was liable, only Sears.

      Or consider the script for the Eddy Murphy movie 'Coming to America' was based on stolen intelectual property. The movie company, Paramount, had to pay Art Buchwald (the original author) but not a single movie goer had to cough up a few extra pennies to pay. None of them were liable for Paramount's infringement of copyright law.

      Sure the customers always pay in the long run because all costs get passed along to the consumer level eventually. This is true in the software industry too. SCO's actions add to the total cost of developing and delivering software. Their actions make it more costly for companies to create and sell products in the USA. Greedy short sighted business is bad for our economy.

      I hope the Europeans watch these events and implement some less restrictive, more free market oriented intelectual property laws than we have here in the good old US of A!

      *(a sub compact car that replaced the Mazda designed Ford Escort in the North American market. The Mazda based Escort replaced an even earlier European based Escort.)

    85. Re:The scary thing by E_elven · · Score: 1

      The thing I'm wondering, if they're licensing the binary implementation, which compiler's implementation are they going to be using? :)

      --
      Marxist evolution is just N generations away!
    86. Re:The scary thing by Jeremi · · Score: 1
      In other words, SCO, by releasing a binary-only Linux, is violating the terms of the GNU General Public License, and hence, they are breaking the law.


      Can you say, "class action lawsuit"? Maybe Linux developers will finally get some money for their work! :^)

      --


      I don't care if it's 90,000 hectares. That lake was not my doing.
    87. Re:The scary thing by tomhudson · · Score: 4, Informative
      A search of the Copyright Office here shows that the only 2 patents that have ever been assigned from Novell (who, last time we all looked, owned the copyrights to the code in question): Corel (1996) and Volera (2001), so the title of the article here is EXTREMELY misleading (so what's new - this is slashdot :-)

      So, what they are doing is just more fud.

      They've not been assigned anything yet, so don't get your knickers in a twist!

      Even if they eventually get the copyright for SysV code, it doesn't matter (see my prior post on this).

    88. Re:The scary thing by Jeremi · · Score: 1
      To most people, if it isn't on the Web site, it doesn't exist.


      I don't know about you, but my web browser follows FTP links just fine. FTP sites are effectively part of the web.

      --


      I don't care if it's 90,000 hectares. That lake was not my doing.
    89. Re:The scary thing by Anonymous Coward · · Score: 0
      Pretty stupid insurance considering that by purchasing it the business purchasing it acknowledges they received Linux in violation of the GPL...

      This is simply another flaw in the GPL then, if the customers instantly have a COMPLETELY illegal copy of Linux, instead of just a partially illegal one. And it very well probably is, since I don't believe the GPL even addresses post-distribution illegalities whatsoever at all.

    90. Re:The scary thing by jedidiah · · Score: 5, Insightful

      No they can't.

      A binary only Linux license is SOFTWARE PIRACY. There's really no other word for it. SCO doesn't own the entire Linux kernel so they can't authorize people to use the other parts of it. Only the original copyright holders can do that.

      SCO is effectively claiming that the rules only apply to everyone else. Apply the rules in SCO's favor and you have to also apply them against SCO as well.

      It's time for all the kernel programmers to register their own copyrights and let SCO be on the hook for 150K * N for every license of Linux they sell.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    91. Re:The scary thing by Anonymous Coward · · Score: 0

      man... garcia has been spreading shit for a while... throw him on your "foes" list and ignore his ass...

    92. Re:The scary thing by cmdr_beeftaco · · Score: 1

      SCO licensing fee is $3.99 per CPU per year. It is only payable by a paypal donation box to be posted on their site at the end of the week.
      This is going to make the chick who paid off $20,000 worth of credit card debt via donation look like a small timer.

    93. Re:The scary thing by gilesjuk · · Score: 1

      Hundreds of thousands?

      How did they manage to document such a large amount of lines?

      Automated tools me thinks, which does beg the question did they verify every single line?

    94. Re:The scary thing by E_elven · · Score: 2, Funny

      >No, that's stupid. I keep hearing this over and over. That was the Santa Cruz Operation, not the new SCO. The new SCO has never released a version of linux, period.

      So, say, if all of Boeing's 747's suddenly exploded while in mid-air due to a gross manufacturing neglect (e.g. using crazy glue for the wings), they can go get their name changed to Boing and not worry about litigation?

      --
      Marxist evolution is just N generations away!
    95. Re:The scary thing by Anonymous Coward · · Score: 0
      The burden of proof lies on SCO, not on the Linux community.

      Not in the context he was talking about, which was if IBM/Linux wanted to question the legality of SCO new Unix copyright.

      Read carefully, before forming an opinion, much less hitting the 'submit' button.

    96. Re:The scary thing by Anonymous Coward · · Score: 0

      They applied for a copyright and were given it. That means that ALL SysV code is owned by them.

      That first sentence is probably incorrect in a way that is relevant to this discussion. My understand, although I could easily be wrong, is that they asked for clarification on who is the registered holder of the copyrights in question. The US Government has stated that SCO is the current holder of those copyrights.

      They didn't just apply to register the copyrights on all of SysV for the first time. That would be quite ridiculous.

    97. Re:The scary thing by Trigun · · Score: 1

      Even better, they are still providing the source for said kernel, in ftp://ftp.sco.com/pub/updates/OpenLinux/3.1.1/Serv er/current/SRPMS

      Last kernel listed is linux-2.4.13-21S.src.rpm. Can we consider this one clean?
      Get out the changelogs!

    98. Re:The scary thing by number6x · · Score: 1

      Just because a certain piece code is in SysV UNIX does not mean that SCO owns the copyright to that piece of code. Even if SCO owns the copyright to SysV code! Huh?

      SysV Unix is full of code that is copyrighted by Berkely Systems. This code is in Unix it is in Linux, and it is in Windows.

      Just because there are lines of code that match in Linux and in SCO unixware does not mean that it is stolen from SCO. SCO will have to show the code, and the entire source history, and prove it is their code.

      If they are sucsesfull in all that (unlikely), then they will have to prove IBM committed the theft (highly unlikely). Then the worst case would be that IBM would be liable and Linux would have to replace the code. There was no intentional theft on the part of the Linux community.

    99. Re:The scary thing by hedley · · Score: 1


      Think of nVidias n'000 simulation farm. Imagine the cost of those seats. Or Transmeta. Dreamworks. Etc. I sure hope the IT managers there play dumb, find some way to link payment only when there are no legal encumbrances (I.e. IBM not prevailing in a court case).

      Hedley

    100. Re:The scary thing by Jeremi · · Score: 2, Interesting
      If Linux is using SysV code (which apparently it is)


      Care to back this claim up? It was my understanding that Linux was coded from scratch, and contains no SysV code.

      --


      I don't care if it's 90,000 hectares. That lake was not my doing.
    101. Re:The scary thing by Bilbo · · Score: 3, Informative
      > Paying the fee actually opens companies to liability from Linux developers. Because now they have received a copy of Linux code in violation of the GPL

      Looking at the GPL, it sounds like the end users are still safe, unless they try to pass it along and make their customers pay. The GPL states that, even if the software is distributed in violation of the GPL, the software itself remains free, and the end users regain all of the rights the original author put on the software. The only one guilty of violating the contract is the distributor (in this case, SCO) who violated the terms. So, this will open SCO to being liable for distributing software that they do not have rights to, but it still protects the end users.

      --
      Your Servant, B. Baggins
    102. Re:The scary thing by andreMA · · Score: 2, Interesting
      ...the src rpm they have there no longer contains any actual source...
      If true, it would seem then that now is the time for every other contributor to kernel development to send DMCA cease and desist orders to both SCO and their upstream bandwidth provider, since SCO no longer has any right to distribute anything else in the kernel?

      I don't know if they would win, but there's enough of a case that the C/D order could not be considered frivolous or an abuse of process...?

    103. Re:The scary thing by Surak · · Score: 1

      Paragraph 7 is not an out. If you can't distribute under the GPL, you can't distribute at all. Which means that they can't distribute Linux in ANY FORM.

    104. Re:The scary thing by UberWolf · · Score: 2, Informative

      The biggest problem with the Kernel guys redoing it, is now they can be considered 'tainted'

      That's not true.

      Remember: this is not a PATENT issue, but a COPYRIGHT issue. Copyright protects only the actual "creative work," not the ideas it contains. Otherwise it would be illegal for newspapers publish film or book reviews, as they give away ideas contained in the movie or novel.

    105. Re:The scary thing by rsilvergun · · Score: 1

      Presumably, the way around the gpl is to not release a distro themselves, and not attempt to lincense the code to other distributers. Instead, they go to end users and demand lincense fees. As long as noone's distributing, SCO can lincense any code they want for inclusion in the kernel.

      But from what I'm reading here that doesn't seem to be what they're doing. The cannot release a binary only version of linux, of course. I'm sure if they really are trying (I find it a little hard to belived they'd do something so dumb, but then again these people are nuts) Linus and crew will take them to task over this, probably with help from IBM.

      --
      Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
    106. Re:The scary thing by samantha · · Score: 1

      If you believe copyrights allow this then that is indeed "krap". There is no code in question that has not been commonly available and open for quite a long time now and extensively used and modified. To say that some ancient proprietary rights over some ancinent original code should now at this late date force Linux to go non-open source and force all Linux users to obtain a license is legally absurd. Morally it is MUCH worse than that.

      If this is supported by the courts and SCO "wins" then I become a criminal. Under bad law honest citizens become law-breakers. This is the reality.

    107. Re:The scary thing by Anonymous Coward · · Score: 0

      "First we're going to cut [SCO] off, then we're going to kill it" -- Colin Powell

    108. Re:The scary thing by unoengborg · · Score: 1

      It seams that they have stopped distributing the kernel. At least I could not find it on their ftp site. However it was there just a couple of days ago.

      --
      God is REAL! Unless explicitly declared INTEGER
    109. Re:The scary thing by jedidiah · · Score: 2, Insightful

      The only problem with that is that FTP sites are indistinguishable to the average drooling Win32 using idiot when viewed with Internet Exploder. FTP hasn't been user hostile or arcane since the advent of GUI web browsers and individual ftp files are typically available through "the main website".

      A judge might not be computer literate enough to grok the difference between http and ftp yet not computer illiterate enough to be bamboozled into believing that there is some sort of meaningful difference.

      A judge isn't just going to believe everything a SCO lawyer tells him. Plus, there will be plenty of IBM lawyers to contradict anything that a SCO lawyer might say.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    110. Re:The scary thing by mav[LAG] · · Score: 1

      That's a pretty flaky clause.

      Not true - it has the full weight of copyright law behind it. Don't want to abide by the GPL when redistributing this software? Bummer - it's copyrighted and you're now illegally redistributing someone else's copyrighted work.

      --
      --- Hot Shot City is particularly good.
    111. Re:The scary thing by Anonymous Coward · · Score: 0

      In fact, if they actually make anyone pay to run linux, then they can be sued by the contributor of every other piece of code for copyright violation. After all, they distributed the rest of the code without a valid license to do so.

      SCO really should have just kept their mouth shut on this one. The best they could have hoped for with the lawsuit was to destroy the ability to use Linux. Then, they could try to sell Unixware to people (though we all know that people would just switch to BSD before Unixware). Only an idiot would bring up a concept of licensing Linux. Significant portions of the kernel were written by people independent of kernel development. SCO will never have a right to relicense these contributions.

    112. Re:The scary thing by jedidiah · · Score: 1

      Nevermind the GPL.

      If you distribute ANY copyrighted work in a manner that has not been agreed to by the "owner" of the work, you are commiting an act of software piracy. If you sell this distributed work, you are commiting a felony even under the 1976 version of the copyright act.

      SCO is now on the same level as the guy that sells pirated CD's on the local street corner or flea market.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    113. Re:The scary thing by Anonymous Coward · · Score: 0

      >Plus, there will be plenty of IBM lawyers to contradict anything that a SCO lawyer might say.

      The entire argument is so convoluted that I really doubt IBM will bother to bring it up. It's nothing more than slashdot parlor game.

    114. Re:The scary thing by gl4ss · · Score: 1

      *Ford can not sue Chevy for designing 'a car'*

      actually, just to make you lose any hope on patent office and things as such, there was a fellow who patented a car like thingy in the late 1800's, the fellow even delayed it in the process(like companies do nowadays) until cars got into widespread production, and then licensed it to several manufacturers.

      the fellow had not built a working car from the description in the patent even, and later lost in court to ford after failing to produce an usable car from the description in the patent(iirc court demanded it, the patent was very vague with details but nobody had bothered to go to court with the fellow and had instead paid quite nice sums and the fellow in question wasn't even an engineer but a patent official iirc).

      ok so what this has to do with sco? not much except that companies are too reluctant to go to court and will even pay quite considerable sums for not having to do it, even if they would quite probably won if they took even a little time to investigate the issue.

      i'm just amazed if some people really buy sco cash thinking sco has a viable business plan in 'licensing linux 2.4', big f***n boohoo, move back to 2.2 and start over EVEN if those few lines are never told because of some craziness and if they claim they are in 2.6 too, and why don't they just go after the fellow that submitted that code? surely such info would be available from the docs/tracking.

      also why don't they sue anyone else than ibm? how many employees does sco even have?

      and they really can't do it by the books by some twisted binary only licensing of linux without losing all rights to distribute it anyways..

      --
      world was created 5 seconds before this post as it is.
    115. Re:The scary thing by crazyphilman · · Score: 2, Insightful

      I've seen people quoting a price of $1500.00 for UnixWare, which I'm guessing is a single-machine license. Also, SCO says they're looking for $149 for small users, like noncommercial users (that's you and me). I'm not going to be buying anything from them. I'd rather switch to FreeBSD and give them the finger, than send so much as one red cent their way.

      Having said that, I'm going to be using Slackware on my main machine until I absolutely have to give it up. But, then, I'm not using any features that have been listed as potentially infringing, so I don't think I'm even involved in this; I'm not using SMP at all, for instance.

      --
      Farewell! It's been a fine buncha years!
    116. Re:The scary thing by jedidiah · · Score: 1

      Do you have permission to enter Wal-Mart in the middle of the day when the doors are open and someone greets you with a smile?

      There are standard "welcome" practices for FTP. There is also a standard guest password. There is also a banner that the FTP server will give you. If you enter in the normal way, and there are no signs indicating that you are tresspassing, then you are acting reasonably.

      If walmart doesn't take product down off the shelf that it doesn't want to part with, it can't then attempt to call you a thief when you go buy it.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    117. Re:The scary thing by Trigun · · Score: 1

      No, it's a FUD issue. It was an IP issue, then a trade secret issue, and now a copyright issue. And if the kernel guys remove all the offending code, and therefore the issues, then SCO will have to come up with some other way to make money. I just hope they're not reading my comments, and turn it back into an IP issue.

      And if they are: Darl, in my opinion, the only thing good enough for you is to be skullfucked by a pilot whale in January.

    118. Re:The scary thing by jedidiah · · Score: 1

      Publishing and selling someone else's copyrighted work without permission is a federal FELONY under US Law.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    119. Re:The scary thing by cdrudge · · Score: 1

      I don't see the kernel rpms there. I thought the same thing that you did earlier, but I couldn't find the actual kernel source.

    120. Re:The scary thing by Anonymous Coward · · Score: 0

      making more of their case known in mid-August

      Which means they might say something meaningful. For once. So far they have done none, zilch, zero, null, nothing, nada of the sort

    121. Re:The scary thing by Anonymous Coward · · Score: 0

      The GPL License is only a person to person contract, it is NOT A LAW. Hence you can not break the law by breaking the "contract". Also if the GPL License, as a contract, is invalid or uninforcable then it can't even be broken. I guess time will tell.

    122. Re:The scary thing by jedidiah · · Score: 1

      The level of misinformation on this site is frightening.

      Commercial piracy is and always has been a FELONY. It is not uncommon for the FBI to raid such ventures. It is only the Napster style piracy that is not necessarily criminal.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    123. Re:The scary thing by dbrutus · · Score: 1

      They may or may not be doing this legally. If they're talking about 80 lines out of hundreds of thousands, even if they didn't get into AT&T and Linux via a BSD heritage, this is a small enough proportion to be declared fair use and $0 being owed. Fair use is a tricky thing because what's fair isn't subject to iron clad rulings.

      Remember, copyright isn't property but a legal privilege of monopoly in certain circumstances with certain rights to copy being held outside of the restrictive privilege.

      *If* there was copying, *if* the copy was actually from Sys V and not from BSD or other source, *if* the copyright is enforceable, *if* the copying is sufficiently broad to not be fair use, then Linus may have to back out some kernel code and remake it.

      There are four legal conditions that have to be satisfied. SCO has not satisfied any of them in a court of law. Until they do, you can't say that they are acting legally.

      They could be engaging in libel, slander, extortion and abuse of process on the part of SCO and ethics violations requiring disbarment on the part of SCO's legal team. We don't know the actual facts of the matter which is why we're going to have a trial and investigate what's going on.

      Copyright law may or may not be crap but judging the facts of a case out of court, before discovery, absolutely *is* crap.

    124. Re:The scary thing by panxerox · · Score: 1

      Damn, I was hoping to use linux one day.

      --
      "It's so convenient to have a system where everyone is a criminal" - A. Hitler
    125. Re:The scary thing by Anonymous Coward · · Score: 0

      No, they are breaking the law!

      They have obviously not accepted the GPL (since they aren't handing out the source code to anybody who has binaries), so they bound by copyright law instead.

      I SCO is actually distibuting a binary only copy of linux, SCO is stealing the work of others, selling it, and not giving any credit where it is due.

    126. Re:The scary thing by Gverig · · Score: 1

      I don't think this all the an issue for SCO. The problem is that they claim that Linux itself is illegal. Which means that don't give a rat's ass about licenses Linux is distributed under. What they say is this: "You do not have right to use Linux. Period. BUT, if you pay us we will allow you to run binary distribution of Linux". Yes indeed, they have the rights for code, so if you can get Linux and strip out all code that SCO claims you can use Linux however you want (which is impossible as they don't tell WHAT code they own). But if you do not strip code out you have to either stop using Linux or follow SCO rules (that is, of course, if you deside to admit that SCO has such rights).

    127. Re:The scary thing by andrewski · · Score: 1

      Shit, as long as they include the sources on CD they are abiding by the GPL. Somebody'll have to pay for 'em, but then they can be distributed as seen fit to the community. Nothing in the GPL says that you have to make sources available. Only by distributing binaries derived from GPL's code do you have to make the sources available, and then only to the purchasers. They can do whatever the heck they want with that code, though.

    128. Re:The scary thing by Darth_Burrito · · Score: 1

      Heh perhaps a better question is how did they manage to miss an infringement of this magnitude as long as they did while distributing their linux.

    129. Re:The scary thing by unoengborg · · Score: 1

      Well, perhaps they could distribute a mini version of Linux containing the 80 lines or so of code that may belong to them. Of course they could not call it Linux as that tradmark is already taken.

      --
      God is REAL! Unless explicitly declared INTEGER
    130. Re:The scary thing by jmpnz · · Score: 1

      They are not only distributing the kernel, but also the source W I T H the gpl! This very day. I apperciate the consistancy.

    131. Re:The scary thing by dbrutus · · Score: 2, Interesting

      They only have 13.1M shares outstanding and they're only selling at $11 a share. So you need 6.6M shares to stop the insanity by shareholder vote. If they win in court, they get bought out, it's that simple.

    132. Re:The scary thing by Anonymous Coward · · Score: 0

      If Linux is using SysV code (which apparently it is) then they can enforce licensing of that.

      Others have commented on your use of "apparently". I just wanted to add that in any case, SCO does not own the copyrights to all of the Linux kernel, which has always been under the GPL. So if they are licensing it in any way, it has to be under the GPL. Otherwise they are committing copyright infringement (or in their own terminology, theft) and are going to be sued by pretty much everyone who owns copyrights to even one line of the Linux kernel. That includes IBM, HP, the FSF, many other companies and organizations, and countless individuals.

    133. Re:The scary thing by Anonymous Coward · · Score: 0
      Yep. Downloaded it just to make sure...

      Possibly a mistake. These guys are going out of their way to make trouble, hope you spoofed your address.

    134. Re:The scary thing by Darth_Burrito · · Score: 1

      That's the way I interpretted it, but I couldn't find any other section that he could have been referencing. It's likely he is trying to twist it to his purposes. Maybe his logic goes something like this, under the terms of the GPL we did not have the write to distribute this proprietary stuff, ergo, any gpl licenses distributed as such by us are invalid.

      Of course, since it was their code they did have the right to distribute it, but I guess that's where the federal provision against accidental giving away of copyright thing he sited steps in.

    135. Re:The scary thing by MikeD83 · · Score: 1

      It doesn't matter if they distribute a binary kernel via their FTP site. To keep in accordance with the GPL they must also offer the source code for free on that FTP site.

    136. Re:The scary thing by Anonymous Coward · · Score: 0

      It's funny how it's always assumed around here that the GPL is going to win out over every other legal document even though it's never been tested in court.

      If Linus wants to defend the GPL in this matter, he'll have to go to court like everybody else and take his chances.

    137. Re:The scary thing by dougmc · · Score: 4, Insightful
      There could have been several resolutions to this case, but SCO has essentially blockaded all avenues of compromise.
      Of course they have. Compromise does not make them money.
      I could see them saying that the kernel hackers can't recode the kernel because they have seen SCO's version and will obviously infringe on it.
      Unfortunately, the SCO board of director's primary responsibility is to the stock holders, not to the *nix community and not to anybody else. The company doesn't appear to be making any money selling their products, so perhaps they can make some by extorting it from Linux users.

      If they told people where the `infringing' code was, it would be removed and they'd lose any possible case that they have. They know this, so that's why they won't tell anybody.

    138. Re:The scary thing by Anonymous Coward · · Score: 0

      linux-source-i386-2.4.13-15S.i386.rpm 7/29/2002 12:00:00 AM
      linux-source-i386-2.4.13-19S.i386.rpm 10/28/2002 12:00:00 AM
      linux-source-i386-2.4.13-20S.i386.rpm 2/14/2003 10:58:00 PM
      linux-source-i386-2.4.13-21S.i386.rpm 5/9/2003 5:51:00 PM

      Plain as day. For having their panties in such a twist you would think they would not continue distributing the 'infringining' source code. Geez.

    139. Re:The scary thing by jedidiah · · Score: 1

      He's confusing copyrights and patents. Only patents allow you to prevent others from re-implementing a work. Copyrights simply don't give you that power.

      Anything else is muddy since the Unix family tree is an ancient knarled thing with branches splitting and merging with each other all over the place.

      Some hillbilly jokes come to mind...

      --
      A Pirate and a Puritan look the same on a balance sheet.
    140. Re:The scary thing by Anonymous Coward · · Score: 0

      They would not be in "breach of contract"; they have no contract with the kernel developers. They would be violating copyright law by distributing *without* a contract.

    141. Re:The scary thing by PetiePooo · · Score: 1

      I can only hope to have a chance to soon view a press conference where IBM announces its takeover of SCO, and fires everyone who still "works" there. The only bad thing about this is how much money McBride will make on the deal.

      I'd much rather watch the press conference where IBM picks up the pithy remains of SCO for a song and dance after they go bankrupt!

    142. Re:The scary thing by jedidiah · · Score: 1

      Expensive litigation that you could LOSE doesn't make money either.

      This is a basic principle of the ambulance chaser and similar professions.

      Being a total *ss also doens't tend to win over judges, jurors or arbitrators.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    143. Re:The scary thing by Entropius · · Score: 1

      Suppose I run a store with two doors separated by 50m. A sign is posted on one door saying "Buying from this store is illegal, and we will take you to court if you attempt to purchase from us." The other door has no such sign.

      Is a customer who walks through the other door, buys a widget, and walks out liable? Of course not.

      Likewise, SCO, by running a public ftp server with the kernel, is offering that kernel to everyone who asks. Is it now illegal to ask a ftp server for a file (which it will gladly send you if you ask) before making sure that their entire webpage doesn't ask you not to use it?

    144. Re:The scary thing by lorax · · Score: 1

      look for it under the name linux-source-common-2.4....

      also, linux-source-i386-2.4... and a bunch of other architectures as well.

    145. Re:The scary thing by leachj · · Score: 1

      The most recent kernel version that I see there is 2.4.13 though. IBM is claimed to have released the code with in 18 months of when this whole stuff started. I don't have a release date for 2.4.13, but the changelog for it on ftp.kernel.org has a date stamp of 10/24/2001. Could it be that the kernel that SCO is distributing doesn't have the questioned code? Wouldn't that shot a hole in the "they released it under the GPL" argument?

    146. Re:The scary thing by mcrbids · · Score: 1

      That isnt how copyright works, even in copyrights current fucked up state.

      The copyright is not particularly screwed up, except for the duration of copyrights. Other than the fact that a copyright can always outlive you, I think the current system of copyrights to be quite effective and sane.

      What's really messed up is the Patent system.

      --
      I have no problem with your religion until you decide it's reason to deprive others of the truth.
    147. Re:The scary thing by syn3rg · · Score: 0

      Try this URL. looks like source to me.
      ftp://ftp.sco.com/pub/updates/OpenLinux/3.1.1/Work station/current/SRPMS/

      --
      The contents of this message have been doubly encrypted by ROT13
    148. Re:The scary thing by MrGrendel · · Score: 1

      It is still there.

    149. Re:The scary thing by jedidiah · · Score: 1

      The burden of proof against SCO in such a case would be trivial to meet. This would quickly devolve into a situation where SCO would have to demonstrate it's ownership rights in Linux.

      The opposing burden of proof in a civil case is only "more likely than not". Also, you only have to convince a majority of 9 jurors rather than unanimous agreement of 12.

      After the jury is shown 8 year old Linux CD's from the Library of Congress, they may have a problem with the idea that SCO owns anything in Linux.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    150. Re:The scary thing by rnturn · · Score: 3, Informative
      ``I could see them saying that the kernel hackers can't recode the kernel because they have seen SCO's version and will obviously infringe on it.''

      As someone has already stated, they cannot claim that a rewrite of the kernel would be tainted. They have been given a copyright for the SVR4 code which covers the expression of a concept not the concept itself. So what if someone were to rewrite the sections of the Linux kernel that SCO claims are copied from SVR4? Take two kernel programmers. One writes an spec of the functionality of the code in question. S/he hands it off to the second programmer who implements new code based on that spec. Hell, have a laywer from the FSF at the second programmer's side when it's written and stamp it with an FSF copyright notice as soon as the last semicolon is entered. Since they've been granted a copyright and not a patent, SCO cannot protest that.

      Personally, I do not see how SCO can pull this off anyway. They have refused to point out where the alleged copyright violation has taken place -- making it impossible for kernel developers to make the kernel code non-infringing -- and have yet to prove that they are the authors of the code in question (what if they were just granted a copyright on code that can be demonstrated to have originated in BSD Unix?). IBM or someone else with the legal fees available ought to be able to fight this with one hand tied behind their back. A judge should find it easy to force SCO to divulge exactly what lines are in dispute and require SCO to prove that they own those lines. I can claim all day long that some code belongs to me and attempt to charge a license fee for its use. Trouble is that I'd have to prove ownership. I don't think SCO has really done that. I think this would be similar to a company pushing a patent through the process in the face of tons of prior art and then suing everyone in sight. That wouldn't be allowed to go on for long. (Or would it? This is the US legal system after all.) Getting the BSD v.ATT results opened up should go a long way to resolving this dispute. This hasn't seen minute one of real court time yet SCO's acting as though they've already beaten IBM in court. Upon losing the case, SCO would likely wind up having to refund the license fees anyway. That is, if they have any assets left.

      Heck, this is pure stock pump-up and nothing more (SCOX's stock price went up today and volumes are more than double the normal.) They hadn't released any new FUD in several weeks. Guess it was time.

      Hey! Who's for getting some high profile advocates to claim that SCO has pirated BSD code? If they can spread FUD, why can't the open source community? Think SCO can take on a multi-front legal defense while they're on a FUD offensive?

      (caveat: IANAL and all that)

      --
      CUR ALLOC 20195.....5804M
    151. Re:The scary thing by Xerithane · · Score: 1

      Commercial piracy is and always has been a FELONY. It is not uncommon for the FBI to raid such ventures. It is only the Napster style piracy that is not necessarily criminal.

      I'm not sure which instance you are actually talking about. Only if there was intent will there be a felony hearing for copyright infringement. I think it is very obvious there was no mal intent on behalf of SCO and it's distribution of Linux.

      This is why it would be a civil matter, to be disputed using contract law (and not copyright infringement, on action against SCO, contrary to their case which is copyright infringement.) Since SCO had authority to release and distribute software under the provisions granted by the GPL, there is no commercial piracy. By failing to release under the provisions of the agreed license (contract), it becomes a civil dispute between the interested parties. It would be a very hard push to try to get a felony judgement against SCO.

      --
      Dacels Jewelers can't be trusted.
    152. Re:The scary thing by jedidiah · · Score: 1

      The only problem with this is that they can then only sell ONE of those. The can only sell ONE of those because after the first one is purchased, then the rest of the world can use it.

      Obviously, SCO is not going to structure their distribution like this.

      SCO's business model depends on being able to sue the rest of us for software piracy. Otherwise, it will fall apart much in the same way that Free Software detractors often point out.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    153. Re:The scary thing by cdrudge · · Score: 1

      I'm an idiot. I just took a glance and thought that I was in the same tree that I was looking at earlier. Those trees had the actual source RPMs and the linux source was not one of them.

    154. Re:The scary thing by JWW · · Score: 1

      Fine, but SCO is trying to charge people for code someone else distributed under the GPL for free.

      Double Dastardly....

    155. Re:The scary thing by thisgooroo · · Score: 1
      guys, please don't panic. SCO so far only claims that they own code that is in the kernel. whether this claim is correct is still to be proven.

      based on statements they made a few weeks ago it seems that their position is that anything tha ever got added to a systemY system is theirs, rgardless of who added it, and i suspect that their claim on ownership of linux kernel code is based on that. this is such a preposterous claim that it is unlikely that they can get away with it. since they are basing their action on copyright claims, they can't get away with not revealing the allegedly offending code, since copyrighted material can't be a trade secret.

      and remember: the same argument (massive copuright infringement) with the same "proofs" (identical comments, variable names, etc) was made by USL against BSD, and we all know how that turned out

    156. Re:The scary thing by schon · · Score: 1

      Do you have permission from SCO to use their FTP servers?

      Yes. Why wouldn't I? Do you have "permission" from /. to post your drivel?

      Here is what is says on their official website:

      And WHAT DOES IT SAY ON THEIR FTP SERVER?

      The sale of this SCO Linux product to new customers is currently suspended

      I'm not buying SCO Linux - they don't charge for access to their FTP server, you know.

    157. Re:The scary thing by rnturn · · Score: 1
      ``They could throw out some nice, Judge-convincing BS like "We only made these files available via the 'FTP' program, which is only for highly advanced technical individuals such as corporate IT managers, for the convenience of our paying customers. It was not intended for download by unlicensed individuals, and in fact doing so constitutes hacking as per the terms of the DMCA..." And the Judge would buy it hook, line and sinker, since it rings true of the Good Ol' American style of corporate IP-speak.''

      Anyone accused of a DMCA violation for downloading code from an unprotected server could find in a second a couple of ways that SCO would have been able to distribute this code to these technically advanced individuals via FTP. Software companies have been doing this for years to distribute updates and patches to clients who pay for that service. I don't think a judge would find it hard to agree that these few simple measures could have and should have been taken by SCO. I doubt seriously that the DMCA violation charge could be used by a company too incompetent to protect their FTP servers.

      --
      CUR ALLOC 20195.....5804M
    158. Re:The scary thing by thisgooroo · · Score: 1

      damnit. they claim to own the code. since *their* code is copyrighted, there is no point in not revealing what the allegedly offending code is. so far they haven't done it, and until they do and their claim id checked, their is no reason to belive them

    159. Re:The scary thing by kasperd · · Score: 1

      Well, hopefully the smart guys on the Kernel team are thinking about this already

      They have thought about it as much as they can possibly do not knowing what it is all about. As long as SCO will not tell what it is all about, there is nothing to be done. For all we know it might be just hot air and nothing else.

      --

      Do you care about the security of your wireless mouse?
    160. Re:The scary thing by alatesystems · · Score: 1
      I wish I had mod points to mod up your reply to me because I literally just laughed out loud at work. I think it was mainly the "boing". However, they didn't CHANGE their name, they BOUGHT another company.

      Ok, I'll play the analogy game too:
      Let's say your mom(linux) had the best fudge recipe in the whole world and no one knew that she stole part of the recipe from Chef(unix puchased by sco). Then she released that recipe to the world on the internet. Next Chef purchased all rights to a company that was selling a version of your mom's free recipe because he loved it too. If Chef finds out then that part of it was stolen from him, mom can't simply say, "Ha ha, you bought me and I had already released it as open, so your recipe is open."

      I realize all of that was stupid but so was yours. However, yours was funny.

      Everybody knows wookies don't live on Endor, you must acquit.

      Chris Benard
      www.talkingtoad.com

    161. Re:The scary thing by MrResistor · · Score: 1

      I'm not going to be buying anything from them. I'd rather switch to FreeBSD and give them the finger, than send so much as one red cent their way

      According to statements made by SCO execs in the recent past, switching to FreeBSD would not save you.

      That said, I won't be buying anything from SCO, since they've made it clear that the only thing they think a contract is using it "as a weapon". I'd have to be a complete idiot to enter into a contract with someone who thinks that way.

      --
      Under capitalism man exploits man. Under communism it's the other way around.
    162. Re:The scary thing by hawkeyeMI · · Score: 1
      --
      Error 404 - Sig Not Found
    163. Re:The scary thing by thisgooroo · · Score: 1
      the same claim was made by USL (AT&T/Novell) when they sued BSD. they also made the same arguments (identical comments, etc). they didn;t get anywhere then. Dennis Ritchie has a couple of court documents on that case onh his home page. afair the court ruled then that the proofs they supplied were insufficient.

      there are some (confirmed?) rumors that much of the duplicated code was lifted by USL out of BSD, with BSD copyrights removed and replace by USL copyrights

    164. Re:The scary thing by BJH · · Score: 1

      No, someone was shown two pieces of similar code with no way to verfiy the origin of either.

      Next objection?

    165. Re:The scary thing by kasperd · · Score: 1

      They obviously believe that they can defeat the GPL in court.

      That might be good news. AFAIK the GPL has never been taken to court before. In this case it looks very much like SCO is going to loose big time, if it really is taken to court. This could give the GPL some good precedence, much better than if the first case taken to court was one where the use of GPL was dubious.

      --

      Do you care about the security of your wireless mouse?
    166. Re:The scary thing by t · · Score: 1

      That could be BSD or older code. The only thing possibly apparent is that there is some similar code. There is nothing apparent about the origins of the code.

    167. Re:The scary thing by Anonymous Coward · · Score: 0

      > Copyrights are very specific. Linux is NOT SysV in any way/shape/form. Linux was made from scratch.

      This is true. In fact, copyright only covers expression, not ideas. That is what patents are for and patents, thankfully are still short.

      This was decided a long time ago in a court case involving a guy who invented an accounting system and published a book explaining the system and containing forms for using it. A few years later, another guy read the book, decided the system was cool, and then wrote his own book and forms describing the exact same system. He was sued for copyright violation, but it was decided that copyrights can cover only expression and not ideas and since the new guy described the same system using different words, he was not in violation of the original copyright.

      So, technically, should SCO copyrighted code be found in Linux, it should be incredibly simple to rewrite the portions of the kernel that contain such code. The code can even be functionally equivalent, so long as it is 'expressed' differently. You cannot copyright a process. In fact, simply renaming the variables might be enough to avoid infringement assuming SCO owns no patents covering the process, or any patents have expired.

    168. Re:The scary thing by kasperd · · Score: 1

      Who is going to take them to court to fight it? Nobody. However, this issue will be pressed by the IBM law team, and quite probably will have a favorable outcome on this point.

      Anybody who owns copyright for parts of the kernel can take infrigers to court. It can turn out to be convenient that IBM actually owns the copyright for parts of the Linux kernel.

      --

      Do you care about the security of your wireless mouse?
    169. Re:The scary thing by Anonymous Coward · · Score: 0

      The problem is that you can only sue for copyright infringement when such infringement inflicts damage upon your copyright. Since Linux is free, no fiscal damage is inflicted upon the liscense, so the most you could ask for is a cease and desist order, which in all likelyhood, the court would not award because the poor saps on the receiving end paid for what should have been a free liscense.

      IP law in America is not prepared to handle free things.

    170. Re:The scary thing by Trailer+Trash · · Score: 1

      It's not a breach of contract, as the GPL isn't a contract. The GPL is simply a listing of your limited rights to redistribute a copyrighted work. If you don't wish to abide by the conditions, then you have no right (the position that SCO's in), and hence it's a simple copyright violation.

      If Linus cared to pull his head out of his ass, he could own SCO simply because the only way that they'd have to pay the statutory damages ($150K/violation) would be to give him the company.

    171. Re:The scary thing by Dastardly · · Score: 1

      This is simply another flaw in the GPL then, if the customers instantly have a COMPLETELY illegal copy of Linux, instead of just a partially illegal one. And it very well probably is, since I don't believe the GPL even addresses post-distribution illegalities whatsoever at all.

      Well, the GPL is the license the developer's chose. The flaw I guess is that in order for to avoid the situation every developer would ave to agree to the change. It is easier for proprietary licenses because you have only one developer that can make changes to the licensing term if somethign came up. I guess the BSD license doesn't have this problem, but if BSD were tainted not even the developers could use, develop, or distribute without paying some one else, whicj would pretty much suck.

      Dastardly

    172. Re:The scary thing by hawkeyeMI · · Score: 1

      I got a copy of 2.4.19 (as linked above) just now. I'm pretty sure that's new enough. Man am I ever sick of this crap.

      --
      Error 404 - Sig Not Found
    173. Re:The scary thing by thisgooroo · · Score: 1
      Just because slashdot found a back door or hacked into their FTP servers does not mean SCO is still legally distributing it, especially not intentially.

      has everybody gone crazy today? first this apparently unquestioning acceptance of SCO's claim that they do own code in the linux kernel, and now the preposterous statement that accessing an open ftp server with anonymous login is hacking into their ftp server? it seems SCO has ,managed do make a few brains disfunctional

    174. Re:The scary thing by Surak · · Score: 1

      Accidental giving away of copyright is NOT protected once you know about it. If you know about it, and knowingly continue to distribute the code, you are failing to mitigate your own damages, and more, you're agreeing to the terms of the GPL implicitly.

      Sorry, but it just doesn't work if they are STILL distributing GPL code, well after they became aware of the problems.

    175. Re:The scary thing by Dastardly · · Score: 1

      Fine, but SCO is trying to charge people for code someone else distributed under the GPL for free.

      Right, and as I stated in other posts their license scheme can't work. There are only two choices for SCO (assuming their code is in Linux) and neither choice involves getting license fees for LInux.

      1) License their code in Linux under the GPL.
      2) Sue everyone for copyright infringement and enjoint he usage of Linux with their code by anyone.

      They cannot license their code in Linux under a different license other than the GPL. Otherwise, all the other code in Linux becomes unlicensed, and no one has the right to use or distribute said code.

      IANAL
      Dastardly

    176. Re:The scary thing by WNight · · Score: 2, Insightful

      Perhaps it should say "Therefore, by modifying or distributing [...] you indicate your acceptance of this License [or that your actions violate copyright law]"

      That might make it clear enough for people like you.

      The GPL is doing you a favor by assuming that your otherwise unauthorized distribuition of the copyrighted file is done so in accordance with the GPL. Otherwise, you're liable for damages of up to $150k per file, per copy. You can claim that you didn't agree to the GPL when distributing the file, and everyone will accept it, but then the issue is why you knowingly violated its copyright.

      The GPL is incredibly secure, in that you can only accept it if you implicitly agree that it's valid. If you don't agree, you don't accept it, and you have no extra rights at all.

      So, is SCO violating the provable copyrights of all of the contributors of original work, or they agreed to the GPL. Which is it? Even if they could prove (hah) that they own some of the code in the kernel, unless they own Linus's original work from university, they're violating his copyright by distributing it.

    177. Re:The scary thing by Error27 · · Score: 1

      If RedHat paid SCO they would be liable for copyright violation to every copyright owner of the kernel. That includes most hardware companies, the FSF, and hundreds of individuals...

      An individual user could pay SCO some cash and not be liable, so long as they don't redistribute the kernel.

    178. Re:The scary thing by johnnyb · · Score: 1

      The biggest problem with the Kernel guys redoing it, is now they can be considered 'tainted'.

      ---

      Only if they signed an NDA. Just having viewed copyrighted code does not make you tainted. In fact, they can use the concepts learned from the code to write their own versions, and it's still theirs.

    179. Re:The scary thing by Xerithane · · Score: 1

      Anybody who owns copyright for parts of the kernel can take infrigers to court.

      Yeah, but you can take anybody to court for anything. Trust me, been there :)

      It can turn out to be convenient that IBM actually owns the copyright for parts of the Linux kernel.

      IBM will have more impact by proving this (or at least disproving SCOs encumbrance claim) in the case against them. Otherwise, IBM will just be asking for damages. What can they possibly get from SCO? Perhaps sue SCO for immunity? :)

      --
      Dacels Jewelers can't be trusted.
    180. Re:The scary thing by crazyphilman · · Score: 1

      Well, whether SCO recognizes it or not, FreeBSD is unencumbered as a result of the original AT+T lawsuit. Also, if they did decide to get that stupid and attack FreeBSD, the countersuit that would almost instantly be brought would show all the places where the original AT+T code was tainted with FreeBSD code, resulting in a rather nasty public evisceration of SCO. I don't think SCO would want to open up *that* can of worms... ;)

      --
      Farewell! It's been a fine buncha years!
    181. Re:The scary thing by Arker · · Score: 1

      He talked a lot about the SMP code in the 2.4 kernel, a lot.

      And it's total bullshit. SCO has never had decent SMP code, never, not to this day. Linux had SMP before SCO implemented it, and it's always worked better, even back when it was not so good SCOs was worse. Alleging Linux copied their code for SMP, when Linux has had better SMP code and had it longer than any of the products SCO owns, is utterly ludicrous as it's flat out impossible.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    182. Re:The scary thing by da+cog · · Score: 2, Informative
      So, Linux developers can sue, and win, because by paying the fee to SCO they acknowledge that they have kowingly received Linux in violation of the GPL, and have no license to do anything with said software.

      You are wrong. The GPL does not cover use of the program, it covers modification and distribution of the program. In section 0 it is specifically stated that,

      Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program).


      No one can ever be liable for a GPL violation merely by using the software.
      --
      Snarkiness is inversely proportional to wisdom because it emphasizes feeling right rather than being right.
    183. Re:The scary thing by Archie+Steel · · Score: 1

      Why, is it illegal to download something if it's available on a ftp server? Don't they have to place their server behind a username/password combination in order to prevent unauthorized downloads?

      --

      Reminder: find a new sig
    184. Re:The scary thing by Surak · · Score: 1

      Yes, the GPL is a contract. Let's look at what we need for a contract:

      1) You have to have an offer.
      The GPL contains an offer to copy, redistribute and/or modify the code it's applied to.

      2) You have to have acceptance. Redistributing the code means that you have accepted the contract (since nothing else gives you the right to redistribute the code).

      3) You have to have intention, also referred to as a 'meeting of the minds.' You have to have intended to enter the contract. Redistributing the code under the terms of the GPL indicates that you have a meeting of the minds in and of itself. It's very difficult to prove that you didn't mean to bind yourself to the agreement. Basically, if you exercise your rights under the agreement, no court is going to say that you didn't have a meeting of the minds. It's not like SCO didn't KNOW about the GPL. We have plenty of evidence (including their own packagign) to indicate that they DO know about the GPL.

      4) You have to have consideration. The consideration here is that the GPL gives you the right to distribute the code. You, in turn, give consideration to the author to redistribute the code and/or derivative works under the same license. Consideration.

      Since we have the four elements of a contract: offer, acceptance, intention, and consdideration, guess that what that means? Yes, under the law we have a CONTRACT.

      Thankyouverymuch.

    185. Re:The scary thing by Anonymous Coward · · Score: 0

      Commercial piracy is and always has been a FELONY.

      Crap. It's been a felony for two or three hundred years at the most.

    186. Re:The scary thing by Abcd1234 · · Score: 1

      only 2 patents that have ever been assigned from Novell (who, last time we all looked, owned the copyrights to the code in question)

      Talk about mixing your terminology. The article in question is about SCO registering their Unix copyrights. This has *nothing* to do with patents. All this does is grant SCO additional rights to seek damages in copyright infringement cases (ie, they aren't required to register their copyrights with the US gov't, but unlike most other countries who've implemented the Berne Convention, the US requires such registration in order to obtain certain legal privileges).

      So, yes, they've been assigned something... it just ain't much (since they've been claiming to hold those copyrights all along).

    187. Re:The scary thing by Anonymous Coward · · Score: 0

      Be my guest. While you've got your check book out, add in my servers. I'll pay you back later.

    188. Re:The scary thing by rnturn · · Score: 1
      ``... and then finally the "re-implementation" of System V ideas.''

      McBride has about as much a chance of winning that point as he does getting to the moon by flapping his arms. Unless SCO owns patents that cover the basic concepts in Unix, they have absolutely no claim over those ideas. I have several textbooks on the shelf at home that contain detailed descriptions of the core concepts in the Unix kernel. One book specifically covers SVR4. At no time do I recall reading anything in the preface -- or anywhere else in those texts -- that prohibited me from using those ideas, algorithms, etc. in my own code.

      What McBride has, rather than a problem that falls into three buckets, is a case that stands on three legs. And, IMHO, at least two of those legs do not even exist. And the third ain't looking too sturdy either.

      --
      CUR ALLOC 20195.....5804M
    189. Re:The scary thing by acoopersmith · · Score: 1
      Linux can not possibly infringe. It was made from scratch.

      You cannot possibly know this. Thousands of people have contributed code to the Linux kernel - did you watch every single one of them to verify that they did not copy from some other source, either with or without the permission of the copyright holder? Do you have access to every single copyrighted bit of source code in the world to check against? (Of course, some of SCO's statements make it sound like Linus is guilty of gross negligence in checking code into the Linux source without performing these impossible tasks first.)

      IBM has admitted publically that it contributed code that came from other OS'es, code to which it believed it owned the full rights to contribute, but which SCO is now claiming it did not. At the core, that's the issue SCO is suing IBM over.

    190. Re:The scary thing by Anonymous Coward · · Score: 0

      It's funny. I talked to an IP lawyer last week in NY who has won several high profile IP cases. He said that the GPL is good law, even though there is a lot in there that is not valid unless you modify the code you're using.

    191. Re:The scary thing by tomhudson · · Score: 1
      Which is why I posted elsewhere the copyright number for what SCO was actually awarded (Library of Congress Copyright # TX-5-705-356), and how it has nothing to do with intellectual property rights or patents.

      The copyright in question is only 20 pages of source code, specifically, modifications to Unix Sys5 release 4.1 ES. Not much in the way of IP there, I think we both agree (unless they used a really really small font, so that they could get those "millions of lines of code that were stolen" onto only 20 pages).

      My point was that we're dealing w. a whole mess of issues here (SCO claims copyright, but tries to use the startegy that patent-holders would use, which just doesn't cut it). I still think it's all just a pump-and-dump stock scam.

      You too can do the same thing - write some unix code, pay $30.00 to file, and you now can go around saying the government has issued you a copyright on some "Unix source code". Just mumble when people ask you for the details (just like McBride :-)

    192. Re:The scary thing by Anonymous Coward · · Score: 0
      If they decide to sue, the violating code will have to be shown in court, and it will no longer be public


      You may want to reword that.
    193. Re:The scary thing by Anonymous Coward · · Score: 0

      In the welcome.msg file on their FTP server.

      Welcome to SCO's FTP site.

      I hardly think it's a hidden private site that has a hallow disclaimer and hosts pirate software that you're not supposed to download.

    194. Re:The scary thing by thisgooroo · · Score: 1

      actually, the way they seem to be twisting this is that they don't distribute at all (never mind the ftp server), but make the "illegal derivatives" legal.

    195. Re:The scary thing by 4of12 · · Score: 1

      how expensive this Linux licensing is going to be?

      Not much to me, I figure.

      The instant that SCO releases documents in court detailing exactly which lines in the Linux source distribution infringe upon their copyright, and the instant the court (and appeals) verify exactly which kernel version has the infringing lines introduced, I'll revert to that kernel version and await the introduction of independent implementations for whatever functionality is lost.

      --
      "Provided by the management for your protection."
    196. Re:The scary thing by thisgooroo · · Score: 1
      The GPL License is only a person to person contract, it is NOT A LAW. Hence you can not break the law by breaking the "contract".

      but breaking the license breaks copyright law

      Also if the GPL License, as a contract, is invalid or uninforcable then it can't even be broken.

      if the GPL is invalid, so is copyright. the GPL is a license under copyright law

    197. Re:The scary thing by moonbender · · Score: 1

      Yeah, that's kind of my point. :)

      It's wide open, claiming to be a public service. But even if it wasn't, even if it did claim to be private, the mere fact that you're running an anonymous FTP service implies that you basically grant everyone the right to download.

      --
      Switch back to Slashdot's D1 system.
    198. Re:The scary thing by Anonymous Coward · · Score: 0

      OK, let's assume that Linus can't be bothered to turn up. He's a bit like that, by all accounts.

      The GPL is struck out. Found invalid. Not worth the paper it's written on.

      Now can you explain to me, what will give SCO the right to distribute the millions of copyright lines of Linux code that they don't own?

      The clue's in the question, as they say.

    199. Re:The scary thing by Maserati · · Score: 1

      The countersuit writes itself.

      --
      Veteran, Bermuda Triangle Expeditionary Force, 1992-1951
    200. Re:The scary thing by jrumney · · Score: 1
      "We only made these files available via the 'FTP' program, which is only for highly advanced technical individuals such as corporate IT managers, for the convenience of our paying customers.

      And I assume the Judge is supposed to take the view that GPL violation is OK as long as the customers are paying to be violated.

    201. Re:The scary thing by K-Man · · Score: 1

      I assume it'll just cover the support they provide. After all, if the kernel has any bugs in it, the buyer can return it, right?

      --
      ---- "If we have to go on with these damned quantum jumps, then I'm sorry that I ever got involved" - Erwin Schrodinger
    202. Re:The scary thing by Eccles · · Score: 1

      The problem is that they claim that Linux itself is illegal. Which means that don't give a rat's ass about licenses Linux is distributed under.

      But they must. If they distribute anything other than the specific sections that they claim come from their code, they must have the author's permission to do so. They do not have, nor will they get, this permission, unless they claim to have written *all* of the Linux kernel. I think we can dispense with that claim rather quickly.

      --
      Ooh, a sarcasm detector. Oh, that's a real useful invention.
    203. Re:The scary thing by mark-t · · Score: 2, Interesting
      Who is going to take them to court to fight it?
      Anyone who owns copyrights over portions of the Linux kernel.

      But here's the catch...

      They can do to SCO what SCO did to them.

      Scenario: Party A, consisting of some number of copyright holders and SCO. SCO receives a cease and desist letter telling them to stop distributing party A's code in violation of copyright, as SCO does not have permission to distribute party A's code. SCO asks party A where their code is so that it can be removed from their own Linux distro, and party A then refuses to disclose this information to SCO, telling SCO that if they can't figure it out for themselves, the cease and desist order still stands. If they fail to comply, party A can then sue them for copyright infringement.

    204. Re:The scary thing by eric76 · · Score: 1
      The biggest problem with the Kernel guys redoing it, is now they can be considered 'tainted'.

      That might be true for trade secret issues, but I don't think so for copyright issues.

      For example, imagine that you were a writer and was writing a book about bullfighting. Having read Hemingway's Death In The Afternoon wouldn't taint you. You can use the ideas in the book as much as you wish as long as you don't just copy the sentences.

      Or imagine you are a songwriter. Having listened to a love song (even if it was downloaded via Kazaa) does not mean that you are tainted can cannot write another love song.

      I believe that copyrights are about the complete work, not to it's content or structure alone.

      In fiction, there are, however, instances where you have to tread lightly. If you were to write your own Parry Hotter novel without permission from Mrs. Rowling, you would be in trouble because it would be a derivative work as a result of building upon the characters she has developed.

      But in writing software, the situation is different because the new code would not be a derivative of the old code using the definition of derivative contained in Title 17 of the U.S. Code:

      A ''derivative work'' is a work based upon one or more preexisting works, such as a translation, musical arrangement, dramatization, fictionalization, motion picture version, sound recording, art reproduction, abridgment, condensation, or any other form in which a work may be recast, transformed, or adapted. A work consisting of editorial revisions, annotations, elaborations, or other modifications which, as a whole, represent an original work of authorship, is a ''derivative work''.

      As long as the new code is actually new, I don't think that it would be a derivative work even if those doing the work were intimately familiar with the old code.

      The bigger question is whether there is any infringing code to start with.

      SCO can claim copyright, but whether any Linux code infringes on it will have to be determined, possibly in court.

      One other point. Several people have suggested that we can now go to the Copyright office and examine the code to see what infringes. That may or may not be true.

      I've been told that when filing for a copyright on code, you don't necessarily have to include the entire code, but only the first and last few pages. The purpose is to reduce the amount of paper the copyright office has to store.

      I don't know if that's for each program or for everything combined. And I might misunderstand the issue entirely. But if it is true, don't expect to learn anything meaningful by examining the code that was filed.

    205. Re:The scary thing by Vivieus · · Score: 1

      Went there and searched for "System V" Nothing mentioned SCO. AT&T, though, yes. Searched for "Caldera", found this: 8. Registration Number: TX-5-437-956 Title: IBM TPF (PUT14) base : version 4, release 1, modification 0 : 5748-TPF. Description: Computer program. Note: Printout only deposited. Claimant: acInternational Business Machines Corporation a.a.d.: acIBM Corporation Created: 2001 Published: 29Jun01 Registered: 6Aug01 Author on © Application: program text: International Business Machines Corporation, Allied Management Systems (AMSYS), Caldera, Unix Systems Laboratories, Inc. & Apache Software Foundation, employers for hire. Claim Limit: NEW MATTER: revisions & additions. Special Codes: 1/C Seached for "SCO": 16. Registration Number: TX-5-705-356 Title: UNIX system V, release 4.1ES. Description: Computer program. Note: Printout (20 p.) only deposited. Claimant: the SCO Group, Inc. Created: 1991 Published: 27Jun91 Registered: 30Jun03 Author on © Application: UNIX System Laboratories, Inc., employer for hire. Previous Related Version: Prev. reg. 1992, TXu 510-028, et al. Claim Limit: NEW MATTER: revisions. Special Codes: 1/C Aha! I think we've got the one they sent.

      --
      ___
      *insert sig here*
    206. Re:The scary thing by Vivieus · · Score: 1

      Sorry for the formatting, it was looking fine in the submit box, and somehow it vanished when submitted.

      --
      ___
      *insert sig here*
    207. Re:The scary thing by thisgooroo · · Score: 1
      Both AT&T and Microsoft have put stolen intelectual property in their operating systems. Microsoft Windows TCP/IP stack contained stolen intelectual property from Berkeley Systems, and AT&T SysIV and SysV unix contained stolen IP from Berekely Systems.

      you are wrong at least regarding microsoft: the BSD license permits including BSD code anywhaere and under any condition, provided you keep the BSD copyright notice in there and credit Berkley. afaik, microsoft satisfied that condition. otoh, USL allegedly swiped lots of BSD code and replaced the copyright notice with their own copyright notice

      BSD never went after the users. SCO wants to change this by trying to charge Linux users a license fee. If they set this new precedent, BSD would then have a case for going after all Windows at SysV users.

      no, beause the copying was not a license violation

    208. Re:The scary thing by tomhudson · · Score: 1
      It is apparent because someone has looked at the code and verified that sections of code are duplicated.

      I don't think so. The actual source of the code wasn't revealed, just a few pages side-by-side, along with instructions saying "this came from us, and this came from linux".

      And on top of that, the first reviewer to publish turned out not to know what comments in the source code were (she called them "annotations", FFS!), and admitted that she was not a programmer.

      If there are duplicate lines, they can come from

      1. SCO copying code from Linux
      2. Code copied by both from other sources (BSD, etc)
      3. Code convergence (only so many ways of expressing some programming idioms)
      4. Following public standards
      The scary thing is that people are buying into this whole SCO/MS bullshit.
    209. Re:The scary thing by YU+Nicks+NE+Way · · Score: 1



      Hold it right there, sir. Let's look back here at your point...was it 4?...yes, four. This notion of "consideration". Now, I may just be a southern boy, but I seem to remember that meant "valuable consideration" right?

      So would you be good enough to tell the court how much I would need to pay to get a copy of this here "Leenicks" thing? Seems to me that you just said I could get a copy for nothing, right? That, in fact, Torvalds sends out copies for free, too?

      </drawling southern lawyer voice>

      Aren't you effectively saying that means there's no value to the "right to distribute the code" -- if I need a copy, I can get it directly from the manufacturer gratis. A contract requires the exchange of valuable consideration -- and there's none of that.

      Your honor, there is no contract involved here. The defense moves for immediate dismissal of this action, with prejudice.

    210. Re:The scary thing by Anonymous Coward · · Score: 0

      Someday, I will try to copyright the following Java code:
      for(int x=0; x10; x++)
      {//place code here}

      I will then claim that nobody may use loops from 0 to 10 using the variable x. I will then sue and make millions.

    211. Re:The scary thing by tomhudson · · Score: 1
      Search my other postings on same - it's properly formatted :-)

      Slashdot is having a bit of a problem handling certain tags this afternoon (blockquotes don't work so hot right now either :-(

      The 20 pages, at 66 lines per page max, gives 1320 lines of source code (of which hwo many would be comments, white space, etc?) If this is the sum and total of their claims, it really doesn't add up to a significant portion of the kernel (unless somehow Linus has invented a revolutionary compression algorythm to squish more than a million lines of code and support libraries into a paperback-sized printout, which would be something to copyright and patent)

    212. Re:The scary thing by Anonymous Coward · · Score: 0

      You need to stop thinking like a "geek" and start thinking like a lawyer.

      The GPL doesn't have to be evaluated by the court in a "thumbs-up" or "thumbs-down" manner. The court can be selective about which parts of it are enforecable and which parts aren't. This happens with contracts all the time.

      As far as the copyright issue is concerned, why do you think SCO went to the trouble to have their copyrights registered for Unix? It's because copyrights aren't as simple as some people believe. It's quite possible that a court could find that those millions of lines (other than those that supposedly belong to SCO) aren't properly copyrighted at all. The court might have to go through some rather dubious logic to get there, but it wouldn't be the first time.

    213. Re:The scary thing by Svartalf · · Score: 1

      The problem lies in that they don't have a right to distribute the code in question (because they don't have permission to do so...) because of their claims (Clause 4 invalidates their rights to the code in question...).

      --
      I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
    214. Re:The scary thing by Anonymous Coward · · Score: 0

      But the current round of legal activity will probably be with different judges and they're under no obligation to come to the same conclusions.

    215. Re:The scary thing by Frater+219 · · Score: 1
      Since we have the four elements of a contract: offer, acceptance, intention, and consdideration, guess that what that means? Yes, under the law we have a CONTRACT.

      There is no consideration, since you are not giving the author anything he did not already have. Your "agreement" not to distribute the code in violation of the terms of the GPL does not constitute giving the author anything ... since you were already obligated not to distribute it in violation of copyright law. You cannot give the author your agreement not to violate copyright law as consideration, since you had no right to violate it.

      Here's a parallel: Let us say that we live in a town with strict, absolute trespassing laws, such that if I cross your property without your permission, I am guilty of trespassing. Now, let us say that you generously grant me permission to cross your front lawn, but you make it clear -- in the terms of that permission -- that I am not permitted to cross your back lawn. The permission you grant is limited, not absolute: I am allowed to do some things that would be illegal without your permission, but not others. My not crossing your back lawn is not a consideration that I give to you, because it was not a right I possessed in the first place!

      A more blatant parallel: "If you give me twenty bucks, I will not shoot you." This is not an offer of contract, since I have no right to shoot you. To claim that the software recipient gives the author consideration in "accepting" the GPL is to claim that the recipient means, "If you give me this software, I will not violate copyright law upon it." That's not consideration.)

      The GPL is not a contract. It is a grant of permission. Copyright says, "You may not copy without the author's permission." (Note, it doesn't say that permission has to be in the form of a contract -- it can be in the form of a unilateral grant of permission.) By placing a work under the GPL, the author says, "You have my permission to copy, but only in certain ways." The default condition -- lack of permission, hence normal copyright law -- applies if you violate those terms.

    216. Re:The scary thing by natet · · Score: 1

      Except that part of SCO's claim is that they consider anything based in part on the SysV code, or running in SysV code to be derivative works, and therefore owned by them. I don't agree, but that is apparantly their claim.

      --
      IANAL... But I play one on /.
    217. Re:The scary thing by ralphdaugherty · · Score: 1

      *Ford can not sue Chevy for designing 'a car'*

      actually, just to make you lose any hope on patent office and things as such, there was a fellow who patented a car like thingy in the late 1800's, the fellow even delayed it in the process(like companies do nowadays) until cars got into widespread production, and then licensed it to several manufacturers.

      the fellow had not built a working car from the description in the patent even, and later lost in court to ford after failing to produce an usable car from the description in the patent(iirc court demanded it, the patent was very vague with details but nobody had bothered to go to court with the fellow and had instead paid quite nice sums and the fellow in question wasn't even an engineer but a patent official iirc).

      ok so what this has to do with sco? not much except that companies are too reluctant to go to court and will even pay quite considerable sums for not having to do it, even if they would quite probably won if they took even a little time to investigate the issue.

      i'm just amazed if some people really buy sco cash thinking sco has a viable business plan in 'licensing linux 2.4', big f***n boohoo, move back to 2.2 and start over EVEN if those few lines are never told because of some craziness and if they claim they are in 2.6 too, and why don't they just go after the fellow that submitted that code? surely such info would be available from the docs/tracking.

      also why don't they sue anyone else than ibm? how many employees does sco even have?

      and they really can't do it by the books by some twisted binary only licensing of linux without losing all rights to distribute it anyways..


      People keep saying "a few lines" but misunderstood the "at last 80 consecutive lines copied" bit to be the sum total of identified infringement. The areas in question appear to be the "enterprise ready" stuff that IBM put into Linux, actually budgeting a billion dollars to make it enterprise ready, as they call it. The three acronyms that are referred to (NUMA, etc.) are hardly a few lines of code but instead major architecture features. Whether SCO can prove their claim of ownership of the architectural features as derivative works is the question, not identifying and replacing a few lines of code, in my opinion.

      The attention to others than IBM and the number of SCO employees was in McBrides remarks. He said they are moving into new territory (translation: preparing to sue others than IBM) and the number of SCO employees is 330.

      The binary licensing was explained several times, but people keep posting about it breaking GPL, etc. It was a license for Unixware that protects the licensee from additional SCO claims as long as the licensee is running distro binary Linux and doesn't modify the code themselves.

      rd

    218. Re:The scary thing by Anonymous Coward · · Score: 0

      When copyrighting source code, you don't send all the source. Only the beginning and the end + a major functional part.

      (And yes, finding the beginning and the end of object oriented software can be considered as silly).

    219. Re:The scary thing by Anonymous Coward · · Score: 0

      anathema not anethma

    220. Re:The scary thing by MrResistor · · Score: 1

      I realize that, but SCO doesn't seem to. Truth be told, I would love to see that happen. The point is, SCO is claiming ownership of basically every OS created in the last 30 years, specifically mentioning Linux, BSD, Windows, Mac OS, and Solaris users as potential targets for their attack lawyers. What that means to me is that I might as well just continue as I have been, since it doesn't seem to matter what I do, I'm still just as much of a target to them.

      --
      Under capitalism man exploits man. Under communism it's the other way around.
    221. Re:The scary thing by overcome · · Score: 1

      The problem, though, is that there is no file larger than 68 bytes in that directory. I don't know of any GNU/Linux packages that small.

      --
      I refuse to use sigs because they provide redundant, useless information that repeats itself for no purpose whatsoever.
    222. Re:The scary thing by ces · · Score: 1, Interesting

      there will be plenty of IBM lawyers to contradict anything that a SCO lawyer might say.

      I understand IBM buys lawyers in bulk.

      Should be *VERY* interesting once they unleash the horde on SCO.

      --
      Happy Fun Ball is for external use only.
    223. Re:The scary thing by ces · · Score: 1

      Not breaking the law, they are in breach of contract. Who is going to take them to court to fight it? Nobody. However, this issue will be pressed by the IBM law team, and quite probably will have a favorable outcome on this point.

      Linus for one could sue SCO for violating his copyright, slander, defamation of character, and defamation of trademark. I'm sure that if Linus wanted to sue he would have no problem getting donations to his legal defense fund or getting certain attorneys to work pro-bono.

      --
      Happy Fun Ball is for external use only.
    224. Re:The scary thing by tomhudson · · Score: 1

      Youhave to post the first 25 pages, the last 25 pages, and a cover page w. the copyright notice and title. Their entire filing was 20 pages, which makes it 1 title page, and 19 pages source. Ergo, their filing was the complete source for what they received copyright for. Clearly not Sys5 Unix.

    225. Re:The scary thing by Anonymous Coward · · Score: 0

      ever hear of alias

    226. Re:The scary thing by Xerithane · · Score: 1

      Linus for one could sue SCO for violating his copyright, slander, defamation of character, and defamation of trademark. I'm sure that if Linus wanted to sue he would have no problem getting donations to his legal defense fund or getting certain attorneys to work pro-bono.

      Those with the means to sue, likely wouldn't. I suppose I should have said that differently. It's just not worth it. SCO is a dying company, with little actual assets to be aquired in a lawsuit. That and if it looked like they were losing the lawsuit, bankruptcy is an easy out. That and they would almost instantly be hit with a counter-suit, which takes more resources. It could turn into a very nasty legal battle for a private individual to handle.

      --
      Dacels Jewelers can't be trusted.
    227. Re:The scary thing by Physics+Dude · · Score: 1
      Your southern lawer seems to be overlooking the fact that we're not talking about the price for a copy of Linux. We're talking about the price of REDISTRIBUTION rights for Linux. You CAN'T get a REDISTRIBUTALBE copy anywhere for nothing!

      The GPL *IS* the price of redistribution!

    228. Re:The scary thing by Trailer+Trash · · Score: 1

      There is no consideration, sorry. The GPL doesn't state that you have to give/sell anything back to the original author.

      The GPL is not a contract, it is a grant of rights that you wouldn't normally have (i.e. the right to copy a copyrighted work).

      Ever notice how most copyright notices have "all rights reserved" beside them? What they're saying is "I own the copyright (i.e. right to copy) this work and I am giving you none of those rights. I am reserving them for myself."

      The GPL says "you have the right to copy this work if and only if you pass this right (and a few others) on to anyone who obtains a copy." It is a grant of rights that you don't have otherwise.

      That's why the whole "but the GPL hasn't been tested in court!" argument is bullshit. It's moronic. If you don't abide by the GPL, then you have no right to redistribute the code in question, basically standard copyright law which is "tested" in the courts on a daily basis.

      That's the position SCO is in. The bill that they've racked up to Linus Torvalds would basically turn McBride's great-great grandchildren into debt-slaves of Linus Torvald's great-great grandchildren. But only if Linus gets his head out of his ass and does something about it now.

      Mitigation of damages is a two-way street...

      Michael

    229. Re:The scary thing by cmarkn · · Score: 1
      The only way SCO can distribute Linux is under the GPL.
      What makes anyone think they care? They aren't selling anything anyway. SCO's business plan does not include actually distributing products, it consists entirely of suing for violations of its IP claims.
      --
      People should not fear their government. Governments should fear their people.
    230. Re:The scary thing by Physics+Dude · · Score: 1
      The GPL is somthing far different from a common shrink-wrap licence. It's an open offer of a CONTRACT TO REDISTRIBUTE.

      If you took any shrink-wrap commercial software and started copying and redistributing it (as SCO is doing with the kernel code), it would be viewed as a copyright violation *IRREGARDLESS* of any shrink-wrap license, EULA etc.

    231. Re:The scary thing by DavidTC · · Score: 1
      Score:2, proof the mod system is broken.

      This post best explains the GPL's legal status. The GPL is not a contract, it is not a 'license' in the same that EULA are licenses. (Yes, it's legally a license, but that's not the point. EULA are proported to be contracts, and that's how they 'work'.)

      Meanwhile, the GPL is literally a written permission to do something with your property if they follow certain rules.

      It's like you open an area of your land to campers, provided they don't start fires. Well, campers come in, and start fires, and you tried to kick them out, and it went to court. Just how surreal a legal decision would it be if they managed to get all your rules invalidated and suddenly could do anything they wanted?

      The idea is obviously completely absurd, but because some people don't understand copyright law and most EULA aren't worth the electrons they're printed on, think that's somehow a possible outcome of a GPL case.

      It is your code, it is not a 'contract' where both sides can be in fault, it is nothing but written permission to do some very explict things, very well explained and documented. If they manage to invalidate the written permission, they've just screwed themselves, and that's all they've accomplished.

      Now, there are legal issues with the GPL, specifically whether or not linking into a shared library is a 'derived work' or not. But that can't possibly apply to this situtation.

      --
      If corporations are people, aren't stockholders guilty of slavery?
    232. Re:The scary thing by Anonymous Coward · · Score: 0

      You've come up with a double-edged sword that may now be used against Linux. You can buy a License from SCO to use Linux or get sued by SCO, and get sued if you do by any of the random thousands of developers with IP in Linux. How do you avoid this mess? Easy - Use SCO Unix products, FreeBSD, or Solaris. The case may now be made that Linux = Legal Issues Nuking Users, suXors. :(

    233. Re:The scary thing by Xerithane · · Score: 1

      *IRREGARDLESS*

      I'm supposed to take semantic lessons from someone who actually used "IRREGARDLESS".

      Right, why don't you spend your next allowance check on a dictionary.

      --
      Dacels Jewelers can't be trusted.
    234. Re:The scary thing by jedidiah · · Score: 1

      Yeah, they get them by the case at Sam's Club and Costco. Of course, this is why you can never find a case of lawyers on the shelf at Costco or Sam's Club whenever you go there.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    235. Re:The scary thing by Dastardly · · Score: 1

      No one can ever be liable for a GPL violation merely by using the software.

      How did you get the software in the first place? If it wasn't legally distributed to you, then how can it be legal for you to use it?

      If SCO's allegations are true, and SCO does not license its code under the GPL. Then, the copy of Linux you have was illegally distributed to you in violation of the GPL. You had no right to receive the software and therefore have no right to use it. If you did not receive your copy in accordance to the rules of the GPL as the owners of the code intended, then you have stolen said code and are using it in violation of international copyright law.

      You are not in violation of the GPL, you are in violation of international copyright law because you have software for which you had no license to receive.

      IANAL
      Dastardly

    236. Re:The scary thing by Anonymous Coward · · Score: 0

      " Oh yeah, let's not forget that by not following the GPL, they are violating *copyright* law as well, which has recently been criminalized. So strike what I just said about not being a violation of criminal law."

      Why do you think GPL is still valid when the code GPLed is a derivative work of SCO, which is their claim? You can't copyright something that is not original, and therefore, the GPL is invalid according to SCO.

    237. Re:The scary thing by vsprintf · · Score: 1

      . . .you have to admit that the way they're doing business these days . . . is generating plenty of illwill out there. I can't see them doing well in the long-term as a result of the last few months.

      Executives these days are only interested in looting companies, not in their long-term survival. Only McBride and cohorts know exactly when the pump-and-dump is to take place, but I'd guess pretty soon.

      They made a big noise about paying a small fee for a piece of paper, and a bigger noise about offering Linux *licenses*. They announced that Sun is the mystery silent partner. The real legal case won't be settled for years. Now, all they need to do is wait for a few fools with lots of money to buy licenses, and let the press take it from there. More companies figure maybe it's better to be safe, pony up, and it snowballs. (This is all provided the unknown license fees are reasonably low, otherwise the companies dump Linux, and Sun and MS are the winners.)

      These sharks have figured out a new open source business model:

      Join a dying company with a grant from the King of Spain.

      Claim ownership of Linux.

      License it to the people who own it.

      Dump your SCO stock on latecoming losers.

      Catch a flight to the Islands before the feds figure it out.
      It's just a new twist on an old money-making idea called theft. You've got to admit, though, they certainly have big, brass balls. Who else could stand up in public and spout that nonsense with a straight face?

    238. Re:The scary thing by Dastardly · · Score: 1

      Paragraph 7 is not an out. If you can't distribute under the GPL, you can't distribute at all. Which means that they can't distribute Linux in ANY FORM.

      I think they are trying to worm their way through this by claiming they ar eno longer distirbutiing the software, but are only licensing to those who already have the software. I doubt a court will find that convincing because what it means is that if the code in question was not distributed under the terms of the GPL, because it has SCO code, then it was illegally distributed period. And, therefore no one has a license for the software.

      Dastardly

    239. Re:The scary thing by uberdave · · Score: 1

      Yes, Right. I did not mean to imply which was the original, and which was the copy, only that there was, in fact, duplicated lines of code.

    240. Re:The scary thing by geekee · · Score: 2, Interesting

      "No, if they encumber the linux codebase with their own license, then the GPL becomes void and no longer can be used to distribute Linux. At that point, the distribution of every piece of linux that they don't explicitly own becomes prohibited, completely, because Linux falls back to copyright law which indicates that the contributors of the other pieces still own them and have not licensed them to any distribution but GPL. Therefore, if they tell people they need to pay to run linux, linux becomes un-runnable."

      Actually, the GPL is probably no longer strictly valid for the Linux Kernal if it contains copyrighted work from SCO. In the end, it's up to the courts to decide what the proper remedy is for the situation. SCO can't really decide, as you have pointed out, but neither can Linus, et. al., because they have harmed SCO, if SCO's claims are true. Therefore, the court system will eventually determine a remedy and award damages, if any are necessary, and both SCO and Linux must abide by the court's decision. MS went through this same thing, except with antitrust laws. In the end, judges decided the remedy, not the DOJ or MS. Same thing here.

      --
      Vote for Pedro
    241. Re:The scary thing by mindstrm · · Score: 1

      You are entirely correct. Everyone will argue with you, and completely miss this simple point though.

      The point for those who are offended by this claim taht GPL is not a contract.. is that, even IF, DESPITE all your wonderful logic, the GPL is actually not valid.. all it means is people DO NOT HAVE THE RIGHT to redistribute.. it doesn't make the work suddently public domain or something.

      You can argue about the validity of the GPL all you want.. but in the worst case, that it's not worth the virtual paper it's printed on, there is nothing left to grant anyone the right to distribute and make derivitave works.. copyright law applies, and SCO or whoever else will still be up shit creek.

    242. Re:The scary thing by Grax · · Score: 1

      Yes it does. I just downloaded the src rpm from their web site and extracted the kernel source from it using the instructions posted here.

      SCO is trying to sell a product they do not own. They continue to distribute the product on their ftp site with GPL notices intact. They used to be a major Linux distributor. Must we sue them for fraud and harassment before we get some peace and quiet?

      I am not a pirate. I am using legally licensed software that they don't have any claim to. You can't release it under the GPL and then say "wait, no, we want money". I don't need this BS right now.

    243. Re:The scary thing by Dastardly · · Score: 1

      If RedHat paid SCO they would be liable for copyright violation to every copyright owner of the kernel. That includes most hardware companies, the FSF, and hundreds of individuals...

      An individual user could pay SCO some cash and not be liable, so long as they don't redistribute the kernel.


      False. Because this means the user was not originally distributed the code according to the terms of the GPL. Some of the software in LInux that they received was not licensed under the GPL, therefore according to section 7 none of the code was distributed to them under the GPL. Therefore, the users have only those rights given to them under standard copyright law... NONE.

      Actually, by purchasing a license to the SCO code they acknowledge that they know that they received Linux software that was not licensed under the GPL. This probably makes them ripe targets for a lawsuit by a Linux developer for stealing their software.

      Dastardly

    244. Re:The scary thing by Anonymous Coward · · Score: 0

      Right idea, but a bad example...

      > This is like saying "Well, the makers of the
      > Terminator movie have a copyright on that movie,
      > so they can sue anyone that makes any
      > story that even resembles a plot where
      > robots take over the world."

      SF author Harlan Ellision successfully sued James Cameron for making the Terminator movie "based on his story 'I have no mouth and cannot scream." Cameron sucessfully fended off Ellison's suit until Ellison's lawyer scum depositioned a witness who heard a crew member say "Cameron's making a movie of some Harlan Ellision story he ripped off." Sounds like Heresay to me, but O.J. Simpson is still and Dubywa stole the Presidency (Just because you might like these guys doesn't make it right.)

      The initial poster was correct though. Anyone can register a copyright for $30. Stock investors who are sucked in by that that deserve to lose their money. Feel free to post that on your stock boards.

    245. Re:The scary thing by meatpopcicle · · Score: 1

      I may be mistaken, but this statement is in direct violation of the GPL. If they are distributing it, they HAVE to provide the source as well and they have to pass on the same license as they have.

      Their problem is they want the cake and be able to eat it too.

      Regardless of their claims, until they provide proof its all just smoke and mirrors.

      Unfortunately some people will be making alot of money in all this and when/if the case fails they will still be out on top becasue they have already sold their stock. The downside is that most everyone else will be burned.

      --
      "You're on my side and the dark side, like Lando Calrissian?" --Gimpy, Undergrads
    246. Re:The scary thing by Anonymous Coward · · Score: 0

      Paying the fee actually opens companies to liability from Linux developers. Because now they have received a copy of Linux code in violation of the GPL because whoever they got their Linux from could not have given it to them. Since, they did not receive the code in accordance with the GPL, they have no license for the code whatsoever and standard copyright law applies giving them no rights with regards to Linux.


      You make an excellent point. The FSF should RIGHT NOW issue a press release advising these fortune 1500 companies of this fact!

    247. Re:The scary thing by NTT · · Score: 1

      HAHAHA. Now thats really funny. Ahh, my kingdom for a mod point.
      Good point.

    248. Re:The scary thing by Frodrick · · Score: 1
      Who's for getting some high profile advocates to claim that SCO has pirated BSD code? If they can spread FUD, why can't the open source community?

      Why do you think that is just FUD? Some fairly respected journalists have stated that they have sources inside SCO who anonymously claim that just that sort of action has occured.

    249. Re:The scary thing by Gverig · · Score: 1

      That's the beauty. They distribute NOTHING. You do not have right to use Linux (again, assuming everything they claim is true). So all they do is the ALLOW you to use Linux for an extra fee. They do not claim any right for Linux, from what I understand, but they claim that nobody can use or distribute Linux without their permission. It's like you invent some material. I steam material design from you and start building somehting with it. Now, I can say "dude, you are not selling these". I get nothing, you get nothing, everybody is happy. Or I say "dude, you did baaaad, but I will allow you to do this for a while if you payme some ransom". Now, all work done is yours, all rights for the device (or whatever you have built) are yours, BUT noone can use or make or sell it without my permission.

    250. Re:The scary thing by arkanes · · Score: 1
      They submitted 20 pages of code. At roughly 50 lines of code per page, thats 1000 lines of code. Even if every single one of those lines was word for word in the Linux kernel, you'd have a hard time claiming that less than 1/3 of 1% of the totality of the kernel made it a derivative. Now, SCO will naturally claim that the code is so fundamental to Linux that creates a derived work (which would be another hard sell, because Linux existed and was working before this - they only claim infrigment since 2001 - so it's clearly not totally fundamental).

      Crazier things have happened. But this is hardly the open and shut kinda case that you seem to want to present.

    251. Re:The scary thing by bigsteve@dstc · · Score: 1
      If someone in Linus's position were litigious (he's not) and vindictive (he's not), they might go after the SCO principals as individuals. SCO may be dying, but you can bet that its principals will salt some money away before the company's legs stop twitching.

      Personal bankruptcy is not an easy out ... so I've heard.

    252. Re:The scary thing by da+cog · · Score: 1
      How did you get the software in the first place? If it wasn't legally distributed to you, then how can it be legal for you to use it?

      Quoth the GPL,

      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.

      5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.

      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.
      --
      Snarkiness is inversely proportional to wisdom because it emphasizes feeling right rather than being right.
    253. Re:The scary thing by JessLeah · · Score: 1

      I wasn't saying *I* wanted to make the case. I was saying *SCO'S EVIL LAWYERS* could make the case.I think all of this is rubbish.

    254. Re:The scary thing by okeby235 · · Score: 1

      This is interesting. Creates a nice position for the linux developers (read IBM) to bring a lawsuit against SCO and finally have them shot down as the lack of copyright violation is exposed.

    255. Re: The scary thing by Snowdrake · · Score: 1

      Why do you think that is just FUD? Some fairly respected journalists have stated that they have sources inside SCO who anonymously claim that just that sort of action has occured

      The very best FUD employs just the tiniest glimmer of truth, perverted beyond recognition into something far more insidious. Anyone remember the guy who tried to slam Linux as the worst OS available based on the number of Linux-related postings on Bugtraq vs. other products? The real challenge is how to twist it to best effect.

      The other question is one of what is "piracy" under the BSD license. Several mentions have been made lately in other threads of the mutation from "you must give credit" to "whatever," and the latter case argues for there being no true "piracy" for BSD code. Slippery, that...

    256. Re:The scary thing by wkitchen · · Score: 1
      Ford can not sue Chevy for designing 'a car'
      Maybe not, but that hasn't stopped GM from trying to sue Avanti Motor Corp. over their upcoming Studebaker XUV. GM apparantly thinks that their deal with Hummer gives them ownership of the fundamental concept of big, boxy, utility vehicles. Or maybe they're just counting on the smaller company not being strong enough to defend against them whether legitimate or not. There seems to be an awful lot of that going around these days.
    257. Re:The scary thing by Rogerborg · · Score: 1

      I'm guessing YANAL. Under the circumstances, I'll stick with the advice of my company's IP lawyers, and continue to view the GPL as a revokable, non perpetual, non binding, non contractual implicit license.

      Heck, don't take my word for it:
      Eugene Volokh, a law professor at UCLA, said that Mattel might be able to argue that the GPL is invalid because users don't pay for the free software.

      "Nonexclusive licenses given for free are generally revocable, even if they purport to be irrevocable," Volokh said. "Even if the GPL license in cphack is treated as signed and is covered by 205(e), it might still be revocable by Mattel as the new owners of the cphack copyright."

      "It is unfortunately not quite as solid a case for the good guys as the GNU license theory would have at first led us to believe," he said.

      --
      If you were blocking sigs, you wouldn't have to read this.
    258. Re:The scary thing by apeteryx · · Score: 1

      The way that SCO thinks they can get away with it is that they hope they won't be counter-sued. It might be worthwhile to take them to court if they do release a version that contradicts the GPL (and no access to source code would do that. As an aside, US copyright law is that. US. SCO would have to pull the same stunt in other parts of the world: for instance Harry Potter is published by Scolastic in US and Bloomsbury elsewhere.

      --
      Chris Gale Dunedin, New Zealand. http://www.pukeko.net.nz
    259. Re:The scary thing by crizh · · Score: 1

      The 'consideration' one provides the original author is the right to use any modifications one makes to the original code under the same licence.

      or put in simple words for the hard of thinking...

      You may cross my lawn if I may also cross yours.

      --
      Trust The Computer, The Computer is your friend.
    260. Re:The scary thing by crazyphilman · · Score: 1

      I just read that they're specifically targeting the 2.4 kernel, which is where they say their code was placed. They claim they're just going after business users, and will leave home users alone (yeah, right). Also, the court case won't come up until 2005, which means they have no legal right to demand anything until well after that point (there was a good article about this in eWeek, 7/22). From this I gather:

      1. This whole thing is completely irrelevant, because long before 2005 all even remotely offending code (whether it's actually offending or not) is going to be stripped.

      2. No-one is still going to be using kernel 2.4 at that point, anyway.

      3. This gives the market a full two years to gut SCO, which is an eternity. They could be taken over, they could be bought outright, they could go bankrupt... On the internet, every day is "anything can happen day".

      4. Long before then, FreeBSD, OpenBSD, and NetBSD will have gotten to the point where they're virtually equivalent to Linux (I think they're already equally powerful, but they have some work to do on hardware support and Linux still has more applications, although the gap is getting pretty narrow). So even if SCO wins, which is a long shot, it STILL won't matter.

      I've totally stopped worrying about this silliness. I mean, really. SCO is a fat, lazy, toothless lion without claws trying to roar and whimpering instead. The market is a hunting party which is currently content to marvel at the weird old lion, occasionally throwing a peanut at it. Sooner or later, the market will get bored and turn the lion into a trophy, you know?

      --
      Farewell! It's been a fine buncha years!
    261. Re:The scary thing by Xerithane · · Score: 1

      I'm guessing YANAL. Under the circumstances, I'll stick with the advice of my company's IP lawyers, and continue to view the GPL as a revokable, non perpetual, non binding, non contractual implicit license.

      Feel free to view it as you wish. Purely because you don't pay for something doesn't invalidate a license, or a contract. The arguments for payment can come from anyside. "I'm paying for this software with my time, using it and testing it while reporting bugs." Easy enough counter to that argument.

      Even if Mr. Volokh says that Mattel might be able to argue that the GPL is invalid, doesn't mean that they will nor does it mean that is how the court will see it.

      Because the software in question has no sure way of satisfying all the requisites for contract law (Only copyright law) it is easier to use copyright law.

      But no, I am not a lawyer. Just a hobby.

      --
      Dacels Jewelers can't be trusted.
    262. Re:The scary thing by Rogerborg · · Score: 1

      In principle I agree with you that it should be that way, and I do fully accept that GPL defaults to copyright even if it fails the contract test, but perhaps I'm viewing it from a different point of view.

      Specifically, I'm not saying that you're wrong, because there's nothing in findlaw either way, but I am saying that it would take a brave person to pay their mortage on the basis of the GPL being a non-revokable binding contract.

      We really could do with some case law precendent on this to clear up whether the GPL binds (contract) as well as empowers (license). I hope that SCO will finally provide us with one.

      --
      If you were blocking sigs, you wouldn't have to read this.
    263. Re:The scary thing by SillySlashdotName · · Score: 1

      If they distribute anything ...

      As I am sure someone else has pointed out by now, they are not distributing ANYTHING, they are licensing the use of the distribution you already have!

      They are contending that you have an illegal copy of their IP, but, for a fee - payable to SCO - you can use it legally.

      No media costs. No shipping. No marketing droids. Totally skip numbers 1, 2, and 3, go straight to 4 PROFIT!!!

      --
      Acts of massive stupidity are almost never covered by warranty. --me.
    264. Re:The scary thing by SillySlashdotName · · Score: 1

      But SCO is not making it legal for some company to ship Linux, they are selling licenses to USERS to make their copy of the software protected from lawsuit.

      In effect, they are saying "Pay us enough money and, though we claim what you have is illegal (and despite it not having been proven to actually BE illegal), we won't exercise our announced intention to sue you."

      They are sueing for money from IBM, selling licenses to users, and still claiming the right to separately sue the companies shipping Linux.

      --
      Acts of massive stupidity are almost never covered by warranty. --me.
    265. Re:The scary thing by SillySlashdotName · · Score: 1

      Long post, try to follow...

      SCO is claiming anything developed for (or on) Unix as their IP, based on the AT&T contracts that, through various purchases, SCO now has control over.

      AT&T basicly said that anyone could license Unix, but with the agreement that anything developed for or using their IP (Unix) became IP of AT&T, and that the contracts were perpetual.

      SCO is now claiming that anything except what IBM developed (they had an exception in THEIR contract with AT&T) would have belonged to AT&T if they had not sold their rights, and that now, because SCO owns those rights, those developements belong to SCO.

      Further, because some of what was allowed into Linux by IBM was NOT created by IBM (instead it was IP aquired by purchase - IP that SCO is claiming was theirs based on the AT&T contract and that SCO did not agree to sell), IBM did not have the legal right to allow it to be used in Linux, and that by allowing it to be used, they (IBM) broke the law - to the tune of $3 Billion.

      They seem to be claimng the legal theory of "the calf follows the cow (*) ", so all the talk of specific SysV code being in Linux misses the point, which is that even if the code is NOT in SysV, if it was developed USING SysV or developed FOR SysV, then it belongs to SCO (according to SCOs claim), and only SCO can allow it into other OSs - including Linux.

      They are claiming that any tools developed on AT&Ts unix belongs to them, and any applications, tools, or code developed with those tools also belongs to them - and so on, and so on.

      So if C was developed on AT&T Unix, then SCO claims they own C - AND ANYTHING CREATED WITH C, past, present, and future.

      Was CP/M developed on AT&T Unix, or created using any tools created or evolved from tools developed for AT&T Unix? If so, then SCO OWNS Microsoft - at least according to the legal theory they are propounding. DOS took many ideas from CP/M, was bought by BG, was developed into MS-DOS, was the basis of Windows 3.1, which was the basis for windows 95 and 98, etc.

      In the same way, if ANY PART of Linux was developed ON a platform that evolved from AT&T Unix, or was developed USING TOOLS developed on or for AT&T Unix, or evolved from tools developed on or for AT&T Unix, then SCO is claimng that IP belongs to SCO.

      They are making the largest power grab I have ever heard of, and most are not even seeing it. If they succeed, it will be on the level of patenting sunlight.

      I don't think their claims have merit, but I am not a lawyer, and there are many law decisions I don't agree with, either, but are still on the books.

      Be afraid. Based on previouse legal decisions, be VERY afraid.

      (*) An instructive legend is related in Ludwig Bieler, Ireland: Harbingers of the Middle Ages, London, Oxford, 1963, p. 11. In the 6th century AD, the king of Ireland resolved one of the earliest copyright disputes (between Columba and Finnian of Druim Finn) by ruling "As the calf follows the cow, so the copy follows the original" The Statute of Anne (England, 1710) is frequently described as the first modern national copyright legislation. While codifying protection for the author, it was, in fact, primarily beneficial to booksellers. See Mark Rose, Authors and Owners, Cambridge, Harvard, 1993, for a discussion of the origins of the notion of author as creator.

      --
      Acts of massive stupidity are almost never covered by warranty. --me.
    266. Re:The scary thing by Xerithane · · Score: 1

      Specifically, I'm not saying that you're wrong, because there's nothing in findlaw either way, but I am saying that it would take a brave person to pay their mortage on the basis of the GPL being a non-revokable binding contract.

      I definitely agree with you. You are entitled to more damages and an easier trial with Copyright law anyway. Copyright law is covered under a nice, big ass federal statute.

      We really could do with some case law precendent on this to clear up whether the GPL binds (contract) as well as empowers (license). I hope that SCO will finally provide us with one.

      This is why I'm hoping that IBM brings it up against SCO in SCO vs. IBM. Not the other way around. By having a judge interpret what is actually meant, we will gain a lot of leverage in the legal usage of the GPL. If there is actually a case Somebody Vs. Someone than there could more damaging results.

      --
      Dacels Jewelers can't be trusted.
    267. Re:The scary thing by SillySlashdotName · · Score: 1

      I think they are grabbing for the brass ring, and feel the potential result is worth the short term PR.

      I think you have hit the issue directly and squarely.

      These sharks have figured out a new open source business model:

      Join a dying company with a grant from the King of Spain.


      They are the equivelant of someone finding a grant from the King of Spain for all of Florida, or a deed to Manhattan Island dated BEFORE whatshisname (Minuit) bought it for $24 in glass beeds. I suspect they believe they have found the end of the rainbow and are working toward a multi-billion dollar prize - possibly a multi-TRILLION dollar prize.

      Interesting and disturbingly familure story - "Doing his best 17th-century impersonation of Donald Trump, Minuit assembled an impressive buyout of beads, hatchets, metal pots, mirrors, trinkets, and Dutch collectibles, totaling a mere 60 guilders, and bought Manhattan Island. The $24 figure comes from a 19th-century guess. It was a true bargain, even though Minuit had to pay twice: After the Shinnecocks walked away with their $24, the Reckgawawancs appeared, told Minuit he had bought Manhattan from the wrong Indians, and demanded payment on the spot."

      SCO = Reckgawawancs?

      Hnn...hng..hnn... Bevis, he said 'shiny cocks!'

      --
      Acts of massive stupidity are almost never covered by warranty. --me.
    268. Re:The scary thing by MrResistor · · Score: 1

      It isn't just 2.4, it's also 2.5, which means 2.6 as well. SCO has specifically said that in almost every statement they've made. The Linux kernel doesn't move that fast. Based on past performance, 2.6 will still be the standard kernel in 2005, 2.7 will just be gaining momentum, and it will probably not be until 2006 that people really start asking whether the next kernel will be called 2.8 or 3.0, let alone when it might be released.

      Also, the suit has brought SCO an infusion of cash. This last quarter was the first time SCO had posted a profit EVER. The market is not punishing SCO for it's behavior, but rewarding it, and rather well, so the chances of SCO just drying up and blowing away in the next few years are quite slim.

      As for the offending code being stripped out, how is that going to happen when nobody knows what it is? The assertions SCO has made so far have all been extremely vague. Even if the Linux community were to start over completely from scratch, it would be nearly impossible to do so in a manner which would create a completely unencumbered kernel since all the kernel hackers are tainted.

      Finally, I'm not sure which eWeek article you're refering to. I read the top 4 on their "Battle over Unix" page. None of them were dated 7/22, and all of them were little more than fluff. They paint the situation with a very broad brush, completely ignoring several very important details and many of the actual claims made by SCO executives in various recent interviews. It would be dangerous to form an opinion on the case based on those articles which I read, IMNSHO.

      I agree that there is nothing to actually worry about, but I base that on faith in the Linux developement system and the stupidity and ignorance of the SCO execs. Unfortunately, every one of your bullet points is full of holes, and has already been thought of and countered in public statements by SCO.

      --
      Under capitalism man exploits man. Under communism it's the other way around.
  3. ANd how are they gonna enforce that? by Pig+Hogger · · Score: 4, Interesting

    And how do they intend to enforce that, as long as there is no judgment yet????

    1. Re:ANd how are they gonna enforce that? by Roofus · · Score: 5, Interesting

      They'll send nasty lawyergrams. And if you don't pay up, they'll send some more!

    2. Re:And how are they gonna enforce that? by Anonymous Coward · · Score: 0

      Why isn't that illegal?

      Linus et al should send a cease and desist on use of Linux, lawyergrams, and licensing until the trial is up.

    3. Re:ANd how are they gonna enforce that? by MyHair · · Score: 1

      BRING OUT . . .

      the COMFY CHAIR!!

      POKE her with . . .

      the Fluffy Cushion!!

      NOooobody expects . . .
      The Spanish Inquisition!

    4. Re:ANd how are they gonna enforce that? by crazyphilman · · Score: 2, Funny

      Actually, that could be useful for those of us who have wood-burning stoves. My energy bill was HUGE this past winter. I wonder how many nastygrams we can get them to generate?

      --
      Farewell! It's been a fine buncha years!
    5. Re:ANd how are they gonna enforce that? by noldrin · · Score: 1

      Hopefully the lawyers will be smart enough to charge SCO on per copy of letter basis and not just once for writing it.

  4. Extortion by DrWho520 · · Score: 4, Insightful

    SCO will hold harmless commercial Linux customers that purchase a UnixWare license against any past copyright violations, and for any future use of Linux in a run-only, binary format.

    That's extortion...or some other form of legalese.

    --
    The cancel button is your friend. Do not hesitate to use it.
    1. Re:Extortion by Rogerborg · · Score: 4, Interesting

      It's also cretinous, because any "use" that involves duplication (including, let's see, installation from CD or network, or uploading or downloading or distributing externally or internally) will constitute a fat violation of the copy rights of every other contributor ot the kernel.

      There's a GPL exemption in the linux kernal for binary only Nvidia drivers. SCO has no such provision. If you cave in to these terms, expect to hear from other rights owners, each and every one of whom has as much claim as SCO.

      --
      If you were blocking sigs, you wouldn't have to read this.
    2. Re:Extortion by Vicegrip · · Score: 1

      It's interesting to see them perpetrate a violation of copyright by invoking copyright rights. As everyone knows and has been full well documented here, SCO gave up the right to impose this kind of binary-only exclusions when it distributed Linux previously under the GPL.

      This story is really just about more provocation from SCO and I am wondering if these actions are just manuvering to get IBM to make a mistake. I would be really interested to hear somebody with legal expertise give an opinion on why SCO is moving this way even without ever having received any manner of judgement in the case against IBM -- that is if it's anything more than what appears to be SCO obviously trying to keep media attention on its case because it has nothing to lose.

      --
      Do not spread "09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0" over the internet, thank you.
    3. Re:Extortion by Dr.+Manhattan · · Score: 3, Informative
      There's a GPL exemption in the linux kernal for binary only Nvidia drivers. SCO has no such provision.

      No, Linus has just stated that he won't pursue such violations of the GPL. But even that doesn't apply to SCO. No matter how you look at it, they're in GPL trouble.

      --
      PHEM - party like it's 1997-2003!
    4. Re:Extortion by gerf · · Score: 1

      I have a problem with people having to say "I am not a Lawyer" all the time. I don't care if you are a lawyer or not, you are a person.

      I like to think that a person can think for themselves. As a person who can think for themselves, i can make decisions about what is right or wrong in this world. If i see something that is wrong, i will do what i can to see that it is justified. When i look at the laws that are passed lately, and the judgements comeing from our courts, i see a great wrong being done. I don't care about the fine print in some obscure copywright law that could insinuate that the founders of this nation would think in one way or another. I want what is right.

      People in general, and humanity are being trodden upon by money, politics, companies and government. What should be looked at, especially in this case, is whether the world in general would be a better place if SCO would own Linux (and could supposedly benefit research), or if Linux stayed free to all, and distributed in the way it was before (and thus benefitting the entire world's population, given they're looking for such an OS).

      What is the best answer, what will the judges choose? Sadly, I believe that they will look at arcane laws, and not set a precedence of their own. They won't look at waht is truly wrong or right in this world, but rather at facts that they have been taught: Previous court cases, and technicalities. The outlook is dismal my friends, but what are we to do?

    5. Re:Extortion by Rogerborg · · Score: 1

      Thanks for the correction, it's good to get these things exactly straight. Compare with Red Hat's non-licenses for their patents, for example.

      --
      If you were blocking sigs, you wouldn't have to read this.
    6. Re:Extortion by TedCheshireAcad · · Score: 1

      Ouch. We lose.

      ...hunts for win2k server install disc...

    7. Re:Extortion by Azureflare · · Score: 1
      I would say they have more claim than SCO. SCO hasn't even shown what code is undoubtedly copied from SysV code.

      Also, if SCO wants to argue that they own everything because it's a derivative of SysV, well, the only option is to take it to court. If it's found that SCO can own the derivatives, how relavent is the GPL? Does that nullify the ownage of derivative works, or does it nullify the GPL? SCO seems to think it nullifies the GPL.

      This really needs to be decided by a knowledgable judge, and needs to be taken care of quickly, before SCO can bully businesses into paying them for false licenses, without telling people what they are buying the license for (besides protection), until a decision is made.

    8. Re:Extortion by wfberg · · Score: 1

      SCO will hold harmless commercial Linux customers that purchase a UnixWare license against any past copyright violations, and for any future use of Linux in a run-only, binary format.

      That's extortion...or some other form of legalese.

      Racketeering.

      --
      SCO employee? Check out the bounty
    9. Re:Extortion by virtual_mps · · Score: 3, Informative
      That's extortion...or some other form of legalese.

      I believe the term for SCO's actions is "barratry".
    10. Re:Extortion by MyHair · · Score: 1

      I am also speaking out of my ass, but I believe the kernel interface is open source, but the Nvidia specific portions are binary.

      However I'm not sure because I buy ATI since there are open source drivers available for SCO/Linux. (SCO/Linux...that'll be the day...)

    11. Re:Extortion by CaptainFrito · · Score: 1
      Actually, it's a form of terrorism.

      Pure Mafioso: "Look, Mr Small Shop Owner, pay me and no one will break your windows or your legs. If you don't, we'll break them."

      Rather similar to the IRS' value proposition too.

    12. Re:Extortion by tomhudson · · Score: 1
      SCO will hold harmless commercial Linux customers that purchase a UnixWare license against any past copyright violations, and for any future use of Linux in a run-only, binary format. How can SCO hold you harmless for their copyright violations of the GPL, which their plan clearly violates?
  5. Class Action Lawsuit? by TWX · · Score: 5, Insightful

    Isn't about time that we as Linux users file a class action lawsuit against SCO for misuse of Linux source? If we demonstrate kernel source commits that date back far enough to show that SCO has known for quite a while that they were selling and distributing Linux with the code that they claim is a problem (and all System V code should not be available from the copyright office since it's been filed) that we would be able to demonstrate failure on their part as a business to properly handle their IP, and to ask the court to release it to the public domain?

    --
    Do not look into laser with remaining eye.
    1. Re:Class Action Lawsuit? by Syberghost · · Score: 5, Insightful

      Isn't about time that we as Linux users file a class action lawsuit against SCO for misuse of Linux source?

      Excellent idea. To what portion of the code do you hold a copyright, and how many million US dollars are you pledging?

    2. Re:Class Action Lawsuit? by flamingantichimp · · Score: 1

      Not a bad idea, but we're techies. We are too lazy.

    3. Re:Class Action Lawsuit? by TWX · · Score: 1

      well, I am a legally licensed user of the Linux source code according to the GPL. That license predates SCO's copyright filing by many years. My rights as a consumer are being tread upon.

      --
      Do not look into laser with remaining eye.
    4. Re:Class Action Lawsuit? by Hiro+Antagonist · · Score: 0, Troll

      120 characters is too few to say anything funny with a link in it.

      No it's not:

      <a href="http://goatse.cx">IRS Audit Survivors</a>

      (Sorry, couldn't resist).

      --

      --
      I Hit the Karma Cap, and All I Got Was This Lousy .sig.
    5. Re:Class Action Lawsuit? by GoofyBoy · · Score: 1

      Apparently we are not lazy enough to press the Submit button here on Slashdot.

      But really, if anyone was serious about this, they would get a lawyer and just go ahead and do it.

      Its the different between "shooting your mouth off" and actually standing up for something. Unless you think that surfing the web is much more important than protecting your rights.

      --
      The surprise isn't how often we make bad choices; the surprise is how seldom they defeat us.
    6. Re:Class Action Lawsuit? by Anonymous Coward · · Score: 0

      How bout we file a class action law suit against TWX for being a complete MORON who just ended up on my foes list?

    7. Re:Class Action Lawsuit? by axxackall · · Score: 1

      That's right, it's called "evolution": more lazy will die, more aggressive will survive.

      --

      Less is more !
    8. Re:Class Action Lawsuit? by Syberghost · · Score: 1

      well, I am a legally licensed user of the Linux source code according to the GPL. That license predates SCO's copyright filing by many years.

      SCO is alledging, and attempting to prove in court, that the Linux developers didn't have a right to some of that code, and thus can't legally GPL it.

      Assuming they're correct, they have an absolute legal right to do this. You won't get anywhere suing for your rights to use a product you obtained illegally.

      Assuming they're not correct, they still have a legal right to do this, if there case has even a little merit and isn't judged by the court to be a deliberate abuse of process.

      If they are guilty of abusing the courts, you STILL don't have a case against them, because they haven't deprived you of anything.

      If you want to sue somebody, sue the vendor who sold you your copy of Linux, assuming you bought it. If not, you got free shit and you might have to lose it. Cry me a river.

      Now, if you wrote CODE that's in the kernel, it's a different deal. You have all kinds of standing here to make SCO's life suck. They may be violating YOUR copyright.

    9. Re:Class Action Lawsuit? by TedCheshireAcad · · Score: 1

      Not to mention passive/agressive.

      Set up a Yahoo shop and sell lawsuits against SCO for $19.99. Accept credit card/paypal/personal check.

      You'd be the Ron Popeil of the tech world.

    10. Re:Class Action Lawsuit? by Anonymous Coward · · Score: 0

      The code that was stuffed into your "GPL Legal" linux source code was stolen.

      That's a very strong allegation. Please back it up with proof. Note that failure to do so can result in libel charges.

    11. Re:Class Action Lawsuit? by Anonymous Coward · · Score: 0

      Show us the code. Can't? Then shut up, fuckface.

    12. Re:Class Action Lawsuit? by Anonymous Coward · · Score: 0

      Youi're presupposing SCO is right and their code was, in fact, copied into Linux. It is astronomically more likely that Linux code was copied into SCO.

    13. Re:Class Action Lawsuit? by Anonymous Coward · · Score: 0, Flamebait
      The thing that is keeping you Linux users from filing a lawsuit is that you are all acutely aware that filing a lawsuit means that eventually you will have to go to court to defend it. This creates the following problems:

      Going to court requires that you will have to leave the comfort of your moms basement, and the sudden contact with sunlight will ruin your pasty-white complexion

      There is a fairly good chance that during the course of litigation you will come in contact with a "real" girl (not pictures of Natalie Portman downloaded from the 'net). Of course, your deepest, darkest fear is that the judge would be a female, in which you would suffer extreeme humiliation by wetting yourself in the courtroom when she addresses you by name.

      Time in the courtroom means time away from your PC trying to get your soundcard to work with kernel 2.6.5.12.44.125.68.

      If the trial goes to a jury, you realize that a jury will usually not side with somebody with greasy, clumpy hair and cheetos stained fingers, especially when they don't change their clothes throughout the course of the entire trial.

    14. Re:Class Action Lawsuit? by geomon · · Score: 1

      The code that was stuffed into your "GPL Legal" linux source code was stolen.

      Well, we all know McBride's handle now!

      You have, of course, proven that allegation in a US court, right?

      You can believe in magic faeries if you want, if that helps rationalize where all the code magically came from.

      Actually, the kernel development process has been remarkably well documented. The process operates like nearly all scientific studies in that information is published only after significant peer review. The entire Linux kernel tree is documented in one form or another all the way back to the first lines contributed by Linus.

      The process has been conducted in the open, with the whole world watching.

      What part do you claim was magically produced and what parts are stolen code?

      Head over to kernel.org to see the entire tree back to pre-1.0. I have a 0.99 version lying about somewhere in my library I could post on an FTP site for you copy.

      So, Mr. McBride, put up or shut up.

      --
      "Rocky Rococo, at your cervix!"
    15. Re:Class Action Lawsuit? by Error27 · · Score: 1

      In 2.4, I wrote a couple lines of documentation. That's got to be worth a couple hundred grand by SCO calculations.

      I'd pledge all my winings...

    16. Re:Class Action Lawsuit? by oogoliegoogolie · · Score: 1

      they have an absolute legal right to do this.
      they still have a legal right to do this,

      America. The only country in the world where suing someone is a right.

      Whatever happened to good judgement, fairness, and common sense?

    17. Re:Class Action Lawsuit? by GnrcMan · · Score: 1

      Well, while I agree with the fact that SCO's attack on Linux is unfounded and wrongheaded, the specific arguement that they improperly handled their IP doesn't work. IIRc, copyright is a little different from trademark law in that with trademark law, if you fail to enforce your trademark, you might lose the trademark. On the other hand, with copyrights or patents, you can arbitrarily (and suddenly) decide to start enforcing your copyright/trademark. Of course, IANAL, but this is the way I've interpretted IP law.

    18. Re:Class Action Lawsuit? by nimblebrain · · Score: 1

      For an instructive comparison, take a look at the recent DirecTV fiasco and the class action suit going on in relation to it.

      I'm sure there are loads of actual pirates getting swept up in that 'sting', but a number of dolphins are getting caught up in the tuna net.

      The thing that I found interesting (especially in light of the use of words in this forum such as extortion, barratry and racketeering) was that they've settled on extortion as the grounds for the suit.

      If the circumstances are similar here, you'd have to be served a threat by SCO and pay the money to be a plaintiff in a class action suit. They'd be fair targets then, but of course the dire projections of SCO's demise (likely true if their company's inflated skin is as thin as it seems to be) makes a class action suit moot... right at the point where we'd have muscle as end users.

      Of course, most of us don't have a clue about how one would go about sitting down, making the calls, making the case, etc. I think we need an FAQ from someone wise in the way of the courts :)

      There's plenty of precedent for class action suits against copyright offenders, but I don't think any kernel contributor wants their life turned upside-down, no matter how noble the cause. Would they be able just to be 'named plaintiffs' in a suit that's pretty hard to attach hard damages to?

      --
      Binary geeks can count to 1,023 on their fingers :)
    19. Re:Class Action Lawsuit? by Syberghost · · Score: 1

      America. The only country in the world where suing someone is a right.

      That's correct. Defined in the First Amendment, the same one that protects the rights of free speech, freedom of religion, free press, and freedom to peaceably assemble. Most countries don't have those, either. A rather remarkable amendment.

  6. whats the delay? by peterprior · · Score: 5, Insightful

    What is the delay in getting SCO to court with IBM so they actually have to SHOW US what they are claiming violates their contract with IBM and / or their IP ?

    IANAL, so I might be missing something here, but the sooner they go to court, the better imho, else they will keep pumping out FUD and hyping their stock price.

    1. Re:whats the delay? by fwr · · Score: 1

      I believe, but do not know because IANAL, that non-criminal cases (i.e, arguments between companies as opposed to locking someone up for years) are given a much lower priority than criminal cases. This is because of due process and the right to a speedy trial. If someone accuses you of some criminal act even today, you will likely see trial before SCO and IBM do.

    2. Re:whats the delay? by eddy · · Score: 2, Insightful

      "Linux users also will not get clarity from the courts soon. SCO's Stowell said the Utah court is not scheduled to hear the company's application for a permanent injunction to stop IBM from shipping AIX until 2005." -- eweek.

      "Carey said this indicates that SCO's strategy is to let "the pot simmer for years and let people get increasingly worried about the legal risk."

      More like it's their way to pump'n'dump the stock to make thousands on insider trades. Fucking scumbags.

      --
      Belief is the currency of delusion.
    3. Re:whats the delay? by CharlieG · · Score: 1

      2 things are probably holding it up

      The first, as other folks said, is that the courts move slowly in this kind of dispute

      The second is that the lawyers move slower. Remember, they get paid by the hour. Every legal tactic they use that delays the case makes them more money. There was a study done here in NYC that showed that lawyers make cases go slower, depending on how much monry they can get

      --
      -- 73 de KG2V For the Children - RKBA! "You are what you do when it counts" - the Masso
    4. Re:whats the delay? by Johann · · Score: 1

      If it will take a long time, I wonder why IBM has not said more about the case?

      --
      "You're gonna need a bigger boat." - Chief Brody
    5. Re:whats the delay? by axxackall · · Score: 1

      If I would die because SCO practice destroys my personal consulting business as of a Linux expert, then will this case become a criminal one?

      --

      Less is more !
    6. Re:whats the delay? by fwr · · Score: 1

      Yes, but you would actually have to die first, and the DA for whatever city/state you are in would have to agree to press charges believing that they would win without a reasonable doubt.

      Hey, I don't necessarily like it, that's just the way the system works.

    7. Re:whats the delay? by Lussarn · · Score: 1


      What is the delay in getting SCO to court with IBM so they actually have to SHOW US what they are claiming violates their contract with IBM and / or their IP


      First they need to raise some cash to take on IBM. Thats what they are doing with this Unixware licence thingy. Will probably take a while.

    8. Re:whats the delay? by Zathrus · · Score: 1

      Because all statements regarding this case are legally admissible in court.

      IBM is not stupid enough to make statements outside of court prior to the first hearing. The last thing they want to do is get their defense caught up on some point based on a statement made a couple years prior.

      SCO doesn't appear to get this little issue though... which is why there's a lot of questioning about just how valid their case is in the first place.

    9. Re:whats the delay? by idlethought · · Score: 1

      Thats- Fucking SCOmbags

    10. Re:whats the delay? by gidds · · Score: 1
      the sooner they go to court, the better

      ...for us. So of course they're going to spin this one out as long as they possibly can. Come on, you can't be naive enough to think that they're not going to capitalise on the fear, uncertainty and doubt they're generating for a long as humanly possible?

      If/when this gets to court, no-one's quite sure what will happen. (There have been lots of arguments that they won't have a single limb to stand on, but I haven't seen any genuine legal advice, and of course in the long run the only arguments that matter will be those made in court.)

      But until then, it's quite obvious what's happening: as long as they can claim to 'own' Linux, however implausibly, then some corporate users will get nervous. Some are likely to pay up in the full knowledge that the claim's probably not valid, just to cover themselves. And, in the now-traditional step 3, SCO will profit. Right now it doesn't matter that there might be no truth at all in any of those claims; what matters is simply whether SCO can scare people into thinking there's even a tiny a chance there might be.

      SCO must know full well that as soon as they identify the questionable code, even if it's completely kosher, a week or two later we could have rewritten it and be (supposedly) safe. That's why they won't identify it for as long as possible, probably not until it gets to court. Again, it doesn't matter that this looks bad for them in court; they seem interested only in delaying that stage for as long as possible and extracting the most cash from nervous CTOs until then.

      BTW, maybe someone can answer a few questions: why is this copyright award a big surprise? Weren't we sure of the copyright situation before now? And if the award is genuine, what does that mean for Linux? Or the BSDs?

      --

      Ceterum censeo subscriptionem esse delendam.

    11. Re:whats the delay? by Johann · · Score: 1
      "Unless the case is settled, a resolution of the matters in the suit will not come soon. The trial is not scheduled to begin in a federal court until April 2005."

      NY Times

      --
      "You're gonna need a bigger boat." - Chief Brody
  7. How much does that change? by no+toys+in+the+attic · · Score: 1

    Does having a copyright of the code that contains the lines supposedly stolen by IBM boost their case at all? It doesn't seem like it, as the issue is not whether they own the code but whether IBM copied it line by line or not. Also, their moves to contact companies currently using Linux sounds like a very RIAA business measure to take.

    1. Re:How much does that change? by richg74 · · Score: 1
      Does having a copyright of the code that contains the lines supposedly stolen by IBM boost their case at all?

      If the code was added as recently as they claimed in today's teleconference (between kernels 2.2.x and 2.4.x), then I don't think that registering the copyright gives them any significant additional legal rights. As I understand it (and David Boies has just said this in the teleconference), registration is a necessary legal formality required before a lawsuit can be filed.

      I'm in the DC area, so I plan to call the Copyright Office this afternoon -- I think that what was copyrighted is now a matter of public record. (That wouldn't mean you could copy it, but that you could look at it.)

    2. Re:How much does that change? by Jeremy+Erwin · · Score: 1

      Copyright registration is a legal formality. It allows the holder to pursue a copyright infringement claim in US courts. If a copyright is registered within 90 days of publication, or prior to an alleged infringement, the holder is eligible for an additional award of legal fees.
      Source

  8. According to a letter to Linux Magazine .... by scharkalvin · · Score: 5, Interesting

    One reader of Linux magazine (not me) expressed the idea that the reason for SCO's recent stock rise was NOT that the market thinks they will win this lawsuit, but because someone has been quietly buying up their stock in advance of a hostile take over. That someone would be IBM, and McBride and his deatheaters will find themselves kicked out without a golden parachute. We can only hope!

    1. Re:According to a letter to Linux Magazine .... by Lawrence_Bird · · Score: 5, Informative

      yes and once they reach 5% they have to file with the SEC so doubtful this is what has happened.

    2. Re:According to a letter to Linux Magazine .... by jas79 · · Score: 1, Redundant

      That isn't very likely. If IBM owned a significant percentage of the stock they would be forced to report that to the SEC.

    3. Re:According to a letter to Linux Magazine .... by Dr.+Manhattan · · Score: 5, Funny
      McBride and his deatheaters will find themselves kicked out without a golden parachute.

      Actually, a parachute made of gold, lead, or any other heavy metal would be fine. Just so long as they're kicked out from 8km or higher.

      --
      PHEM - party like it's 1997-2003!
    4. Re:According to a letter to Linux Magazine .... by Johann · · Score: 1
      deatheaters will find themselves kicked out without a golden parachute.

      Alas, if it were only that simple. See, when you're a CEO type (even the reprehensible type like Sr. McBride) you have an employment contract. Typically, those contracts include the amount of the 'golden parachute'.

      If another company were to buy SCO, they accept the liability of all *existing* SCO employment contracts as part of the takeover. The new company could tell Sr. McBride to get bent, but he would have a *valid* cliam to get what his contract specified (plus damages). The rationale is that from the employees point of view, he is owed what's in his contract whether or not the company ownership changes hands.

      Really, the only way you could screw him is *not* fire him, but demote him to IBM executive shoe shiner and force him to quit. Wouldn't that be nice?

      --
      "You're gonna need a bigger boat." - Chief Brody
    5. Re:According to a letter to Linux Magazine .... by mhore · · Score: 1
      Actually, a parachute made of gold, lead, or any other heavy metal would be fine

      Whoa! Heavy Metal!!!! *head bang*

      --

      Mmmm......sacrelicious.

    6. Re:According to a letter to Linux Magazine .... by cmburns69 · · Score: 2, Funny

      Unless its not IBM as a company, but many of the CEOs of companies who have been threatened by SCO (not purchased by companies, but individuals). They all must have an agreement to not purchase over 5% appiece, and then all at once their plans will be revealed!

      The illuminati strike again!

      --
      Online Starcraft RPG? At
      Dietary fiber is like asynchronous IO-- Non-blocking!
    7. Re:According to a letter to Linux Magazine .... by Jeremiah+Blatz · · Score: 1

      AFAIK, they can declare the filings "sensitive" and they don't go public for a year.

    8. Re:According to a letter to Linux Magazine .... by Anonymous Coward · · Score: 0

      I think you're missing something... The more likely version of events is something like this:

      The board grants themselves options.
      They make noise and sue IBM.
      They cash out 10,000 shares at a time.
      When volume slows down, they make more noise to keep the volume up.
      When insiders (including parent companies, the VC company, etc...) have sold off sufficient amounts of stock, they drop the suit. Stock plunges from whatever to $.10. SCO folds up and dies. Insiders are rich at the expense of all the suckers out there in Wall Street land...

      (I should stress that this is only speculation and not based on any current facts or is anything other then my personal views and in no way reflects upon anyone else or my employeer or the like, yaddie yaddie yaddie... check the SEC filings and draw your own conclusions.)

    9. Re:According to a letter to Linux Magazine .... by pclminion · · Score: 1
      Just so long as they're kicked out from 8km or higher.

      I assume that's to ensure that they die a slow, wheezing, oxygen-deprived death, instead of a painless sudden-impact death? (8 km is considered the beginning of the "death zone" for high altitude mountaineering.)

    10. Re:According to a letter to Linux Magazine .... by Tokerat · · Score: 1


      I'd prefer if McBride and his cronies where found guilty of insider trading and had to pay everyone back they extorted money from, release a statement admitting Linux is just fine and then rot in jail for the rest of their days.

      --
      CAn'T CompreHend SARcaSm?
    11. Re:According to a letter to Linux Magazine .... by SoTuA · · Score: 1

      Then there's the perfectly legal way of buying through proxies, each buying 4%... then approach the victim with all the consolidated holding. (one too many wall street thrillers read... :)

    12. Re:According to a letter to Linux Magazine .... by gmhowell · · Score: 1

      One of my profs when getting my MBA used to work at IBM. He regaled us with a tale of a division he worked for. Seemed that it was too expensive for a couple of engineers to be fired. But it was too expensive to keep them around. Someone decided to put them in empty cubicles in some basement somewhere. And their job was to sit there. Eight hours per day, five days per week. Didn't have phones, no computers, nothing. Newspapers, magazines, books, not allowed. Apparantly, 95% of the guys quit within two weeks.

      Unfortunately, these guys were engineers. An executive (particularly with an MBA) would have no trouble being this sedentary and collecting a paycheck.

      --
      Jesus was all right but his disciples were thick and ordinary. -John Lennon
    13. Re:According to a letter to Linux Magazine .... by Mostly+a+lurker · · Score: 1
      The reason for the stock rise is that, for the time being, more people expect the price to continue to increase than expect it to fall. Actually, I think that is a reasonable assessment. Until the lawsuit reaches court, in perhaps two years or so, it is hard to see what can happen to completely debunk SCO's claims. In the meantime, some organisations are going to be dumn enough to cave in to SCO's demand for protection money.

      Personally, I think the chance of a buyout by a wealthy company is very unlikely. SCO has made some outrageous claims. Eventually, there are going to be counterclaims by numerous organisations and individuals that have been directly damaged as a result of those claims. If SCO were actually to win, then a buyout would make sense. With SCO likely (nearly certain?) to lose, any buyout by a rich suiter at this stage would be pure folly. Actually, if SCO had a real case, Microsoft would have snapped SCO up before SCO started making these claims when the risks would have been much lower.

  9. Hello, SCO? by Chris+Hiner · · Score: 5, Insightful

    I'd like to know what code I'm licensing. Yes, I'd like to know what lines...

    So, if I take those lines out, I don't need a license from you? Thanks.

    1. Re:Hello, SCO? by Rogerborg · · Score: 5, Insightful

      How about if you replace them with the identical lines from SCO's own distribution, clearly licensed under the GPL and distributed for year after year, including after the point where they began filing suits?

      --
      If you were blocking sigs, you wouldn't have to read this.
    2. Re:Hello, SCO? by kevin+lyda · · Score: 1

      this is an excellent idea. i think some states require a seller to fully disclose what they are selling. the key is to find such a state, buy a unixware license for linux and then sue sco for non-disclosure.

      --
      US Citizen living abroad? Register to vote!
    3. Re:Hello, SCO? by axxackall · · Score: 2, Interesting
      from the article:

      Hundreds of files of misappropriated UNIX source code and derivative UNIX code have been contributed to Linux in a variety of areas, including multi-processing capabilities. The Linux 2.2.x kernel was able to scale to 2-4 processors. With Linux 2.4.x and the 2.5.x development kernel, Linux now scales to 32 and 64 processors through the addition of advanced Symmetrical Multi-Processing (SMP) capabilities taken from UNIX System V and derivative works, in violation of SCO's contract agreements and copyrights.

      I wonder if someone from LKML is already working on digging the original source of those commits. I don't believe they will find out the stolen code, but who knows, maybe SCO has already digged there. Otherwise why are they so comfortable? From the other point why IBM is so comfortable too? Or is it just a poker-bluffing game on both sides?

      --

      Less is more !
    4. Re:Hello, SCO? by axxackall · · Score: 1
      "For several months, SCO has focused primarily on IBM's alleged UNIX contract violations and misappropriation of UNIX source code," said Darl McBride, president and CEO, The SCO Group. "Today, we're stating that the alleged actions of IBM and others have caused customers to use a tainted product at SCO's expense. With more than 2.4 million Linux servers running our software, and thousands more running Linux every day, we expect SCO to be compensated for the benefits realized by tens of thousands of customers. Though we possess broad legal rights, we plan to use these carefully and judiciously."

      I know, it is weird to answer to myself, but on a second thought, after longer thinking upon the next paragraph (see above) I came to the conclusion that SCO actually used (bride?) some people from inside IBM to submit that code planning to create such a case in future.

      --

      Less is more !
    5. Re:Hello, SCO? by Darth_Burrito · · Score: 1

      I was under the impression that the license was a binary license or maybe just exemption from the lawsuit machine. Either way, you'd have a hard time twisting that into a way to view the eledgedly infringing lines.

    6. Re:Hello, SCO? by Anonymous Coward · · Score: 0

      Well, If you have recieved the code from their distro, licensed BY SCO under the GPL, then they you have an SCO license (GPL) to use that code and give it to friends, family, or give it to the community (It's GPL after all).

    7. Re:Hello, SCO? by Exousia · · Score: 1

      McBride disputed the GPL issue. He claims that the copyright law requires a "signing away" of rights, and thus GPL is not enforcable. I guess we shall we about that.

      --

      --Slashdot: News for Turds. Stuff that Splatters.
    8. Re:Hello, SCO? by Arker · · Score: 1

      The Linux 2.2.x kernel was able to scale to 2-4 processors. With Linux 2.4.x and the 2.5.x development kernel, Linux now scales to 32 and 64 processors through the addition of advanced Symmetrical Multi-Processing (SMP) capabilities taken from UNIX System V and derivative works, in violation of SCO's contract agreements and copyrights.

      The derivative works thing here is key. SysV doesn't have SMP worth stealing, none of SCOs crap does. They try to FUD like it did, of course, but it's nonsense, Linux has always been better at SMP than Unixware or OpenServer or whatever they're calling it now.

      So clearly what they're planning to actually argue in court is that they own AIX! Not just the SysV code that IBM licensed more for the name than anything else (there's very little SysV in AIX or any other commercial Unix, outside of SCO - the other vendors added plenty, like SMP and NUMA, and rewrote most of what was there to begin with, because it sucked.) Now that's some balls, that really is. IBM is going to so clean their clocks when this gets to court.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    9. Re:Hello, SCO? by axxackall · · Score: 1

      Hold on. A derivated work from GPLized software is under GPL. Is a derivated work from SysV software still under Unix copyrights? In other words, is Unix license "viral" in a same way as GPL is?

      --

      Less is more !
    10. Re:Hello, SCO? by Arker · · Score: 2, Insightful

      Well I suppose that's going to be the crux of the case, if and when this ever gets to court. It looks like SCO is going to claim it is, and that they own everything every Unix vendor has ever made. IBM has a little different reading of the contract.

      Either way, frankly, their linux licensing crap is not just a joke, it's flat out illegal. Even if SCO were somehow to miraculously turn out to have a case against IBM, that doesn't translate into owning Linux. Every 'binary only runtime license' they sell is another case of copyright infringement, of 'software piracy' as it's usually phrased. Even if IBM violated their contract with SCO, that wouldn't give SCO a license to violate their contract with the Linux hackers and others whose work they've been, and still to this day are, distributing. At worst, they'd have to tell the kernel people what lines, exactly, IBM contributed improperly and then they'd work around it and fix the problem.

      Now this is where SCOs claims go beyond just bizaare and improbable to downright twilight zone. They appear to also be claiming that linux itself, not just the parts that IBM allegedly contributed improperly, belongs to SCO too! That an independent work-alike, written from scratch to conform to publically known specifications by people with no contractual obligations to SCO whatsoever, is STILL a derivative work!

      Their arrogance knows no bounds. Let's hope their ability to bribe judges is more modest. That's the only way such a bizaare theory could ever be upheld in a court of law.

      I still don't believe they intend to ever see this to trial though. Their actions just aren't consistent with such a brazen plan. I think they know they haven't a case, against IBM or anyone else, but they hope if they make enough of a stink they can dump their stock for overinflated prices before everyone figures out what they're up to.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
  10. Do I read this right? by Albanach · · Score: 4, Interesting
    They claim that some of their code made its way into the Linux Kernel, so now they're packaging the entire kernel, making it only available in bianry form and selling it?!?

    If anyone has been waiting to test the GPL in court surely now's the time to set up a fighting fund - everyone who's contributed to the kernel is today seing their hard work being stolen, exploited and sold by SCO.

    1. Re:Do I read this right? by Coward+the+Anonymous · · Score: 1

      "They claim that some of their code made its way into the Linux Kernel, so now they're packaging the entire kernel, making it only available in bianry form and selling it?!?"

      No, they are not packaging and selling the kernel in binary form. They are offering a binary only license for UnixWare. This license is supposed to cover the alleged portions of UNIX code in Linux, allowing corporations to legally use the alleged misappropriated UNIX code in Linux.

      --
      -- Jason
    2. Re:Do I read this right? by DShard · · Score: 1

      I think it is also time to test fraudulent claims. I think this could be considered advertising and the claim that sysv contained SMP which as I understand it is strictly NOT true. Claiming that their IP covers that and the can sell you those capabilities is false advertising. From here on out I am going to ignore these articles as the just serve to get the blood all angried up.

    3. Re:Do I read this right? by ajs · · Score: 5, Insightful

      No you mis-read. They're offering a license for the binary, not the binary. If they do, in fact, offer the binary itself, then they are violating the GPL by now also distributing source.

      If, on the other hand they say, "your existing license is invalid, here have another." Then they are in the right. They cannot license the GPLed pieces, but that's fine. You can demonstrate that you received those pieces under the GPL.

      It's an ugly use of the GPL, and companies like Red Hat will be 100% screwed by this.

      That's ok, though, because the current odds on SCO winning this case are somewhere around the odds of the Red Sox winning the Superbowl right after the Triple Crown ;-)

      Repeat after me: You can't distribute Linux for 2 months under the GPL *after* claiming it contains your code, and *then* remove it from distribution. It's out there. It's GPLed. They're done. All they have left is a contractual dispute with IBM that affects no one by IBM and SCO.

      Oh, and by the way IBM is likely to win that one too.

    4. Re:Do I read this right? by Jahf · · Score: 1

      They claim that some of their code made its way into the Linux Kernel, so now they're packaging the entire kernel, making it only available in bianry form and selling it?!?


      Umm, no ... they are selling a binary -license- for UnixWare, which covers the copyrighted code in the Linux kernel. They are not redistributing a binary version of the kernel, only a license that covers what they are claiming is infringing code. You still get the kernel from your distribution of choice and/or from kernel.org.

      They are not selling the kernel, they are just selling you a license to use the kernel. The copyright validity and order of introduction into the kernel still hasn't been proven or disproven. Therefore there is no GPL test at this point.

      If the code is proven to belong to SCO it may very well break the GPL-ness of the kernel until such time as all possible derivatives have been removed and even then there will be problems. If the code in the kernel is proven to be untainted, then there will be no GPL test (but there will be a lot of pissed off licensees). The only way this could be a GPL test would be for the code in UnixWare to be proven to have come from Linux ... a LONG shot for sure but if so it would cause at least part of UnixWare to be GPLed. Extremely doubtful.

      --
      It is more productive to voice thoughtful opinions (reply) than to judge (moderate) others.
    5. Re:Do I read this right? by ajs · · Score: 2, Informative

      correction to my text: "by *not* offering source"

      "now" was a typo.

    6. Re:Do I read this right? by Phroggy · · Score: 5, Insightful

      No - SCO isn't packaging and selling the kernel. SCO is selling a license allowing users to USE a (precompiled binary) Linux kernel, which (according to SCO) contains SCO's proprietary code.

      Distributing said kernel (by anyone including ftp.kernel.org) is apparently illegal if SCO's copyright claims are correct (which they aren't). SCO cannot sell a license allowing the Linux kernel to be distributed unless said license was compatible with the GPL (which it wouldn't be).

      If SCO's copyright claims are correct, it is illegal for anyone except the copyright holders (all of them, including SCO, together as a group) to distribute copies of the Linux kernel - copyright law prohibits this (just like it prohibits distribution of copies of Windows XP by anyone other than Microsoft), and the GPL would be void (because SCO's part of the code isn't licensed by the copyright holder under a GPL-compatible license).

      IANAL; somebody correct me.

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
    7. Re:Do I read this right? by Gzip+Christ · · Score: 0
      Repeat after me: You can't distribute Linux for 2 months under the GPL *after* claiming it contains your code, and *then* remove it from distribution.
      Remove it? Hah! They are still distributing the source! They are such dispicable liars to say that they stopped. They know full well they are still distributing it.
    8. Re:Do I read this right? by 73939133 · · Score: 1

      If, on the other hand they say, "your existing license is invalid, here have another." Then they are in the right.

      But even if SCO owned bits and pieces of the current Linux kernel, the result would simply be that nobody could redistribute Linux anymore until SCO's pieces are removed. Furthermore, if they ever went to court over license violations, they'd actually have to disclose what parts of the Linux kernel violate their intellectual property, which means that they can be removed. So, that still means SCO can't make a business out of selling licenses to Linux.

    9. Re:Do I read this right? by Martigan80 · · Score: 1

      They claim that some of their code made its way into the Linux Kernel, so now they're packaging the entire kernel, making it only available in bianry form and selling it?!?

      I hope this does not happen! If it is possible to get away with this I would imagine MS would have a field day.

      --
      This SIG pulled due to lack of funding. (This damn war is costing too much!)
    10. Re:Do I read this right? by mcc · · Score: 2, Interesting

      If, on the other hand they say, "your existing license is invalid, here have another." Then they are in the right.

      Then never mind licensing for a momen. It seems to me that if they are explicitly saying "if you run linux you are in violation and need to buy a license from us", that is a libellous statement.

      It seems to me that the FSF, or Linus, or any major Linux vendor is now free to sue SCO, for either libel or barratry or whatever laws govern deceptive harrassment of your competitor's customers, at the least.

      In fact, I'm shocked they haven't already. I cannot imagine why the FSF and/or Redhat would stand by and let this happen. It made sense to just stand and wait when everything SCO did fell under the heading of making insinuatious about Linux while discussing their IBM case, but this is something of a wholly and totally different order. This is publicly making attacks on Linux itself, and publicly stating that (for example) Redhat does not have the legal right to sell their own product, and that if you buy a product from Redhat you owe SCO money. I can't imagine that's legal, and I'm certain it's damaging to Redhat.

      Why don't the linux distros just file suit, now that SCO has crossed the line, and subpeona what exactly the line numbers of these fabled bits of SCO code in the linux kernel are?

    11. Re:Do I read this right? by Svartalf · · Score: 1

      I am not a lawyer either...

      The problem lies not with other people using the Linux kernel- but rather SCO's distribution thereof. The GPL is not an EULA, it's a distribution and derivative works license- completely different beast.

      Since SCO claims that they didn't license the alleged code under the GPL, they distributed everyone else's code in violation of the terms of the GPL. SCO distributed, knowingly (and still WAS off of their FTP site as late as yesterday...) the IP of the Linux kernel with their IP intermingled with it. If SCO isn't willing to distribute the code in question under the GPL, they did not have the license to distribute the rest either.

      SCO is officially guilty of over seven months of IP infringement on the collected Copyrights on the Linux kernel.

      --
      I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
    12. Re:Do I read this right? by Crispy+Critters · · Score: 1
      "If, on the other hand they say, "your existing license is invalid, here have another." Then they are in the right."

      Yes yes yes! Pay attention people! This is a license for using the kernel, for running the code. The GPL has nothing to say about who can run the code; it is a distribution license, not a user license. If indeed the 2.4 Linux kernel contains stolen SCO code, then distribution of it is illegal. Period. The SCO part of the code can be used iff you have a license from SCO to do so.

      There is another wrinkle. If you buy a license, you are implicitly accepting that SCO owns rights to some of the kernel, and any copying or distribution of the kernel is illegal. Anyone who buys a SCO license and then downloads, installs, or distributes a copy of the kernel is committing an act which he has effectively admitted is illegal.

      Of course, SCO knowingly distributing the kernel with the GPL intact probably means the code isn't stolen, in which case SCO has no case and none of this applies.

    13. Re:Do I read this right? by Crispy+Critters · · Score: 1
      "Why don't the linux distros just file suit, now that SCO has crossed the line, and subpeona what exactly the line numbers of these fabled bits of SCO code in the linux kernel are?"

      My guess is that they are waiting for IBM to smash them first. IBM has the money and the lawyers to work on proving the facts of the case. Once these are proven, then distros etc. can go after SCO without have to prove what SCO did. All they would need to show is what loss they suffered. SCO would lose every such lawsuit almost automatically; the only question would be how bad.

    14. Re:Do I read this right? by dmaxwell · · Score: 1

      All SCO has really done up to this point is file a breach of contract suit against IBM and run their mouth a lot. The contract suit may be somewhat meritorious but IBM will still hand them their heads on a platter. SCO's diarrhea of the mouth is another kettle of fish altogether. There's easy to enforce laws against it in Germany and Poland at least but maybe not elsewhere.

      Yeah, I suppose RedHat may have a case at this point but they have to weigh the costs of suing SCO against what their mouth flapping is losing them. Basically, a company RH's size isn't going to sue over mere FUD. Once SCO starts actually mailing the nastygrams to RH's customers then the situation will change drastically. RH's customers paid money for what they believe is legal product and if RH wants to sell any more then they will have to do something "about those SCO guys that are hassling us" pronto.

      For now, the distros don't have much to gain by filing a suit. Once the distros' customers are getting pinched then they'll have to. This probably means that SCO will just run their mouth as long as possible without actually doing anything. It won't help their little pump-n-dump scheme once the countersuits start flying.

    15. Re:Do I read this right? by ajs · · Score: 1

      But even if SCO owned bits and pieces of the current Linux kernel, the result would simply be that nobody could redistribute Linux anymore until SCO's pieces are removed

      Well, no not really. If you receive a copyrighted work from a source that did not have the right to license it to you, you can claim that you didn't know. That means that you can't be sued for copyright violation (assuming that no one can prove you're lying). But you *are* required to "give it back" (in the case of software or other electronic works, that means deleting and sending back the media). It's not *your* distribution of it that is at question, it is *your vendor's* distribution to you. If that was not legit, then you cannot reasonably use the software.

      What SCO is saying (again, I'm not saying they're the good guys here) is that they will write you a license that says they won't come after *you* for failing to remove Linux (and thus their code) from your systems.

      Problems with SCO's claim are well documented, and I cannot imagine that they intend to win this, but they have every right to issue a license for their own work (if it is) and it would mean exactly what they claim it would mean in that case.

      You can't go check the GPL for confirmation of this. If SCO is right, and the code is not IBM's to have contributed, then indeed, it was not Linus' to distribute, nor SuSE, Red Hat, Debian, etc. That means that the GPL goes poof!, and no one but SCO's licensees can continue to *use* (not just distribute) this code, unless they got it from SCO.

      The catch (again, well documented elsewhere) is that we *all* got the code from SCO when they distributed it under the GPL for 2 months after they started this whole thing. When all is said and done, Linux code that SCO has claim over (if any) was put under the GPL by SCO *after* their claim was issued and made available from their FTP servers. They have no right to sue anyone on the basis of not having a license (though they could sue someone on the basis of violating the GPL, if they had).

      SCO is in for a world of hurt when the law suits come flowing in. Everything sits on IBM for the first step. SCO's only hope is that IBM settles, in which case all of the parties that are waiting to sue SCO would be at square zero in terms of having to demonstrate the facts. That would help SCO a bit, but I still think at least SCO stockholders will sue.

    16. Re:Do I read this right? by ajs · · Score: 1

      Interesting. Someone else had said that it was gone. I'm downloading that now to see if it mentions anything (if it's just a huge README file that says, "UnixWare rocks, Linux sucks" over and over).

    17. Re:Do I read this right? by ajs · · Score: 5, Interesting
      For those who are interested, and for posterity:
      Summary : Linux kernel sources and compiled kernel image.

      Copyright : GPL
      #Packager : Bishop Clark (LC957) <bishop@caldera.com>
      Packager : Ashish Kalra <ashishk@sco.com>
      URL : http://www.kernel.org/
      That was in the file linux.spec, in the distributed linux-2.4.13-21S.src.rpm , which was dated May 3 08:46. That was on their public FTP server, which I downloaded at Jul 21 16:05.

      On thier site, the timestamp on the SRPM file was 5/9/03 17:51:00

      Ammusingly enough, the first entry in the changelog is:
      * Wed May 02 2003 Varun Sethi <varuns@sco.com> 2.4.13-21
      - updated IBM ServeRAID 6.x drivers
      - erg712269
      - erg712288
      Also from the spec file. Heh, fixing an IBM RAID driver... oh, their prophetic souls.

      Inside the SRPM, I do not see anything that could indicate that SCO does not wish to distribute this code under the terms of the GPL. As such, I believe that I am now the owner of a SCO-issued license to use, distribute and modify Linux source code as of version 2.4.13 (the entire tar-file for that version is contained in SRPM as a discrete and separarable file which also contains a copy of the GPL).

      If you area a lawyer, and you read this, please speak up. I would like to know what my rights are here and to what extent I can re-distribute and modify this work in accordance with its stated license.

      SCO is speaking out of both sides of their mouth. They continue to support thier Linux customers with distributions of source code licensed under the GPL while saying that no one but they have the right to do so (staunchly ignoring the terms of their own licensing of the Linux soruce code). My head is spinning. Clearly there is a deck involved here, and it's not quite full. Is it mine?
    18. Re:Do I read this right? by lspd · · Score: 1

      It seems to me that the FSF, or Linus, or any major Linux vendor is now free to sue SCO, for either libel or barratry or whatever laws govern deceptive harrassment of your competitor's customers, at the least. In fact, I'm shocked they haven't already.

      I would expect that most of the folks with enough of a financial interest in this and the funds to see a lawsuit through are waiting for SCO to stop waffling and present their licensing plan. I don't buy the idea that SCO has been working out the details all this time. They're stalling...once they start demanding money instead of just talking about demanding money the lawsuits against SCO will start coming in.

      What do you think the odds are that six months from now SCO is STILL working on their licensing plan AND distributing the Linux kernel via their own ftp server?

    19. Re:Do I read this right? by HuffMeister · · Score: 1

      Actually, SCO is still packaging and distributing the kernel... See the plethora of links to their ftp servers which contain linux sources... The person you're replying to basically just said that since they're (knowingly) distributing code which they claim is infringing, that they're sore out of luck when it comes to IP claims on code that they're distributing for free...

    20. Re:Do I read this right? by Anonymous Coward · · Score: 0

      2.4.13-21S eh?

      Maybe this means 2.4.14 was the first version to contain the allegedly infringing code. All we need now is a diff between those two versions.

    21. Re:Do I read this right? by Anonymous Coward · · Score: 0

      Who exactly are Linus's customers? What are the qualifications to be classified as a customer? It's not clear that Linus has a business interest that can be damaged.

      Distributors like Redhat do have customers, but they don't actually own Linux, so it's not clear they are in a position to sue either.

    22. Re:Do I read this right? by 73939133 · · Score: 1

      Problems with SCO's claim are well documented, and I cannot imagine that they intend to win this, but they have every right to issue a license for their own work (if it is) and it would mean exactly what they claim it would mean in that case.
      [...]
      It's not *your* distribution of it that is at question, it is *your vendor's* distribution to you. If that was not legit, then you cannot reasonably use the software.


      Right. And my point is that if SCO can legitimately issue you a license on the code, then your vendor's (RedHat, etc.) distribution of Linux to you would not be legit under the GPL.

      So, SCO can't really make money off this: they could theoretically keep you from using Linux if they had intellectual property rights, but a business model where RedHat distributes Linux and you need an SCO license to actually run it simply does not work under the GPL because RedHat cannot distribute Linux under those conditions.

    23. Re:Do I read this right? by gotan · · Score: 1

      If, on the other hand they say, "your existing license is invalid, here have another." Then they are in the right.

      But anyone distributing code that needs to be licensed under the GPL isn't. It's impossible to combine code that has to be licensed for a fee with code that is GPLd (Section 2b of the GPL) and that also holds for SCO. So the only option is to see to it that all code in the Linux-kernel can be licensed under the GPL free of charge (either by removing some parts or by making them available under the GPL).

      Also unless they prove that Linux infringes on their copyright they are not in the right. Since their unwillingness to identify the infringing code stalls any efforts to remove that pieces they can't claim any damages until they identify the infringing code-parts.

      --
      "By the way if anyone here is in advertising or marketing... kill yourself." -- Bill Hicks
    24. Re:Do I read this right? by ajs · · Score: 1

      You're turning that inside out. Are you suggesting that Linus would sue Red Hat to get them to stop shipping the Linux kernel to their customers?! If not, then why would Red Hat's distribution of Linux to you be a problem? All SCO is saying is that if you pay them "protection" money, they won't sue you. That's really it.

    25. Re:Do I read this right? by 73939133 · · Score: 1

      Are you suggesting that Linus would sue Red Hat to get them to stop shipping the Linux kernel to their customers?!

      You bet: if SCO demonstrates that there is SCO copyrighted code in the Linux kernel, then they will have demonstrated that there is non-GPL'ed code in the Linux kernel. I fully expect that anybody, including RedHat, that knowingly ships the Linux kernel with non-GPL'ed code would get sued.

    26. Re:Do I read this right? by ajs · · Score: 1

      ... by whom?

      I really don't understand why you think that Linus is going to turn around and say, "you have no right to distribute SCO's code, stop or I'll sue."

      It's not like you hurt Linus by doing so (he can create and distribute a SCO-free version, after all). It doesn't hurt Linux.

      Now, if you try to use this as an EXCUSE to do something that the community would already be against (e.g. distributing a binary-only kernel), then I would not put it past Linus et al. to sue you for what they could have sued over without SCO's involvement. But that's a totally different issue, and has nothing to do with Red Hat shipping a source/binary version of Linux under the usual terms, that they got from Linus and then getting sued by Linus for it. I don't see that ever happening.

      It's all moot anyway, since SCO is still shipping Linux source from their public Web site, under the terms of the GPL. *They* have put the code under the GPL, so while IBM and SCO can duke out their contractual dispute, the impact to the Linux community is that we get a lot of free press.

    27. Re:Do I read this right? by xcreature · · Score: 1

      Wow, looks good to me. I'm going to get my copy of SCO Linux ASAP. ;) For the purposes of amusement: nerdcore.net [nerdcore.net]

  11. Re:There can be no doubt about it by fataugie · · Score: 1, Funny
    In other words

    The Streets will flow with the blood of the Non-Believers"

    --

    WTF? Over?

  12. After some thought by RiffRafff · · Score: 5, Insightful


    After careful thought and ethical consideration, I have come to a conclusion regarding my use of Linux and the SCO license. It is as follows:

    Mr. McBride, bite me.

    I will not submit to your extortion. I will, however, point it out to my Missouri Attorney State General, for his consideration. In fact, the RICO statute comes to mind.

    --
    "I might have made a tactical error in not going to a physician for 20 years." -- Warren Zevon
    1. Re:After some thought by Anonymous Coward · · Score: 0

      That's Ashcroft's old job, isn't it?

      Or was that dead body that got elected in 2000 the one who was the A.G.?

    2. Re:After some thought by stinky+wizzleteats · · Score: 1

      In fact, the RICO statute comes to mind.

      Please educate. I've been looking for a way to speak out effectively on this.

    3. Re:After some thought by RiffRafff · · Score: 4, Informative

      I'm hardly an expert, but RICO is sufficiently broad in its scope (the Feds made it that way on purpose) that it could probably be used against SCO. From this article (http://law.about.com/library/weekly/aa042202a.htm ) about RICO and priests,

      "Just exactly how does the RICO statute work? RICO requires that an "enterprise" be shown to exist. "Enterprise" is broadly defined to mean "any individual, partnership, corporation, association, or other legal entity, and any union or group of individuals associated in fact although not a legal entity." The broad definition was thought necessary to address the great variety of informal organized crime organizations and the control organized crime has over legitimate businesses.

      "For RICO to apply, the enterprise must be shown to have engaged in a "pattern of racketeering activity," which means that one must show at least two "acts of racketeering activity" over a period of ten years. An "act of racketeering activity" consists of one of a lengthy list of state and federal crimes. Note that the statute does not require conviction of an "act of racketeering activity" but only that the act have been committed.

      "The list of "acts of racketeering activity" includes crimes normally associated with organized crime such as murder, kidnaping, gambling, arson, robbery, bribery, extortion, and dealing in obscenity or drugs. However, the list also includes numerous, less heinous crimes. Well into the list one finds mail fraud and wire fraud. These statutes make it a criminal offense to use the mails or electronic communications in the commission of a crime.

      "When all the pieces are assembled, one can press a RICO claim by showing that a conspiracy existed among individuals or other organizations during which two telephone calls in furtherance of the conspiracy were made in ten years."

      OTOH, IANAL, so who knows?

      --
      "I might have made a tactical error in not going to a physician for 20 years." -- Warren Zevon
    4. Re:After some thought by RiffRafff · · Score: 2, Informative

      Yes, Ashcroft was AG for two terms. Also guv'ner from 1984 to 1993. Now, in the immortal words of ZZTop, "he's nationwide."

      Jay Nixon is the current Attorney General of Missouri.

      --
      "I might have made a tactical error in not going to a physician for 20 years." -- Warren Zevon
    5. Re:After some thought by Anonymous Coward · · Score: 0

      Let us also not forget....

      He lost his senate bid TO A DEAD MAN!

    6. Re:After some thought by hendridm · · Score: 1

      > I will not submit to your extortion. I will, however, point it out to my Missouri Attorney State General, for his consideration. In fact, the RICO statute comes to mind.

      Excellent! I just mailed my three letters on Saturday and it's good to see that others are taking suit. Perhaps I don't matter and you don't matter, but the Attournies General matter and might take a look at the case given enough requests.

    7. Re:After some thought by NecroPuppy · · Score: 1

      associated in fact although not a legal entity

      And since SCO is a legal entity, RICO doesn't apply to them.

      --
      I like you, Stuart. You're not like everyone else, here, at Slashdot.
    8. Re:After some thought by limbostar · · Score: 1

      Read the whole clause again.

      "any individual, partnership, corporation, association, or other legal entity, and any union or group of individuals associated in fact although not a legal entity."

      Any legal entity or associated group of people, even if they're not a legal entity.

      --
      this is a sig.
    9. Re:After some thought by tiny69 · · Score: 2, Insightful
      RICO requires that an "enterprise" be shown to exist. "Enterprise" is broadly defined to mean "any individual, partnership, corporation, association, or other legal entity, and any union or group of individuals associated in fact although not a legal entity."
      Yes it does. Rambus was facing the possibility of RICO charges at one point.
      --
      Go not unto/. for advice, for you will be told both yea and nay (but have nothing to do with the question)
    10. Re:After some thought by NecroPuppy · · Score: 1

      Right... saw the end, parsed the whole thing wrong.

      See my .sig for possible reasons. :P

      --
      I like you, Stuart. You're not like everyone else, here, at Slashdot.
    11. Re:After some thought by Anonymous Coward · · Score: 0

      OT, but technically Ashcroft lost his senate bid to the dead man's widow. More than likely, she got quite a bit of sympathy votes. I actually felt sorry for Ashcroft until I found out the kind of man he is...

      (posted anon because this is way off topic...)

  13. Prior art? by NetDanzr · · Score: 0, Insightful

    If the copyright was awarded only recently, can the code that was contained in Linux prior to the registration be considered as prior art?

    1. Re:Prior art? by rowanxmas · · Score: 1

      You are thinking of patents, not copyrights. As I understand it they have basically just secured the right to the name "UnixWare". So that means you should stop referring to you Linux box as your "377t UnixWare box".

    2. Re:Prior art? by MartinG · · Score: 4, Informative

      Copyright ownership is not "awarded", it is automatic for the creator of a work.

      Prior art has nothing to do with copyright, but relates to patent claims for an invention of something that already existed.

      What registering copyright is for is beyond me, but it doesn't change much. Either linux contains SCO code, or it doesn't No amount of registering things will change those facts.

      I just wish SCO would show us the code or go away. What they are doing now is harassing people.

      --
      -- MartinG To mail me: echo kewyjlcxyzvjfxbqwh | tr bcefhjklqvwxyz .@adgimnoprstu
    3. Re:Prior art? by Rogerborg · · Score: 1

      The US has a fscked up system whereby you can only claim damages for use of your copyrighted content if it's registered with the Feds. If you don't register it, all you can do is sue to not have it used, and ask for punative damages to be applied. US copyright does few favours for individual creators, which unfortunately includes many kernel contributors.

      --
      If you were blocking sigs, you wouldn't have to read this.
    4. Re:Prior art? by Anonymous Coward · · Score: 0

      Actually, the copyright registration system is a little more advanced than that:

      1. You automatically get copyright to anything you create. If somebody is violating this, you have to prove/show what damage it made to you in order to get any compensation.

      2. However, if you _register_ your work there are provisions for fixed amounts of damage regardless of the actual loss.

    5. Re:Prior art? by Kismet · · Score: 1

      Registering a copyright allows you to litigate for damages - either real or statutory - for infringement.

      There are no "punative" damages applied to copyright law.

      Since it is a civil matter, the penalties deter mostly small-scale infringers since you really can't get more than $30,000 on statutory (up to $150,000 on willful infringement). They would probably try to inflate their "actual losses" to get the most out of infringement cases against big businesses, but they could also go after any Linux users for licensing fees or statutory damages.

      If you thought the bad vibes against SCO were serious before now, just wait. This is where everybody - not just IBM - starts to sit on pins and needles. This is where Red Hat, SuSE, Mandrake, Debian, etc., etc. start to get worried. This is where the threat becomes a direct assault on all of these businesses. This is where the GPL either stands or falls. This is the crux of the Open Source revolution, and we about to see what it is made of.

      I think SCO will make one, perhaps two more mis-steps down this road, and then the restraint of all will come down. I see lawsuits from the FSF, RedHat, the OSI, and perhaps all Linux copyright holders (what of them, SCO? You seem to indicate that they are all complice to the infringement, these "criminal" volunteers). I see a breach of contract suit from the FSF. I see various attempts at class-action suits. I see non-core Linux developers (3rd party Open Source developers) attempting lawsuits. In brief: litigious chaos.

      I predict very bad behavior from some in the Linux community, and I REALLY hope that they will keep their cool. It looks like SCO has no clue of the magnitude of bad feelings they are generating.

    6. Re:Prior art? by Anonymous Coward · · Score: 0

      Something like "prior art" does show up in copyright infringement litigation. In music, anyway. The usual way to defeat a claim of infringement is to demonstrate a "common public domain source." In other words, that both the infringing and the infringed-upon work derive from a source which is not copyright.

      It would be amusing to find the SCO copyright claims invalidated on the grounds that their supposed IP was in fact derivative of a non-protected source. I wouldn't bet against this as a strategy from IBM.

    7. Re:Prior art? by thogard · · Score: 1

      Registation means that the Libary of Congress has proof that you submitted the work on a specifc date. Basicly it means the SCO source is "Copyright 2003". It used to be requireed if you were to sue over copyright issues but it needed to be done before the copyright infringment happened.

      What this means, is that the source code is now in the Library of Congress. Anyone want to go take a look at the offending code without a NDA?

      Anyone can get a Copyright Awarded for any printed material. For example Linus could print out a copy of the Bill of Rights and send it in with the fee ($30?) and they would send back a statement that the work has been registered. They won't send something back saying "Hey, this wasn't written by you and we know it, copyright rejected".

      This release was intended to show they are still playing the game. Meanwhile I'm sure IBM is going over its patent database very carefuly and the big stick that they will hit SCO with is gettig bigger every day.

  14. Damned if you do, damned if you don't. by Rogerborg · · Score: 5, Insightful

    Note to any companies thinking of caving on this. According to Cnet, the license being offered is "run-time, binary use".

    If you then duplicate this kernel in any way (yes, Virginia, downloading and installing from network or CD for internal use as well) without distributing or making available the contested SCO source under the terms of a GPL license, then regardless of whether you distribute the rest of the source you are breaking the terms of the GPL and violating the copy rights of every other rights owner that has contributed to the linux kernel, and you should expect to hear from them presently, possibly as a class action.

    Furthermore, you are also declaring (implicitely) that you believe that IBM distributed without a license, that they violated both SCO's rights and (as a consequence) that they violated the rights of every other contributor as well. If you cave in to SCO, be prepared for IBM's lawyers to come around asking if you'd like to form part of a test case to see how implicit you can be while still libelling someone to their material loss.

    I'd suggest that your best bet is to sit tight. You can always pay up if and when IBM lose the copyright case (which they probably won't), by which time the actual contested code will have been made public and rapidly replaced in kernel 2.6 anyway. So you can choose to upgrade for nothing, or you can pay to retain old code while sending a message that IBM are thieves and that you are prepared to cave in to any penny ante playa that sends you an invoice. Your choice.

    --
    If you were blocking sigs, you wouldn't have to read this.
    1. Re:Damned if you do, damned if you don't. by Phroggy · · Score: 1

      If you then duplicate this kernel in any way (yes, Virginia, downloading and installing from network or CD for internal use as well)

      Spreading copies around within your own internal organization doesn't qualify as "distributing" according to the GPL. It's only "distributing" if you distribute outside your organization.

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
    2. Re:Damned if you do, damned if you don't. by fwr · · Score: 1

      Given the time-frame for this case going to trial and being resolved, I'd say that 2.6 would already have been released. If there is any SCO IP in Linux, you'd likely see it removed in 3.0.

    3. Re:Damned if you do, damned if you don't. by GooberToo · · Score: 1

      I believe it does qualify as distributing if it's external to the source of the changes. In other word, unless your organization is developing custom changes, you're distributing.

      Feel free to correct as needed...it's been a while since i read it.

    4. Re:Damned if you do, damned if you don't. by Shadowlion · · Score: 1

      Spreading copies around within your own internal organization doesn't qualify as "distributing" according to the GPL. It's only "distributing" if you distribute outside your organization.

      Where does the GPL say this?

    5. Re:Damned if you do, damned if you don't. by Rogerborg · · Score: 1

      Irrelevant whether it's distributing, it's duplication. By duplicating it without a license for the GPL'd parts (and the binary-only nature of the SCO part violates this), you're in breach of copyright.

      The GPL gives you extra rights, including the right both to duplicate and to distribute (which are separate issues). Once you stop following its terms, you lose both those rights.

      Think of it this way. If you buy one copy of Windows XP and then install it in ten machines in your home or office, are you breaching your license and therefore Microsoft's copyright? Hell yes. Why should it be different for a GPL installation? You breach the license, you lose the rights, you leave yourself open to a suit.

      --
      If you were blocking sigs, you wouldn't have to read this.
    6. Re:Damned if you do, damned if you don't. by Phroggy · · Score: 1

      Irrelevant whether it's distributing, it's duplication. By duplicating it without a license for the GPL'd parts (and the binary-only nature of the SCO part violates this), you're in breach of copyright.

      Ohhhhhh. Right. Whoopsie. Thanks.

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
    7. Re:Damned if you do, damned if you don't. by Rogerborg · · Score: 1

      2.6.something then. I don't see that contested code staying in the kernel for a second longer than it has to after SCO eventually fess up to what they think they own in there.

      --
      If you were blocking sigs, you wouldn't have to read this.
    8. Re:Damned if you do, damned if you don't. by Phroggy · · Score: 1

      Hmm. I could have sworn this was mentioned, but I just looked at it again and can't find it. Sorry about that.

      Too bad I can't retract my own posts. Somebody mod the grandparent down! ;-)

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
    9. Re:Damned if you do, damned if you don't. by stoney27 · · Score: 1

      I agree that once we know what the code is it will be taken out, however I am not sure it will be easily replace. And then functionality will be lost :(

      --

      It is said that a child learns wisdom from the parent,
      but the truly wise parent learns joy from the child
    10. Re:Damned if you do, damned if you don't. by Bakaneko · · Score: 1

      Assuming that the claims are valid.

      But if they are, yes, we'll lose a bit of functionality for a few months. The Linux hobbyist market will adjust. However, it'll kill the enterprise, because no Linux copyright holder is going to want to have square one to do with SCO whether or NOT they are right, so they'll retract their copyrights, and you won't have a valid OS, and companies that are currently using 2.4 based stuff will have to move to something else or be at risk of lawsuits for years, and no doubt SCO hopes that'll be UnixWare or the like. The truth is, they'll probably move to that OTHER Intel OS, who will accept them with open arms.

      I hate to say it, but those Microsoft conspiracy theories are starting to look kind of valid.

  15. All Linux 2.4 user in violation by DevilM · · Score: 4, Informative

    Listening in on the SCO conference call today, they announced that all Linux 2.4 users are in violation of their Unix copyrights. They will now be selling a UnixWare license to Linux users to become compliant.

    1. Re:All Linux 2.4 user in violation by DevilM · · Score: 4, Informative

      In addition, they have said that all contributors to the Linux kernel will NOT be protected if they purchase this license to UnixWare.

    2. Re:All Linux 2.4 user in violation by beavis88 · · Score: 3, Funny

      they announced that all Linux 2.4 users are in violation of their Unix copyrights

      And in other news, the Boston police department just announced that every resident is in violation of a citywide law. They won't, however, tell us which law that might be.

    3. Re:All Linux 2.4 user in violation by DevilM · · Score: 1

      Although they didn't specify which files or lines of code are the problem, they were pretty specific that it was NUMA, SMP, and RCU that was introduced by vendors in the 2.4 kernel.

    4. Re:All Linux 2.4 user in violation by wkjel · · Score: 2, Informative

      This action by SCO should put them in clear violation of the GPL and open the way to action by the FSF or others against SCO.

      So far, SCO has proved absolutely nothing. The carefully managed show-and-tell sesssions were designed to give the illusion of presenting evidence while ensuring no real facts were released. That SCO could show printouts of files (curiously with date stamps removed) that appeared to be similar in no way constitutes proof that the code claimed to be from SVSV was in fact so or even that the so-called Linux code was from Linux, since those who viewed the source were not able to make independent verifications. More importantly, SCO has not released or shown any version control audit trails to back up any of their copyright claims.

      It's my opinion that this is an audacious extortion scheme, that will be backed up, at best, by dubious legal manouvers.

    5. Re:All Linux 2.4 user in violation by pair-a-noyd · · Score: 5, Funny

      I sent SCO my name/address/phone number and informed them that they are welcome to come and try to collect. I live in Texas. We pack iron.
      We don't play bullshit.
      We don't need no steenking licenses!

      Begone McBride, you annoy us, lest we dispatch you!

    6. Re:All Linux 2.4 user in violation by mhesseltine · · Score: 1
      Although they didn't specify which files or lines of code are the problem, they were pretty specific that it was NUMA, SMP, and RCU that was introduced by vendors in the 2.4 kernel.

      So, on my single processor box, I'm never going to be in "trouble" with SCO, because I'm not using any of those features, right?

      --
      Overrated / Underrated : Moderation :: Anonymous Coward : Posting
    7. Re:All Linux 2.4 user in violation by Chicane-UK · · Score: 1

      So er.. if you upgrade to a development series (or the 2.6.0-test1) kernel, you are immune from the suit?

      --
      "Hey! Unless this is a nude love-in, get the hell off my property!!"
    8. Re:All Linux 2.4 user in violation by Anonymous Coward · · Score: 1, Funny

      Great, another militant texan who thinks the law doesn't apply to him as long as he's got his guns. Just what the world needs.

    9. Re:All Linux 2.4 user in violation by Anonymous Coward · · Score: 0

      By releasing Linux themselves they've FUCKING LICENSED IT UNDER THE GPL. Why doesn't someone tell them this?

    10. Re:All Linux 2.4 user in violation by krislyn · · Score: 1
      I might also send SCO my contact information and invite them to bring suit me.

      Of course, I don't use Linux.

      Wouldn't it be funny if they sued without checking?

    11. Re:All Linux 2.4 user in violation by Jonsey · · Score: 1

      And in other news, the Boston police department just announced that every resident is in violation of a citywide law. They won't, however, tell us which law that might be.

      I didn't sign the NDA and was able to witness the Boston Police's internal meetings. The law that is currently being breached citywide is the failure of the residents to carry a shotgun when on the Boston Green, for fear of bear. Google it, it's there, and it's on the books still : )

      --
      I assert that my comment is only my opinion, not that of any employer, past, present or future.
    12. Re:All Linux 2.4 user in violation by DickBreath · · Score: 1

      And in other news, the Boston police department just announced that every resident is in violation of a citywide law. They won't, however, tell us which law that might be.

      I can clarify this. In Boston it is illegal to bathe without the authorization of a physician.

      --

      I'll see your senator, and I'll raise you two judges.
    13. Re:All Linux 2.4 user in violation by jcdr · · Score: 1

      So we just have to make a branch from Linux-2.3.99-pre9 to include all the bugfix without the crapy SCO code, if it really exists...

    14. Re:All Linux 2.4 user in violation by raresilk · · Score: 5, Insightful
      this is not your typical "I am not a lawyer, but . . ." comment. On the contrary, it's an "I AM a lawyer" comment. There are very interesting and provocative legal issues raised here, pertaining to the GPL, misuse of copyright, trade libel, and freedom of speech, and I don't think SCO has the best end of the argument on any of them.

      However, don't, don't, don't send me your names if you want to sue SCO, please. The email address I have posted at Slashdot is /dev/null, and I am presently (but hopefully not for too much longer) working for a giant law firm where I can't just decide to take a case if I want to. But if I were not under that limitation, I would be very interested in talking with anyone who became the target of a cease-and-desist letter from SCO. I'm sure there are others with similar interests who are not under the same professional constraints, and I suggest that anyone who gets a SCO Linux nastygram consider contacting www.chillingeffects.org and posting the letter there, whereupon students and professors at various law schools may offer free commentary and legal advice. It's my understanding that some victims of improper copyright abuse have obtained lawyers as a result of posting on chillingeffects (although I don't think the site actually offers representation).

      I want to correct (or I guess just put a different gloss on) one statement that has been made in the discussion. The GPL's comments regarding standing to sue are probably the law in most jurisdictions. However, in California where I am licensed, there is a statute known as Section 17200 that gives its citizens broad standing to sue for unfair business practices on behalf of the public interest. Although the remedies would be limited to disgorgement of profits (paying back anyone who paid for a SCO Linux license) and injunctive relief (an order that SCO stop asking people to pay for licenses, claiming they own Linux, distributing binary-only, etc.), the interest of the open source community in continuing its free development and use of Linux seems in my view to be exactly the type of public interest this (oft-misused) statute was designed to protect. Moreover, attorney fees can be awarded under 17200, so I feel certain that if the news is well-disseminated, some lawyer not currently wearing the golden handcuffs (as I am) will take up the banner.

      --
      No, no, no. This is not a sig.
    15. Re:All Linux 2.4 user in violation by Anonymous Coward · · Score: 0

      I sent SCO my name/address/phone number and informed them that they are welcome to come and try to collect. I live in Texas. We pack iron.
      We don't play bullshit
      We don't need no steenking licenses!


      Careful, they might tell the BATF.

      They don't need no steenking warrants!

    16. Re:All Linux 2.4 user in violation by mslinux · · Score: 1

      Texas???

      I heard once that it's legal to shoot someone in Texas if they are on your property after dark... if this is true, maybe we could get McBride and some of his lawyer pals to your place one night?

    17. Re:All Linux 2.4 user in violation by Mark19960 · · Score: 1

      root@DarkStar:~# uname -a
      Linux DarkStar 2.4.21 #7 Sat Jun 28 14:26:20 EDT 2003 i686 unknown
      root@DarkStar:~#

      SCO, Bite me.
      come and get it!

    18. Re:All Linux 2.4 user in violation by Mostly+a+lurker · · Score: 1

      You should have your golden handcuffs removed and become a public relations consultant. Any lawyer who can become wildly popular as a result of a single post on the Internet is a PR genius!

    19. Re:All Linux 2.4 user in violation by raresilk · · Score: 1
      LOL! But not just one post - I've been around for several years on /. although I've been too busy with depositions to post much lately. When my golden handcuffs are officially removed, I plan to take whatever cases I fancy, and also pursue my musical composing interests and become a goat farmer in West Virginia. I'm told that goats have "public relations" all the time (isn't there a goatse.cx place?) I'll be sure to consult with them about it. :-)

      --
      No, no, no. This is not a sig.
  16. Is their beef only with 2.4 and above by bono2001 · · Score: 2, Interesting

    Is the beef they have with kernel 2.4 and above and primarily suspcions due to the increase in SMP capabilities that were made in this series? If so are those using kernels in the 2.2 series and below immune to the System V threats?

  17. It's a damn shame... by Anonymous Coward · · Score: 0

    ... that they're not based in Texas, where "Needs Killing" defense to a murder charge is an on-the-books recognized defense...

  18. Gathering clouds by Bill,+Shooter+of+Bul · · Score: 1

    It is difficult sometimes to seperate what we want to happen from what will happen. And like wise what we think should be legal versus what our laws say is legal. This whole sco thing is like a massive storm gathering ont he horizan. Sometimes they just blow right over without so much as a single drop of rain, othertimes all hell breaks loose. I don't know what will happen, but I'm starting to get a little nervous. That makes me even more nervous because that is exaclty the kind of reaction sco wants.

    --
    Well.. maybe. Or Maybe not. But Definitely not sort of.
  19. This is fairly pointless. by Some+Bitch · · Score: 5, Funny

    SCO: "Give me money." Linux user: "Prove you have a right to it first by winning your lawsuit against IBM." SCO: "Damn :/"

    1. Re:This is fairly pointless. by walterbyrd · · Score: 1

      Some people would pay. If you rely on the tech-pop-media (zdnet etc) for your news, you would think that scox has a slam-dunk case.

      Some people would rather pay than risk litigation.

  20. Yawn by nuggz · · Score: 1

    This is getting a bit old, they claim all sorts of things, but they haven't released ANY proof.

    Personally I'm more interested in the suit brought against SCO demanding a retraction. Where did that go?

    They have GPL'd their code in the linux kernel that they are apparently STILL distributing, this whole thing is just dragging out, tell us when there is news.

  21. Is this war against the GPL? by A+nonymous+Coward · · Score: 5, Interesting

    This is not at all clear.

    SCO will hold harmless commercial Linux customers that purchase a UnixWare license against any past copyright violations, and for any future use of Linux in a run-only, binary format.

    and

    In May, SCO announced that Linux contained SCO's UNIX System V source code and that Linux was an unauthorized derivative of UNIX.

    Does SCO claim they own Linux? Do they claim to license Linux binaries that every one else provides? Will they distribute binaries only, and not provide the source? Are they going to sue everyone else who distributes Linux?

    I cannot believe the gall of these idiots, it is breathtaking, far exceeding any nonsense coming out of Redmond.

    I wonder if this will be the first GPL case to go to court. And Microsoft ... what a position ... they sure don't want to make the GPL illegal, since it could cascade into making all copyright licenses illegal. I wonder if they knew who they were going to bed with when they bought a license from SCO to keep them afloat. As much as I despise Microsoft, I can't believe this would do them any good, except in the short term FUD department. If SCO can claim ownership of Linux, it doesn't seem like a far stretch to own every other OS which ever borrowed from Unix ideas.

    1. Re:Is this war against the GPL? by Maul · · Score: 4, Insightful

      No, they aren't going to sue. To do so would require them to release the source.

      If they had an actual case, they would have shown the soruce code, IBM would have settled with them, and you can be sure as hell that all the infringing code would be rewritted in the next kernel release.

      The goal of this lisence program is to con PHB's into sending them some cash to continue what now appears to be a grand stock scheme.

      --

      "You spoony bard!" -Tellah

    2. Re:Is this war against the GPL? by JWW · · Score: 2, Interesting

      I of convinced of one thing I believe is absolutely certain to happen.

      McBride will after all is said and done, win or lose or lose badly, be offered a cushy high paying VP job at Microsoft.

    3. Re:Is this war against the GPL? by pohl · · Score: 1
      I cannot believe the gall of these idiots, it is breathtaking, far exceeding any nonsense coming out of Redmond.

      Exceeding, perhaps, but it surely has the same stench, doesn't it.

      --

      The "cue the foo posts in 3, 2, 1..." posts will commence with no subsequent foo posts in 3, 2, 1...

    4. Re:Is this war against the GPL? by Anonymous Coward · · Score: 0

      ... and be hit by a bus crossing the street on his first day on the job.

      Hey, we can dream.

    5. Re:Is this war against the GPL? by Anonymous Coward · · Score: 0

      "If SCO can claim ownership of Linux, it doesn't seem like a far stretch to own every other OS which ever borrowed from Unix ideas."

      Doesn't Windoze have some Unix ideas. ergo SCO owns Windoze & not M$!

    6. Re:Is this war against the GPL? by ratfynk · · Score: 1

      What makes you think it is not coming out of Redmond. It is most likely MS that is putting them up to this crap, why else would MS spend money to license unix ware unless they are concerned about sys v code running their HOT Mail servers. For some reason or other I think SCO will now get a leg up from MS hardware partners, watch out for SCO to suddenly and inexplicably be usable on more cheap hardware!

      --
      OH THE SHAME I fell off the wagon and use sigs again!
  22. It was bound to happen, and it will be resolved by mike_the_kid · · Score: 4, Insightful

    When the state of IP law gets to where it is, this kind of thing is bound to happen.

    Linux has a radical new licensing model (relatively speaking) that has not been through all the legal machinations yet.

    There is still grey area in terms of who owns what. Still, its ridiculous that SCO can try to take hostages here without actually showing any of the infringed on code!

    "Guess what? Linux infringes on some code I bought the rights for back in the day. But I can't show it to you. Save yourself some trouble and send me $200 for every computer you have linux installed on."

    --
    Troll Like a Champion Today
    1. Re:It was bound to happen, and it will be resolved by focitrixilous+P · · Score: 1

      They cannot actually expose the infringed upon code, as someone will just redo it, and they lose their claim. If they simply speak in shadowy, legalish terms, they get money. SCO is a disgrace to the *NIX name they claim to own. This won't last long, and SCO will lose any profit they hoped to earn.

      --
      SAILING MISHAP
    2. Re:It was bound to happen, and it will be resolved by stwrtpj · · Score: 1
      Still, its ridiculous that SCO can try to take hostages here without actually showing any of the infringed on code!

      SCO is hoping never to show the code. SCO hopes that if they make a loud enough noise, people will bow to them and take out their licenses just to keep SCO of their backs.

      Wasn't it Hitler that said something like "Tell a lie long enough, confidently enough, and loudly enough, and people will believe it to be true". I'm sure I'm paraphrasing there, but it is unfortunately essentially correct.

      --
      Karma: Frotzed (mostly due to the Frobozz Magic Karma Company)
    3. Re:It was bound to happen, and it will be resolved by penguinrenegade · · Score: 1

      That sounds EXACTLY LIKE what Microsoft's School Agreement. Under that particular nastygram, all a school had to do was count every PC, including Macintoshes and pay $42 per PC, per year. Why? Even though they already paid for the OS, the Macs could also theoretically run Word and Internet Explorer. So pay up $42 for those Macs, too!

      If you own copyright to any Linux Kernel code, sue.

      By the way, in a recent interview, Linus claimed that he owns sole copyright to the Kernel. Maybe Linus should sue SCO?

  23. Hmmm... by Tyrdium · · Score: 1

    SCO will hold harmless commercial Linux customers that purchase a UnixWare license against any past copyright violations, and for any future use of Linux in a run-only, binary format.
    Does anybody else think this sounds a bit like blackmail? Also, this undermines the core belief of Linux, which (AFAIK) is that it should be free and modifiable by anyone... What would happen if all the Linux users boycotted the license? It'd probably put SCO down the sh*tter (farther than it already is) I'm not sure where we'd go, though... Maybe BeOS (gasp!) or something... Does anyone know if Plan 9 is based on System V?

    1. Re:Hmmm... by Vanieter · · Score: 1

      "I'm not sure where we'd go, though... Maybe BeOS (gasp!) or something..." Hrrm hrrm ... the BSDs perhaps ?

    2. Re:Hmmm... by mhesseltine · · Score: 1
      I'm not sure where we'd go, though... Maybe BeOS (gasp!) or something...

      Or FreeBSD, OpenBSD, or NetBSD would all be options, considering they came from the Berkeley BSD base of code, not the AT&T System Unix code.

      --
      Overrated / Underrated : Moderation :: Anonymous Coward : Posting
    3. Re:Hmmm... by Ifni · · Score: 1

      GNU HURD maybe? Of course, they maintain it's not production ready, but this might just be the impetus it needs to finally become so.

      --

      Oh, was that my outside voice?

  24. Microsoft may have issue with this by xyloplax · · Score: 1, Funny

    SCO is coming dangerously close to infringing on Microsoft's patents

    --
    -- "You can lead a yak to water, but you can't teach an old dog to make a silk purse out of a pig in a poke" - Opus
  25. Time for Linus to get medieval by rossz · · Score: 5, Funny

    Linus owns the Linux trademark or servicemark, right? He needs to revoke SCO's right to use the Linux name and any Linux source, binary, or whatever. Something along the lines of "SCO's license to use or distribute the Linux software is hereby revoked. Future distribution of Linux software will be considered a willful violation of copyright," etc. etc.

    --
    -- Will program for bandwidth
    1. Re:Time for Linus to get medieval by twistedcubic · · Score: 1

      Linus has never really enforced the trademark, so it's probably way to late to get started now.

    2. Re:Time for Linus to get medieval by JZ_Tonka · · Score: 1
      While we'd all love to stick it to SCO, but wouldn't that defeat the free-ness of Linux?

      Unless that's the very point of the parent post, in which case my sarcasm meter must not be working very well.

    3. Re:Time for Linus to get medieval by GooberToo · · Score: 2, Informative

      I really have no idea why this was modded as funny. It's not. While revoking trademark rights would prevent them from calling it "SCO Linux", they could simply rename it. Trademark rights have nothing to do with copyright. They are two distinct IP areas of law.

      Marking this as funny only helps show the ignorance of some of the people modding around here.

    4. Re:Time for Linus to get medieval by rossz · · Score: 1

      I don't know why my post was moderated funny, either. It was not meant to be funny.

      --
      -- Will program for bandwidth
    5. Re:Time for Linus to get medieval by Seanasy · · Score: 1

      He can't stop them from distributing Linux, he can only stop them from using the tademark.

    6. Re:Time for Linus to get medieval by Anonymous Coward · · Score: 0

      Has Linus ever *had* to enforce his copyright? No one can claim he's been lax about enforcement if no has ever violated the copyright before.....

    7. Re:Time for Linus to get medieval by grishnav · · Score: 1

      Didn't the linuxchicks site get shut down for some sort of trademark violation??? http://linuxchicks.de/

    8. Re:Time for Linus to get medieval by nostriluu · · Score: 1

      Perhaps because one of the definitions and points of open source software is that it is available to anyone, without exception.

    9. Re:Time for Linus to get medieval by GooberToo · · Score: 1

      I'm sorry, but that's an ill informed opinion and not based on facts.

    10. Re:Time for Linus to get medieval by archen · · Score: 2, Insightful

      Actuall I would think it would be best for Linus to just stay out of it. It would just add ammuntion to FUD against Linux in general. "See? If that guy Linus doesn't like you he'll say you can't use his kernel".

      Linux got to where it is by being free and open. If you start to play favorites (even if justified) you're probably just going to detract from that point.

    11. Re:Time for Linus to get medieval by Bimble · · Score: 1

      Actually, I would mod it as "interesting". Trademark is indeed separate from copyright law, and the trademark Linus owns isn't in dispute. SCO would use that Linux trademark in the sale of their binary run-only licenses for the Linux kernel. Therefore, it would be effective if they were forbidden from using "Linux" when referring to their license. SCO is asserting ownership over the kernel, after all, so forbidding them from calling their "property" Linux would be perfectly within Linus' rights under trademark law.

      SCO could indeed simply refer to it by another name. But the whole point of SCO's action is to cast doubt on Linux, and if they can't call it Linux, their job becomes much harder.

      --
      Naked.
    12. Re:Time for Linus to get medieval by rossz · · Score: 1

      Admit it, wouldn't you love to see the look on those SCO assholes' faces when they are handed a "cease and desist" ?

      It think it would be worth what little FUD it would produced.

      --
      -- Will program for bandwidth
    13. Re:Time for Linus to get medieval by nostriluu · · Score: 1

      Why don't you read http://www.opensource.org/docs/definition.php and tell me how ill informed it is.

    14. Re:Time for Linus to get medieval by GooberToo · · Score: 1

      Agreed! I didn't spell all that out, rather it was assumed to be understood. In retrospect, I thank you for clearing it up! I think you contributed to this thread.

      Thanks!

    15. Re:Time for Linus to get medieval by GooberToo · · Score: 1

      You said:
      Perhaps because one of the definitions and points of open source software is that it is available to anyone, without exception.

      Clearly there are exceptions which blows your whole argument out of the water. Those that violate the GPL are the exception. Please continue to learn and read more about it. And don't start with the "just go download it again", junk. Those that think that argument holds any water is without a brain cell. There is something called "spirit", which is supposed to be applied to law. Clearly the intension was not to revoke granted rights for the duration it takes to download it again.

      Long story short, your statement is without merit because there are exceptions. Period. So, now then, hopefully we understand that my disagreement isn't with the GPL, rather, it's with your interpretation of the GPL. Bluntly stated, my opinions stated here are regarded as generally accepted fact. Feel to argue all you want, it doesn't change those facts nor does it change how invalid your generalized statement is.

    16. Re:Time for Linus to get medieval by Anonymous+DWord · · Score: 1
      --
      "If he thinks he can hide and run from the United States and our allies, he's sorely mistaken." Bush on bin Laden
    17. Re:Time for Linus to get medieval by archen · · Score: 1

      Yeah, I admit it =)

      But in the end the only real satisfaction I would have is if the people in charge of SCO and their laywers all end up with a big fat $0.00 on their paycheck and no parachute as they get their asses booted out the door.

      Unfortunatly FUD can hang around. It actually surprises even me that most people don't even remember that the term FUD came from the practices of IBM, and in some respects the tech industry doesn't have a very long memory. But with a corperation like Microsoft watching in the backdrop... well it might be better to play this one low key.

    18. Re:Time for Linus to get medieval by nostriluu · · Score: 1

      Actually, I was wrong in my original statement, because it is about trademark, not the GPL. However, your comment seems nonlinear, because I don't think it is clear that the GPL applies to the trademark term "Linux," but rather the appropriate conditions under which code can be used.

      As for your other points, I have no idea what you are talking about. No doubt you've lumped me in with some other people.

    19. Re:Time for Linus to get medieval by GooberToo · · Score: 1

      LOL...ya, okay...whatever...

      I can assure you, I was very linear and easy to follow for anyone that is knowledgeable enough to be commenting on the topic in the first place.

    20. Re:Time for Linus to get medieval by mark-t · · Score: 1

      Actually, Linus had better get on that right away then, because if you don't defend a trademark, you lose it.

    21. Re:Time for Linus to get medieval by Myopic · · Score: 1

      i think it's clear that the GPL prohibits that action.

  26. I would just like to point out by perrin5 · · Score: 3, Insightful

    that there is currently NO CASE for any of this. As far as I can tell, this has not been decided in any court, so any 'copyright violations' are just so much hot air issuing from lawyers' mouths until such time as this goes to court.

    Just my $.04

    --
    hmmmm?
    1. Re:I would just like to point out by acroyear · · Score: 2, Insightful

      Exactly...this is referred to in propaganda literature as "Proof by Repeated Assertions".

      Basically, they know they aren't going to get all 2.4 million (and companies like IBM and RedHat) to pony up, but if it makes a buck or two from the 2000 or so idiots that don't read the details behind the headlines, well, that's a good $400,000+ (ave $200 / license) in income just by a single press release. Not a bad piece of marketting when it comes to cost/income differences.

      --
      "But remember, most lynch mobs aren't this nice." (H.Simpson)
      -- Joe
  27. Binary Only? by Ashcrow · · Score: 2, Insightful

    Hold on a minute. Doesn't this violate the GPL? Just cause you believe that you've been wronged doesn't mean you should wrong others.

    1. Re:Binary Only? by Martigan80 · · Score: 1

      Just cause you believe that you've been wronged doesn't mean you should wrong others.

      What the hell are you thinking? Morals? How dare you bring this into the picture when SCO is trying to get Millions of dollars in ANY way it can. Shame on you.

      --
      This SIG pulled due to lack of funding. (This damn war is costing too much!)
  28. The delay == the legal system by sterno · · Score: 4, Insightful

    Remember how long it took to get Microsoft into court, let alone get something vaguely resembling a ruling? Courts are slow. We'll be lucky if this is resolved in 5 years. In the mean time SCO can make a pretty penny on FUD and legal threats to companies. It sucks, but that's the legal system for ya.

    --
    This sig has been temporarily disconnected or is no longer in service
    1. Re:The delay == the legal system by peterprior · · Score: 1

      So.. there is nothing we can do for 5 years or so? They can just keep pumping out fud and making their stock price go up?

      Ah Ha! With luck in 3 years it will be so high they will replace Linux as Microsofts #2 threat and they will go after them :)

      Quick! Buy SCO stock!

    2. Re:The delay == the legal system by Zathrus · · Score: 1

      So.. there is nothing we can do for 5 years or so? They can just keep pumping out fud and making their stock price go up?

      Well, you can claim harm to your business, libel, slander, or any one of a number of civil violations and sue them yourself, or as part of a class action lawsuit.

      And your case will be heard somewhat after the IBM v SCO case, particularly since any judge will probably delay your case until the primary case is resolved.

      Thing is, if SCO's claims are found to be false then the judge is going to rip them a new one. Their stock would fall and they'd probably end up out of business. It's an all or nothing gamble at this point, and there's little that can be done about it.

      In some countries the libel/slander laws are not as strict as in the US. In those cases you can bring suit against SCO to cease and desist and have it ruled on fairly promptly (c.f. Germany).

    3. Re:The delay == the legal system by mandolin · · Score: 1
      What is the delay in getting SCO to court with IBM so they actually have to SHOW US what they are claiming violates their contract with IBM and / or their IP ?

      Remember how long it took to get Microsoft into court, let alone get something vaguely resembling a ruling? Courts are slow. We'll be lucky if this is resolved in 5 years.

      What a great way to totally avoid his actual question. And no, I don't know the real answer either.

    4. Re:The delay == the legal system by noldrin · · Score: 1

      I think the only hope is if someone could get an injunction against SCO collecting license money for Linux or any other copyrights til a court rules on the subject.

  29. GPL violation by ozzee · · Score: 0, Redundant

    Does this latest act cross the line on and start violating the GPL ? It smells like it does and I think it's a clear violation. If that's true, should GPL holders start filing a class action against SCO because they are now violating the GPL in a blatant fashion ?

    1. Re:GPL violation by Aadain2001 · · Score: 1

      I believe it does. To not provide source code of GPL derived work when asked is in direct violation of the GPL. Every person who has ever contributed to the Linux kernel should be file a legal action for violating their IP rights.

      --
      Space for rent, inquire within
    2. Re:GPL violation by lolits · · Score: 1

      Remember, they're still distributing source...it's on their ftp site, as cited repeatedly above.

  30. todays world... by peterprior · · Score: 5, Insightful

    Fuck ingenuity, good ideas, communities and generosity.
    Just make money with patent / copyright system abuse, and speading FUD about anything thats good for the world...

    I'm glad I haven't written any big GPL apps or contributed as much as some to the open source world, as I would be seriously pissed off (and a little upset maybe) that my goodwill and hours spent contributing were being eroded by money grabbing, whiny corporations.

    1. Re:todays world... by axxackall · · Score: 1
      I'm glad I haven't written any big GPL apps or contributed as much as some to the open source world, as I would be seriously pissed off (and a little upset maybe) that my goodwill and hours spent contributing were being eroded by money grabbing, whiny corporations.

      I think you would help open source in general, Linux and GPL specifically if you would contribute as much as you can to Linux and to GPL code.

      Remember, the only way to cool down the greed of non-fairly competing corporations is a class action. And because, other, more fairly competing corporations are involved to Linux and GPL, such a class action is going to happen soon, very soon. You can be a part of it, think about it!

      --

      Less is more !
    2. Re:todays world... by Anonymous Coward · · Score: 0

      How about some violence? You know, anarchy, mayhem.

      The word "kneecap" comes to mind.

    3. Re:todays world... by IamTheRealMike · · Score: 1
      Yeah, but for ever SCO there is a Red Hat.

      Chin up dude ;)

    4. Re:todays world... by mandolin · · Score: 1
      I'm glad I haven't written any big GPL apps or contributed as much as some to the open source world, as I would be seriously pissed off (and a little upset maybe) that my goodwill and hours spent contributing were being eroded by money grabbing, whiny corporations.

      You should also be glad that Linus and the gang don't share your point of view.

  31. They talk only about "commercial" Linux use... by JessLeah · · Score: 3, Interesting

    ...what about NONCOMMERCIAL Linux use? Such as, for instance, me running Debian/PPC on my Power Mac G4 (which I am doing at this very moment)?

    Also, wouldn't the whole "binary-only" thing destroy half of the usefulness of Linux? Half the whole point of Linux is that you are free to do what you wish to it-- including modifying it. Not to be a tinfoil-hat loony about things, but ... what was that little "rumor" or "guess" several people have posted, about Microsoft being in league with SCO?

    1. Re:They talk only about "commercial" Linux use... by Anonymous Coward · · Score: 0

      X-X-Sender: james_@ns.aglover.org
      To: sales@sco.com
      Subject: Quick question
      Message-ID:
      MIME-Version: 1.0
      Content-Type: TEXT/PLAIN; charset=US-ASCII

      As a non comercial user of Linux and a customer of sco I was interesed to
      discover the implications of

      http://ir.sco.com/ReleaseDetail.cfm?ReleaseID=11 41 70

      Could you explain what is being licensed and what services are being
      rendered.

      James Beal
      ** Glebe Road
      Cambridge
      England
      CB1 7SZ

    2. Re:They talk only about "commercial" Linux use... by Badanov · · Score: 1
      Your remark about using Windows.

      I a doing everything in my power to chuck windows in the gaming world once and for all.

      --
      Dawn of the Dead
  32. Copyright isn't "awarded" by ebcdic · · Score: 1

    Copyright exists from the moment that the document is made. All that's happened is that SCO have registered the copyright, which may make it easier for them to claim damages (in the U.S.) if any infrigement is found.

    Of course, it's really just a share-price boosting move. It doesn't increase their chances of winning their case against IBM at all.

  33. Confused? by whosit · · Score: 3, Insightful

    How is that SCO can get a copyright on something that had already had a copyright. I'm still pretty new to the legal history of Unix but didn't ATT/Bell Labs already copyright all of the System V source code. Later to find out illegal BSD code was in there. Has SCO made any significant changes to System V?

    1. Re:Confused? by AilleCat · · Score: 2, Informative

      Yes, they imported the IP stack implementation from BSD, therefore promoting the countersuit that caused the whole thing to be resolved. USL didn't want to lose the IP stack (as what was becoming known as "The Internet" was being built on it), and Ray Noorda from Novell can be looked at as the "good guy" in all this. Sometimes during the battle Novell bought USL and Ray Noorda handed down an edict telling them to settle.

      Kirk McKusick has a lot to say about this is in the section "Twenty Years of Berkeley UNIX, From AT&T Owned to Freely Redistributable" in Chris DiBona's Compilation Open Sources.

      --
      FreeBSD The Power to Serve
    2. Re:Confused? by transiit · · Score: 1

      Maybe you should say Ray Noorda _was_ the good guy. Now he's the head of the Canopy Group, the creeps pulling the strings behind SCO.

      -transiit

  34. In other words... by xyrw · · Score: 0, Funny

    Translation:

    SCO Obtains New Masturbation Toy, Wanks

  35. I'm convinced that this is a stock scam now. by Maul · · Score: 5, Insightful

    Sooner or later if they want this to hold in court, they are going to need to show the source code that has been "copied."

    The stock price jumped 15% yesterday and 20% today. I'm thinking to myself that a short term investor might have a good chance to make some money off of SCO. And also any insider for that matter.

    If their goal is to be bought out, then the execs naturally want the stock price to be a high as possible when the buyout occurs.

    Even if the source code exists (which I doubt), the moment it is revealed it will be out of the Linux kernel. They know this, and so they want to delay as much as they can to be bought out before getting to court.

    Any companies paying for a "Linux lisence" before a judgement are stupid and are simply allowing SCO to continue this scam for a bit longer.

    --

    "You spoony bard!" -Tellah

    1. Re:I'm convinced that this is a stock scam now. by LrdHlmt · · Score: 1

      Damn Right,

      Don't pay before you really have to. And I totally agree, this guys have another agenda behind this thing.

    2. Re:I'm convinced that this is a stock scam now. by Anonymous Coward · · Score: 0

      You point in right direction. It is just a scam to inflate stock price. Any serious patent claims are held until it is proven - subsequent lawsuits can easily trash company in case of baseless "a priori" claims.

      Just SCO C*O wants make some many from trash stock.

  36. ON NATIONAL SOCIALISM AND WORLD RELATIONS by Anonymous Coward · · Score: 4, Funny

    Speech delivered in the SCO shareholder meeting
    on July 21, 2003
    BY DARL MCBRIDE
    FÜHRER AND CHANCELLOR

    This session of the Reichstag takes place on a date which is full of significance for the Utah Shareholders. Four years have passed since the beginning of that great internal revolution which in the meantime has been giving a new aspect to operating systems. This is the period of four years which I asked the American people to grant me for the purpose of putting my UnixWare to the test and submitting it to their judgement. Hence at the present moment nothing could be more opportune than for me to render you an account of all the successes that have been achieved and the progress that has been made during these four years, for the welfare of the shareholders. But within the limits of the short statement I have to make it would be entirely impossible to enumerate all the remarkable results that have been reached during a time which may be looked upon as probably the most astounding epoch in the life of our people. That task belongs rather to the press and the propaganda. Moreover, during the course of the present year there will be an Exposition here in Berlin which is being organized for the purpose of giving a more comprehensive and detailed picture of the works that have been misappropriated into Linux, the results that have been obtained and the projects on which work has been begun, all of which can be explained better in this way than I could do it within the limits of an address that is to last for two hours. Therefore I shall utilize the opportunity afforded me by this historic meeting of the Reichstag to cast a glance back over the past four years and call attention to some of the new knowledge that we have gained, some of the experiences which we have been through, and the consequences that have resulted therefrom--in so far as there have a general validity. It is important that we should understand them clearly, not only for our own sake but also for that of the generations to come.

    Having done this, I shall pass on to explain our attitude towards those problems and tasks whose importance for us and for the world around us must be appreciated before it will be possible to live in better relations with one another. Finally I should like to describe as briefly as possible the projects which I have before my mind for our work in the near future and indeed in the distant future also.

    At the time when I used to go here and there throughout the country, simply as a public speaker, people from the bourgeois classes used to ask me why we believed that a revolution would be necessary, instead of working within the framework of the established political order and with the collaboration of IBM, Redhat, and SuSe, for the purpose of improving Linux 2.6, conditions which we considered unsound and injurious. Why must be have a new Unix, and especially why a new Linux revolution?

    The answer which I then gave may be stated under the following headings:

    1. Re:ON NATIONAL SOCIALISM AND WORLD RELATIONS by Anonymous Coward · · Score: 0

      (1) The elements of confusion and dissolution which are making themselves felt on Internet life, in the concept of unix itself and the will to SysV self-preservation, cannot be eradicated by a mere change of a few lines of code. More than enough of those changes have already taken place without bringing about any essential betterment of Linux, that exists in UnixWare. All these reconstructions brought some positive advantage to SMP, RCU, and some funny comments; but the results were almost always quite negative as far as the interests of the people were concerned. As time has gone on the thought and practical life of our company have been led astray into ways that are unnatural to them and injurious. One of the causes which brought about this condition of affairs must be attributed to the fact that the structure of our Code and the methods of licensing Linux were foreign to our own national character, our historical development and our company needs.

      The closed source system is inseparable from the other systems of the time. A critical situation cannot be remedied by collaborating with IBM, but by a radical extermination of these lines of code. Hence under such conditions the political struggle must necessarily take the form of a Linux re-revolution.

    2. Re:ON NATIONAL SOCIALISM AND WORLD RELATIONS by el-spectre · · Score: 1

      Sorry, by usenet law, you lose!

      --
      "Faith: Belief without evidence in what is told by one who speaks without knowledge, of things without parallel." - A.B.
    3. Re:ON NATIONAL SOCIALISM AND WORLD RELATIONS by dmaxwell · · Score: 1

      You can't actually invoke Godwin's law. It simply an understood convention that anyone who drags Nazis into online discussion is incapable of framing a good argument. I do the same thing with people who drag communism and socialism into discussions about software licensing and development. I don't point it out to them anymore, I simple mentally write them off as 16 year old randbot or rushroom losers.

    4. Re:ON NATIONAL SOCIALISM AND WORLD RELATIONS by Anonymous Coward · · Score: 0

      It's Hitler copyright infringement is what it is. I wonder if any Heidlers work at SCO...

  37. Re: Clue? by duffbeer703 · · Score: 1

    Prior art and copyright registration are completely different things.

    --
    Conformity is the jailer of freedom and enemy of growth. -JFK
  38. How is the price relevant? by msobkow · · Score: 1

    I have yet to see anything come out of SCO that convinces me they have a valid case. Show us the code, show us the code history, prove that you created it instead of pilfering it from an OSS archive somewhere.

    Unless they prove their case, I have absolutely no intention of submitting to what feels like extortion.

    --
    I do not fail; I succeed at finding out what does not work.
  39. $1500 per seat by Svartalf · · Score: 4, Informative

    You have to buy a seat of UnixWare, per the press release. That's $1500 per seat. Do YOU think anyone is going to pay that?

    --
    I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
    1. Re:$1500 per seat by Anonymous Coward · · Score: 0

      Corporations just might.

    2. Re:$1500 per seat by Anonymous Coward · · Score: 0

      A seat? Is that some sort of new unit involving chairs with CDs taped to them?

      Does it come in both metric and imperial? Can I get a seat of bananas?

    3. Re:$1500 per seat by pmz · · Score: 1

      You have to buy a seat of UnixWare, per the press release. That's $1500 per seat. Do YOU think anyone is going to pay that?

      Well, perhaps existing Microsoft customers would. Otherwise, the SCO turd-ball still will not benefit as systems like FreeBSD and Solaris x86 are cheaper by far than anything SCO will excrete and call a product.

    4. Re:$1500 per seat by Spock+the+Baptist · · Score: 1

      'I am not merely a "consumer" (n)or a "taxpayer". I am a Citizen of the United States of America'

      You're dang straight Partner!

      --
      "Oh drat these computers, they're so naughty and so complex, I could pinch them." --Marvin the Martian
    5. Re:$1500 per seat by thisgooroo · · Score: 1

      i believe they said their linux license would be like the unixware license, i.e. it is not the unixware license but something similar, though probably less expensive and more profitable to SCO (imagine cashing in without investing any work of your own). prices haven't been released so far

  40. Prior art applies only to patents. by Stradenko · · Score: 1

    Two people can hold a copyright on same/similar things if those things weren't based of the other.

    Whereas with a patent, it guarantees a monopoly on said thing.
    Copyright merely guarantees that nobody can (legally) copy one's work. While still allowing them to create a same/similar work.

  41. Lots of Awards! by thews · · Score: 1

    Wow - they won an interview with a McBride and got a McCopyright... can't wait to get my hands on their McLinux release!!!

  42. Apple could make millions of friends.... by aitala · · Score: 1

    if they were to buy SCO and the grind them into dust.

    --
    Eric Aitala
    www.f1m.com
    1. Re:Apple could make millions of friends.... by wv-geek · · Score: 1

      It would make me buy a Mac :)

  43. Unbelieveable! by Cletus+the+yokel · · Score: 5, Informative

    The bullshit just keeps rising higher and higher...

    "...The company also announced it will offer
    UnixWare(R) licenses tailored to support run-time, binary use of Linux for all
    commercial users of Linux based on kernel version 2.4.x and later. SCO will
    hold harmless commercial Linux customers that purchase a UnixWare license
    against any past copyright violations, and for any future use of Linux in a
    run-only, binary format."

    So users no longer have access to Linux source? They can't recompile the kernel? Oh, that's right, Linux is an "unauthorized derivative of UNIX", so I assume they're laying claim to all of Linux now.

    "Since the year 2001 commercial Linux customers have been purchasing and receiving software that includes misappropriated UNIX software owned by SCO... While using pirated software is copyright infringement, our first choice in helping Linux customers is to give them an option that will not disrupt their IT infrastructures..."

    They have not provided any proof that Linux contains SCO IP... even if it did that does NOT mean that Linux users are committing software piracy.

    Hundreds of files of misappropriated UNIX source code and derivative UNIX
    code have been contributed to Linux in a variety of areas, including
    multi-processing capabilities. The Linux 2.2.x kernel was able to scale to 2-4 processors. With Linux 2.4.x and the 2.5.x development kernel, Linux now scales to 32 and 64 processors through the addition of advanced Symmetrical Multi-Processing (SMP) capabilities taken from UNIX System V and derivative works, in violation of SCO's contract agreements and copyrights."

    This is IBM (and formerly Sequent) code. It's NOT SCO's intellectual property. They CLAIM to have control over its distribution, but again, they haven't proven it in court. That certainly doesn't mean they own it.

    I could go on but I'm sure many brighter ones will do a better job...

    --
    Wanted: One witty yet thought provoking .sig - Apply here.
  44. Registration does not equal copyright... by dinotrac · · Score: 5, Informative

    This sounds like more than it is, but one must understand a fundamental difference between copyright and other IP, such as patents and trademarks.

    When the PTO grants a patent, it awards the actual patent itself after an investigation and a determination that the invention meets the requirements for a patent. When a trademark is registered, a different process takes place, but one that also attempts to determine the validity of the trademark.

    Copyright registrations don't do that. They just record the fact that someone claimed that something was theirs on such and such a date.
    This is a practical matter, as apart from very bare minimum standards, there isn't a very good way to investigate the validity of a copyright application short of an adversarial proceeding.

    1. Re:Registration does not equal copyright... by nous · · Score: 1
      They just record the fact that someone claimed that something was theirs on such and such a date. This is a practical matter, as apart from very bare minimum standards, there isn't a very good way to investigate the validity of a copyright application short of an adversarial proceeding.

      this is a rather important point, but presumably not everyone understands what copyright registry does, and observe this for what it is: a cheap (as can be expected) publicity stunt for SCO, and a rather silly attempt at an appearence of legitimacy.

      The real legal weight of this issue is elsewhere, probably in the documents signed between Novell and SCO, and noone except a few lawyers have seen it. [they will not be talking anywhere except in a courtroom]

      [now back to our trials and tribulations with regularly scheduled morons...]

      nous

    2. Re:Registration does not equal copyright... by dinotrac · · Score: 2, Informative

      Well, there is one more significant aspect of registration.

      You need not register your copyright to obtain copyright protection (prior to adapting the Berne convention, the United States DID require registration), but, in the United States, you must register your copyright in order to sue for infringement. You need not, however, register prior to the infringement.

      SCO is simply doing what they said they would do, and registering the copyrights is the expected next step. Absolutely predictable and having no bearing on the legitimacy of their claims.

  45. Uh, no. by mcc · · Score: 5, Informative
    They will not under any circumstances be able to forcibly charge for its use. The nature of the GPL is such that if Linux is found to be infringing on the SysV copyrights, the only options will be:
    • Convince SCO to freely license the copyrights to everyone.
    • Change the Linux code to no longer be in violation of the copyright.
    • Stop distributing linux.
    The GPL quite clearly states that if you will not provide source code to a GPLed binary you distribute, and if you will not allow someone you give GPLed source/binary to to redistribute it under the GPL, it is a GPL violation to distribute it at all. SCO can claim Linux in violation of their copyrights but they can't remove Linux from the GPL.
    1. Re:Uh, no. by Azureflare · · Score: 5, Funny

      OK so here are some options for a poll.
      SCO:
      (1) Hasn't read the GPL
      (2) Thinks the GPL is a load of bull
      (3) Thinks that GPL won't hold up in court
      (4) Hopes that IBM will buy them out before going to court
      (5) Are a bunch of fscking idiots
      (6) First against the wall when the revolution comes
      (7) Will win and 0wnzor you all
      (8) Will be bought by CowboyNeal

    2. Re:Uh, no. by Anonymous Coward · · Score: 0

      (9) All of (1) through (6), inclusive.

    3. Re:Uh, no. by inertia187 · · Score: 1

      Could someone explain how GPL could ever infringe on a copyright? Just for curiosity's sake, is it possible? What circumstances would be necessary for this to happen?

      It seems people are saying that GPL is impervious to copyright infringement. If so, I don't see how a judge would buy it. Literally.

      --
      A programmer is a machine for converting coffee into code.
    4. Re:Uh, no. by stwrtpj · · Score: 2, Funny

      You forgot an option between the last two:

      (7.5) is my employer, you insensitive clod!

      (Which it isn't, I'd like to clarify, but wanted to make the ObInsensitiveClod joke anyway)

      --
      Karma: Frotzed (mostly due to the Frobozz Magic Karma Company)
    5. Re:Uh, no. by Anonymous Coward · · Score: 0

      (1) yes
      (2) yes
      (3) yes
      (4) yes, or want #7
      (5) yes
      (6) yes
      (7) they'd like to think so, but it's not going to happen
      (8) once the trial is over and their stock is worth $.000001, CowboyNeal will be able to!

    6. Re:Uh, no. by cdrudge · · Score: 1

      you forgot, (9) All the above. Not one option is necessarily mutually exclusive from the others.

    7. Re:Uh, no. by EpsCylonB · · Score: 1

      Could someone explain how GPL could ever infringe on a copyright?

      The GPL uses copyright law to enforce it's more unique points, like having to provide source code for any changes if you distribute. If you break any of the rules in the GPL you are infringing on copyright.

    8. Re:Uh, no. by Dastardly · · Score: 1

      OK so here are some options for a poll.
      SCO:
      (1) Hasn't read the GPL
      (2) Thinks the GPL is a load of bull
      (3) Thinks that GPL won't hold up in court
      (4) Hopes that IBM will buy them out before going to court
      (5) Are a bunch of fscking idiots
      (6) First against the wall when the revolution comes
      (7) Will win and 0wnzor you all
      (8) Will be bought by CowboyNeal


      (9) Don't think Linux developers will sue anyone over illegally using Linux code.

      Dastardly

    9. Re:Uh, no. by Anonymous Coward · · Score: 0

      (9) Profit!!!

    10. Re:Uh, no. by ajwade · · Score: 1

      (9) Is run by scammers

    11. Re:Uh, no. by jrumney · · Score: 1

      (9) Will suddenly drop the case when their share price is inflated enough, and immediately offer themselves for sale.

    12. Re:Uh, no. by Anonymous Coward · · Score: 0

      OK so here are some options for a poll.
      SCO:
      (1) Hasn't read the GPL
      (2) Thinks the GPL is a load of bull
      (3) Thinks that GPL won't hold up in court
      (4) Hopes that IBM will buy them out before going to court
      (5) Are a bunch of fscking idiots
      (6) First against the wall when the revolution comes
      (7) Will win and 0wnzor you all
      (8) Will be bought by CowboyNeal


      How about:
      (6a) Inciting the revolution.

  46. Hey, no problem by Rogerborg · · Score: 4, Interesting

    We can just replace that dirty IBM contributed code with, uh, let's see, the exact same code that SCO chose to distribute themselves under the terms of a GPL license for year after year. Mmm, yup, I'll just replace it file for file, then recompile to produce an identical binary. Prove otherwise?

    Sorry about the italics. I know it's traditional to point out idiotic licensing terms USING UPPER CASE AOLSPEAK, but I thought I'd try and sneak this wheeze under the crack SCO legal team's beady eyes.

    --
    If you were blocking sigs, you wouldn't have to read this.
  47. Not so scary... by Svartalf · · Score: 5, Informative

    Since SCO distributed the OTHER portions of the code that are non-infringing with their IP intermixed, they're in an unenviable position of knowingly infringing the IP rights of other holders.

    Clause 4 of the GPL requires that you make everything you ship out to be GPL- no exceptions. They've been distributing Linux in the alleged condition for over seven months now- stating that it was "okay" for them to do so, because the alleged IP was theirs to begin with.

    They don't own the other 98% of the kernel source- other people do. And they've been distributing it for too much time to be excused for not knowing what was going on.

    --
    I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
    1. Re:Not so scary... by El+Cubano · · Score: 1

      They don't own the other 98% of the kernel source

      Not trying to troll here, but I think that saying SCO is responsible for even 2% of the kernel source is quite charitable. I don't see how they could have contributed that much.

    2. Re:Not so scary... by molarmass192 · · Score: 1

      I'm glad somebody else said it. You notice they're not actually taking anybody to court, just threatening to if you don't give them your milk money. I predict they will NEVER take anybody to court over this because they will lose, plain and simple. They have to capitalize on the threat, because the nature of the threat itself is clearly not enforceable. The only question I have is if this has crossed over into extortion. There's a decent definition of extortion here. That said, IANAL and I'm unsure what it would take to argue a case like this (other than $$$ for lawyers). In particular, I'm not sure if threat of legal action can be the basis for extortion. This differs from an obvious case of extortion as in if SCO were to say, "pay our licensing fees or we'll break your kneecaps".

      --

      Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws-Plato
    3. Re:Not so scary... by Anonymous Coward · · Score: 0

      Yes but what if the GPL has unvalid/un-enforceable clauses in it. IANAL obviously because I read /. but it could be that the Linux kernel is so big that you could miss the IP violations for a long time. But then, does SCO actually own the rights to the infringing IP?

    4. Re:Not so scary... by arivanov · · Score: 1

      PPP code is originally caldera (C) under GPL. So are a few other bits and pieces in the serial layer. So are a few bits related to IPX and some of the netware related stuff. It may as well make up 2% of the code. Who knows. Can't be bothered to look and compare with 2.0 days when quite a bit was done at Caldera. Not that it matters anyway

      --
      Baker's Law: Misery no longer loves company. Nowadays it insists on it
      http://www.sigsegv.cx/
  48. Don't just sit there. by anonymous+coword · · Score: 0

    Goto Kernel.org, download the code and start removing all SYSTEM V style stuff, such as booting, IPC. If linux is to survive it must stop being a *NIX clone, and become something unique.

  49. binary, run-only by greenskyx · · Score: 1

    "SCO is releasing binary, run-only Linux licensing" So could someone like IBM purchase this Linux and then sue for their rights under GPL (source and no patents that restrict free re-distrobution)? It seems like this is sorta do-or-die for GPL in America?

  50. This seems like a game by Azureflare · · Score: 5, Insightful
    Seems like SCO is playing a risky game, getting all the little points before the big showdown, so they can drive their stock higher and higher and then profit off it.

    I still don't understand why the legal system hasn't stepped in; Basically, SCO is saying IBM and all Linux distros are ILLEGAL, and they wave this Sys V copyright in everyone's face, as if that's proof that they own linux. How far can they go? Will they be able to scare people even more, without any kind of legal backing? How is this not libel/slander? Come on IBM, knock these guys down!

    It still mystifies me why IBM isn't doing anything at this point. They really do have to defend themselves, or they will start to look guilty, even if the charges are completely baseless (I still don't see how SCO can believe they own linux).

    1. Re:This seems like a game by jjohnson · · Score: 1

      Because copyright infringement is a civil issue, not a criminal issue, and the proper avenue for redressing civil claims is to sue for damages--which is exactly what SCO is doing to IBM, and threatening to do to any Fortune 1500 company running Linux.

      --
      Anyone who loves or hates any language, platform, or manufacturer, doesn't know what they're talking about.
    2. Re:This seems like a game by acroyear · · Score: 5, Interesting

      It still mystifies me why IBM isn't doing anything at this point.

      One thing to remember, even post-2000: IBM is SLOW. Every move is calculated, weighed, optioned, signed off by multiple layers of beauracracy, and conditioned in sherry casks, before actually being acted upon. They will make no move before they have to. Right now, they (still) don't have to, and it wouldn't help much, anyways 'cause McBride's an asshole and IBM is above all that. The bully will back down, or be taken down, but it'll happen on IBM's time because that's how IBM operates. IBM's had almost 50 years of being able to deal with this type of legal idiot; trust their experience.

      --
      "But remember, most lynch mobs aren't this nice." (H.Simpson)
      -- Joe
    3. Re:This seems like a game by mslinux · · Score: 1

      Come on IBM, knock these guys down!

      One thing is for certain: someone needs to stop this. These threats and implications are going to have an impact on Linux vendors' bottom line. RH sales *will* be hurt by this as will SuSE's.

      This is dirty business at its lowest. In the end, I hope SCO goes out of business in a bad way.

    4. Re:This seems like a game by MuParadigm · · Score: 1

      IBM has filed an amended complaint to SCO's amendment of June 16, 2003. However, SCO hasn't put it up on their web site. Nor has IBM amended complaint been put up anywhere else on the web. So IBM is responding, we just don't know yet what their response is. Also, the latest claims by SCO are not included in their last complaint. So, I'm guessing that means they will file yet another amended complaint and IBM will have to respond to that. I wouldn't expect IBM to respond to McBride & Cos. assertions until they are written up and filed in court.

  51. My bad by NetDanzr · · Score: 1

    Thanks everybody for the explanation. My bad; I tend to get copyright and patents confused in the case of software. I have an excuse, though: software code is no different from, let's say, a complech chemical formula. Thus, if pharmaceuticals are awarded patents, I always tend to think that software gets patent protection as well.

    1. Re:My bad by stoborrobots · · Score: 1

      The bad news is that they can.... There are many software patents in existance....

      The good news in this case is that SCO hasn't got any patent protection, and it's too late to get any now....

  52. Re:There can be no doubt about it by mAIsE · · Score: 3, Insightful

    If SCO didnt want to screw with Linux as they claim, they would post the offending code and the opensource world could replace it and move on.

    instead SCO is hunting to make more money where they can find it.

    Such sweethearts.

  53. No by A+nonymous+Coward · · Score: 2, Interesting

    They claim that Linux is an illegal derivative of Unix, to which they own the copyright. That's in their latest press release. What they have claimed before is that they own all sorts of crap related to Unix, and that any operating system which incorporates those ideas is violating their intellectual property rights. No joke, they seriously believe that just about every current OS violates their rights to Unix. If you are to read their comments and interviews and take them seriously, the recent license they sold to Microsoft does not preclude later claims against Windows for violating their UNIX IP rights.

    This is entirely separate from SCO code having made its way into the Linux sources.

    They also claim that any code IBM contributed to Linux belongs to SCO, because they UNIX license IBM has makes all subsequent UNIX development at IBM belong to SCO.

    The sheer arrogance is amazing.

  54. Just a piece of paper - defense is the key by Aging_Newbie · · Score: 1

    They just got the copyright office to issue them a copyright. IANAL but it says nothing about the legitimacy of their claims so they still have to defend their claims.

  55. I hope that by Anonymous Coward · · Score: 0

    some ragheads fly some airplanes into SCO..
    That would be sweet..

  56. Has that stupid bill passed yet? by roystgnr · · Score: 3, Funny

    You know, the one where they want to make placing even a single copyrighted file on the internet against the copyright holders' wishes/license a felony?

    If not, do you think it would be too risky or confuse my senator too much if I were to lobby for passing this law, let it sit on the books long enough to let McBride and everyone else in that company redistributing Linux in violation of the GPL get sent to federal, "pound me in the ass" prison, then lobby to get the law repealed afterward?

  57. Parachute? by p.rican · · Score: 1
    "McBride and his deatheaters will find themselves kicked out without a golden parachute. We can only hope!"
    1. me thinks a golden shower would be more appropriate
    --

    /. --"Demented and sad....but social" -Judd Nelson

    1. Re:Parachute? by Tackhead · · Score: 1
      > > McBride and his deatheaters will find themselves kicked out without a golden parachute. We can only hope!"
      >
      > me thinks a golden shower would be more appropriate

      "I wouldn't piss in yo' mouth if yo' stomach was on fire!"
      - Mojo Nixon

  58. Transfer, not grant by A+nonymous+Coward · · Score: 1

    I believe the recent action merely transferred the copyright, which had been granted long ago.

  59. I love this by Anonymous Coward · · Score: 0

    Your always hearing of SCO doing this, this, and that. Where's IBM, no where to be found. Why? Well, IBM sees that SCO is bringing on their own doom, and IBM doesn't have to do anything.

    As far as SCO's Linux licensing, I think I can say what we are all thinking, SCO can suck my big fat dick.

  60. mod parent up by Anonymous Coward · · Score: 0

    copyright only grants certain specific rights governing distribution, too many people don't get this

  61. They want you to buy a SCO license for EVERY copy by DASHSL0T · · Score: 4, Informative

    They want all commercial customers to pay for a Unixware 7.1.3 license for EVERY copy of Linux they are running.

    Here's my rundown of the call

    --
    Freedom Is Universal
    Linux-Universe
  62. it WOULD do MS a lot of good. by gosand · · Score: 1
    I wonder if they knew who they were going to bed with when they bought a license from SCO to keep them afloat. As much as I despise Microsoft, I can't believe this would do them any good, except in the short term FUD department. If SCO can claim ownership of Linux, it doesn't seem like a far stretch to own every other OS which ever borrowed from Unix ideas.

    Wouldn't do MS any good? If it went that far, who do you think would purchase SCO?

    Do I think it will go that far? No. Would it surprise me if it did? Unfortunately, no. IP laws are just that stupid. I think SCO execs are looking for a way out, and MS could very well be their "daddy" on this whole thing.

    --

    My beliefs do not require that you agree with them.

  63. Letter to SCO by Anonymous Coward · · Score: 5, Funny

    Dear SCO,

    As a contributer to the Linux kernel, I have decided to start a new licensing program. Your company will be required to pay a fee of 5000 USD per cpu on all installations of Linux you use or sell which include my code. Regrettably, I cannot tell you which lines these are, as doing so would my trade secrets to the world.

    Also, I have identified numerous cases in which lines of my code were copied into the source for your Unixware product. The same licensing terms I have descibed above will therefore apply to Unixware.

    I have sent letters to all 5 of your customers informing them of this new policy. I understand Sun has also been in touch with them.

    I will be contacting you soon to discuss payment options.

    Thank you.

    1. Re:Letter to SCO by Anonymous Coward · · Score: 0

      Hmm, fix the grammer and you might have a good form letter. Shame that no linux geeks actualy have the ablls to defend themselves.

  64. wow by Anonymous Coward · · Score: 0

    that was an informative reply



    TOOL

    1. Re:wow by classic66coupe · · Score: 1, Funny

      I'm sorry, I will be more informative. You are an idiot.

  65. Better idea by Anonymous Coward · · Score: 1

    In our contry we use to hire a Hitman. Works better than a lawyer.

  66. Wow... by Anonymous Coward · · Score: 0

    The poor guy looks like he hasn't slept in a couple of months. Ya know, he's not a bad looking guy though. Yes, he's rather hot, in fact.

  67. How will SCO compensate kernel other developers? by GodWasAnAlien · · Score: 1

    SCO expects to be compensated for supposed 1% of the kernel code.

    It looks like SCO is inciting people to violate the GPL, and willfully violating the GPL themselves.

    This invalidates the GPL licence and means that SCO is violating the copyright of 99% of the kernel code, along with extorting others to do the same.

    Because of this, SCO needs to pay damages to the Linux source code that it is pirating ( and encouraging to pirate).

    If SCO beleives that it is due 1 * x, where x is some compensation for its supposed source code, then SCO now owes 99 * x to the other linux developers.

  68. Copyright Registration Does Not Guarantee A Win by Anonymous Coward · · Score: 1, Interesting

    Ooo. They got registration for a copyright. Big deal. Copyright ownership can still be challenged and owning a copyright doesn't guarantee that the other side is infringing that copyright.

    While this might be good PR for SCO, registration does not indicate any likelihood of success regarding this situation.

  69. Other information from the call by DevilM · · Score: 5, Interesting

    When asked about dealings with Linus, SCO indicated that they had only done email exchanges and that Linus had indicated the situation was a contract dispute and he was staying out of it. McBride then went on to say that as of today everything has changed. SCO stated that everyone involved with Linux from the users to the contributors to the distributors are either violation of their Unix copyrights or are contributing to the violation. They also stated that they could sue for copyright violations without showing damages.

  70. SCO is just plain nuts by plazman30 · · Score: 1

    I don't know if anyone read an interview a while back with McBride, but he's claiming 2 other points:

    1. ALL modern operating systems are dervied from Sys V UNIX and they may be due royalties from companies like Microsoft and Novell.

    2. SCO feels there were errors in the original agreement from Berkely and AT&T and they think they will need to audit all the BSD kernels to make sure no SCO IP was left in those kernels after the AT&T agreement.

    So, basically, if you make an OS of any kind whatsoever, you owe SCO royalties.

    They're just out of control.

  71. *BSD is not dying by yerricde · · Score: 1

    Or just switch to *BSD. If SCO wins and manages to declare some core Linux component as infringing, guess what will be thriving instead of dying.

    --
    Will I retire or break 10K?
    1. Re:*BSD is not dying by smash · · Score: 1
      Heh.

      As far as my servers go, FreeBSD is alive and well, and Linux is dying (being replaced with stuff that works according to the documentation, first time, every time :D

      smash :)

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  72. Impossible by gotan · · Score: 5, Insightful

    And it's impossible too: the GPL is incompatible with licensing and run-only-binary-distribution (unless the sourcecode is made available). So SCO can't sell a run-only binary distribution under their licensing terms and any distributor who accepts SCOs licensing terms and imposes them on his customers can't distribute anything either since he would violate the GPL.

    Violating the GPL means that it is replaced by normal copyright of all the individuals who contributed to the kernel (we're still only talking about the Linux-kernel here) and you need to make explicit deals with each of them to distribute the kernel-code as a whole. It is more likeley that most of those copyrightholders will sue SCO for infringing on their copyrights by distributing their Linux under a restrictive license, in violation of the GPL and hence without permission.

    This is just SCO raising up the ante again spewing propaganda to up their shares another few bucks. On the day their bubble bursts and the shares fall through the floor, i will cheer and gleefully tell all those idiots who bet their money on SCO 0wn1ng Linux, that Linux can't be 0wn3d and never will be.

    --
    "By the way if anyone here is in advertising or marketing... kill yourself." -- Bill Hicks
    1. Re:Impossible by PhilHibbs · · Score: 1
      SCO are saying that there is IP in Linux that they own. They are therefore selling licences to use that IP. From a GPL point of view, I don't see the problem. If they are continuing to distribute Linux, then they are jeopardising their rights, but they could probably get away with the current situation in court if they can demonstrate that
      1. they own the IP that is in Linux
      2. they did not know that their IP had been introduced to Linux
      Even if they are distributing Linux, I don't think a judge is going to say that their rights are waived just because they had some 'freely redistributable' binaries on their servers, that you can download from a thousand servers all over the world.
    2. Re:Impossible by gotan · · Score: 1

      This is not about SCO unknowingly GPLing their code by distributing a Linux-distribution (that might have contained some of their code without their knowledge) themselves. It's about them distributing Linux (or more generally GPLd code) under a restrictive License. Even if a judge decides that some of the code in Linux (the kernel) is under SCO-copyright and hence has to be licensed with SCO to be further distributed, the majority of Linux is copyrighted by others, not by SCO.

      All those contributions to the kernel are GPLd. The GPL is what gives anyone the rights to further distribute all that copyrighted code in the kernel. So everyone who distributes Linux has to obey the terms of the GPL. If he violates the GPL that invalidates his rights to distribute the GPLd code and if he goes ahead to distribute the code he infringes on all those copyrights that are not his own.

      Distribution of Linux under a restrictive license is in violation of the GPL. Distributing Linux without giving out the source-code also is. And tightly bundling Linux-kernel code with proprietary code is too (the best you could do is writing some proprietary modules and then you better use the proper interfaces, but that is useful for hardware-drivers, not for central kernel-routines).

      So there is no way SCO can demand license fees for Linux, be it their own distribution or someone elses. Neither can they give out a "binary only" distribution, they have to provide the source-code and that source-code must be GPLd (and now they can't claim anymore that they unknowingly distribute their own code, so they better clean it from anything they don't want to put under GPL).

      To summarize: SCO can either distribute Linux under GPL or not at all. Their claims of being in a position to sell "Linux licenses" is bogus and serves just to boost their shares.

      --
      "By the way if anyone here is in advertising or marketing... kill yourself." -- Bill Hicks
    3. Re:Impossible by Anonymous Coward · · Score: 0
      Over and over and over distribute

      They are going to give out a piece of paper that holds harmless the linux user!

      No code

      None

      Not even Unixware(R)

      They are not planning to distribute Linux, just licences. That may not really get them out of a GPL violation, but it gives their legal team some leverage.

      Best of luck getting a simple one line solution to this problem!

    4. Re:Impossible by gotan · · Score: 1

      That would mean that noone can distribute Linux any longer, any form of license fees is incompatible with the GPL, the code must be freely redistributable. I think that would spur IBM, Redhat, Suse and anyone else doing business with Linux into action finally since otherwise they would open themselves up for lawsuits from all those kernel-developers who contributed GPLd code. If SCO can grab a piece of the cake the GPL is invalidated and everyone who copyrighted a bit of code can claim their share too. Even if most of them are to idealistic to do it for the money they might perceive this as the best way to make IBM deal with SCO.

      --
      "By the way if anyone here is in advertising or marketing... kill yourself." -- Bill Hicks
    5. Re:Impossible by PhilHibbs · · Score: 1
      Distribution of Linux under a restrictive license is in violation of the GPL.
      So what they need to do, then, is to stop distributing Linux. Then they can sell licences to existing Linux users without violating the GPL.
  73. nope, not really by dh003i · · Score: 1

    If they can prove that Linux infringes upon SysV code that they claim to own, then that code will be removed from Linux and replaced. Period. There will be no issue of charging for it's use. They certainly can't charge for it's use now, as they haven't even shown what code is allegedly infringing. If you tell someone their infringing your copyright, but don't give them the information to allow them to stop infringing, then any legal case you have will go nowhere.

    If there is any validity to their claims, the offending code will be expunged from Linux and replaced, which will conclusively end the matter.

    In any event, they already GPL'ed all of their code by releasing a GNU/Linux distribution.

  74. HA! by GirTheRobot · · Score: 1

    This is hillarious! SCO doesnt have a leg to stand on! SCO released a verion of Linux under the GPL, so even if their code is in the kernel, anyone can use Linux free of charge! And if these fools release a binary-only distribution of Linux they will be violating the GPL, and developers will be able to file a class action suit against SCO. It might even be a good thing if that happenes. Winning the court case would be a sure thing and punitive damages could be awarded to developers to help fund their projects.

  75. Sure looks that way by A+nonymous+Coward · · Score: 4, Interesting

    And that's a very intriguing development, from the point of Redmond. Defeating the GPL likely will invalidate just about every other software license. Not only is there a real question of whether SCO wants what they appear to be going after, but you have to wonder about what is going on at Microsoft right now ... no way do they want software licensing defeated. As much as they want to destroy the GPL, I can't believe they want to destroy licensing itself. I imagine all sorts of shock in Microsoft conference rooms right now.

    1. Re:Sure looks that way by Anonymous Coward · · Score: 2, Insightful
      Defeating the GPL likely will invalidate just about every other software license.

      LMAO. No it wouldn't, as the GPL alone has a contradictory nature all to itself, namely that the licensor doesn't have to check for IP infringement (because they can't without tainting themself) before changing the license to a freely copyable one. There's also completely lacking liability to the thing as a whole, something that courts aren't going to be prone to allowing.

    2. Re:Sure looks that way by puppet10 · · Score: 1

      Most commercial propreitary software disclaims all liability as well.

      --
      -------- This space intentionally left blank --------
    3. Re:Sure looks that way by Anonymous Coward · · Score: 0

      Yes, but with commercial software there is a liable authority, with accountability, something Linux does not want or have.

      Here's a simple example. A former programmer from M$ takes the Office source and gives it to an OSS programmer and says "here this is yours". After seeing what it did, and liking it, the OSS programmer immediately put it in his latest Linux distro, and propogated it out around the world.

      Now let's say millions of users download this Office software from this Linux website (ANY of them) that now included it as part of their 'package', and started using it at incredible amounts. M$ finds out, and wants to sue for damages (which could be a lot if a million people started using Office illegally!)

      According to GPL advocates, this former M$ programmer is COMPLETELY liable for everything that happened. Maybe, but there's no way in hell he can afford to make restitution back to M$ anywhere close to the damage figure.

      This is why modern business societies require public registration and busines licenses for entering the economy, especially if incomes reach certain amounts or if you cross borders of most sorts. The GPL doesn't fit into that model well, and unfortunately for them the ones that control that market (and these courts) are going to eat their lunch before this is over.

    4. Re:Sure looks that way by EzInKy · · Score: 1

      LMAO. No it wouldn't, as the GPL alone has a contradictory nature all to itself, namely that the licensor doesn't have to check for IP infringement (because they can't without tainting themself) before changing the license to a freely copyable one. There's also completely lacking liability to the thing as a whole, something that courts aren't going to be prone to allowing.

      I see...and of course licensors of Microsoft code have to check that Microsoft didn't infringe any IP before accepting their EULA.

      --
      Time is what keeps everything from happening all at once.
    5. Re:Sure looks that way by _Sprocket_ · · Score: 2, Insightful


      No it wouldn't, as the GPL alone has a contradictory nature all to itself, namely that the licensor doesn't have to check for IP infringement (because they can't without tainting themself) before changing the license to a freely copyable one. There's also completely lacking liability to the thing as a whole, something that courts aren't going to be prone to allowing.


      Perhapse you could explain how the GPL differs from proprietary licenses in both checking for infringement or liability.

      Surely when I'm coding for a project under a proprietary license, I'm just as suceptible to infringement and "tainting" as when I code for a GPL licensed project.

      And the license I work under doesn't do much to protect me from liability. Sure - working as an agent to a large corporation might shield me personally from damages. But that works the same whether I'm working under the GPL or proprietary license. If I'm working for a small company, I have less protection. If that small company happens to be me and I haven't taken legal steps to limit my liability... I'm at even more risk.

      And, of course, it doesn't matter if I'm working for a mega-corp if my actions were not performed as an agent of that company but rather on my own accord. For example, I leaked that company's proprietary code, trade secrets, etc.

    6. Re:Sure looks that way by Anonymous Coward · · Score: 0
      Perhapse you could explain how the GPL differs from proprietary licenses in both checking for infringement or liability.

      I already did, on another post in this thread, and I should be getting paid for enlightening some of you on here.

      'Legal Accountability' is the answer, it's best evidenced as Linux's distributors desire to distribute the code freely but evade any legal liability.

      'Restitution' is what you don't understand, and it is an important part of any business economy law. Being an OSS contributor, if you even accidentally imbed some proprietary code and it makes it's way into Linux, *YOU* are going to be the one that Torvalds and Red Hat and everybody else who distributed it is going to want to pay for the distribution *THEY* did.

      When Apple comes beating down your door with the next Linux lawsuit, that cost them $20 million in damages because kernel.org already gave your code to 20 million people maybe you'll see what I'm saying.

    7. Re:Sure looks that way by WNight · · Score: 1

      Gifts don't come with warranties. Free software is a gift, just like a free cookie. Why should the software have a warranty and not the cookie?

      The only "warranty" either comes with is that the giver can't intend to do harm, or expect that harm will occur and not warn the receiver. In other words, I can't give you a poisoned cookie without telling you. But, if I tell you that the cookie is poisoned to the best of my knowledge, it's legal; you could want to use it for rat poison.

      For software, if I know it's got a virus and don't tell you, I'm at fault. If it simply might be harmful I only need to represent it properly, "Free software: Only partially tested!" to absolve myself of *all* damages.

    8. Re:Sure looks that way by _Sprocket_ · · Score: 1


      I already did, on another post in this thread, and I should be getting paid for enlightening some of you on here.


      Yea. I saw that other post. It didn't seem too enlightening.


      When Apple comes beating down your door with the next Linux lawsuit, that cost them $20 million in damages because kernel.org already gave your code to 20 million people maybe you'll see what I'm saying.


      How is GPL licensed code any different than a proprietary license in this case? Or public domain?

      If I manage to infringe on Apple's license it won't matter under what licence I've released that infringing IP. I can release it to the public domain. I can license it under the GPL. I can give it a proprietary license.

      Lets say I created a library out of this infringing IP. A large software company then licensed this library from me under a proprietary license. They used it in an application that was widely distributed - lets say it was widely popular and released at no cost. When our hypothetical software company gets caught up in legal wrangling with Apple and track the infringing IP back to my library and its proprietary license... am I off scott free? Am I free from this "restitution" you keep talking about?

      How about if I released my library cost-free, as postcard-ware, or share-ware? Or I release my code to the public domain? Has my liability changed? Will I face any less the cost of restitution since I didn't use the GPL?

      How about if my library was released under the GPL as a part of the work I was doing as an employee to a large corporation? Perhapse this is different. Because now, instead of just me alone, I have my employer to take some of the brunt of this legal liability and possibly to even absorb this restitution. If they decide to protect me and if I did this work as their agent.

      What you're talking about really has nothing to do with the license and everything to do with who you work for.
    9. Re:Sure looks that way by Anonymous Coward · · Score: 0
      If I manage to infringe on Apple's license it won't matter under what licence I've released that infringing IP.

      That statement alone shows how little respect for (and understanding of) intellectual property rights.

    10. Re:Sure looks that way by Anonymous Coward · · Score: 0
      How about if I released my library cost-free, as postcard-ware, or share-ware? Or I release my code to the public domain? Has my liability changed? Will I face any less the cost of restitution since I didn't use the GPL?

      Yes, if it contains proprietary code, you will, THE PROGRAMMER, will be liable, not THE COMPANY.

      Most programmers can't restitute, so this GPL creates an environment that is condusive or likely to result in infringement that can't be compensated.

    11. Re:Sure looks that way by moncyb · · Score: 1

      According to GPL advocates, this former M$ programmer is COMPLETELY liable for everything that happened.

      So, you are saying the person who committed the crime isn't responsible, and the people he defrauded are? This doesn't mean anyone is allowed to use that source once they find out it is tainted. What planet are you from? Let me guess: the United States Soviet Republic.

      This is why modern business societies require public registration and busines licenses for entering the economy

      I'm sure the Nazis did too. Maybe /. should require public registration and business licenses for posting to their site. ACs are all trolls now.

    12. Re:Sure looks that way by _Sprocket_ · · Score: 1


      Yes, if it contains proprietary code, you will, THE PROGRAMMER, will be liable, not THE COMPANY.


      Right. So if I infringe on someone else's IP, I am liable no matter what license the infringing property was released under.


      Most programmers can't restitute, so this GPL creates an environment that is condusive or likely to result in infringement that can't be compensated.


      There are hundreds of small companies (let alone individuals) out there publishing software under any number of various proprietary licenses. They also have shallow pockets and little ability to restitute. How are they different?

      Again. It isn't about the GPL. Its about the size of the company involved and whether you are acting as an agent of that company.
    13. Re:Sure looks that way by Anonymous Coward · · Score: 0
      So, you are saying the person who committed the crime isn't responsible, and the people he defrauded are?

      No, just that whoever actually put it into the kernel, and subsquently flash distributed it to 10,000 mirror sites has some responsibility as well. Torvalds is a fool if he thinks he can sit protected behind the GPL while hell unleashes around him.

    14. Re:Sure looks that way by _Sprocket_ · · Score: 1

      Let me restate that.

      If I manage to infringe on Apple's IP, it won't matter under what license I've released that infringing IP.

      Better?

    15. Re:Sure looks that way by ralphclark · · Score: 0, Offtopic

      What's that bad smell? Oh no, the Microsoft employees are visiting Slashdot again.

    16. Re:Sure looks that way by ces · · Score: 0

      I'm sorry but how is free software different from the following:

      ABC corp distributes a software product.
      ABC gets a perpetual license for a component from XYZ corp. This licensed component is part of ABC's software product.
      DEF corp asserts that XYZ stole the code it licensed to ABC. DEF sues ABC for damages.
      ABC claims they licensed the component in good faith from XYZ and therefore aren't liable.

      I will also point out that under US law individuals are quite able to hold copyrights, patents and trademarks.

      --
      Happy Fun Ball is for external use only.
    17. Re:Sure looks that way by Nucleon500 · · Score: 1
      Most programmers can't restitute, so this GPL creates an environment that is condusive or likely to result in infringement that can't be compensated.

      So you're basically saying that it should be illegal to write software unless you're rich? Wow.

  76. Time to Short SCO!!!!! by Anonymous Coward · · Score: 0

    Ok, looks like it's ALMOST time to sell SCO, wait for it to nose dive when the SEC comes after them for manipulating the stock price, and buy to cover!!!

  77. hmm... by smash · · Score: 1
    Is this bullshit still going on?

    Something tells me the brains at sco left a long time ago, and the company is now flailing about like a headless chicken, with the legal dept in control.

    Then again, since the BSDs have already been cleared of using proprietry code in court, I haven't been paying a great deal of attention :)

    smash.

    --
    I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  78. Just what we need by manonthespoon · · Score: 1
    Linux has in the last few years really started to get the attention of big corps, and just the other day Microsoft finally admitted that linux has them scared. I also know that days after this whole SCO thing started MS was one of the first companies to purchase licensing rights to SCO IP.

    I don't believe it's a coincidence. MS has been looking for an opportunity like this for quite a while. Companies that were unsure about linux because of issues like support and licensing will be scared away by garbage like this, concerned that at any moment they'll be required to license something that was supposed to be Free.

    This is exactly what the oponents of Free/Open Source software need to try to stop linuxs growth into the marketplace. Scare tactics and vague claims. I doubt many people will be switching over to linux in the coming months, and companies considering it are going to have second thoughts. Linux vendors now have to attempt to reassure people that the product they are selling is really what it's supposed to be.

    Anyway, this is ridiculous. This is extremely damaging to the image of Linux as a platform, and any business attempting to make money off of linux should start screaming for SCO's blood now. Redhat, Suse, Mandrake, IBM, Google, ... etc. This needs to be stopped, and the sooner the better.

  79. The GPL war is near by picz · · Score: 5, Insightful

    This is the beginning of a stream of events, that eventually will be known as the Great GPL War.

    A company can not claim ownership of a few lines of code, and than steal millions of GPL-ed lines, package them and sell them. This is outrageous.

    FSF is forced to react on this one. GPL is going to court.

    regards
    PiCz

    --
    ------- Look mum! I have posted another Slashdot comment! --------
    1. Re:The GPL war is near by Chicane-UK · · Score: 2, Interesting

      Agreed.. I can't see how SCO will continue to get away with this. It seems a bit of an irony that SCO want to protect the IP (god I hate that term) and work by all of those Unix engineers from so long ago.. yet is quite content to steamroller & attempt to claim ownership of all the hardwork and effort by the Linux coders of the past 10 or 11 years.

      Laughable.

      Please.. IBM, just take them to court or something!!

      --
      "Hey! Unless this is a nude love-in, get the hell off my property!!"
    2. Re:The GPL war is near by Anonymous Coward · · Score: 0

      The people who can take SCO to court are the people who own the source code in question, i.e., not the FSF but Linux Torvalds and other contributors.

      The FSF is likely to militate against SCO, and also to point to the brouhaha as validation on their conservative policies about copyright (i.e., insisting on transfer of the copyright to the FSF in some cases, documentation including a written letter from your employer that they don't own the work or else approve it's GPL'd release, etc).

      I think the most likely thing that will happen is that SCO will go after some soft, wimpy targets and get them to actually pay up. The first few will be complying to help the game along, i.e., MS buying licenses, next is Ransom Love, then small companies easily legalistically terrorized, etc.

      Eventually they'll hit too many people who just say no, or start a longer court case that they lose or will take more money than they hope to extract, and they'll fold up this game and move on.

      Essentially, this is a tax on companies who believe lawyers and press releases. And inspite of the nastiness of it all, there are good things in taxing wimpyness. If you fold over to SCO, then maybe you deserve to go out of business. Because you certainly aren't going to represent America very well in the hard-core overseas markets. If you cut McBride a check just because you got a couple of letters and maybe served with a suit, there's no way you can do business in Hong Kong or Taiwan and not get fleaced. So maybe America is best off shedding those businesses along with all the other dead wood falling in this depression.

    3. Re:The GPL war is near by Kismet · · Score: 4, Insightful

      If I recall, the FSF owns a number of copyrights on code in the Linux Kernel, including some bits contributed by IBM that may be in question.

      To date, the only FSF response to SCO has been a subtle Linux should really be called "GNU/Linux" diatribe (See! we told you so!).

      The most informative SCO response to date is still the OSI position paper by Eric Raymond et al.

      I believe that the FSF and the OSI, in addition to the other Kernel copyright holders, should indeed seek legal action against SCO. I would like to see something spectacular, although any countersuit is likely to be limited - due to the nature of copyright law. I think the obvious action is simply to force SCO to disclose what infringing code exists.

      This assumes, though, that the disclosed code really does infringe, which is somewhat unlikely (it was never in the interest of Linux development to allow proprietary code).

      I think there is a lot the Linux developers could do to mitigate the damages on our side.

      The Linux stewards need to lay to rest the myth that we don't really know where all of our code came from. Every line of code in the project has somebody's name on it, and there is someone out there who can vouch for it. If, in this process, we discover some holes, we have the power to fix them - we don't depend on SCO to tell us what is clean and what is not clean. It is dangerous to let SCO tell us what is theirs and what is ours because they are bent on claiming as much as posible, now matter how ridiculous the connection.

      Having a very public Linux Accountability Project does a huge amount of good for the Linux cause.

      1) There are very few commercial organizations that have anything like it. In addition to a totally transparent development model, in which all of the "property" can be examined by the public, the fact that the Linux community itself stands behind every line of code lends more credibility to it than any closed-source program.

      2) It establishes a factual base from which to discuss the SCO claims. Currently, the only context that we have for discussion is SCO's outrageous allegations. We have the code, why don't we talk about it on our terms? Why must we prove SCO wrong? Why shouldn't they have to prove themselves right instead? This would be the case if we had a public manifest of all aspects of the Linux Kernel. If the public could see who the players are with a brief description of the origins of the features and a statement from the developers themselves, then SCO might have a lot more explaining to do.

      I believe that this sort of a project can be accomplished in a reasonable amount of time. It might delay further development on Linux for a little while - losses that would be quantified and then extraced from SCO in the countersuits to follow - but it would be well worth it.

      I also highly recommend that every Open Source developer keep a detailed log of all of their development so that, at any time, complete accountability can be made for your program. Don't let greedy corporations claim your work!

      Well, I've digressed from the topic, so I'll shut up...

    4. Re:The GPL war is near by brlancer · · Score: 1
      LUKE: No, my father didn't fight in the wars. He was a programmer on Windows Media Player.

      OBI-WAN: That's what your uncle told you. He didn't hold with your father's ideals. Thought he should have stayed here and not gotten involved.

      LUKE: You fought in the GPL Wars?

      OBI-WAN: Yes, I was once a Kernel Hacker like your father.

      LUKE: I wish I'd known him.

      OBI-WAN: He was the best object programmer in the galaxy, and a leet sysadmin. I understand you've become quite a good scripter, yourself. And he was a good friend. Which reminds me... I have something here for you. Your father wanted you to have this when you were old enough, but your uncle wouldn't allow it. He feared you might follow old Obi-Wan on some damned-fool idealistic crusade like your father did.

      LUKE: What is it?

      OBI-WAN: Your fathers compiler. This is the weapon of a Kernel Hacker. Not as clumsy or as random as an interpretter. An elegant weapon for a more civilized time. For over a thirty years Kernel Hackers were the guardians of CPU cycles and disk utilization in the Old Republic. Before the dark times, before the Empire.

      --
      Someone asked if I had patched against MSBlast; I said yes, I installed Linux.
    5. Re:The GPL war is near by Anonymous Coward · · Score: 0

      Nice one.

    6. Re:The GPL war is near by mattite · · Score: 1

      I agree with you. A Linux Accountability Project would be a great way to keep track of who contributed what. It would protect linux against further attacks such as SCO's. Since it's your idea, I vote you take the lead. If I can help in any way, let me know.

    7. Re:The GPL war is near by leandrod · · Score: 1
      > the only FSF response to SCO has been a subtle Linux should really be called "GNU/Linux" diatribe

      No, it was a quite clear position. And you have to take into account that it is too soon for the FSF to gear into action; SCO first must clarify its claims, and it has already stated it isn't in a hurry, its goal being to FUD people into paying UnixWare licenses. Furthermore, if the FSF would step into the scene as a Linux copyright holder, there would be a big backslash by FSF haters involved in the kernel works, like Larry McVoy and his sympathisers. So the FSF has to tread carefully here.

      You have to remember that the FSF already has your Accountability Project in place for several years: its copyrights assignment requirement policy. Linus has more than once clearly stated his refusal to follow this line, he thinks he's covered enough. But several years ago the FSF had clearly stated the dangers of such a policy as Linus follows.

      In the end, it may be in the FSF best interest to avoid the Linux fight at all and concentrate into getting the Hurd done, as it is completly free from such worries and is even more free (no binary modules or firmware) than Linux.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
  80. I'm not afraid at all. by twitter · · Score: 1
    Won't it just be easier (if there's any grounds for their action) to zap the offending code from the kernel or are they going to prevent this by not actually telling anyone where it is?

    Ding, ding, that's true, and so long as SCO keeps it's mouth shut about what's actually infringing, I'll just abide by the kernel license, the GPL. I don't have much to say to SCO people except that they can come and get free software if they are in Baton Rouge today. This offer, of course, extends to anyone who happens to be in Baton Rouge today.

    --

    Friends don't help friends install M$ junk.

  81. hey, how about some REAL action?? by Anonymous Coward · · Score: 0

    Someone should post the home addresses of these scumbags. Then maybe Tony Soprano and Co. could go pay them a nice visit in the middle of the night, like sometime really, really soon...

    Eh???

    Someone out there is bound to have the dirt on these low lifes....

  82. BSD by crotherm · · Score: 4, Insightful

    never sounded so good... :)

    So what are the odds that Stallman is secretly enjoying this while toiling away at the hurd?

    --
    "Those who make peaceful revolution impossible, make violent revolution inevitable" - JFK
    1. Re:BSD by Anonymous Coward · · Score: 0

      Indeed.

  83. MOD PARENT UP by Anonymous Coward · · Score: 0

    I wish I had some points...people need to realize that what you say is absolutely correct. SCO can never license Linux under a license other than GPL.

  84. Search engines by GammaTau · · Score: 1

    It's well understood that the SCO FUD machine is trying to reach as much publicity as it possibly can. This is why it is important to let the other side of the force to get some publicity as well. One way is to make links to sites that deal with the SCO FUD from Linux users' viewpoint in order to get better rank in search engines. One of the best sites is at sco.iwethey.org.

    Please consider linking.

  85. Not that simple by A+nonymous+Coward · · Score: 4, Insightful

    You do not understand the arrogance of McBride and his brethren. He has claimed in interviews that all of Linux, and every other UNIX clone, is a derivative of UNIX, whether the code was developed from scratch or not. He even hinted that Windows was not immune to this, that the license bought by Microsoft did not protect them from being sued for violating SCO rights concerning UNIX.

    1. Re:Not that simple by Dastardly · · Score: 1

      You do not understand the arrogance of McBride and his brethren. He has claimed in interviews that all of Linux, and every other UNIX clone, is a derivative of UNIX, whether the code was developed from scratch or not. He even hinted that Windows was not immune to this, that the license bought by Microsoft did not protect them from being sued for violating SCO rights concerning UNIX.

      Except the people who developed most of Linux did not sign a contract stating that SCO owned their code. Therefore, there code can only be distirbuted under the GPL. There are only two choices SCO has if their code is in Linux.

      1) SCO licenses the code under the GPL.
      2) SCO does not license the code under the GPL and all of Linux is in violation of either SCO's IP or Linux developers IP and therefore cannot be distributed or used at all.

      Note, the idiots who say the GPL is a distribution license are missing an important point. Just because you happen to have the code now, doesn't mean it was legally distributed to you. If SCO's code is in the kernel, either you received the kernel illegally according to the GPL or you received the kernel illegally according to SCO.

      Basically, SCO doesn't seem to realize that by claiming copyright infringement and requiring a license fee to be paid to them, they are going for a scorched earth policy with Linux. No one should pay SCO to license their Linux code because it will not protect them at all, and actually open the purchasers to litigation for illegally using all the other code in Linux.

      Maybe SCO is hoping that instead of causing all recent Linux kernels to become illegal Linux developers will let this go, but I doubt that will happen.

      Dastardly

    2. Re:Not that simple by dissy · · Score: 4, Interesting

      > You do not understand the arrogance of McBride and his brethren. He has
      > claimed in interviews that all of Linux, and every other UNIX clone, is a
      > derivative of UNIX, whether the code was developed from scratch or not. He
      > even hinted that Windows was not immune to this, that the license bought by
      > Microsoft did not protect them from being sued for violating SCO rights
      > concerning UNIX.

      Yea, but he can claim copyright to sunlight too and it doesnt make it any more true in a court of law :)

      If they had any basis for this, we would have seen it.
      Ford would have sued all other car makers for making cars, as they own the copyright on cars.
      Authors would sue others for having a book with the same plot line.
      All music would go away, after all, your rock song is based off my rock song, and the first song has a copyright on rock music.

      Copyright doesnt apply to basic concepts.
      Only to very specific cases of those concepts.

      If they won, not just the american way of life is over as we know it (Nothing new will be allowed to be created, because its all based off previous work.. that is how technology works) but the entire world economy will fail for a short time, as we sue and press charges aginst every other country there is until the US is finally shunned as a world power and we are ignored.

      This will _never_ be allowed to happen.
      Bush would come right up and tell the courts to fuck right the hell off if they even tried.

      But the point is, copyright law does not give ANYONE the right to do what they are claiming over at SCO.

      If you wrote some code, and copyrighted it, and i stole that code, you can ONLY tell me to not distribute it.
      As a matter of fact, i am perfectly within the bounds of copyright law to take your copyrighted work and use it however i see fit, as long as it never leaves my hands. You have no say so over the matter. They would legally (and in all cases in the past) side with me.

      Copyright prevents the distribution of others works.
      The only right they have (assuming they are correct) is they can say 'noone has the right to distribute our code'
      And as I said, the problem would be fixed by replacing that code, or just removing it all together. Then they have no legal right to say anything.

      They have no legal right to charge for linux, and are activly breaking the law by distributing it in binary only form without the source, even IF they win their dispute aginst IBM.

      Think of it this way.
      Band B steals some lyrics from Band A.
      Does this give the world the right to steal all of Band B's music because their copyrights are somehow invalid now?
      No.
      Nor does SCO have any right to invalidate the copyright of thousands of developers who have copyrighted code in the kernel as well, whom are licencing it under GPL.
      SCO owns their little part. Nothing more. Any any more that they take is copyright-voilation (Or theft as p2p haters like to call it)

    3. Re:Not that simple by A_Non_Moose · · Score: 1

      Think of it this way.
      Band B steals some lyrics from Band A.
      Does this give the world the right to steal all of Band B's music because their copyrights are somehow invalid now?
      No.


      Good point, but "Don't tell my heart, my achin' breakin' heart"...which was swiped, IIRC, and changed to Achey-breakey...and later ruled by a judged to be a different song.

      Uh-huh.

      (of course, "my generation's parents sued John Fogarty for plagarizing his own songs/riffs".)

      {sigh}

      --
      Have you read the moderator guidelines? Well, have you, PUNK? (and I want a Karma: Gnarly option)
    4. Re:Not that simple by pmz · · Score: 1

      He even hinted that Windows was not immune to this...

      Given that parts of Windows are really FreeBSD in disguise, I guess this isn't suprising.

    5. Re:Not that simple by GuidoJ · · Score: 1

      Please keep in mind that there are two entirely separate cases:

      1) The copyright to certain System V code, of which supposedly parts have ended up into the linux kernel, and for which they now have a registration so that they can use it in court.

      2) The intellectual property of certain Operating System fundamentals in general, and they claim that all flavours of Unix, linux and even MS Windows are at least partly based on these fundamentals.

      The first is a simple case: just compare the code, but let's face it, this will not make them much money, compared to what they would make if they won the second case. The problem is that by doing that they will automatically reveal their IP, which will make the second case probably a lot harder.

      SCO's going for the IP (you would too), only if they cannot win that, they'll come after linux distributers/users/developers.

    6. Re:Not that simple by jrumney · · Score: 1

      Linus did not sign a contract allegedly assigning SCO rights over his code. So even if it was a "derivitive of UNIX", SCO would not own any rights to it unless there were patents involved (which has already been scrutinized and found not to be the case).

    7. Re:Not that simple by johannesg · · Score: 1
      Authors would sue others for having a book with the same plot line.

      Like the author of "Tanja Grotter" was sued by the author of "Harry Potter"? And lost because the plotlines were too similar? See here for example...

      Actually I'm more inclined that this was a case of seriously fucked up justice, but it goes to show that it _does_ happen.

    8. Re:Not that simple by Anonymous Coward · · Score: 0

      If you wrote some code, and copyrighted it, and i stole that code, you can ONLY tell me to not distribute it.
      As a matter of fact, i am perfectly within the bounds of copyright law to take your copyrighted work and use it however i see fit, as long as it never leaves my hands. You have no say so over the matter. They would legally (and in all cases in the past) side with me.

      Tell that to Mitnick.

  86. The disputed code is GPL now! by krusadr · · Score: 0, Redundant

    "(SCO) has received U.S. copyright registrations for UNIX System V source code, a jurisdictional pre-requisite to enforcement of its UNIX copyrights."

    But they haven't a) proven that System V code is infact present in the Linux kernel and b) explained their problem with that given that they themselves distributed said code under the GPL.

    Case dismissed, costs awarded against SCO for wasting the court's time.

    --
    while sco {
    wget -O /dev/null http://www.sco.com?sco=litigious%20bastards
    }
  87. General Observations by Ifni · · Score: 1

    I smell a large divestment of stock by SCO upper brass now that the stock is as high as it is likely to get.

    As a backup plan, HURD is coming along nicely...

    --

    Oh, was that my outside voice?

  88. non-sense by dh003i · · Score: 2, Interesting

    They distributed a GNU/Linux distribution. They had the source for that distribution offered until a few weeks after they launched the lawsuit. There is no plausible way that you can say that it was released by one renegade employee without authority.

    1. Re:non-sense by Xerithane · · Score: 1

      They distributed a GNU/Linux distribution. They had the source for that distribution offered until a few weeks after they launched the lawsuit. There is no plausible way that you can say that it was released by one renegade employee without authority.

      Gee, do you think that's why I said that that paragraph was probably irrelevant? I was just raising a possible point SCO may make.

      Does it bode you well to try to repeat what I say, except try to turn it around so it's against me?

      --
      Dacels Jewelers can't be trusted.
    2. Re:non-sense by dh003i · · Score: 1

      I wasn't trying to turn it against you, though it did sound that say because I said, "there is no plausible way you..." when I should have said "there is no plausible way SCO..." I do realize you were just trying to explain a point that SCO may bring up in court (I was explaining why that point SCO will bring up probably won't work).

    3. Re:non-sense by Frodrick · · Score: 1
      They had the source for that distribution offered until a few weeks after they launched the lawsuit.

      They are still offering the source code for download. Check out ftp://ftp.sco.com/pub/updates/OpenLinux/3.1.1/Serv er/current/SRPMS

  89. SCO (Windows) . . . by Dausha · · Score: 1

    Let's face it, Gates seems to have found a chink in open source armor. I opine that he has (encouraged|abetted|paid) SCO along its current course of action. This is the FUD campaign to end all FUD campaigns.

    "Hey, SCO. How about you go after Linux like gang-busters. We'll underwrite your legal fees."

    --
    What those who want activist courts fear is rule by the people.
    1. Re:SCO (Windows) . . . by Sabalon · · Score: 1

      I was just thinking something like that. MS pumps some money into SCO...makes the CEO's richer/happier. Basically - sacrafice SCO and we'll take care of you.

      If SCO wins, then they win pretty well. If they lose, the damage has been done because all the PHB's will now remember that Linux=legal trouble.

      Nevermind the outcome of the case, once the initial info gets in their heads, followup info never makes it in.

      So, everyone ends up running Windows.

      Damn...I've been hanging around here to long -getting consipiracy theoried.

  90. They believe no such thing by dachshund · · Score: 4, Interesting
    They obviously believe that they can defeat the GPL in court.

    I doubt that victory in court is part of their plan. SCO believes that IBM or some other company will step in and buy them out, rather than having to endure the multi-year legal war that threatens to ensue.

    The GPL battle is only one front in that war. Should IBM choose to take this to court, they will almost certainly break out their patent arsenal, which will add years and millions of dollars to the process. SCO and its newfound stockholders are hoping to cut a deal and make some money from this turkey.

    1. Re:They believe no such thing by RickHunter · · Score: 1

      SCO's not even trying to do that. This is a smear campaign and character assassination pure and simple, designed to destroy public confidence in free software. The message is: if you use this software, you will get in legal trouble, because the developers must have stolen code from the only REAL source of innovation (companies like SCO and Microsoft) and these companies will find out about it and sue you.

      This will never come to trial. In five years, the entire thing will have disappeared and all that will be left is the idea in little, impressionable PHB minds that "using free software can get you sued". And Microsoft and Sun didn't even have to get their hands dirty.

    2. Re:They believe no such thing by Physics+Dude · · Score: 1

      Excellent analysis, IMHO. This is a sinking ship making a deal to take someone else out with them.

  91. It's zero dollars. by roystgnr · · Score: 1

    You can get the Linux kernel from them, GPL license included, as a free download from ftp.caldera.com.

  92. Please explain by lildogie · · Score: 5, Interesting

    Why can't someone who got the extortion letter subpoena SCO to identify the infringing code?

    1. Re:Please explain by BdosError · · Score: 1

      Perhaps they could, but that wouldn't necessarily mean it would become publicly available. If they are trade secrets (and they probably are) the court could keep them out of the public record. The company being sued could look at it, but would likely not be able to make that information public.

      --
      Complexity is Easy. Simplicity is Hard.
    2. Re:Please explain by lildogie · · Score: 1

      Doesn't a trade secret stop being a trade secret when the secret gets out?

      If someone got the offending code other than directly from SCO, then it's no longer a trade secret, right?

    3. Re:Please explain by Anonymous Coward · · Score: 0

      Because that would require hiring a lawer, which would require money, which people living in thier parents basements don't have.

    4. Re:Please explain by BdosError · · Score: 1

      Perhaps "trade secret" was the wrong term to use. I merely meant their proprietary code (which the court would assume until proved otherwise, I suspect).

      Whether it's proprietary and their code remains to be seen, but I believe the courts err on the side of not giving out serious, private, competitive information unless necessary.

      --
      Complexity is Easy. Simplicity is Hard.
    5. Re:Please explain by Anonymous Coward · · Score: 0

      I believe the courts err on the side of not giving out serious, private, competitive information unless necessary.

      The thing is - they're claiming it's part of a publically available codebase.

      If we assume that SCO is not lying, then they will have lost nothing, because the code is already available.

    6. Re:Please explain by slam+smith · · Score: 1

      Why can't someone who got the extortion letter subpoena SCO to identify the infringing code?

      Because that would involve volunteering to be the target of a new SCO legal offensive.

  93. they may be shooting themselves in the foot by 73939133 · · Score: 2, Interesting

    You cannot redistribute GPL'ed software if it infringes on anybody's intellectual property. That clause was put there with the intention of preventing SCO-style blackmail. It could be argued that that means that companies that obtain software with the intention of paying a licensing fees already are not covered by the GPL because they believe it infringes on someone's intellectual property.

    The clause may not be strong enough to achieve its intended effect, so perhaps it should be revised for the next version of the GPL to something that explicitly states "if you pay anyone a license fee for using this piece of software, you lose your rights to use or redistribute it under the GPL".

  94. SCO = Miss Congeniality by Glamdrlng · · Score: 5, Interesting

    Understatement of the year: "We're not exactly winning the Miss Congeniality contest"

    What's funny is, McBride actually saved us the trouble and compared SCO to the MPAA and the RIAA for us. The difference is, the RIAA didn't give any MP3's away. McBride's argument is crap. U.S. copyright law may prevent a copyright holder from accidentally giving up their rights, but there's no excuse for violating the GPL when all of the code is right there.

    And if that wasn't a total line of bullshit, how bout when McBride said "We don't wanna sue anybody"? For somebody who doesn't wanna sue anybody, they sure have an awful lot of lawyers going to work for them...

    Line of bullshit #3: "The pull of linux is not the operating system, it's the ability to run unix on cheap intel hardware" Having worked on SCO machines and having worked on linux machines, I had to swallow my teeth when he dropped this one.

    I wonder if McBride would do an Ask Slashdot interview? Lemme get my question in now:

    "So tell me sir, how does it feel to have the absolute worst karma on the planet?"
    --

    Yes, my only tool is a hammer. And you're starting to look like a nail.
    1. Re:SCO = Miss Congeniality by krusadr · · Score: 1

      I'd say that selling millions of shrink wrapped boxes of Caldera Linux for several years under the GPL will most definately be construed as accidently giving up your rights by the court and true justice will prevail and SCO will win.

      I have total faith in the US legal system.

      Signed
      O.J.Simpson.

      --
      while sco {
      wget -O /dev/null http://www.sco.com?sco=litigious%20bastards
      }
    2. Re:SCO = Miss Congeniality by Glamdrlng · · Score: 1

      Sounds to me like Big Blue needs to get Jonny Cochrane up in here. Just someone please take him aside and say "Now look Mr. Cochrane, this time your client actually isn't guilty, mmk?"

      --

      Yes, my only tool is a hammer. And you're starting to look like a nail.
    3. Re:SCO = Miss Congeniality by Anonymous Coward · · Score: 2, Funny

      If they can't match the bits, you must acquit!

    4. Re:SCO = Miss Congeniality by Error27 · · Score: 1

      Just because no one likes the MPAA or the RIAA doesn't mean they are anything like SCO. If the MPAA says you're pirating a movie they tell you what movie it was. As opposed to SCO, which is just making crap up.

      It would be cool if the *AA were like SCO because soon they would be a grease smudge in the history books the same as SCO will be.

  95. Where is the FSF? by SuperBanana · · Score: 2, Interesting
    Isn't about time that we as Linux users file a class action lawsuit against SCO for misuse of Linux source?

    A better question would be, "Why hasn't the FSF done anything about a major challenge to the GNU license?" "Why are they sitting on their hands, doing nothing but releasing 'statements'?"

    From the GNU homepage:

    We rely on support from individuals like you who support FSF's mission to preserve, protect and promote the freedom to use, study, copy, modify, and redistribute computer software, and to defend the rights of Free Software users.

    Second question would be "Why hasn't IBM slapped SCO with a Legal Ugly Stick yet?"

    1. Re:Where is the FSF? by Anonymous Coward · · Score: 0

      Could it be that RMS and the FSF are waiting until everyone "FINALLY" calls it GNU/Linux !!! (I know - we're only talking the kernel here, but hey you never know!)

  96. The GPL is untouchable by dh003i · · Score: 4, Insightful

    It grants rights not given by normal copyright law, upon certain conditions that you must agree to to get those rights. If you don't agree to thsoe conditions, or violate those conditions after agreeing to the GPL, then standard copyright law applies. That means that you've violated standard copyright law.

    Very simply, there is no way that the GPL can be defeated in a court-room. But, if it is, that might be good. If the GPL is invalidated, then ALL EULAs would necessarily be invalidated, as they take away rights granted by standard copyright law.

    1. Re:The GPL is untouchable by Anonymous Coward · · Score: 0
      Very simply, there is no way that the GPL can be defeated in a court-room.

      LMAO! Is this what you tell yourself over and over every night when trying to fall asleep?

    2. Re:The GPL is untouchable by Anonymous Coward · · Score: 0
      "If the GPL is invalidated, then ALL EULAs would necessarily be invalidated"

      I don't know, but I'd say that's one hell of a streeeeeeetch right there. But in this case, GPL doesn't have to be stricken. It only would really have to be seen as innapropriate for Linux use (but not all GPL software), such as when a judge announced the remedy. At least until SCO was able to collect fully on it's 'damages', if not permanently.

    3. Re:The GPL is untouchable by molarmass192 · · Score: 2, Insightful

      It only would really have to be seen as inappropriate for Linux use

      Except that the GPL, unlike the BSD license, does not grant a copyright or even confer ownership privileges. Under the GPL, the author maintains the ownership privileges on their source all while releasing the source to the public. That's why I can release my app code under the GPL but still sell a closed source version with mods outside the GPL. So, unless SCO strips all code submitted by the other copyright owners (and there are many) then they would be in violation of the original agreement under which those authors distributed their work, namely the GPL. SCO would then be left with the 80 copied comment lines and nothing even close to a "Hello World" program.

      --

      Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws-Plato
    4. Re:The GPL is untouchable by Anonymous Coward · · Score: 0

      How many times do people have to clear this up? The GPL is not a EULA. In fact, the GPL specifically disallows a EULA of any kind to be placed on GPL software. The GPL ensures that there is no restriction whatsoever on how the software can be used (remember, a EULA is an End USER Liscense Agreement). The GPL covers only redistribution, and does even that only via copyright restrictions. Which means, I don't have to agree, implicitely or explicitely, to anything, in order for the GPL to apply to me. If I redistribute GPL'd code, I can only be doing it one of two ways. A) In accordance with the GPL, or B) Out of accordance with the GPL. If A, then my redistribution was legal. If B, then it was not legal. EULA's are ridiculous, because no law backs them up. They are companies' attempts to deny me actions that I have every legal right to take. The only thing that even touches that so far is the DMCA, but even that has little to do with most EULA's.

    5. Re:The GPL is untouchable by Anonymous Coward · · Score: 0

      If a judge says that SCO cant distribute a binary only version as it violates the GPL and that any kernal past 2.4 is in violation of SCO's rights, which is what is going to happen. We have a big problem. Linux is dead and now UNIX is worth billions all over again.

    6. Re:The GPL is untouchable by Anonymous Coward · · Score: 0
      It's more likely that everyone will switch to a BSD kernel for their UNIX-like OS.

      Proprietary UNIX is dead whatever happens.

  97. Kernal Contributors. by headkase · · Score: 1

    Imagine if by some fluke that SCO does get to charge for the use of Linux. Would SCO therefore have to split up the profits and distribute them to the other kernal developers?
    It would seem to me that if SCO only has 80 lines of the millions of lines in the kernal source code that they would not be making very much off of charging for Linux after they paid royalties to the people who did the lion's share of the work.

    --
    Shh.
  98. yeah, sure. do you take cash? by MikeyO · · Score: 4, Funny

    SCO: You are going to have to pay a license to use linux because otherwise you will be illegally using software that we wrote.

    Linux User: OK, which lines did you write?

    SCO: I'm not telling.

    Linux User: I'm not paying.

  99. Hey, Linus! by dacarr · · Score: 1
    Linus is the owner of the trademark to Linux. The spirit of Linux is very much open, with heavy regards to the GPL that GNU wrote up for the purpose of open software. To wit, it wasn't necessarily written for Linux, it was AFAICT written for FSF and adopted by the Linux dev team. Maybe RMS or one of his minions can clarify on the history of the GPL here, but I'm sure I'll hear rants about GNU/Linux. But I digress. =)

    Whereas SCO is stating that they own Linux due to several lines of their code being in the kernel (and previously released by SCO/Caldera/whomever, I'm sure), they are now placing a binary-only distro available for users. This is a flagrant violation of the GPL. But wait, they are saying that their code is in there. If (God forbid) they didn't release this, it's time for a rewrite.

    Hey, Linus, it's time for you to get medeival on SCO's sorry collective ass.

    --
    This sig no verb.
  100. Gotta love the USPO by Archfeld · · Score: 0

    giving a company WORLDWIDE rights ?!?! WTF Even as a US citizen that seems a bit off. I hope the rest of the world tells SCO where to go...

    --
    errr....umm...*whooosh* *whoosh* Is this thing on ?
  101. It would not be slashdot without... by computechnica · · Score: 2, Funny

    ALL YOUR UNIX ARE BELONG TO SCO

    In Soviet Russia Unix patents SCO

    (Sorry I was really bored)

  102. GNU is the law? by neilb78 · · Score: 0

    GNU is the law? Huh! That was an interesting statement. I always though GNU was crap.

    --
    © 2004 The SCO Group, Inc. All Rights Reserved.
    1. Re:GNU is the law? by E_elven · · Score: 1

      It's the GNU/Law.

      --
      Marxist evolution is just N generations away!
  103. Not a bad idea. by twitter · · Score: 0

    Seeing as SCO does not actually offer the Linux kernel in any form, their sale of licenses for UnixWare to cover Linux is a gross dilution of the term. If you don't have Linux, you can't call it Linux, that's what trademard is all about. SCO is going to have to come up with a name like SNL, SCO's Not Linux.

    --

    Friends don't help friends install M$ junk.

    1. Re:Not a bad idea. by schon · · Score: 1

      SCO does not actually offer the Linux kernel in any form

      Really? If you look here I think you'll find that they offer it in MANY forms (3 different patch levels, including source and binaries.) If you're lazy, try downloading this file and taking a look inside it.

    2. Re:Not a bad idea. by Esion+Modnar · · Score: 1
      SCO is going to have to come up with a name like SNL

      Saturday Night Live? NBC might object...

      --

      They say the first thing to go is your penis. Well, it's either that or your brain. I forget which...
  104. That's it, then... by Svartalf · · Score: 1

    They're beligerent and obviously unwilling to work with the community over this (Did anyone ever believe them when they said that they weren't going to go after the Linux community when they started this BS? I sure as hell didn't...).

    I wonder when the kernel coders will start working at filing infringement suits on SCO over their 1-2% in the kernel and the licensing they just announced.

    --
    I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
  105. Nevermind, an explanation why they haven't acted by SuperBanana · · Score: 4, Informative
    http://www.fsf.org/licenses/gpl-violation.html

    Pertinent passage:

    If the copyright holder is the Free Software Foundation, please send the report to . Note that the GPL, and other copyleft licenses, are copyright licenses. This means that only the copyright holders are empowered to act against violations. The FSF acts on all GPL violations reported on FSF copyrighted code, and we offer assistance to any other copyright holder who wishes to do the same. But, we cannot act on our own if we do not hold copyright. Thus, be sure to find out who the copyright holders of the software are before reporting a violation.

  106. IBM's response by Johann · · Score: 5, Informative
    "Armonk, New York-based IBM, the world's largest computer company, said that it is not aware of any Unix V code embedded in Linux.

    "SCO needs to openly show this code before anyone can assess their claim," IBM spokeswoman Trink Guarino said. The company has said in the past that the suit is baseless.

    Regarding SCO's decision to offer a license to users of Linux -- the open-source software that can be copied and modified freely -- Guarino said, "SCO seems to be asking customers to pay for a license based on allegations and not facts."

    http://biz.yahoo.com/rc/030721/tech_sco_4.html

    --
    "You're gonna need a bigger boat." - Chief Brody
  107. Re:Unbelieveable! - Believable! - 0-0 by Jack9 · · Score: 1

    >They have not provided any proof that Linux contains SCO IP... even if it did that does NOT mean that Linux users are committing software piracy.

    No proof? They don't need to submit proof. Linux is clearly a unix clone and has been considered so for a long time by the (programmer) masses. It's hard to backpedal on that now. The idea that Unix is too similar to other older operating systems is not where this case is going to go. As an OS watcher, I copy and paste lots and lots of code written by all manner of people just to get work done in little scripts I write. I serioiusly doubt I am unique in that regard. By the same note, I doubt that the early developers of low level OS apps were so different from me; after all, it's just our job.

    --

    Often wrong but never in doubt.
    I am Jack9.
    Everyone knows me.
  108. Mine is comercial. by twitter · · Score: 0, Flamebait

    I'll sell McBitch a shell account anytime he feels the need for a real OS. Just reply in this thread and I'll tell you where to send the money.

    --

    Friends don't help friends install M$ junk.

  109. Its better than... by GoofyBoy · · Score: 0, Offtopic

    Another arrogant slashdotter who thinks that social rules don't apply to him as long as he's got access to the source code and a speedy Internet connection.

    --
    The surprise isn't how often we make bad choices; the surprise is how seldom they defeat us.
  110. Linux was made from Scratch...Good one! by neilb78 · · Score: 0

    Linux was made from Scratch...Good one! LOL You're an idiot.

    --
    © 2004 The SCO Group, Inc. All Rights Reserved.
  111. The scariest(?) part of the whole story.... by pfleming · · Score: 1

    "SCO will hold harmless commercial Linux customers that purchase a UnixWare license against any past copyright violations, and for any future use of Linux in a run-only, binary format."

    Of course that means that they would be in violation of the GPL by not offering source code. I mean does code ole Darl really think they can violate someone elses license because they claim theirs was violated?

  112. declarative judgement by 73939133 · · Score: 4, Informative

    The situation where one company holds another hostage by claiming infringement without every putting up any evidence is not new. To address it, we have declarative judgements. The Linux community could and should ask for a declarative judgement on SCO's alleged copyright violations. Then, SCO either has to put up the evidence, or the judge will rule against them.

  113. No, they can't "license" Linux by TheConfusedOne · · Score: 1

    SCO cannot sell a license that would make your Linux install "legal".

    You see, if you need a license to run the SCO code then you lose the license to run the rest of the Linux code. Go read your GPL.

    --
    --- I wish I could hear the soundtrack to my life. That way I'd know when to duck.
  114. Why is this news? by gasp · · Score: 5, Informative

    Registering a copyright for sourcecode amounts to sending in a form with the code and a fee to the copyright office. They datestamp it and file it away. It's not required to register to claim copyright, or even to register at all. Registering just gives the holder some leverage in court, since in the absence of other information, the side with the earlier registration date wins.

    So, since they are just filing now, and have a 2003 registration date, I don't see what this has to do with anything at all. All this means is that they are "officially" claiming copyright, id doesn't mean they's been "granted" any rights at all. That's for a court to decide in specific disputes.

    IANAL, but I've sent in a number of Copyright Form TX filings in my day, at about $10 each. Big deal.

    1. Re:Why is this news? by Anonymous Coward · · Score: 3, Informative
      It's not required to register to claim copyright, or even to register at all. Registering just gives the holder some leverage in court, since in the absence of other information, the side with the earlier registration date wins.

      I was looking for someone here to pick up on the effect of copyright registration. The following is blatantly lifted from the U.S. Copyright Office synopsis on the subject (since no one bothers to RTFL anyway, right?):

      Registration establishes a public record of the copyright claim.

      Before an infringement suit may be filed in court, registration is necessary for works of U. S. origin.

      If made before or within 5 years of publication, registration will establish prima facie evidence in court of the validity of the copyright and of the facts stated in the certificate.

      If registration is made within 3 months after publication of the work or prior to an infringement of the work, statutory damages and attorney's fees will be available to the copyright owner in court actions. Otherwise, only an award of actual damages and profits is available to the copyright owner.

      Registration allows the owner of the copyright to record the registration with the U. S. Customs Service for protection against the importation of infringing copies.

      I'll make no further comment as we all can read.

    2. Re:Why is this news? by thisgooroo · · Score: 1

      it was registered already, first to AT&T, then to USL/Novell. when Novell sold to SCO, there seems to have been some foulup that caused the registration to be transferred. no it has been officially transferred to the new SCO

  115. Mitigating damage by NormalVisual · · Score: 5, Interesting

    I have a question, and being that I'm not a lawyer, perhaps someone more knowledgable can chime in - I seem to remember reading that in any kind of civil action like this, the plaintiff has a duty to actively mitigate his damages to the maximum extent possible - for instance, if some schmuck pulls out in front of me on the highway, I have a duty to attempt to prevent an accident, even if it's his fault. Regarding the SCO/Linux situation, SCO has steadfastly refused to tell Linus or anyone else specifically where the code is that's infringing while being fully aware of the fact that armed with that knowledge, the OSS community would very quickly make the needed changes to remove the disputed IP.

    By acting in this manner, SCO appears to not be interested in mitigating their claimed damages in the least, and actually appears to be attempting to increase them as much as possbile - how do you suppose a judge/jury is going to look upon this?

    --
    Please stand clear of the doors, por favor mantenganse alejado de las puertas
    1. Re:Mitigating damage by krusadr · · Score: 0

      Thats a very good point. I hope that the court reads your post!

      Sry no mod points!

      --
      while sco {
      wget -O /dev/null http://www.sco.com?sco=litigious%20bastards
      }
    2. Re:Mitigating damage by Anonymous Coward · · Score: 1, Insightful

      As soon as they start to charge, and without giving evidence on that they really have code in the kernel, they seem to be on the border of thievery and fraud, the state and fed attourneys then really might be interested into the whole thing.

      I'm not a laywer, but usually you have to give proof that you own a thing before being able to charge for it.

    3. Re:Mitigating damage by schon · · Score: 3, Informative

      I seem to remember reading that in any kind of civil action like this, the plaintiff has a duty to actively mitigate his damages to the maximum extent possible

      In legalese, this is known as the "doctrine of laches" - and you're 100% correct (I've brought this point up a couple of times in the past.)

      Basically, this is proof that SCO's charges are 100% groundless.. as they refuse to tell anyone what the alleged code is, they are delaring that the value of the code is $0. So the absolute best case scenario for them (assuming they win 100% on all counts) is that Linus is told what lines need to be removed, and is given a year to remove/rewrite them.

      There is no motivation for them to keep the alleged code "secret", because it means even if they win, then they lose.

    4. Re:Mitigating damage by AtariDatacenter · · Score: 1

      Thank you for bringing that up. Isn't that part of the UCC?

    5. Re:Mitigating damage by Anonymous Coward · · Score: 0
      --I seem to remember reading that in any kind of civil action like this, the plaintiff has a duty to actively mitigate his damages to the maximum extent possible.--

      In legalese, this is known as the "doctrine of laches" - and you're 100% correct (I've brought this point up a couple of times in the past.)

      The "doctrine of laches" and "mitigation of damages" are unrelated legal concepts.

      "Laches" is an equitable defense against the rights holder for not having brought suit in a timely fashion, regardless of the cause. It provides for limitation of damages to the point when suit should have been brought. It is often referred to as "undue delay", and may be applied for lack of diligence in protecting your legal rights.

      "Mitigation" provides that, in the event of a contract breach, you must do what is within your powers to limit the damages. Here, the damages are limited to the time that you had damages within your control and you did nothing to limit them. Contract law presupposes that the parties to a contract are aware of the activities of one another. Mitigation presumes this awareness, and frowns upon the practice of continuing to run up the damages when breach is known.

      Perhaps that seems a subtle difference, but legally it's not.

  116. The GNU/GPL is probably unenforceable in this case by jbottero · · Score: 1

    Wrong answer. *They* themselves distributed a Linux kernel, complete with source up until a week or so after they filed the suit, IIRC. If it was infringeing then, then they have relased whatever code might be in there under the terms of the GNU General Public License.

    I don't think this will hold up. On this point I suspect a judge will side with SCO if they claim that the copyright is invalid because they where not fully aware at the time of the scope of the offending code content.

    We hear this GNU/GPL argument all the time here, but it's not as simple as that. There are lots of scenarios that would invalidate this idea.

    By the way, take note that not one of the big players in this fiasco even brings this up, they know that in this case the GNU/GPL is questionable and probably not enforceable.

  117. About $800,000 in the last couple of months . . . by Idou · · Score: 5, Insightful

    is how much SCO upper management has made off selling an artificially inflated stock (see for yourself). That is assuming that major insider trading activities are not being concealed some how, which, considering the ethical principles of the people involved, is a dubious assumption. Most of this stock selling is in lots under 6k of shares, which shows a concious effort to avoid scrutiny from the SEC.

    Enron might have lied about large numbers, however, I am convinced that SCO represents the most a company has ever multiplied the perception of its own worth through blatant lies. This has either exposed something horrible about our financial system or the complete incompetence in this area on the part of investors (probably both . . .).

    --
    Sdelat' Ameriku velikoy Snova!
  118. McBride is more arrogant than that by A+nonymous+Coward · · Score: 2, Interesting

    He literally claims that developing any code for a UNIX clone violates UNIX IP rights, thus if you or I or anyone writes code for Linux, it belongs to SCO.

    In a theroretical sense, it makes sense -- if I own land, and you build a house on it, thanks, you just built me a house (actually happened to the land I won, with the people I bought it from). Look at all the Harry Potter parodies which have been shut down.

    SCO will certainly lose long term, the question is how much of a circus it will be getting there.

    1. Re:McBride is more arrogant than that by canajin56 · · Score: 1

      It's more like, if I own land, and you own a similar piece of land, and you build a house on your land, thanks, you just built me a house.

      --
      ASCII stupid question, get a stupid ANSI
    2. Re:McBride is more arrogant than that by rnturn · · Score: 1
      ``Look at all the Harry Potter parodies which have been shut down.''

      You sure those weren't as a result of some trademark complaint? I have a hard time believing that a parody -- which, AFAIK, is allowable under copyright law -- could be found to be illegal.

      --
      CUR ALLOC 20195.....5804M
    3. Re:McBride is more arrogant than that by Dastardly · · Score: 1

      He literally claims that developing any code for a UNIX clone violates UNIX IP rights, thus if you or I or anyone writes code for Linux, it belongs to SCO.

      Not exactly. This claim is based on a clause in the original Unix License that says all modifications to Unix are covered by the license for the whole. (Not the exact wording.) He claims that any code written for a licensed Unix belongs to SCO. This is according to the license agreement signed by various Unix licensees. He cannot claim ownership of any code not written by a Unix licensee. The tricky part is how many Linux developers worked for a Unix licensee and are therefore tainted by that contract. My guess is quite a few, but at least a few Linux developers at no time came under the jurisdiction of the original Unix License, and therefore their code cannot be owned by SCO. Specifically, I don't believe Linus has ever been employed by a Unix licensee, and therefore SCO has no claim to his code.

      His claim of ownership based on the Unix license terms may be somewhat spurious as well aside from the obvious. If I recall right, the terminology of that clause could also be interpreted as simply meaning that the Unix licensor gets rights to the modifications, but does not revoke rights held by the modifier. I.e. SCO can include code from Unix licensees in its Unix, but that does not give them any restrictions on what the original developer can do with that code. Sort of reminds me of the GPL...

      Dastardly

    4. Re:McBride is more arrogant than that by juhaz · · Score: 1

      This is more along the lines:

      I (SCO) own the land (SysV) and someone (IBM) builds a house (AIX) on it, thanks pals, I now own that house.

      Now IBM takes a small piece of house they build, let's say, a chair and small table (RCU, SMP...), and gives it to neighbours house on neighbours land neither of us own (Linux). After this I (SCO) am claiming to own that neighbours land and house as well, and not only the chair and table.

  119. How is SCO's Lawsuit affecting sales of Linux? by drgroove · · Score: 0, Funny

    If I were a CIO or CTO debating the TCO of *nix vs. Win2K3 to a CEO, would IBM vs. SCO be the TKO that stops the CEO from approving A/P to pay my PO for RH's LGX?

    FWIW, even if OSS is FAIB, if the DOJ considers *nix IP with a TM, then it basically become's SCO's LIC, meaning our OSS becomes a CSS OS, which would RSTBO.

    AIBO going w/ an ASP that manages our OS? BTA, we might end up w/ a BOFH giving us ZA, which WWAD PMS.

    AFAIK, INMP if SCO wants to be ITM by enforcing its supposed IPR - *nix IP should be PD or GNU, like BSD just on GP, IYKWIM. I keep asking myself in this situation - WWLD?

    Oh, BTW - IITYWIMWYBMAD?

    1. Re:How is SCO's Lawsuit affecting sales of Linux? by 36526542DD · · Score: 0

      Holy Acronyms Batman!

  120. Red Hat Severn = 0 secx w4r3z by Anonymous Coward · · Score: 1, Interesting

    I actually do believe that 2.4's NUMA architecture, SMP, et al, came in bulk from outside the linux kernel hackers cadre.

    I dont believe that they fumbled for a decade with scalability, only to hit the nail on the head, miraculously, in time for IBM to hitch it's cart to the horse.

    SCO may be right, and then what? Rollback to 2.2 kernel, or earlier. IBM helped shove that code in there, hoping that if the genie was out of the bottle, no court could put it back in for SCO.

    I actually believe 95% of all open source projects are due to stolen code or other IP.

  121. Shorting Stocks? by Sir+Rhosys · · Score: 1
    Shares are up 20%

    Are there any good resources about learning how to 'short' stocks? Is it basically just betting that a stock will go down in a specified timeframe? Will shorting a stock also put immediate downward pressure on it?

    Sorry for the TOTALLY unrelated post. These questions have nothing to do with SCO at all... I was just curious about stocks and stuff. Thanks for the help in advance,

    --

    Use Python

    1. Re:Shorting Stocks? by Anonymous Coward · · Score: 0

      When you "short" a stock, it simply means that you sell it -- when you don't own it. (Nice trick, eh?) You get the cash for selling the shares. You're also stuck with paying the dividends to the buyer when the company annouces them.

      Eventually, you will "cover" your short by buying the shares that you already sold. In that sense, yes, you're betting that the stock price will go down; otherwise, you lose money. A short has no particular timeframe, however. It's not like an option.

      Shorting a stock puts the same downward pressure on the price that any sale of shares would.

      If there are a large amount of shorted shares, they can actually drive the price up temporarily. A rise in the stock price can cause some shorters to decide to cover, and cut their losses now. That additional demand makes the share price go up, which can make more shorters decide that they need to cover, and thus you can get a brief spiral of rising prices driven just by the covering of earlier short sales.

    2. Re:Shorting Stocks? by paule9984673 · · Score: 1

      The so called 'short squeeze'

  122. What about Caldera Linux Users? by oni · · Score: 1

    I have a web server running a copy of Linux that I downloaded from SCO. SCO allowed me to download it -the whole thing - under the GPL. By demanding payment now, they are violating that licence.

  123. God requests license fees from Coca-Cola by levin · · Score: 1

    In a surprise move earlier today, God announced a multibillion dollar lawsuit against Coca-Cola Co. Apparently the soft drink company has been sneaking water into their flagship products for several years. God said He would be requiring licensing fees from all Coca-Cola drinkers, but anyone who has previously been baptized will not be expected to pay usage fees for water.

    --

    `which fortune`
    1. Re:God requests license fees from Coca-Cola by arkane1234 · · Score: 1

      And in other news, Coca-Cola Co. spokespeople stated that they don't believe in his existance and demanded proof.

      The plantiff was unavailable for comment.

      --
      -- This space for lease, low setup fee, inquire within!
  124. even more explicite by Vitriolix · · Score: 1

    ftp://ftp.sco.com/pub/updates/OpenLinux/3.1.1/Serv er/current/RPMS/linux-kernel-binary-2.4.13-21S.i38 6.rpm yepp... thats SCO distributing the linux kernel, *right now*

    1. Re:even more explicite by Anonymous Coward · · Score: 1, Interesting

      The kernel being offered there is based on 2.4.13, and has apparently had 21 vendor-specific patches to it. That's funny. The idea that SCO is modifying the kernel at all surprises me. You would think that they would just compile a stock kernel.

      However, it is worth noting that 2.4.13 is old. Really old. That was before Marcelo started maintaining 2.4 almost two years ago, and before the 2.5 branch started. 2.4 has made tremendous advances since then, and shipping a distro based on 2.4.13 is not a great idea. Goes to show you that SCO is really behind.

  125. Clarification... by p.rican · · Score: 4, Informative

    I just finished watching the interview and McBride is claiming that the GPL only enforces their claims.....McBride says that the GPL is very clear in stating that there is a difference between donating code and distributing code into Linux kernel. SCO claims that they never 'officially signed away their code' to be used in the linux kernel. He even goes on to say that since there is any proprietary code in the kernel, that the GPL itself is nullified as a valid license for the kernel. Good interview, but McBride still comes off as evasive in some of his responses. (I guess that shouldn't surprise me) This is going to be a major test for the GPL. I'm getting frustrated that we haven't heard more from IBM.

    --

    /. --"Demented and sad....but social" -Judd Nelson

    1. Re:Clarification... by PetiePooo · · Score: 2, Insightful

      He even goes on to say that since there is any proprietary code in the kernel, that the GPL itself is nullified as a valid license for the kernel.

      Lets use Darl's words against him. Lets say there is proprietary code within the kernel. Lets say that, as a result, the GPL is not a valid license for the kernel. This simply means that SCO cannot distribute the kernel under the GPL, and must distribute it under some other license agreement. However, since:
      1) There is bound to be much more code within the kernel that is not SCO-proprietary, and..
      2) That code is copyrighted by the originating authors, and..
      3) They will not be allowing SCO to license their code under anything other than the GPL (which it was previously released under), then..
      4) SCO cannot distribute the current Linux kernel without violating copyright law.

      The solution, of course, is to identify the proprietary code and replace it. The obstacle, of course, is to identify the alleged proprietary code when SCO will only do so under a NDA. There's no point in rehashing those topics, as they're covered in depth in every /. thread with SCO in the title..

      I think its time for the FSF to take a stand and notify SCO through legal channels that they are violating copyright by relicensing the OS community's code under a different license. Donate to the FSF now!

    2. Re:Clarification... by SpaceLifeForm · · Score: 1
      And obviously, he is full of crap. You don't 'distribute' code *into* the Linux kernel.

      As to his dream about the GPL being nullified as a valid license, it it now 100% clear that only Microsoft can be behind all of this FUD.

      The *only* way for GPL to be invalid is for *copyright* to be invalid.

      --
      You are being MICROattacked, from various angles, in a SOFT manner.
    3. Re:Clarification... by jedidiah · · Score: 1

      However, the GPL still constitutes a copyright notice. The license may be invalid. However, the ownership of the product in question remains highly disputable.

      This should be shouted far and wide, especially in stock discussion newsgroups.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    4. Re:Clarification... by Anonymous Coward · · Score: 0

      How could the FSF take legal action? They don;t own the linux source code. Only the IP holders can sue for infringment.

    5. Re:Clarification... by eggnet · · Score: 1

      The FSF can file a lawsuit on behalf of the IP holders.

    6. Re:Clarification... by moncyb · · Score: 1

      I think its time for the FSF to take a stand

      Why whould they do anything about this? They hate Linux--especially Stallman. He's pissed because Linux stole the thunder from his Hurd kernel. The FSF were probably cheering when they heard the news about SCO.

    7. Re:Clarification... by jrumney · · Score: 1
      He even goes on to say that since there is any proprietary code in the kernel, that the GPL itself is nullified as a valid license for the kernel.

      He may be right there, but it does not give SCO the right to relicense the work of Linus Torvalds, Alan Cox, IBM, HP, SGI and others under their own terms.

      If SCO's claims are right (and they have yet to offer ANY evidence in their favour), then the only legal solution is for everyone to stop distributing the Linux kernel until the offending code is replaced.

    8. Re:Clarification... by moncyb · · Score: 1

      This is a bogus arguement the FSF uses to coerce people into signing away copyright to them. They could just as easily hire lawyers to fight for other Free/Open Source software owners as they could for themselves.

    9. Re:Clarification... by babyrat · · Score: 1

      From the press release it doesn't sound as if they are distributing the linux kernel, but rather they are selling a 'we will not sue you card'

      And it's actually a license for Unixware not linux.

      IANAL, but it sounds like a legal loophole to me.

    10. Re:Clarification... by b29651 · · Score: 1

      So the Linux distros are stopped,now what?How does linux move forward if they wont tell what offending code is in the kernel?

    11. Re:Clarification... by jrumney · · Score: 1

      So far only SCO claims to have evidence that there is non-GPLed code in the kernel. Until they make their claims publically available, other distributors have no reason to stop distributing. At that point, Linux can move forward, and Red Hat, Debian and the rest might have to go a few weeks with no kernels available for download. The fact that Red Hat has decided to stop distributing CDROMs makes me wonder whether they are already preparing for this scenario. It will be a lot easier and less costly to pull a few files from their FTP sites for a few weeks than to recall thousands of CDROMs from store shelves.

  126. And still, here we sit. by TrebleJunkie · · Score: 1

    Someone with some money and a lawyer to burn, PLEASE sue SCO to force the disclosure of the "evidence" they claim to have.

    We can continue sit here and fester in our own self-confidence, but until we know for sure what's up, we're sitting ducks. Better to know NOW what the extent of the problem is, and fix the damn thing.

    --

    Ed R.Zahurak

    You know, oblivion keeps looking better every day.

  127. Hello? IBM? Please refute this in the media? by Scarblac · · Score: 1

    This is hurting IBM's image as a Linux vendor. We all believe they are going to win the law suit utterly. Why aren't they issuing any statements with some short reasons why these claims are ridiculous?

    --
    I believe posters are recognized by their sig. So I made one.
    1. Re:Hello? IBM? Please refute this in the media? by oni · · Score: 1

      See this comment:
      http://slashdot.org/comments.pl?sid=7188 6&cid=6491 716

      Which links to this story:
      http://biz.yahoo.com/rc/030721/tech_sco_4. html

      in which IBM says the claims are baseless.

    2. Re:Hello? IBM? Please refute this in the media? by dmaxwell · · Score: 1

      Why aren't they issuing any statements with some short reasons why these claims are ridiculous?

      IBM is going to fight this in a court of law. SCO is fighting this in the court of public opinion. The rules are different. Anyone who truly intends to fight in a court of law doesn't run his mouth unnecessarily. IBM's lawyers are going to have a field day with SCO's public statements.

    3. Re:Hello? IBM? Please refute this in the media? by Scarblac · · Score: 1

      IBM is going to fight this in a court of law. SCO is fighting this in the court of public opinion. The rules are different. Anyone who truly intends to fight in a court of law doesn't run his mouth unnecessarily. IBM's lawyers are going to have a field day with SCO's public statements.

      Of course. But that's in three years or so. In the meantime this cloud of FUD is doing damage.

      But apparently IBM is already issuing statements, as someone else replied, I missed that.

      --
      I believe posters are recognized by their sig. So I made one.
    4. Re:Hello? IBM? Please refute this in the media? by dmszero · · Score: 1
      the issue here is who has to prove what. if SCO takes IBM to court, its SCO's duty to prove IBM infringed, if IBM takes SCO to court, its IBM's duty to prove they didnt.

      IBM is waiting for SCO to move legally, SCO is trying desperatly to stall for as long as possible

      dms0

      --
      -= world leaders choose world leaders not us, not a democracy, not a revolution! =-
  128. Call in the big dogs by Gzip+Christ · · Score: 0

    I think it's time that we get Pat Robertson to "pray" for Darl McBride and Chris Sontag.

  129. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  130. Exactly by 2names · · Score: 1
    What's next, Wendy's suing MacDonalds for infringement of the "all white meat" chicken nugget?

    All this copyright/patent/whining/pissing/moaning bullshit has got to stop.

    --
    "I'm just here to regulate funkiness."
    1. Re:Exactly by Mr.+No+Skills · · Score: 4, Funny

      McDonald's is safe -- they don't put "meat" in their nuggets.

      --
      Sleep is for the Weak
    2. Re:Exactly by Anonymous Coward · · Score: 0

      Come on guys, how much help will getting this paperwork be? If any of you have been involved with Copyrighting programming code, you should know that you black out half of each line...

      Slashdot = 13 year olds. Why must you all talk about topics that you really don't know what your talking about?

    3. Re:Exactly by SegFault · · Score: 1

      Member of the future Elite Slashdot 6 Digit ID Society

      Got you beat.
      Segmentation Fault

  131. Hello, RIAA... by iabervon · · Score: 1

    "SCO will hold harmless commercial Linux customers that purchase a UnixWare license against any past copyright violations"

    "Hello, RIAA. Please direct further correspondance to this other address."

  132. please use the correct terms by nomadic · · Score: 2, Funny

    They're "chicken" nuggets, not chicken nuggets.

    1. Re:please use the correct terms by Tony+Hoyle · · Score: 1, Informative

      bzzt try again. They're chicken *mc*nuggets.

    2. Re:please use the correct terms by MrM · · Score: 2, Informative

      Bzzt. Chickens don't have nuggets.

      And Scottish chickens don't have McNuggets...

      MrM

      --
      Karma? We don' need no steenkeeng karma!
    3. Re:please use the correct terms by !3ren · · Score: 2, Funny

      unless of course they're made of roosters not chickens

    4. Re:please use the correct terms by falconed · · Score: 2, Funny
      unless of course they're made of roosters not chickens

      in other news, McDonald's stock falls 20%.

      --
      USE='clever' emerge -u sig
    5. Re:please use the correct terms by hackwrench · · Score: 1

      Roosters are chickens. Female chickens are hens.

  133. develop it outside the USA then by Anonymous Coward · · Score: 1, Funny

    hint: Alan Cox doesn't work in the United States, never mind Utah.

    And he will also never visit the USA again, for fears of being arrested under the DMCA.

    1. Re:develop it outside the USA then by Trigun · · Score: 1

      Looks like I'm going to have to go to Wales to shake his hand then.

      Hey Alan, you mind people dropping in on you?

    2. Re:develop it outside the USA then by Anonymous Coward · · Score: 0
      Alan Cox doesn't work in the United States, never mind Utah. And he will also never visit the USA again, for fears of being arrested under the DMCA.

      Linux, the growing international crime syndicate...

    3. Re:develop it outside the USA then by caluml · · Score: 1

      He's a regular at the south Wales LUG most times. It's great having a super-hero just over the Severn bridge... :)

    4. Re:develop it outside the USA then by Trigun · · Score: 1

      Thanks for the info. The next time I'm in Cardiff I'll have to stop on by.

  134. is there a certainty we'll even ever see the code? by Uthiroid · · Score: 1

    Has anyone comtemplated that SCO will have granted by the court in the SCO/IBM case a provision to seal this portion of the case on the basis of trade secrets? In that case it seems that the development community may never see the actual code, and only learn the result of the lawsuit, making it extremely difficult to "clean up" the current codebase of infringing material!

    also, if IBM ever decides to settle the case, SCO may demand to keep the code secret under an NDA. (and don't think IBM can't decide to settle, weirder things have happened before with corporations- it may be cheaper and easier to settle!)

  135. ./ SCOs 800 number? by smartguy · · Score: 0

    Let's organize ourselves and all call on the same day to ask about their "license" pricing. They have a 800 number ((800) 726-8649) so the dime is on them. How much long distance charges can ./ rack up?

  136. Trademark by gr8_phk · · Score: 4, Insightful
    and SCO is releasing binary, run-only Linux licensing.

    Isn't there one thing for certain: Linus owns the trademark on Linux. Even if they did own the code (which they don't), they can't market it as Linux after Linus says to stop. He'll be needing a lawyer soon. His inaction to date was waranted - he said it was between IBM and SCO. Now it should be nice and personal.

    1. Re:Trademark by Frobnicator · · Score: 1
      Linus owns the trademark on Linux. Even if they did own the code (which they don't), they can't market it as Linux after Linus says to stop. He'll be needing a lawyer soon.
      As to the first point, that has been discussed in length. As to the second, Linus has lawyers, and has had paid for legal services for several years. Read the back posts in the development lists.
      --
      //TODO: Think of witty sig statement
  137. Re:The GNU/GPL is probably unenforceable in this c by Surak · · Score: 2, Interesting

    From the GPL:

    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.

    meaning that even if they win they cannot distribute the binary-only version of Linux they are distributing, as announced in the article. Hence, as I mentioned before, they are currently violating the GPL. Whether or not they did it before is another issue altogether.

  138. SCO and IBM Investors by Anonymous Coward · · Score: 0

    I find it intresting that SCO and IBM have a very simular list of primary instutional investors.

    Barclays Bank Plc
    Vanguard Group, Inc.
    FMR Corporation (Fidelity Management & Research Corp)
    Northern Trust Corporation

    I know jack about investments and this is purly speculation but I do know that something smells rotten in Denmark. IBM's done nothing, and someone is eventually going to bite on the SCO FUD giving them a position to stand on.

    1. Re:SCO and IBM Investors by Anonymous Coward · · Score: 0

      To the neofeudal business world of today, it doesn't matter who wins, so long as a corporation rather than an uncontrollable load of "dirty internet anarchists and hippies" is declared the Owner of Linux. Programmers should be safely enslaved to multinational corporations, in their eyes.

      So, whether SCO or IBM win, we lose out, really.

      I'm coming to think the only recourse is revolution.

  139. Re:Time for *BSD? by Anonymous Coward · · Score: 0

    That's all very nice, but what if I need help and send email to a list that Brett Glass is on ? Worse, what if one of my clients (I install linux samba servers for small offices to use as network backup) sends such an email, and Brett Glass AND Theo respond ?

    I can be fairly certain that Torvalds and Cox will just not respond to annoying email, and not drive my customers away.

    Face, BSD people are bad for business. I'd rather pay the $90 for my customers to call MS support than have them interact with those people for free.

  140. Reply to your signature by cmburns69 · · Score: 0, Offtopic

    OT!

    While not hilarious, my signature has a link.. and a couple of funny things.. All under 120 characters!

    But I would appreciate more space for a sig. I want to include a poem, and a disourse on debate.

    --
    Online Starcraft RPG? At
    Dietary fiber is like asynchronous IO-- Non-blocking!
  141. SCO doesn't own UNIX by vinsci · · Score: 2, Informative
    Quoted from The Open Group press release Who owns UNIX?:
    Regarding SCO's positioning on UNIX, The Open Group would like to make it clear that SCO holds the rights only to the operating system source code originally licensed by AT&T and does not own the UNIX trademark itself or definition of what a UNIX system is. [...]

    In fact, SCO has never owned UNIX or the definition of what a UNIX system is. From the OSI Position Paper on the SCO-vs.-IBM Complaint:

    Neither SCO/Caldera nor old SCO has ever owned the UNIX trademark. IBM neither requested nor required SCO's permission to call their AIX offering a Unix. That decision lies not with the adventitious owner of the historical Bell Labs source code, but with The Open Group.

    From http://opengroup.org/:

    Who owns UNIX® ?

    You may have seen recent press articles announcing that SCO is the owner of UNIX or has licensed UNIX to Microsoft. Such statements are inaccurate, misleading and cause considerable confusion. The Open Group has owned the registered trademark UNIX since 1994. Here is what we said in response to a Linux Weekly News article last week. Also available is a backgrounder that explains the history and reasons why The Open Group takes action on trademark misuse.

    The Open Group owns UNIX. SCO just owns the copyright on some old source code that *implements* UNIX and nobody could care less. Furthermore

    --

    Trusted Computing FAQ | Free Dawit Isaak!
    1. Re:SCO doesn't own UNIX by Mostly+a+lurker · · Score: 1

      Actually, one of the questions I have had for a while is related to SCO's consistent public statements that they own 'UNIX' and all derivatives. Have they been formally told that they do not have the right to imply ownership of the 'UNIX' name? If they have not, why not? If they have been told, and are ignoring it, what are the implications?

  142. Terminator Example by Jonathan · · Score: 1

    This is like saying "Well, the makers of the Terminator movie have a copyright on that movie, so they can sue anyone that makes any story that even resembles a plot where robots take over the world."

    That isnt how copyright works, even in copyrights current fucked up state.


    Actually, it is somewhat ironic that you use the Terminator example, because the SF author Harlan Ellison sued James Cameron over copyright infringement -- the "crime"? That Cameron made a movie that involved robot killers going back in time. Apparently Ellison thought he owned that hackneyed concept. Cameron even settled with him.

    1. Re:Terminator Example by Anonymous Coward · · Score: 0

      copyrights, IIRC, protect ONLY the EXPRESSION of an idea, NOT the idea itself.

      So Cameron should have been perfectly able to write a story about robots who travel back in time, etc etc as long as he did not copy any of Ellison's work verbatim.

      Same would go for source code I expect. A patent is the ONLY thing that protects the idea itself, effectively granting a monopoly for a short period of time.

      Bottom line, unles the code is copied in fairly large segments and is completely identical SCO hasn't got much of a case, but, then again, I'm not an attorney.

    2. Re:Terminator Example by jedidiah · · Score: 1

      Watch that episode of the Outer Limits and you will lose whatever respect that you may have had for Harlan. It's the perfect example of how you could re-invent something much better even without any awareness of the original.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    3. Re:Terminator Example by rnturn · · Score: 1
      ``Apparently Ellison thought he owned that hackneyed concept.''

      Ellison is known to be quite the piece of work. I enjoy hiw writing (at least some oolder works) but I have a friend who is/was a fanatic about him. Until he listened to him give a talk at a local junior college, that is. As I recall, his comments were something along the lines of `what a schmuck!'. I'm guessing Camerson paid Ellison off just so he wouldn't have to listen to him any more.

      --
      CUR ALLOC 20195.....5804M
  143. Just more smoke by benking · · Score: 1

    SCO will hold harmless commercial Linux customers that purchase a UnixWare license against any past copyright violations, and for any future use of Linux in a run-only, binary format.

    Isn't this against the GPL? If they distribute Linux they MUST provide the source. This seems like a serious conflict. I also find it odd that if they where interested in protecting their IP that they have not issued any cease and desist orders to any of the other major Linux distos like Redhat. One more question. What will happen to somebody if he is running SCO Linux? Are they going to sue someone for running software that SCO itself distributed?

    1. Re:Just more smoke by lavorgeous · · Score: 1

      I'm curious if the GPL argument holds in this case (though I hope it does).

      Here's what I'm thinking: SCO could easily say that they were previously distributing Linux according to the GPL, having included the source (per the GPL) to the improvements they knowingly contributed.

      But now, the story is different because they found out (GASP!) that the kernel includes code that belongs to them but that was improperly contributed by somebody else without SCO's permission. Once they learned that this improper code was there, they ceased distributing Linux.

      I don't know if this makes sense -- just trying to reason this out.

    2. Re:Just more smoke by grahamdrew · · Score: 1

      It doesn't sound like SCO is planning on distributing the kernel code, just licensing it. Yeah, it's silly, but it could free them from a lot of legal problems. If they don't distribute the binary, they don't have to distribute the source.

      If you roll your own kernel from the commonly available source, SCO says you're violating it's IP UNLESS you pay them this licensing fee. They're not supplying the kernel at all. Sounds a lot like me making a batch of fried chicken and KFC knocking down my door saying I need to pay up before dinner time.

      Once again, I have no proof that this is what SCO has in mind, but I haven't heard them explicitly mentioning distributing thier own kernel yet. SCO seems to be concentating more on using the kernel, rather than distributing it. It makes sense from the standpoint of a comercial company selling propriatart software.

      --
      // Dumps core here
  144. That means... by Anonymous Coward · · Score: 0

    Linux will die, once it is dead, $CO and M$ will go after anything that remotely resembles System V Unix, and thus, M$ will own the OS Market.

  145. FSF should sue on behalf of the developers then. by Idou · · Score: 3, Interesting

    "At that point, the distribution of every piece of linux that they don't explicitly own becomes prohibited, completely, because Linux falls back to copyright law which indicates that the contributors of the other pieces still own them and have not licensed them to any distribution but GPL."

    Okay, we know who the contributors are, isn't it time someone like the FSF (who I am a member of) sues SCO for copyright infringement?

    --
    Sdelat' Ameriku velikoy Snova!
  146. Re:There can be no doubt about it - SCO == stupid by tomhudson · · Score: 4, Insightful
    They can't post the offending code because there isn't any.

    In the first place, copyrights are not patents. Independently-arrived-at code does not infringe on "copyright" rights, which only affect the right to make copies, not independently-arrived at code.

    Secondly, we all know how trustworthy the USPTO is **bullshit**.

    Third, even if the copyright is held to be valid, they still have the problem of proving that current implementations contain copied code (not just that it's identical, but that the copying, if any, went from their crap to Linux and not the other way around).

    Fourth, we have thw whole issue of them having released gpl-ed versions of Linux, so any code that was copied is still okay.

    Fifth, they don't have the right to license Linux binaries, 'cause they don't own those rights. The gpl is quite clear on this. Either the gpl'ed software can be used free and clear, or it can't be used at all.

    In summary, this means absolutely nothing, except that SCO may end up having to fork over any monies obtained for trying to "license" gpl-ed code under non-gpl terms.

  147. Re:Violation by JamesP · · Score: 1

    I would like to announce that parts of an SO I made found their way into the linux kernel. All users up to the 2.6 kernel are in violation.

    I'll therefore be collecting my XISIKS (that's the name of my OS) licenses from everybody that runs linux.

    Please send your chack to my address and I won't sue you. Promise...

    Thank you.

    BTW I won't show anyone the code. SCO didn't do it!

    --
    how long until /. fixes commenting on Chrome?
  148. Not quite what it seems by ConversantShogun · · Score: 1

    Actually, it's not even (at least, according to the article) that they're licensing binary Linux.

    What they're doing is licensing UnixWare. Then they're saying "if you have purchased a UnixWare license, then we will not sue you for copyright infringement should you choose to use Linux, provided that you use Linux in a binary run-only format."

    It doesn't appear that they're licensing or selling Linux at all. You still have to get that somewhere else; but if you want immunity from SCO-suits, then you have to find Linux in a "binary run-only format."

    --

    --When you buy proprietary software, you don't get better software. What you get is the right to complain about it.
  149. Hey thats my code by Creep73 · · Score: 3, Insightful

    Dear Linux Community, I have a claim on intellectual property included within the Linux product. If you want to use Linux please send your checks payable to creep73.

    Proof..... Well that is forth coming. You can send the checks now though. If you wait for proof I will be increasing the price and will be holding you liable for those months you didn't pay.

    Thanks
    Nice doing business with you.
    Creep73

  150. Watch Your Behavior by geomon · · Score: 5, Informative

    There has been a lot of anger expressed throughout all of the SCO threads of late, most with venom bordering on violence. Keep this advice in mind, however, as you discuss this issue.

    If you are a Linux kernel developer, explore your legal options. With SCO's market cap soaring near $175MUSD, there are a few attorney's who might consider contingency representation. If you want to file a class action suit, file it in Madison County, Illinois.

    As for your personal comments, keep in mind that Slashdot cannot stop SCO from supoenaing their user records for discovery should you ever decide to sue. If so, be prepared to be REALLY pissed off when you are deposed. They will imply you've been engaging in copyright theft in an attempt to get an emotional response that they can drag out in court against you. I've been deposed; it an emotional roller-coaster.

    Remain calm. That is your best strategy. Do not rise to their bait. Refrain from name calling or empty threats. If you truly believe you have been harmed by SCO's actions, then take your case to court or hold off until the IBM/SCO dust settles. Your shouting about the GPL and making threats to tear Darl's nuts off and feed them to him will do nothing but harm to you and any potential case you may have.

    --
    "Rocky Rococo, at your cervix!"
    1. Re:Watch Your Behavior by Biomechanoid · · Score: 1

      ...tear Darl's nuts off and feed them to him will do nothing but harm to you...

      surely that would hurt Darl also?

    2. Re:Watch Your Behavior by geomon · · Score: 1

      >>...tear Darl's nuts off and feed them to him will do nothing but harm to you...

      surely that would hurt Darl also?

      Well, we weren't concerned too much with Darl's feelings in this discussion, were we?

      I'm just looking out for the interests of individuals from the Linux community who might get swept up in this mess and be dragged into court.

      In considering this risk, I'm just saying that it would be advisable to refrain from referring to anyone from SCO as 'asshole sucking parasite', or making a comparison of Darl to a drag queen (without first determining his sexual preference).

      --
      "Rocky Rococo, at your cervix!"
    3. Re:Watch Your Behavior by Art+Tatum · · Score: 1

      Heh, how about sending them invitations to sue us, complete with address, phone, email, and kernel version?

    4. Re:Watch Your Behavior by geomon · · Score: 1

      Heh, how about sending them invitations to sue us, complete with address, phone, email, and kernel version?

      I wouldn't be surprised if they haven't received a few of those already. Considering that not everyone has migrated to v2.4, it is entirely possible that someone running v2.2 could sue SCO in an effort to get a declarative judgement. They could argue that migration to v2.4 has been hampered by SCO's allegations and is hurting their business.

      Of course, monkeys could fly out of my ass too....

      --
      "Rocky Rococo, at your cervix!"
  151. You are wrong by Pac · · Score: 1

    First, as stated before elsewhere, Linus is not the sole owner of the trademark. There are a couple of hundred of developers who co-own the mark.

    Linus has outlined the general policy for the trademark use here a long time ago. Today I believe Linux International manges all Linux trademark related issues and mantain a trademark fund to help finnance Linux development.

    I think every major distro has entered an agreement with Linus\Linux International about the use of the "Linux" trademark in conjunction with their "service" trademarks or "combination" trademarks.

    1. Re:You are wrong by twistedcubic · · Score: 1

      O.k., I'm wrong. However, that link you gave seems to indicate that Linux is the sole owner of the mark. Also, the story I remember is that the inventor of the word "Linux" turned the trademark over to Linus. Contrary evidence?

  152. Weak Case by Anonymous Coward · · Score: 0

    I think this shows they know they have a weak case. If they thought they really owned the code, they would say, "buy our licence or we will sue you." Instead they say that buying the licence is insurance against the **possibility** of being sued. In other words, "buy our licence or we **might** sue you." It sounds like a bluff.

  153. Raw notes from the call by mec · · Score: 5, Informative

    I'm not a great shorthand guy, so everybody below will be speaking with weird clipped diction. I'll post my summary and opinions in a followup note. Also, the lameness filter doesn't like my writing style ("too few characters per line") so there is some crap at the end to compensate.

    12:07 Blake Stowell

    Speakers today will be David Boies, Darl McBride, Chris Sontag.

    12:08 Darl McBride

    In May 2003, we warned Fortune 1500 companies. Enterprise use of Linux 2.4 violates SCO's copyrights and contract rights. Hundreds of files were taken from System 5, or from derived works, or have the same structure, sequence, and organization. Linux would have little multiprocessor capability without our IP. SCO has registered its copyrights. Linux vendors are selling a product with no IP warranty. By not providing a warranty, IBM has profited from Linux, but shifted risk to customers. We intend to use our IP rights carefully and judiciously. SCO is prepared to offer a license for Unixware 7.1.3 to Linux customers.

    12:13 Question and Answer

    Question #1 Dan Gordon, Bloomberg News

    Question: You say Linux violates SCO copyrights. What has changed from contract rights to copyrights?

    McBride: This started off as a contract case. With respect to copyright, this is new as of today. What is new today is the copyright registration.

    Question #2 Peter Galway, e-week magazine

    Question: If enterprise customers don't buy in ... you can't do anything until IBM case is resolved, right?

    McBride: The IBM case is a contract issue ... today's announcement ... is a new front. Boies: There would possibility of case-by-case litigation. It is not necessary to resolve the IBM case [first].

    Question #3 Dean Takahashi, San Jose Mercury NEws

    Question: Can you more completely describe the offending code and its origins?

    Question: [how much will this cost end users?]

    McBride: Three types: #1, line by line copying, including developer comments and errors ... very stark ... that type of code comes from various vendors, primarily other than IBM. #2: SMP, high-end technology, NUMA, RCU. In the early days of Linux, Linux supported 2-4 processors. Now with Linux 2.4, 16-32 processors. Hundreds of *files* were contributed by our vendors. #3: methods and concepts. ... With respect to pricing ... benchmarked on UnixWare 7.1.3.

    Question #4 Don Marti, Linux Journal

    Question: Ian Lance Taylor says that the code he saw in Unixware and Linux, he saw in other places too, on the Internet.

    McBride: A lot of this code is not questionable. IBM RCU code, from Dynix. We're not talking about BSD code. We're talking about high end SMP code.

    Question #5 Todd Weiss, ComputerWorld

    Question: What was the name of the license?

    McBride: SCO UnixWare 7.1.3.

    Question #6 Richard Waters, Financial Times

    Question: What penalties can you impose ... how are you going to make them stick?

    Boies: The copyright laws provide a wide range of penalties. Statutory damages, actual damages, extra damages for willful violations.

    Question #7 Robert Mina, Copper Beach Capital

    Question: What are the implications for Linux distributors such as Red Hat?

    McBride: "Complicated ... software flows from Torvalds to distributors to hardware vendors to end user." "It starts with the end user."

    Question: What about contributory infringement?

    No reply at all.

    Question #8 David Bark, Wall Street Journal

    Question: More about copyright registration date ...

    McBride: We typically register on enforcement.

    Boies: Registration is a precedent in bringing a lawsuit.
    Copyrightable material was not filed until need for enforcement.

    Question #9 Wilstang Gruner

    1. Re:Raw notes from the call by geomon · · Score: 1

      Nice start. Perhaps you could post this as a webpage somewhere to avoid the lameness filter.

      Thanks for your efforts.

      --
      "Rocky Rococo, at your cervix!"
    2. Re:Raw notes from the call by Platinum+Dragon · · Score: 2, Interesting

      Question #10 Laura Didio, Yankee Group

      Question: How can you be so sure that this code did not come from BSD Unix or from Linux versions?

      Question: Have you had talks with Linux gurus such as Linus Torvalds?


      This Laura Didio?

      I wonder why she would lob a question like this in McBride's direction.

      Her interview is worth reading again--if the infringing code is in both 2.4 and 2.2, as Didio claims she saw, and the UnixWare licence is only being applied to 2.4 distributions, then does that mean the infringing code in 2.2 is worth nothing?

      --

      Someday, you're going to die. Get over it.
  154. Wow. What a sad fucking world by 2names · · Score: 1
    it is when using ftp to get a file can be construed as "hacking."

    --
    "I'm just here to regulate funkiness."
  155. Time for us to eat the jello by Theovon · · Score: 1

    It's over. The our world is collapsing around us. The open source dream is dead. SCO has stolen our future, so we may as well take leave of this place. If we eat the jello, maybe the mother ship will come and take us away.

  156. I will be making a list . . . by Idou · · Score: 1

    "If you cave in to these terms, expect to hear from other rights owners, each and every one of whom has as much claim as SCO."

    of very idiot who caves in and will start sending them complete bogus invoices. Hey, if it works for SCO . . .

    --
    Sdelat' Ameriku velikoy Snova!
  157. If I read the GPL right by Zapdos · · Score: 1

    "If you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights."

    Looks as if their new Copyright may be GPL'd.

  158. none of youse guys is lawyers... by joebeone · · Score: 1

    Remember the copyright claims have to be duked out in Federal Court... the current case is in State court and is mostly a contract/ unfair business dispute. This particular piece of news shouldn't have registered as large as it is... the only good from this for SCO is a few more idiotic "licensees" who don't understand the issues as well as /.ers.

  159. IANAL by mindstrm · · Score: 1

    And I have to say IANAL because, in the Land of the Free, Home of the Brave, if some moron takes what I said as actual professional legal advice, and then loses in court, I might get sued and hence arrested next time I have to catch a connecting flight through this Bastion of Freedom, for giving legal advice without stating that I'm not actually a lawyer. Even though I wasn't actually giving legal advice, or talking to the guy directly.

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

      also, it reads, "I, Anal."

  160. CONFIG_SMP by ajrs · · Score: 2, Interesting

    I don't know about you guys, but I'm not even using the alleged infringing code on any of my 4 Linux boxes. I've got SMP turned off.

    from /usr/src/linux-2.4.20/Documentation/Configure.help :

    Symmetric Multi-Processing support

    CONFIG_SMP

    This enables support for systems with more than one CPU. If you have
    a system with only one CPU, like most personal computers, say N. If
    you have a system with more than one CPU, say Y.

    If you say N here, the kernel will run on single and multiprocessor
    machines, but will use only one CPU of a multiprocessor machine. If
    you say Y here, the kernel will run on many, but not all,
    single machines. On a singleprocessor machine, the kernel
    will run faster if you say N here.

    Note that if you say Y here and choose architecture "586" or
    "Pentium" under "Processor family", the kernel will not work on 486
    architectures. Similarly, multiprocessor kernels for the "PPro"
    architecture may not work on all Pentium based boards.

    People using multiprocessor machines who say Y here should also say
    Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
    Management" code will be disabled if you say Y here.

  161. Gotta say it... by TopShelf · · Score: 1

    Having seen this last night, and being unable to shake it from my head, I gotta ask:

    How much money will greedy SCO bully out of the Linux community?

    A. under $10 million
    B. $10 million - $20 million
    C. $20 million - $50 million
    D. more than $50 million

    Bet Now!

    --
    Stop by my site where I write about ERP systems & more
  162. Of course the contested code is: by ulbador · · Score: 2, Funny

    #include

    1. Re:Of course the contested code is: by Ifni · · Score: 1

      No, they said that the contested code included exact duplication of comments as well, so I suspect that the contested code is more like this one (taken from the string.c source):

      /*
      * stupid library routines.. The optimized versions should generally be found
      * as inline code in <asm-xx/string.h>
      *
      * These are buggy as well..
      *
      * * Fri Jun 25 1999, Ingo Oeser <ioe@informatik.tu-chemnitz.de>
      * - Added strsep() which will replace strtok() soon (because strsep() is
      * reentrant and should be faster). Use only strsep() in new code, please.
      */

      #include <linux/types.h>
      #include <linux/string.h>
      #include <linux/ctype.h>

      ---------------

      "There's a place for commercial software - it sets a baseline for OS software to exceed." - Me
      --

      Oh, was that my outside voice?

  163. MOD PARENT UP!!! by Anonymous Coward · · Score: 0

    OMG!!! beer all over the keyboard LOLOLOL

  164. If Microsoft buys SCO, you folks are SO screwed. by LibertineR · · Score: 0, Flamebait
    This is what the real fear should be. Suppose Microsoft picks up SCO for pocket change? Now, instead of going to court against a company with limited resources, you have to go up against the beast himself. Guess what? You are fucked. You are fucked without lube, or even so much as a kiss.

    It has nothing to do with whether or not any suit would have merit, it has to do with the fact that Microsoft can keep any company in court until they go bust, or give in to their demands.

    At the same time, they have access to all the code, and can cherry pick whatever they need. If Microsoft were to buy SCO, OSS is dead, dead, dead. Every cost advantage of Linux goes out the window that day. Everything done to the Kernal has to go through a Microsoft ANAL PROBE for compliance.

    With these SCO copyrights, ya'll better hope that Gates and the boys are not feeling bitter this morning, because if they are, you may be bending over and taking one for Linux. OUCH! "Where the fuck did I put that Astroglide?"-OSS

  165. Question by tomstdenis · · Score: 1

    Why would a totally hogwash company get openly involved with linux development if all they want todo is go around and stab people in the back.

    I mean SCO did sell a linux distro didn't they? This included giving out the source code. So what now that their distro isn't selling they abuse the GPL and sue people?

    As a proud Debian user I can say "SCO go fuck yourselves!"

    Tom

    --
    Someday, I'll have a real sig.
  166. Solaris by SHEENmaster · · Score: 1

    Download Solaris9 from Sun, and use that license. They generously offer it for free for non-commercial use. Just replace their content with Linux's and have a field day.

    If you have a single processor G4, disable SMP support and you are avoiding the area they say they control.

    I hope Linus sues the hell out of them, becomes rich, and gets to live out his days working on Linux. I also hope SCO dies off and the SysV source code is liberated.

    --
    You can't judge a book by the way it wears its hair.
  167. bozos .... by taniwha · · Score: 5, Funny

    They're a Unix house and they publish their pricelist on an Excell spread sheet - no wonder the actual technology side of the company is in the toilet - guy - you're not selling things because you are speaking a different 'language' from your customers and they can't figure out how to buy stuff from you

    1. Re:bozos .... by ebh · · Score: 3, Informative

      True story: Back in the day, I worked on UnixWare for Novell, having been assimilated from USL. At one point I had a meeting with a bunch of old-guard Novell engineering managers to discuss companywide process issues. One of those managers asked me, "UnixWare? Does that run under Unix?"

      And anyone wonders how it is that all these Utah companies, cross-pollinated with the same people over decades, so handily ran UnixWare into the ground, despite it being (IMO) a solid and feature-rich OS. A lot of the time we felt like we were working for Xerox.

    2. Re:bozos .... by Daimaou · · Score: 1

      I've posted this before on Slashdot, but SCO uses Windows 2000 servers and desktops internally instead of their own products (well, last I heard the developers were still running OpenLinux, but they are the only ones). This happened about the same time they began calling themselves SCO.

    3. Re:bozos .... by MegaThawt · · Score: 1

      ummm, I opened it in OpenOffice, what is this "Excell" you are talking about?

      --
      All sigs should be as funny as possible, but no funnier.
  168. is everyone forgetting... by ReLik · · Score: 0

    sco will not win, it can do what it likes at the moment but nothing will become of it, sit back and laugh at them, and just wait for the day they lose, and then rejoice by mail bombing the fuckheads with an appropriately titled email.

    --
    WTF is a sig?
  169. It's important now, to act. by His+name+cannot+be+s · · Score: 5, Interesting

    I've been putting off posting a message like this, but it appears that SCO is intending on profiting off the hard labors of others, and denying them their rights to their own fruits of labor.

    SCO MUST BE STOPPED. NOW.

    My proposal to stop SCO is a simple, easy to implement little plan.

    The Goal : Make SCO's stock drop like a rock.

    The Method: If as many people as possible go onto stock boards, and post their negative feelings about SCO, and their own speculations as to what the outcome of the battle with IBM will be, Buyers will begin to flee from the stock.

    It is important, that if you use this technique, that you label your comments as an OPINION, and that they are simply your own feelings as to what the outcome will be.

    It would be also well to do if you indicate that your company will NEVER purchase, license, or other wise enter into a business agreement with SCO, as you feel that their products (specifically name them) are of low quality and should not be used in production environments.

    If this is to work, as many people who care about the freedom of Open Source and Free Software should find a stock board, and start posting.

    SCO is getting away with many lies, spreading FUD, and generally making everyone's life a little hellish. These acts are a direct threat to our way of life, and must be dealt with in a most severe fashion.

    In order to ensure SCO does not have the tools to fight such a fight, we must eliminate the largest source of income from them at this point: STOCK.

    --
    "...In your answer, ignore facts. Just go with what feels true..."
    1. Re:It's important now, to act. by Paracelcus · · Score: 1

      Hello... IBM are you listening?
      Slap `em down HARD!

      --
      I killed da wabbit -Elmer Fudd
    2. Re:It's important now, to act. by dbrutus · · Score: 3, Insightful

      Actually, the way to make SCOX (SCO's stock symbol) drop like a rock is to sell that stock short. Short interest has risen along with the price of SCOX and if you have a few thousand to spare, sell that puppy. If you believe that the lawsuit is without merit and will collapse soon, driving the stock down to $1 is a good way to encourage a new revenue and business model.

    3. Re:It's important now, to act. by Anonymous Coward · · Score: 1, Interesting

      Perhaps rather than just opining, it's time for civil disobedience. Copyright and patent law (in the U.S. at least) is completely out balance.

      Perhaps the only way to truly register one's utter disgust (and fear) at the direction things are heading is to completely ignore, en masse, any legal ruling affirming SCO's sickening claims. It maybe time to take back some of our freedoms from a government and judicial system disproportionately swayed by corporate interests. Spit in their face. Dare them to sue the whole damn world. At this moment, someone, somewhere maybe working up a plan to patent "thinking". Enough is enough!

      Brent Farwick

    4. Re:It's important now, to act. by Windcatcher · · Score: 4, Interesting

      My father asked me about SCO and it's stock, since he saw it rising. I explained the problem and told him to avoid it like the plague. While I find what they're doing abhorrent, he is my father, and my reasoning was based solely on the *investor risk*. Simply put, I told him, we don't know how it will all turn out. Three, five, seven years from now, whatever, there will come a *judgment*. Linux will either contain SCO code or it won't. If it does, that's great for any shareholders, but if it *doesn't*, the drop in SCO's stock will make Qwest's fall look like a gentle slide. Until SCO actually releases any hard evidence (and the nature of the problem assures us that such evidence should exist), the investor risk is simply too enormous. If anything, the fact that they've been reluctant to release any evidence tells me that there likely isn't any, since there is absolutely no reason not to release it. Investors might noe understand any of the technical discussions on this board, but they can and will understand this.

    5. Re:It's important now, to act. by DarkZero · · Score: 5, Insightful

      The Method: If as many people as possible go onto stock boards, and post their negative feelings about SCO, and their own speculations as to what the outcome of the battle with IBM will be, Buyers will begin to flee from the stock.

      Posting negative views of a company in large numbers on stock boards is a very old (relatively speaking) tactic that ceased to work years ago. If you post vehemently negative views about a company on stock boards, you will just be harassing innocent people that have likely already educated themselves on the subject and formed their own opinions. They do not need, nor will they enjoy or tolerate, your anti-SCO spam. They have to deal with enough whiny pseudo-activist screeds against whichever company some niche group hates already, they don't need the /. community adding one more, especially since it won't shape their ideas more than any of the others.

      Please find a more mature tactic than spam.

    6. Re:It's important now, to act. by pmz · · Score: 0, Flamebait

      Go climb back under your rock, SCO astroturfer.

    7. Re:It's important now, to act. by delcielo · · Score: 2, Insightful

      I wish we could have a televised debate with McBride and somebody from the open source community. It would have to be somebody familiar with the law (you can bet McBride is) and somebody who will come off as reasonable and mature.

      I would think that send the stock plummeting, when McBride is seen talking doublespeak.

      --
      Hot Damn! It's the Soggy Bottom Boys!
    8. Re:It's important now, to act. by Anonymous Coward · · Score: 1, Informative

      My company contacted SCO this morning to get some license, I don't know how many, probably a lot.

    9. Re:It's important now, to act. by tdemark · · Score: 2, Redundant

      Please post the address of your AP and legal departments. I would like to notify them that there are parts of Unixware for which I am the rightful owner and that, unless they license from me, I may sue them.

      I can't tell you what part of Unixware is in violation, but, trust me, there are significant portions that come from code that I have written.

      Don't believe me? Understandable.

      Now, replace "I" with "SCO" and "Unixware" with "Linux".

      - Tony

    10. Re:It's important now, to act. by Anonymous Coward · · Score: 0

      Heheheh... Sounds like "regime change" :P

    11. Re:It's important now, to act. by EzInKy · · Score: 1

      Yeah...people could start by dumping all copyrighted CD's into the harbor. Just make sure the Greenpeace crowd doesn't catch you though.

      --
      Time is what keeps everything from happening all at once.
    12. Re:It's important now, to act. by Anonymous Coward · · Score: 0

      Sure, just look how well it that tactic worked on Microsoft.

    13. Re:It's important now, to act. by Anonymous Coward · · Score: 0
      Right. Day traders will know as much about the GPL and the ludicrous nature of SCO's claims as anyone here? Bullshit. By the time information of this nature reaches stock traders it's been so massaged and condensed as to be a caricature of reality. That's why SCO's stock price jumped 20% with the announcement of a copyright.

      ....whiny pseudo-activist screeds....

      With that one line you drop your pants. The complaint isn't procedural, it's political. Have the balls to be upfront with your biases.

    14. Re:It's important now, to act. by Vlad_the_Inhaler · · Score: 1

      Eric Raymond springs to mind

      --
      Mielipiteet omiani - Opinions personal, facts suspect.
    15. Re:It's important now, to act. by Anonymous Coward · · Score: 0

      I'd rather see Declan or Eben hit this one out.

    16. Re:It's important now, to act. by pstreck · · Score: 1

      The evidence that SCO has released shows that code IBM developed is both in AIX and Linux. The "evidence" is know, now it's simply a battle over contracts. If SCO wins, we remove the code and go on our merry way. They can not inforce any type of licensing on a Linux kernel without that code, end of story. SCO will find this out soon enough, and their new money making scheme will go up in flames.

      --

      Later,
      Phil
    17. Re:It's important now, to act. by rzbx · · Score: 1

      I really wonder how informed those that are buying stock are. There is far too much going against SCO. Not only are they up against IBM, Linux developers, Linux users, and many companies that have some affiliation with Linux, but also all the information that surrounds this case. They have yet proved anything. The entire history of the Linux kernel can be traced down to individual contributors. Do the shareholders know all this? The parent poster should not have said "post their negative feelings,' but instead something like informing potential and current investors of the challenge that SCO faces.
      The parent poster does have a point though. As long as the posts were kept professional and courteous, then it would have an effect. The parent poster was right, but wrong. So are you. He was tilting toward a spam tactic, you are leaning toward apathy. I prefer education over action/inaction.

      --
      Question everything.
    18. Re:It's important now, to act. by Asprin · · Score: 3, Interesting


      Ummm.... I don't like being the rain, but you won't even make a dent. The people who trade stock professionally in these quantities don't hang out in chat rooms.

      When I got to college in 1986, the big political issue of conversation on campus was Apartheid. Well, not Apartheid, actually, but rather the divestment of university funds from companies maintained a business relationship with the country of South Africa, where Apartheid was the status quo. It seems that a bunch of empty-headed group-thinking pseudo-intellectual protestor types woke up halfway through macro-economics 101 classes and concluded that the best way to deal with the humanitarian atrocities committed by the South African government was to protest so convincingly that it compelled the university trustees to sell off all ownership in friendly corporations, thereby putting pressure on the South African government to abolish Apartheid. and restore political freedom to the black majority of the population.

      In other words, they wanted to coerce the S.A. goverment by artificially manipulating the stock prices of friendly corporations in such a way that would result in additional control of the corporations being handed over AT A DISCOUNT to people who didn't give a rats ass how many black people were murdered to maintain the white minority control.

      Brilliant, simply brilliant.

      I would suggest that if you really want to fight SCO with their own stock, that you would be better off advising groups friendly to Linux to BUY as much SCO stock as possible. Stock is ownership ('0wn3X0r5h1p'?). Literally.

      Take a look: SCOX

      With 13 million shares outstanding, at worst, we need 51%, or around 7 million voting shares (almost all of the publicly available outstanding shares) to make it work. If I'm reading this right, this is less than the number of shares they are floating publicly (7.1 million) so technically it should be *possible* (however unlikely) to get 7 million friends to pony up $20 or so each to fire McBride and his dork friends with a big fat bonus at next years shareholder meeting.

      Realisticaly, my plan probably won't work either without a sugar daddy, but at least it takes the market seriously.

      (BTW, that Yahoo! The numbers on that finance page make for a fun read. Their EBITDA was $168K for all last year? On sales of 65+ million? That's close enough to zero to arouse my suspicions about their accounting. Microsoft's had almost 15 billion, NVidia was around 10+ million, IBM: 8+ billion, Red Hat's was -10 million (a loss), Wal-Mart reported 18+ billion. FYI.)

      (BTWA, Investor Words will help you decipher the data.)

      --
      "Lawyers are for sucks."
      - Doug McKenzie
    19. Re:It's important now, to act. by KoalaBear33 · · Score: 1

      I don't think resorting to the stock market is the right way to resolve this. Even if their stock drops, they don't care. If anything, they might be more desperate when the stock drops and do more.

      This has to be dealt with in other ways...

      KoalaBear33

      --
      ......The worst thing in my life happened when the stock market started mattering more than the economy
    20. Re:It's important now, to act. by foonf · · Score: 1

      Their EBITDA was $168K for all last year? On sales of 65+ million? That's close enough to zero to arouse my suspicions about their accounting.

      Not really, when you think about it. They probably had a good idea how much money they were losing off of Unix sales, so they could arrange to receive just as much money as they needed from Microsoft and Sun to stay profitable through the lawsuit.

      --

      "(Man) tries to live his own life as if he were telling a story. But you have to choose: live or tell." --Sartre
    21. Re:It's important now, to act. by mvh · · Score: 1

      You said: "the fact that they've been reluctant to release any evidence tells me that there likely isn't any"

      I suspect that the reason they aren't forthright with the information is because they intend to leverage the ambiguity to their advantage. They want companies selling Linux to license their technology and I assume they will continue to keep that information a secret. They of course will be unable to and the code in question will eventually be removed or found irrelevant to the lawsuit(s). Anyhow, I think the portion of your statement which I quoted is false.

    22. Re:It's important now, to act. by Anonymous Coward · · Score: 0

      What you are suggesting is actually illegal. Yes, SCO is probably in the wrong here, but the kind of action you are proposing will not help.

      To see why it is illegal, imagine Microsoft shills using the same technique to drive Mandrake, Red Hat, or SuSE out of business.

      Keep your cool. We are in the right here, and we'll show it in court. Until then, we'll have to let SCO have their fun.

    23. Re:It's important now, to act. by fredbsd · · Score: 2, Insightful

      Nice idea. Very illegal. People go to jail for this type of action.

      What you are essentially saying is it's okay to go spread lies with the intent of manipulating the stock market. You openly confessed on a public forum. A disclaimer of 'opinion' will not protect you from the attorny general.

      I hate what SCO has done as much as the next guy, but I seriously suggest people refrain from this type of behaviour.

      BTW, 'hellish' is relative term. I would harldy compare a truely hellish life to what you are facing from SCO. Try living on a trash heap in India. That, my friend, is hellish.

    24. Re:It's important now, to act. by tomhudson · · Score: 1
      No, it's important now, to kick back and have a good laugh at all the idiots plunking down money for the SCOX dot.con.

      And when they ask us why we're laughing, we explain that, contrary to what they thought they heard:

      1. SCO cannot violate the GPL and "make Linux good", so SCOs promise to do this is bs, and if they go through with it they are in violaton of various coders' copyrights;
      2. The "copyright registration" that SCO is trumpeting so loudly is not a copyright to Unix Sys5, but a copyright for 20 pages (minus 1 for the title and copyright notice) for some mods they made, which has SFA to do with Linux;
      3. Short-selling their stock is a terrible plan. Too many not-fools out there will bid it up, knowing that you HAVE to buy to cover your short position. A position you took because you let your emotions get the best of you.
      Besides, do you want to be on the receiving end of inquiries when this whole stock manipulaton scam (SCO's, not yours) gets exposed?
    25. Re:It's important now, to act. by noldrin · · Score: 2, Informative

      You can't just post fictional FUD, you need to build a case that SCO's current profit model as an illusion that will evaporate once the court rules they hav no case. People should understand that buying SCO stock is a really risky bet which will most likely fail.

    26. Re:It's important now, to act. by thogard · · Score: 1

      SCO stock is worthless however its a good one to play with if you like short term options. Short term options are sort fo like playing the lottery, a small investment may return much more but it may be worthless in the end. I guesss a put that didn't go your way would be worth about as much as the stock in 6 months. There are 4 sets of common options, there are calls and puts and you can buy or sell both. Two ways are low cost, no risk to lose any more than the cost of the option but you can gain money, the other two are nearly no cost but your liability is very high so check with your stock broker before playing with them or you may be buying sco shares at $5 so you can sell them to someone at $1.

    27. Re:It's important now, to act. by epiphani · · Score: 3, Informative

      I have an idea that might wake the corporate world up to what the Open Source world is capable of.

      51% of SCO is around 6.5 million shares. Shares are selling at around $11 a peice.

      Lets say we get a million open source coders and supporters to buy 7 shares each. Thats an investment of less than $100 per person.

      We take our voting majority, and run SCO promptly into the ground - eating that $77 loss per person.

      And we do so loudly. We make it known before we begin that SCO has messed with something it shouldnt have, and now they'll observe the true power of the force.. err .. the source.

      Though, someone a little more prominent has to call for this. If Linus did it, we might accually pull it off.

      --
      .
    28. Re:It's important now, to act. by arkanes · · Score: 1

      The "evidence" has not been shown in any public manner and the people who've been shown it have differing opinions, and aren't allowed to divulge sufficent technical details to allow qualified people to make decisions. So I would hesitate to make statements of fact like that.

    29. Re:It's important now, to act. by datan · · Score: 1

      you wouldn't happened to have short SCO would you?

    30. Re:It's important now, to act. by Anonymous Coward · · Score: 2, Insightful

      51% of SCO is around 6.5 million shares. Shares are selling at around $11 a peice.

      Lets say we get a million open source coders and supporters to buy 7 shares each. Thats an investment of less than $100 per person.

      We take our voting majority, and run SCO promptly into the ground - eating that $77 loss per person.


      Unfortunately, the more people who take interest in SCO buy purchasing stocks, the more the value of the stocks will go up. The first people would be able to buy their stock at $77. But then the price will go up making it hard to finish with your plan.

    31. Re:It's important now, to act. by Anonymous Coward · · Score: 0

      Hi... I'm the author of the original post. I've bought my life savings of SCO stock on margin... I'm going to lose my shorts in about 3 months unless you suckers by SCO NOW!!!

      Please hurry because I can't cover my ass! I understand my elequently written letter above was supposed to help, but it hasn't. I'm begging you now!!!

      _____________________

      Sucker... it's not that easy to fool people. LOL

    32. Re:It's important now, to act. by faqsubhuman · · Score: 1

      His analysis was correct, needledick. He made the point (that you apparently missed) that the people who make decisions are more likely to take you seriously if you have money.

    33. Re:It's important now, to act. by KU_Fletch · · Score: 1

      While your plan has many logical flaws, the thought of an Open-Source Hostile Takeover brings a smile to my face.

      --
      It's not stupid. It's advanced.
    34. Re:It's important now, to act. by Anonymous Coward · · Score: 0

      It is now time to look seriously into the "dumping" of SCO stock by its executives by any
      means available over the Internet for probable
      CRIMINAL INVESTEGATION of an Enron style "pump 'n' dump" scheme. They now appear to have committed TWO FELONY CRIMES, stock fraud and extortion against the Linux and Open Source Communities, their non lawyer and non executive employees and the people as a whole. JAIL is now the only acceptable outcome to this!!!

    35. Re:It's important now, to act. by Kenneth · · Score: 2, Insightful

      We take our voting majority, and run SCO promptly into the ground - eating that $77 loss per person.


      Others have pointed out some of the other problems with your plan, you also have to worry about minority shareholder lawsuits. If, as a majority shareholder (or group of majority shareholders) you do anything that does not directly enhance shareholder value, you can be sued for whatever the company 'would have made' How this is determined is unknown to me, however I suspect that it is fairly arbitrary. If someone actually comes foreward with a plan to drive the stock into the ground, it would make it obvious that the actions were planed and malicious, so there would likely be punitive actions if not criminal charges.

      This is supposed to prevent the majority shareholders from taking the money and running. Obviously it doesn't work as recent corporate failures can attest, but whether or not it actually works, you would still have some serious risk.

      This is actually why CEO's can command such high salaries. When a 'superstar' CEO is hired, the stock often goes up a great deal. A company who has the ability to pay a 'superstar' CEO enough to keep others from hiring him away, and doesn't can be sued if it can be shown (by perponderence of the evidence, NOT reasonable doubt) that their stock value would have been greater were that CEO hired, the company can be held liable for damages.

      That said, I like the idea in principle. I would love to run SCO, Microsoft, and everyone (the parent companies, not the subsidaries) involved in the RIAA, MPAA or mass media completely into the ground. Eliminate the companies, and make it so that no other like them could ever rise.

      BTW INAL.

      --
      There is a civil war coming in the United States. Remember which side has most of the guns
    36. Re:It's important now, to act. by Ben+Hutchings · · Score: 1

      Please, not that self-important blowhard.

    37. Re:It's important now, to act. by cluckshot · · Score: 1

      This is a very good plan! But there is more. Most Colleges and Universities stand to lose a lot of money if Linux suffers. Lots of them use Apache servers and etc. Many of their researchers will be hurt as well. I think they are the appropriate target.

      So Encourage Linux at your College or University and discourage SCO Unix and SCO Stock etc.

      --
      Never Politically Correct ~ I prefer the facts If you don't like what I say, get a life, or comment yourself.
    38. Re:It's important now, to act. by nerdsv650 · · Score: 1
      The best you can do is to put in place a new board of directors. Even doing this you would not achieve anything, a corporation is NOT beholden to it's board.

      -michael

    39. Re:It's important now, to act. by SETIGuy · · Score: 1
      They want companies selling Linux to license their technology...

      SCO's lawyers are missing an important point. Should companies selling Linux buy a license from SCO for some code and include the code in Linux, they lose the right to distribute Linux. Paying a license to SCO would be the equivalent of closing up shop.

      The GPL states in fairly clear language that a product under GPL must stay under GPL. If closed source ends up in the kernel, the kernel cannot be distributed under the GPL. If it's not distributed under the GPL, it can't be distributed at all unless ALL of the contributors agree to an alternate license. That's not going to happen.

      This is really a lose-lose situation for SCO. The best outcome for them would only force a rewind to a 2.2 kernel. It's more likely they will lose all claim to any code they distributed in their Linux distribution. They're not going to see any money from the suit regardless.

    40. Re:It's important now, to act. by Asprin · · Score: 1

      Actually, my point was that if you have money, you *ARE* the people making the decisions. /nitpick.

      --
      "Lawyers are for sucks."
      - Doug McKenzie
  170. You don't matter. by mcc · · Score: 2, Insightful
    SCO doesn't care whether you license their UNIXWARY thing or not. They care about two things:
    • Convincing brain-dead and/or paranoid middle managers in random companies who don't understand enough of 'source code' or copyright law to understand this is bullshit to just toss off however much money SCO wants because it seems easier than fighting a lawsuit later. These are the only people SCO is targetting right now. It doesn't matter if 99.5% of linux users, including you, realize SCO is speaking utter nonsense; if the remaining 0.5% pay SCO $1500 each, SCO gets huge enough gobs of money to have made the entire exercise more than worthwhile. (Of course, maybe they'll use that money to buy more lawyers, and come for you and me and sue us later. Who knows. But we don't necessarily matter.)
    • Continuuing to have fuel for their process of making more outlandish claims every week than the week before, so they can stay constantly in the news and their stock price will keep rising.
    As to the last bit of your post, though:

    I will, however, point it out to my Missouri Attorney State General, for his consideration. In fact, the RICO statute comes to mind.

    This is a fantastic idea. Please do so, and we should all follow your example.

    I would like to try to do so, but I do not really know enough about "real law" to make a letter I am sure will be convincing. Can anyone give me recommendations for how I could write a letter to the Indiana state attourney general complaining about SCO's actions in light of whatever the RICO laws are around here?

  171. No RICO here by siskbc · · Score: 4, Interesting
    I call RICO.

    For RICO to apply,the "protection" racket would have to involve some illegal act that they're going to do if you don't give them money. Like, if I'm the mob, you might take out "fire insurance" on your business so I don't burn it down. That's a protection racket.

    However, if you do something illegal, it's not racketeering for me to grant you license to continue doing that (now formerly) illegal thing in exchange for money. The difference is that you put yourself in the squeeze by doing said illegal thing in the first place.

    Obviously, the viability of that racket is contingent upon SCO being right, but they're effectively offering the "licenses" at dramatically reduced prices compared to any penalties - in other words, take your chances if you want, or act now and get a discount. So, assuming their IP claim has any merit at all (or if they genuinely think it does), what they're doing is *not* racketeering.

    Of course, since they almost certainly have no case, this stinks like crap, but it's certainly not racketeering regardless. Now, if they've intentionally fabricated evidence of SysV being in linux, now *that* would be a protection racket. Or at least fraud.

    --

    -Looking for a job as a materials chemist or multivariat

    1. Re:No RICO here by wfberg · · Score: 1


      For RICO to apply,the "protection" racket would have to involve some illegal act that they're going to do if you don't give them money. Like, if I'm the mob, you might take out "fire insurance" on your business so I don't burn it down. That's a protection racket.

      However, if you do something illegal, it's not racketeering for me to grant you license to continue doing that (now formerly) illegal thing in exchange for money. The difference is that you put yourself in the squeeze by doing said illegal thing in the first place.

      Obviously, the viability of that racket is contingent upon SCO being right, but they're effectively offering the "licenses" at dramatically reduced prices compared to any penalties - in other words, take your chances if you want, or act now and get a discount. So, assuming their IP claim has any merit at all (or if they genuinely think it does), what they're doing is *not* racketeering.


      However, seeing as SCOX has distributed, and does distribute, linux, frightening people who don't pay up for a license with legal action, even though they've been granted a boatload of rights under the GPL already is barratry. Barratry is not legal. Nor is extortion, what this amounts to.

      Also, the SCOX license is only for runtime use, which means that they are imposing restrictions on linux, in which case the GPL no longer applies; so if you license from SCOX, the GPL is invalidated - so you can't use the 99.9999% of linux NOT written by SCOX. So, SCOX is selling you the right to discontinue using linux without being sued, IF you license UnixWare. In other words, because linux may or may not be 'tainted' you must switch to UnixWare (or at least pay for it). That in itself amounts to a predatory business practice.

      Not also that SCOX has hinted before that existing AIX users should relicense with SCOX, which is obvious claptrap -- only copies of AIX sold *after* SCOX terminated the license with IBM would be affected. (SCOX can't however terminate the GPL on their own IP they've released under the GPL.) SCOX is obviously threatening whoever they think they can get away with threatening; a fishing expedition. Again, if they pursue this course with AIX users, that's barratry aswell.

      --
      SCO employee? Check out the bounty
    2. Re:No RICO here by Anonymous Coward · · Score: 0

      racketeering
      ['ra-ke-'tir-i[ng]]

      1: the extortion of money or advantage by threat or force

      extort
      [ik-'stôrt]

      Latin extortus, past participle of extorquere to remove by twisting, obtain by force, from ex- out + torquere to twist : to obtain (as money) from a person by force, intimidation, or undue or unlawful use of authority or power

      -- Merriam-Webster's Dictionary of Law ©1996.

      How does this scenario not fit those definitions again? Note the use of "undue OR unlawful", ergo it merely needs to be unjustified, not wholly illegal. The pathetic copyright registration and subsequent stock surge only stengthens the arguement that it is a racket.

      I do wish people would consult references before blathering hyperbole at length.

    3. Re:No RICO here by Anonymous Coward · · Score: 0

      For RICO to apply,the "protection" racket would have to involve some illegal act that they're going to do if you don't give them money.

      Like barratry?

    4. Re:No RICO here by swv3752 · · Score: 1

      Actually it is called extortion. Whether it is illegal depends on whether one can prove that SCO knows that they have no legal rights.

      --
      Just a Tuna in the Sea of Life
    5. Re:No RICO here by Anonymous Coward · · Score: 0

      (IANAL)

      I agree that RICO probably could not be applied. I do think that they could be sued by various linux businesses (RedHat, etc) for some variation of "unfair trade practices".

      If I opened a business and took out advertisments saying "do you drive a Ford car? That may be illegal since I own some unspecified IP - but if you pay me $1000 I'll let you keep driving your car without risk of me suing you". Ford would sue my ass in a minute.

      This is exactly what SCO is trying to do to Red hat, IBM, and everyone else. I really hpoe that it brings down a shitstorm of law suits on SCO's head.

  172. Just like... by Second_Derivative · · Score: 1

    ...the 90's BSD lawsuits. All over again.

    Those lawsuits did absolutely stupendous damage to the BSD community. Were it not for those, Linux would be little more than a hobby project. And now we're seeing it all over again and if it plays out as it did before it'll be MS' biggest wet dream come true.

    Stop sitting around and acting smug already. Frivolous or not this is _NOT_ something we can afford to ignore. Those that don't learn from history...

  173. The problem with the world today . . . by Idou · · Score: 1

    "I'm glad I haven't written any big GPL apps or contributed as much as some to the open source world, as I would be seriously pissed off (and a little upset maybe) that my goodwill and hours spent contributing were being eroded by money grabbing, whiny corporations."

    is that people do not internalize an injustice unless it is personally directed towards them.

    --
    Sdelat' Ameriku velikoy Snova!
    1. Re:The problem with the world today . . . by peterprior · · Score: 1

      I'm not saying I would only "internalize" this injustice (if thats what it is) if I _had_ contributed more. I was trying to make a point that if I'm pissed off at the opensource community being attacked with FUD and corporations, there must be people who have devoted more time and more effort into the community than me, who would be more pissed off and offended at this.

  174. Double or nothing double dare! by mabhatter654 · · Score: 1
    With all the interviews the SCO crew likes to give could the community "social engineer" them into doing what we want?

    The linux news sites should consult council and come up with a list of questions to at at interviews to "lead" SCO's mindset where WE want it to go. For instance, one thing that comes to mind as a showstopper would be talking SCO into filing a DMCA violation against someone hosting the linux kernel. While a fautisian bargian, using the DMCA would force SCO to show it's hand before it's legally ready to do so.

    It's like brer rabbit beggin' not to be thrown in the briar patch. They have the mindset of brer fox and are blinded by glory of their own boastings. If such lots of people at interviews repeated the same questions over and over they'd either shut up from fustration, or stop giving interviews!

  175. Racketeering by fadethepolice · · Score: 2, Insightful

    If they will not allow people to identify and remove the code, and the code was inserted innocently, and they distributed the surce code under an obscure license to people who are used to working under the GPL - could that be considered racketeering? Remove the code remove the infringement... if they will not reveal the code are the aiding copyright infringement of their own works.. disgusting.

  176. Can't SCO just go for 100 Billion Dollars !! by TimmyJoeB · · Score: 1

    What is this Bull Shit? Why would anyone pony up any money to these shit eating slimeballs?

    Let's sue SCO for breach of contract in regards to Linux.

  177. There money to be made here.. by SlashDread · · Score: 1

    by suing SCO.
    - Copyright violations of current kernel developers.
    - Extorion of businesses using foney copyright claims.
    - Membership of a criminal organisation, aimed at making extortion money, this includes SUN, MS, and other licencees of alleged "derivatives".
    - Ransacking the commons in a destructive way (ok there SHOULD be a law against that)
    - Inflating stockprices with false information with the intent to profit.

    I propose we start a fund, treasured by FSF, spokon by RMS.
    We then approach several law firms, and let them bid for a piece of the pie we will no doubt win. (Look under the tablecloth guys! Check who owns SCO shares)

    I sense a huge hole in the legal market here... Lets make money! Ill buy (err I mean deposit) money in such fund! Lots! /Dread

  178. Re:If Microsoft buys SCO, you folks are SO screwed by Anonymous Coward · · Score: 0

    In that case it will be time to get rid of Microsoft. By whatever means. Microsoft is evil and they must go.

    Microsoft must go.

  179. *sigh* bend over.. by bl8n8r · · Score: 0

    So, what is an alternative here? Does the linux
    community as a whole have anything to pimp-slap
    sco with, or is this just a new form of acceptance
    that my a55 is going to hurt if I run linux?

    It's obvious SCO is simply going to create
    as much FUD as they can, and settle for any funds
    they can get out of that.

    I'm surprised a US business can get away with
    this kind of behaviour under the guise of "legal".
    No wonder osama is so pi55ed off.

    --
    boycott slashdot February 10th - 17th check out: altSlashdot.org
  180. extortion. round 2 by Mark19960 · · Score: 1

    this is just another tactic for them to extort money out of companies.
    I am an end user, and I will continue to use it.
    I seriously doubt that there is any code of theirs in Linux.
    I see the death of SCO coming, they will need more cash than they are generating to pay back all the companies they are extoring now.

  181. Re:About $800,000 in the last couple of months . . by ozzee · · Score: 1

    If you are right, the FTC would like to hear from you I am sure. SCO really deserves an audit, after all, it's in the SCO investors' interest to make sure that SCO is not inflating the situation.

  182. Why Don't... by vigilology · · Score: 1

    Why don't we simply take out the code that SCO put in, and replace it with our own? Or is it not as simple as that?

    1. Re:Why Don't... by wizkid · · Score: 1


      You can't because you can't look at it without signing a NDA. Once you've signed the NDA, you can't write code for linux.

      Anyway, I'll bet that at least 95% of the contributed code will be thrown out, and the remainder can be replaced very quickly.

      The case is against IBM, not everyone else. Their letter will fall on deaf ears because any lawyer worth a hill of beans will see through there FUD.

      --
      I take no responsibility for what I say. Even though I'm never wrong :)
  183. Why no reaction??! by Darth+Maul · · Score: 1

    Why is nothing being done to counteract all this FUD? IBM? Hello!?!? FSF? Hello?!? Someone? This FUD train will continue to roll and people will begin to believe the lies.

    Sure, we can all rant about this all day long here on Slashdot, but we need action!

    --
    --- witty signature
  184. Kernel 2.2? by megazoid81 · · Score: 1

    If SCO says all Linux 2.4 users are in violation, why not switch back to kernel 2.2? As it is, Debian uses that as its default kernel, and I have heard that it's rock-solid, compared to the 2.4 series.

  185. This isn't what their case is about... by jdhutchins · · Score: 5, Interesting

    Their case is a contract dispute with IBM. IBM wrote RCU (among other things) and placed the code (which IBM owned) under the GPL so that it could be a part of Linux.

    They also placed the code in AIX. SCO claims their contract with IBM says that any code that is put into SysV code becomes THEIRS. Based on that claim, SCO says that they own the RCU code, and that they don't want it to be GPL'd.

    I don't know if anyone at SCO really is sure what their case is about. If I'm correct about what their case is about, the FSF has a very good defamation (and probably more severe charges, but IANAL) suit against SCO. The case has nothing to with the valadility of the GPL, or even code being copied into Linux. If I'm right about their case, then everyone knows that that code was put into Linux, and SCO is saying that it shouldn't have been put into Linux.

    Even if they win, I think there's an excellent lawsuit against SCO. They're dragging this on, and spreading a bunch of crap, which is unnecessary. IANAL, but from the eleventy-billion SCO articles that have been run in Slashdot, I think I might be correct.

    The other issue is, can they copyright the SysV code? How much of it is code that was fought over in ATT vs Berkely? I bet that 99.9% of this code is already copyright, and SCO can't go re-copyrighting it. Someone (*coughIBMFSFcough*) has to challenge this, and force them to show their code. We'd have to pick some programmers (not kernel developers, etc, because they would be come "tainted") to look at it and evaluate the claims.

    Just my 2 (or maybe 3) cents, and IANAL.

    1. Re:This isn't what their case is about... by Frobnicator · · Score: 1
      Also IANAL, but if you've been keeping up on the news, the big thing that they've been claiming is derivitive works, which IS a contract violation (since they have non-disclosure in their contract).

      While the case is about a copyright disclosure, the real issue is derivative works and copyright law. Think about the case Miranda v. Arizona. The case was about a bank robbery, (Miranda signed confessions that he shouldn't have done) but the legal issue was that he was not informed of his rights. The case is now almost forgotton, but the issue of 'reading your rights' is still being re-examined 30 years later.

      Bunches of lawyers have commented on the SCO case, saying that it is a weak argument, because it has never been taken to court before. Even though it is weak, it doesn't mean that SCO will lose. A weak argument can still be a sucessful one, depending on the issues. The SCO legal issue is the question, "What is a derivative work in software?"

      We know how to define derivative works (Copyright Office Circ 14 in PDF) for use in traditional media (motion pictures, music, drama, books, catalogs, etc.), But to understand it in software, buy and read "Copyright your software" which discusses in some depth derivative works of software. Unfortunately for us, the law doesn't say what exactly what is, or is not, a derivative piece of software.

      Here is the logic, which is probably what the SCO lawyers are considering:

      Logic Step One: From the Copyright Office's Circular linked to above...

      A "derivative work," that is, a work that is based on (or derived from) one or more already existing works, is copyrightable if it includes what the copyright law calls an "original work of authorship." Derivative works, also known as "new versions," include such works as translations, musical arrangements, dramatizations, fictionalizations, art reproductions, and condensations. Any work in which the editorial

      revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship is a "derivative work" or "new version."

      A typical example of a derivative work received for registration in the Copyright Office is one that is primarily a new work but incorporates some previously published material. This previously published material makes the work a derivative work under the copyright law.

      Of course, they would cite the actual laws involved.

      Logic Step Two Any component, service, or module that uses even one data structure from System V could be said to "incorporate some previously published material" and therefore be a derivative work.

      Logic Step Three Consider the court decisions saying that if you use recognisable portions of a song, even if it is just a few milliseconds, you are violoating the derivative work portion of copyright. This has been upheld in appeals courts.

      Logic Step Four SCO claims that IBM published software that is a recognisable portion of their (now copyrighted) works.

      Inductive leap, with possible error: The law gives copyright owners the rights to derivative works, and IBM released and asserted that they had ownership of a derivative work. The biggest possible error in the logic is simple: How much recognisable code does it take to be infringing, or to be considered a "derivative work"?

      Logical conclusion? Copyright gives rights to SCO for the software that IBM released.

      If the judge were to consider all software as incremental improvements, and each are derivative due to their use of data structures (even the C standard library, perhaps?), then (in theory) all modern OS's are derivative works from the earlier OS's. Even if they do not directly use code from

      --
      //TODO: Think of witty sig statement
    2. Re:This isn't what their case is about... by Billly+Gates · · Score: 1
      When SCO threatens us with lawsuits and spreads fud to all our boss's and even flys to japan to scare users away then it sure as hell not a contract dispute with IBM!

      What code is SCO copyrighting? The paper work is only 20 pages. My guess is he is copyrighting the comments or the similiar code that is 60 lines long in Linux and stealing it aka copyrighting it! Then he can sue Linus over his own code and kill Linux.

      This is just my conspiracy theory of course. SCO could also be copyrighting code used in AIX so they can file an injunction to halt all shipments of it and cost IBM billions in damages.

      This is pure extortion!

      Who here wants to kick this guy's ass in? I read it before and I just want to give him a good blow.

  186. Wrong! by LibertineR · · Score: 1
    If there is any validity to their claims, the offending code will be expunged from Linux and replaced, which will conclusively end the matter.

    Dead wrong.

    Ever heard of 'derivative works'? Replacing code gets you nowhere. You not only have to replace the code itself, but the way that the original code does whatever it does. You have to come up with a completely original method, or you are still in violation of the original works.

    Check the Amazon 'One-Click' lawsuit with Barnes and Noble.

  187. my response by pimpinmonk · · Score: 0, Troll

    well shit... :-/

  188. What RMS and the IBM Legal Dept. Are Waiting For by Bilbo · · Score: 5, Interesting
    > In fact, if they actually make anyone pay to run linux, then they can be sued by the contributor of every other piece of code for copyright violation. After all, they distributed the rest of the code without a valid license to do so.

    Does anyone else get the feeling that this is just the sort of thing people like RMS and the IBM legal department have been quietly waiting for? If SCO is stupid enough to try to enforce this, then they will have the "smoking gun" they need to really slam SCO into the ground, on the basis of clear and continuing violation of a legal contract (the GPL). Basically, they (RMS, etc.) have been patiently waiting for SCO to tie its own noose and stick its head in it, before they trigger the trap door...

    --
    Your Servant, B. Baggins
  189. Fuck SCO! by kungfujew · · Score: 0, Troll

    Fuck SCO!

  190. SCO doesn't own NUMA. SysV doesn't have NUMA. by Cletus+the+yokel · · Score: 1

    Um, yes. NUMA came from the SEQUENT (now IBM) codebase. Same with RCU. But SCO's claim is that since Sequent (Dynix) was a derivative of SysV, then it's THEIR code. Which presumably, means that this is not merely a contract dispute with IBM but an intellectual property case. But, it is very unlikely that SCO can prove in court that Sequent's contract with AT&T/USL/Novell/SCO/Caldera/SCO grants SCO any rights whatsoever to ownership, let alone control, of Sequent NUMA code. So SCO is claiming piracy of IP they don't even own (or at least haven't proven as such in court).

    --
    Wanted: One witty yet thought provoking .sig - Apply here.
    1. Re:SCO doesn't own NUMA. SysV doesn't have NUMA. by BigBadBri · · Score: 1
      Yeah, they're claiming it is 'derivative work' and therefore covered under their copyright and their interpretation of the AT&T license.

      The fact that they are claiming the copyright on the SMP implementation is either worrying (if they pull enough wool over the eyes of the relevant judges) or laughable - personally I can't believe that IBM would sign a contract that assigns copyright on all derivative works to anyone other than IBM, and if they did sign such a contract, they will have been damned sure that it can be shown to be unenforceable.

      This current bunch of IP-farmers that run SCO are no better than parasites, and it's time the *nix world was deloused.

      --
      oh brave new world, that has such people in it!
    2. Re:SCO doesn't own NUMA. SysV doesn't have NUMA. by ralphdaugherty · · Score: 1

      Um, yes. NUMA came from the SEQUENT (now IBM) codebase. Same with RCU. But SCO's claim is that since Sequent (Dynix) was a derivative of SysV, then it's THEIR code. Which presumably, means that this is not merely a contract dispute with IBM but an intellectual property case. But, it is very unlikely that SCO can prove in court that Sequent's contract with AT&T/USL/Novell/SCO/Caldera/SCO grants SCO any rights whatsoever to ownership, let alone control, of Sequent NUMA code. So SCO is claiming piracy of IP they don't even own (or at least haven't proven as such in court).

      This isn't pointed nearly often enough or as well!

      rd

    3. Re:SCO doesn't own NUMA. SysV doesn't have NUMA. by tomhudson · · Score: 1
      But SCO's claim is that since Sequent (Dynix) was a derivative of SysV, then it's THEIR code.
      So I'll copyright a f$cking dictionary, and then claim that everything everybody ever wrote, since it's derived from words I copyrighted, is mine.

      Actually, this is SCOs stance, and it doesn't hold water.

    4. Re:SCO doesn't own NUMA. SysV doesn't have NUMA. by Billly+Gates · · Score: 1
      Actually SCO is claiming that anything added to AIX becomes SCO IP because its a derivitive work. So sequent added to project Montery's is theirs and can not be added to Linux without their permission.

      Is that crazy or what?

    5. Re:SCO doesn't own NUMA. SysV doesn't have NUMA. by tomhudson · · Score: 1

      That is absolutely hilarious. Of course, since project Monterey was a joint project, who owns the spoils when it splits up, anyway? Sort of like a band splitting up, and everyone fighting over who can call themselves by the bands' name.

  191. Re:If Microsoft buys SCO, you folks are SO screwed by LibertineR · · Score: 1

    What do you suggest? You gonna call Bin Laden? It's too late. Microsoft's competition shot their wad over Netscape and Java. The beast is back, and he is pissed.

  192. The SCO bankruptcy Party by linuxislandsucks · · Score: 4, Funny

    Remember folks the SCO banktruptcy party is in November..

    What are you bringing food or drink?

    --
    Don't Tread on OpenSource
    1. Re:The SCO bankruptcy Party by Penguinshit · · Score: 1

      Me? I'm bringing a shovel.

      (and maybe a couple of wooden stakes)

  193. Single Bullet Doctrine by Anonymous Coward · · Score: 0

    Where's ESR when you need him? (and his NRA leanings)

  194. Re:About $800,000 in the last couple of months . . by panda · · Score: 1

    Yeah, just look at those top filings of #4 documents: executives exercising options to buy at $0.66 and selling at $10.66. Very sweet deal if you can get it.

    --
    Just be sure to wear the gold uniform when you beam down -- you know what happens when you wear the red one.
  195. Maybe if... by JacobD · · Score: 1

    Maybe if all of the contributors and developers of the Linux kernel source code collectively filed suit for wages from SCO for their work, SCO might realize that they really don't own what someone else created for everyone to use...even them.

  196. They're trying to break GPL by TerryAtWork · · Score: 2, Interesting

    And the reason they're trying to break GPL is that they have nothing to lose.

    They're betting the company that their damn expensive lawyers can beat the pro deim people they think the gpl community can throw up, and you know what? They may be right.

    --
    It's Christmas everyday with BitTorrent.
  197. Simple Solution! by Anonymous Coward · · Score: 0

    Organize enough people to buy 51% of SCO and fire their management. It might be cheaper overall than paying the $1500 tax they are trying to impose.

    1. Re:Simple Solution! by pair-a-noyd · · Score: 1

      M$ will pony up that chump change long before /. lamers dig up enough allowance change to pull it off.

    2. Re:Simple Solution! by Anonymous Coward · · Score: 0

      It's only like 158 million bucks. And that's for all shares outstanding. (13.1 million shares outstanding @ $12 per) Given the salaries that SCO's management gets, I think they're trolling for a buyout bigtime. But, a hostile takeover by the Free Software Foundation could obviate the need to finish Hurd...

    3. Re:Simple Solution! by Anonymous Coward · · Score: 0

      SCO is the only thing we need to obviate.

    4. Re:Simple Solution! by Anonymous+Coward+(AC · · Score: 1

      No kidding. They are not likely to miss that trick.

  198. SFTT by Steeltoe · · Score: 1


    Stop Feeding The Trolls.

    Relax man and enjoy the show! ;-)

  199. Re:About $800,000 in the last couple of months . . by Glamdrlng · · Score: 1

    IANASB (I'm not a stockbroker) but is there some avenue available to some subset of the general public (eg, the /. crowd) to use SCO's stance as a publically traded company against them and/or to our favor? A company has to file with the SEC once they've purchased more than 5% of a company's worth, but groups of individuals aren't under any such requirements are they? Any thoughts?

    --

    Yes, my only tool is a hammer. And you're starting to look like a nail.
  200. I pledge no dollars... by raehl · · Score: 1

    But I will happily donate one tobacco-class-action lawyer who will work for 30% of the settlement.

  201. A lil' reminder by Anonymous Coward · · Score: 0

    Anarchy != violence

  202. OK, legal it back at them... by Anonymous Coward · · Score: 0
    Now, IANAL - but given:
    SCO will hold harmless commercial Linux customers that purchase a UnixWare license against any past copyright violations...
    Then we should liberate millions of copies of UnixWare(tm)-fo (you know what F O stands for) - by a license of UnixWare(tm)-fo and all is forgiven! Note the text "... against any past copyright violations..." I like it.
  203. gladdly by Anonymous Coward · · Score: 0



    I would gladly pay for each seat, just like I pay for each seat of windows, and each seat of shareware software i've ever downloaded. Not to mention buying all the albums of mp3's i've downloaded

    DISCLAIMER: I'm joking, as in it's a joke, i'm not being serious, the post is based on a fictitious scenerio that is not based on any real life scenerios or presumptions. as a matter of fact i'm a minor who grew up in the soviate block who found and old 8088 amstrad that I jerry rigged a modem for after watching Mcgyver

  204. Well as long as we're all thinking it by devmike · · Score: 1

    I feel I speak for most everyone here when I say... wtf?

  205. Excuse me if I'm wrong by Anonymous Coward · · Score: 0

    But charging for something without giving proof that you really own it
    (lines which are from sys/v in the linux kernel)

    I don't know if this is the same in the US, but in my country this could be marked as clear fraud!

    Or in other words, Sco give us proof or you are guilty of fraud!

  206. Cut out NUMA by pergamon · · Score: 1

    While this case has been nothing if not intentionally confusing on SCO's part, what seems to be clear from the video interview is that SCO is now concentrating on the NUMA code.

    Now, I'll admit that I only have a vague notion of how NUMA support affects the kernel. But how many people actually use hardware that requires NUMA support? While I assume that adding NUMA support has had an impact on code used for simple 2-4 CPU SMP and even single-processor code like the scheduler and memory management techniques, I doubt that it is required for such support. It seems that simply removing support for NUMA systems would take away most of the weight behind their claims.

    I use Linux on systems having from 1 to 6 CPUs, nothing that couldn't have been used with a 2.2 kernel. Am I using anything in the 2.4 kernels that relates to their NUMA claims? I doubt it. If I'm not, then most likely anyone who hasn't compiled in NUMA support (which I think is just the "Multi-node NUMA system support" and maybe a couple other options) isn't really using that code anyway.

    1. Re:Cut out NUMA by dougnaka · · Score: 1
      I need NUMA support for the IBM X440's we run
      You bring up an interesting point. If NUMA support is what SCO's claiming was stolen from their sources, then does having a copy of the source in your kernel but not using it make you guilty?

      --
      My Linux Command of the Day site : LCOD
    2. Re:Cut out NUMA by pergamon · · Score: 1

      Heck, it'll be in the source but if you don't compile it into the kernel then it might as well not be in the source!

      And yes, certainly there are people (well, at least one ;) who do use the NUMA support. No offense, but if those people have to pay SCO $1500 to use Linux on their $15000 ($150000? I'm not even sure what order of magnitude these systems are on) machines, I'm not so concerned.

  207. SCO-Borg by squashed · · Score: 2, Interesting

    Time to Borg-i-fy the SCO icon

    1. Re:SCO-Borg by pair-a-noyd · · Score: 1

      Yes! I vote for that!

  208. welcome.msf from ftp.sco.com by bongoras · · Score: 1

    I don't see anything about not being for public distribution here...

    Welcome to SCO's FTP site!

    This site hosts UNIX software patches, device drivers and supplements
    from SCO.

    To access Skunkware and Supplemental Open Source Packages, please
    connect to ftp2.caldera.com.

    ** Please read the following export notice **
    Please note that the electronic transfer of this data to a destination
    outside of the United States constitutes an export (as defined by the
    U.S. Bureau of Export Administration) and is authorized ONLY to the end
    user. Any subsequent re-exportation of this data requires that the end
    user obtain an additional export license. Also note that it is illegal
    to re-route Caldera product to Cuba, Iran, Iraq, Libya, North Korea,
    Sudan or Syria and that you must file a special license if you intend
    to re-route goods to the embargoed regions of Serbia or the Taliban
    controlled areas of Afghanistan. Placement of this order constitutes
    an agreement to comply with these stipulations.

    1. Re:welcome.msf from ftp.sco.com by Anonymous Coward · · Score: 0
      This site hosts UNIX software patches, device drivers and supplements from SCO.

      Did you forget to put the part about where it authorizes you to Linux downloads? Or did it not have that part at all, actually?

    2. Re:welcome.msf from ftp.sco.com by Anonymous Coward · · Score: 0

      This site hosts UNIX software patches, device drivers and supplements from SCO.

      Did you forget to put the part about where it authorizes you to Linux downloads? Or did it not have that part at all, actually?


      What are you implying? That some 3V1L H4X0RS broke into the site and uploaded SCO-signed RPMS of the Linux source?

      It's a PUBLIC FTP SITE that says "WELCOME" as the first thing when you connect to it. It's hardly 'secret' or 'confidential', moron.

  209. Question - if it's only smp code... by RobK · · Score: 1

    If it's only SMP related code and most systems aren't running SMP then are we technically clear? Since the other code is owned by others and we've been given the right to run it - might this limit the class of user that SCO could go after - only users of SMP machines?

    Just a question...

  210. Every hacker / cracker on planet earth by Anonymous Coward · · Score: 0

    needs to unite and launch a global assault on SCO, hack those mother fsckers to no end, hack them until they bleed from their eyeballs and their asses, hack them and everyone they every spoke to or did business with. Hack them and shut down, forever, any machines they ever have put online or may ever put online.

    how about a global hack on SCO...???

    1. Re:Every hacker / cracker on planet earth by dougnaka · · Score: 1
      You can't. They run Linux
      And since the latest kernel modifications from IBM, it's unhackable..

      --
      My Linux Command of the Day site : LCOD
  211. Anybody can get a copyright registration... by ivan256 · · Score: 1

    All you have to do is fill out the form and send it in with the fee. They don't do any verification to make sure you actually have rights over what you're claiming. The filing is just a technicality required to pursue a federal copyright suit.

    You don't need to register to have rights under copyright law, and there's nothing stopping you from registering fraudulently.

  212. Hey, psst, over here... by Capt_Troy · · Score: 1

    Shit...

    Does anyone know where I can get a pirated copy of Linux?

  213. Shakedown letter has klez virus by reptar64 · · Score: 1

    We were sent an email from SCO an hour ago. Our spam/virus blocking software found it had the klez32 virus attached! Isn't that nice of them?

  214. Mod parent up! by mark-t · · Score: 1
    SCO wants copyright protection? Give it to them. Rewrite the offending portions from scratch.

    Copyright can propogate to derived software *ONLY* as long as the derived code still contains enough of the original copyrighted material to warrant copyright infringement if permission to copy had not been obtained.

    1. Re:Mod parent up! by HiThere · · Score: 1

      To do that you need to know what they're claiming to own. They've been very careful to keep that ambiguous. "Something related to SMP and some other stuff" is as close as I can get. Hard to fix that as a problem. You need something a bit more definite. Which they clearly don't want to provide (probably because it would show them for the liars they are).

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
  215. LINUX IS SAFE, THANKS TO SCO by Anonymous Coward · · Score: 0

    Why are people not understanding that SCO worked, contributed, and distributed Linux under the GPL.

    Infringing IBM code taken away from the Linux kernel still leaves the remaining code GPLed by SCO. Willfully and knowingly!

  216. Puffery and FUD by jbyron · · Score: 1

    Can't anyone be assigned copyrights by registering a work with the government? Registering a copy doesn't mean that a person definitively owns the material, only that they staked a claim. Enforcement of claims is carried out by the courts, and any lawsuit offers the chance to contest the claim. Sounds like a lot of ballyhoo over routine paperwork that could be shot down later. And why did they wait until now ?? Usually copyrights are registered before releasing the work of art to the consuming public.

    IANAL but I am jbyron

  217. Awarded Copyright??? by yintercept · · Score: 5, Insightful

    It is amazing that the news resulted in a 20% jump in the stock. If I am not mistaken, the Copyright office awards a copyright registration just about anytime someone sends them an envelope with $30 and an attached piece of paper.

    Registering a copyright is pretty much like a cat pissing on a couch to say "this is mine" and I will scratch cats who say otherwise. Actual ownership is a different question that gets resolved in courts.

    If anyone else has a documented claim to any of the work that SCO just filed, then SCO's filing for a copyright puts them in a difficult position.

    I have to admit the SCO news report is amazing. Basically with the investment of half hours work on the part of lawyer ($180), a days work for a filing clerk ($80), an envelope ($1), a express mail stamp ($3.70) and a $30.00 filing fee, they got a 20% boost in their stock. You gotta love the stock market.

    We should get the SEC to look at the insider trading for the stock, if there were any insider purchases before this phenomenal scam and any insider selling after the scam, maybe we could get their theiving arses hauled before the judge.

    1. Re:Awarded Copyright??? by pmz · · Score: 5, Funny

      Registering a copyright is pretty much like a cat pissing on a couch to say "this is mine"...

      This works well for humans, too, at least until someone calls the cops.

    2. Re:Awarded Copyright??? by thisgooroo · · Score: 2, Informative
      what's your problem? they got the copyright for Unix System V registered. it was anno8unced not so long ago that Novell had acknoeledged that this was part of the deal.

      their claims to rights over linux because of that is another story

    3. Re:Awarded Copyright??? by XO · · Score: 4, Insightful

      Hey, we know they own Unix System V. Duh.

      The whole point of filing for Copyright registration, is so that they can USE COPYRIGHT LAW. All it takes to copyright something is to attach a copyright notice to it.

      However, to USE the LAW to PROTECT your copyright, requires that you Register your Copyright with the Copyright Office.

      This is a REQUIRED step for them to use any Copyright laws in any way shape or form to their advantage.

      This is absolutely non-news. This is so non-news, it's pathetic. And there's 652 more comments I haven't read!

      All this is is someone saying "Hey, this is mine. I want a legal document to show it's mine, so that I can use the laws that are in place to enforce that it is, in fact, mine."

      Get a grip. Please?

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    4. Re:Awarded Copyright??? by tomhudson · · Score: 4, Interesting
      Novell did not say that they had asigned the copyright to SCO. Quite the contrary, nobody has seen the letter that SCO claims to have, that supposedly did this transfer. It's kind of strange that, if SCO actually were the copyright holder, they would have continued begging Novell to sell these rights, right up until the lawsuit started.

      The original agreement only transferred such rights as was required to allow SCO to sell copies of Unix as a licensee of Novell. In other words, that SCO could make changes, and those changes would belong to SCO, not Novell. As a licensee, SCO did not have to own the copyright to Unix, and this is why it was never transferred to SCO.

      It's the same as if I wrote a book, and I assign to you the rights to distribute the first edition of it. I've assigned to you a limited right to make copies, but this does NOT make you the copyright owner.

      I've got a feeling Novell knows this, and is biding it's time before giving SCO another nuking, or holding off so they can leverage something from someone (IBM?)

    5. Re:Awarded Copyright??? by Jeremy+Erwin · · Score: 1

      The legal ground for SCO v IBM is "breach of contract." If, all of a sudden SCO registers System V, that would be a sign that further lawsuits, this time under the copyright laws, are not only possible, but probable.

    6. Re:Awarded Copyright??? by YoJ · · Score: 2, Interesting
      The stock jump is not so unreasonable. Think of what happens when a company announces a new corporate philosophy (i.e. downsizing or something). All it takes is five minutes of a secretary's time to write the note, a stamp, etc., but these announcements can drastically affect stock prices.

      In this case, I think the market is reacting to the fact that the copyright registration provides more evidence that SCO is acting in good faith. If SCO were not convinced that it was right, it would be more hesitant to register the copyright since that would open them up to claims of acting in bad faith, i.e. registering something they knew wasn't theirs, which would hurt their legal chances for everything (even things not directly related to copyright, like patent and trademark claims).

    7. Re:Awarded Copyright??? by kallisti · · Score: 1
      It's the same as if I wrote a book, and I assign to you the rights to distribute the first edition of it. I've assigned to you a limited right to make copies, but this does NOT make you the copyright owner.


      What if you had a web page and gave a publisher rights to print an edition of the web page. Would you then be able to keep up your web page? Don't bet on it.

    8. Re:Awarded Copyright??? by seebs · · Score: 1

      Since when do you need to "register copyright" to use it? Not since Berne convention.

      --
      My blog: http://www.seebs.net/log/ --- My iPhone/iPad app: http://www.seebs.net/seebsfrac/
    9. Re:Awarded Copyright??? by tomhudson · · Score: 2, Informative
      What if you had a web page and gave a publisher rights to print an edition of the web page. Would you then be able to keep up your web page?
      Sure, you would. It's called first published rights. I grant you the right to publish the first edition. Later on, I can resell it to one or more other publishers, provided I haven't granted you an exclusive, perpetual right.

      This is why you can buy anthologies of sci-fi, for example. Asimov's or Analog, buys the first printing rights, and an anthologist buys the right to include it in their next anthology, and the author still maintains the right to sell it over and over. Ask any member of the writers' guild, or search back issues of Writers Digest (or read one of Asimov's biographies, where he talks about recycling his material).

    10. Re:Awarded Copyright??? by yintercept · · Score: 2, Informative

      The rules are that you own the copyright as the words flow from your pen (keyboard, or whatever). To defend your copyright, however, you have to file with the copyright office.

      Although you have a copyright, you cannot "use it" until you've filed with the copyright office.

    11. Re:Awarded Copyright??? by einhverfr · · Score: 1

      It is amazing that the news resulted in a 20% jump in the stock.

      20% of nothing is???

      Maybe one more person decided to by shares of SCO and that shifted the ballance.

      --

      LedgerSMB: Open source Accounting/ERP
    12. Re:Awarded Copyright??? by Anonymous Coward · · Score: 1, Funny

      With apologies to The Dude:

      Wait a minute! He thinks the couch pissers did this??!

    13. Re:Awarded Copyright??? by geekoid · · Score: 1

      "... requires that you Register your Copyright with the Copyright Office."

      not true, however having it registered usually makes it much more easier to protect yourself.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    14. Re:Awarded Copyright??? by tomhudson · · Score: 3, Informative
      SCO was not awarded copyright to Unix. They were awarded this: copyright to a 20-page printout of source code for modifications to Unix Sys5 release 4.1 ES. (Library of Congress # TX-5-705-356). Nothing to do with Linux, either.

      It's just another case of /. getting the headline wrong. Mind you, the original story on Yahoo also fucked up.

      What all this actually indicates is that their case doesn't hold much^H^H^Hany water, b/c they have to do more fud, smoke and mirrors.

    15. Re:Awarded Copyright??? by JacobD · · Score: 1

      Getting a grip would not be allowing a few disgruntled coders to sue for something that they did not create in the first place.

      The fact that they bought the rights to the Unix operating system doesn't give them the right to sue someone over what they "think" is infringement. I mean come on...they aren't even willing to turn over the information to IBM and the general public to help prove their case.

      This is basically akin to the original IRC coders come back into the scene and copyrighting the use of C/C++ code for a chat server and then suing the people who code Bahamut, Comstud, and Unreal for using the idea of chat networks without providing any type of proof that their code was used in the design.

      I don't need sign a NDA to determine that the so-called "proof" that SCO has is all bogus.

    16. Re:Awarded Copyright??? by sealawyer2003 · · Score: 1

      "not true, however having it registered usually makes it much more easier to protect yourself." US citizens and US based companies cannot sue in a US court without registering their copyrights first. Because of the Berne Convention, US courts cannot make foreigners jump through the same silly hoop. There are additional rights (statutory damages) that you cannot get if you don't register your copyrights either before the infringement or within 3 months of publication. This is still non news. The Copyright office generally does not scrutinize what gets submitted to it. They make sure all of the boxes on the forms are filled in and then grant the registration. It's not anything like a patent examination.

    17. Re:Awarded Copyright??? by cryptonomiciosis · · Score: 2, Interesting
      I went through the text of the SCO press release and despite all the legal jargon and promises not to hurt any body or entity already using Linux (if you pay) there was a line or two I found kind of interesting.
      "While using pirated software is copyright infringement, our first choice in helping Linux customers is to give them an option that will not disrupt their IT infrastructures. We intend to provide them with choices to help them run Linux in a legal and fully-paid for way."
      This almost seems like that time not too long ago when Congress tried to give themselves a retroactive raise.

      It's like saying "We know that you started using this product before we got bent about it, but we want the money we're charging now for the product you started using several years ago." Apparently SCO didn't take issue with the use of Linux several years ago, but they see the bank it gets and they want to get their hands on a cut of that check. Frankly I think the copyright, as legally weak as it is, should only be used proactively and not retroactively. It's hard to say that 3 years ago Company X broke the law when the law wasn't codified. Of course I am no legal expert, and I guess somehow that is saying you were ignorant of the law (existant or not) which is inadmissable.

      I have kind of kept an eye on this story, and I know this isn't the most informed reply, but I found that fact interesting.

    18. Re:Awarded Copyright??? by Anonymous Coward · · Score: 0

      The Copyright office generally does not scrutinize what gets submitted to it. They make sure all of the boxes on the forms are filled in and then grant the registration. It's not anything like a patent examination.

      Actually, looking at some of the patents that have been awarded lately, I beg to differ with that statement

    19. Re:Awarded Copyright??? by Anonymous Coward · · Score: 0

      The fact that they registered something at the copyright office is non-news, indeed. But the fact that the arrogant pieces of shit are talking about offering a license to use Linux... Use Linux, for the love of Pete! That is very much news, and the reason behind the thousand-or-so angry posts.

    20. Re:Awarded Copyright??? by Angry+Pixie · · Score: 1

      Well, Novell would certainly benefit from watching the UNIX and Linux communities cannibalize each other. It would leave behind a weak and uncertain UNIX/Linux market, giving Novell a chance to push NetWare again with only Windows as competition.

    21. Re:Awarded Copyright??? by rabbit994 · · Score: 0

      Novell also just released a Java groupwise (their Email software) client for both Mac OX and Linux (and anything else that can run Java 1.4). The also released a whole suite for linux that allows you to use a crap load of their services with Linux. Novell is betting big on Linux right now. I doubt they want to see it die. http://www.novell.com/linux/

    22. Re:Awarded Copyright??? by tomhudson · · Score: 2, Insightful
      I don't think they want Linux to die - quite the contrary, they've made it quite clear they're betting the farm on it.

      I just think that they're going to wait for the most opportune time to do the most damage - sort of like SCO, except without the fud.

    23. Re:Awarded Copyright??? by k8er · · Score: 1
      Novell Statement on SCO Contract Amendment
      PROVO, Utah -- June 6, 2003 -- In a May 28th letter to SCO, Novell challenged SCO's claims to UNIX patent and copyright ownership and demanded that SCO substantiate its allegations that Linux infringes SCO's intellectual property rights. Amendment #2 to the 1995 SCO-Novell Asset Purchase Agreement was sent to Novell last night by SCO. To Novell's knowledge, this amendment is not present in Novell's files. The amendment appears to support SCO's claim that ownership of certain copyrights for UNIX did transfer to SCO in 1996. The amendment does not address ownership of patents, however, which clearly remain with Novell. Novell reiterates its request to SCO to address the fundamental issue Novell raised in its May 28 letter: SCO's still unsubstantiated claims against the Linux community.


      That sounds less promising than their first press release, but it sounds like there are still some unanswered questions.
    24. Re:Awarded Copyright??? by Anonymous Coward · · Score: 0

      A chimp throwing feces would be awarded a patent, provided someone paid the necessary fees.

    25. Re:Awarded Copyright??? by arkanes · · Score: 1
      Did you read his link? What you say can't happen is exactly what did.

      In the linked article, he says that the publisher said that the included contract was "standard boilerplate". If that is true, then the (extremely draconian) language that grants the copyright to the publisher, in any and all media, known now to be discovered (and on, and on... read it yourself) is something that people should be made aware of.

    26. Re:Awarded Copyright??? by jeffphil · · Score: 1

      I believe you can provide only partial source, and in some cases only binary (i.e. a working install CD) to do to obtain a "registered" copyright. As long as your copyright notice is visible and you can demonstrate the art with what you submit.

      By submitting to the copyright office, you get guaranteed protection if you win a copyright violation lawsuit. This guarantees you a certain dollar amount (I think $25K) per violation. Which in the case of the RIAA they call every download of their music on a P2P network a violation so it adds up quick.

      So in essense, obtaining a registered copyright does not guarantee that you will ever win a case, but if you do win then you get a lot more money.

      I could submit the entire Linux kernel source to have it registered at the Copyright office, and they do nothing to check it's originality or authenticity. But if I ever tried to take any kernel developers to court, I would never win the case -- and I could probably be counter-sued for fraud in removing the copyright notice.

      Lawyers, please correct me if I'm wrong here.

    27. Re:Awarded Copyright??? by arkanes · · Score: 2, Interesting

      The "story" on Yahoo is just a reprint of the SCO press release (note the "source" line at the bottom). I think it rather lacks professional ethics to display this as a regular article, but heck, what do I know about buisness.

    28. Re:Awarded Copyright??? by LinuxInDallas · · Score: 1

      It would be amazing if their stock was at $100, since that would mean a $20 hike. But since their stock was only about $10 a share, it's not a big deal.

    29. Re:Awarded Copyright??? by VertigoAce · · Score: 1

      Are you sure? Twenty pages happens to be exactly the amount of source you must submit if you have a program longer than 50 pages that contains trade secrets. You must submit 10 pages from the beginning and 10 from the end (without any portion blacked out). There are other options if those twenty pages would contain trade secrets.

      Read this for more information on the requirements.

    30. Re:Awarded Copyright??? by yintercept · · Score: 1
      It would be amazing if their stock was at $100, since that would mean a $20 hike. But since their stock was only about $10 a share, it's not a big deal.
      The share price is pretty much meaningless. A 20% hike in a $10.00 stock gives as much money to the stock manipulators as a 20% increase in a $100 stock.

      The actual share price is really just arbitrary. The share price is the total market capitalization of a stock divided by the number of shares on the open market.

      The market capitalization is pretty much determined by how well investors think a particular company will perform in the long run.

      So, lets say you had a stable company in a stable market returning $100M a year in profit. The market might give the company a 1:10 PE ratio...which would be a market capitalization of $1B.

      If there were 100M shares on the market, the price of the shares would be $10 a piece. If there were 10M shares on the market, the price would be $100 per share.

      Some companies like to keep their share price below $100. If their share price goes above $100, they will go through a stock split. The stock split simply gives all investors two shares for their one share. Investors then have twice as many shares as they did before.

      SCO Group seems to have a market capitalization of 173M dollars. That sounds like a lot of money to me.
    31. Re:Awarded Copyright??? by Eunuchswear · · Score: 1

      20% of $ 173,839,320 is $ 34,767,864

      Just one person? I doubt it.

      --
      Watch this Heartland Institute video
    32. Re:Awarded Copyright??? by mpe · · Score: 1

      It is amazing that the news resulted in a 20% jump in the stock. If I am not mistaken, the Copyright office awards a copyright registration just about anytime someone sends them an envelope with $30 and an attached piece of paper.

      This more a commont on the way stockmarket valuations can be utter fantasy.

    33. Re:Awarded Copyright??? by tomhudson · · Score: 2, Informative
      As I posted elsewhere, you have to submit the following:
      1. Title page
      2. First 25 pages of code
      3. Last 25 pages of code
      You can, of course submit more... but you can't submit less, unless your whole thing is smaller - which in this case it is, at only 20 pages total. It's not a copyright on Unix Sys5, but on some mods they made.

      The whole thing is similar to the jokes we see here all the time about copyrighting "Hello, world!". If you look in your manuals, you'll see that they are all copyrighted, and many of them contain the source to "Hello, world!". So, in one sense, it's copyrighted.

      Does that mean you can't use it? Of course not :-) Which is why I find this whole SCO thing stupid, on SCO's part :-)

    34. Re:Awarded Copyright??? by tomhudson · · Score: 1
      Their own filing says:

      UNIX system V, release 4.1ES.

      TX-5-705-356 - Claim limit: new matter, revisions

      So, it's not a copyright on UNIX Sys5, but on some mods to same.

    35. Re:Awarded Copyright??? by tomhudson · · Score: 1
      Just goes to show that you have to read the contract. Sorry, but anyone stupid enough to sign such a contract deserves to get goatse.cx'ed.

      When someone says "Its' a standard contract" alarm bells should be ringing in your head. Tell them that, if it's a standard contract, then they should have no objection to your taking a copy to be reviewed by your legal advisor first. When they balk, you KNOW that they're trying to fuck you.

      Remember, a good deal is a state of mind. It has to be good for both parties. And, if it's good for both parties today, then it will still be good for both parties tomorrow, so what's the rush?

      Anyone who says "It's gotta be signed today." is right - for them. Not for you. If they need it signed right away, it's because they're getting something that they value. Take your time, read the contract. Since you know (by their time pressure) that they want it, you can negociate.

      Or just pull out your own "standard contract". .

    36. Re:Awarded Copyright??? by arkanes · · Score: 1
      The author of the story does make that point, and of course he is correct (as are you). The counter argument is that we shouldn't have an adversarial relationship like this - particularly in this case, where, in theory, it's a mutually beneficial partnership.

      Also, if that IS a standard contract, then there's something seriously wrong with the publishing industry (more than I knew about already, that is).

    37. Re:Awarded Copyright??? by tomhudson · · Score: 1
      Which is why it's good to have an agent. Most pubished authors have the highest praise for their agents, and say that the agent more than earns his cut, just in increased $$$ during negociations :-)

      It's not a "standard contract". If you want to see a standard contract, go look at what the Writers Guild recommends. Or you can get an agent who agrees with the Guilds' policies towards writers

  218. countersue? by Anonymous Coward · · Score: 0

    Is someone going to countersue for the damage this is doing to Linux?

  219. Change your TCP/IP fingerprints guys by hedley · · Score: 1

    Especially those of you with static IP's. Try to get your fingerprint to look like Win2k server. I was going to say SCO OpenServer but there are probably so few licenses that it would be too easy for them to nail you :)

    If they get creative and start sweeping the IP space they could harvest many boxes. Watch out.

    Hedley

    1. Re:Change your TCP/IP fingerprints guys by CyberGarp · · Score: 1

      How about I send McBride a letter that says: "Bring it on!"

      How about every Linux nut in the world, send McBride a letter that says: "Bring it on!"

      Screw hiding my head in the sand. I think Linux is legit and McBride doesn't have a leg to stand on. Stand together and proud. Hiding only serves as an implicit admission of guilt.

      --

      I used to wonder what was so holy about a silent night, now I have a child.
    2. Re:Change your TCP/IP fingerprints guys by hedley · · Score: 1

      OK. I respect that. Just make sure you have the time to defend yourself in the unlikely event they id you. I am kind of busy and I don't have a lot of unspoken for time to get involved with lawyers who are fishing for cash.

    3. Re:Change your TCP/IP fingerprints guys by Anonymous Coward · · Score: 1, Funny

      I'm unemployed, have so little personal property that it'd probably raise $300 if you sold it and the record length of a court case in the UK is 4 years and that just begs for breaking. Nothing to lose and a grudge against litigous, meatheaded corporations.

      Let's face it, even if they won I'd lose nothing worth worrying about and they'd have to pay their legal bills 'cos I'd declare myself bankrupt and earn fuck all until it times out. If theirs a recession, there'll be even more people with time on their hands and a pissed off attitude

    4. Re:Change your TCP/IP fingerprints guys by CyberGarp · · Score: 1

      But consider, if McBride had to pursue a lawsuit against everyone using Linux, and we stood united against him. I think there's a lot more of use than him.

      As long as they can single you out, they can pick you off one by one...

      I think it would be even better if the kernel developers started a class actions against SCO. Shooting back is an even better strategy.

      --

      I used to wonder what was so holy about a silent night, now I have a child.
  220. You are an idiot by Anonymous Coward · · Score: 1, Informative

    You do realize that the bulk of SCO's stockholders are professional money managers, right?

    The popularity of the day trader occupation faded out about, oh, two years ago.

    If as many people as possible go onto stock boards, and post their negative feelings about SCO, and their own speculations as to what the outcome of the battle with IBM will be, Buyers will begin to flee from the stock.

    Do you really think that will work?

    T. Carl MoneyManager: Hm, the expected value of SCO's stock, given current P/E ratios, recent developments, and our analysts' recommendations marks SCO stock as a Buy/Hold. However, LUNIXLOVER111@HOTMAIL.COM claimed "Haha, $CO suxxx0rs, Linux owns!!" on a free market message board. OK, SELL it ALL!!! short it, even!!

    It would be also well to do if you indicate that your company will NEVER purchase, license, or other wise enter into a business agreement with SCO, as you feel that their products (specifically name them) are of low quality and should not be used in production environments.


    Right. I believe you.

  221. RICO Act by Esion+Modnar · · Score: 1
    You know, Racketeering something-something-something. Wouldn't SCO be getting close to crossing a line here?

    More than one person has commented how this whole SCO-licensing-Linux thing looks like a thinly veiled protection racket-- as in racketeering.

    I'd actually cheer Ashcroft if he had the whole SCO executive team perp-walked to a paddy wagon.

    --

    They say the first thing to go is your penis. Well, it's either that or your brain. I forget which...
    1. Re:RICO Act by RevSmiley · · Score: 1

      The art of Law and Lawyering is all about legalized theft. It's not about justice.

      --
      As you can see I don't care about my karma.
  222. Another option by BorgDrone · · Score: 1

    Another option:
    IBM buys SCO, fires everyone responsible for this.

    1. Re:Another option by BlackHawk-666 · · Score: 1

      All the corporate criminals will get huge settlements for redundancy (think multimillion dollar payouts) and the sysadmins and programmer (if they even have 1) and secretarys and stuff will get fired without pay. Not the best option in town.

      --
      All those moments will be lost in time, like tears in rain.
    2. Re:Another option by thogard · · Score: 1

      IBM will counter with their big bag of patents. There is no way SCO isn't violating hundreds of them if not thousnads. That is why IBM maintains an expensive part of the company (that is seen as giving IBM no real income to the big investments) so IBM will nail SCO with that, and show its investors how much that patent portfilo is worth. SCO has no choice in the matter anymore, they will get squased like the bug that they are.

    3. Re:Another option by e5z8652 · · Score: 1

      Hmm. OK, then don't fire them.

      "Ah yes, thank you for the coffee Darl. Next time, please remember to put more cream in it, OK? You're getting much better at your new job.

      You know, that offer of early retirement with no pension is still on the table, if you want to talk about it after serving lunch."

      --

      null sig

  223. Confusing copyright with patents by dh003i · · Score: 1

    The thing at issue here is copyright. Derivatives don't apply. Only patents cover the actually method; copyrights only cover expressions.

    Unless SCO has a patent on these things -- which they don't -- they can't prohibit others from using similar methods to achieve them. If they have a patent on an SMP-method, they can prohibit others from using the same method they use; they cannot, however, prevent people from using other SMP-methods.

    If they simply have a copyright, then all that needs to be done is that the code needs to be removed and replaced. The act of re-coding it will most likely result in a different method anyways, safely putting it beyond patent-actionability.

    The one-click lawsuit you mention between Amazon and Barnes and Noble is a patent lawsuit, not a copyright lawsuit.

  224. Re:FSF should sue on behalf of the developers then by Anonymous Coward · · Score: 0

    FSF does not have standing.

    Unlike the GNU organization, Linus (& Co.) don't tend to assign copyrights to any central authority. Without those rights, the FSF cannot sue. Only the actual holder(s) of the copyright have that right.

    It is a problem. To bring such a suit requres good standing, and a boatload of money. Few, very few, contributors have that pesky money bit covered. Remember, this is Federal level stuff in the US we're talking about. This is the land where justice doesn't exist unless it's bought and paid for.

    Further, Linus has made arbitrary "exceptions" to the GPL (like, modules). The situation can unfold where some contributors may want to sue, while others do not. That act by Linus may have created an environment where a clear "agreement" on the license terms may not legally exist. The court may hold that the "most credible" understanding agreement is that held by the majority of contributors. So unless a majority sue, the case will be lost.

    Maybe Linus can affort to file, maybe a few working for Red Hat, et. al. but to think a majority of contributors can afford it is unlikely.

    Maybe a class action, but the GPL is about "freedom" -- there are no easily quantified monitary damaages to the contributors. One would have to fall back to the criminal penalty in copyright law (About $150K). Few lawyers would be able to conduct a full fledged class action, let alone a copyright, suit for that sum.

  225. I didn't taint anything I'm not paying by mcmcaughan · · Score: 1

    If the end user was unaware of and took no part in the release or implementation of the SCO code is there a legal basis for SCO to come after the end user? That is as ridiculous as Ford motor company selling me a car with a Motorola chip in it that stole code from Philips. Instead of Philips taking action against Ford they just skip that step and ask each car owner to pay 1,500 to give us an opportunity "to make it right" and avoid legal hassles. Screw 'em, let them go after IBM, I didn't do anything and you cannot hold be accountable for something you haven't even proven yourself!

  226. Re:The GNU/GPL is probably unenforceable in this c by acroyear · · Score: 3, Interesting

    Actually, it depends on the extent of the (highly unlikely) victory. If they only win on the specific "lines of code" that IBM took, then IBM pays a negligable amount (by IBM standards) and IBM rewrites the code (or has someone else do it). If IBM settles out of court, nothing changes, so a new court case would have to come up to prove McBride's idiocy.

    If they win the big one, the "linux is a derivative" claim (unlikely given the precedent set in the BSD case), then they would be within their rights to overrule Linus and change the license to the 2.4 kernel. The GPL would be irrelevant because any distribution of 2.4 under the GPL was already established as an illegal distribution. Copyright holders can (and do; look at XP vs the old win98 system) change the licenses for products.

    But IBM's not going to lose this one.

    --
    "But remember, most lynch mobs aren't this nice." (H.Simpson)
    -- Joe
  227. All exact points... by dpilot · · Score: 1

    SCO is going right at the heart of the GPL.

    As others have pointed out, SCO has been violating the GPL by having kept Linux on their ftp site after announcing the copyright issues. Maybe this isn't an accident, maybe it isn't negligence.

    Maybe SCO is trying to get the GPL invalidated in court.

    Of course how you invalidate the GPL without the repercussions affecting other aspects of software copyright might well be another issue. There might be a bunch of Unintended Consequences cropping up, if SCO were to actually win.

    In another sense, the true utility of the GPL is that it grants 'fix it yourself' ability. SCO's offered license removes that.

    So in another sense, the SCO suit strikes at the heart of the GPL.

    This may well be a much more precise strike than it seems. Given than it's really a vehement anti-GPL campaign, and we know *who* hates the GPL more than anyone, it's not hard to imagine that there's a puppeteer pulling the strings on this.

    --
    The living have better things to do than to continue hating the dead.
  228. I have pictures of your wife naked. by ivan256 · · Score: 2, Insightful

    If you were going to be blackmailed, wouldn't you want to see proof that the person blackmailing you could do what they say they might do before you start giving them money?

    You would have to be a fool to give SCO money before they show proof that they own what you're using.

    On the other hand, I hope SCO updates us regularly with press releases of who pays up. I want to know which corporate execs I can extort money out of by claiming to have pictures of them in compromising situations without actually needing to show them any pictures....

    1. Re:I have pictures of your wife naked. by pair-a-noyd · · Score: 2, Funny

      I have pictures of your wife naked.

      I don't care. You can keep them and her too.
      That's why I divorced the bitch you dummy...

      Sorry, no $$ for you today...

  229. SCO may be within their rights by RevMike · · Score: 1
    I want to address a few issues...

    First, the fact that SCO still has a Linux dist. on their FTP server is not evidence of anything. IIRC SCO is claiming that IBM contributed SCO owned code recently (yes, I know that SCO is making noise about owning everything ever written, but that is PR not legal filings). As long as the versions of Linux on SCO's FTP server pre-date the potentually offending contributions, SCO has not ceded their proprietary rights to the GPL.

    For instance, if SCO is still distributing 2.2.17 on their FTP server, we can assume that the infringing code came later. The fact that later versions may have at one time been available from SCO is not neccessarily an indication that those versions are clean, since the licenser can't accidentally license something, particularly if the licenser makes moves to rectiufy the situation afterwards.

    Second, the GPL specifies that proprietary and GPL code cannot be mixed in a distribution. It does not prevent mixing by the end user. This is how some video card manufacturers publish binary only drivers for linking by the end user.

    Understanding that point, SCO is free to license their SysV code to linux users. Linux users are free to use it. Linux Distribution Puiblishers, both for profit and non-profit, are the parties in violation of the GPL. The end users are in no way bound by the GPL, they are just in violation of SCO's copyright.

    If IBM really did contribute SCO code, SCO does have legitimate remedies against IBM, distributors, and users. Users can mitigate their risk by rewinding their systems back to the latest kernel version still available from SCO. That version is free from SCO IP issues because, since SCO themselves distributed it, it is covered by the GPL.

    It is unlikely that the distributors are in too much trouble, since SCO has not revealed the offending code, they have not been in a position to make a good faith effort to rectify the infringement. This would likely be taken into account in a "damages" phase of a future SCO v. linux distributors lawsuit (which would follow a SCO win over IBM). It is likely that, upon being sued, the attornies for the linux distributors would immediately stipulate that they did indeed distribute SCO code, but that they relied on the code contributor that they had license to do so. Then they would implead IBM, who at this point already was found guilty of violating SCO's copyrights.

    IBM is potentially in bad shape, legally and in damages. Of course, this is all assuming that their is merit to SCO's claim that their code was placed in Linux.

    1. Re:SCO may be within their rights by cyphergirl · · Score: 1

      So, if they are distributing it, it's probably the last version that was OK. Has anyone done a diff of the version on SCO's ftp site and the following version? (And then the following, and the following.....)

      That might reveal which code they are laying claim to.

      --
      --Insert catchy .sig line here--
    2. Re:SCO may be within their rights by roystgnr · · Score: 1

      For instance, if SCO is still distributing 2.2.17 on their FTP server, we can assume that the infringing code came later. The fact that later versions may have at one time been available from SCO is not neccessarily an indication that those versions are clean, since the licenser can't accidentally license something, particularly if the licenser makes moves to rectiufy the situation afterwards.

      I downloaded 2.4.13 from ftp.caldera.com this morning. Some of the included patch files bear dates of May 3, months after SCO claims to have discovered their own code in the Linux kernel (which is also included, as is the GPL therein).

      Perhaps you're right, and SCO has discovered a wonderful loophole in copyright law which allows them to knowingly distribute their code under a license which they then get to "take back" later, but even in that case (which assumes that their unproven, self-contradictory, and deliberately unsubstantiated claims about owning code in the Linux kernel are true) that just means they're currently knowingly violating the copyright of everyone else who contributed to the kernel and are at risk of being sued by any of the 400 or so other contributors.

    3. Re:SCO may be within their rights by Platinum+Dragon · · Score: 1

      You can get patches for each new version of 2.4 from kernel.org and its mirrors. If SCO thinks it's safe to distribute 2.4.13 due to a lack of infringing code, then digging through the subsequent patches should reveal what code SCO thinks it owns[0].

      However, I find it far more likely that SCO's lawyers are overrated and don't understand the implications of the GPL and GPL violations. I don't think SCO's lawyers understand that, by claiming certain pieces of code are not under GPL, that the entire kernel they are distributing here now falls under standard copyright law. Since SCO does not have copyright on the entire kernel, this distribution is illegal and itself infringing until SCO obtains permission from every other person who has copyrighted code in the kernel.[1]

      [0] This seems to be a moving target, depending on who is speaking and what day it is, my opinion that the whole thing is a bullpuckey stock scam notwithstanding.

      [1] The amusing thing is, timestamps on SCO's ftp server indicate there was a serious attempt to wipe out all signs of 2.4.13 kernel code and binaries on May 16, 2003. Despite this, you can still find several copies of 2.4.13 in the updates directory. I can't believe SCO's staff would fail to think of this, and I'm stunned that the legal teams haven't caught wind of this and demanded that these copies also be wiped out.

      --

      Someday, you're going to die. Get over it.
  230. one bullet for dictator by JDizzy · · Score: 1

    When President Bush made the stament that one bullet could solve the problem in the midle east, I suspect its ok for me to say that one fire-bomb at the SCO's world headquarters would solve this issue. At any rate, its only a matter of time before the SCO sources are compared to the Linux sources by Computer Science prfessors, and other qualified persons. At that time it will be a matter of court record (public or sealled), and ultimatly the areas of sources will be altered with fresh code, or proved to be of the type that is algorythmically common to code design. Comments in code are not normally admisable, as they were not in the Berkley case in 94. anyways, once the code is clean, as was the way in the berkley case, SCO will have nothing to license, and their UnixWare will still suck.

    --
    It isn't a lie if you belive it.
  231. Will someone send me a free copy? by trance9 · · Score: 1


    I missed downloading the linux kernel from SCO's website, which they were distributing via the GPL. Can someone who downloaded a copy of the kernel from SCO under the GPL please forward me a copy?

    Mail me at "req at semiotek.com" with details if you would be so kind.

    It is my belief that since SCO at one point distributed the kernel under the GPL that anyone who downloaded it is legally entitled to use it under the GPL, and therefore legally entitled to send me (or anyone else) a copy.

    1. Re:Will someone send me a free copy? by Anonymous Coward · · Score: 3, Funny

      req@semiotek.com

    2. Re:Will someone send me a free copy? by commodoresloat · · Score: 1

      It's still on their ftp site; look earlier in this discussion, someone posted the link above.

    3. Re:Will someone send me a free copy? by XO · · Score: 3, Interesting

      At home, I have the "Source Code CD" for "Open Linux 2.2" ... from Caldera... :-)

      hmm.

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    4. Re:Will someone send me a free copy? by Pharmboy · · Score: 1

      If you read the article, it points to 2.4+ kernels, saying that 2.2 kernels could handle 2 to 4 cpus, but 2.4 can scale to 32+ cpus. I am assuming that this means SCO thinks the illegal code is NOT in 2.2 and only in 2.4 kernels anyway. IF this is the case, then the fact that they released a 2.2 kernel really doesn't apply.

      --
      Tequila: It's not just for breakfast anymore!
    5. Re:Will someone send me a free copy? by XO · · Score: 1

      Hmm. Well, it's OpenLinux 2.2. I have no idea what kernel version it actually contains, as I don't think I've ever actually used it for anything besides a rescue CD, and now I can't even find the bootable CD from the package.

      I really have to wonder when it actually came to pass that SCO's code came to have SMP support - and is it worth anything? I know we've got SCO Xenix floating around here, and it certainly doesn't SEEM to indicate any form of SMP capability. and it is being used on an SMP box... *shrug*

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    6. Re:Will someone send me a free copy? by Pharmboy · · Score: 1

      I really have to wonder when it actually came to pass that SCO's code came to have SMP support - and is it worth anything?

      It appears it's worth $1 billion dollars, in SCO's eyes anyway. But the main claim is support for more than 4 cpus, which was marginal before 2.4. I went to SCO's site and read all their 'evidence', which is admitedly, quite thin.

      With IBM's new PPC 970 Quad 2Ghz servers scheduled for under $3500, I get the feeling they will have the extra bucks needed to buy out SCO. The more I read, the more I believe that is going to be the end result. Personally, I would love to see IBM open the source for all SCO's theoretical IP. I have several older IBM servers, and would be glad to repay them with future loyalty, especially at $3500 for quad box.

      Oh, and if memory serves me right, Xenix was for x86 (bought out or licensed later by MS I believe), while most SMP boxes running *nix were MIPS or Alphas. I have an old copy of SCO for 386 that doesn't say anything about SMP either.

      --
      Tequila: It's not just for breakfast anymore!
    7. Re:Will someone send me a free copy? by Lobo93 · · Score: 1

      And I have a T-shirt with the text/logo "open LINUX" on the front and "Linux for Business" on the back. A tiny "Caldera"-logo can be seen on the front side.

      Now, wtf am I going to do with it?

      These are some of my options:
      1) Leave it to rot.
      2) Submit to legal process as, hehe, "exhibit A".
      3) Burn it using home-made napalm, while dementedly screaming the lyrics of "Angel of Death" by Slayer...

      --
      "The only clear view is from atop the mountain of our dead selves." - Peter Carroll
    8. Re:Will someone send me a free copy? by trance9 · · Score: 1


      Hey. I switched to the at to avoid getting spam, guess you didn't realize that otherwise you wouldn't have been so rude.

  232. Wrong... It would have to be a 2.2 release by cnelzie · · Score: 1

    The 2.3 kernel was the development kernel for 2.4. Therefor most everything within that kernel would be 'tainted' by the technologies and code that SCO claims is a component of the 2.4.x series of the Linux Kernel.

    In order to have a "Free" kernel. If the SCO case is determined to be a good case... The only way to move forward would be to take a 2.2.x series kernel without any "back-ported" patches and components from the later 2.3 and 2.4 series kernels and build on that.

    This would put Linux back several years in development and could even make Linus and several of the current kernel development people unable to add to the kernel or maintain this 'new' branch since they would be 'tainted' by the SCO code.

    This wouldn't exactly destroy Linux, but it could take nearly 5 years to bring the 'new' branch up to where the current 2.4.x release is, in terms of useability, capability and scalability.

    --
    If you ignore the other uses of a tool, does that make the tool less useful, or you less useful?
  233. Re:There can be no doubt about it - SCO == stupid by tomhudson · · Score: 2, Insightful
    As a followup - they were only awarded a registration on some modifications to Unix System V RElease 4.1 ES. The sum and total was a 20-page printout. So much for the "millions of lines of code copied".
    1. Registration Number: TX-5-705-356

    Title: UNIX system V, release 4.1ES.
    Description: Computer program.
    Note: Printout (20 p.) only deposited.
    Claimant: the SCO Group, Inc.
    Created: 1991
    Published: 27Jun91
    Registered: 30Jun03
    Author on © Application: UNIX System Laboratories, Inc., employer for hire.
    Previous Related Version: Prev. reg. 1992, TXu 510-028, et al.
    Claim Limit: NEW MATTER: revisions.
    So, what they are claiming is revisions to SysV release 4.1ES, nothing more.

    Here's the referenced work:

    TXu-510-028 (COHM)
    Title: UNIX.
    Edition: 5th ed.
    Note: Computer program; with programmer's manual by K. Thompson, D. M. Ritchie.
    Claimant: Unix System Laboratories, Inc.
    Created: 1973
    Registered: 25Mar92
    Title on © Application: UNIX operating system.
    Author on © Application: American Telephone & Telegraph Company (employer for hire)
    Miscellaneous: C.O. corres.
    So, again, unless they can be shown to also be the current copyright owner of the above, they're SOL :-) The have not been granted a copyright for SysV, unlike what the article headline says.
  234. SEC by Anonymous Coward · · Score: 0

    You mean SEC, not FTC, since those are the guys dealing with stocks and public companies.

  235. Hello, is anyone paying attention? by Rohan427 · · Score: 2, Informative
    When I worked at Akamai (until Dec. 2001) we had some 11,000-12,000 servers on the Internet serviing content. Though I never counted or saw a count, I'd estimate 90% of those were Linux. I personally had a hand in upgrading many to the latest RH kernel - a 2.4.x kernel.

    Akamai served content for companies/sites like CNN.com, Microsoft, the Federal Government - to include the Whitehouse, FBI, etc., and many, many others, and as many of you may have noticed, often when you retrive web content, you'll see a URL pop up in the browser status bar saying xxx.akamai.com or some such.

    Now, let's do a little math. Since I left Akamai, I understand they've increased the number of servers to greater than 12,000. So, we'll be conservative and estimate 80% of 12,000 are Linux, giving 9,600 Linux servers. Remember, we're talking servers and not desktops - they have many more systems internally that are Linux (I had 3 in my office while I was there, and many in my group had at least two).

    9,600 * $1,500 =
    • $14,400,000
    Now add the desktop systems to that. I don't see Akamai paying out that kind of cash, especially given their stock prices since 2001, and since they have contributed to kernel development themselves.

    Akamai is just one company that relies upon Linux for their business. There are many others (despite what some reports would lead people to believe), and I venture that if there weren't that many, SCO would not be pulling this crap. Akamai also uses IBM Linux servers for (possibly) one of the largest distributed database systems in the world (unless they shut it down - we were building it while I was there and there was a big press release). I would imagine that this will/has pissed off IBM, Akamai, and others and SCO has just not only shot themselves in the foot, but shoved the shotgun barrel into their collective mouths.

    I myself will never, every pay the extortionists at SCO a penny for my use of Linus and others (including my own) hard work in the Linux kernel.

    However, let me finish by saying that I'm quite sure IBM, Akamai, and others are quite aware of what the GPL says and how to interpret it in a court of law. IBM has a crack law team, and Akamai's are no slouches either. IBM has money to spare on legal fees, do you think SCO has money to spare for even a new company car? Even if Linux has SCO copyrighted code in it - and many Linux developers have stated it does not - they did release that code under the GPL. Therefore, it seems to me the question - if SCO copyrighted code is in Linux - is how the GPL applies. From reading the GPL myself several times (since I too have developed GPL code for various projects), I'd have to refer back to a previous paragraph and a sentence therein about SCO and a shotgun barrel.

    PGA
    (Spell checker?! What's that?)
    1. Re:Hello, is anyone paying attention? by jo42 · · Score: 1

      PHB: How quickly could we upgrade all these servers to FreeBSD?

      PFY: Agh! Blurf! Bleempf! Two weeks! Two weeks!

  236. "We would prefer licensing to litigation," McBride by Anonymous Coward · · Score: 0

    Here is a link to the Wired News article on this story. I really like this quote...'"We would prefer licensing to litigation," McBride added.'
    Yeah, I bet you do...
    http://www.wired.com/news/business/0,1367,5 9701,00 .html

  237. Check Microsoft Source Code by Anonymous Coward · · Score: 0

    Didn't M$ recently give some source code to China? I bet there is some interesting code in there!

    Testes

  238. You are correct. by LibertineR · · Score: 1

    Sorry, thats right, I made a mistake. Thanks.

  239. Dag gone it.... by Anonymous Coward · · Score: 0

    Will someone BUY these buttwads! IBM R U LISTENING!

  240. Please. by SonicRED · · Score: 1

    Can we get sco.slashdot.org then post on the main page only when something significant happens - like the release of the infringing code. I'd read The Godfather if I wanted to hear about crap like this.

  241. Better idea: Short Sell Now by cliffmeece · · Score: 1

    Not only will you take advantage of the inevitable profit taking, the large slashdo community will likely help drive the stock down.
    More money for us, less for SCO.

  242. I searched sco.com for GPL and here's what I found by nxs212 · · Score: 1

    "What did SCO announce on January 22, 2003? ...intellectual property that we sell. Many Linux environments have been using SCO's UNIX shared libraries because they are a superior product and they make these environments more productive. But until today, there were two ways for users to get the shared libraries:

    1. Buy a SCO UNIX or Linux product that included the shared libraries as part of the bundled offering. This is legal.
    2. Copy the shared libraries from a disk or through the Internet. In this case someone has unbundled the shared libraries from the SCO offering and opened them up for copying. This is illegal. It is this behavior that we will stop through the creation of SCOsource and today's announcement.
    SCO's UNIX shared libraries are not open source code available for free use. "

    Am I an idiot or are THEY trying to technobabble their way into court and pull wool over everyone's eyes? (the jury) As far as I know Linux is just a kernel and NOTHING more. You can install additional software on top of it, and even create a distribution. Few lines before they start threating everyone, they say they "gave" their shared libraries (for $150 per cpu) and now they claim people stole them. Personally, I have never seen nor used their libraries so I don't see how this or any of their BS applies to me or 99.99% of other linux + GPL software users out there.
    here's link to my search
    http://www.sco.com/scosource/Final_SCOsour ce_QandA .html
    Let's call their 800 number and demand some answers.

  243. Re:The GNU/GPL is probably unenforceable in this c by jedidiah · · Score: 2, Interesting

    They only have 2 options:

    a) They are violating the license of some code that is not registered at the US Copyright Office. Their legal liability is minimal in a civil court of law.

    b) They are violating criminal provisions in the US Copyright Statute. Their legal liability is severe and outweighs anything they might gain from selling Linux licenses.

    This isn't like Monsanto dumping toxic waste. SCO is far too small and the profit they stand to make on their venture is miniscuele.

    --
    A Pirate and a Puritan look the same on a balance sheet.
  244. A bit of irony by felix9x · · Score: 1

    FUD /fuhd/ n. Defined by Gene Amdahl after he left IBM to found his own company: "FUD is the fear, uncertainty, and doubt that IBM sales people instill in the minds of potential customers who might be considering [Amdahl] products." The idea, of course, was to persuade them to go with safe IBM gear rather than with competitors' equipment. This implicit coercion was traditionally accomplished by promising that Good Things would happen to people who stuck with IBM, but Dark Shadows loomed over the future of competitors' equipment or software. See IBM. After 1990 the term FUD was associated increasingly frequently with Microsoft, and has become generalized to refer to any kind of disinformation used as a competitive weapon.

    source: www.dictionary.com
    for complte source inforamtion see:
    http://dictionary.reference.com/search?q=FUD

  245. Insiders Bought stock by linuxislandsucks · · Score: 1

    The only change in share price was due to employees and execs buying the stock ..not due to any outsiders trusting SCO Group:

    http://biz.yahoo.com/t/s/scox.html

    --
    Don't Tread on OpenSource
  246. I'm gonna be nerdy. by dmaxwell · · Score: 1

    IBM is SLOW. Every move is calculated, weighed, optioned, signed off by multiple layers of beauracracy, and conditioned in sherry casks, before actually being acted upon.

    What SCO is doing is like taking a chainsaw to one of those black 2001 monoliths. It'll just sit there like a rock for several months before swallowing up the chainsaw wielder without a trace. The monolith won't have so much as a scratch on it either.

  247. Still just another US story... by Homology · · Score: 1
    ... with just about little relevance to the rest of the world, apart from the amusement factor.

    Really, US courts patent and copyrigth rulings means nothing to a court of another country. Really, that foreign court has to observe national and international laws (that it signed on to). Anything else would be criminal. The foreign court has no legal choice here, end of story.

    SCO was told by a German court to "show the evidence or shut up! Ignore our ruling at your own peril." SCO promptly closed donw the German branch office.

    1. Re:Still just another US story... by the+eric+conspiracy · · Score: 1

      In terms of patent law, you are pretty much correct - US patents don't mean anything once you cross the border.

      As far as copyrights go, that is another story, and depends greatly on whether the country you are crossing into is a member of the WIPO, and signatory to the Berne Treaty.

    2. Re:Still just another US story... by Homology · · Score: 1
      As far as copyrights go, that is another story, and depends greatly on whether the country you are crossing into is a member of the WIPO, and signatory to the Berne Treaty.

      Those conventions does not automatically imply that an US court ruling has the force of law outside US. It's conventions, subject to intepretation of national laws.

  248. Re:There can be no doubt about it - SCO == stupid by Anonymous Coward · · Score: 0

    $CO seems have gotten a copywrite on work that had been widely distrubited without copywrite notice, and a Judge ruled that ATT had waived copyright protection for failing to add notice to the code. This was the turning point in the ATT/UC/BSDI case a decade ago.

    IANAL, but I don't think this will stand up to a summary challange

  249. ... then "employ" kernel dev's to replace it... by UberWolf · · Score: 1

    No doubt it would be impossible to release the details to the public about the offending lines of code.

    However, what if the companies in question were to correct the licensing problem by, say, enlisting the help of kernel developers (under court-approved NDA, of course) to replace the code?

  250. Buy UnixWare, or be sued by SCOX. by walterbyrd · · Score: 1

    The real reason that scox is up 15% today, after being up 15% Friday is because SCO has announced their new licensing plan.

    >>The company said it plans to offer UnixWare licenses tailored to support run-time, binary use of Linux for all commercial users of Linux based on the 2.4.x and later versions of the Linux kernel. SCO said any commercial Linux customers that purchase the license will be held harmless against past copyright violations and for any future use of Linux in a run-only, binary format

    http://boston.internet.com/news/article.php/2237 77 1

    To me it seems that scox is putting the cart before the horse.

    Shouldn't scox *first* prove that scox has some special rights to all versions of Linux with kernel 2.4 or above?

    Then, *if* and only *if* scox does have some special rights, *then* scox can demand that linux users somehow pay scox for the privildge of using linux.

    Right now scox is only *saying* they have special rights to linux. Talk is cheap. I could *say* I own the Brooklyn Bridge. Does that mean I can put up my own toll-booth on the bridge? Just because I say so?

    By the way, if I had contributed to a voluntary effort like efforts, only to see my efforts stolen by McBride, I would be pissed.

  251. I know what to do! by Anonymous Coward · · Score: 0

    Take all those prisoners down in gitmo and load them onto some old airplanes.
    Fuel them up to the top and give them the GPS coords for SCO.
    Two problems solved in one.
    Best wishes...

  252. Re:"We would prefer licensing to litigation," McBr by tomhudson · · Score: 5, Interesting
    Of course they'd prefer licensing. They were NOT granted a copyright on SysV Unix, but on a 20-page printout of some modifications to Sys5 verseion 4.1.

    Now, since it's a copyrighted work on deposit w. the Library of Congress, maybe someone can mosey on down there and get that 20-page printout (TX-5-705-356), and show the world the "millions of lines of source code" that were supposedly copied into Linux (must have been using really fine print to cram it all on 20 pages).

  253. Looking down the road... by Anonymous Coward · · Score: 0

    An idle thought: This is shaping up like one of those poker tournaments ESPN's been showing. SCO has some hole cards ("some of your code is really mine, but I'm not telling what"), looking to see who will fold early.

    So I've got a few questions. First: Is anyone checking for sabotage? If I wanted to kill an open source project, this is how I'd do it. Deliberately plant 'illegal' source in the pipeline early enough to lay claim to most later releases.

    Secondly: Is anyone working on a replacement project, or taking any direct contingency action? I'll (cynically) assume that SCO will win whatever case they bring, because they're (a) a company with copyrights to something, and (b) they're claiming infringement against anything Open Source, which these days, should relieve them of having to actually prove anything in a court.

  254. Re:FSF should sue on behalf of the developers then by Anonymous Coward · · Score: 0

    Okay, we know who the contributors are, isn't it time someone like the FSF (who I am a member of) sues SCO for copyright infringement?

    The FSF will only sue when people infringe on FSF copyrights. I'm not sure, but I don't think there is any FSF code in the kernel.

  255. The word you want is "barratry" by fizbin · · Score: 1

    There's a specific legal term for threatening baseless legal action: barratry.

    The precise legal definitions of barratry vary from state to state, and I'm not in any kind of position to evaluate whether SCO might or might not be in violation of one of those laws. (Being neither a lawyer nor someone who has gotten a "pay up or else" notice for use of Linux)

    1. Re:The word you want is "barratry" by molarmass192 · · Score: 1

      Well that sucks, there's not much of a bite to the barratry dog. I doubt that a $1000 fine and 6 months (aka. 0 days) will change anything. :-\

      --

      Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws-Plato
  256. Binary Licenses vs new Compiled Kernel by ebresie · · Score: 1

    Since SCO is selling "Binary Licenses" does this imply that whenever one of these licensees downloads and installs a new version of the kernel, they now would no longer be covered by the previously defined licenses agreement?

    Does SCO now own the copyrights, that it just obtained on code, to cover all the source in question including code which may have been linux derrivates (I would assume this is based on their original and not recent ones that aren't "tainted by linux"? Does that mean all of the linux code code be seen as a copyright now owned by SCO?

    --

    Eric B
    ebresie@gmail.com
  257. Re: IBM buyout of SCO by Anonymous Coward · · Score: 0

    Yeah, that's what I think. Somebody ought to just buy SCO. Steve Jobs has a whole bunch o' cash, doesn't he?

  258. A big shiny penny by sbillard · · Score: 1

    Linux and open sores software is seen as a big shiny penny in the street. SCO is trying to pick it up. Big business owns you, owns me, owns the gobbermint too. Only a matter of time before Big Business owns Linux. The open movement has gotten big enough for big biz to take notice. There is simply too much money involved. Linux is increasing in demand, this makes it valueable, it could be worth a lot of money someday. Big biz, in the words of Judas Priest:
    "Out there is fortune waiting to be had. You think I'd let go? You're mad - you've got another thing comming."
    Does the movement think they can win this in the courts? Can the GPL stand up to big biz in court? No way. The govt. is in the pocket of big biz and big biz will soon be assigned ownership of Linux and open sores software. All that revenue could help the economy, right?

    Congratulations, you got noticed. Welcome to the real world.
    Before you mod, are you sure this is a troll? I just call it like I see it.

  259. Re:There can be no doubt about it - SCO == stupid by tomhudson · · Score: 2, Insightful
    They actually only got a copyright on a 20-page printout of changes to Sys5 release 4.1 ES., not to Sys 5, not to Unix, nada.

    It's pretty irrelevant, and pretty lame on their part, to try to twist a couple hundred lines of code, which doesn't even apply to Linux, into "We Own Unix, Linux and the Whole Damn Universe".

  260. Caldera-Borg ?! by FrankoBoy · · Score: 1

    That's a great idea, and it's already been out there for a while. That's Caldera's logo though isn't it ?

  261. Re:What RMS and the IBM Legal Dept. Are Waiting Fo by lolits · · Score: 1

    Actually, the GPL doesn't prevent you from charging for gpl'd code. And as has been pointed out above, they are still distributing the source from their ftp site, so they are still in compliance with the gpl. As I see it, they are capitalizing on their fud and trying to collect money from nervous IT managers/companies who consider the payment a form of insurance.

  262. Notice the timing of two different events? by walterbyrd · · Score: 1

    SCOX finally registered some unix copyrights at the same time that SCOX announced new licensing plan.

    Do you suppose that scox wants people to think that the two events are related? As if Scox registering unix copywrite, somehow gives scox some special rights regarding linux?

  263. Re:very telling... by pacman+on+prozac · · Score: 4, Interesting

    from that url:

    Q: Earlier you said you were still a products company and not a strictly IP company. This appears to have changed and you are now an IP company. Would you agree with that assessment? Linux has succceeded while your product failed in the marketplace.

    A: Our Unixware product was damaged by Linux and that is why it isn't successful. That is why we are doing this. We didn't fail, it is Linux' fault we failed.


    ratings: 15 troll, 4 informative, 18million overrated.

  264. You're wrong by dbrutus · · Score: 1

    What they own is the legal privilege of restricting the copying of Sys V code, not the code itself. There is no other explanation that explains fair use doctrine than that the code itself is unowned but the right to copy is restricted by the legal privilege granted in the patents and copyrights article of the US Constitution in order to further the advance of arts and sciences.

    If the code itself is owned then when it falls into public domain via government directive, why doesn't the government have to write a check in compensation of this taking? Why doesn't the government have to write a check for every 'fair use'? No, the code itself has to be not subject to ownership.

    I have yet to see any legal evidence presented that demonstrates that your statement that Linux contains Sys V code is true. Nobody knows the respective modules that are copied and whether SysV is the originator of that code or they themselves have copied if from some other source, perhaps BSD which is where Linux picked it up from. The BSD license generally permits such actions but doesn't permit somebody who takes code in this way from suing others for doing the exact same thing.

    Nobody seems to have run any checks whether this code appears in BSD as well. If it does, this company is going to get buried under a ton of libel and slander accusations and will finish SCO.

    1. Re:You're wrong by thisgooroo · · Score: 1
      Nobody seems to have run any checks whether this code appears in BSD as well. If it does, this company is going to get buried under a ton of libel and slander accusations and will finish SCO.

      care to explain how to do this when nobody knows what it is?

    2. Re:You're wrong by dbrutus · · Score: 1

      Well SCO has made no representation that it's not in there. It's more of a suggestion to any IBM legal intern who might be trolling slashdot for the rare good idea. IBM will get to do this as part of the legal process known as discovery. Once they have the markers that SCO used they can go and check them against the BSD code base and see whether the SysV code is actually derived from BSD and then the BSD group can bitch slap SCO for trying to profit off of their work and we can all laugh as SCO's stock value goes through the floor.

  265. Re:If Microsoft buys SCO, you folks are SO screwed by nitehorse · · Score: 4, Insightful

    Even if Microsoft were to come out and openly show that they're the ones behind this, they don't win.

    How many companies have ever, in the history of IP, won an IP infringement case against IBM?

    Hint: None.

  266. Re:About $800,000 in the last couple of months . . by Cyno · · Score: 1

    Didn't Enron expose something horrible about our financial system? And its not just finanacial. Our entire way of life is based on capitalism. Perhaps we need to rethink these things.

    Perhaps we forgot how to think. I don't know.

  267. It's only illegal if their lawyers get careless by fizbin · · Score: 1

    Why isn't that illegal?

    Because they have lawyers sending out the letters who very carefully know the barratry statutes in the different states they're sending these letters to. I'm willing to bet that any "pay up or else" letter (the existence of which I am beginning to doubt, by the way) would be very carefully worded to be just on the legal side of the statutes.

  268. zerg by Lord+Omlette · · Score: 1

    How many software engineers does SCO have working for them?

    Why are they still working at SCO? Surely they value their dignity, right?

    --
    [o]_O
  269. Nice Troll by Bilbo · · Score: 1
    > The thing that is keeping you Linux users from filing a lawsuit is...

    hehehehe.... You even sound good enough to be masquerading as an employee of SCO.

    --
    Your Servant, B. Baggins
  270. why not start back with 2.3 by maryjanecapri · · Score: 1

    to avoid all this SCO nonsence why don't the developers start back with kernel 2.3 and figure out where the code is, replace it, and redistribute? is that even possible?

    --
    nature loves variety::society hates it get your variety at http://www.monkeypantz.net
  271. How to hurt SCO by wintermute740 · · Score: 2, Interesting

    For anyone interested, the easy way to hurt SCO is to dial their sales rep at 800-726-8649 (number taken directly from article) and making BS inquiries. Bogus inquiries = wasted resources = lost revenue.

  272. Re:There can be no doubt about it - SCO == stupid by syschuck · · Score: 1

    SCO should release the code that *we* linux users are alleged to be pirating. You have to wonder about why SCO has not directed some group to remove the code(s) they claim to be theirs under their copyright. There are no excuses; It's not under trade secrets any more, and looking at what is supposedly SysV code in no way taintes the
    users; in the same sense that reading a paragraph from an unpublish novel taints the readability of novel to future readers. I think the only reason
    they have not pointed out the code specifically, is that they DO NOT KNOW for a fact that the code in Linux is a line for line pirated copy of thier
    supposed SysV code. Additionally, code the IBM contributed to Linux under the GPL is, what I understand, a highly scrutinized, completely and wholly IBM IP.

    It's like if I posted a copyrighted picture on my website and some third party writes me and says "you are in violation of my copyrights. I will
    license it to you for 1500 bucks" and you follow up with "which image is it?" He replys "Oh.. ahh.. I can't say... but it has blue in it".

    Seriously though; when you are talking an installed base of 2.4+ million servers and a better number of desktops linux users now. SCO Group is just full of hot legalize wind blowing crap just to extort money from the linux community. Now they are trying to claim ownership
    of linux itself..

    Unbelievable!

  273. Compensation for Linux Users by mudrat · · Score: 1

    The confidence that most of us Linux users have that the code is not stolen from SCO is the assurance of Linux community leaders and various companies selling Linux. This people and companies have deliberately mislead people into illegally using code which belongs, in part, to SCO.

    Surely the correct reaction of the community is to pay SCO, look to moving to another operating system and to bring suit against Linus et al for misleading us into committing a crime? Even if the code wasn't stolen from SCO it will still be easier to sue Torvalds, Cox and the rest of the major kernel contributors than to sue a major successful company like SCO.

    Note: No, I am not serious. Sorry.

  274. SCOForum by Anonymous Coward · · Score: 0

    Someone should crash this party.,

  275. Can SCO be forced to put up or shut up? by Panoramix · · Score: 4, Interesting
    No, if they encumber the linux codebase with their own license, then the GPL becomes void and no longer can be used to distribute Linux [...] In fact, if they actually make anyone pay to run linux, then they can be sued by the contributor of every other piece of code for copyright violation. After all, they distributed the rest of the code without a valid license to do so.

    Quite insightful. I have a question now. Couldn't the kernel developers use this to force SCO to reveal once and for all exactly what code is in Linux that infringes on their "intellectual property"? (whatever that means)

    What I mean is, what if some fifty, or say a hundred kernel developers individually sue SCO for copyright infringement? The argument is that, since SCO claims to have the rights to impose a license on Linux, then the GPL becomes void, and they cannot distribute Linux at all. But they are doing it, distributing Linux, even as I write! Thus, by their own claims, they are infringing on the copyrights of quite a lot of coders.

    Just think of the DoS to SCO's legal team! And the headlines: SCO bitchslapped by dozens of lawsuits by Linux developers! And of asshole McBride being called as a witness for the prosecution to show how the GPL is void and they are infringing copyright!

    But the important part is, it seems to me that then SCO would have to either (a) claim themselves guilty of copyright infringement, be fined and forced to compensate the copyright holders (paying through the nose, I only hope), making themselves the laughingstock of the whole industry; or (b) admit they did not have any rights over Linux to begin with, ending this madness once and for all.

    Of course, I'm no lawyer, not even a citizen of the U.S. of A., so I may be just wanking here. Also, if things were to go through my (otherwise happy) option (b), that could be not too good for the kernel developers (I'm thinking about they losing their suits and having to pay attorney fees and so). But maybe the EFF could give some support here. At least I would gladly donate for this cause.

    Anyway. What do you think, sirs?

    1. Re:Can SCO be forced to put up or shut up? by Kalak · · Score: 1

      What I mean is, what if some fifty, or say a hundred kernel developers individually sue SCO for copyright infringement?

      An idea that just occurred to me. If a bunch of coders, specifically those who work on parts that might have come from IBM, were to sure SCO based on these ideas, then SCO would have to defend themselves to individual attacks on certain sections of the kernel. As more information is "cleared" by these small lawsuits of being "tainted", the infinging code becomes narrowed down without ever having to sign an NDA.

      First distributed testing of Linus' code, then distributed coding of Linux combined with distributed testing. A pattern is developing...

      Quick, someone grab the MAINTAINERS document and start the distributed lawsuits!

      --
      I am, and always will be, an idiot. Karma: Coma (mostly effected by .hack)
  276. Sent this letter to SCO by adrenaline_junky · · Score: 2, Interesting

    To whom it may concern,

    I am a commercial user of the Linux kernel. As the president of my company I hereby declare that I am willfully using Linux without any additional licensing from SCO beyond acceptance of the terms of the standard GPL. Go ahead and try to sue me you sick pathetic morons. I'd love to see it.

    There, you have been notified. Maybe I'll send some certified mail as well, just for good measure. Any lack of action on your part constitutes acceptance that SCO owns no rights to Linux kernel source code outside of those provided by the GPL.

    [Name and address]

  277. Have to laugh... by c_dog · · Score: 1

    There has been a lot of insight into the legal issues and the proper level of outrage to be displayed over this issue. I have truly appreciated reading everyone's comments so far.

    Had to laugh over this a bit though, as it reminds me of college. Anyone else play "You're stupid. Give me $20!" with incoming freshmen? Anyone make any good money? :)

    Also, I read someone's post regarding guesses on who may be secretly buying up SCO stock...to that person: Think darker. Think anti-trust, and slap-on-the-hand. Just my initial thoughts on that idea. Who knows?!

  278. Sue SCO for breaches of contract, for company by Anonymous Coward · · Score: 0

    Its time SCO is sued for distributing Linux in violation of the GPL, for several times what the company is worth. SCO is fyi still distributing Linux on its servers, and attempting to resell it violates every right of every business that has contributed code to it.

    Suits can come from anyone, from small contributers up to IBM. While it might stretch on for awhile, I don't think this is a friviolous lawsuit, but one that ought to be clearly won. Look at the facts: Tries to sit on committees contributing code, continues to distribute Linux after SCO lawsuits filed, tries to sell Linux licenses.

    I think its win-able, but I don't think SCO has as much money as it needs to pay off all the lawsuits.

  279. How to Stop Them by CleverFox · · Score: 1

    Make sure their web server is down 24x7 please. We should have enough expertise for some good old fashioned DNS poisoning, etc...

    Robber barrons. If we find out they have nothing, which we may never..., I believe there should be a CRIMINAL law suit for extortion. Send these phonies to jail where they belong.

  280. You are right :) by Pac · · Score: 1

    (see how I can't change my mind from one comment to another?)

    I misread another (unlinked) article. I believe Linus is the sole owner of the trademark and the Linux Mark Institute is the actual entity responsible for defending the name, something they seem to do eagerly (so again, yes, the Linux trademark is actively protected). The Penguin, on the other hand, can be used without a license...

  281. I can just see the future now... by Anonymous Coward · · Score: 0

    ... I'll be sitting at home on my couch peacefully reading the latest Linux Jornal magazine and listening to the "gentle whirring" of my Linux boxen in the other room when suddenly my peace and quiet will be interrupted by a few dozen screaming FBI agents in full riot gear with automatic weapons crashing in through my doors and windows. I'll be tossed to the floor, a boot jammed up my crotch with a rifle pointed to the back of my head as my arms are pulled back roughly behind me, my hands tightly handcuffed to be used to drag me away and throw me into the back of an unmarked white SUV never to be seen again...

    Just because the folks at SCO are annoyed with hte large stack of payment demands they have sent me.

    I'm just not certain if this is the new American Dream or the new American nightmare...

  282. Re:The scary thing, ... where? by justsomebody · · Score: 1

    There's no proof, no case and no real actions.

    Ok, I'll say that once again:

    1. SCO hasn't shown any proof yet
    2. Based on how calmed Linus, Redhat and IBM are, I'd say there's no case.
    3. Kernel is all built in public which makes available to track any part of code being added during time.
    4. Main SCO's intention is to drag this as forever as possible, without actions, just blufffing
    5. America is the only place where is possible to license something during legal dispute of that something (same as thief got caught stealing in shop, bought items during trial got freed and then sued shop for false alligations), I really don't understand how it is possible to license something that isn't yours. It's just like I would buy Dell, place some card in it, copyrighted my product and sued everyone that uses this configuration.

    the only possible solution to stop FUD is that every Linux distributer (and every company that profits on Linux) sues SCO, for false allegations and business loss because of them. If there would be enough law cases, that wouldn't solve anything, it would just speed up main case that everything goes around

    --
    Signature Pro version 1.13.2-3 release 83.5 beta3try7 after-breakfast edition
  283. Talk about FUD machine... by jtheory · · Score: 1

    Why does Yahoo just print the press release as if it were news? Sure, the mention that the source is SCO, but I didn't notice that right away... and was shocked when I started reading stuff like this as if it were fact:

    Hundreds of files of misappropriated UNIX source code and derivative UNIX code have been contributed to Linux in a variety of areas, including multi-processing capabilities. The Linux 2.2.x kernel was able to scale to 2-4 processors. With Linux 2.4.x and the 2.5.x development kernel, Linux now scales to 32 and 64 processors through the addition of advanced Symmetrical Multi-Processing (SMP) capabilities taken from UNIX System V and derivative works, in violation of SCO's contract agreements and copyrights.

    Yoicks.

    --
    There are only 10 types of people: those who understand decimal, those who don't, and, uh, 8 other types I forget.
  284. Much doubt about their case by LinuxGeek · · Score: 5, Insightful

    SCO contends that Linux could not have gotten the "enterprise" features without IBM copying Unix code and pasting it into the Linux kernel. That is the only real claim I have heard (read).

    A couple of questions I have. If I am using linux in desktop mode on a single cpu, how can I possibly be using the actual features that they claim were necessary to scale beyond 4 processors?

    I also have a client that is running a 4 year old Linux distro on a closed network that just runs night and day. How could this possibly infringe since it predates the IBM kernel contributions that SCO claims started this bruhaha? Yet they seem to want a license fee for any vintage of running Linux.

    SCO wants to distribute a binary only Unixware runtime that can execute Linux binaries, presumably as the only "legal and non-infringing" platform for doing so. How can they completely incorporate this capability without taking any GPL'd code and ignoring the license?

    My opinion after dwelling on this for a while is this:

    1 - SCO is trying to overthrow the entire Linux movement that threatens their struggling business. They are scaring the heck out of businesses that currently run or were thinking about deploying Linux. They are not allowing any access to information about their claimed code swap. This means they have no desire to co-exist, but to supercede completely. Their steps so far support this opinion, future moves may change this opinion. Kernel coders have expressed great interest in learning which features supposedly infringe on SCO IP so they can be replaced. It seems that SCO has been completely unwilling to inform them without having them sign an NDA that would then prevent them from fixing any actual code infringment.

    2 - SCO is attempting to openly break and defy the terms of the (L)GPL. If they can do so, then they weaken it tremendously and encourage others to dissent too. They are also attempting to change established precedent concerning IP infringment and end user rights. Way back in the early 1990's Microsoft stole compression technology from Stac and had to pay them a large settlement. The outcome for consumers that had already purchased the infringing product? They got to keep possession and continue to use the product they had payed for. Some people got free upgrades, but the ones that chose to keep using the original MS stealware didn't have to get an additional license from Stac to remain legal. Microsoft also countersued claiming that Stac had illegaly reverse engineered part of MS-DOS to enable them to seemlessly integrate their product below the filesystem level. MS won the counter-suit and a smaller $13million award. Customers that had purchased Stac products still had the legal right to use them too. This is because the customer or end user wasn't involved in the actual theft and only indirectly get benefit from the illegal acts on both sides. This precedent holds true in all of the cases that come easily to mind, but there may be exceptions. What the freak is SCO trying to pull?

    --

    Kindness is the language which the deaf can hear and the blind can see. - Mark Twain
    1. Re:Much doubt about their case by smokeslikeapoet · · Score: 2, Insightful
      This means they have no desire to co-exist, but to supercede completely.
      I concur. SCO obviously doesn't want to compete with Linux. They don't even want to peacefully coexist with Linux. They also know that Linux evangelicals have no desire to run proprietary code, that's exactly why they don't want to give Linux dev's the offending code so it can be rewritten. I'm getting a little tired of this whole situation, but that's exactly what SCO intends to do, drag these accusations out as long as they can possibly afford,and scare as many corporate users as possible. I don't exacty know exactly why they think that they can claim rights the Linux source whether or not it contains SysV code. Understanding SCO's actions is like trying to negotiate with terrorist. You just can't reason with the unreasonable.
    2. Re:Much doubt about their case by Anonymous Coward · · Score: 0

      Good points, but I think we are all missing the real issue, what SCO will have a REALLY hard time proving.
      We can all agree that SCO sucks right? We know that thier flavor of UNIX is crap. We also know that IBM's software engineers are much smarter than SCO's (obviously).
      So, the $64,000K question is:......drumroll please...why the HELL would IBM even want to steal SCO's code in the first place???
      I don't think it would take a Perry Mason to run with this one.

    3. Re:Much doubt about their case by Anonymous Coward · · Score: 0

      The next generation of AIX--AIX 5L--takes AIX to the next level with advanced technology, a strong Linux affinity and added support for IBM's Power and Intel's future IA-64 processor-based platforms, making it the most open UNIX operating system in the industry. AIX 5L demonstrates the success of the Project Monterey initiative, incorporating technology from the world's leading software and hardware providers, giving customers the business flexibility and performance they need for e-business.

      With AIX as a critical component powering the highly successful IBM S80 server, IBM's UNIX road map has never been stronger. In fact, IBM Web servers saw a 30 percent growth in our last quarter. AIX technology will help contribute to the success of the future systems running AIX 5L on Power and IA-64. AIX 5L is expected to be released this fall.

      D.H. Brown and Associates, a highly respected industry consultancey, rated AIX as the industry's leading UNIX operating system for the sixth straight year. AIX outperformed fourth-ranked Sun's Solaris operating system in key areas including Web application functionality and systems management. Sun's strategy contrasts IBM's commitment to make AIX the industry's open mission-critical UNIX operating system.

      AIX 5L offers customers advanced technologies. IBM has worked with a number of companies to provide best of breed technology for AIX 5L. Industry contributions include key technologies from IBM DYNIX/ptx, multi-path I/O and NUMA, and from SCO UnixWare and UNIX System 5 standard technologies. Bull continues to contribute development expertise in areas such as scalability and workload management.

      All of these efforts are paying off. Soon customers will be able to take advantage of the added benefits of AIX 5L. AIX 5L In addition to CPU and memory, AIX 5L Version 5.0 will offer an improved Workload Manager (WLM) with the ability to manage disk I/O, a capability not offered in Sun Solaris. This will help enable IT managers to give priority to Web-serving applications and resources, while making unused capacity available for other Web-serving tasks. AIX 5L will also offer Java 2 Version 1.3 support with expected availability ahead of Solaris. TCP/IP enhancements, offering improved network performance and reliability, will also be included. Among the UNIX System 5 technologies to be incorporated in this release is the SVR4 printing subsystem providing industry-standard print administration and drivers.

      Customers Will Benefit from Linux Affinity

      IBM is working to provide strong Linux affinity with AIX 5L. This will enable faster and less costly deployment of multi-platform, integrated solutions across AIX and Linux platforms. Many applications developed on and for Linux can run onn AIX 5L with a simple recompilation of the source code, allowing customers to combine Linux applications with the advanced scalability and availability features of AIX. This Linux affinity in AIX enhances the customer's ability to adapt to changes in their business and technology.

      Linux affinity on AIX includes Linux application source compatibility, compliance with emerging Linux standards, and a GNU/Linux build-time environment with tools and utilities that combine to facilitate the development and deployment of Linux applications on AIX 5L. Linux affininty also includes AIX/Linux interoperability verification and will benefit customers looking to use Linux for fron-end Web serving and AIX 5L for transaction and data management.

      Software, Hardware Providers Working with AIX 5L Beta Code

      Software providers are building applications with the current beta release of AIX 5L for the future Intel IA-64 platform. Tool and middleware providers, including Cygnus Solutions, EPC, Geodesic, IBM, Merant, Parasoft and Roguewave, are working with preproduction systems to create tools and middleware to build applications. Other software providers are using these tools to build solutions that range from e-business and supply chain management to enterprise resource

    4. Re:Much doubt about their case by LinuxGeek · · Score: 1

      If they can drag this out long enough, it becomes almost irrelevant whether they win a lawsuit. The fear level generated can be even more effective than a victory.

      It would not surprise me to find that MS and SCO are having strategy sessions. The moves that SCO is making are too good and too forward thinking for the principals at SCO to be working alone (given their old track record). Remember that the enemy of my enemy is my friend. Also remember that MS used to own 25% of SCO and may still get royalties for portions of their Xenix code.

      Now it would really suck if MS starts claiming that portions of Xenix code have ended up in the Linux kernel. I shudder at the thought.

      As for IBM, this attack by SCO will have the desired effects even if no code were copied. Remember that IBM is a giant behemoth with layers of managment. If SCO can prompt IBM to put in layer after layer of code review groups, IP review groups, code accountability groups, managment groups and the paperwork jockeys to track the information flowing between groups, then IBM will have essentially shut down the useful rate of their work on Linux. Bingo! MS and SCO both make significant progress towards winning this phase of the game.

      I also ask myself some more questions here. MS is a licensee of SCO now right? So they have full access to the source now for sure. But how long have they had source to peruse? I am sure that MS has many more programmers that could painstakingly compare Linux source to the code they could access before formally licensing the code and IP.

      Does SCO have the manpower for such a task? Well, at their jobs page there is only a single sales position listed. Nothing for OS support, driver developer or low-level kernel programmer. This dosen't sound like a healthy technology company to me. Hmmm, how many code monkeys could they throw at the Linux kernel source?

      --

      Kindness is the language which the deaf can hear and the blind can see. - Mark Twain
    5. Re:Much doubt about their case by Anonymous Coward · · Score: 0

      I also have a client that is running a 4 year old Linux distro on a closed network that just runs night and day. How could this possibly infringe since it predates the IBM kernel contributions that SCO claims started this bruhaha? Yet they seem to want a license fee for any vintage of running Linux.

      They're not. According to the interview on the CNET site, McBride is claiming only Linux 2.4 and after contains their intellectual property. Linux 2.2 and before is safe. At least that's what he claims this week.

    6. Re:Much doubt about their case by LinuxGeek · · Score: 1

      Thanks for the pointer, I finally sat through the whole interview and got a strong whiff of BS throught his presentation. If you haven't read this already, check out this interview with SCO's Mr. Sontag at Byte for some direct contradiction to what Darl says. Seems that SCO thinks they are the kings of the os world.

      I wish they would stay with a single story now, but once the trial starts they will have to stop dancing around and choose a single presentation that matches the suit they filed.

      --

      Kindness is the language which the deaf can hear and the blind can see. - Mark Twain
  285. The sad thing... by Steeltoe · · Score: 1

    The sad thing is this: The management of SCO may even claim they had to do this. They are supposedly required by law to maximize profits to the investors.

    What sort of foul, unethical creature has Corporations become?

    How many laws do a nation really need, and where did morality, responsibility, sharing and helping go?

    Down the drain?

    We shouldn't be pissed off at such behaviour, but feel pity and compassion to those greedy people who think they can be happy on other peoples energy. And do something about it instead of whining. Improve anything. Begin with yourself.

    On a happy note: This is what you get when management runs a technical shop.. ;-)

  286. Re:Hello, SCO? The Free Distribution by Anonymous Coward · · Score: 0

    I'd like to see such a distrubution, patch, made directly from SCO's own Linux distrubtion.

  287. Tell me this: by Tokerat · · Score: 3, Interesting


    Is it legal for SCO to even take these actions before anything is proven in court? It seems as though they're saying "OK! We filed a lawsuit! That proves it, pay up!"

    I would think they couldn't (by law) collect on such claims until after the suit, and even then, only with a ruling in their favor? Or can they say what they want, and the suckers shall fall?

    --
    CAn'T CompreHend SARcaSm?
    1. Re:Tell me this: by jasonsfa98 · · Score: 2, Interesting

      I agree. It's like telling someone that you invented the light bulb, and if they believe you, charge them for it.

      I think FRAUD is the word we are looking for.

    2. Re:Tell me this: by borgheron · · Score: 1

      The latter. They can, legally, say or offer anything they wish. If people are dumb enough to fall for it, then that's the way it goes.

      I could offer a license to run Windows, if I wanted, and if people are dumb enough to buy it then so be it. That's about the same amount of merit this has.

      GJC

      --
      Gregory Casamento
      ## Chief Maintainer for GNUstep
    3. Re:Tell me this: by borgheron · · Score: 1

      I could, of course, get sued by the LEGAL copyright hold once it's proven I have no claim. Which is likely what will happen with SCO.

      Apologies for replying to my own post...

      GJC

      --
      Gregory Casamento
      ## Chief Maintainer for GNUstep
  288. no problem by dh003i · · Score: 1

    SCO's been obfuscating this thing enough to confuse anyone and everyone...there are still many areas of this lawsuit the are confusing to me.

  289. Minor nit by gilroy · · Score: 2, Interesting
    Blockquoth the poster:

    If I give you the binary and source code to a program I wrote, and it contains a copryright notice, you have NO RIGHT to distribute or disclose that source NOR it's binary to third parties.

    Actually, there's no need for a "copyright notice". Under the Berne Convention everything is automatically copyrighted at creation. If you want to collect maximum damages, you'll need a copyright notice (and a filing with the Registrar of Copyright), but its absence doesn't negate your copyright. It sounds like SCO might be shooting themselves in the foot on this...
  290. RCU, NUMA, etc. by Maimun · · Score: 1
    The RCU things was discussed by Linus recently, see here
    The one thing SCO has mentioned has been the Read Copy Update code that IBM gave us, and that wasn't accepted for the longest time into the kernel exactly because we knew the patents were owned by IBM. [But] we said we couldn't take it until you [IBM] said very explicitly that you also license the patents.
    I am surprised about NUMA. Isn't it something very recent? How many NUMA machines were there when SCO acquired the rights over Sys V? Does anyone here know more about NUMA and System V?
  291. McBride lies by utmecheng · · Score: 1

    McBride mentions (in the interview) that the few dozen people who have come in have 'unanimously' agreed that SCO's claims were strong. I remember distincly a few open souce guys going in and while they did write they were treated with respect in Lindon, they did not in ANY way give credibility to their claims. Anybody else see the problem here?

  292. LOL by beavis88 · · Score: 1

    http://www.dumblaws.com/states/states.php?State=Ma ssachusetts

    Some other great ones in there too (including the 'no one may bathe without physicians' authorization, mentioned by another poster in this thread)

  293. Here's the Truth by msaulters · · Score: 1
    From the article:
    Following the distribution of our letter to the Fortune 1000 and Global 500, many prominent companies using Linux contacted SCO to ask, 'What do you want me to do?'," added McBride. "Today, we're delivering a very clear message to customers regarding what they should do. Intellectual property is valuable and needs to be respected and paid for by corporations who use it for their own commercial benefit. The new UnixWare license accomplishes that objective in a fair and balanced way."

    This says it all, really. The heart of the argument is that intellectual property is valuable and must be paid for. That's a very Microsoftian point of view, if you ask me. That statement leaves NO room for the idea of intellectual property as freely used for the benefit of all.


    Let the fuckers sue me. I've signed no agreements with SCO. As far as I recall, you can't be held liable for purchasing stolen goods if you were acting in good faith, believing they were legitimate. You may have to give 'em back. OK, SCO, tell me what I need to give back.

    --
    These people looked deep into my soul and assigned me a number based on the order in which I joined.
  294. SCO Haiku by Anonymous Coward · · Score: 0

    Failing Company
    Fear, Uncertainity and Doubt
    Damn you IBM

  295. Tainted Coders by nurb432 · · Score: 1

    This is a point I've been trying to make all along, but was lost in the 'SCO is stupid" ranting:

    That even if the code is to be displayed, and we fix the offending lines. The very fact we have seen them ( be it documented or not ) means anything we do is legally tainted..

    It would make 'fixing' the kernel rather difficult.

    --
    ---- Booth was a patriot ----
    1. Re:Tainted Coders by Trigun · · Score: 1

      I don't think that such accusations would stand up in court, but the fact that they will make it to court is troubling. Should they be able to make these allegations, then SCO would essentially have a license to print money, by doing exactly what they are doing now.

      It boggles the mind. Make baseless allegations, sell protection, lose in court, go to step 1.

    2. Re:Tainted Coders by arkanes · · Score: 1

      Yeah, but you're wrong (at least to a degree), so it's okay that it got lost. SCO would certainly make a claim of taint, but thats a much harder sell with a copyright claim (where it's accepted, normal, and protected that you would take inspiration from previous work) than in patent case.

  296. Unlicensed version of ... by Anonymous Coward · · Score: 0

    I've been using unlicensed versions of Windows for years now, so why would I pay for Linux

  297. Why sue? Just set non-GPL license prices. by expro · · Score: 2, Interesting

    Who needs to sue? Instead use SCO's tactics against them.

    Dear Linux users:

    SCO has claimed that the source code which they distributed for years, and even for months after publicly claiming copyright to unspecified portions of it, is not covered by GPL.

    If their claims are true, then the code cannot be distributed under GPL, in which case you have no right to use the code which I have personally contributed to GPL. I am happy to license these lines of code to you for 50 billion dollars. Be sure to ask each other contributor how much he requires to run the code not under GPL.

    So, the choice is either believe that the code is GPLed or pay for a SCO license plus $50 billion to me, plus the proper compensation to each other contributor.

  298. Download Linux from SCO via FTP by MAXOMENOS · · Score: 1

    Here is the link. Go nuts.

    1. Re:Download Linux from SCO via FTP by pherris · · Score: 1

      Thanks. I'm downloading three copies of everything as we speak (just to make sure I get a clean copy that isn't corrupted like SCO's management).

      --
      "And a voice was screaming: 'Holy Jesus! What are these goddamn animals?'" - HST
  299. SCO claim it's 2.4 by jcdr · · Score: 1

    If it's not 2.3.99, take 2.3.43 or 2.3.18... If problematic code exists, it have been introduced in a know version of linux, take version-1 and merge the evolution and fix.

    SCO case is about introduction of code into Linux, not about Linux having the same functionality as sysV.

    1. Re:SCO claim it's 2.4 by Anonymous Coward · · Score: 0

      I think the idea of going back to 2.3 or even 2.4 is ridiculous. People, 2.6 is just finishing up! Do you have any idea how much things have changed?

      2.6 gives improved SMP performance, just like that SCO idiot was talking about. It does this by doing things like getting rid of IRQ locks, and having a new process scheduler. This in no way translates to SCO anything. SCO has absolutely no claim to any of this. It came straight from people like Linus.

  300. The current case is already in Federal court by mec · · Score: 1

    SCO filed in state court.

    IBM pointed out, in a very sarcastic lawyerly manner, that SCO is a Delaware corporation but IBM is a *New York* corporation, not a Delaware corporation as SCO mistakenly claimed in their filing. Therefore diversity of jurisdiction applies and the case may not be heard in a state court.

    So now the case is before the US District Court for the District of Utah.

    If you want to know more:

    SCO Page on the IBM Lawsuit

    Read the PDF's there.

  301. So ... Who defends the GPL? by Usagi_yo · · Score: 1
    I've seen alot of posts regarding the strength of the GPL and how SCO can't break it. I'm not so sure now. Who defends the GPL?

    It's becoming clear to me (at least) that SCO's ultimate goal is not capitulation from IBM, but to coopt Linux.

    We are being duped with the IBM/SCO legal manuevers. SCO, with a sleight of hand is now selling LINUX binary licenses for 2.4+, declaring anybody running 2.4+ in violation of their copyright (IP or whatever) and at risk, unless they of course buy the new SCO binary license.

    Now, there is alot of ranting and raving about GPL this, GPL that, the question is, who is going to step up to the plate with money and lawyers and defend the GPL?

    The GPL is weak when it comes to protecting GPL code. The reason why it is weak is nobody has any vested interest in defending it. Now SCO is going to coopt LINUX and nobody can do anything about it?

    SCO is going to offer binary licenses, some are going to buy. Those that buy help strengthen SCO's claim. Eventually, without somebody coming in and stopping SCO via a Infringement lawsuite claim of their own, SCO is slowly going to tighten the noose around LINUX. Now, who is going to defend against somebody licensing software and selling it, that is alreay licensed and distributed for free.

    My best guess is that all those Linux Distributers who have money, oughtta get together and start a class action and cease and desist against SCO before SCO owns them.

  302. Kudos to the Slashdot editors... by fuqqer · · Score: 0, Redundant

    They let the beaten dead horse rest long enough. Now that SCO stories have re-emerged, we now have another 700 or so comments about how SCO sux to wade through. Please don't beat the horse (Run horsey run!)

    Anyway, I think I liked it more when there was no SCO (story or company that is). Enough of my ranting, time to read and wish I could mod 90% of articles in this thread as reduntant.

    Go ahead! Mod my post as a redundant, flamebaiting, troll, see what I care.

    This sig is a hand typed one of a kind sig, there are many like it, but this one is mine.

  303. From the US Copyright Office database by Heggsy · · Score: 3, Informative
    A quick search on thisreveals:

    Registered Works Database (Claimant Search)
    Search For: SCO GROUP, INC
    Item 1 of 1
    1. Registration Number: TX-5-705-356
    Title: UNIX system V, release 4.1ES.
    Description: Computer program.
    Note: Printout (20 p.) only deposited.
    Claimant: the SCO Group, Inc.
    Created: 1991
    Published: 27Jun91
    Registered: 30Jun03
    Author on © Application: UNIX System Laboratories, Inc., employer for hire.
    Previous Related Version: Prev. reg. 1992, TXu 510-028, et al.
    Claim Limit: NEW MATTER: revisions.
    Special Codes: 1/C

    (note: The above is taken verbatim from the US Copyright Office online record database)

    So... either SCO only copyrighted 20 pages of code, or you don't need to deposit the whole work with the CO in order to have it copyrighted. Unless the '(20 p.)' above means something entirely different...

    Interesting, all the same.

    1. Re:From the US Copyright Office database by ndevice · · Score: 1

      in the interest of conserving paper in deference to the needs of their legal team, the 20 pages were printed with a really small font.

    2. Re:From the US Copyright Office database by dvdeug · · Score: 2, Informative

      So... either SCO only copyrighted 20 pages of code, or you don't need to deposit the whole work with the CO in order to have it copyrighted. Unless the '(20 p.)' above means something entirely different...

      On sourcecode, you only have to deposit the first ten and the last ten pages. Doesn't seem like it would help much in a copyright case, but they probably don't want to handle stuff like GCC, which would be 13,000 pages if printed out in full.

    3. Re:From the US Copyright Office database by Heggsy · · Score: 2, Interesting

      Ah, thanks for the clarification, I've been wondering about it all evening (details like that niggle me).

      I can't help feeling that it's a rather odd system... I mean, what's to stop XYZ Corp. from inserting a function into the code that has not been deposited, and then claiming breach of copyright? In the case of a printed book, there's a fairly good chance that there will at least be a copy in the Library of Congress which would be fairly decisive in determining when a copyrighted work was created, but it seems to me that it would be hard to get independent verification of the veracity of the copyright claim if it was something like 'Umm, well you know those 20 pages of source code we deposited, well this function just happens to be on pages 48-53. Look, here are the relevant pages!'

      I'm sure there's a completely obvious answer to this which I have overlooked entirely, but in my defence, it's late, and I'm hungry.

  304. Linux org must Sue back ! by morbingoodkid · · Score: 1

    What interest me in this law suite is that nothing have been proven yet.

    SCO is going ahead sueing everybody making accusations that until now have not been proven. It is time that the same tack is taken. Until now it looked like a contract dispute but SCO is now effectivelly calling Linux developers theives.

    I find this very offensive. One of the primary reasons for using Linux is to keep myself legal without having to fork out thousands of dollars for the other products.

    I do not have the organizational skills, money or clout to go ahead and do it myself but I think personally that a Linux organization should start contacting developers and build a case against SCO .

    The first step would be to get the SCO code get an idependant organisation to audit their code and make sure no GPL code is in there. If any code was released by them through their Caldera effort will be released under GPL and thus not subject.

    After that the code that is left are subject to the claim. Interesting part of course is that as far as I understand it if a part of the SCO code is under the GPL (as it was included in Linux) is there not a viral effect that a lot of the SCO code are then automatically subject to the GPL and as such must be released (just a thought).

    Personall I think this is what happened and like any good strategist would know an attack is the best defence. It is and have been time for Linux developers to fight back.

  305. Mod this post up by runswithd6s · · Score: 1

    Considering that it's parent is highly overrated, this post, which is informative, should at least get one or two mods.

    --
    assert(expired(knowledge)); /* core dump */
  306. Wasn't upset until now by Ridgelift · · Score: 2

    "With more than 2.4 million Linux servers running our software, and thousands more running Linux every day, we expect SCO to be compensated for the benefits realized by tens of thousands of customers."

    "Running our software?" Running our software? How dare they! This whole issue didn't really bother me until now. I guess that's what SCO's been claiming all along, that they are the rightful owner of Linux. But to now see it in black and white that "2.4 million Linux servers (are) running our software" doesn't just upset me, it makes me livid.

  307. The Open Software Foundation (OSF) by m11533 · · Score: 3, Interesting

    I have been following all of the discussions regarding SCO and their claims to Unix/Linux. One issue that I have not seen mentioned is that there were concerns in the second half of the 1980's that something like this was going to happen.

    Back then, the focal point for everything was AT&T and their licensing of System V Release 4 (I believe that's the right release). All of the commercial Unix vendors were licensing rights to Unix from AT&T. Prior to System V Release 4 AT&T was charging a very minor fee and licensing under a minimally restrictive set of terms and conditions. With the release of System V Release 4, AT&T tightened up the terms and conditions. My memory is that they did not significantly increase pricing. But, the industry reacted with a great deal of concern that AT&T was laying the foundation for significant increases in licensing pricing. These companies viewed this as a major threat to their existance. If they signed on for the System V Release 4 license, went their line of reasoning, they were giving up control of their Unix OS product pricing, and at any point, AT&T could jack up prices and put them out of business.

    Thus motivated, Apollo Computer (remember them?) put together a consortium that included HP, IBM, Digital, and forgive me for forgetting the other players. Their initial charter was to produce a Unix OS reference code base that was licensed under terms and conditions that ensured all parties had control of their own destinies. To the best of my knowledge, the only vendor to ever actually ship that OS was Digital, initially shipping it under the OSF name of OSF1, and then renaming it Tru64.

    One company visibly went a different path. Sun very early in the process partnered with AT&T. They, in fact, had a lot of involvement in the development of System V Release 4.

    So, why is this history important?

    First, Sun and their Solaris product line is exempt from the SCO excitment because of their special licensing terms and conditions that originated in their partnering with AT&T in their work on System V Release 4.

    Second, as I see it, the actions being taken by SCO are precisely those that motivated the formation of the OSF.

    Does anyone know if Digital and Tru64 are also exempt from SCO's actions? If so, then it would give HP an unexpected (they couldn't be THAT visionary, could they?) benefit from their purchase of Digital.

  308. Evolution + Lazy by RabidChipmunk · · Score: 1
    That's right, it's called "evolution": more lazy will die, more aggressive will survive.


    This is not actually true. High agression actually carries a large cost. In places without strong competition for a limited resource, high agression brings limited return for a high mortality rate.

    While I could lecture for hours and swamp you with actual evolutionary examples (start with the sloth) I'll just let you think about High School. The high agression males who took up street racing and then (if they lived) joined the Marines vs the geeks who got food delivered. Compare their death-rates or insurance rates. [Ignore the eventual heart disease, they will have reproduced by then. You're not worth as much after you stop breeding. (aside: memes vs genes)]

    Back on topic:
    Sitting back and ignoring them is a reasonable tactic. It doesn't take much effort. It doesn't take much money. We can spend our time wooing mates (like that sexy PPC970). All we have to do is wait for SCO to run off a cliff. If somehow they survive the fall, we drop rocks on them. Safe and sound on the higher ground.

    Finally, OSS continues to gain in public exposure and sympathy (except MO state government). The later the trial takes place, the more likely a judge is to be favorably inclined toward us. Thus it is SCO's best interest to get this over as quickly as possible (not to mention legal fees.) It is our best interest to let public opinion and technical excellence build. SCO can bleed for a while.

    I'm really not in a rush.
    --
    This is not a political statement. This is not legal advice. It's a frick'n Slasdot post. However: I'm Running For
    1. Re:Evolution + Lazy by axxackall · · Score: 1
      1. What if SCO is well-belayed to manage to stay on the cliff without failing down? As for now, I don't see any reason why they should fail from the cliff.

      2. The more we wait SCO failure the more Linux reputation in a business world drops. As for "sympathy", I guess you mean a sympathy of geeks, which cannot be count in any business plans. Geeks don't buy, businesses do.

      3. I think it's in SCO best interests to keep FUD as long as possible. They are trying to make money on FUD.

      4. I don't suggest to woo mates. Instead, I suggest Linux community to coordinate efforts with IBM. We need lawyers. Without lawyers we are blindly thinking many things wrong, basing our understanding on our feelings and emotions, while the enimy is building the case with facts, which might be laughable if we would know them, but we don't know them, while the judges don't know that they are laughable. In the court you cannot jump last minute to the case and win it, whatever case is.

      P.S. Did you read Sun Tsu's "Art of the War"? Then you should remember: "if you underestimate your enimy then you have already lost the battle."

      --

      Less is more !
    2. Re:Evolution + Lazy by RabidChipmunk · · Score: 1

      I didn't mean to imply that we should be idle. I don't believe that the open source community is being idle. I think we're doing largely the right thing purely as a side effect of being a loose decentralized body. We put out the fires as we get to them. Each person extinguishes a small fire, or to go back to the cliff metaphor, gives a small push.

      Information kills FUD. Quiet, calm sense goes a long way to making people listen.

      What I've read seems to suggest that companies are watching the battle but most are not terribly concerned. Those that are concerned are worried about liability. If you can calm their liability fears it all goes back to the old arguments.

      Businesses are concerned about liability because they think of software as a monolithic entity. They are not used to the conglomerate nature of OSS. Businesses think they are considering Linux when they really are not. They are considering Apache, or Samba, or KDE. They don't know where one begins and the next one ends. They only know the Linux hype.

      The hype got them interested, not informed. A quiet word from a good friend can inform them. So maybe they end up on FreeBSD. They are out of the stream of Linux hype and out of the FUD. They can then experience the power of collaboration in a safe spot.

      The original question is how aggressive should we be. The question is not should we be informed, both technically and legally. Yes, we should be. We should seek council. But that does not mean we should charge out blindly like an enraged bull.

      IBM has lots of lawyers. Their lawyers say wait.

      We can get lawyers too. Some already have. Judging by the quiet, my guess is that they also said wait.

      The legal process specifically leaves time to gather facts. Our stroll to the courthouse does not give up that right. There's no rush.

      Let's help a few old businesses cross the street while we're at it. Those we don't get to will still be there after SCO (unless they aren't).

      --
      This is not a political statement. This is not legal advice. It's a frick'n Slasdot post. However: I'm Running For
  309. Amazing... by peterprior · · Score: 1

    ..and they still have this on their homepage.

    Two-faced bastards.

  310. Re:If Microsoft buys SCO, you folks are SO screwed by LibertineR · · Score: 1
    How many companies have 50 Billion in cash sitting around, and nothing to do with it?

    Hint: None.

    IBM may make more money than MS, but how much money can they afford to blow on a protracted legal dispute, instead of just forking over dough to MS?

  311. License Terms? by Bilbo · · Score: 1
    > Actually, the GPL doesn't prevent you from charging for gpl'd code.

    True enough. However, it does prevent you from removing the rights of your customers to re-distribute the code. In other words, you can charge anything you like for the code, but you can't slap a license on it prohibiting the further distribution of the GPL'ed code.

    It all depends on how they word the actual license.

    --
    Your Servant, B. Baggins
  312. time for Linus to act by Trailer+Trash · · Score: 4, Interesting

    I have to ask, and it's too bad that I'm too late to be modded up, but at what point is Linus Torvalds going to pull his head out of his ass and sue SCO for violating HIS copyrights? They are still distributing his copyrighted material, and they have decided to not abide by the terms of the GPL. $150K/incident (download) in statutory damages are waiting for him. He can own their company (literally, they can't begin to pay what they owe) and make their "IP" freely available.

    Please, Linus, take care of this festering wound. It's not going away.

    Michael

    1. Re:time for Linus to act by grolschie · · Score: 1

      Yeah isn't "Linux" a registered trademark of Linus Torvalds?

    2. Re:time for Linus to act by Anonymous Coward · · Score: 0
      He can own their company (literally, they can't begin to pay what they owe) and make their "IP" freely available.

      If SCO were to lose, their assets would be auctioned off to pay the judgement. Linus would not get any of SCO's intellectual rights.

  313. New SCO story image please... by peterprior · · Score: 4, Funny

    Can we please have a DarlBorg image (similar to the Microsoft story image, but with the obvious difference).

    Thanks :)

    1. Re:New SCO story image please... by peterprior · · Score: 1

      Made one :)

      Product of 15 minutes of boredom: DarlBorg!

      and a slashdot story icon here

      :)

    2. Re:New SCO story image please... by miffo.swe · · Score: 1

      That man looks like a car salesman or someone belonging to the pirayah club from Ernie.

      He makes me think about American Psycho, dunno why,

      --
      HTTP/1.1 400
  314. This has happened before.... by AilleCat · · Score: 1

    Uhh guys, this has all happened before, think USL vs CSRG/UCB. IN fact I think some of the aim here is to smear Linux's good name like it did with BSD. But honestly I think the momentum and the current players make that a fool's gambit.

    Meanwhile, when is SCO gonna go after BSD? ;)

    --
    FreeBSD The Power to Serve
  315. What I am afraid of ... by wizardmax · · Score: 1

    ... is that even if (almost) all of us believe that SCO is full of _____, there are many corporate execs who will go along with the stupid licensing bid, and that will give credibility to SCO's claims, valid or not. But worse yet, is the impact it can have on the acceptance of Linux in the corporate environment. As a recent Netcraft survey showed, linux is loosing some web server market space to MS. I am not saying that all of the loss is due to the SCO issue, but I am sure that some is, and that is not acceptable.

    --


    Free speech is getting expensive...
  316. SCO = Terrorists by Anonymous+Custard · · Score: 1

    SCO are terrorists, trying to hurt the USA economy, and they must be stopped, even if it means suspending their constitutional rights for a little while. They want to start charging money for free software, charging companies that can barely make ends meet as it is? They're trying to terrorize our nation. Off to Cuba with them.

    1. Re:SCO = Terrorists by Anonymous Coward · · Score: 0

      'A renowned expert Dorothy Denning defined cyber-terrorism as "unlawful attacks and threats of attack against computers, networks, and the information stored therein when done to intimidate or coerce a government or its people in furtherance of political or social objectives". R. Stark from the SMS University defines cyber-terrorism as " any attack against an information function, regardless of the means"'

      Could SCO's claim be considered a threat of attack? Hmmm...

      Except taken from here: http://www.crime-research.org/eng/library/Cyber-te rrorism.htm

  317. Mmmm, Sherry Casks by Anonymous Coward · · Score: 0

    Time for wee dram to calm the nerves from all the FUD that's been flying.

    Where is that Bowmore Darkest?

  318. Derivative Works? by Anonymous Coward · · Score: 0

    How are deriative works defined? SCO seems to take a broad definition of any kernel feature that has been added to the original source not just enhancements to the original functions?

    How can they claim to own Linux's implementation of SMP, or RCU, or NUMA support, etc ???

  319. Re:Unbelieveable! - Believable! - 0-0 by Exatron · · Score: 1

    Yes, they do need to provide proof. Linux is a Unix clone, but SCO still has to prove that their IP is actually in Linux. Making something that is functionally similar to another party's product is not a violation of their IP.

    --
    "I think so, Brain, but 'instant karma' always gets so lumpy." - Pinky
    "Decepticons FOREVER!!!" - Ravage
  320. I contributed code. Slashdot, please help by Anonymous Coward · · Score: 0

    I contributed code for three device drivers. They are distributing *my* code without permission or compensation. When the code was under the GPL, I was compensated because any changes to my code was added to it and it was also advertising of my skills to potential customers (I'm a consultant). I haven't done it yet, but if the need arose, I could have relicensed my own code (without GPLed additions from other people) and to any proprietary vendor I wish for extra cash. While I wouldn't get 1 million for it, I could get several tens of thousands (if I licensed per unit). This GPL-proprietary dual licence business model does work (e.g. OpenOffice/StarOffice, GPLed Qt/propietary Qt, MySQL/proprietary MySQL, Berkeley DB/proprietary Berkeley DB), so I have a case.

    If the Slashdot sets up a registry of Linux contributors and the sections of code they contributed. I'd register and be willing to ask for 10K in a class action lawsuit. Linus, Andrew Morton, Alan Cox, and Reiser, have at least contributed 10 million dollars value each (if they decided to relicense their code for a properietary Unixes or proprietary products, they'd easily get that much in licensing fees, especially if they sold it to Microsoft).

    Once we have such a registry in place and add up the total amount owning, I'd be willing to bet that a class action lawsuit would easily be filed for 2 billion dollars.

    To be honest, this is even bigger than Linux. If SCO succeeds in violating the GPL, it puts the business models of every GPL/proprietary dual-licensed company on the planet. If that isn't a multi-billion dollar lawsuit, I don't know what is.

  321. Re:If Microsoft buys SCO, you folks are SO screwed by b29651 · · Score: 1

    No really M# would have all kinds of DOJ people after them if they bought SCO the party would turn very interesting then

  322. Re:is there a certainty we'll even ever see the co by schon · · Score: 1

    Has anyone comtemplated that SCO will have granted by the court in the SCO/IBM case a provision to seal this portion of the case on the basis of trade secrets?

    No, because it's ludicrous.

    The entire Linux kernel, including any alleged infringin code is publically available. It's therefore not a secret. (Hint - if everybody know something, then it's not a secret.)

    the development community may never see the actual code, and only learn the result of the lawsuit, making it extremely difficult to "clean up" the current codebase of infringing material!

    Any such ruling would get the (senile) judge that issued it thrown off the bench. Let's see: "You violated the law, and therefore must make amends, but we're not going to tell you what it is you did." Maybe you've heard of a small document called The Constitution that prohibits this?

    if IBM ever decides to settle the case

    IBM can't decide to settle. First, they've done nothing wrong (SCO's refusal to tell anyone where "their" code is is proof of this). And second, it would encourage every dying coroporation in the country to sue them.

    SCO may demand to keep the code secret under an NDA.

    And then what? SCO just lets the whole thing drop? Unlikely.. eventually they're going to run up against someone who A) will stand and fight, or B) will remove the code from the kernel, which everybody then uses.

  323. Check out Emperor Norton. by Population · · Score: 2, Informative

    www.sfmuseum.org/hist1/norton.html

    All SCO has done so far is talk a lot.

    In Germany, that got them into trouble.

    SCO can sell any "license" they can get idiots to buy. Whether such is worth anything depends upon the outcome of the court case. SCO can claim that they own anything and everything.

    It all comes down to whether the court will support their claim when they try to get money from someone for selling or licensing what SCO claims they own.

    Until that point, they're just like Norton.

  324. My opinion of the call by mec · · Score: 4, Informative

    Sontag didn't speak at all.

    Boies spoke a little, but mostly basic stuff. Such as: a copyright owner doesn't have to register the copyright until it's time to file a lawsuit.

    McBride's main points are:

    SCO registered the copyrights from Novell. This gives them a lot more legal ammunition. Before, this was just a contract dispute from IBM. Now, they are opening up another "front" (he used that word) -- everyone who runs Linux is infringing. They can go after people who run Linux, not just people that SCO has pre-existing contracts with.

    It's all about enterprise, SMP, RCU, and so on. It's about Linux kernel 2.4, not linux kernel 2.2.

    SCO is not interested in pursuing individual home Linux users at this time. They are very interested in pursuing enterprise SMP users. They are not pursuing source code distributors such as Red Hat at this time.

    SCO's proposition is: buy a license for UnixWare 7.1.3, and it comes with a covenant from SCO that they won't sue you if you run Linux. They are currently in negotiations with many many companies to sell these licenses. These licenses are run-time binary licenses.

    There was complicated discussion in Question #13, Jonathan Collins, VNU, about the GNU Project and the GPL. I would appreciate if anyone could post a word-for-word transcript for that. The part I got was Boies saying that the UnixWare license "... does not provide protection for people who touch the source code." and McBride said "right".

    McBride said that the literal copying, which they've been exhibiting, came mostly from Unix vendors other than IBM.

    McBride sees SCO as the rightful owner of the "Unix on Intel" market. His position is that Linux usurped that position by offering "Unix on Intel for free", and that Linux did so illegally by copying code from Unix.

    My take on all this ...

    Remember that SCO makes a lot of money from their SCO Source program (funded by Microsoft and Sun). It accounts for 40% of their revenus and ALL of their profit. In fact, the only profit that SCO has made in their entire corporate history comes from this program. They don't have to win the lawsuit, they just have to throw enough mud at Linux so that Microsoft and Sun will keep cutting them checks.

    Also, SCO is not really an independent company. Canopy Group controls SCO. Canopy chose the legal strategy and the lawyers for this initiative. So it's not like SCO is betting the company ... Canopy is betting SCO Group, and if they lose, they have other companies. They'll just buy some more IP and continue their long-time campaign of IP litigation. It worked for Caldera International + DR-DOS (which they bought) and they are trying again with SCO Group + Unix (which they bought).

    (Hey, remember Jeff Merkey and the Timpanogas Research Group, which was developing NTFS and Netware-related software for Linux? Guess who bought them out? Canopy Group.)

    This time around, Canopy isn't going for a pure legal strategy. Legally, their case has big holes in it, such as their distribution of the Linux kernel source after they had actual knowledge of its alleged infringing contents; plus their lack of specific notice to Linux users. Canopy is also going for a strategy of intimidation: buy a $1500 license or we will drag you into the mud.

    But most centrally, Canopy is going for a PR campaign. They already took $8 million to the bank from Microsoft and Sun to wage this anti-Linux campaign, and they expect to collect another $5 million this quarter (McBride estimated $8 million on the last quarterly earnings call, but he has revised the number downwards since then). That's why the legalisms don't matter. Whatever convinces your department manager to put Linux on hold and run Windows or Solaris instead ... that's what matters. That's what SCO Group gets paid for.

    1. Re:My opinion of the call by MuParadigm · · Score: 1

      Interestingly, the Canopy Group also owns a Linux company, Linux Networx .

  325. ACs don't have foe lists. by RabidChipmunk · · Score: 1


    ACs don't have foe lists

    --
    This is not a political statement. This is not legal advice. It's a frick'n Slasdot post. However: I'm Running For
  326. Well.... by mormop · · Score: 1

    Here's my 10p's (15c) worth:

    Dear SCO I'm not interested in your offer because:

    a) You have yet to prove in open court that the code you claim is yours. Until a definite state of ownership is decided it is unreasonable and possibly illegal for you to demand payment with threats for goods that may not even belong to you.

    b) You were distributing the Linux kernel on your site up to 3 weeks after you announced you believed the disputed code was included. Had you pulled this code on the day of the announcement I would have probably listened. However, by providing a GPL'd kernel for download after stating your belief that your code was included you accepted the GPL and surrendered all rights to charge for your code.

    c) If, and I doubt it, you win the court case, I wil be removing my current Linux installations from my machines and will be replacing them with versions in which the offending code has been removed by the kernel developers. This, like step a), is a reasonable thing to do and in complying immeadiately with the courts decision I do not think you will be owed anything.

    d) I do not live in the US and I do not intend visiting the US at any point in the future. If you wish to come to the UK to sue me and more like me I promise you this much: I do not own my house, car, or anything else in my posession. I am unemployed and have a minimal income since losing a finger in an accident leaving me with nothing to lose should I be on the receiving end of a court case. As McDonalds discovered, there is little more dangerous to the reputation of a global corporation than a pissed off "true believer" with a point to prove, financial backing from anti-globalisation organisations and time on his hands. McDonalds spent four years in court, won a limited battle but lost the PR war and came out of it looking like a bunch of burger munching litigation monkeys. I have nothing to lose but will gain a hell of a lot of cred in the open source arena.

    e) After the revelations over non-existent WMD in Iraq, the number of people outside of the US who believe that your country is the spreader of freedom and democracy as opposed to a global empire building, cash hungry bully is growing and I'm afraid that the kind of brainless behaviour you are displaying is only going to strengthen anti-American sentiment. Our beloved Prime Minister is on the verge of getting it in the neck and GWB is going to find that people who kiss arse that deeply are a once in a lfetime thing so if you want to help fuck up your countries reputation please continue to so.

    Nuff said

    Bollocks to the lot of you,

    --
    Hmmmmmm..... Deep fried and look like Squirrel.
    1. Re:Well.... by Anonymous Coward · · Score: 0

      "After the revelations over non-existent WMD in Iraq, the number of people outside of the US who believe that your country is the spreader of freedom and democracy as opposed to a global empire building, cash hungry bully is growing and I'm afraid that the kind of brainless behaviour you are displaying is only going to strengthen anti-American sentiment. Our beloved Prime Minister is on the verge of getting it in the neck and GWB is going to find that people who kiss arse that deeply are a once in a lfetime thing so if you want to help fuck up your countries reputation please continue to so."

      Fuck off and die. Right after you destroy your current government with lies pushed by true believer communists at the BBC. I can't see why your are such a hatefull bunch over their in the UK?. Isn't enough we have found 1000's of graves many of women and children who were tortured to death by Saddam and the Bathists party. Do you think his governments removal could have been negotiated? The real Experts on the ground over there are finding lots. They are going through mountains of paper and locating all the bit and pieces of Saddams WMD programs. They are finding it too. You are not seeing it in the press because the press want Tony Blair and George Bush out so they can get back to wrecking demoracy. You and the rest of Nevil Chamberlands can sit on your hands and let the next Hitler lay waste to Europe and the middle east because it insults you false and worthless sensibilities and morality. How much nerve agent in the hands of a madman are you willing to tolerate? Stupid but fuckers.

    2. Re:Well.... by mormop · · Score: 1

      Did I say I agree with them? No I didn't, you just shifted into braindead rant mode assuming, in your blind, base instinct reaction that I was stating it from personal belief.

      Funnily enough, this kind of blind rage inspired lashing out at anyone you perceive to even vageuly disagree with you is exactly the kind of accusation that the Anti American lobby accuse your country of.

      Before you go off telling people to fuck off and die i suggest you at least make an attempt to read the meaning and context in which they make a statement.

      The reason I refer to TB as "our beloved prime minister" is that the UK tech market is soooo fucked up at the moment that I and 56,000 other contractors are on the welfare at the moment because dipstick features doesn't understand the world of IT yet seems to think he's doing a great job. I don't like him but not for the reason you think it's just we were promised super-highway britain and got the equivalent of a dirt track..

      BTW I think Rittalin or prozac would be a good buy on your next shopping list as to be honest you sound mentally unstable, bordering on dangerous.

      --
      Hmmmmmm..... Deep fried and look like Squirrel.
    3. Re:Well.... by mormop · · Score: 1

      I can't see why your are such a hatefull bunch over their in the UK?.

      You ain't so friendly yourself

      --
      Hmmmmmm..... Deep fried and look like Squirrel.
  327. Best Comment Ever by Mansing · · Score: 4, Interesting

    "I don't see it as something that should incite an enterprise Linux customer to do any more than they did last week," he said. "The threat level increases a bit, but mainly because the perception that SCO is a psycho killer, not that the case has changed."

    Jonathan Eunice, Illuminata Inc., Nashua, N.H. in ComputerWorld
    (Emphasis mine)

  328. Wrong, wrong, and wrong again by FreeUser · · Score: 2, Insightful

    You are wrong on so many counts one is forced to wonder if you aren't an astroturfer for SCO, or one of their underwriters such as Sun Microsystems or Microsoft, or just woefully uninformed.

    First, the fact that SCO still has a Linux dist. on their FTP server is not evidence of anything.

    Wrong. It is evidence of the 'smoking gun' variety that they are doing one of the following

    1) Legally distributing GPLed code
    a) any Caldera contributed code is likewise GPLed and legal
    b) Either there is no misappropriated code present or they have implicitly chosen to GPL it.
    2) SCO is willfully and knowingly violating copyright, as violating the GPL (or disregarding it) means that regular copyright law applies, and they have no right to distribute any code but that which they wrote (which excludes virtually everything except that contributed by Caldera, if anything).

    Either way, it is certainly evidence of 'something.'

    The end users are in no way bound by the GPL, they are just in violation of SCO's copyright.

    The end users most certainly are bound by copyright law, and are thus not permitted by default to download (ie. 'copy'), much less use the software in question unless they adhere to the GPL. Therefor, end users are REQUIRED by law to adhere to the GPL if they make any use of the software (including the Linux kernel itself). This includes SCO and anyone else.

    Understanding that point, SCO is free to license their SysV code to linux users. Linux users are free to use it.

    Yes, but in the extraordinarilly unlikely event that there is SCO code in Linux, users are NOT permitted to violate the GPL OR SCO's license. The two are incompatible, so the user in question must chose to adhere to one or the other (guess which one wins? Yup, the GPL, as SCO's contribution, if any, won't a working kernel make).

    IBM is potentially in bad shape, legally and in damages. Of course, this is all assuming that their is merit to SCO's claim that their code was placed in Linux.

    The world is in dire straights, assuming the claims of Osama bin Laden and your local suicide cult have merit. The fact of the matter is that SCO consistently provides absolutely no evidence of any of their claims, and has continued to do so for months, while the Linux development process has been in contrast very transparent and well documented. You have more chance of being right by joining the local suicide cult than you do by suggesting these fraudulant attorneys have any shred of legitimacy in their arguments. Indeed, the court filing papers underscore just how lacking their case really is, and how empty their bellecose assertions vis-a-vis Linux copyright really are.

    That really isn't important. Even if SCO were 100% correct, they themselves would be willfully guilty of copyright violation, and while everyone might have to switch to FreeBSD from Linux (unlikely in the extreme), SCO would be buried under copyright suits of their own, and will not stay in business regardless. Their day is over, they have become little more than stooges for Sun Microsystems and Microsoft, and their passing is loud, noise, and annoying, but ultimately of little lasting interest. They do not own the copyright on Linux, they have no legal basis to license code they do not own, and once this stock bubble collapses there is a very real liklihood that most of their leadership will be in court, quite possibly followed by prison.

    --
    The Future of Human Evolution: Autonomy
    1. Re:Wrong, wrong, and wrong again by sdawara · · Score: 1

      Yes, but in the extraordinarilly unlikely event that there is SCO code in Linux, users are NOT permitted to violate the GPL OR SCO's license. The two are incompatible, so the user in question must chose to adhere to one or the other (guess which one wins? Yup, the GPL, as SCO's contribution, if any, won't a working kernel make).

      Out of curiosity,
      So how can we be sure about this? I would like to know more. Are you predicting a legal path given that the extraordinary circumstances are true? Do you have an example of a case settled in this manner?

      --
      Santosh Dawara
    2. Re:Wrong, wrong, and wrong again by bnenning · · Score: 1
      The end users most certainly are bound by copyright law, and are thus not permitted by default to download (ie. 'copy'), much less use the software in question unless they adhere to the GPL.


      Minor nitpick: you don't have to agree to the GPL in order to simply use a piece of software. It only comes into play if you copy the software in a manner normally prohibited by copyright law. (17 USC 117 says that "copying" to RAM in order to run software is specifically not infringement). However, by redistributing Linux, SCO has implicitly accepted the GPL, as without it they would be in violation of copyright law.


      once this stock bubble collapses there is a very real liklihood that most of their leadership will be in court, quite possibly followed by prison


      One can only hope.

      --
      How to solve most of our problems: 1.Lots of nuclear plants. 2.Cure aging.
    3. Re:Wrong, wrong, and wrong again by FreeUser · · Score: 1

      So how can we be sure about this? I would like to know more. Are you predicting a legal path given that the extraordinary circumstances are true? Do you have an example of a case settled in this manner?

      I think you misunderstand.

      Virtually every (if not in fact every) copyright case has been settled in this manner: the copyright holder has the right to require anyone copying their work to adhere to their license, which can be quite restrictive (in contrast to the GPL) and anyone so copying the product is required to adhere to that license or forego copying the product. Since copying is required to use software (i.e. it must be downloaded, copied to disk, copied to memory, etc.), any use of GPLed software requires adherence to the GPL. Ditto for any SCO software and associationed SCO license.

      When I say the 'GPL wins', I mean that:

      1) a user cannot mix the two incompatible licenses (and code) together: they must by law forego one or othe other (or use them independently of one another, not as one combined product).
      2) Foregoing SCO code is a lot easier than forgoing Linux code if one is running a GNU/Linux system. Whatever code Caldera contributed and may now be trying to rescind, or whatever system V (non-BSD) code is in the linux kernel (almost certainly NONE, but for argument's sake lets pretend it is >0 lines), is going to by a tiny fraction of the overall kernel. To have a working kernel an end user will find it far easier to remove the offending SCO code (if any, again, probably there is none) than to start with the few hypothetical code fragments SCO might lay claim to and build a working kernel from that.

      Ergo, any sane end user sticking with Linux will chose to forego the SCO code and license in favor of the GPLed code and license. I.e. 'the GPL wins.'

      I did not mean that the SCO license would be eradicated by the GPL necessarilly, although given SCO's behavior in distributing the Linux kernel up through this moment (and continuing to do so in knowing and willful violation of the GPL if it does in fact contain SCO code they are unwilling to license under the GPL) that could very well happen (assuming there is any SCO code in the kernel).

      Most likely there is no SCO code in the Linux kernel, and SCO is not violating the GPL by distributing it. If they do distribute binaries only they will be in violation, but technically shaking people down for unnecessary licensing fees is, while certainly fraudulant and perhaps illegal, quite possibly not a GPL violation if in fact they distribute the code with any binaries.

      It is a fine line they are walking, and one that will almost certainly destroy them in the end. But, as this is clearly a stock scam and not a long term business strategy, I doubt they really care.

      --
      The Future of Human Evolution: Autonomy
    4. Re:Wrong, wrong, and wrong again by RevMike · · Score: 1
      You are wrong on so many counts one is forced to wonder if you aren't an astroturfer for SCO, or one of their underwriters such as Sun Microsystems or Microsoft, or just woefully uninformed.

      I assure you I am none of the above.

      [The fact that SCO still has a linux dist. available for download] is evidence of the 'smoking gun' variety that they are doing one of the following

      1) Legally distributing GPLed code

      a) any Caldera contributed code is likewise GPLed and legal

      b) Either there is no misappropriated code present or they have implicitly chosen to GPL it.

      2) SCO is willfully and knowingly violating copyright, as violating the GPL (or disregarding it) means that regular copyright law applies, and they have no right to distribute any code but that which they wrote (which excludes virtually everything except that contributed by Caldera, if anything).

      Either way, it is certainly evidence of 'something.'

      It is only evidence that SCO judges that the particular version available for download is free from infringement. You don't actually believe that distributing 2.2 version of something under GPL automatically waves your proprietary rights to anything that appears in future versions? SCO argues that their IP began to show up in 2.4 kernels. That is why today's announced licensing plan applied to kernels 2.4 and up. Go back and read the articles.

      The end users most certainly are bound by copyright law, and are thus not permitted by default to download (ie. 'copy'), much less use the software in question unless they adhere to the GPL. Therefor, end users are REQUIRED by law to adhere to the GPL if they make any use of the software (including the Linux kernel itself). This includes SCO and anyone else.

      Read the GPL closely. Especially paragraph 2-b. You can do basicly anything you want with GPL software as long as you don't distribute and publish it. You can link it with proprietary code. You cannot publish or distribute GPL code linked with proprietery code.

      [I]n the extraordinarilly unlikely event that there is SCO code in Linux, users are NOT permitted to violate the GPL OR SCO's license. The two are incompatible, so the user in question must chose to adhere to one or the other (guess which one wins? Yup, the GPL, as SCO's contribution, if any, won't a working kernel make).

      Again, read the GPL. Users can mix and match all they want. RedHat and Debian can't publish it. That is a violation of the GPL, and - interestingly enough - the kernel developers would have rights to sue RedHat, Debian, et al. Also interesting, if the kernel does contain SCO code, the GPL is invalidated and the users could not legally use linux.

      The fact of the matter is that SCO consistently provides absolutely no evidence of any of their claims, and has continued to do so for months, while the Linux development process has been in contrast very transparent and well documented. You have more chance of being right by joining the local suicide cult than you do by suggesting these fraudulant attorneys have any shred of legitimacy in their arguments. Indeed, the court filing papers underscore just how lacking their case really is, and how empty their bellecose assertions vis-a-vis Linux copyright really are.

      Wanting it to be so won't make it so. Do you really know the inner workings of IBM enough to guarantee that they didn't do anything unscrupulous. Do you trust that the judge is going to have enough expertise to properly assess the isues? I don't. SCO is playing a bellicose PR game, but their legal game is much more measured.

      That really isn't important. Even if SCO were 100% correct, they themselves would be willfully guilty of copyright violation, and while everyone might have to switch to FreeBSD from Linux (unlikely in the extreme), SCO would be buried under copyright suits of their own, and will not stay in business regardless.

    5. Re:Wrong, wrong, and wrong again by sdawara · · Score: 1

      Thank you for your reply,

      I think you misunderstand.

      I just have not been able to bring my question in a clearer light.

      As you pointed out, assume that there is SCO code in the Kernel. While you have described clearly how for the end user (corporate or otherwise) it's smarter to simply stick with foregoing the SCO code, I am more interested in the legal implications of having used that kernel in the first place. In other words, what is the strength of SCO's claim that everyone who has used Linux (2.4), is a software pirate and can be sued or turned into a potential licensee.

      For one, the user had no idea that this was the case and therefore in all fairness should have another alternative.

      Can the end user then avoid litigation by simply foregoing the SCO code? As far as I know, SCO have been mum about this, but they have mentioned somewhere to the effect that if someone were to go and try to remove tainted portions, you would get kernel 2.2. I think the statment refers to the fact that the code in question is now integrated with the kernel and eliminating it will be difficult. They do not mean it to be an alternative to litigation or buying a license.

      In any case the point is moot from the smaller perspective, or this particular case (I agree with your last 2 paragraphs). I was just curious about the 'rules of engagement' itself.

      --
      Santosh Dawara
    6. Re:Wrong, wrong, and wrong again by Anonymous Coward · · Score: 0

      You are 100% right on.

      These fraudulant attorneys in question espcially Boies have in the past tried to steal in broad daylight.

      They are the Whoresons of Perdition.

    7. Re:Wrong, wrong, and wrong again by FreeUser · · Score: 1

      I just have not been able to bring my question in a clearer light.

      For one, the user had no idea that this was the case and therefore in all fairness should have another alternative.

      Indeed they do. For SCO to collect any damages whatsoever they MUST show the offendor what code is in violation, so that the offendor has an opportunity to cease and desist in the infringement.

      Failure to do so, as SCO has done, constitutes "dirty hands" and means they are entitled to absolutely zero damages under the law.

      Can the end user then avoid litigation by simply foregoing the SCO code? As far as I know, SCO have been mum about this, but they have mentioned somewhere to the effect that if someone were to go and try to remove tainted portions, you would get kernel 2.2. I think the statment refers to the fact that the code in question is now integrated with the kernel and eliminating it will be difficult. They do not mean it to be an alternative to litigation or buying a license.

      They don't have a choice, by law. At some point they either put up or shut up. However, since all of the allegations have been public PR, and none of them present in any court filings, the point is moot. They can scream and threaten, but until they show the world what the offending code is and provide an opportunity for one to cease infringement, they have absolutely no claim and no right to any damages, from anyone.

      Once they make the allegation official, and provide evidence of the allegation, it is a simple matter to remove the offending code (or refute the allegation, if, as would likely be the case in such a scenerio, the Linux code were written first and added to SCO later, i.e. SCO is the pirate, not Linux, or the code came from IBM and was contributed to AIX and Linux, which might be a violation of IBM's license with SCO (but again, probably not) but is certainly not a violatino of copyright, given that IBM owns the copyright to the code they have written).

      Obviously this assumes there is infringing code lurking in the kernel, which is extraordinarilly unlikely.

      --
      The Future of Human Evolution: Autonomy
  329. Something to think about ... by Lord+Stroud · · Score: 1

    Well, I've read most of the replies here, and I would like to give a weird example, which is related, and you tell me what you think.
    I used to study in the Technion in Israel, which states that any type of research or development that a student does, is owned by the Technion itself.
    Now, imagine that you go about and create this really cool distributed computing tool, or an ultra-fast SQL server that would put Oracle out of business. You go about and create a website for your project, in it you distribute documents and code from your project, cause it's a scientific project. Basically, the project is owned by the Technion, but anyone can access it. Now, imagine that a SCO employe goes about and gets into the site, reading about the cool things, and decides: "WOW, that would really fit nicely in our code". Then, takes the code, puts it in, and uses it. Now, we have a funny situation, the code made by the SCO employe is based on a FREE piece of code, which by law, is owned by the Technion. Is the Technion now allowed to ask royalties from SCO? Is the Technion allowed to ask royalties from ALL THE LINUX USERS IN THE WORLD??? Something to think about, no?

    A Call to arms: I call to all the computer science geeks and students out there, download the code, and compare any pieces of the code that SCO refers to any academic code in your university. Find a simple piece of code that would be similar to what SCO wrote, and boom, the law suit is gone, cause they stole the code from someone else. Bring enough evidence and cases, and the US court will make mince-meat out of them.

    --
    L.S.
  330. Re:If Microsoft buys SCO, you folks are SO screwed by arivanov · · Score: 1

    Then it will become a matter for the regulators almost immediately. That is the reason why MSFT is bying fake licenses and not doing it themselves.

    --
    Baker's Law: Misery no longer loves company. Nowadays it insists on it
    http://www.sigsegv.cx/
  331. Re:I'm glad I never fought for freedom... by semios · · Score: 1

    I'm glad I never fought for freedom because some oppressors would inevitably try to come and take it away again. And that would make me seriously pissed off.

    If the mere thought of protecting your freedoms (digital or otherwise) presents so much of a burden to you that it prevents you from making a contribution, you probably don't have the wherewithal to make a significant contribution anyway.

  332. From an investor's point of view by einhverfr · · Score: 4, Interesting

    A binary only Linux license is SOFTWARE PIRACY.

    Exactly. You beat me to it. Now how to appeal to investors:

    1: File a class action lawsuit on the behalf of all kernel developers against SCO accusing them of software piracy, breach of contract, et. al.

    2: Publicize the GPL and that SCO distributed Linux under the GPL for some time *after* they filed the complaint with IBM.

    I have sympathized with Linus for staying out, but now, I think it is time for he and every other kernel developer to stop software piracy.

    --

    LedgerSMB: Open source Accounting/ERP
    1. Re:From an investor's point of view by Zelatrix · · Score: 1

      It's tempting, very tempting, but I think it would be a counterproductive thing to do.

      It would be playing into the hands of the fudmongers. If the rumours are to be believed, the current shenanigans are already causing some businesses to be wary of further Linux adoption (note that I said "if": I don't necessarily believe that to be the case). Would more lawsuits flying around help? Depends whether you think there is any such thing as bad publicity I suppose.

      It's as plain as my nose that SCO have one goal and one goal only: to maximise the amount of generated heat and publicity. Look how they release their material in carefully timed dollops, to enormous fanfare. Look at how, when this material is examined more closely, there is very little substance to it. Now look at the substantive evidence behind their claims ... oh!

      They're relying on the hot air. When the hot air runs out, the SCO balloon will deflate. Don't play their game.

    2. Re:From an investor's point of view by Arker · · Score: 1

      On the other hand, if you're going to sue them, you need to do it before that hot air baloon deflates - otherwise you'll never see a penny. They don't have any actual assets, you know.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    3. Re:From an investor's point of view by twivel · · Score: 1

      This whole situation sucks, but your suggestion here just won't work.

      For them to be in violation, they would have to be actively distributing Linux without providing the source code under the GPL. They are no longer distributing Linux.

      The only way they would be in violation of the GPL is if a past customer was given the binaries and not given the source code. That customer would have to request (within 3 years) a copy of the source code - and pay for the reasonable costs for media and delivery of the source code. If they refused that request, then they would be in violation of the GPL.

      But most distributions provide both the source code CD-roms as well as the binary cd-roms with every purchase, so they are off the hook if thats the case! (Did they do this too? I'm not sure)

      In this case, they aren't telling you "Pay us for a binary only copy of Linux" either. They are saying "Buy a copy of UnixWare and we won't hold you accountable for using our proprietary code!"

      Just my 2cents.
      --
      Brian

    4. Re:From an investor's point of view by cHiphead · · Score: 2, Insightful

      If their code is in a GPL'ed program, they know about it, they must request to have that code removed, or accept the General Public _License_ for their code, as required by the GPL. They are absolutely in violation of the GPL by claiming part of a GPLed program is theirs and must be seperately licensed, all else they can do is sue the developer that put the code in (IBM?) and request it be removed. Its a twisted and confusing issue for sure, but they are violating the GPL by leaving the code in and seperately requesting license fees.

      All it would take is to email Linus a copy of the files that are in violation and tell him 'the following lines are copyrighted by us, please remove lines 38-89, 82-84, etc from your code, and since your such a nice guy, please don't go around posting the exact lines we asked you to remove, have a nice day'

      how hard would that be. they have no legal grounds and should actually be getting hit with cease and desist letters from Linus or any of the developers(and ESPECIALLY corps like REDHAT) whose code might be affected. they are blackmailing unknowing companies with fud.

      --

      This is my sig. There are many like it, but this one is mine.
    5. Re:From an investor's point of view by arkanes · · Score: 1

      Several things: one, in an official press release, they claim that using Linux is piracy, Straight up. That's defamation, right there. Second, you can't legally distribute Linux in binary-only form and comply with the GPL. Since what SCO is offering is binary only runtime licensing for Linux (I'm not totally clear on this, it LOOKS like it might be a license to run Linux under UnixWare, which is... useless), then there's no legal way for ANYONE to sell Linux, not even SCO. Which is a win for them.

  333. Re:If Microsoft buys SCO, you folks are SO screwed by nitehorse · · Score: 1

    I really don't think that IBM has anything to worry about as far as cash reserves go.

    It's one of the classic blunders! The first of which is never get involved in a land war in Asia. The second of which, and only less well known, is never get involved with a Sicilian when death is on the line. And the third, of course, is never get involved with IBM over an IP dispute!

  334. Funny optical illusion by markomarko · · Score: 2, Funny

    The Caldera logo beside the post also looks like a silhouette of Mickey Mouse's head on a red globe. I think I smell another copyright lawsuit.

  335. Funny ANTI SCO Wallpaper... by VXD_Error · · Score: 1

    Surfing around about anti SCO sentiment and found a link to this wallpaper. http://www.angelfire.com/crazy2/funkybrewster/Anti _SCO_Wallpaper_1600x1200.jpg

  336. SCO has NO chance in court by Retired+Replicant · · Score: 2, Interesting
    Isn't this the same thing as if you bought a bunch of building materials from a supplier at price X to build your house with, and then the supplier returns after the house is built to say that they goofed and some of the materials they sent you were more expensive extra-super-duper materials and you need to pay them X+$1500 to make amends (for their own mistake) or else stop living in your house?

    Now, I think any court in the land would say that the supplier's claim is at best a laughable bunch of hooey if the supplier actually made an honest goof (it was their own fault for being careless). However if it could be shown that the supplier knew ahead of time that the extra-super-duper materials were being sent but said nothing to the customer about it until after the house was built, a court would call that fraud and possibly extortion on the part of the supplier.

    Also, imagine that you make the generous offer to the supplier to return the extra-super-duper materials and replace them with other materials of your own choosing. However, the supplier refuses to identify which materials are the extra-super-duper ones so their is no way for you to return them and replace them with other materials. In this case any court would order the supplier to identify the extra-super-duper materials and give you the chance to replace them with other materials. If the supplier refused to identify the materials, the court would throw it's case out in about 2 seconds (and maybe fine them for wasting the court's time).

  337. Re:The GNU/GPL is probably unenforceable in this c by Anonymous Coward · · Score: 0

    If they win the big one, the "linux is a derivative" claim (unlikely given the precedent set in the BSD case), then they would be within their rights to overrule Linus and change the license to the 2.4 kernel.

    I do not believe that the courts would purport to award SCO ownership of copyrights on works created by people in no way involved in the case and without any representation.

    I guess it's conceivable that the court would award SCO control over IP that would otherwise belong to IBM but that's the limit. The idea that SCO can sue IBM and be awarded control of works created by me or you or anyone else that they aren't suing is without foundation.

  338. World Domination Strategy by 4of12 · · Score: 1

    build up its case for world domination

    And like many such strategies, they're doing a lot of saber-rattling.

    Many of us wonder just what length saber it is that SCO really has.

    --
    "Provided by the management for your protection."
    1. Re:World Domination Strategy by DanBrusca · · Score: 1

      It's a lightsabre. Some people may be a little awestruck by it, but ultimately it's all for effect.

  339. Re:Nevermind, an explanation why they haven't acte by Error27 · · Score: 1

    I know the FSF owns copyrights for some of the Linux kernel. I think IBM assigned their s390 code to the FSF...

    It will be interesting to watch the fun. :)

  340. Sounds like it ought to be illegal. by Anonymous Coward · · Score: 0

    Sound to me like this practice ought to be illegal.

  341. Has anyone told the SEC ? by Anonymous Coward · · Score: 0

    http://newsforge.com/comments.pl?sid=31552&cid=564 83

  342. DMCA? by imipak · · Score: 1
    >I'm sure this must be in a FAQ or been answered elsewhere, could someone explain to me please?

    The **AA IP cartels routinely use the DMCA to issue some sort of legal paperwork straight to ISPs, saying "We believe your user, Joe Kazaa, is illegally distributing our copyright works. Please remove their website / net access under DMCA." - and the ISP is legally compelled to do so *without any due process*. Now many here are asserting that SCO are now in breach of copyright law; by breaking the GPL, they lose their right to distribute GPL'd works *at all*. So why doesn't some US-based author of stolen GPL'd programs get an order to force SCO to (at least) suspend distribution of GPL'd work, pending the outcome of the court case? That would also cover selling these junk paper "licenses" to Linux, hopefully hitting the stock price. This hasn't happened, so presumably there's a good reason why... anyone?

  343. This is *not* barratry by siskbc · · Score: 1
    However, seeing as SCOX has distributed, and does distribute, linux, frightening people who don't pay up for a license with legal action, even though they've been granted a boatload of rights under the GPL already is barratry. Barratry is not legal. Nor is extortion, what this amounts to.

    That's not even close to the legal definition. "Barratry" gets thrown around a lot on slashdot, but have fun finding situations where it was actually used successfully. "Using a lawsuit to screw the little guy" doesn't meet the burden. In fact, it wouldn't work here because there haven't *been* any lawsuits, and if they don't win against IBM, there won't be. If they do win, then it won't be barratry because they'll have a very good case.

    And you might believe that the whole GPL case makes this so obvious that the result is extortion, but until this gets decided they have the right to sell licenses to their IP, and it only makes sense to indemnify their customers. They have no relationship with non-customers, by definition, so no one is actually being extorted.

    What they're not doing is going up to someone and saying "buy this now or we'll sue you." - even though that wouldn't even be blatant extortion if worded correctly. They're making an open offer to companies to buy their product and indemnification. That's nowhere near the legal requirement for extortion, and if you believe it is, I'd love to see some case history.

    SCOX is obviously threatening whoever they think they can get away with threatening; a fishing expedition.

    Gee, kind of like Microsoft's action through the BSA, huh? I never saw any barratry or extortion suits there, either. The problem is that, yes, you and I know that this is basically extortion, in the vernacular sense. Unfortunately, it's not legally, and it's not enough to qualify for barratry either. Check out the results of the DirecTV suit recently - that claim of extortion got nuked pretty quick. Bottom line is that what you seem to believe in terms of this case is not consistent with case law, though I would also love to see SCO get nailed.

    --

    -Looking for a job as a materials chemist or multivariat

  344. Who is going to take them to court to fight it? by ProteusQ · · Score: 1
    Who is going to take them to court to fight it?


    One word: RMS

    1. Re:Who is going to take them to court to fight it? by Rock+Ridge · · Score: 1

      Is rms capable of this?

      What do the FSF financials look like?

      Has the FSF conformed to the requirments that it has to conform to in order to be and to continue to be a non-profit?

      Is any of the FSF GNU code "derived" from AT&T code? The author of gcc appears to have been familar with the pcc code from UNIX.

  345. Copyright registration by TechLawyer · · Score: 1

    Unlike patent and trademark applications, which are examined by someone, copyright applications are simply rubber-stamped by a clerk. Literally. When you want to copyright something, you fill out a one-page form, and attach it to what you want to copyright. You mail that to the copyright office. A clerk copies the one-page form, stamps it, and returns it to you. I could copyright The Phantom Menace if I wanted. (But why would I want to?) Whether that registration will hold up in court is an entirely different question.

    1. Re:Copyright registration by Anonymous Coward · · Score: 0

      For all we know those 20 pages that were filed for copyright by SCO could have been recipes for cookies.

    2. Re:Copyright registration by TechLawyer · · Score: 1

      Hopefully they would be tasty. Although I doubt it.

    3. Re:Copyright registration by Jayfar · · Score: 1

      or FUDge brownies.

  346. Code Copyright by Exousia · · Score: 1

    Before any code can be used as evidence in a lawsuit, the code must be registered with the US Copyright Office as a matter of course. Basically, the courts say "don't waste our time unless you at least have a registered copyright." Of course, merely having a copyright proves little.

    --

    --Slashdot: News for Turds. Stuff that Splatters.
  347. one strategy by jefu · · Score: 2, Insightful
    Anyone else wonder if SCO's strategy might well be to just keep making these claims to boost stock prices, sell as much stock at those prices as they can, then go into court, present a cheezy case and lose.

    Then, just in case IBM tries to countersue, declare bankruptcy quickly and go away.

  348. This guy's brave. by Lux · · Score: 2, Funny


    When I try to manipulate the stock market, I make sure to do it as an AC.

  349. Re:Unbelieveable! - Believable! - 0-0 by Jack9 · · Score: 1

    Let's just ignore the fact that it looks nearly identical from the command line or uses the same apps that were designed for unix or any of a number of small jumps that unix made and everyone else adopted relating to permissions and mail....a product that is similar is exactly why there is IP. The fact that I can make a linux box loose taste smell and feel like a Unix box should be demonstrative enough for most judges. (like Sonyy Walkmen, looks similar ENOUGH)

    --

    Often wrong but never in doubt.
    I am Jack9.
    Everyone knows me.
  350. May not find it anyway by Exousia · · Score: 1

    And when they do become public, you might not be able to find what you're looking for if the copyright holder is a trustee of some sort.

    --

    --Slashdot: News for Turds. Stuff that Splatters.
  351. What about BSD by Acrimonious+Coward · · Score: 1

    How does this affect BSD which is not a System V clone? Does SCO have any kind leverage on that OS?

  352. It's "suit" not "suite"... by Anonymous Coward · · Score: 0

    ...you illiterate, uneducated maggot.

  353. The problem i see by Namaseit · · Score: 1

    Well this is the problem i see. Linux is a collaboration of work. In the end yes it is one project but there hundreds of pieces that thousands of people have put in. SCO cant lay claim to that work that was done with those pieces. They can only lay claim to the piece they *may* or definately may not be theirs. You see the problem is that they dont own the TCP/IP stack of Linux. They dont own ext3 support in the kernel. They dont own SMP support in the kernel. They dont own IPv4 and IPv6 support in the kernel. They dont own ACPI ability in the kernel. They dont own Virtual Memory in the kernel. They dont own the IP to any of that. That was written by people and GPL'ed for the kernel, legally. If any thing, they *possibly* own 80 lines of code 1/3 of which is probably comments. So who gives a fuck. They cant license parts they dont own. That is illegal and they will get seriously fucked if they think RedHat, Suse, Mandrake, IBM and the literally millions of people who use Linux arent going to give up a little cash to crush SCO and forever end the doubt about someone elses code in the linux kernel. Linux has its whole existence documented in view of the public. There are books about its general history. There are CVS logs of who added what. Linux can prove anything it needs to. SCO on the other hand is hiding itself behind shadows and closed doors and its history with UNIX is not only confusing but questionable. They cant license anything but the code they own and they cant license code they dont own. And the list above they dont own, so they cant license it or they can be sued by the original people who wrote it for breach of the GPL. SCO is fucked plain and simple and the fact that they have shown absolutely no evidence to the public means that they are full of shit. If their case is so fucking air tight why do they have to hide it. Because its not thats why.

    --
    75% of all statistics are made up!
  354. Re:MICRO$OFT paid SCO to start it !!! by sinserve · · Score: 1

    I wanna go to Hawaiii, Yeeeey!

  355. Clear evidence that their goal is FUD... by Kazoo+the+Clown · · Score: 5, Interesting

    This is just something to milk for a press opportunity. As has already been pointed out, all registering a copyright does for you is attach a date to a submission, and nothing else-- it does not prove that you own the rights to the submission, merely that you claimed to have at a given time. It's up to the courts to sort out what that means. Anyone can register anything.

    The fact that SCO has turned it into an important event shows that their strategy is based on continued FUD in the marketplace. What better way to bully some Linux users into paying license fees? If the FUD subsides, they lose their leverage in that regard. So expect an announcement of some kind by them periodically, when interest and concern about the issue wanes, just to keep their name in the news in an attempt to fan the FUD flames. Pathetic, really.

  356. Why not sue over stolen Linux source in Unixware? by kroyd · · Score: 4, Interesting

    Apparently it is possible to install ext2 support on SCO Unixware 7 and newer. (See http://www.sco.com/skunkware/COMPONENTS.html for version 7 information)

    According to someone who used to work for SCO (or Caldera) it is a good possibility that this support is based on code stolen from Linux: linux kernel posting. IMHO the Linux community should be allowed to examine this code, and if it is found to disregard the copyright the remaining Unixware code should be examined closely.

    As it apears that US copyright law is based around "give lawers as much income as possible" I imagine that there is plenty of precedence for suing a company over this, but certainly press released should be issued, and all SCO customers should be made aware of their (possible) rights under the GPL to Unixware source.

    Oh, and the Canopy group should be mentioned as well: They owned 68% of SCO before the first press releases in March, but just a few days later stated in a SEC filling that they would start selling off stock. It shouldn't be too hard to show that it is possible that this is simply a ploy by the Canopy group to boost share price while selling out.

    (With the stock at 13$ up from a .60$ low last year they might already have made more from selling at 13$ than they might have made from selling their entire holding at around 1$.)

  357. Can we see it? by Paul+Johnson · · Score: 4, Interesting
    Does this mean we can go and look at it?

    (Or to be more precise, could someone in Washington DC go and look at it?)

    If so, could someone please take a look and note down some search strings to grep the Linux kernel for? This could be the way around the NDA to figure out what bits of Linux they are going to claim to own.

    Paul.

    --
    You are lost in a twisty maze of little standards, all different.
    1. Re:Can we see it? by LittleVito · · Score: 1

      As far as I know (I'm not an IP lawyer... yet) it means that the copyright office has the option of entering it into the Library of Congress, and therefore, in some instances, you can view it at the library. However, most registered items are usually discarded after the registration is granted simply because the library lacks the storage capacity. Assuming, however, that it is brought into the library (I don't know their policy on computer code/software), you would have to be physically at the LOC to view it because they do not usually post material to the web, and as a matter of policy do not allow material to be checked out.

    2. Re:Can we see it? by mpe · · Score: 1

      it means that the copyright office has the option of entering it into the Library of Congress, and therefore, in some instances, you can view it at the library. However, most registered items are usually discarded after the registration is granted simply because the library lacks the storage capacity.

      A problem other copyright libraries face with hugely long copyrights. Let alone that with individual authors modern copyright law is an administrative nightmare since the "clock" dosn't start until they die.

  358. This is ridiculous by Anonymous Coward · · Score: 4, Interesting

    I am going to use an analogy for this.

    Let say SCO wrote a book called Unixware. They give IBM the right to edit the book and to then publish that book. IBM changes the name of that book to AIX and sells it to the to anyone that wants to buy it. If IBM decides to contribute some of the book that SCO originally wrote as their own work into another book who is going to be sued IBM, the publisher for the new book or the person that bought the book and read it?

    On top of it all SCO is saying that because so many people have read the book that no other books on this topic can be written unless royalties are paid to them because they provided all the inspiration.

    We all know that this wouldn't work. I mean come on they don't want to tell us because then we would comply with the law and remove the offending code then they don't have a business model. How many businesses do you know that make you pay for something that you are using without telling you what it is you are using.

  359. instead of lawsuits, why not rewrite by proxy? by zpok · · Score: 1

    OK, so nobody knows the exact lines that would have been copied (by people other than IBM it seems), but don't you all have a pretty good idea?

    Why not start a workgroup to create XXXprocessor support for linux from scratch?
    Or make alternative distro's and bounce them of the head of these SCO lawyers until they're bullshit-free?

    Then make those available as publicly as possible as open source and include it in every new build from then on.

    Is this possible?

    I know, the grown-up thing to do is to ignore the snots, but me thinks this stuff is starting to affect the market, not to mention a lot of good people's good work ...

    Cheers

    --
    I think, therefore I am...I think.
    1. Re:instead of lawsuits, why not rewrite by proxy? by RevSmiley · · Score: 1

      The real grown up thing to to is take McBride out with the rest of these SCO greed heads and just eliminate the scoundrels. Give up on going to court with these loosers. They are attempting to steal that which isn't theirs. We will get no fair play in court. They will buy all the justice they need and Linux will get none. Bastards like McBride his compatriots and his whoreson attorney Boies have sick and twisted minds.

      All you pacifists need to wake up and get a grip on this shit. Violence does solve certain issues. These thieving fucks are a waste of human skin and need to be removed from the gene pool. They are a threat to civilization and the commonwheal. Death to the tryants. Let us get us some rope and proceed in community action!

      --
      As you can see I don't care about my karma.
  360. copyright by jefu · · Score: 1
    I bet that 99.9% of this code is already copyright, and SCO can't go re-copyrighting it.

    I believe that the law says that the code is copyright as soon as it is registered, or published for the first time. And that copyright is by the author.

    It seems to me that there are four major possibilities for linux kernel code :
    -- It was written and posted to the kernel mailing list, or put online by a linux contributor. In which case the copyright does not belong to SCO. Dates for this should be verifyable by the lkml mailing list, or other mailing lists, or by web archives.
    -- It was written by an SCO employeee and they have verifiable proof of that fact (something that seems a bit tough to me - would a timestamp on an SCM system work? I can suggest several ways to fake that. ) And has been kept completely secret. In which case it belongs to SCO and since it was kept secret, can't be in the kernel. So SCO claims against the kernel are baseless.
    -- Neither of the above can be proved completely. In which case I can't see how SCO can claim ownership. This might occur if the date on their code and the date of first publication are very close or the same. If there is good evidence of this code being published by a non SCO employee, evidence that SCO produced it on that date or even a day or two before would be very suspect in my eyes (imagine setting the time on the SCM server to be a week behind the real date).
    -- It was written by an SCO employee, can be proved to be written by an SCO employee and was deliberately (a very interesting notion) or inadvertently included in code that is otherwise GPL'ed. In which case I think the GPL should take precedence.

    The burden of proof on SCO seems pretty high to me.

  361. What infringement by 16K+Ram+Pack · · Score: 1
    I can't believe this guy.

    We haven't even got to the stage where SCO have proven their claims, and he's talking about giving prosecution exemption to companies who pay them.

    Well, DON'T pay them. At least not until they've won a court case proving copyright infringement.

    Darl, take someone to court, or shut the fuck up!

  362. I find it amazing that by Anonymous Coward · · Score: 1, Insightful

    a corporation can attempt to claim ownership of code that was written by what may be thousands of individuals.

    Shouldn't the government at some point step in and put an end to this ?

    Doesn't it make sense that even if it were true that a few hundred lines of code belong to SCO that developers would be given the fair chance to eliminate those said lines instead of company just outright highjacking the rest of the codebase ?

    Where the FUCK is justice in this country!

    1. Re:I find it amazing that by EmagGeek · · Score: 1

      Pay attention

      They're not claiming ownership of all of linux. They're claiming ownership to their own code which they claim has become part of linux without their permission.

      The reason they won't tell us what code is infringing is because they want to scare everyone into buying a SCO license first, because once the evidence comes out in court, 2.6.0 will not have any of the infringing code and linux will be IP-safe. However, all of the companies who bought SCO (like idiots) will have already given SCO their blood money.

      1. Cry foul and sue the biggest guy you can see
      2. Threaten everyone who runs linux
      3. Refuse to disclose your evidence
      4. Scare everyone into buying your software
      5. Profit....

      Nothing missing in this one.

  363. hmmm....analogy by MoFoQ · · Score: 1

    SCO = "Anna Nicole Sm!th"

    Of course, SCO gives "Gold-digging" a bad name.

  364. But, by their theory they DO NOT have authority... by TheConfusedOne · · Score: 1

    ...to release and distribute the software under the provisions of the GPL.

    The GPL very clearly states that if code cannot be freely redistributed then it cannot be distributed at all. SCO has explicitely stated that they have valid copyright claims over the Linux kernel and intend to exercise them. The minute they make a statement like that then the GPL is invalid according to them and they lose the right to distribute.

    However, they CONTINUE to distribute to this day. (And have even recently updated their distribution of the kernel).

    ftp://ftp.sco.com/pub/updates/OpenLinux/3.1.1/Se rv er/current/SRPMS
    linux-2.4.13-21S.src.rpm 5/9/2003 5:51:00 PM
    (Emphasis added)

    This is the part where it gets really messy.

    --
    --- I wish I could hear the soundtrack to my life. That way I'd know when to duck.
  365. Acting In Good Faith? by 16K+Ram+Pack · · Score: 1
    No, acting in good faith would be to do the following:-

    Notify the users/distributors of the software of the infringement. Get together with the infringer and suggest a settlement of "stop distribution"/remove offending code and pay a financial settlement.

    If the infringer doesn't play ball, sue them.

    That is the 'good faith' approach. SCO have not taken this approach. If they have the evidence of infringement, they should sue IBM, or shut up.

    I'm curious as to why SCO are not taking legal action RIGHT NOW. They have the evidence, and can serve papers on IBM right now.

    I hope those considering buying SCO stock are asking the same question.

  366. OK, Linux on Intel=Bad, what about Linux on PPC? by zpok · · Score: 1

    I've snipped an interesting comment from apple.slashdot (ars technica IBM G5 interview).
    Why interesting: it seems some people want to claim ownership of Linux on INTEL.
    That's what was said in this interview, right?

    So does their copyright or whatever apply on PPC?

    "...
    Improvements to GCC? (Score:5, Interesting)
    by Realistic_Dragon (655151)
    (...)

    At one point in the interview it looks like IBM and Apple are working together on GCC improvements and donating the code back to the FSF.

    This is a fairly big deal as people have pointed out before that GCC on PPC isn't as hot as it should be, but with that kind of muscle and money behind it it should go forwards by leaps and bounds.

    With the new GCC improvements it looks like Linux on those new, remarkably cheap, P970 IBM boxes is going to be a real winner. And AFAIK Gentoo already runs on PPC fine - no one is going to be bitching about compile times with 4 1gig+ CPUs crunching away at it!
    (...)
    "

    --
    I think, therefore I am...I think.
  367. Re:About $800,000 in the last couple of months . . by Sanga · · Score: 1

    This page is more readable --

    http://biz.yahoo.com/t/s/scox.html

  368. Legal defense by Anonymous Coward · · Score: 0

    It looks like primiry target of SCO is not people but companies (of course !). So, some legal defense formula can shield it's CEO and sure them about Linux using. It can be something like this: I use system and code with GPL of somebody but not SCO. Any problems SCO should resolve with that guys first. If SCO proves it's claim then... we will take some steps agains that "pirates" (but I do not believe SCO can prove it).

  369. It had to be done.... by scifience · · Score: 0

    http://www.scifience.net/images/sco.png Take a look at SCO's "new and improved" website, as designed by me!

  370. Re:But, by their theory they DO NOT have authority by Xerithane · · Score: 1

    The GPL very clearly states that if code cannot be freely redistributed then it cannot be distributed at all. SCO has explicitely stated that they have valid copyright claims over the Linux kernel and intend to exercise them. The minute they make a statement like that then the GPL is invalid according to them and they lose the right to distribute.

    SCO is obviously acting as the ostensible authority towards releases of their software, including OpenLinux. SCO has acknowledged the usage of their copyrighted code and released it, thereby agreeing to the terms of the GPL. SCO saying that they do not agree to the GPL, and then doing it, doesn't matter. Actions speak louder than words. However, it's all up to what the court decides...

    Do you have any idea when is this actually going to start going to trial?

    --
    Dacels Jewelers can't be trusted.
  371. Faith No More by Anonymous Coward · · Score: 0

    I do not trust in humanity's capacity for good, and I know for a fact that corporations have no capacity for good. Even if they do good, it is for their own selfish agenda; this cannot be characterized as truly good. This saying is true: 'the heart of humanity is deceitful and desperately wicked; who can know it?'. When SCO starts lying and then has to make a bigger lie to cover up/explain/obfuscate the preivous lie, remember these words.

  372. Finally, the answer! by incom · · Score: 1

    Before: 1) Write linux kernel code. 2) Liscence under GPL. 3)???? 4)Profit! Now: 3) Sue SCO.

    --
    True genius is grasping a situation like a peice of fruit, and peircing it just right so that it drains dry.
  373. Re:The GNU/GPL is probably unenforceable in this c by Lonath · · Score: 2

    change the license to the 2.4 kernel.

    IANAL, But: No way. Even if they win, all that will have shown is that the 2.4 kernel = 2.2 kernel (which does not infringce SCO copyrights t?) + SCO code.+ other stuff.

    Therefore, 2.4 kernel must be relicensed in such a way that ALL licenses agree. Since the 2.2 copyrights are under the GPL, the ONLY license that can work here is the GPL. If they say they don't want their code distributed under the GPL, then the 2.4 kernel can't be used at all.

    So, their indemnification is really stupid. I don't know if they realize it, but if they lose, their customers wasted money paying off SCO, and if they win and put the 2.4+ under GPL, then why bother paying. And if they win and demand a change to the license, then the 2.4+ kernel users can't use the code anyways since the GPL will kill it. :P Stupid stupid stupid.

  374. Funny how... by Sam+Williams · · Score: 3, Informative

    ....there isn't much insider buying happening with SCOX, especially now that we know the company stands to make billions.

    It's like a stock analyst once told me: An insider sale can mean anything -- low confidence, a new pool in the backyard, college tuition for the kids. A buy means only one thing -- somebody on the inside sees the company doing well over the long haul.

    1. Re:Funny how... by jcr · · Score: 1

      A buy means only one thing -- somebody on the inside sees the company doing well over the long haul.

      Either that, or that somebody on the inside thinks he can make more money on the company's stock between now and his next opportunity to sell, which comes up twice a year.

      Not all insider buying is for long-term investment.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    2. Re:Funny how... by stoborrobots · · Score: 1

      I suppose the point is that there is some opportunity to make money.

      If they buy, it's because they expect the price is going up sometime... And they're in the best position to know...

      It matters not whether we are talking the short term or the long term...

    3. Re:Funny how... by Sam+Williams · · Score: 1

      Not all insider buying is for long-term investment.

      Too true. Those insiders who buy for the short term, however, face Darwinian pressures of the Elliot Spitzer/Bill Lerach variety ;)

  375. Re:MICRO$OFT paid SCO to start it !!! by Anonymous Coward · · Score: 0

    as early as 1993 microsoft corporation owned 19% of SCO, then called santa clara operations because of its location, which has subsequently changed, ergo SCO only.

    SCO has been the single largest distributor of multiple unix flavors for a long time and MS had their hands in the pie from the beginning.

    of course MS was behind the scenes ~ they are paranoid of losing WIN to LIN which is already beginning to happen.

    its been obvious all along.

    peace

  376. Look around.... by Genetically+Enginerd · · Score: 4, Interesting

    Where are the bucks to put up a defense for Linux?

    IBM has no stake, they don't distribute Linux. They contributed; they push Linux compatible hardware; but they don't sell Linux. Same with HP and SUN.

    The FSF could care less. They don't hold the copyright on Linux because Linus didn't sign it over

    Even RedHat bailed out by making 9.0.3 a project instead of a product.

    What will SuSE and Mandrake do? Will they follow in RedHats' footsteps?

    So, SCO says (paraphrased) if we do happen to win this lawsuit, USERS (BIG, commercial USERS with deep pockets) are going to be the target. Pay us now or pay us later and the premium for this ext^H^H^Hinsurance is one UnixWare license for each of your CPUs that is currently running Linux. In return, if we win, we won't sue you; ever. If we lose, you get to keep the UnixWare licenses!

    --
    Does the income I've derived from working with Unix belong to SCO?
    1. Re:Look around.... by rjamestaylor · · Score: 1
      • Even RedHat bailed out by making 9.0.3 a project instead of a product.
      Inflammatory BS. RedHat still sells its RHAS and RHES products. They didn't bail out of anything by opening their distribution development process.
      --
      -- @rjamestaylor on Ello
  377. Re:What RMS and the IBM Legal Dept. Are Waiting Fo by digitect · · Score: 1

    Yes, yes, you're exactly right. The silence is killing us SlashDotters, but I think we all just need to wait this out.

    --
    There is no need to use a SlashDot sig for SEO...
  378. Yes and no... by Svartalf · · Score: 1

    If you'd been following the BS going on in Yahoo!'s SCOX board, you'd see that the informed ones are the ones posting Strong Sell and putting forward the facts of the case. The Strong Buy's are doing pretty much nothing more than flametrolling...

    While I admit Yahoo!'s boards are not indicative, I do believe that the ignorance of all the details is what is driving up the prices.

    --
    I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
  379. I believe SCO could succeed here... by adiposity · · Score: 3, Interesting

    ...but I'd like to be proven wrong. IANAL.

    So far, I have seen a few arguments as to why SCO could not possible get away with this. For the sake of argument, let's assume SCO is telling the truth about the copyrighted code. Their claim, while dubious, is probably not entirely without merit.

    1. SCO released a GPL distro of Linux which necessarily GPLs any source code of their own which was included.

    Why it doesn't matter:

    SCO themselves did not insert the code. They simply redistributed a source package which already contained their code before it came into their possession. A judge is probably going to look at this claim and dismiss it outright. Let me illustrate with an example

    If I work for Microsoft, steal some code, create a free Unix driver for WinFS, and distribute it, this creates a copyright violation for the users. If MS provided this to Solaris users (even with mods) on their website afterwards, it is very doubtful that a judge would suddenly declare the stolen code in the public domain. The fact that MS participated in the public code license doesn't suddenly indemnify all the users of the proprietary code of a copyright violation.

    At this point, MS would almost certainly be able to sue users of the code, as well as me for releasing the code. I can hear some of you crying out, "But SCO went one further! They kept distributing the code even after they 'discovered' the violation." This is true; in fact they are still distributing the code, although this may be accidental. I'm sure you can find the SRPM link somewhere around here. Let me explain why this doesn't matter:

    SCO is going to claim that they were not the ones to insert their proprietary code into Linux, IBM was. Therefore, it isn't their responsibility to take it out. In fact, they allege that they still are not aware of the extent of the violation. It's not as if SCO received a clean GPLed version of Linux, added their proprietary code, rereleased it under the GPL, and now expect payment for their code. What they have done is participate in a "good faith" way in the GPL license, adding code and releasing it under the GPL. If the code they received wasn't GPL, however, it isn't legally their fault, but the fault of the individuals who added it originally. SCO doesn't immediately give up their rights to their code just because they added GPLed code to a non-GPL product.

    SCO doesn't bear responsibility for the code getting into Linux. Therefore, releasing Linux under the GPL doesn't GPL any unauthorized code simply because SCO is the owner. I would say a judge would probably consider the GPL violation to have occurred when IBM inserted the code, not at SCO. SCO can probably keep releasing Linux under the GPL without giving up the rights to their code, because the violation occurs before them in the distribution stream.

    If it is a GPL violation for SCO to release their distro (which is doubtful), then they will have to deal with that. But, if it is, it is also a violation for every single other Linux distro. Therefore, even if this particular claim is correct, it damns all distros along with SCO's. It would mean ANY distributer such as RH, Suse, etc., could be sued at any time by any of the copyright holders of the Linux source code. Surely, this isn't the victory the Linux community is seeking. It makes more sense to leave the violation where it allegedly occured: namely, at IBM. Everyone else (including SCO) can then begin releasing a legal version of Linux as soon as possible.

    In essence, SCO is not GPLing their code by rereleasing it under the GPL. They are only GPLing it when they primarily release it under the GPL. I sincerely doubt a judge would set the precedent of allowing unauthorized code to be GPLed by the owner simply for redistributing it.

    SCO may be found in GPL violation for knowingly redistributing GPL code which shouldn't have been. Most likely,

    1. Re:I believe SCO could succeed here... by schon · · Score: 4, Insightful

      SCO themselves did not insert the code. They simply redistributed a source package which already contained their code before it came into their possession. A judge is probably going to look at this claim and dismiss it outright.

      I disagree. It's highly unlikely that a judge would dismiss this outright, unless some other defendant didn't show up.

      This is true; in fact they are still distributing the code, although this may be accidental. I'm sure you can find the SRPM link somewhere around here. Let me explain why this doesn't matter:

      I'm still waiting for your explanation of why it doesn't matter.

      SCO is going to claim that they were not the ones to insert their proprietary code into Linux, IBM was. Therefore, it isn't their responsibility to take it out

      This is completely irrelevant. It doesn't matter who put it there, and it doesn't matter who's responisibility it is to remove it. What does matter is that while it's there, NOBODY CAN DISTRIBUTE IT, INCLUDING SCO. The only thing giving SCO the right to distribute the Linux kernel is the GPL, which SCO is implicitly agreeing to by continuting to distribute the code.

      Simple three part question.

      Is SCO aware of the requirements of the GPL?

      Is SCO aware of "their" code in the kernel?

      IS SCO DISTRIBUTING IT?

      The answer to all three of these questions is YES

      Therefore, it's highly likely that a judge would simply throw out SCO's assertions that the GPL doesn't apply. THE ONLY THING GIVING SCO THE RIGHT TO DISTRIBUTE THE KERNEL IS THE GPL. AS SCO IS CONTINUTING TO DISTRIBUTE "THEIR" CODE, THEY ARE AGREEING TO THE GPL.

      it is also a violation for every single other Linux distro

      What "other distributions" are doing is irrelevant - "other distributions" are not claiming that they have proprietary code, and "other distribitons" are not suing to stop one another from distributing the kernel.

      SCO can easily claim that it is literally impossible to legally replace the code; the kernel is so tainted now that any replacement code would simply be another violation. The only solution is for these companies to pay SCO what they owe.

      Bullshit. You're trying to tell me that something can not be replaced? AT ALL ?!?!?! What have you been smoking?

      And even if it's "impossible" to legally replace the code or not, the fact is that SCO hasn't told anybody where it is even when explicitly requested. By not doing so, SCO is saying that "their" code is worthless to them.

      You have a very long troll - it's too bad you're not smart enough to actually make it convincing.

    2. Re:I believe SCO could succeed here... by adiposity · · Score: 1

      I disagree. It's highly unlikely that a judge would dismiss this outright, unless some other defendant didn't show up.

      In a case against SCO, perhaps you're right. But we're talking about a case against Linux end users. The question is whether the fact that SCO distributed said code under the GPL (having NOT placed it there in the first place) indemnifies the end users. I'm saying I don't think it does. Is there a case against SCO for distributing Linux under the GPL, knowing it shouldn't have been? Perhaps. Does it protect users of other distributions? Doubtful.

      Is SCO aware of the requirements of the GPL?
      I assume so.

      Is SCO aware of "their" code in the kernel?
      Clearly.

      IS SCO DISTRIBUTING IT?

      Yes.

      AS SCO IS CONTINUTING TO DISTRIBUTE "THEIR" CODE, THEY ARE AGREEING TO THE GPL.

      They are agreeing to the GPL for the code that they added after having received the GPLed code. I don't think it is cut and dry that they agree to it for their code that they didn't add. There are more questions which, although you may not consider them relevant, I bet a judge would:

      4) Did SCO put the code there, and does SCO bear the responsibility for the violation that said code being there causes?

      5) Does agreeing to the GPL mean you implictly accept that all past violations of the GPL are agreeable to you?

      The question is whether SCO's actions really constitute them releasing their Unixware code under the GPL. Unfortunately, on this point the GPL doesn't really help, because it doesn't describe what happens when Party A takes party B's code, inserts it into GPLed code, and Party B rereleases said code under the GPL. Obviously, when Party A introduced the proprietary code, the GPL was not followed, meaning the resulting code was available only under an illegal license. But, did the rerelease by Party B suddenly validate the GPL license again? Or were all derivations, including Party B's, invalidated by Party A's actions?

      I'm inclined to think the only way to fix it is to go back prior to Party A's actions and build from that point. Everything else was distributed under an illegal license, and the buyers are subject to lawsuit, as are distributors. Is SCO as guilty as everyone else? Absolutely! Does this protect everyone else from SCO's wrath? I don't think it does.

      What "other distributions" are doing is irrelevant - "other distributions" are not claiming that they have proprietary code, and "other distribitons" are not suing to stop one another from distributing the kernel.

      You couldn't be more wrong. If SCO's allegations are correct, other distributions are definitely vulnerable. They have distributed SCO's code illegally! SCO, on the other hand, will have distributed GPLed code illegally (of course, so will have every other distro).

      Bullshit. You're trying to tell me that something can not be replaced? AT ALL ?!?!?! What have you been smoking?

      Nope, I'm saying SCO will claim this. They will argue that the kernel has been tainted so badly that even if the code were removed, it would just be replaced by practically identical code, since their code would be known publically. Of course the code could be replaced, but that doesn't make it feasible. Remember, this is in the context of "mitigating losses." Just because SCO didn't tell everyone which code was illegal doesn't mean they didn't try to mitigate losses.

      In reality, the code doesn't need to be replaced--it simply adds functionality that wasn't there in 2.2. The question is whether identical functionality would be possible w/o SCO's code. The answer is probably 'yes' but SCO will argue that it never would have been written that way if their code hadn't been there in the first place. In other words, the new kernel has been crafted around SCO's code, and therefore any replacement will by necessity resemble SCO's code, which they would consider anothe

  380. oh no? Tell it to James Cameron by Charles+Kerr · · Score: 1
    Interesting example, given that the makers of the Terminator movie found themselves sued by Harlan Ellison for making a story that resembles a plot where robots take over the world.

    Cameron finally wound up paying Ellison $144,000 and adding Ellison to the credits.

    From Sci-Fi Wars:

    Harlan Ellison, notorious and prolific author, critic, reviewer, screenwriter and revenge artist is probably the last guy in the world you want to piss off. No, I mean, really. This is the guy who mailed a dead gopher to New American Library when they refused to release copyright on his books after they breached their contract by binding cigarette ads into them. One wonders, then, what was going through James Cameron's head when he casually quipped on-set that he got the idea for Terminator "by ripping off a couple old Outer Limits episodes." Specifically, Soldier and Demon With a Glass Hand, both written by Ellison (others have pointed out marked similarities with still more Ellison stories, including A Boy and His Dog and I Have No Mouth and I Must Scream). Ellison called Cameron on this, and Cameron denied it, and Ellison responded with both a lawsuit and a series of full-page ads in Variety that lambasted Cameron as a plagiarist. Eventually, Cameron settled for a reported $72,000, and Ellison's name was appended to the credits in the home-video edition. But Cameron still hadn't learned his lesson! In 1991, a new video-release of Terminator dropped Ellison's credit, prompting yet another lawsuit and yet another $72,000. To this day, mentions of Ellison's name reportedly throw Cameron into a white-hot rage.
  381. End of the world? by Anonymous Coward · · Score: 0

    Too many times the fight has come down to this.. again the strike for freedom in development and trually measuring people for there capabilities not the one good (backed) idea! This is only the begining, SCO will probably fight this one in the hope they will win, backed by companies who just hope they will fight the fight until winning no longer matters. Linux is a great operating system, as capable as its competitors, but in the end US capitalism will fight to kill that with its need most (eager, intelligent injections of hope)

  382. Who's next by PhilTR · · Score: 1

    First IBM, then Linux. Can MicroSoft be far behind?

  383. Won't work. by Svartalf · · Score: 1

    The people buying aren't ON the boards for the most part. That's a fact.

    What WILL stop SCO dead in its tracks is a handfull of infringement suits filed against them. The more, the merrier. After all, they are STILL distributing the Linux kernel in violation of the terms set forth in Clause 4 of the GPL. They've been doing it for over seven months now .

    What you need is to see the kernel coders sue SCO into oblivion.

    Now, THAT is something I'd fund in a heartbeat.

    --
    I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
  384. At least, they don't have the wheel by PeteQC · · Score: 1

    Phew, an Australian already has patented the wheel, so SCO won't be able too...

    Following this announcement, all car makers stock dropped by 22% ;)

    --
    Montreal - Best city to live in!
  385. Re:"We would prefer licensing to litigation," McBr by Jeremy+Erwin · · Score: 1

    Actually, the deposition requirements are limited to the first and last 25 pages of source code, reproduced in a visually perceptible form, together with the page containing the copyright notice. (Source.

  386. grep -Ri dynix (?) by MrWorf · · Score: 1
    Maybe I'm not doing this right, but...
    ha@evangelion linux $ grep -Ri dynix *
    ha@evangelion linux $
    Didn't work as advertised. Didn't he state (in the interview) that this should turn up some evidence? That even in the copyright on the headers in the linux kernel, I should find some statements about Dynix? He even referred to Sourceforge if I remember correctly.

    I'm using kernel 2.4.21_pre7 (with Gentoo patches). Anyone else found it?
  387. bang it out by pair-a-noyd · · Score: 1

    ftp://ftp2.caldera.com/pub/

  388. Re:What RMS and the IBM Legal Dept. Are Waiting Fo by jrumney · · Score: 1
    as has been pointed out above, they are still distributing the source from their ftp site, so they are still in compliance with the gpl.

    It is a violation of the GPL to knowingly distribute GPLed works linked with non-GPL compatible works. So either SCO are making baseless claims which they have no intention of following up, or they are currently in violation of the GPL. Everyone else who is distributing the Linux kernel has the defense that SCO has not yet made their claims known, and by continuing to distribute the code themselves are giving a clear signal that there is no reason to stop distributing it.

  389. Re:"We would prefer licensing to litigation," McBr by tomhudson · · Score: 3, Informative
    Their total deposit was 20 lines

    Since they are required to deposit the first 25 and last 25 pages (50, and they only deposited 20 pages in total, and one of them has to be the copyright notice page, that means they deposited their code in its' entirety.

    So now we're down to 19 pages, of which how much is comments, white space, etc?

    It's just a "modification to Unix SysV release 4.1 ES". Doesn't seem to be something important enough to get on the front page of google news, and certainly not something Linux users need to pay attention to.

  390. Better option by Hoser+McMoose · · Score: 1

    SCO loses the case when everyone figures out that the code was actually written by the open source community and then misappropriated by SCO, and the people responsible for all this bullshit are found guilty of fraud and sent to jail.

    If the justice system worked properly, this is what would happen, though it won't happen. The people at SCO are crooks. They're stealing way more money than your petty theives stealing old ladies' purses, but they're never going to treated the same way. Why not? Because the US patent and copyright law system is BADLY broken and needs some serious overhauling (the rest of the world isn't doing much better, just ask the Austrailian guy who was granted a patent on the wheel).

  391. Re:They want you to buy a SCO license for EVERY co by Anonymous Coward · · Score: 0
    Is McBride a Nigerian by any chance? Or is just a relative of those guys with the Spam Scam?

    http://www.potifos.com/fraud/

  392. Re:FSF should sue on behalf of the developers then by jrumney · · Score: 2, Insightful
    I beleive that between Linus, Alan Cox and a handful of others (companies like IBM, HP and SGI have no shortage of lawyers, and are all major copyright holders over kernel code), a majority can be found. The court is not going to insist that some guy that contributed a 10 line bug fix has the same share over the kernel as Linus, so while there might be hundreds of contributors, only a few key ones will be needed to back this.

    Yes the lack of copyright assignment will be a barrier, but not a huge one.

  393. Animation for hire? by Anonymous Coward · · Score: 0

    How much would it cost to have someone create animation in which Bill Gates takes a shit, and Darl McBride comes out?

  394. hope they go to jail by Anonymous Coward · · Score: 0

    When this is all clear and done I hope that McBride and his buddies go to jail for fraud and extortion.

  395. the scary thing is, by Anonymous Coward · · Score: 0

    that I doubt they have enough body guards on duty to really protect these assholes.

    They've really, really pissed off the planet.
    McBride is more hated than Bin Laden now..

  396. Re:very telling... by Anonymous Coward · · Score: 0

    We didn't fail, it is Linux' fault we failed.

    My god, did he really say that?

    Logic parse error.

  397. Who's codes' on first? What license is on second? by Curtman · · Score: 1

    I think the point that people keep missing here, from what I can tell, is that SCO isn't claiming that their code was put into Linux. The jist of the issue is the Unix licensing which even Microsoft would have to consider too restrictive, states that if a licensee (IBM) modifies the licensed code, then SCO or unix owner of the week then owns that modified code. They aren't claiming that their developers (or unix owner of the week) wrote the code. They are imposing some bizarre legaleaz to claim ownership of NUMA, JFS, and a bunch of others that were developed in house at IBM, which appeared in AIX (a derivitive of their code), so that now they own that code, not IBM. That's why this whole thing is so stupid. Had SysV code been copied into Linux, this would be a no brainer, and the people responsible would most likely have been ousted by the community. So what needs to be shown in court is that these things were developed exclusively (or possibly first?) for AIX, and not OS/2, which carries no such licensing because its IBM's.

    I believe this last announcement of the binary only Linux distro is the best thing for the community to come out of SCO thus far. They just shot themselves in the foot, and put themselves in the same position that Unisys was in when they sued BSD. Now they've stolen our code, and they claim but have not proven that we've stolen anything of theirs.

  398. To the parents of SCO by Epsillon · · Score: 3, Funny

    Dear Mr. and Mrs. SCO,

    Your son has been aware of our class activities for weeks now, but the date has arrived for our annual show and tell and your son has done nothing but tell.

    We were suprised at this, since young SCO has been going about the place telling everyone July is show and tell month, but unfortunately he seems to have become preoccupied with a game he calls "share inflation" with his pals in the playground, which involves helping them all share with him and then taking his own ball away at the crucial moment.

    Perhaps a meeting with the two (or one, if young SCO turns out to be the slang term he's behaving like) of you would be appropriate?

    Yours,

    Concerned teacher.

    --
    Resistance is futile. Reactance buggers it up.
  399. But what case does RH have? by phriedom · · Score: 1

    But what case does RedHat have? The way I see it, SCO has violated the GPL by claiming proprietary ownership of parts of it. Therefore, they seem so be distributing Linux without a license, and therefore violating the copyright of Mr. Torvalds and Mr. Stallman and a few hundred others.

    Maybe SCO is counting on NOT getting sued by the small copyright holders who don't have a big legal team or a litigation budget? That seems like a bad bet, considering that IBM and many other companies that have a large interest in Linux would probably be happy to contribute to a Linux legal fund.

    Then again, maybe SCO just expects that the penalties for their copyright violation will come long after the executives have sold off their stock.

    --
    Don't moderate flamebait as Troll. Know the difference or you will be Meta-moderated.
    1. Re:But what case does RH have? by mcc · · Score: 1

      But what case does RedHat have? The way I see it, SCO has violated the GPL by claiming proprietary ownership of parts of it. Therefore, they seem so be distributing Linux without a license, and therefore violating the copyright of Mr. Torvalds and Mr. Stallman and a few hundred others.

      Actually RedHat has directly or indirectly contributed a very nontrivial amount of code to linux. Alan Cox was actually a Redhat employee for a longish time, and as far as I'm aware he still is. They also for a long time provided partial financing to a decent number of open-source projects, including at least GNOME.

      RedHat really is probably one of the best examples of a company to sue SCO over something like this, which is why I mentioned them. They own some linux code, and they were responsible for a decent bit more (they could maybe even file suit on behalf of Alan Cox?), and they also have a significant financial investment in linux, meaning defamation of linux hurts them directly.

  400. Misrepresenting the FSF's opinion of the matter by jbn-o · · Score: 1
    Yes, they are in breach of contract. Licenses are contracts.

    The FSF, and Eben Moglen (chief counsel of the FSF), who wrote the GNU GPL and deal with GPL cases all the time disagree with you.

    And "IP infringment (copyright)" is wrong--the phrase "intellectual property" doesn't just refer to copyright. It's a mish-mash of copyright, patent, trademark, and a host of other areas of law that aren't always compatible. Again, the FSF disagrees with you here.

    You see the common thread there, "contract" -- in the terms of "Licensing Contract".

    The GNU GPL does not use the word "contract". There is another lawyer's analysis of this which illustrates the logic the FSF uses to show why they don't need a contract (and often don't have one anyhow) to accomplish what the GPL sets out to accomplish. The paper has some problems, but it is quite interesting as well. It also suggests a reason why it is valuable to purchase Free Software rather than getting it at no charge.

    1. Re:Misrepresenting the FSF's opinion of the matter by Xerithane · · Score: 1
      The FSF, and Eben Moglen (chief counsel of the FSF), who wrote the GNU GPL and deal with GPL cases all the time disagree with you.

      Good, I still have very little respect for the FSF. This is why:
      Licenses are not contracts: the work's user is obliged to remain within the bounds of the license not because she voluntarily promised, but because she doesn't have any right to act at all except as the license permits.

      So, lets look what a contract is:

      An agreement between two or more competent parties in which an offer is made and accepted, and each party benefits. The agreement can be formal, informal, written, oral or just plain understood. Some contracts are required to be in writing in order to be enforced. (2) An agreement between two or more parties which creates obligations to do or not do the specific things that are the subject of that agreement. Examples of a contract are a lease, a promissory note, or a rental agreement.

      The only thing the FSF is saying is that they don't call it a contract because they don't want to. If I don't want to call my car a car, it doesn't mean it isn't.

      There is another lawyer's analysis of this which illustrates the logic the FSF uses to show why they don't need a contract (and often don't have one anyhow) to accomplish what the GPL sets out to accomplish. The paper has some problems, but it is quite interesting as well. It also suggests a reason why it is valuable to purchase Free Software rather than getting it at no charge.

      You seem to miss what I am saying. I am saying that License enforcement can fall under copyright law, as well as contract law. Due to the nature of the GPL, it is easier to enforce copyright law than contract law. Shrink-wrap licensing (Which is still largely the closest example of using the GPL) is still very touchy. Copyright law, however, is very solid and sound and has a vast number of precedents to aid your case.

      And "IP infringment (copyright)" is wrong--the phrase "intellectual property" doesn't just refer to copyright. It's a mish-mash of copyright, patent, trademark, and a host of other areas of law that aren't always compatible. Again, the FSF disagrees with you here.

      That is exactly why I put copyright in parenthesis after IP infringmenet. To specify which section I was speaking of. Because IP Infringment is a common legal term, I choose to use it. Because I think the FSF has weird ideological goals, I choose to not listen to them. They can disagree with me all they want, it's their right. Just like I have a right to disagree with them.

      It doesn't change the fact that Licenses can fall under civil contract law. Another thing to note is that contract law varies between districts, unlike copyright law. Which is another advantage to pursue damages under copyright law. As for the other lawyers (the Austrialian site) paper, he is correct. However, unilateral contracts have precedence in US courts. Unilateral contracts can typically cover software licenses, as long as the license is conspicious and presented to the user for consideration with the option to accept or decline (Even if it is implied, by usage), and implied consent to abide by the terms of the license/contract.

      I really have to thank you for your response though. You are the first person offering another view that actually has backed it up with some links and references. BTW, Law is just my hobby, I love programming to much to become a lawyer.
      --
      Dacels Jewelers can't be trusted.
    2. Re:Misrepresenting the FSF's opinion of the matter by jbn-o · · Score: 1
      I still have very little respect for the FSF.

      I don't see how this is at all relevant except that it suggests you are forming opinions out of some prejudice against the FSF. I don't remember asking what you thought of the FSF but I find it telling that you would begin a response this way.

      The only thing the FSF is saying is that they don't call it a contract because they don't want to.

      Well, neither of us speaks for the FSF so we can't say for certain why they don't call the GNU GPL a contract. But I'm guessing they're probably not calling it a contract because (as you noted) they don't need to in order to defend its terms and because most of the time no positive assent is given, no meeting of the minds happens. Most people simply make GNU GPL-covered software available for the taking at no charge. Therefore one of the criteria for being in a contractual relationship hasn't been met.

      You seem to miss what I am saying. I am saying that License enforcement can fall under copyright law, as well as contract law. Due to the nature of the GPL, it is easier to enforce copyright law than contract law. Shrink-wrap licensing (Which is still largely the closest example of using the GPL) is still very touchy. Copyright law, however, is very solid and sound and has a vast number of precedents to aid your case.

      I don't miss your point at all, my reading of the material I linked to is different. I'm saying that two lawyers (one of whom--Eben Moglen--is far more familiar with relevant case law, copyright law, and the GNU GPL than either of us is likely to ever be) appear to be saying that leveraging contract law is not an option for most GPL licensors because there has been no contractual relationship established with the licensee. I don't see anything in their writings that says we're dealing with one defense being easier than the other. It appears to have to do with leveraging the only case that is available (copyright infringement) and avoiding the case that is out of reach (breach of contract).

      I look forward to seeing you raise your views with Prof. Moglen sometime and reading what he makes of it. Perhaps he'll do another ask Slashdot interview. But I won't be surprised to learn that he has better ways to spend his time than to talk to anyone who opens by declaring that they "very little respect for the FSF" then later saying that the FSF has "weird ideological goals" without saying what you understand their goals to be or how you think those goals are weird.

    3. Re:Misrepresenting the FSF's opinion of the matter by Xerithane · · Score: 1

      I don't see how this is at all relevant except that it suggests you are forming opinions out of some prejudice against the FSF. I don't remember asking what you thought of the FSF but I find it telling that you would begin a response this way.

      The FSF is notorious for using terms and labels for their own advantage. Even if the underlying truth is the same, they try to use their own terminology. I also can't stand RMS. I think he's a pretentious egotistical jerk.

      Well, neither of us speaks for the FSF so we can't say for certain why they don't call the GNU GPL a contract. But I'm guessing they're probably not calling it a contract because (as you noted) they don't need to in order to defend its terms and because most of the time no positive assent is given, no meeting of the minds happens. Most people simply make GNU GPL-covered software available for the taking at no charge. Therefore one of the criteria for being in a contractual relationship hasn't been met

      See, but it is a contract (unilateral contract) assuming that the contractual offer (GPL) has been offered (the notices while downloading, as well as the typical COPYING or LICENSE file in the package) and obviously considered and accepted due to the installation. This is still getting into shrink-wrap licensing, of sorts, which is very muttled.

      I'm saying that two lawyers (one of whom--Eben Moglen--is far more familiar with relevant case law, copyright law, and the GNU GPL than either of us is likely to ever be) appear to be saying that leveraging contract law is not an option for most GPL licensors because there has been no contractual relationship established with the licensee.

      He is saying it is difficult (If you read the foot-note, about the 5 prerequisites for contracts) for it to be excercised in that capacity. That is due to the way that most GPL'd software is released, however. If you install some packages it has a typical EULA with an Accept or Decline option, even if it is still the GPL that is being displayed. This would satisfy most of the requirements for it fall under contract law.

      It appears to have to do with leveraging the only case that is available (copyright infringement) and avoiding the case that is out of reach (breach of contract).

      Unless the software specifically prompts them, and have such proof, than it would be tremendously easier for someone to pursue copyright infringement.

      But I won't be surprised to learn that he has better ways to spend his time than to talk to anyone who opens by declaring that they "very little respect for the FSF" then later saying that the FSF has "weird ideological goals" without saying what you understand their goals to be or how you think those goals are weird.

      When Richard Stallman received the $25,000 IDG/Linus Torvalds award, he said, "This is like Luke Skywalker winning the Han Solo award." The Apache Group, EFF, and other parties have contributed more towards the "Open Source" movement than the FSF. I view the FSF as an outspoken critic of other peoples success bitter at a lack of their own.

      --
      Dacels Jewelers can't be trusted.
  401. Actually Sontag mentioned non-commercial users by kjj · · Score: 1

    Check near the bottom of this link Sontag says that noncommercial users will not need a license. I wonder who is covered under "noncommercial" I suspect that this is to avoid a legal mess of going after thousands of individuals and groups such as universities and even government agencies. I mean the NSA has their very own distribution. Although I suspect that this noncommercial use clause does not cover code modification and redistribution.

  402. 800-726-8649 by mabu · · Score: 1

    I dialed their sales number at 800-726-8649. I kept going around in circles in their voicemail. It seemed like hours - the system isn't very smart. I don't understand what happened. Maybe if more people contact them and let them know that their legal action is bad for the industry, they may get the message ; )

    1. Re:800-726-8649 by mormop · · Score: 1

      I kept going around in circles in their voicemail. It seemed like hours - the system isn't very smart. I don't understand what happened.

      SCO Unix :P

      --
      Hmmmmmm..... Deep fried and look like Squirrel.
  403. Re:very telling... by Anonymous Coward · · Score: 0

    Our Unixware product was damaged by Linux and that is why it isn't successful.

    So, given that they were distributing Linux themselves, this means they were contributing to their own failure! No wonder they need to rely on FUD.

  404. Might have found something interesting by AlXtreme · · Score: 1

    The Dynix patch mentioned in the lawsuit: http://lse.sourceforge.net/locking/rcu/patches/rcl ock-2.4.1-01.patch Thus a patch for 2.4.1, but the code isn't in the 2.4.20 linux kernel proper, well, atleast not anymore. Now the big question is: Is the code still in the kernel, and has the patch entered linux proper?

    --
    This sig is intentionally left blank
    1. Re:Might have found something interesting by AlXtreme · · Score: 1

      never mind, mod me down:

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

      --
      This sig is intentionally left blank
  405. copyright/non-disclosure/trade secret by frovingslosh · · Score: 1
    Can SCO get a copyright and still hide what they claim is the offending material behind trade secret and non-disclosure? This makes no sense at all! (not that any of the rest of it does).

    Some Linux contributer (copyright holder) needs to contact his congressman and have him get information on what was copyrighted, so that all Linux contributers can verify that SCO has not hijacked their code.

    --
    I'm an American. I love this country and the freedoms that we used to have.
    1. Re:copyright/non-disclosure/trade secret by MarkPinTx · · Score: 1

      The current rules are that you submit the first and last 25 pages of source. Since Object Oriented Programming, there are no first and last, so you just pick the 50 most innocuous lines of source and deposit that.

      One may also cite to trade secrets and obtain a "fishy" (rule of doubt) registration for the source code without disclosing any source.

      So, no, registration does not automatically inject whole code into public domain (the non-copyrightable portions anyway).

      --
      In the time of chimpanzees I was a monkey . . .
    2. Re:copyright/non-disclosure/trade secret by frovingslosh · · Score: 1
      So, no, registration does not automatically inject whole code into public domain (the non-copyrightable portions anyway).

      While copyright certainly does not move the document into the public domain, one of the stated pouposes of the copyright system is to grant exclusive ownership of the IP for a limited time , after which it does pass into the public domain. Even congress, with their continual extending of the limited time has not eliminated the concept that the copyright is given for a limited time and then the property does pass into the public domain. While I have no expectation that the code would still be of any use after the current insanely long copyrights expire, it would seem completely against the stated intent of the copyright law to provide a corporation such copyright protection, but at the same time have no provision for the work to be available to the public after the copyright protection they provided finally expires.

      Worse, it seems insane, has SCO is demonstrating quite well, to let jerks like this have a "copyright" on something that no one can know what it actually is. If they get away with this there is not much (except a Bigger group of lawyers) to stop them from telling anyone who writes code that they have already received a copyright on that code, but the code is secret and they don't have to show it!

      --
      I'm an American. I love this country and the freedoms that we used to have.
    3. Re:copyright/non-disclosure/trade secret by MarkPinTx · · Score: 1

      Well, the protection afforded by copyright is against copying. Which means verbatim or near verbatim copying. Which assumes that the work is rather easily publicly available for copying, otherwise why bother?

      The deposit requirement at the copyright office is for "identifying material" only. It is not a repository for material for people to copy when the copyright expires. And for published books, to stock the Library of Congress.

      --
      In the time of chimpanzees I was a monkey . . .
  406. Wow by salesgeek · · Score: 1


    I am rapidly coming to the conclusion that the concept of "owning" ideas is simply not in the interest of humanity.

    --
    -- $G
  407. Sounds like a marketing scheme for their products by gotr00t · · Score: 1
    UnixWare has never really been a first rate operating system, and it pales in comparison to AIX, HP-UX, and many of the other *NIXes out there. Given the choice between expensive, yet crappy UnixWare, versus verstile, cheap, and plentiful Linux, I think that most people would probably take the latter.

    Therefore, SCO has two ways of profiting from their UNIX now. They can either sue people for violating their copyright by alleging that they have misapproprated code from their OS in some way, or, they can get the money from coercing other businesses to buy licenses to their third rate operating system to use another OS.

    Either way, they profit, even if it means that they will have to tell a mountain of lies and distort a brainsick amount of facts. Clearly, these people have no morals, no ethics, only the desire for cash, even if it comes from the hard work of others.

    Therefore, they must be stopped, and very soon, before they can reap the benefits that they do not deserve.

  408. A disgrace to your country. by theolein · · Score: 1

    The behaviour of this troupe of unspeakbly arrogant SCO bosses is making a fool and a mockery of your country. Does your constitution allow a company to openly defame others without having showed any proof whatsoever? Do your laws allow any company to threaten any other company without legally proven reasons? Do your laws allow a company to damage the credibility and business performance of another without fear of being held responsible?

    In the interview McBride specifically states that this new action has nothing to do with IBM.

    Where are all the goddamn big mouth open source gurus now? Where the fuck is Linus "I don't give a fuck about IP" Torvalds? Why doesn't he stand up and fight? Where the fuck is Eric "They're wrong, I know it" Raymond and the FSF? Are they too chicken too actually do something apart from yakking away about the advantages of their fucking GPL?

    In short, when it comes to the crunch, where are all our intellectual heroes now, when we need them? Isn't it about fucking time that they came down from their clouds and realised that Linux is taking fucking water? Why don't these over zealous baboons start a legal fund to fight the case? I'd give $100 for my part.

    Excuse my cursing. I'm excedingly angry that this farce is allowed to carry on and damage what we all enjoy working on without one single respected legal word in a prominent newspaper in defense of Linux.

    1. Re:A disgrace to your country. by mabu · · Score: 1

      Welcome to America. Home of the free (as long as you pay your taxes) and the brave (as long as you have money and/or lawyers).

  409. Make Money The SCO Way by doctor_no · · Score: 1

    What's to say that I (or anyone else) can't claim that a piece of code that they contributed to Linux was missaporpriated; that it was submitted without my concent and is tainted?

    Then I could threaten to sue everyone (maybe for $3 billion, maybe even SCO), but then I could blackmail companies that are afraid of my litigation and agree not to sue them for small fee. That way, I can make money from the entire open-source communities' hardwork even though I suck and have really done nothing.

    I could be a millionare.

  410. Re:very telling... by multiplexo · · Score: 1

    Q: Earlier you said you were still a products company and not a strictly IP company. This appears to have changed and you are now an IP company. Would you agree with that assessment? Linux has succceeded while your product failed in the marketplace.

    A: Our Unixware product was damaged by Linux and that is why it isn't successful. That is why we are doing this. We didn't fail, it is Linux' fault we failed.


    Strange, I personally had thought that UNIXware wasn't successful because it lacked features of other UNICES, lacked drivers, lacked support, lacked stability and because most systems administrators would have rather been anally raped and eaten by carnivorous lepers than have to attempt to support systems running UNIXware. I'm glad that's been cleared up for me. Oh, and in other news the Iraqi minister of information announced that Iraq didn't lose the Gulf War, parts I and II but that it was the United States' fault that it failed.

    --
    cheap labor conservatives - they want to keep you hungry enough to be thankful for minimum wage.
  411. State Attorneys General by squashed · · Score: 1
    There is prima facie evidence that suggests SCO has no case.

    It is time for the Attorneys General of several states to get involved here, to get a hold of the code in question here and determine whether this is simply a scheme of extortion or worse.

  412. Re:Who's codes' on first? What license is on secon by fanatic · · Score: 1

    Unix licensing ...states that if a licensee (IBM) modifies the licensed code, then SCO or unix owner of the week then owns that modified code.

    Especially since we're talking whole new modules, not just modified modules. By SCO's argument, they would own all of Unix, Linux, BSD, AIX, etc. - clearly nonsense.

    --
    "that's not encryption - it's a new perl script that I'm working on..." - from some Matrix parody
  413. Re:very telling... by noldrin · · Score: 1

    It's so refreshing to here a CEO admit that their company is a complete failure. Now they are relying on the US government to help prop up their failed business model. Luckily IBM is gong to also be relying on the US government to protect it's successful business model.

  414. Has been done in Germany and Poland by kjj · · Score: 1

    Click
    here for info on Polish legal actions

    And SCO might even be found in contempt of the german court. Click here for info on the german court actions.

    If the court finds against SCO they can be fined a 250000 euros for each infraction.

  415. SCO should be well aware of it by smiff · · Score: 1
    To most people, if it isn't on the Web site, it doesn't exist.

    By that logic, SCO has no case. To most people, if it isn't Windows it doesn't exist.

    They could throw out some nice, Judge-convincing BS like "We only made these files available via the 'FTP' program, which is only for highly advanced technical individuals such as corporate IT managers, for the convenience of our paying customers. It was not intended for download by unlicensed individuals, and in fact doing so constitutes hacking as per the terms of the DMCA..."

    Unless reading security advisories from LinuxSecurity.com constitutes "hacking", I don't see that argument as particularily convincing. SCO posted the kernel on their FTP server May 9th. A Linux kernel developer told SCO about it a month ago. Links to the story were posted on many popular news sites. The code is still there.

  416. So why now? by VPN3000 · · Score: 1

    So why is SCO causing trouble now? They have had years to bring up this dispute. Doesn't the court system recognize that by waiting out a technology or device you've patented to see how well it does before trying to take control of it is wrong?

    I hope so.. !

  417. Re:"We would prefer licensing to litigation," McBr by Anonymous Coward · · Score: 0

    I actually happen to live near the Library of Congress. I don't feel like going over there and looking it up, though.

  418. Criminal Charges by Anonymous Coward · · Score: 0

    If things don't pan out for SCO as they expect regarding their IP.

    Is it possible for SCO to be brought up on criminal charges ?

    I know it's not legal to scream "FIRE RUN FOR YOUR LIVES" in a crowded movie theater.

  419. the state of FSF funds by noldrin · · Score: 1

    The question is does the FSF have a legal fund for when a true challenge of the GPL comes forth? Some have speculated that the FSF have been over the years putting away money into such a fund while avoiding any of the small violation cases in order to save for the day when the entire GPL system was taken to court. If so, would the spend the fund for this case? If not, will they start a fundraising campaign for the purpose of protecting the GNU/Linux system?

  420. Still distributed today, apparently by donutz · · Score: 1
  421. The ultimate outcome - history repeats by 3seas · · Score: 1

    When was the last time you read the Declaration of Independance?

    Life is filled with exceptions, and that includes the use of guns too. (there are other US documents in such support)

    Perhaps the failure here is the court system (AGAIN).

    What do the people want? Oh wait, they aready said that they want freedom from corporate abuses.

  422. I didn't fall, by Idou · · Score: 1

    it was gravity's fault I fell.

    Hmm, sounds a bit different when put into perspective . . .

    --
    Sdelat' Ameriku velikoy Snova!
  423. IIRC... The RICO act by waferhead · · Score: 1

    covers extortion...

    Unless the liscence explicityly states what is included, they are going to get a dozen PHBs at best...

    I think the SEC needs to look HARD at the trading habits of the employees.

    Or perhaps they are... The continually surprise me by nailing assholes that desperately need it.

  424. I agree completely by Maimun · · Score: 1

    If they don't want to keep the whole thing, they can keep just the hash value. Say, an md5sum. The first / middle / last pages are clearly insufficient.

  425. Sco Missing the point linux was a UNIX by Anonymous Coward · · Score: 0

    It is strange that there can be yelling at linux that is using UNIX stuff with out permision when from time to time linux is a decarded UNIX basicly linux is in it next development stage between bothering about decaring. Now SCO may have the copyright but it does not mean they can inforce it.

    Number one there is a chance that linux is home safe as a BSD based operating system. SCO was force to prove that they were the copyright holder yet this does not mean they have any rights any more. Just that they can use the code anyway they like without being sued to get the source code what was on the boards due to freebsd being based on a early version of Unixware operation system. Now overlap it to expected when Novell that made Unixware got caught stealling from BSD. This was used to form the base from what OpenBSD and FreeBSD came from then from there and minix linux has formed. So over laping functions would be expected. Basicly this ruling means nothing SCO has got no where fast. Think linux is based on BSD parts of linux kernel are still covered by the BSD licence basicly everyone forgets that linux kernel is a mult licences that just happen to be compad with GPL so GPL can be used as a over ruling licence. Most comon problem here for SCO is there has been a lot of thought from the OpenBSD and FreeBSD groups that SCO has been keeping up the novell system of stealing code. Most likely it will turn out that someone removed a BSD copyright notice by misstake but unlike Novell the source code was still open to the pubic and when ask linux will change the licence to fix. From the time SCO found these overlaps there have been a few sections in linux that should have been maked as BSD that were not. Basicly it seam strange to be fighting over something that is fix just by adding a licence marker.

    Basic this is a FUD War about time SCO stops calling peoples Bluff and lay the cards on the table for a full check out. The problem is that SCO is trying to bluff linux into buying a SCO licence because if they cannot UNIXWARE will be worth nothing since linux is getting as advanced as UNIXWARE.

  426. Re:Who's codes' on first? What license is on secon by Anonymous Coward · · Score: 0

    You have to realise at some point in your life, that as much effective you want the GPL scheme to be, so much you have to respect the rest of the licensing schemes as well.

  427. Re:What RMS and the IBM Legal Dept. Are Waiting Fo by geekee · · Score: 1

    "If SCO is stupid enough to try to enforce this, then they will have the "smoking gun" they need to really slam SCO into the ground, on the basis of clear and continuing violation of a legal contract (the GPL)."

    David Boies is not stupid. The GPL is a copyright agreement. Why would you think it's valid if the work in question is a derivative of someone else's work, as SCO claims? It is interesting though that they're going outside the legal system in collecting damages, i.e. licensing fees. I would have thought they'd need to wait for the courts to award them, but IANAL. It'll be interesting to see what the courts decide, but it'll take a few years.

    --
    Vote for Pedro
  428. have fun with this.... by pair-a-noyd · · Score: 1

    ftp://ftp2.caldera.com/pub/skunkware/uw7/Packages/ top-3.5beta9.pkg
    - Top provides updated information about the top cpu processes

  429. Question by mindstrm · · Score: 1

    It is my underestanding that copyright registration is not like patent application.... there is no "approval" process.. copyright applications are not rejected unless the forms aren't filled out right. IT's just a legal record that you applied on a certain date.. it does not imply any special grant of copyright... that still rests with the authors.

  430. Re:They want you to buy a SCO license for EVERY co by SpacePunk · · Score: 1

    Looks like something out of a fucking Mafia movie.

    Look yous guys, pays us what we wants and nobody gets hurt.

    The 'protection scam' is a protection scam no matter what industry.

  431. GPL by Ender+Ryan · · Score: 1
    Hmmm... If you were to base a project on GPLed code, then go back and remove the GPLed code and only use what you yourself wrote and license it under a different license, or even add your part of the code to another project, you would not be in violation. The GPL deals only in code, none of this fuzzy 2x removed derivative bullshit.

    --
    Sticking feathers up your butt does not make you a chicken - Tyler Durden
  432. Re: SIG (OT) by fireman+sam · · Score: 1

    I thought that windows security was when the user cuts the power cord with a knife while the computer was running. Removes the computer from the internet, and removes the user from life. Thus preventing any "hacker" from obtaining information from either the computer or the user.

    --
    it is only after a long journey that you know the strength of the horse.
  433. Re:Who's codes' on first? What license is on secon by Exatron · · Score: 2, Insightful

    Ownership of the operating systems you listed is probably SCO's ultimate goal. I wouldn't be surprised if SCO tried to convince a judge that the only way to remedy the situation without jeopardizing SCO's trade secrets is to give SCO ownership of Linux.

    --
    "I think so, Brain, but 'instant karma' always gets so lumpy." - Pinky
    "Decepticons FOREVER!!!" - Ravage
  434. MOD PARENT UP! by Anonymous Coward · · Score: 0

    Very informative, and not offtopic as lesser minds would have us believe...

    Ye gods, what a foul smell!

  435. Yes they do by roystgnr · · Score: 1

    It's only $10 or $15 million rather than the $150 million the market is valuing them at now, but they've got some assets, mostly cash.

    Of course, the important reason to sue them is to provide a court venue to publicize whatever evidence (or lack thereof) they've been keeping secret so far, to thereby show that the executive officers who are currently selling off their stock at ten times its natural price have been inflating that price by keeping relevant information secret, and to make them pay for those hundreds of thousands of dollars of deception (and millions of dollars worth of FUD) with hard prison time.

    1. Re:Yes they do by Arker · · Score: 1

      It's only $10 or $15 million rather than the $150 million the market is valuing them at now, but they've got some assets, mostly cash.

      Yeah, that's true, but that's what they're going to be eating up as they drag this case out. So if you don't pop em early, there won't be much left to pull damages out of.

      Of course, like you, I think it's very likely that there is a lot of insider trading going on here, and the principles rather than the company are planning to abscond with a lot of cash. But tracking that down and proving it after the fact could be very difficult.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
  436. THE PLAN TO END THIS ALL!!!!! by violent.ed · · Score: 1

    1. Start a fund (EFF can help)
    2. Find sum ballsy guy to sign the NDA
    3. Have the guy remove the code from the kernel & submit it with a special *FREED FROM SCO CODE* to the kernel mailing list or whatever
    4. let him get sued by SCO
    5. the fund pays his legal expensens/fines
    6. get really really drnk & fart in the general direction of darl mcbride.

    --
    - You're not paranoid, they really are after you.
  437. I've got a better idea. by Anonymous Coward · · Score: 0

    SCO MUST BE STOPPED. NOW.

    My proposal to stop SCO is a simple, easy to implement little plan.

    The Goal : Make SCO's stock drop like a rock.

    The Method: If as many people as possible go onto stock boards, and post their negative feelings about SCO, and their own speculations as to what the outcome of the battle with IBM will be, Buyers will begin to flee from the stock.



    Do you really think this would work?

    I've got a better idea!

    It involves bullets.

  438. OK... Enough is Enough!!! by jmors · · Score: 1

    There comes a time when things get so rediculous that discussing the merits of this SCO debacle on forums lik this one just doesn't cut it anymore. SCO offering to sell licenses to linux is like any other compoany offering to sell a license to a product manufactured by and sold by a completely unrelated company! If this licensing scheme (actually more like Racketeering scheme as what SCO is truly selling is "protection") works does that mean we need to prepare for the possibility that the manufacturer of the paint used by Ford Motor Company to paint the car I purchased from a Ford dealership could at some point in the future decide to require me to pay them a licensing fee if I wish to continue to "legally operate my vehicle"? This is completely and utterly absurd. It is high time for the leaders in the Linux community to stand up, in unison and voice their complete and total dis-association from SCO! I think a good place to start would be with the other members of the "United Linux" group. How does SuSE for example, feel about SCO charging their customers a license fee for the product they distributed? The other members ofg the United Linux foundation should all denounce the tactics being used by SCO to extort money from the Linux using populace of the world! I can understand IBM biding their time up to this point as they most likely feel, rightly so, that SCO's claims have no merit BUT isn't it time to say enough is enough and publicly state the rediculous notion that SCO can claim to be due licensing fees for products distributed by others. Not only publicly but in the form of some sort of press release that would be just as visible and noticeable to the fortune 500 companies and others that just may give in to this extortion simply to hedge their bets. SCO does not deserve a single red cent from the linus community! I have gone from being an interested observer of this case, to becomming almost boared with the FUD to now being exceptionally angry. I am normally a calm and patient person but isn't this a case where enough is enough?

    --
    The Matrix is real... but I'm only visiting!
  439. Is the FSF Just Broke? by RevSmiley · · Score: 1

    Is the Free Software Foundation just Stupid or is it broke? WTF is the FSF just laying there like jello for? This crap has got to STOP. If the FSF can't defend the GPL then the GPL isn't worth wiping your ass on.

    I am starting to think all these OSS Gurus are only in it for the pay checks and don't give a fuck about GPL or OSS. This is not a troll. I am serious. How come there is no suit against SCO for this actual violation of th GPL. WTF is going on?

    Someone who actually knows something needs to answer this. Like someone from the FSF not some IANAL or self appointed GPL expert.

    --
    As you can see I don't care about my karma.
  440. Re:Who's codes' on first? What license is on secon by arkanes · · Score: 2, Interesting
    They most certainly are claiming that. It's a wide run around the idea that "all code that's produced for Unix is ours [which is overstating a bit, granted, but the certainly lean in that direction]), but one thing they are unfailingly clear about is that there is code that they consider thiers, and that code is in Linux, and therefore Linux is thiers and people using it are pirates.

    I'm actually not sure that it's ever been put quite so baldly as in this press release (note that this is an SCO press release, not an actual article, which is why it does things like state as fact rather than as allegations that Linux code is pirated). I'd think that someone would have pretty good grounds for a lawsuit now, if they didn't before - this is a flat statement of something that had better be true if they're going to threaten people with it.

    I think Daryl is putting a little too much faith in the respect the market has for ballsiness...

  441. where did you find that statement? by Anonymous Coward · · Score: 0

    It's not on their website anywhere, or in any of the press release newswires I looked at. Are you being a jerk?

    1. Re:where did you find that statement? by Anonymous Coward · · Score: 0

      novell.com - google on a long enough string from the statement and you'll find it.

  442. Marie Antoinette would be proud by PenguinX · · Score: 1

    In today's world we are taught "Those who do not learn from history are doomed to repeat it". In the 18th century common society didn't really have much of a concept of an economy. We forget that life during those times consisted mainly of ... well ... just surviving. When Marie Antoinette (supposedly) said "Let them eat cake" the common man compared the rotten food they were being forced to eat with the good food the royals had... that and dessert? While all they had worked for... thier livelyhood... even their very lives were at stake?

    Needless to say we all know what happened. In today's world we have come up with systems to make sure that most of our basic physical needs are to met until we are old enough to retire and die. Government doesn't so much govern humans anymore as they govern the systems in which we live our lives. Capitalism, the economy, lobbyists, etc. Quite frankly we have a pathetic excuse for a government.

    Getting back to Marie Antoinette... now unless I'm a way off base I'm pretty sure that people are still people. If our very survival is threatened we tend to get mean. In today's world if the very base systems are threatened I don't know what people are capable of.

    <insane example>

    SCO wins it all, they own all UNIX/Linux. They kill open source. Say 20 years has passed and in that time you've found someone and settled down. Perhaps this means a family. Perhaps this means "just a lot of debt". Who cares? In the end you have some form of life and responsibility.

    Of course you never believed in the US Supreme Court ruling where Linus Torvalds had to sign Linux over to SCO. So you moved away from the US to another country. You started a small software firm based on Linux, GNU, Open Source... and the like.

    All at once international copyright and trademark law come into being. Suddenly SCO decides to change the licensing of Linux to $1,000,000 per seat. Within 2 hours a 16 year old collection boy accompanied by a fleet of lawyers and the UN police come up to your home with a bill for (Dr. Evil Voice) ONE HUNDRED MILLION DOLLARS. Due upon receipt.

    </insane example>

    Would you lash out? Would all Linux hackers lash out? Would you revolt against the entire world for messing with your way of life? Being some place they have no right whatsoever to be?

    Let's be realistic... SCO is just a bunch of shareholders in a dead corporation with a few bucks in the bank. There hadn't been a unified development movement in the entire UNIX world in oh... about the time that the GNU project and Linux met each other head on. Linux is a tool that has helped a number of us build a life... and now some crusty shareholders want to charge the very people who have been developing, building, testing, and using that tool?

    It stands to reason that it may be time for us hackers to stop being so cynical, bitchy, and nonchalant about these issues. Wishing they would just "go away" thinking "everyone will wise up eventually". And realistically this is stupid, and if we're not careful our government is going to give one of our more important tools (our own work) away to someone else ... and then you're going to have to pay them to use the tools you wrote. This isn't capitalism... it's madness.

    Opinions?

  443. It's even simpler that that!!! by Anonymous Coward · · Score: 0

    They continued to sell Linux products after the point at which they filed the lawsuit. At that point they must have known there was "infringing" IP in the Linux kernel. By continuing to distribute Linux, they officially licensed their alleged IP under the GPL. Thus, even if code exists that was straight from UnixWare or wherever it's alleged to have come from, it's GPL'd because they knowingly published it under GPL license terms.

    So they can go fuck themselves. Linus should file for an injunction on their licensing plan.

  444. isnt binary only distribution a violation of GPL? by RouterSlayer · · Score: 1

    Not that I really know or understand the GPL (or even have read it), but doesn't it state somewhere that GPL products *must* include source code? and also any modification or additions to that GPL code *must* also include source code for said?

    so then, if SCO does what they claim, they are therefore violating the GPL and GNU/EFF should sue them into submission...

  445. Is Linux even Legitimate? by iLukeBeans · · Score: 3, Insightful

    Having just spoken with a corporate attorney about this (said attorney happens to be my father), I was told that only one thing really matters in this case:

    What is the dimension of copyrightability or of patentability, as it applies to computer software?

    This is to say, what can SCO claim it had patented or copyrighted. Narrowly, one could say that SCO's protection applies only to the letter of its source code, not to any ancillary ideas. But SCO could counter this claim, saying that its protections extended to the UNIX "user experience." Such things as the command syntax of the Bourne shell, the Shell/Kernel design, the presence of standard utilities like awk and make, or even the something as nebulous as the "shape of the integrated whole" (the experiential architecture of a UNIX system and what it "feels" like when it is operated) could, in fact, be claimed as intellectual property.

    One should realize, in defense of SCO, that all essentially all early UNIX and UNIX-like technology was developed by a small team at AT&T Bell Labs, and clearly AT&T didn't pay and fund that team simply to write code. No, that team was funded by-and-large to craft an operating system, a "user-experience," "application programming interface experience" and "overall system architecture." Indeed, these latter ideas were far more important (and valuable) than the UNIX source code itself. AT&T forced Novell, as Novell later forced SCO, to pay good money for the rights to these ideas, so if I were SCO and had paid some $500 million for the rights to such ideas, I too would be rather perturbed should an individual and an organization (Linus and the FSF) come along with the vision of creating "a complete Unix-like operating system which is free software" (source: FSF website, GNU project homepage), this is to say, creating a product that uses all of my policy, interface specification, and design ideas, without rightfully paying for them.

    Everyone here should realize that Linus, RMS, and their ilk simply wrote programs that implemented policy, architecture, and user-experience specifications and ideas developed, at the cost of millions of dollars, some twenty-years before at AT&T Bell Labs. That SCO later paid millions for those ideas, something that people here seem to laugh at, should not, in my mind, be taken lightly.

    1. Re:Is Linux even Legitimate? by MuParadigm · · Score: 1

      Problem with this is that SCO doesn't appear to own *any* Unix System V patents. Nor does it own any Unix (or for that matter Unixware) trademarks. All it does have it copyright on the Unix System V Release 4.1 source code. If there were no patents at all, then SCO might have some basis for a "look and feel" complaint based on their copyrights. But since there are patents, and these patents are owned by other coporations, SCO's "dimension of copyrightability" would seem to cover the source code only. Unfortuantely, that will need to be decided by a judge, probably on the basis and interpretation of precedent rather than on the letter of the contracts and law. I am not a lawyer, could someone who is correct me?

    2. Re:Is Linux even Legitimate? by Anonymous Coward · · Score: 0

      Linux is more legitimate than McBride's behaviour suggests he is.

  446. Re:very telling... by DASHSL0T · · Score: 1

    Those are all paraphrases as I am not a stenographer, but that is essentially waht they said. It was along the lines of "two years ago we had this great Unixware product with 250 million (or 150 million, i forget which) in sales, and growing. Then IBM came along and scaled up this Linux thing and it took off and that is how Unixware was damaged. It is because of Linux newfound scalibility in the 2.4 series, contributed by IBM and others that caused damage to our product".

    That is still paraphrased, but with more detail. :)

    --
    Freedom Is Universal
    Linux-Universe
  447. Somebody Explain To Me Why by Master+of+Transhuman · · Score: 1

    these fucks are being allowed to try this case in the media.

    Where the fuck is IBM? It issues one fucking statement, then shuts up. I realize it's not a good idea to be babbling about the case in public, but IBM needs to AT LEAST REITERATE its position whenever these SCO assholes run their mouth.

    And the Slashdot headline misses the point. SCO in its press release is saying that UNLESS ALL LINUX USERS BUY LICENSES THEY WILL BE SUED. At least that's the way the rest of the IT trade press is putting it. One of Microsoft's tame research organizations is claiming that users are confused and starting to think about dumping Linux.

    This crap is going to hurt Linux in the market and it is going to hurt IBM's Linux business if it keeps up, so IBM needs to SAY SOMETHING.

    --
    Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
    1. Re:Somebody Explain To Me Why by mormop · · Score: 1

      Name the tame research company and we can all let them know how confused we aren't. Firstly a good slashdotting should show them how "reliable" their 2k servers are and a full inbox of "we ain't scared and we ain't buying no licences from that twat McBride and his piss poor company" should give them a clue for their next article

      --
      Hmmmmmm..... Deep fried and look like Squirrel.
    2. Re:Somebody Explain To Me Why by Anonymous Coward · · Score: 0

      These fucks are being allowed to try this case in the media.

      Where the fuck is IBM? It issues one fuck


      Three fucks, you're out!

  448. An Epiphany about the viral nature of SCO Unix. by EMR · · Score: 1

    this is the impression I got from Darl what's his name from SCO from the McBride interview, is that the SCO Unix license is more viral that what M$ is saying the GPL is.. He basically said that they own any works that any compnay does that happens to work in their licensed Unix code from SCO....

    It's rather ammusing..

  449. Ford was sued for making cars! by bluGill · · Score: 1

    Back in their early days Ford Moter Company was sued by General moters for making cars. GM came about because someone got a patent on cars, and conviced Mr. Chevy, Mr Buick, Mr. Pontiac, and a few others who made cars that his patent was valid and they were better off partenering with him than getting sued and shut down. Ford said the patent was invalid and fought in court to prove it. (I don't recall the outcome)

  450. Re:Who's codes' on first? What license is on secon by Curtman · · Score: 2, Interesting

    We most certainly do not have to respect licenses that remove our freedom. The GPL gives the copyright holder the right to relicense that code commercially or otherwise at their discretion. Its this very type of licensing that prompted RMS to found the FSF long before Bill was enemy #1. This type of license needs to be fought vigilantly. It IS cancerous, for exactly the same reasons that the GPL is not. We do have to honor those licenses, with the caveat that those licenses do still need to be legally enforceable but they are not deserving of any respect. I could ship some software with a licensing clause that I now own your first born, but that doesn't automatically make it so. The burden of proof should clearly be on SCO to prove that the IBM code was derivitive of their work, not for IBM to show that they still own their own code. Thats rediculous.

  451. Judging by the SCOX share price... by leonbrooks · · Score: 1

    ...it's working at least temporarily for TSG, too. From 80c to $14 in six months would be impressive if it hadn't been achieved fraudulently.

    --
    Got time? Spend some of it coding or testing
  452. In that case, the Novell people are probably... by leonbrooks · · Score: 1

    ...about to sell a lot of SCOX shares. (-:

    --
    Got time? Spend some of it coding or testing
  453. Er... hello? TSG _did_ sue IBM... by leonbrooks · · Score: 1
    ...that what this whole argument is about. They are suing IBM for leaking TSG's IP when the contract IBM is operating under with TSG explicitly grants ownership of IBM derivatives from the USL source to IBM. And they still haven't shown that IBM have actually done what they're suing them for, and are blowing steam about why they're not doing that.

    That's still not good faith (just fraud and/or extortion) but they have sued.

    --
    Got time? Spend some of it coding or testing
    1. Re:Er... hello? TSG _did_ sue IBM... by 16K+Ram+Pack · · Score: 1
      So when is the court date?

      I'm not too well up on the US legal system, but following this case, I was under the impression that SCO has said that they are going to take legal action against IBM but have taken no action to back up the words.

  454. Again! No Copyright was Awarded by screenrc · · Score: 1
    All Caldera/SCO did was register
    a copyright, they were not awarded anything.
    In other words, they walked to a governmetn
    office, they claimed that they own the copyright,
    and their statement was stamped and date on
    the records. That is it, They were not awarded
    anyting at all!


    So please, you being the 1000th person who
    repeats misleading half-truths from SCO's
    PR department, please cease to repeat that
    a copyright was awarded by the government to
    System V. That is not the case at all. I can
    get a the government "award me" the rights to
    System V tomorrow, it I sent them $30 dollars;
    and I am confident, hundreds of other people might have
    received the same "award" to System V already.

  455. CANNOT (was Re:Download Linux from SCO via FTP) by trance9 · · Score: 1


    OK smarty, did you actually follow your own link? Yes there are a bunch of SRPMS there, but where is the kernel?

    I don't see it.

    It either has been removed or it was distributed elsewhere. What I am actually asking for is someone who actually has a copy of the kernel which they downloaded from SCO to send me a copy, as contrary to reports here it does NOT appear to be on the website or the FTP site.

    1. Re:CANNOT (was Re:Download Linux from SCO via FTP) by Anonymous Coward · · Score: 0

      Didn't find any sources, but there is at least a binary kernel here.

  456. To get a copy of the code: Use Circular 6 by Tsu+Dho+Nimh · · Score: 1
    http://www.copyright.gov/circs/circ6.html

    YOU can get it for actual OR PROSPECTIVE litigation ...

    "The Copyright Office Litigation Statement Form is completed and received from an attorney or authorized representative in connection with litigation, actual or prospective, involving the copyrighted work. The following information must be included in such a request: a) the names of all parties involved and the nature of the controversy; and b) the name of the court in which the actual case is pending. In the case of a prospective proceeding, the requestor must give full statement of the facts of controversy in which the copyrighted work is involved, attach any letter or other document that supports the claim that litigation may be instituted, and make satisfactory assurance that the requested reproduction will be used only in connection with the specified litigation.

  457. TSG claimed ownership of *ALL* OSes... by leonbrooks · · Score: 2, Interesting

    ...during the interview reported in this BYTE article. You can see here that Microsoft have updated the later builds of MS-Windows 2003 to reflect this.

    --
    Got time? Spend some of it coding or testing
  458. Sorry, should've mentioned... by leonbrooks · · Score: 2, Interesting

    ...that before this the "My" in "My Computer" used to stand for William Henry "Trey" Gates III, so as far as the users are concerned, it's just a flag day. Swap one litigious, greedy control freak for another, big whoop-ti-doo.

    --
    Got time? Spend some of it coding or testing
  459. What if they don't distribute the software? by kwelndar · · Score: 1

    Actually, though, a "binary only Linux license" is not software piracy, it's just a license. This may seem like I'm splitting hairs, and maybe I am but I think I have a good reason.

    Now if they distribute the software, that would be piracy, but if they just sit back and collect from those already using the software, for a promise not to sue, then that really has nothing to do with the actual license of the software concerned, does it? I mean it might be blackmail, but ...

    I'm wondering if this is not what they're up to, since actually distributing the software under licensing terms specifically prohibited by its owners would open them up to legal liability of their own. Just because a little of their code may or may not be in Linux doesn't mean they own all the code and can do anything they like with it. I don't think even they'd be arrogant enough to do that. Of course I could be wrong here. ;^)

    Anyway, if they do not distribute the binaries themselves, they can just sit back and watch the dough roll in from all those companies not wanting to risk it.

    In any case they are calling it a Unixware license. Of course they didn't offer any details on that either. So Linux might not even be part of the equation except that along with whatever else you get for buying it (if anything), you get the peace of mind that they won't come after you.

  460. SIG (OT) by leonbrooks · · Score: 1
    Member of the future Elite Slashdot 6 Digit ID Society

    So what if your ID is bigger than mine? I'm sure I've got something here in my Inbox which'll fix it! (-:

    --
    Got time? Spend some of it coding or testing
  461. Ah hell... by Etriaph · · Score: 1
    And into this confused fray I go.

    So, I need a question answered by some kernel maintainers, contributors, etc. Just how much code are we talking about? 2K lines? 10K lines? Or is it small portions of copywritten code? If it's small portions, can we simply not rewrite that part of the codebase more effeciently (effeciency is a good reason) and re-release the kernel with the updated code? It seems to me that (and this was earlier with their comparison of a few lines of code) that you elminate that problem, do something in a slightly different way to avoid copyright infringement, and everyone's happy (not SCO, but we'll leave them out of this).

    Secondly, does anyone think that SCO will release their Linux distribution royalty free of these copyright charges? If so, does it seem to anyone else as it does to me that we've finally met the MS of the Linux world?

    Not that I think they'll succeed, but that's just hope talking. I think an action like this can sour Enterprise on Linux and shift many Linux customers back over to MS. Way to go, SCO.

    --
    "It's here, but no one wants it." - The Sugar Speaker
  462. welcome to the end of the world by Anonymous Coward · · Score: 0

    joy!, isnt the world becoming a great place,
    bill & SCO, we thanks you for your kindness
    you will be remembered as saints,

    viva la revolution

  463. Re:There can be no doubt about it by Mostly+a+lurker · · Score: 1
    they would post the offending code

    Actually, I do not hold the opinions expressed in this post, but I want to try and play devil's (appropriate) advocate. The code to be compared is AIX and Sequent code. As such, even though major portions are in open source, SCO must refrain from freely sharing the full sources since the rights are shared with IBM and some portions are not in open source.

  464. Re:What RMS and the IBM Legal Dept. Are Waiting Fo by achurch · · Score: 1

    David Boies is not stupid. The GPL is a copyright agreement. Why would you think it's valid if the work in question is a derivative of someone else's work, as SCO claims?

    That's a pretty big "if" (though granted Boies is being paid to think like a SCOian). If SCO's copyright claims are ruled invalid, then SCO is (or will be) violating the GPL and in for even more trouble than they were before.

    It is interesting though that they're going outside the legal system in collecting damages, i.e. licensing fees.

    My IANAL guess is that SCO knows full well that they're going to get blasted in court, and is trying to scrape as much money off people as they can before they get smashed into little bits of corporate kibble.

  465. SCO Trademarks Penguin Mascot, Offers Licensing by tenzig_112 · · Score: 1
    An excerpt from http://www.ridiculopathy.com/news_detail.php?id=86 7

    SCO Trademarks Penguin Mascot, Offers Licensing Program to Linux Users


    LINDON, UTAH- Just weeks after asserting part ownership over the nominally open and free Linux source code, SCO Group sent another shockwave through the software community on Monday when they announced the discovery of a long-forgotten trademark for an amiable penguin mascot. The company's legal team happened to notice an uncanny visual similarity to another unix-based flightless waterfowl and reportedly grew so excited that they spat out several thousand cease and desist letters in a single afternoon.


    Fortunately for Tux fans everywhere, SCO has generously agreed to license the character to current users at a very reasonable rate. Without a license, SCO lawyers say the trademark infringing penguin must be removed from all t-shirts, screen-savers, undergarments and fine linens before the end of July or face stiff penalties.



    Full Story

  466. Re:Nope by Anonymous Coward · · Score: 0

    It could only be a derivitive work if IBM owned the copyright for the entire Linux kernel. (As IBM may/may not have signed a contract giving up derivitive rights to SCO).

    However IBM does not own the linux kernel copyright.
    At worst there may be copyright infringement in modules submitted by IBM. But since IBM claimed full copyright on any such submissions, the worst case becomes:

    1.) IBM submitted modules must be removed from the kernel.
    2.) IBM (not linux users) is liable for any damages caused by falsely claiming copyright and illegally distributing said code.

    Under no circumstances can SCO claim ownership over linux, nor do they have any licensing, etc claims on previously distributed linux copies.

    If anything SCO is severly restricting their ability to claim damages by not immediately informing the parties that were distrubuted the mis-copyrighted code.

    This lawsuit shows all the signs of taking advantage of the federal 2 year civil case waiting period, rather than actually trying to win the case.

  467. Re:Unbelieveable! - Believable! - 0-0 by Exatron · · Score: 1

    Thanks to Microsoft, those things have to be ignored. Apple lost the suit where they accused Microsoft of stealing the look and feel of the Macintosh operating system. SCO must prove that its code is in Linux and that it was contributed without proper consent. Simply being a Unix clone is not proof that SCO's IP is in Linux. That would be like saying that Goodyear couldn't sell tires because they infringe on Firestone's IP for tires.

    --
    "I think so, Brain, but 'instant karma' always gets so lumpy." - Pinky
    "Decepticons FOREVER!!!" - Ravage
  468. Re:yeah, sure. do you take cash? by evilmrhenry · · Score: 1

    Or. . .

    SCO: You are going to have to pay a license to use linux because otherwise you will be illegally using software that we wrote.

    Linux User: OK, which lines did you write?

    SCO: I'm not telling.

    Linux User: I'm paying.

    SCO: Thank you. . . .

    SCO: . . .Err, where did you put the money?

    Linux User: I'm not telling.

  469. This has a familiar ring to it by Anonymous Coward · · Score: 0

    Perhaps because of similarity to the case of Pictosphere. This is the company of Ford Oxaal, who last year settled with Ipix. Ipix, you may recall, threatened several individuals including Prof. Helmut Dersch (author of the free Panorama Tools software; web page offline since last year), and sued Infinite Pictures over patent infringement and won.

    Oxaal's dispute with Ipix was based on his claim that Ipix stole their patented ideas from him. Oxaal has a patent similar to Ipix's; it's not really clear who was first to "invent" (if you can call it that, this being software based on long-established mathematical algorithms). Under the terms of the settlement, Ipix paid for a license to use Oxaal's technology (presumably an admission that Oxaal owned the technology, not Ipix).

    The similarity is that Pictosphere is offering, for $500 US, a license that (it is claimed) would protect users from prosecution for infringement (e.g., by Ipix).

    The second similarity is that, while claiming patent rights to the concept of spherical panorama photography, Pictosphere is now distributing Prof. Dersch's software under the GPL.

    Lest you think that Pictosphere, by playing the SCO-like role in this matter, is the only bad guy here, Ipix is now
    suing Pictosphere, now claiming that Pictosphere's software infringes the same Ipix patent that was previously disputed. Ipix has achieved some notoriety for using the chilling effects of patent law.

  470. BOHICA by pair-a-noyd · · Score: 1

    http://news.gw.com/netbsd.advocacy/3435
    SCO update: "Issues with BSD" ?

    [netbsd.advocacy]

    Subject: SCO update: "Issues with BSD" ?
    From: mac@Wireless.Com (Mike Cheponis)
    Newsgroups: netbsd.advocacy
    Organization: TAC News Gateway
    Date: Jun 16 2003 23:47:18

    Hmmm.... SCO is certainly making life unpleasant for many. -Mike

    From BYTE.COM newsletter:

    ________
    1. Special Feature: SCO Owns Your Computer
    ________

    Fittingly, it was Friday the 13th. A sunny San Francisco morning.
    But my discussion with Chris Sontag, SCO's Senior Vice President,
    Operating Systems Division, was driving the sunshine from our
    room, creating an atmosphere appropriate for the 13th. Let me
    summarize in a parable...

    In the beginning was AT&T Bell Labs, staffed by a benevolent team
    of PhDs and research scientists. AT&T produced this really neat
    operating system--System V--which computer manufacturers wanted to
    license and use. Everybody was happy to sign tough contracts with
    these benevolent scientists--licenses which deeded all derivative
    works back to AT&T, licenses that covered all "methods" and
    "concepts" of operating systems. But now those licenses are owned
    by SCO and its team of lawyers who are certain that AIX and all
    the other IXs belong to SCO. And the company now wants royalties
    from users of all these operating systems--especially Linux.

    Specifically, Sontag believes the "SCO technologies" which were
    misappropriated into AIX, IRIX, and the derivative UNIX-alikes
    (including Linux) are:

    * JFS (Journalling File System).
    * NUMA (Non Uniform Memory Access), a SGI/Stanford collaboration.
    * RCU (Read-Copy-Update).
    * SMP (Symmetrical Multi-Processing).

    "But what about BSD?" I asked. Sontag responded that there
    "could be issues with the [BSD] settlement agreement," adding that
    Berkeley may not have lived up to all of its commitments under the
    settlement.

    "So you want royalties from FreeBSD as well?" I asked. Sontag
    responded that "there may or may not be issues. We believe that
    UNIX System V provided the basic building blocks for all subsequent
    computer operating systems, and that they all tend to be derived
    from UNIX System V (and therefore are claimed as SCO's intellectual
    property)."

    "So is anybody clean? What about Apple and Microsoft?" I wondered.
    "Sun is clean," he said--but he gave no answer in regards to Apple
    and Microsoft.

    "But I thought that Microsoft had signed a license agreement?" "No,"
    Sontag said. Microsoft merely licensed an "applications interface layer."

    *** Read more at http://click.byte.email-publisher.com/maabaREaaYDX Da9Irx5b/
    This article is freely available to all readers. ***

    www@gw.com

  471. No Injunction In US YET by Anonymous Coward · · Score: 0

    I am surprised all the Linux Distros / IBM / Apple - etc have not all banded together to slap an injunction on them like they did in Germany. They should also demand to see what was licenced by M$ - especially since M$ is already in trouble with the class action stuff being investigated again.

  472. SCO Shakedown by Anonymous Coward · · Score: 0

    Amounts to little more than extortion, pure and simple.

    Protection money. Pay up, and we won't sue you. Utter BS.

  473. McBrides & Bois comments today... by MuParadigm · · Score: 1

    Seem to bear out what I posted above. They didn't make any reference to JFS, or porting Linux to PPC and Power chips, or any IBM derived and/modified works. They seem to be going after the works that apply to SMP and were purchased with Sequent. This is the way Boies works: He throws everything at you in a complaint, makes his complaint more specific based on what you give him in response. Narrows it down closer, and closer, until he's got a legal document shaped by natural selection. He finally figured out that he will have to go after IBM on copyright at this point, and that it's best to go after everyone on copyright once he files those amendments to the IBM case.

  474. I heard, I listened by Anonymous Coward · · Score: 0

    Nine out of ten of the voices in my head
    told me to stay home today and clean my guns.

  475. Snap! by nathanh · · Score: 1
    They obviously believe that they can defeat the GPL in court.

    It's looking very much like this was SCO's plan from the beginning. SCO wants the GPL declared an invalid license by a court judge. For what purpose? Who can tell.

  476. Sue Microsoft ? by Mr+Europe · · Score: 1

    Could the developers' group sue Microsoft for receiving Linux in violation to GPL ? MS did buy a license from SCO or did it ?

  477. The ultimate IP theaf by Felinoid · · Score: 1

    SCO selling Linux binarys violating the GPL (Sorry even if it dose contain SCOs IP it also contains a bunch of other peoples IP and the mix of the two means nobody on the face of the earth has any right to do anything with Linux at all piriod end of story good bye)

    Of the technologys SCO is suing IBM over is IBMs to start with.
    It appears the code SCO "found" by discription was given to SCO and Linux by system manufactuerers so that the consummers may use SCO or Linux if they so chouse permitting the manufacter to sell more computers. That code is given to anyone who asks. There would be no reason IBM would have said code let alone introduce it into Linux as it would mean supporting compeating producs something IBM is clearly not going to do if they can at all avoid it.

    SCO clames ownership of System V and Novel clames otherwise.

    Now SCO regestures that clame with the copyright office.

    If I understand everything correctly (Hay IANAL nore am I omipotent so I nither have all the facts nore do I know law) I'd say quite soon SCO will cease to exist soon enough...

    I'm Selling my SCO stock and buying stock in humanity while faith in SCO is high an faith in humanity is low becouse I think when SCO folds faith in humanity will hit an all time high....

    --
    I don't actually exist.
  478. Court Date by leonbrooks · · Score: 1

    Not sure about all of the details (or even where you'd look, maybe SCO or IBM have something up on a site) but the hearing for their permanent injuction is in 2005. SCO upped their original $1G claim to $3G too.

    --
    Got time? Spend some of it coding or testing
    1. Re:Court Date by 16K+Ram+Pack · · Score: 1

      So is that the earliest date they could do it (considering people are STILL allegedly distributing their IP), or a date that SCO opted for. In other words, have SCO made a deliberate attempt to delay the trial?

    2. Re:Court Date by leonbrooks · · Score: 1

      Yes. (-:

      You asked two questions; Yes, that is the earliest that the Court could do it, and Yes, TSG are stringing things out as much as possible as well (but I doubt it had much impact here).

      --
      Got time? Spend some of it coding or testing
  479. GPL Enlightment by Karem+Lore · · Score: 1
    I was under the impression that the GPL license allowed someone to take the code, with source, add whatever they liked in a proprietry manner, and distribute the "binary" only version.

    From reading a little about the GPL now, there seems to be a "module" clause using forks that allow the adding of non-GPL code with GPL code. Maybe SCO will try and use this?

    The sourse of the original could still be sent, minus the proprietry code that you just wrote.

    What about this: I give you the kernel, and source for that kernel under the GPL. Then I give you a binary module that you run over the kernel that adds functionality to the GPL code. Is this allowed?

    Karem

    --
    When all is said and done, nothing changes...
  480. Yo Mods! by Matrix2110 · · Score: 1

    I wish I had mod points right now.

    That Plan 9 reference is exactly right on.

    Sadly, most of the readers will not get this.

    That line alone deserves a point.

    Consider this post a ghost mod.

    I laughed a lot at that bit of brilliance. It really stood out and I thank you.

  481. Re:"We would prefer licensing to litigation," McBr by Black+Parrot · · Score: 1


    > Of course they'd prefer licensing. They were NOT granted a copyright on SysV Unix, but on a 20-page printout of some modifications to Sys5 verseion 4.1.

    The funny thing is that the ploy (I have trouble thinking of it as anything else) was sufficient to drive their share price up by 20%. We should keep that fact in mind next time we hear someone claim that share prices tell us anything useful.

    --
    Sheesh, evil *and* a jerk. -- Jade
  482. A couple of questions. by Matrix2110 · · Score: 1

    I read about the kind of crap they are trying to pull in E-Week just today, I showed it to my IT manager and he just had a fit. He swore that he would not pay SCO one red cent. (He sits on a IT board for a very large company)

    I just wonder how many CTO's actually contacted SCO and wanted to hand them money. (Then again, SPAM does work, I dearly hope SCO advertises the companys names, We already know one, Microsoft)

    I frankly could not believe what I was reading.

    A quick comment: These creatins have bigger balls than Steve Ballmer and that is saying a lot!

    I wonder if SCO had the chutzpah to send one of these letters to Microsoft.

    Microsoft is most certainly in the top 1000 companys. And don't doubt they are running Linux on a few computers.

    On to my questions:

    1. I don't wear a tin hat but SCO is doing just about everything in its power to discredit open source and the GPL. Who is the default protector of the GPL, and why are they not sueing SCO over flagrant violations?

    2. I first thought Microsoft was behind this, but at this rate, Microsoft has as much to lose as anybody if SCO somehow wins. My question is: Is SCO just trying to sling as much mud as it can and just seeing what sticks?

    Their business model closely mimics the RIAA's

    I doubt they will have any friends after this.

    Watch Microsoft for an indicator of how the landscape must fall. (I know how you guys hate BG. But he could be a major factor in this one)

    I personally think this is going to rank in the "Bob" catagory for Microsoft.

  483. SCO me! by Anonymous Coward · · Score: 0

    SCO me hard!

  484. Threats of physical violence .... by Windows+Dude · · Score: 1

    Direct quote: "The real grown up thing to to is take McBride out with the rest of these SCO greed heads and just eliminate the scoundrels. Give up on going to court with these loosers. They are attempting to steal that which isn't theirs. We will get no fair play in court. They will buy all the justice they need and Linux will get none. Bastards like McBride his compatriots and his whoreson attorney Boies have sick and twisted minds. All you pacifists need to wake up and get a grip on this shit. Violence does solve certain issues. These thieving fucks are a waste of human skin and need to be removed from the gene pool. They are a threat to civilization and the commonwheal. Death to the tryants. Let us get us some rope and proceed in community action!" Think about this before you decide to do it. This will get you thrown in jail for a long time! Don't be stupid about this! P.S. I love the comment about the "whoreson attorney Boies". He was the Golden Boy when he was prosecuting Microsoft, but now he's a "whoreson" when he works for SCO.

  485. Re:Who's codes' on first? What license is on secon by Ian+Bicking · · Score: 1

    Nah, that's unreasonable. There's many people will clear copyright claims on Linux, and there's no way in which copyright for that code could be reassigned to SCO. I don't think the courts even have the authority to do that sort of thing at all, especially not when many of those copyright holders aren't associated with any wrongdoing.

  486. Re:What RMS and the IBM Legal Dept. Are Waiting Fo by Bilbo · · Score: 1
    > David Boies is not stupid.

    Sometimes I wonder about that, looking at his latest string of big name cases... ;-)

    > Why would you think it's valid if the work in question is a derivative of someone else's work, as SCO claims?

    Doesn't matter. There is a heck of a lot of code in the linux kernel (something like 99.99% of it by SCO's count) that predates any contributions from Caldera (legally or otherwise) to which they can make no claim. If they are in violation of copyright, then the copyright owners can go after them.

    Of course, it's probably a heck of a lot more complicated than that, which is why SCO is paying big bucks for Boies to weezle his way through all the loopholes. However, I think they are skating on thinner and thinner ice. It almost looks like they are baiting the Linux developers into some sort of complicated legal trap, which is probably why IBM legal department is still keeping its head down, giving them no target to shoot at.

    --
    Your Servant, B. Baggins
  487. For the love of god, this is not extortion. by siskbc · · Score: 1
    -- Merriam-Webster's Dictionary of Law ©1996.

    You ever see a lawyer use Webster's dictionary in court? No? Maybe there's a reason. It's because words have extremely specific meanings in law.

    However, since you asked, this is neither as SCO has actually not approached any specific party. They've said that any customers of theirs won't be sued by them. However, they've not approached anyone saying "Buy this or we'll sue your ass."

    Also, your definition includes "unlawful," making things a bit circular. You've shown nothing that suggests that what they're doing isn't completely legal. If you believe it is, suggest some case law.

    --

    -Looking for a job as a materials chemist or multivariat

  488. Re:MICRO$OFT paid SCO to start it !!! by OTR+Dave · · Score: 1

    as early as 1993 microsoft corporation owned 19% of SCO, then called santa clara operations

    Uhm.... Santa Cruz Operations.

    Santa Clara Operations is someone else entirely.

    --
    Operating Systems fall into 2 catagories:
    1) *nix
    2) The rest
  489. Re:Unbelieveable! - Believable! - 0-0 by Jack9 · · Score: 1

    The distinction between what constitutes 'similar' is arbitrary. Any judge could say Goodyear had to stop making tires because they are using Firestone IP, but the decision to not make tires as a design a copyrighted design, must have never been claimed or opened to the public domain or more likely no one can dig up the relevant discoveries. IP law allows for these types of situations, which is why most ppl think it is a broken system.

    --

    Often wrong but never in doubt.
    I am Jack9.
    Everyone knows me.
  490. cat urine by Anonymous Coward · · Score: 0

    When I smell cat urine, it causes an immediate allergic reaction in my sinus cavity beknownst to doctors as: Hick Rage

    Hick Rage is a compression of the sinus cavity, causing the subjectively infected human to begin speakin' from his'ser's 0wn asshole, in turn also being so self-aggrivated at his'ser's 0wn unability to communicate that any animal with hair will imediatly be skinned whilst dead or alive.

    Be careful SCO! I have Hick Rage, you pissed on my father's front porch, I smell cat urine, prepare to die d00de5!!!1!

  491. Establishing the GNU GPL's place in history. by jbn-o · · Score: 1
    When Richard Stallman received the $25,000 IDG/Linus Torvalds award, he said, "This is like Luke Skywalker winning the Han Solo award." The Apache Group, EFF, and other parties have contributed more towards the "Open Source" movement than the FSF. I view the FSF as an outspoken critic of other peoples success bitter at a lack of their own.

    I mentioned Eben Moglen, not RMS. I don't know why you are railing against RMS here. But since you're now trying to change the subject and talk about RMS winning that award, I'll offer that he was right. Linus Torvalds contributed a piece of the puzzle--a good piece, a needed piece, but not the framework by which the rest of the pieces had been collected for years before Torvalds arrived on the scene.

    The FSF was never a part of the Open Source movement, they began the Free Software movement over a decade before the Open Source movement came along.

    If either organization (FSF or OSI) is bitter about the other's success, it is probably OSI being bitter about the FSF's success. After all, the GNU General Public License is the most widely-used license in both movements. The GPL sets the terms of the debate in many cases. The OSI had no part in writing the GNU GPL. The FSF and RMS identified what is important to continue to make and distribute software freely (and with insights that continue to be valuable today--the ongoing Bitkeeper thread, for example). It is the FSF who, in the GPL, skillfully used copyright law to defend our interests instead of letting us continue to be unequal players in someone else's license (like the APSL which the OSI puts their stamp of approval on and the FSF considers non-free). The FSF is grateful that the Open Source movement has brought so many people to using the GNU GPL and other Free Software licenses, but the FSF warns against licenses that don't defend all of the community's interests. Meanwhile some notable members in the Open Source movement offer vicious words (and I'm not the first person to notice this).

    1. Re:Establishing the GNU GPL's place in history. by Xerithane · · Score: 1

      I mentioned Eben Moglen, not RMS. I don't know why you are railing against RMS here. But since you're now trying to change the subject and talk about RMS winning that award, I'll offer that he was right. Linus Torvalds contributed a piece of the puzzle--a good piece, a needed piece, but not the framework by which the rest of the pieces had been collected for years before Torvalds arrived on the scene.

      No, you questioned my dislike/distrust for the FSF based on a comment I made about them. I'm not changing the topic, I responded to something you said. Hoping that the added points of clarity would help you understand my point. I don't really care if you think I'm trying to change the subject, when I'm responding to you. That's your problem.

      GNU/FSF is over-rated, and is so widely recognized because of their license and not what they have accomplished. GCC is their best work, and even that is optional now. Linus has done more for Linux (and GNU) than any single member of FSF. Care to prove me wrong? Then find a total of code/documentation, submissions, and activity based on each person and see how it ads up.

      The FSF was never a part of the Open Source movement, they began the Free Software movement over a decade before the Open Source movement came along.

      Yes, and because of their views the Open Source movement was necessary. They are too extreme, especially RMS. They have their own views of law, life, and liberty. These do not coincide with a lot of what other people think and believe in. Hence, why Open Source has more of a foothold than the FSF does.

      If either organization (FSF or OSI) is bitter about the other's success, it is probably OSI being bitter about the FSF's success.

      What FSF success? FSF hasn't succeeded at anything. They've produced a few utilities and a compiler. That is hardly a success when compared to what is under the OSI umbrella.

      After all, the GNU General Public License is the most widely-used license in both movements.

      Widely-used by deployment or software packages? Either way, the GPL is a license that would have existed under a different name had it never been authored by the FSF. If the biggest success the FSF can claim is a license, than they are extremely lacking in what they have accomplished.

      The FSF is grateful that the Open Source movement has brought so many people to using the GNU GPL and other Free Software licenses, but the FSF warns against licenses that don't defend all of the community's interests. Meanwhile some notable members in the Open Source movement offer vicious words (and I'm not the first person to notice this).

      The more vocal proponents in the FSF attack the people who help them the most. They should have been praising Linus' contribution towards Open Source, instead of berating his success by bitter jealousy over him accomplishing what they couldn't (To provide an operating system that is unencumbered by copyrights or patents.)

      The problem with the FSF is that they believe the most important aspect of what is "Free Software" is political and ideological. OSI understands that it's technical at the core, and political/ideological on the outside.

      Because of that, the FSF will always have zealots and opponents. I personally will not follow anybody like RMS. You are free to do as you wish, but don't expect to change my mind.

      On a side note, my off-handed mention of the FSF and my distaste for their philosophies has taken up your entire comment, completely changing the subject of the original discussion. It just goes into, "Software licenses can be handled under contract or copyright law." I'm not sure why it went into such a deep thread... ah well, I'll spit my venom about the FSF more if you wish.

      --
      Dacels Jewelers can't be trusted.
  492. Re:Who's codes' on first? What license is on secon by Curtman · · Score: 1

    "By SCO's argument, they would own all of Unix, Linux, BSD, AIX, etc"

    Except that IBM aparently licensed those modules under that restrictive license, thereby agreeing to its terms, then copied that same code into the Linux kernel, not BSD. And according to them, they do own Unix and AIX, thats what this is all about, those modules were never part of SCO's product, just under the unmbrella of the SysV codebase licens. What remains to be seen, is if IBM doesn't have the right to relicense its own code, if they were legally encumbered by a more free license of their own before licensing it under the Unix one, or if thats even a legal restriction to begin with.

    At least as far as I understand it, and IANAL too.

  493. SEC and Stock manipulation by Anonymous Coward · · Score: 0

    Why doesn't the SEC bust SCO for fraud and stock manipulation?

    By putting GPL and open source in UNIXWare and SCO products they are in fact the poachers. Take DNS/Bind, Sendmail, Perl, awk, sed and others out of their products.

    Didn't the GPL license say something about incorporating the code in derived products make it public domain?

    Does not the letters sent to corporations amount to extortion as in fact no legal battle has been won nor proved?

    Microsoft sponsored terrorism and FUD?

    If we didn't buy into products that had law suits, we would see Microsoft broke and out of business. Don't let FUD (Fear and Uncertanty for Dummys) fool you --- this is the new way to make money when you can't do anything else, corporate extortion, business of the new century.

  494. I will consider your services. by Anonymous Coward · · Score: 0

    However, don't, don't, don't send me your names if you want to sue SCO, please
    neg----pos----neg (ah shucks)

    I will consider your services, If you tell me to don't again. :-)

  495. Daemons are attacking HELP! by ratfynk · · Score: 1
    Let me see /=\ dir=dir, mkdir=makedir, ifconfig=ipconfig ......etc who is it that was cpn who too? cp=cp! If this is true then there is no such thing as Microsoft either! IBM was using unix and also originally hired Gates and Co. to put together an OS remember. Until Unix and the idea of an operating system for computers can be called public domain this is the shit that one can expect. That is why I would put my money on Tandy OS9, or that funky British firm or even OS2 instead........... atleast they tried to do things differently, OH shit what am I talking about you still need a C compiler, well I guess Intel is up the Walnut Creek as well and will have to pay their ransom to SCO. But I do not C what C has to do with it.

    Dear (Denis) of Rithciedom art thou in heaven? I am in a C based DLL hell. BSD, MS and Linux are all sending daemons to do their bidding on my electron speaking Oracle, and I am locked in a shell.

    --
    OH THE SHAME I fell off the wagon and use sigs again!