Slashdot Mirror


SCO NDA Online at LinuxJournal

shadowbearer writes "The full text of the SCO NDA is available here at LinuxJournal. IANAL, but my reading of it makes me understand all the industry "No way!" style comments. Here's a snippet:
"Dan Ravicher, an attorney who specializes in free software and open-source issues at the firm of Patterson, Belknap, Webb & Tyler, said in an interview there are three key problems with the NDA. First, Ravicher said, "SCO can pick and choose among all its evidence" to show only the parts that back up the company's claims. "They're agreeing to let you see the half of the picture that they want you to see", he added.""

441 comments

  1. Section 8 by Waab · · Score: 5, Funny

    Under Section 8 (Injunctive Relief), if I sign the NDA and then even threaten to reveal any of what SCO showed me:

    SCO shall be entitled ... to preliminary and permanent injunctive relief

    Does this mean they can send me down for the dirt nap?

    1. Re:Section 8 by Anonymous Coward · · Score: 0, Interesting

      Wow, someone's really (ab)using their subscription. :P

    2. Re:Section 8 by cshark · · Score: 4, Interesting

      They don't even want to you divuldge file extensions. Wouldn't that keep any programmer from well... programming? It would suck to sign this agreement and then find out you need to switch careers or SCO will SUE you.

      --

      This signature has Super Cow Powers

    3. Re:Section 8 by Anonymous Coward · · Score: 0

      is this NDA actually enforceable?

      --
      my new signature: "Let's support SCO by making mirrors of their ftp server! wget -r -O /dev/null ftp://ftp.sco.com"

    4. Re:Section 8 by Anonymous Coward · · Score: 0, Interesting

      That's not abuse; it's the intent of Slashdot's subscription model. The moderation system is broken. It favors those posting early on in a story. Rather than fixing it, the staff here simply decided to use it to make money. If your karma isn't high enough to suit you, simply buy more.

    5. Re:Section 8 by rking · · Score: 5, Funny

      is this NDA actually enforceable?

      Maybe, maybe not, but breaking it will get you added to SCO's we-will-sue list. Next press release it'll be IBM, 1500 Linux using companies, Novell and now Slashdot's Anonymous Coward.

    6. Re:Section 8 by Lumpy · · Score: 4, Insightful

      it doesnt matter. their NDA is 100% worthless.

      their ENTIRE sourcecode will be revealed in court to professional witnesses under court order, not under some fantasy bullcrap SCO's lawyers dream up.

      SCO is doomed, their NDA is proof that they have nothing and the whole thing is nothing more than a scam that the CEO and other company officials are trying to pull.. I put these guys lower than the scumbags at Enron.

      I'd tell everyone I know to avoid SCO, but nobody has used their products cince 1990.

      the response I get is S C Who? that company that went to hell in the early 90's that had the crappiest Unix on the market?

      SCO has been a running joke in the Unix market for decades... their NDA is just further proof.

      --
      Do not look at laser with remaining good eye.
    7. Re:Section 8 by Imperator · · Score: 2, Interesting

      Or just take a few months off and then the contract will disappear with the company.

      --

      Gates' Law: Every 18 months, the speed of software halves.
    8. Re:Section 8 by Ryvar · · Score: 2, Funny

      that company that went to hell in the early 90's that had the crappiest Unix on the market?

      You're thinking HP (HP-UX). Otherwise, yeah.

      --Ryvar

    9. Re:Section 8 by Ryan+Amos · · Score: 1

      Wow, posts this insulting are usually modded down as trolls or flamebait. The only difference is that this one is true. Guess that really says something about this whole thing ;)

    10. Re:Section 8 by munro · · Score: 5, Insightful

      They didn't have the crappiest UNIX on the market back in the day - it was awesome to be able to run UNIX on cheapo 386 hardware, and it worked really well.

      I feel sorry for the excellent engineers and businessmen who made that happen (more than twenty years ago), their ancient and respectable company name has been turned into shit by a bunch of dot-com bubble idiots with a hangover and a patent lawyer.

    11. Re:Section 8 by SN74S181 · · Score: 1

      You never know, these days. Someone like Ray Noorda may come along and buy the company just for the rights to sue people, like he did with DR-DOS. Distressed properties and failed software firms can be a gold mine for the greedy, angry, and litigious.

    12. Re:Section 8 by Jason+Earl · · Score: 1

      That's a good one. SCO is nothing more than a rebadged Caldera, which Ray Noorda already owns! In fact, the lawsuit over DR-DOS was between Microsoft and Caldera (now SCO).

      Makes your head hurt, don't it.

      In other words the greedy, angry, and litigious already own SCO. You would have to be a dunderhead to sign an agreement with those weasels.

    13. Re:Section 8 by Slime-dogg · · Score: 1

      I wonder... If every slashdotter signed the NDA, then each and every one of us violated it, would SCO then have to sue each and every one of us? If that were so, we could grind the company into the ground through litigation, kind of like a legal version of the DDOS.

      --
      You need to restart your computer. Hold down the Power button for several seconds or press the Restart button.
    14. Re:Section 8 by geekee · · Score: 1

      Yes. No one doing open source programming should sign this NDA. Once you see the SCO code, anything you write is tainted, and they can claim you got your ideas from them.

      --
      Vote for Pedro
    15. Re:Section 8 by geekee · · Score: 1

      Wait a minute. So in the Dr-DOS lawsuit, Caldera was the good guy, because they were going up against MS. Now their the bad guy because they're going up against Linux? People should sort good from bad based on principles, not the software running on their machines.

      --
      Vote for Pedro
    16. Re:Section 8 by Anonymous Coward · · Score: 0

      I don't have any principles, but it was pretty clear to me at the time that MS was illegally bundling MS-DOS and MS Windows together, denying DR-DOS a market.

      Right now, nobody has any evidence about this SCO thing -- if they come up with something, opinions will change.

    17. Re:Section 8 by Zork+the+Almighty · · Score: 1

      I don't have any principles...

      So have you passed the BAR exam yet ?

      --

      In Soviet America the banks rob you!
    18. Re:Section 8 by Anonymous Coward · · Score: 0

      It sounds very much like a preemptive attack :-O

    19. Re:Section 8 by Anonymous Coward · · Score: 0

      Then why are we all behind IBM when they invented the tactics that microsoft has perfected?

    20. Re:Section 8 by s4m7 · · Score: 1

      and now Slashdot's Anonymous Coward.

      Would that be a reverse-class-action lawsuit?

      --
      This comment is fully compliant with RFC 527.
    21. Re:Section 8 by jepaton · · Score: 1
      Hewlett Packard still peddles HP-UX:

      HP RISC architecture based workstations

      HP-UX 11i operating system

      Can't be *that* bad if they still develop the hardware for their operating system.

      PA-RISC/HP-UX is perhaps one of the last examples of the old-HP - where every piece of equipment was designed and manufactured in-house. They used to make their own screws for goodness sake!

    22. Re:Section 8 by cduffy · · Score: 1

      ...because they're not still using those tactics?

    23. Re:Section 8 by Anonymous Coward · · Score: 0

      Don't generalise like that. In the DR-DOS case, MS were shown to be generating completely spurious error messages when Windows 3.1 (a batch GUI, not an OS) was run on top of DR-DOS instead of MS-DOS.

      So Caldera had grounds to complain - MS were misleading consumers and deliberately breaking Windows on DR-DOS

      In this case, Caldera/SCO are making a completely different (and somewhat insane) claim. The sad thing is that some people are putting the burden of proof on the accused rather than the accuser. It is up to SCO to prove their claim. Signing a stupid and downright dangerous NDA with them when the code will come out in court in a few weeks is a bit silly.

      Note that Caldera is not a really a person (except under very stupid american laws) - it doesn't act like one, it doesn't empathise like one, and it doesn't deserve to be treated like one.

    24. Re:Section 8 by nickos · · Score: 1

      It was Microsoft XENIX originally wasn't it?

    25. Re:Section 8 by surprise_audit · · Score: 1
      SCO shall be entitled ... to preliminary and permanent injunctive relief

      Isn't that rather jumping the gun? I thought it was up to a judge to grant injunctions...

    26. Re:Section 8 by Prior+Restraint · · Score: 1

      I thought it was up to a judge to grant injunctions...

      It is, but if you agree in writing, no less that they're entitled to the injunction, then if they go to a judge for an injunction, you can't really put up much of an argument.

    27. Re:Section 8 by BenEnglishAtHome · · Score: 1

      Well, I feel sorry for me. My whole career is built on the rack of servers 20 feet from me running SCO OSR 5.0.4. The OS is reliable and does the vital jobs we require but we're migrating off of SCO, anyway. The servers are being migrated to virtual machines running on mainframes and the clients are now a part of Interix, er..., Microsoft Unix, er...,

      oh, hell, what do they call it now?

      Oh, yeah - Windows Services for Unix.

      Joy.

      Now my career consists of jumping to the mainframes or dropping back to supporting a Unix running on top of WinXP. I'll probably wind up doing the latter and, thus far, it's been a nightmare. Anybody got any good book recommendations on "Windows Services for Unix"?

    28. Re:Section 8 by Trepalium · · Score: 1

      Look for "Explosives for Dummies", or "Demolitions for Dummies" for everything you need to know about managing Windows servers, especially when running "Microsoft Windows Services for Unix".

      --
      I used up all my sick days, so I'm calling in dead.
    29. Re:Section 8 by Anonymous Coward · · Score: 0

      How about the Holy Bible? Or the Koran?

    30. Re:Section 8 by cHiphead · · Score: 1

      Anybody got any good book recommendations on "Windows Services for Unix"?

      The Bible, more specifically, those parts about the return of the Beast.

      --

      This is my sig. There are many like it, but this one is mine.
  2. Beware of unilateral contracts by zptdooda · · Score: 5, Informative

    "IN CONSIDERATION of the mutual promises ..."

    This contract was created by only one side of the deal. So it's worded precisely the way SCO wants it for their maximum advantage. Usually in a dispute courts will favour the party which didn't create the unilateral contract, but it looks like they've covered off that angle by choosing Utah.

    Bilateral contracts, where the parties negotiate and both have input into the final wording signed, are much safer as a rule.

    This is a one-sided contract by a known litigous company.

    The person signing gives up all kinds of rights, is straitjacketed legally, and doesn't even make any money on this.

    All the risk with no reward.

    What could the counterparty to SCO possibly gain by agreeing to this?

    I usually try to be ambivalent, but can't seem to find anything redeeming here.

    --
    Esteem isn't a zero sum game
    1. Re:Beware of unilateral contracts by PD · · Score: 5, Funny

      And the facts are going to come out during the trial anyways, so all you'd gain by signing the NDA is a small amount of time to look at the code before everyone else does. Not unlike subscribing to Slashdot.

    2. Re:Beware of unilateral contracts by AlecC · · Score: 5, Interesting

      What could the counterparty to SCO possibly gain by agreeing to this?

      Money. The counterparty would presumable be being employed as an Expert Witness in the lawsuit. Fees for such witnesses are normally very lucrative. >$1000/day plus expenses for the research phase (reading the code) and more for attendance in court are the figures I have heard.

      --
      Consciousness is an illusion caused by an excess of self consciousness.
    3. Re:Beware of unilateral contracts by captnjameskirk · · Score: 5, Informative

      IAAL, and this is not a "contract" until the other party signs it. Unitl then, it is just words on paper. No one is being forced to enter into this agreement, and in fact most have decided not to. A "unilateral contract" is the acknowledgment of one party to do something for (or to) another party, without requiring that party's consent or consideration on their part. Calling the draft of a proposed contract "unilateral" simply because it was drawn by one party is misleading. There is, in fact, mutual consideration here for those that sign, regardless of how limiting it may seem.

    4. Re:Beware of unilateral contracts by Zzz · · Score: 2, Interesting

      If SCO goes bankrupt, would that void the NDA?

    5. Re:Beware of unilateral contracts by dnoyeb · · Score: 1

      If I am not mistaken or IIANM as everyone on slashdot likes to lead off.. a contract is invalid if it does not benefit both parties. What is the benefit to the signer? satisfaction of curiosity?

    6. Re:Beware of unilateral contracts by Wavicle · · Score: 1

      Out of curiousity... My exposure to contract law is limited, but... Isn't a contract supposed to include payment of consideration to be valid? I know that in real estate transactions (which is where my experience comes from) family members can create contracts between one another with "love and affection" being the consideration. Is "getting to see SCO's source" considered payment of a consideration?

      --
      Education is a better safeguard of liberty than a standing army.
      Edward Everett (1794 - 1865)
    7. Re:Beware of unilateral contracts by captnjameskirk · · Score: 2, Informative

      Consideration does not have to be money. Probably the most used definition is "some right, interest, profit or benefit accruing to the one party or some forbearance, detriment, loss or responsibility given, suffered or undertaken by the other." The source is what SCO is giving as consideration. Losing the ability to freely discuss the code except as SCO permits is what the other party would give as consideration.

    8. Re:Beware of unilateral contracts by DarkHelmet · · Score: 1

      Hmmm, considering that you're a subscriber to slashdot, something tells me you'd sign the NDA, yes? ;)

      --
      /^[A-Z0-9._%+-]+@[A-Z0-9.-]+\.[A-Z]{2,4}$/i
    9. Re:Beware of unilateral contracts by PD · · Score: 1

      SHIT!! I hate it when I get my schwarz TWISTED!

    10. Re:Beware of unilateral contracts by PMCausey · · Score: 1

      IANAL, but I think yes, but only if SCO is dead and buried. A client of ours was subject to a non-compete agreement as the result of his sale of his companies to a publicly-traded entity. Well, the publicly-traded entity went out of existence, and the client was immediately able to go into the same business as before.

      Again, IANAL, but it would appear that the death of SCO would nullify any agreements that it reached.

      --
      I'm not really a CPA, I just play one on TV
    11. Re:Beware of unilateral contracts by greppling · · Score: 1
      What could the counterparty to SCO possibly gain by agreeing to this?

      Slashdot karma of course, by being able to post extremely well-informed comments! Any takers?

    12. Re:Beware of unilateral contracts by budgenator · · Score: 3, Insightful

      IANAL but the way I read it is if you sign, you cannot disclose anything that SCO relieved to you, even if you've seen it before. Particaly speaking if SCO stole or devised independently YOUR code, placed it in the relieved code, you could no longer distribute the code that they stole or devised independently without breaching the NDA. Nothing to gain, every thing to lose.

      --
      Apocalypse Cancelled, Sorry, No Ticket Refunds
    13. Re:Beware of unilateral contracts by budgenator · · Score: 1

      I don't think so, who ever bought the rights to unix Source code that SCO claims to own, would probably buy the NDA's also, no sense in buying copyrights, trade secrets, and trademarks ect unless you can control them.

      --
      Apocalypse Cancelled, Sorry, No Ticket Refunds
    14. Re:Beware of unilateral contracts by DarkHelmet · · Score: 2, Funny
      The ring! I can't believe you fell for the oldest trick in the book! What a goof! What's with you man, come on?

      </offtopic>

      --
      /^[A-Z0-9._%+-]+@[A-Z0-9.-]+\.[A-Z]{2,4}$/i
    15. Re:Beware of unilateral contracts by mkldev · · Score: 3, Interesting
      Which is 100% unenforceable. By law, an NDA becomes null and void if the material it covers becomes public, regardless of how it becomes public or when it became public... unless you made it public while under the NDA. If you have distributed the code previously, the NDA cannot cover it, regardless of language to the contrary.

      In effect, that means that the NDA is probably not worth the paper it is printed on, assuming that we're all correct that the code in qustion was just stuff AT&T stole from Berkeley back in the 80s.... That having been said, I wouldn't want to test that theory by signing the NDA and then publishing their source code.... :-)

      --
      120 character sigs suck. Make it 250.
    16. Re:Beware of unilateral contracts by gmhowell · · Score: 1

      YMBAL, BAYAJ (You Might Be A Lawyer, But Are You A Judge?) Unless you are, your opinion is worth... Not much. Until there's a trial, all we can rely on are best guesses. Granted, your guess is worth a hell of a lot more than mine, but the existence or not of mutual consideration is, I believe, up to a judge and/or jury.

      --
      Jesus was all right but his disciples were thick and ordinary. -John Lennon
    17. Re:Beware of unilateral contracts by TC+(WC) · · Score: 1

      The 'benifit' would be getting to see the source code. That's perfectly legitimate, it's just that nobody thinks it's worth signing the NDA to see.

    18. Re:Beware of unilateral contracts by rhizome · · Score: 1

      This would be an interesting form of legal martyrdom. To get access to the code and straight up posting it all over the place with your name on it and not even trying to be sly about it. P2P, FTP, WWW, IRC, it's time we put this internet thing through the proverbial wringer of the courts.

      --
      When I was a kid, we only had one Darth.
    19. Re:Beware of unilateral contracts by Anonymous Coward · · Score: 0

      Neither can I. IAAL, and the simple rule is that any ambiguities in a contract are to be interpreted against the part who wrote it. Contracts 1.01

    20. Re:Beware of unilateral contracts by Asprin · · Score: 1

      Entirely off-topic and straight out of Compton, I have exactly the same complaint about credit card companies - I hope they go out of business, too.

      --
      "Lawyers are for sucks."
      - Doug McKenzie
    21. Re:Beware of unilateral contracts by Firehawke · · Score: 1

      At the very least, it'd be interesting to see how it all worked out. No way in HELL I'd volunteer, though-- the risk is just a bit too much for my tastes, and the odds are little better.

    22. Re:Beware of unilateral contracts by anesq. · · Score: 1
      IAAAL (I Am Also A Lawyer), but rely on advice on an anonymous internet board at your own peril, obviously.

      Consideration is required in a contract, but consideration does not have to be in the form of something that is an advantage to the other side. SCO's consideration is showing the information. It doesn't matter whether the person seeing it is pecuniarily or otherwise advantaged by seeing the information. In essence, SCO is saying "In exchange for me agreeing to show you my stuff, you promise not to show it to anyone else." Companies do this all the time in the context of giving information to potential vendors, for example.

      In law school the example given is the young man who agrees to forgo wine, women and song until he is 25 in exchange for a promised large payment from his rich and straightlaced uncle. The nephew's pious life does not materially benefit the uncle in any way, but it's still consideration, and the contract is enforcable.

      That being said, this is an extremely restrictive NDA. I wouldn't hand it out with a straight face. I sure wouldn't sign it, at least without some serious modifications, including exceptions to the restrictions for publicly available information, disclosures required by law and a venue change to somewhere more convenient than Utah.

  3. More dirty SCO tricks by dtolton · · Score: 5, Interesting

    It is interesting to note that if what Ravichner is saying "the
    NDA does not exclude information that the recipient obtained in
    ways other than from SCO" is true, then signing the NDA could
    prevent you from disclosing any information about SCO code even
    if the court rules that SCO's distribution of the code (with
    Linux) made it public.

    So you could in theory be binding yourself to confidentiality
    with regards to SCO's code even if (when?) the ruling goes
    against SCO!!

    As SCO has said, binding legal agreements are far more
    compelling in a court of law than copyrights. I wouldn't touch
    that agreement with a ten foot pole.

    Unfortunately, as we knew it would be all along, this is just
    another ploy by SCO. They won't give you full access to the
    code, you can't talk about the specifics, they can bind you from
    disclosing already public information, and to top it all off,
    they can make you come to Utah to defend yourself in court.

    --

    Doug Tolton

    "The destruction of a value which is, will not bring value to that which isn't." -John Galt
    1. Re:More dirty SCO tricks by Anonymous Coward · · Score: 5, Funny

      I wonder if SCO is run by Scientologists...

    2. Re:More dirty SCO tricks by Anonymous Coward · · Score: 5, Funny

      Mormons. Same thing, except they have a database fetish.

    3. Re:More dirty SCO tricks by senrik · · Score: 1

      ~I wonder if SCO is run by Scientologists...

      Not Scientologists..... Raelians.

      --
      "the difference between myself and a madman is that I am not mad" -Salvadore Dali
    4. Re:More dirty SCO tricks by Anonymous Coward · · Score: 0

      At least they figured out
      long ago that the modern web
      browser can handle word wrapping
      without inserting additional,
      unnecessary line breaks. UNLIKE
      SOME PEOPLE.

    5. Re:More dirty SCO tricks by floppy+ears · · Score: 4, Insightful

      Not only that, but in theory, even if a court ordered you to disclose the "Confidential Information" you would not be allowed to do so under this agreement.

      I have seen hundreds of NDAs in my career, and practically every one of them that I have seen has an exception allowing you to make disclosures if ordered to do so by a court. This is very important; if you don't follow a court order, you could go to jail.

      And if this happened and you did follow the order, then you'd screwed under this agreement. Talk about putting yourself between a rock and a hard place ...

      --

      "If I could live to be several hundred
      I could take a walk and really wander, really wonder."
    6. Re:More dirty SCO tricks by hughk · · Score: 3, Informative

      No contract can prevent you from disclosing information in court. No contract can oblige you to do anything against the law. This is about as basic a contract law as you can get. An NDA that didn't give an execption about testimony is in itself on dubious legal grounds which is why it is explictly permitted.

      --
      See my journal, I write things there
    7. Re:More dirty SCO tricks by morgajel · · Score: 2, Informative

      like everyone else, IANAL.

      if your legally obliged to do something for the court, and their contract keeps you from doing it- hence the contract forces you to break the law- doesn't that make the contract itself null and void?

      I seem to remember somewhere that contracts can't be enforced if it requires a partymember to break the law.

      --
      Looking for Book Reviews? Check out Literary Escapism.
    8. Re:More dirty SCO tricks by Anonymous Coward · · Score: 0

      yes.

      it's like if you make a contract to kill somebody, you don't have to honor that contract.

    9. Re:More dirty SCO tricks by naarok · · Score: 2, Informative

      A small quible, but I believe it would only null and void the section that is requiring you to do something illegal. The remainder of the contract would still be in force. That is what section 9 "severability" covers.

    10. Re:More dirty SCO tricks by Anonymous Coward · · Score: 0

      Tenets of this particular Mormon sect:

      (1) Some one-to-one relationships replaced by one-many relationships.

      (2) Say the following: Codd, God. Coincidence? I think not.

      (3) A superset of SQL-92 was the Adamic Tongue.

      (4) There are actually several degrees of glory *higher* than fifth normal form!

      (This is probably only going to be funny to the union of database geeks and people actually familiar with Mormons, but what the heck!)

    11. Re:More dirty SCO tricks by chickenwing · · Score: 1
      So you could in theory be binding yourself to confidentiality with regards to SCO's code even if (when?) the ruling goes against SCO!!
      Yes, but it is hard to enforce for a company that is out of business to enforce such rights.
    12. Re:More dirty SCO tricks by Anonymous Coward · · Score: 0

      Easier to keep track of the wives and kids, eh :)

    13. Re:More dirty SCO tricks by geekee · · Score: 1

      Of course. Whether or not SCO is lying, you still shouldn't have the opportunity to post their code on the web. That's the point of an NDA. This is not a ploy. It's common sense. That said, of course anyone working on OSS should NOT sign this agreement. Once you do that, SCO can claim you saw their code and stole it, whther or not it's true.

      --
      Vote for Pedro
    14. Re:More dirty SCO tricks by Asprin · · Score: 1


      You know, with all these ridiculous stipulations, it seems to me that it would be a lot easier if we just download the Linux source and read the "offending" code out of there.

      What do they think we're gonna do -- *STEAL* it?

      --
      "Lawyers are for sucks."
      - Doug McKenzie
    15. Re:More dirty SCO tricks by MaggieL · · Score: 1

      (This is probably only going to be funny to the union of database geeks and people actually familiar with Mormons, but what the heck!)

      You must mean "intersection"....so I'm inferering you're from the LDS side.

      --
      -=Maggie Leber=-
  4. Ha! by krisp · · Score: 3, Insightful
    7. No Obligation to Disclose. SCO has no obligation under
    this Agreement to disclose to RECIPIENT any Confidential
    Information which SCO elects to withhold.


    In other words, we can show you only what makes us look as if we have a case
    1. Re:Ha! by Keeper · · Score: 1

      Question ...

      If their case is "there is code we own that is copied in linux", then wouldn't they have to show you the code that was copied? I mean, either they show it or they don't. If they show it, they make their point. If they don't, they don't make their point. How can you show a piece of code that makes their point while excluding other code which would negate their point?

    2. Re:Ha! by Pyre · · Score: 2, Insightful

      Suppose the two sides of the code are exactly the same (except for comments/whitespace). There isn't any proof of its origin. If I can be unscrupulous, copy a piece of code, and change the comments and copyright notices, I'm sure more experienced people can too. (No, I've never done so...)

      Small blocks of code simply aren't very interesting; lots of programmers use similar variable naming conventions and coding styles; and many people "reinvent the wheel" when writing small utility functions (atoi(), strstr(), etc. anyone?).

      AT&T, Novell, et. al. might have to come to SCO's rescue for any real proof, and I'm sure they want to get involved. Really.

    3. Re:Ha! by The_K4 · · Score: 2, Insightful

      If i'm reading this correctly IANAL but I think that you sign it, they show you the linux code, and then say end of show. IF you say ANYTHING you breach the contract. You can't even tell people that they didn't show you anything. This NDA is a smokescreen.

    4. Re:Ha! by haystor · · Score: 4, Insightful

      This NDA is useful for those people that may be interested in whether these claims are true, but aren't interested in developing kernels. Consider a client wavernig on whether or not to buy SCO or Linux support. They sign the NDA, SCO shows them they are the proper owners of the ultra-secret code, then they buy gobs of stuff from SCO.

      I don't believe that's the case here at all but that's not the fault of this NDA. It would be valuable and usable to someome.

      --
      t
    5. Re:Ha! by LoadStar · · Score: 2, Interesting
      If i'm reading this correctly IANAL but I think that you sign it, they show you the linux code, and then say end of show. IF you say ANYTHING you breach the contract. You can't even tell people that they didn't show you anything. This NDA is a smokescreen.

      The NDA allows the recipient to release a public statement regarding the materials shown - so if they screw you, you can legally release a statement that says so. Any further restraints would be infringing free speech rights and likely would be stricken as constitutionally invalid.

    6. Re:Ha! by Chakde+Phate! · · Score: 2, Insightful
      If their case is "there is code we own that is copied in linux", then wouldn't they have to show you the code that was copied?

      Yes, but there's more. To prove that Linux stole code off them, you would have to have access to their whole source tree.

      The only possible way to prove that IBM stole SCO's code is as follows:
      1. Produce source code which was allegedly in SCO before it was in Linux
      2. Prove the date it was added to Linux (this is easy, as source code from all the previous versions is archived)
      3. Prove the date it was in SCO
      The only way to do the last one is to compile a whole version of SCO from, say, 1995, using the code they submit, and compare it against an actual binary from 1995. You can only do this if you have access to all the source code for that release -- so this NDA is even more worthless!
    7. Re:Ha! by The_K4 · · Score: 1

      However if they tell you that there are NO lines of code, you cannot give any indication of that to the public without violating the NDA!

    8. Re:Ha! by ebh · · Score: 5, Informative

      [Claimer: I worked at USL and Novell doing configuration management for parts of Unix System V from 1993 to 1996. Disclaimer: I have no involvement with the development of Linux or any proprietary Unix now.]

      They probably won't have to go to AT&T or Novell for historical data, except as secondary verification. SCO has the source code repository (in ClearCase and in other formats) going back to 1984 and, for some things, earlier.

      IANAL, but if I were working for SCO and were asked to prove the charges, showing the matching code would only be the first step. The second step would be to show where the code was first introduced in the USL-originated repository. The third step would be to be prepare to show that the timelines in the repository were not altered (think "cleartool setevent"; this is where AT&T might come into the picture). The fourth step would be to show that the code was the IP of SCO or its ancestors from the day it was checked in (i.e., it's not itself stolen GNU code or something). The fifth step would be to show (possibly through subpoena of the AIX source repository) that the code in question was introduced into AIX as a result of a code drop from SCO or its ancestors. The sixth step would be to show (through examination of the Linux [etc.] repositories) that the code in question was introduced into Linux (etc.) as a result of a code drop from IBM subsequent to its being obtained from SCO.

      That's the easy (if time consuming) part, establishing the paper trail.

      The hard part is then proving that the transfer of the IP into the Linux source base was done knowingly (or whatever else would be actionable under the SCO/IBM contract), and that the Linux coders couldn't possibly have thought it up on their own (e.g., it can't be some algorithm every freshman CompSci student implements as a class project.)

      I really can't see SCO's "they can't possibly have had the knowledge or resources to build and test this" claim holding up. They're going to have to present much more convincing positive evidence than that.

      Good bloody luck.

    9. Re:Ha! by bobKali · · Score: 1

      Even if the 3 conditions you mentioned are met, it is still possible that the code from both Linux and SCO originated from a common source (i.e. the fact that chimps and humans share most of our DNA does not necessarily indicate that one of us evolved from the other, but rather that we evolved froma common ancestor.)

      Defending against this would require time to research the questioned code to locate its true common source. Something SCO could be trying to frustrate by not releasing which code is suspect to the community.

    10. Re:Ha! by Keeper · · Score: 2, Insightful

      While you can't say "there was no code shown" you can say "Based on what I saw I believe they don't have a case."

      And let's face it, if they have nothing, go to court, and then show nothing, they're going to lose anyway, so it's not exactly a big deal...

    11. Re:Ha! by saden1 · · Score: 1

      If were IBM I'd get hold of all the original authors of the alleged code that has been copied and ask them to testify that "this code is original and that there is no way anyone else could have written it without looking at his/here code."

      It is reasonable to assume that the alleged stolen code had long been developed in an academic setting before it ever found its way into UNIX.

      --

      -----
      One is born into aristocracy, but mediocrity can only be achieved through hard work.
    12. Re:Ha! by Keeper · · Score: 1

      The goal SCO intends with this "public showing" is to convince their audience that they do indeed have a case. If the people they show it to are smart enough to ask for this to be shown, either SCO shows it and convinces them (what they want), or lets their audience walk away unconvinced (what they don't want).

      Any way you look at it, it isn't a big deal. The "public" showing does nothing. It's not like the facts will change between the lawsuit and the "showing."

    13. Re:Ha! by Malfourmed · · Score: 3, Informative
      Consider a client wavernig on whether or not to buy SCO or Linux support. They sign the NDA, SCO shows them they are the proper owners of the ultra-secret code, then they buy gobs of stuff from SCO.
      So the NDA is a marketing tool.

      But then, so's the entire lawsuit...

    14. Re:Ha! by prockcore · · Score: 1

      7. No Obligation to Disclose. SCO has no obligation under
      this Agreement to disclose to RECIPIENT any Confidential
      Information which SCO elects to withhold.

      In other words, we can show you only what makes us look as if we have a case


      It's even worse than that.. they can simply call you up and say "there is no code, we don't have a case, we're bluffing" and you couldn't tell anyone.

      In fact, I bet that's exactly what they're doing...

    15. Re:Ha! by prockcore · · Score: 1

      Consider a client wavernig on whether or not to buy SCO or Linux support. They sign the NDA, SCO shows them they are the proper owners of the ultra-secret code, then they buy gobs of stuff from SCO.

      It seems to me that if they bought gobs of stuff from SCO, they'd be violating the NDA, because they'd be telling the public what SCO showed them.

      Maybe not directly, but they'd still be making a statement.

    16. Re:Ha! by geekee · · Score: 1

      I agree with the 1st part of your comment. However, if they can show a few hundred identical lines of code, and that they wrote it 1st, based on your strategy, they don't really need to do much else. The probability that two sets of code use the exact spacing and variable names is low. However, if they're trying to prove that the code was altered to make it look original, the case becomes much tougher. The whole "knowledge and resources" argement certainly won't hold up in court.

      --
      Vote for Pedro
    17. Re:Ha! by The_K4 · · Score: 1

      I believe that even if you said that, people could conclude that they had not shown you any code, and you would have "given" away that info. This NDA is drafted in a way that gives them alot of power over what you can say. Either way, i don't think it would be really worth the risks to ANYONE to sign this thing and get the "sneek preview" of their evidence. It's just more FUD.

  5. NDA for the NDA? by GGardner · · Score: 5, Funny

    I'm surprised that the NDA isn't under NDA itself.

    1. Re:NDA for the NDA? by rusty0101 · · Score: 1

      Sorry, that's a Microsoft trick. Probably pattented, and SCO isn't interested in paying Microsoft royalties for that process.

      -Rusty

      --
      You never know...
    2. Re:NDA for the NDA? by Rich0 · · Score: 2, Insightful

      While certainly cute, that couldn't actually fly. Well, you could have an NDA for the NDA, but that NDA could be published. An NDA isn't binding until it is signed, and prior to that point you can disclose it.

      Now, they could have an NDA for the NDA, so they will only show the main NDA after signing the smaller one. However, the first NDA you are shown could be disclosed. Then again, it probably wouldn't be nearly as juicy for amunition - it would just say something like you will never disclose anything you see on the next piece of paper to anyone for any reason...

    3. Re:NDA for the NDA? by killmenow · · Score: 1

      Perhaps part of Microsoft's recent SCO licensing agreement was a "cross-license", allowing SCO to use the NDA-of-NDA patent without paying Microsoft.

    4. Re:NDA for the NDA? by ShmuelP · · Score: 1

      As others have pointed out, the first NDA wouldn't be protected, and therefore that one could be disclosed.

      However, if the goal is to prevent disclosure of the NDA, an easier solution would seem to be to copyright it. That won't prevent someone from analyzing it and reporting the analysis of the NDA, but would at least prevent posting the whole text on the web.

      --
      Solution to blink tags: wrap them in another blink tag, with a javascript delay loop, so they cancel each other out
    5. Re:NDA for the NDA? by Anonymous Coward · · Score: 0

      Sounds more like an old school IBM CDA - Confidential Disclosure Agreement

    6. Re:NDA for the NDA? by kmahan · · Score: 2, Funny

      Probably a shrinkwrap license to make the NDA be under NDA.

      --
      Invalid Checksum. Retrying.
    7. Re:NDA for the NDA? by the+gnat · · Score: 4, Insightful

      Actually, that sounds quite a bit like shrink-wrap software EULAs, where you only get to see the license after you've already bought and opened the package.

    8. Re:NDA for the NDA? by BrynM · · Score: 1
      I actually thought twice about posting this because I bet some SCO jerk is reading this and might try something stupid...

      "an easier solution would seem to be to copyright it"
      Under current copyright law since it has been written it is copywritten. It does have an ever shrinking chance of entering the public domain someday though.
      --
      US Democracy:The best person for the job (among These pre-selected choices...)
  6. Be nice you guys.. by grub · · Score: 5, Funny


    SCO can only show you half the evidence now as they haven't made up the other half yet. Just be patient and play nice, boys.

    --
    Trolling is a art,
    1. Re:Be nice you guys.. by cshark · · Score: 5, Interesting

      Yeah. I was reading an article at news.com.com where mcbride was saying how they haven't finished assessing the scope of their case yet. Which seems odd to me bacuase companies usually know what the scope of your complaint is before your go around suing people. I mean, otherwise, how do you know what you're complaining about?

      --

      This signature has Super Cow Powers

    2. Re:Be nice you guys.. by Anonymous Coward · · Score: 0

      Utah: Nothing but frivolous SCO lawsuits and polygamy.

      Ya, those Winter Olympics were nothing. Only this three week event watched by billions

      The 5 national parks there are pretty wussy too. Arches? Sheer cliffs thousands of feet tall? Pure wilderness with no roads for many miles....ya, there's nothing exciting about Utah...

      But then Utah must suck, because it has SCO. It doesn't have any cool companies that attack SCO...like Novell...oh wait, Novell is a Utah company...

    3. Re:Be nice you guys.. by Anonymous Coward · · Score: 0

      You forgot to say that they don't have polygamy anymore. That ended in the 1850s. Talk about being behind the times!

      Random fact, the plural mariage rate of members of the LDS church was a bit above half of that of the country as a whole.

    4. Re:Be nice you guys.. by Anonymous Coward · · Score: 1, Insightful

      It seems to me that a Rule 11 motion against SCO and its attorneys would be in order, if SCO didn't properly asses the merits of its case before filing suit. Methinks McBride may have said too much!

    5. Re:Be nice you guys.. by siskbc · · Score: 1
      It seems to me that a Rule 11 motion against SCO and its attorneys would be in order, if SCO didn't properly asses the merits of its case before filing suit. Methinks McBride may have said too much!

      That's an interesting point - McBride seems to never clear his comments with the lawyers before opening his mouth. One damning one is that he's effectively suing IBM for possible linux malfeasances because Linus doesn't have any money. He's admitted to a reporter that IBM is just the local deep pockets. Nice going.

      --

      -Looking for a job as a materials chemist or multivariat

    6. Re:Be nice you guys.. by Anonymous Coward · · Score: 0

      Winter Olympics? Yeah and how much did it cost our state? What did we get in return other than a few weeks of tv coverage? Oh well, at least it isn't Jersey.

  7. NDA to sign the NDA by Anonymous Coward · · Score: 2, Interesting

    From what I read elsewhere, and I can't confirm it, but this is the 1st NDA you need to sign before seeing the real (2nd) NDA.

    I'm not kidding.

    P.S. SCO's stock is going up like crazy today. Big volume too.

    1. Re:NDA to sign the NDA by interiot · · Score: 1
      • P.S. SCO's stock is going up like crazy today. Big volume too.
      Yup, up 30% today. That's okay though; short high, sell low.
    2. Re:NDA to sign the NDA by AndroidCat · · Score: 1

      I'm suprised that I haven't received pump and dump spam regarding them yet. Give it time.

      --
      One line blog. I hear that they're called Twitters now.
    3. Re:NDA to sign the NDA by EvilAlien · · Score: 1
      Thats because investors have realized that SCO has signed a secret deal with Microsoft that will mean great profits.

      In return for megabucks from Redmond, SCO has agreed to make itself much more hated than Microsoft, thereby allowing Microsoft to win the hearts and minds of the /. hoards... after all, they'll be too busy hating SCO to defend against Microsoft trickery.

      --
      perl -e 'print $i=pack(c5, (41*2), sqrt(7056), (unpack(c,H)-2), oct(115), 10)'
    4. Re:NDA to sign the NDA by TheDredd · · Score: 1

      so the 2nd NDA will be something along the lines like:

      We have no case
      There is no source
      but our stock is skyrocketing!

  8. Picture? by sporty · · Score: 3, Funny
    They're agreeing to let you see the half of the picture that they want you to see.


    Well, if a picture is worth a thousand words, and half a picture is prolly worth about 500...

    I say we use those 500 words and tell sco the many ways to "get bent".
    --

    -
    ping -f 255.255.255.255 # if only

    1. Re:Picture? by Anonymous Coward · · Score: 0

      Screw Flanders.

    2. Re:Picture? by Monkelectric · · Score: 1

      Except its a logarithmic progression, half a picture is worth 2.698 words.

      --

      Religion is a gateway psychosis. -- Dave Foley

    3. Re:Picture? by Anonymous Coward · · Score: 0

      Half a picture is still a full picture. It's just cropped differently.

    4. Re:Picture? by not-folly · · Score: 3, Funny

      Then my 2.698 words would be "Get bent, SC..."

      --
      Karma: Sucks (Mostly due to the fact that you suck)
    5. Re:Picture? by p3d0 · · Score: 1

      How did you arrive at that number?

      --
      Patrick Doyle
      I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
    6. Re:Picture? by TFloore · · Score: 1
      Well, if a picture is worth a thousand words, and half a picture is prolly worth about 500...

      Well, the best way I know to get bent is to go scuba diving for longer than your dive ocmputer or dive tables say you can, and ascend rapidly with no decompresison stops. 30 minutes at 130ft should do it, diving air.

      But that took way less than 500 words.
      --
      This is my sig. There are many like it but this one is... Oops. Frank, I've got your sig again! Where's mine?
    7. Re:Picture? by Anonymous Coward · · Score: 0

      They already have their heads up their collective asses, how much more bent can they get?

    8. Re:Picture? by meringuoid · · Score: 1
      Hmm... so, we have half a picture in which to tell SCO what we think of them...

      www.goa...

      --
      Real Daleks don't climb stairs - they level the building.
    9. Re:Picture? by Monkelectric · · Score: 1

      log(500), but it was a joke ... wasn't supposed to make too much sense

      --

      Religion is a gateway psychosis. -- Dave Foley

    10. Re:Picture? by p3d0 · · Score: 1

      Oh I see. So a whole picture is worth 3 words.

      --
      Patrick Doyle
      I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
    11. Re:Picture? by sporty · · Score: 1

      Nono.. half the picture follows log().

      --

      -
      ping -f 255.255.255.255 # if only

  9. I made a copy of the NDA by Anonymous Coward · · Score: 4, Funny

    and sent it to them next day mail. I signed it Linus Torvalds.

  10. nda my heart by double_plus_ungod · · Score: 1

    this is a big question i have: why show evidence if you're just gonna hush up those who see it? that doesn't make any sense to me if they really do have a case to make against linux.

    1. Re:nda my heart by Lxy · · Score: 4, Insightful

      I think the purpose is twofold. For one, SCO thinks they have a claim, and want people to able to back them up. Let's say Linus looks at the source and says that indeed, SCO has a case. SCO now has the re-affirmation from Linus himself that they have a case, and Linus can now publicly say "watch out, they have a case". He can't do anything more than that, but he can at least strengthen SCO's point. Also, they can then subpoena Linus in court.

      The second reason is to find out if they really have a case. If Linus can prove to SCO that they're full of BS, SCO can back out now before they lose everything they have in legal fees. They'll need that money, since no one on Slashdot will pay SCO for anything ever again.

      Yes, I realize that Linus has already stated that he won't look at the code, for good reasons, I just used him as an EXAMPLE.

      --

      There is no reasonable defense against an idiot with an agenda
      :wq
    2. Re:nda my heart by stratjakt · · Score: 1

      slashbots are a hoot

      They'll need that money, since no one on Slashdot will pay SCO for anything ever again.


      I mean you'd think someone on slashdot had paid for it before. They have much more to gain, and little to lose. They'll drum up business no matter what you, or Linus, think.

      --
      I don't need no instructions to know how to rock!!!!
    3. Re:nda my heart by ichimunki · · Score: 3, Informative

      Linux: Telling Microsoft where to go since 1991

      With respect to your sig: I believe Linux was originated due to problems with Minix, which is not a Microsoft product. Just a thought.

      --
      I do not have a signature
    4. Re:nda my heart by jedidiah · · Score: 4, Insightful

      EVERYONE ELSE bought from SUN, IBM & HP before this little stunt, and everyone else will continue to buy from SUN, IBM & HP afterwards.

      The fact that SCO is a sue happy little pissant isn't going to impress anyone that's potentially interested in a robust Unix server.

      This might harm Linux, this might help Microsoft, there's even a slim chance that it will harm Unix in general. However, SCO is still going down the toilet.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    5. Re:nda my heart by ninewands · · Score: 4, Interesting
      Quoth the poster:
      I mean you'd think someone on slashdot had paid for it before. They have much more to gain, and little to lose. They'll drum up business no matter what you, or Linus, think.

      You forgot your </i> tag after the quote, but that's not the point of my responding to your flamebait instead of modding you down. Modding down stifles discussion, while responding stimulates it.

      I have official boxed sets of several Linux distributions. I pay for them with my employers' money in order to support free software companies. (I'm a *n*x admin at a large university). My employer supports me in this practice. However, in truth, when I install a new Linux box, I boot up from the CD and install the distro over the 'net so that it comes up with the most up-to-date packages already installed.

      That being said, I've never bought a SCO (nee Caldera) distro because I've never thought they had anything to offer over and above the base Debian distro they built from. Their recent behavior has put me in the frame of mind that even if they DID offer a significant improvement over the base Debian distro I would not buy their product, so, yeah, there ARE slashdotters who pay for Linux and who will NOT ever buy from SCO as a result of this lawsuit.

      Just my $0.02
    6. Re:nda my heart by buss_error · · Score: 1
      Yes, I realize that Linus has already stated that he won't look at the code, for good reasons, I just used him as an EXAMPLE

      Linus has to keep "clean hands". In this case, he can't look at code under an NDA. This allows him to refute any charge "YOU COPIED MY CODE!!!!" by saying, "But I never saw your code. How could I have copied it?"

      Now, the pun on "Clean Hands" and SCO code is obvious, so let's just let it go.

      --
      Necessity is the plea for every infringement of human freedom. It is the argument of tyrants; it is the creed of slaves.
    7. Re:nda my heart by dnoyeb · · Score: 1

      Actually, Linus position is meaningless because he can not disclose it. He can NOT say, "hey they have a case" because that would be against the NDA. Just like saying, "they have no case" would also be against the NDA.

      But yes, if they are super confident, they can subponea Linus, without knowing his position. (though I am sure he can disclose his opinion to them)

      I agree with your 2nd point totally.

    8. Re:nda my heart by Anonymous Coward · · Score: 0

      (I'm a *n*x admin at a large university).

      *N?X surely, i cant think of any UNIX derivative or clone that requires a '*' rather than a '?', using it would make your term overly loose. please amend accordingly, kthxbye.

    9. Re:nda my heart by ssdairy · · Score: 1

      ... saying "they have no case" would also be against the NDA.

      Is this possibly a way for SCO to silence some of its critics? Don't believe us, we'll show you the code under NDA. After reviewing the code, if you still don't believe us, too bad, you can't talk about it any more.
    10. Re:nda my heart by mark-t · · Score: 1
      Let's say Linus looks at the source and says that indeed, SCO has a case. SCO now has the re-affirmation from Linus himself that they have a case, and Linus can now publicly say "watch out, they have a case". He can't do anything more than that, but he can at least strengthen SCO's point.
      What I would do if I were Linus is sign the thing. And if I felt SCO had a case, I would then proceed to remove the code from Linux. I would give no announcement whatsoever about the reasons for the changes beyond an obscure "I felt that these changes needed to be made". SCO has no legal right to dictate what a person can or cannot have personal feelings on, even under NDA, so that would be the end of it. SCO could continue to pursue their case for copyright infringement or trade secret violation in the first place (if it ever was legitimate, SCO would have legitimate rights to compensation, even though their code had been removed from the picture.)

      Now granted, the entire Open source community would then be abuzz with speculation about the premise that the code that was changed actually belonging to SCO, but if nothing was ever actually said, then the NDA wouldn't be getting broken.

    11. Re:nda my heart by Anonymous Coward · · Score: 0

      The minute Linus Torvalds signs the NDA he will be SCO's bitch for life. Any change he makes to the Linux kernel will have to be diffed against the code he saw. If he mistakenly reconstructs something from the SCO code in Linux, he'll be sued into oblivion. So I praise heaven that you are not Linus Torvalds.

    12. Re:nda my heart by Lxy · · Score: 1

      The reason Linus won't sign is that every piece of code he works on from that point is either scrutinized by SCO or banned altogether. If any linux coder signs this NDA, the proper thing to do would be to ban them from contributing code to the kernel. They are now contaminated with the knowledge of SCO's code, which could actually lead to a new problem: knowly adding SCO code to the kernel.

      It's a messy proposition, which is why SCO can't find anyone to sign their NDA.

      --

      There is no reasonable defense against an idiot with an agenda
      :wq
    13. Re:nda my heart by Anonymous Coward · · Score: 0

      I've bought four boxed cds of Linux distributions for home, one for work (the only non-Windows machines on the premises are my Linux box and my Mac). So yes, here's another /.er who pays for Linux and will not ever buy from SCO.

    14. Re:nda my heart by mandolin · · Score: 1
      That being said, I've never bought a SCO (nee Caldera) distro because I've never thought they had anything to offer over and above the base Debian distro they built from

      Caldera's distribution was RPM-based. AFAIK it had nothing to do w/Debian.

    15. Re:nda my heart by Anonymous Coward · · Score: 0

      I agree SCO is fucked! I don't know why anyone would want to use it before this whole fiasco. They'd have to be living in a cave if they are to keep using it.

    16. Re:nda my heart by steveg · · Score: 1

      As a matter of fact, they claim to have designed RPM for Red Hat. RH disputes this :)

      --
      Ignorance killed the cat. Curiosity was framed.
    17. Re:nda my heart by Anonymous Coward · · Score: 0

      knoppix. A linux distro.

    18. Re:nda my heart by Anonymous Coward · · Score: 0

      > Is this possibly a way for SCO to silence some of its critics? ...

      Only the stupid/foolish ones.

    19. Re:nda my heart by Anonymous Coward · · Score: 0

      They'd have loved to have gotten Linus and other developers to sign and look at even 10 lines of their code. Then it would be the end of their participation in OSS and possibly employment with any software company due to "tainting".

    20. Re:nda my heart by Anonymous Coward · · Score: 0

      The fact that SCO IS SUE HAPPY means my company won't even consider SCO products since there are other equal or better products out there from companies that won't sue you just for being their customer.

    21. Re:nda my heart by dnoyeb · · Score: 1

      had not thought of that. Simple and clean. It was worth a shot :)

  11. SCO's Position: Sign it or Don't See the Goods. by Mr.+Balsakon+Yurchen · · Score: 1

    Seeing part of the picture is better than none of the picture. Hopefully, we will have enough old men for an accurate interpretation of the elephant. Unfortunately, this is SCO's show and they can take their ball home: for now.

    --
    Kill the White Man
    1. Re:SCO's Position: Sign it or Don't See the Goods. by tomhudson · · Score: 5, Interesting
      Seeing part of the picture is better than none of the picture.</quote>

      Really? I'm of the opinion (and I think most reasonable people would agree) that if someone wants to pick and choose what they show, htey have something to hide.

      So, what are they hiding?

      It's pretty obvious - the fact that they don't have a case. After all, the the code is in fact already in open-source software, it's already public.

      I certainly wouldn't want to look at their piece-of-shit code, just like I wouldn't want to look at anything coming from the Beast of Redmond - to avoid future charges of infringement/theft/copying.

      End result: Anyone stupid enough to go along with this qualifies for the darwin awards. They've certainly removed themselves effectively from the pool of OSS developers.

    2. Re:SCO's Position: Sign it or Don't See the Goods. by Anonymous Coward · · Score: 0
      Seeing part of the picture is better than none of the picture
      In that case, I have made this really nifty program. It can do everything Linux can do, and more. It is not GPL, and some idiot has stolen my code and put it into Linux.

      I can prove it, too. If you sign this really obnoxious piece of paper, I can show you the pieces of code that are mine in the Linux kernel. No, really! *copypaste* See how similar they are! Isn't this awful? Let us go and tell the courts, huh?

      I also have this bridge you may want to have a look at.

    3. Re:SCO's Position: Sign it or Don't See the Goods. by jgerman · · Score: 1

      Not to mention it will be entered into public record again if the case goes to court.

      --
      I'm the big fish in the big pond bitch.
    4. Re:SCO's Position: Sign it or Don't See the Goods. by CVaneg · · Score: 1
      Seeing part of the picture is better than none of the picture. Hopefully, we will have enough old men for an accurate interpretation of the elephant


      That assumes that SCO lets people see different parts of the code, when in reality they will most likely display the same parts of the code to anyone willing to sign the NDA. So instead of the classic result of the story where each blind man senses a different feature of the elephant, each man is steered toward the same feature of the elephant without comprehending the whole.

    5. Re:SCO's Position: Sign it or Don't See the Goods. by Anonymous Coward · · Score: 0

      The NDA is the thing that's going to stuff them up in court. SCO have made absolutely no attempt at mitigation for the claimed infringement. The way an IP case usually works is this:

      Company A discovers an infringement of their IP in a competitors product.

      Company A contacts Company B and Demands removal of the infringing IP from Company B's Product.

      If Company B complies with the request, the case is closed.

      If Company B doesn't comply, _then_ Company A goes to court to seek removal and damages.

      We all know that if SCO publicised the code it would be removed from Linux within a matter of hours. The Linux community hates IP problems and doesn't want it to be any part of Open Source.
      SCO is withholding the code _only_ so that they have something to sue over. This doesn't go over well with a Judge.

      Even if SCO has a claim (which I don't believe they do) The fact that they have not tried to get anyone (IBM, Linux Community, et al) to do something about it, they just ran to court and are trying to sue for a billion dollars. They're showing that they aren't "offended" by the IP infringement, they just want money.

      Bye Bye SCO...

  12. I just saw the code... by Anonymous Coward · · Score: 5, Funny
    it seems like the infringing part is the following:
    // you are not supposed to understand this
    1. Re:I just saw the code... by (startx) · · Score: 0, Offtopic

      that's a C++ style comment. Since UNIX is in C I'm sure the infringing part is more like

      /* you are not supposed to understand this */

    2. Re:I just saw the code... by loucura! · · Score: 1

      Ah, but GCC allows you to compile c programs with C++ style comments.

      --
      Black and grey are both shades of white.
    3. Re:I just saw the code... by GGardner · · Score: 1
      Everyone knows that it is

      /* You are not expected to understand this */
    4. Re:I just saw the code... by Anonymous Coward · · Score: 0

      Not if you use -ansi ;)

    5. Re:I just saw the code... by tuffy · · Score: 1
      Ah, but GCC allows you to compile c programs with C++ style comments.

      That shouldn't be surprising, since C++-style comments are C99 compliant. Thus, any compiler implementing the C99 standard should support them.

      --

      Ita erat quando hic adveni.

    6. Re:I just saw the code... by unborn · · Score: 1

      Which would of course mean that SCO has used GCC-suited code stolen from the GNU community.

    7. Re:I just saw the code... by taniwha · · Score: 1

      yes - but b/* you are not expected to understand this */ predates not only GCC but modern C - it comes form a day when "i =+ 1" was the valid syntax (and "I += 1" was not). And where structure fields lived in their own global name space (don't ask - it let you implement unions in a particularly sad way)

    8. Re:I just saw the code... by loucura! · · Score: 1

      But that predates both Linux and SCO anyway, so your point is moot.

      --
      Black and grey are both shades of white.
    9. Re:I just saw the code... by tlk+nnr · · Score: 1
      According to this website this comment is in the Sixth Edition Unix source:

      *
      * You are not expected to understand this.
      */

      And in linux-1.2.13/mm/swap.c:
      /*
      * Buddy system. Hairy. You really aren't expected to understand this
      */


      The same sentence in Sixth Edition Unix and the Linux source code - an obvious case of malicious infringement of a valuable trade secret owned by SCO in the Linux kernel. The only change is "You really aren't" instead of "You are not" - additionally evidence this is willful infringement: The infringer was aware of what he was doing and did a minor change, to hide the evil theft.
    10. Re:I just saw the code... by A+non-mouse+Cow+Herd · · Score: 1

      Which would of course mean that SCO has used GCC-suited code stolen from the GNU community.

      When I worked on a product that ran on SCO, we found a bug in their compiler that made it not work, their tech support reply was basicly "What, you are using the SCO compiler ? Use GCC instead. That's what we do." That doesn't mean they stole GCC of course, just that they downloaded it like everyone else.

    11. Re:I just saw the code... by Anonymous Coward · · Score: 0

      But that predates both Linux and SCO anyway, so your point is moot.

      But not the Unix codebase that SCO owns... may own... has rights to... something like that.

    12. Re:I just saw the code... by loucura! · · Score: 1

      Well, granted, but according to Novelle, they have no rights to, and do not own. SCalderaO is just acting as an aggressive licensing unit... AFAICT

      --
      Black and grey are both shades of white.
    13. Re:I just saw the code... by budgenator · · Score: 3, Informative

      a SCO system is pretty useless by Linux standards, scripting is all bourne shell, AWK, and TCL/TK; the utilities are all vintage 70's stuff like more (can't back scroll) rather than less and vi rather than emacs or vim. So what must people who actualy use or admin SCO systems do is install some modern GNU utilities, Perl, and of course GCC.

      The other thing to remember is that most SCO systems aren't used for anything except running one vertical app. Ours runs Command Dental System, a cobol suite of programs that are multi-user over serial lines to wyse 60 terminals. It was ported over from xenix, and what was funny is SCO changed from curses to ncurses when they change from 16 bit xenix to 32 bit openserver and this cause bizzar characters to appear in the screen boarders and support(Command Dental) couldn't figure out that the only thing they had to do to correct it was to change the systems default font!(I didn't dare change it myself because with a support contract, if you change anything, everything is forevermore your fault.)

      An other area that SCO had good penatratrion in is resturants, multiple waitress stations intputing orders with touch screens and swipe cards.

      --
      Apocalypse Cancelled, Sorry, No Ticket Refunds
    14. Re:I just saw the code... by budgenator · · Score: 1

      SCalderaO, I like that, when I read it, it gives me a mental picture of a cat leaping into a pot of boiling water, which is about as self-destructive as insulting 3/4 of your customers that use linux at home and wished that they had it at work instead of unixware/openServer, and at the same time picking a fight with IBM.

      --
      Apocalypse Cancelled, Sorry, No Ticket Refunds
    15. Re:I just saw the code... by taniwha · · Score: 1

      ummm - I'm not sure my point had anything to do with SCO or Linux ... I think I was trying to put that particular comment (which I stared at over and over when I first ported V6 to another platform - untill it did become obvious) in context

    16. Re:I just saw the code... by d^2b · · Score: 1
      According to someone who drank the NDA koolaid, you may be correct.

      Apparently amoung the evidence presented by Caldera/SCO is that there are comments allegedly copied from SysV to Linux.

      Well, for those of you who believe analysts, that pretty much settles it. Mind you, you probably lost all your money on Telecom stocks, so SCO is unlikely to sue you anyway :-)

    17. Re:I just saw the code... by tonyl · · Score: 1
      scripting is all bourne shell, AWK, and TCL/TK; the utilities are all vintage 70's stuff like more (can't back scroll) rather than less and vi rather than emacs or vim. So what must people who actualy use or admin SCO systems do is install some modern GNU utilities, Perl, and of course GCC.

      While SCO has been slow with this stuff, modern versions have had Perl for a while and the latest 5.0.7 has most of what you'd expect a modern Unix system to have. See http://aplawrence.com/Reviews/osr507.html if you care.

      I don't disagree with the rest of your post, though the "bizarre" characters problem probably could have been solved some other way:

      http://www.pcunix.com/SCOFAQ/scotec2.html#oldapps

      and http://www.pcunix.com/SCOFAQ/scotec2.html#mapchan

      --
      -- Tony Lawrence
  13. Its assholes like SCO... by dangermurphy · · Score: 1

    .. who hold back progress. Nothing like a bunch of crappy press to shelf that new OSS project for another year. Looks like well have to develop on the mainframe in COBOL74 again. Dicks.

  14. Phew! by Archangel+Michael · · Score: 4, Funny

    And to think, I was having SCO news withdrawal.

    This should fix me till Monday!

    --
    Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
  15. courtesy of nasdaq... by peterprior · · Score: 4, Informative

    Symbol Last Sale Change Net / %
    SCOX $ 8.48 1.88 +28.48%

    do they know something we don't ?

    1. Re:courtesy of nasdaq... by tuffy · · Score: 1
      do they know something we don't ?

      Doubtful. Investing in SCO is like betting $1 on the lottery. Most likely it's a waste of cash, but there is that one in a billion chance it'll turn out big.

      --

      Ita erat quando hic adveni.

    2. Re:courtesy of nasdaq... by Anonymous Coward · · Score: 0

      Unfortunately, I think the problem is that they do not know what we know.

    3. Re:courtesy of nasdaq... by Arker · · Score: 4, Interesting

      No, it's just the gambling instinct.

      Although we all know SCO doesn't have a case, most investors aren't that savvy. Plus, even without a case, you always have a chance in the US - you can pull a crazy judge after all. So the investors are figuring, maybe they win, maybe IBM settles or buys them out... if either of those things happened SCO stock could suddenly be worth a lot more. There's always a good amount of money in the stock market looking for the high risk gamble-moves that could bring a good payoff. Most of those investors, of course, are sensible enough to keep the bulk of their holdings in safe stuff, but they still budget a certain percentage for risky buys... anyway I'd figure those are the buyers. The sellers are probably the SCO executives and their pals, who presumably have a more realistic understanding of their chances.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    4. Re:courtesy of nasdaq... by GoofyBoy · · Score: 1

      28% on large volume?

      What is different from today from yesterday? Thats something to think about.

      --
      The surprise isn't how often we make bad choices; the surprise is how seldom they defeat us.
    5. Re:courtesy of nasdaq... by n0ano · · Score: 4, Funny
      Maybe the market is reacting to the news that Microsoft can't innovate, most innovation is coming from Open Source and since SCO is a big defender of open source then....


      On second thought the more likely answer is that people who buy stocks are idiots

      --
      Don Dugger
      "Censeo Toto nos in Kansa esse decisse." - D. Gale
    6. Re:courtesy of nasdaq... by Anonymous Coward · · Score: 1, Informative

      It's interesting, the earliest slashdot story I could find on the SCO saga is this one from January, and look at the 6 month graph. Stock price going up as SCO gets more and more media attention, perhaps?

    7. Re:courtesy of nasdaq... by Anonymous Coward · · Score: 0

      Umm, a PR related NDA stunt?

    8. Re:courtesy of nasdaq... by BigBadBri · · Score: 1
      Nah - it's just that they've finally settled on the NDA, which gives investors the sense that they're serious about the lawsuit.

      As soon as the early investors figure the stock has moved enough, they'll bail out again.

      Besides, what else are they to do with all the cash they pulled out of Big Blue after the SEC investigation story?

      --
      oh brave new world, that has such people in it!
    9. Re:courtesy of nasdaq... by PhxBlue · · Score: 1, Insightful

      What is this, fortune-telling through NASDAQ? You'd have better luck reading SCO's future with tea leaves than looking at a one-day stock price. If you look at the longer-term trend of their stock over the last quarter or year, that's actually useful information. A one-day rise or fall, in and of itself, is a hiccup.

      --
      !#@%*)anks for hanging up the phone, dear.
    10. Re:courtesy of nasdaq... by interiot · · Score: 2, Interesting
      • Although we all know SCO doesn't have a case, most investors aren't that savvy.

      I'm just curious how many slashdotters have shorted SCO's stock. I've been told it's a bad idea for stock market newbies to jump right in with shorting, but this seems like a good bet...

    11. Re:courtesy of nasdaq... by Jason+Earl · · Score: 5, Insightful

      SCO management knows that if they can keep their story in the news then people might start to believe they actually have a case.

      The fact of the matter is that SCO isn't aiming their press release at members of the Linux community (or even members of the larger computing community), they are aiming these press releases at the large population of rubes that might be interested in gambling on an "insider deal." SCO's allegations are ridiculous to anyone with any knowledge of the situation, and their tactics are crude and hamhanded to any with an inkling of knowledge about the case. The mere fact that they keep issuing press releases should trigger alarm bells. Everything SCO management says is evidence, if they were trying to win they would listen to their legal counsel and do their talking in court.

      In short, SCO isn't trying to win a court case; they are trying to hype their stock.

      To an outsider their case looks like a bunch of poor underdogs who have are fighting an IBM Goliath. SCO's target audience doesn't have a clue about source code or NDAs, and to them the offer to prove their case almost certainly looks genuine. These people don't know about the GPL or the UC Berkeley AT&T court case. They don't even know that SCO isn't Santa Cruz Operations (the former UNIX company), but that SCO is really just Caldera (the former Linux company). They simply see that a small company claims to have rights to some code, and some journalists (and Microsoft) keep adding credence to their story.

      This is a pump and dump scheme, nothing more, nothing less. Think of it as a variation on the Dot Com Boomers that hyped their stock up to the moon despite the fact that they knew that they had no chance of making a profit. Everyone makes fun of the dot com management teams, but they weren't stupid. They weren't selling pet food, or medical advice, their stock price was the real product they were hawking. The guys that founded those companies generally made a big fat pile of money at the subsequent investors expense. And it was all perfectly legal.

      SCO management is in a similar position. They aren't going to win their case, but that doesn't matter, because right now their stock is what they are really selling. The difference is that the "Big Lie" in this case isn't that online commerce is going to change the world. The story this time is that scrappy SCO from Lindon, Utah has got IBM by the short hairs. It's pure @#$!!, but it plays well on TV.

      As long as the SCO insiders jump through SEC hoops when they sell (and they have plenty of time to sell), and as long as they don't laugh out loud while pretending they have a case, it's all perfectly legal.

      Caveat Emptor.

    12. Re:courtesy of nasdaq... by Shadow+Wrought · · Score: 1

      According to the sticky remnants of this morning's hot chocolate and coffee (poor man's mocha), SCO is still looking for a case. I would tell you more (third cushion on the left *wink*)but there is this NDA thingy...

      --
      If brevity is the soul of wit, then how does one explain Twitter?
    13. Re:courtesy of nasdaq... by Arker · · Score: 1

      I'd be very careful doing this. If I understand correctly, shorting is essentially a bet on the price going down within a particular timeframe. I'd be quite sure SCO stock will be worthless when this is over, but it could take quite some time, and it could easily go up before it goes down...

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    14. Re:courtesy of nasdaq... by Elwood+P+Dowd · · Score: 1

      No, it's just the gambling instinct.

      Amen. It always cracked me up to hear my boss on the POE floor talk about how marker makers were necessary because they added stability and sanity to an otherwise irrational market - and then weeks later he'd be calling us frantically:

      "Is there a buyout at sixty? There's a rumor here that IBM|Microsof|McDonalds|Pepsi is making a buyout at sixty! Have you guys heard anything? What's going on? [froth][froth]"

      Of course, he wasn't the kind of guy to act on that BS, but the pits were certainly full of them. This recent spike doesn't necessarily relate to news, insider trading, or anything in any way even vaguely resembling reality.

      --

      There are no trails. There are no trees out here.
    15. Re:courtesy of nasdaq... by arkanes · · Score: 1

      Because when it was 5% on small volume a bunch of people saw it going up and started a stampere. You don't think the stock market works on logical principles, do you?

    16. Re:courtesy of nasdaq... by jbr439 · · Score: 1

      Despite what others are saying, these kind of large
      movements rarely happen without a trigger of some sort. It could be news, it could be rumour; but there's usually something causing it. So, I would say, yes, something has happened that we are currently unaware of. The true importance of this something is a different issue altogether.

    17. Re:courtesy of nasdaq... by Josh · · Score: 2, Interesting

      They heard fundamental data today that Linux was doing really well in the server market and also that Microsoft is afraid of Linux (all Linux stocks went up, VA Linux went up even more), and they are confused enough to think that SCO may somehow "own" an important chunk of Linux.

    18. Re:courtesy of nasdaq... by pyrrho · · Score: 1

      you are 100% correct imo. But furthermore, sign a contract with SCO (e.g. the NDA) and they have more to sue you for. It's like a fishing expedition. Trolling in the legal sphere.

      --

      -pyrrho

    19. Re:courtesy of nasdaq... by u-235-sentinel · · Score: 3, Funny

      They are getting ready for the lawsuit against SCO when the stock collapses :D

      --
      Has Comcast disconnected your Internet account? Same here. You can read about it at http://comcastissue.blogspot.com
    20. Re:courtesy of nasdaq... by Jason+Earl · · Score: 2, Insightful

      I wouldn't sign anything SCO management gave me. The only good news is that eventually this case will either go to trial or SCO will go out of business.

      Here's to hoping that the SCO management gets so greedy that they make a mistake and the SEC nails them to a tree.

    21. Re:courtesy of nasdaq... by Anonymous Coward · · Score: 0

      hmmm ... possible behind the scenes BIDDING WAR between IBM and Microsoft? Darl McBride vaulted into "most revered" CEO status alongside Neutron Jack? Who knows?

    22. Re:courtesy of nasdaq... by capnjack41 · · Score: 1
      fuckin' M! I was thinking about buying just a few shares of SCO the other day (when it was $6). I could have made a few bucks (140%).

      If I were to buy just like 10 shares from one of those cheapo brokerage things, the most I'd lose is under $100, but if they win the suit with IBM, get bought by IBM/whoever then I'd make some cash, and end up with stock with another company. Right? (I don't really know how this stuff works)

    23. Re:courtesy of nasdaq... by c0dedude · · Score: 1

      yeah nasdaq loves asshats who sue people for no good reason. Generates publicity and buzz around a stock. Not only that, SCO is looking pretty damn powerful with those threatining letters. All moronic reasons to buy stock, but popular ones.

      --
      Since when has this country used intellectual elite as a pejorative term?
    24. Re:courtesy of nasdaq... by michael_cain · · Score: 1
      As long as the SCO insiders jump through SEC hoops when they sell (and they have plenty of time to sell), and as long as they don't laugh out loud while pretending they have a case, it's all perfectly legal.
      IANAL, but I think you've exaggerated at least a little. If they have no case and they know it -- for example, they know that the evidence was all forged -- then it's criminal fraud and any profits they realized selling shares will be taken from them. Proof in court of stock fraud is often difficult, but the authorities seem to be having some success in some of the more egregious recent cases like Enron and Worldcom.
    25. Re:courtesy of nasdaq... by geekee · · Score: 1

      "Although we all know SCO doesn't have a case..."

      If you haven't signed the NDA and looked at the evidence, you know nothing, like everyone else. The investors are taking a long shot that SCO'll get some money or be bought by IBM. Given that Cadence won a similar case against Avant!, it's not impossible for SCO to win, if they're telling the truth.

      --
      Vote for Pedro
    26. Re:courtesy of nasdaq... by chance2105 · · Score: 1

      Oh yeah. Agreed. When the lie gets big enough, eventually it starts to look as if it wraps around the other end ...

    27. Re:courtesy of nasdaq... by Jason+Earl · · Score: 1

      SCO's evidence isn't forged. Their case is simply ridiculously flimsy.

      Enron and Worldcom are different. What these companies did was inherently illegal. They knowingly broke GAAP rules, and then foisted this bad information off on investors. SCO, on the other hand, simply is overstating their case. Think of it as VA Linux pretending it was going to be able to compete with Dell long-term in the Linux server business. It could have happened, but it wasn't particularly likely. Notice how none of the VA Linux guys ended up in jail when their stock went through the roof. Even those that sold stock at ridiculously high levels weren't breaking the law.

    28. Re:courtesy of nasdaq... by michael_cain · · Score: 1

      In fact, no one outside of a few people at SCO really know whether their case is strong, flimsy, or forged, because they're not showing anyone enough to make an informed judgement. Overstating the case is one thing. Actually forging evidence would be quite another, and just as inherently illegal as lying about your accounting.

      The saddest part of this, for me, is that corporate capitalism in the U.S. has reached a point where so many companies have been caught cheating that it doesn't seem unreasonable to entertain the idea that SCO might be cheating too...

  16. break the NDA? by jamienk · · Score: 0, Redundant

    What would happen if someone anonymously violated the NDA (say on slashdot)?

    1. Re:break the NDA? by gnuadam · · Score: 1

      Hilarity would ensue.

      --
      You say :wq, I say ZZ. Why can't we all just get along?
    2. Re:break the NDA? by ojplg · · Score: 1

      Considering the maximum number of people who will ever possibly sign this is one, they will have pretty compelling proof of who spilled the beans.

    3. Re:break the NDA? by lpp · · Score: 5, Insightful

      I would imagine that part of what they can do by putting into the NDA the option to withhold whatever evidence they wish is to reveal specific exclusive pieces to whomever signs up. Joe One gets lines 400-500 of foo.c while Jane Two gets lines 800-900 of bar.c and ne'er the twain shall meet.

      That way if 400-500 of foo.c is revealed anonymously as part of the conflicting code, SCO can go back and sue Joe One knowing he is the only one they showed that particular piece of code to.

      At least, if I were SCO, that's what I would do.

    4. Re:break the NDA? by geekoid · · Score: 2, Funny

      Since you would be the only one to sign it, even SCO could figure out who did it!

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    5. Re:break the NDA? by pyrrho · · Score: 2, Insightful

      I think it's just prohibit takers from appearing in court against them. If linus looks at evidence by NDA, he can't talk about it in public. It's to stiffle the opposition with a trojan horse, more than anything else.

      When you sign that NDA you give MORE RIGHTS to SCO... i.e. more ways to sue you.

      Remember, according to SCO, copyright is what you use against strangers, contracts you use against partners. Now go sign the contract! (i.e. the NDA)

      --

      -pyrrho

    6. Re:break the NDA? by Anonymous Coward · · Score: 0

      Bad idea

      SCO would then sue the organization running slashdot to get your IP address [I assume every message logged has an IP address associated with it] and logs to cross-check every message you've posted.

      With the IP address, they'll find your ISP. And then they'll find you (or be very close).

      Admittedly NAT/Proxy make this harder. (not so dialup/dhcp - they'll just subpoena those records from the ISP). That's why the cross-check to find out more will be useful, particularly if it points to an actual acct on slashdot for some messages.

  17. Red Flag by killmenow · · Score: 5, Insightful
    RECIPIENT acknowledges that it will receive access only to a portion of information relevant to these issues.
    One would think only a moron would sign an NDA that didn't guarantee access to ALL information relevant to these issues.

    I didn't even read beyond the first section because that quote says it all right there.
  18. Here's the lines in question, NDA be damned... by X86Daddy · · Score: 1, Troll
    1. Re:Here's the lines in question, NDA be damned... by QuMa · · Score: 1

      That's really convincing, especially considering the fact that Rusty has recently rewritten the module handling code.

  19. Simple Really by finkployd · · Score: 4, Insightful

    There is a constant flood of people who keep asking why SCO does not just show everyone the evidence if they really have a claim. I mean the code already exists for the public to look at in the linux kernel, so why not just point out which lines that are talking about?

    (for purposes of this discussion I am going to pretend SCO really has a legit claim and is not just doing this to get bought out)

    Here is why: They want to collect royalties. They cannot collect royalties if the code in question is removed and replaced with "clean" code, which is what will happen within minutes of them announcing exactly which lines of code are in violation.

    My guess is they would want all evidence to be secret, and never disclosed to the public else they lose their imagined "windfall" they plan to make via royalties on future sales of Linux distributions (or just extorting users of Linux directly).

    Can you just see it? "To keep our IP secret we cannot tell you what code is infringing on our property, buy we will let you keep doing it for a small fee. Don't worry, we will tell you if the code is ever removed or changed and stop charging you"

    Now before you scoff at this as the stupidest thing you have ever heard, think: Is this idea any sillier than everything else that has happened in this SCO fiasco so far?

    Finkployd

    1. Re:Simple Really by zonix · · Score: 1
      "To keep our IP secret we cannot tell you what code is infringing on our property, buy we will let you keep doing it for a small fee. Don't worry, we will tell you if the code is ever removed or changed and stop charging you"

      If I were to pay them (or anyone else for that matter) royalties, wouldn't I get to see what I'm paying for?

      z
      --
      What would an EWOULDBLOCK block, if an EWOULDBLOCK could block would? -- me
    2. Re:Simple Really by Anonymous Coward · · Score: 1, Informative

      But it's damn hard to collect damages when you didn't exercise due diligence to tell the infringing party that what they were doing that infringes.

    3. Re:Simple Really by dmaxwell · · Score: 4, Insightful

      Here is why: They want to collect royalties. They cannot collect royalties if the code in question is removed and replaced with "clean" code, which is what will happen within minutes of them announcing exactly which lines of code are in violation.

      Which the basis of another lawsuit itself. In effect, SCO would also get to charge royalties for the work the community did. Every other contributer to kernel (and whatever other software they want to extort money from) would probably have good reason to sue SCO. They would be committing a theft far larger than the one they allege was committed against them. If they don't step carefully, they're already staring the barrels of multiple countersuits for GPL violation. Attempted royalty collection would just throw more fuel on the fire.

    4. Re:Simple Really by waynemcdougall · · Score: 5, Funny
      Dear SCO

      Thank you for your letter requesting royalties. I must advise you that I have modified my copy of Linux and it now longer contains any of the code you allege is your property.

      I would be happy to show you my revised code so you can verify my claim, if you wouldn't mind filling out this NDA (attached). Oh, and don't forget to let me know which lines you want to see. I have my lines of source code sorted in alphabetical order for your ease of reference.

      --
      Recycle PCs and build a wireless community network www.hillsborough.org.nz
    5. Re:Simple Really by unborn · · Score: 1

      But wouldn't the person who pirated the code be aware of what he exactly pirated and proceed to clean it up anyways?

    6. Re:Simple Really by Darth+Yoshi · · Score: 1
      My guess is they would want all evidence to be secret, and never disclosed to the public else they lose their imagined "windfall" they plan to make via royalties on future sales of Linux distributions (or just extorting users of Linux directly).

      I was thinking about that. On the other hand, under section 7 of the GPL, everyone must cease distributing Linux immediately, kind of a GPL catch-22. I guess everyone would have to start using one of the BSDs or GNU/HURD.


      --
      // TODO: fix sig
    7. Re:Simple Really by slipstick · · Score: 1

      This has already been answered a thousand times, but whats a thousand and one amongst friends.

      SCO is obligated to disclose the supposed "infringing" code in order to reduce any possible harm. They can't simply say that they are being harmed and will be harmed in the future therefore everyone give us money. They must act to mitigate that harm.

      Secondly by not disclosing the supposed infringing code they could be viewed to be implicitly agreeing to it's disemination via the GPL license.

      --
      Sure information wants to be free, but how much are you willing to pay for the packaging?
    8. Re:Simple Really by mark-t · · Score: 1
      Right and right. On both points.

      Everyone who is familiar enough with the Linux kernel already knows *WHAT* sco's secrets are, they just don't know *WHICH* lines sco's secrets are at. SCO has no claims whatsoever to damages that are currently occurring due to their secrets being "out in the wild" because the only secret they actually have isn't one they have any trade secret rights to: *WHERE* in the kernel their code is. The code itself is already public knowledge, and any secret it may have contained is irrevocably lost.

    9. Re:Simple Really by glenstar · · Score: 1
      or GNU/HURD.

      Hahahahahahaha!

    10. Re:Simple Really by joebeone · · Score: 1

      good point... I betcha someone out there has copies of the UnixWare\SCO code... and the kernel source is available. Any geeks with time and the UnixWare\SCO source on their hands want to do a large-scale diff of the two codes and try to predict what sections of the linux kernel will be implicated... the areas of the kernel are somewhat limited as it is clear SCO is implicating "enterprise" features.

    11. Re:Simple Really by spitzak · · Score: 1

      By that logic I should be able to collect royalties from Stephen King for his newest book. He copied something I wrote. No I won't tell him or anybody what he copied, but he owes me!

    12. Re:Simple Really by iabervon · · Score: 1

      Anyone forced to pay royalties to SCO for using this code could sue SCO for damages (in the amount of the royalties, plus penalties, which tend to run 2x) for their current refusal to reveal the information necessary to avoid copyright infringement.

      Anyone wishing to distribute Linux would be forced to remove the code from their distribution, since nobody can offer the code under the GPL, as they would lack a suitable license to it. So all new installations would quickly be exempt. Distributors would probably be eligible for damages, as well, due to SCO's refusal to provide the information on their copyrighted work.

      SCO will essentially have to GPL the code in order to avoid being sued by everybody whose life they're making difficult; they want to postpone this occurrence until after the contract case with IBM is done, so as not to interfere with that. They also want to spread FUD as long as possible without getting sued; as soon as they reveal what their code is and who seems to be using it, the FUD ends and the legal fingerpointing starts.

    13. Re:Simple Really by budgenator · · Score: 1

      that's the fly in the ointment, if the dev came up with the same code independently, they would know what code was infringing.

      --
      Apocalypse Cancelled, Sorry, No Ticket Refunds
    14. Re:Simple Really by lspd · · Score: 1

      On the other hand, under section 7 of the GPL, everyone must cease distributing Linux immediately, kind of a GPL catch-22. I guess everyone would have to start using one of the BSDs or GNU/HURD.

      And I'm sure "killing the Linux kernel" comes in third place on SCO's Christmas wish list. If Linux died suddenly it would certainly put a kink in the plans of companies planning to migrate from Unix to Linux. The BSD's are good, and it's likely your favorite distro would convert to a BSD kernel (Debian has BSD and Hurd ports in the works for unrelated reasons), but how many business would be willing to live with the possiblity that BSD is exposed to the same risks.

    15. Re:Simple Really by karlm · · Score: 1
      You would be violating the GPL if you require an NDA as part of seeing your modified kernel code. OTOH, you could copy the source to a CDR or pay someone to engrave it on a bowling ball, tatoo it on a rabbid pitbull, or whatever... then shove it up McBride's ass and send SCO a bill for the media costs... provided they ordered the source code.

      Unless alphabetized is the form in which you manipulate the code, you would also need to provide regular source as well. However, if you wanted to put both forms on two pitbulls and shove them both up McBride's ass, I believe that would be allowed by the GPL.

      --
      Copyright Violation:"theft, piracy"::Anti-Trust Violation:"thermonuclear price terrorism"<-Overly dramatic language.
    16. Re:Simple Really by geekee · · Score: 1

      Your post is biased, although your motive is probably correct. If SCO is correct, they deserve compensation. That said, of course they'll milk it for all it's worth by making the time to fix the offending code as long as possible. Right now they don't even know if they'll get $1. Why would they make the situation worse by allowing Linux developers to fix the problem without fairly compensating SCO for the damage. If someone steals my ideas and people make money from it, I want more than just the cessation of the use of the ideas, I want a pice of the action for the money made. SCO wants the same.

      --
      Vote for Pedro
    17. Re:Simple Really by waynemcdougall · · Score: 1
      You are quite incorrect. This is a common misunderstanding of the GPL and it's important to get it right. The GPL (version 2) states For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have.

      But I am not distributing my SCO friendly version of Linux so this provision does not apply.

      Moreover, I can take any software under GPL, modify it to my own heart's desire, and I'm under no obligation to make the changed programme, or the source code, available to anyone.

      Nor does my having any GPL software, modified or not, require me to make the source available to anyone, unless I am distributing it.

      So I'm quite entitled to offer SCO my alphabetised listing so they can check if their proprietary for (i=1;i>=n;i++) is present or not.

      We apologise for this GPL community service announcement and return you to your regularly scheduled /.

      --
      Recycle PCs and build a wireless community network www.hillsborough.org.nz
    18. Re:Simple Really by Anonymous Coward · · Score: 0

      My guess is they don't intend to ever get to court so don't plan on being forced to hand over any source in public.

      Giving it out now would be extremely stupid if that's the case.

    19. Re:Simple Really by karlm · · Score: 1

      Hmm... I was going under the assumption that distributing the alphabetized source counts as distribution of a derrivative of the GPLed work.

      --
      Copyright Violation:"theft, piracy"::Anti-Trust Violation:"thermonuclear price terrorism"<-Overly dramatic language.
    20. Re:Simple Really by waynemcdougall · · Score: 1

      Nope, coz see I'm not distributing the program. Making alphabetised source (well ideally SCO can just tell me what lines they are interested in and I can just send them an extract :-) ) available in response to a legal challenge would not count as distributing the program because a) it's not the program, and b) it's not a distribution of the program.

      --
      Recycle PCs and build a wireless community network www.hillsborough.org.nz
  20. The final line by egoff · · Score: 4, Funny

    This NDA will self-destruct in ten seconds.

  21. If you're reading this Mr. Ashcroft... by TrekCycling · · Score: 0, Offtopic

    Please don't take the fact that I'm on the same message board as this guy to mean that I'm "against us". I know with the Patriot act it's pretty easy to get labeled a terrorist, so I just want to cover my butt before the feds come busting down my door.

    Thank you. God Bless America.

    1. Re:If you're reading this Mr. Ashcroft... by Anonymous Coward · · Score: 0
      Oh, grow up, you silly, self-aggrandizing nitwit.

      Wah, wah, wah, Ashcroft, wah, Patriot Act, wah, wah, look at me!

    2. Re:If you're reading this Mr. Ashcroft... by TrekCycling · · Score: 1

      Who's the silly, self-aggrandizing nitwit? I was making a joke.

    3. Re:If you're reading this Mr. Ashcroft... by Anonymous Coward · · Score: 0

      I think he was talking to himself.

  22. They must really think everyone else is stupid. by Fly · · Score: 1

    First they claim that open source developers could not possibly be smart enough to make Linux as good as it is, and then they expect people to accept their obscene NDA.

    --
    end of line
  23. YOU SO FUNNY!!! LOLOLOL!!! by Anonymous Coward · · Score: 0

    Never seen those jokes before.

    Sit down and shut up.

  24. And yet another bonus by Sean80 · · Score: 1
    So the best people who can sign the NDA are precisely the people who won't be able to understand what they see?

    Sure, I can program in C, but without an intimate knowledge of the Linux kernel, who the hell knows what goes on in there?

    I once proved that God was a seven-headed Hydra by reading too much into a Shakespeare play I once read at school, so I'm wary of leaping to conclusions like this, but surely somebody at SCO must've realised that this would happen.

  25. Cringely by LMCBoy · · Score: 5, Interesting

    Bob has some interesting thoughts this week. The column is about how, IF there is UnixWare or OpenUnix code in Linux, it was most likely Caldera itself that put it there, not IBM. This isn't a new idea, but he provides quotes from Ransom Love at the time which sound pretty damning.

    SCO/Caldera's motto at the time was "Unifying Unix with Linux for Business". To the extent that wasn't just hype, how can they blame anyone but themselves for migrating their UNIX code into Linux?

    --
    Liberal (adj.): Free from bigotry; open to progress; tolerant of others.
    1. Re:Cringely by Anonymous Coward · · Score: 0

      Bob Cringely is a loudmouth reactionary buffoon. He's more in the dark about this than the 15 year old slashbots doing all the ranting and raving.

    2. Re:Cringely by Anonymous Coward · · Score: 0

      but he provides quotes from Ransom Love at the time which sound pretty damning.

      Ransom Love? Is that his real name?

    3. Re:Cringely by Anonymous Coward · · Score: 0

      Reactionary? You're saying that he's an extreme conservative that wants to undo liberal progress? Are you sure that's the word you meant to use?

    4. Re:Cringely by swb · · Score: 1

      With a name like that he should be a rock star or a porn star, not a suit with a fucked up career.

  26. Re:Someone in California end this... by JohnnyCannuk · · Score: 1

    How the hell did Eric Rudolph get access to a computer?

    --
    Never by hatred has hatred been appeased, only by kindness - the Buddha
  27. There really is no way to do this right by X · · Score: 3, Interesting

    The whole NDA thing is a pretty rediculous farce. The fundamental principle is that SCO does not want it revealed what code in Linux is in question. Since that code is already public knowledge, if they let you publish information "obtained from other sources" you can basically publish the relevant code.

    SCO also doesn't want to have to turn over everything they got. They basically want to just throw down their Unix trade secrets and Linux source code, and have people draw their own conclusions. A contract with more flexibility could open them up to having to share a lot of other things related to the case.

    As for the state of Utah clause, it's pretty typical for a contract to have some state governing its enforcement, and typically the home state of the company drafting the contract. Sadly, they aren't a Delaware corp. :-(

    I think SCO is as evil as the next guy, and I think the NDA thing is a red herring, but I have to say I can't see how else they could have written this NDA without compromising secrets that they obviously feel they need to protect.

    --
    sigs are a waste of space
    1. Re:There really is no way to do this right by codefool · · Score: 2, Funny
      if they let you publish information "obtained from other sources" you can basically publish the relevant code.

      Good point - but what I don't understand is why they don't put a limit on the Linux side of things? Such as - keep this secret until a judge says this is over, owtte.

      I think SCO is as evil as the next guy

      So, how evil is the next guy ;-)

      --
      "Stop whining!" - Arnold, as Mr. Kimble
    2. Re:There really is no way to do this right by NecroPuppy · · Score: 2, Interesting

      The fundamental principle is that SCO does not want it revealed what code in Linux is in question. Since that code is already public knowledge, if they let you publish information "obtained from other sources" you can basically publish the relevant code.

      So what would stop someone who saw the "infringing" code from publishing the rest of the kernal, etc, except for what they saw?

      Since they haven't published anything that they were shown by SCO, they aren't in violation of the NDA.

      It would then be a simple job to determine which portions were missing, and then call SCO's bluff.

      Or does that make too much sense?

      --
      I like you, Stuart. You're not like everyone else, here, at Slashdot.
    3. Re:There really is no way to do this right by X · · Score: 1

      Good point - but what I don't understand is why they don't put a limit on the Linux side of things? Such as - keep this secret until a judge says this is over, owtte.

      Because once you publish this, the claim that they have any "trade secrets" basically goes away. Imagine if the court ruled in SCO's favor, and they you published away (and legally too). The "trade secret" status would be lost.

      This is the pain with trade secret cases. In order to prove your case, you have to present the secrets, but once you do it, they are no longer secrets, making the court case pointless. The notion of sharing these secrets with anyone prior to trial is pretty rediculous. At least in the courtroom there are restrictions which prevent the secrets from being shared except as directed by the judgement. Outside of that it's far more complicated. :-(

      --
      sigs are a waste of space
    4. Re:There really is no way to do this right by mbonar · · Score: 1

      The only people who would sign the NDA would be IBM legal staff so they can see if there is a good reason to settle out of court. It's probably already been done. The question in my mind is if IBM does settle out of court, is that the end of this issue? I have a right to life without advertising.

      --
      ... There's no such thing as time; we invented it.
  28. What happend to their original lawyer? by arf_barf · · Score: 1

    I read on CNET that they have a new councel from the Canopy group. What happend to the David Boise looser?

    1. Re:What happend to their original lawyer? by mec · · Score: 2, Informative

      CNET updated the story. SCO has a new in-house lawyer, but they are keeping the current lawyer, Boies, as well.

      The new lawyer, Ryan Tibbitts, worked on the Caldera versus Microsoft suit. He's done this kind of work before.

  29. Re:Come someone... by stevesliva · · Score: 1

    IANAL = I am not a lawyer. Fragging = Killing someone with a fragmentation grenade, usually. Vietnam connotations. Try google next time.

    --
    Who do you get to be an expert to tell you something's not obvious? The least insightful person you can find? -J Roberts
  30. Re:Come someone... by Sean80 · · Score: 1

    I believe it's I am not a lawyer.

  31. M$ care about other peoples copyright by Sigurd_Fafnersbane · · Score: 0, Offtopic

    At BBC, theregister etc there is a story about Sendo suing Orange over patent infringement on the Orange SPV Smartphony. The link is at Sendo vs Orange

    It seems M$ should have bought a licence to Sendos patents before giving it away to HTC and others.

  32. SCO by Anonymous Coward · · Score: 1, Insightful

    Since the lawsuit is directed at IBM, why doesn't IBM just do a diff AIXSOURCE LINUXSOURCE and publish it? It seems to me that is all anyone has to do to bury this once and for all.

    1. Re:SCO by Smallpond · · Score: 1


      er..
      because SCO isn't claiming they took code and put it in AIX. They claim that the joint work they did on Monterey (proposed Unix for Intel-based) leaked over into Linux.

      You might as well ask them to diff z/OS. Maybe they stole code for their mainframes.

  33. Shit Man! by Greyfox · · Score: 1
    If we wanted to steal something from SCO, it should have been that good ol' text-mode version of the Steve Jackson game "Ogre" (I think that was the name of the game) that shipped with Xenix back in the day. Nothing else of theirs was particularly worth stealing.

    "Ski" from DG/UX was a pretty cute game, too...

    --

    I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

  34. Re:Come someone... by gregm · · Score: 1

    Usually IANAL means I Am Not A Lawyer however it must be taken in the context of the discussion. If you're discussing mowing lawns it might mean I am not a lawnmower. Various perversions of the original crop up all the time.

    Fragging refers to killing one's opponent in the first person shooter doom. It might have come out before that or might be an old military term but Doom was where I was exposed to that term.

    G

  35. Counter suits by Tim+Macinta · · Score: 5, Interesting
    I downloaded the Linux source from SCO just yesterday at ftp://ftp.sco.com/pub/updates/OpenLinux/3.1.1/Serv er/CSSA-2003-020.0/SRPMS (their server did not respond a minute ago when I checked to see if it was still there). Wouldn't the fact that they are strongly implying that it is not OK for others to distribute Linux in it current form make their distribution illegal since they lose their right to distribute it when attempting to add conditions to the GPL?

    Could somebody who has contributed to the Linux kernel explicitly revoke SCO's license to redistribute it and then counter-sue to get them to stop? It would seem that SCO has lost their right to distribute the kernel by attempting to add restrictions on top of the GPL (which the GPL forbids) and that as a result somebody who owns part of the kernel could enforce a revokation of their ability to use the GPL'ed code. Wouldn't it be great if all the kernel contributors did this at once? SCO would quickly be drowning in countersuits. (Maybe we could even see the headline In Soviet Russia, Linus sues SCO!)

    Of course, I'm not a lawyer, so I don't know how realistic of an approach this would be.

    1. Re:Counter suits by raffe · · Score: 1

      Maybe the code is in redhat and suse and NOT in OpenLinux? Maybe they didnt put it thiere own distro. Maybe Ibm helped suse and redhat.
      Who knows? Cant we get an ask slashdot with a good lawyer in this case?

    2. Re:Counter suits by njchick · · Score: 2, Interesting
      It is possible that the infridging code was added after version 2.4.13. Maybe it's only in the Alan's branch or only in the 2.5.x series. Think XFS or extended attributes or some ia64 code or something like this.

      As for revoking the license, it would merely deny the right of SCO to distribute Linux kernel, including security fixes. I don't think it's a good idea. Since GPL doesn't govern the use of the software and neither does the copyright law, SCO still would be allowed to use Linux internally.

    3. Re:Counter suits by ErikTheRed · · Score: 1

      Thanks! I'm downloading the code from there right now... Even if it's of no legal use, it's still fun to fuck with SCO's bandwidth (I probably need to download about 50 backup copies too, just in case)! How about we all hit their homepage a few times an hour for the next few weeks? If not us, perhaps our perl scripts?

      --

      Help save the critically endangered Blue Iguana
    4. Re:Counter suits by Tim+Macinta · · Score: 1
      As for revoking the license, it would merely deny the right of SCO to distribute Linux kernel, including security fixes. I don't think it's a good idea.
      That's not the point. The point is to force their hand now. Those 1,300 (or was it 1,500?) threatening letters that they sent to Linux companies could very much be construed as SCO saying that those companies may not redistribute Linux, even though the letters may not have said exactly that. If somebody sues them for attempting to add restrictions to the GPL they will either be forced to say that redistribution of at least the source that SCO itself is distributing is OK or they will need to screw over their current customers by ceasing to issue security fixes, as you pointed out. In my opinion, the sooner somebody counter-sues them to force their hand the better because their is way too much FUD flying around.
    5. Re:Counter suits by HiThere · · Score: 1

      What I want to know is "how is it legal for them to stop distributing the source?". Did they distribute the source already to everyone who bought a distribution from them? If they didn't, then stopping the distribution of the source is, itself, a violation of the GPL. (They can stop after, I seem to remember, seven years.)

      Of course, they don't have to let you download it. They can insist that you purchase it on CDs, for a reasonable handling fee. But they are generally forbidden from stopping the distribution unless they always gave away the source with the binaries.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    6. Re:Counter suits by Anonymous Coward · · Score: 0

      Maybe the code is in redhat and suse and NOT in OpenLinux?

      Ah! So a simple diff between the two would reveal which code they are aiming at!

  36. Imagine the SCO Employee NDA by BrynM · · Score: 4, Funny

    4. COMPLAINING. Employee shall not, upon leaving the office, complain, celebrate, share or disclose any details of any day at work or the disposition (good or bad day) of any day. Further SCO reserves the right to alter the empoyee's view of any working day based on whether SCO believes it to be a good or bad day at work.

    --
    US Democracy:The best person for the job (among These pre-selected choices...)
  37. Re:Come someone... by AlecC · · Score: 1, Offtopic

    What is IANAL?

    I Am Not A Lawyer.

    If you take advice marked thus and get into legal trouble, you are entirely on your own. Mind you, anybody who takes legal advice from the Web/Usenet is a workd class fool anyway.

    Also, what is fragging?

    Literally, killing with a fragmentation grenade - a means occasionally used to get rid of disliked officers.NCOs in the Vietnam war.

    Figuratively - destroying with great force.

    --
    Consciousness is an illusion caused by an excess of self consciousness.
  38. How about a new Letterman segment? by SilentReproach · · Score: 1

    You guessed it - Stupid SCO tricks!

    --
    Religion is the opium of the people. Evolution is the opium of scientists.
  39. Re:Come someone... by Kyoya · · Score: 1

    You can find most internet/tech related jargon on one of the various Jargon File Nodes floating about the net.

    http://info.astrian.net/jargon/ for the to lazy to google. :)

    --
    To strive, to seek, but not to yield
  40. Questions for SCO by mec · · Score: 1

    Disclosure: I have a short position in SCOX.

    Permission granted to anybody to use this text for any purpose. I would particularly like it if journalists asked these questions of SCO executives.

    Questions for SCO
    2003-06-05

    ===

    Did SCO sign a contract with IBM for Project Monterey?
    (if yes) Will you file that contract as an exhibit in your suit against IBM?
    (if no) Why did you undertake a large joint development project with IBM with no contract?

    ===

    Your UNIX contract rights depend on a contract with Novell.
    Are you going to file your contract with Novell as an exhibit in your suit against IBM?
    Are you going to make your contract with Novell available to the press?

    ===

    Who has signed your NDA and received copies of confidential materials?
    If the identities of all the NDA recipients are confidential, can you tell us how many there are?

    ===

    Have you provided legal notice to any person or organization which distributes Linux software of any specific source code lines that you claim infringe on your intellectual property?

  41. Definition of Confidential Information by I_redwolf · · Score: 1

    "Confidential Information" means any and all data;snip. They don't clarify that so that is all that I really need to see, if you sign the NDA you might as well never even say the word kernel, or for that matter you might as well never talk about anything relating to programming or computers. Anything you say afterwards could be used against you in a very malicious nature by SCO.

  42. "I Am Not A Lawyer" by treebeard77 · · Score: 1
    1. Re:"I Am Not A Lawyer" by Znonymous+Coward · · Score: 1

      Thanks!

      --

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

  43. What if? by mslinux · · Score: 1

    What if this is a big plan on the part of Big Blue? What if they are paying SCO to bring this legal challenge so that questions about IP in Linux can be addressed in court? IBM gets a free and clear Linux to push against MS Windows, Sun Solaris, Apple OS X, etc. And SCO gets money or is bought out... everyone gets what they want.

    Or, maybe this is an attempt by IBM to take over Linux; be the only 'authorized' Linux distributer. Anyone else see the possibilities here????

    1. Re:What if? by JDBrechtel · · Score: 2, Funny

      Yea....it's possible that you're clinically insane.

  44. Probably Daryl Maniuplating his penny stock by Anonymous Coward · · Score: 0

    He's probably creating a buzz by buying a little bit which makes it appear as if there's a demand and driving prices up, meanwhile, selling twice as much as he bought.

    A sucker is born every minute.

  45. NDA means nothing. by Lumpy · · Score: 2, Insightful

    as soon as it get's into a court they cant play these stupid games.

    The ENTIRE sourcecode will have to be revealed in court. or they need to just give up.

    I know that judges are corruptable, but they aren't idiots.

    --
    Do not look at laser with remaining good eye.
    1. Re:NDA means nothing. by Anonymous Coward · · Score: 0

      The source code may be revealed in court under a protective order. There's no requirement it ever see the public light of day.

  46. Not so simple. Really. by EdgeShadow · · Score: 4, Interesting

    Here is why: They want to collect royalties. They cannot collect royalties if the code in question is removed and replaced with "clean" code, which is what will happen within minutes of them announcing exactly which lines of code are in violation.

    All right. Let's say SCO does have a legit claim and does want to collect royalties. Even so, at one point or another, they'll have to reveal the "code in question" to, at the very least, the parties involved in the lawsuit, if not to the general public as well. If they never reveal said code, then how the hell can they prove that it was copied? That would be akin to accusing someone of stealing without even specifying that which was stolen.

    Now, even when they do reveal said code, they are claiming that damges have already taken place. So, even replacing the code with "clean" code will not suffice to pay for past damages, though it would prevent future infractions. If SCO wins, the judge would likely rule that either the code be removed or end users of Linux pay royalties to SCO. Again, this is only a speculation; I am certain, however, that SCO will be unable to force Linux users to keep their "illegal" version of Linux so that they would have to pay royalties.

    In any case, I and many others feel that SCO's claims are bogus and that they've no chance in court. Even if the code is, in fact, copied, it still remains unclear whether or not SCO really has the rights to it and, even if they do, whether or not average Linux users are in violation.

    1. Re:Not so simple. Really. by Anonymous Coward · · Score: 1, Interesting

      This is not a copyright case - yet -. The judge in this case will rule onto IBM, and only IBM. The outcome of this particular case may well hold ZERO meaning for the rest of us.

      You cannot collect royalties from a Trade Secret unless the counter party agrees to do so. IBM and SCO were in a deal together. Maybe SCO's Unixware "kickass" IP stack is really BSD -- and THAT alone could be the secret. As other's have said about the NDA, IBM may still be forbidden from discussing the BSD connection, or helping Linux to also make that connection.

      If IBM were to put BSD's IP stack into Linux, it could be found at fault, and have to pay. But, only IBM would have to pay. The "secret" would stand as lost and Linux would move along like nothing happened.

      Now, SCO might be playing a cute legal gymnastics game. First, they seek state damages for what is also a copyright infringement as a "Trade Secret". Then they collect from IBM the $Billion they claimed they would have made from the market. ONLY THEN, will they move on to Federal court with proof of infringment in hand, against Linux at large. (with the material fact of infringement developed in evidence under secrecy and court sealed as a Trade Secret).

      Now the copyright case v. Linux may find itself lost in a summary judgement (very, very, quickly). The offending code will be published only then, leaving Linux with precious little time to release a "clean and tested" post-infringement version or for people to migrate to that new version. SCO sends out a letter to the Fortune 5000 saying they want $xx for continued use of all infringing versions of Linux.

      SCO could, for a short while, double dip. They claim IBM lost them the market and they should be paid damages, but copyright law will give that market back to them. Generally, "double dipping" is frowned upon but I have a feeling this might work. Utah has no copyright jurisdiction and could not defer to those, nor would the more absolute rights of copyright disipate in the state action.

      In light of the BSD rulings, it is most unlikely that SCO could toss Linux out of the market.

    2. Re:Not so simple. Really. by AlphaSys · · Score: 1

      Dude:

      Why would you post this AC? That is the most insightful, informative comment I've heard anybody come up with regarding this whole mess. As much as I don't like to hear it, it sure does make alot of sense that that could be the strategy (and even the specifics) in this mess.

      Caldera would've had every right to use BSD-licensed components (and the IP stack would be a good choice!) in their proprietary implementations, and could easily have set it up to where it was stipulated that this not be divulged outside of an NDA. That could constitute a "trade secret" of sorts. And even though the BSD code is available for review by anyone who agrees to the license, if anyone "hinted" that that particular code be examined very carefully for ideas, then there could not only be a valid argument, but it may even be something we could see IBM doing. And who would blame them (except SCO who was already using the secret ingredient themselves and didn't want the cat out of the bag)?

      However, if this is the case, once the genie is out of the bottle, you surely can't very well put it back in, and the OSS developers also couldn't possibly be held accountable for reviewing code published under that educational-type license and having learned from it. In such a case, sole remedy would be due of the one entwined in the NDA and the OSS community at large would feel no sting and, I dare say, wouldn't have to change any code either since the source of the information would have been legit even if the source of inspiration was less than. But Calde^H^H^H^H^HSCO probably would like to spread the FUD as wide as it can while it can.

      If this scenario turns out to be true (that SCO 'borrowed' pieces of BSD-licensed methodologies and then called the unique implementations of them trade secrets), it would be very interesting to see WHEN these adoptions were selected and committed to SCO's own tree. If the history were recent enough, IBM may be able to not only point out that the information was freely available, but that SCO baited them into it (as a way to thwart their growing relationship with OSS and a way to backdoor Linux from at least a PR standpoint) -- doing something that was blatantly and obviously unoriginal at its roots (but in a way that was cleverly protected by the NDA), waving it under the nose of Big Blue and then seeing how long it took to find its way into the CVS commits. It makes me think of the Beastie Boys.

      I can't stand it... I know ya planned it

      Either way, any Judge that could be convinced that this is the way it went down would probably also feel like SCO deserves what they got. You just don't dare the big guy on the block to take your lunch money... what're you gonna do about it?

      IANAL, but what you said made sense to me

      --
      Can I bum a sig? I left mine at the office.
    3. Re:Not so simple. Really. by Anonymous Coward · · Score: 0
      Hey, stupid. Some people post AC and have a lot to say. What is being said is more pure than when some karma whore such as yourself likes to brand himself to what he consideres insightful.

      And coming from you - this being the most insightful thing you've ever seen here - isn't even a compliment.

      Now, you will learn something, a valuable lesson, newbie. The mobocracy rarely mods up AC posts. The Slashbots arent concerned with content, its conformance. Reading this place at anything higher than -1 is like putting a shit filter on your ass.

      Oh yeah, you know you are a poser when you use ^H 5 times to erase a single word in insert mode when a single ^W would have worked just fine to erase "Calde" What a loser. What a loser.
    4. Re:Not so simple. Really. by AlphaSys · · Score: 1

      To be accurate, I said it was the most insightful comment I've seen on this topic.

      --
      Can I bum a sig? I left mine at the office.
    5. Re:Not so simple. Really. by Anonymous Coward · · Score: 0

      oh big boy, show /. who is the man. Editorialize yourself and make sure you seem to be the righteous one. You show them big boy.

      You have a size complex. You are an intellectual fucking retard, with delusions. You are a little pussy that gets his ass whipped in RL. And you come here to be somone. HAHJAHAHAHAHHA. Hehhee.

      Im snickering. This is classic, vlassic.

  47. judge in pocket by josepha48 · · Score: 1
    They must have a Judge in their pocket to get this to go anywhere. That is the ONLY reason for keeping it in the state of Utah. Any 'financial' reason is secondary.

    I woulnd't sign this with SCO's president's hand holding the pen, and the VP moving it!

    --

    Only 'flamers' flame!
    Does slashdot hate my posts?

  48. The Worst Part... by blenderfish · · Score: 2, Interesting

    From the article: "They could sue me and make me go to Utah to prove I didn't disclose confidential information" Speaking as someone unfortunate enough to live in Utah... *shudder* Well, at least if a case did make it to Utah, the local theocracy probably wouldn't take a "controlling" interest in the affair, and you might get a fair trial. (Hey, it's not all bad-- one advantage of living in Utah is that I at least theoretically have access to the same supply of sweet, sweet crack that the guys at SCO are apparently smoking.) - Blenderfish

  49. Why Can't by Anonymous Coward · · Score: 0

    Why can't IBM, RedHat and the other big dog Linux companies have their people compare all the past and present Linux code against SCO's code which was available freely until recent retraction.
    plus i am sure, you can stumble upon the System V code on the net. Who knows it might be code stolen from Berkely by Att. Some intelligent perl scripts running on a Beowulf cluster :) might do the job. It will be cheaper than legal fees.

  50. SCOX stock rating "report card" by dcavanaugh · · Score: 4, Informative

    Stock Financial Health Grade change
    The Morningstar Financial Health Stock Grade has changed from B- to F. For details,
    click here

    Stock Profitability Grade change
    The Morningstar Profitability Stock Grade has changed from Not Available to F. For details,
    click here

    Stock Growth Grade change
    The Morningstar Growth Stock Grade has changed from A to A+. For details,
    click here

    I suspect this won't be a "growth stock" for very long.

    1. Re:SCOX stock rating "report card" by janda · · Score: 1
      The Morningstar Growth Stock Grade has changed from A to A+.

      Growth stocks are speculative. If SCO does manage to win this, what do you think will happen to their stock? I suspect that as more things come out (e.g. commentary on the NDA), this will change.

      --
      Karma: Food Fight (Mostly affected by Date Plate).
    2. Re:SCOX stock rating "report card" by kalidasa · · Score: 1

      Seems to me that anyone grading it as an A+ growth stock (which I assume - IANASB - means that the reward/risk ratio is very good) is gambling on IBM getting sick of this and making it go away by throwing money/IBM stock at the SCO stockholders.

  51. Wow! by Arker · · Score: 1

    Since the lawsuit is directed at IBM, why doesn't IBM just do a diff AIXSOURCE LINUXSOURCE and publish it? It seems to me that is all anyone has to do to bury this once and for all.

    That's a really freakin good idea. It would be a little more complicated than that, of course, but but not all that difficult really. Surely they've already done that internally... well I hope they have. It seems like the most obvious thing in the world now, but I'll admit I hadn't thought of it until I read the post I'm quoting.

    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
    1. Re:Wow! by cowmix · · Score: 1

      AIX is not based on SYS V code so the diff would not really work out very well. They would have diff Linux against whatever the last batch of code they received from SCO before the 'party' was over between them.

  52. Re:Come someone... by n0ano · · Score: 1

    No, the term fragging was used long before Doom. I was always told that the term appeared during the Viet Nam war when GI's used to remove officers they disliked by tossing a fragmentation device (aka grenade) to the officer. Note that there was an instance of this during the recent war in Iraq.

    --
    Don Dugger
    "Censeo Toto nos in Kansa esse decisse." - D. Gale
  53. Re:I Am Concerned by stratjakt · · Score: 1

    Because they love typing ANAL in uppercase. It is creepy.

    --
    I don't need no instructions to know how to rock!!!!
  54. What could the counterparty to SCO possibly gain? by Anonymous Coward · · Score: 2, Interesting

    I agree.

    Why in the world would ANYONE agree to something like this?

    To gain some bizzar form of personal satisfaction?

    Maybe to "take one" out of some sick sense of undying love for SCO?

    It sure isn't like you can, even remotely, help get Linux "cleaned up". Indeed, if Linux were to happen to "fix" anything, even by an accidental change, SCO would like come after the NDA signitories like rabbid utonian dogs.

    Anyone playing along with this whole NDA charade, in the smallest way, is simply paying homage to some scheme or other of SCO's. For NOTHING of value in return.

    Why do this? SCO is a scoundrel. Don't gift any value or meaning to their cause.

    BEST CASE REASON --- You agree with SCO and just want to check before you try and negotiate a license fee for your copies of Linux.

    But why? Your risk doesn't even start until SCO demonstrates a case. Even then, you don't have to pay -- you have to take affirmative steps to correct the problem. Why volunteer fees, in advance of SCO even having a licenseing program available?

    BEST BUSINESS REASON -- You work for Microsoft and your bonus next year is based on your offering your services under the NDA "to protect the God, Flag, and Motherhood of IP in general".

    Stupid is what stupid does. That's probably the biggest risk in Free Software. Any fool can step up "on behalf of "the community"" and make claims like SCO's look good.

    SCO wants to show the court that XXXX people believed enough in SCOs claims to investigate them at considerable risk to themselves. This is about a Trade Secret, after all, and if what SCO has is that awe inspiring then there must be something to it.

  55. Utah by Arker · · Score: 1

    Quick quiz: Who was it that said "If they kill me, promise me you'll carry my body over the border to Wyoming, cause I wouldn't want to be caught dead in Utah"?

    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
    1. Re:Utah by blenderfish · · Score: 3, Informative

      Easy.

      Joe Hill.

      Any Utah-hater worth his salt'd know that one!

      (Actually, for the record, I don't completely hate Utah. It just can be frustrating at times. Whoever has that .sig about "democracy dies behind closed doors" has it right. So very right.)

      - Blenderfish

  56. Insider Trading? by Anonymous Coward · · Score: 0

    Is it just me or does the large amount of shares the directors of SCO received (~30,000 at $0.001/ea per director) in late February of this year look like insider trading? I mean, they had to know at this time where their future lay.

  57. Re:Come someone... by ninewands · · Score: 1
    Quoth the poster:
    Fragging refers to killing one's opponent in the first person shooter doom. It might have come out before that or might be an old military term but Doom was where I was exposed to that term.

    Fragging came from the method whereby disaffected troops in Viet Nam rid themselves of officers with whom they had a MAJOR problem. You just rolled a FRAGmentation grenade into his hooch in the middle of the night.

    Those of us who wore green suits and little metal bars during that era don't care too much for the term.
  58. SCO wants a sock puppet, not an expert. by Tsu+Dho+Nimh · · Score: 1
    "1. (snip)RECIPIENT acknowledges that it will receive access only to a portion of information relevant to these issues.
    7. No Obligation to Disclose. SCO has no obligation under this Agreement to disclose to RECIPIENT any Confidential Information which SCO elects to withhold."

    No way! They want a sock puppet, not an honest analysis of the problems.

  59. ...the scope of the complaint... by burgburgburg · · Score: 1

    The scope of the complaint is exactly equal to whatever length they feel the need to go to extract the amount of money they feel they can get from Microsoft/IBM/anyone else. And since Microsoft is inclined to fund a long-term effort, tying the scope down would limit the payoff.

  60. Its like a train wreck. by Captain+Rotundo · · Score: 1

    I tell you I do no kernel coding, and I am familiar with C. This is a severely restrictive agreement, but doesn't it just make you wonder what the hell they have? Is this all a big bluff, or is there something that actually is damning? I can think of compelling reasons why SCO would be so restrictively secretive in both cases. Of course, IANAL, but it seems I would be tempted to sign just to see what the heck its all about, the same way we are tempted to look at an accident on the road, sure we are giving up attention to driving, and may possibly see something we actually don't want to, but we just can't resist.

    I can see why everyone is saying not to sign it, it is terrible, but don't you just wish we could find someone to bite the bullet?

    Am I the only one not convinced that SCO is entirelly bluffing and once the time comes for the flop they will have to fold?

    1. Re:Its like a train wreck. by Darkninja666 · · Score: 1

      Hell, I'd be surprised if they make it to the flop. I have a feeling that it will be settled out of court, with either a bootheel or money.

      --
      Secure multi-mediation is the future of all webbing...
  61. Re:Come someone... by Anonymous Coward · · Score: 0

    IANAP but I did some hacking on C64 basic before..

  62. warning the SCO!!! by Anonymous Coward · · Score: 0

    SCO very powerfull. the SCO first to courts the IBM. it is bringing much unknown and the sneaky.

    even now i know US goverment will attacks the IBM at the bringing behest of the SCO. the equity of the inspected is to devalue in the very soon will be not good. not good!! the IBM will suddenly and fall fast!!

    the SCO is now even now there with you and is very very bastard!!

  63. No by Chakde+Phate! · · Score: 1

    Seeing part of the picture is better than none of the picture.

    How do we know that SCO hasn't grabbed the code they show us straight from the Linux kernel source tree, circa 1995?

    The only way they can prove their case is to demonstrate that a source tree including the offending files compiles to a binary identical to one from a date before those features were added to Linux.

    Of course, that doesn't even begin to address the fact that different programmers often solve the same issues in very similar ways...but then, we know they never had a case to begin with anyway.

    1. Re:No by budgenator · · Score: 1

      This potentialy includes all of the shell scripts included in both unix and linux, the file layouts, maybe they are saying the a fs that's
      / /lib /usr /usr/home /etc /var

      is part of the copyright/trade Secret/whatever

      --
      Apocalypse Cancelled, Sorry, No Ticket Refunds
  64. Re:I made a copy of the NDA by Anonymous Coward · · Score: 0

    You should create an NDA saying you won't say anything
    at all in public and sign it to whoever's in charge
    of SCO. That would show them.

  65. demoralized by HBI · · Score: 1

    Anyone else getting demoralized about this whole thing?

    I know in my heart it will be litigated out successfully.
    I know I wasn't the original author of this OS.
    I know my job means that I have to use Win32 mostly for business purposes.

    Still, this is eating me up, the whole SCO thing. The few Linux boxes I have are like a hope of throwing off the Microsoft yoke at work, and these bozos are threatening to take that all away.

    --
    HBI's Law: Frequency of calling others Nazis is directly correlated with the likelihood of the accuser being Communist.
    1. Re:demoralized by realdpk · · Score: 1

      What's eating me up is that /. et al are so hell bent on propogating this, so far as anyone can tell, unfounded claim. Once or twice a day, they put an article up on the main site to help spread SCO's FUD. Who knows why? It's not like there's any new information day by day.

      I vote (heh, I know, doesn't matter) that /. stop giving SCO the attention it so desperately wants until the code in question is revealed.

    2. Re:demoralized by Phinn · · Score: 2, Interesting

      I agree. It is demoralizing. But Slashdot is a demoralizing site. Just about all we read here is how the MPAA, RIAA, Microsoftâ(TM)s, SCO want to take things away from us. Think about it, Slashdot is not exactly uplifting, empowering stuff is it? At best it's alarmist and reactionary and sometimes entertaining, like the posts on a poll. But I digress...

      The thing is it's not about money anymore for these companies; it's about power - those who have it and those who want it. SCO is a wanna-be, Linux (yes Linux) is a wanna-be, Microsoft is (perhaps) doing all it can to hold on to it. You know what though? I don't fucking care. I don't care about Openoffice vs. Office, Linux vs. Windows, stability, or if I have to have a license to play some damn music file. I really only care about security, meaning I care if my information gets into the wrong person's hands. As long as I'm not the victim of a theft or assault I'll do what I need to do to get by in this world. And that's what most people do (read Joe Six-pack).

      I just don't understand the instance that Linux should or must become the next Microsoft. That's really what this is all about, SCO is just getting in the way of that goal and it's pissing people off. So ask yourself "would the world really be that much better if it was Linux that was on 95% of the desktops?" It might be more *fun* for you, but it doesn't really matter. All you'll have is the power that Microsoft has now and will be faced with the same basic problems.

      At the end of my life I won't be thinking "Damn, I wish I had fought harder to be able to use linux at work..." and I don't think you or anyone else here will be either.

  66. If... by happyhangone · · Score: 1

    Now we got an idea of what a pact with satan looks like... breed this NDA with MS EULA...

    1. Re:If... by geekoid · · Score: 3, Funny

      no. A pact with Satan wold be subtle. this is a pact with stupid.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    2. Re:If... by Squidgee · · Score: 1
      Dammit and my mod points just went away...

      Seriously though, this is the WORST NDA I've ever seen.

  67. Re:I Am Concerned by Cro+Magnon · · Score: 1

    1. Because they want to make it clear that I Am Not A Lawyer.

    2. They might be admitting that I-ANAL!

    --
    Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
  68. Possible outcomes by Ashtead · · Score: 2
    What's the deal here?

    To the extent this isn't moot, insofar as whoever signs this NDA and sees the disputed source code, cannot say anything about what he has seen. Then, what is up with this partial source? Why isn't SCO wanting to show all of it?

    Let us now assume that someone will be sufficiently bold and/or daft so as to actually go ahead and sign this NDA, and thus get to see this fabled source code.

    SCO shows some part of the code, it is anybody's guess what or how much it will be, but there will be some nevertheless. There are two possible outcomes:

    Either the code seen is discovered to be infringed, and SCO has a case, although whoever saw this cannot say so, upon his head be it.

    Or the code is not infringed. The professional who has seen the code still may not tell, but this time there's really nothing to say either: some other code in there could still be infringed and the only conclusion is that time has been wasted.

    Either way, this comes out slightly less than useful. No wonder not many have bothered.

    --
    SIGBUS @ NO-07.308
  69. Larson by Per+Wigren · · Score: 4, Funny

    This whole SCO-thing reminds me of an old Gary Larson strip where a cowboy in a gunfight is told something like "If you get shot, don't just die! Be dramatic! Jump around screaming or something, then die!"

    --
    My other account has a 3-digit UID.
  70. Who wins? by ehiris · · Score: 1

    This thing needs to end. There will be no winning party in the whole trial. IBM will lose, SCO will lose and sadly Linux already started to lose!

    The only winning party in this whole nightmare will be Microsoft. If anybody at SCO has any consideration for Linux or Open Source they should STOP NOW and concentrate their resources on something productive! Even if SCO will win the trial, they will win rights on something that won't be worth anything in a very short time. Linux is alive because it is open source. DON'T SHOOT THE PENGUIN!

    1. Re:Who wins? by bstadil · · Score: 1
      sadly Linux already started to lose!

      I think your are wrong. The IP issue and the GPL was a fight that had to be fought at some point.

      Linux has enough momentum now to continue the steamrolling and we could not have asked for a better partner in the fight than IBM. Second it is a weak enemy.

      --
      Help fight continental drift.
  71. My take on this by AKAImBatman · · Score: 0

    DO NOT SIGN THE NDA!!! Not a single person! If you sign it, SCO will have "expert witnesses" at their disposal. If no one signs it, I assume that the court will appoint someone with appropriate credentials. IANAL.

    1. Re:My take on this by senrik · · Score: 1

      I was thinking about signing it, simply to be discredited by any cross examination. After all, I don't 'do' c Code at all....

      --
      "the difference between myself and a madman is that I am not mad" -Salvadore Dali
    2. Re:My take on this by Squidgee · · Score: 1
      Yes, but you see, the court doesn't appoint expert witnesses; expert witnesses are hired (as in payed) by the party involved.

      While many experts are perfectly truthful, the money can sway opinions, or make certain proof up and disappear. This is why courts require *all* evidence to be discolsed: so the other side can have their own expert(s) go over the evidence as well.

    3. Re:My take on this by budgenator · · Score: 1

      I actualy I know that "experts" are well interviewed and rehearsted before giving their depositions; if your interviews aren't to the hiring parties liking, another will be hired that is more benificial to the sides arguements.

      a good expert can spin for quite a while on 2% of a case and gloss over 98%, even in cross-x without lieing, remember an expert opinion is an opinion.

      --
      Apocalypse Cancelled, Sorry, No Ticket Refunds
    4. Re:My take on this by Anonymous Coward · · Score: 0

      I wouldn't mind seeing RMS as their "expert witness". C'mon, RMS! Take one for the team!

      Yeah, baby!

  72. On Honor by Bob9113 · · Score: 1

    It is amusing (in the tragic/comic sense) to me that what was originally designed to protect honorable companies from dishonorable people has become a weapon wielded by dishonorable companies. This looks like a pretty standard NDA, and a lot less onerous than most software EULAs (even those from supposedly honorable companies like Ximian).

    My favorite piece:
    11. Waiver. Any waiver of, or promise not to enforce, any right under this Agreement shall not be enforceable unless evidenced by a writing signed by the Party making said waiver or promise.

    Translation - when the blow-dried business weenie / marketroid says, "Oh don't worry about this, it's just for our protection, we would only ever use it defensively." - he's lying. By the time the ink is dry there will be someone checking SourceForge, the USPTO, and the Library of Congress for your name to see what they can hijack.

  73. Copyright? by gotan · · Score: 1

    While an "NDA for NDA" wouldn't work as several others pointed out would copyright do the trick? I know that some legal texts are copyrightprotected (bad as it is) and i am wondering when we will see copyright-notices under contracts like that NDA, just to prevent them being publicly sneezed at.

    --
    "By the way if anyone here is in advertising or marketing... kill yourself." -- Bill Hicks
  74. Re:STOX up 29% by Anonymous Coward · · Score: 0

    > P.S. SCO's stock is going up like crazy today. Big volume too.

    this is unreal, ... i wish my virtual cash wasnt virtual :;)

    just look at it,... +29%!

  75. Shorting by tres3 · · Score: 3, Informative
    Shorting is borrowing someone else's stock so that you can sell it now. Eventually you will have to replace that stock but there is no timeframe involved. Betting on movement in a prticular timeframe is where options come into play. If you buy puts then you are buying the right to sell the stock within a certain time frame at a price that is determined at the time the options contract is bought/sold. If you are buying calls then you are buying the right to buy stock within a certain time frame at a price determined at the time the options contract is bought. Likewise you can sell the contracts thereby selling someone else the opportunity to exercise the options contract within a certain time frame.

    Bottom Line: buying options contracts has a predetermined downside: the cost of the contract. On the good side there is no limit to the upside; the more the price of a stck moves in the direction that you guessed the more money that you make. On the other side of the story is that of selling contracts. There is a limited upside: the cost of the contract. There is an unlimited downside though; the more the price of a stock moves against you the more you loose. There is not really any way out of selling a contract except the expiration date. That said you can buy an options contract that is in the opposite direction from the one that you previously sold and stop the bloodletting there by essentially making money on one instrument while loosing it on another at the same time. The general rule of thumb, the reason that there are about as many people selling contracts, either puts or calls, as there are people that want to buy them is that 90% of the contracts will expire worthless.

    There is a major differences in options contracts in Europe and the US: when they can be exercised. In the US options can be bought and sold at any time during the contract. In Europe contracts can only be sold on the date that they mature. Either way they are priced by a method known as The Blask Scholes method. These two economists won a Noble Prize for developing these equations and the markets have never been the same since. The price that they come up with is based on many different things: the current price, the volume of stock, the amount of stock in play, and how fast the price is moving, among others.

    Back to selling stock short. The borrowing of stock is arranged by brokerage houses so you need not worry about that detail but if the price goes up the brokerage house can and will demand that you have enough cash in your account to cover the margin between the current price and that which you bought it at. If you don't have enough margin the brokerage house will do whatever it thinks is necessary to cover their ass as anything that you cannot cover is their loss. That often includes liquidating everything that you own. Just make sure that you have the required margin!!!

    1. Re:Shorting by rakeswell · · Score: 1
      Bottom Line: buying options contracts has a predetermined downside: the cost of the contract. On the good side there is no limit to the upside...

      Yes. What's interesting to me, especially since most option traders I know don't do this, but, it's the people who write (or sell) contracts that are the real winners in the options market. These are the people who write a contract, collect the premium, and when the contract expires out the money, the've earned a modest amount of money -- the premiums they collected. However, you do this consitantly, and it adds up. The upside is limited, but so is the downside if, say, you're writing covered calls (selling calls against stock you already own).

      I've found that most people get into options because they are attracted to that unlimited upside, but they get burned soon enough and either swear off options, or leave it at coverd calls.

      It's a curious thing about options, that they can be the safest investment you make, depending on the options strategy you use, or they can be the most volotile and dangerous.

      --
      All one has to do is hit the right keys at the right time and the instrument plays itself. - Johann Sebastian Bach
    2. Re:Shorting by waveman · · Score: 1

      "There is a major differences in options contracts in Europe and the US: when they can be exercised. In the US options can be bought and sold at any time during the contract. In Europe contracts can only be sold on the date that they mature. Either way they are priced by a method known as The Blask Scholes method. These two economists won a Noble Prize for developing these equations and the markets have never been the same since. The price that they come up with is based on many different things: the current price, the volume of stock, the amount of stock in play, and how fast the price is moving, among others."

      Options can be bought or sold at any time, European or American. However only American options can be exercised before the end date.

      "Blask Scholes method" should read "Black Scholes method". It is not entirely accurate, particularly for way out of the money options. various hacks exist to make it more accurate.

    3. Re:Shorting by tres3 · · Score: 1
      Thanks for the correction. I realized that I should have said exercised and not bought/sold but only after I submitted. The other is a typo, one of three in the origianl post.

      There is a lot to learn about this topic, such as covered options, spreads, straddles, etc.. But since the original topic was SCO blah blah blah. I thought just covering the basics was enough. I think I did ok at that but I did make that one significant mistake about exercising options.

    4. Re:Shorting by tres3 · · Score: 1
      There is not really any way out of selling a contract except the expiration date.

      To be clear this should probably say: There is really no way of getting out of a contract that you previously sold except the expiration date. Since you sold it earlier the correct way out would be to buy it back. It is too much trouble to contact the original buyer and buy it back so you need to buy another contract that makes money while the first one loses money. This is starting to get into the area of spreads straddles and other options investment strategies -- This is offtopic considering the original topic of: SCO's attempt to screw over the Linux community

  76. Posting this NDA is a DMCA violation. by Anonymous Coward · · Score: 0

    I will be reporting this to SCO so they can take legal action against the party who posted this.

  77. NDA prevents any GPL testimony by dnoyeb · · Score: 1

    I imagine that they are being careful. What if they show you something and you say, "hey I wrote that!" And that is released under GPL.

    And of course they can not show all the code. They know that programmers are lazy sometimes and simply copy code they should not have. (or bring code from their last job). I know I keep a personal copy of everything I write ;) Unless they audit their code monthly, which I am sure they do not, they can't be sure themselves they are not violating the GPL or some other license or copyright.

  78. Strange bedfellows by dpilot · · Score: 1

    How's this for a conspiracy theory...

    There has already been some debunking of the theory that Microsoft is funding SCO, so I've got two new candidates. How about the RIAA and MPAA?

    It's all based on the issue of "economy of scarcity" vs "economy of abundance". The latter is what Open Source offers, and some would think is the natural way of handing most IP matters. All that is needed is a business model to make sure artists/authors/inventors get paid, so they'll keep creating.

    But the prime thrust of the RIAA/MPAA (and BSA, for that matter) has been to keep IP in the mode of "economy of scarcity", because under a scheme focused on artists/authors/inventors, they're left out. So far music, movies, etc have remained under a scarcity model.

    However, there is a strong and growing amount of software that remains in the "economy of abundance" model. As long as Open Source exists and thrives, the siren call of an alternative business model beckons to artists/authors/inventors, especially those who feel at the short end of the stick from media conglomerates.

    So in order to retain scarcity for the long haul, it's necessary to kill/discredit abundance. SCO is now at the forefront of this.

    I don't know if this is an attempt at humor, or not.

    --
    The living have better things to do than to continue hating the dead.
  79. Re:I made a copy of the NDA by FyRE666 · · Score: 2, Funny

    and sent it to them next day mail. I signed it Linus Torvalds.

    Well I sign all my mail "Rob Malda", especially my email - it seems to keep my own email address free of spam ;-)

  80. The linux kernel isn't one thing by tvm662 · · Score: 1

    All this talk of SCO making money from licencing anyone who distributes the linux kernel (once they have proved that it contains their IP) depends on the fact that the kernel is a binary, which it is not (always), it is a collection of source file. If a distribution doesn't contain kernel binaries then SCO would have to say which files contained their IP.

    Hypotheitcally if I wrote a program that made a request for each kernel source file seperately from a web server and then built the binary for me - could SCO sue the web server owner, saying they let me have some of SCO's IP, without saying which files? Each request to the server is different and only a few violate SCO's IP.

    Tom.

  81. The First Rule about SCO NDA by zornorph · · Score: 1

    DO NOT TALK ABOUT SCO NDA

    --
    http://bike.stu.ph/rides - free GPS routes available for Garmin, Magellan, GPX and Google Earth
  82. Re:Simple Really - simple yes, but you're wrong by notasheep · · Score: 1

    They have an ongoing lawsuit with IBM over this. Since when is it a good idea to broadcast your evidence all over the place months before it goes to trial?

    Sheesh, people, I'm glad none of you are lawyers for the plaintiff.

    --
    Your mind looks a little cramped. Why don't you stretch it a little?
  83. Let's not Slashdot them, but here's some stuff... by Anonymous Coward · · Score: 0
    Be careful! We wouldn't want to Slashdot SCO's servers.

    Remember that bandwidth costs money, so LET'S NOT ALL DOWNLOAD THIS AT ONCE! Maybe someone can set up a mirror.

    Try this interesting Linux file:

    http://www.sco.com/images/pdf/eserver/not-any-more -eserver_sysadmin.pdf (4 MB)

    They also distribute Linux software like Mozilla:

    ftp://ftp.sco.com/pub/scolinux/server/4.0/updates/ SRPMS/mozilla-1.0.1-38.src.rpm (28 MB)

    Doesn't this show that they are still in the Linux business?

    Again, DO NOT SLASHDOT THEM. Remember that they are in a tough situation and need all the money they can get for the numerous lawsuits they are launching. Wouldn't want their servers to go down or something because of the Slashdot effect...

    ;)

  84. Whats to stop this by WhiteWolf666 · · Score: 1

    Sure, its illegal. But I don't think that it can be stopped.

    Disclamer: I DO NOT have the balls to do this. I wish I did. Maybe if I lived in another country. My puny little balls make me fearful of nearly every legal risk. I don't speed, and I don't disclose NDA protected material. I won't sign this NDA, 'cause I'm scared like a little dog.

    What if, say, John Doe, signed the NDA, got the documentation, scanned it in, removed all personally identifiable charateristics, and then uploaded it to freenet?

    Just a thought. Any of you black hats with big, titanium bullet-proof balls willing to do this? (Note, these are figurative balls. I know MANY females with bigger balls than me. This is not designed to be misogynistic. Any flames will end up burning my balls, and won't be responded to, because I'll be cradling my balls in ice )

    Specifically trouble-making types---seems like you could cause SCO a lot of pain and trouble by pulling a stunt like this, and if you were a lot smarter than me (maybe not that much smarter), you could do it and not get caught.

    Just my 2 cents.

    --
    WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
    1. Re:Whats to stop this by realdpk · · Score: 2, Interesting

      Dunno. They may release a different "map"* of the supposedly infringing code to each person, so they could identify the leak. However, I didn't see anything there (correct me if I'm wrong) that said someone couldn't replace the code and then submit a patch to Linus.

    2. Re:Whats to stop this by Skreems · · Score: 2, Interesting

      If so few people are signing this, and they're only showing partials, they can probably tell who leaked by what information goes out. And then they come to take your balls...

      --
      Slashdot needs a "-1, Wrong" moderation option.
      The Urban Hippie
    3. Re:Whats to stop this by realdpk · · Score: 2, Interesting

      er.

      * since the code is already released, it'd basically be a map, and I guess some code from their archives to back up the claim.

  85. only SCO will sign the NDA by u19925 · · Score: 2, Interesting

    Looking at the NDA, looks like only people who are friendly with SCO will dare sign it. Then they will tell people that the Linux and IBM violated SCO's IP.

  86. The other half... by Jasin+Natael · · Score: 3, Insightful
    "They're agreeing to let you see the half of the picture that they want you to see", he added.

    I wonder if the other half might contain Linux code that's crept into SCO? Mod me down for the consipracy mongering if you want, but there's got to be some reason SCO is behaving this strangely.

    --Jasin Natael
    --
    True science means that when you re-evaluate the evidence, you re-evaluate your faith.
  87. Re:Simple Really - simple yes, but you're wrong by slipstick · · Score: 1

    When it cannot have any possible damage to your case, and would only go towards increasing your stock value. Something which I just realized is that share holders of SCO could argue that the executives are actually depressing the stock price since if they released the evidence and it actually "proved" their case the stock would go through the roof. Thus they have a fiduciary responsibility to reveal that code NOW not later.

    Look, if they've been harmed, than they've been harmed and there is nothing that IBM or anyone else can do. The evidence must be presented before trial anyway to give IBM time to prepare a defense. With IBMs stable of lawyers that time period will be as long as they need. You can't just walk in to court and say "hey here's the evidence, now show today that we're wrong or pay up!" This isn't a case on Perry Masonary. There will be no surprise evidence in this case.

    The only thing gained by not clearly disclosing which lines of code have supposedly been infringed is continued uncertainty and continued exposure in the media. In fact because it can be argued that SCO is not disclosing this code and thus not actively trying to mitigate harm that they will get a less favorable view in front of the judge.

    Furthermore, at the risk of repeating myself, as long as they hold out for no good* legal reason they may be implicitly agreeing to the GPL'ing of the supposedly infringing code.

    * since nothing is gained by holding out, and the code must be presented long before the trial goes to court to give IBM a chance to respond the current ramblings of SCO have no basis in legal fact or fiction, e.g. "no good legal reason".

    --
    Sure information wants to be free, but how much are you willing to pay for the packaging?
  88. 400-500?!? by ProfessionalCookie · · Score: 1

    That would be like a hundred lines of code. From what I understand (from reading slashdot) they only have about 5. That coud be why they're only offering 5 NDAs.

  89. And the other thousand posts must have... by Anonymous Coward · · Score: 0

    Got it right.

    > SCO is obligated to disclose the supposed "infringing" code in order to reduce any possible harm.

    Nope. You are simply wrong.

    "Harm", for SCO, started the moment IBM commited the act SCO claims (if, indeed, IBM did the deed at all). The "Harm" may well continue into the future if the information IBM released cost SCO marketing value into the future.

    SCO is under no obligation to "reduce" harm. It simply can't collect on harm it could have prevented.

    In this case, SCO will hold that releasing the "secret" they are trying to protect would be more harmful than letting the market move on as it were for a short while longer. Thus they might claim they ARE trying to mitigate the greatest of multiple harms in this case.

    > Secondly by not disclosing the supposed infringing code they could be viewed to be implicitly agreeing to it's disemination via the GPL license.

    Again wrong. No such thing as "implicit" agreements when it comes to Copyrights, Patents, or Trade Secrets. If it isn't explicity granted by the owner, there is simply no agreement binding on the owner.

    The GPL plays into all this because SCO (or its predecessors, successors, or assigns) have released versions of Linux they claim contain their secrets. Doing that was an explicit and binding grant by the owner of the IP.

    > They can't simply say that they are being harmed and will be harmed in the future therefore everyone give us money.

    At least you got that one sort of right. But you've still missed the target.

    Damages happen when you mis-appropriate IP without the owners permission AND act in bad faith.

    IBM signed a paper that acknowledged SCO's "property". Releasing that property was an act of bad faith. IBM pays. Now, if SCO doesn't give IBM the means to "fix" that wrong, then SCO may have stopped the clock when it comes to damages or reduced the damages overall.

    Red Hat distributes Linux under a good faith undertstanding that the owner (Linus) permits said distribution. Red Had cannot be held for damages unless 1) they had reason to belive Linux was misrepresenting his ownership interest; OR 2) SCO demonstrates they have a rightful ownership interest of their own AND Red Hat fails to abide by SCOs terms.

    "Damages" start the moment you know, or should have known, you were misappropriating another's IP.

    The Day SCO demonstrates a legal interest in Linux is the day YOU must start paying royalties to them for using it. Or, that is the day you must stop using it altogether. If you do neither that day, damages start.

    1. Re:And the other thousand posts must have... by slipstick · · Score: 1

      >> SCO is obligated to disclose the supposed "infringing" code in order to reduce any possible harm.

      >Nope. You are simply wrong.

      Won't be the last time I'm sure...

      >"Harm", for SCO, started the moment IBM commited >the act SCO claims (if, indeed, IBM did the deed

      Yup, not in dispute.

      >SCO is under no obligation to "reduce" harm. It >simply can't collect on harm it could have >prevented.

      As I noticed on slashdot the other day "a difference, that makes no difference is not a difference".

      This is in fact exactly what I meant by "mitigating harm". They can't collect on harm they can prevent.

      >In this case, SCO will hold that releasing the >"secret" they are trying to protect would be more >harmful than letting the market move on as it >were for a short while longer. Thus they might >claim they ARE trying to mitigate the greatest of >multiple harms in this case.

      They can claim the moon is made of blue cheese, it won't make it so. The "secret" is already out there, it makes no difference whether they release that info now or later except in that users and developers of Linux would be able to remove the supposedly infringing code, something that will happen eventually. This removal isn't a nefarious plot to rob them of their due monies since they can't rightfully collect on harm that might result from this point when they are refusing to reveal that code. As you noted if they were harmed than IBM must pay for harm already performed. The harm can continue in the future as it reduced the value of the secret. But by not revealing a "secret" that is no longer secret they are making no good faith attempt to stop any supposed copyright or trade secret infringement by others. So they will not be able to collect damages from others for supposed harm during this period.

      >> Secondly by not disclosing the supposed
      >>infringing code they could be viewed to be
      >>implicitly agreeing to it's disemination via the
      >>GPL license.

      >Again wrong. No such thing as "implicit" >agreements when it comes to Copyrights, Patents, >or Trade Secrets. If it isn't explicity granted >by the owner, there is simply no agreement >binding on the owner.

      I said they "could be viewed as implicitly agreeing" I didn't say it was legalling binding.

      >> They can't simply say that they are being >>harmed and will be harmed in the future
      >>therefore everyone give us money.

      >At least you got that one sort of right. But >you've still missed the target.

      Since it was an extremely colloquial statement I'm not surprised you think so.

      >Damages happen when you mis-appropriate IP
      >without the owners permission AND act in bad
      >faith....
      >
      >Red Hat distributes Linux under a good faith >undertstanding that the owner (Linus) permits >said distribution. Red Had cannot be held for >damages unless ... 2) SCO demonstrates they have >a rightful ownership interest of their own AND >Red Hat fails to abide by SCOs terms.
      >
      >"Damages" start the moment you know, or should >have known, you were misappropriating another's >IP.
      >
      >The Day SCO demonstrates a legal interest in >Linux is the day YOU must start paying royalties >to them for using it. Or, that is the day you >must stop using it altogether. If you do neither >that day, damages start.

      No, the day SCO demonstrates a legal interest in some code that may be in the Linux kernel is the day I must stop using that code. They must reveal that code to me for me to stop using it. This does not mean I must stop using Linux. Due to the nature of this software as both a user and possible distributor of the source code they must reveal how I am infringing their copyright so that I can remove that code myself.

      Attempting to place the court proceedings under Trade Secret status will do them no good

      --
      Sure information wants to be free, but how much are you willing to pay for the packaging?
    2. Re:And the other thousand posts must have... by Anonymous Coward · · Score: 0

      > This is in fact exactly what I meant by "mitigating harm"...

      Good. But, there is a gowing body of /lawyers that seem to think SCO has to "reduce harm" inflicted on the likes of Linux programmers if they "kill" Linux so late in the game. You know, the programmers wouldn't have wasted their time had they known, etc. etc.

      > The "secret" is already out there...

      So, you know what it is? Thought not. The secret is still a secret.

      > They must reveal that code to me for me to stop using it.

      No, I don't believe they must. They need only dutifully inform you that a court of law has found they have a lawful ownership interest, the extent of that interest, and what they require for you to continue to exploit that interest.

      > This does not mean I must stop using Linux.

      Actually, it does. If SCO has misappropriated copyrights in Linux, then any version of Linux that contains that code is a derivitive work. You "can't use Linux at all" until such time as a work of Linux is produced that is a non-derivitive work.

      > they must reveal how I am infringing their copyright so that I can remove that code myself.

      No, they don't. They have no obligation to you beyond asserting their valid ownership interest in the derivitive work. They don't even have to inform YOU directly, you are obligated as soon as you know, or should know, their claim is valid. They have exactly zero obligation to assist you with any form of "self-help", like helping you find and remove their works for a larger derivitive.

      For SCO to assert (with valid legal standing) "we own copyrights in all works prior to Linux 2.whatever" is more then enough. If the court seals the proceedings, so be it. They owes you nothing more.

      This could get quite sticky, actually. If SCO wants to go the copyright route they could find Linux pre-version whatever infringing on the basis of the first few lines of code they find. Let time pass, "clean" versions be released, end-user adoptions be made, then assert their ownership in a new legal proceeding over the next few lines of code. And so on, as long as they have code somewhere in the work.

      > I said they "could be viewed as implicitly agreeing" I didn't say it was legalling binding.

      Ok, lawyer 101. You can safely assume "agreements" are "binding", unless they run counter to existing law (like... We agree you'll kill my wife for $100).

    3. Re:And the other thousand posts must have... by Anonymous Coward · · Score: 0
      > They must reveal that code to me for me to stop using it.

      No, I don't believe they must. They need only dutifully inform you that a court of law has found they have a lawful ownership interest, the extent of that interest, and what they require for you to continue to exploit that interest.

      I interpret that to mean, "You are doing something illegal. I cannot tell you what it is, but you must cease doing it immediately."


  90. Re:Simple Really - simple yes, but you're wrong by Anonymous Coward · · Score: 0
    They have an ongoing lawsuit with IBM over this. Since when is it a good idea to broadcast your evidence all over the place months before it goes to trial?

    This has been discussed before. Just because they show their evidence, and even if all the infringing code is replaced tomorrow, that does not excuse the infringement. All the evidence is still there on thousands of CDs and web sites. For example, if somebody steals your car, and the police catch them, just because you get your car back doesn't excuse the thief.


  91. gpl? by Suppafly · · Score: 1

    It would seem to me, that if SCO plans on showing any gpl'd linux code other than what they claim is stolen from them, they would be violating the gpl by putting restrictions upon releasing gpl source code to binaries that they have distributed.

    The FSF should jump on their case about distributing linux binaries for years and now trying to get out of showing the code for free. It would seem that this NDA couldn't cover any code released under the gpl, just code that SCO has in their propriatory unix product so anyone seeing both, could say what part of linux is in question.

    1. Re:gpl? by AlphaSys · · Score: 1

      You, sir, are absolutely right. The NDAs limitations violate the GPL which SCOLDERA has already agreed to.

      --
      Can I bum a sig? I left mine at the office.
    2. Re:gpl? by Anonymous Coward · · Score: 0

      Look at you! - spewing gook and calling people sir like this is some sort of RP board. You dont care about the GPL movement, you are a Windows kiddie. You have never read a flamewar in LKML (re: GPL Nvidia drivers, BitKeeper/KitBeeper or Mcvoy) or elsewhere when RMS goes on a rant. You are just jumping on the bash SCO populist bandwagon. You are a malcontent who knows not why he fights for what he fights for. Amusing to watch.

    3. Re:gpl? by AlphaSys · · Score: 1

      Really, AC, Give it a reast. I was cursing Orem slack when you were learning how to plug in a keyboard.

      --
      Can I bum a sig? I left mine at the office.
    4. Re:gpl? by AlphaSys · · Score: 1

      Oh, god. Made a typo while making a keyboard ad-hominem attack, Can't wait to see what that gets me.

      --
      Can I bum a sig? I left mine at the office.
    5. Re:gpl? by Anonymous Coward · · Score: 0

      Dude: you are the biggest loser on Slashdot. If the HoF had a place for this, it would be yours by a longshot.

  92. SCO Anthem... by techturtle · · Score: 1

    I heard this song on the radio today and thought "This should be the SCO anthem!".
    In the words of the great Don Henley:

    Dirty little secrets
    Dirty little lies
    We got our dirty little fingers in everybody's pie
    We love to cut you down to size
    We love dirty laundry

    We can do "The Innuendo"
    We can dance and sing
    When it's said and done we haven't told you a thing
    We all know that Crap is King
    Give us dirty laundry!

    The whole thing applies...

    --
    If you don't have something nice to sig, then don't sig anything at all.
  93. Boies == attorney conflict-of-interest (COI) by Anonymous Coward · · Score: 0

    Boies worked for IBM as representation against the Feds some years ago. Now he's attempting to work for IBM's adversary. This is blatant attorney conflict-of-interest, and pretty much banned by every legal bar association on the planet. Both SCO and Boies are so freaking stupid that they didn't realize this little problem until now. Lawyers have been known to lose huge malpractice suits when they negligently take on a client who is an obvious C.O.I. case, they've even been known to get disbarred because of it.

  94. Bullshit. by twitter · · Score: 2, Interesting
    You don't think that:

    1. The experts are already known.
    2. The experts must know the evidence and be unrestrained in what they say.
    3. The courts will provide the evidence to the experts so that the above condition is met.
    4. SCO just wants to make trouble and this whole case is propaganda?

    That the NDA would be unacceptable was so predictable it's not even funny. Only M$ and SCO shills would sign that thing and SCO is going to say stupid things about free software advocates who refuse to put themselves at the mercy of the state of Utah. Next, they will plant chunks of code someplace and say the anarchists put it there.

    Fuck you SCO.

    --

    Friends don't help friends install M$ junk.

  95. My Vow by Thing+1 · · Score: 1, Troll
    I vow to post these instructions every time an article on SCO comes up.

    My Favorite, from the other night. Put the following in the file get_sco.sh and then "chmod u+x get_sco.sh":

    #!/bin/sh
    wget -O /dev/null ftp://ftp.sco.com
    This will download their entire FTP site (to /dev/null of course).

    Put it in a loop if you really want to hurt them:

    while true ; do ./get_sco.sh ; done
    Report back when the site's down.

    This works on the bash shell, which is the default under Cygwin on Windows -- so Windows users can help also.

    --
    I feel fantastic, and I'm still alive.
  96. Better buy put options by gotan · · Score: 1

    I'd buy put-options, since i think that SCO shares will soon drop below $1. Another tactic might be to buy shares and a lot more put options. That way if SCOX experiences any drastic changes, be it up or down, you win. It will be quite interesting to watch SCOX when IBMs Unix-license with SCO expires and SCOs bluff not to renew the license is called.

    --
    "By the way if anyone here is in advertising or marketing... kill yourself." -- Bill Hicks
  97. True. by twitter · · Score: 1
    One would think only a moron would sign an NDA that didn't guarantee access to ALL information relevant to these issues.

    Moron or a shill. They want to be able to discredit anyone who would say they are full of shit. "They don't have all the information." they can say. So what exactly are they showing? What's the point? Their shills can say, "I've seen the code and SCO is dead to rights." without having to prove a thing.

    It's SCO precictable. Expect loads more BS to flow before these morons go away.

    --

    Friends don't help friends install M$ junk.

  98. Oh, this one's a gem by dmforcier · · Score: 2, Funny

    12. Construction. ... This Agreement represents the wording selected by the Parties to define their agreement and no rule of strict construction shall apply against either Party.


    In other words, "This Agreement means what we intend it to mean, and not what it actually says."

    I wouldn't touch it with a 10 ft pole.

    {Not that I actually have a 10 ft pole, and I didn't intend to imply by listing a 10 ft pole in the text that the text has anything to do with an actual 10 ft pole, and you agree that ... bleh)
    --
    You can't take the sky from me!
  99. This is all getting out of hand... by Demerara · · Score: 3, Interesting

    I have followed this story since it broke. Right now, I'm none the wiser. The publication of the NDA is not really revealing - it's what you'd expect given the rhetoric.

    Nor is SCO's suit against Novell the real issue. IMHO, what's needed is for one of the 1,500 leading companies to whom SCO sent their "Stop Using Linux Or Else" messages to pony up, get some quality IP attorneys and throw it right back at SCO.

    Picture it. Acme Widgets Inc respond to SCO with a clear message that they will NOT stop using Linux unless SCO can provide evidence of their claim.

    Now, bluff firmly called, SCO have to put up or shut up. Acme Widgets Inc have to convince a judge to force SCO to identify the code they claim (not trivial). And somehow (and IANAL) this has GOT to get into the public domain - not SCO's code but the GPL's Linux Kernel sections claimed by SCO.

    Once this happens, the uber-geeks who gave us Linux can replace the SCO sections with newly-developed code and we can all go about our business. Given the community's sparkling record on patch turnaround time, this could be concluded rapidly enough to offer Acme grounds for a dismissal.

    C'mon Acme - go for it!

    I believe SCO are trying to protect their IP - it's their methods which are truly offensive. Even if this case blows over, does the Open Source community want contributions from people like this?

    The same might be said for IBM's silence on the issue - as Edmund Burke (IIRC) put it "evil will prevail when good men do nothing".

    --
    Backward%20compatibility%20is%20over-rated
    1. Re:This is all getting out of hand... by Anonymous Coward · · Score: 0

      Reading this post I keep thinkin your are referring to "acme" the kernel hacker at conectiva...

      I keep wonderring, "why does acme have to do all the work?"

      PS: The same might be said for IBM's silence on the issue - as Edmund Burke (IIRC) put it "evil will prevail when good men do nothing".

      IBM is keeping silent because that's what anyone does who wants to win a court case. When the time comes, you'll see how badly SCO pays.

  100. SCO uses Linux by Anonymous Coward · · Score: 0, Offtopic

    Thought this was interesting. If you look up www.sco.com on netcraft this is what you get.

    The site www.sco.com is running Apache/1.3.14 (Unix) mod_ssl/2.7.1 OpenSSL/0.9.6 PHP/4.0.3pl1 on Linux. FAQ

  101. Secrecy? On the Internet?? There's a novel idea by ThePatrioticFuck · · Score: 1
    And the facts are going to come out during the trial anyways, so all you'd gain by signing the NDA is a small amount of time to look at the code before everyone else does.

    What, you think it's gonna take until the trial for this info to leak? I give it an hour once the first people outside of SCO see the "proof" :)

    TPF

  102. If I had any money... by Thing+1 · · Score: 1
    If I had any money, I'd be buying 1-year puts and calls on SCO, near the current strike price.

    Why? Well, going long (buying) stock is good when it's going up. Going short (selling before buying, by borrowing the stock from your broker -- you need a margin account for it) makes money when the stock goes down.

    Options make money within a certain timeframe on stock moves. Back when I did have money, late 1998 I believe, I thought Dell would move but wasn't sure which direction, so I bought both puts and calls, in equal dollar amounts. The stock moved up, and I made money on the calls and lost 100% on the puts. However, the amount I made was something like 700% (God I miss the 90s!), so the bet paid off bigtime.

    Right now, either SCO has something up their sleeve (which the evidence, such as there is, doesn't seem to support) or they're a fuckedcompany and will be sleeping with the fishes before long. One year is plenty of time for this to pan out (if I was more of a gambler, I'd say 3 months).



    Dammit, I said all that and turns out there are no options for SCOX stock. Oh well. Here's the current options for DELL in case you want to learn more (the CBOE has more info in their links -- see the Learning Center at the top right).

    --
    I feel fantastic, and I'm still alive.
  103. Oh sillyness by magi · · Score: 1

    People looking at the source code doesn't help a thing as they can't find out the source of the source just by looking at the source. All you can find out is, "Hey, they really look similar, I wonder why?"

    What needs to be communicated, publicly, is the exact files and lines of code in Linux sources that allegedly violate SCO's Intellectual Prescious. However, even then the Linux community can do only half of the job in determining the source of the source. The other half is determining who wrote the SCO code and when. That requires a police investigation -- interrogations of old or former SCO developers and such.

    The review of the allegedly violating code has no legal meaning. Only what happens in court matters.

    And only a complete idiot would sign such an NDA with a company that has gone crazy suing others for NDA violations. Only write an NDA manufactured by a court dealing with the matter, when you have been called as a witness.

    IANAL, etc.

  104. Re:Come someone... by jedidiah · · Score: 1

    I heard from a Marine that served two tours over there that they would just shoot annoying Louie's in the back. Nevermind sneaking around at night with the grenades.

    --
    A Pirate and a Puritan look the same on a balance sheet.
  105. Why not just go look for it yourself? by IO+ERROR · · Score: 1
    Look, I found LOTS of SCO code in Linux! It was pretty easy, too. All I had to do was use those evil utilities "find" and "grep".

    error@sky /usr/src/linux-2.4.20 $ find . -name "*.c" | xargs grep -lwi SCO
    ./arch/i386/kernel/microcode.c
    ./drivers/add on/qla2200/qla_vendor.c
    ./drivers/bluetooth/hci_b csp.c
    ./drivers/bluetooth/hci_h4.c
    ./drivers/blu etooth/hci_usb.c
    ./drivers/char/applicom.c
    ./dri vers/char/console.c
    ./drivers/char/rio/rio_linux. c
    ./drivers/char/rio/rioboot.c
    ./drivers/char/ri o/riocmd.c
    ./drivers/char/rio/rioctrl.c
    ./driver s/char/rio/rioinit.c
    ./drivers/char/rio/riointr.c
    ./drivers/char/rio/rioparam.c
    ./drivers/char/ri o/rioroute.c
    ./drivers/char/rio/riotable.c
    ./dri vers/char/rio/riotty.c
    ./drivers/net/hp100.c
    ./d rivers/net/wan/sdladrv.c
    ./drivers/net/tlan.c
    ./ drivers/video/virgefb.c
    ./fs/bfs/inode.c
    ./fs/sy sv/super.c
    ./net/bluetooth/hci_conn.c
    ./net/blue tooth/hci_core.c
    ./net/bluetooth/hci_event.c
    ./n et/bluetooth/sco.c

    Looking through these files, it seems as though some SCO employees have contributed code to Linux directly, and some other code was lifted more or less directly from SCO source code. I don't know what the legal status of any of this code is, but it could make a good starting point for taking a serious look at SCO's claims.

    I also don't know what impact it would have on the kernel if all this code had to be removed or rewritten. Everytime I've tried to hack on the kernel, I've managed to get completely lost.

    --
    How am I supposed to fit a pithy, relevant quote into 120 characters?
  106. Amend the GPL! by dipipanone · · Score: 1

    They've certainly removed themselves effectively from the pool of OSS developers.

    I'd like to see it go further than this. I'd like to see the GPL amended so that the code can be used by anybody except employees of SCO and their customers.

    Unfortunately, as I'm not a programmer (and as a result I'm not overly familiar with the GPL), I don't know how feasible such a move would be, but it would certainly be a cute case of tit for tat.

    SCO threatens Linux customers, Linux threatens SCO's customers right on back -- and eventually we'll see who has history on their side.

    1. Re:Amend the GPL! by Anonymous Coward · · Score: 0

      Cute? No, not really.Just unbelievably petty.

    2. Re:Amend the GPL! by tomhudson · · Score: 1
      Gotta agree w. you there. There's nothing to prevent developers to specify a licensing scheme other than the GPL, of course.

      We could call it the NPOSL - non-proprietary open-source license:

      This software may only be used in conjunction with non-proprietary, open-source, open-standards software and operating systems. Distribution with, copying of or porting the code to a proprietary or closed application/system/whatever is prohibited.
      :-)
    3. Re:Amend the GPL! by dipipanone · · Score: 1

      I don't really have any problem with people using open source software with proprietry software. Free as in freedom, and all that good stuff.

      However, it seems to me that when you've got somebody out to destroy you, it's insane to be giving them freebies while you do it.

      So SCO don't like Linux? Well, lets see how their customers feel about that. Given the choice between running SCO software, and having access to the vast quantities of GPL'd software, I wonder which they'd choose?

      My guess is that denying SCO's customers access to GPL software would kill them faster than any court case.

      You may see that as petty. I see it as denying your enemies the opportunity to slaughter you using your own weapons, and as such, that's just common sense.

    4. Re:Amend the GPL! by tomhudson · · Score: 1

      I agree. It's one thing to compete fairly, quite another to feed the hand that's biting you. SCO couldn't compete fairly, so they're biting (hopefully MUCH more than they can chew).

  107. This "SCO" is really Caldera. by Anonymous Coward · · Score: 3, Informative

    Caldera bought the SCO name and properties, and then changed their name. These shots are being called from the former Caldera's headquarters.

  108. Write an alternative contract by Anonymous Coward · · Score: 0

    ESR perhaps? And propose that. As it stands now, they'll never get any witnesses that are "impartial" or on the other side of the accusations. ACINAL, but I'd think that whether or not such people can be called as witnesses having seen the code would be of crucial importance as to how any sane judge (perhaps that's where I go wrong ;-) would weigh these "expert witnesses".

  109. Damn Achronyms by r_cerq · · Score: 3, Funny

    They probably think NDA stands for No Details Available.

  110. Seen the code by Anonymous Coward · · Score: 1, Interesting

    I signed the NDA, and have seen the code.

    Do SCO's claims have merit? Sorry I'not allowed to tell you.

    Just kidding :) I'm only a lowly AC.

    However I do think this type of course is likely to be the case for the any real analyst who does sign their NDA. If you look at the code and then publicly reach a conclusion one way or the other, you are practically pinning a big "sue me" sign on your back, especially if the court's final judgement is not 100% in indetical with what you say. If you say the code infringes and the court says no, IBM and Linux-friends come after you. If you say it doesn't, you get a letter from SCO's lawyers.

  111. Just a thought.... by Anonymous Coward · · Score: 0
    Has anyone ever considered taking advantage of all those open source and free software P2P tools by getting everybody to sign the NDA, then having one unscrupulous person just happen to "accidentally" slip it out on Gnutella? I mean, it's untraceable, so there's built-in plausible deniability....

    Imagine that... a chance to use P2P for good....

  112. Suggestion: by the_real_tigga · · Score: 3, Interesting

    In order to reduce bandwidth usage of both the Slashdot infrastructure
    and Slashdot readers' internet conections, when replying to articles covering
    anything legalese, just leave out the ubiquitous "IANAL, but", and only
    in case you are a lawyer, use "IAL, therefore" or "IAL, hencewith".

    Thank you.

    --
    my .sig is better than yours.
  113. I'll do it! by Laplace · · Score: 1

    My wife and children frequently refer to me as a soul-less bastard. I'll sign the NDA. What do I have to lose?

    --
    The middle mind speaks!
  114. scohurt.sh by gmhowell · · Score: 1

    #!/bin/sh
    while true
    do wget http://www2.caldera.com/download_files/049-000-001 DL/volution_manager_1.1_eval.iso -O /dev/null
    done

    eliminate spaces in the url first.

    --
    Jesus was all right but his disciples were thick and ordinary. -John Lennon
  115. Re:Come someone... by budgenator · · Score: 1

    Originaly, fraging was throwing a fragmentation grenade into someones tent while they were sleeping, the someone was usually a superior Office or NCO. Grenades leave little forensic evidence that could be collected without a FBI crime-lab, so the murderer usualy got away scott-free. This was quickly expanded to include shooting people durring fire-fights, which is often difficult to seperate from freindly-fire accidents.

    Military leadership is the art and science of telling a group of people who out-number you, and are armed with pistols, rifles, and grenades to do things that could very easily get them killed or maimed, and having them do it.

    --
    Apocalypse Cancelled, Sorry, No Ticket Refunds
  116. Re:Secrecy? On the Internet?? There's a novel idea by aridhol · · Score: 1

    They control what you get. What makes you think that everybody gets the same code? They could give different people different parts of the code (the "important" part, as well as some "identifying" code). Then, they can tell who posted it.

    --
    I can't say that I don't give a fuck. I've just run out of fuck to give.
  117. missing the obvious by SimonInOz · · Score: 1

    Let me see - SCO are claiming that the Linux code (available to anyone) has been copied from their code.
    SCO are happy to show their code to anyone who signs an agreement agreeing not to use it.
    But they claim their code is the same as the Linux code - which is available to anyone ...
    So all you get to see is two pieces of code, supoposedly the same. It doesn't sound too interesting ... look mum, these two screens of code are the same!

    Sounds pretty boring.

    --
    "Cats like plain crisps"
  118. SCO Allegations and NDA by othertimothy · · Score: 1

    How does one know that SCO has not manufactured the evidence by taking Linux source code and wrapping it in their style of comments just so they can compare Linux source code to the artificial evidence? Considering the amount of time that elapsed between the date of SCO's allegations and the date of their announcement that they will let people see their evidence and the restrictive nature of the NDA it makes me wonder that they aren't trying to a "Wag The Dog" maneuver.

  119. Re:From the GPL... by PhilTR · · Score: 1

    "The ENTIRE sourcecode will have to be revealed in court."

    Not quite. The code can be shown to the judge "in camra" ie., in his chambers.

  120. Let SCO reveal their experts by J+Story · · Score: 1

    This NDA is obviously a problem. As an alternative, would SCO be willing to reveal who their "experts" are who assert code violations, and make them available for questioning?

    It should be instructive to ask these experts about the conditions around their claim:

    • did they check the "offending" code for prior art?
    • what specific files contain the code?
    • why does the code purportedly offend?
      Word-for-word copying? (If so, how much?)
      Copying of ideas?

    How about Slashdot preparing a top-ten list of questions for them?

  121. What's to stop them making it up? by Anonymous Coward · · Score: 0

    "SCO can pick and choose among all its evidence" to show only the parts that back up the company's claims. "They're agreeing to let you see the half of the picture that they want you to see"

    Just means they haven't quite finished falsifying the evidence yet....

    Seriously, though..Linux code, as we all know, is freely perusable by anyone who can be bothered..SCO's code is only viewable on SCO's say-so.
    What's to stop them presenting a bunch of code that they've worked up to "prove" their point?

    Anyone who called them out over a lie would clearly have been ferreting in their precious source, and thus eligible for exile on Pluto under the DMCA!
    Who needs evidence? We've got Lawyers! Stall 'em until we can make some up!

  122. Analyst reports identical code in SCO and Linux by Anonymous Coward · · Score: 0

    Informationweek.com reports that one of the first analysts to see SCO's "proof" (under NDA) did find matches between SCO and Linux code

  123. "Caldera" means burned out volcanic hole by konmaskisin · · Score: 1

    ... usually these things end up collapsing in on themselves.

  124. inforweek concludes that SCO copied into linux. by walterbyrd · · Score: 1

    Larua Didio concluds that SCO code was copied into Linux. Here is the article:
    URL: http://www.informationweek.com/story/showArticle.j html?articleID=10300314

    1. Re:inforweek concludes that SCO copied into linux. by Anonymous Coward · · Score: 0

      It seems this Laura Didio just spilled the beans.. Hope she really knew what she was reading because if she didn't she better be prepared for a lawsuit.

    2. Re:inforweek concludes that SCO copied into linux. by I_redwolf · · Score: 1

      Ok; http://news.com.com/2100-1001-222044.html

      How does she know the code wasn't copied from Linux to Unixware or that it wasn't freely given to Linux? She must be very positive to say something like that.

    3. Re:inforweek concludes that SCO copied into linux. by Anonymous Coward · · Score: 0
      A quick google search of Laura Didio indicates that she may also be a Principal at ITIC. They are a company that makes revenue from selling software licenses.

      That sounds like a pretty good reason to tout the merits of SCO's weak case. She's got secondary motivation for wanting people to start buying licenses for SCO IP in Linux. More $ for her. I don't think any real unbiased analysts are going to do a thorough review of these code snipets.

  125. McBunkum has admitted to exactly this. by L.+J.+Beauregard · · Score: 1
    [SCO] want to collect royalties. They cannot collect royalties if the code in question is removed and replaced with "clean" code, which is what will happen within minutes of them announcing exactly which lines of code are in violation.

    McBunkum has admitted to exactly this in the IBM-buy-us-out article:

    The open-source community, however, won't be be given an opportunity to remove any offending code and replace it with new material, he [McBunkum] said. Instead, damages will continue to be sought.

    Is there any doubt left that the judge needs to smack this guy down like the liar and FUDster that he is?

    --
    Ooh, moderator points! Five more idjits go to Minus One Hell!
    Delendae sunt RIAA, MPAA et Windoze
  126. SCO means Sour Cream and Onion by Anonymous Coward · · Score: 1, Funny

    Not my favorite flavor of UNIX, that's for sure.

    1. Re:SCO means Sour Cream and Onion by Anonymous Coward · · Score: 0

      So does that mean SCC is Sour Cream and Chives?

  127. Don't give them ideas!!! by Anonymous Coward · · Score: 0

    they wouldn't have been clever enough to figure that one out by themselves...

  128. SCO Owns UNIX copyrights by Anonymous Coward · · Score: 0

    After all the Novell hoopla, SCO does apparently own UNIX copyrights but not the patents - according to a 1996 contract amendment.

  129. Re:Not so simple. Really. ^H ^W by Anonymous Coward · · Score: 0

    Heh. That AC napped you on the ^H. That was sweet. Dude: You're gettin a Dell!

  130. SCO owns UNIX copyright by Anonymous Coward · · Score: 0

    After all the hoopla about whether SCO or Novell owns the UNIX copyrights - News.com is reporting that a recently rediscovered contract between Novell and SCO dated 1996, seems to indicate that SCO do infact own the copyright (but not patents) for UNIX.

    Meanwhile over at InformationWeek, the first analyst to report back on seeing SCO's "proof" under NDA, says she did find matches between Linux and SCO code. Laura DiDio, a Yankee Group analyst says she finds this "very damaging" - although of course Penguin lovers will probably be already be speculating about other possible reasons for any possible matches.

  131. Have to see the comit history, too by dbc · · Score: 2, Informative

    Who cares if you see source?
    Saying: "Looky looky! Same bits!" proves nothing.
    You have to look at source tree A and source tree B and the commit history with dates, and then you at least know who included it in the source tree first... still, *that* proves nothing.
    SCO must show the provenance (sp?) of the code in question, with a prerponderance of the evidence. Both A and B may have copied code from the same text book, same manufacturer's ap note, same whiteboard in a CS lecture, whatever. Unless SCO can show that they had it first, and that there is little likelihood it could have come from someplace else, only then do they have a case.
    Looking at source without commit histories is pointless. Looking at commit histories does not establish where the source came from.
    So, looking at source under NDA proves what, again?

  132. Twisted Coverup of GPL Violation? by friartux · · Score: 1

    Here's a thought for you: presumably SCO source is a little harder to come by than Linux source.

    Who's to say that any duplicated code wasn't Linux code misappropriated by SCO?

    Or code (and according to recent stories, comments) from *BSD?

    It would be a very twisted way to try to turn a GPL violation into a profit... and recent crud from SCO has certainly been twisted and warped in every other way possible.

  133. Some statements are inacurate by towatatalko · · Score: 1

    Some of your statements are inaccurate;
    âoebuying options contracts has a predetermined downside: the cost of the contractâ â" since you buy something it has its price but why is that disadvantage in buying options? It isnâ(TM)t, because options cost far cheaper than the âoeunderlyingâ value of the stock. IBMâ(TM)s share that cost say $90, for 100 shares youâ(TM)d pay $9000, while one call option at $90 âoestrikeâ might cost just $300. For every one point, or $1, if IBM stock goes up, you gain some value. So, on 100 shares youâ(TM)d gain 100 (shares) * $1 = $100, but your total investment was a whooping $9000.

    At the same time if you bought just 10 call options, your investment is $3000 and with $1.00 price movement in stock the gain would usually be $400*10=$4000 subtracting investment of $3000, youâ(TM)re left with $1000 gain, right? If you could use the whole amount of $9000 for buying call options youâ(TM)d have around $3000 in gain. Thatâ(TM)s why options are such attractive leverage against the underlying stock value: you donâ(TM)t need to have huge money to use options and gain more than by buying/selling stocks.

    âoeThere is a limited upside: the cost of the contract. There is an unlimited downside though; the more the price of a stock moves against you the more you looseâ â" not really clear what you mean by âoea limited upsideâ. Downside/upside are basically have the same potential for calls and puts depending on the stock movement. If the stock moves against you thereâ(TM)s nothing that prevents you from closing your position and exiting with a limited loss, you donâ(TM)t have to wait until the option loses its all premium value or expires worthless âoeout of the moneyâ at the expiration date.

    âoeThere is not really any way out of selling a contract except the expiration dateâ - ??? on what options?, equities, stock options? You probably never traded any options yourself, I make several option trading a day, in and out, the same option can be bought/sold at your own decision and nothing else, you donâ(TM)t need a broker to do that or wait until expiration date for that option to make profit. I would recommend Optionetics or Shaffer's option tradding classes for those who are into this subject.

    --

    IP was invented for the sake of lawsuits.
  134. Picture this by Oper+Sorcerer · · Score: 1

    Make SCO share a jail cell with Martha Stewart. The clueless nitpickers deserve each other.

    --

    karma: Marianas Trench (mostly blub blub)
  135. I'm sorry--- you say that US' tort system changed? by MickLinux · · Score: 5, Insightful
    Last I knew, it was always possible to buy professional witnesses to say whatever you want them to say. And you think that MSCO won't be buying witnesses?

    Quite seriously, a major reason for America's economic troubles, according to the Harvard Global Competitiveness Report, is a failure of the court systems, especially in contract law.

    Although the whole report is for sale, you can click through to some pdfs, and read them. Especially interesting is the Executive summary, in which [p. 19] they say that they are increasing the weighting of technological innovation, [p. 20] note that the US has fallen to #2 and Finland has taken #1.

    Yet for the case of the United States [p.37], they note that the bubble has burst, and they say that technology is *overrated*. They also note that the major problems with the US are the undermined court system, now ranked around #14.

    What that means is that they US hasn't just fallen to #2. In reality, the US has already fallen a good deal farther. And when you consider that superpowers *do* have more power, and therefore fall under the category of "more competitive" all other things being equal, that means that the US is really hurting, and is probably going to hurt more. Fallen, fallen, is Babylon and all that.

    Now, flip over to the Cato Institute, and you can find documents [or this] where they point out that the fall Argentina's peso was engineered, and that this represented a major additional break from the rule of law. But what also hurt was that their court systems were completely corrupted, and their society had separated into two societies: the taxed and the government folks.

    Well, hate to break the news, but it's looking a lot like what Argentina had, America is getting ready to eat themselves. Not that it will be exactly alike. I fully expect a blackmarket boom in Argentina, followed by [1% chance] them becoming the top economic power in the world if they are good to each other, or [99% chance] them turning military and conquering most of South and Central America, and sending a pressure hammer of refugees into North America. The US, on the other hand, I expect to slide into corruption, and be overwhelmed by said pressure hammer.

    But back to the topic at hand, I don't think we can necessarily expect expert witnesses, truth, and Justice to prevail, in light of the American way.

    So if you're into Linux, download all the source code you can right now, and put it on CDs/DVDs, and keep it. You may find that it is quite valuable for internal use, and public use after you're sure that it's clean. Don't let Linux depend on America, because America has different ideas right now.

    --
    Correct Horse Battery Staple: 72 bits of entropy. Enter "Correct H" into google. When it generates the phrase, that's
  136. You mean like Krakatoa / Crete? by MickLinux · · Score: 1
    Hate to break it to you, but "Caldera" is one of the most violently destructive naturally-developed volcano types around. First the bubble of magma rises to the surface. Then it releases steam for a few days, until the pressure drops down to below that necessary to hold the roof up. Then it falls in and explodes an a giant ... well ... blast ... that would dwarf the tiny thing at Mt. St. Helens.

    There are probably more violent geologic activities than that -- for example, a wall of lava 500 m high that rushed from eastern Washington State to the pacific in the age of the dinosaurs [talking off the top of my head here... and I have a very unreliable memory].

    But my impression was that that wall of lava could have been stimulated by cracks in the Earth's crust after an asteroid impact.

    Point being, though, wouldn't it be ... well, something amazing, if M$ had been targeting Linux from the first, and named had their little trojan horse named Caldera as their little signature of smugness as they ...

    Nah. Couldn't be.

    PS. There's a caldera under Long Valley near Cal Tech, and I think there's another under Minnesota. And don't believe the PBS documentary about Krakatoa and climatic change -- when my Dad and I were watching that, he said "they lied, outright there" twice, and stopped the VCR, and pulled out some magazines [Sci Amer, Nat Geo], and showed where references made in the PBS documentary said exactly the opposite of the referenced material.

    --
    Correct Horse Battery Staple: 72 bits of entropy. Enter "Correct H" into google. When it generates the phrase, that's
  137. SCO people are not Mormons by Anonymous Coward · · Score: 0

    Mormons believe in being honest. SCO has not shown that ability. Mormons believe in freedom. SCO does not. In fact SCO acts the way that Mormons believe Satan would act.

  138. SCO: Inventors of the "Hello, World!" Program by Anonymous Coward · · Score: 0

    I can just imagine the code they will show. It will look something like this:

    #include<stdio.h>

    int main(int argc, char **argv) {
    printf("Hello, World!\n");
    return 0;
    }

    Now, with seeing that, what could you legally code? Are you still allowed to program and use the same functions as them?

  139. Re:NDA for the NDA? Rule #1 by Anonymous Coward · · Score: 0

    "The first rule of the NDA is that you do not talk about the NDA!"

  140. Must be Robin Hood by tonyl · · Score: 1
    Apparently at least one person agrees with SCO after seeing the code: http://informationweek.com/story/showArticle.jhtml ?articleID=10300314.

    She says she was shown indentical comments. If true, that could be rather damning.

    I wish they would at least publish the comments though. It's hard to know what she saw. Some similarity in simple comments could be accidental. But if it's long strings of identical comments..

    Most of what I read at Slashdot doesn't seem to care if it's true or not. If IBM really did steal code, doesn't that mean anything? Or is it OK to steal as long as the people you steal for are happy - is this some Robin Hood thing?

    Before you get pissed at me:

    Look, I don't like this at all. I think this can do serious damage to both Linux and Unix and that the only people who win here are the immoral scum who run Microsoft. But if it really is theft, the fact that a great big stinking mess follows is not a reason to ignore it.

    The fallout from this lawsuit could destroy my business. It could quite literally change my whole life, and not for the better. I have a lot to lose, and the prospects are rather frightening. But that doesn't change morality: if it IS theft, then whatever has to happen has to happen, and if it destroys me, well, that's life, right?

    I'm still hoping that this is going to blow over fairly harmlessly. Of course I'm also hoping to win the lottery next week, right?

    --
    -- Tony Lawrence
  141. Re:Not so simple. Really. ^H ^W by AlphaSys · · Score: 1

    Busy day today, so I'll make this short.

    No, Dud, I'm not gettin' a Dell today. I have more of their kit than I care to. Set up two full racks last week. But whatever the boss wants, the boss gets. Today, I'm taking delivery of two Teradata NCR racks and meeting with a Liebert rep to get a new standalone power unit and two separate natural gas generators to hold up my facility and HVAC units.

    It's pretty amusing to watch you congratulate yourself on a your own OT pointless post.... not.

    Oh well, there's the truck. gotta go. Ta-ta.

    --
    Can I bum a sig? I left mine at the office.
  142. WTF are you talking about? by Anonymous Coward · · Score: 0

    What are you talking about? Your post just sounds like paranoid rambling.

  143. Hope IBM Crushes them by panda · · Score: 1

    I don't want IBM to buy them out. I want this to drag on until SCO runs out of money.

    IBM has more disposable cash than SCO, than Microsoft.

    Frankly, I hope they get SCO to hand over all their source code going to back to before SCO acquired UNIX. I'd love the chance to audit their code against historical Linux code.

    Five will get you ten that either SCO employees put the code in Linux as Cringley suggest or they "stole" the code from Linux. No one will know the truth of what happened unless SCO can be made to release all of their source code, even historical releases.

    I'd sign the NDA, if they'd agree to give me all their source going back, and all the time I need to look it over. I'm not working on any kernel projects, and I'm not even working on KDE any more so, why not?

    --
    Just be sure to wear the gold uniform when you beam down -- you know what happens when you wear the red one.
  144. Re:I'm sorry--- you say that US' tort system chang by 5KVGhost · · Score: 1

    Ah, so stringing together vague accusations of widespread corruption with random snippets of economic theories ripped out of context is "Insightful". I do like how you worked in the obligatory reference to Linux as the shining beacon of hope in a World Gone Mad. That sort of thing is always good for a little extra karma.

  145. Re:SCO people are not Mormons -- sources? by Anonymous Coward · · Score: 0
    No?

    http://www.mormonstoday.com/000806/B4Caldera01.sht ml

    "News about Mormons, Mormonism, and the LDS Church

    Sent on Mormon-News: 04Aug00

    Caldera Expands By Acquiring SCO Division "

  146. You mean by MickLinux · · Score: 1

    That the anonymous mudslinging didn't have support, but the post it was slinging mud at did?

    Okay.

    Suggestion, though: go ahead and read the links. They're actually quite interesting. And no, they were not random snippets of economic theories ripped out of context.

    The first group (harvard) is data and analysis. It is prepared for the UN, but it is actually a quite valuable compilation.

    The other group *is* economic theory, but they've typically been right ahead of time. It's pretty good work they do.

    That said, I *could* be wrong. I don't claim divine inspiration for this. I rather came up with a scenario that I consdier to be more likely than other scenarios, in a pleurality fashion. Only time will tell, though.

    And no, I didn't point to Linux as the shining beacon of hope etc, etc, etc. I rather said "get it while you can, if you want it, because Linux' shining beacon of hope in justice may not come through." I expect there will be plenty who want it. Quite frankly, I didn't point to any shining beacon of hope in a world gone mad -- but if you want one, try www.worldchallenge.org . That's the best I can suggest for you -- start there.

    Can I ask, though, where exactly you are invested that this hit such a sore spot for you? And I don't mean necessarily economically invested, as in M$ stock, SCO stock, or whatnot. I mean, where are you invested, possibly psychologically or personally, that it hit such a sore spot?

    --
    Correct Horse Battery Staple: 72 bits of entropy. Enter "Correct H" into google. When it generates the phrase, that's
  147. Re:Not so simple. Really. ^H ^W sugarbitch by Anonymous Coward · · Score: 0

    Oh man, you really like /. to live vicariously. You aren't doing anything of this. This is all lies. You act like you are some sort of manager, but in reality and by your own admission, you are an IT plebian, most likely helpdesk, and some PHB's beck and call.

    You put machines in a rack. OH MY GOD, You are so uber to me now, be still my beating heart. Luckily, where I work, the IT gophers do that.

    And your story about the Leiberts and the HVAC is such a crock, I'm laughing. You went to some NOC's online brochure and started chugging out this trash. You know, if anyone had the money and the need for the kind of infrastructure you are hinting at, I feel bad for the share and equity holders of that company: They have a moron like you even taking delivery. Taking delivery: Translation, you get to drag the skid into place and mount the shit while the real McCoy does the brain work. You are such a freakin plebe. Hehehehe. This is great watching your digital janitor ass wave his digital janitor mop all over the place.

    HAHAHHAHA.

    And then saying there is the truck, gotta go. Whaaaahahahah. More holes in your bullshit than Lorraine cheese.

    Summation for this last bullshit: WHAT A FUCKING LOSER THAT MISTER TUFF STUFF HAS TO PROVE TO SLASHDOT HE IS IN PROXIMITY OF SERIOUS IRON.

    Hahahhaa.

    He can "take delivery" (read: physically move) of big iron but he cant figure out ^W hahahahha.

  148. AC -- Let's take it outside by AlphaSys · · Score: 1

    OK, nobody here wants to listen to us swap insults and beat our chests. But I'll do my best to accomodate your need you spew bile and recieve feedback for it. I have replied to your comment with a jornal entry. Against my better judgement, I have even enabled comments on it.

    Knock yourself out.

    --
    Can I bum a sig? I left mine at the office.
    1. Re:AC -- Let's take it outside by Anonymous Coward · · Score: 0

      OK, nobody here wants to listen to us swap insults and beat our chests. But I'll do my best to accomodate[sic] your need you spew bile and recieve[sic] feedback for it. I have replied to your comment with a jornal[sic] entry. Against my better judgement[sic], I have even enabled comments on it.
      Knock yourself out.


      For such a worldly, well studied right hand man to the CEO, you certainly spell wonderfully. I checked out about half your entry. It is such crap I didn't finish it. Your fantasies are amazing. Just let me say this: Your ability to embellish is impressive. Liars of your caliber take a better trained eye to spot. Your ability to be emphatic or halfway emotional about something means that the lies are constructed from partial truths. You can thus convince yourself that you are indignant, angry. You would have to be on of those two to put the time you put into this. Despite your bad spelling and other errors of that nature, you do spend time doing this. This for me is a vitriolic stream directed at you because your propagate lies and you are the type of people that I don't want to be associated with. Anyone who listens to you is a victim.

      You are a sad liar. If you go back and look at your posts, I can deconstruct your lie with your own words. Since you don't matter I'm not going to do this, but, it is simple. Just about every one of your statements of fact can be debunked with your own words. My mental scratchpad is full of things you have said which make all or your fantasy about being CEO's boy bitch hilarious. The details are precious. You think by providing a serious of minutia that only someone willing to provide such details is not a liar.

      I like the terminology you use. You aren't one to be reading technical publications, EE Times or Microprocessor Report. I know hardware guys when I see them. Not you. Nor are you a DBA, not a programmer, nor a technical officer or someone who knows much about anything. You aren't technical, but you aren't management. What you are is a jack of all trades, master of none, and you read Ziff Davis crap and read whitepapers and basically, you talk a lot of shit about stuff you really have no idea about. Amusing. A digital janitor suck up with big fantasies.

      And your motivations for taking things offline to the Journal is clear, because you have debunked yourself in the past you are afraid someone else will pick up on your lies.

      I stopped reading your journal here " but it is still entertaining." Your crap just gets really boring.

      I know the perfect job for you. A reported at the New York Times.