Slashdot Mirror


SCO Claims IBM/SGI Licenses are Revokable

shadow099 writes "SCO claims in an open letter writen by Blake Stowell, Director Public Relations SCO, that the Unix licenses to IBM and SGI can be revoked. " This is just the latest volley in the ongoing circus. It keeps getting funnier!

378 comments

  1. Somebody PLEASE put a bullet hole by Anonymous Coward · · Score: 0, Funny

    in Darl McBride's head. I understand mob rule is teh sucks, but in this case, it's justified. He is insane.

    1. Re:Somebody PLEASE put a bullet hole by Anonymous Coward · · Score: 0

      No, we don't want to kill him. That would just be tasteless. We need to do what I've been saying all along. Take that money that IBM and SGI will be spending on legal defenses and hire a couple of brutes to beat the hell out of him. The use the remainder to buy off the judge and jury.

      That way it will serve as an example to the rest of the dumb fucks out there.

  2. It all started when by ShatteredDream · · Score: 1, Funny

    Clinton got away with "it depends on what the meaning of is, is......."

    1. Re:It all started when by Anonymous Coward · · Score: 0

      How odd. I thought it started with "I am not a crook" or "I forgot".

    2. Re:It all started when by Guppy06 · · Score: 1

      I'm not sure which is worse: A presiden't that doesn't understand "is," or a Congress that doesn't understand "shall make no law."

    3. Re:It all started when by thaylin · · Score: 1

      how about if ATT&T did not transfer the contacts (it is a long shot). Also notice how they did not bring up IBM's agreement.

      --
      When you cant win, ad hominem.
    4. Re:It all started when by Anonymous Coward · · Score: 0
    5. Re:It all started when by Anonymous Coward · · Score: 0

      Let's see. Clinton was impeached and he had his law license removed. I do not think you understand what the meaning of the words "got away with" is.

    6. Re:It all started when by Jeremiah+Cornelius · · Score: 1
      Nixon: "I am not a crook"

      Reagan: "I don't recall"

      Kissinger is refeshingly blunt: "The illegal we do immediately. The unconstitutional takes a little longer."

      --
      "Flyin' in just a sweet place,
      Never been known to fail..."
  3. Can we drop this? by Anonymous Coward · · Score: 0, Insightful

    Do we have to hear about every time SCO takes a shit? I really don't care about the 4 weekly articles about them that says the same shit and then the posts that say the same shit. There has to be more interesting news articles to read about and discuss than SCO.

    1. Re:Can we drop this? by Anonymous Coward · · Score: 0

      No doubt. NEWS FLASH! SCO IS RUN BY IDIOTS! I mean, wake me when it's over. Until then, shut the fuck up already.

    2. Re:Can we drop this? by hermancarl · · Score: 1

      Remember System Enhancements Associates (SEA). As I remember they took public domain code for the then quite popular and advanced *.arc library package and then sued the recognized original author into financial ruin. It traumatized me and, from what I remember, the then incipient open source community. Later came AT&T's corporate (not the creators of UNIX at Bell Labs) legal action against BSDI and Berkeley. Another trauma. SCO's action are the latest attempt to appropriate the work of others (it does not matter if from Linus Torvalds, IBM, or SGI) via perversions (IMHO) of the legal system. What is at risk is the painfully constructed safeguards(BSD and GNU licences inter alia) truly dedicated and creative people have used to protect their output for the common good. We can not help but be distracted from more productive work. And, this distraction and the diversion of resources to utter waste is the real price society is paying.

      --
      HermanCarl
    3. Re:Can we drop this? by LC+Gundo · · Score: 1

      Yes, can't we just blackhole everything that emanates from Utah? It wouldn't hurt if Utah was physically cordoned-off either. Sure, it might inconvenience some people--Utah being so near to the United Sates and all--but I don't think this is an unreasonable action to take. After all, Utah is the source of mostly awful things: Rosanne, The Osmonds, all that horrid salt, and now SCO.

      --
      I'm time traveling, right now
    4. Re:Can we drop this? by ebbomega · · Score: 1

      Because God forbid you filter so that Caldera topics don't come up on your front page.

      There are those of us who are genuinely intrigued by this whole debacle. I'm personally already signed up for the SCO Roadshow, and I find every little bit of information useful here.

      So if you don't want to hear about SCO, just don't read the articles. I'm certain there are enough articles kicking around slashdot that you don't absolutely need to read every single SCO-related one.

      --
      Karma: Non-Heinous
    5. Re:Can we drop this? by Anonymous Coward · · Score: 0

      Do we have to hear whining from people who can't figure out Slashdot filters every time a SCO story is commented on?

    6. Re:Can we drop this? by squiggleslash · · Score: 1

      SEA was the original author. They sued PKWare, authors of PKARK, who allegedly took the original SEA ARC binaries and distributed modified versions of them. The result, interestingly, was SEA became persona-non-grata on the BBSes, Phil Katz rewrote his compressor to come up with PK-ZIP, and in turn cooperated with a public effort to create a free ZIP (InfoZIP, comes with most Linux distributions.)

      --
      You are not alone. This is not normal. None of this is normal.
    7. Re:Can we drop this? by Anonymous Coward · · Score: 0

      This article isn't under caldera, it's under Linux Business. Did you ever consider that maybe that is what I was trying to get at?

    8. Re:Can we drop this? by Anonymous Coward · · Score: 0

      Physically cordon off Utah?

      Funny, I was about to say the same thing about California... Asshole...

    9. Re:Can we drop this? by Anonymous Coward · · Score: 0

      Phil Katz...dead in a sea of garbage. Man, talk about seriously messed up.

    10. Re:Can we drop this? by Anonymous Coward · · Score: 0

      There is. All you have to do is click on the appropriate headline. There are plenty of them at numerous news sources.

      So! If SCO news is so bad why are you reading about SCO?

    11. Re:Can we drop this? by hermancarl · · Score: 1

      Thanks for remembering the name Phil Katz. Is there any authorative thread to read up and to bring it into context with the SCO farce. I admit having never researched it and having gotten my info via disjointed BBS postings. It was definitely before general public access to the Internet. Without much hope I will try the search engines on Phil Katz and SEA. It is this potential for fruitful interaction that makes Slashdot valuable and way compensates for the many inane postings.

      --
      HermanCarl
    12. Re:Can we drop this? by riffer · · Score: 1
      Phil Katz did not alter SEA's binaries, though they claimed he did. He just wrote better programs to manipulate the .ARC format (i.e. faster, which was very critical in the 286/386 days). There was some dispute over whether he'd copied parts of their source code, though SEA distributed the source freely.

      SEA found themselves utterly and totally alienated by the BBS community, especially when they started throwing around shit like "We've trademarked the .ARC extension" and saying anyone writing ANY program that manipulated the .ARC format in ANY way owed them money. SEA insisted the file format was copyrighted.

      Phil went on to develop a new, better compression file format (Our loyal friend this many years, ZIP). Not simply different compression but the file structure itself was more robust then .ARC, with deliberate room for future additions. And of course Phil went out of his way to make the format of ZIP archives widely and freely available and anyone could make ZIP-compatible programs without owing him anything.

      Remember PKZIP 0.91? BBS sysops the world over rapidly switched to that beta from SEA's ARC format/programs and never looked back. ARC died a quick and silent death... SEA did not, unfortunately.

      Here's the full story...

      The computing community the world over lost a good friend when Phil passed away. :(

      --
      In the darkness of future past, The magician longs to see. One chants between two worlds, "Fire, walk with me!"
    13. Re:Can we drop this? by ebbomega · · Score: 1

      Uh....

      Smoke crack much?

      It's under Caldera.

      Regardless of whether or not the one they show on the FRONT page is Caldera, it's still a Caldera article. Go ahead. look up. Look wayyyyy up. Now what do you see? OH! A Caldera symbol? Dear God No!

      If you had Caldera blocked, this whole troll thread would have been avoided. What a pretty concept.

      --
      Karma: Non-Heinous
  4. Is it just me by Sir+Haxalot · · Score: 1

    Irrevocable? Hmmmmmmmmmmmm.
    Is it just me that things the 'Hmmmmmmmmmmmm' is very unprofessional?

    --
    I have over 70 freaks, do you?
    1. Re:Is it just me by Anonymous Coward · · Score: 0

      Yes.

    2. Re:Is it just me by Anonymous Coward · · Score: 0

      Is it just me that things the 'Hmmmmmmmmmmmm' is very unprofessional?

      Is it just me that thinks that 'things' is not a verb?

    3. Re:Is it just me by Anonymous Coward · · Score: 0

      Maybe they should change it to...

      Can we survive as a company? Hmmmmmmmmmmm.

    4. Re:Is it just me by El · · Score: 3, Funny

      Just picture Dr. Evil putting his pinky to his mouth and saying it: "Irrevocable? Hmmmmmmmmmmmmm." See, it fits perfectly, doesn't it?

      --

      "Freedom means freedom for everybody" -- Dick Cheney

    5. Re:Is it just me by Anonymous Coward · · Score: 0

      Sir Haxalot is a karma whore troll. He is currently trying to gain Karma by posting google cache links in various articles all over slashdot so he can later use his karma-enhanced account to post trolls later on without worrying about killing his karma and having the added bonus of posting at +1 or +2 while doing it. The sad thing is that when he posts links, he posts the same links that were in the article summary and violates copyright law by copying the article text verbatim. He even posts links to outdated Google Cache copies of the articles, even when the article links STILL WORK! So moderators, I ask that you review his Posting History and see that what he does is nothing more than plagarism, trolling, and blatant karma whoring.

    6. Re:Is it just me by Anonymous Coward · · Score: 0


      Actually if you look at his posting history, you'll see his whoring doesn't accomplish the goal. His karma/post ratio stinks like McBride's soiled Friday night panties.

    7. Re:Is it just me by crmartin · · Score: 0, Flamebait

      Oh, just shut the fuck up.

    8. Re:Is it just me by Anonymous Coward · · Score: 0

      So the guy has a sense of humor, do you mind? SCO may think in ways most of us cannot follow (but then, so do most americans as far as many europeans are concerned :) But that doesn't mean the dude can't make a joke or write something informal, especially in an email!

    9. Re:Is it just me by Anonymous Coward · · Score: 0

      Nothing's informal when the law is involved. It's stupid emails like that one that sink companies. It astounds me that they're actually responding to anything... I would expect them to clam up, they're on the verge of a legal decision that will decide the fate of the company (essentially... if the judge allows discovery to go through, then the jig is pretty much up and world+dog will set the hounds on them) and this guys cracking jokes on a major online publication about his legal opponents. SirHaxalot was right, it is very unprofessional.

    10. Re:Is it just me by Anonymous Coward · · Score: 0

      Looks like a fake letter. As dumb as SCO is they would not be stupid enough to write a letter so retarded.

    11. Re:Is it just me by Anonymous Coward · · Score: 0

      This is really quite funny. You have Sir Haxalot replying to every single posting he makes anonymously claiming the original posting is a troll. The question I have to ask is why?

    12. Re:Is it just me by t_bonee · · Score: 1

      That and picture Darl, as Dr Evil of course, when they up the ante against IBM going, "3 BILLION Dollars. MmmHaahaha!"

    13. Re:Is it just me by Anonymous Coward · · Score: 0
      Hey, it's the "Sir Haxalot is a karma whore troll" troll! I love you man!

      I'm the "Hey it's the Sir Haxalot is a karma whore troll troll troll"! Whee!

  5. Slow news day? by Faluzeer · · Score: 1

    This was first published on Friday...

    1. Re:Slow news day? by TopShelf · · Score: 1

      Sometimes, though, the Mysterious Future is a couple days away...

      --
      Stop by my site where I write about ERP systems & more
  6. Except... by Chicane-UK · · Score: 1

    It keeps getting funnier! ..its just not funny any more. Its downright frustrating, and whilst I appreciate the coverage Slashdot is giving me (I want to see what asses SCO are making of themselves) I can't wait to see SCO screwed in court and hopefully nailed by the financial regulators over their pump & dump tactics.

    Sigh.

    --
    "Hey! Unless this is a nude love-in, get the hell off my property!!"
    1. Re:Except... by Anonymous Coward · · Score: 0

      nailed by the financial regulators over their pump & dump tactics

      I really hope the SEC does its job.

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

      financial regulators over their pump & dump tactics.

      If that was going to happen, it would have started by now. It will not. This is another MS, Qwest, and Enron. Pay us and we will look the other way.

    3. Re:Except... by lowmagnet · · Score: 2, Insightful

      Yes, just like how they caught Enron, WorldCOM and Comcast before it was too late. They are a hindsight organization, if ever there was one.

      --
      Heute die Welt, morgen das Sonnensystem!
    4. Re:Except... by sg_oneill · · Score: 1

      Actually I want to first see the shareholders in sco screwed over first. *THEY* are the evil bastards who are encouraging these slimes.

      --
      Excuse the Unicode crap in my posts. That's an apostrophe, and slashdot is busted.
    5. Re:Except... by AllUsernamesAreGone · · Score: 1

      No, hopefully they'll get blown off the face of the earth in a radioactive dustcloud after Darl and chums have been slowly and viciously tortured to the point of jibbering insanity (although it might be hard to tell when this has happened). Ah, a man can dream....

    6. Re:Except... by lowmagnet · · Score: 1

      Not a bad idea, except it will have an effect felt all over the tech market and may hurt other investors.

      --
      Heute die Welt, morgen das Sonnensystem!
    7. Re:Except... by Lectrik · · Score: 1
      after Darl and chums have been slowly and viciously tortured to the point of jibbering insanity (although it might be hard to tell when this has happened).


      I don't think we've quite perfected the torture techniques required to make a person more sane.

      Then again if anyone has a spare time machine my squad of samurai banana troopers can get a head start.
      --
      --- As to make my comment seem, by comparison, more intelegent... doodie doodie doodie poop poop poop!
  7. NO! you've said the word we cannot hear! by LinuxThis · · Score: 0

    not IS! you wouldnt get very far in life not saying IS.

    1. Re:NO! you've said the word we cannot hear! by Paleomacus · · Score: 1

      True. However the meaning of 'is' can be ambiguous.

    2. Re:NO! you've said the word we cannot hear! by grub · · Score: 0, Offtopic


      It's a reference to Monty Python and the Holy Grail.. Don't think too hard about it.

      --
      Trolling is a art,
    3. Re:NO! you've said the word we cannot hear! by Lobo93 · · Score: 1

      Yeah... ;)

      But if you feel a bit nihilistic or generally frustrated with the limitations of your language: this would represent the answer.

      --
      "The only clear view is from atop the mountain of our dead selves." - Peter Carroll
    4. Re:NO! you've said the word we cannot hear! by ddimas · · Score: 1
      The E-Prime examples appear to be loaded. Not only do they appear longer than the Standard English, they in fact contain more information. The E-Prime syntax does not clarify matters, it simply leads to clumsy circumloqutions.

      If you really want to try thinking differently (and more logicaly), try Latin or Greek.

  8. So? by DarkHazard · · Score: 1

    So? What will happen once their licenses are revoked? SCO will shout at them and tell them to pay up for a new license. This is laughable. The SCO has no chance of getting them to renew their licenses! Its just a desperate last hope for a desperate company.

    1. Re:So? by Captain+Goatse · · Score: 0

      If they do not renew their licenses, what are they going to use instead? GNU/Linux?

      Good luck trying to replace SCO/Unix with GNU/Linux in all of the world without any problems.

      I can already see the headlines: "IBM controlled by hackers."

    2. Re:So? by MoonFog · · Score: 1

      The SCO has no chance of getting them to renew their licenses! Its just a desperate last hope for a desperate company.
      They still get attention they want. I've seen this "desperate last breath of a dying company" about SCO for months now. Lot of people shaking their heads going "they will soon be gone", but SCO is still here, unfortunately.

    3. Re:So? by The+Analog+Kid · · Score: 1

      SCO already did, and IBM told them to shove it. However I find it very funny in the fact that if SCO wins, the money won't last forever. Whose going to buy a Unix license when your threatened that your license will be revoked. There only going after commercial Linux users. So what they are going to bill much of Hollywood, that's not going to go over well.

    4. Re:So? by gl4ss · · Score: 1

      companies(size of sco) don't die in a day or two, not even in a month or two(ok, if they're dotbombs maybe then).

      they could very well be a dying company for a year or two to come.

      --
      world was created 5 seconds before this post as it is.
  9. SCO is a PR nightmare. by Anonymous Coward · · Score: 0

    The only way that any company will do well these days is to have a good rapport with developers. SCO is offending everyone. Let's just say they win (hypothetical, not realistic), they will still go under due to all of the bad publicity.

  10. interesting 2 months notice by shaitand · · Score: 1

    first of all, that quote pertains to AT&T, second of all sco gave 1 week notice, not two months.

    1. Re:interesting 2 months notice by cperciva · · Score: 0

      Two months is the amount of time which they are required to allow for IBM/SGI/whomever to correct violations of the license. SCO gave them that time.

    2. Re:interesting 2 months notice by Haeleth · · Score: 2, Insightful

      > SCO gave them that time.

      Really? I thought they were required to give them two months from when they told them what the violations WERE, not from when they claimed that violations EXISTED.

    3. Re:interesting 2 months notice by rgmoore · · Score: 4, Insightful

      SCO did not give them that time. They didn't spell out exactly what the breach was, much less what specific remedies would allow SGI to cure it. The contract requires SCO to specify those things before they can take action. That's the purpose of the waiting period- to give the licensee time to cure his breach and avoid losing his license. The clock can't start until SCO does its part, and by failing to detail the alleged wrongdoing on SGI's (or IBM's) part they've failed to abide by their side of the contract.

      --

      There's no point in questioning authority if you aren't going to listen to the answers.

    4. Re:interesting 2 months notice by Anonymous Coward · · Score: 0

      Not quite. SCO's argument is that the release of XFS etc constituted a contract violation, and that there was essentially nothing that SGI/IBM could do to remedy the breach (which is true, because the code is now "open source").

      But it really doesn't matter because even if SCO had specified exactly what IBM/SGI had to do to cure it, IBM/SGI would have told them to fuck off and the thing ends up in front of a judge no matter what.

      The current Press Release war is really just a sideshow and has no real bearing on the UNIX Contract case. It doesn't really matter what SCO says -- they want to revoke System V licences and they've known from day 1 that they are going to have to get a judge to agree.

    5. Re:interesting 2 months notice by Anonymous Coward · · Score: 0

      Yes, but they forgot to tell them with specificity how the license was being violated. Therefore, no notice was given. SCO is up a creek without a paddle.

  11. The obvious comments... by Arker · · Score: 5, Insightful

    I'll get a few obvious observations out of the way.

    First, they love to cite that original contract, but they don't talk about the addendums. There's a reason for that.

    Secondly, even by that contract unamended, they would still have to actually specify what the supposed violations are before they could start the clock running so far as notice. They've steadfastly refused to do this, proving that they're acting in bad faith.

    Third, just because they claim something is a violation doesn't make it so. If they really thought they had violations here, they'd be in a hurry to get to court, but instead they've been stalling.

    So, in conclusion, more hot air from a guy that's known for it.

    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
    1. Re:The obvious comments... by YU+Nicks+NE+Way · · Score: 2, Insightful

      I don't think that any of these three claims is correct.

      First, the only addenda I've seen are in the IBM-ATTIS contract. This is not an action against IBM, but against SGI. The IBM addenda may change the outcome for AIX, but have absolutely no impact on Irix. More, the AIX issues are clouded by the question of Sequent's contract: it does not contain the extensions of rights clauses in the IBM addenda. If the Sequent-ATTIS contract is held to be binding on IBM for those items which were developed using Sequent's expertise, then the terms of the IBM-ATTIS addendum are irrelevant.

      Second, we know that SCO did, in fact, start the clock against SGI some months ago -- SGI's last SEC filing demonstrated that.

      And, third: no, there is no reason at all the SCO would ever be eager to get into court. Just because you're right doesn't mean you'll win. Look at Microsoft and Eolas. Microsoft is "right", but Eolas won anyway. Will that be reversed? Possibly, but how much is the doubt worth?

      SCO's best strategy is to convince one company that they've got a claim and that the company is in violation of that claim. If they can do that without going to court, then they are golden: if any entity which they sued caves, then SCO can move against companies like Red Hat and SuSE, and against the Australian Competition Commission.

    2. Re:The obvious comments... by darkov · · Score: 1

      SCO's best strategy is to convince one company that they've got a claim and that the company is in violation of that claim. If they can do that without going to court, then they are golden: if any entity which they sued caves, then SCO can move against companies like Red Hat and SuSE, and against the Australian Competition Commission.

      So all SCO has to do is convince IBM to hand over $3Bil with no proof. Gotcha. If SCO manage to do that I'll buy a Linux license. I don't see how one party agreeing to anything effects any other party though. Nothing is proven.

      And how are they going to move against the ACCC? They haven't even issued a ruling of any sort, or even said they're in a position to. Even if they did, they couldn't be sued for it. They may be able to take court action to seek a ruling be overturned.

    3. Re:The obvious comments... by Arker · · Score: 2, Insightful

      First, the only addenda I've seen are in the IBM-ATTIS contract. This is not an action against IBM, but against SGI.

      Actually there are apparently actions against both, with the IBM suit being the biggest. The article was explicitly talking about both of them. So the IBM addenda are definately relevent there.

      Also, although I haven't seen it either, SGI claims they have a similar addendum.

      More, the AIX issues are clouded by the question of Sequent's contract: it does not contain the extensions of rights clauses in the IBM addenda. If the Sequent-ATTIS contract is held to be binding on IBM for those items which were developed using Sequent's expertise, then the terms of the IBM-ATTIS addendum are irrelevant.

      Possibly. I'm sure IBMs lawyers have gone over the relevant documents thoroughly, however, in fact I know they did so long before Caldera decided to rebrand themselves as SCO.

      Even if SCO prevails in court on that one issue, they're going to get their butts handed to them on so many others it could only be a pyric victory.

      Second, we know that SCO did, in fact, start the clock against SGI some months ago -- SGI's last SEC filing demonstrated that.

      They said they did. That doesn't mean they actually did so, in a legally enforceable way. If they can't or won't detail the alleged breach in such a way that SGI could know what to do to rectify it, and/or if the supposed breach is not an actual breach, then it means nothing.

      And, third: no, there is no reason at all the SCO would ever be eager to get into court. Just because you're right doesn't mean you'll win. Look at Microsoft and Eolas. Microsoft is "right", but Eolas won anyway. Will that be reversed? Possibly, but how much is the doubt worth?

      Actually, I think this example makes my point. Under the law as it stands, Eolas was right and that is indeed why they won against an opponent that was in a far better position to wage a legal battle. Eolas didn't dick around with delaying tactics, they got into court and got their ruling. I don't happen to think that the law as it stands in this case is sensible or good, but that's how it is.

      SCO claims this is a pretty straightforward case of breach of contract with IBM and SCO (although they keep making contradictory statements on the periphery) and if that were the case it would indeed be the smart business decision to do everything possible to get this in front of a court ASAP. IBM can pay the lawyers indefinately, but SCO cannot. If SCO had a case, they would be trying to get this heard as quickly as possible, and IBM would be the one scurrying around and delaying things interminably.

      SCO's best strategy is to convince one company that they've got a claim and that the company is in violation of that claim. If they can do that without going to court, then they are golden: if any entity which they sued caves, then SCO can move against companies like Red Hat and SuSE, and against the Australian Competition Commission.

      Nonsense. Getting someone to cave wouldn't affect the legal issues, it wouldn't set a precedent, it certainly wouldn't have any affect on the Aussies. At best, it would mean an infusion of cash.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    4. Re:The obvious comments... by sg_oneill · · Score: 1

      Dude, SCO might say theyve started that clock, but it hasnt started till they tell them the breach. *NO* court would accept that.

      SGI has remedied the *MINOR* breaches it previously had, and is free. Its own analysis proved that.

      Also its vital to remember that SCO are lying about alot of this. I'd wager that the primary reason they are stalling, is because perjury can land folk in jail.

      --
      Excuse the Unicode crap in my posts. That's an apostrophe, and slashdot is busted.
    5. Re:The obvious comments... by DotNetGuru · · Score: 1

      SGI has remedied the *MINOR* breaches it previously had, and is free. Its own analysis proved that.

      They gave the code to the entire world. Can I still go to kernel.org and get an old kernel with the code? I suspect the answer is yes, and if it isn't, I suspect the code is floating around somewhere still. How do you remedy that?

    6. Re:The obvious comments... by Arker · · Score: 1

      They gave the code to the entire world. Can I still go to kernel.org and get an old kernel with the code? I suspect the answer is yes, and if it isn't, I suspect the code is floating around somewhere still. How do you remedy that?

      Last I checked you can get it from SCOs site too. The code in question is, at the very least available under a BSD style license, and is almost certainly public domain anyway. So there is no copyright issue that needs to be remedied and never was - only a contract issue. That contractual issue was remedied.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    7. Re:The obvious comments... by Znork · · Score: 1

      "SGI has remedied the *MINOR* breaches it previously had, and is free. Its own analysis proved that."

      Well, according to the usual definition of copyright they would be. However, SCO isnt using the same definition of derivative works as the rest of us. Remember, they're claiming that everything like XFS or JFS or RCU that has been developed to be able to run on something based on SCO's intellectual property is by extension the property of SCO too.

      So if you rewrite the law and live in an imaginary world then SCO is correct and IBM and SGI arent in the clear.

    8. Re:The obvious comments... by Anonymous Coward · · Score: 0

      Not only do they have to specify the violation, but they have to provide the opportunity to remedy it. ...unless within the period of such notice all breaches specified therein shall have been remedied;

      I would argue that "specify" means give the lines of code, and then SGI can revoke that contribution to Linux kernel, thereby remedying it?

    9. Re:The obvious comments... by rgmoore · · Score: 1

      They're not claiming that XFS, JFS, RCU, etc. are their property. They're claiming that those things are contractually protected, i.e. that the developers promised not to reveal them. That's a technical point, but if you look at all of SCO's press releases and public statements, they never actually say that they own those things. They say that they're protected by SCO's IP rights, which include patent, copyright, trademark, trade secret, and contract rights. I happen to think that their argument is nonsense, since the side agreements pretty clearly spell out the right of licensees to recycle code that they developed themselves, but at least SCO is not completely out to lunch on the issue.

      --

      There's no point in questioning authority if you aren't going to listen to the answers.

    10. Re:The obvious comments... by Usagi_yo · · Score: 1
      That and they don't talk about remedies of contract breach.

      There is a certain amount of goodwill in contracts. I'm sure that notifying somebody in a timely manner that they are in violation is one of them, along with remedies enumerated in the contract.

      Not like patent infrindgement, where it is common to let the other guy get up and running and making money before you sue the rug out from underthem.

      Worthwhile to note that all of SCO's claim of Patent and IP and copyright infrindgement does not address the contract license of Unix by IBM from AT&T and thus SCO. The are inevitably separate issues.

    11. Re:The obvious comments... by Anonymous Coward · · Score: 0

      Now lets say they do get the contract 'revoked'. What can SGI and IBM do? Im sure there is something like 'whats yours is yours and whats mine is mine' in that contract somewhere. Wouldnt that just instantly make everything that ibm and sgi put in there up for grabs in such a way that ibm and sgi could do what they want with it? Also Im sure they both contributed parts that are key to the way SCO unix works. Such as patent swaps, code swaps, and the like. SCO could find themselves without any legal wiggle room if they revoke that contract.

      What I am saying is that SCO could be in a world of pain if they DO revoke. So lets hope they do!

      Also im sure if IBM wasnt trying to get rid of their flavor of unix im sure they are now. SGI is fairly screwed it was their main product!

      Course what I just said is wild speculation. As without us seeing the contracts they can say what they want. No matter if it is right or wrong. We just have to take their word for it.

    12. Re:The obvious comments... by Anonymous Coward · · Score: 0

      i love it when people post with authority and posture as if they KNOW...REALLY AND TRULY KNOW.

      you are outta here buddy.

    13. Re:The obvious comments... by YU+Nicks+NE+Way · · Score: 1

      I haven't seen any citations from SGI claiming a similar irrevocable transfer of rights in an addendum, and I've been watching. Can you point me to one? I agree with you that the existence or non-existence of such an addendum is critical.

      As to Sequent: Sequent + SGI == control of ccNUMA. Control of ccNUMA == stranglehold on the kernel scheduler for Linux 2.4.x and later.

      SCO didn't say that they had started the process to revoke SGI's license. *SGI* said that they'd been notified by SCO that the process had been started.

      And as to wanting to be in front of a court: you do realize that Microsoft's attorneys thought they had an unbeatable hand in the Viola browser? Nevertheless, Microsoft fought as hard as it could to stay out of court, precisely because a jury is totally random. SCO has a warchest of $30+ Million from MS and Sun, even assuming that they don't have any hidden licensees. Thirty M$ is plenty of money to support carrying this on to the bitter end.

      As to the Aussies: getting someone to cave and acknowledge fault is enough to provide prima facie evidence that there's merit to the case. You're right that there would be no precedential value from a legal standpoint, but SCO doesn't care about a precedent in Germany or Australia. It only cares about not having its US case derailed.

    14. Re:The obvious comments... by Anonymous Coward · · Score: 0

      > The IBM addenda may change the outcome for AIX, but have absolutely no impact on Irix.

      Maybe, maybe not. The addenda uses the term "understanding". Yes, it was drawn by AT&T in regards to the contract it drew with IBM.

      But, SGI signed a nearly identical main contract. Since contracts are only as good as the "understanding" they represent between the parties, the IBM side letter could be used to demonstrate AT&T's side of that understanding in regards to their contractual wording, in the general sense (and for all parties). These fixings of understanding are some of the kinds of very sorts of documents you hope to uncover in discovery.

      The question will be, how much of that letter was "understanding" and how much was "addendum". AT&T agreed changes to IBM's contract cannot help SGI, but any explanation by AT&T of an existing term, shared by both IBM and SGI, may.

  12. FUCKING MORON SCO EXECS by Tuxinatorium · · Score: 0, Flamebait

    Send them 10,000 copies of Goatse.cx in their email! Better yet just hack their computers and make them display nothing but goatse all day long!

    1. Re:FUCKING MORON SCO EXECS by Anonymous Coward · · Score: 1, Funny

      Ok, Jonny, run along and play while big people talk. Jackass.

    2. Re:FUCKING MORON SCO EXECS by El · · Score: 1, Funny

      Don't mud wrestle with a pig. Not only will you lose, but the pig will enjoy it! Oh, and that's spelt "Mormon", not "moron"... and counter to popular opinion, there IS a difference!

      --

      "Freedom means freedom for everybody" -- Dick Cheney

    3. Re:FUCKING MORON SCO EXECS by Anonymous Coward · · Score: 0

      Don't you think they have enough assholes as it is?

    4. Re:FUCKING MORON SCO EXECS by IM6100 · · Score: 1

      I'm starting to wonder if these 'SCO' topic posts are intended to draw off the ignorant potty-mouths and detract them from the important and interesting discussion threads.

      Seems to be working.

      --
      A Good Intro to NetBS
    5. Re:FUCKING MORON SCO EXECS by krumms · · Score: 3, Funny

      No, no, hackers would be better served in downloading this top secret "Linux" operating system of theirs that they seem to love so much and distributing it to thousands of people across the globe! Maybe even for free?

      How cool would that be?

    6. Re:FUCKING MORON SCO EXECS by Epistax · · Score: 1

      What use is that? I'm sure it's all their homepages.

    7. Re:FUCKING MORON SCO EXECS by Tuxinatorium · · Score: 0

      Ha Ha so original I still like the idea of toymenting those evil motherfuckers in whatever way you can. Putting a trojan on their computer to make it always display goatse or tubgirl on top of everything would definitely work nicely.

  13. Well... by DrEldarion · · Score: 1

    Well, he does seem to have a point, whether it's the "right" thing to do or not. If there's no place in the license that says it's irrevocable (and, quite to the contrary, actually says that it is revocable), then they shouldn't assume that it is.

    How he goes about saying it, though, is quite assholish, and I don't agree with the whole situation, but it seems that the contract does allow them to revoke the licensing.

    -- Dr. Eldarion --

    1. Re:Well... by Anonymous Coward · · Score: 0

      The point I think, when IBM and SGI say their licenses are irrevocable, is that they're perpetual. IE barring anything else, SCO can't just say "your license runs out next year, you have to pay for more". The license is paid for , and can't be just changed and more $$ asked for.

      However, it's revocable if SCO prove the license terms have been broken. They haven't done this yet.

    2. Re:Well... by jhunsake · · Score: 1

      when IBM and SGI say their licenses are irrevocable, is that they're perpetual

      IBM and SGI aren't stupid, they wouldn't say one thing when they meant another.

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

      Of course they would. It's a marketing game until it goes to court.

    4. Re:Well... by jhunsake · · Score: 1

      You think pre-trial public statements can't be introduced in court?

    5. Re:Well... by Dashing+Leech · · Score: 1

      Actually, if you read the IBM contract addendum, it does actually say it is irrevocable. That's not an interpretation, it actually uses the word "irrevocable". (Check out some of the other posts, it's copied here somewhere.) As for SGI, it's not clear if they have such an addendum.

    6. Re:Well... by bovinewasteproduct · · Score: 1

      Actually, if you read the IBM contract addendum, it does actually say it is irrevocable. Yes it does. It just means that the license does not have to be paid for. Here is the full clause from earlier:

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

      Now look at the bold text, what DOES the Related Agreements say? That is the question. That addendum relates soley to the royalties. If the Related Agreements say they can issue UNIX licenses except on days of the full moon, it means just that. They can issue licenses everyday with no royalties, EXCEPT on days of the full moon. If they do so anyway, they are in violation.

      BWP

    7. Re:Well... by Anonymous Coward · · Score: 0

      It doesn't really matter what IBM says -- they're still selling UNIX, so obviously they aren't acting like their licence can be revoked.

      Therefore any press release is 100% PR.

  14. In response: Open letter to SCO by r00zky · · Score: 1

    Dear SCO management:
    SCO, as a company, is revokable.

    Yours truly
    - r00zky

    --
    I'm a chainsmokin' alcoholic sociopath, so-ci-o-path
    1. Re:In response: Open letter to SCO by xanadu-xtroot.com · · Score: 1

      I know you're making a joke and all, but, you're not that far off. It's the stock holders that can vote for the company to go belly up. They're not...

      --
      I'm not a prophet or a stone-age man,
      I'm just a mortal with potential of a super man.
  15. Specifications by marcelC · · Score: 1

    The excerpt from the contract states that ther is a 2 month term to act on the "Breaches specified" in the "Written notice" which should precede it.

    As far as I'm aware SCO has yet to disclose all of the code. So what does this add to our circus parade?

  16. Two months to fix? by Anonymous Coward · · Score: 0
    He's a fucking moron.

    Even his own example says that IBM would have two months to fix any problems.

    But SCO won't tell anyone what they think the problems are.

    "Your honor, IBM is breaking our contract, but we can't tell anyone how"...

    Yeah, that'll work.

  17. Spelling correction... by Anonymous Coward · · Score: 0

    It's "revocable", not "revokable".

    1. Re:Spelling correction... by I+Like+Swords!!! · · Score: 1

      Actually, both spellings are acceptable. It's like grey/gray. They both mean the same thing.

      --
      .unsigged
    2. Re:Spelling correction... by crmartin · · Score: 1

      Both are actually considered correct.

    3. Re:Spelling correction... by BetterThanCaesar · · Score: 1

      Wait... exchanging C for K? Obviously it must mean that SCO will be claiming that they own KDE as well, now.

      --
      "Stop failing the Turing test!" -- Dilbert
  18. Things that make you go hmm by mazarin5 · · Score: 1

    You know, it does make me think that. Hmmmmmmmmmmmm..... (how many ellipsis are appropriate for that many 'm's anyways?)

    --
    Fnord.
  19. Darl: So what if I'm losing the game?? by Esion+Modnar · · Score: 1
    It's my bat, it's my ball, and unless you play by my rules, I'm going home, and taking them with me!

    It's not fair, waaaaaahhhhh! (Red-faced temper tantrum)

    --

    They say the first thing to go is your penis. Well, it's either that or your brain. I forget which...
    1. Re:Darl: So what if I'm losing the game?? by Anonymous Coward · · Score: 0

      Thing is the Linux Community brought the bat and the ball and we have Big Blue to back it up. But SCO is still whining about how the bat and ball is still really theirs.

    2. Re:Darl: So what if I'm losing the game?? by Esion+Modnar · · Score: 1

      Exactamundo. It was never his bat and ball to begin with, but he's hoping people won't notice.

      --

      They say the first thing to go is your penis. Well, it's either that or your brain. I forget which...
  20. Funny? No, this is just sad by bunhed · · Score: 2, Funny

    So the husband is at the door, with the suitcase packed and the and a one way plane ticket in his hand and the wife is screaming she's going to divorce him. Pathetic really.

  21. Are they really losing it? by Core-Dump · · Score: 1

    It looks like the CO's (or lawyers) at SCO are really losing it, revoke a licence?? and compare it with a drivers licence??
    When you drive drunk you are a danger to everyone around you, therefore the drivers licence can be revoked.

    When you (atleast that is what sco claims) use some code in Linux you can't revoke a licence, you can only sue there assess off (or try to)
    I still havn't seen any proof from SCO that source from SCO is/was used in Linux, so i would say, first show the proof THEN revoke/sue the company's.

    But noooo.... sco wants everybody to be afraid and start shaking in there chairs because they have a Linux home-firewall-router.

    Whats up next?? Sco charging Superman because he has a "S" on his chest, and that "S" is part of "SCO"

    When will this soap end??

    --
    What would you do without a monitor? Sit and look stupid behind a keyboard and a mouse
    1. Re:Are they really losing it? by treat · · Score: 1
      When you drive drunk you are a danger to everyone around you, therefore the drivers licence can be revoked.

      Actually, the legal basis in the US is somewhat different. Driving is a privilege, not a right. A privilege granted by the government that can be taken away for any reason at any time without due process, a right to appeal, or anything like that.

      This is why your license can be taken away not only for driving drunk, but for other offenses that have nothing to do with driving. This is also why the DMV can require your social securitiy number (in violation of federal law), your fingerprint, and outrageous fees to get a license.

    2. Re:Are they really losing it? by SmallFurryCreature · · Score: 1
      Yup a tiny little detail they seem to have missed is that it is the cops who revoke your license throught the justice system. Not the original license giver, the department of motor vehicles.

      At least that is the case in holland not sure about the US but from tv it sounds the same :P

      --

      MMO Quests are like orgasms:

      You may solo them, I prefer them in a group.

    3. Re:Are they really losing it? by Anonymous Coward · · Score: 0

      .. while the company lawyers are reading this...

      Hmm... Superman has an "S" on his chest... hey, we've got a *great* idea! ...

    4. Re:Are they really losing it? by Fulcrum+of+Evil · · Score: 1

      Driving is a privilege, not a right.

      Well, driving on public roads is a privelege. If I'm a rich idiot and lose my license, I can still race, provided that the sanctioning body allows it. Barring that, I could drive around on my 2 mile driveway and send my butler out to fill the tank.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
  22. An open letter by Anonymous Coward · · Score: 2, Funny

    C

    1. Re:An open letter by Tellarin · · Score: 1

      the C letter is not an open letter, it is part of The S"C"O Group, and as such belongs to SCO (according to their lawyers?)

      you better be careful or you could get sued by them for infriging their IP

    2. Re:An open letter by JamesP · · Score: 1

      Remember that SCO owns the rights to C so you better have sent the check for $699

      --
      how long until /. fixes commenting on Chrome?
    3. Re:An open letter by Anonymous Coward · · Score: 0

      And according to SCO, since the alphabet contains the letter 'C', the alphabet is a derivative work, and belongs to SCO. SCO are currently considering their legal options ;)

    4. Re:An open letter by Anonymous Coward · · Score: 0

      "C is for crackhead, that's good enough for me! Oh, C is for crackhead, that's good enough for SCO!"

    5. Re:An open letter by Anonymous Coward · · Score: 0

      Legacy letters like "C" should not be used in this day and age. You can easily use modern letters such as "J2EE" and "EJB" instead. These provide much needed demand for the hard drive storage, CPU manufacturing and ISP bandwidth industries, which the letter "C" sadly does not provide.

    6. Re:An open letter by Anonymous Coward · · Score: 0

      You know the lameness filter is broken when...

  23. I'm no lawyer ... by nuance9 · · Score: 1

    But since when does one paragraph out of a no doubt lengthy contract definitively prove anything?

    --
    what?
  24. Wait a minute... by Anonymous Coward · · Score: 0

    Does this mean that weed is now "tocable?"

  25. only FUD by OMG · · Score: 2

    Blake Stowell (SCO) writes:
    "You can't take code based on a license you signed, change it a little and then give it away for free (as in the case of XFS from SGI)." (emphasis mine)

    Firstly SGI has a good point in saying it is allowed to make XFS open source. And secondly SCO execs should learn that GPL licencing is not about "free beer". Probably a court will need to tell them soon what the meanings of the GPL licence are.

    1. Re:only FUD by Anonymous Coward · · Score: 0

      Let me get this straight: you take crappy 30 year old System V code, change it a LITTLE, and get XFS out of it? Right. Good point, Stowell. When you guys are done, the Albertsons down the street needs a few more baggers. Just give them a call. I will vouch for your.

    2. Re:only FUD by Eric+MB+Lard+MD · · Score: 1
      SCO are on very weak ground complaining about XFS.

      Groklaw had a reference to Caldera advertising how wonderful their Linux was, with features such as XFS.

      Nor can SCO claim they were unaware that XFS was in Linux. Surely no Unix company can have missed the announcements in 1999 when SGI said they would be releasing this. SCO are a bit late getting round to complaining about this + in the meanwhile Caldera has been busy profiting from XFS (and actively advertising the fact).

      If their beef with SGI is related to XFS they haven't got a let to stand on.

    3. Re:only FUD by FirstOne · · Score: 1
      "SCO are on very weak ground complaining about XFS."

      If SCO revokes SGI's unix license, I suspect SCO will loose all rights to use XFS and any derivatives. After all, if SGI's unix license gave them rights to use XFS, then revoking it would automatically undo those rights! I can see SGI coming back and nailing SCO with a huge counterclaim.

    4. Re:only FUD by Anonymous Coward · · Score: 0

      First of all, SCO doesn't currently use XFS. Second, the GPL licence doesn't contain any provisions that would allow SGI to prevent SCO in particular from using it.

  26. "Irrevokable" by cperciva · · Score: 4, Interesting

    IBM/SGI's licenses are "fully paid up and irrevokable". That's specific legal language which means "SCO can't demand more licensing fees, and it can't pull the license on a whim". That in no way restricts the ability of SCO to revoke a license which has already been invalidated by IBM or SGI violating its terms.

    I'm not saying that IBM or SGI has violated the terms of their UNIX licenses; but if they have, that "fully paid up and irrevokable" language is irrelevant in this case.

    1. Re:"Irrevokable" by rgmoore · · Score: 1
      I'm not saying that IBM or SGI has violated the terms of their UNIX licenses; but if they have, that "fully paid up and irrevokable" language is irrelevant in this case.

      That's not necessarily true. Somebody pointed out that this is one area where the driver's license analogy is fairly apt. Not all violations against ones driver's license result in revocation as a penalty. Most don't, in fact. Instead they're punishable by something less, like a fine. Similarly, revocation is not SCO's only option in this case. They might be compensated by a financial penalty, and injunction against a violating company transfering any more code to open source, or something like that. Imposing some lesser penalty would be reasonable particularly if, as SGI claims, the violation is trivial. SGI has admitted that they are in technical violation of the license, having released a couple of hundred lines of SVR4 code. Revoking their license over such a trivial breach would be grossly disproportionate.

      --

      There's no point in questioning authority if you aren't going to listen to the answers.

    2. Re:"Irrevokable" by jjo · · Score: 3, Insightful

      SGI has in no way adimiited a breach of its license agreement. It has identified about 200 lines of code SVR4 code that very likely has already released to the public. In an adundance of caution, SGI has excised that code from its Linux distributions.

      I really don't know where this idea of "SGI admitting fault" got started, but I can guess.

    3. Re:"Irrevokable" by rgmoore · · Score: 0
      That in no way restricts the ability of SCO to revoke a license which has already been invalidated by IBM or SGI violating its terms.

      In the IBM license, for instance, this is explicitly spelled out. Right after the bit about the license being irrevocable, perpetual, and fully paid up, it says:

      Notwithstanding the above, the irrevocable nature of the above rights will in no way be construed to limit Novell's or SCO's rights to enjoin or otherwise prohibit IBM from violating any and all of Novell's or SCO's rights under this Ammendment X, the Related Agreements, or under general patent, copyright, or trademark law.

      It seems pretty clear from that sentence that SCO does have the right to revoke IBM's license for cause. Of course the best evidence is that they have failed to follow the terms under which such revocation would take place- in particular by failing to spell out IBM's alleged breach- but they have the right to do so.

      --

      There's no point in questioning authority if you aren't going to listen to the answers.

    4. Re:"Irrevokable" by minkwe · · Score: 1

      Sorry You missed the point. Where does it say revocable there? It says SCO can prevent violation by IBM. It doesn't say by revocation. There are lots of ways to prevent violation other than by revocation.

      You guys are playing into SCO's game here!!!!! Be careful what you say.

      --
      "Fighting terrorists with millitary might is like killing a mosquitor on your Dad's forehead with a rifle."
    5. Re:"Irrevokable" by Lulu+of+the+Lotus-Ea · · Score: 1

      'cperciva's analysis is wrong. Stipulating the unlikely fact that IBM/SGI DID violate some term of the license, that gives SCO action to enjoin the VIOLATION... pointedly, NOT to revoke the original rights. Under the stipulation, SCO would also merit recovery of resultant damages. But there's just no way it can touch the underlying licensing rights, no matter what.

    6. Re:"Irrevokable" by Arker · · Score: 2, Interesting

      Notwithstanding the above, the irrevocable nature of the above rights will in no way be construed to limit Novell's or SCO's rights to enjoin or otherwise prohibit IBM from violating any and all of Novell's or SCO's rights under this Ammendment X, the Related Agreements, or under general patent, copyright, or trademark law.

      It seems pretty clear from that sentence that SCO does have the right to revoke IBM's license for cause. Of course the best evidence is that they have failed to follow the terms under which such revocation would take place- in particular by failing to spell out IBM's alleged breach- but they have the right to do so.

      Not at all. What you quote doesn't say anything of the kind. It says they may enjoin IBM from violating the contract. It doesn't say they can terminate the contract. There is a huge difference.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    7. Re:"Irrevokable" by Dhalka226 · · Score: 1

      Revoking their license over such a trivial breach would be grossly disproportionate.

      <p>Legally speaking, if a contract is violated it can be null-and-void. It may very well be disproportionate--isn't this whole thing rather ridiculous?--but it would be within their legal rights.

      <p>I personally don't care for the driver's license analogy. The way government has to deal with citizens is always far different from how citizens have to deal with one another. Federal employees are near impossible to fire, for instance, even for incompetence; the same isn't true in the private sector.

  27. And why... by moody834 · · Score: 1

    ...is this considered a post-worthy piece of news?Surely McBride will say countless other stupid things today. Must we have a post for those, too? We surely have enough reason at this point to have a weekly roundup of SCORN (SCO References/News)?

    Seriously, save screen real estate for more interesting things (things with a point, dammit!), like, "Georgy Russell: What will she do now?"

    --
    /* * We did not get what we need .. we cannot sleep ..
  28. Circus maybe, but... by Anonymous Coward · · Score: 0

    I'm just glad this article wasn't another "So and so's government considers using Linux". Holy christ... lately it seems like Slashdot's main focus is to tell us about every single time someone even thinks about using Linux (of course, as we've often witnessed they often end up sticking with Windows in the end). HOW ABOUT SOME REAL NEWS!!

  29. yawn. by ErikZ · · Score: 1

    Then do it already SCO. It might actually help you with your court case.

    What? It's a completely bogus claim? Then why are you annoucing it? Who are you trying to impress?

    I wonder if their lawyers are working by the hour, and need to do stuff like this to charge billable hours.

    --
    Democrats or Republicans. They are both taking us to the same place and they are not afraid of us anymore.
    1. Re:yawn. by Anonymous Coward · · Score: 0

      They actually HAVE *revoked* IBM's AIX license. Not that IBM cares. It also extended protection to all its customers concerning AIX.

  30. Silly question maybe... by scsirob · · Score: 1

    Does the current SCO product include a file system as good as XFS? If so, what is it's name and how does it perform?

    If not, why do they claim this to be SCO property but don't make their customers benefit from it? Just curious...

    --
    To Terminate, or not to Terminate, that's the question - SCSIROB
    1. Re:Silly question maybe... by DemENtoR · · Score: 1

      Who is your daddy, and what does he do? Sorry, just had to do it.

  31. he said, she said.. by grub · · Score: 1


    Everybody in this charade are sending open letters to one another. It's as if SCO is trying to scare other companies into settling whereas the companies SCO are suing are trying to decide this in the court of public opinion.

    They should all just shit or get off the pot. SCO; show some code. IBM/SGI/et all; show what you've found. This fiasco has gone on long enough.

    --
    Trolling is a art,
  32. Re:Bah by E_elven · · Score: 1

    It's not off-topic. Inappropriate and criminal, sure :)

    --
    Marxist evolution is just N generations away!
  33. Can someone revoke his license to good health? by speedfreak_5 · · Score: 1

    Seriously, this guy needs to be taken down a couple of notches. Blake and his ilk come around talking smack about how they own code in linux, and they don't show $#!t. I'm tired of this crap. They need to either put up and show some code or the cocky bastards should be sent into fedreal PMITA prison.

    --
    Why yes I am paranoid! Thanks for asking!
  34. Re:Grammar, OT by E_elven · · Score: 1

    3.

    --
    Marxist evolution is just N generations away!
  35. "specifying any such breach" by Ghazgkull · · Score: 1

    "...AT&T may ... at any time terminate all the rights granted by it hereunder by not less than two(2) months written notice to LICENSEE specifying any such breach , unless within the period of such notice all breaches specified therein shall have been remedied;"

    Doesn't this say that SCO has to inform the licensee of the violation and give them a chance to remedy the problem within two months?

    1. Re:"specifying any such breach" by Anonymous Coward · · Score: 0

      Absofuckinfluteley if they dont show they cannot revoke

  36. XFS and copies by jbolden · · Score: 2, Interesting

    The letter's main point seems incorrect. IBM and SGI have a license to distribute the quote sounds like it is from a license to use. Given SCO's previous honesty I'd question whether he is quoting the correct license.

    One side point was even worse, "You can't take code based on a license you signed, change it a little and then give it away for free (as in the case of XFS from SGI)."

    How is XFS based on a license that SGI signed? AT&T and SCO for that matter have nothing similar.

  37. Why ?? by Crashmarik · · Score: 1

    I have read over SGI's licenses and I've found no place where it says it is irrevocable. Why would anyone in their right mind sign over a license to anyone that was not revocable?

    You have to ask is Mr. Stowell being disingenuous or is he meerly extremely naieve. The answer is very simple when the license was issued it was a condition of the contract and was a deal breaker. Most hardware vendors particularly in the timeframe of the dealings had much larger capital outlays on their proprietary products than software companies. It would have been foolish to allow a software vendor unilaterally and retroactively terminate their business.

    I have to ask once again what Mr. Stowell is smoking when he talks about no one issuing an irrevocable license. Seeing, as all of the programmers that work for SCO have in effect done this with their work product.

  38. Do not become complacent by skroz · · Score: 0, Troll

    While SCO's antics are often confusing and sometimes amusing, this is not a matter that should be taken lightly. Too many people are taking this lightly, and I have a fear that at the end of the day, the OSS community is going to be caught bent over with their pants down looking back on a grinning SCO.

    The court system in the US is less than predictable, and often makes ludicrous decisions in favor of seemingly frivolous lawsuits (see RJR Reynolds, McDonalds, and KB Toys.) Linux CAN lose, and defeat in just this one battle would be disasterous.

    And what does SCO have to lose? They admit that they only have a few hundred customers, and it would be no big loss to the world for the company to disappear. SCO execs have already made their money, so defeat wouldn't harm them much, even if it meant the end of their corporation.

    Linux, on the other hand, would be utterly destroyed. Invalidation of the GPL would mean that existing GPL'd software could be incorporated into commercial code without restriction or credit to the original author. Commercial vendors would be at SCO's mercy, and many would be forced to fold. Non-commercial linux developers without funds to support a lawsuit would be forced to fold. Linux, at least in the US, would be dead.

    Be amused, but those that are in a position to make a difference need to take this VERY seriously, or risk a serious blow to Linux' very existance.

    --
    -- Minds are like parachutes... they work best when open.
    1. Re:Do not become complacent by pknoll · · Score: 2, Informative
      Invalidation of the GPL would mean that existing GPL'd software could be incorporated into commercial code without restriction or credit to the original author.

      No, it wouldn't. If the GPL is found to be invalid, then normal copyright law applies. Nothing written under it could be distributed, extended, etc. without express permission from the copyright holder. The GPL doesn't protect code; copyright law does that. The GPL grants freedoms where normal copyright law would restrict them.

    2. Re:Do not become complacent by Anonymous Coward · · Score: 0

      "Invalidation of the GPL would mean that existing GPL'd software could be incorporated into commercial code without restriction or credit to the original author"

      Not true. No license, no right to use it. Only if the restrictions are absurd, the restrictions can be set aside. That is not the case

    3. Re:Do not become complacent by cyt0plas · · Score: 2, Insightful

      Invalidation of the GPL would mean that existing GPL'd software could be incorporated into commercial code without restriction or credit to the original author.

      Actually, no, it wouldn't. In that case, standard copyright law would apply, which says that you can't distribute it, modified or not, without a valid license from the author. Copyright authors could still distribute their software under the GPL (it's a copyright license, so the copyright holder can't violate it). GPL v3 comes out (with a fix for whatever made GPL2 get thrown out), they release their software under GPL3, and all is good.

      If needs be, Linux could be re-released under GPLv3 from a country which still accepts the licensing agreement. Then work continues as normal.

      --
      Contact Me (got tired of viruses emailing me).
    4. Re:Do not become complacent by ekuns · · Score: 1

      Invalidation of the GPL would mean that existing GPL'd software could be incorporated into commercial code without restriction or credit to the original author.

      No, that's totally wrong. If the GPL is invalidated, the code will not go into the public domain. If an existing license fails, the code goes back to the copyright of each individual author. This means legally no-one could use the code without getting permission from each and every author. If the GPL is invalidated for a given chunk of code, it would become unlicensed, but not public domain. And not unlicensable unless that was a specific condition of the court.

      And that would be if the GPL were totally invalidated by this court case, which would stun me. At most, I could see a court decide that the GPL license has been invalidated on a given chunk of kernel code due to abuses. Because, yes, courts periodically make decisions that do not seem to be based in the facts. If the GPL license were invalidated for the kernel due to these alleged abuses, I really doubt that would have any legal consequence to any other GPL licensed product.

      As an aside, as others have pointed out, SCO quotes the latest revised version of a license when it is in SCO's favor, but quotes the original AT&T licenses (ignoring later revisions) when that license is in SCO's favor. In a court of law, such logic would not hold up.

      And as many lawyers have pointed out, SCO's lawyers would be punished for Barratry if they brought their accusations about the GPL into a court of law. That is, the argument that the GPL is invalid because it tries to superceed the copyright act. That's just silly. If the GPL superceeds the copyright act, then most licenses do so also.

      I agree with your statement that we should not be complacent. That just because their arguments are specious -- doesn't mean the court will find against them.

    5. Re:Do not become complacent by chrisv · · Score: 1

      ... Invalidation of the GPL would mean that existing GPL'd software could be incorporated into commercial code without restriction or credit to the original author. ...

      Actually, at that point, it would become governed by copyright law, which is more restrictive (without permission by the owner of the copyright, anyway). So crediting the author is irrelevant, because there is still a copyright violation if the code is stuck into commercial code, or distributed, or much of anything really.

      As well, commercial vendors wouldn't necessarily be under the mercy of SCO (because, even IF SCO is found to own certain bits of Linux kernel source code, they don't own the kernel in it's entirety), rather they would be under the mercy of the copyright holders of all of the code in question that they distribute (which could very easily be hundreds of thousands of individuals). I would imagine that most of the other predictions you've made are correct, though.

      --

      Dogma: Dead (mostly because your Karma ran it over)

    6. Re:Do not become complacent by mark-t · · Score: 1
      The GPL grants freedoms where normal copyright law would restrict them.
      You were right on the money until you said this.

      Tell me... where does copyright law restrict freedom?

      Or are you referring to the "You need explicit permission from the coypright holder before you are allowed to distribute" phrase?

      Because if so... you may be interested to know that restriction still applies to GPL'd software. Any copyrighted work that can be legally protected by copyright law may also have, at the copyright holder's discretion, any reasonable terms or conditions that must be met in order to have legally recognized permission to redistribute. More often than not, these terms are something to the effect of "must obtain written permission from the publisher" or what have you. In GPL'd software, the terms are simply that one agree to the terms of the license.

      So the GPL doesn't grant anything that normal copyright law doesn't grant. It only grants an easier path to obtain permission to redistribute than most copyrighted works happen to.

      This is why the GPL can't easily be invalidated. If it were, the foundations of copyright itself would be virtually destroyed, as copyright holders would no longer be able to freely dictate terms for obtaining permission to redistribute. All copyright holders everywhere would essentially no longer be in control of their own work, and copyright would become legally meaningless.

    7. Re:Do not become complacent by ShinmaWa · · Score: 5, Insightful

      The court system in the US is less than predictable, and often makes ludicrous decisions in favor of seemingly frivolous lawsuits (see RJR Reynolds, McDonalds, and KB Toys.)

      I quote this from Snopes, which I found in my research before posting this reply. Barbara stated it better than I could have: Only rarely do ridiculous lawsuits result in windfalls for the plaintiff; these cases are almost always either thrown out or the judgement goes for the defendant. Some celebrated "outrageous" suits wherein judgement went for the plaintiff prove upon closer examination to be far less "outrageous" than originally presented in the media. (For example, the "woman scalded by hot coffee" suit, which at first blush looked like the height of frivolity proved to be a perfectly legitimate action taken against a corporation that knew, thanks to a string of similar scaldings it had quietly been paying off, that its coffee was not just hot, but dangerously hot. The Association of Trial Lawyers of America provides an excellent description of this case).

      Linux CAN lose, and defeat in just this one battle would be disasterous.

      Remember, IBM is being sued, not "Linux". Linux is a product, not a company nor an organization, and IBM is not a Linux vendor. If SCO won in its case against IBM, there would be a chilling effect on Linux to be sure, but I have a hard time seeing it as "disasterous". In the event that IBM loses, it would have to pay damages to SCO and... that's it. SCO would be barred from suing Linux vendors or users because that would be "double dipping". SCO would have been awarded damages from IBM already and therefore relieved of its harm. Linux would be fixed based on discovery and court records and life would go on. Granted, it would be an indelible mark on the OS and wide-scale adoption would be hampered, but I don't think it would be disasterous.

      Linux, on the other hand, would be utterly destroyed.

      I highly doubt it. There's simply too much money invested. Do you honestly think that the hundreds of companies, including goliaths like IBM who has invested billions into Linux, are going to just throw up their hands and say "oh well, we give up"? Of course not! Within WEEKS (yes, WEEKS -- not months nor years) Linux, like a phoenix, would be reborn from its ashes. There's just too much force behind it.

      Invalidation of the GPL would mean that existing GPL'd software could be incorporated into commercial code without restriction or credit to the original author.

      This is very incorrect. First of all, SCO hasn't brought the GPL into the lawsuit, only IBM did in its countersuit. In the very unlikely scenario that the GPL is "invalidated" for some reason, the software doesn't become public domain for Pete's sake!! That's just silly and wrong. The GPL only grants rights, it does not take them away. If the GPL is invalidated, then the GPL'ed software would have no license at all, and people would not be legally allowed do anything at all with it, other than perhaps use it... and I'm not even sure about that.

      However, most GPL'ed software says that the license is something along the lines of "version 2 or whatever is the latest version". If "version 2" of the GPL is invalidated, there would soon be a "version 3" that solved whatever grounds "version 2" was invalidated on that would be applied to GPL'ed software.

      --
      The /. Effect: Thousands of users simultaneously accessing a site to not read its content.
    8. Re:Do not become complacent by spitzak · · Score: 1
      So the GPL doesn't grant anything that normal copyright law doesn't grant. It only grants an easier path to obtain permission to redistribute than
      most copyrighted works happen to.


      The GPL does "grant" permission to redistribute and spells out exactly how you can. You don not have to "obtain" permission, so this certainly is a grant of a freedom that normal copyright does not have.

      Even a copyright that says "you can copy this if you send me your first-born" is a grant of freedom, since in normal copyright you cannot copy even if you do send your first-born.

      If you have a piece of GPL code, you can still do everything you can with copyright, for instance you can still ask the original author for permission to copy the work (in case you want to copy it in ways that are not granted by the GPL).

      I think the reason so many are confused about the GPL is that for 99% of the users it has no effect (since they are not intending to copy and redistribute the programs). There is also the fact that receiving any large block of legalese usually means somehow that you are getting screwed. And also for the modern person, almost any piece of source code they have ever seen has been public domain, leading them to the conclusion that this is the natural state for visible source code and thus to the conclusion that the GPL is some kind of restriction (while those same people would think a GPL on a printed book would be a grant, since the natural state for a printed book is that you are not allowed to copy it). Oddly enough these same people who complain about the GPL's "restrictions" don't see any problem with the fact that they cannot copy closed source compiled binaries, and would not even complain if they recieved a copy of linux that was missing the source. But somehow the existence of source code that they can read but cannot copy is somehow a huge restriction on their freedom, while the absence of that source code at all is ok.

    9. Re:Do not become complacent by mark-t · · Score: 1
      The GPL does "grant" permission to redistribute and spells out exactly how you can. You don not have to "obtain" permission, so this certainly is a grant of a freedom that normal copyright does not have.
      Actually, you *DO* have to obtain permission to redistribute even with GPL'd work. It just so happens that all you have to do to obtain this permission in the case of a GPL'd work is agree with the terms of the license. Just because it doesn't "sound" as official as getting written permission directly from an authorized source, doesn't mean that it isn't still a process of obtaining legally recognizable permission.
    10. Re:Do not become complacent by Prior+Restraint · · Score: 1

      However, most GPL'ed software says that the license is something along the lines of "version 2 or whatever is the latest version".

      The most notable exception to this being the Linux kernel.

    11. Re:Do not become complacent by Anonymous Coward · · Score: 0

      Yes and if a US court makes a decision that basically takes the copyrighted work of many people from around the world and gives control of it to SCO or even to one and all, the other countries of the world can pass new laws saying software cannot be copyrighted and/or patented and then where are we?

      They could even just say that in order for a software copyright to stand, the source code must be submitted in a compileable form, along with all tools necessary to compile it, to the said country's copyright office. What would this do?

      In view of Microsoft's practical monopoly, I don't think other countries would look too kindly on a US court giving control of the only possible credible rival to another US firm.

      Then again, I have been wrong on more than on occasion in the past and expect to be wrong again sometime in the future and could be wrong right now as well.

      A Nony Mouse

    12. Re:Do not become complacent by Anonymous Coward · · Score: 0
      Within WEEKS (yes, WEEKS -- not months nor years) Linux, like a phoenix, would be reborn from its ashes. There's just too much force behind it.

      Isn't that wishful thinking?

    13. Re:Do not become complacent by tgibbs · · Score: 1
      So the GPL doesn't grant anything that normal copyright law doesn't grant.

      The copyright law does not "grant" anything, except for limited fair use exceptions. It does, however, allow for the copyright owner to grant permission. The GPL is an example of permission, granted by the copyright owner. If the GPL is ruled invalid, then no permission to copy the GPL'd work exists, and people who wish to copy it will have to request new licenses from the copyright owner.

    14. Re:Do not become complacent by nagora · · Score: 1
      In the very unlikely scenario that the GPL is "invalidated" for some reason, the software doesn't become public domain for Pete's sake!! That's just silly and wrong.

      It's also what SCO are claiming.

      TWW

      --
      "Encyclopedia" is to "Wikipedia" what "Library" is to "Some people at a bus stop"
    15. Re:Do not become complacent by Alsee · · Score: 1

      Absolutely right about the GPL.

      Sorry for the following rant, but I really hate to see the concept of "fair use" twisted backwards. Such logic is all too often used to justify horrendous changes to copyright law.

      The copyright law does not "grant" anything, except for limited fair use exceptions.

      Copyright law does not grant fair use. Prior to the passage of copyright law there was no restriction on any use. Fair Use is a constraint on the extent and reach of copyright. Copyright protections do not reach into or exist in the area of fair use. In some cases these constraints on copyright exist because it would be unconstitutional for copyright law to attempt to restrict certain activities.

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
    16. Re:Do not become complacent by cduffy · · Score: 1

      However, most GPL'ed software says that the license is something along the lines of "version 2 or whatever is the latest version". If "version 2" of the GPL is invalidated, there would soon be a "version 3" that solved whatever grounds "version 2" was invalidated on that would be applied to GPL'ed software.

      Actually, there's an increasing number of Free Software developers (myself among them) who are explicitly unwilling to license our software under Version 3 of the GPL. Go read what RMS has planned for it -- basically it's intended to become much, much more incompatible with non-GPL software licenses.

    17. Re:Do not become complacent by anthonyrcalgary · · Score: 1

      I googled around, and looked on Stallman's site and the GNU site and I couldn't find it... do you have any links?

      --
      When someone might yell at me, it has to be OpenBSD.
    18. Re:Do not become complacent by GileadGreene · · Score: 1
      Guess it's time to dust off my FreeBSD CD then :-)

      Seriously though, you are way off base regarding the effects of "invalidating the GPL", as numerous other posts have pointed out. Not only that, but it's not clear that SCO's suits against IBM and SGI would in any way affect the validity of the GPL.

      This "crisis" is nowhere near as dire as you make out. Even if SCO gets exactly what they want, they will get a dead shell of an OS. The Linux userbase will migrate to a kernel not encumbered by SCO pettiness.

    19. Re:Do not become complacent by cduffy · · Score: 1

      See the bits about "closing the ASP loophole":

      http://newsforge.com/article.pl?sid=00/11/01/163 62 02

      The concern is that there will be some attempted changes to what is considered "linking" (with regard to creation of derivative works) to increase the viral nature of the GPL in cases where no actual inclusion of the GPL-covered code into the would-be derivative work is done (as where a free ASP-type interface is used by a non-free client). There is of course a legal limit with regard to what can be considered a derivative work, but RMS (or was it Bruce Perens? Not sure which) has mentioned something regarding a potential workaround for that. (Sorry, can't re-find my reference wrt that).

      Any change potentially increasing (or otherwise modifying) the viral nature of the GPL is something I'll want to review before making my software subject to it.

    20. Re:Do not become complacent by Anonymous Coward · · Score: 0

      SCO would be barred from suing Linux vendors or users because that would be "double dipping".
      I've see a lot of stupid statements on /., and this is the stupidest. If SCO wins, of course they can go after other copyright infringers. Double jeopardy applies only to criminal cases.

    21. Re:Do not become complacent by ShinmaWa · · Score: 1

      Isn't that wishful thinking?

      Maybe... but I have a lot of faith in the collective power and drive of the open source community. When properly motivated (and I would say that would be more than enough motivation), I think productive output would be amazing.

      Imagine hundreds, maybe thousands, of individual open source developers along with dozens of corporations working collectively toward one common goal: "Fix this kernel as fast as possible!"

      It would be a coordination nightmare, but the amount of output would be absolutely stunning.

      --
      The /. Effect: Thousands of users simultaneously accessing a site to not read its content.
    22. Re:Do not become complacent by Anonymous Coward · · Score: 0
      In the event that IBM loses, it would have to pay damages to SCO and... that's it. SCO would be barred from suing Linux vendors or users because that would be "double dipping".
      Standard disclaimer: IANAL Umm, how is this true? IBM does not indemnify its customers (end users or other distros) from lawsuits resulting in copyright/license violations. As such, not only is IBM accountable, but so are the people who bought it. Same thing as with the RIAA. Not only are people who rip the songs and distribute them liable for damages, but so are the people who download them. This is not the same thing as double-jeopardy (being tried for the same crime twice). This is about trying different parties for different violations, though the violations occurred in the same product. You may be able to make a claim based on stolen property law -- i.e. if you bought a stolen item in good faith that it was not stolen, you are not liable for posessing stolen property (of course, you must give it back). But I think that may be quite a stretch for copyright violations to stretch into personal property law.
    23. Re:Do not become complacent by ShinmaWa · · Score: 1

      The concept of "double jeopardy" (a criminal concept protected agaisnt by the 5th amendment) has nothing to do with "douple dipping" (a tort concept regarding severally collecting damages).

      "Douple dipping" is collecting from multiple sources for the same damages. Many jurisdictions have laws barring double dipping. In those that do not, most judges frown upon the practice and tend to summarily reject such claims.

      --
      The /. Effect: Thousands of users simultaneously accessing a site to not read its content.
    24. Re:Do not become complacent by ComputerSlicer23 · · Score: 1
      Actually, Linux as a specific instance, couldn't be re-released under the GPL v3 automatically. Read the code in the the COPYING file in the linux source code. It specifically states that it is under GPL version 2, and only version 2 unless otherwise specifically stated.

      Until they could identify all the original copyright holders, and get them to sign off on version 3 of the GPL they would unable to release the software under it. It would mean large sections of the Linux kernel (mainly drivers) would have to be re-written. As far as I know several very important things like ext2 were written by people who fell off the face of the planet. People have been looking for Remy Card for a long time, he was the original author of most of the ext2 filesystem. Maybe he turned up, but last I knew he was still MIA.

      Linus Torvalds intentionally doesn't hold all of the original copyright. He doesn't want to be seen as someone who could be co-opted into "stealing" Linux. If he held all of the original copyright. He could literally sell it to the highest bidder under any licensing agreement they want (the FSF could do the same with Emacs or GCC). Linus could sell the copyright to IBM or Microsoft for a big wad of sweaty money if he so chose under those conditions. To build trust with everyone, he decided that that everybody who wrote some retaining their copyright gave everyone a legal hold on the Linux. That build up a lot of trust. However, it is an anchor when it comes to relicening the Linux kernel.

      Mozilla had similar problems when they went to a tri-license, so clearly it can be done. However, there are still parts of Mozilla that haven't been relicensed.

      Kirby

    25. Re:Do not become complacent by ShinmaWa · · Score: 1

      You are right, "double dipping" is not the same as "double jeopardy". That's why they have different names. :)

      Double dipping is attempting to collect from multiple parties for the same damages. In many places its not allowed and most others it is seriously frowned upon as being unfair.

      This is an example of double dipping. Two people together do $500 worth of damage to my property during the same act. Double dipping is if I sue each of them severally and attempt to collect $500 worth of damages from each (for a total of $1000).

      SCO has already said that IBM's alleged infractions have caused them $1 billion in damages. If IBM pays up, they've been compensated for those damages and can not seek to be compensated again from others for those same damages. That is double dipping and would be considered "unfair" in the court of equity.

      --
      The /. Effect: Thousands of users simultaneously accessing a site to not read its content.
    26. Re:Do not become complacent by arkanes · · Score: 1
      Simply put, Stallman doesn't like the fact that a web interface doesn't fall under the GPL - for example, you can take PHP, modify it, and run a public web site with it without needing to make the source for your modified GPL available.

      Personally, I say buggers up to that. There's other licenses that require the publishing of any modiications period, use one of those if thats what you're after.

    27. Re:Do not become complacent by Anonymous Coward · · Score: 0

      As I said before, IANAL. :) It seems to me that while all actions up until a supposed verdict in favor of SCO could be found as not being able to sue the end users, all FUTURE actions after said verdict would be permissible for suing for more damages. Basically, with the verdict would come a "cease and desist". All parties that do not cease and desist would be subject to lawsuits. (After all, they are continuing to use software for which they have not obtained a proper license.)

      It also seems that the action of distributing non-licensed software and the action of using non-licensed software can be considered different actions, thus can be sued separately. I'm not sure, that seems to be a loose interpretation. I would say this would be harder to convince a court than the first one.

      BTW, thanks for your clarification of "double dipping" verses "double jeopardy". :)

    28. Re:Do not become complacent by spitzak · · Score: 1

      Since zero work or communication is needed to "obtain" the right to redistribute the source, it can be considered a gift or grant by the GPL. Another way to look at it is that somebody who has zero interest in redistributing the source still has the rights to do so. If in fact there was some "work" required to "obtain" these rights, then the person with zero interest in using these rights would not have them, right?

    29. Re:Do not become complacent by sir99 · · Score: 1
      If [Linus] held all of the original copyright [to Linux]. He could literally sell it to the highest bidder under any licensing agreement they want (the FSF could do the same with Emacs or GCC).
      The part about the FSF isn't true. The copyrights to all non-trivial contributions to GNU programs are assigned by contract to the FSF, with obligations on both parties. If the FSF closed the source to Emacs, all contributors could sue the FSF for breach of contract, since one of the conditions is that the FSF must license the program in question under GPL-like terms. I had a hard time finding a copy of this agreement (and there are apparently several variations depending on the situation), but here's one example. That said, I like the multiple-owners model of Linux better.
      --
      The ocean parts and the meteors come down
      Laid out in amber, baby.
    30. Re:Do not become complacent by jrumney · · Score: 1
      It's also what SCO are claiming.

      If you needed more more convincing that it's just silly and wrong, that should do it.

    31. Re:Do not become complacent by anthonyrcalgary · · Score: 1

      I agree...

      Authors are free to use whatever license they choose and I am free to not use their software. That said, I find the GPL hypocritical. "This is Free Software, subject to the following conditions.".

      It seems to be working, but the BSD license seems to be working too (Before anyone says BSD is dying, consider that things like Apache use a BSD-like license).

      --
      When someone might yell at me, it has to be OpenBSD.
    32. Re:Do not become complacent by fredrik70 · · Score: 1

      If the GPL would be invalidated all code would be protected by copyright (which is the reason fsf recommends you to turn over the copyright to them, since they got the resources to protect the copyright in case of violation - not really needed if your'e one of the big guys, i.e. IBM, etc). the GPL would be rewritten, all code would be placed under the new lcence and it would all be dandy again.

      --
      if (!signature) { throw std::runtime_error("No sig!"); }
    33. Re:Do not become complacent by cyt0plas · · Score: 1

      From the GPL itself:

      Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. So, if they specify a version, you could go with the new v3. If they don't specify a version, you can still go with v3. Perhaps a program could say "only v2", but I personally haven't seen one do so.

      --
      Contact Me (got tired of viruses emailing me).
    34. Re:Do not become complacent by ComputerSlicer23 · · Score: 1
      I'm going to be an ass now, you can stop reading if you'd like:

      I've read the GPL, the LGPL, and the COPYING file of the Linux source carefully before. It's pretty clear you've never bothered to read the one for Linux.

      Follow the instructions in my message. Specifically, read the message in COPYING from the linux source tree. You would then see a program that says only v2.

      From the /usr/src/linux/COPYING, second paragraph:

      Also note that the only valid version of the GPL as far as the kernel is concerned is _this_ particular version of the license (ie v2, not v2.2 or v3.x or whatever), unless explicitly otherwise stated.

      Kirby

    35. Re:Do not become complacent by pknoll · · Score: 1
      That is a better way to say it, thanks. I was indeed referring to obtaining permission.

      With the GPL, you don't need to obtain permission from the copyright holder to distribute; you simply need to agree to the terms of the license. It is more free in that way; you are assumed to have permission as long as you adhere to the conditions set forth.

    36. Re:Do not become complacent by cyt0plas · · Score: 1

      I stand corrected. It happens sometimes :)

      --
      Contact Me (got tired of viruses emailing me).
  39. Hmmm...there is one worrying thing by psicic · · Score: 4, Funny

    The piece itself is about nothing : the term irrevocable doesn't mean it can't be revoked, it usually just means it can't be revoked for no reason - i.e. there has to be a breach of the terms of the license. (That's assuming there isn't a clause somewhere that says 'This license can never be revoked.')

    There is one worrying thing, and I quote:

    {Villain fingers pussycat}

    If that's an accurate description of what Mr. Stowell was doing, shouldn't somebody call the RSPCA???

    --
    Concrete analysis...
    1. Re:Hmmm...there is one worrying thing by Anonymous Coward · · Score: 0

      I think Utah might be just a bit out of their jurisdiction. Perhaps you mean the ASPCA?

    2. Re:Hmmm...there is one worrying thing by Art+Tatum · · Score: 1

      Come on, the cats enjoy it!

  40. Am I going to have to separate you two? by cyclist1200 · · Score: 2, Funny

    SCO issued a statement today saying "Yuh huh!"

    IBM and SGI issued a joint reply stating "Nuh uh!"

  41. Well, then! by willith · · Score: 1

    I hereby claim that I have the power to revoke THE SUN!

    1. Re:Well, then! by Anonymous Coward · · Score: 0

      Shhhh, Sun is next on SCO's list... Remember Java,
      A Java runtime for Unixware means Java is a derivative according to SCO's definition.

    2. Re:Well, then! by Anonymous Coward · · Score: 0

      I hereby claim that I have the power to revoke THE SUN!

      If you aren't

      1. the man in the moon
      2. a major rain-god, or
      3. cowboyneal orbiting earth

      then I would say that you're smoking crack, sir!

    3. Re:Well, then! by Haeleth · · Score: 1

      Revoke the Sun? Please do! There are too many tabloids around anyway.

    4. Re:Well, then! by TheRaven64 · · Score: 1

      I'm afraid I'm going to have to send you a Cease and Desist. It turns out you're infringing my patent on megalomania (as licensed to SCO, Microsoft and the US Government).

      --
      I am TheRaven on Soylent News
  42. Waiting ... by NotoriousBob · · Score: 0

    I've been dreadfully waiting for this day to cash in my SCO shares. Just waiting for the cheques from IBM/RedHat.

    --

    RRS, aka The Notorious BOB
    www.notoriousbob.co.nr
  43. What'll it achieve if they do? by dacarr · · Score: 1

    SCO will say "No license for j00!" to IBM, towhich they 900 lb gorrilla will walk up to them and basically say "revoke this" in response. I fail to see what this is going to achieve on SCO's part.

    --
    This sig no verb.
    1. Re:What'll it achieve if they do? by xanadu-xtroot.com · · Score: 1

      SCO will say "No license for j00!" to IBM, towhich they 900 lb gorrilla will walk up to them and basically say "revoke this" in response. I fail to see what this is going to achieve on SCO's part.

      Well here on planet Earth, and in the US specificly, that's called a Paper Trail. McBride told IBM and SGI that their license is dead. OK, fine. IBM and SGI stand up and say "ummm... nope." So now McBride can say "Well I mentioned it to them, and gave them the proper notice about it it all, but they (points finger) didn't see it that way and went against what I said. So now, your honor, why would you listen to a couple people that fought me tooth and nail on technicalities when I gave them plenty of notice of my intentions?"

      You see? Welcome to American Court System 101. You want fries with that?

      --
      I'm not a prophet or a stone-age man,
      I'm just a mortal with potential of a super man.
    2. Re:What'll it achieve if they do? by Fulcrum+of+Evil · · Score: 1

      Well here on planet Earth, and in the US specificly, that's called a Paper Trail. McBride told IBM and SGI that their license is dead. OK, fine. IBM and SGI stand up and say "ummm... nope." So now McBride can say "Well I mentioned it to them, and gave them the proper notice about it it all, but they (points finger) didn't see it that way and went against what I said. So now, your honor, why would you listen to a couple people that fought me tooth and nail on technicalities when I gave them plenty of notice of my intentions?"

      Except that Darl never gave due notice - he has yet to specify what the infringements are or how they may be remedied, so he hasn't given any notice. Beyond that, the license is not revokable. Apparently, SCO can only 'enjoin infringement'. Also, consider that this is the same SCO that claims rights to everything associated with SysV code, such as the XFS code that SGI wrote themselves.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
  44. sigh by Anonymous Coward · · Score: 0

    The end can't come soon enough for SCO. These idiots need to produce something useful rather than trying to litigate a profit. It's just a long very slow death rattle. Hopefully a buy out or bankruptcy will come soon. These guys are ridiculous buffoon looters and everyone but them seems to know it.

  45. Need Novell approval for revocation by thegrendel · · Score: 1

    The SCO Group can revoke Unix licenses
    only with the approval of Novell.
    This is why the AIX "revocation" was invalid.
    This is why the threat to revoke SGI's
    IRIX license is nothing more than a PR ploy,
    an attempt to pump the stock price.

  46. Re:Open Source Hell by Treacle+Treatment · · Score: 1


    And your point is?

    --
    TT
  47. Hmmmmmmm by Anonymous Coward · · Score: 0

    Does the hmmmmmmm make anyone else think of a grade school argument. I can't wait for the "I know you are but what am I?" or "I'm rubber and you're glue..." lines in the next SCO letter.

  48. Specs' by synonymous · · Score: 1

    The failure of SCO to specify is advantagous in two ways, one is that anyone can still trod along and still have a two month cushion when they finally prove it, while the other is that everyone has a chance to scour the kenel and it's pieces looking with a magnifying glass for anything that could be a problem. This is merely going to open and set center stage for all the acts in the future as well expose how sedated and trained folks are to having feces pressed into the ear.

  49. last convulsions of a headless chicken by Anonymous Coward · · Score: 0

    I heve held executive positions in a few companies that went tits up and I have seen this before. My view on SCO is that it has come to examine closer the writing on the wall. I don't have to wait for the last chapter, I've read the book. Next steps -- corporate cards will lock up, medical insurance will bounce, creditors will show up at the door, all the good stuff. Why is it relevant to an IT company what a lawer says in this context or another? If you look at the product, it's not there. Why SCO? Why not BSD, Linux, SUN? No reason.

  50. By the Original by Shadow+Wrought · · Score: 4, Informative
    ...any time terminate all the rights granted by it hereunder by not less than two(2) months' written notice to LICENSEE specifying any such breach, unless within the period of such notice all breaches specified therein shall have been remedied;...

    So, by the original language, the license can only be revoked by specifying the breach. SCO has yet to specify the breach so much as point in its general direction.

    The other proviso is that if the breach is fixed (ie the infringing stuff is removed) then the license can no longer be revoked. So, if the offending code in Linux is identified and removed- there is no breach.

    Is it just me or are they no even bothering to hide their alterior agenda anymore?

    --
    If brevity is the soul of wit, then how does one explain Twitter?
    1. Re:By the Original by h00pla · · Score: 2, Insightful
      Is it just me or are they no even bothering to hide their alterior agenda anymore?

      And this agenda is: Keep SCO in the news at all costs

      --
      I've been swashdotted -- Elmer Fudd
  51. How intelligent by Anonymous Coward · · Score: 0

    Did your post really merit +1 Karma Bonus?

    What did you contribute to this discussion?

    1. Re:How intelligent by crmartin · · Score: 1

      The wisdom of age.

    2. Re:How intelligent by azzy · · Score: 2, Funny

      Mod parent's parent up. Mod parent down. Mod this up. Mod children down. And get me a beer while you're at it.

    3. Re:How intelligent by klafhat · · Score: 1

      Mod parent funny!

      --

      Tell me more, tell me more

    4. Re:How intelligent by crmartin · · Score: 1

      I'll have a coffe and two doughnuts.

  52. Back to the Unix wars by panurge · · Score: 1
    Meanwhile it is back to the Unix wars as usual, with a twist.
    • SuSE: Use our Linux, we're protected because we were part of OpenLinux along with those SCOundrels
    • HP: Use our Linux, we are protected because we have a secret condom and we promise you won't catch anything.
    • IBM: So we're being sued. Hell, $3 billion is small change. Excuse us a moment while we thump our chests and then bury these creeps in fecal pellets.
    • SUN: Linux is crap for the server anyway. But here's this really, really neat corporate desktop which just happens to be SuSE underneath, see above.
    • All together: "Mind you, don't go buying no Linux from some two cent little organisation that just might get sued to hell and back"
    I guess if you got all the marketing people from the organisations mentioned above and asked them to write an essay, "Darl McB: pain in the ass or unexpected business bonus", they'd be typing away for a long time.
    --
    Panurge has posted for the last time. Thanks for the positive moderations.
    1. Re:Back to the Unix wars by argent · · Score: 1

      BSD: We already had this lawsuit, and won, and by the way... those bits of code you showed? They're specifically covered under the settlement terms of that agreement. So everyone else is safe unless, I guess, you buy the University of California and retcon something scary out of the BSD license.

    2. Re:Back to the Unix wars by Flower · · Score: 1

      SCO: BSD didn't win. We settled out of court. And we have reason to believe that they violated the settlement agreement (editor's note - Go back and check out the interview in BYTE for the exact quote.) We'll examine that issue when we are done with the current caseload.

      --
      I don't want knowledge. I want certainty. - Law, David Bowie
    3. Re:Back to the Unix wars by argent · · Score: 1

      BSD: The TCP/IP stack in Unixware is derived from the Lachman port of the BSD stack to System V. USG used that code without attribution in violation of their agreement with the University of California. Ironically, if SCO decides to rip that code out the only credible alternative is the independently developed and GPL-ed code in Linux.

  53. YOU FORGOT THE MAGIC by Anonymous Coward · · Score: 0

    This terrible open-source shit cut off the end of my NORWAY? flood. Here is my humble attempt to make up for it:

    N O R WAY?NORW A Y ? N O R W A Y?NO R W A Y ? N ORW A Y ? N O R W A Y ? N O R W A Y ? N O R W A Y ? N O R W A Y ? N O R W A Y ?N O R WAY?NORW A Y ? N O R W A Y?NO R W A Y ? N ORW A Y ? N O R W A Y ? N O R W A Y ? N O R W A Y ? N O R W A Y ? N O R W A Y ?N O R WAY?NORW A Y ? N O R W A Y?NO R W A Y ? N ORW A Y ? N O R W A Y ? N O R W A Y ? N O R W A Y ? N O R W A Y ? N O R W A Y ?N O R WAY?NORW A Y ? N O R W A Y?NO R W A Y ? N ORW A Y ? N O R W A Y ? N O R W A Y ? N O R W A Y ? N O R W A Y ? N O R W A Y ?N O R WAY?NORW A Y ? N O R W A Y?NO R W A Y ? N ORW A Y ? N O R W A Y ? N O

    1. Re:YOU FORGOT THE MAGIC by Anonymous Coward · · Score: 0

      Gods damnit, you feeble fuckwit! You were supposed to eat the yellow pills! Now you've gone ahead and awoken the anger of thousands of norwegians which I might add, are the descendants of the berserking Vikings!

      Dude, you've really done it now...

  54. MOD PARENT UP by The+One+KEA · · Score: 1

    You are most definitely correct, sir. Just because we think we have the moral high ground in this case doesn't mean that SCO doesn't have something to go on.

    To those of you fighting this case, KEEP FIGHTING!

    --
    SCREW THE ADS! http://adblock.mozdev.org/ Proud user of teh Fox of Fire - Registered Linux User #289618
  55. MOD IT UP! by TheSHAD0W · · Score: 1

    Out of all the comments posted on this article, this is the first that includes a rebuttal.

  56. Of course a license can be revoked by Eric+Ass+Raymond · · Score: 2, Insightful
    What will happen once their licenses are revoked? SCO will shout at them and tell them to pay up for a new license.

    So what usually happens if a company keeps using licensed material after the license has been revoked? They get sued, are found guilty of using intellectual property without a proper license and punished.

    And of course licenses are revokable (unlike some people here seem to believe). Even if the license is fully paid, it can still be revoked if you are found in breach of the contract. Hell, IBM is using a similar argument against SCO's Linux.

    1. Re:Of course a license can be revoked by sg_oneill · · Score: 1

      So what usually happens if a company keeps using licensed material after the license has been revoked?

      It hasnt been revoked. Theres no basis for that. To revoke a licence you have to tell someone why, not just vague alusions of "we revoked your licence, you have to guess why".

      --
      Excuse the Unicode crap in my posts. That's an apostrophe, and slashdot is busted.
    2. Re:Of course a license can be revoked by budgenator · · Score: 2, Insightful

      The crux of the matter is SCO can revoke for cause, when the licensee is in violation of the contract.

      One point that may cause a violation is the release of code that is a derivative, of code that was placed in SVR4, such as IBM made a journalizing files system for SVR4 unix such as AIX, released the code as in distributing AIX then took that code out and made minor mods and released it in LINUX. That in my second and third hand lay knowlege of the issues would violate the contract and alow SCO to terminate IBM's SVR4 liciense. IBM will of course argue that the file system was developed indepently of the operating system and that a derivative of the file system was later modified and place in AIX, and that the filesystem that went into LINUX was again taken from the independant, pre-SVR4 sources and therefore not a unix derivative covered by the licience and contract terms.

      If the court buys SCO's version, IBM's goose is cooked, they lose their SVR4 liciense and owe SCO $3 billion; If the court buys IBM's version, SCO's goose is cooked and their assets go on auction, and their officers probably get hefty fines from the SEC and or jail time.

      SCO even if they win, lose because they've pissed away good will they might have had in the developer community, and what good is an operating system with software that was state-of-the-art circa 1980, for businesses in the 2003?

      --
      Apocalypse Cancelled, Sorry, No Ticket Refunds
    3. Re:Of course a license can be revoked by that+_evil+_gleek · · Score: 1

      Right, revoked with cause, not at whim.

      But what about this language:
      "You have to abide by the statutes of a license or it can be revoked."

      Statutes of a civil contract? No, I think the word there is terms, isn't it? ( Or, maybe clauses). "Statutes" makes one think of official, legislated law. A driver's license is given out by the State, the GOVERNMENT, it is not a contract between two parties, it's not business. How is that even applicable to this?

      He seems to be confusing criminal code and civil law. Rhetorical FUD?
      Or just cluelessness?

    4. Re:Of course a license can be revoked by Anonymous Coward · · Score: 0

      i wonder if the fact that the specific language of the license say that at&t is the onnes that can pull the license not the owners of the unnix intelectual property.

      seem to me like a minor loophole but it may have some weight because sco purchased the unix licens not the at&t department stated in the license.

    5. Re:Of course a license can be revoked by urulokion · · Score: 1
      And of course licenses are revokable (unlike some people here seem to believe). Even if the license is fully paid, it can still be revoked if you are found in breach of the contract. ...

      That would normally be the case of more normal boilerplate license agreements. Unless both parties come to an agreement to make the license irrevocable. That is what happened in the IBM case.

      SCO has even kindly posted the addendums to the IBM software agreement. It is labeled as Exhibit D on SCO web page about the case. I'll even quote the relevent paragraph.

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

      (The emphasis in the paragaph is mine) The "Consideration" section is a schedule of payments of several millions dollars.

      So it appears that the (old) SCO and IBM agreed to make IBMs rights to develop and distribute AIX irrevocable. The SCO Group has to live with the contract. No amount of sabre rattling or public whining can change it.

      If SCO miraculously wins their laysuit against IBM, they will get a number of remedies and reliefs. But revoking IBM's license isn't one of them, even if IBM gwas iving away System V and AIX source code with every system that they sold.

    6. Re:Of course a license can be revoked by fermion · · Score: 1

      And they need to specify the violation, prove the violation, and give time to remedy the violation. Prior to this there is cause to revoke the license, and speaking of revoking the license in merely a marketing ploy and unlikely to be of any legal signifince.

      --
      "She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
    7. Re:Of course a license can be revoked by Dashing+Leech · · Score: 1
      Thank you. I was looking for someone to post the actual contract clause.

      It seems just about the only way around this clause is that it depends on what "rights" are actually written in the "Related Agreements". Does anybody have a copy?

    8. Re:Of course a license can be revoked by nathanh · · Score: 1
      The crux of the matter is SCO can revoke for cause, when the licensee is in violation of the contract.

      One point that may cause a violation is the release of code that is a derivative, of code that was placed in SVR4,

      No, they cannot. The license explicitly says that the license is irrevocable. It does not say "irrevocable except for these cases where the license can be revoked". That would be silly.

      The license does say that SCO can enjoin IBM from infringing their rights. That's a different meaning to revoke. Revocation is simply one way of enjoining. But the license explicitly says that revocation is not going to happen. SCO will need to use another method to enjoin IBM. Possibilities include fines, penalties, royalties, injunctions, etc.

      But not revocation. SCO cannot revoke the license. You are playing into SCO's plot by thinking they have a point. They are fibbing. Go to Groklaw. This particular point has been beaten to death. SCO CANNOT REVOKE THE LICENSE WITH IBM.

    9. Re:Of course a license can be revoked by Crispy+Critters · · Score: 1
      "a derivative, of code that was placed in SVR4, such as IBM made a journalizing files system for SVR4 unix such as AIX, released the code as in distributing AIX then took that code out and made minor mods and released it in LINUX."

      Don't be a FUD victim. There is a specific legal definition of "derivative" with respect to copyrights. It doesn't matter whether the file system was originally written for AIX or not. For it to be a derivative, it must contain material copyrighted by SCO, in other words something taken from SCO's SysV codebase. If IBM took file system drivers from SCO's SysV code and modified it to add journaling, that would be a derivative. A journaling file system written from scratch without referring to SysV code cannot be a derivative.

    10. Re:Of course a license can be revoked by RedWizzard · · Score: 1
      If the court buys SCO's version, IBM's goose is cooked, they lose their SVR4 liciense and owe SCO $3 billion; If the court buys IBM's version, SCO's goose is cooked and their assets go on auction, and their officers probably get hefty fines from the SEC and or jail time.
      SCO has asked for $3B, but they are not guarenteed that amount even if the court finds in their favour. Unless the contract specifies some minimum amount that IBM must sell their versions of Unix for it is possible that the courts may decide that there are have been no damages inflicted. It's also possible that the courts could uphold both SCO's and IBM's complaints - SCO could win the case but still fall prey to IBM's patent violation claims.
    11. Re:Of course a license can be revoked by budgenator · · Score: 1

      SCO could win the case but still fall prey to IBM's patent violation claims.
      personaly I think this is why SCO is trying so desperatly not to show exactly what code they claim is in violation. If SCO was required to remove all code that violated an IBM patent, there might not be anything left.

      --
      Apocalypse Cancelled, Sorry, No Ticket Refunds
  57. Why does this stuff keep getting reported? by coupland · · Score: 2, Interesting

    SCO has won nothing. They have disclosed nothing. They have accomplished nothing. They keep beating their chests and making outlandish statements every time they go a couple days without being in the headlines. But we keep reporting it and acting shocked. Darl McBride and SCO are the corporate equivalent of a kid eating dog poo out of the sand box for attention. Ignore them, they will go away.

    1. Re:Why does this stuff keep getting reported? by Eric+Destiny · · Score: 0

      You must be new to Slashdot. Welcome.

      --

      "The meek shall inherit the earth, the rest of us shall go to the stars." Isaac Asimov

  58. Couple of points by Zocalo · · Score: 3, Redundant
    Firstly, this is supposedly taken from SGI's license, and does not cover any ammendments or addendums. At this level of license negotiations both parties lawyers will have a lengthy negotiation to get various terms altered and struck out before either party signs. I doubt very much that IBM's license is going to be the same somehow, and quite possibly (probably) both IBM and SGI's licenses *do* have non-revokable clauses.

    Secondly, if Blake Stowell had actually read his own contract properly he would found this bit: "...in addition to any other remedies that it may have, at any time terminate all the rights granted by it hereunder by not less than two(2) months' written notice to LICENSEE specifying any such breach, unless within the period of such notice all breaches specified therein shall have been remedied.". I particularly find the bits about "other remedies" and "breaches specified" of note. IANAL, but that implies to me that SCO is obliged to to both disclose details of what is in breach (not necessarily publically), which it hasn't done as far as I am aware, then give IBM/SGI two months to correct that breach.

    I suspect SCO's refusal to disclose any information prior to an actual trial is going to bite them in the ass somehow.

    --
    UNIX? They're not even circumcised! Savages!
  59. What happens when SCO wins? by Anonymous Coward · · Score: 0

    Slashdotters thought the DMCA was funny and unbelievable, too. Slashdotters seem to believe that the world operates on a rational basis such that they can reliably predict the outcome of cases like this based on what they think are the principles of law in the US and elsewhere. Slashdotters are naive. (Slashdotters generalize a lot.)

    Optimism gets you nowhere today. The world's too corrupt. I don't know what the outcome will be, but after the DMCA, the Patriot Act and Operation Pipe Dreams I'm not really finding this "funny". Just scary.

    1. Re:What happens when SCO wins? by Anonymous Coward · · Score: 0
      Slashdotters thought the DMCA was funny and unbelievable, too.
      Only the fucking stupid ones.
  60. Re:Grammar, OT by CableModemSniper · · Score: 1

    3 ellipses would be .........

    --
    Why not fork?
  61. MOD PARENT UP! by Anonymous Coward · · Score: 0

    Had me falling off my chair. Simple but well played.

  62. In other news... by JamesP · · Score: 1

    McBride revokes the law of gravity, claiming DMCA issues...

    "We licensed that law before, if you want to use it, please send a check for $699"

    --
    how long until /. fixes commenting on Chrome?
  63. GPL and court damage. by Cheerio+Boy · · Score: 2, Funny

    The GPL interprets court actions as damage and routes around them.

    Seriously I can't see it taking very long for the authors to re-group and patch the GPL to fix the issues.

    If this truly were to happen I'd give it about 6 months before the GPL and all the code was re-released.

    But wait! That would only happen in a properly working legal society. I forgot that this is all happening in New Berlin where the courts follow George W. Furer.

    Or at least that's what he seems to be trying to make it anyway...

    *blink*

    Why are there black SUVs on my lawn suddenly?

    --

    "Bah!" - Dogbert
  64. Looking into the future... by wozster · · Score: 1

    Which prison do you think Darl will serve his time at?

    1. Re:Looking into the future... by ekuns · · Score: 1

      Which prison do you think Darl will serve his time at?

      I would be surprised if there is any prison time for anyone at SCO or any of their lawyers. Especially with the administration in the White House at the moment, where in the post-Enron days the rules for oversight are weaker than they used to be. I would pretty much be surprised if any suits are brought against anyone at SCO, even for the pump & dump. Even for the fairly obvious Microsoft financing of this lawsuit, including Bill's wife running a company that is more or less the only entity purchasing SCO stock, and is thus the corporate entity responsible for SCO stock price being so high.

      Remember, in the US, white collar crime is almost never prosecuted. And even when it is, it's often just to make an example of someone so it looks like something is being done.

    2. Re:Looking into the future... by sg_oneill · · Score: 1

      Which prison do you think Darl will serve his time at?

      I dunno, but I somehow think his ligigous threatening won't work well against some 6' hells angel called "Bruiser" who is really keen on Darl picking up the soap.

      --
      Excuse the Unicode crap in my posts. That's an apostrophe, and slashdot is busted.
    3. Re:Looking into the future... by Anonymous Coward · · Score: 0

      Camp X-ray.

      Well, look at it this way, by the time he's finished, he's going to have pissed enough people off, wasted huge amounts of US budget and generally made life miserable for a lot of people by spreading propaganda and acting like a spoilt little fucktard. The amount of damage done to others for personal gain is pretty friggin' huge - comparable on a person to person basis to a war on terror.

      And knowning the US legal system, the war against SCO will last as long as the war against OBL et al. Where was the controversial code located? Will they ever find Darl McBride? Does he have doubles?

    4. Re:Looking into the future... by Anonymous Coward · · Score: 0

      "Remember, in the US, white collar crime is almost never prosecuted."

      It's a bit more complicated than that. If *you* tried to do some "white collar crime", *you* would probably get caught, prosecuted, sentenced to probation or sent to prison, and the whole time, everyone to whom you suggest that "white collar crime is almost never prosecuted" will meet you with a blunt lack of understanding of any such notion. They will have never heard of anyone getting away with anything, period.

      On the other hand, if someone with serious political connections gets caught doing white collar crime, they are more likely to be able to control (1) the venue in which they are prosecuted, and (2) the quality of their representation.

  65. Ammendment X by Col.+Klink+(retired) · · Score: 3, Informative
    Why would anyone in their right mind sign over a license to anyone that was not revocable?

    Namely because there are other ways of enforcing your contracts. I haven't seen all of the SGI contracts, but here is Ammentment X to the IBM contract and it clearly states IBM has an "irrevocable" and "perpetual" contract. It also says that SCO is not otherwise limited from enjoining or prohibiting IBM in other ways.

    --

    -- Don't Tase me, bro!

  66. To paraphrase Star Wars... by adrianbaugh · · Score: 1

    Princess Linus: "Help me, IBM Kenobi, you're my only hope!"

    --
    "'I pass the test,' she said. 'I will diminish, and go into the West, and remain Galadriel.'"
    - JRR Tolkien.
  67. I agree with SCO on this one.. by Anonymous Coward · · Score: 0

    If a company stole your source code, then proceeded to profit off your works, then refused to share any of the profits. Why should you continue to do business with them?

    The most logical action would be to cease any business dealings with a company until the issue with their IP theft from your company could be resolved.

    SCO is not a megacorporation like IBM, so they have to handle this situation in other ways. It's up to SCO to make the decision how to proceed with resolving their alleged IP theft. Why are there so many arrogant people with the idea in their heads that they are the ones to dictate how this company should be run?

    1. Re:I agree with SCO on this one.. by Anonymous Coward · · Score: 0

      I take it, then, that you've read more than just the SCO press releases? Also, have you read the actual license agreements in their entirety, the sale contract of the UNIX source from AT&T to Novell and Novell to SCO (as amended), the full text of the suit and countersuit (both as amended) and have an established legal practice in copyright, intellectual property, and contract law?

      Woohoo, another anonymous armchair juror sides with the crap he's been spoon-fed. Let me go and sign up for the SCO Road Show right now!

    2. Re:I agree with SCO on this one.. by Anonymous Coward · · Score: 0

      You didn't even argue any of those points. You just tried to discredit the poster because he more than likely doesn't have 'an established legal practice in copyright, intellectual property, and contract law'.

      In my world, if a company owns source code that has been ilegally used by another company to profit, then they should be compensated. No one needs to read any press releases or licenses to come to that conclusion.

      You must like the taste of shit because the linux zealots have been spoon feeding you plenty of it lately.

    3. Re:I agree with SCO on this one.. by jedidiah · · Score: 1

      In MY WORLD, you typically have to PROVE that you have been harmed before you can extract payment from your intended victims.

      Thusfar, all SCO has done is to make unsubstantiated accusations bordering on defamation and attempt to lay claim to other people's source code.

      "Unix" has a murky past which makes ANY claim of sole ownership highly dubious.

      --
      A Pirate and a Puritan look the same on a balance sheet.
  68. SCO are trying to apply a viral license technique by heironymouscoward · · Score: 1

    Having possibly learnt this trick from Microsoft. XSF is, whatever else might be defined in the original contract with AT&T, a work produced by SGI. Now, if I license a product from a company, and distribute my own works with that product, I would be quite angry if I was told those works were "derivative".

    Yet this seems to be what SCO are arguing. The original SYS V license was, it appears, so powerful that its mere presence on a disk would turn all other software into Unix source code!

    It is amusing when you consider the hate focussed onto the GPL for applying a much milder form of a "viral license", namely that true derived works are permitted under certain conditions.

    --
    Ceci n'est pas une signature
  69. It's all slashdot's fault! by Anonymous Coward · · Score: 0

    Without slashdot as news platform nobody would hear/know about SCO's crap.

    Thank you, slashdot for spreading their FUD since months now. It's NOT entertaining. It never was.

    Everyone who pays to read these SCO news first is angry.

    1. Re:It's all slashdot's fault! by Anonymous Coward · · Score: 0

      Look, SCO FUD is primarly aimed at *investors*, not unemployed/student/underpaid slashdot readers. And this stuff is gobbled up and analyzed by folks on the yahoo boards and other investor forums. The stock chart should speak for itself.

      If you want to talk about someone being trolled hard by SCO, look at those guys at "groklaw". A bunch of volunteer attorneys for IBM who eat up every SCO press release and then stroke each other's cocks whenever they find some minor inconsistancy.

    2. Re:It's all slashdot's fault! by Anonymous Coward · · Score: 0

      I make over 150k/year, you?

  70. Re:XFS and copies by argent · · Score: 1

    SCO appears to be saying that their license had some kind of hidden GPL-like "anything you ship with this is part of it" clause. At least that's the only interpretation I can come to some of their claims that this or that bit of software clearly created by IBM or SGI - and not directly based on System V - is covered as a derivitive work.

    Given the effort the FSF has gone into to craft the GPL and make that as watertight as they can, I find it hard to believe that AT&T managed to slip one in under the radar of IBM and SGI and the rest of the big boys. Especially since it seems they did it accidentally. :)

  71. How long? by Ohreally_factor · · Score: 1

    How long has "beleaguered Apple" been dying now? Has it already been 10 years?

    --
    It's not offtopic, dumbass. It's orthogonal.
    1. Re:How long? by TheCrazyFinn · · Score: 1

      Closer to 25.

      That shit started with the Apple III.

      --
      "You've got an invalid haircut" -Warren Zevon - Life'll Kill Ya
    2. Re:How long? by Anonymous Coward · · Score: 0

      So, who has been dying the longest? Apple or BSD?

    3. Re:How long? by TheCrazyFinn · · Score: 1

      Apple.

      By a couple of years. BSD's only been dying since 4.2

      --
      "You've got an invalid haircut" -Warren Zevon - Life'll Kill Ya
  72. Its not a Unix License friend by linuxislandsucks · · Score: 1

    Its nto a Unix License, friend!

    The only group that can license Unix is OpenGroup!

    Its a license to specifc unix implementation IP code only..

    --
    Don't Tread on OpenSource
    1. Re:Its not a Unix License friend by Anonymous Coward · · Score: 0

      For the sake of sane discussion, I think we can say "UNIX" when we mean "UNIX System V" implementation code, since historically they were the exact same thing.

  73. And in other news by Naito · · Score: 1

    hot air coming out of SCO contributing to global warming

  74. SCO is selling SAMBA, Is this legal? by Lost+Penguin · · Score: 0
    SAMBA for sale

    This is an outrage!

    Can we believe it?

    --
    I am the unwilling control for my Origin.
    1. Re:SCO is selling SAMBA, Is this legal? by meringuoid · · Score: 1

      SAMBA is copyrighted software. SCO does not own that copyright and AFAIK has not yet claimed to. However, the GPL allows SCO to redistribute SAMBA, and to charge for it if they like. But SCO think the GPL is invalid... This is going to be so much fun.

      --
      Real Daleks don't climb stairs - they level the building.
  75. SCO's threat to proprietary software licensing by L.+J.+Beauregard · · Score: 2, Insightful
    When SCO "revoked"[1] IBM's license, they rattled their sabers at IBM's customers who were already using AIX. It's reasonable to think that they will make the same threats against IRIX users.

    Now suppose that SCO manages to make this stick. How can we ever again have confidence in proprietary licenses, if the customer can have its license revoked through no fault of its own, but through the fault (real or alleged) of its vendors? Or its vendor's vendor? Or its vendor's vendor's vendor's vendor, which turns out to be some small software house in Middle of Nowhere, Idaho, which the customer in question never even heard of?

    The GPL, OTOH, specifically disclaims any right to terminate the rights of sublicensees:

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

    ---------
    [1] Predicated, of course, on proving that IBM actually breached its license, but SCO would rather gloss over that unimportant detail.

    --
    Ooh, moderator points! Five more idjits go to Minus One Hell!
    Delendae sunt RIAA, MPAA et Windoze
    1. Re:SCO's threat to proprietary software licensing by rdean400 · · Score: 1

      Actually, SCO's just trying to scare people. The actual language of the UNIX license is pretty clear (that IBM's customers' licenses are can't be declared null and void). The license says that if the agreement is terminated, then IBM must return or destroy all copies of source code in its possession. It does not provide the power to revoke end customer licenses, unless they were purchased after the license was terminated.

    2. Re:SCO's threat to proprietary software licensing by El_Ge_Ex · · Score: 1

      It's reasonable to think that they will make the same threats against IRIX users.

      What IRIX users??? :)

      (ducks)...

      -B

    3. Re:SCO's threat to proprietary software licensing by Shadowlore · · Score: 1

      Middle of Nowhere, Idaho

      That's Middle of Nowhere UTAH. Sheesh,

      Oh, and SCO isn't a software house anymore, they are a lawsuit and sabre rattling house.

      "What if they called a war and nobody showed up?" Ask SCO.

      --
      My Suburban burns less gasoline than your Prius.
  76. All the way to the bank... by rajafarian · · Score: 1

    I was thinking that it is important that SCO keep making statements such as these for two reasons:

    1. Keeps the price of their stock up.

    2. They can be cleared of pump and dump in case they lose. "Your honor, we did not make 'false and misleading statements to the marketplace.' No, your honor we really believe what we are saying. Here's more proof: On these days (shows list of public statements) we said it for the whole world to see/hear!" This way Darl won't be competing with the goatse guy in jail.

    1. Re:All the way to the bank... by Anonymous Coward · · Score: 0

      Well of course Darl won't be competing with the goatse guy!!!

      I have it on the highest authority that the photograph of the goatse guy *is* Darl McBride.

      The photograph was allegedly taken in the future by a time travelling investigator (who shall remain nameless) who surreptitiously entered the office of Darl McBride's personal physician (using cloaking technology that I cannot discuss.) The investigator reports the photograph was taken several hours after the conclusion of SCO's lawsuit with IBM.

      The investigator reports that Darl McBride in the instant before the photograph was taken was heard to say "My bottom hurts!" and "Their lawyers were mean!" The investigator swears that "... he sounded just like that Ralphie kid, you know the police chief's son, on the Simpsons."

    2. Re:All the way to the bank... by Anonymous Coward · · Score: 0

      Naaa! That not it.

      All the SCO people are simply stealing, lying, jerks who think that they have God on their side because of where they live.

  77. What of the GPL??? by 3seas · · Score: 1

    Are SCO still distributing Linux?

  78. Correction by headkase · · Score: 1

    Invalidation of the GPL would mean that existing GPL'd software could be incorporated into commercial code without restriction or credit to the original author.
    No, the authors would still own the individual copyrights to the code they wrote.

    --
    Shh.
  79. Where's the Think Geek T-Shirt? by Eric+Damron · · Score: 1

    SELECT manager FROM SCO WHERE clue > 0
    0 records returned

    --
    The race isn't always to the swift... but that's the way to bet!
  80. Honestly by NetNinja · · Score: 1

    When does all this bull crap stop? I guess there are no legal ramifications to put these guys in jail for making false claims and statements?

  81. Speaking of revoking lisences... by a_nimble_bahai · · Score: 1

    SCO is in blatent violation of the GPL and they continue to include GPL software as if they owned it. If we legally force SCO to stop using OSS, then we stop SCO from existing.

    1. Re:Speaking of revoking lisences... by cdn-programmer · · Score: 1

      I am starting to gleen what the SCO legal strategy _might_ be.

      The copyright convention includes the premise of derived works. This introduces the concept but does not define either what a derived work is or what the boundries might be.

      Many years ago the legal theory was at least speculated about that when an operating system loaded a program that in effect this became at that point one large program and at that point copyrite on the whole OS would then apply to the program being loaded under the idea of it becomming a derived work.

      I do not know if there was actual litigation at the time or if this was just some crackpot speculation (and I hope it was the latter).

      Yet - we have the exact same issue when we look at a function added to a program. Suppose we have some working code under copyright "A". Then someone comes along and adds function B. They can claim that the function they added should fall under copyright "B". However I think it may be quite arguable in court that the derived work that inculdes functions A&B is really a derivative of program A. Of course the opposite can be argued as well. Should the tail wag the dog or should the dog wag the tail?

      Suppose one were talking of a large poem. The Hash has 100 verse poems and some are rather good and we have some who take great delight in reciting them from memory - start to finish.

      As a case in point, if a person decides to improve a verse or two and then add a verse or two, is the resulting poem a derived work? This is the exact problem that software developers face.

      If after a period of time we have a series of small steps leading from program A through an AB phase and finally arriving at program B and eventually we find there isn't a single line of program A left... then we still have the situation that one could argue that B has been derived from A and we have the evidence of the small steps to prove it. We simultaniously have the argument that B was simply a step by step rewrite of A and hense B is not derived.

      A big dilemma happens however when we have two working systems A & B who each are independantly developed and stand on their own two feet. If these are somehow merged and become one then it is an open question of whether AB derives from A or whether it derives from B. And in this case a court could be asked to rule. It would be a civil case and in civil cases the 50% rule applies. After all is heard, the side with the best argument wins. Would the measure of "best" in this case be perhaps the number of lines of code in A verses B?

      Well - that is the simplistic view... that of likening code to stanza's in a poem. Reality is really much worse. A stanza is an entirely arbitrary division, just as a single line is. In fact, single words could just as easily form the standard of division which defines where we can place boundries.

      I would argue that in the case of George Harrision's "He's my Lord" verses the copyright infringment claim of "He's so Fine" that the judge felt copyright infringment should be found by the division of music at the equivalent of 5 or 6 notes and this would be the equivalent of a phrase boundry in a poem. By the judge's ruling in Harrison's fight, the lyrics and rhythm and emphasis that disinguishes one's use of a few notes in a song wasn't very relevant. Clearly in my mind the judge was rather misguided or naive or had a grude. But that is JMHO for what it is worth.

      In computer software we do have the problem that whether a few lines of code are in an inline block or in an internal function or an external function or even an external dynamically loaded function - that they essentually are the same lines of code.

      Probably most programmers feel that such a block of code should have its _own_ copyright. Perhaps so, but I've rarely seem a copyright notice slapped onto a block of code inserted in a program, yet I will see it often in external functions but rarely if ever in internal functions even though its th

  82. Re:An open letter .. to SCO by Anonymous Coward · · Score: 0

    Two more: F U

  83. It's funny really... by Anonymous Coward · · Score: 0

    They were going to name a James Bond film "License Revoked" until they figured that the US market wouldn't understand what it was getting at, so they renamed it "License to Kill".

    License to kill... Hmm... Oh Darl...

  84. Educational by bstadil · · Score: 1
    I love you Dog Poo analogy, however there is some benefits to this Soap Opera

    Treat it as an educational process

    We get to learn about:

    - Contract Law

    - Licensing, notably GPL

    - State of the Art media manipulation

    - Insights into the stock market and hopefully SEC

    - International Law. Notably Australia and Germany

    - Criminal Law like Mail-fraud

    - History of Unix

    --
    Help fight continental drift.
  85. Smells like a DUCK! by ezh · · Score: 1

    I do not really believe that SCO would allow so unprofessional comments about their case, unless it is a PR trick (very bad one, in this case).

  86. Somebody please, ask Novell... by SharpFang · · Score: 1

    ...to revoke the SCO license. If the smarties think they can say "Okay, end of playing, that toys were borrowed and now I want them back", show them they were REALLY borrowed. And after that, Novell will grant licenses to IBM and SGI directly and SCO will remain without OS.

    --
    45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
  87. Dumb by rdean400 · · Score: 1

    IBM filed attachments to their countersuit showing that SCO doesn't have carte blanche authority to revoke licenses. The sale agreement of the transfer rights gave Novell a veto card in case SCO wanted to terminate a UNIX source license. According to another attachment to the countersuit, Novell exercised that right with respect to IBM's license.

  88. Why is this funny? by Anonymous Coward · · Score: 0

    "It just keeps getting funnier!"

    Why is this funny? There doesn't seem to be anything humorous here at all. There's a point of contention involving some legalese as to whether or not some boring old license is revokable. You might agree with some of the points, you might disagree with some of them... but why would it be funny?

  89. Re:XFS and copies by jbolden · · Score: 1

    The funny thing is that getting it to work under Linux destroys the argument that the code is part of Unix. I.E. you can often prove B has derived status relative to A by showing that B is worthless without A. The fact that SCO admits that XFS works fine with Linux disproves it being "part" of Unix.

  90. XFS is original work by RageEX · · Score: 1

    "You can't take code based on a license you signed, change it a little and then give it away for free (as in the case of XFS from SGI)."

    This guy actually thinks XFS is a minor tweak of 20 year old SySV code?

  91. Hey Darl! by niko9 · · Score: 1

    You might as well staple your ball sack together, 'cause if you can't lick 'em, join 'em!

  92. Oh my goodness.... by jotaeleemeese · · Score: 1

    In which sense was MS "right"???? Morally, maybe. Legally, give me a break. Morality and legality are issues that non necessarily intersect.

    MS was found in violation of a patent that the holder registered legally and defended it in consequence. If the US patent system is in shambles that is a completely different matter, MS was not in the right as proven by a court of law.

    With SCO we have a company that has nothing, has been shown to be lying in a public forum and in ignorance of what is in their own obsolete code.

    I think you are thorhougly confussed.

    --
    IANAL but write like a drunk one.
  93. ulterior motives...AGAIN by spamchang · · Score: 1

    check the stock price correlation before/after the public hears about this letter. then watch SCO execs dump stock. $@!#!

  94. She spilled the coffee on herself by Kohath · · Score: 1

    She spilled the coffee on herself. Therefore, the lawsuit was frivolous and ANY damages unjustified.

    Why is that so hard for you people to understand?

    1. Re:She spilled the coffee on herself by lakeland · · Score: 1

      Yes she did. If I make a cup of coffee at home, and spill it on myself then I don't get first degree burns. If I got to McD, order a coffee and spill it on myself then I do. See the difference?

    2. Re:She spilled the coffee on herself by Anonymous Coward · · Score: 0

      You jump in front of your wife's bicycle, you only get bruises. You jump in front of your neighbor's wife's Chevy Suburban, you get killed. Clearly, you can sue your neighbor's wife for negligence, since she didn't need that SUV to get around, she only needed a bicycle, which, had you jumped in front of it, would only have caused you bruises.

    3. Re:She spilled the coffee on herself by lakeland · · Score: 1

      Hmm, interesting argument

    4. Re:She spilled the coffee on herself by ShinmaWa · · Score: 1

      She spilled the coffee on herself

      Its obvious you don't know much about the lawsuit. The coffee was near boiling when it was served. The styrofoam of the cup was literally breaking down and melting due to the heat of its contents.

      The lawsuit was NOT about her spilling coffee on herself. The lawsuit was about serving an unsafe product that melted its container and caused first degree burns. McDonald's knew it was too hot and was causing injuries, but served it that way anyway. That, my friend, is negligence. Why is that so hard to understand?

      --
      The /. Effect: Thousands of users simultaneously accessing a site to not read its content.
    5. Re:She spilled the coffee on herself by jedidiah · · Score: 1

      If your neighbor's wife just happened to be SPEEDING, then it is just and reasonable to hold her partially accountable for the ensuing harm. You make it sound as there is no possible way for the SUV driver to be contributing to the idiocy of the situation.

      That is simply false.

      McDonald's was speeding, was a chronic speeder and had run into many other people.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    6. Re:She spilled the coffee on herself by jedidiah · · Score: 1

      Put more simply: THEY KNEW that they were contributing to a dangerous situation. Instead of acting to avoid the problem, they sought only to SUPRESS public knowledge of the problem.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    7. Re:She spilled the coffee on herself by alienw · · Score: 1

      Coffee is _supposed_ to be boiling hot when served, you fuckwad. Now, perhaps it shouldn't have been served in a styrofoam cup, but the woman was holding it in her crotch when she spilled it. That, my friend, is pure idiocy. Why is that so hard to understand?

    8. Re:She spilled the coffee on herself by HardCase · · Score: 1
      Well, other than the fact that you're completely wrong, I agree with you. At 180 degrees, you WILL get burned. At 130 degrees, it takes about 30 seconds for it it to burn.


      Most places sell coffee at 150 to 165 degrees because a spilled cup will cool to around 140 degrees by the time it soaked through clothing, and keep cooling, giving a comfortable margin of time to either get out of the hot clothing or for it to cool enough that it would not burn.


      At 185 degrees, third degree burns will result in three to ten seconds.


      And I challenge you to drink a boiling hot cup of coffee. Go ahead, try it! And don't complain!


      -h-

    9. Re:She spilled the coffee on herself by nathanh · · Score: 1
      Coffee is _supposed_ to be boiling hot when served,

      No it's not. Boiling hot water burns the beans and ruins the coffee. You're supposed to brew it a few degrees below boiling. It's tea that you brew with boiling water.

      But this is totally irrelevant, because the temperature you serve the coffee doesn't have to be the same as the temperature you brewed the coffee. It was very negligent for McD's to serve boiling coffee to anybody, and exceptionally negligent to serve boiling coffee to anybody in a car, where the expectation for spilled liquids is fairly high. This was the finding of the court, and I agree with it.

  95. It's a blatan ripoff! by SHEENmaster · · Score: 1

    int main(int arc, char **argv){

    Appears in each's fsck app, as do several hundred occurences of } in both the fsck apps and the kernel code.

    You guys just keep bashing SCO as if they have no evidence, despite all the code that has been stolen from them by IBM and SGI.

    --
    You can't judge a book by the way it wears its hair.
  96. Irrevokable... by MadCow42 · · Score: 1

    You keep using that word... I do not think it means what you think it means.

    q:]

    MadCow.

    --
    I used to have a sig, but I set it free and it never came back.
  97. So the next step is.... by codefungus · · Score: 1

    ...the stock price goes up 49 cents on Monday, the execs dump some more stock (I think it's in their business plan), this news fizzles out in about 5-6 days then go back to step 1, which is make some dumb announcement... ...isn't this illegal? Or not really in the land of republicans (The U.S. (TM)(C)(c)) ...

    --
    -- A cat is no trade for integrity!
  98. Re:Open Source Hell by Anonymous Coward · · Score: 0

    So... COLA isn't enough anymore? You wintrolls just have to explode in anal-retentive anger and hunt down those heathen linux-hippies at every curb and corner, huh?

    Common wintroll memes:

    "Linux makes you stupid."
    "Linux users are gay, and most commonly pederasts."

    If only one of you fucking M$-sheep would dare tread in front of me...I'd rip your head off and shit down your throat - Duke Nukem-style!

    So "hear ye" this: Linux will come down on your imbecile head as a force of nature per se; lean back and enjoy the mushroom cloud...

  99. Changing code by Skapare · · Score: 1
    You can't take code based on a license you signed, change it a little and then give it away for free (as in the case of XFS from SGI). If SCO allowed companies to contribute derivative UNIX code to Linux and give it away for free, it would destroy the value of all other versions of UNIX, including SCO?s own, not to mention the versions of UNIX made by SUN, HP, IBM, SGI, Sequent, Hitachi, Fujitsu, Siemens, and every other one of the 6,000 other licensees. Why would SCO not have such a provision in their licenses? This line of thinking is absolutely ludicrous.

    What is ludicrous is thinking that that an entirely new development (as in the case of XFS from SGI) can somehow be thought of as derivative from UNIX just because it might be added back in to it. Maybe I should be calling up the DEA about the heavy drug use going on in Utah. Just because SGI integrated code licensed from SCO with their own development does not transfer ownership of that code to SCO, unless there were specific terms of that in the license SGI signed. And if that was the case, SCO wouldn't be trying to claim XFS is derived from UNIX, but would instead be pointing clearly to that clause. It isn't there and SCO has no rights to XFS other than as SGI has licensed (GPL?).

    Many big businesses all the time do cross-licensing where each ends up with rights to use intellectual property of the other. SCO somehow thinks they get to own everything (like their claim to the entirety of Linux, even though hundreds of developers unrelated to SCO did the actual work).

    --
    now we need to go OSS in diesel cars
  100. so which of the SCO suits by alizard · · Score: 1
    just got another block of stock options he wants to unload while he still can?

    Don't know if anyone else has noticed, but these announcements usually come by odd coincidence whenever some SCO insider wants to unload.

    1. Re:so which of the SCO suits by EmagGeek · · Score: 1

      Can you provide data to substantiate this claim?

  101. Licenses really can be revoked by Skapare · · Score: 2, Informative

    Licenses really can be revoked under the terms of the license itself. The terms a government issues a drivers license under would include the specific laws involved. They cannot just arbitrarily revoke a drivers' license, but they can under those specific laws. If you commit certain actions the law says you may lose your license for, it can be revoked.

    Likewise, a private license for use of some property can also be revoked under the agreed terms. Generally, if the agreed terms are violated, the license can be revoked. If SGI and/or IBM did release UNIX intellectual property to the public, that would be such a violation. And we do know SCO is claiming that.

    The issue now comes down to whether such a claim is valid. Did SGI take XFS from UNIX and release it publically. That cannot be the case, however, because there is no XFS in UNIX. SGI developed XFS themselves. Arguably, pieces of XFS might have gotten some UNIX code in there, but once pointed out, that can be removed. Did SCO perform due diligence in pointing that out? Not until recently have they started pointing at any specific violations (while still making vague and unsubstantiated claims that lots of other violations exist), and those are weak due to previous releases in other forms.

    And how the hell do we know there isn't any violations in SCO's non-Linux closed-source product ... violations of the GPL with code taken from Linux and put in there?

    --
    now we need to go OSS in diesel cars
    1. Re:Licenses really can be revoked by fermion · · Score: 1
      As has been mentioned, they key point is how and for what causes a license can be revoked. In the case of SGI and IBM it looks like they are contracted for perpetual licenses and there is due process for the termination of the license.

      In your example of a drivers license, this would mean that I am guaranteed renewal unless, for instance, I break a specific law. The State would have to prove that I broke an exact law and said law was grounds for termination. In fact, it would be wrong for the State to talk about my 'license being terminated' prior to the time that a court found that I had broken a specific law. Even then there might be another court case to show that the act was in fact violation of the license. Until such court decisions, violation would be a possibility, not a reality.

      What SCO is trying to do is treat the license as if it was a short term deal that had to be renewed on regular basis. In such cases one can say the license will be revoked. No due process is needed. The license expires and it is not renewed.

      What IBM and SGI are trying to say is SCO cannot do this, and until the violations are proven, probably in court, and until negotiations have failed to find a compromise, the license will remain in effect. In fact, SCO may be in violation of the license, and is likely to be shown as negotiating in bad faith, for it's public comments.

      --
      "She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
    2. Re:Licenses really can be revoked by iapetus · · Score: 1

      Forget proving the violations, SCO still haven't actually specified in any detail what the violations are, which is a necessary first step according to the license snippet they put forward (which you can bet shows their point in the most positive light possible...)

      --
      ++ Say to Elrond "Hello.".
      Elrond says "No.". Elrond gives you some lunch.
    3. Re:Licenses really can be revoked by nathanh · · Score: 2, Insightful
      Likewise, a private license for use of some property can also be revoked under the agreed terms. Generally, if the agreed terms are violated, the license can be revoked. If SGI and/or IBM did release UNIX intellectual property to the public, that would be such a violation. And we do know SCO is claiming that.

      Addendum X to the UNIX license with IBM says the license is irrevocable. There are no words in the license or addendum that say "oh, unless you do this, in which case we can revoke it". The license is irrevocable.

      The license even makes things clearer: it says the license is perpetual. Now explain to me why the license would say perpetual and irrevocable and less than a page later give conditions for revocation? Hint: it doesn't.

      The UNIX license with SGI might be different. Somehow I doubt it. I recall SGI saying that they also have an irrevocable agreement in an addendum.

      The addendum says that the UNIX license can be enjoined if there are any violations. This means to force into compliance. Not to revoke. If the license is irrevocable and it states that the license is irrevocable then it'd hardly make sense if the license could actually be revoked.

      In the most imaginative intepretation, enjoin could perhaps permit an injunction. But that will require a judge to decide, and SCO first has to submit a request for injunction to the court (and you might notice they haven't done that). The word "enjoin" definitely doesn't give SCO the right to revoke the license, because it's very clear that the license is irrevocable.

    4. Re:Licenses really can be revoked by RedWizzard · · Score: 2, Insightful
      Licenses really can be revoked under the terms of the license itself. The terms a government issues a drivers license under would include the specific laws involved. They cannot just arbitrarily revoke a drivers' license, but they can under those specific laws. If you commit certain actions the law says you may lose your license for, it can be revoked.
      Please don't use the driver's license analogy that SCO have introduced. A driver's license is totally different (legally) from IBM/SGI's licenses to use Unix code. IBM/SGI's licenses are simply contracts allowing the use of certain SCO property in certain ways. A contract can have almost any provision (the obvious exception being illegal activities). Driver's licenses are not contracts, they are permits which can be granted and revoked as provided by the law. SCO have introduced the analogy of driver's licenses to obfuscate the issue and to make their claims seem stronger.
  102. Ammendment X? by Anonymous Coward · · Score: 0

    This "amendment" says that said source code will remain private. If SCO source code did indeed end up in Linux, this document pretty much proves that IBM is in default of the contract. This document doesn't absolve IBM by a long shot.

    1. Re:Ammendment X? by jedidiah · · Score: 1

      That's a pretty big IFF.

      Thusfar, they have only demonstrated their lack of ability to distinguish their property from elements contributed by others (BSD).

      --
      A Pirate and a Puritan look the same on a balance sheet.
    2. Re:Ammendment X? by Anonymous Coward · · Score: 0

      "That's a pretty big IFF."

      No shit, that IFF is at *least* 50% bigger than it should be...

  103. STOP REPEATING LIES! by Anonymous Coward · · Score: 0

    "(For example, the "woman scalded by hot coffee" suit, which at first blush looked like the height of frivolity proved to be a perfectly legitimate action taken against a corporation that knew, thanks to a string of similar scaldings it had quietly been paying off, that its coffee was not just hot, but dangerously hot. The Association of Trial Lawyers of America provides an excellent description of this case"

    Every time someone points out how frivilous this case is and was, one of you scum come crawling out of the woodwork to claim it was reasonable.

    IT ISN'T!!!!

    If you spill hot liquids on yourself, you will get burned. Really badly burned. The fact that a few people are stupid doesn't mean the lawsuit has merit, it just means that a few people are stupid and that people like you try to profit from stupidity.

    I wish trial lawyers like you all die of cancer caused by something funny, like spending too much time whoring yourselves for a few bucks.

    You make me sick.

    Let me say a prayer for you:

    "Dear jesus, let the cleansing cancer take hold in this sub-human and let him die slowly. So slowly that the doctors take all his money, and throw his wife into prostitution and his kids into crack whores. In your name we pray, amen"

    1. Re:STOP REPEATING LIES! by Gregg+M · · Score: 1
      Every time someone points out how frivilous this case is and was, one of you scum come crawling out of the woodwork to claim it was reasonable. IT ISN'T!!!! If you spill hot liquids on yourself, you will get burned. Really badly burned.

      Really? So you go into a restaurant and get a coffee that's so hot it burns the skin off of you.... and you think that's reasonable? Forget the fact she spilled it. If she drank the coffee she would 've burned her tongue and mouth so badly she might have been a lot worse off. Look at this clip I found...

      The simple accident caused third-degree burns on more than 6 percent of her body. She was treated in a hospital for a week. McDonald's served coffee 20 or so degrees hotter than the industry standard. The woman, Stella Liebeck, underwent numerous skin-graft surgeries as a result of her third-degree coffee burns to her thighs and groin area. She had permanent scarring on more than 16 percent of her body.

      McDonald's had already ignored more than 700 similar claims of coffee burns, many involving children. The company even ignored a request from the Shriner's Burn Institute in Cincinnati to turn down its coffee.

      So I guess you're the scum! Skin grafts and a week in the hospital care of McDonalds is not reasonable.

      --
      Linux is only free if your time has no value. Windows is only free if you threaten to use Linux.
  104. I see the difference by Anonymous Coward · · Score: 0

    "See the difference?"

    Yes. You are whore who will defend your right to make money for nothing until your dying breathe. Hopefully, some disease will take you away sooner rather than later. And end the suffereing for the rest of us.

    You fucking leech.

  105. Maybe, but we now know a lot about you by Anonymous Coward · · Score: 0

    "Its obvious you don't know much about the lawsuit"

    You're one of those people who either are a trial lawyer trying to defend your whorish behavior or you're a moron.

    Neither comparison is particularly nice.

    Hope you're sterile so you can't breed and infect the earth with more of your kind.

  106. It just keeps getting better. by Anonymous Coward · · Score: 1, Insightful

    When the initial charges were leveled against ibm and sco's stock price was in the tank, ibm had a tough decision. Whether to buy sco or fight them. Each time a new "open letter" is put out the chance that ibm will buy sco diminishes. The one great unknown is what will m$ do? After all bill could buy sco with the change he finds in couch. So why doesn't he do it? Because he doesn't believe sco has a case, even if he were to pick up the banner and run with it. After all his over-riding goal is to slow the adoption of linux and given the bungling, foot shooting excercise that sco is doing on a nearly daily basis he is not about to buy a sinking ship.

    What seems most interesting is what will happen 3-5 years from now. Sco can only delay the law suits from Redhat and ibm for so long. They continue to alienate there distributors as well as squandering any good will within the development community that might have existed, based on there past performance. At the same time, sun is bleeding to death and can't sustain its support for sco. Sun's problems are really caused by poor management decisions and an inability anticipate the future of the server market.

    To sgi's credit they moved quickly to identify and fix the problems they were responsible for. Whether sgi's license will be revoked can only be sorted out in court. This is a real serious problem for sco because they don't want to go to court. Given sgi's quick action to sco allegations it seem unlikely. But this is the us court system so it's probably a crap shoot. Ultimately, sco has only one card to play. They must prove they have some right to linux source code. Whether those rights are direct, as in copied code or whether they can "leverage" some rights by asserting claims of "derived" code remains to be proven. If they were hoping to settle this out of court that bet seems to have been a dismal failure for them since it looks like ibm is willing to go the distance.Only a very small number of companies are buying sco licenses while a very large number are continueing to deploy linux. This shows how the vast majority of people see the long term impact on linux.

  107. I agree with you 100% by Anonymous Coward · · Score: 0

    "You must like the taste of shit because the linux zealots have been spoon feeding you plenty of it lately"

    Dear Sir:

    Thanks for the fine input.

    Now please die.

    With loving respect,

    Darl "Shake-n-Bake" McBride

  108. Oh dear... by Tore+S+B · · Score: 1

    ...Now we're going to have to use Linux. Get our 2000 programmers to look through the kernel and make improvements, and submit it back to the kernel tree. Ohhh.... The wonderful sound of SCO being screwed together with Unix. This is a major major Good Thing for Linux. Now they will have elite programmers, the kind that stays overnight to bum a few instructions off that frequently used routine, to add that neat implementation of... oh, yeah, and rewrite... oh and... Can't wait to see what happens now.

    --
    toresbe
  109. Double dipping by EriDay · · Score: 1

    In the event that IBM loses, it would have to pay damages to SCO and... that's it. SCO would be barred from suing Linux vendors or users because that would be "double dipping".

    I think you may have this confused with "double jeopardy" in a criminal case.

    If you [contractually] rip me off, and so does the guy down the street, I can sue you both. That's what class action lawsuits are all about.

    1. Re:Double dipping by ShinmaWa · · Score: 1

      I'm tired of posting it. See here

      --
      The /. Effect: Thousands of users simultaneously accessing a site to not read its content.
  110. I hereby revoke SCO's license to Linux code by kasperd · · Score: 1

    I have written a few lines of the Linux kernel, and since SCO have publicly stated, that they do not accept the GPL, I see no problem in revoking their license. By SCO logic (since UNIX code is in Linux) that also mean their UNIX license has been revoked.

    --

    Do you care about the security of your wireless mouse?
    1. Re:I hereby revoke SCO's license to Linux code by Trejkaz · · Score: 1

      Absolutely.

      If through some stroke of luck they manage to show that the GPL doesn't hold in court, then every single individual who ever contributed a single line of source code to any software which has ever run on Linux, can sue SCO.

      --
      Karma: It's all a bunch of tree-huggin' hippy crap!
  111. if... by pyrrho · · Score: 1

    ... he catches the disease in a McDonalds... big $$$ for the estate!

    --

    -pyrrho

  112. Another open letter... bah! by jmorris42 · · Score: 1

    They are just trolling again, please don't feed the trolls.

    If they send it to a court it might mean something, something tossed out to get the /. crowd riled up again or attract a few more ignorant investors doesn't really matter.

    And no I don't care about the investors who are getting screwed. "It is immoral to let a sucker keep his money." (quoting RAH) Anyone sinking money into what was a penny stock earlier this year without investigating the situation deserves to get shafted just as hard as the idiots who bid Amazon up to a valuation higher than Boeing in the .bomb days.

    --
    Democrat delenda est
  113. So IBM cannot sell AIX? by solprovider · · Score: 1

    Take this as completely theoretical. I believe SCO is evil and IBM is going to destroy them. But...

    What if SCO is able to revoke IBM's license to sell Unix? The contract is broken. IBM pays $3B. And IBM needs a quick replacement to convert all those AIX installations.

    The contract is broken, so IBM no longer has any obligation to protect Unix. And the customers demand all IBM proprietary technology must be in the replacement that the courts have ordered IBM to provide.

    IBM cannot use Unix. They need an OS that can replace AIX, meaning it can run their customers' Unix applications. Can this be done with OS/390? OS/400? OS/2? Or will IBM immediately pump all that technology into Linux?

    IBM Linux could become suitable for big iron in a very short time.

    Not that all that technology must be added to RedHat or SuSE. The big loophole in the GPL is that it only matters if you distribute the binaries, and that "distribute" means customers, and U.S. law uses NDAs to change a customer into a development partner that is legally associated with the developer so the GPL is not relevant. But it would only take one customer to demand a replacement without signing an NDA to force IBM to GPL all this code. Will any company chance their information systems becoming obsolete because they did not sign a contract that does not affect themselves while IBM is offering a big discount?

    Let us assume that IBM plays nice and GPLs all changes to the Linux kernel. They could still keep the code that uses those changes proprietary, but the kernel is improved. (And IBM offers Torvalds $1B to oversee the project, and he would take it because it would mean fantastic progress for GPL'd Linux.)

    I have no idea how this situation helps SCO. I think it would be the final straw and "Unix is dead" would appear everywhere. I doubt SCO has put any thought into the consequences of their actions, other than they might get $3,000,000,000. I know that much money would make me happy, so maybe that is the only point, and they expect Unix to die anyway.

    --
    I spend my life entertaining my brain.
    1. Re:So IBM cannot sell AIX? by iq+in+binary · · Score: 1

      Let us assume that IBM plays nice and GPLs all changes to the Linux kernel. They could still keep the code that uses those changes proprietary, but the kernel is improved. (And IBM offers Torvalds $1B to oversee the project, and he would take it because it would mean fantastic progress for GPL'd Linux.)

      Emphasis mine.

      Have you even read the GPL? Any modifications to the Linux kernel are necessarily GPL'd as well. The fact they have not released the source for the kernel changes is going against the GPL whole-heartedly. Seems IBM is still around and un-harassed as far as obeying the GPL, so I'd guess they have not made any un-published changes to the kernel. End of story.

      --
      Of all the Universal Constants, here's one I know: Nice guys finish last ;)
  114. I fail to see by dtfinch · · Score: 1

    Where his quote says SCO can revoke licenses. It clearly says only AT&T has that right, and should have been revised if the power was to be transferred to SCO.

    1. Re:I fail to see by C_Kode · · Score: 1

      Maybe because now SCO owns AT&T's rights?

  115. IP attorney Mark Radcliffe noted: by Anonymous Coward · · Score: 1, Informative
    "IP attorney Mark Radcliffe noted:
    Irrevocable means you can't terminate, you can only get injunctive relief (stopping breaching the agreement), otherwise irrevocable would have no separate meaning."


    Yahoo seems to know what 'irrevocable' means:
    http://suewidemark.netfirms.com/geocities_ yahoo.ht m


    Radcliffe also noted that the rights sought by Yahoo and other community sites are exactly those that publishers are granted under U.S. copyright law: the right to distribute, reproduce, publicly perform and display, and modify or make a derivative product.


    So while members think they are only receiving space to place their intellectual property, the Web sites are acting like publishers.


    Getting back to Stowell, he seems to forget that their amended complaint is a tort about contract violations by IBM, not patents, trademarks or copyrights.


    From a Mozilla interview: "An important question in the SCO IP sagas has been whether SCO-Caldera owns copyrights for JFS (Journaling File System), RCU (Read, Copy, and Update), NUMA (Non-uniform Memory Access) software, and other AIX code that IBM contributed to the Linux kernel. Simply put these are important code packages that help to make GNU/Linux an enterprise and server grade operating system.


    It appears from Blake Stowell's answers to the copyright-related questions that SCO says it does not have copyrights to JFS, RCU, and NUMA software code or to items (a) through (k) of paragraph 108 of SCO's Amended Complaint in the SCO-Caldera v IBM lawsuit.


    It also appears from Blake Stowell's answers that SCO does not claim copyright to any of the IBM-written AIX code. All SCO claims copyright to in AIX is that AIX code which is Unix code that was included with System V code that IBM licenses from SCO.


    That seems to remove most, if not all, SCO's claims that the Linux kernel contains SCO-copyrighted code. "

  116. Use the force, Luke--use the RIAA! by shanen · · Score: 0

    The solution is to use the enemy's strength against him. Kind of a problem here since SCO doesn't have any *REAL* strengths, but at least they claim to have strong lawyers.

    Lawyers as assets [asses?] should make the RIAA leap to mind. As already noted, the RIAA is eager to sue copyright infringers, even if the IP addresses can be faked. So setting up a number of P2P servers using IP addresses that belong to SCO should be sufficient to get that side moving.

    The other side is more of a challenge. SCO claims they want to defend IP, but RIAA doesn't have any and doesn't pretend to. They haven't actually created anything except money for themselves and a lot of mumbles about "defending artistes" somewhere. Somehow the DMCA has to be linked to IP so SCO will attack via that route... Judging by their existing lawsuits, it doesn't have to be a sensible or realistic link.

    --
    Freedom = (Meaningful - Coerced) Choice != (Speech | Beer^2), and sad sock puppets' bad mods avail them naught.
  117. MOD PARENT DOWN by Anonymous Coward · · Score: 0

    cyt0plas is a moron

  118. Screw UNIX let it die by Anonymous Coward · · Score: 0

    Let's just all let UNIX die a graceful death and onward with BSD and Linux. SCO is just digging a deeper grave for UNIX each time they open there mouth.. I would have thought they would have finally woke up to the fact that they are running UNIX with each nail they put in the coffin. But then again maybe that's SCO's plan in since day one.

  119. Enough is enough by Anonymous Coward · · Score: 0

    Fuck SCO. What little market share they had remaining is going to dry up as a result of this silliness. They've had plenty of time to make money by actually providing value to their customers. Since they haven't been able to do that, we end up with this last minute arm flailing as the swimmer drowns a nasty death.

    Good riddance.

  120. Except For Germany.. by Anonymous Coward · · Score: 0

    I thought there was a court case forbidding them to spin fud like this in Germany. Their press releases would be so much clearer and better if they included , except for Germany.

    The German justice system needs help/remind/fine SCO once more. Germans read international press releases and news too. Sadly, the ACCC in Australia, has not made a determination, yet. As the list of qualifications grows, people will get the message.

  121. Flaim Bait Trolling, but... by iamatlas · · Score: 1
    Why is it that so many people believe they are experts in this matter along the lines of "SCO is wrong and here is my own slightly different version of why and you are wrong about why SCO is wrong because..."

    Lets face it, even the lawyers in this group are not experts in this matter. Those who are? IBM and SCO. Work for IBM? Work for SCO ::shudders:: come on down. Otherwise lets stop the legal and tech essays at IANAL or IANAEOTI (I am not an expert on this issue) and leave it at that. Because adding a "but" after that is like saying to the guy having a heart atack "No, I'm not a doctor, but I play one on TV"

    So is it too much to ask that we all just keep our mouths shut on this, having exhauseted everything we know to say about it before the summer began? Can we all stop arm chair Quarterbacking or backseat driving this issue? Think of it this way- when your boss catches you slacking off a little, what's the best way to handle it- do some goof cover up and start trying to look busy, or play it off as though you're not doung anything wrong, maybe even tell him he has got to take a look at this email you got forwarded... You get the point. SCO is just a big bear. Don't feed it. It will go away.

  122. Kill him Jesus! Kill Him! by Anonymous Coward · · Score: 0

    "So I guess you're the scum!"

    What are the only two creatures that scurry when the lights turn on.... cockroaches and trial lawyers.

    That aside.

    Lets break it down... see, you get it, but to put the responsibility back on the person isn't *profitable* for people like you. But lets break it down anyway.

    1) Coffee is hot
    2) People like hot coffee
    3) People who want coffee to go sometimes want to enjoy their coffee
    4) Some people burn easily
    5) Some people are stupid
    6) Some stupid people burn easily
    7) Water when its bubbling is boiling at around 212 degrees
    8) Coffee is never boiling after brewing or else it tastes lousy
    9) Cold coffee tastes just as bad
    10) So does warm coffee
    11) So when the coffee is on the stove, its ... at most... at 185 degrees. As soon as its poured and put into cups, it will cool off pretty fast; usually 160-170 within a minute.
    12) Still you can get burned at that temperature, although most people will get redness
    13) Other people will get more serious burns
    14) Life sucks sometimes
    15) If you get hot coffee in a fragile cup, never put it between your legs.
    16) Rule 15 is understood by everyone over the age of 6.
    17) Yes, I checked with my kids
    18) Stupid people exist
    19) Stupid people go to McDonalds
    20) Stupid people drink coffee
    21) Stupid people do stupid things with coffee, like...put it between their legs
    22) If you do stupid stuff, that's the breaks. Life's a bitch. I feel so sorry
    23) Sometimes accidents even happen to good, smart people
    24) Life is still a bitch
    25) McDonalds likes to sell coffee
    26) McDonadls sells coffee that appeals to their customers
    27) Othewise, customers will go someplace else
    28) Shit heppens.
    29) Trial lawyers depend on stupid juries to pay large verdicts to "teach McDonalds a lesson"
    30) Lawyers like this should all die of cancer
    31) And then go to hell
    32) Amen

    Hope that was plain enough for you, Moron.

  123. do your own homework by alizard · · Score: 1
    Start with this article from Bloomberg News for background.

    To get dates of insider stock sales, go to the SEC site and go to the EDGAR links.

    Then, just pop over to the SCO company site for their press releases announcing various and sundry things that can be expected to increase stock prices.

    Draw your own conclusions. You should find some. . . interesting coincidences.

  124. You DO Realize by Greyfox · · Score: 1

    That the only thing that could cause the GPL to become invaild is if the court finds that EULAs over all are invalid. It's much more solid than the EULAs that come from the commercial world. Every commercial software house on the planet would be in a world of hurt if a court comes out and says "EULAs are not legal." Has the general concept of an EULA ever been tested in court?

    --

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

  125. Why we can't afford to ignore SCO by X-Nc · · Score: 1
    There have been many, many articles and opinions on the insanity that is surrounding the Caldera/SCO Group brouhaha. It seems that a day can't go by without some silliness coming from them. Many people are tired of reading about it and I know a number of people have suggested, as you have, that if we ignore them they'll go away. After all, they don't have a leg to stand on now. They are just full of noise and hot air. While this may be true, ignoring them is the last thing we should do.

    The bottom line here is the old saying, "Perception is Reality." Yes, the Caldera/SCO Group is blowing nothing but very thick smoke. Yes, indemnification is a joke and a non-issue. Yes, it's all about FUD and trying to kill Linux. However...

    The fact of the matter is that the world outside of the Open License community can only go by what it reads and hears. And everything they are hearing, from both sides of the fence, just makes them gun shy. It matters little whether or not Caldera/SCO Group have a real claim on any code. Just the idea that they "might" is enough to do some damage to the Open License community and the actual software produced under said licensing. Ranting about it will not help. Being silent will not help. The only way I can see that will counter this is with calm but firm statements of truth by the community when discussing it with those who are outside of the community or in any published forum. Make sure that you have all the ammunition that is available on the subject when going into a situation where you might be confronted with FUD. Calmly explain to those who aren't as knowledgeable as we are about the facts. Don't get hyped up or excited. Don't make it a big deal. And definitely don't over exaggerate Open Licensed softwares capabilities. Think of it as explaining to your young child that there are no monsters under the bed. Be calm, be reassuring, be honest. This will do far more to take the wind out of the FUD than anything else we could do.

    --
    --
    If I actually could spell I'd have spelled it right in the first place.
  126. Derivatives by mb10ofBATX · · Score: 1

    Lets do a little math...

    XFS or JFS == Derivative Work?
    Noooooo... it just works on top of the OS.

    NUMA/SMP == Derivative Work?
    Arguably... but SCO ain't making the case, IMO.

    So lets shuttup about XFS and JFS. I like 'em both. Lets talk more about NUMA and SMP and what all is going on there.

  127. Just picking nits by Anonymous Coward · · Score: 0

    Alterior does not exist in the english language. The word you are looking for is ulterior. Today's grammar lesson brought to you by the letter K.

    1. Re:Just picking nits by Shadow+Wrought · · Score: 1

      Thanks letter K! I honestly thought it was alterior all these years. DO'H!

      --
      If brevity is the soul of wit, then how does one explain Twitter?
  128. That's funny... by Anonymous Coward · · Score: 0

    I didn't think SCO had a director of public relations...

    1. Re:That's funny... by frkiii · · Score: 1

      They have one.

      But he is doing a piss-poor job of it.

      Their "public relations" have been flushed down the toilet, heading for the sewage processing plant.

      SCO has given themselves absolutely no future current (or recently current) customers. No one will want to deal with these sleeze bag bunch of liars, cheats and two-faced sons-o-b__ches in the future.

      Regards,

      Fredrick

  129. Hostile Takeover? by kcb93x · · Score: 1

    So should we, as a community, make a hostile takeover of SCO stock? Pay bottom dollar, but take as much as possible (just enough to have 51%, or whatever's written in their agreements needed to force it our way) Shut down the company, and/or give their IP to the public, under GPL or some other license?

    I know this would be a *massive* undertaking, but it's possible...

    somebody tell me if I'm full of s*** or if this *truely* is viable.

    --
    There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
  130. OK, What happens next? by ThisIsFred · · Score: 1

    SCO is going to implode, no doubt about it. What happens to that Unix code afterward?

    --
    Fred

    "A fool and his freedom are soon parted"
    -RMS
  131. IBM Funds Sco lawsuit by overlordhab · · Score: 1

    Just think for a moment if SCO was right and IBM's license is revoked. IBM will have to pay the licence fee again. SCO will use the money to pay for the lawsuit against IBM.

  132. SCO can also claim that... by zeruch · · Score: 1

    ...the moon is made of blue cheese, but until they can prove it I say they are full of ripe turd there as well.

  133. What makes you think this is real? by harlows_monkeys · · Score: 1
    It's in The Register, for God's sake, with no link to a source, quoting a letter allegedly sent directly to a Register "reporter", that shows up nowhere else on Google.

    The Register has a sense of humor. I suspect they are exercising it.

  134. "In their right mind" by Stackster · · Score: 1

    "Why would anyone in their right mind sign over a license to anyone that was not revocable?"

    Why would anyone, judging from the statements they made in the recent months, have any reason to believe that the people in SCO's management are in their right minds?

    --

    There are 010 kinds of people. Those who understand octal, those who don't, and 06 other kinds of morons.
  135. Avoiding the GPL by solprovider · · Score: 1

    Have you even read the GPL? Any modifications to the Linux kernel are necessarily GPL'd as well.

    Have you even read the GPL? Did you actually read my post to which you are responding? The GPL has a very narrow scope that is easily avoided.

    The paragraph in my post just before the one you criticized explains the loophole in the GPL. Yes, modifications to GPL'd software are GPL'd. But the GPL only applies when you distribute software. If you make changes to Apache, and only use it at your company, the software has not been "distributed" and you are not required to provide the source to anybody. If you give or sell it to another company, you must make the source available to that company, but you could contract that they not distribute the software or the source to anybody else. An NDA (Non-Disclosure Agreement) allows you to share technology without allowing that technology to be distributed to others. A well-written NDA could be used to sell GPL'd code without providing source code.

    Most software comes with contracts/licenses that state that it may be used on a certain number of machines for a given time period and may not be shared. All the DRM news is about companies trying to enforce those contracts through technology, even though the technology does not allow for fair-use.

    Even the SCO circus is about the same battle. SCO thinks they own the rights to Unix, and they believe that the licenses to sell Unix implies that the licensees must protect Unix. Given that, then any code written to improve Unix cannot be shared with OSes that compete with Unix. Yes, they have warped minds, but it does make sense if you take the correct drugs.

    I was writing about a hypothetical future where IBM dumps all of their technology that makes AIX special into a Linux-based OS. It is likely that much of it can be handled by proprietary programs outside the kernel, but anything related to making the kernel robust on 64+ processors would require kernel modifications. Nothing I said implies that IBM has not obeyed the spirit of the GPL so far, but in this hypothetical future situation, they would be giving away much of their private technology.

    It is possible for IBM to take Linux and turn it into the next version of AIX. My point was that if they did this, they would want to protect their technology, and there is a way for them to do it. I was not implying that IBM would violate the spirit of the GPL. I was not implying that these events would ever happen, since that requires IBM's Unix license to be revoked and I doubt that even our courts would allow that. IBM sells hardware; the OS is just an extra, so I doubt they would even care, except for the existence of HP and SGI and the other Unix sellers who would not mind reading the source to an OS that included all of IBM's tricks.

    --
    I spend my life entertaining my brain.
    1. Re:Avoiding the GPL by Znork · · Score: 1

      "If you give or sell it to another company, you must make the source available to that company, but you could contract that they not distribute the software or the source to anybody else. An NDA (Non-Disclosure Agreement) allows you to share technology without allowing that technology to be distributed to others. A well-written NDA could be used to sell GPL'd code without providing source code."

      No, limiting the recievers rights is not acceptable under the GPL. Section 6: "You may not impose any further restrictions on the recipients' exercise of the rights granted herein.". This applies to any kind of limitations, ranging from patents to NDA's.

      The GPL is pretty well thought through. There are no loopholes like that. The only grey areas are in the areas of dynamic runtime loading of code to specified ABI's and the application service provider hole.

    2. Re: Avoiding the GPL by solprovider · · Score: 1

      limiting the receivers' rights is not acceptable under the GPL. Section 6: "You may not impose any further restrictions on the recipients' exercise of the rights granted herein.". This applies to any kind of limitations, ranging from patents to NDA's.

      There is no spoon. (Sorry.)
      There is no receiver. There is no recipient. The nice part (from a legal perspective) is that an NDA can make a company a development partner which is part of the company for purposes such as patents.

      So my company rewrites half of Apache. We do not want to distribute the code, but you are a friend, so we will lend you a server with everything configured. You ask about the source code, and we present the NDA stating that you are a development partner, will be testing the software in a production environment, and have no rights to any of the modifications.

      Under U.S. patent law, that is legal, and there is no distribution of software because those companies are partners. So there is no "recipient" to have rights restricted. So there is still a hole in the GPL.

      ---
      I like the GPL. I think it is as good as it gets for sharing software.

      And this hole cannot be closed. Try adding something stating the moment you change something you are required to tell the world. Who would touch software if you had to issue a press release every time you changed a line of code? You must be able to work on it without being required to distribute.

      (IANAL. Is this a good place to put that?)

      --- Why I know this
      We are developing software. We think we can get patents. We cannot discuss the features that might be patented with anybody with whom we do not have an NDA without losing our ability to patent those features. Well, we would have one year to file in the U.S., but we would immediately lose the right to file in Europe. The NDAs protect our rights to file, and we insist all potential customers sign them before we give a sales presentation. This limits to whom we can sell, so we want to get the patents filed so we can skip this step. It is possible for a company with the clout of IBM to force every "customer" to sign an NDA to become a "partner" to avoid the "distribute" clause.

      Again, I am not saying this would ever happen, just that it is possible.

      --
      I spend my life entertaining my brain.
    3. Re: Avoiding the GPL by Znork · · Score: 1

      "So my company rewrites half of Apache."

      Well, first of all, if your company rewrites half of Apache you can do whatever you want with the code except call it Apache, if I remember the Apache license correctly. The Apache web server is not under the GPL.

      Second, an NDA does not a legal organizational entity make. You can try signing an NDA with a 'development partner' and give them Windows under your site license and see what MS thinks about wether you're the same organization or not.

      Patent law has nothing to do with it. The companies may be partners however much they wish to; they're still not the same organization, not when contracting Windows, not when distributing GPL software, nor when sued for copyright violations.

      "We are developing software. We think we can get patents. We cannot discuss the features that might be patented with anybody with whom we do not have an NDA without losing our ability to patent those features."

      The restrictions on patents have nothing to do with distribution between organizations. The restrictions are that there must not be any previously published prior art (altho with the current patent offices around the world you could probably publish it in 200 meter burning letters across the sky and they wouldnt notice anyway). You are, of course, entirely able to limit this publishing by enforcing an NDA, which works fine with patents, as patent restrictions arent concerned with limited distribution, only publication, and as a consequence of that, with public distribution. Copyrights on the other hand are concerned with nothing but distribution, in any way or form. The legal aspects are very different.

      As an aside, it actually has happened (twice, I believe). The companies in question engaging in the NDA covered distribution changed the NDA's and published source after chats with FSF's legal counsel, even if they were just temporarily engaging in the practice for understandable reasons.

    4. Re: Avoiding the GPL by solprovider · · Score: 1

      My mistake, bad example: I forgot the Apache License is BSD-style.

      Your mistake: bad example: MSWindows is not GPL. Their licenses are extremely draconian. Anybody releasing their source code would have very serious legal difficulties. But as a consultant, companies often share their proprietary licenses with me so I can work on their systems. As long as someone pays for the licenses, the proprietary software companies do not care whether the license is used by an actual employee or a partner. NDAs do not affect this practice, just financial wisdom.

      You are correct: Patent law does not apply here. (For the record, our software is completely home-grown, and does not include code from any other project, GPL'd or not.)

      The companies in question engaging in the NDA covered distribution changed the NDA's and published source after chats with FSF's legal counsel, even if they were just temporarily engaging in the practice for understandable reasons.

      Do you have links? I do not remember this method being used. I remember several cases where GPL'd software was distributed, and the FSF was able to get the source distributed too. And you state that the NDAs needed to be changed, so maybe they were legal, but did not keep the spirit of the GPL? Most companies want to keep on the good side of the open source community, and will bend to keep them happy. The good publicity is worth more than any advantage from keeping the code secret for a few months.

      This thread was speculating about a possible reason (losing the Unix license) that IBM would consciously break the spirit of the GPL. If IBM really needed an Unix-like OS in a hurry, they would probably start with a mature BSD rather than the weaker and GPL-encumbered Linux. (That is what Apple did.)

      As I said, IANAL. I am interested in the links that this has been tried. But I seriously doubt IBM would bother trying it.

      --
      I spend my life entertaining my brain.
    5. Re:Avoiding the GPL by iq+in+binary · · Score: 1

      If it's not distributed, then they are obviously not making any profit off of it.

      No harm, no foul.

      --
      Of all the Universal Constants, here's one I know: Nice guys finish last ;)
    6. Re: Avoiding the GPL by Znork · · Score: 1

      One link about the Lindows NDA would be: http://old.lwn.net/2002/0418/. The companies in question were Lindows and Corel. You may be able to find more on google; unfortunatly it seems it's much easier to find references to the problems than references to the peaceful resolutions.

      As these cases concern distributions, as software collections, it's not entirely an exact match for the case either; as collections carry a separate copyright on the collection in itself, it's possible to slap an NDA on the collection itself. The GPL terms would be fulfilled as long as any GPL components in the collection were not covered by the NDA and the source to those components were released. As it's hard to find good references on the resolution of the cases I cant tell if that's how it was dealt with.

      Anyways, I think you're right that the most damaging aspect of such issues would be the negative publicity anyway. I dont think it's possible to sidestep the GPL by hiding organizational borders under an NDA, but the decision on wether distribution has or has not taken place would be up to a court. There are even murkier areas there tho; what if you sign a consultancy contract with your prospective customers? Or what about cross-ownership between companies? In such cases it might come down to intent.

      Personally I doubt IBM would go down the proprietary Unix road again. They've learned the lesson that "proprietary and different" in general means "worse" in the Unix world; the resulting lack of ports and supported software means you lose more buisness than you gain through any proprietary nice features. Better for them to gain customers through competent consulting and good hardware. The only Unix company that didnt quite get that part is probably Sun, but they've gotten away with it by being the most common platform.

    7. Re: Avoiding the GPL by solprovider · · Score: 1

      The Lindows example is a definite "distribution" sold to many people who care about the GPL, the NDA was probably click-wrap, and Lindows needs the goodwill of the open source community.

      The GPL states:
      "You may not impose any further restrictions on the recipients' exercise of the rights granted herein."

      If IBM sold BigCompany a CD containing some software for the cost of the media ($1,000,000) and BigCompany promised not to request the source or redistribute the software, there is no one to complain about it. What could happen? Bruce calls IBM and says "You didn't give BigCompany the source." IBM says "They didn't want it." Richard calls BigCompany and says "You need the source." BigCompany says "We have outsourced every IT position to IBM. They have the source. We don't want it. And if we had it, we wouldn't give it to you anyway." No blood, no foul.

      ---
      Hey, we are back to the point of my original post about SCO revoking IBM's Unix license. The hypothetical situation was that IBM needed to replace AIX ASAP. IBM does not care about software. They do care about competitive advantage, and they hate SUN. They are willing to kill the best software available today just to attack SUN.

      Would they release their "proprietary and different" technology under GPL? Maybe.

      They could start their new OS with a BSD. Then they could keep it proprietary.

      But releasing it under GPL could be another attack on SUN. If SUN wants the changes, then SUN must recreate Solaris under GPL. Then SUN loses the advantage of their "proprietary and different" software. The end result is that there is no more proprietary Unix, and SCO goes down the drain.

      --
      I spend my life entertaining my brain.
  136. Better wash that pinky... by Ratface · · Score: 1

    After all the closing comment to the article was "Villain fingers pussycat"!

    You don't want to go popping that pinky in your mouth after that!!

    --

    A little planning goes a long way...
  137. Look at this quote! by TA · · Score: 1
    The guy says:

    "You can't take code based on a license you signed, change it a little and then give it away for free (as in the case of XFS from SGI)."

    He's saying that SGI got XFS from SCO and then "changed it a little". SGI should sue the guy for slander.

    TA

  138. What the... by rifter · · Score: 1

    SCO's arguments get curiouser and curiouser. And their lies get bigger. Consider, from the article:

    You can't take code based on a license you signed, change it a little and then give it away for free (as in the case of XFS from SGI). If SCO allowed companies to contribute derivative UNIX code to Linux and give it away for free, it would destroy the value of all other versions of UNIX, including SCO's own, not to mention the versions of UNIX made by SUN, HP, IBM, SGI, Sequent, Hitachi, Fujitsu, Siemens, and every other one of the 6,000 other licensees. Why would SCO not have such a provision in their licenses? This line of thinking is absolutely ludicrous.

    Hmmm, why would SCO give a license like the aforementioned? Well, of course they would never allow an irrevocable license! Never! And SCO's licenses would not allow you to create anything remotely related to the licensed product without giving it back to SCO along with your firstborn child! But this is all academic because it was not SCO that granted this license in the first place. It was AT&T, and even then there were addendums upon addendums over the years.

    As for the thing about XFS, I think it would be wise for SCO to shut their trap on that one. They are publicly claiming XFS is ripped off from code in SysV UNIX? Really?! That would explain why XFS is standard on all SCO and other UNIX implementations, wouldn't it? Oh I forget it is not. I wonder why that is? Could it be that SGI invented XFS themselves and put it in their Irix and Linux products? Nah! All innovation begins and ends with SCO!

    Man, they get more gall every time. The fact of the matter is that the current company has created no IP ever. It has built its business on IP it bought from other companies, and which it is trying to extend to include IP it could not begin to pay for. It wants to take by force what it cannot create or buy on its own. HMm.. sounds like their sole customer, Microsoft!