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

Mirror for the slashdot effect

[zubernerd]

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

Re:Mirror for the slashdot effect

[Saint Aardvark]

And another, 'cos what the hell:

http://saintaardvarkthecarpeted.com/linux_vs_sco_m atrix.html [saintaardv...rpeted.com]

Re: Mirror for the slashdot effect

[Black Parrot]

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

Pointless effort

[Anonymous Coward]

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

Re:Pointless effort

[zubernerd]

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

Re:Mirror for the slashdot effect

[dschuetz]

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.

Re:Mirror for the slashdot effect

[Anonymous Coward]

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

A year? hahahahaha

[sterno]

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.

Re:A year? hahahahaha

[HiThere]

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 [e-mail]
He invites comments. (No particular note on what kind of comment was desired.)
Another mailing address is [e-mail], 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.

Re:A year? hahahahaha

[LinuxGeek]

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.

Re:A year? hahahahaha

[tupps]

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.

That would be the worst thing for Linux

[GoofyBoy]

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.

Re:That would be the worst thing for Linux

[jfinke]

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.

Bait and Switch

[fiftyvolts]

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.

Re:Bait and Switch

[jfinke]

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.

Re:That would be the worst thing for Linux

[_Sprocket_]

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.

Re:That would be the worst thing for Linux

[jfinke]

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 aft

Re:That would be the worst thing for Linux

[_Sprocket_]

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 bi

Re:That would be the worst thing for Linux

[EvilTwinSkippy]

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?

Re:That would be the worst thing for Linux

[fanatic]

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 [itworld.com]? 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.

Re:A year? hahahahaha

[cybermage]

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.

SCO vs. IBM vs. [INSERT YOUR NAME HERE]

[oaf357]

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.

Re:Mirror for the slashdot effect

[alienw]

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.

Re:Mirror for the slashdot effect

[Archie Steel]

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.

Re:Mirror for the slashdot effect

[Znork]

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.

Re:Mirror for the slashdot effect

[AstroDrabb]

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.

Catch-22 in SCO argument

[cait56]

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.

Perhaps IBM is hosed, but. . .

[kfg]

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

Re:Mirror for the slashdot effect

[Spazmania]

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

Re:Mirror for the slashdot effect

[Anthony Boyd]

Geeze. Even the mirrors are getting slashdotted!

Re:Mirror for the slashdot effect

[dark-br]

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

SCO Matrix...

[TWX]

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

Re:SCO Matrix...

[hendridm]

> 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 ;)

Re:SCO Matrix...

[Llywelyn]

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

Re:SCO Matrix...

[canajin56]

Keanu Reeves as Tux

You're best leaving Tux as a plush toy. Better actor AND more marketable

Re:SCO Matrix...

[Xformer]

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.

Article is slashdotted..

[Gortbusters.org]

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.

Re:Article is slashdotted..

[crazyphilman]

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!

Slashdotted

[dimmu]

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

FUD factor not included

[wilfie]

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

The Google Cache

[_Sambo]

And here it is

http://216.239.37.104/search?q=cache:FOhL0ah_AIQJ: www.cyber.com.au/users/conz/linux_vs_sco_matrix.ht ml+Linux+vs.+SCO:+The+Decision+Matrix&hl=en&ie=UTF -8 [216.239.37.104] Slashdot. The fastest crasher on the web.

Matrix

[darth_MALL]

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

Anothr example of...

[cruppel]

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

Not only that...

[Atario]

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

Re:Anothr example of...

[MeanMF]

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.

Re:Anothr example of...

[no reason to be here]

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.

Sticking their heads in the sand

[siskbc]

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.

Re:Sticking their heads in the sand

[Trailer Trash]

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.

Copyright standoff doesn't protect redhat.

[siskbc]

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 S

Agreed

[michaelggreer]

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

Re:Anothr example of...

[smoondog]

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 accusati

Hmmm...

[Tiresias_Mons]

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

Re:Hmmm...

[GreatOgre]

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

Matrix?

[Raster Burn]

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.

Jesus...

[tevenson]

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

It becomes easy once you realize...

[reimero]

There is no SCO.

One trick pony table.

[Godeke]

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

Re:One trick pony table.

[Error27]

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.

Re:One trick pony table.

[Godeke]

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 co

Re:One trick pony table.

[GoofyBoy]

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.

Re:One trick pony table.

[jedidiah]

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.

Re:One trick pony table.

[GoofyBoy]

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

Re:One trick pony table.

[Morel]

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 [gnu.org], but others differ [siliconvalley.com].

Cheers,

Morel

Re:One trick pony table.

[tlk nnr]

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 contai

You just need to look at the last line...

[greppling]

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

Re:You just need to look at the last line...

[JordoCrouse]

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

Re:You just need to look at the last line...

[KillerHamster]

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.

Re:You just need to look at the last line...

[GoofyBoy]

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.

Look, they're not stupid.

[s20451]

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.

Re:Look, they're not stupid.

[molarmass192]

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.

Re:Look, they're not stupid.

[PickaBooga]

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.

Re:Look, they're not stupid.

[iabervon]

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.

If you take the Red Pill...

[EvilTwinSkippy]

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.

Handy

[evilpenguin]

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.

Preaching to the quire

[b.foster]

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 [microsoft.com] 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.

Re:Preaching to the quire

[Anonymous Coward]

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

Re:Preaching to the quire

[pongo000]

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 [chinapage.com])

Re:Preaching to the quire

[RickHunter]

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.

Chance of SCO success?

[DeadSea]

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

Re:Chance of SCO success?

[jo42]

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

Comment removed

[account_deleted]

Comment removed based on user account deletion

Re:Lawsuit is irrelevant

[Darth]

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.

"Linux is unaffected"

[hendridm]

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

The lawyer would have to argue against the GPL

[TheConfusedOne]

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

Re:"Linux is unaffected"

[jedidiah]

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.

Lame analysis jumps to conclusions.

[Distan]

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.

Reminds me of Office Space

[pavon]

Who needs a decision matrix when you can have a Jump [slashdot.org] to [slashdot.org] Conclusions [slashdot.org] Board [slashdot.org]?

They forgot a scenario

[toastyman]

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.

Linux is unaffected?

[John Harrison]

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.

Re:Linux is unaffected?

[spitzak]

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

Ransom Love's Linuxworld 2000 Keynote Speech

[NZheretic]

The SCO group, and both Old SCO and Caldera before it, directly acknowledged and assisted IBM with the scalablity of Linux [weblogs.com]

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 [ddj.com]

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 [iwethey.org]

A mp3 capture [iwethey.org] 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.

The SCO/Linux FAQ

[heironymouscoward]

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.

Here's the Comment Template for this Topic

[jazman_777]

I am not a lawyer, but --insert long lawyerly opinion here justifying your deepest wishes for Linux--.

interesting quote

[walterbyrd]

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

For an actual relevent thesis of SCO vs. IBM...

[RALE007]

see the OSI's release on the suit: OSI's IBM vs. SCO Position [opensource.org]

It is the most relevant and insightful material I have seen to date and I highly recommend reading it.

Rather One Sided

[nurb432]

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

RTFA? they picked Redhat

[JimmytheGeek]

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.

Re:Matrix schmatrix!

[mcc]

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

Re:Appropriate

[adilsonoliveira]

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

Re:Appropriate

[ElectricPoppy]

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