Slashdot Mirror


SCO Announces Final Termination of IBM's Licence

ickle_matt writes "SCO have announced the final termination of IBM's UNIX license, despite Novell telling them they can't. Interestingly enough there's a new set of "stolen code" figures in the release - 'approximately 148 files of direct Sequent UNIX code to the Linux 2.4 and 2.5 kernels, containing 168,276 lines of code. This Sequent code is critical NUMA and RCU multi-processor code previously lacking in Linux. Sequent-IBM has also contributed significant UNIX-based development methods to Linux in addition to the direct lines of code specified above.' "

807 comments

  1. Interesting... by mjmalone · · Score: 4, Interesting

    It's interesting that SCO is taking such drastic measures such as the license termination and licensing linux to end users before they even go to trial. The logical conclusion one draws from such measures is that they do not have a case, and do not think they can win. I can't believe that the court system is allowing this to occur, but I am willing to bet that IBM will not honor SCO's license termination and there will likely be either an addition to the current IBM suit against SCO, or a new one regarding thies termination.

    Also, aren't the NUMA and RCU multi-processor patents owned by IBM? SCO might own some of the code, but since they are licensing IBM's patents IBM could sue them for infringing on their patents. Is this part of the current IBM v SCO lawsuit?

    1. Re:Interesting... by aed · · Score: 4, Interesting

      Also, aren't the NUMA and RCU multi-processor patents owned by IBM? SCO might own some of the code, but since they are licensing IBM's patents IBM could sue them for infringing on their patents. Is this part of the current IBM v SCO lawsuit?

      Maybe. As far as I understand the stories, IBM has written NUMA and RCU code for their System V based Unix (AIX)
      IBM's System V license seems to state that when they add code to their SysV (==AIX) that code has to be treated as the rest of the SCO owned SysV code. So IBM wrote some code, included it in SysV/AIX, and now they can't include the exact same code in Linux, because of their SysV contracts with SCO...

    2. Re:Interesting... by u-235-sentinel · · Score: 5, Insightful

      "Also, aren't the NUMA and RCU multi-processor patents owned by IBM? SCO might own some of the code, but since they are licensing IBM's patents IBM could sue them for infringing on their patents. Is this part of the current IBM v SCO lawsuit?"

      It was my understanding they were not suing for use of those products though they probably should. What I find interesting is SCO terminates the license violating their agreement with Novell. I wonder if they can be sued by Novell for violating the contract. Exactly what SCO 'claims' IBM did.

      SCO claims IBM can't be trusted because they violated a contract and now SCO goes out of their way to violate another contract. Sounds like an internal problem with the company. I strongly suggest they see a shrink. These guys can't see straight anymore.

      --
      Has Comcast disconnected your Internet account? Same here. You can read about it at http://comcastissue.blogspot.com
    3. Re:Interesting... by endeavour31 · · Score: 2, Informative

      Actually, SCO is simply asserting what it considers to be a legal right over the software via licensing. Their legal arguments would be weaker if they did not take steps to protect their IP. Please note I am NOT taking SCO's side here but these events are perfectly reasonable from a legal point of view as strategic posturing.

      Courts are just a forum for dispute resolution - don't confuse this with justice.... an entirely different concept.

    4. Re:Interesting... by Thom-in-NC · · Score: 5, Informative

      There is an interesting article "Novell letters throw new light on SCO-IBM case" published in The Age that discuss letters sent to SCO by Novell asserting that Novell has "the right to compel SCO to waive or revoke any of its (SCO's) rights under the contract [involving SCO, IBM, and Novell]." In the letters Novell basically tells SCO that SCO cannot terminate IBM's license. These letters were apparently used as exhibits in IBM's countersuit of SCO.

      --
      -- Signature withheld by popular demand.
    5. Re:Interesting... by MoneyCityManiac · · Score: 5, Insightful

      As far as I can tell, here's the SCO/IBM problem... I'm sure many /.ers will correct me if I'm wrong. :-) Sequent made a contract with SCO many years ago. The important part of the contract, according to SCO, is this (taken from the press release, empahsis mine): SCO's System V UNIX contract allowed Sequent to prepare derivative works and modifications of System V software "provided the resulting materials were treated as part of the Original [System V] Software." Restrictions on use of the Original System V Software include the requirement of confidentiality, a prohibition against transfer of ownership, and a restriction against use for the benefit of third parties. Now IBM has its own seperate license for developing AIX, their UNIX brand which doesn't have that whole "resulting materials were treated as part of the original software" clause. Basically, IBM's contract allows it to derive all it wants and SCO does not own it. Sequent develops some nifty NUMA and RCU multi-processor code for its version of UNIX. But IBM goes and buys Sequent. Sometime later, IBM adds said nifty code to Linux. Here's where the legality of IBM's move comes into question... as previously mentioned, IBM is allowed to go and create derived works from UNIX and retain ownership of said works. Because it owns the work, its allowed to add that work into Linux. But SCO claims the RCU/NUMA code was developed under Sequent's contract, which means that derrived work is owned by SCO, and not IBM. Ergo, IBM should not have been allowed to add the code to Linux. That's what I make of it anyways. Whether SCO has a case or not is up to the lawyers/courts to decide.

    6. Re:Interesting... by japhmi · · Score: 5, Interesting

      IBM's System V license seems to state that when they add code to their SysV (==AIX) that code has to be treated as the rest of the SCO owned SysV code.

      However, IBM (and Sequent before them) has made very sure that they wrote up a general outline of how the process works, and then made an implementation on AIX (and Dynix/ptx). They then made a very similar implementation on Linux. As long as they can show that both implementations came from the general outline, there should be no problem.

      Heck, they should be able to argue that they can copy their stuff from AIX to Unix as long as there is a general outline. They may be able to argue that as long as they wrote it, and nothing of Unix comes out to the public, that they're in the clear.

      --
      "Giving money and power to government is like giving whiskey and car keys to teenage boys" P. J. O'Rourke
    7. Re:Interesting... by Alan+Partridge · · Score: 2, Interesting

      " But SCO claims the RCU/NUMA code was developed under Sequent's contract, which means that derrived work is owned by SCO, and not IBM."

      Presumably IBM would say "but the Sequent code when added to Linux does not infringe that arrangement".

      Wouldn't they? Don't know how that would help AIX though...

      --
      That was classic intercourse!
    8. Re:Interesting... by Dav3K · · Score: 2, Interesting

      OR, SCO strongly believes that they have an unbeatable case and are proceeding along this path with the certainty of a lemming marching toward the sea. I really can't see any company continuing on like this if they didn't think they had at least a shot of winning something. Overblown? definately. A complete hoax? Definately not.

    9. Re:Interesting... by nuser · · Score: 5, Insightful
      As far as I understand the stories, IBM has written NUMA and RCU code for their System V based Unix (AIX) IBM's System V license seems to state that when they add code to their SysV (==AIX) that code has to be treated as the rest of the SCO owned SysV code.

      That was a few days ago. Today SCO are claiming the same thing but in relation to Sequent (now owned by IBM). Basically claiming that any code Sequent added to their Unix has to be treated as if it is part of the original Sys V code base.

      The story is confusing in mentioning Novell. It seems Novell are a party to the original IBM deal, and can prevent termination of IBM's AIX license. I'm not sure it follows that Novell have the same position in relation to the Sequent / SCO deal. I guess we'll have to wait for IBM to respond.

    10. Re:Interesting... by Anonymous Coward · · Score: 0

      an addendum to the contract with AT&T specifies that all code IBM writes on their own (i.e., without copying the code from SysV or having the developer look at SysV code while programming) is IBM's property.

    11. Re:Interesting... by Edward+Scissorhands · · Score: 5, Interesting

      This is INCORRECT. As I have written in a paper available here, IBM's contract with AT&T (and now SCO) explicitly states that code developed by IBM is the property of IBM and is NOT a derivative workof AT&T (now SCO).

      HOWEVER, the contract between Sequent and AT&T has NOT been made public by SCO nor IBM and so it is not clear to third parties whether or not the Sequent-AT&T agreements give Sequent the same rights as were given to IBM, though one may speculate based on the format of the IBM-AT&T agreements (see my article for full details).

      Fundamentally, this is a contract law case in which the status of the Sequent-AT&T and IBM-AT&T agreements are defined. In other words, when IBM bought Sequent, what happened to the Sequent-AT&T agreement? Were it made null and all dealings between Sequent and AT&T now under the stipulations of the IBM-AT&T agreement? Or is it the case that code developed by Sequent is still bound by the original Sequent-AT&T contract?

      Someone more familiar with contract law will have to respond; however, I believe that if in fact ANY code developed by Sequent BEFORE it was bought by IBM AND that code was placed in a SysV derivative (in this case probably Dynix/ptx) AND that code was placed in the Linux kernel, then it may very well be the case that SCO is standing of firm legal ground on that issue.

      There are, of course, other details to this situation which may invalidate SCO's claims to right of the code, such as the GPL, and unclean hands doctrine (both arguments which IBM has included in its rebuttal) but I suppose we'll have to wait and see what happens. Also, read my article. :)

    12. Re:Interesting... by minus_273 · · Score: 3, Funny

      dont you just hate viral licences like that ;)

      --
      The war with islam is a war on the beast
      The war on terror is a war for peace
    13. Re:Interesting... by rking · · Score: 2, Insightful

      But SCO claims the RCU/NUMA code was developed under Sequent's contract, which means that derrived work is owned by SCO, and not IBM.

      Close, except that they don't claim to OWN the code, they claim that IBM/Sequent is contractually prohibited from distributing that code (which IBM/Sequent owns) hence breach of contract and trade secret violations.

      Of course the theory that code with no Unix code in it is in some way derivative of Unix code just because it has ALSO been added to Unix isn't likely to get anywhere, but that's the straw they're clutching at.

    14. Re:Interesting... by phoebus1553 · · Score: 1

      So if that is the case, then IBM should never have owned the RCU/NUMA stuff anyway, it should have been transferred to SCO at the time of the sale of Sequent to IBM. Sounds a lot like the Cisco stuff, you can buy the hardware, but you don't get a license to the software on it because that's nontransferrable.

      So who's at fault now? I dunno

      --
      ----- - The beatings will continue until morale improves
    15. Re:Interesting... by Waffle+Iron · · Score: 5, Funny
      In other words, when IBM bought Sequent, what happened to the Sequent-AT&T agreement? Were it made null and all dealings between Sequent and AT&T now under the stipulations of the IBM-AT&T agreement? Or is it the case that code developed by Sequent is still bound by the original Sequent-AT&T contract?

      It just goes to show that whether it's object-oriented programming or contract law, multiple inheritance is likely to be hard to understand.

    16. Re:Interesting... by Tuqui · · Score: 0, Redundant

      That contract is more "VIRAL" than GPL!!

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

      Indeed. At least with the GPL you retain your own Copyrights and are free to relicence your work.

    18. Re:Interesting... by macdaddy357 · · Score: 1

      Speaking of termination, why doesn't IBM just make all those assclowns at SCO sleep with the fishes? Big Blue aren't exactly known for being nice guys.

      --
      How ya like dat?
    19. Re:Interesting... by aug24 · · Score: 1
      Interesting post, thanks. I read all this slightly differently to you, as hinging on the phrase:

      derivative works and modifications

      where presumably SCO will say that the disputed code is a modification of SysV, but IBM will say that it is an addition to SysV. IANAL, but I think a judge will find that one pretty easy to call ;-)

      J.

      --
      You're only jealous cos the little penguins are talking to me.
    20. Re:Interesting... by Anonymous Coward · · Score: 0

      It only takes 8 years...

    21. Re:Interesting... by Anonymous Coward · · Score: 0

      > IBM's System V license seems to state that when they add code to their SysV (==AIX) that code has to be treated as the rest of the SCO owned SysV code.

      That does seem to be the crux of SCO's point.

      Boy, and they said the GPL was "viral"!

      Gates should get wind of this. A quick change to the EULA and bamm, all your programs are "belonging" to him. Run once on Windows, banned from running anywere else.

      Cute, but somehow I doubt it will stick. Gez, It really had better not -- or non-Microsoft programmers can pretty much go home and take up gardening.

      And, the kicker. Alot of BSD code made its way into a number of AT&T based Unix variations. Does SCO now own BSD?

    22. Re:Interesting... by Anonymous Coward · · Score: 0

      There is an interesting parallel between SCO's licensing scheme and the "GPL Cancer" that we've been warned of by Microsoft.

      Just my 2 cents worth of FUD =)

    23. Re:Interesting... by Edward+Scissorhands · · Score: 2, Interesting

      I suppose, though, since no one has as of yet explained it to me, I can't say I've tried to understand it. Got any info?

      Oh, what the hell, I'll guess. I'm guessing that with OOP, how multiple inheritance is defined is dependent on what language you are talking about, and in contract law it is dependent on the law and on precedent.

      An approach that I would personally favour in both programming and law is that where two classes (contracts) need to be parents of another class, where the two classes (contracts) have the same functions/variables (clauses/definitions), the class (contract) lower down in the hierarchy (chronology); i.e., the more immediate parent node, takes precedence.

      This strikes me, off the top of my head, as being fairly reasonable at least in programming. I don't really know how the hierarchy would work in contract law. Again, someone more knowledgeable will have to comment.

    24. Re:Interesting... by dbialac · · Score: 1
      It's interesting that SCO is taking such drastic measures such as the license termination and licensing linux to end users before they even go to trial



      More specificaly, all of this is designed to create FUD. Microsoft is 100% behind this. They win if SCO wins -- Linux may no longer be free, or at least not until key components are rewriten. Even then, the name is tarnished. If SCO loses, Microsoft can go around and say "See, the GPL took SCO's IP!"



      Gates really doesn't need a license for UNIX as they haven't marketed XENIX in years. The license is nothing more than a conduit to funnel money to SCO for doing the lawsuit. I'm sure there was some unwritten agreement between Bill and SCO where if they took the legal action, MS would finance it. Further, Microsoft is undoubtedly the company who bought the licenses for Linux the other day from SCO.



      What's interesting about this is the fact that SCO is charging license fees for code they don't have the rights to charge for. Why? They don't own the code.



      Bill Gates serving 10 years for manipulating markets, libel, fraud, extortion, etc.? The SEC does not look kindly upon this kind of stuff. Maybe something like this will expose him for the crook he really is.

    25. Re:Interesting... by Anonymous Coward · · Score: 0

      ...or an elaborate and successful pump and dump scheme. Did you miss the bit about SCO executives selling off 1.3 million dollars worth of stock, from options priced at pennies on the dollar of current inflated prices, in the past two months?

    26. Re:Interesting... by VivianC · · Score: 2, Insightful

      OR, SCO strongly believes that they have an unbeatable case and are proceeding along this path with the certainty of a lemming marching toward the sea. I really can't see any company continuing on like this if they didn't think they had at least a shot of winning something. Overblown? definately. A complete hoax? Definately not.

      It could be the mother of all bluffs. They are trying to become anoying and costly enough to justify being bought out as a more cost effective solution that further litigation. Plus, IBM and other companies involved also need to factor in the risk of getting a judge who would rule for SCO and make everything more costly through appeals.

      SCO leaders also appear to be hedging their bets by selling off some shares as the price goes up.

      --
      Viv

      Gmail invites for ip
    27. Re:Interesting... by ichimunki · · Score: 1

      Fascinating article and excellent links to boot! Thank you.

      --
      I do not have a signature
    28. Re:Interesting... by urulokion · · Score: 3, Informative
      It's interesting that SCO is taking such drastic measures such as the license termination and licensing linux to end users... I can't believe that the court system is allowing this to occur, but I am willing to bet that IBM will not honor SCO's license termination and there will likely be either an addition to the current IBM suit against SCO, or a new one regarding thies termination.

      I don't thing a court would issue an injunction against IBM, as that would effectively nullify IBM's contract. I can't see that happening. And IBM doesn't have to worry about SCO's termination their license. SCO can't terminate the license, period. It's written in contracts.

      From SCO's Exhibit D

      1 No Additional Royalties. Upon payment to SCO of the consideration in the section entitled "Consideration", IBM will have the irrevocable, fully paid-up, perpetual right to exercise all of its rights under the Related Agreements beginning Jan 1, 1996 at no additional royalty fee. ...

      Note the terms irrevocable and perpetual. I don't think it can be made any plainer.

    29. Re:Interesting... by j7953 · · Score: 4, Interesting

      Thanks for that explanation.

      Now what I am wondering is, even if it was not legal for Sequent/IBM to add the code to Linux, how can SCO sell a license to use that code with Linux if they don't even own it?

      --
      Sig (appended to the end of comments I post, 54 chars)
    30. Re:Interesting... by Dav3K · · Score: 1

      I agree there is a lot of bluffing going on. However, for the SCO execs to continue down this path with nothing to substantiate a valid point of contention is ridiculous. SCO probably thinks their case will fail, hence the FUD, but they obviously feel there is enough strength in their case to fire off a lawsuit at IBM without incurring barratry, or criminal charges. It is one thing to get counter sued and have your company go bankrupt (which it is slowly doing anyway) and quite another for executives and lawyers to face personal criminal charges. They must think they have enough to cover their asses in case it goes bad for them or they would not have had the balls to pull this in the first place.

      After all, a whole lot of bad press can be a great thing if you know how to spin it.

    31. Re:Interesting... by Anonymous Coward · · Score: 0

      they do not have a case

      Oh, really? You mean, maybe before today somebody thought they had one?

    32. Re:Interesting... by LehiNephi · · Score: 1

      The thing is that their shares are no longer skyrocketing in response to their claims. Temporarily creeping up, perhaps.
      SCOX

      --
      Help find a cure for cancer. Join the [H]orde
    33. Re:Interesting... by jdhutchins · · Score: 1

      I wonder what SCO's claims are. I highly doubt that the AIX kernal and Linux kernal are similar enough to simply use the same code. So IBM would have had to do a rewrite of their code, or use an entirely different codebase. If the codebases are entirely different, then SCO can't claim it's a derivative work, because although they do the same thing, it's different code. If they did a rewrite, I'm not sure what the legal standing would be, if it's still AIX code, or if it's not.

      Disclaimer: I'm not a lawyer and I don't know very much about the AIX or Linux kernals, but these are my best guesses.

    34. Re:Interesting... by ksheff · · Score: 1

      So if one believe's SCO's view of things, companies were paying another company (AT&T originally) so that they would not have any control over technology that they created, patented & copyrighted.

      So why did Unix splinter?

      --
      the good ground has been paved over by suicidal maniacs
    35. Re:Interesting... by rcamans · · Score: 0

      This is only true if RCU and NUMA are derivitive works, something that is yet to be addressed. If they are original works done for Unix of any sort, that does not automatically mean they are derivitive works. Or am I wrong?

      --
      wake up and hold your nose
    36. Re:Interesting... by qtp · · Score: 1

      I find it hard to believe that IBM would agree to a license that would prevent them from licensing thier own code or using it in another project. If SCOs license dictates this as you say it does, then IBM would be prevented from using anything they wrote for AIX in any other non-AIX implementation, including any of IBMs other OS. It would also mean that any AIX implementation would become SCOs "trade secret" property.

      I seriously doubt that that is the case. IBM is known to be quite proficient at prtecting thier own interests.

      --
      Read, L
    37. Re:Interesting... by BigFire · · Score: 1


      Their stock is currently on a downward slide. They need something to inflamed the imagination of the un-informed investors into buying these stocks.

    38. Re:Interesting... by LauraW · · Score: 2, Informative
      This is totally off-topic, but what the hell; it's definitely more interesting than SCO's latest blather.

      >the class (contract) lower down in the hierarchy (chronology); i.e., the more immediate parent node, takes precedence.

      In the OOP languages that I'm familiar with, that's exactly what happens. It could be argued that this is the whole point of OOP, or at least a major one. The interesting case is when a language supports true multiple inheritance and a subclass directly inherits from two classes that have the same functions. (I mean that both classes are "parents", rather than one parent and one grandparent.) My C++ is rusty, but if I remember right it handles this case by saying that the parent class that was listed first in the declaration wins. Java (and C# I think) solves this by disallowing multiple inheritance.

      For contracts, my understanding is that if a later contract between two parties explicitly contradicts an earlier contract, the later one wins. By explicitly, I mean that the later contract says that it's amending the earlier one, e.g. "This provision replaces section 3, paragraph 7 of the contract between X and Y dated Sept 2, 1997, hereinunder(1) attached as amendment A," or equivalent legalese. On the other hand, if the contracts are just plain contradictory (or can be interpreted that way), then the later one will usually win, but only after the lawyers and judges argue about it for a long time.

      No, IANAL, but I've had to work with them a bit.

      (1) I think that's the first time I've ever used the word hereinunder. Someone save me before it's too late!

    39. Re:Interesting... by Durandal64 · · Score: 1

      A court has not determined that the IP in question is, in fact, SCO's. They have no more right to claim the Linux kernel as their IP than I do. Thus, all they are doing is fear-mongering and spreading FUD. No one is obligated to pay them anything for licensing, because they have not demonstrated ownership of the IP in question. Until a court says differently, SCO does not own Linux, nor is anything in the Linux kernel the property of SCO.

    40. Re:Interesting... by Anonymous Coward · · Score: 0

      You a canadian is trying to argue US contract law?

      So Mr. Lawyer, how can code "placed" (your words) into a SysV derivative (AIX) be a derivateve of SysV Unix and thus be bound by said contract? If it was "placed" then clearly it was developed OUTSIDE of said SysV derivative (AIX) and thus is not a derivative work in and of itself.

    41. Re:Interesting... by digitalunity · · Score: 1

      On the other hand, if the contracts are just plain contradictory (or can be interpreted that way), then the later one will usually win
      Not necessarily. It could be said, with legal precedent, that the second contract is invalidated by the first because the company didn't have the legal means to fulfill contract obligations of the second contract. It would probably be nullified. Here's an example
      Contract A: company 1 signs contract with company 2
      Contract B: company 2 signs contract with company 3, but A & B's clauses are contradictory.

      Contract B is deemed null and void by a court because company 2 didn't have the legal means to enter into contract B.

      I've oversimplified this, and this isn't true for all cases(most commonly, when any of contract A's terms are illegal), but this is generally true.

      AFAIK, the only time contract B would supercede contract A is if both contracts were between the same parties. However, I'm not a lawyer and this isn't legal advice. However, I have taken a few classes in contract law(many years ago).

      --
      You can't legislate goodness. Let each to his own destiny, by will of his freely made choices.
    42. Re:Interesting... by Wakko+Warner · · Score: 1

      I am willing to bet that IBM will not honor SCO's license termination and there will likely be either an addition to the current IBM suit against SCO, or a new one regarding thies termination.

      Well, I can tell you that the F500 company I work for still happily purchases and uses AIX all the time. I've got the purchase orders to prove it. So, whatever SCO did today or in June really doesn't matter one bit to IBM, to myself, or to the rest of the computing world.

      - A.P.

      --
      "Remember when the U.S. had a drug problem, and then we declared a War On Drugs, and now you can't buy drugs anymore?"
    43. Re:Interesting... by scrytch · · Score: 1

      > Also, aren't the NUMA and RCU multi-processor patents owned by IBM?

      Doesn't matter, the suit is about copyright. If SCO licensed the patent, then produced code with IBM, Novell, cobbler elves, and the Trilateral Commission ... anyway, if they own the copyright to the source code of an *implementation* of the patent, and that copyright is infringed, they still have a case. In fact, if the code is indeed copied verbatim, then someone did a bad somewhere, and the code need to be removed.

      SCO of course doesn't want the code removed, as their own statements have made clear. This has bad faith and estoppel by laches written all over it... IANAL, but IBM seems to agree.

      --
      I've finally had it: until slashdot gets article moderation, I am not coming back.
    44. Re:Interesting... by Anonymous Coward · · Score: 0

      Actually, the original contract was between AT&T and Sequent. Later AT&T sold UNIX copyrights & contracts to Novell, who later sold them to SCO. To my knowledge, the original Sequent & AT&T contract has not been made public. It is possible that the AT&T & Sequent contract is much more favorable to SCO than the AT&T & IBM Contract, but we don't know yet. Even if the original contract specified that derivative works were treated as part of the Original system V software, it is possible the concept of unclean hands could ruin SCO's legal ambitions.

    45. Re:Interesting... by Ian+Lance+Taylor · · Score: 1

      Also, aren't the NUMA and RCU multi-processor patents owned by IBM? SCO might own some of the code, but since they are licensing IBM's patents IBM could sue them for infringing on their patents.

      I'm not sure exactly what you're getting at, but IBM could only sue SCO for patent infringement if SCO's code actually uses NUMA and RCU. There is no particular evidence that it does.

    46. Re:Interesting... by Anonymous Coward · · Score: 0

      Cringley covered the Sequent code ownership tangle in an earlier column.

      http://www.pbs.org/cringely/pulpit/pulpit2003061 9. html

      Relevent quote being;

      "According to Laura Didio of the Yankee Group, "[SCO's] claims are not limited to just one area of the Unix System V kernel. SCO claims there are multiple instances of copyright violations. SCO said these include: NUMA (Non Uniform Memory access) a mechanism for enabling large multiprocessing systems, RCU (Read Copy Update) (and) SMP. All of the aforementioned functions represent high end enterprise performance and scalability functionality portions of the code."

      And all those parts appear to have come originally from Sequent Computer Systems, now owned by IBM. RCU was implemented in Sequent's DYNIX/ptx, a legally-licensed derivative of System V, in 1994 for SMPs and in 1996 for NUMAs. The RCU code inside the Linux version 2.2 kernel even includes the name of Paul McKenney, who was a major contributor to both the DYNIX and Linux versions. The same guy wrote both pieces of code and probably did do some cutting and pasting between them. To SCO, this is the smoking gun that makes IBM viable for treble damages because SCO's UNIX licenses cover derivative works. That means if I have a System V source code license and I change that code, any changes I make live under the original UNIX copyright.

      So that makes IBM guilty, right? Wrong.
      If we go back to the Sequent RCU research papers published about this work, we'll see they are very carefully written to present a general way of solving this problem on almost any multi-threaded operating system. It is a general solution. In the key paper, the first mention of some version of UNIX doesn't come until page five under the "implementation" section. They did this work -- work that was supported by a variety of federal grants and involving more companies than just Sequent -- to develop a concept that they then implemented on UNIX.

      Now let's think about the UNIX license and how it concerns intellectual property claims. I am not a lawyer, but unfortunately, I have been involved in several copyright and trademark cases, and believe I know the law in this area. SCO looks inside the System V source code and finds this implementation. They look in the Linux source code and find a similar or identical implementation. Sure enough, both can be traced to the same programmer at Sequent, which is now owned by IBM. And SCO, as the UNIX IP enforcer, owns the license for all derivative works -- all derivative UNIX works. David Boies sees this as his smoking gun and he's going to use it. But David Boies is not an IP lawyer by trade. This is key.

      The IBM lawyers (who ARE IP lawyers) will strongly argue that none of this matters since we have a case of a single person who did two very similar implementations based on his earlier research. Both his UNIX and Linux versions (works B and C) were derived from his original research (work A) which was not exclusively limited to UNIX. His paper shows that was the case and while SCO may see it as the smoking gun, IBM will see it as the proof of innocence.
      What SCO owns (forgetting for the moment Novell's contrary ownership claim and perhaps AT&T's) is the copyright on this particular work as applied to UNIX. But Linux is not UNIX, so applying the same ideas -- even the same code if it comes originally from an upstream source -- is not necessarily copyright infringement.

      Say I write a new high-level programming language, then do nearly identical implementations of that language for UNIX and Linux and the UNIX version is made part of some official UNIX distribution. Does that mean the Linux version violates the UNIX copyright? No. But I wrote both versions and the code is identical. Surely that is a copyright violation? No. This isn't a matter of clean rooms and virgins and reverse engineering, it is a matter of precedence and authorship. Sequent (now IBM) did not give up all its rights to the code when it was m

    47. Re:Interesting... by Meowing · · Score: 1

      See, there's that *thing* again, this assertion that the Sequent techniques were trade secrets. These techniques were patented. Patented techniques aren't trade secrets, by definition.

    48. Re:Interesting... by jcr · · Score: 1

      It's interesting that SCO is taking such drastic measures such as the license termination and licensing linux to end users before they even go to trial.

      Drastic and fictitious measures. SCO has no power to terminate IBM's UNIX licenses.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    49. Re:Interesting... by Anonymous Coward · · Score: 0

      > IBM has written NUMA and RCU code for their System V based Unix (AIX) IBM's System V license seems to state that when they add code to their SysV (==AIX) that code has to be treated as the rest of the SCO owned SysV code.

      Copyright NEVER "creeps", it NEVER becomes "one" with any other author's work. It is always a case of "your stuff" and "my stuff", brought together.

      To create a derivative you MUST merge two distinct works into one. RCU+Unix results in a derivative; RCU+Linux results in a different derivative. RCU, alone, is not a "derivative" of anything as it is an original work.

      Oh, and a work doesn't have to "stand on its own". You don't have to be able to "run" NUMA. It might be lines 10-15, 90-222, and 500-900 inside a Unix subroutine. Nonetheless, it is an original work and NOT a derivative of "Unix". The combination of those lines + Unix, and only that combination, creates a new derivative work based on Unix and NUMA.

      Even if RCU/NUMA was written "for" Unix, "order" doesn't matter. A work is a work. You wrote it, or I wrote it -- line by line. To be otherwise would imply a copyright holder holds sway over "use" of a work, when the law grants no such power.

      SCO says...

      "SCO's System V UNIX contract allowed Sequent to prepare derivative works and modifications of System V software "provided the resulting materials were treated as part of the Original [System V] Software." Restrictions on use of the Original System V Software include the requirement of confidentiality, a prohibition..."

      Indeed "RCU+NUMA+Unix" "results in" "AIX" and "Dynix/ptx", both of which are treated to this day as strictly propriatary works, just as the AT&T/SCO license demands. The resulting derivative IS being handled the same as SCO owned code.

      But "NUMA", "RCU", and "NUMA+RCU+Linux" are not the "the results of" any combination involving SCO's Unix. They simply are not derivative works of Unix, and not subject to being called such by SCO.

    50. Re:Interesting... by MuParadigm · · Score: 1


      Just read your analysis, and I want to say, "Really well-done".

      However, I disagree that the Sequent/ATT agreements give "ownership" of Sequent's derivative work to ATT. It seems that Sequent was simply required to treat the derivative work "as if" it were part of the original System V source.

      Since ownership was not given to ATT, when the code moved to IBM it would come under IBM's contracts rather than Sequent's.

      I'm not a lawyer. I think this is a debatable point, though, and may need a more sophisticated defense than the code that originated at IBM.

    51. Re:Interesting... by Anonymous Coward · · Score: 0

      Even if that's true and IBM and SCO end up duking
      it out in court for a few years, can't the linux community crank out it's own clean-room implementation and tell SCO to fuck themselves?
      Is SCO's business so fundamentally screwed that
      their legal team is their only remaining profit center?

    52. Re:Interesting... by screenrc · · Score: 1
      I read the opposite today, perhaps in ZNET.
      The reporter said that IBM was allowed to
      write code based on methods and concepts of system V, and distribute it,
      as long as IBM wrote it themself and did not
      copy from other people's copyrighted works.


      It seems SCO "discovers" more and more "violations"
      every day, but have yet to show proof. Maybe it
      time for me to join a similar racket and start
      sueing IBM for billions. Why not? I can also
      announce that thousant of files were stolen
      from me throught the decades and placed on Linux
      in open view, and yet I did not know about it
      until now that I need the money.


      Make no mistake, the SCO v.s IBM case is just
      the podium from where SCO circulates FUD, as
      instructed by Microsoft. Whover is is concerned
      by "who will win the lawsuit" is totaly missing the point.

    53. Re:Interesting... by packman · · Score: 1

      So if this code implementing NUMA and RCU is now part of the Sys V codebase - SCO basicly owns code (written by IBM/Sequent) which implement at least 2 patents of IBM?
      Couldn't IBM sue them for this because SCO doesn't have any licence for these patents but having "their" code commercially used and distributed?

      This would be a rather funny trial I think ;) :p

    54. Re:Interesting... by mpe · · Score: 1

      Maybe. As far as I understand the stories, IBM has written NUMA and RCU code for their System V based Unix (AIX) IBM's System V license seems to state that when they add code to their SysV (==AIX) that code has to be treated as the rest of the SCO owned SysV code. So IBM wrote some code, included it in SysV/AIX, and now they can't include the exact same code in Linux, because of their SysV contracts with SCO...

      And certain people moan about the GPL being viral... About the only was this could work is if SCO are claiming that their System V licence includes assigning copyright to SCO. Otherwise IBM's rights as copyright holders trump any agreement they may have made with SCO.

  2. IBM's solution by Anonymous Coward · · Score: 5, Insightful
    IBM failed to cure its breach of the Sequent-IBM contract, or to offer any solution whatsoever to cure its breach.

    That's not true. IBM's solution is simple. Since there is no breach, the offer to cure is contained in the countersuit.

    Tomorrow SCO's quarterly report comes out, sell your stock before the insiders can.

    1. Re:IBM's solution by TopShelf · · Score: 4, Interesting

      Case in point - an interesting article over at ComputerWorld about how IBM is pitching Linux to the banking industry, as a migration path away from OS/2.

      Those nefarious nogoodniks - trying to ensnare innocent customers in their illegal activities!!!

      --
      Stop by my site where I write about ERP systems & more
    2. Re:IBM's solution by pacman+on+prozac · · Score: 4, Interesting

      And part of that is....punitive damages (according to IBM press release)...IBM aren't just going after SCO for what they are owed...they are going to stop them ever doing this again. And lets not kid around, the normal damages from this case could run into hundreds of millions...

      Mcbride can stop chewing his pinky and mouthing off about "1 million dollars" now, cos that won't even pay for the ink to write all the 0's on the end of the cheque he will soon have to write :)

    3. Re:IBM's solution by akpoff · · Score: 2, Insightful
      "Clarifying" the name of the company by targeting "Sequent-IBM" may actually signal a change in SCO's tactics. SCO has previously claimed (generically they will claim) they were terminating IBM's license. As we've seen, they can't because of its irrevocable nature plus the fact that Novell won't go along. They now may claim (more precisely amend the suit to claim) only IBM's non-AIX-derived code lines are in contract violation. Sequent's license presumably doesn't have the same irrevocability and perhaps has more strict derivability clauses. Hence, SCO may try to claim that while IBM can distribute code developed under the AIX code line, Sequent had no such rights and since NUMA etc. were developed under the Sequent code line they're subject to interpretation under the license then in effect, i.e., Sequent's. It's a huge stretch, but it may be the only shot they've got left.

      So, in addition to the question of "derivative works", this suit now may hinge on the heritage of the code and the license it was developed under. It could come to questions of when IBM bought Sequent, when the code was developed and whether the $10M+ IBM paid Novell covers other Unix Sys V-derived code they later add in. In other words, did IBM buy a universal license for any and all Unix development, including code acquired through M&A, or just for AIX development? Do IBM have the (bought and paid for) right to move code developed for Dynix/ptx to AIX and hence Linux?

    4. Re:IBM's solution by Yxes · · Score: 1

      I have a link to listen to their report tomorrow at 11:00am EST and you don't have to signup with SCO to get it.

      http://ir.sco.com/visitors/event/build2/MediaPre se ntation.cfm?MediaID=8930&Player=2

      In case anyone is interested.

    5. Re:IBM's solution by Anonymous Coward · · Score: 0

      I think if I were in Utah right now, I'd be looking out for Blue Helicoptors and Men in Blue..

    6. Re:IBM's solution by JCCyC · · Score: 1

      Just pray to God that they don't send the Men in Mauve.

      (Whoever gets that reference earns my undying respect)

    7. Re:IBM's solution by hayden · · Score: 1

      I don't think SCO liked the "Go fuck yourself" reply from IBM. Some people are just too sensitive.

      --
      Nerd: Derogatory term typically directed at anybody with a lower Slashdot ID than you.
    8. Re:IBM's solution by bernywork · · Score: 1

      This is something that I couldn't believe.

      http://biz.yahoo.com/t/80/4661.html

      BROUGHTON, REGINALD C
      Senior Vice President

      Sold 70,000 shares over the past two months to the total of ~$843,000.

      He still has 120,000 shares, but at the same time... Rats leaving a sinking ship?

      --
      Curiosity was framed; ignorance killed the cat. -- Author unknown
  3. The next headline? by mao+che+minh · · Score: 5, Funny
    IBM announces the final termination of SCO

    Ahhhh.....I can dream, can't I?

    1. Re:The next headline? by oPless · · Score: 3, Funny

      <T3>They'll be back</T3>

    2. Re:The next headline? by Ian+Wolf · · Score: 1

      I wonder if Novell will have the cojones to back up their position and sue SCO.

      The way things are going this going to become a "Royal Rumble".

      Hmmm, anyone else think Ransom Love sounds like a Porn/Wrestling name?

      --
      "The words of the prophets are written on the Slashdot walls."
    3. Re:The next headline? by SpaceLifeForm · · Score: 5, Funny
      Or...

      SCO is S0C1

      For those not from the Mainframe world, a S0C1 is an abend code meaning 'Operation Exception'. That means the program attempted to perform an operation which is not legal.

      --
      You are being MICROattacked, from various angles, in a SOFT manner.
    4. Re:The next headline? by BrokenHalo · · Score: 1

      Well I'm well and truly from the Mainframe world, and I wouldn't have known about S0C1. But then there are more mainframe platforms in this world than IBM, no matter what the latter try to tell us.

    5. Re:The next headline? by roman_mir · · Score: 1

      Were those mainframe operation codes created by IBM by any chance? I guess they can tell what is legal and whatnot.

    6. Re:The next headline? by TomTraynor · · Score: 1

      My other favourites would be:

      OC2 - Priviliged Operation - what you require to look at their code

      0C4 - Protection Exception - what you get when you dont buy their license

      --
      Panic now, beat the rush!
    7. Re:The next headline? by jkabbe · · Score: 1

      I still giggle whenever I hear someone say "what's a S0C4?"

    8. Re:The next headline? by vex24 · · Score: 1

      I'm pulling for...

      "SCO SOL"

      --

      People shape laws. Not the other way around.

    9. Re:The next headline? by St.+Alfonso · · Score: 1

      SCO announces IBM is now on "double secret probation"; hires Dean Wermer as legal consultant.

    10. Re:The next headline? by njchick · · Score: 1
      Yes, it's used in IBM assember for S/360 and above.

      [OT] You have been befriended for your signature :-)

    11. Re:The next headline? by desktopheap · · Score: 1

      i actually cringed when i saw this one. s0c7 came to mind... ( data exception ) as well s806 (mainframe equivalent to 404)

      --
      Jesus died for your sins. Make it worth his time.
  4. Yahoo Mirror by Chaltek · · Score: 4, Informative

    To avoid the slowness of SCO's Cold Fusion, use this Yahoo! Finance mirror of the Press release:

    http://biz.yahoo.com/prnews/030813/law050_1.html

    1. Re:Yahoo Mirror by Anonymous Coward · · Score: 0

      Why not add to their broadband bill and just keep pounding away on their site?

    2. Re:Yahoo Mirror by donutz · · Score: 2, Funny

      To stick it to SCO, avoid the Yahoo Finance Mirror and go straight to the SCO press release:

      http://ir.sco.com/ReleaseDetail.cfm?ReleaseID=1159 95

    3. Re:Yahoo Mirror by orionware · · Score: 0

      Coldfusion is not what is making the site slow unless it's like version 2.

      Obviosuly you know nothing about coldfusion as the newer versions rival asp/.net in speed of delivery.

      --


      Karma means nothing to me, so suck it...
    4. Re:Yahoo Mirror by finkployd · · Score: 1

      Obviosuly you know nothing about coldfusion as the newer versions rival asp/.net in speed of delivery.

      Meaning it still sucks. Thanks for the update :P

      Finkployd

    5. Re:Yahoo Mirror by Anonymous Coward · · Score: 0

      It's not slashdotted. It's just running ColdFusion.

      Seriously though CFs biggest problem is stability under load. It's speed isn't _too_ bad under Linux.

  5. C'mon SCO! by Jonsey · · Score: 5, Funny

    Just release the infringing code lines so we can comment it out, doom your profits, and get on with our lives!

    Incidentally, they claim 2.5 kernels too... is that new? I thought only 2.4 was an issue.

    --
    I assert that my comment is only my opinion, not that of any employer, past, present or future.
    1. Re:C'mon SCO! by paitre · · Score: 1

      They've been claiming the infringing code is in 2.4 and later kernels for a while now...
      not new...

    2. Re:C'mon SCO! by Anonymous Coward · · Score: 0

      They claim 2.4 and later, usually 2.5 would come after 2.4...

    3. Re:C'mon SCO! by BoysDontCry · · Score: 2, Funny

      I'm using 2.6.0-test3 just to be safe!

    4. Re:C'mon SCO! by eXtro · · Score: 5, Informative

      2.5 isn't a from-scratch rewrite of the kernel so large portions of the kernel source code are common. Apparently the changes were introduced in the 2.4 kernel so the 2.2 kernel isn't a problem. The above isn't implying that I believe that there is any validity to SCO's fraudulent claims.

    5. Re:C'mon SCO! by Jonsey · · Score: 1

      Didn't know that. Thanks though... Perhaps I'll (need to) start keeping closer tabs on this now.

      --
      I assert that my comment is only my opinion, not that of any employer, past, present or future.
    6. Re:C'mon SCO! by colonwq · · Score: 1

      what about the 2.3.xx kernels? If 2.4.0 is bad, how about the last 2.3.xx?

      It sounds like they are throwing a wide blanket over all the current linux versions. :wq

      --
      -- Phase 1: Collect under pants Phase 2: ? Phase 3: Profit
    7. Re:C'mon SCO! by wirelessbuzzers · · Score: 1

      Just release the infringing code lines so we can comment it out, doom your profits, and get on with our lives!

      Riiiiiight... like you're going to comment out some 200,000 lines of code in your kernel.

      --
      I hereby place the above post in the public domain.
    8. Re:C'mon SCO! by tomhudson · · Score: 4, Insightful
      poster wrote:
      Riiiiiight... like you're going to comment out some 200,000 lines of code in your kernel.
      not necessary. the story said that the "offending lines" were contained in 148 files containing 168,276 lines of code.
      1. he actual "infringing" code could very well be only, say, 80 lines, distributed in various places in the 148 files
      2. more likely, the "infringing code" isn't infringing, but that's another story
      What most people have failed to grasp is that copyright doesn't give you exclusive rights in any shape or form. It's not a patent.

      Just look on your bookshelf. How many programming books do you have that contain "hello.c". All the books are copyright, and yet anyone can copy "hello.c" without infringing. Why? Because copyright applies to specific works (the book, for example), not insignificant snippets, or even loosely-derived derivative works (wholesale copying is another matter - characters, plot, setting all the same == probable copyright infringement). And if you can show that you developed it independently (clean-room implementation of BIOS, for example), you haven't violated someone else's copyright anyway.

    9. Re:C'mon SCO! by Anonymous Coward · · Score: 0
      Riiiiiight... like anyone is claiming it 200,000 lines of code in the kernel.

      Even SCO isn't that fscked up. What's your problem?

    10. Re:C'mon SCO! by Gherald · · Score: 1

      Because 2.3 was the development series for 2.4 , 2.3 probably has a good chunk of the code that was allegedly incorporated into 2.4

    11. Re:C'mon SCO! by Anonymous Coward · · Score: 0

      It's a viral license. So now all of Linux is infringing. By virtue of being linked together and distributed as a single unit.

      Viral licenses were not invented by RMS. And no matter who writes them or what they say, they are bad news. Well unless you are a lawyer paid by the hour.

    12. Re:C'mon SCO! by Sri+Lumpa · · Score: 1


      I use Linux20030811-srilumpa just to be on the safe side.

      If you want the same, non claimed to be infringing kernel just download your favorite version of the kernel and change the version number.

      --
      "The obvious mathematical breakthrough would be development of an easy way to factor large prime numbers." Bill Gates,
    13. Re:C'mon SCO! by EMH_Mark3 · · Score: 2, Funny

      ...*80* lines in *148* files?

      --
      Burn the land and boil the sea, you can't take the sky from me
    14. Re:C'mon SCO! by tomhudson · · Score: 1

      Sure - the same 80 lines in 148 files.

    15. Re:C'mon SCO! by stripe · · Score: 1

      The infringing code is probably be found with a simple grep of "^#$". :p

    16. Re:C'mon SCO! by EMH_Mark3 · · Score: 1

      Oh. Well they'd report that as 80*148 lines :)

      --
      Burn the land and boil the sea, you can't take the sky from me
    17. Re:C'mon SCO! by tomhudson · · Score: 1

      Nah, that's the RIAA formula, ... except that some of those lines were really long, so they count double *-)

    18. Re:C'mon SCO! by wirelessbuzzers · · Score: 1

      Ah, yes, I misread. I had thought it was 168,000, plus several thousand before.

      But still, you probably can't just comment out all those lines of code; you'd probably have to rewrite a fair amount of code to remove it, and you might end up reimplementing what SCO did. Even if it is all SMP stuff, implementing SMP (NUMA, whatever they added) in your kernel can have an effect on the single-proc version too (for instance, the threading and synch models).

      --
      I hereby place the above post in the public domain.
    19. Re:C'mon SCO! by Anonymous Coward · · Score: 0

      2.5 isn't a from-scratch rewrite of the kernel so large portions of the kernel source code are common. Apparently the changes were introduced in the 2.4 kernel so the 2.2 kernel isn't a problem. The above isn't implying that I believe that there is any validity to SCO's fraudulent claims.

      Shouldn't 2.3 also be listed as one of the kernel versions affected?

    20. Re:C'mon SCO! by sanx · · Score: 1

      I'm using Windows XP. It was cheaper to license...

    21. Re:C'mon SCO! by joostje · · Score: 1

      How many programming books do you have that contain "hello.c". All the books are copyright, and yet anyone can copy "hello.c" without infringing
      Or Brian Kernighan and Dennis Ritchie may have a way to get rich quick!

  6. web server running IIS? by dd · · Score: 5, Interesting

    Well, one wonders if SCO trusts any of the operating systems it sells, or has sold, in recent times. Take a look at the http response string for the web server used in this announcement:
    $ HEAD http://ir.sco.com
    200 OK
    Connection: close
    Date: Wed, 13 Aug 2003 14:42:15 GMT
    Server: Microsoft-IIS/5.0
    Content-Type: text/html
    Client-Date: Wed, 13 Aug 2003 14:42:16 GMT
    Client-Response-Num: 1
    Page-Completion-Status: Normal
    Page-Completion-Status: Normal

    1. Re:web server running IIS? by HogynCymraeg · · Score: 2, Funny

      But their main site is running... wait for it.... Linux! http://uptime.netcraft.com/up/graph/?host=sco.com Lookms like they changed to linux between March and August last year from.........SCO UNIX.

    2. Re:web server running IIS? by Znonymous+Coward · · Score: 5, Interesting
      --

      Karma: The shiznight, mostly because I am the Drizzle.

    3. Re:web server running IIS? by zuhl · · Score: 1

      Netcraft.com reports Apache/1.3.14 (Unix) mod_ssl/2.7.1 OpenSSL/0.9.6 PHP/4.3.2-RC on Linux for www.sco.com.

      ir.sco.com is running IIS on Windows 2000 as you say.

      Interesting, to say the least.

    4. Re:web server running IIS? by darthaya · · Score: 1

      FUD?

      (~)> HEAD http://ir.sco.com
      200 OK
      500 Can't connect to ir.sco.com:80 (Bad hostname 'ir.sco.com')

      (~)> HEAD http://www.sco.com
      200 OK
      Connection: close
      Date: Wed, 13 Aug 2003 14:56:48 GMT
      Server: Apache/1.3.14 (Unix) mod_ssl/2.7.1 OpenSSL/0.9.6 PHP/4.3.2-RC
      Content-Type: text/html
      Client-Date: Wed, 13 Aug 2003 14:51:30 GMT
      Client-Response-Num: 1
      X-Powered-By: PHP/4.3.2-RC

    5. Re:web server running IIS? by Anonymous Coward · · Score: 0
      $ HEAD http://ir.sco.com


      How dare you give head to SCO?
    6. Re:web server running IIS? by dd · · Score: 1

      No, they probably really are running windows on ir.sco.com (Investor Relations). Wouldn't it be a hoot if they were running linux :-)

      I like the cnames for this host:
      Non-authoritative answer:
      ir.sco.com canonical name = cald.client.shareholder.com.
      cald.client.sharehol der.com canonical name = client.shareholder.com.
      Name: client.shareholder.com
      Address: 170.224.5.43

    7. Re:web server running IIS? by Anonymous Coward · · Score: 1, Informative

      Neither of these servers are actually in the sco netblock, however. www.sco.com is being hosted by Noorda Family Trust, at www.nft.com. ir.sco.com is being hosted, ironically enough, by Sequent Computer Systems.

    8. Re:web server running IIS? by Evro · · Score: 3, Informative

      This is totally meaningless.

      $ dig ir.sco.com

      ; <<>> DiG 9.2.0 <<>> ir.sco.com
      ;; global options: printcmd
      ;; Got answer:
      ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64936
      ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 2, ADDITIONAL: 0

      ;; QUESTION SECTION:
      ;ir.sco.com. IN A

      ;; ANSWER SECTION:
      ir.sco.com. 14393 IN CNAME cald.client.shareholder.com.
      cald.client.shareho lder.com. 1793 IN CNAME client.shareholder.com.
      client.shareholder. com. 1793 IN A 170.224.5.43

      ;; AUTHORITY SECTION:
      shareholder.com. 14286 IN NS ns1.shareholder.com.
      shareholder.com. 14286 IN NS ns2.shareholder.com.

      ;; Query time: 18 msec
      ;; SERVER:
      ;; WHEN: Wed Aug 13 11:08:36 2003
      ;; MSG SIZE rcvd: 132

      This investor relations page is being hosted by someone else.

      --
      rooooar
    9. Re:web server running IIS? by ihummel · · Score: 2, Funny

      Ah, but SCO paid their own liscensing fee so that's okay in their book.

    10. Re:web server running IIS? by christooley · · Score: 1

      Even better, the netblock owner for ir.sco.com is Sequent. How hilariously ironic is that.

    11. Re:web server running IIS? by sdmartin101 · · Score: 5, Informative
      But who is that someone else, you might ask?

      $ host ir.sco.com
      ir.sco.com. is an alias for cald.client.shareholder.com.
      cald.client.sharehol der.com. is an alias for client.shareholder.com.
      client.shareholder.com. has address 170.224.5.43

      $ whois -h whois.arin.net 170.224.5.43
      [whois.arin.net]

      OrgName: Sequent Computer Systems, Incorporated
      OrgID: SCS-65
      Address: 1000 River Street
      City: Essex Junction
      StateProv: VT
      PostalCode: 05452
      Country: US

      NetRange: 170.224.0.0 - 170.227.255.255
      CIDR: 170.224.0.0/14
      NetName: SEQUENT-B
      NetHandle: NET-170-224-0-0-1
      Parent: NET-170-0-0-0-0
      NetType: Direct Assignment
      NameServer: NS1.RALEIGH.USF.IBM.COM
      NameServer: NS2.RALEIGH.USF.IBM.COM
      Comment:
      RegDate: 1995-04-21
      Updated: 2001-04-06

      TechHandle: ZI22-ARIN
      TechName: Role Account
      TechPhone: +1-866-373-6714
      TechEmail: noc@ibm.com

      # ARIN WHOIS database, last updated 2003-08-12 19:15
      # Enter ? for additional hints on searching ARIN's WHOIS database.
      IBM!
    12. Re:web server running IIS? by Evro · · Score: 1

      Heh. Now that's funny!

      --
      rooooar
    13. Re:web server running IIS? by Anonymous Coward · · Score: 0

      Someone please mod the parent post to the very limit. That's just plain cool.

    14. Re:web server running IIS? by Ian+Lance+Taylor · · Score: 1

      Remember that the company currently called SCO used to be called Caldera, and was a Linux company. The change from SCO Unix to Linux is probably about the time that www.sco.com was transferred from the old SCO (now called Tarantella) to the new SCO (formerly called Caldera).

  7. Details are coming out by Dancin_Santa · · Score: 3, Insightful

    Though it's simply a number of files and number of lines, SCO is actually putting their ass on the line by giving a description of where the code resides.

    Finally, this case has become interesting.

    But I'm sure /. can find a way to beat the topic to death.

    1. Re:Details are coming out by cshark · · Score: 1

      Ah, but how do you know they're pointing to the right place? With Mcbride's attitude of late, I'm thinking maybe they are trying to send the community on a wild gouse chase. Then again, this whole game of smoke and mirrors isn't doing anything for their credibility either.

      --

      This signature has Super Cow Powers

    2. Re:Details are coming out by Anonymous Coward · · Score: 0

      What the hell is a gouse?

    3. Re:Details are coming out by cosmo7 · · Score: 1

      What the hell is a gouse?
      don't you ever go to the zou?

    4. Re:Details are coming out by cshark · · Score: 1

      Nou nou nou, you bouth have it wrong

      --

      This signature has Super Cow Powers

  8. pump pump pump by dnotj · · Score: 3, Funny

    DUMP

    --
    No more Micro$oft bashing from me. Its like bashing at the special olympics.
    1. Re:pump pump pump by Anonymous Coward · · Score: 0, Funny

      mmm...German porn...

    2. Re:pump pump pump by ronaldb64 · · Score: 1
      Hehehe... does this mean we solved the ???...

      1) Pump

      2) Pump

      3) Pump

      4) DUMP!

      5) Profit!

      --
      There's no place like 127.0.0.1
  9. Angry... by Bistronaut · · Score: 5, Interesting

    "...was terminated for improper transfer of Sequent's UNIX source code and development methods into Linux." (emphasis mine)

    You heard it here first, people. SCO owns the UNIX development methods too. That means that producers of just about any software (because who hasn't been influenced by UNIX development methods?) will have to pay off SCO. What a bunch of bull.

    1. Re:Angry... by sharlskdy · · Score: 4, Funny

      By development methods, do they mean "use of the vi editor"?

    2. Re:Angry... by kpansky · · Score: 1, Funny

      > By development methods, do they mean "use of the vi editor"?

      No way. SCO isn't 1337 enough to use vi. They are, however, evil enough to use EMACS.

      --

      --Kevin
    3. Re:Angry... by dtfinch · · Score: 1

      Indents, bracing, "/* */" vs "//" comments, naming convention... :)

    4. Re:Angry... by grub · · Score: 1


      By development methods, do they mean "use of the vi editor"?

      Perhaps. Of course, real men just "cat > foo.c" and don't make mistakes. I guess SCOs people will read this and scour through the cat source now..

      --
      Trolling is a art,
    5. Re:Angry... by bucktug · · Score: 2, Funny

      I hearby would like to license the development method of drinking much caffinated beverages... staying up way to late on a debug session and remaining paste white year round.

      Take THAT!

      --Turvey

      --
      I had a flame... but she had a fire.
    6. Re:Angry... by varslot · · Score: 2, Funny

      No, it only applies to "use of the Emacs editor".

      --
      There arises from a bad and unapt formation of words a wonderful obstruction to the mind. (Francis Bacon)
    7. Re:Angry... by multipartmixed · · Score: 2, Funny

      > No, it only applies to "use of the Emacs editor".

      Don't you mean the GNU Emacs editor?

      --

      Do daemons dream of electric sleep()?
    8. Re:Angry... by Gherald · · Score: 1

      > Don't you mean the GNU Emacs editor?

      No he means the GNU/Emacs OS.

    9. Re:Angry... by Anonymous Coward · · Score: 0

      By development methods, do they mean "use of the vi editor"?

      No, I doubt it, they probably are referring to GNU-emacs.

      After all, with his company going down in flames, why wouldn't Darl throw another can of gas in the mix...

      Go get'im RS!

    10. Re:Angry... by cybercuzco · · Score: 1

      Ha, I use emacs!

      --

    11. Re:Angry... by Raereth · · Score: 1

      Of course, real men just "cat > foo.c" and don't make mistakes.

      And the ubermensch just "cat > foo" followed by "chmod a+x foo".

    12. Re:Angry... by lildogie · · Score: 1

      > By development methods, do they mean "use of the vi editor"?

      No, they mean the use of filenames on the command line.

    13. Re:Angry... by ShortRound · · Score: 1

      why does your source need execute privileges?

      ahh shit I'm probably missing something.

    14. Re:Angry... by sanx · · Score: 1

      Nope, it's the use of 'ls' to see what files you've written. You are hereby required to pay the sum of $100 for each directory listing you make from now on, with a further $50 for every parameter you pass to it. Oh, and just sign over your first-born as recompense for your past illegal use of this development technique...

    15. Re:Angry... by Rogerborg · · Score: 1

      Why do you assume it's source? foo, not foo.c

      --
      If you were blocking sigs, you wouldn't have to read this.
    16. Re:Angry... by Raereth · · Score: 1

      The idea was to actually type in the compiled form of the program.

      I probably should've written it as "cat > a.out" or something.

  10. I'll be back... by gilesjuk · · Score: 0, Redundant

    Can't someone just terminate SCO? I'm getting sick of their spoilt child politics.

    1. Re:I'll be back... by akac · · Score: 2, Insightful

      The only way to terminate SCO _right now_ would be to buy them. And that would reward the idiots. Any other method such as patent infringement lawsuits, etc... would just cause a prolonged death.

  11. It's okay by 91degrees · · Score: 5, Funny

    I've just revoked SCO's licence to use their own code. And I hereby revoke the right of anyone to tell me I can't do that.

    1. Re:It's okay by Znonymous+Coward · · Score: 3, Funny

      Too late, I already revoked everyone's ability to revoke last year. I bought the rights from Novell to do so.

      --

      Karma: The shiznight, mostly because I am the Drizzle.

    2. Re:It's okay by 91degrees · · Score: 1

      I checked the terms of the revokation. You forgot to exclude yourself from the ability to revoke, and revoked in alphabetical order.

      Users Znugget through to ZZTop still have the power to revoke.

    3. Re:It's okay by Alan+Partridge · · Score: 1

      I think you'll find that I licensed those same rights to Novell in 1978, and their licence did NOT include the right to sell the revokabilty to a third party.

      Therefore you now owe me all the money in the world plus 1 dollar.

      --
      That was classic intercourse!
    4. Re:It's okay by killmenow · · Score: 5, Funny

      From my Netware 3.12 server (3.12 was released in September of 1993)...

      F:\PUBLIC>revoke.exe

      Usage: REVOKE rightslist* [FOR path] FROM [USER|GROUP] name [options]
      Options: /SubDirectories | /Files

      286 Rights: 386 Rights:
      --------------- --------------------
      ALL = All ALL = All
      R = Read S = Supervisor
      W = Write R = Read
      O = Open W = Write
      C = Create C = Create
      D = Delete E = Erase
      P = Parental M = Modify
      S = Search F = File Scan
      M = Modify A = Access Control

      * Use abbreviations listed above, separated by spaces.

      Novell is clearly still the holder of the right to revoke.

    5. Re:It's okay by u-235-sentinel · · Score: 1

      You're not the only one revoking stuff around here. Looks like others are removing SCO support from their products. Here's an example

      http://www.xvid.org/

      Ok so they might be kidding. I doubt it was there in the first place ;D

      --
      Has Comcast disconnected your Internet account? Same here. You can read about it at http://comcastissue.blogspot.com
    6. Re:It's okay by roman_mir · · Score: 1

      I am sorry, you cannot do that since your statement is partially patented by me but I cannot tell you which part. I however am terminating your right to use a language. English I mean.

    7. Re:It's okay by rev_sanchez · · Score: 1

      I think we should avoid getting down on their level. Maybe we could just add dick jokes to all the linux kernel packages and patches and claim parody protection.

      --
      If you didn't come to party don't bother knocking on my door. Prince '1999'
    8. Re:It's okay by scalis · · Score: 1

      Too late, I already revoked everyone's ability to revoke last year. I bought the rights from Novell to do so

      Great! Can you please sue my bank? They claim they can revoke my credit card and that is clearly in violation of this!

      --

      True ravers don't need drugs
  12. So can IBM attack SCO now? by PatSand · · Score: 3, Funny
    BFD...

    I'd rather see IBM send in the attack lawyers in the black limos (their version of the black helicopters)...

    That would be like shooting fish in a barrel with a cannon...

    and well worth a video copy; would put it right next to my Rocky and Bullwinkle cartoons...

    --
    Supreme Granter of Doctor of Obviology Letters ("A FIRM Command of the Obvious")
    1. Re:So can IBM attack SCO now? by Lord_Dweomer · · Score: 1
      My thoughts exactly. What I'd love more than anything right now is a Flash cartoon dramatization of SCO's impending doom at the hands of IBMs legal team. In fact, I'm surprised one hasn't been made already. Oh wait, this is Slashdot, nobody uses Flash.

      --
      Buy Steampunk Clothing Online!
    2. Re:So can IBM attack SCO now? by BrokenHalo · · Score: 1
      I'd rather see IBM send in the attack lawyers in the black limos (their version of the black helicopters)...

      Personally, I don't care how they do it. I just wish they would get a move on. SCO are behaving like brats, and anyone who can succeed in squashing them like the cockroaches that they are will be doing us all a favour.

    3. Re:So can IBM attack SCO now? by GlassUser · · Score: 1

      That's right. Can you say remote root exploit? Please stick to standards. Thanks,

    4. Re:So can IBM attack SCO now? by CowboyMeal · · Score: 1

      Quick! someone post an ASCII art version!

      --
      Your credit card information wants to be free.
    5. Re:So can IBM attack SCO now? by Anonymous Coward · · Score: 0
      This is Slashdot we HATE flash!

      I also hate that 2 minute timer thing.

    6. Re:So can IBM attack SCO now? by Lord_Dweomer · · Score: 1
      So what would the standard be instead of Flash just out of curiosity. I don't know of any other software that lets you create complex animations in a reasonably small file size for the web except for Flash.

      --
      Buy Steampunk Clothing Online!
    7. Re:So can IBM attack SCO now? by GlassUser · · Score: 1

      SMIL (sounds like "smile") does this. More information can be found at http://www.w3.org/AudioVideo/

  13. bluff much? by Paddyish · · Score: 5, Funny
    Next we'll see the 'Super-Final termination notice', to eventually be followed by the 'No-really-we're-serious-this-time-guys-last-ditch -final termination notice'...

    gimme a break. SCO, WHY WON'T YOU DIE???

    1. Re:bluff much? by Znonymous+Coward · · Score: 1

      It reminds me of this furniture store we have in town that has been having it's "Lease termination sale" for the past 3 years. I wish their lease really would get terminated so I don't have to see the commercial again.

      --

      Karma: The shiznight, mostly because I am the Drizzle.

    2. Re:bluff much? by hal9000 · · Score: 1

      The first notice (June 16) revoked IBM's license for AIX. This one revokes Sequent-IBM's license for "Dynix/ptx."

      I think the word "final" in the headline is just part of the legalese, and does not imply that the previous revocation was in any way not final.

      --
      Look out honey, 'cause I'm using technology; Ain't got time to make no apology
    3. Re:bluff much? by rebelcruier · · Score: 1

      yup, and after the 'No-really-we're-serious-this-time-guys-last-ditch -final termination notice'... has been posted I fully expect the United Nations will step up and sue SCO for infringing on their development methods ;-)

    4. Re:bluff much? by mr_z_beeblebrox · · Score: 1

      Next we'll see the 'Super-Final termination notice', to eventually be followed by the 'No-really-we're-serious-this-time-guys-last-ditch -final termination notice'...

      Nope. I have a tip that they are selling their stock to finance an army of young people to harass and taunt RS6000 purchasers outside of resellers 'na na you don't have an OS'

    5. Re:bluff much? by geomon · · Score: 1

      Hmmmm..... IBM is Animal House?

      I don't know about that one. I can't see ANY IBM executive being from Animal House.

      Deltas don't wear hose suspenders.

      The 25th Anniversary DVD will be released soon.

      --
      "Rocky Rococo, at your cervix!"
    6. Re:bluff much? by NorthDude · · Score: 1

      >> SCO, WHY WON'T YOU DIE???

      Because we are in a movie. And in movie, when they kill the bad guy, the bad guy always get back on it's feet for a last fight. You know, with the blood all over it, the gun holes and everything...

      --


      I'd rather be sailing...
    7. Re:bluff much? by chiph · · Score: 1

      Next thing you know, they'll be claiming that Kevin Mitnick transferred a copy of the SCO source to IBM when he hacked into their systems back in 1987.

      Chip H.

    8. Re:bluff much? by JamesTRexx · · Score: 1

      gimme a break. SCO, WHY WON'T YOU DIE???

      Maybe because they run on *BSD?? :-P

      --
      home
    9. Re:bluff much? by FuzzyBad-Mofo · · Score: 1

      Hmm.. maybe not IBM, but I think Stallman might qualify! Thx for the link.

    10. Re:bluff much? by Doomdark · · Score: 1
      As long as THAT is followed by Dubya attacking SCO, and wiping out SCO leadership (plus their sons), I think that would work out just fine!

      And after THAT we can all start looking for those allegedly easy-to-spot infringing lines of code that everyone from FBI to Mossad knew were there, ready to be deployed in 45 minutes! :-)

      --
      I like paying taxes. With them I buy civilization -- Oliver Wendell Holmes
    11. Re:bluff much? by mink · · Score: 1

      I have only ever goten RS6K hardware via mailorder or delivery.
      Are there places you can walk in and buy things like a P-series cluster? You wont be walking out with it unless you bring a powerloader or forklift.

      --
      Well I've wrestled with reality for thirty five years doctor, and I'm happy to say I finally won out over it.
    12. Re:bluff much? by mr_z_beeblebrox · · Score: 1

      You are right, that would be quite the site.

      Are you kidding at 175 lbs. this is the portable as/400 (I know not Unix) but the image just strikes me funny, imagine circuit city having that!

  14. Bah! Final! by Lispy · · Score: 2, Insightful

    When will they announce the final, final Termination? Tomorrow? This is actually too funny to be true.

    1. Re:Bah! Final! by jcknox · · Score: 1

      Maybe they mean final termination as in "this is our last shot at terminating IBM's license before they eat our lunch in court."

    2. Re:Bah! Final! by Lonath · · Score: 2, Funny

      When will they announce the final, final Termination?

      When they have no more stock do dump?

    3. Re:Bah! Final! by Rob+Riggs · · Score: 1
      When will they announce the final, final Termination? Tomorrow?

      Right after the "double secret termination" phase!

      --
      the growth in cynicism and rebellion has not been without cause
  15. Final Stock Pump by DrWho520 · · Score: 5, Insightful

    How can these guys still be going?!? This is obviously another try at pumping up the stock. Does not unsubstantiated rumor to pump stock prices coupled with stock dumping by company executives indication that SOMETHING might be a little wrong here?

    SEC...hello!!!

    --
    The cancel button is your friend. Do not hesitate to use it.
    1. Re:Final Stock Pump by st0rmshad0w · · Score: 4, Insightful

      As there is an amazing amount of comment here about what we all see as something the SEC should look into, I can't help but wonder if anyone here has either picked up the phone or dropped an email to the SEC itself to clue them in, since they don't appear to be paying attention. Maybe we should all take 5 minutes out of our day?

    2. Re:Final Stock Pump by WCMI92 · · Score: 1

      "As there is an amazing amount of comment here about what we all see as something the SEC should look into, I can't help but wonder if anyone here has either picked up the phone or dropped an email to the SEC itself to clue them in, since they don't appear to be paying attention. Maybe we should all take 5 minutes out of our day?"

      Considering that SCO has already said they had terminated IBM's AIX license (some weeks back), this announcement is clearly another stock pump..

      EVERY TIME their stock price levels or goes down, SCO makes another ridiculous announcement to get a biz headline to make it go back up.

      This time, I'm betting yesterday's executive stock dump story was the trigger...

      Last
      9.93
      Change
      +0.20
      % Change
      +2.11%
      Previous Close
      9.72
      Day's Low
      9.70
      Day's High
      10.23
      Volume
      41,266

      And it's working too... Morons... Are investors as stupid as the average computer user?!

      --
      Corporatism != Free Market
    3. Re:Final Stock Pump by Li0n · · Score: 1

      well, they probably are average computer users so...

      --

      ~
      ~
      :wq
    4. Re:Final Stock Pump by Khomar · · Score: 4, Insightful

      How do we know that the SEC isn't already watching the SCO? They could be giving them enough rope to hang themselves before they spring the trap. Until their case proves to be fraudulent (it appears to be overwhelmingly so now, but there is no irrefutable proof... that will be coming soon), there may actually be nothing with which the SEC can actually prosecute at this point. Once everything is in the clear and their lawsuit is proven to be what we all here believe it to be, then the SEC, who has probably been gathering evidence all of this time, will be prepared to move in. I highly doubt that the SEC is failing to notice a story of this magnitude.

      --

      I believe in de-evolution. God made the world perfect, man fell, and its been going downhill ever since!

    5. Re:Final Stock Pump by Zebra_X · · Score: 1

      I'm sure they are watching - this can't possibly be ignored. The only way that SCO and the people involved in this SCAM is to prove that SCO's claims are in fact, untrue. Until such time as that is proven the officers of the company are free to trade their shares so long as they do so in accordinance with insider trade laws.

      There is one thing that is glaringly fishy as far as insider trading goes... REGINALD CHARLES BROUGHTON is listed as conducting many trades over the last few months. Not only has he been selling exising shares but the company keeps "Awarding" him stock conviently, when the stock is at a low point. Sounds like our REGINALD is getting free stock from the comapany and selling it. It "feels" wrong but I'm not a lawyer!

    6. Re:Final Stock Pump by ChazeFroy · · Score: 1
    7. Re:Final Stock Pump by Anonymous Coward · · Score: 0

      The SEC doesn't give a flying f'ck (excuse my french) about this or they would have put an end to this long ago. The only other possibility is that they're still a bit miffed at IBM and want to see it get burned a bit before stepping in and doing anything. What other explaination is there? If you want the SEC to step in and tell SCO to shut up and go screw itself, the only way it's gonna happen is if you flood your congressman/congresswoman and the whitehouse with emails, letters, notices, petitions, etc stating that SCO is out for a pump and dump money grab, you're tired of their illegal harrasement of Linux and IBM and you'd like to see the SEC step in and take these guys down because there's so much information out there screaming scam that you'd have to be parked on the far side of Solaris Prime not to hear it.

    8. Re:Final Stock Pump by leandrod · · Score: 1
      > a pre-filled out SEC complaint form

      Great, thanks! Already sent.

      Suggestion: each one please do change the text as to look like you actually thought about the issues... we don't want to be called astroturfers.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    9. Re:Final Stock Pump by richg74 · · Score: 2, Informative
      I've had a little experience with how the SEC works in this kind of situation. I wouldn't expect to see any overt enforcement action until there is some actual evidence that SCO's claims are bogus. Trading by corporate insiders is not, in itself, illegal, as long as they follow the rules (Form 4 filings, sale restrictions, etc.). What would be illegal (securities fraud, which is a criminal offense) would be SCO officers or directors knowingly making material false statements. (An SCO shareholder could also file a civil lawsuit.)

      From the Securities Exchange Act 1934 (as amended), section 32:

      any person who willfully and knowingly makes, or causes to be made, any statement in any application, report, or document required to be filed under this title or any rule or regulation thereunder or any undertaking contained in a registration statement as provided in subsection (d) of section 15, or by any self-regulatory organization in connection with an application for membership or participation therein or to become associated with a member thereof, which statement was false or misleading with respect to any material fact, shall upon conviction be fined not more than $5,000,000, or imprisoned not more than 20 years, or both.

      The SEC has a good page sumarizing the relevant US Federal laws. (Incidentally, according to Netcraft, www.sec.gov is running Linux. Do you suppose they've received their menacing letter and invoice from SCO yet? :-)

    10. Re:Final Stock Pump by devphaeton · · Score: 1

      Here's a start....

      http://zgp.org/linux-elitists/1058969817.4188.39 .c amel@warthawg.html

      This (above) isn't me, but i plan on filing one this evening myself.. but i am going to gather up lots of evidence and make sure i don't just sound like a seething moron. The URL for the complaint form is at

      http://www.sec.gov/complaint/cf942sec9570.htm

      Which brings us to a point: Anyone filing a complaint against the SCO Group with the SEC, *please* refrain from sounding slanted or ignorant. Be sure to be factual, accurate and watch all your speling and, punctuation. marks

      The more professional each complaint is, probably the more attention they will pay to it.

      --


      do() || do_not(); // try();
    11. Re:Final Stock Pump by thejackol · · Score: 1

      Aah but that's where it's at. It's a story of great magnitude to us, because we see one story a day about it here.

      Most people I know haven't even heard of the damn case. So someone taking 5 minutes off their day would really help, me thinks. I'd have done it if I were there.

    12. Re:Final Stock Pump by Anonymous Coward · · Score: 0

      I can't wait for the picture of McBride in handcuffs....

    13. Re:Final Stock Pump by sehryan · · Score: 1

      I highly doubt that the SEC is failing to notice a story of this magnitude.

      Unless the SEC doesn't read slashdot.

      --
      The world moves for love. It kneels before it in awe.
    14. Re:Final Stock Pump by Anonymous Coward · · Score: 0

      umm, because shrub's in the white house?

    15. Re:Final Stock Pump by Asprin · · Score: 1

      Wow, what a coinkeydink!

      I just found this article from The Salt Lake Tribune via Google News that posted earlier today.

      In a nutshell:
      Executives at Lindon, Utah-based SCO Group have sold more than 126,000 shares for about $1.2 million since the IBM suit was filed. Before that, SCO insiders hadn't sold shares in more than a year. The officials are facing higher tax bills because of the increased value of their options and restricted shares, said Chief Executive Darl McBride. The shares have gained more than fourfold since the company filed suit against IBM in March.

      "The guys don't want to be selling," McBride said. McBride said he has no plans to sell his shares. Senior Vice President Chris Sontag, who heads the company's software-licensing unit, also hasn't sold shares, McBride said.

      The executives are selling shares on a preset schedule to avoid suggestions of improper trading, McBride said. The SEC's Rule 10b5-1 allows insiders to sell shares of their company on a preset schedule, even if he or she has information that could affect the stock price. Insiders at companies including Staples Inc. and Amazon.com Inc. have used 10b5-1 plans.

      Now, that's DARL'S position on the matter and niether he nor Sontag have sold any stock yet. The stock that has been sold totals around 1.2 million for everyone, which is chump change in terms of the current value of their portfolios.

      Yeah, they might be dumping stock, but it looks like they're doing it legally.

      --
      "Lawyers are for sucks."
      - Doug McKenzie
  16. The end is nigh! by Znonymous+Coward · · Score: 1

    These PRs are used strictly to inflate stock value. Sell your SCO stock before the ship sinks (if you are dumb enough to own any in the first place).

    --

    Karma: The shiznight, mostly because I am the Drizzle.

    1. Re:The end is nigh! by HogGeek · · Score: 2, Interesting
      "if you are dumb enough to own any in the first place"

      I wouldn't call making about $3K ( so far ) off of this farce "dumb"...

      SCO is playing a game, and I'm going to make as much money off of it I can...

  17. So that is why... by CreatorOfSmallTruths · · Score: 2, Interesting

    ... SCO managers dumped their shares ?
    btw, does this means that non SMP machines are in the clear???

  18. McBride? McBriii-ide? Hello? by re-geeked · · Score: 5, Funny

    : noogie

    Sequent's code belongs to IBM! Hello? McBride?

    --
    "You can't get something for nothing." - my grandfather, on the stock market and Reaganomics.
  19. blahblah by tschernogates · · Score: 0, Troll

    SCO again. I wonder who knew them before all this theater they did.
    I didn't.

    --
    -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
    How should I know what I'm thinking before I read what I wrote?
    1. Re:blahblah by dre80 · · Score: 1

      Actually, you may have... They used to be known as Caldera. They own the rights to DR-DOS and a few other random forgotten pieces of software, and they used to sell Caldera Linux too. That last bit is partially why this whole debacle is ironic, of course...

  20. No Threatening Of Customers by Chaltek · · Score: 5, Interesting

    "Customers may not acquire a license in Dynix/ptx from today's date forward."

    In a departure from their standard MO, SCO doesn't threaten IBM customers who currently hold Dynix/ptx licenses, and instead just claims that no new licenses may be issued.

    Maybe they are starting to worry about gettting nailed on extortion charges?

    1. Re:No Threatening Of Customers by Anonymous Coward · · Score: 0

      Isn't there something called indemnity that is provided by commercial software makers that says that the buyer can't be sued for IP violation, only the company?

    2. Re:No Threatening Of Customers by Anonymous Coward · · Score: 0

      Yes, but SCO wants IBM to provide indemnity for its customers, but this goes against our motto: "don't give SCO anything it wants."

      Plus, it just doesn't make sense to sue end-users (unless they are a nice-sized corporation with some money). There must be several million individual Linux users, suing each one would be costly. It would make more sense to sue the source of the copyright violation (IBM, if they actually did anything wrong) and milk them dry.

    3. Re:No Threatening Of Customers by Anonymous Coward · · Score: 0

      I, and the parent that I replied to, were talking about SCO suing end-users of IBM's Unix, whose liscense SCO just revoked, not Linux.

  21. Class-action suit by macdaddy · · Score: 3, Interesting

    I would REALLY like to see someone file a class-action suit against these clowns, charging them with extortion and fraud so that ALL Linux users can join in. Imagine a C-A suit with tens, perhaps hundreds, of individuals and companies on one side and wee little SCO on the other. That would truly be a sight to see and I for one would join in a heartbeat.

    1. Re:Class-action suit by macdaddy · · Score: 1

      Whoops. I meant to say was "...tens, perhaps hundreds, of thousands of...". My bad. I'm in too big of a hurry today.

    2. Re:Class-action suit by wren337 · · Score: 1


      But wouldn't tens of thousands of small claims court cases be so much more fun?

    3. Re:Class-action suit by Fulcrum+of+Evil · · Score: 1

      I would REALLY like to see someone file a class-action suit against these clowns

      Nah, better to have SCO defend themselves against 200 individual actions.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    4. Re:Class-action suit by macdaddy · · Score: 1

      Ha ha! True! Yes both would be quite a sight. Why limit ourselves to just one? Why not both?

    5. Re:Class-action suit by Bistronaut · · Score: 1

      The legal thinkers are already working on this, but (from what I understand - IANAL) it is better to wait for IBM to win its case. After that, it will be much easier (although by then SCO will be a dried-up husk of a company without even its inflated stock price).

    6. Re:Class-action suit by st0rmshad0w · · Score: 1

      Cripes man! It'd take forever. I'm still waiting for my $12 from the record company pricy fixing thing.

    7. Re:Class-action suit by Anonymous Coward · · Score: 0

      However, what if SCO were to win their case against IBM, even if only partly?

      Then all those who partook in the class action suit will now be identified by SCO who can then take steps to sue YOU for use of THEIR IP.

      I knows it's not a popular thought, but there still may be some merit to SCO's lawsuit. I think there's more than a few who would best choose to remain out of sight until this is all over. One of the reasons to go with Linux in the first place is cost. If a few hundred bucks matters to some people then those people certainly wouldn't want to get caught up in something like this.

    8. Re:Class-action suit by Anonymous Coward · · Score: 0

      IANAL, but I believe that extortion is criminal, not tortious, so is not a basis for a civil suit. That said, I am sure that some entreprising lawyer could find some nice restraint of trade/damage to income type of suits in the civil arena. :)

    9. Re:Class-action suit by idiotnot · · Score: 1

      Except extorition is a criminal complaint....

      Class Action suits are worthless, BTW. Only the attorneys involved get rich.

    10. Re:Class-action suit by Anonymous Coward · · Score: 0

      There may be liability insurance policies that SCO has that should pay for damages resulting from lawsuits. I am sure they are worth at least a few million dollars.

    11. Re:Class-action suit by lildogie · · Score: 1

      > I would REALLY like to see someone file a class-action suit
      > against these clowns, charging them with extortion and fraud

      IANAL, but aren't extortion and fraud crimes, where as class action suits are civil actions?

      Crimes and civil actions are handled by different branches of the justice system.

  22. Where the hell is the SEC? by Anonymous Coward · · Score: 0

    Yes, we are all just geeks who don't really know a lot about stock market rules. But you don't have to be a genius to figure this one out. They pump their stock one day before the quarterly results with some bogus claims and the SEC is just sitting there and waiting for the whole thing to blow up, so they can look like morons afterwards. Just a year after Enron the SEC is failing misserably once again.

    1. Re:Where the hell is the SEC? by Anonymous Coward · · Score: 0

      Insiders are typically blacked out of trading within several days to weeks of quarterly earnings reportage.

      Also, insider sells and buys must be registered and approved with the SEC before the transaction may be performed.

      Yes, you don't know much about the stock market or SEC rules.

    2. Re:Where the hell is the SEC? by Anonymous Coward · · Score: 0

      And just like Ken Lay && MS, it shows that being a contributer to W will go a long way. There is a reason why it is called the Right wing. Give to Bush/Ashcroft.

    3. Re:Where the hell is the SEC? by utmecheng · · Score: 1

      They aren't dumping that many shares. Look up any other company. It isn't odd that a few thousand shares are sold and purchased all of the time. Sure they would sell more if the SEC wasn't watching them, but the SEC can't say 'you cannot sell 7,000 shares because... you have a lawsuit coming up'. Thats absurd. If every insider dumped hundreds of thousands of shares, then you might have a point. But it is not that big of a deal.

  23. SCO are suing IBM over Linux? by ariels · · Score: 2, Funny

    Why is a "News for Nerds" site only covering this now?

    Where has /. been over the past weeks?

    --
    2 dashes and a space, or just 2 dashes?
    1. Re:SCO are suing IBM over Linux? by Anonymous Coward · · Score: 0

      I could also ask you: 'Where have you been?' ;oP

      http://slashdot.org/search.pl?query=sco+ibm

  24. SCO planting code by in7ane · · Score: 4, Interesting

    This may have come up before, and there may well be ways to check.

    But what is preventing SCO from adding in code from Linux (which is openly available) into their (closed) UNIX code and then claiming is was there first and was 'stolen' by Linux? C'mon, we are not expecting SCO's management to play fair here - how hard would it be to backdate code additions?

    1. Re:SCO planting code by Anonymous Coward · · Score: 2, Informative

      They'll be plenty of people with older (licensed) versions of SCO Unix cose against which SCO's copies could be compared. It may be under NDAs, but no court in the world would punish anyone who breaks that NDA to expose any barratry and fraud on behalf of SCO.

      Besides, the court could probably subpoena such escrow code as part of the discovery process.

      PS : I'm a lover, not a lawyer

    2. Re:SCO planting code by in7ane · · Score: 1

      OK, I see - as long as they are not holding the 'only' version of the old code (I guess even they were not evil enough to just distribute binaries before - now they do) it will be easy to check.

      Mod grandparent down before it starts sounding like a conspiracy theory.

    3. Re:SCO planting code by Anonymous Coward · · Score: 0

      Yeah, they'll just sneak it while Linus isn't watching. Its not like he doesn't keep a detailed Changelog and the entire kernel ML archives mirrored across thousands of computers around the world, leaving a paper-trail as big as Mt. Fiji.

    4. Re:SCO planting code by isoga · · Score: 1

      dumbass - they said planting linux code in SCO not the other way round!

    5. Re:SCO planting code by FreeMars · · Score: 1

      what is preventing SCO from adding in code from Linux (which is openly available) into their (closed) UNIX code and then claiming is was there first and was 'stolen' by Linux?

      The original author of the Linux code?

      --
      Email: slashdot3@FreeMars.org (Address will be abandoned when it gets spam.)
    6. Re:SCO planting code by BootSpooge · · Score: 1
      But what is preventing SCO from adding in code from Linux (which is openly available) into their (closed) UNIX code and then claiming is was there first and was 'stolen' by Linux? C'mon, we are not expecting SCO's management to play fair here - how hard would it be to backdate code additions?

      They could fake up their source code control system repositories with little effort. But they would not be able to demonstrate a check out and a build that would match any binaries they shipped.


    7. Re:SCO planting code by Kismet · · Score: 1

      But what is preventing SCO from adding in code from Linux (which is openly available) into their (closed) UNIX code and then claiming is was there first and was 'stolen' by Linux? C'mon, we are not expecting SCO's management to play fair here - how hard would it be to backdate code additions?

      Because every line of code in the Linux source control system has somebody's name on it. If they contribute their own code to the Linux kernel, it has to go through an acceptance process by Linus or one of the Linux stewards. If it turns out to be SCO code, then we know who can account for it, and can investigate their ties with SCO.

    8. Re:SCO planting code by NaugaHunter · · Score: 1

      Old distributions exist that can be checked against newly compiled builds to see if they match. In other words, if code segment 'A' was added later there would be no way to compile it to match a preexisting build.

      And older builds could be gotten from old clients, if nowhere else. It may be complicated to get them, but they exist to be checked.

      --
      R: That voice. Where have I heard that voice before? B: In about 365 other episodes. But I don't know who it is either.
    9. Re:SCO planting code by schon · · Score: 1

      they would not be able to demonstrate a check out and a build that would match any binaries they shipped.

      No?

      You think it's just a coincidence that the "smoking gun" they keep showing under NDA happens to be comments? Didn't one of the analyists say that some of the code was different, but the comments were the same?

      Gentlemen, don your tinfoil hat, if you please:

      What if SCO, in it's zeal to drum up evidence, finds code in Linux and Unixware that do similar things, or looks similar.. they then take the comments from Linux, and put them into Unixware..

      Then (as you say) they fake up their repositories, and viola - instant compilable code that will (with the same compiler and settings) pass the publically-available-binary test.

  25. SCO terminating license by godot42a · · Score: 1

    Hasta la vista, IBM?

  26. Okay. by Canthros · · Score: 3, Interesting

    So this pretty much all hinges on whether or not SCO owns any and all code that was derived from the original UNIX source, since they state that the code in question was originally written by Sequent (and, therefore, not SCO).

    --
    Canthros
  27. So, the truth's out, is it? by brotherscrim · · Score: 5, Interesting

    Oh, now the line is that there is "Sequent-UNIX" code in the kernel, with no mention of Sys V code?

    So, what we're really talking about is IBM code. No more BS weasle-words, they're talking about code they NEVER owned in the first place.

    Well, that tears it: SCO's suing IBM for contributing their own code to the kernel. Yeah, that's totally gonna hold up in court.

    1. Re:So, the truth's out, is it? by Ian+Lance+Taylor · · Score: 1

      The lawsuit against IBM was always about IBM/Sequent taking code which they had written and contributing it to Linux. In the lawsuit SCO claims that by contributing that code to Linux, IBM violated their contract. SCO isn't claiming that they own that code; they are claiming a contract violation based on an extended notion of derivative work.

      SCO's claim concerning Linux licensing is not about the IBM code. It is about different code which SCO claims was copied directly from Unix into Linux. That is the code which SCO is showing under NDA.

      Two different things.

  28. SCO files "We really mean it this time" suit by reverendG · · Score: 1

    WHO CARES?!

    I'm having a hard time paying attention to these people. Is that what they want?

    It seems like there are 3 SCO stories a day on /. Maybe one day we'll actually get down to brass tacks and find out if IBM is going to give them the Sheila or what.

    --

    Why should I argue rationally with someone being irrational? I'll just mock them instead.
  29. Code won't be released until trial by streak · · Score: 4, Insightful

    SCO would make a bad move to release the code before the trial under something less than a NDA.
    Linux kernel developers would probably have the offending pieces rewritten in a week and back-ported to all 2.4/2.5 kernels within another week.

    But honestly, I really don't think IBM cares what SCO does at this point. They know their argument is probably not going to hold water in court.

    Unfortuately, with the way our justice system works, it will not be heard in court until probably late 2004/2005.

    1. Re:Code won't be released until trial by nagora · · Score: 2, Interesting
      Linux kernel developers would probably have the offending pieces rewritten in a week and back-ported to all 2.4/2.5 kernels within another week.

      Which is what they should want if they are really suffering damage; they can still sue for past damages. By not revealing the code SCO are giving a judge a very clear signal that they are not suffering enough to need the code removed ASAP and don't therefore need any major compensation.

      TWW

      --
      "Encyclopedia" is to "Wikipedia" what "Library" is to "Some people at a bus stop"
    2. Re:Code won't be released until trial by JimDabell · · Score: 1

      SCO would make a bad move to release the code before the trial under something less than a NDA.
      Linux kernel developers would probably have the offending pieces rewritten in a week and back-ported to all 2.4/2.5 kernels within another week.

      It's already been pointed out a hundred times, so once more won't hurt.

      Rewriting Linux now will not do a damn bit of good. It doesn't absolve anyone from past infringements, and it won't mean that IBM did not breach their contract.

      When it comes to trial, even if we all find out that Linux is infringing on SCO's IP, all the non-disclosure will have done is make the judge less likely to award damages to SCO.

      The only reasonable explanation I have heard for the secrecy is that they can't substantiate any of their claims.

    3. Re:Code won't be released until trial by Tsu+Dho+Nimh · · Score: 3, Interesting
      " SCO would make a bad move to release the code before the trial under something less than a NDA."

      That's why RedHat's suit is interesting, because they are asking for a fast decision based on the BS that SCO has been shoveling. If SCO refuses to prove it's claims of infringement by showing the code, and proving not only that SCO holds the copyright, but that their code predates the Linux stuff ... RedHat gets not only a legal declaration that it's kernel code does not infringe, but gets damages too.

      They could end up owning SCO before IBM even gets to court, which means that they would therefore be suing IBM ... and I think they could settle amicably.

    4. Re:Code won't be released until trial by Whispers_in_the_dark · · Score: 1

      In fact isn't it a bit of a tennant in civil court that the parties are duty-bound to prevent damages if it is within their power? From what I can see much of the supposed damage could have been mitigated by SCO with a simple email or newsgroup posting. If that's correct than I don't see how they are entitled to almost any damages at all.

    5. Re:Code won't be released until trial by Anonymous Coward · · Score: 0
      SCO would make a bad move to release the code before the trial under something less than a NDA.

      That entirely depends on the goals. If they are trying to seek restitution there's no reason not to release the code. The facts can't be changed.

      If they are trying to force a settlement or pump and dump, then keeping the code secret is the best thing to do.

      The way I see it, releasing the code just speeds up the process. If the process ends with them dead, they want to slow it down as much as possible.

      Linux kernel developers would probably have the offending pieces rewritten in a week and back-ported to all 2.4/2.5 kernels within another week.

      This will happen whenever the code is released, so it makes not difference.

    6. Re:Code won't be released until trial by Tsu+Dho+Nimh · · Score: 5, Insightful
      "It doesn't absolve anyone from past infringements"

      The clock on SCO's ability to sue the infringer/s started ticking last summer, when they claim to have noticed the problem. They have under two years to file a proper infringement of copyright suit aginst any and all infringers. (3-year time limit) Undre copyright law, whoever submitted the code is the infringer, not the unknowing distributors or totally innocent user. AFTER the infringement case/s are settled, the court may, at the court's discreton, order destruction of all copies of the infringing material. But not until the whole damned thing is settled ...

      Distributors are much the same as book or magazine publisher: you must formally notify them of a copyright infringement by one of their authors (specifying not only that there is infringement, but EXACTLY what is infirnged (showing your proof of holding the copyright), and where (in a book you published in the last decade is not enough). You have to give them enough information to investigate and decide if it's infringing or not. Only after all this, and a court decision, if they continue to publish or distribute the infringing material, do they become actual infringers.

      SCO has not even begun the processs that you have to follow to get copyright infringements cleared up. And their flat REFUSAL to identify the infringing material would certainly be held against them by a judge. Freezing downloads and quickly rewriting the offending code is what the developers not only WOULD do, it's what they legally MUST do, and SCO is preventing them from doing it ...

    7. Re:Code won't be released until trial by Zathrus · · Score: 3, Insightful

      Agreed on everything you said (excellent grasp of copyright law BTW), except that the GP post is still correct -- it doesn't matter.

      SCO isn't suing over copyright claims, they're suing over breech of contract and disclosure of trade secrets. If they can prove that then it doesn't matter, vis a vis the IBM suit, whether or not the Linux code is changed -- IBM still broke the contract and released trade secrets. The kernel devs could release a 100% brand new, totally non-infringing kernel tomorrow and it wouldn't change the arguments in the IBM suit.

      All of this would have a dramatic effect on the Red Hat suit though, and I agree that that's the more interesting and relevant suit anyway. After all, even if IBM did breech contract and release trade secrets, SCO can't stuff the toothpaste back in the tube -- those trade secrets are null and void now and there's nothing that can be done about them (except for IBM paying a ton of money).

      Of course, SCO's suit against IBM is only slightly less flimsy than their nebulous copyright infringement claims...

    8. Re:Code won't be released until trial by Anonymous Coward · · Score: 0

      > duty-bound to prevent damages

      Not exactly. If they accept the damages, they don't have to do anything about it. However, in choosing to let the damages go, you can't come back later and make a claim.

      > if it is within their power?

      SCO will claim it is not within their power to release the code. They are saying the same license that binds IBM to a NDA binds them. In fact, that would be true. SCO releasing secret code would indeed harm those to whom they licensed the code.

      BUT, in this case, the code is already out from under the NDA and is no longer secret. The Unix licencess would well be damaged by having their "secret code" in the public eye under Linux. However, the public knowing the location of the code in Linux can do them no possible harm. Even if "location" could case harm, SCO could have asked IBM to remove the offending code in any of a series of patches that left the code in question beyond recognition.

      SCO will, likely, lose that claim. If so, they will be bound from collecting damages that they could have prevented. "Linux licenses" will be pointless, the upping from $1 to $3Bln will likely be disallowed, etc.

      > From what I can see much of the supposed damage could have been mitigated by SCO with a simple email or newsgroup posting.

      That is part of IBM's case, I believe. SCO/Caldara/UnitedLinux were all VERY involved in Linux development. That suggests they , um, at least, read the Kernel newsgroup. It would have been really hard to miss all the threads passing by on RCU/NUMA updates. SCO can't claim ignorance, nor can it claim "damage" after doing nothing.

    9. Re:Code won't be released until trial by Anonymous Coward · · Score: 0

      > Only after all this, and a court decision, if they continue to publish or distribute the infringing material, do they become actual infringers.

      Not always true. An illegal DVD reproduction outfit can be called to terms, day 1. Things are different when you intentionally participate in infringment.

      But, in any potential Linux case, you're pretty much on target. The copyright violation is not obviously knowing, and the claim is, in fact, under contention. IBM owns the copyrights in question.

      SCO's potental copyright claim on Linux is different from those on IBM. If SCO is found to have "control rights" on IBM's code, then IBM may have to pay up for releasing it.

      That still leaves the very concept of a SCO "Linux license" most bizzar.

      1) Even if IBM loses, SCO simply can not file a copyright claim on code IBM owns. Even if IBM was not allowed to release the code. A copyright suit demands you 1) "own" the copyright and 2) that it be properly registered in your name. SCO can't demonstrate either.

      2) There are no patent issues, at least none related to SCO's ownership.

      3) It isn't a trademark issue. Yet, I guess, but who know's with SCO.

      4) You and I have no contract with SCO.

      So, SCO"s "IP" isn't copyright, patent, trademark, or contractual. What other basis is there for "IP"? Karma?

    10. Re:Code won't be released until trial by gotem · · Score: 1

      SCO will have a very hard time trying to mantain the stock price until then, they will run out of topics for a press release

    11. Re:Code won't be released until trial by Anonymous Coward · · Score: 0

      SCO would make a bad move to release the code before the trial

      Wrong.

      SCO is making a bad move by not releasing the code before the trial.

      Linux kernel developers would probably have the offending pieces rewritten in a week and back-ported to all 2.4/2.5 kernels within another week.

      And how is that bad for SCO? SCO is claiming that they are being injured. The first thing they have to do is to attempt to stop it.

      By refusing to tell anyone where the alleged infringing code is, they're making it impossible to collect any damages.

  30. Care to let SCO know what y'all think of this? by Anonymous Coward · · Score: 0

    Just follow the directions here.

  31. Official notice of your Poor Post by Anonymous Coward · · Score: 1, Funny

    PoorPost Form v. 0.1

    Your post has been moderated positively but that moderation must have been in jest or error. Your post sucks. Please review this form to understand the weaknesses in your post and how to produce higher quality posts in the future.

    [*] Your post was modded funny but is not really funny. This is because:
    () You post simply used M$ instead of MS
    () You went back to beating the Windows security dead horse
    (*) You made a tired SCO joke
    () You made a Jon Katz joke (who?)
    () MS blowz, linux rules (or a variant)
    () You made an unoriginal joke about Slashdotting (servers turning to powder, melting, etc.)
    () Other (please comment here: )

    [] Your post is modded insightful, informative, or interesting. In fact it
    is neither of the three. This is because:
    () You stated the obvious
    () You simply tossed out lots of five-dollar words
    () It was in response to a poorly-written post or troll
    () You copied text from a previous post that really might have been one of the three I's
    () You simply criticized Microsoft without making it funny
    () It is bloated with unnecessary technical claptrap
    () All you did was pose questions (like a stoner)
    () All you did was pose questions (like a lawyer)

    [] Your post may be rated too highly in general for the following reasons:
    () You are an asterisk who has, knowing the story's release time in advance, pounceposted to get first p0st and get modded up early
    () You are one of the editors and are getting your ass kissed
    () One of your fans has weighed in for you
    () One of the editors has blessed it with an "underrated"

    [] Additional comments:

    Thanks for posting! Better luck next time! :)

    ( This form is currently in alpha and suggestions for its improvement are
    always welcome. )

    1. Re:Official notice of your Poor Post by Anonymous Coward · · Score: 0

      PoorPost Form v. 0.1

      Your post has been moderated positively but that moderation must have been in jest or error. Your post sucks. Please review this form to understand the weaknesses in your post and how to produce higher quality posts in the future.

      [] Your post was modded funny but is not really funny. This is because:
      () You post simply used M$ instead of MS
      () You went back to beating the Windows security dead horse
      () You made a tired SCO joke
      () You made a Jon Katz joke (who?)
      () MS blowz, linux rules (or a variant)
      () You made an unoriginal joke about Slashdotting (servers turning to powder, melting, etc.)
      () Other (please comment here: )

      [] Your post is modded insightful, informative, or interesting. In fact it
      is neither of the three. This is because:
      () You stated the obvious
      () You simply tossed out lots of five-dollar words
      () It was in response to a poorly-written post or troll
      () You copied text from a previous post that really might have been one of the three I's
      () You simply criticized Microsoft without making it funny
      () It is bloated with unnecessary technical claptrap
      () All you did was pose questions (like a stoner)
      () All you did was pose questions (like a lawyer)

      [*] Your post may be rated too highly in general for the following reasons:
      () You are an asterisk who has, knowing the story's release time in advance, pounceposted to get first p0st and get modded up early
      () You are one of the editors and are getting your ass kissed
      () One of your fans has weighed in for you
      () One of the editors has blessed it with an "underrated"
      (*) You created a long, dumb ass form, showing you have nothing worthwhile to do with your life.

      [*] Additional comments:
      Go die.
      Thanks for posting! Better luck next time! :)

      ( This form is currently in alpha and probably should never be used again as it was a very stupid idea. )

    2. Re:Official notice of your Poor Post by n1nj4k3n · · Score: 2, Funny
      You created a long, dumb ass form, showing you have nothing worthwhile to do with your life.

      You don't read Slashdot very often, eh?

    3. Re:Official notice of your Poor Post by Anonymous Coward · · Score: 0

      Not religiously enough that the comment would apply to me.

    4. Re:Official notice of your Poor Post by Anonymous Coward · · Score: 0, Offtopic

      PoorPost Form v. 0.1

      Your post has been moderated positively but that moderation must have been in jest or error. Your post sucks. Please review this form to understand the weaknesses in your post and how to produce higher quality posts in the future.

      [] Your post was modded funny but is not really funny. This is because:
      () You post simply used M$ instead of MS
      () You went back to beating the Windows security dead horse
      () You made a tired SCO joke
      () You made a Jon Katz joke (who?)
      () MS blowz, linux rules (or a variant)
      () You made an unoriginal joke about Slashdotting (servers turning to powder, melting, etc.)
      () Other (please comment here: )

      [] Your post is modded insightful, informative, or interesting. In fact it
      is neither of the three. This is because:
      () You stated the obvious
      () You simply tossed out lots of five-dollar words
      () It was in response to a poorly-written post or troll
      () You copied text from a previous post that really might have been one of the three I's
      () You simply criticized Microsoft without making it funny
      () It is bloated with unnecessary technical claptrap
      () All you did was pose questions (like a stoner)
      () All you did was pose questions (like a lawyer)

      [*] Your post may be rated too highly in general for the following reasons:
      () You are an asterisk who has, knowing the story's release time in advance, pounceposted to get first p0st and get modded up early
      () You are one of the editors and are getting your ass kissed
      () One of your fans has weighed in for you
      () One of the editors has blessed it with an "underrated"
      () You created a long, dumb ass form, showing you have nothing worthwhile to do with your life.
      (*) You merely copied the parent post and added nothing but a minor tweak.

      [*] Additional comments:
      Go die.
      Thanks for posting! Better luck next time! :)

      ( This form is currently in alpha and probably should never be used again as it was a very stupid idea. )

    5. Re:Official notice of your Poor Post by Anonymous Coward · · Score: 0

      PoorPost Form v. 0.1

      Your post has been moderated positively but that moderation must have been in jest or error. Your post sucks. Please review this form to understand the weaknesses in your post and how to produce higher quality posts in the future.

      [] Your post was modded funny but is not really funny. This is because:
      () You post simply used M$ instead of MS
      () You went back to beating the Windows security dead horse
      () You made a tired SCO joke
      () You made a Jon Katz joke (who?)
      () MS blowz, linux rules (or a variant)
      () You made an unoriginal joke about Slashdotting (servers turning to powder, melting, etc.)
      () Other (please comment here: )

      [] Your post is modded insightful, informative, or interesting. In fact it
      is neither of the three. This is because:
      () You stated the obvious
      () You simply tossed out lots of five-dollar words
      () It was in response to a poorly-written post or troll
      () You copied text from a previous post that really might have been one of the three I's
      () You simply criticized Microsoft without making it funny
      () It is bloated with unnecessary technical claptrap
      () All you did was pose questions (like a stoner)
      () All you did was pose questions (like a lawyer)

      [*] Your post may be rated too highly in general for the following reasons:
      () You are an asterisk who has, knowing the story's release time in advance, pounceposted to get first p0st and get modded up early
      () You are one of the editors and are getting your ass kissed
      () One of your fans has weighed in for you
      () One of the editors has blessed it with an "underrated"
      (*) You created a long, dumb ass form, showing you have nothing worthwhile to do with your life.

      [*] Additional comments:
      Go die.
      Thanks for posting! Better luck next time! :)

      ( This form is currently in alpha and probably should never be used again as it was a very stupid idea. )

  32. isn't this enough to find matches? by ArmorFiend · · Score: 5, Insightful
    'approximately 148 files of direct Sequent UNIX code to the Linux 2.4 and 2.5 kernels, containing 168,276 lines of code. This Sequent code is critical NUMA and RCU multi-processor code previously lacking in Linux.

    Doesn't some linux zealot happen to have these sources lying around? Can't he/she just start looking for long matches in the Linux kernel?

    Can't Linux developers just audit all their "critical NUMA and RCU multi-processor code", to look for shady origins? There's a big difference between the 80 lines previously claimed and the 168,000 lines now claimed!
    1. Re:isn't this enough to find matches? by antibryce · · Score: 3, Insightful
      Can't Linux developers just audit all their "critical NUMA and RCU multi-processor code", to look for shady origins?


      SCO is finally admitting that it is Sequent code in Linux that they are upset about. There's no reason Linux developers should have to remove this code since IBM now owns Sequent and is legally allowed to contribute code it helped develop and now owns.

    2. Re:isn't this enough to find matches? by valisk · · Score: 3, Interesting
      You don't have to be a zealot to know that this is the code IBM donated from their Sequent division.

      What will be interesting is if when the dust settles this is the kernel code that SCaldera have claimed is theirs and has been copied verbatim into the Kernel.

      Pretty amusing when you consider that not a single line of this code originated with SCO/Caldera/AT&T or Novell and in fact the SCO group have never owned any of this code and agreements and amendments to the original SYS 5r4 license signed between IBM and AT&T grant IBM full control over any code they create for use with AIX, and that Sequent developed the technology seperate from Unix but implemented it on Unix which disallows claims from SCaldera that the code is a derivative of their work.

      --

      Economic Left/Right: -0.62
      Social Libertarian/Authoritarian: -3.69
    3. Re:isn't this enough to find matches? by Anonymous Coward · · Score: 0

      Well, they say it's actualy because of the way Sequent licenced System V. So it's not a simple as you say. The details don't really matter, because tomorrow SCO will have a different story. They can keep changing the story until they finally sue someone using Linux, but I doubt that will ever happen. The insiders at SCO will have cashed in all the options and sold all the stock by then.

    4. Re:isn't this enough to find matches? by Anonymous Coward · · Score: 0

      Note that this has already been address. I don't have the URL handy, but for example. RCU was the concept and product of University research. Sequent's example was specifically labelled as a way for implementing RCU in Sequent's environment. I suspect the University involved will have some harsh words for SCO regarding SCO's attempt at IP theft from the University.

      Sorry about not having the URL handy but I'm sure some Googling Guru (tm) can locate it and post it.

    5. Re:isn't this enough to find matches? by clarkc3 · · Score: 1

      check out this post for the url and info.

    6. Re:isn't this enough to find matches? by g0del · · Score: 3, Funny
      Pretty amusing when you consider that not a single line of this code originated with SCO/Caldera/AT&T or Novell and in fact the SCO group have never owned any of this code and agreements and amendments to the original SYS 5r4 license signed between IBM and AT&T grant IBM full control over any code they create for use with AIX, and that Sequent developed the technology seperate from Unix but implemented it on Unix which disallows claims from SCaldera that the code is a derivative of their work.

      That sentence should be taken out back and shot.

    7. Re:isn't this enough to find matches? by penguin7of9 · · Score: 1

      Doesn't some linux zealot happen to have these sources lying around?

      ftp.kernel.org has the complete history, as do the version control archives.

    8. Re:isn't this enough to find matches? by Dcnjoe60 · · Score: 1

      You have to look at how SCO counts tainted source code. If I write a module or a driver or something, say for memory manipulation or even a video driver and to get it to work, I need to change something in the kernel, maybe add a defines or change a simple setting, or add a line to see if my code is loaded and if not, load it, SCO rightfully says I've made a derivative work.

      The question is what part is the derivative work? The changes I made to the kernel, the module or driver or both. Here is where the problem comes in. Most likely, the changes made to the kernel could be construed as derivative. But to claim that the module itself is would mean that by extension of that flawed logic, any module, program, script, etc. that can be used with Unix is also a derivative work.

      To follow that logic to the extreme (and why the court won't) is to say that even Oracle is a derivative work!

      Let's say the courts rightfully declare that code that is still owned by other people but used by Unix is not a derivative work and only changes made to the kernel, to make such code work, could be constituted as derivative works. Then there are two questions at stake. First does this more limitedly defined derivative works constitute a significant infringement on SCO? Only the courts will tell, but most likely the amount of infringing code will be very small (maybe 80 lines).

      Second, regardless of the first question, does this more limitedly defined derivative works keep people from being able to add code to Unix without loosing their rights to their own code. If so, the courts would most likely hold that this is a barrier to competition and it's sole purpose is to prevent competition and is therefore invalid (there are numerous cases to back this up).

      Either way, it is highly unlikely that the courts will agree with SCO. Finally, if they do, then there is a whole nother discussion on what copyrifht ownership means, since SCO says that IBM/Sequent own their code. If you own copyright to something but can't use it freely as you wish than copyrights must not have any real value at all. I don't think that courts would not throw out all of the case law on copyrights just to appease SCO's dillusions.

      Dcnjoe60

      p.s. just thought of something, if the courts did throw out all the copyright laws on the books, what would that do the RIAA and the DMCA?

    9. Re:isn't this enough to find matches? by Anonymous Coward · · Score: 0

      They included white space this time.

    10. Re:isn't this enough to find matches? by El · · Score: 1

      If these 148 files are "direct Sequent UNIX code", then shouldn't they still have the Sequent copyright in them? I've never worked for any company that didn't put a copyright notice in every file as a matter of general principle. Is SCO alleging they copied the files but removed the copyright notices?

      --

      "Freedom means freedom for everybody" -- Dick Cheney

    11. Re:isn't this enough to find matches? by Anonymous Coward · · Score: 0

      SCO is finally admitting that it is Sequent code in Linux that they are upset about. There's no reason Linux developers should have to remove this code since IBM now owns Sequent and is legally allowed to contribute code it helped develop and now owns.

      Since it's the Sequent code that's the problem, the termination of the AIX license is illegal. IBM can screw them over on that one.

      Since SCO's claims are based originally on AIX, IBM can claim all sorts of damage to reputation and business things.

      Ofcourse it's not SCO's trade secret, since the patents belong to IBM. It's just SCO's code, which is copyright infringement; if the Sequent Contract is in force, and is as SCO claims.

    12. Re:isn't this enough to find matches? by valisk · · Score: 1

      Sadly, that sort of thing happens when you wake up as drunk as you were when you went to sleep :..(

      --

      Economic Left/Right: -0.62
      Social Libertarian/Authoritarian: -3.69
  33. Re:McBride? McBriii-ide? Hello? by Speare · · Score: 5, Funny
    Hello, McBride? McBriii-ide? Hello? :noogie:

    Think, McBride. If I checked in my NUMA code under your copyright, I'd get sued. You wouldn't want that to happen, would you? ... Would you!?

    Look, your stock's down. :poke: Ha hah, don't be so gullible, McBride.

    --
    [ .sig file not found ]
  34. What'd ya expect? by cblguy · · Score: 3, Funny

    It's Wednesday. Time for the SCO Press Release. Just like tomorrow's Thursday. Time for the latest Microsoft Windows Update patch. Anyone surprised by this "next ridiculous statement"? I'm not...

  35. Since when have Press Releases by Boss,+Pointy+Haired · · Score: 5, Insightful

    been part of the due legal process?

    This really pisses me off that companies put out "press releases" covering what should be a private matter between the parties involved.

    Why don't journalists just ignore SCO in the same way a parent ignores a screaming child pushing for an ice cream?

    1. Re:Since when have Press Releases by brotherscrim · · Score: 1

      parents don't get paid for paying attention to their screaming kids.

    2. Re:Since when have Press Releases by Anonymous Coward · · Score: 0
      Since when have Press Releases been part of the due legal process?
      Since around the time due commencing groundless legal actions became the first step in a management pump-and-dump of their stock holdings...
    3. Re:Since when have Press Releases by Boss,+Pointy+Haired · · Score: 1

      True, but I thought the press didn't like people whoring for attention; which is obviously what SCO are doing...

    4. Re:Since when have Press Releases by tomhudson · · Score: 3, Insightful
      poster wrote:
      Why don't journalists just ignore SCO in the same way a parent ignores a screaming child pushing for an ice cream?
      ... because the SCO case is like a big train wreck happening before your eyes ... it's horrible to watch, but you can't tear your eyes away from all the destruction. SCO still hasn't figured out that the light at the end of the tunnel is another (much bigger) train.
    5. Re:Since when have Press Releases by Anonymous Coward · · Score: 0

      Haven't been reading tech journals (sic) for the past 10 years, have your?

      Seriously, if PR can be (poorly) regurgitated as analysis, why not as 'part of the due legal process?'

    6. Re:Since when have Press Releases by Anonymous Coward · · Score: 0

      True, but I thought the press didn't like people whoring for attention

      No offence, but have you read a newspaper in the last 100 years?

    7. Re:Since when have Press Releases by renard · · Score: 2, Interesting
      Since when have Press Releases been part of the due legal process?

      They're not. They are a longstanding part of the classic pump-and-dump, however.

      Why don't journalists just ignore SCO...

      1. This is Slashdot. There are no journalists here.
      2. This is just a link to SCO's press release - there is no evidence that actual journalists are paying attention to it, as yet.
      3. If SCO can move the markets with this horse manure, then it doesn't matter how badly it smells, it's still news.
      -renard
    8. Re:Since when have Press Releases by plugger · · Score: 1

      The press like anything which helps their publications to sell.

    9. Re:Since when have Press Releases by babyrat · · Score: 1

      in the same way a parent ignores a screaming child pushing for an ice cream?

      Oh for crying out loud, don't ignore your screaming child - you may be used to ignoring the screaming but everyone else around you isn't! I almost bought a kid (never seen him before but he was whining uncontrollably to his mother) a candy bar the other day just to get some peace and quiet whilst waiting in line.

    10. Re:Since when have Press Releases by Anonymous Coward · · Score: 0
      Good Lesson you taught the kid:

      You cry enough and someone will give you what you want.

      FM 888

    11. Re:Since when have Press Releases by geekoid · · Score: 1

      first, it is announced to influence stock prices.

      second, it is the journelist responsibility to see that people are aware of newsworthy items. this is a news worthy item because it effect so many people.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    12. Re:Since when have Press Releases by jrhick · · Score: 1

      Now you have set the kid on the path to become a VP in SCO/Caldera.

      --
      Jay R. Hickman Data Communication Services
    13. Re:Since when have Press Releases by AnotherBlackHat · · Score: 1

      Why don't journalists just ignore SCO...


      Never happen.
      But they could use a comment from an opposing source as the headline. For example:

      "RMS says latest SCO press release a complete fiction."

      -- this is not a .sig
    14. Re:Since when have Press Releases by MachineShedFred · · Score: 1

      Funny, I thought my Saturday Night activities were part of the classic pump-and-dump.

      Oh, no wait... they are the classic fsck and chuck! My mistake!

      --
      Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
  36. /. does it again. by sinserve · · Score: 1

    Why isn't this in the "It's Funny, Laugh" section? Nothing saying SCO
    like a cute fat-boy's foot icon.

    1. Re:/. does it again. by Anonymous Coward · · Score: 0

      You think fat boys are cute too? Rawr!

  37. Profit! by Dausha · · Score: 1

    I think SCO has finally figured out what that vague middle step is in the concept to profit cycle. It is actually two steps instead of one.

    3a. Sue major corp for 'alleged IP violations' (i.e. Pump)
    3b. Board members dump stock on unsuspecting investors (i.e. Dump)
    3b (alt). Get bought out by major corporation 4. Profit!

    But, for all of you who are like me and have wondered what these guys have been smoking (and perhaps, where you could get some), it is becoming increasingly obvious that they are flailing in the wind to elevate stock prices so they can dump and run. They will all then quietly resign and the incoming board will reap the chaos sown.

    --
    What those who want activist courts fear is rule by the people.
  38. IBM Press Release by Ralph+Wiggam · · Score: 1, Funny
    From: IBM Headquaters
    Date: 8/13/2003
    Re: SCO termination of UNIX license

    To be read aloud in high pitched whiney voice

    Ooooohhhh. I'm so scared.

    -B

  39. RCU, NUMA... by Anonymous Coward · · Score: 5, Interesting

    So, if the "stolen" code is in RCU and NUMA, why are they asking money from single processor systems? AFAIK this RCU and NUMA stuff is all SMP related, and not even compiled in single processor systems.

    1. Re:RCU, NUMA... by FJ · · Score: 4, Interesting

      But you can download a version of the 2.4 kernel source from SCO for free. There are no license agreements or anything to sign.

      In other words, they are distributing the same thing they are saying has been stolen.

    2. Re:RCU, NUMA... by dangermen · · Score: 0

      I'm not using RCU or NUMA in 2.4. Sue me SCO, I'll sue your shit right back for harassment.

    3. Re:RCU, NUMA... by donutz · · Score: 1

      But you can download a version of the 2.4 kernel source from SCO for free. There are no license agreements or anything to sign.

      And the obligatory link (download the kernel and all the rest of SCO's linux distro's source) is...

      ftp://ftp.sco.com/pub/updates/OpenLinux/3.1.1/Serv er/current/SRPMS/

    4. Re:RCU, NUMA... by DickBreath · · Score: 2, Interesting

      I wonder how it will sound to a judge and jury for SCO to claim damages on something where they are helping to create the damage.

      1. Offer Linux for download.
      ---and---
      2. Don't disclose the IP infringement so that the infringement can be cured by parties who are not willfully infringing, such as Red Hat, SuSE, etc.

      --

      I'll see your senator, and I'll raise you two judges.
    5. Re:RCU, NUMA... by John+Harrison · · Score: 1
      I usually don't respond to ACs, but this one is modded up to +5 and needs clarification so here goes...

      NUMA is not SMP. They are two different technologies for putting multiple processors in a machine.

    6. Re:RCU, NUMA... by Ian+Lance+Taylor · · Score: 1

      SCO is trying to get money from Linx users on the basis of code which SCO claims has been copied directly from Unix into Linux. This is the code which SCO has been showing under NDA.

      This code is not the same as the code which is the basis for the IBM lawsuit.

      Two different things.

    7. Re:RCU, NUMA... by Anonymous Coward · · Score: 0
      Either you've seen the code under the NDA, (in which case you're possibly in a position to make the statement that it's different code, but in all probability in breach of the NDA), or you haven't (in which case you're bullshitting).

      Which is it?

    8. Re:RCU, NUMA... by Ian+Lance+Taylor · · Score: 1

      In fact, I have seen the code under NDA.

      But I don't need to do that in order to say that it is different code. SCO is saying that already--they are just saying it in a (possibly deliberately) confusing manner.

      SCO is claiming that code was copied directly from Unix to Linux. That is the code they are showing under NDA. SCO is also claiming that IBM/Sequent has contributed code to Linux, in violation of IBM/Sequent's contract with AT&T.

      I hope that you agree with that.

      Now, think about it: the IBM/Sequent code is not in Unix. Why would it be? SCO didn't write it, nor did any previous owner of the Unix source code. IBM certainly didn't give it to SCO. Why would they? For IBM, it's a competitive advantage.

      So when SCO claims that code has been copied directly from Unix into Linux, they can not be talking about the IBM code, as that code was never in Unix in the first place.

      QED.

  40. contents of letter notification sent by SCO to IBM by cswiii · · Score: 0, Offtopic

    helo IBM
    ehehh1!1 j00 R t3h 0wn3d!!11
    u will nevar figuor out who t00k u down!!
    LEENUX SUX!!

    SCO

    ps NYEAH!!1

  41. I love this part! by willy134 · · Score: 2, Funny
    The SCO Group (Nasdaq: SCOX) helps millions of customers in more than 82 countries to grow their businesses everyday. Headquartered in Lindon, Utah, SCO has a worldwide network of more than 11,000 resellers and 4,000 developers. SCO Global Services provides reliable localized support and services to partners and customers. For more information on SCO products and services, visit http://www.sco.com .

    Helps millions of customer!!! Yeah by serving legal notices. I think they are spending more time reading linux code than they are fixing any of their own code.

    --
    Can you ping me now?... Good!
    1. Re:I love this part! by justsomebody · · Score: 1

      Yeah, since when their three customers count for millions.

      --
      Signature Pro version 1.13.2-3 release 83.5 beta3try7 after-breakfast edition
  42. In other breaking news... by chrisgeleven · · Score: 3, Funny

    IBM has announced today that it has terminated SCO's right to existance. A tomb stone has been made that says "R.I.P. SCO, You ungrateful bastards." and has a holographic penguin to the top of the inscription that continiously pisses on the letters S-C-O.

  43. In other news... by Psarchasm · · Score: 4, Funny

    SCO has recently announced their new corporate logo, and policy for dealing with IP piracy.

    --
    http://windows.scares.us
  44. The plot ... by AftanGustur · · Score: 1


    By now, everyone should have figured out what SCO is up to ...

    It's simply a group of people who bought a broken company they thought had some value, found out it didn't, and are now trying to get some of their money back by inflating their stock with press releases and selling it as they go..

    Belive me, SCO will try to stall it's case against everyone for as long as possible..

    --
    echo '[q]sa[ln0=aln80~Psnlbx]16isb572CCB9AE9DB03273snlbxq' |dc
  45. Have fun. by Anonymous Coward · · Score: 0

    Blake Stowell, +1-801-932-5703, bstowell@sco.com, or Marc
    Modersitzki, +1-801-932-5635, both of The SCO Group; or Avi Dines, or Brian
    Willinsky, both of Schwartz Communications, +1-781-684-0770,
    sco@schwartz-pr.com, for The SCO Group /Photo: NewsCom: http://www.newscom.com/cgi-bin/prnh/19990421/SCOLO GO
    AP Archive: http://photoarchive.ap.org
    PRN Photo Desk, 888-776-6555 or 212-782-2840

  46. I wonder how much influence /. has on SCO stock? by DG · · Score: 3, Funny

    I can't help but wonder how much influence Slashdot might have on SCO stock price.

    Like if Slashdot were to "accidentally" publish a story like "SCO Insider Reveals Code Copied From Linux to UnixWare!' - how much would the stock drop?

    Makes one think... not that I'd suggest anybody actually TRY this.

    DG

    --
    Want to learn about race cars? Read my Book
  47. The stolen lines revealed by Fresnik · · Score: 3, Funny
    Finally the "stolen lines" have been revealed. It seems that the 168,276 lines of code are in fact duplicates of only 5 lines of code. These are:

    1. #else
    2. #endif
    3. //
    4. /*
    5. */
    1. Re:The stolen lines revealed by TheViffer · · Score: 1

      And finally ...

      6.

      --
      -- Knowing too much can get you killed, but knowing who knows too much can make you rich.
    2. Re:The stolen lines revealed by Overly+Critical+Guy · · Score: 0

      Yeah, a variation of this joke gets posted to EVERY SINGLE SCO ARTICLE and it never stops being so inventive, funny, and clever.

      They're referring to comment delimiters and preprocesser statements! LOL!!!11

      Disregard, if I'm being overly critical.

      --
      "Sufferin' succotash."
    3. Re:The stolen lines revealed by RyuuzakiTetsuya · · Score: 1

      except I own the exclusive right to #ifdef.

      TIME TO SUE

      --
      Non impediti ratione cogitationus.
    4. Re:The stolen lines revealed by Fresnik · · Score: 0

      "A good joke is still funny no matter how many times you hear it."

  48. SCO forum postponed by Brian+Blessed · · Score: 2, Interesting

    There's a notice on ir.sco.com about the SCO forum, which was to be held in Las Vegas next week:

    Notes: SCO Forum in Las Vegas has been postpoined until Autumn 2003

    Read into that what you will...

    - Brian.

    1. Re:SCO forum postponed by Anonymous Coward · · Score: 0

      I'll read nothing into this. I was on the phone with SCO yesterday. It is Autumn 2003.

      I'll be there for SCOx web services, not for SCO UNIX.

      Yes, I'm being anon for a reason.. I don't need to be hunted down while I'm there...

    2. Re:SCO forum postponed by Chmarr · · Score: 1

      I'll read in that someone can't spell :)

      It seems strange, though, that they still have all their glitzy web pages advertising the SCO Forum, but there's one tiny little part that says the forum is postponed. Here's my analysis:

      1. It was some kind of crack.

      2. It really is postponed, But they don't want to advertise the fact, both for the obvious reasons of negative PR, but also because they want all the anti-SCO crowd to turn up anyway. They've probably emailed all the people who have actually registered to make sure they're not cheesed off. However, this will seriously impact the people who legitimately wanted to turn up, but were going to sign-in on the day.

    3. Re:SCO forum postponed by Anonymous Coward · · Score: 0

      SCO Forum was orginally going to be held this spring. It was postponed until Aug 17th through Aug 19th.

      They have all of their "glitzy web pages" on their site about SCO forum, because they are still hosting it. Call the MGM Grand if you don't believe it and see if the conference space is still reserved by SCO. I'll be you $100 that it's still on...

    4. Re:SCO forum postponed by Chmarr · · Score: 1

      Well, it appears that SCO have updated their calendar software to remove the 'postpoinment'[sic] message :)

    5. Re:SCO forum postponed by MS_leases_my_soul · · Score: 1

      Maybe they thought it was more prudent to put their money into lawyers right now instead of the 10,000 security guards it would have taken to try to keep the riot from starting.

  49. injunction by siskbc · · Score: 4, Interesting
    It's interesting that SCO is taking such drastic measures such as the license termination and licensing linux to end users before they even go to trial. The logical conclusion one draws from such measures is that they do not have a case, and do not think they can win. I can't believe that the court system is allowing this to occur,

    Good point. I don't know why IBM hasn't filed for a temporary injunction against the license termination. It would accomplish two things. 1) it would put AIX users a bit at ease (even if IBM has indemnified them), and 2) would get this thing in a courtroom quicker which is *obviously* the last thing SCO wants. I believe when they start getting legal defeats the stock will tank.

    --

    -Looking for a job as a materials chemist or multivariat

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

      I don't know why IBM hasn't filed for a temporary injunction against the license termination.

      They haven't, because they don't need to. They have a license, which is "perpetual and irrevocable".

      would get this thing in a courtroom quicker which is *obviously* the last thing SCO wants

      But it could backfire against IBM as well - asking a judge to do something like that is asking for trouble.

      A better solution (and it appears to be the one that IBM is using) is to go ahead 'business as usual', then if SCO harrasses their customers, get an injunction against them for interference, which would (probably) get SCO shut down for good.

    2. Re:injunction by DoctorPepper · · Score: 2, Insightful

      Because IBM steadfastly maintains that SCO doesn't have the right to terminate their license. If they filed for a temporary injunction, it would be tantamount to admitting that SCO does indeed have the right to terminate the license.

      --

      No matter where you go... there you are.
    3. Re:injunction by Anonymous Coward · · Score: 0

      It may get it into a courtroom quicker, but it may also draw out yet another aspect to this whole mess. I may be wrong, but I'm thinking IBM wouldn't go too far in challenging certain aspects simply because they'd give validity to SCO's position in general. It's more like a PR move than anything else: the less IBM fights (in some respects) the less viable SCO looks with their very active legal/PR machine...albeit a very broken machine.

      IBM can kill off SCO in less time if there are fewer issues to work out in court.

    4. Re:injunction by Zeinfeld · · Score: 1
      Good point. I don't know why IBM hasn't filed for a temporary injunction against the license termination.

      They did.

      The IBM countersuit goes into quite a bit of detail on the issue. They claim that their license is irrevocable and they list a series of issues in connection with it. They have obtained a statement from Novell that states that they are in compliance with the contract and that SCO does not have termination rights.

      IBM seeks a variety of inhjunctions, in particular to prevent SCO purporting to claim that the license has been terminated.

      In other news SCO announced that they have appointed Bill O'Reilly as their VP of frivolous littigation/

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    5. Re:injunction by Anonymous Coward · · Score: 0

      > I don't know why IBM hasn't filed for a temporary injunction against the license termination.

      Maybe IBM wants to use this legal attack as a formal justification to drop AIX, which is something probably in the air since some time.

    6. Re:injunction by anthonyrcalgary · · Score: 1

      I don't know why IBM hasn't filed for a temporary injunction against the license termination.

      They might just ignore the license termination and treat it as though it's not credible. IBM might just be egging SCO on to do increasingly stupid things that will ultimately hurt them in the lawsuit and expose them to liability.

      Before this is over, IBM's various countersuits are going to award IBM more in damages than SCO is worth. Even if SCO wins the lawsuit, they're fucked. IBM will pound them into rubble until the only way to settle up will SCO stock... all of it.

      --
      When someone might yell at me, it has to be OpenBSD.
    7. Re:injunction by Anonymous Coward · · Score: 0

      No, it would be tantamount to claiming that SCO has not proven its case and therefore can be enjoined from revoking the license.

    8. Re:injunction by budgenator · · Score: 1

      IANAL but if SCO says they've; terminated the license that IBM uses to distribute AIX, it follows that any distribution of AIX is illegal. I f you say somebody such as IBM is illegaly distibuting something such as AIX, then you'd better be able to back it up in court, or be prepared to face a devestating judgement for slander/libel

      --
      Apocalypse Cancelled, Sorry, No Ticket Refunds
    9. Re:injunction by MuParadigm · · Score: 1


      Read IBM's counter-suit please. They did file for temporary injunction, as well as declatory injunction and permanent injunction: "...in particular from i) misreprenting SCO's rights and IBM's rights to UNIX technology, such that SCO can, will, or has in fact, revoked IBM's right to use UNIX..."

      And so on.

  50. Tivo Linux version by Munelight · · Score: 1

    If all the code SCO is complaining about is only in the 2.4 and up kernels, then why are they going after Tivo? I thought the Tivo kernels were 2.0 and 2.2..? Then again I have a history of not knowing what I'm talking about.

    1. Re:Tivo Linux version by MS_leases_my_soul · · Score: 1

      I was under the impression TiVo ran version 2.4.4. Upgrading the TiVo Kernel

    2. Re:Tivo Linux version by LinuxHam · · Score: 1

      bash-2.02# uname -a
      Linux (none) 2.1.24-TiVo-2.5 #8 Wed May 8 15:38:27 PDT 2002 ppc unknown


      Not my Series 1 sa. You managed to get bileduct /.ed, so I can't see what you were linking to.

      --
      Intelligent Life on Earth
  51. Fly on the wall by the+eric+conspiracy · · Score: 1, Funny

    I would like to be there when IBM's legal department gets notification of the double secret termination. There should be wondrous laghter.

  52. Thats what SCO Says but....... by big-giant-head · · Score: 5, Interesting

    IBM owns those patents. You can't say BTW since we license something to you, we now own your patents. IF, big IF, that were the case, IBM would have made them sign a cross-licensing agreement allowing IBM to keep control of thier patents.

    IBM has owned those patents since '92 when they bough sequent, sequent had those patents since the late 80's so either way SCO SOL.

    --

    So Long and Thanks for all the Fish.
    1. Re:Thats what SCO Says but....... by aed · · Score: 5, Informative

      I'm not talking about patents here, but about literal source code.
      According the press release 'SCO's System V UNIX contract allowed Sequent to prepare derivative works and modifications of System V software "provided the resulting materials were treated as part of the Original [System V] Software." Restrictions on use of the Original System V Software include the requirement of confidentiality, a prohibition against transfer of ownership, and a restriction against use for the benefit of third parties.'

      So IBM's patents aren't transferred or licensed to SCO, but if they write code for a System V derivative work (such as AIX) they can't use the code in Linux. The contract basically says 'All your AIX code are belong to SCO'

    2. Re:Thats what SCO Says but....... by rarose · · Score: 4, Interesting

      IBM bought Sequent in '99.
      (I'm an ex-IBMer who transfered to Beaverton right after the sale, and it's absolutely terrible to see what IBM did to the Sequent culture.)

      --
      --Rob
    3. Re:Thats what SCO Says but....... by Anonymous Coward · · Score: 5, Informative
      AFAIK the contract was superceeded by a following letter. IBM when purchasing agreed to all the original terms of the contract then a letter between IBM and AT&T containing a huge number of amendments to the contract was signed.

      This letter specifically gave back to IBM the rights of any code they created to enhance or extend the AIX/SYS5R4 OS.

      This straight away rules out such claims unless SCaldera believe they can convince a Judge and Jury that the superceeding agreement is invalid in someway.

      Something I rather doubt :)

    4. Re:Thats what SCO Says but....... by aflat362 · · Score: 3, Funny
      I hate to be the guy to reply to your Sig, but Carpe Alec is "Sieze the fish" in Latin. Sorry I don't know the Latin word for Carp (I doubt there is one).

      It bothers me when phrases are used in mixed languages like "Mexican restaurante" instead of "Restaurante Mexicano".

      --

      Conserve Oil, Recycle, Boycott Walmart

    5. Re:Thats what SCO Says but....... by Anonymous Coward · · Score: 1, Funny

      Cyprinus carpio.

      Carpe cyprinus carpio.

    6. Re:Thats what SCO Says but....... by msgmonkey · · Score: 5, Insightful

      In addition to this point it will be argued that regardless of the contract position NUMA and RCU are not integral parts of UNIX and could be applied to any operating system being add-on "features" and hence can not be regarded as derivative works.

    7. Re:Thats what SCO Says but....... by greed · · Score: 5, Insightful

      Just a point of clarification, AIX is actually SVR3-based, not SVR4. And there's been a LOT done do it since AT&T handed the code over, as anyone who's programmed for or adminned AIX can tell you.

      Like it or loathe it, you know it is 'different' from both SVR4 and BSD.

    8. Re:Thats what SCO Says but....... by Gherald · · Score: 2, Funny

      it's absolutely terrible to see what IBM did to the Sequent culture

      Buy them suits?

    9. Re:Thats what SCO Says but....... by leandrod · · Score: 3, Interesting
      > IBM's patents aren't transferred or licensed to SCO, but if they write code for a System V derivative work (such as AIX) they can't use the code in Linux.

      Actually SCO mention their contract with Sequent. A lawyer should tell us if Sequent's terms bound IBM in Sequent-related code, or if IBM's terms take effect to all subsidiaries bought by IBM.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    10. Re:Thats what SCO Says but....... by Jboy_24 · · Score: 4, Interesting

      I think also to the point is that by writing NUMA and RCU for AIX, IBM was in no ways bound not to rewrite NUMA and RCU for linux.

      It might turn out that the code in question was really only supportave code, libraries and header information taken from a common ancestor, BSD or earlier unixies

      SCO might be trying to make the point that by taking some code from BSD/AIX and merging with other code then releasing it to Linux, IBM in fact released all the code to linux.

      I point to other posts, made throughout all this time, that AIX's supportave architecture and framework is fastly different then Linux, and a direct copy of code would not work.

    11. Re:Thats what SCO Says but....... by ray-auch · · Score: 4, Informative

      Actually the GPL is not anywhere near as viral as this license - if (big if) it means what SCO say it does.

      The GPL doesn't take away any rights _you_ have to _your_ code, including adding it to other products under other licences. What it says is that if you combine your code with other GPL code you have to release the result under the GPL.

      SCO seem to be claiming that if you add your code to their unix code, it isn't just the resulting unix variant that is a derivative work, but your code (in isolation) is also.

      If SCO are correct, if you took code from another of your products and added it to Unix you would lose the right to ship that other product. That wouldn't happen if you added that code to a GPL product.

    12. Re:Thats what SCO Says but....... by dbrower · · Score: 1
      Don't get it. Sequent was doomed; their lovely culture was a dead end.

      -dB

      --
      "It if was easy to do, we'd find someone cheaper than you to do it."
    13. Re:Thats what SCO Says but....... by Anonymous Coward · · Score: 0

      The article says the copied code comes from dynix (Sequent's verion of UNIX SYS V) not AIX.

    14. Re:Thats what SCO Says but....... by rarose · · Score: 2, Interesting

      No... Sequent the business might have been doomed (due more perhaps to executives and their race car habits than technology), but Sequent the culture was a success.

      --
      --Rob
    15. Re:Thats what SCO Says but....... by Anonymous Coward · · Score: 0

      feeling a little blue? heehee

    16. Re:Thats what SCO Says but....... by Thornkin · · Score: 2, Insightful

      I don't think it matters if they are integral parts. SCO is talking about copyright infringement. Even if NUMA and RCU could be on any OS, this particular implementation of them cannot. I find it hard to believe that IBM would have agreed to grant its copyrights to AT&T/SCO/Current Unix Owner.

    17. Re:Thats what SCO Says but....... by msgmonkey · · Score: 4, Informative

      The Linux RCU code is not from AIX nor Dynix, please read this post: http://slashdot.org/comments.pl?sid=74586&cid=6686 573

      Infact SCO admit they down own the copyrights to RCU, NUMA or JFS as per this story:
      http://mozillaquest.com/Linux03/ScoSource- 24-Copyr ights_Story01.html

      Cutting through the noise SCO are claiming that IBM can not add technology added to AIX to Linux it's more to do with contracts than copyrights.

    18. Re:Thats what SCO Says but....... by ksheff · · Score: 1

      It wouldn't. By SCO's definition, anything written on or for a Unix system is theirs. Write a device driver for something like a terminal server? Oops. Sorry Digi, that's not yours anymore. It's SCO's.

      By that reasoning, then since it's not their code anymore, the vendor shouldn't have to support it. Nope. It's SCO's code now. Make them provide bug fixes & security patches. Maybe the Unix vendors should bill SCO for the years of maintenance that they performed on "SCO's code"?

      --
      the good ground has been paved over by suicidal maniacs
    19. Re:Thats what SCO Says but....... by SillySlashdotName · · Score: 5, Informative

      People still don't seem to get it...

      IBM != Sequent (for year values less than 1992)

      IBM had a contract/license variation with AT&T. Sequent did not. Anything IBM developed, IBM owned. Anything Sequent developed (before being bought and becoming part of IBM), based on the original AT&T license, belongs to the owner of SYS V, so the (rights to the) developements did not belong to Sequent and could not be sold to IBM in '92, so IBM does not own them, never did own them, and can not give them away - they belonged to Novell, and now to SCO.

      Could this possibly be a (perhaps THE) legal leg for SCO's lawsuit?

      This reply completely does not address your admittedly very good point about the patents, as I don't know how the license issue would afftect the patent issue. I.e., can I patent an idea that legally belongs to someone else, even thought it was my idea and I submitted it myself? I would guess 'yes', but it would depend greatly on the exact wording of any contracts/licenses - and we are right back to the license issue. Also, would you be able to charge me license fees on the idea you own, but I patent? Could I charge you for using my patent if you legally own the idea?

      My head is starting to hurt... :->

      --
      Acts of massive stupidity are almost never covered by warranty. --me.
    20. Re:Thats what SCO Says but....... by Dalcius · · Score: 1

      If IBM can own the patents but not the source, that doesn't preclude them from putting the same type of implementation into Linux, even with the same programmers (as they've patented the implementation), they just can't copy.

      This should be interesting, regardless.

      --
      ~Dalcius
      Rome wasn't burnt in a day.
    21. Re:Thats what SCO Says but....... by sharkey · · Score: 1
      Carpe Alec is "Sieze the fish"

      I thought it was "Seize the herrings".

      --

      --
      "Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
    22. Re:Thats what SCO Says but....... by Anonymous Coward · · Score: 0
      that AIX's supportave architecture and framework is fastly different then Linux,

      ... or that AIX's supportive architecture and framework is vastly different than Linux's

    23. Re:Thats what SCO Says but....... by Anonymous Coward · · Score: 1, Funny

      How can the culture be considered anything other than a failure if it lead to the failure of the business?

    24. Re:Thats what SCO Says but....... by jonabbey · · Score: 1

      What it says is that if you combine your code with other GPL code you have to release the result under the GPL.

      It doesn't, actually. What the GPL says is that the GPL doesn't grant you the right to redistribute an intermingling of GPL code with your proprietary code, unless that commingled body is itself licensed under terms no more onerous than the GPL.

      Have you commingled GPL'ed code with your own proprietary code? No problem, so long as you don't distribute.

      Have you commingled code licensed under the GPL with proprietary code and distributed with greater restrictions? Again no problem, so long as the copyright holder(s) on the GPL'ed code are willing to grant you an alternative license for that usage. The GPL can't stop that sort of thing, it just doesn't grant affirmative permission for it.

    25. Re:Thats what SCO Says but....... by rarose · · Score: 4, Insightful

      Because business is no measure of success or failure for a culture. The Sequent folks had more respect for each other and treated each other better than any other company I've been at. They volunteered in the community together, they participated in after-work sports events together, and they have the best alumni networking I've seen.

      There are many reasons for the failure of the business, but none of them had to do with the people working there.

      --
      --Rob
    26. Re:Thats what SCO Says but....... by javiercero · · Score: 1

      Actually IBM bought Sequent in the late 90s (98/99) I believe.

    27. Re:Thats what SCO Says but....... by alienw · · Score: 1

      Could I charge you for using my patent if you legally own the idea?

      You can't own an idea. The closest you can come to that would be a patent. A copyright simply protects a certain chunk of text, of source code, or some other representation of an idea. If you write your own chunk of code that uses the same idea, it's yours (unless there are patents involved).

    28. Re:Thats what SCO Says but....... by ray-auch · · Score: 1

      It doesn't, actually. What the GPL says is that the GPL doesn't grant you the right to redistribute [...]

      Yeah, ok, you do have to distribute to come under that requirement - which is what I meant when I said "have to release", but I needed to add "if you release" because of course you don't _have_ to release/distribute...

      an intermingling of GPL code with your proprietary code, unless that commingled body is itself licensed under terms no more onerous than the GPL.

      Ah, now you're in a similar miswording trap I think - the commingled body absolutely does have to be under the GPL: "the distribution of the whole must be on the terms of this License" - to quote clause 2.

      You can't add extra conditions to the GPL (which might lead you to state "no more onerous than") but, crucially, you also can't take the GPL's conditions away. You can't, for example, link GPL code to (less onerous) BSD code and release the result under BSD.

      All the above is assuming you aren't the copyright holder for (all of) the code in question, if you are then you can do what you like (unless you added it to Unix & believe SCO).

    29. Re:Thats what SCO Says but....... by jonabbey · · Score: 1

      You can't add extra conditions to the GPL (which might lead you to state "no more onerous than") but, crucially, you also can't take the GPL's conditions away. You can't, for example, link GPL code to (less onerous) BSD code and release the result under BSD.

      Just so. Perhaps I should have said "no more onerous to RMS' sense of ethics than".. ;-)

    30. Re:Thats what SCO Says but....... by oolon · · Score: 1

      One question is, do we know exactly what licence sequent had? If I were IBM I would be keeping that one close to my chest till there day in court, because it would be so useful for damages. IBM went to alot of trouble to get its AIX licence, IBM has an army of lawers when it bought sequent I feel sure it worked out ownership of code, otherwise its purchase is useless, and where required clean room implementions would be used before integrating code. I also feel sure IBM will be able to prove this. Perhaps even have videotape of people entering it ;-)

      James

    31. Re:Thats what SCO Says but....... by nutznboltz · · Score: 2, Informative

      Dynix/ptx started with a SVR3 source code tree. They became SVR4 by writing their own code to meet the API specifications in order to save some money over buying an SVR4 code base.

    32. Re:Thats what SCO Says but....... by MuParadigm · · Score: 1


      No, SCO is not talking about copyrights. Copyright infringement does not show up in any of their court claims (yet), nor does it show up in the press release.

      They are taking about "derivative works". Their claim is that IBM's contract with ATT required IBM to treat any derivative works with the same level of confidentiality that is required for the licensed System V code. In other words, this is a claim that IBM violated its contract with ATT/Novell/SCO.

      Under what legal theory SCO extends that into 'ownership' of the intellectual property, no one seems to know. The theory is that there is System V code supplied by other vendors in the Linux kernal, but SCO hasn't really identified what "Intellectual Property" it's licensing in their new license.

    33. Re:Thats what SCO Says but....... by MuParadigm · · Score: 2, Insightful


      That is a really good question. Tom Carey, an IP lawyer, said in an interview with Mozillaquest.com (I know, I know) that he wasn't sure that IBM's licensing terms would apply to the Sequent code.

      I'm not a lawyer, but I've looked through the contracts pretty extensively, and I can't see any wording in the contracts that would apply to "IBM and all its subsidiaries". If there were such language, then I'd guess the Sequent code would now fall under the IBM contracts.

      Without that language, the case is a little murkier. Since IBM made Sequent a division of IBM, rather than retaining its corporate identity (as they did with Lotus), I'm guessing that Sequent should be considered a part of IBM now for the purposes of the licensing. The case might be different if the code was supposed to be "deeded" back to ATT, but it's not clear that that is the case.

      If it comes up, and it sure looks like it will, then it's something the judge will probably have to decide. There doesn't seem to be any clear wording in any of the contracts to deal with case of IBM taking over another Unix licensee.

    34. Re:Thats what SCO Says but....... by AlphaSys · · Score: 1

      Right, and it has been made clear previously that NUMA, RCU were designed outside of UNIX and then implemented there, just like they were other places. So SCO has rights to those features on SCO UNIX, but that is the extent of it. Sequent (and hence IBM) retains the right to implement same wherever they see fit. If the implementation is similar, well, duhhh, LINUX is supposed to support a lot of UNIX-like stuff.

      BTW -- at some Teradata training this week, I laughed my ass off to hear the instructor talk about some older versions of their software running on AT&T SVR4 that had an implementation of a JFS type file system supplied by Veritas! The dates he gave pretty much give SCO a run for their money on originating (much less owning) a JFS on UNIX, especially considering they still distribute that file system royalty free and with no agreement with anyone to do so and have for years.

      --
      Can I bum a sig? I left mine at the office.
    35. Re:Thats what SCO Says but....... by MuParadigm · · Score: 1


      Sequent's agreement with ATT does not give the derivative works to ATT; it merely requires that Sequent treat the derivative works as it would the System V Source code. (Section 2.01, Exhibit F, on SCO's web site.)

      The question is whether that requirement to keep the code confidential, etc., is perpetual once implemented, or whether the requirement would become moot under IBM's contracts once they took over Sequent. Since ownership of the code wasn't "deeded" back to ATT, I'm guessing that Sequent's obligations under their old ATT contracts will be superceded by IBM's.

      But that is really going to be up to the judge. I don't think any of us can know for sure how that one will go, lawyer or not. But I'm not a lawyer, and it would be really nice to see the opinion of a lawyer who has also read all the documents involved.

      Also, keep in mind that their may be other documents we don't know about. Who would have guessed that Novell retained control over SCO's enforcement of the ATT contracts until that little tidbit came out in IBM's counter-claim?

    36. Re:Thats what SCO Says but....... by MuParadigm · · Score: 2, Informative


      Sequent's licenses are available at SCO's web site as Exhibits G & F.

      However, they are identical to the first two IBM licenses, Exhibits A & B at SCO's website, so if you've already seen those, then you've pretty much seen the Sequent licenses.

    37. Re:Thats what SCO Says but....... by Anonymous Coward · · Score: 0

      > The question is whether that requirement to keep the code confidential, etc., is perpetual once implemented, or whether the requirement would become moot under IBM's contracts once they took over Sequent.

      The question is neither. The question is answered in the definition of "derivative work". The contract requirement is perpetual, and the requirement would not become moot. IBM sensed the potential issue early on and asked for an "understanding" from AT&T, and got it. Such an understanding would probably apply to everyone, but particularly to any asset IBM procured later (Sequent) that was encumbered by a similar AT&T contract.

      But, Linux is not a derivative of Unix. As long as IBM/Sequent treat AIX/Dynix in the same way they would treat AT&T's original work, they are in compliance with the license. AT&T can surely demand this, as their own "original work" is under a valid copyright and would be part of any such derivative. Derivatives can only be distributed if every holder of a copyright compiled into the work agrees.

      If you asked, IBM could sell you a a license for the raw Unix V, un "AIXed". You could also buy a license for AIX/Dynix. And, you'd find, all those licenses would treat each of these products the same.

      SCO hopes (actually, it probably knows it does not), that "treatment of a derivative work" creeps into all the component works from which it is comprised. But, by every finding on the books, component works under copyright are stand alone entities.

      Note the perceived need to clarify "System V" in "...the Original [System V] Software". There really is no "Original" to a derivative work, other than the derivative work itself. All works available to copyright are "original", by law. A deriviative is a compilation of original works by two or more others. RCU is original. NUMA is original. System V is original. Linux is original.

    38. Re:Thats what SCO Says but....... by thogard · · Score: 1

      The sequent system was closer to the Unix version 10 (used in phone switches) than sys V R 1->5. SCO never got the rigths to the phone switch unix. SCO is playing stupid games with the biggest patent holders in the world. If for some strange reason SCO wins aginst IBM, IBM will simply say "ok we owe you $X billion but we would like to talk about how your going to pay for the licenses for some of our patents".

    39. Re:Thats what SCO Says but....... by Magnetic_Monopole · · Score: 1

      Considering that they 'found' the copyright transfers in the back of a filing cabinet (marked "Beware of the Tiger"), they might not want to start to question agreement amendments.

    40. Re:Thats what SCO Says but....... by pavera · · Score: 1

      The thing is this,
      Sequent developed these ideas as white papers first, as concepts and those concepts were patented. Then they implimented those concepts in dynix. Now even if SCO does own all of dynix code (which is questionable) the patents are still simply concepts, which IBM had every right to acquire, and every right to impliment on its own in subsequent systems (AIX, Linux, OS/2 if they wanted) as long as they didn't use dynix implimentation as the base and used the conceptual white papers to develop the AIX and Linux versions of the features.

    41. Re:Thats what SCO Says but....... by aflat362 · · Score: 1

      That was funny. I have mod points but can't mod you up 'cause I'm already in this thread.

      --

      Conserve Oil, Recycle, Boycott Walmart

  53. The code they talk about is ... by OMG · · Score: 1

    ... not so hard to locate now.

    Given the numbers it should be easy to prove either

    a) that there is no possible combination of the given number of files with the given number of LOC in the kernel sources

    or

    b) that a matching combination is not contributed by someone who could have had access to any information from SCO IP (which I doubt it even exists).

    Has done someone something like this before ?

  54. Other SCO news/Computer Associates Settles by Col.+Klink+(retired) · · Score: 3, Interesting
    In other SCO news, Computer Associates Agrees to a $40 Million Settlement.

    This is an unrelated case (remember, Canopy Group makes a living suing people). However, given the timing, I am now lead to believe that part of the settlement was that CA agreed to buy some of SCO's phony "Linux Licenses".

    --

    -- Don't Tase me, bro!

    1. Re:Other SCO news/Computer Associates Settles by idiotnot · · Score: 1

      I certainly didn't get the "buy licenses" part from the story.....

      The issue of the case was CA was supposed to help sell licenses and didn't.

      So, where is the evidence which leads you to believe?

    2. Re:Other SCO news/Computer Associates Settles by Col.+Klink+(retired) · · Score: 1

      > So, where is the evidence which leads you to believe?

      It's pure speculation, but consider:

      Yesterday, SCO announces a Fortune 500 bought Linux licenses.

      Today, SCO/CA announce that they have settled their outstanding dispute.

      No one can figure out who would be silly enough to buy a license to use Linux from SCO. But SCO desperately needs naive investors to think that they have some legitimate claims, and selling a license would (and did) help their stock price. So here they are in negotions with CA for a settlement. They could easily say to CA: "Since you're about to give us $40 mil anyways, why don't we say part of that is for a Linux runtime license. Doesn't cost you any more, and you won't have to deal with us again."

      --

      -- Don't Tase me, bro!

  55. inexect arithmetic by Anonymous Coward · · Score: 0
    Just to reiterate:
    approximately 148 files of direct Sequent UNIX code to the Linux 2.4 and 2.5 kernels, containing 168,276 lines of code
    How can an approximate number of files contain and exact number of lines ?
  56. morons announce termination of unprecedented evile by Anonymous Coward · · Score: 0

    's liesense to exist on yOUR planet any longer.

    that's right. those foulcurrs are about to experience a power that they have built their felonious kingdumbs, denying the existence of.

    the lights are coming up now.

    you can pretend all you want. our advise is to be as far away from the walking dead contingent as possible, when the big flash occurs. you wouldn't want to get any of that evile on you.

    as to the free unlimited energy plan, as the lights come up, more&more folks will stop being misled into sucking up more&more of the infant killing barrolls of crudeness, & learn that it's more than ok to use newclear power generated by natural (hydro, solar, etc...) methods. of course more information about not wasting anything/behaving less frivolously is bound to show up, here&there.

    cyphering how many babies it costs for a barroll of crudeness, we've decided to cut back, a lot, on wasteful things like giving monIE to felons, to help them destroy the planet/population.

    no matter. the #1 task is planet/population rescue. the lights are coming up. we're in crisis mode. you can help.

    the unlimited power (such as has never been seen before) is freely available to all, with the possible exception of the aforementioned walking dead.

    consult with/trust in yOUR creator. more breathing. vote with yOUR wallet. seek others of non-aggressive intentions/behaviours. that's the spirit, moving you.

    pay no heed/monIE to the greed/fear based walking dead.

    each harmed innocent carries with it a bad toll. it will be repaid by you/us. the Godless felons will not be available to make reparations.

    pay attention. that's definitely affordable, plus you might develop skills which could prevent you from being misled any further by phonIE ?pr? ?firm? generated misinformation.

    good work so far. there's still much to be done. see you there. tell 'em robbIE.

    the rest of the wwworld is laughing/crying at/for US in sympathy/disgust, as we fall/jump into the daze of the georgewellian corepirate nazi life0cide, whilst criticizing their ip gangsters, which are also members of the walking dead.

  57. Yeah, Right by Ed+Almos · · Score: 1

    Hmmm, let's see here

    Nine IBM servers all running AIX 24/7

    Seven IBM servers all running SuSE Linux 24/7

    A set of bogus claims from SCO that get wilder by the day.

    If the SCO Scooby gang try and take any of these babies away from me I'll see them in court.

    Ed Almos
    Budapest, Hungary

    --
    The more corrupt the state, the more numerous the laws. - Tacitus, 56-120 A.D.
  58. AIX as dangerous as Linux now by DaveInAustin · · Score: 1

    So why isn't the Gartner group warning folks to "go slow" on using AIX for mission-critical applications too? If you give SCO any credibility, then you have to believe AIX contains unauthorized SCO intellectual property too.

    --
    --- http://davidnehme.blogspot.com
    1. Re:AIX as dangerous as Linux now by Anonymous Coward · · Score: 0

      Wasn't it reported that versions of NUMA etc were reimplemented by Sequent engineers for AIX after IBM bought Sequent. While there may be a real infringement with Dynix source it won't matter if AIX source was incorporated since IBM's contract allows that. And if that's true there's no infringement and closing down the Dynix contract is unjustified.

      Would IBM have shown SCO the relevant source from either AIX or Dynix? Seems unlikely, so SCO may be guessing what happened. Can't see IBM lawyers missing something like this myself or forcing a 140+ file rewrite without good reason.

    2. Re:AIX as dangerous as Linux now by Sircus · · Score: 1

      Because IBM are indemnifying their AIX customers.

      --
      PenguiNet: the (shareware) Windows SSH client
    3. Re:AIX as dangerous as Linux now by gotr00t · · Score: 1
      It might because SCO is lacking the funds to make Gatner say what they want to say anymore.

      Either that or the fact that SCO's claims are not making sense anymore(like they ever had). Imagine all the readers of a newspaper getting sued because the publisher ALLEDGEDLY put another paper's article in it. There is a limit to how far liability goes, and it certianly does not extend down to the consumers in this case. Saying that AIX or Linux is "dangerous" to use not only makes no sense, but is just giving into the BS and unproven claims of SCO that have never been proven in a court of law.

  59. Next SCO announcement... by wcrowe · · Score: 2, Funny

    SCO announces IBM now under double-secret probation.

    --
    Proverbs 21:19
  60. Re:nothing to loose by Anonymous Coward · · Score: 0

    SCO is hopeless. They have nothing to loose.

    Darl & co. may be odious, but I'm sure they at least know the difference between the words "loose" - as in adj., slack / not tight, and "lose", as in v., to fail at a challenge or misplace an object..

  61. so when are we going to see a Single CPU distro? by rednuhter · · Score: 1

    How long before someone fudges the kernel source to just work on single processors then?
    That would sort out most home users then SCO can charge busineses liciencing to use the multi-processor code.
    'corse that still screws over the universities running clusters of quad CPU machines.

    --
    ERR 411[Max number of witty sigs reached]
  62. For them, Linux is not a problem by vrt3 · · Score: 1

    For SCO, running Linux doesn't create legal problems, not even in their own extraterrestrial view of the whole thing.

    --
    This sig under construction. Please check back later.
  63. Re:nothing to loose by Anonymous Coward · · Score: 0


    nothing to loose

    lose.. fucking retard.

  64. The stakes get higher and higher by Anonymous Coward · · Score: 0
    This game of chicken is now getting very interesting. With this latest announcement, it seems pretty clear that either there really is something to SCO's claims, or they're so far out in left field that it's time to fit them for rubber rooms and those dashing sports coats with the sleeves that meet in the back.

    Personally, I think the chance of SCO having a legitimate claim regarding at least of the code in question are about 1 in 3. But until this announcement I thought it was 1 in 10.

  65. ObAnimalHouse by red+floyd · · Score: 1

    When does SCO put IBM on "Double Secret Probation"?

    --
    The only reason we have the rights we have is that people just like us died to gain those rights. -- Cheerio Boy
    1. Re:ObAnimalHouse by Anonymous Coward · · Score: 0

      >When does SCO put IBM on "Double Secret Probation"?

      Someone needs to puke on McBride.

      Silly question: any volunteers?

  66. Appropriate quotation by Anonymous Coward · · Score: 0

    "Someone has to teach that guy (SCO) how to die."
    -Col. Jack O'Neill, Stargate Sg1, "Maternal Instinct"

  67. What's Next? by 4of12 · · Score: 2, Funny

    SCO announced late yesterday evening that all companies running Linux were dangerous felons and that SCO was in the process of filing criminal complaints against members of the board of directors for those corporations.

    Darl McBride, reached by satellite phone offshore on his recently-purchased yacht, told reporters that the whole affair,

    "It was not about Linux. It never was."

    "The reason we're taking this action is to enforce the sacred rights of intellectual property that Abraham Lincoln enjoyed and which made this country great and the envy of the free world. Those responsible are just as bad as Enron executives and should be take away publicly in shackles so justice can be served."

    "To make my point unambiguous, I'm seeking to have the State of Delaware revoke the corporate charters of these companies that continue to flout the law in the faces of hard-working American families."
    Asked to comment about SCO executives recent selling of SCO shares, McBride made staticky noises with his mouth and said:
    "You're breaking up!"

    "I have to run now to take my sick children to the hospital!"

    "Take care and God bless!"
    --
    "Provided by the management for your protection."
    1. Re:What's Next? by markhb · · Score: 2, Interesting

      I looked through the various SCO complaints at http://www.sco.com/ibmlawsuit/, and I noticed something particularly rich. If you look at the original SCO complaint, you'll notice that they twice refer to IBM as a Delaware corporation. They are not; IBM is a New York corporation (reference their latest 10-Q). They fixed it in the June amended complaint, but screwing up something as basic as the identity of your defendant is still hideously sloppy.

      Remainder of my .sig: be the majority of voters.

      --
      Save Maine's economy: write stuff down. All comments are exclusively my own, not my employer.
  68. Not the UNIX license. by wfberg · · Score: 4, Informative

    This is the license for some product called Dynix, quite distinct from IBM's AIX licensing.

    Interestingly, this contract is with Sequent, not IBM. They're now alleging that Sequent gave IBM (it's parent) the code, breaching this contract. But seeing as IBM is a different company than Sequent, surely they were not under an obligation to keep that code to themselves; Sequent fudged up by giving it to IBM, so why should IBM's license to AIX be revoked? The Sequent contract read, according to this press release, that derivative could should be treated "as if" it were UNIX code, not that it actually became the property of SCOX.

    It looks to me that the code was a trade secret at Sequent ("treaded as if..") but they retained copyright. Then it got divulged to IBM, who even obtained the copyrights, and could disperse of it as they pleased. Liability is then ristricted to Sequent's officers who breached the contract with SCOX, and perhaps some IBM officers if it can be prover they coerced Sequent. IBM's AIX license and copyrights (and thus ability to GPLize) stand, IFF this press release contains the actual facts!

    --
    SCO employee? Check out the bounty
    1. Re:Not the UNIX license. by rarose · · Score: 1

      And to the best of my knowledge IBM isn't selling any legacy Sequent NUMA-Q servers which are the only machines capable of running Dynix/ptx.

      In other words this announcement really means so so little. It's like CP/M announcing they're revocing MS-DOS's ability to duplicate their INT interfaces...

      --
      --Rob
    2. Re:Not the UNIX license. by EmagGeek · · Score: 3, Interesting

      "why should IBM's license to AIX be revoked?"

      It hasn't been. The license is perpetual and irrevokable. Barring a court order to the effect, IBM still has license to sell AIX. Darl McBride is just on crack.

      If Sequent retained the copyright to the code in question, then SCOX does not have any business suing over violation of someone else's copyrights. Either SCOX or Sequent own the copyright, but not both.

      IBM is going to squash SCOX like a little bug. I imagine that when the stock goes below $1 and is delisted, IBM will probably open up the petty cash account and make all of this go away.

    3. Re:Not the UNIX license. by pavera · · Score: 1

      Well,
      IBM bought Sequent, how is Sequent not going to "divulge" what they are doing?? IBM owns them, that would be like me buying a house and the old home owner saying, ok well here it is, but you can't use the basement, its off limits because of the terms under which we bought the house. Furthermore, IBM retains the rights to do with as they please anything with any code/process/idea that they own in connection with Unix, thus anything they obtained in the purchase of Sequent would be under IBM's license.

    4. Re:Not the UNIX license. by wfberg · · Score: 1

      IBM bought Sequent, how is Sequent not going to "divulge" what they are doing?? IBM owns them, that would be like me buying a house and the old home owner saying, ok well here it is, but you can't use the basement, its off limits because of the terms under which we bought the house.

      A house isn't a legal person. If you buy a company that has a fiduciary duty (such as a bank) or that has signed NDAs with other companies that in some way exclude you, the new owner, from access to certain secrets, you can bet your ass they are liable if they divulge those secrets.

      If you buy Boeing, they still won't tell you about their topsecret government contracts, other than if they're making a profit or not..

      Now, if Sequent had merged with IBM it would have been a different story; but in that case all its contracts would have to have been renegotiated because they would be transferred to a new entity.

      When you buy another company, certain parts of it will be useless to you. That's why you don't take it at face value, but you have to go through a process of due diligence. That's why often companies are bought for less than their stock is being traded on the market. It's like buying a house even though you know you're going to be knocking down a few walls and renovating the kitchen.

      --
      SCO employee? Check out the bounty
  69. Re:I wonder how much influence /. has on SCO stock by WCMI92 · · Score: 1

    "'I can't help but wonder how much influence Slashdot might have on SCO stock price.

    Like if Slashdot were to "accidentally" publish a story like "SCO Insider Reveals Code Copied From Linux to UnixWare!' - how much would the stock drop?"

    If investors in SCOX were reading Slashdot they wouldn't buy it in the first place....

    Most likely they are bottom-feeders who are gambling on the lawsuit as if it were a lottery.

    Anyone who loses their shirt on this stock DESERVES it to happen...

    --
    Corporatism != Free Market
  70. loFl by Ender+Ryan · · Score: 1
    So, RCU and NUMA are the infringing technologies? Ok, IBM bought Sequent, which developed both these technologies, but nevermind that for now.

    RCU and NUMA are VERY recent additions to the Linux kernel, and most machines running kernel 2.4 are NOT USING RCU AND NUMA!

    Furthermore, SCO's claim that Linux is "derivative" is completely ludicrous now, as RCU and NUMA can be removed easily, even in the 2.6 kernel. It would remove some nice features for SMP systems, but that is all, from what I understand.

    SCO's claim to ownership of those technologies is dubious at best, and I'm sure IBM will be victorious in court.

    --
    Sticking feathers up your butt does not make you a chicken - Tyler Durden
  71. This is nothing new by roystgnr · · Score: 1

    It's just the same claim they made before: that they have some sort of super-contract that transfers the copyright ownership of any code which ever gets linked to Unix code to them, whether they wrote it or not.

    They'll be putting their ass on the line by either showing any copied code that they actually own or by showing some basis for their "we own everything you wrote" claim other than a misunderstanding of what a "derivative work" is.

  72. SCO Group to Shoot Babies by mfago · · Score: 2, Funny

    In other news, SCO unveils their latest threats (found this editorial on HardOCP).

    Over-the-top? Yes...

  73. SCO markets Linux?? - Yahoo by mgessner · · Score: 1

    According to this this page at Yahoo! Financial, "The SCO Group, Inc. develops and markets software based onthe (sic) Linux operating system."

    REALLY? I thought they did UNIX!

    Doesn't this mean all of this is for nothing, if they develop and market software based on Linux?

    This implies that THEY put the contested code into Linux, and they're too stupid to know it.

    --
    "Sometimes the truth is stupid." - Lawrence, creator of Prime Intellect
  74. Errr THIS IS NEW by Quietlife2k · · Score: 1

    A lot of comments seem to think that this is a "re termination" of IBM's AIX License - accourding to the article (yes I read it) IT'S NOT ABOUT AIX This is a new allegation relating to Sequent (an IBM subsiduary). As for the RCU I *believe* IBM has this covered as the work on RCU that was donated to Linux was *NOT* from the work done at Sequent, but was from their OS/2 work on a *similar* technology. NUMA work however has not been mentioned as yet by IBM.

  75. I have a brilliant idea! by Anonymous Coward · · Score: 0

    I pull the other 4095 CPUs out my TiVO and I'm in the clear!

  76. If SCO had a case, by ihummel · · Score: 1

    wouldn't it have been incredibly stupid of IBM to have put that code in the Linux kernel, since the Linux kernel is wide opened and everyone has access to it. It doesn't make a lot of sense, unless one buys into a conspiracy theory about IBM eventually buying SCO and then trying to own Linux in the same way that SCO is now trying to own Linux, which I personally don't.

  77. It's official by ajs · · Score: 5, Insightful

    So, it's official: SCO's complaint is entirely about Sequent, and their contributions to UNIX and Linux.

    For those who don't know, Sequent was a super-computer company that developed a lot of the software techniques that make today's multi-processor machines (especially the more-than-2 processor systems) work well. Sequent's code was its own, and IBM bought Sequent, so at first glance IBM has every right to contribute this code to Linux, even though it has also been sold to USL/SCO.

    So why is SCO suing? Because they feel that this code was written "for UNIX" and thus cannot be contributed to Linux without carrying a "taint" of UNIX IP.

    SCO has made many claims about "stolen UNIX code", but that's a sham as we now see. What SCO is really upset about is that code that they think is encumbered by them, but not actually theirs was inappropriately licensed without compensation to SCO. It's not UNIX code, it's allegedly-UNIX-encumbered code, but that doesn't sound as good in a press release demanding $32 from every TiVo user....

    In fact it sounds suspiciously like a case where SCO will have to fight an up-hill battle over IP rights that aren't really clear to begin with, and even then they have to fight the GPL issue, which (given that they still offer a Linux kernel for download) will be difficult.

    SCO is going to burn over this, and I really do think that the owners and all C-level executives of the company are going to end up in jail. It's just too brazen a lie and scam to go unchecked. The FTC and SEC will at least have to launch a token investigation to demonstrate that they're not 100% asleep at the wheel...

    1. Re:It's official by panda · · Score: 4, Insightful

      SCO is going to burn over this, and I really do think that the owners and all C-level executives of the company are going to end up in jail. It's just too brazen a lie and scam to go unchecked. The FTC and SEC will at least have to launch a token investigation to demonstrate that they're not 100% asleep at the wheel...



      Yeah, sure. Just like all the executives at Enron and Worldcom went to jail after all their illegal acounting and other shady business practices. I don't think so. Your faith in the FTC and SEC makes me laugh!



      --
      Just be sure to wear the gold uniform when you beam down -- you know what happens when you wear the red one.
    2. Re:It's official by Anonymous Coward · · Score: 0
      Yeah, sure. Just like all the executives at Enron and Worldcom went to jail after all their illegal acounting and other shady business practices. I don't think so. Your faith in the FTC and SEC makes me laugh!


      What! I'm glad that they were able to get real criminals like Martha Stewart off the streets.

    3. Re:It's official by WCMI92 · · Score: 1

      "Yeah, sure. Just like all the executives at Enron and Worldcom went to jail after all their illegal acounting and other shady business practices. I don't think so. Your faith in the FTC and SEC makes me laugh!"

      Considering that, comparatively, SCO is a flyspeck of a company, and that it likely has no huge political allies (or politicos who have been "gifted" by it), they are FAR, FAR more likely to get the hammer dropped on them by the SEC, as a show that they are "serious" about this kind of thing.

      On the other hand, Boies is representing them... Boies has been a Democrat party pawn for some time, so that may suggest some political connections there...

      --
      Corporatism != Free Market
    4. Re:It's official by Anonymous Coward · · Score: 1

      They'll go to jail because Enron and Worldcom executives got away with it.

    5. Re:It's official by ajs · · Score: 1

      Just like all the executives at Enron and Worldcom went to jail

      That was very, very different. First off, it's not clear that either of those companies is as much to blame for what happened as the banks that build them out of a constant stream of loans backed by their stock which the banks' analysts were propping up.

      Second, that wasn't a case where the company was going directly to millions of consumers and saying "you owe us money for stolen property" (as they have done against TiVo owners) when a) there was no stolen property, just a dispute over licensing rights b) the dispute was far from settled, and wasn't likely to go their way c) the claims were repeatedly answered with a request for details which was denied. About the only part that's similar is the executives are using it as a chance to dump stock for profit.

      In the first case, you have a company that's inflating stock using the market against itself to make money.

      In the second you have a company that's inflating stock using fraudulent scare-tactics against millions of consumers to make money.

      I think SCO is far, far, far more deserving of some major crack-downs from the regulatory bodies.

    6. Re:It's official by Cragen · · Score: 1

      Sorry. As much as I agree with most of your post, the idea that the FTC and the SEC will "have to launch" anything is wishful thinking. (unfortunately) The probability of their investigating the SCO fiasco is directly related to total amount of the the non-Geek news coverage (which is not too good), including the possibility that certain elected officials could reap prime-time TV news coverage in the process. He11, the Law firm that advised Enron is still rated #6 in some legal industry rag. (See Washingtonpost.com 08/13/03 for further info.) I just don't think this case will really ever be big or influential enough to catch Uncle Sammy's constabularies' attention. Then, I have gone from cynical to "boo-ya". (Beliefs are just laziness.)

    7. Re:It's official by PolR · · Score: 1
      So, it's official: SCO's complaint is entirely about Sequent, and their contributions to Unix and Linux.
      I am not sure that it is entirely about that. Sequent's code is relevant to the Dynix license cancellation, but they keep changing their story. They may well complain about other portions of the code when taking future actions.
    8. Re:It's official by FatRatBastard · · Score: 1

      Boies has been a Democrat party pawn for some time, so that may suggest some political connections there...

      And if the current administration is still in power if and when this happens how happy would they be to embarrass the guy who defended Gore in Florida? In one word: VERY.

    9. Re:It's official by ajs · · Score: 1

      probability of their investigating the SCO fiasco is directly related to total amount of the the non-Geek news coverage

      Please cite a major news outlet that has not already covered this. I just read a great piece in the Wall Street Journal (print) and have seen stories on every Web site that carries a Reuters feed (that includes CNN, MSNBC, etc).

      If the SEC or FTC starts looking into it, that's when you'll see the prime-time coverage of the sort "Tonight on Local News 1, TiVo owners are being backed by the government as they investigate the claims of a Utah software company who says TiVo's "Linux" software is theirs, and users must pay them to use it! All that and the weather after these messages!"

      You may think this is geek news, but it stopped being that around when SCO started threatening joe-average who bought a high-tech toy at Circut City. If you normalize your SCO-boneheaded-move meter so that only one big mistake shows up, that would be the one.

    10. Re:It's official by Anonymous Coward · · Score: 0

      "Yeah, sure. Just like all the executives at Enron and Worldcom went to jail after all their illegal acounting and other shady business practices. I don't think so. Your faith in the FTC and SEC makes me laugh!"

      They are up on charges, but the trials aren't over yet. There is this little "due process of law" thing we have here, you know.

    11. Re:It's official by Ian+Lance+Taylor · · Score: 1

      I'm repeating myself a lot here, because people keep getting this wrong day after day.

      SCO is not trying to sell Linux licenses on the basis of the Sequent code. They are doing it on the basis of completely different code which SCO claims has been copied directly from Unix to Linux. The latter code is what SCO has been showing under NDA.

      There is the IBM lawsuit code, and there is the Linux licensing code. Two different things.

    12. Re:It's official by Anonymous Coward · · Score: 0

      SCO is going to burn over this, and I really do think that the owners and all C-level executives of the company are going to end up in jail. It's just too brazen a lie and scam to go unchecked. The FTC and SEC will at least have to launch a token investigation to demonstrate that they're not 100% asleep at the wheel...

      yeah, I saw it here the other day...
      Darl McPrisonBride!

      HAHAHAHAHAHAHHA!!!!!!!!

  78. There are NO "shady origins" by Anonymous Coward · · Score: 0
    Can't Linux developers just audit all their "critical NUMA and RCU multi-processor code", to look for shady origins? There's a big difference between the 80 lines previously claimed and the 168,000 lines now claimed!

    The NUMA and RCU code was donated by IBM. It's not "shady", it's known. The problem is SCO claims IBM didn't have the right to give its own code to them, because they claim that any code IBM wrote for UNIX after they acquired the license is SCO's.

    Doesn't make sense? It doesn't make sense to them either...like many people have already said...pump the price, dump the stock. That's what makes sense to them, but hopefully it'll make sense to the SEC as well.

  79. Matching Source code found!! by Tmack · · Score: 4, Funny
    Here are a few of those matching lines:

    printf("\nstuff");

    and

    main() {

    and

    int x,y;

    and dont forget:

    }

    Tm

    --
    Support TBI Research: http://www.raisinhope.org
    1. Re:Matching Source code found!! by Garion911 · · Score: 1

      You forgot a few: /*
      */ //

      --
      Slashdot is like Playboy: I read it for the articles
    2. Re:Matching Source code found!! by Anonymous Coward · · Score: 0, Offtopic

      PoorPost Form v. 0.1

      Your post has been moderated positively but that moderation must have been in jest or error. Your post sucks. Please review this form to understand the weaknesses in your post and how to produce higher quality posts in the future.

      [] Your post was modded funny but is not really funny. This is because:

      () You post simply used M$ instead of MS

      () You went back to beating the Windows security dead horse

      () You made a tired SCO joke

      () You made a Jon Katz joke (who?)

      () MS blowz, linux rules (or a variant)

      () You made an unoriginal joke about Slashdotting (servers turning to powder, melting, etc.)

      () Other (please comment here: )

      [] Your post is modded insightful, informative, or interesting. In fact it
      is neither of the three. This is because:

      () You stated the obvious

      () You simply tossed out lots of five-dollar words

      () It was in response to a poorly-written post or troll

      () You copied text from a previous post that really might have been one of the three I's

      () You simply criticized Microsoft without making it funny

      () It is bloated with unnecessary technical claptrap

      () All you did was pose questions (like a stoner)

      () All you did was pose questions (like a lawyer)

      [*] Your post may be rated too highly in general for the following reasons:

      () You are an asterisk who has, knowing the story's release time in advance, pounceposted to get first p0st and get modded up early

      () You are one of the editors and are getting your ass kissed

      () One of your fans has weighed in for you

      () One of the editors has blessed it with an "underrated"

      (*) You created a long, dumb ass form, showing you have nothing worthwhile to do with your life.

      [*] Additional comments:

      Go die.
      Thanks for posting! Better luck next time! :)

      ( This form is currently in alpha and probably should never be used again as it was a very stupid idea. )

  80. Curiouser and Curiouser by GearheadX · · Score: 3, Interesting

    You know. I can't help but wonder where all that stock actually WENT to when folks started to dump it. You can't exactly sell the stock to thin air, somebody's gotta buy it.

    Right?

    I wonder who bought the stock that's been selling off.

    1. Re:Curiouser and Curiouser by Wateshay · · Score: 1

      Of course somebody bought it. People competing over trying to buy the stock is what makes the price go up. If they'd had a hard time finding someone to buy their stock, the price would have gone down until someone was willing to pay the new price.

      As P.T. Barnum said, "there's a sucker born every minute" (or was it second?)

      --

      "If English was good enough for Jesus, it's good enough for everyone else."

    2. Re:Curiouser and Curiouser by bbhack · · Score: 1

      Market makers are obligated to take up slack.

      --
      The next thing to remember is to put next things next.
    3. Re:Curiouser and Curiouser by Munson+Man · · Score: 1

      and McBride is right on time

    4. Re:Curiouser and Curiouser by Anonymous Coward · · Score: 1

      > I wonder who bought the stock that's been selling off.

      Everybody who's been selling short.

    5. Re:Curiouser and Curiouser by davmct · · Score: 1

      All the people that shorted it? ;)

    6. Re:Curiouser and Curiouser by Anonymous Coward · · Score: 1, Insightful

      Alot of that stock ended up with large investment firms and is now being shorted.

    7. Re:Curiouser and Curiouser by EmagGeek · · Score: 1

      Easy - all the people who sold short when it was 15 - they love buying it back at 9 :)

    8. Re:Curiouser and Curiouser by Tsu+Dho+Nimh · · Score: 2, Insightful
      People who hope the stock will go higher buy it. Popple covering a short sale buy it.

      Right now, SCO is a day-trader's dream - few outstanding shares, very volatile, and yet affordable.

    9. Re:Curiouser and Curiouser by dead+sun · · Score: 1

      No, shorting involves selling somebody else's share with promise to rebuy it later, hopefully at a lower price. People beginning a short sale would actually increase the number of buyers needed. People finishing a short would be rebuying, but lets look at this, who's going to rebuy now when the price is up but going to crash?

      --
      If not now, when?
    10. Re:Curiouser and Curiouser by Lord_Dweomer · · Score: 1
      "Right now, SCO is a day-trader's dream - few outstanding shares, very volatile, and yet affordable."

      And very predictable, cuz when you start to see the stock price dropping, you can wait for the press release to be made shortly after, and then sell for a huge profit.

      As a side note, I wonder if anybody has made a graph correlating the date/time of the press releases to a stock chart. It'd be interesting to see if ALL of the press releases were made when their price dropped considerably.

      --
      Buy Steampunk Clothing Online!
    11. Re:Curiouser and Curiouser by Anonymous Coward · · Score: 0

      My guess is:

      Stock Shorters?

      Sold it when SCO started this nonsense and buying the cover before it implodes?

  81. Some lawyers are going to be rich by Anonymous Coward · · Score: 0

    very very rich with this case.
    They are the only winner.

  82. SCO Announces Final Termination of IBM's Licence by 010_digital_100 · · Score: 2, Funny
    SCO: I suggest you pay...
    IBM: or what...you'll release the dogs, or the bees, or the dogs with bees in their mouth, and when they bark they shoot bees at you?

    --
  83. Linux must be so bloated by Anonymous Coward · · Score: 0

    that 100,000 lines of code is just a teensy sub-system. Windows is worse perhaps. Now back in the days of GEOS you could fit a bitmapped screen, an OS and applications and user data into 64K.

    1. Re:Linux must be so bloated by Anonymous Coward · · Score: 0

      I ran GEOS on a 286 back in the day as part of my part time job at an accounting office.

      It's amazing that the GUI ever took off as well as it did considering how dog slow that POS operating environment was. I wonder how fast it would nowadays on a souped up P3..

    2. Re:Linux must be so bloated by WindowPane · · Score: 1

      Hell Yeah. I still have a couple of printouts of school reports that I did using GEOS. My first exploration into different typefaces and I'd use'm all in one document printed out on a Mannesman Tally 80 dot-matrix printer. Time for the rise of Assembler.

      --
      No Brains, No Headaches
    3. Re:Linux must be so bloated by Anonymous Coward · · Score: 0

      It ran on that fancy-schmancy intel hardware as well? I thought the original wasn't too shabby for a 1MHz 6502 and 64K of RAM.

  84. (combining stories) by 11223 · · Score: 1

    Can we test license termination and code misappropriation claims with a lie detector?

  85. Aha! Taste my Super-Final Termination Attack! by Lord+Custos · · Score: 2, Insightful

    Is it just my imagination, or is this whole mess like a bad parody of Dragonball Z?
    SCO is like Mr Satan ("Hercule") in that it is cowardly, conceited, inept and over its head. And now SCO is launching its "Satan Special Ultra Super Megaton Punch" (which is the same as an ordinary punch...just with lots of empty fanfare.)
    IBM is like Maijin Buu, and it will soon unleash its version of the Human Extinction Attack against SCO.

    1. Re:Aha! Taste my Super-Final Termination Attack! by Alan+Partridge · · Score: 1

      Only you and a load of 4 year olds watch that show, no-one else knows what you're on about.

      Sorry.

      --
      That was classic intercourse!
    2. Re:Aha! Taste my Super-Final Termination Attack! by hummassa · · Score: 1

      I wouldn't let my 4yo kid watch Dragonball... Men, I would be the target of the "human extermination" punch :-)

      --
      It's better to be the foot on the boot than the face on the pavement. ~~ tkx Kadin2048
  86. SCO is using RIAA math -- Explains all! by eddy · · Score: 4, Funny

    Maybe they're using RIAA-math? They might mean that one file is typically 50 lines, so any file with say 2000 lines counts as "the equivalent of 40 files"

    (for those who don't get it, see here)

    --
    Belief is the currency of delusion.
  87. This is a separate license by solman · · Score: 1

    IBM has two license agreements with SCO. Previously the AIX license has garnered most of the attention. Now SCO is terminating the other license, which I believe was acquired by Sequent before Sequent was acquired by IBM.

  88. linux kernel 2.6 by LocalHero · · Score: 2, Interesting

    Does that mean that we can run the 2.6 kernel without the risk of beeing sued? :).

  89. SCO Announcement ploys losing effect by TWX · · Score: 1

    As of about 8:00AM MST, SCO's stock value has reached almost what it was when they closed yesterday. Yahoo Finance has a nice graph.

    It's nice to see that their blatantly screwed up press releases aren't helping them anymore.

    --
    Do not look into laser with remaining eye.
  90. Hmmm SCOX is up and IBM is down by Anonymous Coward · · Score: 0

    Well...we know how to change that. All IBM has to do is say We are the IBM, lower your firewalls surrender your servers. You will be assimilated. Resistence is futile.

  91. Quick! by JeanBaptiste · · Score: 1

    get the SCO execs some Creatine!!!

  92. If MacBride etc start taking creatine ... by tmroyster · · Score: 1

    ... will they get any smarter?

  93. SCO Forum is CANCELED by Mansing · · Score: 1

    Posted on Yahoo! Finance

    Check out the PR. The World was not enough. Bye bye SCO Forum:

    http://ir.sco.com/Calendar-Detail.cfm?EventID=11 60 3

  94. As A Matter of Fact by RetiefUnwound · · Score: 2

    SCO execs HAVE been dumping their shares:


    SCO Senior Suits Dump Shares

    --
    "Nothing is so important that you cannot make fun of it." -Clarke
  95. My ancestor invented fire.. by packethead · · Score: 1

    So the age of fire would not have been possible. Cooked food, heat, manufacturing. The Industrial revolution, steel! Yes folks, I have rights to everything! You OWE ME!!!! Pay up now, or I will revoke your right to have ever existed this far into the future!! Pay me!! NOW!!!!!!!!!!!!!

    --
    .sig
  96. Rewrite by truthsearch · · Score: 1

    Given enough info is it worth the community's time to simply re-write those files SCO is putting to question? Rather than wait out the storm and let the image tarnish further, maybe the code in question should just be rewritten now. It would certainly be worth IBM's time to keep the same APIs and re-write the underlying code so there can be no question from anyone that it's not "stolen." IBM could then cut the argument short and say, "It's not yours, but even if it was it's rewritten now."

  97. Interesting by Anonymous Coward · · Score: 0

    If SCO claims aren't true no surprise, but if they are, IBM is guilty of putting patented material they liscensed for SCO in the Linux kernel illegally. If MS had put your Linux code in it's kernel and payed no attention to copyright or patent law the majority of you would be screaming for their head.

    Corporate Troll

    Has anyone noticed that if you don't post the OSS Linux anticorporate status quo you get modded down and labeled a troll? bet this message does!

    1. Re:Interesting by CaptTrips · · Score: 1

      CORRECTION -- Second Paragraph, Second Sentence, "The obvious answer is the market was privy to Linux." I meant to write "The obvious answer is the market WASN'T privy to Linux."

      Sorry for the confusion.

      --

      grep >= ! == $your
  98. Maybe next week... by Kanon · · Score: 1

    SCO will put IBM's Unix licence on "Double Secret Probabtion"

  99. Wall street will probably reward SCOX by Anonymous Coward · · Score: 0

    The sad part is the technically clueless that
    inhabit Wall street will probably "reward" SCOX
    for their "ballsy" move.

  100. Anyone up for a road trip? by Anonymous Coward · · Score: 0

    McBride, Darl C
    1799 Vintage Oak Lane
    HOLLADAY, UT 84121
    801-424-2006

  101. No wonder SCO didn't recognize the code by Camel+Pilot · · Score: 1

    One of the interesting issues with this case is that SCO distributed via GPL the very code they claim is their code. The obvious question that people have asked is why didn't they recognize this code in their distribution. Now i guess their defence is that they didn't recognize it because they didn't write it - IBM did.

  102. What the hell is wrong with the mods? by Anonymous Coward · · Score: 0

    This is funny, not flamebait! ;)

  103. Novel by WindBourne · · Score: 4, Interesting

    I suspect that we will hear in the next day or two, that novell files a major lawsuit and asks the courts to drop SCO's right to resell Unix.
    They have already indicated that Novell has the right to tell SCO that they can not do this action. It now becomes breach of contract unless there was some item in the contract about this.

    --
    I prefer the "u" in honour as it seems to be missing these days.
    1. Re:Novel by BiggerIsBetter · · Score: 1

      Wasn't there a post-original-agreement letter from some Novell middle-exec giving SCO clear ownership of Novell's Unix rights? I might be wrong, but I thought that was why Novell went quiet over all this.

      --
      Forget thrust, drag, lift and weight. Airplanes fly because of money.
  104. Re:contents of letter notification sent by SCO to by Anonymous Coward · · Score: 0

    SCO SEZ LEAVE B4 UR EXPUNGED

  105. Flatland by grikdog · · Score: 1

    The only serious question remaining is how rapidly SCO will enter Flatland. If it takes some time for IBM lawyers and amicus curiae to suck all the loose cash out of SCO's hyperinflated stock, the slowly spreading grease deposit should represent a high grade discovery for Flatland wildcatters. At projected velocities, however, SCO's impact will likely encounter the Flatlandish event horizon too fast to prevent useless misting over the entire basal plane.

    --
    ``Tension, apprehension & dissension have begun!'' - Duffy Wyg&, in Alfred Bester's _The Demolished Man_
  106. A bit off-topic but... by sabri · · Score: 0, Troll

    Server: Apache/1.3.14 (Unix) mod_ssl/2.7.1 OpenSSL/0.9.6 PHP/4.3.2-RC on www.sco.com. Really wonder how they can actually take themselves serious.

    --
    I'm not a complete idiot... Some parts are missing.
  107. multi processor, eh? by samhalliday · · Score: 1, Interesting

    if all the "stolen" code relates to multi-processing, then why do SCO feel they can license linux running on single processor machines?

    1. Re:multi processor, eh? by phrostie · · Score: 1

      I've been asking about that too!
      can't wait for an answer.

    2. Re:multi processor, eh? by TheShadow · · Score: 3, Interesting

      Not exactly true. They are complaining about the NUMA code. NUMA is "Non-Uniform Memory Architecture." It means that some CPUs in the system may be "further" away from certain portions of memory than other CPUs and vice versa. Most users of Linux are on SMP machines, in this case all CPUs are equally "close" to memory... so this code is irrelavent to most users.

      --

      --
      "What do you want me to do? Whack a guy? Off a guy? Whack off a guy? Cause I'm married."
    3. Re:multi processor, eh? by Phroggy · · Score: 1

      Most users of Linux are on SMP machines

      Most users of Linux who use more than one CPU you mean? I'd say most users of Linux are on single-CPU machines without SMP.

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
  108. Re:Power to the people! by Anonymous Coward · · Score: 0

    Did you pay to post that comment? Well did you? DID YOU?

    You theiving fucking commie bastard. Go shoot yourself you freeloading cum dumpster fuck.

  109. A thought by dstutz · · Score: 3, Insightful

    I don't know if anyone else has mentioned this before or even if it's possible but...
    Everyone knows that the linux sources are quite readily available to basically anyone with an internet connection. SCO Unix sources are only available from SCO, hence the need for people to go to SCO and sign the NDA if they want to see the alleged infringing code snippets. What if it's SCO that copied Linux code into their proprietary Unix and then bitched to the world that we stole from them? It's not like anyone but employees of SCO are in a position to audit THEIR code. I don't know...just my little conspiracy theory. I can't believe this has gone on as long as it has and am just waiting for SCO to crash and burn.

    1. Re:A thought by da5id+car1ad · · Score: 1

      on a side note to this, how do they prove when the code was entered? i mean it's not an all together hard thing to do to change a date here or there. i can almost see this going to court and lawyers handing over pages of code and pointing to the dates on them....... scandalous /da5id

      --
      /da5id
    2. Re:A thought by thejackol · · Score: 1

      Once they tell us what code it is they're talking about, it shouldn't be too much of a problem to go back into code and find exactly who put it in. The way they're going with the whole case, it's quite possible.

  110. Well, it makes sense by WindBourne · · Score: 1

    Otherwise, they would be running their own stuff (shudder).

    --
    I prefer the "u" in honour as it seems to be missing these days.
    1. Re:Well, it makes sense by Anonymous Coward · · Score: 0

      They still are running their own stuff.

    2. Re:Well, it makes sense by Anonymous Coward · · Score: 0

      No, they are running other ppls work and trying to take credit where not due.

  111. Press release typo by Anonymous Coward · · Score: 0

    I found a typo in the company description:

    > The SCO Group (Nasdaq: SCOX) helps millions of customers in more than 82 countries to grow their businesses everyday

    it should be

    The SCO Group (Nasdaq: SCOX) sues millions of customers in more than 82 countries to grow their businesses everyday

  112. Other options to hurt SCO by mrsev · · Score: 1

    If they think that I am going to licence my ftp server that I built from old components (P1-64Mb-30Gb HD), they must be on crack.

    One option for fighting SCO would be to swamp them.

    In my opinion every GNU/linux user should email SCO asking to buy a licence from them. Then request that the contracts and details be sent by snail mail. This will waste their time dealing with us and hopefully cause them to miss out on some poor fools who are actually trying to buy a licence.

    My 0.02EUR anyway

    1. Re:Other options to hurt SCO by micq · · Score: 1

      lol... then, when they do respond with a form license, make alterations (retyped, of course) and submit for their approval... send everything certified return reciept requested directly to their legal department...

      poor clerk...

  113. i have to interject here... by ed.han · · Score: 2, Interesting

    as a former employee in the financial services industry, linux is far from a secret. indeed, at one company that will remain nameless, 500-1000 linux servers were delivered approximately 1 year ago (more?) as part of an evaluation, not from OS/2 but from MS.

    the senior IT people really do know their stuff, at least in that firm; it just takes a while to push change of that scope.

    ed

  114. Hmmm by Anonymous Coward · · Score: 2, Interesting
    IBM is bad. They put NUMA into Linux. SGI is OK, they only put NUMA into Linux. SCO is wonderful, they provided developers with the machines and money -to- put NUMA into Linux.


    If SCO had a case, they'd be suing all those involved. Notice that they're targetting IBM, who they can likely cast in the role of the Big Bad Guy, picking on lil old SCO. They can't do that with SGI, who's not much bigger, these days.


    Also notice how they really did NOT want Red Hat involved, which is -definitely- in the realm of tiny, poor and (when they want to) are able to pull the "cute kid on the block" type pose.


    If SCO had a case, they'd be suing everyone on the NUMA development site. They aren't. They'd be suing all companies which have exported previously commercial UNIX code to Linux. They aren't.


    Ergo, SCO have no case. But the damage they can cause the industry as a whole (win or lose) could be potentially nmassive. The USAF has nothing on SCO, when it comes to collateral damage.

    1. Re:Hmmm by dr+bacardi · · Score: 1

      Actually, based on market cap, Redhat is huge compared to SCO, and even SGI (almost) doubles 'em. Granted, SCO is suing IBM for more than Redhat is worth, and you get more media from suing IBM (everybody has heard of them) vs. Redhat.

      Anyway, as of now, here are the caps:
      SCOX: 132.2M
      SGI: 214.6M
      RHAT: 1.162B
      IBM: 140.3B

  115. I posted this late last time... by Alakaboo · · Score: 4, Funny

    But maybe this time it's even more appropriate. :)

    SCOX (Lola) Song

    Enjoy...

    (To the tune of "Lola" by The Kinks)

    I met them in a club down in Santa Cruz
    where you code in C and it looks just like
    the Linux kernel... K-E-R-N Kernel

    They walked up to me and asked me to desist
    I asked them their name and in a cowardly voice they said,
    "SCOX"... S-C-O-X SCOX, sco sco sco sco-X

    Well I'm not the world's most intelligent guy
    But when they showed me the code I almost cried
    Oh my SCOX, sco sco sco sco-X

    Well I'm not dumb but I can't understand
    How they stay in business with blood on their hands
    Oh my SCOX, sco sco sco sco-X

    Well they filed their claims and sued all night,
    thanks to Microsoft's failing might
    They picked me up and sat me on their knees
    Saying, "Linux coder won't you turn and flee?"

    Well I'm not the world's most logical guy
    And when I looked at the comments
    I almost fell for their bullshit
    bull bull bull bull-shit

    sco sco sco sco sco-X

    I laughed them away. I walked to the court.
    I filed a countersuit. They'll be down on their knees.
    Now that IBM is looking out for me

    And that's the way that I want it to be
    They'll clean them out and make them pay
    Oh my SCOX, sco sco sco sco-X

    Linux will be UNIX, and UNIX will be Linux
    It's a scratched-out, messed-up, crazy diagram
    thanks to SCOX. sco sco sco sco-X

    Well I posted to LKML just a week before
    saying I never ever leaked code before
    SCOX smiled and said "We understand,"
    saying, "Linux coder, you can do what you can"

    Well I'm not the world's most open source guy
    but I know Richard Stallman and I bet that they'll fry
    oh my SCOX, sco sco sco sco sco-X

    sco sco sco sco-X

  116. Re:web server running IIS? Does anyone know... by Anonymous Coward · · Score: 0

    If they patched their WebDav vulnerability?

  117. What about the GPL? by Anonymous Coward · · Score: 0

    If I license a GPLed software application and make modifications to it, all rights to those modifications revert to the GPL if I choose to distribute the changes.

    If the SCO/IBM license is not binding, then how in the hell would the GPL (or any other software license) be binding?

    1. Re:What about the GPL? by Wateshay · · Score: 1

      Those modifications only revert to GPL in the context of being additions to the GPLed application. Your code still belongs to you, and you're welcome to put the code you wrote into a closed source application, too.

      --

      "If English was good enough for Jesus, it's good enough for everyone else."

    2. Re:What about the GPL? by Anonymous Coward · · Score: 0

      "In the context of being additions..." to the Unix source that IBM licensed from SCO.

  118. Wait it gets better by kaltekar · · Score: 1

    SCO is sending out Invoices to commercial Linux users. Seems that asking wasn't enough. See
    http://www.zdnet.com.au/newstech/os/story/0,2 00004 8630,20277173,00.htm

    --
    Ahh.. The mind what a wonderful trap!
  119. SCO might have a case here by Teahouse · · Score: 2, Interesting

    The AIX suit is lame and they will lose. The sequent thing is entirely different. Sequent had a limited licence that clearly states they can't put the nUMA technology into the public realm. This is the first time I have seen SCO actually have a case in their legal argument. The question is how will this affect Linux? Can NUMA be done while working around the SCO IP?

    --
    "Curiosity killed the cat, but for a while I was a suspect."- Steven Wright
  120. Plausible candidate for `infringing' file by hak+hak · · Score: 1

    I grepped for `RCU' in the Linux source (2.6.0-test3), and one particularly `suspected' file is kernel/rcupdate.c, written in 2001 by an IBM employee and copyrighted by IBM. The copyright notice also says it is based on previous work by another IBM employee. There are 45 files in total containing `RCU'. (Haven't tried `rcu', `NUMA', or `numa' yet.)

  121. Triple Top Secret Termination! by HydraSwitch · · Score: 1

    Sorry, but I really can't take this seriously until it reaches the triple termination point.

  122. Linux is worth $79,000 by Sgt+York · · Score: 2, Interesting
    Let's see....148 lines of IP in 168,276 lines of code is ~0.088% of the code. SCO says their contribution is worth 699 / CPU / distro. So....699/0.00088 = $79,000.

    I am currently using the most valuable peice of software I have ever seen....cool. I'm rich.

    --

    There is a reason for everything. Sometimes that reason just sucks.

    1. Re:Linux is worth $79,000 by UTPinky · · Score: 1

      Re-read the press release again. They're claiming that its 148 files and 168,276 lines of code. Not 148 out of 168,276 lines of code

      --
      I'm only paranoid because everyone is against me...
    2. Re:Linux is worth $79,000 by BigGar' · · Score: 1

      You misread, actually its the:
      set of "stolen code" figures in the release - 'approximately 148 files of direct Sequent UNIX code to the Linux 2.4 and 2.5 kernels, containing 168,276 lines of code.

      They are saying that all 168,276 lines of code is infringing.

      --


      Shop smart, Shop S-Mart.
    3. Re:Linux is worth $79,000 by nbahi15 · · Score: 1

      Both of you reread the article and get back to me. I need the report of SCO infringing code by COB today.

    4. Re:Linux is worth $79,000 by Sgt+York · · Score: 2, Funny
      That'll teach me to RTFA before I try to be funny.

      Ah, who am I kidding. This is slashdot.

      --

      There is a reason for everything. Sometimes that reason just sucks.

  123. I wish SCO would explain.... by lynx_user_abroad · · Score: 1
    So how exactly does one go about submitting SysV code into the Linux source tree? I thought they only accepted Linux code there?

    And in the same vein, does that mean every printf ("Hello World!"); now belongs to SCO?

    Somebody please explain?

    --

    The thing about things we don't know is we often don't know we don't know them.

  124. Troubling moves by SCO.... by CooCooCaChoo · · Score: 5, Insightful

    Having followed this issue, it seems rather funny that that this whole rampage against the GPL and other opensource licenses was first started by Ransom Love.

    When McBride came onto the scene he started to talking about IP issues. I have no issues with a company setting out to see their IP is being used and whether the parties that are using it have paid the appropriate licenses for it.

    Lets fast forward a little. SCO suddenly kills off their Linux business and throws all their programmers to SuSE so basically SCO simply becomes a reseller. Considering that they have made no profits so far from Linux and have almost a 0% marketshare, maybe their last resort is hair spliting.

    Over the next several months the accusations have moved from being IP vioations to contractural issues.

    Lets give a brief rewind, the last version of SCO Linux to be released before Ransom Love left was Caldera OpenLinux 3.1.1 and it was loaded with 2.4.13. Having the RCU code in the Linux kernel since the VERY early test releases, and it has taken almost 21 releases, around 2 years for SCO to come out of the wood works and complain.

    Here is my take, when Ransom Love was in "their" they most likely looked at the possibility of litigation, however, due to a gray area in the IBM contract Love most likely decided not to persue a dead end law suite.

    Fast forward to today and we have a new management trying their luck in a vein hope of sucking money out of IBM to prop up their failing business.

    Sorry, UnixWare and OpenServer failed because they "suck". Sorry, I can't come up with a better adjective for their current line up. Poor scalability, waaaaaay over priced, heck, it makes Microsoft look charietable with their license pricing and they have next to no ISV and IHV support. No wonder SCO is dying.

    --

    "The difference between pornography and erotica is the lighting" - Woody Allen

    1. Re:Troubling moves by SCO.... by Kismet · · Score: 1

      When Ransom was the new CEO of SCO, he was full of Open Source ideology.

      In those days, SCO was asked about moving Unix IP into Linux. Ransom said they were doing their best to "open up" the Unix technologies, but that a lot of things belonged to 3rd parties, and SCO didn't have the rights to them. See this article.

      Then we have Ransom's LinuxWorld 2001 keynote where he discusses SCO's role in helping IBM get enterprise features into Linux. One of his statements went as follows: "But clearly we are going to add components back to the Linux kernel on both IA-32 and IA-64 platforms". This was during the whole Monterey project as I recall.

      So if you look at SCO in this context, you get the idea that they knew very much what was going on, that they sanctioned it, and that they probably even helped expedite it. It doesn't make sense for Ransom to start raising IP questions when he has made statements about SCO's support of Enterprise Unix features in Linux.

    2. Re:Troubling moves by SCO.... by i_r_sensitive · · Score: 2, Funny

      Sorry, UnixWare and OpenServer failed because they "suck". Sorry, I can't come up with a better adjective for their current line up. Poor scalability, waaaaaay over priced, heck, it makes Microsoft look charietable with their license pricing and they have next to no ISV and IHV support. No wonder SCO is dying. Hear, hear! I remember my first Linux installation... I got a set of Slackware CDs from the MIS, a sort of joke gift he thought. I retired to my lab and immediately scavenged some hardware to give it a shot. Gods! I was impressed. After a few hours poking around here and there my first considered reaction was: 'This thing is a UNIX-killer.' At the time I was an SE/FE in an SCO-shop, back in the 3.2r4.2 days... In every way, even then (late '93 or early '94, there was snow, that's about all I remember...) that Slackware box was a breath of fresh air. The supported hardware was good, covering a reasonable cross section of common to high end parts 'n' peripherals, certainly more extensive than SCO. And the hits kept coming, networking included, at no added cost, several compilers, also at no added cost. A mind-boggling array of software, almost too much. Within a week I had that little puppy, built out of spare parts humming along-side the production servers. That box eventually housed the company's first permanent internet connection, and matured into their first proxy/firewall. Over the years I've used many Linux distributions, and have had the unfortunate responsibility of assessing follow offerings from SCO. Each and every time I would select another distro and compare the two. Consistently I found myself disappointed with the SCO offerings. Now, almost ten years later, there are still a few SCO machines around, clustered in a little corner of the server closet, under the Caldera VSP certificate and stuffed Tux holding a sign which reads: ABANDON HOPE, ALL YE WHO LOG ON HERE!

      --
      "Talk minus action equals nothing" - Joey Shithead, D.O.A.
      "Talk minus action equals /." -
    3. Re:Troubling moves by SCO.... by CooCooCaChoo · · Score: 1

      I guess you fail to remember the anti-GPL tirade he went on when they released OpenLinux 3 which had a per-seat licensing policy.

      Over the next couple of weeks he promoted the BSD license over GPL and claimed that the GPL was bad for business.

      The question I want to know is why SCO/Caldera just simply use the BSD license. Had they simply started to use another license the whole issue would have been a footnote to a footnote.

      Ultimately SCO/Caldera failed because they failed to utilise the investments they made into their own product and what made it worse they didn't make the issue any easier by simply isolating themselves from the opensource community by failing to contribute and enhace the opensource software they used in their one products.

      Compare what SCO/Caldera did to KDE vs the effort and time Redhat, SuSE and Mandrake put into their distribution both from a visual (GUI) point of view and support (both software support and third party package availability).

      SCO/Caldera dug their own hole and now they are looking for a scape goat for their bad management practices. IBM being the biggest cash cow and Linux proponent was/is the perfect target.

      --

      "The difference between pornography and erotica is the lighting" - Woody Allen

  125. Management of SCO has already won by Anonymous Coward · · Score: 1, Insightful

    The annoying part of this whole business is the fact that no matter the outcome of any of the lawsuits SCO has hardly any money in capital so there is nothing there to get. Sure, if IBM or Red Hat win their respective law suits, they can suck each last penny from them [SCO]. Unfortunately, this will never compensate for the shadow that was cast on Linux at the moment of its uprise. So basically the guys already have their money gained from stocks, and now nothing more to lose.

  126. License Termination for 1's and 0's by hampton2600 · · Score: 1

    I would like to make it officially known that some code that I wrote in 1985, as a small child, contained some intellectual property known as "0" and "1". The code I own contains this code and therefore, I am calling for a halt of all things digital. Thank you. -The Hampton2600.com Legal Team

    --
    "I don't want to start a holy war here..."
  127. Actual transcript smuggled out of the courthouse by paiute · · Score: 5, Funny

    SCO-None shall compile.
    IBM-What?
    SCO-None shall compile.
    IBM-I have no quarrel with you, brave SCO, but I must distribute UNIX.
    SCO-Then you shall be sued.
    IBM-I command you to stand aside.
    SCO-I move for no corporation.
    IBM-So be it!
    IBM draws his sword and approaches the SCO. A furious fight now starts lasting about fifteen seconds at which point IBM delivers a mighty blow which completely severs the SCO's left
    arm at the shoulder. IBM steps back triumphantly.
    IBM-Now stand aside worthy adversary.
    SCO-(glancing at his shoulder)
    'Tis but a scratch.
    IBM-A scratch? Your arm's off.
    SCO-No, it isn't.
    IBM-(pointing to the arm on ground)
    Well, what's that then?
    SCO-I've had worse.
    IBM-You're a liar.
    SCO-Come on you pansy!
    Another ten seconds furious fighting till IBM chops the SCO's other arm off, also at the shoulder. The arm plus sword, lies on the ground.
    IBM-Victory is mine.
    (sinking to his knees)
    I thank thee O Lord that in thy...
    SCO-Come on then.
    IBM-What?
    He kicks IBM hard on the side of the helmet. IBM gets up still holding his sword. The SCO comes after him kicking.
    IBM-You are indeed brave SCO, but the fight is mine.
    SCO-Had enough?
    IBM-You stupid bastard. You haven't got any arms left.
    SCO-Course I have.
    IBM-Look!
    SCO-What! Just a flesh wound.
    (kicks IBM)
    IBM-Stop that.
    SCO-(kicking him)
    Had enough?
    IBM-I'll have your leg.
    He is kicked.
    IBM-Right!
    The SCO kicks him again and IBM chops his leg off. The SCO keeps his balance with difficulty.
    SCO-I'll do you for that.
    IBM-You'll what... ?
    SCO-Come Here.
    IBM-What are you going to do. bleed on me?
    SCO-I'm invincible!
    IBM-You're a loony.
    SCO-SCO always triumphs. Have at you!
    IBM takes his last leg off. The SCO's body lands upright.
    SCO-All right, we'll call it a draw.

    --
    If Slashdot were chemistry it would look like this:Cadaverine
  128. Proprietary Code Snippet...? by pragma_x · · Score: 5, Funny

    #include "fud.h"
    #include "enron.h"

    void SCO_keep_alive()
    {
    while(!inCourt()){
    try{
    generateFUD();
    extortLicensesFromLinuxUsers();
    }
    catch(ImpendingIBMSuit suit)
    {
    int numShares = MAX_INT;
    dumpStock(numShares);
    terminateLicense("IBM");
    }
    }
    fileChapter(11);
    }

    1. Re:Proprietary Code Snippet...? by Anonymous Coward · · Score: 0

      #include "fud.h"
      #include "enron.h"

      void SCO_keep_alive()
      {
      while(!inCourt());
      {
      try{
      generateFUD();
      extortLicensesFromLinuxUsers();
      }
      catch(ImpendingIBMSuit suit);
      {
      int numShares = MAX_INT;
      dumpStock(numShares);
      terminateLicense("IBM");
      }
      }
      fileChapter(11);
      }

      watch your syntax errors u baffoon, apparently i need less whitespace, how annoying, well at least i didnt get my code wrong, you fool

    2. Re:Proprietary Code Snippet...? by msgmonkey · · Score: 1

      C++ code in the linux kernel?!? heracy I say!

    3. Re:Proprietary Code Snippet...? by Anonymous Coward · · Score: 0

      You forgot:

      #include "martha_stewart.h"

    4. Re:Proprietary Code Snippet...? by jdennett · · Score: 1

      Now, c'mon, how did that get past pedants code review? So, catch by const reference, make numShares const if it's not going to change, and use std::numeric_limits::max() instead of INT_MAX, to please the anti-preprocessor crowd. Thanks.

    5. Re:Proprietary Code Snippet...? by Anonymous Coward · · Score: 0

      --------------------Configuration: pragma_x - Win32 Debug--------------------

      Compiling...

      pragma.cpp

      u:\pragma_x\pragma.cpp(1) : fatal error C1083: Cannot open include file: 'fud.h': No such file or directory
      Error executing cl.exe.

      pragma_x.exe - 1 error(s), 0 warning(s)



      Dang, I was hoping to earn some money this way....

  129. bluff much? by FuzzyBad-Mofo · · Score: 1

    Don't forget about the Double Secret license termination notice!

  130. SCO's strategy by xyote · · Score: 1

    I believe SCO's real strategy is to appear more stupid than they really are in order to provoke an irrational reaction from the Linux community. After all, if they behaved in a reasonable manner and identified the code in breach of their copyright, Linux developers would just rewrite the offending code and that would be the end of it as far as Linux is concerned. And all SCO would be left with would be to sue a corporation much larger then they are. There must be a method to their madness.

  131. The question I haven't seen asked by ...+James+... · · Score: 1

    So what happens if SCO has a legitimate claim and IBM really did steal some code? What happens?

    1. Re:The question I haven't seen asked by Anonymous Coward · · Score: 0

      Easy. The kernel team rewrites the "violating" code and releases a SCO-free version.

    2. Re:The question I haven't seen asked by smash · · Score: 1
      IBM sues SCO for patent infringement and breach of the GPL.

      Because they're still selling Openserver, etc after IBM has lodged their countersuit, the patent infringments may carry punitive damages (triple).

      IANAL, etc - just what I interpreted from IBM's counterclaim document...

      smash.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  132. percentage of kernel code... by capsteve · · Score: 1

    i can't be sure of the exact figures, but the 2.4 kernel is just a little over 3 million lines of code(2.2 was 1.7 million lines). SCO claims 'approximately 148 files of direct Sequent UNIX code to the Linux 2.4 and 2.5 kernels, containing 168,276 lines of code' we're talking about 5% of code (could be less if comments are stripped out?). i think once this gets to court, the argument is going to end up boiling down to fair usage...

    IANAL, but as i understand it, legally there is no set percentage or figure for what is considered fair usage.

    --
    three can keep a secret, if two are dead - benjamin franklin
  133. 168276 lines of code? Let's see them!!! by swordgeek · · Score: 2, Interesting

    OK, I've tried to understand SCO's requirement for signing an NDA. Normally this makes sense for companies revealing proprietary code.

    But the whole basis of this case is taht the code has been improperly released to the public! If SCO is telling the truth (HAH!), then we ALREADY HAVE THE CODE they're contesting! Take your code to court, get a sworn and signed affidavit that the code you're showing is unaltered, from before IBM released these suspicious lines, and then SHOW IT TO US!

    Of course a few weeks ago, McBride declared that they couldn't reveal which bits of the Linux code infringed, because then the coders would just go and fix it. If they refuse to allow this to take place, then I'd say they're not quite bargaining in good faith.

    --

    "People who do stupid things with hazardous materials often die." -- Jim Davidson on alt.folklore.urban
    1. Re:168276 lines of code? Let's see them!!! by Anonymous Coward · · Score: 0

      In answer to your topic, the 168,276 lines of code happen to be all CR's when some coder fell asleep (lack of Mtn. Dew/Bawls/etc) on the keyboard and the EOF got pushed waaaaaaaaaaaaaaaay down to the end....

    2. Re:168276 lines of code? Let's see them!!! by mark-t · · Score: 1
      McBride declared that they couldn't reveal which bits of the Linux code infringed, because then the coders would just go and fix it
      There are several responses to this:
      1. Supposedly, even if the code was changed, the developers who changed it would have been "tainted", so wouldn't SCO still own the code on that basis?
      2. SCO alleges that it would not have been possible for Linux to have reached its current status without stealing SCO's IP, but if the code could be so easily changed, it's obviously not that critical to the functioning of Linux. How, by any sense, could something so easily changed be worth 3 billion dollars? (Here's a clue, SCO... the reason it hasn't been changed already isn't because your code is so valuable, it's because those that could change it don't know exactly which lines you're talking about)
      3. Even if the code were changed before the court date, IBM would still be liable for damages caused due to breach of contract, if such a breach ever occurred. The amount of these damages cannot reasonably be presumed to be less simply because the so-called infringing lines were replaced in short order because of the legally pressing demands to replace those lines in the first place.
      Assuming SCO actually has a real case (and I don't think they do... this has looked like a stock scam almost from day one), whatever amount that SCO was actually eligible to collect on the date that they first announced the problem was the maximum that they could have possibly claimed for this case. SCO has abysmally failed to future mitigate damages, which will probably reduce the amount they can get. They're reasoning for failing to mitigate is rationally flawed, and that presents a another major blow to their case, further reducing the amount they will be able to get.
  134. Re:McBride? McBriii-ide? Hello? by tcopeland · · Score: 1

    > Look, your stock's down

    The stock price for today is interesting. Up a bit initially, then back down as the excitement fades.

    Begone, SCO!

  135. Should have checked this before... by ickle_matt · · Score: 1


    How many lines of code are there in the Linux kernel? Don't have sources to hand at the moment, but I'd wager that 168,000 lines may actually be greater than the total size...

  136. NUMA and RCU? Then why... by arth1 · · Score: 5, Insightful

    With the code being NUMA and multi-processor patents, then why does SCO claim a hefty license fee for *single CPU* linux installations?

    It's part of the kernel that you can't even use if you wanted on a single-CPU box!
    So what's the fee for, again?

    Regards,
    --
    *Art

  137. More than you might think by llywrch · · Score: 1
    The other day someone posted to /. that the SCO Group told him they were no longer selling licenses to use Linux.

    It was quickly repeated on other Linux news sites, & made The Inquirer. The SCO Group had to spend time fighting that false report.

    (For the record, I suspect what happened was that the original poster accidentally dialed the wrong number, had not been the first to misdial that number, & the person who answered had decided to play a prank.)

    Geoff

    --
    I think I see a trend here. Maybe for them it really would be easier to muzzle the entire internet than to produce p
  138. Dead Stock Walking! by Tsu+Dho+Nimh · · Score: 1

    If IBM didn't believe them the first time and specifically denied it in their reply, and Novell told them they have no right to do it, why does SCO think repeating the same allegations in another press release make it any better.

    Apparently the stock needs another shot in the arm to keep the dead stock walking until the insiders can dump enough options to make it all worthwhile.

  139. Count lines by perbu · · Score: 2, Interesting
    Wow. ~169 000 lines of code. If you subtract drivers, network and filsystmens from the Linux Kernel (2.4.20) you end up with approx. 35 000 lines of code.

    Can anyone tell med where the rest is? Is there really so much NUMA-code in Linux 2.6?

    1. Re:Count lines by babyrat · · Score: 1

      Wasn't JFS one of the original technologies that SCO mentioned was in question? Better put back the filesystem source and do a recount.

  140. ay it ain't so! by 110100 · · Score: 1
    Sequent-IBM has also contributed significant UNIX-based development methods to Linux in addition to the direct lines of code specified above.

    Please send me $699 if you would like to continue using my fork-and-knife-based eating methods.
    --

    I have never regretted my speech,
    but I have frequently regretted my failure to speak.
  141. SCO and RIAA! by Anonymous Coward · · Score: 0

    I think SCO and the RIAA should join forces, just think of it, all they do is claim they own everything and sue everyone...what a business model.

  142. Can't seem to find it by Anonymous Coward · · Score: 3, Informative

    Looking though the 2.4.21 sources it looks like RCU isn't even merged into the mainline kernel yet. As for NUMA, it effects all of about 20 files. So can somebody tell me where the hell SCO is finding 148 files of copied code!?! Hell, the core code in ipc, mm, and kernel is only 58 files.

    1. Re:Can't seem to find it by ratfynk · · Score: 1

      It could be that the IBM 390 smp code is what they are talking about. The linux-2.4.20/arch/s390x /kernel/smp.c to be specific. It is interesting that the final static_void seems to point to the future of non smp where individual addressed processors can have different memory timing values. Perhaps they tried non symetrical but found that the addressing and timing became to difficult. Reading the comments is fascinating. It remains to be seen where SCO is really talking about but I have the feeling that the smp code for IBM processors was the first place to look. The RCU and Numa might be just to throw Linus off track.

      --
      OH THE SHAME I fell off the wagon and use sigs again!
    2. Re:Can't seem to find it by what+the+dumple+is · · Score: 1

      If that were the case then why would they send threatening letters to those who have compiled Linux on x86 and alpha? Also--there's no mention of sequent or anything here and the comments indicate that the work is based on...

      /*
      * arch/s390/kernel/smp.c
      *
      * S390 version
      * Copyright (C) 1999,2000 IBM Deutschland Entwicklung GmbH, IBM Corporation
      * Author(s): Denis Joseph Barrow (djbarrow@de.ibm.com,barrow_dj@yahoo.com),
      * Martin Schwidefsky (schwidefsky@de.ibm.com)
      *
      * based on other smp stuff by
      * (c) 1995 Alan Cox, CymruNET Ltd <alan@cymru.net>
      * (c) 1998 Ingo Molnar

      I believe stuff must be some sort of technical term. Better question...why do they keep changing their story with each press release? Who will be the Mark Furhman of this case? Will the glove fit?????

      Holy FUD, Batman! Tune in next week^H^H^H^H^H^H^H^H^Htomorrow. Same SCO time. Same SCO channel.

  143. They were just too greedy by ansible · · Score: 1

    You know, what's really going to lose the case for SCO is that they just got too greedy.

    If they had stopped distributing in any fashion Linux on the day they announced the lawsuit, they might have still had a chance.

    But since they are continuing to distribute Linux through their website, they have done nothing to curb infringement of their "valuable IP".

    I guess they couldn't live without those support contracts for Linux they had already signed. There's smart greedy, and dumb greedy. And so a few hundred thousand dollars will now cost them 3 billion (potentially). Dumb, dumb, Dumb.

  144. Has SCOForum been canceled by isn't+my+name · · Score: 1

    Is it Autumn in August?

    A post on the Yahoo SCOX board points to this note on the SCO website regarding SCO Forum that says it is postponed until Autumn 2003.

    Is this an old note and do they think August is Autumn or is this the first clue that they are postponing it until later?

  145. Wait a minute - IBM now owns Sequent by Anonymous Coward · · Score: 3, Interesting

    As a former Sequent employee, my recollection is that IBM, SCO, and Sequent entered into a joint development for NUMA optimizations for UNIX. I can't believe that:

    1) IBM doesn't have rights to that
    2) IBM bought Sequent but didn't buy their code

    SCO's actions get weirder all the time!

  146. Who has the most to gain? by Anonymous Coward · · Score: 0

    Has anyone asked the question who has the most to gain from the legal proceedings (besides the lawyers?) I am not into conspiracy theories as a rule, but it seems to me, that Microsoft may have a lot to gain from turmoil in the Linux world...

    Just a thought....

  147. We need an Ask Slashdot for the SEC by unsinged+int · · Score: 1

    Really. I bet we could think of some great questions. They obviously couldn't comment directly on SCO, but answers to general questions like "how seriously do you take email from random people suggesting you investigate a company" would be interesting.

  148. NUMA from SCO my ass by Anonymous Coward · · Score: 5, Informative

    mm/numa.c:
    /*
    * Written by Kanoj Sarcar, SGI, Aug 1999
    */

    arch/x86_64/mm/numa.c:
    /*
    * Generic VM initialization for x86-64 NUMA setups.
    * Copyright 2002 Andi Kleen, SuSE Labs.
    * $Id: numa.c,v 1.6 2003/04/03 12:28:08 ak Exp $
    */

    /*
    * linux/arch/alpha/mm/numa.c
    *
    * DISCONTIGMEM NUMA alpha support.
    *
    * Copyright (C) 2001 Andrea Arcangeli <andrea@suse.de> SuSE
    */

  149. No it's not. by eddy · · Score: 1

    You know, FUD isn't okay just because it works in your "direction".

    Yes, the note is misspelled, but it does say Autumn 2003, no? Well, in my part of the world, that's now.

    --
    Belief is the currency of delusion.
  150. What I wanna know... by Anonymous Coward · · Score: 0

    SCO 'terminates' IBM's license to Unix. However, according to Novell, SCO doesn't have the right to terminate IBM's license.

    Novell informed SCO that it had no rights to terminate IBM's license but SCO does it anyway. Would this put SCO in breach of contract with Novell? Obviously I've never read the SCO/Novell agreement but it would certainly be interesting if SCO has breached contract. And its implications would be even more interesting.

    You think you're tired of SCO??? Some of my extended family works for SCO and some of us are ardent linux advocates. When my family gets to gether, we don't fight about religion or politics, we have OS holy wars!

  151. "UNIX-based development methods" by Overt+Coward · · Score: 3, Insightful

    "UNIX-based development methods" -- huh? What exactly are these "methods", and under what terms does SCO claim to have ownership of such "methods"? What part of IBM's contract held by SCO licenses these "methods" and restricts their use?

  152. Did anyone notice... by HuffMeister · · Score: 3, Interesting

    That SCO's tune has changed about the AIX license: It says at the bottom of the press release that no one can acquire NEW AIX licenses. IIRC, at the time of the last BSA (Big SCO Announcment) the claim was that all AIX licneses were null and void and nobody had a right to be running SCO... Isn't that odd? I wonder if IBM's lawyers will brow-beat SCO's lawyers with that piece of McBridian Megalomania...

    1. Re:Did anyone notice... by frkiii · · Score: 1

      Yeah, it's like: At first... SCO: You, your customers, their familes, dogs, relatives of any sort, friends, political representatives and their mistresses, etc., can no longer use software that we own.... And now... SCO: Well, sorry (cringes), I meant that only you can't do anything with software we own, even though we don't really own it. And we really mean it this time, you are in big trouble mister! (Places hands on hips and glares threateningly.) SCO's antics are at least entertaining, make me laugh. They should get a new mascot "SCOzo the Clown". The mock up of Darl as Ronald McDonald could be a start, using SCO's corporate colors, cept with a big red and white bullseye target on his butt with a sign on his back saying "Kick me!" Regards, Fredrick

  153. Sleeping Giant by earthforce_1 · · Score: 4, Insightful



    "I fear that we have awakened a sleeping giant
    and filled him with a terrible resolve"

    Admiral Isoroku Yamamoto
    December 7th, 1941

    Anybody not see the parallels? SCO has launched an unprovoked sneak attach against the sleeping giant, (IBM) and the Linux community. And this war will end the same way, with the legal equivalent of an atomic bomb delivered to SCO.

    --
    My rights don't need management.
    1. Re:Sleeping Giant by Anonymous Coward · · Score: 0

      Not to mention that SCO has ties to al Qeida and that this lawsuit is funded by a joint effort between Saddam and Bin Laden.

      I say we carpet bomb SCO's HQs and look for WMDs.

    2. Re:Sleeping Giant by Anonymous Coward · · Score: 0

      Now that's funny. Sorry I can't mod you up.

    3. Re:Sleeping Giant by Anonymous Coward · · Score: 0

      SCO doesn't care if they get wiped out. They (execs and owners) are making more money dumping stock than they would ever have made as a software company. They are just cashing out.

    4. Re:Sleeping Giant by scalis · · Score: 1

      But still, David beat Goliath with a small rock.

      --

      True ravers don't need drugs
    5. Re:Sleeping Giant by Anonymous Coward · · Score: 0
      Yeah, but David had God on his side.


      Somehow I don't think that applies here...

    6. Re:Sleeping Giant by smash · · Score: 1
      Anybody not see the parallels? SCO has launched an unprovoked sneak attach against the sleeping giant, (IBM) and the Linux community. And this war will end the same way, with the legal equivalent of an atomic bomb delivered to SCO.
      Yep, and I've actually been using the words "Sleeping giant" in my SCO discussions with friends ;)

      There are certain companies you just DON'T fuck with, unless you're one of the other companies in that league.

      IBM, Microsoft, and Sony are 3 of those companies...

      smash.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  154. Almost certainly not. by eddy · · Score: 1

    Yes, surprise, people don't go strictly by the meteorological definitions in such matters as where the seasons start and end.

    --
    Belief is the currency of delusion.
  155. Linux's Future After SCO by wthynot · · Score: 4, Insightful

    I believe Linux adoption will skyrocket immediately after SCO's case finally dies (along with SCO itself). Linux has already been well-proven technically, but success in the courtroom gives an impression of corporate backing and strength, and more will look at Linux as terra firm. And the bigger SCO's claims get, the stronger Linux will look after a victory. Even average home users often decide what tech products they will buy based on which companies/brands will likely be around for a while, and they are probably least likely to pick a cheapie newcomer just for cost's sake. (Yes, Linux is 10+ years old, but you know what I mean.) Eh well, another $.02US gone...

  156. Not SCO's, was Re:web server running IIS? by bourne · · Score: 1

    ir.sco.com is running IIS.

    But that's not a SCO host, that's shareholder.com:

    $ host ir.sco.com
    ir.sco.com. is an alias for cald.client.shareholder.com.
    cald.client.sharehol der.com. is an alias for client.shareholder.com.
    client.shareholder.com. has address 170.224.5.43

    It is very common for the entire IR site to be handled by an external Investor Relations firm like shareholder.com. That way they can manage simultaneous release of press releases by fax, conference, and web without having to coordinate with the true company's admin monkeys.

  157. SCO fits into the Black Knight of MP's Holy Grail by GReaToaK_2000 · · Score: 1

    Tonight the part of the Black Kniggit will be played by SCO and the Part of King Arthur will be played by IBM, Red Hat and just about everyone else in the linux community... :)

  158. ....sound of your death. Good bye, Mr. McBride. by roman_mir · · Score: 1


    My name.... is SCO!

    bang, bang.

    Ooh, sorry..... wrong movie!

  159. Sounds like the scene from A Few Good Men by pfleming · · Score: 1

    Outside the courtroom Weinberg: "What was that in there? 'Your honor, I object.' 'Overruled' 'I strenuously object' 'Oh, in that case, sustained' It doesn't work like that..."

  160. These files are extremely well known... by Kjella · · Score: 2, Insightful

    After all, IBM commited those patches under no form of secrecy, and it was no secret either that they were based on Sequent code. Makes you wonder why they needed the smokescreen NDA and FUD-spewing huh? Everybody that signed it and said "well they look similar" and helped SCOs FUD campaign now looks like a complete idiot, because of course they're identical.

    If SCO had said this straight away, IBM would simply go "Yep we did that, they're identical. And we had every right to." Instead, they chose to make a great mystery with wild conspiracy theories out of it to pump their stock up. However, the illusion is fading bad, and now they need bigger numbers (80 lines? no 168,276 lines!), cheaper media stunts (like the Fortune 500 licence) and more and more farfetched reasonings. Very soon, the bubble will break.

    Kjella

    --
    Live today, because you never know what tomorrow brings
    1. Re:These files are extremely well known... by Ian+Lance+Taylor · · Score: 1

      The NDA isn't about the code which IBM/Sequent wrote and contributed to Linux.

      The NDA is about different, unrelated, code, which SCO claims was copied directly from Unix into Linux.

      It is the latter code which is the basis for SCO's Linux licensing. The code which IBM wrote is the basis for the lawsuit against IBM. Two different things.

  161. Someone, please buy Atari's Unix rights please... by The+Lynxpro · · Score: 1

    Atari was a licensee (sic) of Unix System V. directly from AT&T when they wanted to offer a Unix option for the TT030 computer systems (Motorola 68030 based). Perhaps someone should check with the current Atari (ie. Infogrames) to see what the terms of that license was. Maybe Atari/Infogrames could transfer the rights to another company, and they could sell a Unix System V. package with Linux bundled with it dirt cheap and thereby beat SCO at its own game just in case IBM and Red Hat lose... The end user would actually be buying a Unix System V. package and all the IP rights with it for certainly a lot less than the direct $699 SCO bribe...

    --
    "Right now, somewhere in this world, Scott Baio is plowing a woman he doesn't love," - Peter Griffin, *Family Guy*
  162. You think SCO still uses code? by roystgnr · · Score: 1

    That's so cute. But no, they sold all their computers months ago, to pay for more lawsuits.

  163. Test by Raven42rac · · Score: 1

    This whole hullabaloo has the foul odor of extortion (allegedly, /covering my ass) emanating from it, like those companies that sue small business websites saying they patented hyperlinking or shit like that. Maybe this is SCO's new business plan. Yes SCO will burn, Big Blue will go on, unfettered.

    --
    I hate sigs.
  164. Re:NUMA and RCU? Then why... by PurpleFloyd · · Score: 1
    What's the fee for? Extorting people worried about Linux licensing (read: big business).

    Interestingly, the logic behind that claim is similar to the logic behind SCO's core claim: SCO believes that it has trade secret rights to the NUMA and RCU code developed by IBM and Sequent, because it was developed for AIX and Linux, and a lot of the files are the same. Since SCO has trade secret rights to UNIX and thus most of AIX, they seem to think that the shared code between the AIX RCU and NUMA implementation and the Linux NUMA and RCU implementation is a derivative work of Unix and thus they are the only ones allowed to license it (while the code still belongs to IBM, they can't do much with it because it's SCO who has the ability to license it).

    SCO seems to think they have a strange Midas touch: whatever they touch, becomes theirs. We'll see how that holds up in court.

    --

    That's it. I'm no longer part of Team Sanity.
  165. Yawn by Jugalator · · Score: 1

    Seriously, I thought these stories were funny at first, but right now they're mostly like sequels to a funny movie that get less and less funny as more are made. What I'd like to see now is how SCO is judged, but I guess there are a dozen of episodes left until that. :-P

    --
    Beware: In C++, your friends can see your privates!
  166. RCU Code NOT from Sequent Unix by msgmonkey · · Score: 5, Informative

    I've just had a look at the original RCU patches contributed by IBM for 2.4.1, (RCU web site, http://lse.sourceforge.net/locking/rcupdate.html)

    One of the copyright notices from a file:



    Support for deferred freeing of memory using Read-Copy Update
    mechanism.

    Copyright (c) International Business Machines Corp., 2001

    This program is free software; you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation; either version 2 of the License, or
    (at your option) any later version.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
    GNU General Public License for more details.

    You should have received a copy of the GNU General Public License
    along with this program; if not, write to the Free Software
    Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.

    Author: Dipankar Sarma [dipankar@sequent.com]
    (Based on a Dynix/ptx implementation by
    Paul Mckenney [paul.mckenney@us.ibm.com])



    IBM aquired Sequent in 1999, the copyright notice on this file from 2001. The important thing is that this code is based on an implementation and not the actual original code as such this is not Dynix/pty code.

    SCO could argue that since it is based on the code then it is actually a copy, however from what I have seen of the contract clauses (mainly from groklaw) IBM are free to use any knowledge/processes/etc gained from adding to AIX.

    Probably the two pieces of code look similar and I can believe even the comments since the implementor had access to original code. In addition to this it could be argued that it would be impossible to implement the code without there being similarities or even being nearly identical in places. For example try implementing a bouble-sort/linked list/etc without the code looking similar.

    The only thing left are the RCU patents and IBM own these.

    Having looked at this now SCO's case is pretty thin, they could win of course nothing is impossible (though unlikely), however it would just be a case of copyright violation and someone outside of IBM could do a re-implementation of RCU. In addition since RCU is n't part of the mainstream Linux kernel so I cant see how they could claim any substantial damages let alone $3 billion.

  167. Re:NUMA and RCU? Then why... by Anonymous Coward · · Score: 0

    1. This has nothing to do with patents.

    2. You can use IO-APIC on uniprocessor systems. If you grep the kernel changelogs for ibm you will see they contributed heavily to apic code.

    3. SCO sucks.

  168. Now as I understand it by bobKali · · Score: 4, Interesting

    The code in question was originally developed as a theorhetical process and was then added to UNIX. Stating that because it was subsequently added to UNIX makes it the property of SCO would be like Ford saying that because Pioneer car stereos can be installed in Ford cars that gives them the right to sue Pioneer for making a kit that allows those same radios to be installed in Chevrolet cars.

    I suppose you can sign a contract stipulating just about anything - and since we havn't seen the Sequent contract yet (if ever) there could be something idiotic like that in there.

    1. Re:Now as I understand it by Ugot2BkidNme · · Score: 1

      If ford made the cars and Pioneer had an exclusive liscence to engineer to Ford Cars and improve on them. Then in terms they were not allowed to use the same engineering design to enhance Chrystler cars is stated in the agreement the design modification although owned by Pioneer are essentually exclusive to Ford. Now lets say Chrystler buys Pioneer, then applies thattechnology to their own brand of cars. They have just Violated teh Agreement with Ford and are now subject to Lawsuit. Its really Very simple if this is the Case SCO is right IBM did violate a liscence agreement. Is it immoral Sure as hell is but then again. You make somethign that costs 699 a liscence and someone else comes around makes a near identical product and charges nothign for it you would be pissed as well.

    2. Re:Now as I understand it by killmenow · · Score: 1
      You make somethign that costs 699 a liscence and someone else comes around makes a near identical product and charges nothign for it you would be pissed as well.
      But the key here is that SCO, the SCO in this suit, the SCO that used to be Caldera, didn't make anything. They bought up some contracts a while back and the new batch of executives in charge are better at making lawsuits than they are at making products.
    3. Re:Now as I understand it by Anonymous Coward · · Score: 0

      but what SCO is pissed about is they've been licensing a product for $1000+ a machine and in the meantime someone develops a better product that can be had for free. Why do you think the original SCO (the one that makes Tarantella - not the renamed Caldera), got out of the business? They knew their products were doomed. This is a case of a new executive team being brought in that doesn't understand the company's past, can't or won't make the changes necessary to make the business plan to work, and because of that, falls back to Canopy Group 101: How to Sue Your Business Partners for Fun and Profit.

    4. Re:Now as I understand it by trashme · · Score: 1
      The code in question was originally developed as a theorhetical process and was then added to UNIX. Stating that because it was subsequently added to UNIX makes it the property of SCO would be like Ford saying that because Pioneer car stereos can be installed in Ford cars that gives them the right to sue Pioneer for making a kit that allows those same radios to be installed in Chevrolet cars.
      You are confusing patent and copyright. Sequent developed the theoretical process of RCU, if they patent it, the patent is not transferred to SCO.

      However, if they implement RCU by modifying code licensed from SCO, and then IBM put this code into Linux, SCO may have a case. But that's for the courts to decide.
  169. SCO's carefully phrased release... by dilute · · Score: 4, Interesting

    ...doesn't implicate Linux per se (though part of the intent undoubtedly is to taint Linux by association).

    The release says that IBM was (allegedly) contractually obligated to treat its OWN work product which it developed based on SCO's predecessor's code in the same way (i.e., subject to the same restrictions) as the code it had licensed from SCO. It quite carefully says that IBM contributed "148 files of direct Sequent UNIX code" to Linux. But what SCO is talking about here ("Sequent UNIX code") is IBM's code, and not SCO's or AT&T's code. If IBM agreed to make its own code be subject to the license (and IBM says that it did not, since it claims that this provision was overriden by a side letter agreement that made completely different arrangements), then this would be a matter of contract between IBM and SCO (which IBM is very vigorously contesting). It would not mean that SCO owns the copyright to subject matter independently developed by IBM.

    It would not, even if true, give SCO any rights vis-a-vis a Linux user who had nothing to do with IBM and/or its contract with SCO. Off hand, I would say that the only way a Linux user would be at risk would be if there were substantial code written by the original copyright owner that found its way in some recognizable form into the Linux 2.4 or 2.5 kernels, and (even it that turned out to be the case), if the copyright owner never gave its permission for that code to be included. I have not seen where either of these contentions has been clearly alleged, except by implication, as a result fo SCO's threats.

    It is of course possible that there is such code overlap, but it is SCO's burden to prove it. I have not seen any proof of this. Even if they were to prove it, the Linux user would then be allowed to show SCO's consent to this inclusion, such as by the authorized release of the code in question under the GPL.

    It seems to me that SCO's case against the typical Linux business user is awfully speculative at this point.

  170. SCO wins by staying out of court. by siskbc · · Score: 1
    A better solution (and it appears to be the one that IBM is using) is to go ahead 'business as usual', then if SCO harrasses their customers, get an injunction against them for interference, which would (probably) get SCO shut down for good.

    Right, but this AIX crap is really just a proxy war for the fight against linux users, and everyone knows it. If it weren't for that, I'd agree with you. However, as of now, SCO hasn't made any legal moves against linux users, they've just been playing a PR game. As it stands, "business as usual" is NOT good for linux users.

    IBM needs to unify those two fights from a legal perspective, while SCO would prefer to keep them legally separate, only drawing parallels between them as they want in the media. SCO's fight against linux users depends on them having some success in avoiding the legal arena, where they have little chance. Every day this stays out of court is a win for SCO.

    That's why I think IBM should expedite this thing. Because if it never goes to court, SCO wins through erosion of linux marketshare in enterprise applications, as well as the potential for revenue through linux "licensing." Additionally, they depend on their inflated stock price to finance this game and provide a windfall in the event they sell out of their position. Giving them a legal setback would really hurt their stock price, and would cripple them in terms of their strategy.

    --

    -Looking for a job as a materials chemist or multivariat

    1. Re:SCO wins by staying out of court. by Ian+Lance+Taylor · · Score: 1

      this AIX crap is really just a proxy war for the fight against linux users

      Well, no, this AIX crap is about trying to get $3 billion out of IBM.

      It's going to take SCO a long time to get $3 billion out of Linux users at $1300 a pop.

    2. Re:SCO wins by staying out of court. by WhiteWolf666 · · Score: 1

      IBM's already filed this injunction...

      Sort of.

      They've filed an injunction to prevent SCO from claiming that IBM's license has been revoked.

      SCO doesn't have the right to revoke IBM's license. Perpetual, and irrevocable.

      IBM claiming that they need to stop SCO is not the correct approach. Instead, IBM is demanding that SCO not be permitted to say that the license has been revoked, because there is no way for SCO to revoke it.

      This will hurt SCO's stock, me thinks.

      --
      WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
  171. MOD PARENT UP by grendelkhan · · Score: 2, Troll

    Sequent / IBM have no names on these files. What the heck is SCO talking about now?? Where are the NUMA files that orignated from IBM that contain Dyniz sources??

    --
    Wu-Tang Name: Half-Cut Skeleton Get your own Wu-Na
  172. Interesting by CaptTrips · · Score: 1

    So does SCO's claim say that only Linux 2.4 and 2.5 contain chunks of Unix code, or was this Unix code always there as part of the original Kernel? If the code was always they're as part of the original Kernel, then I find it interesting that Linux from day one was open-source. This meant SCO has access to the source code, probably reviewed it thoroughly and would have determined that parts of the code were from Unix.

    One has to wonder why they didn't address this issue in Linux' early years. The obvious answer is the market was privy to Linux. So like a good company, they sat back quietly and waited for Linux to germinate the Tech Industry. When this was successful then they would start their campaign of extracting license fees.

    On one hand I think this is a shady thing to do. Yet since they own the rights to Unix' code they have a legitimate claim to ask for money to use that code. This puts them in a unique position of being a Monopoly in that they can do whatever they want and they'll probably still be alive tomorrow because frankly we all know that Unix is a DAMN GOOD platform to run just about anything on (enterprise or non-enterprise).

    My two cents...

    --

    grep >= ! == $your
  173. If you really want to hurt them... by shub · · Score: 1

    ...Try shorting their stock. It's currently around $9.75. If you short ten shares to $0.01, that won't even cost you $100 (the stock is unlikely to ever go back above $10, certainly not within your short window).

    One person doing this isn't really going to hurt them. Millions of Linux users around the world doing this would bury the company.

    Of course, one person in a different thread said that they worked at a brokerage and SCO was one of the companies they weren't allowed to short, due to lack of liquidity of the shares. So, you might have to go looking for a place that would let you place a short, but you should still be able to do it.

    --
    Brad Knowles
    http://daily.daemonnews.org/ -- if you're not
  174. What innocent customers? by scruffyMark · · Score: 1

    They're bankers! How can you even suggest they're innocent?

    --

    What is the robbing of a bank, compared to the founding of a bank? -- Bertolt Brecht

  175. Getting closer to the complaint by Anonymous Coward · · Score: 0

    First, let me say that IANAL... but at least I RTFA. I think SCO/Caldera is beginning to close in on their actual complaint, and rather than making grandiose claims, it's beginning to look a lot smaller than $3bn (IMHO). Why they made a more reserved announcement than "All your Dynix are belong to us" on the eve oif their results announcement is a mystery to me. Is Boies trying to restrain their enthusiasm? There may be an argument that Sequent's SysV license is not covered by Amendment X, in which case, Dynix/PTX may be a derived Unix, and under the terms of the license, maybe the source must be "treated as part of the Original [System V] Software." But the source isn't necessarily "resulting materials" in terms of the contract, so even that's hazy. The numbers of files and lines will also turn out to be misleading. I predict the "approximate" numbers 148 and 168,276 will dwindle as this goes on. But SCO's still got enough of the Good Stuff to assert that "Unix based development methods" are covered by a license. What ever that Stuff is, they should be getting FDA approval, and replacing TV...

  176. I don't think I need a license. by chrome · · Score: 2, Interesting

    I did a quick calc against my gentoo-sources tree. Sure, its a bit different to vanilla, but what the hell, it will be roughly right.

    4592051 lines of code, only counting .h and .c files.

    168276 lines of disputed code, stated by SCO in their latest press release.

    If every line of code SCO claims to be in Linux IS in Linux, then it is only 3.6% (roughly) - and of that code, they claim that MOST of it is the NUMA and RCU (what is RCU? Can someone enlighten me?) - code that 99% of people don't even use anyway!

    1. Re:I don't think I need a license. by ctid · · Score: 1

      RCU stands for Remote Copy Update. I have no idea what that is. I'm pretty sure I don't need it for my Athlon 1200MHz CPU :-)

      --
      Reality is defined by the maddest person in the room
  177. No, no, no by TheConfusedOne · · Score: 2, Funny

    Unix development methods:

    printf( "Got here!/n" );

    --
    --- I wish I could hear the soundtrack to my life. That way I'd know when to duck.
    1. Re:No, no, no by Zathrus · · Score: 1

      That's "Got here!\n" :)

      One day maybe we'll have a debugger that works on AIX with C++ code... currently neither dbx w/ xlC nor gdb w/ g++ work. They both core quite nicely though.

  178. Dates by jefu · · Score: 1
    Is it possible that this action by SCO will enable faster actions by IBM/Redhat...?

    By terminating IBM's license, SCO is saying that IBM can't make money now on related products now. Since the scheduled court date is more than a year off, this could impose a serious hardship (so to speak) on IBM.

    It would seem to me that that would give IBM a way to push for an injunction stopping this quickly, or a way to push for a faster trial.

  179. Take this IBM..... by Anonymous Coward · · Score: 0

    As of now they're on Double SECRET Probation! - Dean Vernon Wormer :)

  180. DejaVu without dupes? by mrjb · · Score: 1

    I must be confused, prolly cause I didn't follow the entire soap series. Help me get this straight.

    First SCO terminated IBM's license. Then IBM said, "You can't, the license is perpetual" Now several weeks later, SCO says "Seriously, we *REALLY* terminate your license." So now IBM is going to have to explain them again?

    --
    Visit http://ringbreak.dnd.utwente.nl/~mrjb/growingbettersoftware to download your free copy of the book
    1. Re:DejaVu without dupes? by SuiteSisterMary · · Score: 1

      To quote The Gord, from IBM to SCO, "Just because you say it doesn't make it so."

      --
      Vintage computer games and RPG books available. Email me if you're interested.
  181. These numbers must be very very old now.... by frkiii · · Score: 1

    At the bottom of their "SCO puts IBM on double secret probation" press release, some numbers are given: "The SCO Group (Nasdaq: SCOX) helps millions of customers in more than 82 countries to grow their businesses everyday. Headquartered in Lindon, Utah, SCO has a worldwide network of more than 11,000 resellers and 4,000 developers." I bet a new survey of countries, resellers and developers (a true survey), would show something like: 2 countries. 0 resellers. 2 developers. 5 lawyers. But we count all Linux distributions, resellers and developers as "ours" also, because we say so, so there! So the numbers are much higher! Regards, Fredrick --------- I still like the "SCOzo the Clown" idea....

  182. Re:Actual transcript smuggled out of the courthous by toomuchPerl · · Score: 1
    SCO-All right, we'll call it a draw.

    And you call yourself a Monty Python fan? In the context of this quote, it should be IBM-All right, we'll call it a draw.

    Jeez.
    -toomuchPerl

  183. Here is some info from IBMs src by ratfynk · · Score: 1
    Just for the interest of where the IBM smp code is in the Kernel Source, it took a little digging but if the individuals would like to respond this might be interesting, I know it is a little bit of a troll but what the heck;

    /* * arch/s390/kernel/smp.c * * S390 version * Copyright (C) 1999,2000 IBM Deutschland Entwicklung GmbH, IBM Corporation * Author(s): Denis Joseph Barrow (djbarrow@de.ibm.com,barrow_dj@yahoo.com), * Martin Schwidefsky (schwidefsky@de.ibm.com) * * based on other smp stuff by * (c) 1995 Alan Cox, CymruNET Ltd * (c) 1998 Ingo Molnar * * We work with logical cpu numbering everywhere we can. The only * functions using the real cpu address (got from STAP) are the sigp * functions. For all other functions we use the identity mapping. * That means that cpu_number_map[i] == i for every cpu. cpu_number_map is * used e.g. to find the idle task belonging to a logical cpu. Every array * in the kernel is sorted by the logical cpu number and not by the physical * one which is causing all the confusion with __cpu_logical_map and * cpu_number_map in other architectures. */

    --
    OH THE SHAME I fell off the wagon and use sigs again!
  184. Future to the Back by EmagGeek · · Score: 1

    Biff: Hey, McBride! You got that homework I asked you to do for me?

    McBride: Well, no, biff, I was going to start working on it, but I couldn't find anyone to steal if from

    Biff: *noogies* THINK, McBride, THINK! I need plenty of time to copy it into my kernel to make it look like it's mine. How else am I going to sue whomever you copied it from?

    McBride: uh, uh, okay, Biff, I'll try to get you some Linux code as soon as I can.

    1. Re:Future to the Back by buford_tannen · · Score: 1

      lol! excellent reference!

      --
      Buford "Mad Dog" Tannen
  185. Back to "derivative work" by TheConfusedOne · · Score: 1

    The complaint on SCO's side is that Sequent did this work for their Sys V Unix and thus should be considered a derivative work and protected thusly.

    However, if you look at a lot of the work it was originally done (and patented) in a non-OS specific manner. Thus, the work was done and then IMPLEMENTED under their version of Unix. This makes a huge difference in that the original source of the work is not their Unix and thus isn't derived from their Unix.

    --
    --- I wish I could hear the soundtrack to my life. That way I'd know when to duck.
    1. Re:Back to "derivative work" by Anonymous Coward · · Score: 0

      I think substantial new features, such as NUMA and RCU could never be considered at the same level as a "translation", "editorial revision", "elaboration", etc.

      Anyway, SCO admits IBM "owns" copyrights on NUMA and RCU. That admission means SCO knows these works must be, at least "seperate works". Since IBM is not SCO, I'd think "independent" applies as well.

      So SCO's contact says "derivative", but their evidence and PR keeps saying "collective work". It seems, the two are different things.

      From Washington University...

      Compilations

      A "compilation" is defined in 17 USC 101 as "a work formed by the collection and assembling of preexisting materials or of data that are selected, coordinated, or arranged in such a way that the resulting work as a whole constitutes an original work of authorship." A "collective work" is a type of compilation and is defined as "a work, such as a periodical issue, anthology, or encyclopedia, in which a number of contributions, constituting separate and independent works in themselves are assembled into a collective whole."

      Derivative works

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

      Futher, from the law itself:

      "The copyright in a compilation or derivative work extends only to the material contributed by the author of such work, as distinguished from the preexisting material employed in the work, and does not imply any exclusive right in the preexisting material. The copyright in such work is independent of, and does not affect or enlarge the scope, duration, ownership, or subsistence of, any copyright protection in the preexisting material." 17 USC 103 (b)

      Indeed.

  186. uhh...why oh why.... by mAineAc · · Score: 1

    can't someone fix the blaster worm to take out SCO instead of poor old Microsoft.

  187. Just Recompile Without Multiprocessor Support by Anonymous Coward · · Score: 0
    If you have any doubts about the outcome of the IBM/SCO wars, just recompile your kernel without multiprocessor support.

    If you can't do that, simply rest easily considering that SCO is *still* releasing the source code to Linux on their own ftp server. There is no way they can claim ignorance of the code contents now. They have VDH (very dirty hands). If this suit were to go to court tomorrow it would last a whole two or three days after the judge reads IBM's counterclaims and (after laughing out loud for 15 minutes) told the bailiff to arrest the SCO representatives for a frivolous and vexatious suit and remands them to SEC authorities for their lame pump and dump scheme.

  188. Ever hear of "the Big Lie" ??? by Salgak1 · · Score: 2, Interesting
    At risk of a Godwin's Law violation, allow me to quote Adolf Hitler, creator of this tactic:

    The great masses of the people will more easily fall victims to a big lie than to a small one.

    And SCO's telling a real whopper. . .

  189. The real game... by Nic-o-demus · · Score: 4, Insightful

    I posted this in a thread yesterday, but it got sort of buried and I think /.ers ought to keep it in mind:

    SCO's Shell Game

    Some quotes:

    None of the threats make legal sense. If they did, SCO would be able to get an injunction to shut down Linux users. In practice, SCO hasn't even been able to get an injunction against IBM and won't get a court hearing on its request to do that until 2005.

    Meanwhile, a German court told SCO in June that it must stop threatening Linux users. And an Australian government agency is looking into charges that SCO is essentially running a shakedown racket by claiming that Linux users must buy a license they don't actually need.

    And SCO's tactics don't make business sense, either. SCO is a software company that has slashed its R&D budget, alienated its customers and demolished the value of its brand. That's not the way you build a business.

    So, what do you do when you have no real business but your stock price keeps going up? We all learned that lesson during the dot-com bubble: You use that stock as currency.

    . . .

    Got all that? If it sounds like a shell game, well, that's the way Canopy likes to move its companies around. But in effect, Canopy used SCO's stock price, boosted by SCO's Linux threats, to rake in a couple of million dollars in cash behind the scenes.

    And apparently it worked. Which means we can expect that as long as Canopy can find ways of cashing in on SCO's threats against Linux users, those threats will keep coming -- no matter how little sense they make.

    1. Re: The real game... by Black+Parrot · · Score: 1


      > And apparently it worked. Which means we can expect that as long as Canopy can find ways of cashing in on SCO's threats against Linux users, those threats will keep coming -- no matter how little sense they make.

      But the pump appears to be wearing out. Previous FUDnouncements drove the stock up to nearly 14, but today's only has it back up to about 10 (from 9.x yesterday).

      Maybe this won't last much longer.

      --
      Sheesh, evil *and* a jerk. -- Jade
    2. Re:The real game... by Anonymous Coward · · Score: 1, Interesting

      > None of the threats make legal sense.

      Perhaps, but that hasn't stopped them.

      > If they did, SCO would be able to get an injunction to shut down Linux users. In practice, SCO hasn't even been able to get an injunction against IBM and won't get a court hearing on its request to do that until 2005.

      A preliminary injunction usually requires a bond to cover potential damage, should the injunction be later found done in error, at trial. How big do you think such a bond would have be to cover the potential damage of "stopping" linux? Trillions? Hundreds of Billions?

      Whatever the number, SCO sure ain't got it.

      > Meanwhile, a German court told SCO in June that it must stop threatening Linux users.

      Laws differ. In some places you can make no public finding "of law" regarding a dispute until "the law" is decided in court. IANAG, but perhaps SCO must remain silent, even if they think they are dead-to-rights on the matter.

      > And an Australian government agency is looking into charges that SCO is essentially running a shakedown racket by claiming that Linux users must buy a license they don't actually need.

      Gernally speaking, Governmental agencies must "look into" all charges. UFO's in the back yard? Fed's zapping your brain with lasers? They don' have to "look" very hard, but they always "look into" things.

      > And SCO's tactics don't make business sense, either. SCO is a software company that has slashed its R&D budget, alienated its customers and demolished the value of its brand. That's not the way you build a business.

      Ok. Divide the remains, after lawyers, of a $3Bln settlement by the number of shares outstanding. Done.

      > So, what do you do when you have no real business but your stock price keeps going up?

      Again, do the division. What's a share worth? You're betting on the outcome of the case, nothing more.

    3. Re:The real game... by PhilHibbs · · Score: 1
      None of the threats make legal sense. If they did, SCO would be able to get an injunction to shut down Linux users.
      I don't think that's true, because to get an injunction shutting down linux users, you'd have to prove imminent and ongoing harm to SCO, which is not the case. They may be out of pocket, but me continuing to run Linux on my laptop is not harming them. The balance of harm is seriously towards the Linux users being shut down and therefore would be an unreasonable emergency injunction.
  190. AIX vs. Dynix/ptx by Valdrax · · Score: 4, Interesting

    This letter specifically gave back to IBM the rights of any code they created to enhance or extend the AIX/SYS5R4 OS.

    Yes, it did. However, if they don't have such an agreement over Dynix/ptx, then IBM may very well be screwed. If what SCO says is true (even though what they said about their right to terminate AIX wasn't), then IBM may be in a world of hurt. If Dynix/ptx code must be treated as a derivative of System V, then there may be actual trouble here. Remember, AIX and Dynix/ptx are completely separate products with completely separate licensing schemes. SCO may have actually found a legal leg to stand on. Unless IBM can produce similar documentation about Sequent's code, it may belong to SCO.

    (By the way, how does SCO have Dynix/ptx source code to compare against the Linux kernel?)

    --
    If it's for-profit but free, you're not the customer -- you're the product (e.g., the Slashdot Beta's "audience").
    1. Re:AIX vs. Dynix/ptx by MuParadigm · · Score: 1


      SCO has copies of source code from all its licensees.

      I posted a while ago that the Sequent code seemed like the most likely place for SCO to have a legitimate claim, but that supposition rested on 2 points:

      A) That the Sequent code did not come under the umbrella of IBM's licenses when IBM purchased them (I'm sure IBM will argue that the code now falls under their licenses)

      B) That their are no upstream rights to the NUMA and RCU code prior to Sequent's implementation. (Fortunately, it appears there *are* upstream rights that would take precedence over SCO's "intellectual property" claims -- in that the algorithms and technologies were first published by Paul McKenney in a generalized, i.e. non-Unix, context)

      So, I don't think SCO has a leg to stand on here either, but IBM *may* have to present a different defense for the code originated at Sequent than for its AIX code.

    2. Re:AIX vs. Dynix/ptx by Anonymous Coward · · Score: 0

      Yes, it did. However, if they don't have such an agreement over Dynix/ptx, then IBM may very well be screwed.

      My understanding (and correct me if I'm wrong), is that the letter in question is a "letter of understanding" rather than a "side agreement". My understanding is that a "letter of understanding" applies to all companies that signed a similar contract; that is, how AT&T interprets that clause in the contract dealing with derivative works.

      A previous poster claimed (and it made sense to me) that AT&T must apply a "letter of understanding" to everyone that signed a simliar contract, as opposed to a "side agreement" that would only apply to IBM. In which case, that inerpretation must apply to Dynix/ptx's contact also.

      I have not seen the letter in question, not am I a lawyer, so I can't be sure exactly what it says or what it means.

  191. Interesting stock reporting. by JaJ_D · · Score: 5, Informative

    If you check out the Nasdaq stock report for sco the following shareholders with >5% is shown:

    Ralph Yarro
    Darcy Mott
    Canopy Group Inc
    John Wall

    If you then check out The Canopy Group website you will see the following as board members

    Ralph Yarro - CEO & Presedent
    Darcy Motto - Vice President, Treasurer and Chief Financial Officer

    This gives the Canopy group at least a 15% stake in SCO, possibly more.
    If you look at SCO's board and then have a look at their share trading, you see the following:-

    Charles BROUGHTON (VP world ops) sold about 120,000 USD worth of shares in the last two months
    Robert BENCH (CFO) sold about 120K USD in last few months
    Jeff HUNSAKER (s. VP)sold about 120K USD in last few months
    Other than McBride (CEO) most of the board have ofloaded shares in the last month or two. To give you an idea of the "peak" of share selling. According to the Nasdaq the number of "insider" trades (i.e. board members) in the last 12 months was 15, and 12 (all of which were sales) of those were in the last 3 months (or as its know just after the Linux thing).

    Yarro and Mott both also sit on the board of SCO.

    Does that stink or is it just me?

    Jaj

    1. Re:Interesting stock reporting. by PierceLabs · · Score: 1

      It is very interesting ideed, but the real question is whether or not they've done anything that's truly illegal. Many of these CEOs do many things that may be morally wrong and scummy, but may not be in fact truly illegal. It will be interesting to see what the true legal status of this action is on the parties involved because I'm sure they are stupid enough to do something so obvious while the SEC and the administration are parading executives in front of the cameras.

  192. Re:McBride? McBriii-ide? Hello? by DrWhizBang · · Score: 1

    That's it! SCO stole IBM's car, went back in time with linux source code, and used it to build Unix!

    and Linux rides a skateboard and wears Calvin Klein undies!

    --
    Schrodinger's cat is either dead or really pissed off...
  193. End-users have no liability by yeremein · · Score: 1

    So SCO's new story is that, even though IBM owns the relevant copyrights, IBM didn't have the right to donate NUMA and RCU to Linux.

    Well, IBM did.

    SCO has no grounds to charge end-users license fees for using this code, as SCO owns no relevant copyrights or patents.

    SCO is welcome to seek damages for breach of contract against IBM, which of course they are. This is their only recourse, however. Good luck.

  194. Derivative Works by Robawesome · · Score: 1

    Dynixs' contract was very specific about derivative works. NUMA is not a "derivative work". How could it be? UNIX had nothing like it. In addition, Dynix did ALL their work in a cleanroom, then later used the stuff with UNIX, not as part of it. Also, I read IBM's counterclaim. If I was SCO, I would have shut my fat mouth.

    --

    I did NOT learn everything I need to know in kindergarten.

  195. leave it in your ass by Ender+Ryan · · Score: 1
    "Most users of Linux are on SMP machines"

    Please don't pull stuff like that out of your ass, it stinks. Just leave it up there, until you find a restroom(or bush...) so you can properly relieve yourself.

    --
    Sticking feathers up your butt does not make you a chicken - Tyler Durden
    1. Re:leave it in your ass by TheShadow · · Score: 1

      Please forgive me oh Great One for my mistake. I meant to say that most users of linux who have multi-processor machines are using SMP machines rather than NUMA.

      There is that better? Or should I still go find a restroom?

      Asshole.

      --

      --
      "What do you want me to do? Whack a guy? Off a guy? Whack off a guy? Cause I'm married."
  196. Billy Madison reference... by Helios808 · · Score: 2, Funny

    Mr. McBride, what you've just said is one of the most insanely idiotic things I have ever heard. At no point in your rambling, incoherent response were you even close to anything that could be considered a rational thought. Everyone in this room is now dumber for having listened to it. I award you no points, and may God have mercy on your soul.

  197. Shhhh!!!!! Geez.. by Anonymous Coward · · Score: 0

    Cripes....do you want to help SCO?! Stop helping them already...

    Seriously though, the fact that SCO has a remote legal basis for each accusation is enough to keep the SEC out of this. When SCO goes down however, I'm sure they'll at least try to find proof that SCO knew these were hopeless legal angles. SCO may be many things, but the people there aren't stupid enough to document their underhanded shit.....you'll never find a message in hard or soft form that states what they're really doing. They'll make it out of this situation with some money in their pockets, it really boils down to how much.

  198. Re:Actual transcript smuggled out of the courthous by agentforsythe · · Score: 1

    erm no the original post was correct fool

  199. NUMA and RCU are patented by Anonymous Coward · · Score: 2, Informative
    My guess is that IBM holds both hardware and software patents. Since any Sequent agreement with ATT (or whoever owned Unix at that point) cannot possibly be misconstrued as transferring patent ownership to the owners of UNIX, that means that SCO almost certainly does *not* own the NUMA and RCU patents. IBM on the other hand almost certainly owns those now.

    If you people had really been following the whole idea of derivative works you would have realized that there are *many* things that cannot be considered derivative works. One of those things are algorithms that can only be expressed a certain way (ie: software patents). Another one is code that is hardware dependent (ie: hardware patents).

    NUMA and RCU are almost certainly considered to be one or both of those.

    BRRRRKKKK! Sorry, SCO. The time is up. Not only have you still been releasing all of the kernel code under the GPL, you are trying to encumber another companies software and hardware patents.

    Don't pass GO. Go striaght to jail.

  200. I pressume... by Anonymous Coward · · Score: 0

    SCO rebates IBM their $699?

  201. And apparently you were asleep... by FreeUser · · Score: 2, Interesting

    ...when it was also pointed out numerous times that SCO's unwillingness to divulge what is infringing and where, thereby making it impossible for those alleged to be infringing to correct the problem and avoid doing so, makes them ineligable for any compensatory or punitive damages of any kind. This is a well established civil doctrine with a mountain of precident to dwarf Everest (look up "dirty hands" and "clean hands" with regard to civil law if you are still confused).

    Rewriting Linux now will not do a damn bit of good. It doesn't absolve anyone from past infringements, and it won't mean that IBM did not breach their contract.

    IBM's alleged contract violation is between IBM and Caldera-renamed-SCO and has absolutely no bearing on Linux. IF, and I stress IF (because as others have pointed out, an overwhelming amount of evidence indicates it is almost certainly not the case), Linux were infringing on a SCO copyright, liability would only exist AFTER SCO has provided the information and the kernel coders have had an opportunity to remove the infringing code. Interestingly enough, even that liability is probably close to zero as a direct result of SCO's current actions (not disclosing the source code, i.e. not doing everything in their power to alleviate so-called damages, thereby indicating rather strongly that the damages aren't significant. Again, there is a mountain of precident for this sort of thing...)

    When it comes to trial, even if we all find out that Linux is infringing on SCO's IP, all the non-disclosure will have done is make the judge less likely to award damages to SCO.

    No. The lack of disclosure will have made it impossible for the judge to award damages to SCO. Well, not impossible (a judge can do anything), but impossible for it to hold up on appeal. Again, the mountain of precident on that point is huge ... indeed, it appears to be a basic tenent of civil law.

    IANAL, this is not legal advice, do your own research, yada yada yada.

    The only reasonable explanation I have heard for the secrecy is that they can't substantiate any of their claims.

    That is a reasonable explanation, but not the only one. A couple of others include

    1) an agenda to spread FUD against Linux and free software, financed, perhaps even contracted by, an interested third party who wishes to keep their own hands clean (three guesses on who that might be).

    2) minimal claims are valid, but SCOX and Darl et. al. can benefit much more financially by keeping the specifics ambiguous than they can by disclosing exactly how minor the infringement is.

    Again, I think your explanation is the most likely: there is no infringement whatsoever. But there are a few other explanations that are just as reasonable, and nothing precluding several of them applying in parallel.

    Regardless, and here is the bottom line: SCO's own behavior has precluded any liability for those using, deploying, developing, and reselling Linux, with the exception of IBM, who may have some liability based on a contractual technicality (but probably does not, as their IP attorneys are quite savvy and would have likly settled were that the case). All muttering and innendo to the contrary is nothing more than SCO produced FUD of the lowest order, quite possibly at the behest of (and certainly financed by) SUNW and MSFT.

    --
    The Future of Human Evolution: Autonomy
    1. Re:And apparently you were asleep... by JimDabell · · Score: 1

      ...when it was also pointed out numerous times that SCO's unwillingness to divulge what is infringing and where [...] makes them ineligable for any compensatory or punitive damages of any kind.

      I mentioned this briefly in the post you are replying to. You even quote it later on. Granted, I said "less likely" and not "impossible", but you agree that it's not impossible. How was I asleep?

  202. Webcast of Conference Call by joepa · · Score: 2, Funny

    Looks like we might have a chance to see the first Slashdotted conference call.

    1. Re:Webcast of Conference Call by Ian-K · · Score: 1

      Hmmm... time to be creative in these registration form fields, guys...

      I certainly was :-)

      Trian

      --
      I'm no longer fed up with MS Windows: I go rid of them :)
  203. Maybe IBM and SCO are colluding by MS_leases_my_soul · · Score: 5, Interesting

    OK, maybe it is time to put my tinfoil hat on and start looking out the window for black helicopters, but what if this is all a nod-and-wink kind of scheme.

    IBM and SCO make it known that IBM is thinking of buying SCO. Instead, SCO sues IBM. SCO's stock price goes up. SCO's owners dump stock (getting rich) and SCO uses the inflated stock price to buy up small companies. Once SCO has all the pieces in place, IBM suddenly forces things into court and SCO is blown away. SCO stock plummets. *THEN* IBM buys them for a basement bargin price.

    This does multiple things for IBM. (1) Publicity. (2) Good PR with the Linux crowd as IBM "saves the day". (3) They get more stuff in the SCO buyout. (4) It places IBM's competitors in the Linux arena on shaking ground while all this is happeneing, possibly forcing some out of business.

    Suddenly, in the end, IBM has a Linux distro, AIX for the high-end, lots of other IP, and a rep as being the big champion for Linux that is willing to put its money where its mouth is.

    Right about that time, IBM would be ready to take on Microsoft again for the servers and desktops. IBM gives away the desktop OS just to have an in and starts recapturing the mid-level servers. As IBM becomes the "leader" of Linux, why would you not go with IBM and AIX on the big iron since IBM makes it one smooth continuum of *nix?

    Man, I have got to stop drinking 10 diet cherry cokes while on medicine for a head cold before I post. =)

    1. Re:Maybe IBM and SCO are colluding by Zork+the+Almighty · · Score: 1

      Sorry, I seem to be a little confused on something. If SCO's stock is low, and then the price goes up, how does SCO get more money ? They would have to issue new stock, wouldn't they ?

      --

      In Soviet America the banks rob you!
    2. Re:Maybe IBM and SCO are colluding by WCMI92 · · Score: 1

      SCO execs have stock. And stock options. A number of them cashed some of these in recently and made a SHITLOAD of money where before all this slander there was none to be had.

      SCO execs are calling the shots on their ridiculous press releases. Any coincidence? I think not.

      --
      Corporatism != Free Market
    3. Re:Maybe IBM and SCO are colluding by Anonymous Coward · · Score: 1, Informative

      The company doesn't sell all its stock during an IPO. That would be stupid. Instead some of it remains with the company. They can do a split, sell stock, give it out as options. It is bargaining power and companies like bargaining power.

    4. Re:Maybe IBM and SCO are colluding by budgenator · · Score: 1

      Suddenly, in the end, IBM has a Linux distro, AIX for the high-end, lots of other IP, and a rep as being the big champion for Linux that is willing to put its money where its mouth is.
      But it's not realy working for SUN, a Linux vs. Solaris strategy, so why should it work for IBM as Linux vs. AIX? I think IBM is smart enough to see it's Linux all the way or Linux no way, mixing Linux and unix just doesn't work. The developement of Linux is just to nimble, no single vendor could ever keep their unix product suffiecently better than Linux to justify the price difference for long.

      --
      Apocalypse Cancelled, Sorry, No Ticket Refunds
    5. Re:Maybe IBM and SCO are colluding by Lazy+Bastard · · Score: 2, Informative
      The company doesn't sell all its stock during an IPO. That would be stupid. Instead some of it remains with the company. They can do a split, sell stock, give it out as options. It is bargaining power and companies like bargaining power.
      This statement is hopelessly naive and needs to be corrected.

      When a company is formed, a maximum number of shares is authorized. This number is usually quite large (many times what the company will issue for some time). Even then, this maximum can be changed at a later date. The number of authorized shares is pretty much meaningless. The idea that a company "holds back" shares or "doesn't issue all the shares" in an IPO is meaningless.

      What is important, is the number of shares outstanding. That is the number of shares issued - shares bought back by the company (shares bought back are called Treasury Stock). Of course, if the company sells or gives away treasury stock, those shares are once again considered outstanding. The number of shares you own, divided by the number of shares outstanding is the percentage of the company you own.

      The stock sold in an IPO is newly issued stock (in all but a incredibly small number of cases). Nobody has ever owned this stock before. The proceeds of this sale go directly into the coffers of the company (less the commission to the investment bank). One of the thing that the red herring & final prospectus describe how this money will be used.

      The people and institutions that owned stock prior to the IPO still own the same amount of stock they did before. However, their shares are now diluted which means that they represent a smaller percentage of the company than they did before. Their shares are also Restricted Stock and cannot be traded on the open market. Their is a pain-in-the-ass process by which it can be converted in limited quantities, which is how insiders get to sell their stock eventually.

      At a later point, the company may issue new shares to raise more capital. This is called a secondary offering. Once again, these are NEW, never before issued shares.

      When a company goes through a stock split, no new shares are issued. It doesn't "use up" shares that are sitting around. The only thing that happens is that the old shares are replaced by a larger number (or in the case of a reverse split, smaller) of new shares.

      The real limit on issuing new stock? Dilution lowers the price of the stock. The exchanges set minimum price levels and will boot a stock off the exchange if it trades below that price.

    6. Re:Maybe IBM and SCO are colluding by eniu!uine · · Score: 1

      I think most of your insane paranoid idea makes perfect sense(scary). All except this:

      "Suddenly, in the end, IBM has a Linux distro,"

      I don't think IBM will want a Linux distro. If they distribute code licensed under the GPL they are indemnifying all Linux coders from suits using IBM's famous patent portfolio. Of course they have already done this with some major stuff(RCU et al.), but this way they can pick and choose.

    7. Re:Maybe IBM and SCO are colluding by Anonymous Coward · · Score: 0

      I have found a post down below with some eery evidence to make this theory hold water.

      Here...

      http://slashdot.org/comments.pl?sid=74586&cid=66 86 213 ...another reader finds a link to none other then IBM!

      Very freaky.

    8. Re:Maybe IBM and SCO are colluding by daveisoverlord · · Score: 1

      owners dump stock (getting rich) and SCO uses the inflated stock price to buy up small companies.

      I agree totally with the owners getting rich part, but I'd have to disagree with the purchasing small companies. Who would trade their company for SCO stock? Any tech company has to know how precarious the currently overpriced stock is right now. At any time the stock price could plummet. I wouldn't trade my company for that stock right now. Plus, I'm sure the smallest due dilligence audit would reveal the wild swings in the stock price over the past year.

      I think somebody would have to be pretty dumb to sell their company for SCO stock.

      --
      The perception of reality is more important than reality itself.
    9. Re:Maybe IBM and SCO are colluding by neonmagic · · Score: 1

      Well...you're both wrong, here's why I think...

      1. Microsoft is involved - heavily, this is their effort to 'legally' discredit and kill Linux as a competitor.

      Think about it - who has been saying that the GPL is 'viral' for quite some time now? Microsoft. Who has been saying that Linux interferes with IP rights for some time now? Microsoft.

      Microsoft is a hard ball company - they don't fork out money for no reason at all. They ONLY pay when they have to. Microsoft wouldn't pay SCO huge amounts of money for licences/IP rights usage etc unless they had to. And they certainly wouldn't party with lots of money unless they could see the actual infringements.

      Microsoft has a HUGE legal arm. Who is the legal group for SCO in this case? The same legal firm that looked after Microsoft vs DOJ. Coincidence? I don't think so. Not at all. Considering in the Microsoft vs DOJ case there was some instances of IP that came up and had to be dealt with.

      Think about it - Microsoft 'funds' SCOs case on clear legal ground that it knows it will win. SCO does a background deal with Microsoft that after case is over, they split the winnings, SCO will sell itself to Microsoft. Then Microsoft owns both Unix and Windows! Complete market dominance. Dig this as well - it means Microsoft can distribute a 'legal' variation of Linux as they have a licence, but deny licences to other Linux companies, therefore killing any competition that way. They can also dictate kernel development etc etc.

      Microsoft says it has a Linux testing section for usability purposes. Yeah right, and i'm Santa Claus. The sole purpose was so that they could get the code and dissect it, looking for IP stuff to help SCO sue on. Quite elementary dear Watson. Be realistic here, how many lines of code does the kernel have? How many employees does SCO have that would be able to search thru the traditional Unix System V kernel and Linux kernel and compare lines? Not enough. That points to me that someone else did it for SCO - it also counts for them being vaguish...and why Gartner (a strong analyst support of Microsoft products and always has been) is saying to stay away from Linux.

      Microsoft has learnt from it's Netscape/DOJ days and has covered its ass so tight that they can't get caught out on this one or linked I bet. That way they can't be done for anti competitive or monopolisation attempts and in breach of DOJ. Clever Microsoft! Either way Microsoft wins.

      Dave W Pastern

      PS if you reply to this thread can you please email the reply to me at david@dia.net.au - I rarely check /. posts.

      --
      Slashdot can go and get fucked.
    10. Re:Maybe IBM and SCO are colluding by bernywork · · Score: 1

      "Who would trade their company for SCO stock? "

      Simple. People who want out of their business who can ditch the stock straight away.

      If there is enough trading of the stock (turnover) then it's quite possible that they can sell their company, get the hell out, and immediately cash in. Yes, there is some risk to it going downhill fast, but if you can ditch it quickly you might be able to make more money than if you sold the company for cash.

      --
      Curiosity was framed; ignorance killed the cat. -- Author unknown
    11. Re:Maybe IBM and SCO are colluding by raindog2 · · Score: 1

      The interesting thing is that IBM already *has* distributed Linux many times; it was preloading it on PC's for a while, and I'm pretty sure it's them giving you a copy of Linux when you buy that shiny new zSeries.

      Also, have a look at the IBM Linux Technology Center which appears to have lots of patches and other source tarballs available for download from various IBM servers. I think IBM is (like any large publicly owned corporation) best treated with caution, but I also think Linux users are safe from patent claims by virtue of all the stuff IBM's distributing under the GPL.

    12. Re:Maybe IBM and SCO are colluding by bedessen · · Score: 1

      Your theory is somewhat plausible, but you have got to realize that it's quite illegal on multiple fronts: fraud, insider trading, securities fraud, barratry, abuse of the legal system, conspiracy, etc.

      What you are basically implying is that the executives of both IBM and SCO sat down and decided that the benefits of this mastermind plan outweigh all the risks -- getting caught, being exposed, third parties mucking it up, etc. You are essentially accusing IBM/SCO of doing something akin to an Enron-level scandal. You've got to remember that IBM is no fly-by-night company, they're a blue chip that's been around for more than a century. To outright suggest that the management of such a company would take such a huge gamble with its reputation, name, and future is outlandish.

      If I came up with some plan that involved IBM executives cooking the books and "skimming the change drawer" on a massive scale (which is about as illegal and corrupt as the plan you sketched), I would be modded down as flamebait for such a baseless accusation. Yet you put some polish on it and it gets +5 Interesting.

      IBM is not so desperate for cash/influence that they would risk such an outrageous plan. It's just not how you do business at the helm of a blue-chip.

  204. SCO = Calvinball by Fenris+Ulf · · Score: 5, Funny

    I've finally figured out what this SCO debacle reminds me of: a game of Calvinball.

    Contract disputes are legal play, except on Reverse Days or while standing in the Invisible Box. SCO attacks Linux users with FUD, and Novell makes them sing the Sorry Song. But SCO claims Novell was in the Reciprocity Zone, so it has to sing the song instead.

    SCO says it owns IBMs code because IBM crossed the Hidden Contract line, but IBM claims today was negative day and now it wants everything that SCO owns.

    The score is now 12 to Q, and I eagerly await the next round.

    1. Re:SCO = Calvinball by Exatron · · Score: 1

      I always thought it was more like blernsball.

      --
      "I think so, Brain, but 'instant karma' always gets so lumpy." - Pinky
      "Decepticons FOREVER!!!" - Ravage
    2. Re:SCO = Calvinball by meliadus · · Score: 1

      Mornington Crescent!

      --
      "Self-denial is indulgence of a propensity to forego." - Ambrose Bierce
  205. Re:SCO Forum is CANCELED -- NOT! by PB8 · · Score: 1

    It's back. Must have been some hackers messing around just before the big meeting. Or another sly play to get the price to drop a bit then zoon up just before the forum.

  206. NUMA? SGI? by espidre · · Score: 1

    I was under the impression that NUMA code was contributed by SGI when they made their unfortunate leap into linux. At least that is what their marketting at the time seemed to indicate.

  207. Re:McBride? McBriii-ide? Hello? by Obiwan+Kenobi · · Score: 1

    It's McFly

  208. AT&T - Sequent contracts available here by mec · · Score: 3, Informative

    Exhibit F
    Exhibit G

    I agree with the meat of your analysis about Sequent. I don't know enough contract law to comment on SCO's thesis about Sequent.

  209. small claims anyone? by RouterSlayer · · Score: 1

    Y'know small claims court is only $45.
    I'm sure some of the /.ers can afford that.
    Why don't some of us sue them for extortion?
    I'm sure some of the developers here would have
    something to lose if this nonsense continues much
    longer.

    -things that make you go "hmmmmmm"

  210. Hahahahaha ! by Anonymous Coward · · Score: 0

    Finally we found the scum who is responsible for vi !

  211. Sequent by Zathrus · · Score: 3, Insightful

    For those who don't know, Sequent was a super-computer company that developed a lot of the software techniques that make today's multi-processor machines (especially the more-than-2 processor systems) work well.

    Not just a super-computer company... they also built high end Unix servers. Georgia Tech had a Sequent box running Dynix as the main campus computer system from the late 80's to early 90's. IIRC, hydra was a 16-CPU system with 386DX's. And while at the end of its life (1993 I think) it was godawful slow, it was still better than the Sun box (which later became boxes) that replaced it (GT and Sun discovered that Solaris did very poorly in a heavily task switched environment, spending up to 80% of CPU time in overhead... that's improved since, but AFAIK they never quite fixed the problem). Dynix was the first Unix OS I ever used. It was a helluva lot better than Ultrix, but that's about all I recall about it.

    at first glance IBM has every right to contribute this code to Linux

    Yeah, but SCO is claiming that Sequent's license didn't include transferral of license, that the various multiprocessor technologies were derivative works, and that SCO retained rights to all derivative works under that license. IBM did buy a perpetual, non-revokable, fully paid, yadda yadda yadda license for Unix, but that was prior to the purchase of Sequent. SCO is thus claiming that Sequent's license holds true here and that IBM didn't have the right to distribute the code without SCO's approval. IBM does, however, hold the patents to the technologies in question. It may become a question not only of which license applies, but also whether or not the code contributed to Linux was the same as the code that Sequent had or if it was a re-implementation of the patent that IBM holds.

    1. Re:Sequent by SmackCrackandPot · · Score: 2, Informative

      The Opensource organisation have an evolution chart. This is a simplifed version from the UNIX timeline history. Bang up to date as well (July 31st is the most recent update). It's in a similar style to those civilisation charts that nearly every History teacher has pinned on the wall. Looks like one civilisation is about to become extinct.

    2. Re:Sequent by TurnYourRadioOn · · Score: 1

      Yes, but there are two more clinkers: (1) the amendment to IBM's original licensing deal with AT&T, which antedates SCO and gives IBM the right to do as they please with their work in connection with Unix, and (2) the third party in the IBM-SCO licensing arrangement, Novell, who apparently retain veto rights over SCO's actions, and already exercised their veto back in June. The pit of problems that SCO has to climb out of to make their lawsuit succeed just keeps getting deeper and deeper...

    3. Re:Sequent by Platinum+Dragon · · Score: 1

      It may become a question not only of which license applies, but also whether or not the code contributed to Linux was the same as the code that Sequent had or if it was a re-implementation of the patent that IBM holds.

      The argument may eventually come down to whether 12-line chunks of code, reimplemented, are a copyright violation. It's not bloody likely that the Sequent-written multi-processor control code for Dynix would work in Linux were it simply dropped in wholesale, but it's quite possible, even probable, that chunks of code (perhaps even eighty lines long... hmmmm...) need to be similar, due to the nature of the Sequent implementation that IBM purchased along with the company.

      My guess: SCO is claiming entire files are copyright violations, when in reality only certain small chunks of code are similar. Some files may be very close to source files from Dynix's multiproc implementation, due to factors common to multiproc-capable operating systems. If IBM can prove that the code written for Linux is based solely on a theoretical document with possible examples, and not actual Dynix source files, SCO is fucked, hard. SCO's complaint about "UNIX development methods" sounds like a reference to exploratory theoretical documents that some other posters said were written by a Sequent employee before such functionality was implemented in any OS. Unless there's something very wacky in Sequent's contract with AT&T that goes beyond handing source code rights over to the owner of SysV, SCO is desperately fishing for a case here, even more than before. This also demonstrates that their press releases are the stuff of pump-and-dump schemes, puffery and bluster about subject completely unrelated to what they're claiming in court.

      At first, the details seem to possibly damn IBM for dropping code they didn't control into Linux, but IBM only has to prove the Linux code is simply a new implementation based on a source common to Dynix, AIX, and Linux--examples and theory documents.

      --

      Someday, you're going to die. Get over it.
    4. Re:Sequent by 10Ghz · · Score: 1
      Yeah, but SCO is claiming that Sequent's license didn't include transferral of license, that the various multiprocessor technologies were derivative works, and that SCO retained rights to all derivative works under that license.


      If that's the case, why hasn't that scalability-code appeared in SCO's UNIX-offerings? They claim that Sequent/IBM contributed hi-end features to Linux that were really property of SCO. They claim that while their own flagship product lacks those very same features.
      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    5. Re:Sequent by Zathrus · · Score: 1

      Because they still don't have the patent rights.

  212. Damn, *that's* interesting by siskbc · · Score: 4, Insightful
    IBM and SCO make it known that IBM is thinking of buying SCO. Instead, SCO sues IBM. SCO's stock price goes up. SCO's owners dump stock (getting rich) and SCO uses the inflated stock price to buy up small companies. Once SCO has all the pieces in place, IBM suddenly forces things into court and SCO is blown away. SCO stock plummets. *THEN* IBM buys them for a basement bargin price.

    I tell ya, it's definitely wacko, but it's not completely retarded, I have to say that. The one key is that when SCO does all this buying up of small companies, it would have to be done with SCO *stock* - I'm sure that's what you intended - which would actually be plausible in their situation, since they're a stock-rich/cash-poor company.

    There are two problems I see with the theory. First, I don't see SCO taking over any small companies right now. ;) Second, the time frames are a little off. SCO would need time to perform all these takeovers, as those never proceed quickly. Second, IBM can't afford the lawsuit spectre to last too long, as there's the threat that companies will get scared of linux and such, fleeing into the arms of Sun or MS. That would make the whole scheme counterproductive.

    So I don't think that's what's going on here. That said, it *is* a pretty nice scheme, and I wouldn't be surprised to see it pop up elsewhere, assuming it hasn't already. I think it would be outrageously illegal, but might not be impossible to pull off. The only real problem I see from a practical standpoint is trust - when the lawsuits start, puffing up the value of the smaller company to be taken over, they gain an advantage that could be acted upon if they decide to make the fake lawsuit real.

    They'd almost have to give the larger company some faked "smoking gun" evidence that gave them a clear "out" of the lawsuit, if filed. In this situation, it would be like some SCO developer last year sending a memo saying something like, "Hey, have fun with the JFS code I posted to the kernel dev team yesterday. Free of charge compliments of Caldera."

    But I will say, it's not impossible.

    Man, I have got to stop drinking 10 diet cherry cokes while on medicine for a head cold before I post. =)

    I think that would be a good policy for sure.

    --

    -Looking for a job as a materials chemist or multivariat

    1. Re:Damn, *that's* interesting by Pharmboy · · Score: 1

      There are two problems I see with the theory. First, I don't see SCO taking over any small companies right now. ;)

      Actually, they are. Computer World published and article on it called SCO's Shell Game. Also found other tidbits while Googling(tm) around. They make a claim, their stock goes up, they issue new shares and buy stuff by trading the new shares.

      Now, I don't say the parent is absolutely correct, but there is some real validity to his claims. Not necessarily probable, but very possible. The parent is not that far off my line of reasoning.

      --
      Tequila: It's not just for breakfast anymore!
    2. Re:Damn, *that's* interesting by WEFUNK · · Score: 1

      I will second your opinion that the original post is "Damn" interesting (along with your follow-up) but I will add one more problem with this theory: by taking on and incurring the wrath of so many third parties, SCO has probably added to much potential liability for anyone who buys them out.

      I actually argued in a previous post (earlier story) that IBM should buy SCO out at a ridiculously low price, partly to spite SCO's management and partly to avoid any potential cover-up in a settlement. But now I disagree: if IBM bought them out now then just about anyone involved with Linux or who has delayed Linux deployments would have a legitimate beef with the new IBM/SCO and could even point to IBM's case as an admission of guilt by IBM/SCO.

      Great theory otherwise, and probably a less uncommon situation than we'd prefer to believe.

      --
      My next sig will be ready soon, but friends can beat the rush!
  213. The Current SCO Situation...via the medium of song by Gourou · · Score: 1

    The Current SCO Situation...via the medium of song

    Please mirror and spread if you agree with the sentiment (if not the singing :-)

    The Asshat Song [heypod.co.uk] [2.73MB MP3]

  214. Re:McBride? McBriii-ide? Hello? by Anonymous Coward · · Score: 0

    McFried?

  215. Next claim by SCO? stop breathing or we sue! by Viduliya · · Score: 1

    I believe to be a PUMP-N-DUMP scheme for SCO stocks just before all the SCO execs leave the country to retire. When SCO lose the current law suite and if they live long enough for another, then this will likely be SCO's next extortion scheme.


    To all those in violation of SCO intellectual property by "breathing":

    Unless you pay SCO One Billion Dollars for Licensing "breathing" you will be sued! We have proof that you are in violation of our intellectual property. This violation occurs in the sub-process "inhale". But, we will not show it to you specifics, instead we will just sue unless you stop "breathing" immediately this moment we will sue you!

    Really we will, unless you already paid us. If you have paid then go right ahead and "breath" we give you permission to go right ahead and proceed breathing until the next time we decide to sue you for "exhaling".

    Have a nice day.

    -SCO

  216. SCO's legal approach - derived work by Animats · · Score: 5, Interesting
    It's starting to become clear what SCO's lawyers are thinking. They're laying the groundwork for a broad claim of copyright coverage of a derived work.

    What constitutes a derived work is going to be the real copyright issue here. Outside the software arena, the notion of a derived work has been very broadly interpreted. Movies based on novels have been held to be derived works even when the connection between the two included little more than the title and the name of the lead character.

    IBM has retained Cravath, Swaine, and Moore, probably the strongest litigation firm for difficult cases in the world. The Cravath approach on big cases is to put an army of lawyers on the problem and litigate everything to death. We'll probably see a detail-oriented litigation, rather than one based on broad principles. Following a Cravath lawsuit tends to be a mind-numbing experience for all concerned.

    1. Re:SCO's legal approach - derived work by Oswald · · Score: 1

      In your opinion (I'll keep in mind that's all it is ;), would this indicate that IBM perceives a lack of broad principles on which it might base its case, or a pragmatic desire to crush these bugs in the most expedient way available?

    2. Re:SCO's legal approach - derived work by Darken_Everseek · · Score: 1

      IANAL, of course, but it would seem a detail oriented case is designed to drag the lawsuit out as long as possible.

      Failing the summary judgement which I'm sure IBM is hoping for, I think they're going for a war of attrition; which is probably the most sound strategy. Versus SCO, they're not capable of losing one; regardless of the principles or the judge.

  217. Don't like SCO? Give 'em a call... by Anonymous Coward · · Score: 1

    From the termination announcement:

    "Blake Stowell, +1-801-932-5703, bstowell@sco.com, or Marc Modersitzki, +1-801-932-5635, both of The SCO Group"

    Better yet, get your autodialing modem to call...

  218. A question SCO Group forgot to ask.... by linuxislandsucks · · Score: 1

    A question SCO Group forgot to ask was..

    What happens when Novell terminates the Unix sales contract with SCO Group?

    I have guess...

    Profits and their Price goes ..

    DOWN!!!!!!!

    --
    Don't Tread on OpenSource
  219. Resulting Materials by Tussinator · · Score: 3, Insightful
    From the press release:

    SCO's System V UNIX contract allowed Sequent to prepare derivative works and modifications of System V software "provided the resulting materials were treated as part of the Original [System V] Software."

    The Resulting Material of Sequent's modifications was Dynix/tx. The components of that modification were SysV, RCU, and NUMA.

    Being only two of the components of the modification, I don't see how SCO has the right to apply SysV licensing terms to any future use of Sequent-IBM's RCU and NUMA technology.

  220. Don't you just love these SCO discussions? by Anonymous Coward · · Score: 0

    It is the only way to get positively moderated for flaming or just being vulgar

    Thanks SCO for making me laugh like a fool every day I see the Caldera logo.

  221. Re:Actual transcript smuggled out of the courthous by geekoid · · Score: 1

    that is the best peiece in the monty python game. heh.

    --
    The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  222. Wait that's pretty drastic! by Anonymous Coward · · Score: 0

    Shouldn't IBM be given "Double Secret Probation" first?

  223. my favorite SCO post yet by Anonymous Coward · · Score: 0

    In reference to this thread:

    http://gcc.gnu.org/ml/gcc/2003-07/msg01564.html

    Kean Johnston, Engineer @ SCO (for at least 6 years), writes:

    ---

    >> Err... I think the L in GNU GPL stood for License.

    And I thought the GP was general public, not "general public we like, agree with politically, socially or morally".

    For obvious reasons I can comment very little on what has gone on in this thread although my restraint has been the hardest thing I have had to endure in along time. All I can say is I encourage people to think about the words "open", and to look at the real scope of SCO's lawsuits not at reactionary, often misguided and religiously "patriotic" assertions made in the heat of passion and not in the cold light of logic.

    I really wish I could say more but I can't. I may have said too much. But in these postings please can people remember that many of the folks at SCO are just geeks like the rest of you, who use, like and contribute to open source projects.

    ---

    Sounds like their might be some conflict between the "fellow geeks" working at SCO, and the management. It also seems like even the programmers at SCO have no idea what the GPL means.

  224. The movie hit of 2004 by bobeszcica · · Score: 1

    Terminator 4: The Final Termination

  225. Re:McBride? McBriii-ide? Hello? by Anonymous Coward · · Score: 0

    i'd really be interested in McBride doing a slashdot interview. if he's so confident of his case, he should have no problem facing those of us who are affected.

  226. But that one never works! by dacarr · · Score: 2, Funny
    McBride: Rocky, watch me shut down IBM's license to use Unix!

    Rocky the Squirrel: Again?

    McBride: This time for sure!

    Rocky: But that one never works! McBride: Nothing up my sleeve, and.. PRESTO! (pulls out a copy of Debian)

    Rocky: And now here's something we hope you'll really like!

    Bullwinkle: (carries a clue-by-four with IBM written all over it, beats McBride)

    --
    This sig no verb.
  227. There is no such entity as Sequent-IBM by walterbyrd · · Score: 2, Interesting

    Yet Caldera-Sco uses the term "Sequent-IBM" no less than six times in that press release. I guess Caldera-Sco is getting desperate.

    If this press release were about only Sequent, it wouldn't make sense - there no longer is any Sequent. If this press realease were only about IBM, it woulnd't make sense - that press release went out months ago.

    But since this press release is not about IBM or Sequent, but about "Sequent-IBM" it all makes sense, right?

  228. MINUX was (C) so Linux = theft from the beginning by Anonymous Coward · · Score: 0

    MINUX was (C) so Linux = theft from the beginning. Quid ex post facto pro

  229. IBM should kill their SysV-based OSes by Anonymous Coward · · Score: 0

    They should be base their new OS on a BSD OS.. bring it up to UNIX 03 Standard and add support for any non-standard implementations to better support older AIX software, get a few certifications on standards they support.

    They can provide bugfixes back to the original project, new features they want to give away, and keep their code closed. Any software that had been distributed with a OS based on SysV should be challenged as not being a derivative, and is a software for UNIX. Any code that is a derivative, rewrite it from scratch. IBM won't have to care about future code they write, being infected with contracts by SCO.

  230. Sequent Culture by crucini · · Score: 1

    That sounds like a way more interesting story than yet another SCO dropping. Why don't you write it up and submit it here or on kuro5hin?

  231. Hey morons DO SOMETHING ABOUT IT by eadint · · Score: 1

    If you are a lawyer could you point out how i could file a small claimes cour suit against them. what grounds would i use and the general procedure.

    Stop complaining and put you money where your mouth is.
    I am tired of this SCO crap. When are you people going to stop whining and do something about it. If you have contributed to the Linux kernel, sue SCO for damaging your product and under the terms of their claims they owe you for licensing. If you have been given an invoice from SCO, sue them and report them for extortion. If you have bought a license, sue them for false advertising. Whining about it on slash dot will accomplish absolutely 0, bubkiss, dittly. This is the only way to strike back at a company that uses litigation as a business model. Use litigation to counter them. There is not other way to stop SCO. There were allot of people that said fascism, Stalin and Hitler were bad people, but nobody actually did anything about it (until it was too late) so my fellow slashdotters, before you post one more reply to an SCO article, why don't you put you money where your mouth is file a small claims court. against SCO, and then comment about that.
    If there are any lawyers out there please write how to do that or point to the relevant documentation.

    1. Re:Hey morons DO SOMETHING ABOUT IT by classic66coupe · · Score: 0

      people usually glady take advice from someone who calls them a morons - fyi (sarcasm)

  232. Change of subject by Anonymous Coward · · Score: 0, Redundant

    It is interesting how this follows recent reports of SCO executives selling off their own SCO stock...
    Media manipulation anyone?????

    1. Re:Change of subject by MImeKillEr · · Score: 1

      And as such, there should be a law barring people from being able to sell stock that has increased in value due to a lawsuit, unless you're not a current HCE (highly-compensated employee. eg. CIO, CEO, CFO, etc).

      --
      Cruising the internet on my TI-99/4A @ a whopping 300 baud!
  233. SCO is really getting desperate by m.dillon · · Score: 3, Interesting
    SCO is really getting desperate. They've cried wolf so many times now that even the stock speculators have finally caught on. Their stock price hardly blipped at the latest announcement. SCO is fast running out of curve balls to throw.

    In fact, IBM addresses both the issue of the stock price manipulation and SCO's continued misrepresentation of the AIX license in their counterclaim. For SCO to continue to make these sorts of public statements is insane.

  234. 168,276 lines of code by Anonymous Coward · · Score: 1

    Yeah Right!!! Surely SCO is counting system calls. For every fork() you use you own SCO $0.10.

    Eki

  235. You are being disingenuous by FreeUser · · Score: 1

    I mentioned this briefly in the post you are replying to. You even quote it later on. Granted, I said "less likely" and not "impossible", but you agree that it's not impossible. How was I asleep?

    When you said:

    Rewriting Linux now will not do a damn bit of good. It doesn't absolve anyone from past infringements, and it won't mean that IBM did not breach their contract.

    Rewriting Linux does a great deal of good (assuming the very unlikely for the sake of a theoretical argument, namely that there is infringing code in Linux), as it stops the infringement. Furthermore, as has been pointed out (and IMHO your choice of verbiage seriously downplays), Caldera-now-renamed-SCOs own actions does make it impossible to collect damages of any kind (I merely included the extremely remote possiblity of a lower court judge making a foolish ruling in contradiction of basic civil law, which is extremely rare but can happen. I would go so far as to say it is virtually impossible that SCO would prevail at the appellate level even under those extremly unlikely circumstances).

    I find your initial description "all the non-disclosure will have done" to be disingenuous (it implies a slight change in liklihood, dismissing the overwhelming, fundamental nature of the precidents as they relate to SCOs unconscionable actions and unwillingness to discose), and your spinning of my "well, a judge can do anything" as tacit agreement of your apparent dismissiveness likewise misrepresentative of what I was saying.

    --
    The Future of Human Evolution: Autonomy
  236. SCO is fundamentally wrong in charging Linux users by Zapdos · · Score: 1

    When a book publisher copies text from another book publishers published works. The book publisher that has been plagiarized sues the offending book publisher. They do not hunt down and charge fees to every one who purchased or read the offending work.

  237. SCO's definition of derived work. by EMR · · Score: 1

    This whole case seems to be an issue of what a derived work it.. This is what seems to be SCO's definition to me. (metaphore to cars)

    OK.. I design a cool spiffy car radio that I let GM use in their cars... so all GM cars have this cool car radio.. But then I decide to take my cool car radio and decide to give it to Volkwagon later.. but GM says I can't do that because my car radio is a derived work of GM cars..

    *DISCLAIMER* The car company names were chosen at random and have no bearing on the morality of said car companies.. Personally this commentor doesn't even own a car.

  238. But! by Anonymous Coward · · Score: 0

    Even assuming IBM is violating Sequent's license, and assuming that SCO is the legally aggrieved party, it in no way invalidates their separately made AIX license. So SCO is still in the wrong.

  239. Stock Statistics by koa · · Score: 2, Insightful

    I don't know if anyone else hase a different viewpoint on this, but I was just looking at the stock graphs and comparing the fluctuations between SCOX and IBM and also RHAT stock indexes. How come IBM and RHAT stay very constant while SCOX seems to raise but is extremely erratic? Wouldnt logic dictate that if the market beleived SCO's story (by buying stock) then the IBM and RHAT should take even a small dive becuase of this? But they dont.

    Just looks weird to me.

    --
    ....move along....nothing to see here....
  240. who reviews the code? by Anonymous Coward · · Score: 0

    Are there coders that still work for SCO (and therefore lost their souls) that are reviewing Linux sources? Couldn't two developers find two identical solutions to the same programming problem? Sounds too easy to say some code belongs to them when only one side has open sources...

  241. senator joe mccarthy said it best: by wolftone · · Score: 1

    regarding the "approximately 148 files" "I have in my hand fifty-seven cases of individuals who would appear to be either card carrying members or certainly loyal to the Communist Party..." (1950)

  242. No really by wafflemonger · · Score: 2, Funny

    Your lisence is up when I count to three. One. Two. Two and a half. Two and three quarters. Two and seven eighths . . .

  243. How conveinant by pair-a-noyd · · Score: 1

    that the stock took an upturn.
    Let's see who's selling today, eh??

    Also watch as this story on /. gets more attention, you'll see the stock go down.

    No kidding..

  244. No no no, it's just like Terminator DVD's by webslacker · · Score: 1

    First they release the regular edition Termination

    Then they release Final Termination

    Then it's Ultimate Termination with extra litigation that was cut from the original edit

    Afterwards they do a new transfer with digital restoration (letters are easier to read) and call it Extreme Termination!

  245. Didn't get it wrong? by Anonymous Coward · · Score: 0

    catch(ImpendingIBMSuit suit);

    that semicolon is a touch misplaced.

    1. Re:Didn't get it wrong? by classic66coupe · · Score: 0

      hehe, that rocks.

  246. What could they do to get IBM to switch sides by Thiarna · · Score: 2, Interesting

    Looking at this little dispute, the only real risk that strikes me is if IBM decide to support SCO/Caldera's interpretation of the copyright, licenses and patents involved. They would not have to just give in, but could end up with ownership of some of the software in question, on condition they demand license fees or just stop their support of OS development. It just occurred to me they might be trying to get IBM to score some sort of own-goal. Is there any way that either by defeating the SCO suits, or winning their own, that IBM could impair their own property rights in some way? Possibly not against SCO, but maybe in some seemingly unrelated matter against Microsoft.

    Of course I have no evidence that even suggests anything along these lines, just that historically IBM have been one of the main "big evil corporations", and I'm not sure if they have changed completely. And the conspiracy theorist in me can't accept this whole fiasco is just a case of securities fraud.

  247. Re:Actual transcript smuggled out of the outhouse by ftg888 · · Score: 0

    SCO EXEC's sell stock. SCO BASED Computers Implode SCO Source Code Turns Into a Rampant Virus Bent on the distruction of WINDOWS PRODUCTS.. /dev/earth is 98% full...please delete someone soon.

  248. Where's the Code Ownership Clause? by grendelkhan · · Score: 1

    The only thing mentioned about unauthorized distribution in these are where it says that Sequent cannot distribute modified or unmodified copies of the code licensed from AT&T. There isn't dick in here about who own new code that is attached to the code licensed from AT&T.

    Game. Set. and Match. IBM.

    --
    Wu-Tang Name: Half-Cut Skeleton Get your own Wu-Na
    1. Re:Where's the Code Ownership Clause? by Edward+Scissorhands · · Score: 1

      Look at Section 2.01 of Exhibit F. Derivative works fall under the contract terms.

    2. Re:Where's the Code Ownership Clause? by dbrutus · · Score: 1

      Look at Section 2.03, IBM's modification letter, accepted by AT&T, is valid and thus all the Sequent written code is transferred right back over as it then would come under the terms of the IBM/AT&T license.

    3. Re:Where's the Code Ownership Clause? by Edward+Scissorhands · · Score: 2, Insightful

      Well that's just what the court case is all about, right? I mean, I never meant to suggest that, in fact, SCO was right or anything, I was merely outlining where I thought that the debate would take focus. If it's true that the IBM/AT&T agreement takes precedence over the Sequent/AT&T agreement even when talking about code developed at Sequent and put into Dynix before IBM bought Sequent, then I think that's great. Personally, I'd like SCO to FOAD. My point is that I don't know what the contract law says about this situation, or even if it says anything at all. That's all I'm saying. But my desire for a clear headed analysis forces me to put aside my dislike for SCO and just examine the situation as I see it, that's all I'm saying.

    4. Re:Where's the Code Ownership Clause? by grendelkhan · · Score: 1

      And does this qualify as a modification or an addition? If you're making somthing that exists better, that's modification. If you're adding features that were not present in the initial codebase (things like NUMA and RCU that the USPTO thought was original enough to grant a patent to), then does that fall under the same heading as a modification?

      Again, I don't know, just asking.

      --
      Wu-Tang Name: Half-Cut Skeleton Get your own Wu-Na
    5. Re:Where's the Code Ownership Clause? by Edward+Scissorhands · · Score: 1

      Well my inclination in this case is to say that it doesn't matter. I think once it's put into Dynix, it falls under the agreement. It's a tough contract, to be sure, but the responsibility falls to the signing parties to make sure that the terms of the contract are agreeable. Maybe Sequent just didn't have a very good bargaining position against AT&T, so they couldn't get the same amendment that IBM got. Maybe their lawyers just didn't pay close enough attention or just didn't care. Who knows? I guess if there's something that can be learnt from this, it's never to "sell your soul" when it comes to intellectual property. Always try to retain ownership of the work you do. I guess it's a principle thing-- don't sell out. If you're being offered a contract where you don't like the terms then never hesitate to walk. Stick to your principles, and you'll always be covered.

    6. Re:Where's the Code Ownership Clause? by dbrutus · · Score: 1

      The problem is that it isn't just a court case but also something akin to corporate blackmail. The Unix codebase is so widespread that even if SCO only has a 1% chance of winning it makes rational economic sense to settle and pay for the likely unneeded licenses if the cost to license is less than 1% of the damages a lawsuit would create.

      As long as that money is enough to pay the salaries of the 350 SCO employees, they'll continue this forever. That's not advancing the arts and sciences but engaging in criminal racketeering.

    7. Re:Where's the Code Ownership Clause? by dbrutus · · Score: 1

      When IBM bought Sequent they sent a letter to AT&T regarding the Sequent code. The letter specifies that the Sequent code should be handled under the IBM license agreements from then on. AT&T accepted the letter and the matter was settled. Such a letter is permitted under the Sequent contract under section 2.03.

      This maneuver is a major loser for SCO and the only benefit that they can possibly get is licensing revenue from people who have too much at stake to risk even the miniscule chance that SCO will win. SCO is engaging in blackmail, building their business plan around it, in fact. They're turning into a criminal enterprise as they've failed at being a computer company.

  249. How about sco.slashdot.org by Anonymous Coward · · Score: 0

    Well, there is enough stuff about sco to fill a new server, right? right?

  250. In related news by sdcharle · · Score: 3, Funny

    A panhandler announced the termination of a passersby's right to wear pants in public when the man refused to pay him a $1 'pants tax'.

  251. Computer Associates 497 of Fortune 500 by Anonymous Coward · · Score: 1, Interesting

    isn't Computer Associates a Fortune 500 company?
    they just settled a lawsuit with the Canopy group with the no details disclosed.

    do they run linux?

  252. Re:McBride? McBriii-ide? Hello? by Anonymous Coward · · Score: 0

    That's it, I'm going to fucking kill you.

  253. This is getting very, very repetitive... by titzandkunt · · Score: 1


    1) Who's to say SCO didn't steal the code, hmm?


    2) But they distributed it under the GPL!!!


    3) It's a pump 'n' dump, pure and simple.


    4) Bill's mighty hand is behind all this...


    5) Darl is an ass!


    6) etc, etc, etc...

    How the fuck did the parent get modded insightful, fer chrissakes?

    T&K.

    --
    Political language ... is designed to make lies sound truthful and murder respectable...
  254. Re:McBride? McBriii-ide? Hello? by Anonymous Coward · · Score: 0
    No it isn't. Check the script (available everywhere) and the IMDB:

    "Michael J. Fox .... Marty McBride"

    YOU'RE WRONG, MCBRIDE.

  255. SCO don't need the law? And code has been named! by theolein · · Score: 1

    SCO's termination of the Sequent-IBM UNIX System V license is self-effectuating and does not require court approval.

    WTF? SCO now no longer needs the law? My gut reaction to this would be that SCO is desperately trying to push up the stock price in the face of the IBM/RH countersuits handed out last week, but on second thoughts I noticed that now SCO has finally named the offending code.

    This all boils down to the question of what a derivative work is and whether SCO has any control whatsoever over code bought by IBM. It makes me realise that SCO has a better chance in court than we previously thought.

    This is the time for the kernel developers to remove the NUMA and RCU code and get cracking on alternatives.

  256. Dunno if anyone else noticed this... by korny69 · · Score: 1
    whois sco.com

    [whois.internic.com]
    ...

    Expiration Date: 02-sep-2004
    ...



    Gee, that is about how long I thought this would all last. If they are not even registering their domain for longer than a year, maybe they do not plan to be around in a year?! <insert loud music: dum dum dum>

    --

    The biggest security hole sits between the keyboard and chair.
    -Andrew McAllister

  257. What SCO is doing... by slewfo0t · · Score: 2, Insightful

    It looks to me that their whole approach here is to try to claim that Linux is a direct derivitive work of Unix... They are similar, But I don't know if it will fly in court. It would be like saying that Open Office is a derivitive of MS Office. Same kind of thing I suppose...

    This whole thing with code has me baffled too... what did they do, claim that all the for...next loops are theirs??? How far can they can take this stuff?

    - Slew -

  258. SCOForum 2003 Sponsors by Anonymous Coward · · Score: 1, Informative

    Maybe people should write letters to the following companys that are sponsoring SCOForum 2003, telling them you will no longer do business with them, as long as they support SCO.

    List of Sponsors:

    Hewlett-Packard
    CRN
    Microlite Corporation
    Century Software, Inc.
    Lone Star Software
    DTR Business Systems
    Digi International
    TeleVideo
    Multi-Tech Systems
    InoStor
    Open Systems
    Rasmussen Software, Inc.
    Tarantella
    Equinox Systems
    Maxspeed Corporation
    TelSoft Solutions
    BASIS International
    Vultus, Inc.
    Synergetic Data Systems, Inc. (SDSI)
    fP Technologies, Inc.
    TAKGroup

  259. Re:NUMA and RCU? Then why... by Ian+Lance+Taylor · · Score: 1

    The code for NUMA and other multi-processor stuff is the basis for SCO's complaint against IBM.

    It isn't the basis for SCO's claim that Linux infringes on SCO's IP. That is based on code which SCO claims has been directly copied from Unix into Linux. This code has only been revealed under NDA. It is not NUMA, etc.

  260. Some UNIX code in Linux... by Anonymous Coward · · Score: 1, Informative

    I found some similar code from System III in Linux
    This code can not be found in BSD 4.4...

    I think ate_utils.c is known but there are some
    similar .h files

    I have the full report but is long enough to fit here
    just use diff

    If you do not have System III source, it can be found
    on the Net as sys3.tar.gz /2420/arch/ia64/sn/io/ate_utils.c - /sys3/usr/src/uts/pdp11/os/malloc.c; /sys3/usr/src/uts/vax/os/malloc.c /2420/drivers/macintosh/macserial.h - /sys3/usr/include/sys/reg.h; /sys3/usr/src/head/sys/reg.h /2420/include/asm-mips64/termbits.h - /sys3/usr/include/sys/tty.h; /sys3/usr/include/termio.h; /sys3/usr/src/head/sys/tty.h; /sys3/usr/src/head/termio.h /2420/include/asm-ppc64/termbits.h - /sys3/usr/include/sys/tty.h; /sys3/usr/include/termio.h; /sys3/usr/src/head/sys/tty.h; /sys3/usr/src/head/termio.h /2420/include/asm-ppc64/termios.h - /sys3/usr/include/sys/ttold.h; /sys3/usr/src/head/sys/ttold.h /2420/include/asm-s390x/errno.h - /sys3/usr/include/errno.h; /sys3/usr/src/head/errno.h /2420/include/asm-s390x/termbits.h - /sys3/usr/include/sys/tty.h; /sys3/usr/include/termio.h; /sys3/usr/src/head/sys/tty.h; /sys3/usr/src/head/termio.h

  261. Stop! Or... by weston · · Score: 1

    I'll say stop again!

  262. Re:McBride? McBriii-ide? Hello? by Anonymous Coward · · Score: 0

    No shit, doofball. I bet you're gullible enough to buy a subscription too.

  263. Did SCO sue Jesus yet? by gelfling · · Score: 1

    WKOLWJGFS

    What kind of lawsuit would Jesus get from SCO?

  264. very informative by siskbc · · Score: 1
    Actually, they are. Computer World published and article on it called SCO's Shell Game. Also found other tidbits while Googling(tm) around. They make a claim, their stock goes up, they issue new shares and buy stuff by trading the new shares.

    Nice article! And they did it just like I figured - acquisition using their newly valuable stock.

    Naturally, this doesn't mean IBM is in on it, but it does support the idea that SCO was just using this ruse for free money. Clearly they're using their stock price to get stuff for free.

    Now, I don't say the parent is absolutely correct, but there is some real validity to his claims. Not necessarily probable, but very possible. The parent is not that far off my line of reasoning.

    Like I said, there was a lot of interesting stuff in his post. He was right on (evidently!) about SCO using their "smoke and mirrors" stock price to acquire real assets.

    --

    -Looking for a job as a materials chemist or multivariat

    1. Re:very informative by Pharmboy · · Score: 2, Funny

      Naturally, this doesn't mean IBM is in on it, but it does support the idea that SCO was just using this ruse for free money. Clearly they're using their stock price to get stuff for free.

      Perhaps that is the goal: You realize your company is worth $100 (example, easy math). You convince everyone it is worth more, say $1000. You take the $900 in extra stock you just issued, and buy $900 worth of real companies. In the end, your company is theoretically worth $1900, until you lose your lawsuit, at which time it is back to worth $900 purely because of the assets you purchased. Now, the key is to sell when it is as close to $1900 as possible, but anything between $900 and $1900 is worth your time, especially if you don't really own the stock, just the options, thus not costing you anything. You CAN get rich doing this, but it involves one extra step.

      This is the critical part: You have to start writing your new book WHILE you are in prison, not after you get out. This works out pretty well because you will have lots of free time in between sodomy sessions. The good thing is you don't have to pretend your innocent anymore, those books don't sell anyway. Instead, write about how you learned from the experience, and how its really "the systems" fault, because it was so easy to do. So, instantly, even though YOU did it, you can blame the system, sell some book, probably get a great consulting gig or go on a speaking tour, and you will probably only have to spend 3 to 5 years actually in jail.

      --
      Tequila: It's not just for breakfast anymore!
  265. Re:Stock Statistics Like who bought! by ratfynk · · Score: 1

    It would help if the actual SCO purchasers were named. I think you would quickly find some slush funds doing the SCO buying. I just wonder who owns the funds. A few MS dot com instant millionaires per chance? Someone is buying up SCO and it is not small time speculators or mutuals it is people who do not care about margins, thats for sure. Just wish some jounalist could find out and let the cat out of the bag. Might even prove to be a little interesting as to how the SCO exes are getting big money out of the law suit, and who put them up to it. I hope the AG in New York is looking into this right now. These dot com morons might get their ass kicked, would you hire an ex-SCO exec? I still think they shot all their accounts before doing this number, something Martha Stewart most likely did also.

    --
    OH THE SHAME I fell off the wagon and use sigs again!
  266. Must... Resist... Dark Side... by Anonymous Coward · · Score: 0

    SCO is dying
    ------------

    It is official; Netcraft confirms: SCO is dying

    One more crippling bombshell hit the already beleaguered SCO community when IDC confirmed that SCO market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that SCO has lost more market share, this news serves to reinforce what we've known all along. SCO is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.

    You don't need to be a Kreskin to predict SCO's future. The hand writing is on the wall: SCO faces a bleak future. In fact there won't be any future at all for SCO because SCO is dying. Things are looking very bad for SCO. As many of us are already aware, SCO continues to lose market share. Red ink flows like a river of blood.

    OpenServer is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time OpenServer developers Ransom Love and Mike Krotch only serve to underscore the point more clearly. There can no longer be any doubt: OpenServer is dying.

    Let's keep to the facts and look at the numbers.

    OpenServer leader Darl McBride states that there are 7000 users of OpenServer. How many users of UnixWare are there? Let's see. The number of OpenServer versus UnixWare posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 UnixWare users. SCO/OS posts on Usenet are about half of the volume of UnixWare posts. Therefore there are about 700 users of SCO/OS. A recent article put UnixWare at about 80 percent of the SCO market. Therefore there are (7000+1400+700)*4 = 36400 UnixWare users. This is consistent with the number of UnixWare Usenet posts.

    Due to the troubles of Walnut Creek, abysmal sales and so on, Caldera went out of business and was taken over by Tarantella who sell another troubled OS. Now Tarantella is also dead, its corpse turned over to yet another charnel house.

    All major surveys show that SCO has steadily declined in market share. SCO is very sick and its long term survival prospects are very dim. If SCO is to survive at all it will be among OS dilettante dabblers. SCO continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, SCO is dead.

    Fact: SCO is dying

    1. Re:Must... Resist... Dark Side... by borgheron · · Score: 1

      Isn't this the same form-filled posting that I see for BSD some of the time??

      Not that I don't hope that it's true, mind you.

      GJC

      --
      Gregory Casamento
      ## Chief Maintainer for GNUstep
  267. Sequent, not IBM by msobkow · · Score: 2, Informative

    The issue is that Sequent developed the RCU code for Dynix/ptx (their SVR4/BSD personality hybrid) after publishing papers and submitting for patents on the related algorithms. The RCU code in Dynix/ptx is only an implementation of the IP, not a transfer of the IP itself.

    All SCO has acquired is the right to use and distribute the RCU implementation Sequent deployed as part of Dynix. It does not transfer ownership of the RCU algorithms and patents to SCO, though it probably implies SCO has a perpetual right-to-use the RCU algorithms as implemented in Dynix.

    SCO needs to prove that IBM used the Dynix implementation verbatim for AIX or Linux, rather than using code developed from the research papers and patents they acquired via Sequent. Further, they'll need to show that the Dynix code was not actually ported from a generic multi-OS code base (i.e. a generic OS sample implementation, such as you find in some textbooks.)

    As multi-processor AIX was scaling quite nicely before IBM acquired Sequent, I don't think they're going to have any difficulty proving that AIX is not encumbered by Dynix code. Further, as Dynix was only running on x86 hardware while AIX runs on Power RISC cores, I really don't see how the core RCU code could even have made it's way from Dynix into AIX -- wouldn't the core RCU routines be hand-tweaked assembly rather than C code?

    --
    I do not fail; I succeed at finding out what does not work.
  268. Re:Power to the people! by Anonymous Coward · · Score: 0

    We are very, very big software company.

    We don't care shit about your work.

  269. How SCO makes money by siskbc · · Score: 1
    Well, no, this AIX crap is about trying to get $3 billion out of IBM.

    Please, everyone including SCO knows that will NOT happen. I would bet their plan does not involve the acquisition of 3 billion dollars. If that somehow accidentally happened, I'm sure they'd love it, but if theit plan consisted of the suit alone, they'd be moving with it, not playing the PR game/

    It's going to take SCO a long time to get $3 billion out of Linux users at $1300 a pop.

    Not...really. Considering that MS only makes $200 max per install, even considering that linux has a much lower install base than windows, the numbers are staggering. Particularly since they don't have to lift a finger to get the cash. Think about it. Are there a million machines running linux? Yes? There's a billion. So if that worked, which it won't, there would actually be a pile of cash.

    But what this is really about is extorting IBM. SCO knows damned well that few companies are going to pay $1300 to use linux. And if they can sow enough fear, they can hurt IBM's sales of linux.

    So given that they can't win the suit, and they won't get much revenue from linux simply because no one will pay it, where does their revenue come from? By extorting IBM. Their fortunes in this case revolve around two things: 1) keeping their stock price high by lying to mentally retarded investors who actually think they're going to get $3B, and 2) getting IBM to possibly buy them out to keep SCO from spreading fears about linux, which would (in their mind) cripple the market IBM is attempting to dominate.

    --

    -Looking for a job as a materials chemist or multivariat

  270. So what? by k12linux · · Score: 1
    SCO have announced the final termination of IBM's UNIX license, despite Novell telling them they can't.

    Big deal. SCO tells IBM that their license is terminated. IBM gives SCO the finger (it's legal equivelent anyhow.) Now if SCO wants to enforce their license termination, they have to get an injunction against IBM which says they can't sell/license AIX until trial. Short of an injuction it's business as usual for IBM.

    What judge is going to give a preliminary injunction against a company as big as IBM? Especially one that would hurt them financially as bad as this would? Any judge in their right mind wouldn't want to risk the fallout. They'll allow IBM to continue with AIX until SCO proves their case in court.

    If (really big IF) SCO wins at trial, they might be able to collect some fees from IBM for the time between terminating the license and the trail. But this just gives a judge more reason to not rule for an injuction now.

    If Novell really did retain the right to control how SCO licenses and enforces licenses, then they had the right to tell SCO they couldn't revoke IBM's license. And if that's true, IBM is basically at zero risk of fallout from this. You can be sure IBM's laywers will point these facts out to a judge.

    This seems to be a case of SCO crying that they are going to take their ball and go home... when somebody else actually owns the ball and was just lending it to them.

  271. Re:Stock Statistics Like who bought! by koa · · Score: 2, Interesting

    Lots of good points to that, and it brings up some serious paradoxes that have been causing this uproar, specifically:

    A few MS dot com instant millionaires per chance?

    In my opinion, absolutely. In my experience, stocks are baught and sold by people who have a vested interest in the _FUTURE_ of a corporation. At this point, however, I'm pretty sure that noone who has any technological background would ever buy an SCO product again, or stock for that matter!

    I hope the AG in New York is looking into this right now

    As do I, but thus far it does seem as though anyone (Feds) are either a) looking into it and just keeping quiet to get as much dirt as they can before they blow the whistle .. or b) not doing anything and are actually asleep at the wheel. Only time will tell.

    These dot com morons might get their ass kicked, would you hire an ex-SCO exec?

    No, and I wouldnt ever buy an SCO product ever again. As I have stated above.

    At least one thing is certain in my mind. Becuase SCO is so blatently gung-ho about destroying their public image, and showing that they care less about their Brand recognition than your average ./ reader nowadays. (If I owned the SCO brand, I wouldn't do this and I dont know anyone who would!) This whole fiasco is bound to be over very soon.

    --
    ....move along....nothing to see here....
  272. Dead Horse, beaten soundly by PatSand · · Score: 1

    Not SCO behavior...they deserve our utter contempt, spam, and junk mail...

    Sequent is being phased out--IBM has stopped shipping them and is telling customers to bail out soon (I believe it was last year, if I recall correctly)...I remember one large financial customer looking to shift from Sequent to IBM or Sun last year and looking for DBAs to help migrate things...

    The gist of it is that nobody should be buying new Sequent (dynix/pt) licenses since the hardware is going away...

    or have the drugs kicked in too hard?

    --
    Supreme Granter of Doctor of Obviology Letters ("A FIRM Command of the Obvious")
  273. Protest SCO by Anonymous Coward · · Score: 1, Informative

    I just modded in this topic, so I had to logout to post.

    I'm far far away from vegas, but SCO is having a show there in three days. If any slashdotters are in the area I suggest pulling the permits and protesting infront of the SCO show. As someone who has done work on SCO stuff in the recent past, I will now move every customer I can off their product and onto another operating system.
    We need to show those that use SCO that the people who do support work on the SCO operating systems will no longer do any further work on SCO based systems (in the past couple of years I did some work on a Xenix system, so it's plural).

    http://www.sco.com/2003forum/

  274. Forensics by booch · · Score: 4, Interesting

    Almost all Linux code gets modified over time. All Linux versions are publicly available. You could compare the various Linux versions with the SCO version(s). This would give you a good idea when the transfer happened. Assuming SCO has a record of their versions (it would be hard to believe they don't have any revision control system) you could do it both ways.

    I'm betting that SCO would not be smart enough to take the original Linux version, but would take a newish Linux version. Showing that Linux had older (less "good") versions and SCO did not would be evidence that SCO had taken the code from Linux, not vice-versa.

    So assuming that the code base(s) change(s) significantly over time, determining the provenance of version-controlled code is not all that difficult. Think of it in biological terms -- we can identify the lineage of various species/specimens by comparing their DNA and their ancestors' DNA.

    --
    Software sucks. Open Source sucks less.
  275. Most Obscurely Hilarious Joke On /. Ever by Effugas · · Score: 1

    This makes me want to play with mainframes just so I witness the error myself.

    Wow.

    --Dan

  276. Licencing Shakedown and Stock Pumping by Anonymous Coward · · Score: 0

    How about complaining to the FTC?
    The FTC controls business practices (ie, the licence shakedown)
    The SEC controls securities activies (ie, the stock pumping)

    Or, since what SCO is doing is illegal in Germany and Australia, those of us in Germany or Australia could launch class action lawsuits for every single linux user to be compensated for every single linux *copy* they have or use.

    Just bankrupt SCO, RIGHT NOW.

  277. Development Methods... by BlabberMouth · · Score: 2, Interesting

    Using Unix based development methods, whatever that means, is not illegal unless the method is one that has been patented by SCO. (Such a patent does not exist.) Furthermore, since when does buying code from another company give you any right to the method they used to create it? I'd say that Unix based development methods, whatever they are, are probably taught by scores of Universities around the world and have been for quite some time. Are all of those people somehow inserting SCO trade secrets into their code? It looks like that is what SCO is trying to say.

  278. Linux is a registered trademark.... by cmptrmaniac62 · · Score: 2, Interesting

    Here's an idea, maybe Linus can sue SCO for misuse of a registered trademark... None of their releases have given proper credit to Linus for the Linux REGISTERED name.

    Also, he might be able to claim that their "OpenLinux" is too close to the Linux trademark...

    Yes Virginia, Linux is a registered trademark of Linus Torvalds.

  279. HaHa, No UnixWare Here... Oops, We're the Vendor. by cmptrmaniac62 · · Score: 1

    SCO won't even run their own site on UnixWare

    SCO is hosting their site on Linux... I guess they know their own OS is not good enough to handle the load.

    See netcraft...

  280. multiple licenses? by Anonymous Coward · · Score: 0

    An idea that I haven't seen come up yet is this:
    If IBM owns the code, why can't they distribute it under multiple licenses. Specifically, why can't it be included in dynix (or aix) and be subject to those licensing restrictions as well as be distributed under GPL? The "derivative work" would be the entirety of dynix (or aix) and sco would have rights to that derivative work, but IBM would still have rights to the code itself and be able to license it elsewhere as it desired.
    I only glanced over the licensing agreements, but it seemed that what sco gained rights to was the "derivative work" itself, and NOT the specific means of derivation...

    1. Re:multiple licenses? by pavera · · Score: 2, Interesting

      Well,
      SCO is claiming that the contract under which IBM got system V to develop AIX (and Sequent got system V to develop dynix) made the system V license viral like the GPL meaning the contract said "If you add anything to this, it must be licensed under the same system V license and you may not license that code/IP in any other way". Much like the GPL says "You can make changes but all changes must be licensed under the GPL, and this is the only way you can make and distribute changes". So depending on the wording of the contract and whatever "side letters" IBM may have from AT&T or Novell, this could be a valid claim, and if so would simply mean that some non-IBM developers would have to get the RCU, NUMA, and JFS specifications (IBM vigorously developed these things as "concepts" first and code later) and recreate the features from the white papers describing how the features work.

  281. Compuserve, Unisys, Gif? by trolman · · Score: 2, Insightful

    Does not anyone remember Compuserve, Unisys, and the GIF debacle? Think about the past and try not to relive it. Hey?.

  282. Why Not Start Over at Linux 2.2 !!! by Anonymous Coward · · Score: 0

    If IBM did indeed violate the copywrite on the trade secret code, why not just have that army of programmers start a clean room project to replace it. It's only 6 months of kernel development and it kills off the SCO claim entirely???

    -Mike the Anonymous

  283. terminate sco's lawyer license. please. by Anonymous Coward · · Score: 0

    subject says it all.

  284. I'm Waiting by Greyfox · · Score: 1

    I'm waiting for SCO to try to claim IP rights over everything I've written in UNIX since 1987. You "Hello World" users out there are gonna be shit-outta-luck!

    --

    I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

  285. Owner and ownership rights. by heech · · Score: 1

    Your analysis is incredibly informative. No idea as to the final outcome of course... but it's perfectly possible, I believe, to have "ownership" over property without retaining all of the rights to that property.

    Obvious examples include exclusive distributorship licenses that exist for everything ranging from books to movies. Or, in the case of real estate, leasehold rights.

    Even though the makers of Gigli retains ownership of the movie asset (which is also not 'real' property, similar to source code), they do not have the rights to show the movie publically. It is the distributor that now owns the rights to do so.

    Ownership of an asset, despite common experience, does not imply right to use the asset in any way you choose.

  286. Does SCO think that we're really that stupid? by The+Evil+Muppet · · Score: 1

    SCO says "heaps of our code from the old SysV codebase, the USL codebase and the UnixWare codebase was copied into Linux!"

    Are there any kernel gurus out there that would care to tell me about what level of work is involved in bringing code from another OS (say, one of the BSDs) into the Linux kernel? Is it even reasonable to expect that code from a UNIX kernel rooted in the past could have it's code shoehorned into the Linux kernel line-for-line as SCO are alledging?

    Back to the OpenServer->Linux migrations! Damned SCO, I am not paying for UnixWare so that I can tell it to emulate OpenServer.

  287. Re:Can't seem to find it Here maybe? by ratfynk · · Score: 1

    Well I just looked at the Alpha smp.c and found that it is dependant on linux/smp.h which is just a switch, and not very complicated to boot! Here is the alpha smp.c origin linux/arch/alpha/kernel/smp.c
    *
    * 2001-07-09 Phil Ezolt (Phillip.Ezolt@compaq.com)
    * Renamed modified smp_call_function to smp_call_function_on_cpu()
    * Created an function that conforms to the old calling convention
    * of smp_call_function().
    *
    * This is helpful for DCPI.

    Since this is saying that it is reliant upon an old smp_call_function() then maybe that is what SCO is bitching about. However looking at the rest of the smp.c's for all the other arch they seem to be independant of smp_call_function(). Very interesting. So there might be a bunch of old Compacts out there that are not in compliance?

    --
    OH THE SHAME I fell off the wagon and use sigs again!
  288. Wasn't that Goebbles? by Anonymous Coward · · Score: 0

    AFAIK it was Joseph Goebbles, the minister of propaganda, that said that.

    1. Re:Wasn't that Goebbles? by shanen0 · · Score: 1
      Doesn't matter as far as Godwin's Law in concerned. First, there's an exclusion if you try to invoke it deliberately, and second, the rule covers all Nazis, too.

      But most importantly, nothing is liable to terminate these "vigorous" threads save SCO's self-immolation by litigation.

  289. Iff Linux's code came from Sequent; it didn't by leonbrooks · · Score: 0

    And The SCO Group know this. They're just whipping their shares into one last frenzy so they can dump big-time and flee back to The Canopy Group for protection. We should be publishing articles seriously asking whether D'ohl is a closet AL Quaeda agent.

    --
    Got time? Spend some of it coding or testing
  290. SCO Used to Give it away FREE by Anonymous Coward · · Score: 0

    A real press release from 97

    FOR IMMEDIATE RELEASE

    CONTACT:

    Monika Laud
    SCO
    TEL: 408/427-7421
    FAX: 408/427-5448
    monikal@sco.com

    UNIX UNBOUND!

    SCO Provides FREE UNIX System Licenses To Students, Educators and UNIX
    Enthusiasts Around The World

    SCO Forum96, Santa Cruz, CA (August 19, 1996) -- In a move that empowers
    students, educators and UNIX system enthusiasts with free access to the
    worlds most popular business computing environment, SCO today announced
    plans to provide a free license to use its popular UNIX systems,
    including SCO OpenServer and SCO UnixWare, to anyone in the world who
    wants to use them for educational and non-commercial use to enable the
    evaluation and understanding of UNIX systems. The bold move has
    far-reaching implications for the future of the UNIX platform and marks
    the stunning public debut of SCOs stewardship of the UNIX system. It
    also represents the first time in more than 20 years that the owner of
    UNIX technology has provided the operating system free of charge to the
    public.

    Alok Mohan, SCOs president and CEO, said, "This is only the second time
    in UNIXs 25-year history that the owner of the technology has made this
    offer. The last time this happened, a $60-billion-dollar industry was
    born." The UNIX system was in its infancy when AT&T Bell Labs gave it
    away for free to colleges and universities to help with research and
    development projects. Soon, thousands of students were learning to
    program on UNIX systems. After graduation, they took that knowledge
    into the corporate world, building a $60-billion-dollar industry. The
    legacy of AT&Ts gift to universities includes the Internet, the World
    Wide Web, multiprocessing, and much more. Today, the UNIX system is the
    software engine that processes trillions of dollars of business
    transactions around the world.

    "SCO believes it is time to return the favor," said Mohan, "and deliver
    the result of more than 20 years of technical innovation back to
    educators and students worldwide. With the explosive growth of the
    Internet and the breadth of development tools for UNIX systems available
    today, one can only imagine what this new generation will do with this
    open operating system platform."

    What the Students Will Get

    The availability of free UNIX system licenses begins with SCO OpenServer
    license, followed closely by a free SCO UnixWare license. The initial
    availability of a free SCO OpenServer license provides UNIX system
    enthusiasts with access to a high-end, commercial quality UNIX product
    that would normally be out of reach due to price constraints. Students,
    as well as professionals who use the UNIX system at work, now have an
    affordable means of running the UNIX platform at home, enabling them to
    create a home BBS or web site.

    Whats In Free SCO OpenServer?

    With a Free SCO OpenServer license, users interested in UNIX technology
    have access to a fully functional, single user version of the SCO
    OpenServer Desktop System, which includes SCO Doctor Lite, and SCO
    ARCserve/Open Lite from Cheyenne, and the SCO OpenServer Development
    System. The SCO OpenServer Desktop is an advanced, single user UNIX
    operating system that delivers RISC workstation capabilities and
    performance on cost-effective Intel architecture platforms. The Desktop
    System integrates a powerful 32-bit, multitasking, X/Open UNIX system
    compliant operating system with networking, graphics, and Internet
    facilities. The Development System includes a set of state-of-the-art C
    compilers, debuggers, application programming interfaces,

  291. Perhaps you're talking about Amendment X? by leonbrooks · · Score: 1
    Amendment X gives both IBM and Novell some pretty amazing contract powers. Novell can tell The SCO Group to jump, and they must jump. Presumably with the delays and potential for mistakes in court in mind, N can further act on behalf of TSG in carrying out N's will WRT the contract - which they did when TSG gave themselves airs and graces about IBM's right to develop and distribute AIX. It also made the agreement "perpetual and irrevocable", so N didn't even need to go that far, in theory (but you can understand why they did). "Please, Brer TSG, don't throw me in the legal briar patch!"

    It's certainly more substantial, sweeping and better verified than the "bottom of a locked filing cabinet in a disused lavatory marked 'beware of the leopard' Amendment 2" for a different contract that TSG dug out for the (few, essentially useless) copyrights they wanted transferred.

    --
    Got time? Spend some of it coding or testing
  292. Even granted your premises... by leonbrooks · · Score: 1

    ...IBM proper have a licence to use SysV-R4 code (even granted TSG's rantings, they unquestionably did have such a right after they macrophaged Sequent), so whatever Sequent contributed back to that codebase as per their own agreement, IBM would have had a right to use via their separate SysV-R4 licence.

    --
    Got time? Spend some of it coding or testing
  293. does anyone really care? by smash · · Score: 1
    .... I'm sure as shit that IBM don't.

    For those who didn't read it yet, go have a gander at the countersuit being lodged by IBM.

    Regardless of the validity and strength of SCO's claims, they're fucked, due to patent violation, breach of the GPL, etc.

    As to the rest of us - well, I think SCO tried to pull a swifty and people baulked. The fact that only ONE idiot has payed them for a license (and there's been publicity to that effect) indicates to me that 1) people don't care/believe SCO, and 2) once they find out that no one is paying, those who do care will stop taking them seriously.

    All they've achieved is woken up IBM, who's going to prevent them from being able to sell any of their SCO products (their other supposed source of income) due to patent violation.

    Life is good :D

    smash.

    --
    I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  294. This just jeeps getting funnier and funnier! by borgheron · · Score: 1

    I just can't stop laughing. Wasn't Sequent and *independently* owned and operated company? Hasn't SCO admitted that IBM owns the copyrights to NUMA and RCU?

    This is just so damn funny, I can't believe it. I always knew that Linux would eventually beat proprietary UNIX in the marketplace, but I never expected it to go out with such an unbelievable whimper.

    GJC

    --
    Gregory Casamento
    ## Chief Maintainer for GNUstep
  295. Barratry? by borgheron · · Score: 1

    Just in case anyone knows....

    When does it get to the point where Boies and his firm can be charged with barratry? So far none of his strategies have worked against the community and it does seem like he's telling SCO to instigate all of this knowing that they've no chance in hell.

    That seems to be the definition of barratry:

    Barratry \Bar"ra*try\, n. [Cf. F. baraterie, LL. barataria. See
    {Barrator}, and cf. {Bartery}.]
    1. (Law) The practice of exciting and encouraging lawsuits
    and quarrels. [Also spelt {barretry}.] --Coke. Blackstone.

    Later,

    GJC

    --
    Gregory Casamento
    ## Chief Maintainer for GNUstep
  296. Aso. by Anonymous Coward · · Score: 0

    "SCO Announces Final Termination of IBM License"

    Common Sense announces final termination of anyone who gives a shit what SCO is doing.

    -Frapazoid. Sorry, I couldn't help it!

  297. She sells C Shells by the sea? Sure... by leonbrooks · · Score: 1
    From your article...
    Which versions of the Linux kernel did SCO sell?

    They had 2.4 up to something like 19 on their FTP servers until well after they sued. Think in terms of months. They still have pieces of same up there to this day.

    --
    Got time? Spend some of it coding or testing
    1. Re:She sells C Shells by the sea? Sure... by Edward+Scissorhands · · Score: 2, Insightful

      Yeah, I didn't mention anything in my article about the GPL. That's going to be a huge part of this lawsuit as well, but I didn't want to touch it with a ten foot pole. The GPL is going to have its day in court for sure, and the outcome is going to have gigantic ramifications. Let's say that IBM is off the hook because of the GPL, well, then people like Sun or Microsoft will probably use that fact to scare people away from the GPL by highlighting it's "viral" nature and the danger that it could effectively destroy a company's rights over their own technology should they not fully understand what and how they use GPL code. On the other hand, if the GPL is shown to not be valid (though I have no reason to believe that it would end up that way), that would devastate the open source/free software movement as we know it. Obviously, the movement would heal and continue on, but in what form is anybody's guess.

      In all honesty, I'm not sure what SCO is trying to accomplish here. If they had, in fact, removed all Linux kernels from their software and stopped distributing GPL'ed code that they claimed infringed their rights as soon as they made their case public, then the courts might let them off the hook with having released their code under the GPL. But to just let it sit on their FTP servers for months afterwards makes me think that they actually want IBM to use the GPL defense. I have no idea why, though, as it makes SCO's case that much weaker.

    2. Re:She sells C Shells by the sea? Sure... by WCMI92 · · Score: 2, Insightful

      If the GPL is ruled invalid, then EVERY "shrinkwrap" EULA is invalid.

      The GPL doesn't take ONE SINGLE RIGHT away from you that is granted by copyright law. It grants you rights you DO NOT have under copyright law (redistrobution, right to use the code to make derivitive works), only if you meet it's condition (license derivitive works under the GPL).

      As much as MS would like to do away with the GPL (the GPL itself is what makes it impossible for MS to do away with Linux by conventional methods), to have EULA's ruled invalid would have a DEVASTATING effect on them...

      --
      Corporatism != Free Market
  298. Chronology by leonbrooks · · Score: 1
    For contracts, my understanding is that if a later contract between two parties explicitly contradicts an earlier contract, the later one wins.

    So if a contract contradicts itself (say that six times fast), the text furthest down the contract - being conceptually "later" in the contract - wins?

    --
    Got time? Spend some of it coding or testing
  299. LINDON, UTAH... by tunacanrana · · Score: 1
    ...get ready
    to go
    WORLDWIDE!

    Let's get it on!

    Jealous cowards try to control
    they distort what we say
    try to stop what we do
    when they can't do it themselves

    We
    are tired
    of your
    abuse!
    Try
    to
    stop us,
    it's
    NO USE!

    from Rise Above apologies to Greg Ginn

    Rise above,
    We're gonna rise above.

    1. Re:LINDON, UTAH... by Geotopia · · Score: 1

      Rock on Lindon! I think it's the first time we ever made national press (not counting agricultural news stories).
      I used to work in Scotts Valley, CA and we had lots of former SCO employees at my job there. Then I moved to Lindon, and next thing I know, there's going to be a lot of former SCO employees here as well. I may move to Canada, maybe SCO will follow?...

  300. Yep, you're wrong. by Anonymous Coward · · Score: 0

    If IBM/Sequent owns copyrights on NUMA, RCU, JFS, as SCO itself has said -- then they are, by definition, "original works".

    Copyright law demands no less. You cannot copyright anything other than an "original work".

    A derivative work is a compilation of two, or more, original works. "Derivative work" DOES NOT mean one "came from, or because of, or is somehow related to" another. Copyright does not recognize "use" at all, and the concept of "following" would imply the law had a "use sensitivity" that it simply does not. The order of creation between any two works that ultimately form a derivative doesn't matter to copyright.

  301. Pumping and Dumping by insipid · · Score: 1

    SCO execs really have been dumping stock since the lawsuit was filed according to this article.

    Some highlights, since the lawsuit was filed SCO's stock has quadrupled. The insider sales since March were the first such sales in more than a year. So far they've taken in U.S. $1.2 million.

    --

    dp
    ---
    http://insipid.com
  302. TSG has already ceased selling new Linux... by leonbrooks · · Score: 1
    ...and they don't need any Linux code themselves to run their extortion racket.

    You could, however, hurt The SCO Group (different to the Santa Cruz Operation, different company, different people, different management, different culture; all they have in common they got from The Canopy Group) and anyone who is dumb enough to still be running one of their Linuces by insisting that they destroy all source and binary copies of your IP (Linux kernel) in their possession and recall and destroy every copy or Linux that they ever sold or licenced. As I understand the law and the GPL, any kernel developer who contributed code that they distributed has the right to do that.

    If you really want to add insult to injury, send them a court injunction requiring them to identify their F500 licencee (it will be Microsoft) as part and parcel of that recall and destruction.

    --
    Got time? Spend some of it coding or testing
    1. Re:TSG has already ceased selling new Linux... by WhiteWolf666 · · Score: 1

      I'm not certain that you can get a court to have them destroy/recall all copies of linux they have sold/licensed.

      I do believe, however, that you can win damages from them, for copyright violation. I think it is something like $10,000 per violation.

      You don't even have to go after the customers---just the distributor (TSG).

      --
      WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
  303. But who will think of the lemmings? by leonbrooks · · Score: 1
    and are proceeding along this path with the certainty of a lemming marching toward the sea.

    So who plays the role of the journalists herding them off the cliff for the cameras? Lemmings don't naturally jump off cliffs, the odd one falls (gets nudged) off by accident. Only humans are stupid enough to do that voluntarily.

    --
    Got time? Spend some of it coding or testing
  304. No, the case is NOT about copyright by leonbrooks · · Score: 1

    The case is about contract violations. But none of the contracts in question have been violated by anything TSG is climing. OTOH, TSG have violated those same contracts on two counts and at least three occasions.

    --
    Got time? Spend some of it coding or testing
  305. Sorry, can that be disqualified on Godwin rules? by leonbrooks · · Score: 1

    To wit, deliberately making a "You're new here" post on SlashDot with intent to solicit karma?

    --
    Got time? Spend some of it coding or testing
  306. They have to rejigger the logo... by leonbrooks · · Score: 1

    ...to show a silhouette of D'ohl holding a pistol to a penguin's head.

    --
    Got time? Spend some of it coding or testing
  307. SCO Announces Final Termination of IBM's Licence by Anonymous Coward · · Score: 0
    Insurance Claims to be Tested by Lie Detector

    It kinda fits - or rather, I wish we could use a lie detector on Darl McBride.

  308. SCO Didn't Complain When NUMA was on NT by grendelkhan · · Score: 1

    Very interesting article referenced in discussions at Groklaw by quartermass, IBM announced after buying Sequent that they planned on adding NUMA to Linux, and it was already running with NT and (eventually) 64-bit NT.

    Why all the fuss now?

    --
    Wu-Tang Name: Half-Cut Skeleton Get your own Wu-Na
  309. Runners up... by leonbrooks · · Score: 1
    07. *
    08. }
    09. #include <stdio.h>
    10. #include <stdlib.h>
    11. #include <signal.h>
    12. exit (0);
    13. int main (int argc, char ** argv) {
    14. while (argc --) {
    15. Copyright (c) 1978, Regents of the University of California
    16. ...

    Are we done yet?

    --
    Got time? Spend some of it coding or testing
  310. This time it's not about AIX, it's about Dynix/ptx by The+Monster · · Score: 1
    This time, they are saying that the Sequent license means that Dynix/ptx is a derivative form of Unix, and that the leakage of the NUMA and RCU code to Linux is a violation of the license. They're not even talking about AIX this time.

    They hope to get a court to rule that they do indeed own the code, and can collect lotsabux as a result, or alternatively if they don't, that can be used to attack the GPL's assertion of control over derivative works as well.

    --

    [100% ISO 646 Compliant]
    SVM, ERGO MONSTRO.

  311. Re:NUMA and RCU? Then why... by Anonymous Coward · · Score: 0

    With the code being NUMA and multi-processor patents, then why does SCO claim a hefty license fee for *single CPU* linux installations?


    Yeah, and what about the stupid $32 imbedded Linux license? What's THAT for? 8-way multiprocessor PDA's?

  312. SCO is in a lose-lose situation by GooglyWoogly · · Score: 1

    Let's assume that SCO is right, and that there IS copied code in linux from sysV. It seems to me that 1 or more of the following will happen:

    (i) linux developers will clean room re-develop the offending code, thereby fixing the breach. SCO loses.

    (ii) if (i) doesn't happen for some reasons I can't fathom, then SCO stops all use of linux kernel 2.4 upwards. Linux drops back to 2.2 (losing years of work) and restarts from there. SCO loses, linux loses some time.

    (iii) if (i) & (ii) can't happen, then SCO wins the battle, linux is killed. Will millions of linux users spend $699 or $1299 on SCO linux ? NO! Most would shift over to freebsd/openbsd, and a few might go to MS & Apple. SCO loses the war. FreeBSD/OpenBSD wins.

    It really seems like a well planned short term survival strategy but a really poor long term survival strategy by SCO. Are they doing drugs or what ?

  313. codes... Methods? Gimme gimme by Anonymous Coward · · Score: 0

    fuck the code, the methods can reproduce the code and then we can tell them to F off. How can you prove that a thousand hackers used one method over the other?

  314. Maybe will become issue of residuals.... by dbc · · Score: 1

    All you developers should pay attention to this issue at all times.

    Software contracts between companies should address the issue of "residuals". In simple terms that is: "stuff programmers remember". Basically, the contract might state that the programmers involved specifically *can* work on similar, potentially competing stuff in the future, as long as they no longer have access to the code in question and are woking only from "residual" knowledge. The contract instead might state that you can *not* work on similar stuff for X number of years, regardless. Also, the contract might be silent on the issue.... bad news for you, but it does generate billable hours for lawyers. Did your boss explain the residuals clause the last time he pointed you at some work on a joint project with another company? Ask about it if s/he didn't.

    In a past life (at a company not yet mentioned)Dipanker sat a few cubes down from me... DS is one very^3 smart dude... I suspect he could have remembered a lot. I sure as hell hope he does not get deposed... he's far too nice a guy to have to suffer that.

  315. Re:Actual transcript smuggled out of the courthous by toomuchPerl · · Score: 1
    oh really?

    try watching the movie again, "fool".

    King Arthur in the context of the original post is IBM, and IBM says "Alright, we'll call it a draw" -- Arthur then proceeds to walk away.

    -toomuchPerl
    Sippin' on Jolt and Dew, laid back. With my mind on my cubicle and my cubicle on my mind.

  316. Fiction quote (Re:Sleeping Giant) by NKJensen · · Score: 1

    It seems to be a film quote from 1970 with no evidence.

    Check out

    http://www.wikipedia.org/wiki/Isoroku_Yamamoto's _s leeping_giant_quote

    or try Google with "Isoroku Yamamoto giant" as the search words.

    --
    -- From Denmark
  317. chill out man by Ender+Ryan · · Score: 1
    Relax man, I was obviously not intending to flame, hence the (attempted :-) humorous nature of my post.

    Sorry I misunderstood you.

    Cheers.

    --
    Sticking feathers up your butt does not make you a chicken - Tyler Durden
  318. Re:SCO Announces Final Termination of IBM's Licenc by mink · · Score: 1

    I really dont want to see the day that SCO decides to release the Robotic Richard Simmons.

    --
    Well I've wrestled with reality for thirty five years doctor, and I'm happy to say I finally won out over it.