SCO NDA Online at LinuxJournal 441
shadowbearer writes "The full text of the SCO NDA is available here at LinuxJournal. IANAL, but my reading of it makes me understand all the industry "No way!" style comments. Here's a snippet:
"Dan Ravicher, an attorney who specializes in free software and open-source issues at the firm of Patterson, Belknap, Webb & Tyler, said in an interview there are three key problems with the NDA. First, Ravicher said, "SCO can pick and choose among all its evidence" to show only the parts that back up the company's claims. "They're agreeing to let you see the half of the picture that they want you to see", he added.""
"Dan Ravicher, an attorney who specializes in free software and open-source issues at the firm of Patterson, Belknap, Webb & Tyler, said in an interview there are three key problems with the NDA. First, Ravicher said, "SCO can pick and choose among all its evidence" to show only the parts that back up the company's claims. "They're agreeing to let you see the half of the picture that they want you to see", he added.""
Section 8 (Score:5, Funny)
Under Section 8 (Injunctive Relief), if I sign the NDA and then even threaten to reveal any of what SCO showed me:
SCO shall be entitled ... to preliminary and permanent
injunctive relief
Does this mean they can send me down for the dirt nap?
Re:Section 8 (Score:4, Interesting)
Re:Section 8 (Score:3, Interesting)
Re:Section 8 (Score:5, Insightful)
their ENTIRE sourcecode will be revealed in court to professional witnesses under court order, not under some fantasy bullcrap SCO's lawyers dream up.
SCO is doomed, their NDA is proof that they have nothing and the whole thing is nothing more than a scam that the CEO and other company officials are trying to pull.. I put these guys lower than the scumbags at Enron.
I'd tell everyone I know to avoid SCO, but nobody has used their products cince 1990.
the response I get is S C Who? that company that went to hell in the early 90's that had the crappiest Unix on the market?
SCO has been a running joke in the Unix market for decades... their NDA is just further proof.
Re:Section 8 (Score:5, Insightful)
I feel sorry for the excellent engineers and businessmen who made that happen (more than twenty years ago), their ancient and respectable company name has been turned into shit by a bunch of dot-com bubble idiots with a hangover and a patent lawyer.
This "SCO" is really Caldera. (Score:3, Informative)
I'm sorry--- you say that US' tort system changed? (Score:5, Insightful)
Quite seriously, a major reason for America's economic troubles, according to the Harvard Global Competitiveness Report, [harvard.edu] is a failure of the court systems, especially in contract law.
Although the whole report is for sale, you can click through to some pdfs, and read them. Especially interesting is the Executive summary [harvard.edu], in which [p. 19] they say that they are increasing the weighting of technological innovation, [p. 20] note that the US has fallen to #2 and Finland has taken #1.
Yet for the case of the United States [p.37] [harvard.edu], they note that the bubble has burst, and they say that technology is *overrated*. They also note that the major problems with the US are the undermined court system, now ranked around #14.
What that means is that they US hasn't just fallen to #2. In reality, the US has already fallen a good deal farther. And when you consider that superpowers *do* have more power, and therefore fall under the category of "more competitive" all other things being equal, that means that the US is really hurting, and is probably going to hurt more. Fallen, fallen, is Babylon and all that.
Now, flip over to the Cato Institute [cato.org], and you can find documents [cato.org] [or this] [cato.org] where they point out that the fall Argentina's peso was engineered, and that this represented a major additional break from the rule of law. But what also hurt was that their court systems were completely corrupted, and their society had separated into two societies: the taxed and the government folks.
Well, hate to break the news, but it's looking a lot like what Argentina had, America is getting ready to eat themselves. Not that it will be exactly alike. I fully expect a blackmarket boom in Argentina, followed by [1% chance] them becoming the top economic power in the world if they are good to each other, or [99% chance] them turning military and conquering most of South and Central America, and sending a pressure hammer of refugees into North America. The US, on the other hand, I expect to slide into corruption, and be overwhelmed by said pressure hammer.
But back to the topic at hand, I don't think we can necessarily expect expert witnesses, truth, and Justice to prevail, in light of the American way.
So if you're into Linux, download all the source code you can right now, and put it on CDs/DVDs, and keep it. You may find that it is quite valuable for internal use, and public use after you're sure that it's clean. Don't let Linux depend on America, because America has different ideas right now.
Re:Section 8 (Score:5, Funny)
Maybe, maybe not, but breaking it will get you added to SCO's we-will-sue list. Next press release it'll be IBM, 1500 Linux using companies, Novell and now Slashdot's Anonymous Coward.
Beware of unilateral contracts (Score:5, Informative)
This contract was created by only one side of the deal. So it's worded precisely the way SCO wants it for their maximum advantage. Usually in a dispute courts will favour the party which didn't create the unilateral contract, but it looks like they've covered off that angle by choosing Utah.
Bilateral contracts, where the parties negotiate and both have input into the final wording signed, are much safer as a rule.
This is a one-sided contract by a known litigous company.
The person signing gives up all kinds of rights, is straitjacketed legally, and doesn't even make any money on this.
All the risk with no reward.
What could the counterparty to SCO possibly gain by agreeing to this?
I usually try to be ambivalent, but can't seem to find anything redeeming here.
Re:Beware of unilateral contracts (Score:5, Funny)
Re:Beware of unilateral contracts (Score:4, Insightful)
Re:Beware of unilateral contracts (Score:4, Interesting)
In effect, that means that the NDA is probably not worth the paper it is printed on, assuming that we're all correct that the code in qustion was just stuff AT&T stole from Berkeley back in the 80s.... That having been said, I wouldn't want to test that theory by signing the NDA and then publishing their source code.... :-)
Re:Beware of unilateral contracts (Score:3, Funny)
</offtopic>
Re:Beware of unilateral contracts (Score:5, Interesting)
Money. The counterparty would presumable be being employed as an Expert Witness in the lawsuit. Fees for such witnesses are normally very lucrative. >$1000/day plus expenses for the research phase (reading the code) and more for attendance in court are the figures I have heard.
Bullshit. (Score:3, Interesting)
That the NDA would be unacceptable was so predictable [slashdot.org] it's not even funny. Only M$ and SCO shills would sign that thing and SCO is going to say stupid things about free software advocates who refuse to put themselves at the mercy of
Re:Beware of unilateral contracts (Score:5, Informative)
More dirty SCO tricks (Score:5, Interesting)
NDA does not exclude information that the recipient obtained in
ways other than from SCO" is true, then signing the NDA could
prevent you from disclosing any information about SCO code even
if the court rules that SCO's distribution of the code (with
Linux) made it public.
So you could in theory be binding yourself to confidentiality
with regards to SCO's code even if (when?) the ruling goes
against SCO!!
As SCO has said, binding legal agreements are far more
compelling in a court of law than copyrights. I wouldn't touch
that agreement with a ten foot pole.
Unfortunately, as we knew it would be all along, this is just
another ploy by SCO. They won't give you full access to the
code, you can't talk about the specifics, they can bind you from
disclosing already public information, and to top it all off,
they can make you come to Utah to defend yourself in court.
Re:More dirty SCO tricks (Score:5, Funny)
Re:More dirty SCO tricks (Score:5, Funny)
Re:More dirty SCO tricks (Score:5, Insightful)
I have seen hundreds of NDAs in my career, and practically every one of them that I have seen has an exception allowing you to make disclosures if ordered to do so by a court. This is very important; if you don't follow a court order, you could go to jail.
And if this happened and you did follow the order, then you'd screwed under this agreement. Talk about putting yourself between a rock and a hard place
Re:More dirty SCO tricks (Score:4, Informative)
Re:More dirty SCO tricks (Score:3, Informative)
if your legally obliged to do something for the court, and their contract keeps you from doing it- hence the contract forces you to break the law- doesn't that make the contract itself null and void?
I seem to remember somewhere that contracts can't be enforced if it requires a partymember to break the law.
Ha! (Score:4, Insightful)
In other words, we can show you only what makes us look as if we have a case
Re:Ha! (Score:2)
If their case is "there is code we own that is copied in linux", then wouldn't they have to show you the code that was copied? I mean, either they show it or they don't. If they show it, they make their point. If they don't, they don't make their point. How can you show a piece of code that makes their point while excluding other code which would negate their point?
Re:Ha! (Score:3, Insightful)
Re:Ha! (Score:4, Insightful)
I don't believe that's the case here at all but that's not the fault of this NDA. It would be valuable and usable to someome.
Re:Ha! (Score:4, Informative)
But then, so's the entire lawsuit...
Re:Ha! (Score:3, Interesting)
The NDA allows the recipient to release a public statement regarding the materials shown - so if they screw you, you can legally release a statement that says so. Any further restraints would be infringing free speech rights and likely would be stric
Re:Ha! (Score:3, Insightful)
And let's face it, if they have nothing, go to court, and then show nothing, they're going to lose anyway, so it's not exactly a big deal...
Re:Ha! (Score:2, Insightful)
Small blocks of code simply aren't very interesting; lots of programmers use similar variable naming conventions and coding styles; and many people "reinvent the wheel" when writing small utility functions (atoi(), strs
Re:Ha! (Score:5, Informative)
They probably won't have to go to AT&T or Novell for historical data, except as secondary verification. SCO has the source code repository (in ClearCase and in other formats) going back to 1984 and, for some things, earlier.
IANAL, but if I were working for SCO and were asked to prove the charges, showing the matching code would only be the first step. The second step would be to show where the code was first introduced in the USL-originated repository. The third step would be to be prepare to show that the timelines in the repository were not altered (think "cleartool setevent"; this is where AT&T might come into the picture). The fourth step would be to show that the code was the IP of SCO or its ancestors from the day it was checked in (i.e., it's not itself stolen GNU code or something). The fifth step would be to show (possibly through subpoena of the AIX source repository) that the code in question was introduced into AIX as a result of a code drop from SCO or its ancestors. The sixth step would be to show (through examination of the Linux [etc.] repositories) that the code in question was introduced into Linux (etc.) as a result of a code drop from IBM subsequent to its being obtained from SCO.
That's the easy (if time consuming) part, establishing the paper trail.
The hard part is then proving that the transfer of the IP into the Linux source base was done knowingly (or whatever else would be actionable under the SCO/IBM contract), and that the Linux coders couldn't possibly have thought it up on their own (e.g., it can't be some algorithm every freshman CompSci student implements as a class project.)
I really can't see SCO's "they can't possibly have had the knowledge or resources to build and test this" claim holding up. They're going to have to present much more convincing positive evidence than that.
Good bloody luck.
NDA for the NDA? (Score:5, Funny)
Re:NDA for the NDA? (Score:2)
-Rusty
Re:NDA for the NDA? (Score:3, Insightful)
Now, they could have an NDA for the NDA, so they will only show the main NDA after signing the smaller one. However, the first NDA you are shown could be disclosed. Then again, it probably wouldn't be nearly as juicy for amunition - it would just say something like you will never disclose anything
Re:NDA for the NDA? (Score:5, Insightful)
Be nice you guys.. (Score:5, Funny)
SCO can only show you half the evidence now as they haven't made up the other half yet. Just be patient and play nice, boys.
Re:Be nice you guys.. (Score:5, Interesting)
NDA to sign the NDA (Score:2, Interesting)
I'm not kidding.
P.S. SCO's stock is going up like crazy today. Big volume too.
Picture? (Score:4, Funny)
Well, if a picture is worth a thousand words, and half a picture is prolly worth about 500...
I say we use those 500 words and tell sco the many ways to "get bent".
Re:Picture? (Score:2)
Re:Picture? (Score:3, Funny)
I made a copy of the NDA (Score:4, Funny)
Re:I made a copy of the NDA (Score:3, Funny)
Well I sign all my mail "Rob Malda", especially my email - it seems to keep my own email address free of spam
I just saw the code... (Score:5, Funny)
Re:I just saw the code... (Score:2)
Re:I just saw the code... (Score:2)
Re:I just saw the code... (Score:2)
That shouldn't be surprising, since C++-style comments are C99 compliant [gnu.org]. Thus, any compiler implementing the C99 standard should support them.
Re:I just saw the code... (Score:4, Informative)
The other thing to remember is that most SCO systems aren't used for anything except running one vertical app. Ours runs Command Dental System, a cobol suite of programs that are multi-user over serial lines to wyse 60 terminals. It was ported over from xenix, and what was funny is SCO changed from curses to ncurses when they change from 16 bit xenix to 32 bit openserver and this cause bizzar characters to appear in the screen boarders and support(Command Dental) couldn't figure out that the only thing they had to do to correct it was to change the systems default font!(I didn't dare change it myself because with a support contract, if you change anything, everything is forevermore your fault.)
An other area that SCO had good penatratrion in is resturants, multiple waitress stations intputing orders with touch screens and swipe cards.
Phew! (Score:5, Funny)
This should fix me till Monday!
courtesy of nasdaq... (Score:4, Informative)
SCOX $ 8.48 1.88 +28.48%
do they know something we don't ?
Re:courtesy of nasdaq... (Score:5, Interesting)
No, it's just the gambling instinct.
Although we all know SCO doesn't have a case, most investors aren't that savvy. Plus, even without a case, you always have a chance in the US - you can pull a crazy judge after all. So the investors are figuring, maybe they win, maybe IBM settles or buys them out... if either of those things happened SCO stock could suddenly be worth a lot more. There's always a good amount of money in the stock market looking for the high risk gamble-moves that could bring a good payoff. Most of those investors, of course, are sensible enough to keep the bulk of their holdings in safe stuff, but they still budget a certain percentage for risky buys... anyway I'd figure those are the buyers. The sellers are probably the SCO executives and their pals, who presumably have a more realistic understanding of their chances.
Re:courtesy of nasdaq... (Score:3, Interesting)
I'm just curious how many slashdotters have shorted SCO's stock. I've been told it's a bad idea for stock market newbies to jump right in with shorting, but this seems like a good bet...
Shorting (Score:4, Informative)
Bottom Line: buying options contracts has a predetermined downside: the cost of the contract. On the good side there is no limit to the upside; the more the price of a stck moves in the direction that you guessed the more money that you make. On the other side of the story is that of selling contracts. There is a limited upside: the cost of the contract. There is an unlimited downside though; the more the price of a stock moves against you the more you loose. There is not really any way out of selling a contract except the expiration date. That said you can buy an options contract that is in the opposite direction from the one that you previously sold and stop the bloodletting there by essentially making money on one instrument while loosing it on another at the same time. The general rule of thumb, the reason that there are about as many people selling contracts, either puts or calls, as there are people that want to buy them is that 90% of the contracts will expire worthless.
There is a major differences in options contracts in Europe and the US: when they can be exercised. In the US options can be bought and sold at any time during the contract. In Europe contracts can only be sold on the date that they mature. Either way they are priced by a method known as The Blask Scholes [optionanimation.com] method. These two economists won a Noble Prize for developing these equations and the markets have never been the same since. The price that they come up with is based on many different things: the current price, the volume of stock, the amount of stock in play, and how fast the price is moving, among others.
Back to selling stock short. The borrowing of stock is arranged by brokerage houses so you need not worry about that detail but if the price goes up the brokerage house can and will demand that you have enough cash in your account to cover the margin between the current price and that which you bought it at. If you don't have enough margin the brokerage house will do whatever it thinks is necessary to cover their ass as anything that you cannot cover is their loss. That often includes liquidating everything that you own. Just make sure that you have the required margin!!!
Re:courtesy of nasdaq... (Score:5, Funny)
On second thought the more likely answer is that people who buy stocks are idiots
Re:courtesy of nasdaq... (Score:2)
As soon as the early investors figure the stock has moved enough, they'll bail out again.
Besides, what else are they to do with all the cash they pulled out of Big Blue after the SEC investigation story?
Re:courtesy of nasdaq... (Score:5, Insightful)
SCO management knows that if they can keep their story in the news then people might start to believe they actually have a case.
The fact of the matter is that SCO isn't aiming their press release at members of the Linux community (or even members of the larger computing community), they are aiming these press releases at the large population of rubes that might be interested in gambling on an "insider deal." SCO's allegations are ridiculous to anyone with any knowledge of the situation, and their tactics are crude and hamhanded to any with an inkling of knowledge about the case. The mere fact that they keep issuing press releases should trigger alarm bells. Everything SCO management says is evidence, if they were trying to win they would listen to their legal counsel and do their talking in court.
In short, SCO isn't trying to win a court case; they are trying to hype their stock.
To an outsider their case looks like a bunch of poor underdogs who have are fighting an IBM Goliath. SCO's target audience doesn't have a clue about source code or NDAs, and to them the offer to prove their case almost certainly looks genuine. These people don't know about the GPL or the UC Berkeley AT&T court case. They don't even know that SCO isn't Santa Cruz Operations (the former UNIX company), but that SCO is really just Caldera (the former Linux company). They simply see that a small company claims to have rights to some code, and some journalists (and Microsoft) keep adding credence to their story.
This is a pump and dump scheme, nothing more, nothing less. Think of it as a variation on the Dot Com Boomers that hyped their stock up to the moon despite the fact that they knew that they had no chance of making a profit. Everyone makes fun of the dot com management teams, but they weren't stupid. They weren't selling pet food, or medical advice, their stock price was the real product they were hawking. The guys that founded those companies generally made a big fat pile of money at the subsequent investors expense. And it was all perfectly legal.
SCO management is in a similar position. They aren't going to win their case, but that doesn't matter, because right now their stock is what they are really selling. The difference is that the "Big Lie" in this case isn't that online commerce is going to change the world. The story this time is that scrappy SCO from Lindon, Utah has got IBM by the short hairs. It's pure @#$!!, but it plays well on TV.
As long as the SCO insiders jump through SEC hoops when they sell (and they have plenty of time to sell), and as long as they don't laugh out loud while pretending they have a case, it's all perfectly legal.
Caveat Emptor.
Re:courtesy of nasdaq... (Score:3, Insightful)
I wouldn't sign anything SCO management gave me. The only good news is that eventually this case will either go to trial or SCO will go out of business.
Here's to hoping that the SCO management gets so greedy that they make a mistake and the SEC nails them to a tree.
Re:courtesy of nasdaq... (Score:3, Funny)
Red Flag (Score:5, Insightful)
I didn't even read beyond the first section because that quote says it all right there.
Here's the lines in question, NDA be damned... (Score:2, Troll)
module.c, line 54 [linux.no]
module.c lines 153-155 [linux.no]
and most potentially damning, signal.c, line 430 [linux.no]
Comment removed (Score:5, Insightful)
Re:Simple Really (Score:2)
If I were to pay them (or anyone else for that matter) royalties, wouldn't I get to see what I'm paying for?
zRe:Simple Really (Score:5, Insightful)
Which the basis of another lawsuit itself. In effect, SCO would also get to charge royalties for the work the community did. Every other contributer to kernel (and whatever other software they want to extort money from) would probably have good reason to sue SCO. They would be committing a theft far larger than the one they allege was committed against them. If they don't step carefully, they're already staring the barrels of multiple countersuits for GPL violation. Attempted royalty collection would just throw more fuel on the fire.
Re:Simple Really (Score:5, Funny)
Thank you for your letter requesting royalties. I must advise you that I have modified my copy of Linux and it now longer contains any of the code you allege is your property.
I would be happy to show you my revised code so you can verify my claim, if you wouldn't mind filling out this NDA (attached). Oh, and don't forget to let me know which lines you want to see. I have my lines of source code sorted in alphabetical order for your ease of reference.
Not so simple. Really. (Score:4, Interesting)
All right. Let's say SCO does have a legit claim and does want to collect royalties. Even so, at one point or another, they'll have to reveal the "code in question" to, at the very least, the parties involved in the lawsuit, if not to the general public as well. If they never reveal said code, then how the hell can they prove that it was copied? That would be akin to accusing someone of stealing without even specifying that which was stolen.
Now, even when they do reveal said code, they are claiming that damges have already taken place. So, even replacing the code with "clean" code will not suffice to pay for past damages, though it would prevent future infractions. If SCO wins, the judge would likely rule that either the code be removed or end users of Linux pay royalties to SCO. Again, this is only a speculation; I am certain, however, that SCO will be unable to force Linux users to keep their "illegal" version of Linux so that they would have to pay royalties.
In any case, I and many others feel that SCO's claims are bogus and that they've no chance in court. Even if the code is, in fact, copied, it still remains unclear whether or not SCO really has the rights to it and, even if they do, whether or not average Linux users are in violation.
The final line (Score:5, Funny)
They must really think everyone else is stupid. (Score:2)
Cringely (Score:5, Interesting)
SCO/Caldera's motto at the time was "Unifying Unix with Linux for Business". To the extent that wasn't just hype, how can they blame anyone but themselves for migrating their UNIX code into Linux?
There really is no way to do this right (Score:4, Interesting)
SCO also doesn't want to have to turn over everything they got. They basically want to just throw down their Unix trade secrets and Linux source code, and have people draw their own conclusions. A contract with more flexibility could open them up to having to share a lot of other things related to the case.
As for the state of Utah clause, it's pretty typical for a contract to have some state governing its enforcement, and typically the home state of the company drafting the contract. Sadly, they aren't a Delaware corp.
I think SCO is as evil as the next guy, and I think the NDA thing is a red herring, but I have to say I can't see how else they could have written this NDA without compromising secrets that they obviously feel they need to protect.
Re:There really is no way to do this right (Score:2, Funny)
Good point - but what I don't understand is why they don't put a limit on the Linux side of things? Such as - keep this secret until a judge says this is over, owtte.
So, how evil is the next guy ;-)
Re:There really is no way to do this right (Score:3, Interesting)
So what would stop someone who saw the "infringing" code from publishing the rest of the kernal, etc, except for what they saw?
Since they haven't published anything that they were shown by SCO, they aren't in violation of the NDA.
It would then be a simpl
Shit Man! (Score:2)
"Ski" from DG/UX was a pretty cute game, too...
Counter suits (Score:5, Interesting)
Could somebody who has contributed to the Linux kernel explicitly revoke SCO's license to redistribute it and then counter-sue to get them to stop? It would seem that SCO has lost their right to distribute the kernel by attempting to add restrictions on top of the GPL (which the GPL forbids) and that as a result somebody who owns part of the kernel could enforce a revokation of their ability to use the GPL'ed code. Wouldn't it be great if all the kernel contributors did this at once? SCO would quickly be drowning in countersuits. (Maybe we could even see the headline In Soviet Russia, Linus sues SCO!)
Of course, I'm not a lawyer, so I don't know how realistic of an approach this would be.
Re:Counter suits (Score:3, Interesting)
As for revoking the license, it would merely deny the right of SCO to distribute Linux kernel, including security fixes. I don't think it's a good idea. Since GPL doesn't govern the use of the software and neither does the copyright law, SCO still would be allowed to use Linux internally.
Imagine the SCO Employee NDA (Score:5, Funny)
Definition of Confidential Information (Score:2)
NDA means nothing. (Score:3, Insightful)
The ENTIRE sourcecode will have to be revealed in court. or they need to just give up.
I know that judges are corruptable, but they aren't idiots.
SCOX stock rating "report card" (Score:5, Informative)
The Morningstar Financial Health Stock Grade has changed from B- to F. For details,
click here [morningstar.com]
Stock Profitability Grade change
The Morningstar Profitability Stock Grade has changed from Not Available to F. For details,
click here [morningstar.com]
Stock Growth Grade change
The Morningstar Growth Stock Grade has changed from A to A+. For details,
click here [morningstar.com]
I suspect this won't be a "growth stock" for very long.
Larson (Score:5, Funny)
only SCO will sign the NDA (Score:3, Interesting)
The other half... (Score:4, Insightful)
I wonder if the other half might contain Linux code that's crept into SCO? Mod me down for the consipracy mongering if you want, but there's got to be some reason SCO is behaving this strangely.
--Jasin NataelThis is all getting out of hand... (Score:4, Interesting)
Nor is SCO's suit against Novell the real issue. IMHO, what's needed is for one of the 1,500 leading companies to whom SCO sent their "Stop Using Linux Or Else" messages to pony up, get some quality IP attorneys and throw it right back at SCO.
Picture it. Acme Widgets Inc respond to SCO with a clear message that they will NOT stop using Linux unless SCO can provide evidence of their claim.
Now, bluff firmly called, SCO have to put up or shut up. Acme Widgets Inc have to convince a judge to force SCO to identify the code they claim (not trivial). And somehow (and IANAL) this has GOT to get into the public domain - not SCO's code but the GPL's Linux Kernel sections claimed by SCO.
Once this happens, the uber-geeks who gave us Linux can replace the SCO sections with newly-developed code and we can all go about our business. Given the community's sparkling record on patch turnaround time, this could be concluded rapidly enough to offer Acme grounds for a dismissal.
C'mon Acme - go for it!
I believe SCO are trying to protect their IP - it's their methods which are truly offensive. Even if this case blows over, does the Open Source community want contributions from people like this?
The same might be said for IBM's silence on the issue - as Edmund Burke (IIRC) put it "evil will prevail when good men do nothing".
Damn Achronyms (Score:3, Funny)
Suggestion: (Score:4, Interesting)
and Slashdot readers' internet conections, when replying to articles covering
anything legalese, just leave out the ubiquitous "IANAL, but", and only
in case you are a lawyer, use "IAL, therefore" or "IAL, hencewith".
Thank you.
Have to see the comit history, too (Score:3, Informative)
Saying: "Looky looky! Same bits!" proves nothing.
You have to look at source tree A and source tree B and the commit history with dates, and then you at least know who included it in the source tree first... still, *that* proves nothing.
SCO must show the provenance (sp?) of the code in question, with a prerponderance of the evidence. Both A and B may have copied code from the same text book, same manufacturer's ap note, same whiteboard in a CS lecture, whatever. Unless SCO can show that they had it first, and that there is little likelihood it could have come from someplace else, only then do they have a case.
Looking at source without commit histories is pointless. Looking at commit histories does not establish where the source came from.
So, looking at source under NDA proves what, again?
Re:nda my heart (Score:5, Insightful)
The second reason is to find out if they really have a case. If Linus can prove to SCO that they're full of BS, SCO can back out now before they lose everything they have in legal fees. They'll need that money, since no one on Slashdot will pay SCO for anything ever again.
Yes, I realize that Linus has already stated that he won't look at the code, for good reasons, I just used him as an EXAMPLE.
Re:nda my heart (Score:3, Informative)
With respect to your sig: I believe Linux was originated due to problems with Minix, which is not a Microsoft product. Just a thought.
Re:nda my heart (Score:5, Insightful)
The fact that SCO is a sue happy little pissant isn't going to impress anyone that's potentially interested in a robust Unix server.
This might harm Linux, this might help Microsoft, there's even a slim chance that it will harm Unix in general. However, SCO is still going down the toilet.
Re:nda my heart (Score:5, Interesting)
You forgot your </i> tag after the quote, but that's not the point of my responding to your flamebait instead of modding you down. Modding down stifles discussion, while responding stimulates it.
I have official boxed sets of several Linux distributions. I pay for them with my employers' money in order to support free software companies. (I'm a *n*x admin at a large university). My employer supports me in this practice. However, in truth, when I install a new Linux box, I boot up from the CD and install the distro over the 'net so that it comes up with the most up-to-date packages already installed.
That being said, I've never bought a SCO (nee Caldera) distro because I've never thought they had anything to offer over and above the base Debian distro they built from. Their recent behavior has put me in the frame of mind that even if they DID offer a significant improvement over the base Debian distro I would not buy their product, so, yeah, there ARE slashdotters who pay for Linux and who will NOT ever buy from SCO as a result of this lawsuit.
Just my $0.02
Re:break the NDA? (Score:2)
Hilarity [fark.com] would ensue.
Re:break the NDA? (Score:5, Insightful)
That way if 400-500 of foo.c is revealed anonymously as part of the conflicting code, SCO can go back and sue Joe One knowing he is the only one they showed that particular piece of code to.
At least, if I were SCO, that's what I would do.
Re:break the NDA? (Score:3, Funny)
Re:Someone in California end this... (Score:2)
Re:SCO's Position: Sign it or Don't See the Goods. (Score:5, Interesting)
Really? I'm of the opinion (and I think most reasonable people would agree) that if someone wants to pick and choose what they show, htey have something to hide.
So, what are they hiding?
It's pretty obvious - the fact that they don't have a case. After all, the the code is in fact already in open-source software, it's already public.
I certainly wouldn't want to look at their piece-of-shit code, just like I wouldn't want to look at anything coming from the Beast of Redmond - to avoid future charges of infringement/theft/copying.
End result: Anyone stupid enough to go along with this qualifies for the darwin awards [darwinawards.com]. They've certainly removed themselves effectively from the pool of OSS developers.
Re:Come someone... (Score:2)
Fragging refers to killing one's opponent in the first person shooter doom. It might have come out before that or might be an old military term but Doom was where I was exposed to that term.
G
Re:Come someone... (Score:2, Offtopic)
I Am Not A Lawyer.
If you take advice marked thus and get into legal trouble, you are entirely on your own. Mind you, anybody who takes legal advice from the Web/Usenet is a workd class fool anyway.
Also, what is fragging?
Literally, killing with a fragmentation grenade - a means occasionally used to get rid of disliked officers.NCOs in the Vietnam war.
Figuratively - destroying with great force.
Re:Utah (Score:3, Informative)
Joe [pbs.org] Hill [iww.org].
Any Utah-hater worth his salt'd know that one!
(Actually, for the record, I don't completely hate Utah. It just can be frustrating at times. Whoever has that
- Blenderfish
Re:If... (Score:4, Funny)
Re:Whats to stop this (Score:3, Interesting)
Re:Whats to stop this (Score:3, Interesting)
* since the code is already released, it'd basically be a map, and I guess some code from their archives to back up the claim.