Slashdot Mirror
SCO Lists Specific Code-Infringement Claims
mugnyte writes "Those tireless folks at groklaw have transcribed and published the documents from the latest IBM/SCO hearing. In it, the exact lines of the supposed Dynix / AIX / Linux logic are given. SCO claimed that Linux's read copy update, journaling file system, enterprise volume management system, AIO (Asynchronous I/O), and "scatter gather" I/O code had been derived from either AIX or Dynix/ptx. Now we can take a look at what SCO thinks makes Linux an enterprise-ready platform started at 2.4, stealing away their market share. However, IBM released these things under the GPL ... so what license did IBM really have from SCO to do this? Which raises the question, What license did SCO have from Novell to disallow this?"
If Novell's letters to SCO are an indication, SCO did not have the license to deny IBM privelege of doing this.
This sig no verb.
So when are any of the 1,500 companies that received letters from SCO inviting them to purchase Linux licenses going to step up and complain to the US Postal Inspectors? To me, SCO committed fraud, misrepresentation, and extortion based upon their communications. Postal fraud is enough to send their entire board of directors to the slammer.
"Right now, somewhere in this world, Scott Baio is plowing a woman he doesn't love," - Peter Griffin, *Family Guy*
Whenever I read an SCO story, you never hear about the 2.6 kernel. Is this kernel so different that it lacks alleged "IP infringement?" I've heard of specific 2.4 kernels having problems, but none of the recent stuff. Is this an indication that maybe it is safest to go with 2.6 to get SCO off our back?
So, they are complaining, in part, that IBM tricked them: "They made secret plans, and didn't tell us!"
"Send an Instant Karma to me" - Yes
Well, I was having a look through this 'list' and most of them are meaningless lines that just happen to coincide. Check out this blatant infringement from net/bridge/br_stp.c:43
3
p = br->port_list;
You damned linux hippies, stealing that highly critical line has ruined SCO's business!
http://lxr.linux.no/source/net/bridge/br_stp.c#L4
No need for the party I guess.
Cheers Koz
(BIG)Assuming SCO does own some codes in Linux, and from I can read recently, Linux users seem to claim they can quickly identify those infringing codes, issue a patch and get those codes out of Linux.
This is all fine, but I want to know if SCO can still sue for past damages? E.g. the time span that those unlicensed codes were being abused?
P.S. This is just a question based on the worst case scenario.
Rock that crushes, Paper & Scissors that don't matter.
For much of the document, SCO appeared to do little more than highlight IBM's contributions to Linux. They seemed to argue that IBM transferred ideas or programming concepts into Linux rather then cite any specific meaty line by line code examples. One key point that even SCO makes in this document is that these are features that have never been part of Unix. SCO lists a lot of Linux code however they don't seem to be able to list specifically what parts of their code were lifted. A good analogy would be 2 authors writing different books on the same subject. It seemed as if SCO was claiming ownership of the ideas as if they wished they owned the patents to them. When asked what portions of Linux they own, SCO refused stating the request was "overly broad and unduly burdensome". SCO also danced around the issue that they themselves contributed to Linux and distributed the code in question under the GPL by claiming ignorance. Once I heard a joke about someone who claimed ownership of the Brooklyn bridge and tried to sell it. How is SCO claiming ownership of Linux and trying to sell it any different from that situation?
...that this has already gone farther than anyone at SCO anticipated (I'll bet a SCO license that they thought IBM would either settle or buy them out - which was a stupid assumption frankly), and now they are in a position they can neither retreat from (without instantly self-destrcuting in the process, something Boies now has too much of a stake in to allow) or advance with any real hope of winning.
It could almost be seen as a courageous effort if it wasn't so fucktastically stupid.
I'll bet a SCO sitewide license that Darl is starting to regret having ever shown up for this little legal soiree.
They have claimed, under penalty of perjury, in the IBM trial that they do not have a copy of the USL settlement.
Here they make specific claims in reference to the same settlement.
Which is the truth, and which is evidence of perjury?
SCO is "so" full of it that I'm just amazed. Anyone remember Xenix? Well, a long time ago SCO support was in a nutshell $100.00 a question. I called them in regards to the "new" USRobotics HST modem support, and they couldn't figure it out. Guess what? I figured it out myself and like a idiot, sent the fix to SCO. Am I entitled to compensation? Nahhh..., was I credited... nope. This company is lame!
Life was hell, then I discovered Linux...
>what the hell is David Boies doing backing these con artists?
I'm not sure he is. He has yet to appear in court on their behalf. His firm is being paid a great deal of money, win or lose.. my guess is that by contract they have to see this suit to the bitter end. I suspect they signed that contract without knowing both sides of the story. I doubt David Boies personally has any intention of polluting his reputation further with this case. When Kevin (Darl's brother) appeared in court instead of Boies, that was a possible indication that Boies wants to distance himself as much as he can from this case. Darl can't find anyone but his brother (and a couple other well paid,win or lose lawyers) to buy into his crackpot theories on "IP".
I know it was a joke but let me tell you something.
The further up you go in an organization more you lie every day. If you are aprogrammer you might only have to lie once or twice a week.
If you are promoted then you find yourself lying more often because you have to lie both to your bosses and your underlings.
As you go up you may find yourself lying a dozen times a day just to get through.
I imagine a CEO pretty much lies constantly. I bet they don't even know the difference between a truth and a lie anymore.
War is necrophilia.
I wanted to see what they were whining about, so I downloaded 2.4.1. None of their line numbers make any sense. They're claiming we copied comments about Linux from them? And blank lines? Am I missing something here??
In the bush era of no penalties for Worldcom or Enron execs Daryl may be laughing at all of us a few months from now.
I'm not sure where you get your information, but Andrew Fastow (Enron CFO) and his wife are going to jail. Jeff Skilling (Enron CEO) will likely be charged this week. You can check here.
You may also be shocked to notice that the crimes in question took place between 1996 and February 2001. Now, who was the President during those years?
Now, if you want to complain about how the Bush administration messed up the Microsoft case, I with you, brother.
Viv
Gmail invites for ip
When you're too lazy to do your homework, what do you do? You cheat.
... I can say that this assertion is simply wrong. People cheat when they are desparate; when they don't understand what is going on, when they fear failing. The way you notice cheating is not when people do something right, but rather when they do something wrong. People who are clever enough to cheat well will probably observe that it is less trouble to apply their cleverness to simply doing the work, than to cheat effectively; cheating effectively requires considerable effort.
/. and McBride is that very few /. readers would have the spine to stand up and assert something as outlandish as SCO asserts. To /. folk, the SCO business is all very abstract, there's a billion dollars and a corporation at stake ... but it's not our money or our corporation. It's more like the WWF, where there is an official Bad Guy who will, at the end of the evening, get stomped by the Good Guy, for the pleasure of the viewing audience.
As a Genuine University Professor, who has seen a lot of cheating
Petty cheating persists because it is expensive to prosecute. Think about it. In the university setting, for example, faculty are rewarded for bringing dollars and fame --- not for upholding academic standards among their students. If I catch someone cheating on an exam, it is my fervent hope that they will readily admit it, because if they don't, I have to weigh the cost of spending perhaps 40 man-hours (my own time, and others) to deal with an isolated case of petty cheating --- by someone who is almost certainly headed for a dismal grade anyway. People who cheat in class do not get good grades! Seriously! There are steps one can take to make cheating very difficult. For example, if my classes are small enough (under 24 students or so), I try to have an oral final exam. Anyone who can cheat during a one-on-one oral exam, well, they have a very special gift indeed. But I need at least a half hour for each exam, and there is no putting that work off on TA-slaves.
I have run into "malicious" cheaters, but such behavior is very rare --- at least among university students (engineers). Now, it may very well be that CEOs of modern corporations are cut from a different cloth --- Larry Ellison, for example, seems to be the very avatar of acquisitiveness --- but most people are pretty good. And flawed --- sort of like Zoyd Wheeler, in Pynchon's "Vineland."
It's fun to beat up on people who find themselves, through a moment of weakness, in a terrible fix. We have often not bothered to understand their circumstances, nor acknowledge our own role in their predicament. Ronald Reagan, for example, liked to blow hard about the Welfare Queen, a terrible creature which exists in about the same measure as Grendel.
For another example, consider the American Taliban, John Walker. He's a pretty fat target for abuse; but is it so surprising to the nerds of slashdot that someone might do the things that Walker did? And then when someone like Steve Earle writes a sympathetic song about Walker, the derision is turned up to 11. (try this google; most of the entries are either parodies or negative criticism, poisonous "patriotism" or other nonsense.)
If the real case of Walker makes you uneasy, how about the great supernerd John Hackworth in Neal Stephenson's magnificent "The Diamond Age." Hackworth wanted nothing more than to raise his daughter well; he "cheated," got caught in one lie, tried to cover it up, and wound up spectacularly entangled in a series of punishments that lasted over a decade.
So, anyway. It's fun to beat up on SCO, and McBride. One of the differences between most people who read
So, pay attention to the interesting analysis performed by Groklaw-folk, but mod yourself down if you're merely going to hurl abuse at Darl and SCO. This is a tragedy unfolding; a very human tragedy.
"The Buy Now" Page:
http://www.thescogroup.com/scosource/linuxl icense. html
leads to the
How to purchase and activate a SCO IP License" page
http://www.thescogroup.com/scosource/howtobu y.html
Step 1:
Review the SCO IP End User Licensing Agreement (EULA) to understand the terms and conditions and rights granted with the SCO IP License. Please click here to review the EULA.
Step 2:
Make your selection of the pertinent SCO IP license for your Server or Desktop system, and purchase by credit card through our online store. Your license will be delivered electronically to the e-mail address specified in your order form.
Step 3:
Register your SCO IP license to complete the legal activation of your license and to receive an electronic copy of the EULA.
Note: you will be required to provide the name of the Server to which the SCO IP License will be applied. Please have this information available when you register your software.
Which links to the EULA Page
http://www.thescogroup.com/scosource/eula.ht ml
THE SCO GROUP, INC.
INTELLECTUAL PROPERTY LICENSE
(This Agreement is available to all entities using a SCO Operating System distribution)
IMPORTANT, READ CAREFULLY ALL TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT ("AGREEMENT") WHICH HAS BEEN PROVIDED TO YOU AND IS INCLUDED WITH THE CERTIFICATE OF LICENSE AUTHENTICITY ("COLA"). BY EXERCISING YOUR RIGHTS UNDER THIS LICENSE, YOU ACKNOWLEDGE THAT YOU HAVE READ THIS AGREEMENT AND UNDERSTAND IT, AND YOU AGREE TO BE BOUND BY ITS TERMS AND CONDITIONS. IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT, DO NOT USE THE RIGHTS GRANTED HEREUNDER IN ANY MANNER.
YOU UNDERSTAND AND AGREE THAT SCO MAKES NO GRANT OF RIGHTS OR WARRANTIES OF ANY KIND EXPRESSED OR IMPLIED WITH RESPECT TO ANY SOFTWARE OTHER THAN THE SCO INTELLECTUAL PROPERTY DEFINED BY THIS AGREEMENT.
This Agreement does not include any rights to access, use, modify or distribute any SCO source code in any form under any licensing arrangement.
DEFINITIONS
"Agreement" is the contract between you ("You") and The SCO Group, Inc. ("SCO"), relating to the rights acquired by You. The Agreement comprises (i) this document, (ii) any amendments agreed by both You and SCO in writing and (iii) any additional terms and conditions included in the COLA. Such additional terms may pertain, without limitation, to the following: term, fees and payment, number of permitted CPUs, registration requirements, restriction on runtime environment and transfer of Your rights.
"Code" shall mean computer programming instructions.
"CPU " shall mean a single physical computer processor.
"Desktop System" means a single user computer workstation controlled by a single instance of the Operating System. It may provide personal productivity applications, web browsers and other client interfaces (e.g., mail, calendering, instant messaging, etc). It may not host services for clients on other systems.
"Method" shall mean the human or machine methodology for, or approach to, design, structure, modification, upgrade, de-bugging, tuning, improvement, or adaptation of Code.
"Operating System" shall mean software operating system Code (or Code that substantially performs the functions of an operating system) that is a distribution, rebranding, modification or derivative work of the UNIX(R) operating system or otherwise incorporates Code covered by SCO IP which is not commercially licensed by SCO or one of SCO's authorized licensees.
"System" shall mean a computer system, containing the licensed CPUs, controlled by a single instance of the Operating System.
"Object Code" shall mean the Code that results when Source Code is processed by a software compiler and is directly executable by a computer.
"UNIX-based Code" shall mean any Code or Method that: (i) in its literal or non-literal expression, structure, format, use, functiona
How can 83 lines be copied to only two lines?