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.

156 of 1,388 comments (clear)

  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 eupheric · · Score: 4, Funny

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

    3. 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.

    4. 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
  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 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?
    2. 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
    3. 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.

    4. 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.

    5. 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.

    6. 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.

    7. 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.

    8. 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).

    9. 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.

    10. 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.

    11. 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.
    12. 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.

    13. 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.

    14. Re:The scary thing by Surak · · Score: 4, Interesting

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

    15. 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.

    16. 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

    17. 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 !
    18. 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
    19. 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.

    20. 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.
    21. 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).

    22. 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.
    23. 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
    24. 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.

    25. 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
  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!

  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 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!
    3. 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".
  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?

  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.

  7. 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 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!
  8. 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.
  9. 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 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.

    2. 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;
    3. 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?
  10. 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 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
  11. 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.
  12. 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 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!

    4. 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.
  13. 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 :/"

  14. 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

  15. 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
  16. 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
  17. 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?
  18. 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
  19. 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.

  20. 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?

  21. 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?

  22. 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

  23. 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:

  24. $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
  25. 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
  26. 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.
  27. 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.

  28. 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

  29. 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.
  30. 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
  31. 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 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
  32. 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.

  33. 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?

  34. 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
  35. 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.

  36. 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.

  37. 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
  38. 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.

  39. 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 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...

  40. 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
  41. 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 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)

  42. 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.

  43. Please explain by lildogie · · Score: 5, Interesting

    Why can't someone who got the extortion letter subpoena SCO to identify the infringing code?

  44. 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.
  45. 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.

  46. 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.

  47. 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.

  48. 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
  49. 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.

  50. 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.

  51. 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 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.

  52. 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!
  53. 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

  54. 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.

  55. 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!
  56. 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.

  57. 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

  58. 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!"
  59. 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

  60. 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.

  61. 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 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.

    2. 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.

    3. 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.

    4. 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
    5. 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.

      --
      .
  62. 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

  63. 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.

  64. 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
  65. 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
  66. 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 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/
    3. 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?)

    4. 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.

  67. 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
  68. 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).

  69. 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
  70. Re:Will someone send me a free copy? by Anonymous Coward · · Score: 3, Funny

    req@semiotek.com

  71. 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.

  72. 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.

  73. 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?

  74. 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
  75. 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/
  76. 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?
  77. 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.

  78. 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.

  79. 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

  80. 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 :)

  81. 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.

  82. 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)

  83. 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
  84. 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.

  85. 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$.)

  86. 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.
  87. 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.

  88. 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.

  89. 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?
  90. 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.

  91. 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.

  92. 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.
  93. 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.