Slashdot Mirror


Linux vs. SCO: The Decision Matrix

hexidec writes "Haven't seen this here yet, though I may have missed it. Anyway... A group of Australian techies have put together an analysis matrix of the likelyhood of each SCO Unix claim being true, and what outcome would most likely result if so. Puts a lot of the various recent suppositions in one handy place."

457 comments

  1. Mirror for the slashdot effect by zubernerd · · Score: 5, Informative

    Ahhh... I feel the slashdot effect. Since this doc has tables, I put a mirror up. http://mirrors.tatay.org/lnxsco.html Cheers y'all!

    --
    Accentuate the positive, don't waste your mod points on the negative.
    1. Re:Mirror for the slashdot effect by Saint+Aardvark · · Score: 4, Informative
    2. Re:Mirror for the slashdot effect by dschuetz · · Score: 2, Insightful

      As long as we're mirroring it, anyone feel like transposing it from a 10-by-5 into a 5-by-10 table? Would make reading it MUCH easier.

    3. Re:Mirror for the slashdot effect by Anonymous Coward · · Score: 5, Insightful

      You will notice that the purported decision matrix (implying a logical document with conclusions deduced by scientifc logic from given hypotheses) says at the bottom of all possible outcomes 'linux is unaffected'.

      In case you hadn't guessed, this is far from the logical document the name suggests, but really a portrayal of one person's viepoint. The conclusion, namely that linux is unaffected in all cases is clearly false, as I can think, regardless of my own *opinions* of what chance such an event is said to have, that a judge *could* decide linux was infringing, and that it would be illegal to use it without paying Sco royalties.

      There are many pro-Linux assumptions such as that Sco opened the source by distribution Caldera made any putative copyright violation legal since they were doing it themselves. This is an assumption you cannot make without a legal decision.

      This document adds nothing to the debate - the only thing that will is a decision in a year or so's time in court, and in the mean time Sco can frighten people into not using Linux

    4. Re:Mirror for the slashdot effect by Anthony+Boyd · · Score: 1

      Geeze. Even the mirrors are getting slashdotted!

    5. Re:Mirror for the slashdot effect by geekmetal · · Score: 1

      Why not have slashdot mirror the link before posting the story?

      Although many users seem to be amused by this repeating event, it would be worth considering for the editors at slashdot.

      --
      There are two kinds of egotists: 1) Those who admit it 2) The rest of us
    6. Re:Mirror for the slashdot effect by Famatra · · Score: 1

      The best mirror technique that slashdot editors could use would be to use Freenet. It would cost nothing in bandwidth for Slashdot to mirror the content, and would be free advertisement for Freenet.

    7. Re:Mirror for the slashdot effect by mugnyte · · Score: 1

      Yeah, illegal to use Linux without paying royalties. Linux was born of OSS and could be again quite quickly. This could be just the first incarnation of the matrix.

      But overall, your post is simply an opinion - as (in)valid as the original table. IMHO, no educated judge or jury could accept SCO as the rights holder to Linux as a whole. SCO's unixware is dead weight in the business world.

    8. Re: Mirror for the slashdot effect by Black+Parrot · · Score: 5, Funny


      > > Ahhh... I feel the slashdot effect. Since this doc has tables, I put a mirror up.

      > And another, 'cos what the hell

      Could someone post a decision table for which link I should click?

      --
      Sheesh, evil *and* a jerk. -- Jade
    9. Re:Mirror for the slashdot effect by alienw · · Score: 4, Insightful

      that a judge *could* decide linux was infringing, and that it would be illegal to use it without paying Sco royalties

      This is not true. SCO cannot force anyone to pay royalties *unless* there are patents involved (there aren't). Any SCO-owned code in Linux (if it exists) could be removed and replaced, and no royalties would be needed. The only entity that might potentially have to pay is IBM, and that would be damages rather than royalties.

    10. Re:Mirror for the slashdot effect by dark-br · · Score: 5, Funny

      This "matrix" has been slashdoted, please "reload" :)

    11. Re:Mirror for the slashdot effect by Archie+Steel · · Score: 5, Informative

      I don't know...I do find the argument that SCO continued to distribute Linux after they knew (and, in fact, announced) that allegedly infringing code was in it to be quite compelling. The GPL is not just there for show, it is a license and as such is based on the same law as the one that makes other software licenses valid.

      Now, SCO's argument is that even if they did distribute Linux, they weren't aware of their code allegedly being in Linux. However, and this is important, they continued to distribute it afterward - and not a day or two, but a full month after disclosure. In other words, they knowingly distributed the offending code under the GPL, therefore releasing it to the Linux community. Note that this has, in fact, not much to do with the lawsuit against IBM, which is a breach of contract suit. SCO seems to have acknowledged that they can't legally sue Linux companies, which would be a violation of the GPL, and therefore Linux will be unaffected even if SCO wins against IBM. In other words, they're saying "the genie's out of the bottle, we can't put it back in, but at least we'll sue the one who let it out." That's how I read it, anyway. IANAL.

      --

      Reminder: find a new sig
    12. Re:Mirror for the slashdot effect by SpaceLifeForm · · Score: 1

      Gee, slashdotters are actually reading!

      --
      You are being MICROattacked, from various angles, in a SOFT manner.
    13. Re:Mirror for the slashdot effect by ichimunki · · Score: 1

      They have considered and rejected this idea. Read the FAQ.

      --
      I do not have a signature
    14. Re:Mirror for the slashdot effect by geekmetal · · Score: 1

      Thanks for that information, gotta run through that FAQ.

      --
      There are two kinds of egotists: 1) Those who admit it 2) The rest of us
    15. Re:Mirror for the slashdot effect by AstroDrabb · · Score: 4, Insightful
      The conclusion, namely that linux is unaffected in all cases is clearly false, as I can think, regardless of my own *opinions* of what chance such an event is said to have, that a judge *could* decide linux was infringing, and that it would be illegal to use it without paying Sco royalties.
      Not true. The open nature of Linux will make it VERY easy to remove any offending code and continue on. Sure, anyone that wants to continue to use the offending code will have to pay, however, I don't see anyone doing that. Also, the open nature of Linux will make it VERY easy to replace any funtionality that may have been removed. It is not illegal to reimplement any of the offending code. So, in this respect I think that this document is correct in its assumption that Linux will pretty much be unaffected.
      --
      If Tyranny and Oppression come to this land,
      it will be in the guise of fighting a foreign enemy. -James Madison
    16. Re:Mirror for the slashdot effect by cetan · · Score: 1
      --
      In Soviet Russia...michael would be rotting in Siberia!
    17. Re: Mirror for the slashdot effect by marklark · · Score: 1

      No need to click...

      The bottom line seems to be "Linux is unaffected."

    18. Re:Mirror for the slashdot effect by DataPath · · Score: 1

      Linux kernel developers are quite capable of backing out offending code, marginalizing the whole issue. Most of the technologies SCO referred to are of little relevance, or easily re-implemented.

      In the case of RCU, IIRC SCO was claiming ownership of related patents. SCO owns no such patents, but it's possible that under their contract with Novell they do have a right to those patents. SCO cannot exercise them until they have arranged with Novell to transfer ownership of those patents. If the patents never make it into SCO's hands, then the only problem is if the code was copied line-by-line. In which case it's easily re-implemented. If not, if I understand correctly, there are numerous other solutions to that hardware issue.

      --
      Inconceivable!
    19. Re:Mirror for the slashdot effect by Znork · · Score: 5, Insightful

      You're not quite correct. The GPL is actually not based on the same law that makes other software licenses valid. Most licenses for proprietary software are based on contract law, as they often attempt to restrict what you're allowed to do with the software beyond copyright limitations. This is what makes the whole "agreement" part necessary. Contract violations are rarely criminal, usually entail damages only, and are enforced in court by civil lawsuits.

      The GPL on the other hand is not entirely based on contract law; if it were, it could theoretically be challenged in court for some form of gain, and would quite possibly have been long ago. Instead, it deals entirely within the realm of allowing you to do things that you are not allowed to do within copyright law. As the GPL is the only thing granting you the right to modify and distribute the software you cannot distribute the software without adhering to the terms of the GPL (unless you obtain specific permission to do so from the copyright owner). Violating the GPL means you've violated copyright law by distributing copyrighted material without permission and that possibly means a criminal violation (depending on local law and things like wether it was done for profit), with entirely different consequences. This is one of the reasons you dont see any cases of companies challenging the GPL; few lawyers, I believe, would recommend engaging in something that may very well end up with their clients broke and in jail (and hey, wanna bet the RIAA and MPAA will try to lobby in the death penalty for copyright violations soon?).

      Due to these differences the GPL is probably more "valid" than most ordinary proprietary software licenses, and violations can carry far heavier penalties, depending on copyright law in the country where it took place.

    20. Re:Mirror for the slashdot effect by stilltwentysomething · · Score: 1

      Google's Cache:

      http://www.google.ca/search?q=cache:mkRx2aiBJC0J :w ww.cybersource.com.au/users/conz/linux_vs_sco_matr ix.html+&hl=en&ie=UTF-8

    21. Re:Mirror for the slashdot effect by Anonymous Coward · · Score: 0

      Any SCO-owned code in Linux (if it exists) could be removed and replaced, and no royalties would be needed.

      Huh? That's complete bollocks. Even if you replace the code immediately, you still have to pay royalties for your past infringements or be sued.

    22. Re:Mirror for the slashdot effect by Spazmania · · Score: 2, Insightful

      a judge *could* decide linux was infringing, and that it would be illegal to use it without paying Sco royalties.

      No, he couldn't. He *could* decide the Linux kernel version whatever to version whatever are infringing and that folks are enjoined from using or distributing *those versions* since the breach of SCO's IP would force the cancellation of the GPL contract on them.

      After that, it becomes a cat and mouse game, with SCO trying to collect from alleged infringers, Linux authors trying to collect from SCO for infringement, etc. Meanwhile, the infriging code having necessarily been identified, its removed from Linux, a non-infringing version is released and Linux as a whole motors on.

      It would, however, be wise to make sure that none of your daemons explicitly identify the Linux version you're running.

      --
      Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
    23. Re:Mirror for the slashdot effect by cirkus · · Score: 1

      -Ahhh... I feel the slashdot effect. Since this doc has tables, I put a mirror up. http://mirrors.tatay.org/lnxsco.html Cheers y'all!

      It seems that even the matrix can be slashdotted

    24. Re:Mirror for the slashdot effect by deanpole · · Score: 1

      Not only that. More recently SCO annouced its customers need not fear litigation, thus effectively granting them a license. This is a licence by the (supposed) copyright owner for use in conjunction with GPL code. GPL'ed for one is GPL'ed for all.

    25. Re:Mirror for the slashdot effect by Anonymous Coward · · Score: 2, Interesting

      Even if you replace the code immediately, you still have to pay royalties for your past infringements or be sued.

      Ahh, no. Read a bit about the doctrine of laches.

      Best case scenario (for SCO):
      if a judge decided that SCO's allegations were true, and decided that royalties need to be paid, then the royalties would begin at the time that SCO informed them..

      Worst case scenario (for SCO, assuming they win):
      Judge rules that because SCO refused to tell anyone where the alleged infringing code is, that the code has no value, and the Linux users don't have to remove it.

      Most probable scenario:
      Since SCO refuses to disclose the alleged infringing code, a jude would most likely rule the code in question has no monetary value, so SCO doesn't get any royalties, but it still has to be removed by a set date.

      Either way, the absolute best thing that can happen for SCO is that they gain nothing.

    26. Re:Mirror for the slashdot effect by Archie+Steel · · Score: 1

      Very interesting. I stand enlightened.

      --

      Reminder: find a new sig
    27. Re:Mirror for the slashdot effect by Old.UNIX.Nut · · Score: 1

      > There are many pro-Linux assumptions such as
      > that Sco opened the source by distribution
      > Caldera made any putative copyright violation
      > legal since they were doing it themselves.
      > This is an assumption you cannot make without
      > a legal decision.
      > This document adds nothing to the debate.

      YES ... thanks!!!

      Even if the person(s) who did this were an IP lawyer(s) in AU that would mean nothing in the USA where laws are VERY different.

      I could find no mention of "qualifications" on the site in question, so it might be safe to assume this person(s) has none. Somone might want to mention this to the author(s).

      Don't you just love people with absolutely no qualifications rendering legal opinions that are often pure BS???

    28. Re:Mirror for the slashdot effect by Mostly+a+lurker · · Score: 1
      Now, SCO's argument is that even if they did distribute Linux, they weren't aware of their code allegedly being in Linux. However, and this is important, they continued to distribute it afterward - and not a day or two, but a full month after disclosure.

      If you accept their argument that the company is so blitheringly incompetent that they did not realise that major parts of UnixWare were in Linux, it is surely consistent to accept an argument that they did not realise they has web servers that were distributing that source code.

    29. Re:Mirror for the slashdot effect by plierhead · · Score: 1
      Not true. The open nature of Linux will make it VERY easy to remove any offending code and continue on. Sure, anyone that wants to continue to use the offending code will have to pay, however, I don't see anyone doing that. Also, the open nature of Linux will make it VERY easy to replace any funtionality that may have been removed. It is not illegal to reimplement any of the offending code. So, in this respect I think that this document is correct in its assumption that Linux will pretty much be unaffected.

      And a big 'ol NOT TRUE right back at ya. Sure, the situation could be put right, so Linux will be fine in the future, but if wrongdoing is proved SCO could certainly go back and look for damages for the period that the "illegal" code was in use. Just because you make it right doesn't mean no harm took place in the past.

      --

      [x] auto-moderate all posts by this user as insightful

    30. Re:Mirror for the slashdot effect by jrumney · · Score: 1
      Now, SCO's argument is that even if they did distribute Linux, they weren't aware of their code allegedly being in Linux. However, and this is important, they continued to distribute it afterward - and not a day or two, but a full month after disclosure.

      They are still distributing GPLed code which they beleive to contain their IP, even now. From http://www.sco.com/scosource/linuxqanda.html:

      Q: What Linux activities at SCO are specifically being suspended?
      A: SCO will suspend all new customer sales of Linux products. SCO will continue to honor all contractual obligations with existing customers including product updates, service, and support
    31. Re:Mirror for the slashdot effect by japhmi · · Score: 1

      Most probable scenario:
      Since SCO refuses to disclose the alleged infringing code, a jude would most likely rule the code in question has no monetary value, so SCO doesn't get any royalties, but it still has to be removed by a set date.


      Um... if SCO refuses to disclose the code, and the judge then orders it to be removed, then how can anyone remove it without first being told what code to remove?

      --
      "Giving money and power to government is like giving whiskey and car keys to teenage boys" P. J. O'Rourke
    32. Re:Mirror for the slashdot effect by jak163 · · Score: 1

      If they win a judgment that there was infringement, they can sue for damages. The impact on the Linux community would not be restrictions on future implementations of Linux, but financial.

    33. Re:Mirror for the slashdot effect by jak163 · · Score: 1

      Hrm I should add that these damages would precede their knowing distribution of the code under GPL as asserted in this decision matrix, but conversely could include the value of all subsequent lost business. This is based on the assumption of a favorable court decision, the likelihood of which is another matter.

  2. SCO Matrix... by TWX · · Score: 5, Funny

    We'll cast Hugo Weaving as SCO, Keanu Reeves as Tux, and Laurence Fishburne as IBM. Carrie-Anne Moss would make an excellent IBM, since IBM's products are fairly sleek and sexy right now, and I'd really like to get into IBM...

    --
    Do not look into laser with remaining eye.
    1. Re:SCO Matrix... by TWX · · Score: 1

      Wow. I so totally screwed that up. Fishburne was supposed to be the FSF... Carrie Anne Moss would be good as IBM.

      And in the words of Agent Smith, "Dammit."

      --
      Do not look into laser with remaining eye.
    2. Re:SCO Matrix... by Anonymous Coward · · Score: 0

      And Novell as Cypher?

    3. Re:SCO Matrix... by Anonymous Coward · · Score: 0

      And the Japanese tub girl is IBM, and she knows no English, all she can say is "IBM.. IBM..." as she craps all over Carrie-Ann Moss.

    4. Re:SCO Matrix... by hendridm · · Score: 5, Funny

      > Carrie-Anne Moss would make an excellent IBM, since IBM's products are fairly sleek and sexy right now, and I'd really like to get into IBM...

      That is quite possibly the geekiest thing I've ever read on Slashdot...

      Can't say I disagree though ;)

    5. Re:SCO Matrix... by Xformer · · Score: 1

      You're thinking about Microsoft. Cypher ended up betraying to the machines, remember? Novell's been trying to get SCO to calm down, since they actually own the rights to what's being disputed.

      --
      All I want is a kind word, a warm bed and unlimited power.
    6. Re:SCO Matrix... by Llywelyn · · Score: 4, Funny

      "and I'd really like to get into IBM.."

      One difference, your chances with IBM are probably a lot better than they are with Carrie-Anne Moss--such is life.

      Sigh.

      --
      Integrate Keynote and LaTeX
    7. Re:SCO Matrix... by Anonymous Coward · · Score: 0

      Must have been a Freudian slip. Maybe you really want to get into Laurence Fishburne. ;-)

    8. Re:SCO Matrix... by Anonymous Coward · · Score: 0

      No way! RSA would be Cypher!

    9. Re:SCO Matrix... by canajin56 · · Score: 5, Funny
      Keanu Reeves as Tux
      You're best leaving Tux as a plush toy. Better actor AND more marketable
      --
      ASCII stupid question, get a stupid ANSI
    10. Re:SCO Matrix... by flok · · Score: 1

      Ok, I just laughed my brain out.
      Thank you :o)

      --

      www.vanheusden.com - home of Multitail, HTTPing, CoffeeSaint, EntropyBroker, rsstail, bsod, listener, nagcon, nagi
    11. Re:SCO Matrix... by samhalliday · · Score: 1

      no ways; Fishburne would be RMS!!! what about all that religous sheeat going down in Zion... all hail the emacs which will save us...

    12. Re:SCO Matrix... by CausticWindow · · Score: 1

      Oh my fucking god. I just realised that I won't be able to do linear algebra ever again. That stupid pathetic action movie has ruined a part of math for ever, and it's not even remotely connected to maths.

      Grow the fuck up. Take some hard core hallucinogens. Understand it all. Forget the fucking "Matrix" kang foo films.

      --
      How small a thought it takes to fill a whole life
    13. Re:SCO Matrix... by G-funk · · Score: 1

      I believe you'll find

      "Can get into carrie-anne-moss" and
      "Can get into IBM"

      mutually exclusive :)

      --
      Send lawyers, guns, and money!
  3. Article is slashdotted.. by Gortbusters.org · · Score: 1

    but let's just cut to the chase: Linux wins. SCO might give IBM a bloody nose, but they're not gonna knock that giant down.

    --
    --------
    Free your mind.
    1. Re:Article is slashdotted.. by crazyphilman · · Score: 5, Funny

      Actually, it's more like this:

      IBM, Red Hat, and SuSE are bikers hanging out at a seedy bar in Southern California, by the shore. Their harleys are parked out front, all choppers, gleaming and evil looking. Currently, IBM and Red Hat are playing a traditional game: each holds a lit cigar to his forearm while SuSE counts the seconds, with two twenty dollar bills at stake. A few feet away, the BSD brothers are playing cards at an outside table, a quart of Mexican tequila and a bunch of shotglasses next to the deck. Periodically, they throw back a shot. Their rusty Jeep Renegade sits nearby. Suddenly, there's a little lawnmower sound. A go-kart with a broken muffler pulls up, bumping into the Harleys and knocking them down. IBM, Red Hat, and Suse ferociously stride over and bellow.

      "HEY, MAN! THOSE ARE OUR BIKES!"

      A fat little kid wearing a shirt with wide horizontal stripes and a pair of bermuda shorts held up by orange suspenders jumps out of the go-kart and saunters over to the bikes. He's got freckles, bright red hair, and triple-thick glasses. He's obviously not "all there".

      Fat kid: "Hi. I'm SCO. Motorbikes suck; I drive a go-kart." (kicks the nearest bike, breaking the headlight). If it wasn't for my Go-Kart technology, you wouldn't even HAVE these bikes. You should buy me some beers in appreciation."

      IBM: (seething). "That was my bike. Kid, you really shouldn't have done that." Red Hat: (shakes head). SuSE: (muttering) "Gott in Himmel" (laughs)

      IBM walks over, grabs the kid by the suspenders, and lifts him clear off the ground, bouncing him up and down while looking him over. Then, he tosses the kid way up in the air, catching him on the way down by his underwear waistband and yanking upwards with both hands. With a great stretching sound, the drawers pull all the way over the kid's head. IBM lets go, and they snap into place.

      Everyone: MUHAHAHAHAHAHAH! Red Hat: "Hey, IBM, do that shit again!" SuSE: "Funny!" The BSD brothers: "huh huh huh huh -- HE said SHIT!"

      SCO (through his underwear): "You buncha creeps! My grandfather used to own this land. I'll tear down this bar and make you take your alky bullshit somewhere else! And, what's up with that biker gay-chic thing?"

      IBM: "Oh, my lawd, he went there." Red Hat: "Oh, you didn't..." SuSE: "Uh oh..." BSD Brother number 1: "Oh, boy, here we go."

      IBM leans over, grabs the kid by the ankles, and heads to the outhouse. He kicks the door open, goes in, and the door slams.

      (from inside)
      SCO: Noooooooooo!
      (SPLASH, SPLASH, SPLASH).

      IBM comes walking back out, without SCO. He takes a long pull from the tequila bottle.

      IBM: "Damn." BSD Brothers, in unison: "What, what happened, man?" IBM: "Damn..." Red Hat: "Hey, where'd the brat go?" SuSE: "Yeah, you gave him the swirly, right?" IBM: "Yep." Red Hat: "So... ?" IBM: "He's a slippery little bastard when he gets wet. Popped right out of my hands and went down into the latrine!"

      Everyone: "NO WAY!"

      IBM: "Yeah... Poor little bastard. Ah, well. What can you do? Maybe he'll swim back up outta it."

      (about a minute later)

      SCO flops out of the toilet seat, landing on the ground in front of the toilet, covered in green goo.

      SCO: "URH! URG! CTHULU FLAGNTH!" Red Hat: "Hey, boys, somethin' ain't right about that kid, man. It looks like he's growin' fins."

      Everyone looks. SCO has turned into a weirdo fish-man.

      SCO: "CTHULU FLAGNTH!" IBM: "Well, whaddaya know?"

      SCO runs across the parking lot, and leaps off the cliff into the sea.

      SCO: "CTHULU FLAAAAAAAAAAAGNTH!" (SPLASH)

      IBM, looking over the edge. "Well, I guess that's about that." Red Hat: "You don't see THAT every day." SuSE: "Pass me that there tequila bottle, ok?"

      (fade to black)

      You all thought I was going to get into the Microsoft/Cthulu thing, didn'tcha? Ha! Fooled ya!

      --
      Farewell! It's been a fine buncha years!
    2. Re:Article is slashdotted.. by Anonymous Coward · · Score: 0

      Funny, but, I thought it was "Cthulu ftaghn"?

    3. Re:Article is slashdotted.. by sudog · · Score: 1

      It is, of course. :)

    4. Re:Article is slashdotted.. by jeffkjo1 · · Score: 1

      Man.....
      Somebody's got an overactive imagination.

    5. Re:Article is slashdotted.. by the-build-chicken · · Score: 1

      dudes been smoking again

  4. Slashdotted by dimmu · · Score: 2, Informative

    It looks like the site is already slashdotted. I have mirrored the page at http://www.sais.nl/linux_vs_sco_matrix.html

    --
    -- Cliff Albert
  5. FUD factor not included by wilfie · · Score: 2, Insightful

    It's good that the FUD is being fought, but there could still be an effect which is not accounted for here.

  6. google cache by Anonymous Coward · · Score: 0, Redundant

    http://216.239.57.104/search?q=cache:mkRx2aiBJC0J: www.cybersource.com.au/users/conz/linux_vs_sco_mat rix.html+&hl=en&ie=UTF-8

    1. Re:Google cache by Anonymous Coward · · Score: 0

      Did we really need a 3rd post linking to the google cache??

    2. Re:Google cache by anthony_dipierro · · Score: 1

      No, we most certainly didn't.

  7. google cache version by DOsinga · · Score: 0, Redundant

    Hi,

    Site seems down already. Read it at google:

    1. Re:google cache version by DOsinga · · Score: 1

      Oops slashdot didn't like my html:

      http://216.239.37.104/search?q=cache:mkRx2aiBJC0 J: www.cybersource.com.au/users/conz/linux_vs_sco_mat rix.html+&hl=en&ie=UTF-8

    2. Re:google cache version by Anonymous Coward · · Score: 0

      Haha karma whoring asshole forgot the link. Rot in hell ass...

  8. Slashdotted by rabbit994 · · Score: 0, Redundant

    Looks like it was slashdotted already. It basically says we all knew along. SCO is full of S*** and going to be laughed out of court.

  9. Appropriate by ElectricPoppy · · Score: 1

    SCO's reality fits in quite well with the whole notion of the Matrix. Replace Agent Smith and friends with a bunch of rabid lawyers. Though I can't really picture Torvalds doing Martial Arts.

    1. Re:Appropriate by adilsonoliveira · · Score: 2, Informative

      Maybe it's not difficult: Linus' wife, Tove, *is* a martial arts expert (Finland's karate champion, IIRC).

      --
      Faith can move mountains. I prefer dynamite.
    2. Re:Appropriate by Anonymous Coward · · Score: 0

      Ok, GIMP wizards! Now's youre chance to shine. Bring us Matrix Reloaded screen captures with Linus' face oover Reeves', and Darl's over Smith's in the Big Brawl.....

    3. Re:Appropriate by CraigV · · Score: 1

      His wife can stand in for him. She's something like 5-time Finnish karate champ.

    4. Re:Appropriate by VP · · Score: 1

      Though I can't really picture Torvalds doing Martial Arts.

      That's why he married the Finnish national karate champion ;-).

    5. Re:Appropriate by Theatetus · · Score: 1
      Though I can't really picture Torvalds doing Martial Arts.

      Maybe not Linus, but his wife sounds good enough at karate (or was it Tae Kwan Do?) to do the fight scenes.

      --
      All's true that is mistrusted
    6. Re:Appropriate by ElectricPoppy · · Score: 3, Funny

      I guess Linus could be Morpheus. Or maybe the kid with the spoon. Calmly sitting on the floor and saying, "there is no copyright violation".

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

      SCO's reality fits in quite well with the whole notion of the Matrix. Replace Agent Smith and friends with a bunch of rabid lawyers. Though I can't really picture Torvalds doing Martial Arts

      Linus Torvalds: "I know code-fu!!??!!"

    8. Re:Appropriate by caluml · · Score: 1

      Mrs Torvalds vs. Mrs Gates, anyone?
      Mud, foam, and oil should all play their part in it.

    9. Re:Appropriate by vsprintf · · Score: 1

      His wife can stand in for him. She's something like 5-time Finnish karate champ.

      McBride testifies: "IBM gave away our heritage, and Linus took it because he's lousy at protecting IP".

      Mrs. Torvalds starts across the courtroom and breaks Sontag's spine when he tries to stop her and then messes up McBride's moussed hair before snapping his neck.

      The judge rules it a double suicide.

      You gotta love happy endings.

  10. it's dead by Anonymous Coward · · Score: 0, Troll

    thanks subscribers! You fucked it for the rest of us!

  11. first post? by y2dt · · Score: 0

    the site is slashdotted and there aren't even any posts. doesn't anybody post BEFORE reading the article anymore??

    =)

    1. Re:first post? by dimmu · · Score: 1

      Well actually people can read the article before they CAN post comments. Thanks to Slashdot subscription (which is always a nice way to read slashdot articles without slashdotted links :)

      --
      -- Cliff Albert
  12. Matrix by darth_MALL · · Score: 3, Funny

    Is there a site listing a matrix of the possible links that could survive a slashdotting?

    1. Re:Matrix by Lane.exe · · Score: 2, Funny
      *menacing look*

      But what good is freedom when you don't... have a brain?

      --
      IAALS.
  13. Anothr example of... by cruppel · · Score: 5, Insightful
    ...blind speculation, I think.

    Those ratings at the top indicating the likelihood of these allegations (or whatever you want to call them) don't really mean anything. They're just speculation and opinion, much like the 17,000 /. comments dealing with this whole deal. It reads nice and legal-sounding, but to me it looks like a table formatted thread straight off this site.

    1. Re:Anothr example of... by MeanMF · · Score: 4, Insightful

      blind speculation, I think

      I would lean more towards wishful thinking than blind speculation, but I think you're on the right track. They're not basing this on any actual evidence because the evidence has not been made available to the public yet.

    2. Re:Anothr example of... by no+reason+to+be+here · · Score: 1

      They're not basing this on any actual evidence because the evidence has not been made available to the public yet.

      Probably b/c there is no actual evidence.

    3. Re:Anothr example of... by Anonymous Coward · · Score: 0

      what .. information from The Intarweb being
      pure speculation and worthless opinion and
      probably being more full of holes than your
      girlfriend's diaphragm? ..

      it Can't be True

      especially not when it has gone through the rigors
      of being validated for posting on slashdot

      because we all know how competent the editors
      are

      oh yeah

    4. Re:Anothr example of... by smoondog · · Score: 2, Insightful

      I agree. Although the info (not speculation) in the individual cells is interesting, everything else is (biased) speculation. This is one of the dumber /. articles in a while, IMO. They say that the liklihood that "There is no infringing code" is "Most Likely." HTF do they figure that? Sure they haven't released any code, but frankly, it is in their best interests *not* too, either way. Why give a potential legal defense time to grow on /. and in the hands of IBM's lawyers? I would point wild accusations without releasing evidence, too, even if I was right. I also think that it is pretty likely that some code leaked in (probably by accident). SCO may be annoying serial legal leaches, but they aren't going to make up completely untrue stories to get their way. At some point someone would find out and the management team would be personally liable.

      -Sean

    5. Re:Anothr example of... by shadow303 · · Score: 1

      Well, what do you expect from people who call a table a matrix? They're probably lucky to even have a clue of what is going on.

      --
      I've got a mind like a steel trap - it's got an animal's foot stuck in it.
    6. Re:Anothr example of... by gpinzone · · Score: 1

      I would lean more towards wishful thinking than blind speculation

      They're all strawman arguments made by a biased observer. So no, it's not blind speculation. It's just plain misleading. BTW, does the person who created this list have a law degree? I'm just curious how s/he comes to the conclusion that the few number of days between the time that SCO found the problem and pulled their Linux distrbution equates with SCO gifting the allegedly stolen code under the GPL.

    7. Re:Anothr example of... by civilizedINTENSITY · · Score: 1

      Actually the fact that SCO continued to distribute is well documentated. Thats a fact. BSD's continued existence after the ATT mistake is also a fact, futher muddying SCO's claim. Historical fact. Rather that "blind speculation" I'd suggest that claims were laid next to facts. Facts are evidence.

    8. Re:Anothr example of... by civilizedINTENSITY · · Score: 1

      What makes it "unlikely" is how SCO is basing their claim on whats "their" code.

      'We believe that UNIX System V provided the basic building blocks for all subsequent computer operating systems, and that they all tend to be derived from UNIX System V (and therefore are claimed as SCO's intellectual property).'

      "In more detail, SCO claim to have full IP rights to several major components of any high-spec OS:

      * JFS (Journalling File System).
      * NUMA (Non Uniform Memory Access).
      * RCU (Read-Copy Update).
      * SMP (Symmetrical Multi-Processing).

  14. Hmmm... by Tiresias_Mons · · Score: 2, Interesting

    ...all the linux is unaffected conclusions, while probably right, make is seem a little like the following line of analysis:

    1) Something here
    2) ...
    3) Profit!

    I don't know, just seemed like kinda a cheesy chart to me, although a lot of the points he made were decent enough, the analysis seemed cheesy.

    --
    "But that's just my opinion, I could be wrong" - Dennis Miller
    1. Re:Hmmm... by GreatOgre · · Score: 1

      I don't know, just seemed like kinda a cheesy chart to me, although a lot of the points he made were decent enough, the analysis seemed cheesy.

      I agree. Especially since almost every argument comes back to "SCO released this after discovering the infringement."

  15. Pointless effort by Anonymous Coward · · Score: 5, Informative

    Why host the page on your own site when google already HAS THE CACHE

    1. Re:Pointless effort by zubernerd · · Score: 4, Funny

      I wanted to see how long it took for my link to be saturated. Can't do that with google.

      --
      Accentuate the positive, don't waste your mod points on the negative.
    2. Re:Pointless effort by Anonymous Coward · · Score: 0

      Why not just search for "How long will it take for me to saturate my link?" on google?

    3. Re:Pointless effort by Saint+Aardvark · · Score: 1

      Amen, brother!

    4. Re:Pointless effort by Anonymous Coward · · Score: 1, Insightful

      WHy don't the editors just link to the Google cache instead of the original page? Some sites are so small, this should be obvious.

    5. Re:Pointless effort by ComaVN · · Score: 1

      That's... interesting. Here are some of the results I got:

      Mulitcultural Long Hair Care Forum
      The Moon Landings Were NOT Faked
      and, best of all:
      PoopReport.com: Your Source for Poop.

      --
      Be wary of any facts that confirm your opinion.
    6. Re:Pointless effort by Delirium+Tremens · · Score: 1

      Excuse me for asking, but if he does not host the page anymore, then isn't it likely that Google will purge its own cached copy?

    7. Re:Pointless effort by jazman_777 · · Score: 1
      I wanted to see how long it took for my link to be saturated. Can't do that with google.

      For some reason this reminds me of the joke: what did the sadist do to the masochist? Nothing.

      --
      Slashdot: Failed Car Analogies. Amateur Lawyering. Anecdote Battles.
    8. Re:Pointless effort by Anonymous Coward · · Score: 0

      Masochist: Beat me! Beat me!
      Sadist: You wish!

  16. Finally, a decent SCO Analogy by Anonymous Coward · · Score: 0


    This guy heading up SCO is like a 1 year old who just keeps packing his diaper, over and over. However, no one changes him. He just gets stinkier and stinkier and pretty soon he's got poop shooting up his back and down both legs.

  17. Linux, Sco, Matrix... by Anonymous Coward · · Score: 0

    Classic SLashdot!

  18. Matrix? by Raster+Burn · · Score: 5, Funny

    Morpheus: SCO is everywhere. It is all around us. Even now in this very room. You can see it when you look out your operating system. Or when you boot your AIX box. You can feel it when you surf the web. When you compile your kernel. When you mount your filesystems. It is the lawsuit that has been pulled over your eyes to blind you from the truth.

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

      I dont get it. Do all super-geeks like you talk like that?

    2. Re:Matrix? by anshil · · Score: 1

      I counted already the posts until this very predictable joke appears :)

      --

      --
      Karma 50, and all I got was this lousy T-Shirt.
    3. Re:Matrix? by tomstdenis · · Score: 1

      By far the funniest thing I have read all day.

      Congrats.

      --
      Someday, I'll have a real sig.
    4. Re:Matrix? by darkov · · Score: 1

      Morpheus: If you believe that SCO has your code, then SCO has your code. If you believe that all your Unixes belong to them, then they have all your Unixes. In SCO, if you get sued by SCO, you lose your shirt... but it doesn't have to be that way...for Oracle spoke of...

    5. Re:Matrix? by civilizedINTENSITY · · Score: 1

      Amen, brother! Thats the best Matrix metaphor I've seen on slashdot yet.

  19. Missed.... by GI+Joe+51 · · Score: 1

    The seemed to missed the 'Proven' one of 'This debate has been going on so long, we just want the damn thing to be over!

  20. Jesus... by tevenson · · Score: 2, Funny

    I, seriously, just got the biggest headache ever. SCO must be desperate for something to do as of late.

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

      and if you look at their stock, I totally don't understand why it's as high as it is:
      11.811

      *shrug*

  21. It becomes easy once you realize... by reimero · · Score: 5, Funny

    There is no SCO.

    --

    ----------

    Something clever
    1. Re:It becomes easy once you realize... by Anonymous Coward · · Score: 0

      and no infringing code.

    2. Re:It becomes easy once you realize... by Anonymous Coward · · Score: 0

      and no weapons of mass destruction

    3. Re:It becomes easy once you realize... by Anonymous Coward · · Score: 0

      but there are Weapons of ASS Destruction ;P

    4. Re:It becomes easy once you realize... by Anonymous Coward · · Score: 0

      I can see it clearly now.
      Bush just confused ass and mass (and look at him it's the same thing)
      But even if it doesn't justify a war, it is still illegal to download weapons of ass destruction.

    5. Re:It becomes easy once you realize... by Anonymous Coward · · Score: 0

      There is no SCO...

      there is only Microsoft.

    6. Re:It becomes easy once you realize... by The+Cydonian · · Score: 1
      Indeed, (in Laurence Fishburne's voice)
      Unfortunately, no one can be told what the infringing code is. You'll just have to see it for yourself.
      Baah, too many Matrix jokes for the day. :-|
  22. One trick pony table. by Godeke · · Score: 4, Insightful

    The argument contained within this table leans heavily on the "continued distribution of GPL code after realization of the consequences thereof". I believe they will try the "it took us time to remove it" argument, but that's pretty weak when you consider that the time elapsed isn't just the time from the public lawsuit, but that there must have been internal discussion as well...

    --
    Sig under construction since 1998.
    1. Re:One trick pony table. by Error27 · · Score: 2, Insightful

      Some of their quotes in interviews indicate that they didn't understand the implications of the GPL until around May 19. (Without the code being under the GPL, their actions would have merely been unethical instead of illegal).

      The other interesting thing is that they are still distributing the code from their website.

    2. Re:One trick pony table. by GoofyBoy · · Score: 3, Insightful


      This is the weakest point in the matrix, they seem to think that courts are not influenced by arguments. SCO, if their lawyers are good enough, can claim that the time lasped was "reasonable" or something else to get around it.

      Even if you think that its a strong case either way, its what the courts decision which is what matters for businesses.

      --
      The surprise isn't how often we make bad choices; the surprise is how seldom they defeat us.
    3. Re:One trick pony table. by Morel · · Score: 2, Insightful

      Weaker still when you take into accout the fact that the GPL has never been proved legal in a court of law. The FSF may think the GPL is strong enough, but others differ.

      Cheers,

      Morel

    4. Re:One trick pony table. by arkanes · · Score: 1

      If thats truly the case, I certainly theres a shareholder lawsuit against McBride, because thats grossly negilgent. Or even if he just says tahts the case.

    5. Re:One trick pony table. by Quino · · Score: 1

      the link you offerred as differing actually supports it:

      "But legal agreements are supposed to matter in our system. Just because the GPL turns the idea of intellectual property somewhat around doesn't make it less valid."

      He does mention that he knows of some people that seem to think the GPL isn't a good idea, but wraps up the article with the above sentence.

    6. Re:One trick pony table. by jedidiah · · Score: 3, Informative

      Certain arguments are simply too laughable to be taken seriously. The notion that one should have ample time to continue to be in breach of a contract is fundementally abusurd. One should not reasonably expect ANY judge to accept such argumentation.

      Besides, such argumentation would undermind SCO's claims of damages.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    7. Re:One trick pony table. by tlk+nnr · · Score: 2, Interesting

      The argument contained within this table leans heavily on the "continued distribution of GPL code after realization of the consequences thereof".

      The whole block is bogus:
      SCO makes two independant claims: that IBM violates their contract with SCO, and that Linux contains source code from the SCO Unix code base without authorization. They began with their lawsuit against IBM on March 6th, and at that time SCO board members said that this is about SCO-IBM, not about Linux.
      The claims that the kernel contains copyright violations came later, I don't remember the exact date.
      Additionally, SCO distributes a version of the 2.4 kernel, and that it's possible that the infringing code is only in 2.5.

      _If_ there is a chance to claim that SCO placed their IP under the GPL by knowingly distributing, then it is the support program for their current customers: SCO said that they will continue to support them, and on the Usenix conference session about SCO-Linux one of the speakers mentioned that the source is still avaliable from their support download site.

      Are there any SCO Linux customers around? Can anyone download the kernel sources and check if COPYING is still inside?
    8. Re:One trick pony table. by Godeke · · Score: 2, Interesting

      Hmmm. I don't think that the courts would put up with "we were distributing this code under the GPL, but we didn't read it first" defense. Ignorance is one thing courts rarely factor in, and in the case of corporate contracts, almost never. Deception is a different case, but I doubt anyone can say the GPL is deceptive - it states its intentions pretty clearly.

      The fact that they had the GPL on the code makes the understanding of the ramifications a moot point. What SCO has said was they didn't know their code was in the product, and that *might* fly. The fact it was left in distribution for probably ~3 months after such discovery (assuming it took a month to fire the lawyers up and do the groundwork) is the interesting factor.

      I was commenting more on the fact that this was about the *only* interesting thing the table had to say.

      --
      Sig under construction since 1998.
    9. Re:One trick pony table. by Anonymous Coward · · Score: 0

      The people behind the lawsuit are management. They can feign ignorance (which shouldn't be hard since they are ignorant).

      "Your honor, until May 14, we did not realize that our Linux distribution also contained the infringing code. We believed that only AIX contained the infringing code. As soon as we learned of the infringement in Linux, the code was immediately removed from our website and we thoughtfully warned the Linux community of the problem. It is clear to us that IBM initially copied code into their AIX operating system and then later copied it into the Linux kernel without permission."

    10. Re:One trick pony table. by GoofyBoy · · Score: 2, Informative

      >The notion that one should have ample time to continue to be in breach of a contract is fundementally abusurd.

      The keyword here is "Reasonable".

      All they have to do is prove to a judge, a human being, that in the complex legal system that they acted "reasonable", then there is a chance that the time elasped is not a valid point.

      If a case gets to the courts, anything could happen.

      --
      The surprise isn't how often we make bad choices; the surprise is how seldom they defeat us.
    11. Re:One trick pony table. by Svartalf · · Score: 1

      Per the statements made by Stowell, they knew about the alleged code infringement since the end of last year. That places it in an October/November/December timeframe. They had their reasonable amount of time from that point until they filed (anywhere from 3-5 months...) and they proceeded to distribute everything for at least another 2-3 months past that.

      It's not going to wash in a court that they took anywhere from 4-7 months to finally decide to take action with regards to the source, especially when they filed a case against IBM over the same in the middle of the 4-7 month timeframe. While they can still claim that they didn't license the code under the GPL, they can't claim it's legit to ship it under the current state of things if there IS SCO code not licensed under the GPL in the Linux kernel.

      SCO's got a nasty problem if what they've been saying is true- and it doesn't involve them unknowingly GPLing the code (which can't technically happen...). The license grant of the GPL is revoked if you knowingly distribute code that is not GPLed intermixed with GPLed code. They KNOWINGLY did it, stating IN PUBLIC that it was okay for THEM to do so since it was their IP to begin with. This translates into something like 4-6+ months of infringement of the Linux kernel sources because they no longer had a license to distribute the code in question.

      There's already several suits in progress that address that issue with SCO.

      --
      I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
    12. Re:One trick pony table. by MuParadigm · · Score: 1

      Since SCO removed it's Linux distro *before* the suit was filed on June 16, I doubt that its continued presence after the initial termination *warning* will be a factor.

    13. Re:One trick pony table. by Znork · · Score: 1

      It's worse than that for SCO. As long as they are shipping updates and such to their customers for openlinux they cant even cease to distribute the code or they'd be in violation of the GPL, nor can they restrict the terms on the code in question (and the source is still available for ftp). If they have contracts with customers that could be difficult to do, especially since they would have to say they wanted to break the contract because they're having internal intellectual property disputes within the company and arent sure they have the right to ship the code they claim to own...

      They're really managing amazingly well at shooting themselves in the foot.

    14. Re:One trick pony table. by roystgnr · · Score: 1

      As soon as we learned of the infringement in Linux, the code was immediately removed from our website and we thoughtfully warned the Linux community of the problem.

      Their removal postdates their "thoughtful warnings" by months.

    15. Re:One trick pony table. by Anonymous Coward · · Score: 0

      "There's already several suits in progress that address that issue with SCO"

      Any details? Sounds like SCO's opened a can of worms...

    16. Re:One trick pony table. by Grax · · Score: 1

      The Linux distro is not the issue here. The Linux kernel is the issue. SCO continues to distribute the Linux kernel source to this day.

      Here are the instruction for downloading the kernel source from SCO directly.
      Kernel Source provided by SCO

      Make sure you are in the directory you want to extract the kernel source to
      rpm2cpio linux-2.4.13-21S.src.rpm | cpio -i
      tar -xvjf linux-2.4.13.tar.bz2

      You now have a perfect copy of the kernel source in the linux directory, just as if you had downloaded from kernel.org and extracted it yourself.

    17. Re:One trick pony table. by Grax · · Score: 1

      The rpm kernel source here contains the exact same tar.bz2 file that you can download from kernel.org.

    18. Re:One trick pony table. by Anonymous Coward · · Score: 0

      if their lawyers are good enough, can claim that the time lasped was "reasonable" or something else to get around it.

      Hopefully, the don't hire Cochran:

      Ladies and Gentlemen, (Pulls down picture of Chewbacca) this is Chewbacca. Chewbacca is a Wooky from the planet Kishic, but Chewbacca lives on the planet Endor. Now think about it. That does not make sense. Why would a Wooky, an eight-foot-tall Wooky, want to live on Endor with a bunch of two-foot-tall Ewoks? That does not make sense. But more important, you have to ask yourself what does this have to do with this case.

      [Jury stares in silence]

      Nothing! Ladies and Gentlemen, it has nothing to do with this case. It does not make sense. Look at me. I'm a lawyer defending a major software company and I'm talkin' about Chewbacca. Does that make sense? Ladies and Gentlemen, I'm am not making any sense! None of this makes sense!

      And so you have to remember when you're in that jury room deliberating and conjugating the Emancipation Proclamation, does it make sense? No! Ladies and Gentlemen of this deposed jury, it does not make sense. If Chewbacca lives on Endor you must find for my client.

    19. Re:One trick pony table. by Wah · · Score: 1

      no kidding. To think they couldn't effectively argue this point is to miss the whole point of the legal system.

      Heck, just blame it on some techie who spends all day reading /. and didn't take the time to comb the (very complex and confusing) webserver for old code.

      If they stopped offering commercial support (or whatever it was they were doing before taking up suing as a business model) when they noticed the problem, it wouldn't be too much of a stretch to convince a judge that they "missed a spot" while cleaning up.

      --
      +&x
    20. Re:One trick pony table. by MuParadigm · · Score: 1

      Point. Touche. I thought they had removed that from their sites. Continued distribution after actually filing the suit is definitely problematic for them.

    21. Re:One trick pony table. by civilizedINTENSITY · · Score: 1

      But they want to continue to support their linux customers, including updates. If they prove (which I doubt) that any linux distribution is illegal, then their distribution is also illegal. The rights they derived from the GPL to modify and distribute evaporated too. What they should have to do (under their claimed scenerio) is buy back every copy they sold.

    22. Re:One trick pony table. by jedidiah · · Score: 1

      Continuing to distribute a product that contained their own alleged trade secrets and proprietary source code cannot be reasonably interpreted as "missed a spot".

      They are trying to sue IBM for what they themselves are guilty of.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    23. Re:One trick pony table. by Wah · · Score: 1

      I agree totally. And it's not even 'continuing', it's doing it at all. Selling a product under a licence like the GPL and then trying a 'takeback' later, seem rather indefensibly on the face of it.

      I'm just saying that being a hypocrite is something that can pass for lawful from time to time. If it is argued effectively, or against uneffectively.

      I'd love to see someting like this go the Supreme Court. That would be a wild ride.

      --
      +&x
    24. Re:One trick pony table. by jedidiah · · Score: 1

      "argued effectively" is the problematic part here.

      Many people believe in this case that even if SCO is in the right that they don't have the legal resources to win in court. It's not an unreasonable judgement considering the principals in this case.

      --
      A Pirate and a Puritan look the same on a balance sheet.
  23. Slashdot Matrix by TJ6581 · · Score: 1

    On a scale of one to SCO'ed I say that this webserver is done for.

    --
    "Freedom of speech has always been the abstract red-headed stepchild of the Constitution"
    -Suck
  24. Suppositions? by Anonymous Coward · · Score: 0

    So this is a supposition repository? A suppository?

  25. You just need to look at the last line... by greppling · · Score: 5, Insightful
    ...to see what a biased analysis this is. "Linux unaffected" with 100% certainty? Come on, we all have seen things go horribly wrong in courts. And have seen impact of pure FUD with no basis whatsoever.

    Yeah, I know I will get modded down for just suggesting that SCO's action might have some effect, but well...

    1. Re:You just need to look at the last line... by JordoCrouse · · Score: 3, Insightful

      ...to see what a biased analysis this is. "Linux unaffected" with 100% certainty?

      It seems to me that this entire matrix is based on the fact that SCO continued to distribute its Linux distro long after the lawsuit had been brought, indicating that the code was therefore gifted to the community. So no matter what happens, Linux wins.

      Now, that may be true (and wouldn't it be nice if it was), but I would like to hear what the legal eagles think about this particular defense. It seems to me that this should be more of a "last gasp" defense, but definately not something you would want to trot out in opening statements.

      --
      Do you have Linux and a DotPal? Click here now!
    2. Re:You just need to look at the last line... by KillerHamster · · Score: 4, Insightful

      And even if Linux is not affected legally, this lawsuit could permanently scare a lot of companies and individuals away from using Linux, and OSS in general. Maybe it already has.

    3. Re:You just need to look at the last line... by GoofyBoy · · Score: 4, Insightful

      This might be the biggest threat to Linux, that historical fluke of nature that changes everything.

      1. Businesses love Linux because its free and robust.
      2. This infingement hits the nightly news. People get half the story.
      3. The case drags on and its not resolved. Business people think "Am I opening the company to paying infingement charges (unexpected costs) and making a career-limiting decision. Wouldn't it be better to go to MS and just have everything known?"
      4. The case is thrown out. Business people think "Linux dodged the bullet this time. But what about the next time? Do we really want to risk something that could happen again?"

      And so effectively kills Linux attempt at getting into the workplace.

      --
      The surprise isn't how often we make bad choices; the surprise is how seldom they defeat us.
    4. Re:You just need to look at the last line... by Quino · · Score: 1

      of course, there isn't hard data to back either claim up, but there is at least some evidence that the SCO thing isn't actually having a "chilling" effect on Linux. Actually, according to this article, it's having "no" effect on Linux deployment:

      from ad link within slashdot, of all places:

      http://newsforge.com/article.pl?sid=03/06/23/212 20 8&mode=nested&tid=3


      Teresa recalls only one minor -- and in the end harmless -- bit of fallout from the SCO brouhaha. "One customer put a temporary hold on Linux purchases because of the SCO letter," she says. "Then they let it go. It was a one-week delay."


      Who knows what effect the SCO thing is actually having on Linux deployment, but at least it's muddled enough that it isn't clear. I think at least it seems very unlikely that the SCO temper tandrum is having a serious effect.

    5. Re:You just need to look at the last line... by Scott+Wood · · Score: 1
      So, would that be like the way Apple's look-and-feel lawsuit had a permanent chilling effect on the adoption of Windows in corporate environments, even though Windows "dodged the bullet" that time?

      Or perhaps like the lawsuit over BSD, or any of numerous other unsuccessful lawsuits that have been brought over the years? I would imagine that most large corporations would be used to these sorts of games by now.

    6. Re:You just need to look at the last line... by MadCow42 · · Score: 1

      You forgot 5:

      5) In the end, IBM squashes SCO, gets all the remaining Unix IP in the process of countersuing, releases it to the world under GPL and Linux lives happily ever after in the clear just like the BSD code base.

      MadCow.

      --
      I used to have a sig, but I set it free and it never came back.
    7. Re:You just need to look at the last line... by Malcontent · · Score: 1

      You are right.

      Most CIOs are exactly that stupid.

      --

      War is necrophilia.

    8. Re:You just need to look at the last line... by Anonymous Coward · · Score: 0

      Well, Windows adoption didn't seriously get started until after Apple's case was pretty much neutered.

      Not saying those two events are related, because much like Linux, Windows basically snuck in the backdoor.

    9. Re:You just need to look at the last line... by Anonymous Coward · · Score: 0

      You didn't get modded down because you still claimed SCOs case is bogus. Beleive me, every time I tell the /. community their analysis is bogus, I get modded down. I read the first 2 entries on the matrix and their all pure bullshit. The 1st one is, they haven't shown the copied code publically, therefore there is no copied code. That's a complete non-sequitar. then they said SCO released their code themselves by not pulling it until 2 months after they informed IBM. Give me a break 2 months is a heartbeat in the business world and the case hasn't even gone to trial. That arguement is pathetic. It's amazing how emotional attachment to something complete destroys people ability to reason objectively.

    10. Re:You just need to look at the last line... by Anonymous Coward · · Score: 0

      here that sound?

      it's the sound of MS/SCO seeded moderators fumbling with their mice and keyboards hitting your post with modups as fast as they can (without staining their shorts)

    11. Re:You just need to look at the last line... by A_Non_Moose · · Score: 1

      Wouldn't it be better to go to MS and just have everything known?

      AAAAhahahahaha.

      funniest fricking thing I've read all day...and looking at your User#, all I can say is welcome back, you've been away a while, haven't you?

      {seg...j/k}

      --
      Have you read the moderator guidelines? Well, have you, PUNK? (and I want a Karma: Gnarly option)
  26. Hehe ... by BillsPetMonkey · · Score: 0

    SCO will claim that all UnixWare code is original and belongs to SCO

    "ALL YOUR UNIXWARE CODE ARE BELONG ... " Ah. never mind.

    --
    "It's not your information. It's information about you" - John Ford, Vice President, Equifax
  27. please oh please by Anonymous Coward · · Score: 0

    it would be the best possible thing for SCO to
    bury linux (even tho the whole deal is SCO vs
    IBM, not linux) .. linux on the desktop is a
    massive failure. why?

    o - every monkey out there has their own take
    on how things should work

    o - few monkeys are being paid

    the end result being dozens of nearly identical
    projects with completely different code bases,
    different data formats and developers that abandon
    the project due to lack of recompensation

    linux for Servers - linux wins there .. but not
    for the desktop .. for years i've tried to make
    linux a useful desktop environment, and it is so
    long as i don't want to do anything remotely
    interesting - putty and goscreen lets me use my
    win box as effectively as a linux desktop without
    depriving me of the more well fleshed windows
    applications .. and all windows needs is a decent
    shell environment to be just as useful .. hell,
    m$ should open the source to windows .. that would
    ensure their dominance completely, as their profit
    centers should be the applications

    -1 flamebait
    -1 offtopic
    -1 troll
    -11 Truth

  28. In the end, SCO have released the code by OpCode42 · · Score: 1

    They released it in their distro after they found it was there. Therefore, they have opened up the code.

    Am I wrong?

  29. Not only that... by Atario · · Score: 5, Funny

    ...but they forgot a row in the table:

    Effect on SCO:
    Everyone hates them
    Everyone hates them
    Everyone hates them
    Everyone hates them
    Everyone hates them
    Everyone hates them

    --
    "A great democracy must be progressive or it will soon cease to be a great democracy." --Theodore Roosevelt
    1. Re:Not only that... by Anonymous Coward · · Score: 0

      Very funny :)

      And also very true.

    2. Re:Not only that... by DrCode · · Score: 1

      Shouldn't there be a "MS loves them" in that row somewhere?

    3. Re:Not only that... by kop · · Score: 1

      You forgot two rows
      ?
      ?
      ?
      ?
      ?
      ?
      And
      profit!
      profit!
      pro fit!
      profit!
      profit!
      profit!

  30. RTFA? they picked Redhat by JimmytheGeek · · Score: 2, Insightful

    It looked like they were pursuaded to pay more for the Redhat enterprise option rather than go with a cheaper SCO upgrade. The gist is that SCO was mired in rebranding, and not doing anything innovative or otherwise improving the product.

    They had already determined that the crucial app would run well on either platform and the migration pain was not significant enough to mention.

  31. Look, they're not stupid. by s20451 · · Score: 5, Interesting

    I am distressed that most of the anti-SCO argument seems to be based on the fact that SCO continued to publish Linux after claiming infringement.

    David Boies is a smart man, and surely he or his legal team would have thought of this. They must have some sort of legitimate defense up their sleeve. Maybe a direct attack on the legitimacy of the GPL?

    I think it will run something like this: Linux is important to SCO's business. Even though they discovered violations in linux, they had to continue to release linux or suffer grave damage to their business. They should not be made to suffer for the malicious actions of IBM, and they did not voluntarily release their own source code, so the GPL should not apply to their proprietary code that somehow found its way into linux.

    --
    Toronto-area transit rider? Rate your ride.
    1. Re:Look, they're not stupid. by ThePlague · · Score: 0

      Hell, they could have been contractually obligated to continue releasing Linux even after they "discovered" the "offending" code. IBM breaking their contract is not a tenable reason to break their own 3rd party contracts.

      I don't know, of course, but I would imagine their justification for continuing to release it would go something like this.

    2. Re:Look, they're not stupid. by b29651 · · Score: 1

      Right so they appoint SCO as guardians of the Linux code.If you think about this it is because our society has been conditioned to think you arent too smart if you arent making money and are giving something away for free cause nothing is free in life.Free as in freedom to use as you see fit.Alien thinking to the business model.they are going to try to show that this proves that Linux cant control the source of its code so it needs better controls.IBM is smarter than SCO is my one hope .

    3. Re:Look, they're not stupid. by njdj · · Score: 1

      David Boies is a smart man, and surely (...)

      David Boies' goal is to make a lot of money. It's most unlikely he cares about SCO. He'll do the best he can, and if SCO's case is hopeless, a loss will not damage his career.

    4. Re:Look, they're not stupid. by molarmass192 · · Score: 4, Insightful

      Wrong, they knew about the code in March, they continued to distribute the software until May. Therefore, as per section 4 of the GPL:

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

      I quote Mr. Sontag, SCO will continue to support SCO Linux users and "hold them harmless from any SCO intellectual property issues regarding SCO Linux and Caldera OpenLinux products,". Long story short, they cannot only indemnify Caldera Linux users under the GPL, so they've effectively absolved all Linux users by absolving Caldera Linux users and freed the infringing code to the GPL in the process. Sontag should have kept his mouth shut because beyond the IBM suit, this case now has a 0% chance of succeeding, even if code was copied verbatim, barring having the GPL itself completely discredited.

      --

      Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws-Plato
    5. Re:Look, they're not stupid. by evilWurst · · Score: 1

      Boies is a hireling of SCO, not it's boss. Notice that Boies has been silent? Notice that all the contradictory information from SCO that poisons its own case comes from their top officers?

      I give the man credit, but SCO clearly ignored his advice on this matter, and it's out of his hands.

    6. Re:Look, they're not stupid. by Anonymous Coward · · Score: 0

      Check out naked-gcc. It strikes at FSF's crown jewels. They are rogues, and they are making gcc without the gpl license. Where is FSF on this matter?

    7. Re:Look, they're not stupid. by PickaBooga · · Score: 4, Insightful


      I don't know why people keep bringing up the possibility of the GPL being illegitimate.

      If the license is illegitimate, then the only thing that would remain is the legal rights of the copyright holders (the individual authors, or the companies they work for, or the EFF if the author transferred the copyright, etc.) In most countries, the copyright is automatic.

      Since SCO distributed copyrighted code, they would have to explain under what license they were authorized to do so, or admit they violated the copyright. They cannot claim the GPL if it is invalid (obviously), so then they would have to secure the rights from all those people, companies, organizations individually, under the laws of dozens of countries. Since almost all the copyright holders would be hostile to licensing to SCO, they would demand outrageous fees for SCO's past and current distribution.

      Besides, any legal means of breaking the GPL could be used against the software licenses of Microsoft, Adobe, Symantec, etc. That is why those companies are so scared of the GPL, it cannot be attacked directly, without destroying their ability to distribute code under the control of a license.

    8. Re:Look, they're not stupid. by expro · · Score: 1

      I agree. I cannot imagine that a competent attorney would say about continuing to distribute Linux kernel source and binaries as they still do today "don't worry, that won't hurt us in court."

      I am not an attorney, but even if they felt rock solid for some unknown reason, the saying goes that whatever you have to prove in court, an attorney will give you a 50/50 chance, because in court anything can happen, so I think you don't intentionally leave extra loose baggage lying around. Leaving this sort of loose baggage lying around seems to mean that someone in charge has priorities other than pursuing Linux distributors.

      They have said many conflicting things, and on certain occasions they have said that it is unlikely that they will go against Linux distributors, and they indicated that they actualy understood the GPL and the difficulty of extracting license fees from Linux kernel users. They certainly GPL out of the current lawsuit. IBM's non-disclosure obligations are independent of GPL issues.

      It would be hard for Linux developers to counter-sue them for only the threatening letters they have sent out. The minute they start suing Linux users or demanding license fees, they open themselves up to hundreds of suits from kernel contributors.

    9. Re:Look, they're not stupid. by iabervon · · Score: 3, Interesting

      David Boies has only signed on to prove that IBM violated the terms of some private contract between SCO and IBM. SCO continuing to publish Linux after claiming infringement has no bearing at all on this question. SCO's claims, aside from this one issue, are merely press releases and personal comments intended to make SCO stock worth more; this doesn't require a legitimate legal defense for their actions, or even a legitimate justification of their claims.

      Linux will certainly be unaffected by the outcome of the SCO v. IBM suit, because it is not a party to the suit. SCO would have a number of problems bringing an IP-related lawsuit against someone over Linux, which is what would be required to have any effect legally on Linux; they don't seem to own any IP of significance, they've licensed any IP they do have to everyone, and they've refused to identify any IP they might own.

    10. Re:Look, they're not stupid. by John+Miles · · Score: 1

      David Boies is a smart man, and surely he or his legal team would have thought of this

      When's the last time he won a case?

      --
      Dahlmann tightly grips the knife, which he may have no idea how to use, and steps out into the plain.
    11. Re:Look, they're not stupid. by eric76 · · Score: 2, Interesting
      I am distressed that most of the anti-SCO argument seems to be based on the fact that SCO continued to publish Linux after claiming infringement.
      Actually, that's just a minor aside to the argument.

      The real qeustion is "Could Linux developers or users have any liability to SCO?"

      So far, the answer is clearly "NO". There is no possibility of any Linux developer (apart from IBM) or users having any liabilities based on everything we have seen.

      The so-called SCO code in Linux has, so far, been the intellectual property of IBM, not SCO. SCO's argument is that because IBM used it in AIX, that IBM is somehow not allowed to apply their intellectual property to any other use outside of AIX.

      While it is possible that SCO might prevail, they would have to prevail against IBM primarily for using their code in violation of their contract. If it was a violation of the contract, and I seriously doubt it, than IBM would be the only ones on the hook because of their contract violation.

      The rest of us do not have contracts with SCO and have done nothing to violate any contracts with SCO. In other words, we have no duty to SCO for using any code contributed to Linux by another party when that party owns the code in question.

      By the way, has anyone called IBM's sales line number (888-746-7426 if I remember correctly) but with an 800 instead of an 888? It's a sex line! That really threw me for a loop when ordering a motherboard to replace one done in by lightning.

    12. Re:Look, they're not stupid. by Anonymous Coward · · Score: 2, Insightful

      The GPL defense isn't completely one of "you released your code under GPL so it's free". The fact is that contrary to what SCO would have the world believe, even if their claims are true 99.9% of the Linux code was written by independant developers. In order to lawfully distribute the intellectual property of those developers (which SCO has done) they have to accept the condition of not imposing further restrictions on that code. Sure SCO owns "their" code and can put whatever restrictions they want on it, but they cannot combine "their" code with GPL code and distribute it under a restrictive royalty-based license. True they didn't actually combine the code themselves and may not have been aware of it at the time, but they cannot distribute a hybrid kernel to only their Caldera customers without violating the IP rights of all the kernel developers.

      Just because the Linux kernel is distributed under a liberal license, that dosen't make the kernel developer's rights any less important than SCO's rights to the code they allege to own. The worst thing that can happen is that the offending code will have to be replaced. SCO cannot force another outcome upon the Linux community without effectively stealing the legitimate Linux code from its creators.

    13. Re:Look, they're not stupid. by Anonymous Coward · · Score: 0

      Does it mean that SCO either distributed the code under GPL or had its rights under GPL terminated?

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

    14. Re:Look, they're not stupid. by An+Onerous+Coward · · Score: 1
      I think it will run something like this: Linux is important to SCO's business. Even though they discovered violations in linux, they had to continue to release linux or suffer grave damage to their business. They should not be made to suffer for the malicious actions of IBM, and they did not voluntarily release their own source code, so the GPL should not apply to their proprietary code that somehow found its way into linux.
      I cannot imagine this working quite the way you envision. If I'm running a newspaper, and I discover that one of my reporters has been stealing stories off the news wire and calling them his own, can I keep publishing his stories because they're a vital part of my business? Or if I'm making glazed doughnuts, and find out that my glaze supplier is watering the glaze down with lead-based paint, would I be legally justified in using up the rest of my stock while suing the bejeebers off my supplier?

      Of course, not using the stock might mean that doughnut production could screech to a halt for a few days, seriously harming my business. Somehow, I don't think the courts would care.

      No matter how vital Linux was to their buisness--even if ceasing distribution would tank the company--it didn't give them permission to ignore the GPL and continue distributing code. They don't want their code distributed under the GPL? Then they should have taken the steps to ensure that it wouldn't be as soon as the first whiff of infringement came along.

      I don't think that they'll lose rights to any of the allegedly infringing code. But I think their continued distribution will seriously limit their ability to claim damages. But that's just my own speculation.
      --

      You want the truthiness? You can't handle the truthiness!

    15. Re:Look, they're not stupid. by EzInKy · · Score: 1

      Right so they appoint SCO as guardians of the Linux code.

      I doubt a court could do that because it would violate the copyrights of the hundreds who contributed to the kernel source tree.

      --
      Time is what keeps everything from happening all at once.
    16. Re:Look, they're not stupid. by molarmass192 · · Score: 1

      The way I read it, both.

      --

      Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws-Plato
    17. Re:Look, they're not stupid. by jak163 · · Score: 1

      Even if they indemnified users from the point at which they knowingly distributed their code forward, they could sue for damages caused up to that point, as well as future lost business stemming from purchasing decisions made up to that point.

  32. Waiting for the day by stephenry · · Score: 1

    What makes me upset about this whole situation is the fact that once the true nature of SCO's allegations against Linux become apparent, the company will not be able to sustain itself financially long enough to recieve the retribution.

  33. If you take the Red Pill... by EvilTwinSkippy · · Score: 5, Funny
    You can't be told what the infringing code is, you have to see it for yourself.

    This is your last chance.

    You tale the Blue pill, and you decline the NDA. You come to your senses and walk away.

    You take the Red pill and you stay in wonderland, and SCO will show you just how deep the Rabbit hole goes. Oh, and you can't tell anyone what you saw.

    --
    "Learning is not compulsory... neither is survival."
    --Dr.W.Edwards Deming
    1. Re:If you take the Red Pill... by Tackhead · · Score: 1
      > You take the Red pill and you stay in wonderland, and SCO will show you just how deep the Rabbit hole goes. Oh, and you can't tell anyone what you saw.

      That's no Rabbit Hole! That's a Space Station! [darlmcbridse.cx]

    2. Re:If you take the Red Pill... by Dr.+Zowie · · Score: 1
      Back in my day I had to write games in BASIC, on a 4.7Mhz computer with no hard disk and 128K of RAM. And I was grateful


      You had a 4.7 MHz computer? I wrote graphics shoot-em-ups in INTEGER BASIC on a 1.077 MHz Apple ][. And they were cool.

      Before that, we used to go down the university in the middle of the night and play ADVENTURE on the PDP-11.

    3. Re:If you take the Red Pill... by LordSkippy · · Score: 1

      128K of RAM? Luxury! Oh how we use to dream of having a 128K of RAM! We only 64K of RAM, and we had to share it with 256 users - or the system admin would slash us to death with a bread knife!

      My apologies to Monty Python.

      --
      My karma is in a nose dive
    4. Re:If you take the Red Pill... by EvilTwinSkippy · · Score: 1
      darlmcbridese.cx, has that replaced goat.se.cx?

      Never mind, I have have enough images permanently burned into my retna from Usenet...

      --
      "Learning is not compulsory... neither is survival."
      --Dr.W.Edwards Deming
    5. Re:If you take the Red Pill... by Citizen+of+Earth · · Score: 1

      Back in my day I had to write games in BASIC, on a 4.7Mhz computer with no hard disk and 128K of RAM. And I was grateful

      Luxury! I only had a 1-MHz computer and 5K of RAM. And I was grateful! (Well, my 1-MHz was as good as your 4.77).

  34. Matrix schmatrix! by tkittel · · Score: 1

    Matrix my this and matrix my that.

    I always thought a matrix was a mathematical object - the two-dimensional equivalent of a vector (or however one chose to look at it).

    If a science fiction movie has to name a computer program which simulates every part of life, its called "The Matrix".

    If something doesnt work in Enterprise it is because "The matrix" is not aligned.

    And now, if someone presents something in a table, it is also a matrix?!?

    maybe i'm just in a pedantic mood today :-)

    1. Re:Matrix schmatrix! by mcc · · Score: 1
      If a science fiction movie has to name a computer program which simulates every part of life, its called "The Matrix".

      This isn't totally unreasonable. The following is from the 1913 Webster's Dictionary; note entries 1 and 2. They seem to describe "The Matrix" from the sci-fi movie you mention perfectly.
      Ma"trix (?), n.; pl. Matrices (#). [L., fr. mater mother. See Mother, and cf. Matrice.]

      1. Anat.

      The womb.

      All that openeth the matrix is mine. Ex. xxxiv. 19.

      2.

      Hence, that which gives form or origin to anything
      ; as: (a) Mech. The cavity in which anything is formed, and which gives it shape; a die; a mold, as for the face of a type.


      (b) Min. The earthy or stony substance in which metallic ores or crystallized minerals are found; the gangue.

      (c) pl. Dyeing. The five simple colors, black, white, blue, red, and yellow, of which all the rest are composed.

      3. Biol.

      The lifeless portion of tissue, either animal or vegetable, situated between the cells; the intercellular substance.

      4. Math.

      A rectangular arrangement of symbols in rows and columns. The symbols may express quantities or operations.
    2. Re:Matrix schmatrix! by tkittel · · Score: 1


      Hmm... quite interesting.

      I guess when you think about it (which i didnt) it makes sense that the word "matrix" must have meant something before it was used for mathematics, as mathematical matrices has only been used for what? - 100 or 150 years?

      "that which gives form or origin to anything" seems to fit the role it has in connection with the bunch of numbers inside it nicely.

      But i can still make jokes about star trek right? :-)

    3. Re:Matrix schmatrix! by LordSkippy · · Score: 1

      Yes, you can always make jokes about Star Trek.

      --
      My karma is in a nose dive
  35. Dubious. by Anonymous Coward · · Score: 1, Interesting

    If SCO is right and there is infringing code, then the fact that they willfully released any such code within their own Linux kernel distribution, even after they knew that there was supposed code infringement, released that code into the GPL forever, absolving it from any further claims by SCO.

    This isn't necessarily the case. SCO has quite a lot of leeway based on the fact they can claim their GPL rerelease of code taken from the linux community was a mistake, having not realized their own code was in there. The fact that they'd make a statement like that and not point out it's a dodgy argument casts doubt on this entire document.

    1. Re:Dubious. by NecroPuppy · · Score: 1

      True.

      However, as others have said, the fact that they then didn't immediately pull their Linux release hurts them somewhat.

      It's like discovering you can opt out of a spam list, not opting out for another few months, and then complaining you still got spam for the months between the times you learned about the opt out, and actually used it.

      --
      I like you, Stuart. You're not like everyone else, here, at Slashdot.
  36. Handy by evilpenguin · · Score: 3, Insightful

    I like this. All the uninformed and irrelevant speculation by armchair lawyers put into one slashdotted source. A great timesaver.

    That said, we all know that in the long run Linux has to be unaffected. If they prove infringement a great deal of effort will go into producing non-infringing code. In the long run, it will be just fine. This is mainly about a dying company trying to get some money to pay the receiver.

  37. How can this be??? by ChrisSontagsAnus · · Score: 1
    Bois promised me:

    1. Steal Linux

    2. ???

    3. Profits!

  38. vegas style by Jack+Schitt · · Score: 1

    ok... now that we have a matrix drawn up, let's place those bets...

    --
    This message brought to you by Jack Schitt's Previously Shat Shit
  39. Oh... by Anonymous Coward · · Score: 0

    Already slashdotted... can anyone get the matrix reloaded?

  40. Preaching to the quire by b.foster · · Score: 4, Insightful
    Although the concept of a decision matrix is a good one, these authors chose instead to squander their opportunity to present both sides of the case by presenting a one-sided, dubious view that may or may not have anything in common with the court's ultimate interpretation.

    For instance:

    • "SCO have yet to reveal any conclusive evidence that they can show there is code that they have developed, which is now in Linux illegally." Although I also doubt that SCO has any conclusive evidence, as a former paralegal I can assure you that there are many good reasons why they would be harmed by showing their cards right now.
    • "SCO released any infringing code: Proven." This is decidedly false, as this has not been proven in a court of law. Codes of procedure, rules of evidence, and whether or not the judge got laid last night all have significant bearing on whether or not the court will have enough evidence to deem this point "proven."
    • "Final Outcome: Linux is Unaffected." This is completely false. Linux has already been affected by companies who have shown increased sales since beginning to spew FUD about "stolen IP" in Linux. I have several friends at various Linux vendors who claim that sales are down and that customers have mentioned the suit very often as a reason to hold off on adoption of open source software. The BSA is lobbying foreign governments to avoid open source because of this case, even as we speak. We may be able to fix a few lines of snarfed code in 15 minutes and end the whole ordeal, but Linux may never get its credibility back if contributors can be shown to have caused the problem. Never forget that it takes a long time to build trust but trust can be lost in a matter of seconds. And articles like this that spread pro-Linux FUD are just as detestable as the garbage spewed from Redmond.
    1. Re:Preaching to the quire by Anonymous Coward · · Score: 4, Funny

      Preaching to the quire ROFL!!!! I suppose I should inchoir as to why your spelling sucks!

    2. Re:Preaching to the quire by rodentia · · Score: 1

      This insightful comment by a former paralegal is a good example of the sort of malinformed speculation that passes for insight in this debate. That SCO had freely released the code ostensibly infringed by GNU/Linux and had done so under the GPL and had done so until quite recently is an historical fact which is not amenable to a juridical determination. Period. Oh, and WTF is a quire?

      --
      illegitimii non ingravare
    3. Re:Preaching to the quire by swb · · Score: 1

      At first I thought it was some Olde Englishe expression or something and I was wrong all along for thinking it was "Preaching to the choir".

      M-W says a "quire" is a 1/4 of a ream of paper.

    4. Re:Preaching to the quire by Anonymous Coward · · Score: 0

      It's spelled "choir"

    5. Re:Preaching to the quire by pongo000 · · Score: 5, Informative

      Linux has already been affected by companies who have shown increased sales since beginning to spew FUD about "stolen IP" in Linux.

      So true. But companies won't come right out and admit to this -- makes them look foolish.

      Case in point: I was all set to introduce our school district (>50,000 students, 9 high schools) to Linux as an economic alternative to Novell. Servers were purchased (ProLiant DLs with dual processors and 6-disk RAIDs), Linux was installed, testing was done, quotas set up, we were ready to roll -- and then SCO dropped their bombshell. A week went by...two weeks...I discovered that due to "security" concerns, the servers were to be converted to Novell servers.

      "Security" concerns? Bullshit. I had already worked several weeks with the network gurus to put their security concerns to rest.

      This is but one government entity. The damage SCO has caused is quite extensive, and those who deny it are hiding their heads in the sand.

      Who would have thought that Linux (and open-source software in general) would be brought to its knees by an indirect blow? Here we were, thinking the battle was to be fought in Redmond, when in fact we were flanked by SCO and didn't even realize it until it was too late.

      Such is the price of hubris and arrogance. "If you know the enemy and know yourself, you need not fear the result of a hundred battles. If you know yourself but not the enemy, for every victory gained you will also suffer a defeat. If you know neither the enemy nor yourself, you will succumb in every battle." (Sun Tzu, Art of War)

    6. Re:Preaching to the quire by u19925 · · Score: 1

      "The BSA is lobbying foreign governments to avoid open source because of this case, even as we speak."

      Asking BSA whether you should use Linux is like asking Ford whether you should use public transport. If any foreign government listens to BSA and decides not to use Linux, then it is guilty of stupidity or corruption.

    7. Re:Preaching to the quire by Anonymous Coward · · Score: 0

      While I agree with you on most of your points, will Linux really be affected ultimately? Because technically, Linux was never meant to "compete." It was meant to "entertain" the fiddling's of computer developers, designers, and users the world over. At worst, it no longer will be used by big bad corporations, but instead by nimble, quick home users and small businesses who can afford to take bigger risks and buck the big bad corporations, and most importantly, the rules.

      This means that Linux ends up becoming the more useful OS for doing the really powerful stuff, while Microsoft, UNIX, and SCO become the slow dying giants that just don't cut the mustard, or the cheese, for that matter.

    8. Re:Preaching to the quire by Anonymous Coward · · Score: 1, Funny

      as a former paralegal I can assure you....
      whether or not the judge got laid last night all have significant bearing on whether or not the court will have enough evidence to deem this point "proven."
      I hope we can count on you to do your part.

    9. Re:Preaching to the quire by arkanes · · Score: 1
      Assume for the moment that SCO has ironclad, indisputable evidence of code that they provably, in an ironclad way, own the copyright to has been commited into Linux. What harm would they be done by telling the Linux community what code this is so it can be removed?

      SCO ceartainly has provably released any infringing code. There's no possible argument against this. Whether that release is legally meaningful is more debatable, but considering the time lapse I think it'd be a pretty uphill battle.

      The "Linux is unaffected" line is hyperbole, I agree, but if you read it as "the legal status of Linux is unaffected" it's much more correct. Certainly this case can and has harmed commercial adoption of Linux.

    10. Re:Preaching to the quire by jedidiah · · Score: 1

      > "SCO released any infringing code: Proven."
      > This is decidedly false

      Bullsh*t. Simple facts do not need to be confirmed by a judge or jury in order to be true. SCO continued to distribute their version of Linux after they began slandering the Linux kernel, it's contibutors, and the pedigree of the source. No amount of weak excuses or 500 year old precedents can alter that.

      Arrogance is no defense under the law.

      These facts are all available for the more well funded litigant in this matter to exploit.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    11. Re:Preaching to the quire by RickHunter · · Score: 4, Interesting

      I have several friends at various Linux vendors who claim that sales are down and that customers have mentioned the suit very often as a reason to hold off on adoption of open source software. The BSA is lobbying foreign governments to avoid open source because of this case, even as we speak. We may be able to fix a few lines of snarfed code in 15 minutes and end the whole ordeal, but Linux may never get its credibility back if contributors can be shown to have caused the problem.

      And finally, we come to the root cause of the suit. No, there's no any infringing code. There never has been, and there never will be. But now that SCO's made the accusation, it will be impossible to dispose of. Whenever someone mentions Linux, the "but didn't they steal code from Unix?" question will pop up. Whenever a Microsoft sales rep is talking to a PHB, and the PHB mentions "open source", or "Linux", or even (yes, even) "BSD", the sales rep will be able to say "Ah, but what about that stolen code?" And as the MPAA, RIAA, and BSA have proven so well, stolen's a little red-flag word. No-one wants anything to do with stolen. And not only is Linux tainted, but SCO's nebulous assertions about "Unix" and "SysV" derived works make all Unix-descended systems seem tainted. Which leaves guess who as the sole survivor?

      SCO has no proof. IF this suit ever gets to court, and doesn't just vanish into the mist, they'll get smacked down so hard by IBM that they won't know what hit them. But that possibility will always be out there. After all, Linus cannot check every submission to make sure it wasn't "stolen" from some piece of proprietary software. Its impossible. Neither, however, can Microsoft check to make sure that one of their coders didn't "steal" code from proprietary software, or even a GPL'd program. Its a red herring, designed to make Linux look tainted and criminal for a problem that's common to ALL software.

      I think everyone's first thought was right - SCO is looking to get bought out. But not by IBM - by Microsoft. The executives and top investors know they're on a sinking ship, and are currying favour with MS to try and get on what they see as more sure footing. And making a bundle off their investments while they're at it, by inflating their stock price and selling during the high.

      I sincerely hope these suckers get smacked down hard by an FTA investigation, and whoever's backing them gets nailed with criminal charges.

    12. Re:Preaching to the quire by Anonymous Coward · · Score: 0

      Um...most of this is garbage spewed by Redmond

    13. Re:Preaching to the quire by Anonymous Coward · · Score: 0
      This is but one government entity. The damage SCO has caused is quite extensive, and those who deny it are hiding their heads in the sand.

      I can confirm another installation where Linux was dropped at the last minute for Solaris. The SCO case was directly mentioned as a reason for the last minute change. The other "reasons" were obviously fluff because they'd been addressed and accepted on previous Linux deployments.

      Linux rollouts are effectively on-hold because of SCO's claims. Linux is hurting. Badly.

    14. Re:Preaching to the quire by DataPath · · Score: 1

      Linux is not a company. No one's stock is going to go down. Linux will be the same the day after the ruling as the day of as it was the day before. Whether people use it or not is their choice, it won't make Linus have to pack up his Linux and go home to Finland. It won't make any major corporate users of Linux drop it (it'd be so much less expensive to just pay SCO the stupid royalties than to migrate to a different infrastructure). Universities will still find it a useful tool in science and engineering.

      As long as Linux has its figurehead, and it's major corporate users and research organizations all behind it, Linux will plough onward even if RedHat files chapter 11 and every single fortune 500 company that doesn't already use Linux decides it never will.

      And that doesn't even mention the huge enthusiast base both inside the US and all the foreign oorporations that are not bound by the outcome of a US legal battle.

      --
      Inconceivable!
    15. Re:Preaching to the quire by Anonymous Coward · · Score: 0

      Don't worry when your network folk are having to work on there resume because they have no job because the school district has no money then they will come back in line.

    16. Re:Preaching to the quire by Badanov · · Score: 1

      I fail to see how Linux would be adversely affected in any case, especially if IBM wins in a convincing way. I gotta tell you I was worried for a bit about this SCO suit, but now I am sane. Win, lose or draw, I will continue to use RedHat/Linux products as long as they continue to distribute it. Let us not forget, IBM has committed to using Linux in a big way. So if an MS sales person tells a buyer about 'stolen code', if the IT buyer has any intellect at all, (s)he will know that IBM deploys Linux and could send the MS sales guy packing. Such contentions could concievably blow up in Microsoft's face. PLUS: I will continue to shoot my very own mouth off about chucking MS for Linux regardless of the outcome. As they say in marketing parlance, you know they're lying. Come to Linux and see asthetics in computing (or soemthing like that.)

      --
      Dawn of the Dead
    17. Re:Preaching to the quire by RickHunter · · Score: 1

      I know they're lying. You know they're lying. Heck, even the PHB might know they're lying... About this. But they're right about one thing - Linus can't prove there's no stolen code in the kernel. The assertion's still out there, and it can't be disproven. Whenever it gets brought up, there'll still be this "stolen code" idea attached to it.

      Its called "character assassination", and its doubly effective because Linus can't respond in kind. (He lacks the cash)

      And for many things, IBM's no longer the "you'll never get fired" buy. MS is, and this just reinforces that. After all, everyone "knows" that IBM was big in the '80s but isn't anymore. Isn't supporting underhanded development just the kind of thing a company like that would do to get back on top?

      For the record, I'm writing this on a Debian Linux box.

    18. Re:Preaching to the quire by Anonymous Coward · · Score: 0

      Fuck you are stupid. SCO did not "release" the code -- they simply redistributed it. The juridical determination is going to be that nobody gives a shit about slashbot GPL logic games, including IBM's lawyers.

    19. Re:Preaching to the quire by Anonymous Coward · · Score: 0

      Why are you criticizing the article and then showing bias yourself? Comments like "Although I also doubt that SCO has any conclusive evidence" and "Linux has already been affected by companies who have shown increased sales since beginning to spew FUD about "stolen IP" in Linux." show you're no more objective than the authors of the page. You have no basis for these claims, so quit being a hypocrite. You're no better than the authors of this garbage loosely called news.

    20. Re:Preaching to the quire by Anonymous Coward · · Score: 0

      as a former paralegal I can assure you

      Shit! So when people talk about IBM parachuting in a murder of lawyers, they're not kidding?

    21. Re:Preaching to the quire by Mostly+a+lurker · · Score: 1
      SCO is looking to get bought out. But not by IBM - by Microsoft.

      Any wealthy company (possibly even including IBM) that bought SCO at this stage would be crazy. At some stage, when SCO's claims have been completely debunked, the claims against SCO start for damage to business and/or repuation of a long list of individuals and organisations. As long as SCO is a small independent company with very limited financial resources, this is not very relevant. But what large organisation would take the risk of billions in damages?

    22. Re:Preaching to the quire by Anonymous Coward · · Score: 0

      The school district should have documented this decision fully, then they can sue triple damages when the decision comes down.

      Ass EFF and others have said, failure to clariy matters is reckless. Everyone else with a linux interest will be in for their chop too. The lesson here, is make honest, documented decisions.

    23. Re:Preaching to the quire by civilizedINTENSITY · · Score: 1

      Spelling nazi...Then someone'll suggest he might make a good nazi prision guard... then comparisons of SCO's D. McBride and Hitler with der furhur seeming not so evil...add a MS conspiracy theorist and its all there, 'cept for the goat.

    24. Re:Preaching to the quire by Omni-Cognate · · Score: 1

      Cathedrals are shaped like a cross. If I remember correctly, the parts of the cathedral corresponding to where the unfortunate crucifixee's arms would be are called the transepts, and the part where his body and legs would be is the nave. What I certainly remember correctly (having sung in a number of cathedral choirs) is that the area corresponding to where the head would be is called the quire.

      The quire is where the choir sits, but it is also where the clergymen sit (there can be quite a lot in a cathedral).

      Considering that most of the people in the choirs in which I sang would probably be considered by the preacher to be in need of a good sermon (choirs are selected for singing ability, not piety), the phrase "preaching to the quire" (ie preaching to the clergymen), seems to capture the intended meaning much better than "preaching to the choir" (ie preaching to a bunch of giggling kids who wouldn't know god if he smote them).

      Since quire is pronounced the same as choir, I would hazard a guess (only a guess, mind you) that "preaching to the quire" was the original, and "preaching to the choir" an inevitable corruption.

      --

      "The Milliard Gargantubrain? A mere abacus - mention it not."

    25. Re:Preaching to the quire by RickHunter · · Score: 1

      Right, which is why a an actual buyout is unlikely. I'd expect a transfer of IP and upper management, and the promotion of some scapegoat (probably a techie) to take the fall. And there's still the question of whether the claims against SCO could be made - notice that they've not made many specific assertions? Mostly just general statements about "stolen code" and "corrupted IP".

      Besides, as you point out, SCO is a small, independent company. What happens if they decide they've done enough damage (or made enough money off the stock) and file for bankruptcy? (Because, of course, of the damage caused by those evil Linux pirates!) Is there anyone left who can be sued?

    26. Re:Preaching to the quire by jak163 · · Score: 1

      Perhaps part of the problem this accusation is so damaging is that the community is dependent on SCO to say what the offending code is. IOW if they were able to document the source of all the code, then perhaps there would be no FUD?

  41. Chance of SCO success? by DeadSea · · Score: 4, Interesting
    For SCO to get anywhere on this lawsuit:
    1. If SCO doesn't own the copyrights that it claims --> Lawsuit fails
    2. If there isn't any infringing code in Linux --> Lawsuit fails
    3. If SCO can't prove that IBM put the code there --> Lawsuit fails
    4. If SCO can't convince a court that they were duped into distributing the infringing code under the GPL in their own Linux distribution --> Lawsuit fails
    5. If SCO can't convince a court that there should be monitary damages --> Lawsuit fails
    So what if there is infringing SCO code in Linux and SCO manages to play the duped victim with their own distribution under GPL?
    1. Linux developers replace the code and release a new version. Any infringing sections are rumored to be in the tens (not hundreds or more) lines. This should happen very quickly.
    2. Linux users upgrade to the newest version and would no longer be in violation
    3. SCO could try to sue more people for past offenses, for which they would likely be awarded very little as the infringement is so small and users were not aware of the infringements (even after the lawsuit was announced as SCO isn't telling what infringes).
    1. Re:Chance of SCO success? by jo42 · · Score: 1

      3) IBM spends more $$$ on coffee worldwide than it would take to buy out SCO...

    2. Re:Chance of SCO success? by Anonymous Coward · · Score: 0

      Error in line 5, *SCO NULL pointer dereference

    3. Re:Chance of SCO success? by adamshelley · · Score: 1, Insightful
      If SCO can't prove that IBM put the code there --> Lawsuit fails

      I think that its important to mention this. SCO have only sued IBM in their belief that IBM as put this code into Linux. If IBM hasn't and SCO cannot prove it then this lawsuit is a done deal. Also, if SCO sues IBM and loses, I don't believe they have the right to sue someone else on the same terms. If they want to do this they have to sue IBM as well as any other potential entity with money that could of done it at the same time. (i'm not a lawyer, that was my understanding of the law though-in canada)

      Also, If companies are running linux and IBM did put the code in the kernel and SCO proves this and wins then would SCO could be able to sue companies selling / distributing the offending kernel verions: I have my doubts. Cases like this set precedents in courts and any judge who wants to do that is going to have to come up with some colorful ruling so that companies who have an interest in slowing GPL distributed software could not easily & annonymously(to frame a competing body) ruin many GPL'd projects by entering in fraudulant code into the source. Meh.

      Unfortunately SCO only has money to lose, money which they wouldn't have if this lawsuit didn't start: so they're ahead either way. Linux is already losing because of the uncertainties involved in this legal action. it is also scarey that IBM is allowing FUD to be spread. IBM should stand up and explicly deny the code copying instead of simply arguing that its AIX liscense is irrevocable. As fas as we can tell (the public) any programmer with access to a copy of the unix code in question could of submitted it. (is this right to assume, doesn't linus review the code and check off who submitted it?) IBM could easily deny its involvement and pass it off an anonymous source: the offending lines.

    4. Re:Chance of SCO success? by Osty · · Score: 2, Informative

      Linux users upgrade to the newest version and would no longer be in violation

      Yeah, right. That's not going to happen. Assuming that there is infringing code, that the code is relatively minor, and that kernel developers can quickly replace it with non-infringing code, there's still the problem of getting users to use that code. Sure, the few thousand crazies that update their kernel on every RC version or Alan Cox patch will be first in line, but they're a very small minority. Even if Linus decides to release a new kernel version just for those changes (probably likely, if it needs to be done), you're still only dealing with a minority of people that stay on top of minor kernel version changes.


      Now you're left with two distinct types of users, both much more prevalent than the previous examples. First, you have people running Linux on production machines or machines that otherwise need to remain stable. Not only does updating the kernel mean downtime for a reboot (if you're only allowed ~15 minutes of downtime a year, a reboot can cut into a huge chunk of that budget), but this is new code. Adequate stress testing would need to be performed, pushing deployment back several weeks (assuming that no issues crop up to delay the deployment). The remaining type of user encompasses everything from the greenest newbie to non-zealot power users. They're the people that either don't know (newbies) or don't care (people that want to get work done, rather than spending all of their time compiling and deploying kernels). The latter can be mitigated somewhat with the auto-update tools available now, but those still require user intervention.


      What that all boils down to is that SCO may have some leverage even if the kernel developers do quickly remove any infringing code. And that's not even covering issues like the need for distribution makers to release new versions, and potentially the need to pull remaining boxed software stock to avoid continuing infringement by selling software with an old kernel.

    5. Re:Chance of SCO success? by eric76 · · Score: 2, Interesting
      Now you're left with two distinct types of users, both much more prevalent than the previous examples. First, you have people running Linux on production machines or machines that otherwise need to remain stable. Not only does updating the kernel mean downtime for a reboot (if you're only allowed ~15 minutes of downtime a year, a reboot can cut into a huge chunk of that budget), but this is new code. Adequate stress testing would need to be performed, pushing deployment back several weeks (assuming that no issues crop up to delay the deployment). The remaining type of user encompasses everything from the greenest newbie to non-zealot power users. They're the people that either don't know (newbies) or don't care (people that want to get work done, rather than spending all of their time compiling and deploying kernels). The latter can be mitigated somewhat with the auto-update tools available now, but those still require user intervention.

      However, presumably anyone running such code is probably using an older version without the so-called offending code in it. Anything they have with the latest code would likely be in testing and not running production equipment.

    6. Re:Chance of SCO success? by jynx78 · · Score: 1

      Not entirely correct. SCO never has to say where or what the code is to the public. They have to submit it to the courts as evidence; but they'll probably move to have it sealed from public eyes. So they could win, that's always been a chance with the current court situation. And they don't ever have to reveal publically where or what the code is.

  42. SCO gains by geekmetal · · Score: 1

    I guess SCO has got enough news coverage from this issue and possibly some customers too. They sure are playing with fire.
    Their persistance makes me hesitate in writing them off, wonder whats up their sleeve.

    --
    There are two kinds of egotists: 1) Those who admit it 2) The rest of us
  43. "Linux is unaffected" by hendridm · · Score: 4, Insightful

    > SCO made initial IP claims against IBM in March 6th 20032, and only removed the source code to its Linux distribution in May 14th 20033 Thus SCO have gifted this code to the Linux community.

    The author of this piece seems pretty sure Linux will be unaffected by the outcome of this case. What about this:

    SCO realizes there is infringing code in Linux, but continue to release their distribution anyway. Perhaps they felt since their code was already infringed upon, why should they be punished in lost sales by pulling their product which was developed unknowingly with stolen code? Could it not be argued that once an invalid license always an invalid license? Since the infringing code was included without their permission, its license under the GPL was never valid.

    To illustrate my point: Let's say Pepsi owns Nutrisweet and have patents on the artificial sweetener. Let's say they also resell Dr. Pepper products in their soda machines. Let's also say that Dr. Pepper developed their own artificial sweetener for Diet Dr. Pepper that infringes on some of Pepsi's IP. Once Pepsi finds out about it, are they required to pull all Diet Dr. Pepper from their machines, thus hurting sales and requiring extra man hours?

    Obviously, this isn't a perfect example because you don't license a can of soda to a consumer. However, couldn't a good lawyer argue that the crime was done and the time period where SCO was releasing their code under the GPL was to give them time to "tie up loose ends" with that product line while minimizing the negative impact on their bottom line? It seems like a "victim" of such "theft" should be entitled to pick up the pieces within a reasonable time frame.

    Just a thought. I just don't think we should be celebrating until the court case is over.

    1. Re:"Linux is unaffected" by leomekenkamp · · Score: 1

      Interesting, but you are forgetting one thing: SCO may believe they own the code IBM wrote, and say for the sake of argument they are right. Then there is still all the other code written by numerous individuals, all under their own copyright and under the GPL.

      It does not matter wether or not 'SCOs code' was illegally inserted into linux (GNU/linux, whatever), fact is there is a lot of code there belonging to others and licenced under the GPL. If SCO keeps on using that code, they should conform to the terms of the GPL. If they do not, they are in conflic with copyright law.

      --
      Wenn ist das Nunstueck git und Slotermeyer? Ja! Beiherhund das Oder die Flipperwaldt gersput.
    2. Re:"Linux is unaffected" by Darth · · Score: 1

      SCO realizes there is infringing code in Linux, but continue to release their distribution anyway. Perhaps they felt since their code was already infringed upon, why should they be punished in lost sales by pulling their product which was developed unknowingly with stolen code?

      It is irrelevent that the code was already infringed upon. They have a legal avenue to stop that infringement and fix any violations. Unless certain IP bills going through congress pass, they do not have the right to violate the law just because they think someone might be violating their copyright.

      Could it not be argued that once an invalid license always an invalid license?

      Sure. that isnt the point, though.

      Since the infringing code was included without their permission, its license under the GPL was never valid.

      It was not valid initially. However, once they knew the code was in there and continued to distribute it, they set themselves up in a bad situation. As it stands now, they either willingly gave permission for the code to be distributed under the GPL, or they have (by their own admission) willfully and knowingly violated the copyright of every piece of open source software in the distribution they are making available.

      So basically, they've either given permission for the code to be used under the GPL or they have committed thousands of copyright violations of the same magnitude as the one they are charging IBM with.

      That's the rock and hard place their actions have put them in.

      --
      Darth --
      Nil Mortifi, Sine Lucre
    3. Re:"Linux is unaffected" by arkanes · · Score: 1

      No matter whether the code they released was done on purpose or not, if they choose to claim IP rights on it, then they're in violation of the GPL _right now_ as well as those 2 months for distributing everything ELSE in Linux. No matter what.

    4. Re:"Linux is unaffected" by prgrmr · · Score: 1

      couldn't a good lawyer argue that the crime was done and the time period where SCO was releasing their code under the GPL was to give them time to "tie up loose ends" with that product line while minimizing the negative impact on their bottom line? It seems like a "victim" of such "theft" should be entitled to pick up the pieces within a reasonable time frame.

      IANAL, but according to copyright law, this is entirely dependant on whether or not it is judged that SCO failed to protect its copyrights when it release the code in question on the very first occurance. For SCO to say that they were fooled by conditions in the GPL is argueably specious and I would think that they have a better defense than that.

    5. Re:"Linux is unaffected" by Anonymous Coward · · Score: 1

      "SCO realizes there is infringing code in Linux, but continue to release their distribution anyway. Perhaps they felt since their code was already infringed upon, why should they be punished in lost sales by pulling their product which was developed unknowingly with stolen code? Could it not be argued that once an invalid license always an invalid license? Since the infringing code was included without their permission, its license under the GPL was never valid."

      Here's the problem with that scenario. If they felt the GPL was invalid and kept shipping their Linux distribution, they are guilty of willful violation of copyright. Without the GPL, they have no right to distribute the vast majority of the software in their distribution, least of all the kernel.

    6. Re:"Linux is unaffected" by jedidiah · · Score: 2, Insightful

      Except SCO is suing someone else for "stealing their source code". SCO can't continue to distribute Linux without "stealing someone else's source code" or giving away their own.

      That's all there is too it.

      They decided to ignore everyone else's intellectual property while whining that their own had been violated.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    7. Re:"Linux is unaffected" by deblau · · Score: 1
      SCO realizes there is infringing code in Linux, but continue to release their distribution anyway. Perhaps they felt since their code was already infringed upon, why should they be punished in lost sales by pulling their product which was developed unknowingly with stolen code?

      Because a company is required by 18 USC 1839 to take "reasonable measures to keep such information secret". As soon as SCO thought there might be trade secret code in Linux, they were obligated to cease distributing the code (and sue IBM, of course) at once, or lose trade secret protection. The other relevant section is 18 USC 1832, which covers theft of trade secrets, and which I imagine is going to be at the heart of SCO's case. Even if SCO win, 1832(b) limits damages to $5 million anyway, which is pocket change for IBM, and not nearly enough to bail out SCO (even with trebled damages). If SCO is looking to this lawsuit to save themselves, they're going to have to go after bigger fish than trade secret misappropriation.

      --
      This post expresses my opinion, not that of my employer. And yes, IAAL.
  44. Re:Mirror for the slashdot effect (Freenet Mirror) by Anonymous Coward · · Score: 0

    Here is a mirror link for Freenet users:

    http://127.0.0.1:8888/CHK@Jct8ig~B7MHAPwJR7ujiaw RJCrEPAwI,teuZ6buZbWFlqH5QRmItsQ

    Other then providing anonymity, Freenet's distributed structure makes it immune to the slashdot effect!

  45. Response To Total Information Awareness: +1, Fun by Anonymous Coward · · Score: 0

    For dossiers on government officials Government Information Awareness

    Cheers,
    W00t

  46. Huh? by azzy · · Score: 1

    What is the matrix?

    1. Re:Huh? by Mistah+Blue · · Score: 1

      A cool movie with Keeanu Reeves and Laurence Fishburne.

    2. Re:Huh? by The+Bungi · · Score: 1

      Something most Slashdot posters think actually exist. But - and herein lies the rub - it doesn't.

    3. Re:Huh? by azzy · · Score: 1

      Ahh.. I know which pill you took!

  47. Lame analysis jumps to conclusions. by Distan · · Score: 4, Insightful

    This whole thing reads like an exercise in assuming the outcome is "Linux is unaffected".

    What if:

    1: A court rules that SCO code has been put into Linux by someone other than SCO.

    2: A court rules that the GPL is non binding upon source code previously released by SCO.

    3: A court rules that any party using such source is and has been in violation of SCO's patents, and is open game for damages.

    No matter what me, or you, or the author of this "matrix" thinks the GPL says, the only thing that matters is what a court decides it says.

    1. Re:Lame analysis jumps to conclusions. by eric76 · · Score: 1

      I think that courts are generally not going to be very impressed by behavior designed to maximize damages rather than to minimize damages.

      If SCO were to identify the code immediately in order to give everyone a chance to analyze it for possible infringements and remove that which is infringing, a judge might be more likely to grant them damages.

      It's kind of like if your next door neighbor threw a rock through your bedroom window. The proper thing to do is to repair or replace the window immediately. If you wait two years for the trial, you may have suffered from quite a bit of water damage, but it is extremely unlikely that your neighbor is going to have to pay for those damages since they were from your own failure to mitigate damages and not from his willful misconduct.

    2. Re:Lame analysis jumps to conclusions. by EzInKy · · Score: 1

      1: A court rules that SCO code has been put into Linux by someone other than SCO.

      Possible...

      2: A court rules that the GPL is non binding upon source code previously released by SCO.

      Then SCO will need to negotiate proper licenses for the code it has been distributing.

      3: A court rules that any party using such source is and has been in violation of SCO's patents, and is open game for damages.

      What patents?

      --
      Time is what keeps everything from happening all at once.
  48. Reminds me of Office Space by pavon · · Score: 5, Funny

    Who needs a decision matrix when you can have a Jump to Conclusions Board ?

  49. Yes, it is also a matrix by Anonymous Coward · · Score: 0

    A Matrix is any multidimensional array which contains data.

    Therefore, the information on the linked page is a matrix. It is a two-dimensional table containing data. The fact that the data is english text rather than a "proper" mathematical object does not change that.

    Within the sci-fi movie, "The Matrix" was a *nickname* for a large software package. The implication seems to be that the reason for this is that the software package is based around a data model where all global state information is stored in a single large matrix-- or, possibly a more complex data model which happens to be designed in such a way that any particular "viewpoint" within the data model can be presented as a simple matrix. This seems fairly reasonable, given nicknames by nature do not necessarily have to describe the thing they describe totally accurately.

    It is a well-known fact that Star Trek is stupid.

    1. Re:Yes, it is also a matrix by tkittel · · Score: 1

      >A Matrix is any multidimensional array which contains data.

      Well not in my world where anything with more than two indices is a tensor.

      But it is quite possible that people in different fields use different conventions - it is after all just a matter of terminology.

      For me a matrix is a useful object because i can invert it, take its determinant, find its eigenvalues, etc. I can't really do that if the entries does not (at least) belong to a group.

      If a matrix is nothing more than a table (or a multi-dimensional table) why not just call it that instead?

    2. Re:Yes, it is also a matrix by Anonymous Coward · · Score: 0
      Well not in my world where anything with more than two indices is a tensor.

      Tension, apprehension, and dissention have begun.

  50. Sticking their heads in the sand by siskbc · · Score: 4, Interesting
    A lot of what they say is complete bullshit. I would love to see Linux come out of this stronger than ever, I really would, but this guy's way off the mark on a lot of things.

    First, he claims that Linux is fine becuase SCO indemnified users. No, only customers of SCO linux. There's a big difference there.

    Then, he claims that Linux is OK because it only affects IBM from a breach-of-contract standpoint. Yeah, except for it establishing a finding of fact that can be used in later suits against linux users/distros.

    Finally, he makes the old, tired argument that the GPL saves us. That's all well and good except that the GPL, being a bit of a non-standard contract, has never been tested in court.

    A great deal of what they wrote is either false or misinterpreted. Like the article in Forbes (I think) last month said, the linux community is NOT served by sticking its collective head in the sand and expecting IBM and the GPL to come riding in on their respective white horses to save us. There are real risks here - granted, some of them are farfetched, but stranger things have happened.

    --

    -Looking for a job as a materials chemist or multivariat

    1. Re:Sticking their heads in the sand by Trailer+Trash · · Score: 4, Interesting

      Finally, he makes the old, tired argument that the GPL saves us. That's all well and good except that the GPL, being a bit of a non-standard contract, has never been tested in court.

      I cringe every time I see this point being made. The GPL isn't relevant, really. If the GPL doesn't "stand up in court", then no problem, standard copyright law takes over. SCO has no other right to distribute the Linux kernel under copyright law beyond those given by the copyright holder.

      What this means practically speaking is that if SCO violated the GPL, and the GPL is declared invalid, then SCO has instead violated standard copyright law. The statutory damages are $150,000 per incident. Everytime someone downloads the Linux kernel source from their website, ka-ching. Every sale that they've made, ka-ching. Pissing off Richard Stallman suddenly sounds like the better way off, eh?

      The bottom line is that SCO continues to distribute the Linux source code. As such, they're either agreeing to distribute it under the terms of the GNU GPL (which don't allow extra burdens to be placed on the code) or they are directly violating copyrights. They are far better off if they get off with a simple GPL violation; $150K/download adds up quickly.

    2. Re:Sticking their heads in the sand by DataPath · · Score: 1

      Just a little fine point - only linux users with kernels containing SCO's "enterprise hardened" code would be subject to royalties in the first place. RCU, JFS, etc don't really touch a lot of users.

      Incidentally, GPL is no more non-standard than the clause in early Unix licenses that had no expiration. They were lacking what's referred to as a "sunset clause" which effectively returns the IP of the involved parties back to their creators at the end of the contract period. SCO is effectively asserting that there wasn't a sunset clause on ANYONE's contracts, and that they therefore own ALL Unix code, whether it was written by AT&T or not.

      In the end, looking at all the shaky issues surrounding SCO's case (patent ownership, questionable licenses that were issued 20-30 years ago, the difficulty in proving that THEY originated the code in question, SCO's opensourced old unixes), there's really no action that CAN be taken. We're only two moves into the chess game.

      --
      Inconceivable!
    3. Re:Sticking their heads in the sand by siskbc · · Score: 1
      Just a little fine point - only linux users with kernels containing SCO's "enterprise hardened" code would be subject to royalties in the first place. RCU, JFS, etc don't really touch a lot of users.

      True, but does the fact that I don't use those features exonerate me? Let's say I'm a large company and I use linux because it's cheap (or whatever), and I think RCU is a university. Does that clear me? I dunno - I mean, I still acquired an OS with those features, whether I compile them into the kernel or not. I bet SCO could consider hitting a company like that.

      Incidentally, GPL is no more non-standard than the clause in early Unix licenses that had no expiration. They were lacking what's referred to as a "sunset clause" which effectively returns the IP of the involved parties back to their creators at the end of the contract period. SCO is effectively asserting that there wasn't a sunset clause on ANYONE's contracts, and that they therefore own ALL Unix code, whether it was written by AT&T or not.

      That's true, and it's a good comparison - the linux community is effectively arguing for one and against the other. So, if you believe in either completely strict or loose copyright law, you lose on one or the other.

      In the end, looking at all the shaky issues surrounding SCO's case (patent ownership, questionable licenses that were issued 20-30 years ago, the difficulty in proving that THEY originated the code in question, SCO's opensourced old unixes), there's really no action that CAN be taken. We're only two moves into the chess game.

      Right, but to continue your metaphor, SCO is playing like the guy who starts throwing his queen around on move 3. He's probably going to do something stupid and kill his game, but it's dangerous for you too. That's where we're at now.

      Do remember too that SCO's strategy doesn't appear to be winning a court case. I believe, as do many, that they're playing for a buyout/payoff. To accomplish that, all they have to do (in their mind) is hurt the value of linux to the point that it makes it worth IBM's cash to have them go away. For that, they don't need a real case, they need FUD. Of which they've provided ample amounts.

      --

      -Looking for a job as a materials chemist or multivariat

    4. Re:Sticking their heads in the sand by DataPath · · Score: 1

      In regards to the Linux community arguing for one and against the other, there are some differences. Other no-sunset clause licenses were shot down in court - there was a precedent. It had lost previously in court. The GPL, as far as I know, has never been central to a court case for its legality to be tested. And I think, in all honesty, that the GPL has never seriously been tested because people on both sides fear testing the GPL - one side because they're afraid it will win, and the other side because they're afraid it might lose.

      In reference to the SCO case, the Linux community is arguing for one and against the other, but that's not really so selfish, because in essence, SCO is doing the same thing to their favor.

      Don't forget that IBM has DeepFritz playing for it.

      If SCO is playing a gambit just to get bought out, its a dangerous one. All it takes is a clear court win for IBM to make the whole SCO thing look like a sad day in history when a little kid threw a temper tantrum. After all, Microsoft lost two antitrust suits in 10 years, and they came away from both with public opinion saying "yeah, what they did was wrong, but not THAT wrong." Linux, I think is just as capable (although I can say nothing to the likelihood) of walking away from this with a nearly untarnished image, that will only improve with time.

      And finally, a disclaimer:
      I'm just playing counterpoint to your arguments, my own views are more middle-of-the-road.

      --
      Inconceivable!
    5. Re:Sticking their heads in the sand by siskbc · · Score: 1
      In regards to the Linux community arguing for one and against the other, there are some differences. Other no-sunset clause licenses were shot down in court - there was a precedent.

      That's of course a fair point, but unless I'm mistaken, sunset clauses are also held up sometimes. Bottom line is, without digging too far into the law, that there's a lot of wiggle room in all of the contract law involved, enough so I wouldn't feel too secure if I were invested in linux.

      The GPL, as far as I know, has never been central to a court case for its legality to be tested. And I think, in all honesty, that the GPL has never seriously been tested because people on both sides fear testing the GPL - one side because they're afraid it will win, and the other side because they're afraid it might lose.

      Ain't that the truth. But that in itself is enough to add enough uncertainty that I'm not as sure of IBM's ultimately victory, which seems to be a foregone conclusion around here.

      In reference to the SCO case, the Linux community is arguing for one and against the other, but that's not really so selfish, because in essence, SCO is doing the same thing to their favor.

      Naturally! But SCO has a few avenues it can "win" on - they're taking the tactic that a bunch of crappy attacks make one decent one. So they could conceivably punt the "sunset" thing, and they have many other bad arguments left. Linux has stronger positions, but has to win effectively all the issues.

      If SCO is playing a gambit just to get bought out, its a dangerous one. All it takes is a clear court win for IBM to make the whole SCO thing look like a sad day in history when a little kid threw a temper tantrum.

      Yes and no. Remember to distunguish SCO the company from the people who are running SCO, who have a lot of stock options made valuable from exactly the behavior they've shown so far (ie, FUD). SCO is currently being run by the Canopy group, lawsuit experts. So if SCO loses this, I'm sure Darl et al have golden parachutes waiting for them, and I bet they've all already cashed out enough options near the $10 share price to cover their initial investment and then some. So they don't expose themselves to the same kind of risk that the company does - but why do they care, eh? Run the company into the ground after cashing out, get a fat settlement, or get a fat award from a court case. Honestly, I can't think of *any* outcome of this that isn't a victory for the people running SCO. They've already won, and isn't that scary?

      And finally, a disclaimer: I'm just playing counterpoint to your arguments, my own views are more middle-of-the-road.

      Hey, no problem. Only thing wrong with playing devil's advocate is the whole being in hell part. ;)

      --

      -Looking for a job as a materials chemist or multivariat

    6. Re: Sticking their heads in the sand by Black+Parrot · · Score: 1


      > That's all well and good except that the GPL, being a bit of a non-standard contract, has never been tested in court.

      It's not that odd. If you buy a house in certain ritzy neighborhoods the purchase contract requires that you not sell the house to anyone of certain 'undesirable' ethnicities, and the contract has an inductive application just like the GPL.

      There may be a legal hole in the GPL, but if so I doubt that it's the part everyone is in doubt about.

      --
      Sheesh, evil *and* a jerk. -- Jade
    7. Re:Sticking their heads in the sand by Dastardly · · Score: 1

      First, he claims that Linux is fine becuase SCO indemnified users. No, only customers of SCO linux. There's a big difference there.

      Not that big of a difference because there is only 1 way to indemnify SCO linux users.... License Linux including their code to their customers under the GPL.

      Here is why.

      If the SCO code in Linux is not licensed to their customers under the GPL. Then, those customers cannot use SCO Linux because they are not licensed to use the rest of the Linux code because that code is licensed under the GPL.

      Basically, what it comes down to for SCO is that either they have licensed the SCO code in Linux to their customers under the GPL, and by extension everyone. Or, they have not, and therefore no one is licensed to use Linux. There is no middle ground where some are licensed under a different license, and some have no license at all.

      Assumption: The GPL is upheld as written.
      IANAL

      Dastardly

    8. Re: Sticking their heads in the sand by ReconRich · · Score: 1

      If you buy a house in certain ritzy neighborhoods the purchase contract requires that you not sell the house to anyone of certain 'undesirable' ethnicities

      If you're in the USA, I wouldn't try enforcing that in court - housing discrimination due to race is illegal. Combine this with the fact that a contract with an illegal provision is invalid (except in the case in which both parties agree that the contract is "separable", which means only the illegal provision is invalid. Separability can be struck down by a judge though, so watch out). This could make the whole contract invalid. Ritzy neighborhoods hate that.

      -- Rich

      --
      Free your mind and your Ass will follow -- George Clinton
    9. Re: Sticking their heads in the sand by Black+Parrot · · Score: 1


      > > If you buy a house in certain ritzy neighborhoods the purchase contract requires that you not sell the house to anyone of certain 'undesirable' ethnicities

      > If you're in the USA, I wouldn't try enforcing that in court - housing discrimination due to race is illegal.

      OK, maybe the courts don't tolerate it anymore. (I was surprised that such arrangements were legal when I first heard of them.)

      The underlying concept that I was groping for was "covenant running with the land", described here as -

      A covenant runs with the land when the burdens, benefits, or both pass to succeeding holders of the estate.
      So the "running" nature of the GPL is not actually a legal innovation.

      Of course, "covenants running with the land" may have explicit legislative endorsements in land ownership laws, in which case a court might not be willing to generalize the concept to copyrighted material. But the basic idea of the GPL isn't the legal novelty that everyone presumes it is.

      --
      Sheesh, evil *and* a jerk. -- Jade
    10. Re:Sticking their heads in the sand by Maserati · · Score: 1

      No no no. The GPL issue is with SCO distributing the GPL'd code, not with the end user's use of the software. The GPL has exactly zero restrictions on use of software, only on its distribution. They have tainted intellectual property (if such a thing is anything more than a legal hallucination), but they do not have stolen property.

      So they don't have to reinstall their servers, but they might want to switch distros because their support contract with SCO is about to vanish in a puff of Chapter 7.

      --
      Veteran, Bermuda Triangle Expeditionary Force, 1992-1951
    11. Re:Sticking their heads in the sand by Citizen+of+Earth · · Score: 1

      They are far better off if they get off with a simple GPL violation; $150K/download adds up quickly.

      Your notion here seems a little strange. A "simple GPL violation" *IS* a copyright violation. You're copying something while violating the license that would have given you the right to do so; result: you have no right to copy the thing and you are violating the authors' copyrights. Ka-ching! $150K!

      It's merely because of the generousness of the GPL community that violators of the GPL heretofore have gotten off lightly by modifying their practices to stop the violation, but this community might not be quite so kind to SCO. Linus, et al. should counter-sue SCO for copyright infringement. This would make a big story in the press and SCO's stock price would take a panic attack.

    12. Re:Sticking their heads in the sand by Znork · · Score: 1

      "And I think, in all honesty, that the GPL has never seriously been tested because people on both sides fear testing the GPL - one side because they're afraid it will win, and the other side because they're afraid it might lose."

      Not really. People on the infringing side fear testing the GPL because they lose wether they win or lose. If they lose they have to follow the terms of the GPL, if they win they still dont gain the right to distribute someone elses copyrighted code.

      The FSF side has not been the least afraid they might lose. They have tended to approach the enforcement aspect out of court first, as compliance with the GPL has been considered more important than nailing someone to the wall tho. This far that strategy has been very successful.

      A GPL violation automatically becomes a copyright violation as the GPL is what grants you the right to distribute copyrighted code. The question of wether or not you may distribute copyrighted code without permission has been very well tested in court. Any infringer faces the risk of going up against well established precedent and criminal charges for copyright violation.

    13. Re: Sticking their heads in the sand by Znork · · Score: 1

      That analogy is flawed. Restrictions in who you can sell to would be restrictions in the rights you ordinarily have under the law, which is entirely different from the GPL.

      A better analogy would be if you rent a house and wish to tear down a wall. The landlord could require that you adhere to certain standards or even employ certain contractors to do the work, as you would not ordinarily have the right to tear down a wall in property you do not own.

      The GPL sets the terms under which you may do things you're not legally allowed to do otherwise. This is entirely different from restricting you from doing something you are otherwise legally entitled to do.

      In both cases you need the permission of the actual owner to engage in what you wish to do. Without that permission you just cant do it.

    14. Re:Sticking their heads in the sand by Anonymous Coward · · Score: 0
      Finally, he makes the old, tired argument that the GPL saves us. That's all well and good except that the GPL, being a bit of a non-standard contract, has never been tested in court.

      Well if the GPL is invalid, it's pretty much a huge part of Linux and GNU which collapses anyway.

    15. Re:Sticking their heads in the sand by Dastardly · · Score: 1

      No no no. The GPL issue is with SCO distributing the GPL'd code, not with the end user's use of the software. The GPL has exactly zero restrictions on use of software, only on its distribution. They have tainted intellectual property (if such a thing is anything more than a legal hallucination), but they do not have stolen property.

      But, if a portion of the code belongs to SCO, then SCO has to distribute the Linux under the GPL. If SCO did not distribute the code according to the GPL, then the users of that code cannot use it. Because either/and:

      1) They are not licensed to use SCO's code.
      2) SCO is not licensed to Distribute Linux wth SCO's code because they did not distribute under GPL.

      There are only two choices: SCO's code is distributed in Linux according to the GPL. Or, SCO's code is not GPL's and therefore Linux distributed with SCO's code is illegally distributed because the Linux code requires GPL to distribute.

      An interesting implication here is that SCO cannot get royalties for their code in Linux. They can get judgements/settlements for copyright violation, but if they don't want their code GPL'd then it cannot be in Linux. Kernel hackers will have to remove the code and all versions with SCO code will have to be removed. The GPL does not allow SCO to license their code under a different license.

      Note, this is not relevant to the IBM case. If IBM put the code in Lnux in violation of their license they are still on the hook., whether SCO chooses to leave the code GPL'd in the future, or force it to be removed is a decision SCO can make independent of the IBM results.

      IANAL
      Dastardly

    16. Re: Sticking their heads in the sand by ReconRich · · Score: 1

      I was surprised that such arrangements were legal when I first heard of them

      They probably weren't (after sometime in the '70s). However, if everybody in the neighborhood agrees with them, no "undesirables" ever show up, etc. it'll never see the inside of a courtroom. What it does do is make a "club" of people who keep the "undesirables" out by social pressure/manipulation.

      -- Rich

      --
      Free your mind and your Ass will follow -- George Clinton
  51. so this essetially says... by WPIDalamar · · Score: 0, Offtopic

    hey sco ... STFU

  52. Agreed by michaelggreer · · Score: 1

    Nothing new, just more opinions. Using the corporate "formatting means expertise" method is not especially helpful, but it is clear and well-done.

  53. They forgot a scenario by toastyman · · Score: 4, Funny

    SCO hires Johnny Cochrane

    Likelihood: Very likely

    Evidence: While SCO has not yet hired Johnny Cochrane on their legal team, most pundits (John Dvorak included) are predicting it.

    What if SCO does: Chewbacca is a Wooky from the planet Kishic, but Chewbacca lives on the planet Endor. Now think about it. That does not make sense. Why would a Wooky, an eight-foot-tall Wooky, want to live on Endor with a bunch of two-foot-tall Ewoks. That does not make sense. But more important, you have to ask yourself what does this have to do with this case.

    Nothing. Ladies and Gentlemen, it has nothing to do with this case.

    It does not make sense. Look at me. I'm a lawyer working for a major software company and I'm talkin' about Chewbacca. Does that make sense? Ladies and Gentlemen I'm am not making any sense. None of this makes sense. And so you have to remember when you're in that jury room deliberating and conjugating the Emancipation Proclamation, does it make sense? No. Ladies and Gentlemen of this deposed jury it does not make sense. If Chewbacca lives on Endor you must convict. The prosecution rests.

    Final Outcome: Linus Torvalds wakes up in his bed and says, "Mom? I just dreamt that me and IBM and SCO were trapped in a court case that made no sense and we were talking about everything that happened to us except that it was all wrong, and ended with us eating ice cream."

    I think I know where my bet is.

    1. Re:They forgot a scenario by localghost · · Score: 1
      Evidence: While SCO has not yet hired Johnny Cochrane on their legal team, most pundits (John Dvorak included) are predicting it.
      Main Entry: 1wrong
      Pronunciation: 'ro[ng]
      Function: noun
      Etymology: Middle English, from Old English wrang, from (assumed) wrang, adjective, wrong
      Date: before 12th century
      1 a : an injurious, unfair, or unjust act : action or conduct inflicting harm without due provocation or just cause b : a violation or invasion of the legal rights of another; especially : TORT
      2 : something wrong, immoral, or unethical; especially : principles, practices, or conduct contrary to justice, goodness, equity, or law
      3 : the state, position, or fact of being or doing wrong: as a : the state of being mistaken or incorrect b : the state of being guilty
      4 : prediction of John Dvorak
    2. Re:They forgot a scenario by Anonymous Coward · · Score: 0

      It's written that way: Kashyyyk, Wookie

  54. Basic spelling 101 by Anonymous Coward · · Score: 0

    ITYM 'choir'...

  55. A year? hahahahaha by sterno · · Score: 4, Insightful

    We won't have a decision in a year. Think about how long the Microsoft case dragged out. IBM is going make sure to drag this out and make it as expensive for SCO as possible. By the time any decisions will have been rendered by a judge, it will likely be irrelevant.

    --
    This sig has been temporarily disconnected or is no longer in service
  56. Lawsuit is irrelevant by scsirob · · Score: 4, Insightful

    We can argue over the outcome of a lawsuit forever, but the damage has long been done. It's not about a lawsuit, it's about reputation. And Linux' reputation will be tainted for a very long time to come.

    Any company with an axe to grind towards Linux wants this story dragging on forever. For all we know, even IBM may be involved, as it gets a lot of media coverage over an issue that's not about their core business... You may have noticed this is all dragging on between large corporations. Their world, the world outside /., revolves around MONEY, and any way they can make it is acceptable.

    --
    To Terminate, or not to Terminate, that's the question - SCSIROB
    1. Re:Lawsuit is irrelevant by Darth · · Score: 3, Insightful

      We can argue over the outcome of a lawsuit forever, but the damage has long been done. It's not about a lawsuit, it's about reputation. And Linux' reputation will be tainted for a very long time to come.

      yeah. I mean, look at the chilling effect it has had on the adoption of linux by major japanese multinational corporations. Since this lawsuit, there's only been one international organization of major corporations formed to utilize embedded linux in their future products.

      The business world wont care about SCO's ip threats as long as they are sure SCO can be neutered. Businesses (generally speaking) will violate any law they think they can get away with, as long as there's money in it.

      --
      Darth --
      Nil Mortifi, Sine Lucre
    2. Re:Lawsuit is irrelevant by DeadSea · · Score: 1
      Their world, the world outside /., revolves around MONEY...

      This article shows how unlikely it would be for the SCO lawsuit (or its fallout) to cost a Linux using company any MONEY.

      SCO is sowing fear, uncertainty, and doubt, and the article puts it in perspective. The absolute worst that could happen to the average company that has used Linux is that they have to pay a small licensing fee to SCO for the prior use of SCO code. In actuality, SCO will stumble at some point in their crusade. If that scares a business away from Linux, that business needs to do a better job of risk management.

    3. Re:Lawsuit is irrelevant by GoofyBoy · · Score: 1


      It is a serious chilling effect.

      Its not only SCO, but how will any company out there know that there isn't some patent infringement lurking in the code somewhere?

      A Blue Screen of Death is an inconvenence for the vast majority of companies. The potential of legal action/paying damages is something that makes any CEO sit up and take notice.

      --
      The surprise isn't how often we make bad choices; the surprise is how seldom they defeat us.
    4. Re:Lawsuit is irrelevant by Darth · · Score: 1

      how is that different than the patent infringement claim going through the courts against microsoft right now?

      That problem exists in closed source as well. It's just impossible to do any oversight when dealing with closed source solutions.

      --
      Darth --
      Nil Mortifi, Sine Lucre
  57. The most damning thing for SCO... by Eric+Damron · · Score: 1

    may be that they continued to release a version of Linux for two months after they notified IBM that they felt some code was infringing.

    It will be up to a Judge to determine if SCO acted in a timely manner but I don't think that they did.

    --
    The race isn't always to the swift... but that's the way to bet!
  58. Hurd by Anonymous Coward · · Score: 1, Funny

    Don't you think we should all switch over to GNU/Hurd anyway, just in case?

    1. Re:Hurd by Sanction · · Score: 1

      Hmm, with the speed of the US "justice" system, the Hurd should at least be in beta by when the case is done with appeal :)

      --
      Well I'm the doctor and I say you're dead, so shut up and take it like a man!
  59. Linux is unaffected? by John+Harrison · · Score: 3, Insightful
    Though "Linux is unaffected" is listed as the outcome of every possible scenario, this conclusion hinges on the argument that SCO continued to distribute Linux after the lawsuit. This would have the effect of causing the offending code to be placed under the GPL and thus the problem is solved.

    I think this logic is a simplification of the legal situation, and is being used as an ace-in-the-hole by author. The author is making the assumption that the court will agree with this catch all and so none of the other aspects of the case matter.

    He should write another matrix with the assumption that the "donated to the GPL" argument has failed. That would be more interesting.

    I don't think the SCO has a case, but I can at least imagine a scenario in which Linux would be affected.

    1. Re:Linux is unaffected? by spitzak · · Score: 2, Interesting
      In that case they have violated the copyrights of all other contributors to Linux. You are not allowed to distribute Linux except under the GPL, otherwise you are violating copyright.

      Their only possible excluse is to claim lack of knowledge of putting the code into Linux. However: their failure to immediately stop distributing it before or when they published their claims, their failure to provide instructions on how to remove the offending code from the previously-distributed versions and thus make them GPL-compliant, and most damaging their claim that their own customers are not in trouble but other users of Linux are, are all going to be very bad for them. Each of these is a good proof that they knowingly violated the GPL and thus the copyrights of thousands of programmers.

    2. Re:Linux is unaffected? by John+Harrison · · Score: 1

      What if they choose to attack the GPL? Everyone has been waiting for the courts to weigh in on it, maybe this will be the case in which it happens.

    3. Re:Linux is unaffected? by spitzak · · Score: 1
      No, if the GPL is invalid than they violated copyrights by giving away the code. Nothing other than the GPL allows them to redistribute the code. They would lose badly unless they could successfully eliminate copyright itself.

      There is enormous corporate interest in keeping copyright the way it is, including the ability to allow a receiver to violate a copyright in carefully prescribed ways (ie only your customers or the printing company you hired or a palladium-enabled browser is allowed to violate the copyright). Any useful attack on the GPL would be an attack on that, and the value of Linux (or of eliminating Linux) is diddlysquat compared to that.

  60. It'd be difficult by sterno · · Score: 2, Insightful

    First of all SCO has to proove that copyrights were actually infringed. Then after they proove that, which won't be easy, they will have to proove that their release of the code under the GPL was an accident. Neither one of these is easy to proove, and proving both would be an amazing feat.

    --
    This sig has been temporarily disconnected or is no longer in service
    1. Re:It'd be difficult by Anonymous Coward · · Score: 0

      You misspelled 'prooving', looser.

  61. Matrix by pulse2600 · · Score: 2, Funny

    Looks like we just slashdotted The Matrix! The machines no longer have control over us!!!!

  62. Final Outcome by curtisk · · Score: 1
    5 minutes of my time has been affected.

    While good in concept, there's too much tilt on this analysis. The case could hinge simply on the judge's possible dislike for Penguins, or that he plays golf with Orrin Hatch and his son, or that SCO spins the "open source leaders'" comments so far out of whack

    O.J. is running free, whodathunkit? It seemed like an open and shut case. But after all, if the glove doesn't fit, you must acquit! .....right?

    --

    Sehr geehrter Toilettenbenutzer!

  63. Looks like Tux dropped some foam... by Anonymous Coward · · Score: 0

    ...cause SCO is going up in flames.

  64. Hmm. by Dthoma · · Score: 1

    Ok, GIMP wizards! Now's youre chance to shine. Bring us Matrix Reloaded screen captures with Linus' face oover Reeves', and Darl's over Smith's in the Big Brawl..."

    Wow, normally I'd have to pay for that kind of entertainment!

    --

    Note to M1-ers: a curt but otherwise insightful message is not "Flamebait" or "Troll".

    1. Re:Hmm. by Maserati · · Score: 1

      That's the funniest thing I've ever seen NOT modded up.

      Insightful too...

      --
      Veteran, Bermuda Triangle Expeditionary Force, 1992-1951
  65. thank god! another SCO article by Anonymous Coward · · Score: 1

    I was feeling lonely and sad, because lately I haven't seen hide
    nore hare of a SCO post. But now slashdot has once again turned
    my frown upside down. Darl McBride can speak japanese so now
    he is a bi-lingual con artiest. this reminds me when my parents
    divorced, my mother wanted money from my fathers new wife because she stole him away. SCO just needs to get over it.
    until they produce a decent product it doesn't matter how much
    they bully around opposing UNIX like OS's no one is
    going to buy their product.

  66. SCO vs. IBM vs. [INSERT YOUR NAME HERE] by oaf357 · · Score: 3, Interesting
    It is a tad biased. However, if you take away the editorial it can be very helpful to public analysis of the case.

    Perhaps someone could release a "spin-free" version of this document and then let readers draw their own conclusions. I imagine that a few of the conclusions would correlate with this matrix.

    This matrix seems like a shot at SCO's attempt to win this case in public as opposed to in court. We all know that this is going to take quite some time to muddle through the court system. We also all know that the courts will have the final decision in this matter.

    1. Re:SCO vs. IBM vs. [INSERT YOUR NAME HERE] by Anonymous Coward · · Score: 1, Interesting

      However, if you take away the editorial it can be very helpful to public analysis of the case.

      Um, if you took away the editorial parts, you would only be left with "Linux r00lz!!!"

    2. Re:SCO vs. IBM vs. [INSERT YOUR NAME HERE] by daviddennis · · Score: 1

      No, you wouldn't, because that itself is an editorial part!

      I thought it was pretty well done in setting out the various arguments. It was a little repetitious in its claims that Linux would be entirely uneffected, but it's difficult not to come to that conclusion in any event.

      I believe Linux would in fact be affected by one specific scenerio. If IBM put SCO's code into Linux, and that code was copied on to millions of machines through distributions such as Red Hat, there would be a genuine copyright infringement, and Red Hat et al would be liable. Companies using Linux might also be liable, but only until they upgraded their distributions to ones without the infringing code.

      You could theoretically put Red Hat et al out of business that way, and make SCO the only legal Linux distribution. But I don't think SCO would bother, simply because the Linux distribution companies never had enough money to matter. The potential reward wouldn't even cover the costs of litigation.

      However, I think by far the most likely version of events is that IBM copied old BSD code, and that was a perfectly legal act. IBM may be a conservative, stuffy, blue-nosed company filled with lawyers, but, well, sometimes it's actually GOOD to be a conservative, stuffy, blue-nosed company filled with lawyers, and this is one of those times.

      What a strange story this is. I didn't think I'd ever hear of a case where open-source programmers are rooting unapologetically for gigantic International Business Machines Corporation and its lawyers to make mincemeat out of a tiny outfit that probably doesn't have the total annual revenues of IBM's legal department.

      And - even stranger - they are absolutely right to do so.

      Go, IBM legal, go!

      (I never thought I'd ever hear myself make that kind of statement!)

      D

  67. Re:Mirror for the slashdot effect (Freenet Mirror) by jonathan_ingram · · Score: 2, Funny

    Freenet links are only immune to the Slashdot effect to the extent that, due to the nature of the system, *every* Freenet link feels Slashdotted, no matter how popular it is.

  68. SCO did NOT indemnify Linux! by Anonymous Coward · · Score: 0

    Several times in the matrix, they make this claim: "Further, SCO have also indemnified all users of Linux against any prosecution7"

    However, SCO simply *assured* Linux users that they wouldnt be sued. Since when is that an indemnity?! SCO is under no legal obligation to stick to what they wrote in a letter in which they merely seek to "assure" people.

    IANAL, so I stand to be corrected on this.

  69. Somthing is not kosher here... by Anonymous Coward · · Score: 0

    Ok, let's say, for the point being, that SCO is totally correct in every accusation they make (holy shit!) and that there's some of their copyrighted code that accidentally made it into Linux. They removed the code from their own distribution, and asked that everyone else follow suit. But the claim is that once you go GPL it's GPLed for ever, yet I've had conversations with people on here (slashdot) that claim the opposite. And they're self-styled "experts" on OSS and GPLed code. So... if it was a mistake (by whomever, and it really doesn't matter who fucked that up) then SCO is well within their rights and legally acting and their code can be, and must be, un-GPLed...but it can't be because, like the dead once you're buried it matters not how you died.

    Should not intent become part of the equation? If SCO made a mistake (or IBM or martians with satelite dishes...whoever) then the code has to go back to propietary. Especially if the persons responsible did not have the authority to donate such code. Right? If the GPL doesn't allow for such, then GPL is fux0red beyond redemption.

    1. Re:Somthing is not kosher here... by EzInKy · · Score: 1

      I don't think the argument is that their code can't be "un-GPL'd" so much, it's more of if their code is "un-GPL'd" then SCO has been distributing other people's copyrighted code without a proper license because they didn't follow the terms of the GPL.

      --
      Time is what keeps everything from happening all at once.
  70. Re:A year? hahahahaha by HiThere · · Score: 3, Informative

    Based on the way SCO is spending money, I'm fairly sure that the intention is mainly to cause MS to spend money. Yesterday, e.g., I received a "Presorted STD" publication from SCO. I have no idea why, and called them up to ask to be removed from their mailing list (will they? ??).

    FWIW, SCO can be reached at:
    1-800-726-8649

    The editor of the ad was at ptaylor@sco.com
    He invites comments. (No particular note on what kind of comment was desired.)
    Another mailing address is info@sco.com, but they don't particularlly ask that comments be sent there.

    Of note is that they claim that Java 1.3.1 and the Java runtime are Open Source tools. (I suppose that Sun may have changed the license, but the last time I looked the binaries were definitely NOT open source, much less Open Source, though parts of it might have reasonably been called that.)

    But sending out a mass mailing to people who aren't even vaguely interested in your product doesn't sound to me like a company interested in conserving it's financial resources.

    --

    I think we've pushed this "anyone can grow up to be president" thing too far.
  71. transpose tables by nslu · · Score: 2, Informative

    Hesse Ruderman has a bookmaklet to transpose tables (which would rotate table pi/2 radians, making it tall & narrow & readable), works in mozilla, opera, ie.

    look there:
    http://www.squarefree.com/bookmarklets/pag edata.ht ml

  72. That would be the worst thing for Linux by GoofyBoy · · Score: 5, Insightful

    Meeting:

    Tech guy 1: Lets implement Linux, its free and robust.
    Tech guy 2: Lets go with Windows, it costs more but there is that lawsuit which if SCO wins we might have to pay some undefined charges.
    Boss: What lawsuit?
    Tech guy 1: <goes on about how its fruitless and how SCO is the devil and blah blah blah repeating every Insightful post he's read on slashdot>
    Boss: So Linux might or might not be infringing on someones code and we might be opening the company to legal action?
    Tech guy 1: Yes but its just games that SCO...
    Boss: Which version of Windows should we get?

    So the longer this lawsuit goes on, the more decisions like this will have to be made.

    --
    The surprise isn't how often we make bad choices; the surprise is how seldom they defeat us.
    1. Re:That would be the worst thing for Linux by jfinke · · Score: 5, Informative

      Thank you. That is exactly what has happened at my company. My linux servers (which were soon going into production) are being formated with W2K as we speak.

    2. Re:That would be the worst thing for Linux by _Sprocket_ · · Score: 5, Insightful


      My linux servers (which were soon going into production) are being formated with W2K as we speak.


      Sucks to be you. MY boss, already impressed with the existing production Linux servers and our development environments, has asked me how we can go about getting MORE linux in to our production environment. And I am currently hashing out an IT plan for a new system that is based on Linux (although its more like a network appliance).

      It is expected that SCO's publicity stunt is going to affect some IT managers. Especially with the implied backing of Microsoft. But I question just how much "damage" is really being done.

      To be honest, I expected my situation to be simular as the parent poster's. I am currently in a very conservative environment that has not always embraced Open Source (or more accurately, like many other organizations, it wasn't fully aware of Open Source in its midst). Seeing this conservative (and very Windows-centric) environment embracing Linux and MacOS X is rather interesting. Watching it continue this trend despite the FUD is facinating.

      Wish your boss had the same outlook as mine.
    3. Re:That would be the worst thing for Linux by EvilTwinSkippy · · Score: 2, Insightful
      Don't worry, you'll be formatting them back the next time the BSA gets a bird up it's ass about your company's licenses.

      Lets see, Linux lawsuits... Zero (1 outlandish one pending.) Windows lawsuits...

      • Well you have your run of the mill disgruntled employee dimes you out for alleged infractions
      • There is still the pending patent nastiness with SQL 2000
      • Hmm, Stacker anyone?
      --
      "Learning is not compulsory... neither is survival."
      --Dr.W.Edwards Deming
    4. Re:That would be the worst thing for Linux by mcdrewski42 · · Score: 1

      Boss: Which version of Windows should we get?

      Perhaps someone should should really be talking to this guy:

      Law guy 1: due diligence - "The process of investigation, performed by investors, into the details of a potential investment, such as an examination of operations and management and the verification of material facts."

      --
      /* affect != effect */ void affect(int *thing,int effect) { *thing += effect; }
    5. Re:That would be the worst thing for Linux by Anonymous Coward · · Score: 2, Funny

      I wish my boss didn't have outlook at all. Fucking worms keep ruining my weekends.

    6. Re:That would be the worst thing for Linux by jfinke · · Score: 2, Informative

      Yep, well you are lucky one. It cracks me up to see all these posters talking about how this lawsuit doesn't matter. It is affecting the adoption of Linux. I was bringing these boxes in as low cost alternatives to Solaris and Sparc. Now, they are being converted to W2K. Wish I had decided to force them to spend more money! :) Funny thing is that legal hasn't said a word about the fact that we are running AIX boxes everywhere. That point really puzzles me, since they are the ones that SCO is going after! Oh well, it is a funny world that we live in.

    7. Re:That would be the worst thing for Linux by Anonymous Coward · · Score: 1, Insightful

      > Funny thing is that legal hasn't said a word about the fact that we are running AIX boxes everywhere. That point really puzzles me, since they are the ones that SCO is going after! Oh well, it is a funny world that we live in.

      Legal is looking at IBM as a lawsuit target of their own if SCO turns out to be right and AIX can't be used. Legal will expect IBM to indemnify them, and sue if not so.

      Who would this scenario apply to for Linux? Which distro were you going to use? Did they have a large enough [I assume] U.S. presence to be sueable if needed?..

    8. Re:That would be the worst thing for Linux by _Sprocket_ · · Score: 2, Interesting


      Legal is looking at IBM as a lawsuit target of their own if SCO turns out to be right and AIX can't be used. Legal will expect IBM to indemnify them, and sue if not so.


      So what you're saying is buy IBM Linux solutions.


      Who would this scenario apply to for Linux? Which distro were you going to use? Did they have a large enough [I assume] U.S. presence to be sueable if needed?


      Now this presents an interesting problem. You're going to want someone big enough to sue. But you don't want them too big or they'll have better lawyers. Of course, you don't want them to be too small or there will be nothing left to sue if you don't act fast enough.

      Maybe there's a better business strategy than "who can we sue".
    9. Re:That would be the worst thing for Linux by fanatic · · Score: 3, Insightful

      Thank you. That is exactly what has happened at my company. My linux servers (which were soon going into production) are being formated with W2K as we speak.

      Your boss is a dumbshit and you should have argued harder because:

      • Never heard of Timeline vs. Microsoft ? This is a proven, decided case - where MS SQL developers have infringed by using software the received from Microsoft - not the unfounded assertions SCO is making.
      • IBM, Oracle, Dell, CELF, and others are all going full speed ahead because they know it's nonsense.
      • SCO's suit agains IBM is a contract dispute with IBM. Even if they win, it's a, (probably impossibly) long way to get from there to collecting the first penny from a Linux user. Since, as Novell states, SCO doesn't own the patents on UNIX, any offending code (IF there is any) can be written around.
      • I was looking at the windows kernel and saw binary sequences identical to those in some of my programs. I'm suing Microsoft! They owe me a trillion dollars!. I'm going after all users of Microsoft products! They owe me 2 trillion dollars! What's your idiot boss going to do now? "Omigod, someones suing Microsoft".
      Honestly, I'm not thrilled with my managment but they they've got it hands down over your boss.
      --
      "that's not encryption - it's a new perl script that I'm working on..." - from some Matrix parody
    10. Re:That would be the worst thing for Linux by Anonymous Coward · · Score: 0

      1 800 BSA ROCKS

      what's the name of your company again?

      "and then those home burned cd's of win2k flew out the window so fast they left an afterimage on my retinas"

    11. Re:That would be the worst thing for Linux by bayduv1n · · Score: 2, Insightful

      Risk Management 101

      Likelihood that your company will be sued by SCO - unlikely

      Likelihood that your company will undergo a Microsoft Licence audit - very likely

      Expected cost of SCO damages to your company - approaching zero

      Expected cost of purchasing additional MS licences - several thousands of dollars

    12. Re:That would be the worst thing for Linux by Anonymous Coward · · Score: 0

      You mistyped 'C' as 'R' up there.

    13. Re:That would be the worst thing for Linux by Trogre · · Score: 1

      Perhaps Tech Guy 1 needs to explain that Linux is a heck of a lot less illegal than Windows.

      If I had to make a decision based on which one I think will be around in ten years, I know which one I'd be picking, and it wouldn't be coming from Redmond.

      --
      "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
    14. Re:That would be the worst thing for Linux by unoengborg · · Score: 1

      Boss: Which version of Windows should we get?

      Tech guy 1:
      One that we are sure doesn't contain BSD code.
      As SCO have hinted that even systems using BSD code may be at risk.

      Boss:
      What versions doesn't have BSD code in them?

      Tech guy 1:
      We don't know. Only MS knows that for sure. But at least the IP stack in windows is believed to be of BSD origin. To be be reasonalbe sure of avoiding lawsuits we should use Solaris as Sun Microsytems had a much better deal with AT&T than all other Unix venders.

      --
      God is REAL! Unless explicitly declared INTEGER
    15. Re:That would be the worst thing for Linux by Anonymous Coward · · Score: 0

      umm... would it be Windows?

    16. Re:That would be the worst thing for Linux by SlashDread · · Score: 1

      Tech guy 1: Lets implement Linux instead of this crappy Open Server/UnixWare. Mind you, our database vendor, prefers Linux.
      Tech guy 2: Lets not. Its dangerous. We rely on trust from our customers.
      Tech guy 1: Lets provide our customers with trust, lets get support from IBM. Let us make money from trust.
      Boss: IBM is doing Linux? Our Database vendor wont support SCO in time? Lets switch NOW. /Dread

    17. Re:That would be the worst thing for Linux by GoofyBoy · · Score: 1

      Let me repeat myself;

      Tech guy 1:

      Thats sort of what you are doing.

      What does the boss think? I am potentially opening myself up to having to justify my decision to my boss, the CEO, the legal department when I could have stuck with the crowd.

      I can explain why I need to spend for a $1000 a Windows license to my boss.
      I don't think I can, or would even want to risk, explaining why did I use something which has a questionable legal status.

      You might say "But the legal status is not questionable...."

      Your boss doesn't even want to have to begin to have that converstation.

      --
      The surprise isn't how often we make bad choices; the surprise is how seldom they defeat us.
    18. Re:That would be the worst thing for Linux by fanatic · · Score: 1

      Let me repeat myself: Some Microsoft users have real, it'-been-to-court, proven, actually for real liability, as opposed to the nonsense SCO is spouting. Why is Windows the preferred alternative inb the face of actual facts?

      Sorry, but do we really have to abandon a product because somebody says that their uncle said his brother-in-law sow some code in there that mught infringe? Get real. nothing has been proven,

      --
      "that's not encryption - it's a new perl script that I'm working on..." - from some Matrix parody
  73. Re:Icon for this argument by tomhudson · · Score: 1

    We already do: Bill Gates as the Borg.

  74. The Matrix... by c4Ff3In3+4ddiC+ · · Score: 1

    Is it possible to slashdot The Matrix?? I thought so...

    --
    *twitch*
  75. Matrix, SCO link by phorm · · Score: 1

    Hmm... Decision Matrix... Matrix. I can already see the relevance in regards to the code that has supposedly been copied by Linux...

    "Unfortunaly, no one can be told what the source code is. You have to see it for yourself. After signing our huge NDA, of course!
    Linux user? Just follow the agen... er gentleman in the dark suit"


    Somehow I think that SCO took the wrong pill, they're still a bit out-of-touch with reality :-)

  76. SCO still distributing the code by Tom7 · · Score: 1

    It's interesting that SCO is still distributing the linux source code right now.

    This matrix is obviously a bit biased, but I do believe that linux will be able to legally continue to exist, no matter what. Even if we find out that someone broke into SCO's vaults and stole trade secret source code and pasted it verbatin into linux, it really should be easy to rewrite that code so that it's not infringing. We could start today if SCO told us what parts were infringing, but of course they don't want that...

  77. Judge Gate on the Case by infonography · · Score: 1

    Judge Gates - SCO wins the Lawsuit, the Linux Users are sentanced to 40 years Using Windows ME, with Microsoft Bob preinstalled.

    --
    Sorry about the writing. Robot fingers, you know? Cliff Steele in DOOM PATROL #23
  78. On the contrary by Royster · · Score: 1

    In the MySQL infringement case that the GPL was the contractual basis for the suit and the standard for behavior of both parties was not even a question. The license was part of the case and the judge was ready to enforce it.

    Anyone who doubts that the GPL is enforcable has a fool for a lawyer. Now it may not be completely enforcable in the way that GNU zealots claim, but as an IP license, it is on very strong footing in a court of law.

    The lack of legal challanges to the validity of the GPL should be viewed as a tacit admission of its validity.

    --
    I have discovered a truly marvelous sig, unfortunately the sig limit is too small to contain i
  79. Final Score by douglips · · Score: 1

    I think there is a typo in this matrix. The bottom line should read:

    Final Score: FATALITY!

  80. pregnant cows by jfm3 · · Score: 1

    "SCO claims that they were duped into releasing the source code initially, that they didn't realise that the Linux kernel had their source code. There has also been much discussion about legal precedent on this, relating to the selling of pregnant cows."


    For some reason, pregnant cow selling laws sound very funny to me. I googled a bit but couldn't come up with anything. Can somebody clarify what what "legal precedent" relating to pregnant cows they're refering to?

    1. Re:pregnant cows by cyphergirl · · Score: 1

      (see my post above -- replied to the thread instead of to your post)

      --
      --Insert catchy .sig line here--
  81. how annoying by infonography · · Score: 1

    http://www.vcnet.com/bms/departments/innovation.sh tml#bob Let's see if it come out right now.

    --
    Sorry about the writing. Robot fingers, you know? Cliff Steele in DOOM PATROL #23
  82. On cows and such... by cyphergirl · · Score: 1

    Farmer A has a cow for sale. Farmer B wants to buy the cow. They agree on a price. Farmer B forks over the cash and takes his new cow home. Sometime later, the cow gives birth.

    Farmer A is pissed because if he had known the cow was pregnant, he would have doubled the price. Farmer B is a happy camper cuz he got a freebie.

    --
    --Insert catchy .sig line here--
  83. derived SCO table by jfroebe · · Score: 1

    select operating_systems.name, derived_table_1.SCO_Property,
    derived_table_1.ord ers, derived_table_1.whine,
    str_replace(legal.action, "settle", "litigate")
    from operating_systems,
    (select
    str_replace(source_code, "Linus Torvalds", "SCO Unix")
    as "SCO_Property",
    case money.company
    when "Microsoft"
    then "Do as master orders"
    when "Gates Foundation"
    then "Do as master orders"
    when "IBM"
    then "Revoke Unix license"
    when "Sun"
    then "Pretend Sun is master but do what real master orders"
    else
    "Blame Linux stole Unix source code"
    end as "Orders",
    case
    when patindex("%IBM%", developer) > 0
    then "IBM Stole it from us"
    when patindex("%Torvalds%", developer) > 0
    then "IBM Stole it from us"
    when char_length(developer) > 0
    then "IBM Stole it from us"
    else
    "IBM Stole it from us"
    end as "whine"
    from money, linux_source
    where money.time_period > "Jan 1, 1900 00:00:01" or money.company = "IBM") derived_table_1, legal, revenue where patindex("%SCO%", operating_systems.name) = 0 OR patindex("%Microsoft%", operating_systems.name) = 0 AND revenue.incoming revenue.revenue_microsoft

    --
    No one has seen what you have seen, and until that happens, we're all going to think that you're nuts. - Jack O'Neil
  84. My favorite part by Marc2k · · Score: 1

    ..is when (partially relating to your statement) SCO realized that GPL restrictions held them to indemnify Linux users/vendors, and the internal comment from Chris Sontag had something to do with not pursuing lawsuits against Linux vendor because they "do not want to destroy Linux".

    --
    --- What
  85. The lawyer would have to argue against the GPL by TheConfusedOne · · Score: 2, Insightful

    There is very exacting language in the GPL that states if any section/code is tainted then the whole license is invalid.

    So, either the license is valid and thus all is GPL'd or SCO was illegally selling unlicensed work. (Either way they're in trouble.) You see, if they prevail on their case then they lost all rights to the rest of the code being distributed. Additionally, they continued to distribute the code (both clean and "tainted") in source code form with the GPL stamped on each file for two months beyond the time they made a formal legal challenge.

    Your example fails unless you add in the following: in order to sell Dr. Pepper, Pepsi agrees that all contained ingredients are fully licensed and immune to any claims that they (Pepsi) might have against Dr. Pepper. You see this is the real crux of the matter.

    By releasing the code, SCO obstensibly agreed to the terms of the GPL. It's kind of late to try and say "I didn't mean it" now.

    --
    --- I wish I could hear the soundtrack to my life. That way I'd know when to duck.
  86. Re:A year? hahahahaha by cybermage · · Score: 3, Interesting

    IBM is going make sure to drag this out and make it as expensive for SCO as possible. By the time any decisions will have been rendered by a judge, it will likely be irrelevant.

    Here, here.

    In all likelyhood, IBM will drag it out until SCO is dead. It's the only sensible response.

    If SCO wanted to save face, and perhaps live on, they'd do better to turn 180 degrees and contribute to Linux. They could actually make a market for an SCO Linux distro and port their proprietary applications to run on their Linux distro and keep licensing the apps the way they always have.

  87. When is this likely to be resolved? by billtom · · Score: 1

    Like most /. readers I've read a whole lot about this SCO thing. And like most /. readers I don't think that SCO has much chance of success and there probably won't be any long term impact to Linux.

    But, like most /. readers, I'm pretty tired of reading about it.

    So I ask you, when is this going to be resolved?

    Let's assume that SCO doesn't drop their claims and IBM doesn't buy them out. I don't know much about the US legal system when it comes to these kinds of cases, so I don't know how these types of cases usually last or what the procedures are.

    Is this going to be resolved in, say, August? Or is this going to be like the MS trial and we'll still be reading about it two years from now?!

  88. If the code doesn't fit you must acquit by Mouth+of+Sauron · · Score: 1

    Nevermind the IBM copyrights, they are the result of laboratory contamination.

    1. Re:If the code doesn't fit you must acquit by Oper+Sorcerer · · Score: 1

      If your code's been SCO'd You'll be in court a load!

      --

      karma: Marianas Trench (mostly blub blub)
  89. Catch-22 in SCO argument by cait56 · · Score: 5, Interesting

    For SCO to prevail it will have to establish that it owned the code, and that it was included in Linux distributions with malice and/or a callous disregard for the property rights of the code's true owners, but that SCO's "accidental" release of the same code under the GPL was not deliberate and shouldn't be held against it.

    It seems to me that SCO was in a far better position to recognize that the code being distributed as part of Caldera was in fact part of SCO's property than it was for other Linux distributors who did not have access to that confidential code.

    1. Re:Catch-22 in SCO argument by Anonymous Coward · · Score: 0

      For SCO to prevail it will have to establish that it owned the code, and that it was included in Linux distributions with malice and/or a callous disregard for the property rights of the code's true owners

      Where did you get this rubbish? Sure, if copyrights were knowingly infringed upon it can _raise_ punitive damages, but even if you have no clue, you are still liable.

    2. Re:Catch-22 in SCO argument by cait56 · · Score: 1

      If there is no malice, and no callous disregard for the property rights of others, then the only corrective action that could be demanded would be

      • removal of the infringing code: something the entire Linux community has already offered to do, but can't because the allegedly infringing lines have not been publicly identified.
      • perhaps pay royalties on the portion of Linux revenues that those lines of code represented: Let's see 80 lines over how many was that?

      Seriously, go look up some cases on inadvertent quoting without citation. You won't find any billion dollar judgements.

  90. Internal memo from SCO by harley_frog · · Score: 2, Funny
    From: Darl C. McBride, President and CEO
    To: All SCO Employees
    Re: Pills

    All employees are reminded to take the BLUE pill every morning, not the RED pill. The BLUE pill is for good; the RED pill is evil. Employees will be given a BLUE pill every morning when they report in for work. All RED pills are to be turned into security for proper disposal. Any employee who reports an unauthorized RED pill to security will be given an extra SCO stock share as a bonus.

    Signed,

    Darl C. McBride

    --
    It's all fun and games until someone loses the key to the handcuffs.
  91. I can't help but see this as biased by bulletproof+troll · · Score: 1

    Honestly, you think this is mathematically sound? It's got linux bias.

  92. Perhaps IBM is hosed, but. . . by kfg · · Score: 4, Insightful

    Please note that only code introduced by *IBM* into *UNIX first* is effected by SCO's claims.

    None of the code seems to be included in the kernel. Many distributions do not, and never *have,* included IBM's code.

    Thus Linux itself and distros that do not include such code will remain entirely unaffected even if 100% of SCO's claims are found by a judge to be true.

    At some point in the process SCO will have to take the possibly awkward step of *identifying* the specific bits of code they claim infringe.

    Why do you think they have refused to so so far?

    Because Linux could cleanse itself overnight and cease to infringe. i.e, Linux would be unaffected, and they know it.

    They're actually trying to *force* infringment by denying Linux distros the *right* to not infringe.

    This alone should indicate what slimey bastards they really are and lay doubt well at their doorstep.

    KFG

  93. *My* decision Matrix by MrWa · · Score: 2, Insightful
    Considering the impact this has already had on Linux, the fact that every possible scenario these guys could think of has no effect on Linux, my conclusion is that this matrix doesn't matter.

    As other posters have said, it is quite possible that a judge will in fact decide that Linux does infringe on SCO patents or copyrights or trade secrets or what-have-you. The mere fact that something doesn't make sense in no way means that the U.S. court system wouldn't decide that in that manner.

  94. They just need to be cleverer than Wall St by EmbeddedJanitor · · Score: 1
    This is a con-job to pump up their stock. You don't need to be factually correct to pull off a hype based effort.

    Look at Bush telling little lies about WMD. Nobody seems to care that he lied to get his way.

    Linux is important to SCO's business nonsense - SCO does not have a business.

    --
    Engineering is the art of compromise.
  95. double-jeopardy by Romeozulu · · Score: 1

    >> if SCO sues IBM and loses, I don't believe they have the right to sue someone else on the same terms.

    And you'd be wrong. This isn't a criminal trial. There is no such thing as "double-jeopardy" in civil trials.

    1. Re:double-jeopardy by adamshelley · · Score: 1

      That that is not at all what I meant. Let me explain:

      I lost some money for a unspecific reason.

      steps:

      1. blame someone
      2. sue someone
      3. lose
      4. get angry
      5. sue someone else
      6. lose
      7. get angry
      8. sue someone else
      9. ...

      The legal system, to my knowledge, doesn't allow this. foo.

  96. Sleek and sexy? by jabber01 · · Score: 1

    You've never had to admin WebSphere, I take it?

    Sure, v.5 might be sleek and sexy, but just as with Carrie-Anne Moss, I won't know for sure until I get my hands on it - though it certainly looks it in the promo.

    However, a few years ago they both looked sleek and sexy, and believe you me, WebSphere was none of those things. The WS of yore was less like Carrie-Anne Moss, and more like Roseanne Barr - bloated, offensive, unstable and just plain tedious after the novelty wore off in the first 10 minutes of interaction.

    --

    The REAL jabber has the user id: 13196
    What you do today will cost you a day of your life

  97. Copyright standoff doesn't protect redhat. by siskbc · · Score: 2, Interesting
    I cringe every time I see this point being made. The GPL isn't relevant, really. If the GPL doesn't "stand up in court", then no problem, standard copyright law takes over. SCO has no other right to distribute the Linux kernel under copyright law beyond those given by the copyright holder.

    You're right, but that's not quite where I'm going with it. I'm just saying that the GPL isn't a savior in this case, I don't believe, despite that people want it to be.

    What this means practically speaking is that if SCO violated the GPL, and the GPL is declared invalid, then SCO has instead violated standard copyright law. The statutory damages are $150,000 per incident. Everytime someone downloads the Linux kernel source from their website, ka-ching. Every sale that they've made, ka-ching. Pissing off Richard Stallman suddenly sounds like the better way off, eh?

    Well, they're betting the company anyway, so if they lose then Stallman can get his $150,000 after all the other creditors have picked over the carcass. In other words, heads they win, tails don't matter anyway.

    The bottom line is that SCO continues to distribute the Linux source code. As such, they're either agreeing to distribute it under the terms of the GNU GPL (which don't allow extra burdens to be placed on the code) or they are directly violating copyrights. They are far better off if they get off with a simple GPL violation

    Potentially, although I still don't think that this situation gets all linux users/distros out of the woods. In other words, SCO might be on the hook to Linus (who owns copyright on the kernel), but Red Hat et al might be on the hook for distributing SCO's code - and they don't have any copyrights to fight back with (well, none that matter here). And I don't know how that will shake out - I don't know for sure that they cancel. Basically we have a Mexican standoff, but Red Hat doesn't have a gun. The question might be how far Linus would go to protect them.

    Bottom line is you are completely correct, but I'm not sure that it matters, because standard copyright doesn't ultimately protect Linux users and redistributors - only the GPL would do that by effectively open-sourcing SCO's stuff.

    --

    -Looking for a job as a materials chemist or multivariat

    1. Re:Copyright standoff doesn't protect redhat. by Dastardly · · Score: 1

      Potentially, although I still don't think that this situation gets all linux users/distros out of the woods. In other words, SCO might be on the hook to Linus (who owns copyright on the kernel), but Red Hat et al might be on the hook for distributing SCO's code - and they don't have any copyrights to fight back with (well, none that matter here). And I don't know how that will shake out - I don't know for sure that they cancel. Basically we have a Mexican standoff, but Red Hat doesn't have a gun. The question might be how far Linus would go to protect them.

      But, the point is that either everyone is off the hook or no one is. SCO cannot pick and choose who is licensed to use their code and who isn't because they can only distribute Linux code with modifications under the GPL. So, either they distribute it to their customers under the GPL, and by extension everyone. Or, they distribute it to no one, and everyone is using Linux and their code without a license, and hence illegally.

      IANAL

      Dastardly

    2. Re:Copyright standoff doesn't protect redhat. by babyrat · · Score: 1

      In other words, SCO might be on the hook to Linus (who owns copyright on the kernel),

      AFAIK, Linus hold the trademark of linux. Each individual contributor of the code would hold the copyright to that code.

      So if the GPL is invalid and they are in violation of copyrights, it could be $150 000 to Linus and Richard, and Bill and Fred and Jane and Bob and everyone else who has contributed code to a linux distribution (both kernel code and user land code). Seems like that would be a LOT of money per violation considering the thousands of contributors.

    3. Re:Copyright standoff doesn't protect redhat. by Trailer+Trash · · Score: 1

      Well, they're betting the company anyway, so if they lose then Stallman can get his $150,000 after all the other creditors have picked over the carcass. In other words, heads they win, tails don't matter anyway.

      It's not $150K, it's $150K per violation. Each time somebody downloads it, it is a separate violation.

      You're right that copyright won't protect everybody else, but hopefully Linus will get his head out of the sand at some point and have his lawyer tell SCO they're going to get a bill that'll make their IBM lawsuit look like chump change if they don't give it up.

      $1B is fewer than 7000 downloads. I could probably pull the kernel source down that many times tonight with a script.

      Michael

    4. Re:Copyright standoff doesn't protect redhat. by civilizedINTENSITY · · Score: 1

      But you also said "First, he claims that Linux is fine becuase SCO indemnified users. No, only customers of SCO linux." I find this an interesting and new twist, though. They did release under the GPL and still they are saying, "SCO will continue to support our SCO Linux and OpenLinux customers and partners who have previously implemented those products and we will hold them harmless from any SCO intellectual property issues regarding Linux. SCO will continue to honor all contractual obligations with existing customers including product updates, service, and support."

      Now the GPL is what grants them the right to distribute, and they can't attach further restrictions to the GPL. It seems either we must all me safe, or else the restrictions on me force the distribution to their customers to have been illegal.

      "If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program."

      Seems like SCO wants to have it both ways, though. Any lawyers out there willing to comment?

    5. Re:Copyright standoff doesn't protect redhat. by Anonymous Coward · · Score: 0
      There are actually something like 400 seperate copyright holders to the linux kernel (a lot more contributors, but these are the major copyright holders).

      Let's say 300 of them sue for copyright infringment.
      Let's say they ask for $100,000 per infringment.
      Let's say that there has been 10,000 downloads/sold copies of the infringing code.

      That's a 300 billion dollar lawsuit! Even Microsoft would have trouble surviving that!

    6. Re:Copyright standoff doesn't protect redhat. by EzInKy · · Score: 1

      ...but Red Hat doesn't have a gun.

      Actually they do, and its a Rapid Phire Machine gun.

      --
      Time is what keeps everything from happening all at once.
    7. Re:Copyright standoff doesn't protect redhat. by siskbc · · Score: 1
      It's not $150K, it's $150K per violation. Each time somebody downloads it, it is a separate violation.

      OK, but if they lose the gambit they're bankrupted anyway, as that shar price will drop from $10 to about $0.20. So it doesn't really matter if a penalty is $6.37 or $200,000,000,000 - the money isn't going to be there to take, so it will be irrelevant.

      You're right that copyright won't protect everybody else, but hopefully Linus will get his head out of the sand at some point and have his lawyer tell SCO they're going to get a bill that'll make their IBM lawsuit look like chump change if they don't give it up.

      That would be the hope, certainly. And while one would hope he would, I definitely wouldn't want to bank my company's financial solvency on Linus's goodwill, however nice a guy he is.

      --

      -Looking for a job as a materials chemist or multivariat

  98. Re:A year? hahahahaha by Metasquares · · Score: 1

    They've already passed the point of no return. They've alientated and threatened their potential and actual customers to the point where huge civil litigation (or a buyout) is the only thing that can give them the capital they need to survive for more than a few months. For that matter, even the full $3 billion they're asking won't save them for very long if their income slows to a trickle. It would seem logical that SCO is looking for a buyout, but if they are, they're going about it very poorly.

  99. Re:Slashdot has sunk to a new low by Anonymous Coward · · Score: 0

    [ed. note: no it isn't]

  100. Ransom Love's Linuxworld 2000 Keynote Speech by NZheretic · · Score: 4, Interesting
    The SCO group, and both Old SCO and Caldera before it, directly acknowledged and assisted IBM with the scalablity of Linux

    In August 2000, just days after Caldera purchased the Old SCO server division, the then CEO of Caldera, Ransom Love, made a keynote speech at LinuxWorld 2000. A RealPlayer video stream of the event can be found at DrDobbs Journal's Technetcast

    In the question and answer session at the end of the keynote, Love was asked about the possible conflict over Monterey and Linux AI-64

    A mp3 capture of the following transcribed portion

    Q: What happens about Project Monterey, because that conflicts with the IA-64 Linux, 64-bit Linux?

    Love: OK. I don't -- if we do our job right in making Linux scale over like UnixWare to the degree that everybody, that we know we can... May I ask, some people have said, "Well, people have tried this in the past, but they haven't been that successful," may I suggest: we don't have any ulterior motives for not making it successful. Technologically has not been the reason why it hasn't done it before. There's always some other motive, right? And so to talk about Monterey, clearly we want to make sure we have the same level of Linux integration on Monterey that we would have in our Unixware product. Now, we don't control, I mean, we have a great relationship... it's a joint development relationship with IBM which we intend to preserve ... but they have similar interests and so this is really a very synergistic, uh, this transaction is great for all of the major partners as they have already wanted to embrace Linux moving forward.

    Now, let me address one other aspect of your question, which is that the Monterey Project is in conflict with the IA-64 Linux Project. I don't believe it's in conflict at all. Now, clearly, we have tremendous vested interest in the IA-64 Linux Project and with the acquisition of SCO, they've been doing a lot, so you combine those, and we've got one of the more comprehensive offerings, I believe, on the IA-64 Linux. So that's clearly an area that we're very committed to. But like Unixware, there's elements of the Monterey kernel that are more scalable, OK? Now, on the IA-64 platform, I don't know how long of window that is, but today, it's a little bit more robust and more scalable than the IA-64 Linux is today. Now, I'm not saying that over time that won't change.

    But, and let me address one other thing. Sorry, (laughs) you're getting all of it through one question. But clearly we are going to add components back to the Linux kernel on both IA-32 and IA-64 platforms. We'll work with Linus and everyone in order to make that available. That will take some time. And as I mentioned earlier, I don't know that over time you can have a single kernel -- in fact I know you can't -- that will scale, you know, the breadth of IT technology needs. So I think we're looking, in the Linux community, at having multiple kernels, so...

    Q: Multiple Linux kernels? Or multiple UNIX kernels?

    Love: Multiple Linux kernels as well, over time.

    Q: Thank you.

    Love: You bet.

    SCO has NO effective case against either IBM, HP or anyone else.

    1. Re:Ransom Love's Linuxworld 2000 Keynote Speech by Anonymous Coward · · Score: 0
      The quote is at 44 minutes 30 seconds into the video stream.

      But clearly we are going to add components back to the Linux kernel on both IA-32 and IA-64 platforms. We'll work with Linus and everyone in order to make that available.

      Interesting....

    2. Re:Ransom Love's Linuxworld 2000 Keynote Speech by Anonymous Coward · · Score: 0

      Someone should send this to IBM's lawyers at
      cravath.com

  101. Make up your minds! by PetWolverine · · Score: 1

    SCO claims to own ALL derived works of System V Unix: Unlikely
    (boldface emphasis added)

    We don't even know for certain whether or not they're claiming this? Come on, SCO, get your act together!

    --
    I found the meaning of life the other day, but I had write-only access.
  102. So what if this guy is wrong. by Crazy+Eight · · Score: 2, Interesting
    Does anyone doubt Linus and company could rewrite any offending code out of the kernel? One might suppose that by the time a decision is reached in court the code in question (if it exists) will have morphed beyond (infringable) recognition.

    Side note: Suppose that dark day comes and certain kernel versions are deemed illegal to use. imagine the bandwidth spectacle that would follow as Linux users worldwide upgrade to "vmlinuz-2.6.x-clean".

    1. Re:So what if this guy is wrong. by fanatic · · Score: 1

      as Linux users worldwide upgrade to "vmlinuz-2.6.x-clean".

      More like "vmlinuz-3.4.x-clean". I think.

      --
      "that's not encryption - it's a new perl script that I'm working on..." - from some Matrix parody
  103. Re:This is fucking retarded by Anonymous Coward · · Score: 0

    Look at the evidence that caused the US to go to war. By comparison, slashdot's angst filled 15 year olds are pretty rational and level headed.

  104. year 10,000 bug report by ratfynk · · Score: 0, Offtopic

    just try setting your system clock to March 6th 20032,
    Invalid time specification, which is about when the Sco case might finally come to court!

    --
    OH THE SHAME I fell off the wagon and use sigs again!
  105. Re:Preaching to the choir by Fakir · · Score: 1

    Is there any validity in Linux users and advocates creating a class action suit against SCO to either retract their charges or at least publicly retract those portions that claim damages from Linux? IBM can defend themselves, but the Linux community must stand for itself. It's easy to show in speculative terms how this lawsuit and the FUD surrounding it have hurt Linux adoption. It seems that Linux (and those that defend it) should be allowed to sue for damages.

    --
    ---------- Hot Rats!
  106. Re:More decisions like this... by dildofire · · Score: 1

    you don't really enjoy making money, do you?

  107. Isn't SCO pushing IBM to abandon AIX for Linux ? by file-exists-p · · Score: 1

    From what I understand, it seems very unlikely for SCO to hurt Linux. Even if "stolen" portions of code could be found, they could be removed and rewritten in days - okay, I am not a lawyer. This said, isn't all this mess just pushing IBM to abandon AIX and completely convert to Linux ?

  108. Re:More decisions like this... by yerricde · · Score: 2, Funny

    PHB tells you "Flip burgers." No hesitation.

    --
    Will I retire or break 10K?
  109. Go with it - news media pro Linux by kupci · · Score: 0
    This is anything but the sticking their heads in the sand bit, that seems like a bit of FUD to frighten Linux/AIX users who are hanging tight. What are they supposed to do? Give SCO license money? Switch to Sun or HP?

    What with all the FUD out there surrounding this case, a little pro-Linux stuff on the web - what the heck? One should take with a grain of salt pretty much anything written about this case, whether pro-SCO or not. Right now it's media jousting, nothing is settled in the courts, but it probably is a good idea for the Linux side to downplay this in the media in various ways, being careful not to give any ideas away to SCO.

    Forbes is rather M$ biased - you know -"Capitalist Tool" - don't give it too much credence. Used to be a good mag. They had a big article awhile back about how M$ was working so hard in China, all about security, sharing the source etc. Somehow they had avoided the whole reason *why* they had to work so hard, which was namely Linux. So either they knew it but didn't mention it, or totally missed the real reason. That's part of the danger for M$ right now, in that if they are so anti-Linux, they end up making managers take notice of Linux, such that they say "what's all this stuff about Linux Ballmer keeps yelling about? We need to get one of those!"

    That's all well and good except that the GPL, being a bit of a non-standard contract, has never been tested in court. What doesn't kill us makes us stronger.

  110. The GPL is relatively untested in court by gharveybob · · Score: 1

    Interesting analysis, but almost everything positive for Linux is predicated on the fact that the GPL is bulletproof and will hold up as valid in court. As I understand it, the GPL has never really been tested in a case like this. There's no guarantee that it provides the protection that folks seem to be hoping for. Look at the way the DMCA is being tested in courts now... to the point that it's validity is being called into question. I wonder if the basic premise of the GPL will hold up under that kind of scrutiny. Especially when direct financial support for the legal expenses are lacking.

    1. Re:The GPL is relatively untested in court by EzInKy · · Score: 1

      In the unlikely case that the GPL doesn't hold up, then under what license has SCO been distributing other peoples copyrighted code?

      --
      Time is what keeps everything from happening all at once.
  111. The SCO/Linux FAQ by heironymouscoward · · Score: 5, Insightful

    Question: SCO has declared itself a victim of breach of contract by IBM, specifically WRT AIX. Why, then, is it attacking Linux so specifically and directly?
    Answer: the goal of this exercise is to attack Linux, nothing else.

    Question: why is IBM saying nothing?
    Answer: they believe SCO might win, and are willing to sacrifice Linux if necessary.

    Question: why is Microsoft saying nothing?
    Answer: everyone knows they hate Linux, so no-one believes their propaganda any longer. They need a fresh mouthpiece. SCO is that mouthpiece.

    Question: why is Microsoft so intent on harming Linux?
    Answer: the goals of Linux and all OSS are nothing less than the total anhilation of Microsoft. War is not a nice thing. This is not a metaphor: we are talking about the lives of people you know.

    Question: if it is war, how do we win?
    Answer: this is a good question, and timely. You win wars by avoiding the battles you cannot win and by winning those you can.

    Question: what is the ultimate goal of Microsoft?
    Answer: the closure of the "development gap", in which the right to create code still lies in the hands of the individual. Ultimately, this power must be restricted to licensed programmers only. Nothing less than that makes sense. If your think this is exageration, look at other professions, then think about the public's perception of hackers, Linux kernel hackers, and virus writers.

    --
    Ceci n'est pas une signature
    1. Re:The SCO/Linux FAQ by j_w_d · · Score: 1

      Question: why is IBM saying nothing?
      Answer: they believe SCO might win, and are willing to sacrifice Linux if necessary.


      Because, unlike SCO, they listen to their lawyers, when told not to talk about the case.

      --
      ------ The only greater hazard to your liberty than n politicians is n+1 politicians.
  112. Here's the Comment Template for this Topic by jazman_777 · · Score: 3, Funny

    I am not a lawyer, but --insert long lawyerly opinion here justifying your deepest wishes for Linux--.

    --
    Slashdot: Failed Car Analogies. Amateur Lawyering. Anecdote Battles.
  113. Trade Secrets by feenberg · · Score: 2, Interesting

    I thought the basis of SCOs claim was that IBM
    had revealed trade secrets. In that case, SCO
    has a strong obligation to take care that the secrets are not revealed, as would IBM. But once the secrets become public knowledge, they are freely available to anyone - SCOs only recourse is against IBM for damages. The fact that SCO published the secrets themselves would be a difficult problem for them to overcome if they sought to prevent a third party from using the material. Perhaps they could appeal to copyright law to protect the former secrets, but they would have to reveal just what they thought had been copied, even under DMCA.

  114. Re:A year? hahahahaha by LinuxGeek · · Score: 3, Interesting

    Sounds more like a company that is grasping at straws on the side of the river bank as they are drowning. The 'license fee' that MS recently paid them amounts to throwing them a string that will only be helpful if someone else decides to tie a rope onto the string. My guess is that their only hope is for a judge to make IBM tie on that rope.

    --

    Kindness is the language which the deaf can hear and the blind can see. - Mark Twain
  115. interesting quote by walterbyrd · · Score: 4, Interesting

    "obviously Linux owes its heritage to UNIX, but not its code. We would not, nor will not, make such a claim."

    -- Darl McBride, CEO, The SCO Group. August 2002

    http://www.linuxjournal.com/article.php?sid=6293

    Check out the 8th paragraph.
    ----

    BTW: scox stock price has surged over the few sessions, and insiders are selling like mad. I think insiders just filed to sell 300K shares after the market closed.

  116. Bait and Switch by fiftyvolts · · Score: 2, Insightful

    You should have told your boss that there is another alternative that has all the benefits of using linux with none of this legal nonsense called BSD.

    Note that I am not saying BSD is better than linux, or that it is "not dead" or is "dead" or whatever. I'm just that perhaps pitching BSD might go over a little better with those who make decisions right now.

    1. Re:Bait and Switch by jfinke · · Score: 2, Insightful

      Yes, I agree that BSD whatever is a viable solution. However, Linux is a supported solution by many corporations. With Dell and Oracle presesnting RH Linux and 9i RAC as their preferred solution, there is much more support for Linux over BSD varients. Besides, Sontag and McBride have already said that BSDs may be another target. And the second that they say "may", companies wary of lawsuits (such as mine) are going to stay away.

  117. That summed it up nicely. Bite me, SCO! by Anonymous Coward · · Score: 0

    SCO can bite me :)

    http://sign-SCO-upfor-gayporn.biz

  118. Re:A year? hahahahaha by tupps · · Score: 3, Insightful

    By the sounds of it the people backing SCO now are purely intersted in leveraging SCO's intellectual property rights, not actually making a product. My guess is that once this case is over, whichever way it goes, SCO will disappear.

    --
    Go out and get sailing!
  119. For an actual relevent thesis of SCO vs. IBM... by RALE007 · · Score: 5, Informative
    see the OSI's release on the suit: OSI's IBM vs. SCO Position

    It is the most relevant and insightful material I have seen to date and I highly recommend reading it.

    --
    Beware blue cats moving at .99c
  120. Count the Lawyers by puckhead · · Score: 1

    Tech2 INAL so why should a PHB take his advice about SCO's lawsuit? Rather than make the case yourself, point out that lawyers for IBM, Sony, Hitachi, Phillips, Oracle, HP, Dell and many other large humorless firms remain unimpressed with SCO's case.

    --
    Watching Cowboy Bebop in my jammies, eating a bowl of Shreddies.
  121. Re:A year? hahahahaha by vsprintf · · Score: 1

    If SCO wanted to save face, and perhaps live on, they'd do better to turn 180 degrees and contribute to Linux. They could actually make a market for an SCO Linux distro . . .

    SCO is dead (not just dying like BSD :) to the Linux community. After the SCO's employees little anti-Linux demonstration, I have no remorse about watching that company swirl down the toilet like a departed gerbil (rest in peace). I don't believe there is anything they could do that would allow them to make a viable Linux distribution again. Their only hope for survival is to convince some addlepated judge that they have sole license to all operating systems that somewhat resemble UNIX(R)(C)(TM)(Pat. Pend.).

  122. Rather One Sided by nurb432 · · Score: 2, Interesting

    People need to realize that they really could have a case here.. its pointless to embark on this stunt if they didn't feel they had a chance.. just beacuse we have not seen the evidence doesnt mean its real.

    If they win, we are all screwed. Even if they dont, the damage being done to public opinion about the OSS movement will take years to repair.

    Remember too, its not what *WE* believe, or what we feel is right or wrong, its what a judge decides.. and he wont give a damn about public opinion ( if has a decent judge ), but instead what the facts and arguments from both sides add up too..

    --
    ---- Booth was a patriot ----
    1. Re:Rather One Sided by walterbyrd · · Score: 1

      >>its pointless to embark on this stunt if they didn't feel they had a chance.. just beacuse we have not seen the evidence doesnt mean its real

      Is that a joke? SCOX stock is up 600% since they started this lawsuit, and you better believe the insiders are selling like mad. SCOX said they noticed the offending shares last December. In January top execs gave themselve hundreds of thousands of options for $0.001 each.

      SCOX was selling for $0.60 a share this year, which is more than scox is worth, considering that scox has never had a profitable year, and scox is losing marketshare fast. Now scox is selling for about $12 a share.

      Far from pointless.

    2. Re:Rather One Sided by Sanction · · Score: 1

      You do realize that most leagal action is taken with the intent that it never ends up in court. You just try to make it so expensive to defend in the court case that your target settles out of court. SCO was trying to either get a hefty settlement, or get bought outright. Very seldom does an action like this happen because the attacker believes that their action has merit.

      --
      Well I'm the doctor and I say you're dead, so shut up and take it like a man!
    3. Re:Rather One Sided by achurch · · Score: 1

      People need to realize that they really could have a case here.. its pointless to embark on this stunt if they didn't feel they had a chance..

      Not necessarily. Put yourself in McBride's shoes:

      • If you do nothing, you're screwed.
      • If you sue and lose, you're screwed.
      • If you sue and win, you just might be able to pick up enough pieces to do something with.

      The "sensible" course of action should be obvious.

      I do agree, though, with your assessment about the damage to public opinion. Linux (and open source) folks really need to get moving to counter it.

  123. That's choir, idiot! by Anonymous Coward · · Score: 0

    Learn spellin' people!

  124. The GPL isn't automatic by roystgnr · · Score: 1

    No license can be: the only way any SCO-owned code is going under the GPL is if SCO employees with the authority to do so specifically release it under that license. It'll be up to a court to decide whether leaving it on their webserver for months with the license attached "counts".

    Now, granted, placing their code under the GPL may be the only way of keeping themselves in compiliance with the GPL for the code they sold and redistributed, and therefore the only way of protecting themselves from being sued for hundreds of thousands of counts of copyright infringement by each of hundreds of kernel developers, but for all we know they'll prefer the lawsuits.

  125. Re:Another example of... by Nailer · · Score: 1

    Actually, there has been - an analyst leaked that the Read Copy Update code in the Linux kernel source is identical to that of Unix and there's a fairly good chance this is actually the case. GIYF.

  126. Re:YOU NAILED IT! by Anonymous Coward · · Score: 0

    i just conquered your sister's fat ass, and BOY OH BOY do I feel great too! gee thanks gizzmo!

  127. Eddie Cochran by BigBadBri · · Score: 1
    I predict a big dose of Summertime Blues for the lovely Darl McBride, unless he tries Something Else.Perhaps he'd be better off trying to explain to IBM that there are Three Steps to Heaven, or to switch sides, a la Cut Across Shorty.

    Otherwise, Big Blue will steal his Pretty Girl, his Stockin's amd Shoes, and Darl will turn into a Skinny Jim and suffer a Nervous Breakdown.

    C'mon, Everybody!

    Damn - wrong Cochran(e).

    --
    oh brave new world, that has such people in it!
  128. David Boies also tried to prove Gore won FL by Anonymous Coward · · Score: 1, Insightful
    Anyone remember that dumbass "mathematician" who tried to prove that first-column (i.e., Presidential) canditates on the ballot were more prone to error by comparing them to candidates for other offices? This was part of the attempt to cast doubt as to the accuracy of the FL vote counts.

    The data they (Boies et al) used was from elections where the all the candidates they selected were in the same column - dumb fuck didn't even bother to look at the ballots used to try to "prove" voting error.

    Boies's attempt to lawyer Gore into the Presidency was a piss-poor piece of lawyering that destroyed any chance Gore ever had.

    Way to go SCO - get a guy who's most famous for his failures.

  129. Re:Chewbacca Is Gay by halo8 · · Score: 1

    -1 off topic... if you hadnt been an AC this would have been a +5 hillarious

    --
    The More Knowledge you have the Luckier you Get- J.R. Ewing
  130. RedHat would hit back...HARD. by dmaxwell · · Score: 1

    Potentially, although I still don't think that this situation gets all linux users/distros out of the woods. In other words, SCO might be on the hook to Linus (who owns copyright on the kernel), but Red Hat et al might be on the hook for distributing SCO's code - and they don't have any copyrights to fight back with (well, none that matter here).

    Bzzzzzzzzzt! Nice try! Thank you for calling!

    RedHat has made considerable contributions to the kernel over the years. They employ Alan Cox and a number of other kernel hackers to directly contribute to the Linux kernel. That means Red Hat does have "copyrights that matter". Can SCO potentially bash RedHat for their IP? Yes, but RedHat can kick them right back for violating their IP. Oh! And some of that has a patent on it. And after they get through playing rowshambay with RedHat, they can play it with the other Linux companies.

    All of this assumes that they have the stomach to get multiple ball kicks after IBM's legal team sodomizes them in court.

    1. Re:RedHat would hit back...HARD. by Jaysyn · · Score: 1

      Thanks guy. I just got this awful picture of a giant penguin in a suit borehogging Darl over a judges bench. Thanks a lot.

      Jaysyn

      --
      There is a war going on for your mind.
    2. Re:RedHat would hit back...HARD. by siskbc · · Score: 1
      Bzzzzzzzzzt! Nice try! Thank you for calling!

      Nobody likes a dick. Fuck off. It was an example, you knob, so substitute instead one of the many distros without any copyright in the kernel, and the point holds.

      --

      -Looking for a job as a materials chemist or multivariat

    3. Re:RedHat would hit back...HARD. by dmaxwell · · Score: 1

      Nobody likes a dick. Fuck off.

      Pot meet kettle.

      BTW, all of the commercial distros have IP in the kernel and even if they go after some floppy based distro hosted in someone's basement, the commercial distros can't permit the attack on their licensing regime. And they'll be in violation of RH's patent as soon as they try anything against a distro.

  131. Your boss by Anonymous Coward · · Score: 0

    ... will be the first against the wall when the revolution comes.

    He's overreacting.

  132. Deja vu by TeknoHog · · Score: 1

    I just saw "Linux is unaffected" many times in a row. Must be a glitch in the matrix.

    --
    Escher was the first MC and Giger invented the HR department.
  133. Watch where M$ is moving by kentsin · · Score: 0

    It is strange if M$ did not buy out SCO if the claim is true.

  134. Fishing for trolls by Anonymous Coward · · Score: 0

    Ah, not surprising. A document with no legal grounds that states Linux will be unaffected and Slashdot eats it up.

    Guess what, because Linus says something doesn't make it true and because you don't like SCO it doesn't make them wrong, legally. Grow up, then learn to face them on "grown up" grounds, with actual legal precedent.

  135. Thanks Michael... by Anonymous Coward · · Score: 0

    for putting any piece of factually-void garbage that bashes SCO on the front page and call it news. Great to see how objective you are. Even the NYTimes would laugh you out of their building if you put /. on your resume, and they have writers that make up stories.

  136. ...they're not stupid? by manvantaradude · · Score: 1

    McBride makes atrip to Japan.
    News media states SCO plans to make an announcment after the trip.
    The anouncement will be that everyone owes them money and they will sue you if you don't pay up.
    That sounds pretty stupid.

    I also noted that it was mentioned that some of the people they intended to visit were currently SCO customers. They will be told to do it their way or face a lawsuit.
    A non-agression pact with SCO is a bad idea.

  137. Just a thougt, please dont flaimbait by aws4y · · Score: 1

    here is the funny thing, IBM is playing it close to the vest, there just letting SCO talk. Here is an Idea, they could be using the lawsit to force their customers over to linux. In reality the legal conundrum that SCO is in right now only works against IBM and they have admitted that under the GPL they cannot sue linux companies. Also they do not own any of the IP that they are claiming was infringed.(Follow the patents.) If IBM is forced to abandon AIX then they could tell all there customers to go to Linux.

    Or even better this is the exchange in court.

    SCO: Here is the code we claim is infringing.

    (hands a stack of paper to the Judge)

    Judge: IBM what say you?

    IBM: Does any of the code contian a for loop?

    SCO: Yes.

    Judge: I fail to see the relevence?

    IBM: We own a patent for that particullar coding mechanism.

    (IBM hands Judge incredebly old patent that is still valid.)

    Judge: So you do, Case dismissed.

    -Just food for thought. I think that any damage done to linux will most likely be superficial as the OSDL will be unaffected and IBM will still have a vested intrest in linux.

    --
    Did Glenn Beck rape and kill a girl in 1990? gb1990.com
  138. Venue shopping issue critical! by Anonymous Coward · · Score: 0

    People, as someone who has worked in the court system, I can tell you, if Boies shops around for the right judge, he can get that judge (contrary to all reason) to declare that all of Linux is infringing, or some similar nonsense. Even if the judge KNOWS he's gonna be reversed, there are judges out there that are used to routinely getting reversed, and it would be enough to deal such a body blow to IBM(specifically) and Linux (generally) that may not be easily recovered from. While an appeal from a boneheaded decision drags on, companies and developers abandon Linux and Open Source in droves, and who's to guarantee that even IBM wouldn't throw in the towel and decide it's just not worth it. Sure, it could buy out SCO, but by then the damage will be done.... We need to keep in mind that in the court system worse things have happened...

  139. Maybe the constitution needs tweeking. by Bill,+Shooter+of+Bul · · Score: 1

    Its obvious how unbiased everyone here is. I guess we are lucky that patent law is so easy that we can pick it up in our spare time. I think the time has come to replace our courts with slashdot. Just post each court case let everyone post comments, and which ever post gets modded the highest wins. If its funny,rather than interesting then its a tie.

    --
    Well.. maybe. Or Maybe not. But Definitely not sort of.
  140. Author response by Anonymous Coward · · Score: 0
    I decided to ask the author about what his/her/their qualifications were to render this judgement in the matrix on the web site in question.

    Here is the response I received.

    "One does not need to be an IP lawyer to understand the issues involved."

    PLEASE save us from these EXPERTS ... ROFLMAO!!!

  141. Reminds me of a Donald Duck episode by Anonymous Coward · · Score: 0

    Where an old business parter (SCO) of Scrooge McDuck (Linux) claims all of Scrooge's riches are his because he invested originally in their business a single silver pocketwatch and never was repaid. The partner was presumed dead when his ship wrecked, and Scrooge became rich in time. Its later resolved by exposing the partner as some sort of crook, which fits SCO exactly (=

  142. Re:Rather One Sided - don't worry... by towatatalko · · Score: 1

    "People need to realize that they [SCO] really could have a case here...", that's the assumption their case is based on, but that's a subjective notion on their part, whatever that means for them, in court they will have to show what that really is and so far the prospect for that is far from certain, or even less than on sound grounds, shaky, some would say. Therefore, I'm not going to lose my sleep over their PR in news media, because those claims are just that: not worth the paper it is printed on.

    --

    IP was invented for the sake of lawsuits.
  143. Should use Aggressive Negotiations with SCO by spaceturtle · · Score: 1

    I think that the linux community should use more "Aggressive Negotiations" with SCO. Some progress has been made with the german libel lawsuit. Since most of the technology they claim is stolen is owned by others, from JFS to SysV (http://www.novell.com/news/press/archive/2003/05/ pr03033.html) it seems that some of their more personal accusations could be libelous. Since the IBM lawsuit does not involve copyright violations, forcing a lawsuit on this issue could force them to put or shut up much earlier. Also since the LVM code chosen was not IBM's, it is rather surprising that it is "copied" from SCO. Proving that it was SCO that pirated the code could be useful from a PR point of view. We should not merely sighing when SCO claims that Linux is like napster. We should note that the only reason that SCO got away with it for so long was because like napster that closed their source. The best case senario is not SCO going away after giving Linux a beating in the press, it is people associating piracy with the Bolshevik like secrecy of closed source software. "Windows XP? Isn't that like that SCO, and Napster? Sorry, Windows Paper Clip Server 2000 seems just right for the job but we just can't take the risk that they are hiding IP violations under their NDAs." "Linux needed millions of developers world wide to reach enterprise level. Windows 2050 could not have reached enterprise without the code that IBM stole from linux. Yer honour, IBM has clearly terminiated the GPL, and has lost the right to distribute GPL-AIX. Thus windows licenses are now invalid, and all customers must switch to linux. The customers knew they were using closed source that had not be subject to peer review for IP violations, so they not innocent parties." Mwahahaha! Attack is the best defense! Mwahahaha!

  144. Re:Another example of... by Anonymous Coward · · Score: 0

    /s/Unix/Aix

    RCU is IBM's code.

  145. Check. by Crazy+Eight · · Score: 1

    Yer right.

  146. Re:A question about Linux by EzInKy · · Score: 1

    The same way you would compile MS's kernel if you could manage to find a working version of Windows, of course.

    --
    Time is what keeps everything from happening all at once.
  147. IANAL But ...... by Quietlife2k · · Score: 1

    SCO claims not to have known that their code was in linux while they were distributing it... (Lets ignore that they continued to distribute it after they knew) Whatever happened to "Ignorance is no defence in the eyes of the the law" ? If they win does it mean that I can kill someone, then claim in a court of law that I did not know that it was illegal and therefore get away with it ?? I think not !! Furthermore what about "Caveat Emptor" (let the buyer beware) in this instance SCO "bought into" linux (as a marketable product) and therefore it was their resposibility to perform "due dilligence" to protect themselves. It seems that they (either knowingly or otherwise) ignored one of the basic business rules - "cover your own ass first". There has been enough "fud" circulated about the "viral" nature of the GPL that they cannot have been completely unaware of the ramifications of releasing their own linux distrobution. Just my tuppence worth.

  148. Finally, their evil plot becomes clear by Lonesome+Squash · · Score: 1
    Once they've prevented IBM from distributing AIX, IBM will have to distribute Linux on all their systems. IBM will suck up all available Linux, leaving the rest of us with nowhere to turn but SCO's Dark Lord, Microsoft.

    Incidentally, was anyone else here geeky enough that when they first started seeing those Armani Exchange ("A|X") tee shirts they started wondering why all these attractive people were into AIX?

    --
    Behold the riant ape! Beware, his crooked thumbs!
  149. "quire" is a variant of "choir" (m-w.com) by VXneko · · Score: 1

    "preaching to the quire" and "preaching to the choir" are both correct. please, do /. a favor and ROFL somewhere else. Note to all wanna-be spelling nazis: spelling proficiency is a rechoirment. OR acchoir a dictionary AND learn how to use it.

  150. Because that may change. by Ungrounded+Lightning · · Score: 1

    Why host the page on your own site when google already HAS THE CACHE

    Because, if the page changes, the google cache will also eventually change.

    Don't you think we want to see the version this article is talking about, rather than a later spin-controlled version?

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way