FSF Statement on SCO vs. IBM 413
tomdp writes "Eben Moglen, Law professor and general counsel for the Free Software Foundation, has written a statement about SCO's lawsuit against IBM."
"Hello again, Peabody here..." -- Mister Peabody
First line... (Score:5, Funny)
Re:First line... (Score:2)
Re:First line... (Score:3, Funny)
The first thing that came to my head reading the parent was Dana Carvey's ChruchLady skit about Santa Claus - where she re-arranges the leters in Santa to spell *thunderous voice* SATAN!!!
"Well, idn't that special!!!"
Soko
Re:First line... (Score:5, Informative)
Re:First line... (Score:5, Funny)
Re:OK, so when does this party get started?.... (Score:5, Insightful)
For most of us, that surely is the point. This is Slashdot, of course we are all Linux fans, of course we want to see SCO kicked into the long grass. But even if it were to turn out the "wrong" way, it were better done sooner than later. Just suppose SCOs allecagtions are true (I doubt this as much as most). IBM gets hit with massive damages - bad for IBM shareholdres but IBM, and they, will live. But SCO has revealed all the bits of GNU/Linux it believes to be ripoffs (it has to, in order to estimate the damages and to claim future royalties). So the Linux community cuts them out, does without some of them, and puts in a panic effort to do a cleanroom rewrite of those that are really necessary. I bet that if Torvalds, Stallman & Co. put out a "Save Our System" call, any really crucial bits of the system could be duplicated in three months.
And the Linux cimmunity could get back to growth as normal. This is because the FUD would have been dissipated. The harm being done by the SCO lawsuit hanging over GNU/Linux, and SCOs threatening letters, is far greater than the harm done by ripping out the offending code - if there is any. We, the Linux community, need a quick resolution.
In English law - I don't know about US law (and IANAL anywhere) - there is a duty on a plainiff in a civil case to take all reasonable steps to minimise any losses resulting from the harm being done to them. If you think I am infinging your copyright, you have a duty to tell me as soon as possible, not wait cackling while my potential fine piles up. If such an obligation exists in US law, SCO are not observing it. The cannot claim that every line of GNU/Linux is theirs. In fact, they cannmot claim that the fragnents allegedly stolen by IBM are crucial to the system, because it existed as a working system before IBM ever became involved. But they do claim that they have lost sales of their Unix product because Linux, incorporating their stolen code, is so good. It seems to me, therefore, that they have a duty to expose the code they allege to be stolen, and allow the Linux community to remove it. If their theory about the value of their code (if any) is true, Linux will drop in functionality and their sales will correspondingly recover; they may then claim for past, but not future, sales lost. In fact, I think that Linux would barely huccup. As I say, three months top level work by the community should repair all significant holes in the system.
So if anybody knows how to speed thes up, pleas tell. And for heavans sake, nobody do anything which could slow it down.
Thank you FSF (Score:4, Informative)
Kudos FSF and Eben Moglen
Definite Quality article (Score:3, Informative)
I think this will certainly put to rest any out there nervous about this case. Well, except IBM.
amazing restraint (Score:2)
Just so you guys know, SCO does have a secret biochemistry lab working on a coffee-eradicating bacteria.
Re:Thank you FSF (Score:4, Funny)
Yeah... but did anyone get the sense that Stallman read the draft essay and had Eben inject that paragraph about calling it 'GNU/Linux' instead of just 'Linux'?
Headline: Microsoft Bankrupt, Linux Rules the World
Stallman: Ahh!!! It's GNU/Linux, damnit.
Headline: Linux Marketshare 60%, Microsoft GPL's Windows
Stallman: Noooo... it's 'GNU/Linux'... Linux is only a kernel!
Headline: Extraterrestials Obliterate Eastern Seaboard
Stallman: 'GNU/Linux' everyone, 'GNU/Linux'...
Re:Thank you FSF (Score:5, Insightful)
Headline: Microsoft Bankrupt, Linux Rules the World ...GNU/Linux...
Stallman:
You: Wah! Stallman is pushing his "GNU/Linux" agenda!
Headline: Linux Marketshare 60%, Microsoft GPL's Windows ...GNU/Linux...
Stallman:
You: Wah! Stallman wants to take over the world!
Headline: Extraterrestials Obliterate Eastern Seaboard ...GNU/Linux...
Stallman:
You: Wah! Stallman said that phrase again!
Re:Have you noticed... (Score:5, Funny)
Shut up you pompus twit. I've no time for jerks like you - I have to go play with my RMS and ESR action-figures.
(kidding)
Re:Thank you FSF (Score:3, Insightful)
Re:Thank you FSF (Score:3, Insightful)
Why it's important. (Score:5, Insightful)
As everyone knows, they went from "Trade secret" to "license violation" to "copyright violation" to alleging "patent" almost.
They went from talking about their secrets making it into linux, to pointing out it was actually code that was NOT their secret, but that they technically may have an exclusive license to, due to some wording in IBM's Unix license.
They are saying many confusing things, and backing it up with little.
Sco -vs- IBM is between SCO and IBM. Hopefully the rest of the world is smart enough to realize that the free software world is more than happy to obey the law, if only someone would tell them what they are doing wrong.
So it's good for people, lawyers, and organisations to put forward their own researched opinions as to what the ramifications of SCO's actions are, because the public needs both sides.
Re:Thank you FSF (Score:5, Funny)
No place for that on Slashdot.
BTW, did you know that Daryl McBride is, in fact, the goatse.cx man?
(you just need to view him from the 'right' angle)
Re:Thank you FSF (Score:5, Insightful)
While I'm generally not all that fond if the name nitpicking either, it's actually a relavent distinction for once - SCO has been spouting off things about "whole programs copied" which tends to imply that they're talking about quite a bit more than the kernel. Which also raises questions - we can all figure out where kernel source code came from. Not all projects are as careful about logging changes.
Amen (Score:3, Insightful)
Their problem is the fear of becoming irrelevent and I have some news for them. Shouting "call it GNU/Linux" several times a week is one of the fastest ways to make that fear come true. The Free Software community is a harsh meritocracy and of late about all the FSF has been producing is nonsense about GNU/Linux and n
Re:Amen (Score:4, Interesting)
Maybe it should be called Red Hat/Linux then.
Seriously, when referring to the whole system, you don't call it Linux anyway. You call it whatever the system is called. In my case, Gentoo Linux. Or in other cases, Debian GNU/Linux, Red Hat Linux, or Mandrake Linux. The term 'Linux' properly refers to the kernel. But there's nothing wrong when referring to Linux generically to call it 'Linux' but I don't know.
For that matter, Solaris ships with a Freeware disc consisting of mostly GNU projects like GNOME, gcc, GNU toolchain, etc. Why doesn't Stallman insist it be called GNU/Solaris?
Appreciating the FSF's contribution (Score:5, Insightful)
I'd say their view of copyright law, software programming, and giving respect by calling things by their given name is considerably "grow[n] up". What you don't appear to understand is that SCO's language is purposefully unclear so they can leave their options open on what to sue for. The FSF was simply being thorough in their explanation by showing that SCO's language lead to a losing case.
No on both counts--their fear is probably closer to not having enough money [fsf.org] to do all the things they want to do, and no you don't have any news for them. Perhaps you haven't been around long enough to know what contributions the GNU project has made to our community (ideological and programmatic). The political forces are at work challenge both the Open Source and Free Software movements and must be met by focusing our efforts on lobbying for political support, not just more code.
Getting a working GNU/Hurd system has been accomplished and looks to me like it is now in the stage where it is not ready for most computer users but it does boot. Improvements and extensions to the system (as well as getting the Hurd on a new microkernel) continue to arrive. This is all significant and needed progress but more code will not help stop harmful policies from being adopted under the cry of "harmonization" (such as EU adopting software patents or stopping the US Congress from extending the term of copyright again), nor will it stop various US states from adopting legislation that could (among other things) make it illegal to have a firewall unless the local telecommnications corporation says otherwise, or a host of other things that adversely affect our community. The FSF continues to speak on these issues and support Free Software development; the FSF is relevant nearly 30 years after they began.
Don't think that developing code must be done instead of working on other issues. All this and more needs to be done and is being done all at the same time.
Re:Amen (Score:3, Insightful)
What seems to piss off the FSF is that the Free Software community as a whole seems to have decided the Linux movement's 'third w
Re:I don't really see this (Score:3, Interesting)
Putting the GNU where Debian do
it's more part of the whole philosophy (Score:3, Informative)
Furthermore, I'd argue that Debian is a good example of RMS's argument that Linux is just a kernel, and n
Re:Nobody "sees" Linux either! (Score:3, Interesting)
If using GNU code automatically infects the name then I guess when Microsoft was shipping the GNU toolchain (with source) as part of the POSIX joke in NT 3.1, Stallman should have been shouting down anyone calling it Windows NT and saying it should be properly called GNU/NT.
It just doesn't work that way. The GNU toolchain is just that, a toolset. Important? Yup. Usefull? Yup. But just because DOS used to be crap without Norton Utilitie
Re:Yeah (Score:3, Insightful)
GNU/Linux/XFree/KDE/etc.
Or, if you choose a single name, choose the most singificant single contributor: GNU.
This is the FSF claim.
Re:Yeah (Score:5, Insightful)
What has GNU contributed to Linux? The GNU tools don't count since they a) predate Linux and b) according to the FSF are strictly intended for GNU and any use others make of their Free Software is just a bonus. So just what has the FSF/The GNU Project done with the express purpose of aiding the Linux based distributions? (Hint: there are some, but not many and those are often tangential. Certainly not a significant share though.)
I'm sorry but the FSF can't have it both ways, either they ARE still working on GNU and shouldn't be creating confusion by trying to stick that name to other people's unrelated work or should admit defeat and adopt one of the existing distributions into the GNU Project and rename it as the Official GNU System. Hell, they could fork RedHat and do the world a real favor by providing a freely redistributable version of a stable RedHat. I'd even BUY that from them if they didn't want per seat licensing.
In a nutshell, what I'm saying is that if you expect people to call it GNU it better have a GNU on the login screen, not a hat, lizard or penguin.
But to date, Linux is not GNU. As to the Linux the kernel and Linux the OS confusion, it really isn't. We all know what people mean when they use the word, and to date if it uses the Linux kernel and the distribution want to call it Linux and fly the penguin flag everyone accepts it as a new member of the Linux family.
In the end this is why they are so hysterical about GNU/Linux and don't give a crap about renaming Solaris to GNU/Solaris. Because of Linux, few people care anymore whether GNU ever ships a working system. Linux is a threat to their ego and their need to control. It is the penguin they hate, bacause in the marketplace of ideas more people consider themselves followers of the Penguin banner than members of the GNU herd.
(yea, bad pun)
The FSF has done some wonderful things, and will probably do more in the future, but I for one am glad things worked out where the FSF was never given that much control because like most fanatics they serve a useful purpose but should NEVER be given real power. (See current world affairs for examples.)
p.s. This isn't flamebait. If you disagree, point out where I'm in error instead of modding.
Re:Yeah (Score:4, Insightful)
I don't understand your argument about the GNU tools not counting. When you write a program, it doesn't touch the kernel directly; it gets all its services from language support libraries (the C and C++ libraries). These are all GNU. Similarly, without the GNU tools you don't have a usable system.
But in answer to some of your other questions: the FSF provided key funding to get the Debian distribution launched. Eben Moglen, the FSF lawyer, has worked behind the scenes to pressure more than a hundred different GPL violators to comply with the license, and has helped many people who didn't assign their copyright to the FSF deal with legal issues (notably the mysql folks).
The Debian folks are working on a distribution that runs the GNU C library and Debian packages on top of a BSD kernel. You won't be able to tell, when using such a system, that you aren't using a Linux-based system, because all the apps will work just the same.
You are right that the FSF tools aren't designed specifically for Linux, they are key infrastructure for all the BSD systems as well, and also Apple's OSX.
Re:Yeah (Score:4, Insightful)
I disagree ... (Score:2)
It was important in this article to carefully distinguish between the kernel and a complete system (as compared to UNIX) to at least sweep one part of the SCO FUD away.
I would have said this is a valid way, legally, to get to the nub of the argument and to then deliver the knock out blow blow, indicating that they had then released the code under GPL.
Of course the GPL argument applies to ev
I'm surprised it wasn't released earlier (Score:5, Interesting)
Moreover, is it just me, or has the case really gone from something that is targeted at Linux (kernel) that many people worry about into just an internal dispute between IBM and SCO that not many really worry about anymore? I woudn't be suprised if the latter was true.
We will publish no brief before its time. (Score:5, Insightful)
Most of what's come out of SCO is so self-contradictory that the only intelligent response is "What the hell are you saying?" Until they can nail down exactly what they're complaining about, there's nothing else to do but demand that they give the particulars.
Re:We will publish no brief before its time. (Score:2, Funny)
Re:We will publish no brief before its time. (Score:5, Funny)
I picture an IBM lawyer taking out the SCO board:
*BANG*, Head Shot!
*BANG*, Double Kill!
*BANG*, Multi Kill!
*BANG*, Ultra Kill!
*BANG*, Monster Kill!
Re:We will publish no brief before its time. (Score:2)
Spend your next vacation on exotic LB426
psst, if you're referring to the planet in Alien (when it was unnamed) and Aliens I believe it's called LV426. Otherwise still a funny sig.
Re:We will publish no brief before its time. (Score:3, Funny)
Damn, your right! What is that V doing next to the B anyways?
I also realized I missed 3 members of SCO's board, so:
*BANG*, Killing Spree!
*BANG*, Rampage!
*BANG*, Dominating!
Re:We will publish no brief before its time. (Score:3, Funny)
Legal[IBM]: damn l337 h@x0rs....
Re:We will publish no brief before its time. (Score:4, Insightful)
In this case the FSF lawyer seems to be taking the best approach for damage limitation. Ask SCO for specific details of the parts of Linux they claim are infringing.
Courts tend to try to act in a reasonable way. The two big issues for a copyright lawsuit are financial losses and intention. It is unlikely that the courts are going to impose substantial damages for unintentional infringement if there is no financial loss for the copyright holder or gain for the alleged infringer.
What the FSF is doing here is taking the moral high ground. Clearly there is no way anyone can prove the provenance of every line of code in a million lines of source. But they can demonstrate that they are not willfully infringing.
SCO knows that there is no chance of significant damages if the alleged infringing code is replaced before the case comes to trial. That is the reason they are trying to avoid stating their claim. It is an utterly futile legal strategy, in the first place the court is not going to set a trial date before SCO specifies the lines of code at issue. Secondly the fact SCO is trying to prevent linux removing the alleged infringing code is likely to be taken into account by the court.
Re:We will publish no brief before its time. (Score:3, Insightful)
That's bullshit, go ahead and ask any IP lawyer. Just because the infringing code is removed doesn't negate the fact that the infringement occured, and it would have absolutely no negative effect on any damages awarded.
As a strategy it's completely braindead. Not only would pointing out the infringing code have no effect on any legitimate claims they have against IBM, but fai
Re:We will publish no brief before its time. (Score:3, Informative)
Removing the alleged infringing code does not eliminate the infringement but it does significantly limit the damages.
If the infringement is deemed to be willful the plaintif is entitled to statutory damages irrespective of any actual damage that occurs and punitive trebled damages.
If th
A Legal Virus... (Score:5, Interesting)
This article seems to confirm my suspicion that this lawsuit is a business strategy rather than a principled legal action. If it is also true they they themselves distributed the code under the GPL for which they now seek copyright protection, then maybe the GPL is really the target. Perhaps their lawyers believe that if they can make an argument that invalidates the GPL then they can indeed make a claim against IBM.
But, it is important to note that the exploit here would be of the copyright laws rather as a remedy for some improper action by IBM.
In this sense, the lawsuit is the legal equivalent of a virus. It is seeking to exploit a weakness in the code . Rather than doing something just and benevolent (as lawsuits are intended), this suit seems to seek to exploit a weakness for selfish gain or malevolent satisfaction.
Beyond that, the lack of distinction between GNU and Linux in their pleadings as described in the EFF statement is just lame on SCO's part. Lord knows, both Mr. Stallman and Mr. Raymond have done what they could to ring that bell. Some SCO investigator should have picked up on that.
Re:A Legal Virus... (Score:5, Insightful)
Re:A Legal Virus... (Score:3, Interesting)
1) They won't ever be able to take control o fthe Linux kernel. That their code was used in it does not give them any legal right to the other code in it. And, no, they really aren't that stupid.
2) The GPL doesn't come into this case. It's a case about contract violations alleged against IBM. IBM allegedly broke their contractual limits on disclosing SCO code. The contract violations are much more damaging than any IP violations, so IP ownership just doesn't come into it in this case. I
Re:A Legal Virus... (Score:5, Interesting)
Where life is going to get interesting is who is going to be suing SCO for damages. They have made very public and very damaging accusations against just about everyone. Someone is going to sue for defamation, and probably win.
Re:A Legal Virus... (Score:3, Informative)
I do not disagree with you, but when will they finally be forced to try to produce a real case? Based on what I have seen of US litigation in the past, is there not every prospect of years of unsubstantiated FUD before they ever have to produce something for a court to make a decision about?
Re:A Legal Virus... (Score:3, Insightful)
It would apply, however, if they start suing Linux distributors or users. But that isn't really on the horizon.
Re:A Legal Virus...Most Definitely (Score:5, Interesting)
Law suits imho (I teach media law) are far more often strategies than principled legal action. Sometimes the strategy is principled, and sometimes not. Many famous law decisions by the US Supreme Court were "set up" by one or even both parties to render a decision. So, in U.S. v. Haggerty (the federal flag burning case) someone deliberately burned a flag during a protest in order to bring the law suit. In another example, corporations are required by law to "defend" their trademarks, or risk them entering the public domain, so not that long ago Intel began to demand that a non-profit group that teaches yoga to young people in juvanile detention called "Yoga Inside" change their name because it violated the trademark "Intel Inside." Sometimes principles come out of law decisions, but lawsuits are strategies. My exmaples are two of the less henious strategies out there, but the law is a self-replicating virus even when its biproducts are principled.
Re:A Legal Virus...Most Definitely (Score:2)
You are correct. I think I might have not chosen the best word. I was referring to principle with a lower case p, as in "we own the code." I don't see how they can even believe that in this case.
Voiding GNU wouldn't work (Score:3, Informative)
Voiding the GPL would be mostly shooting themselves in the foot. The GPl is mostly a promise by the owner of the software in question that they will not sue you for copyright violation if you agree to -- and follow certain principles
If SCO were to step in front of the court and claim that they believed that the GPL was void. They would be arguing that they have been kn
Corporate Naivete? (Score:3, Insightful)
Wow, this is a surprise - we're talking about a corporation here, not a philanthropist. This is like saying 'the way this shark is circling around me confirms my suspicion that it wants to eat me and not be my friend.'
Corporation's motivations and ethical motivations are completely orthogonal to one another. In some cases, what's best for the company (& shareholders) is ethical
Mmmm (Score:5, Funny)
Re:Mmmm (Score:2)
That aside, they are at least keeping people posted on what is going on with the SCO situation, even if it is getting a bit redundant, this behavior by SCO is a serious problem for the open source community and to innovation in
Trade secret has been dead for awhile (Score:5, Interesting)
Just a refresher for trade secret protection to apply, everyone who comes into contact with the information, has to agree to a NDA, has to be informed that the information is trade secret, and has to be informed that the company will take action against them if they reveal it. The company further has to have regular trade secret audits to review procedures and make certain that the information isn't being improperly divulged.
Take an operating systems course in college ? Look at anything from GNU ? SCO going after IBM for trade secret infringement is laughable. Whats even funnier is they hired a lawyer who couldnt even get a decent judgement against microsoft for anticompetetive practices, after the introduced obviously fabricated evidence into court
Re:Trade secret has been dead for awhile (Score:3, Insightful)
I bought a book on Unix a few years back that had a CD in the back with the source code.
It was for educational purposes...
The core issue is IP, not SCO (Score:2)
Re:The core issue is IP, not SCO (Score:4, Funny)
They have an compressor sucking the surrounding air, bottling it in tanks, and being sold for $1000/liter. The bottle comes with a free mask, what a deal!
When no one buys this SCOair, they call the constables over to complain about all the nose pirates. They insist that the elephant (IBM) next door it sucking all the air with his trunk and giving it to everyone.
Someone points out that just last week these same folks had tried a similar scheme with bottled water. After an hour of SCO's screaming the authorities cart the SCOair people away for disturbing the peace.
A better view of the same issue (Score:5, Insightful)
"Moreover, there are straightforward legal reasons why SCO's assertions concerning claims against the kernel or other free software are likely to fail. As to its trade secret claims, which are the only claims actually made in the lawsuit against IBM, there remains the simple fact that SCO has for years distributed copies of the kernel, Linux, as part of GNU/Linux free software systems. Those systems were distributed by SCO in full compliance with GPL, and therefore included complete source code. So SCO itself has continuously published, as part of its regular business, the material which it claims includes its trade secrets. There is simply no legal basis on which SCO can claim trade secret liability in others for material it widely and commercially published itself under a license that specifically permitted unrestricted copying and distribution."
So instead of claiming they inadvertantly GPLed it, we should rather say, they only made it worse by distributing it themselves, and cannot claim any liability from other people doing the same.
In case you missed yesterday's SpongeBob: (Score:4, Funny)
SpongeBob lays down and acts dead.
Patrick: Uhh, you're dead.
SpongeBob: No Patrick, I'm SCO!
Patrick: What's the difference? Ha ha ha
SpongeBob: Ha ha ha ha.
Operating System? (Score:2, Informative)
Now that the FSF claims the OS to be the kernel plus the GNU utils, do we have to change the definition? Is CS a democratic science ruled by majority? I know, I am picking nits. I have a whole basket full.
Re:Operating System? (Score:2)
Say, what is the proper term for the whole computer, sans screen and peripherals? CPU really means the processor chip. I've always like "Computer". Workstation sounds impressive, but it usually refers to the whole setup (plus computer companies are reserving the word for their brawnier offerings.)
Re:Operating System? (Score:2)
I think the word you are looking for is `box'.
Aren't we just helping SCO... (Score:3, Interesting)
Once it stopped appearing daily on all the news sites around, everything would calm down a bit, and the case would generally be seen as a private law suit about trade secrets between two companies having a long history of cross-licensing agreements, i.e. nothing that extraordinary.
But I see that at least some news sites seem to have started understanding this already:
We unsuccessfully tried to ignore the SCO v. IBM fracas, mostly because ... [linuxjournal.com]
and
We know just how you feel [lwn.net] (lwn.net commenting on the above quote from Linux journal...)
its gnu/linux dammit (Score:2, Interesting)
SCO is protecting Linux (Score:5, Interesting)
Someone needs to draw the media's attention to this point: SCO itself has protected the Linux kernel againt any claim of infringement by SCO. Those 1500 companies SCO mailed letters to can rest assured that they have nothing to fear--SCO itself has released the kernel under the GPL and therefore SCO has given everyone in the world a license to use it.
They may have a case against IBM, but SCO itself has given a license to everyone else.
This needs to get more play in the press, and I think it's the most important point in the article.
Re:SCO is protecting Linux (Score:2)
Re:SCO is protecting Linux (Score:5, Insightful)
Did not SCO have developers working on the code inhouse?
If they are modifying and distributing the code themselves, and over a period of several YEARS, you would think that someone there would have caught this, eh??
No, incompetence and ignorance is not an excuse.
They KNEW what code was in the kernel and distributed it under the GPL.
If they did *not know* then they are ignorant bastards and that's just too bad for them, they still ditributed the code under the GPL and had ample time to not only catch but to rectify any descrepancies...
Re:SCO is protecting Linux (Score:2)
C//
Geek lawyering and Dobby's sock (Score:4, Interesting)
What is omitted from this discussion, and what Eben certainly must already know, is that if SCO redistributes in good faith Free products that it receives from the community, then the illegal inclusion by a third party of material copyrighted by SCO does not in any way lessen SCO's claim to that copyright.
It's as if you sold your house "as is", and while you were in the office signing over title someone stole your car and parked it in your garage.
What's pretty obvious is that Open Source Software functions like an online magazine or bulletin board, to which malicious or incompetent users may illegally post copyrighted material. Once the violation is identified, the offending content is removed. The legal standing of companies reselling the content would be the subject of this suit.
Suppose O'Reilly published a "Best of
Re:Geek lawyering and Dobby's sock (Score:4, Insightful)
That depends on whether the court holds that SCO should have been more diligent in reviewing the source code before they released their version of Linux. If they had done a thorough review they would certainly have found the offending code This could be a lose-lose situation for Open Source.. If the court finds that SCO was not responsible for reviewing the code, then the copyright infringement case against the authors of Linux can go forward. If they find that SCO was responsible and that the code is now GPL, it would mean that anybody who publishes open source software is responsible for its content, whether they wrote the code or not. I have no idea which way the courts will come down on this issue, but it could definitely complicate publishing open source software.
What's pretty obvious is that Open Source Software functions like an online magazine or bulletin board, to which malicious or incompetent users may illegally post copyrighted material.
This argument didn't help Napster. There's a distinction in the law where financial incentive is concerned. Bulletin board operators don't gain anything by copyrighted material being posted on their systems (unless they do it themselves to attract users). Software vendors do gain an advantage by using code from other software since they save the cost of writing the code themselves.
Re:Geek lawyering and Dobby's sock (Score:2)
But they can't make that argument in court and expect it not to be shot down in flames. By their own admission, they continued selling the supposedly infringing product, under the GNU license, for many m
In summary (Score:2, Troll)
Yeah right.
semantic error (Score:2)
When you write "UDP/IP", you are referring to "UDP over IP". You are not implying that some entity "UDP" is the owner of "IP" -- "UDP" is not an adjective modifying "IP". The same thing applies to "GNU/Linux", which refers to the GNU system (glibc, gcc, and the GNU tools) running on top of the Linux kernel.
If the FSF were to have their own "Linux distro", they might call it "GNU GNU/Linux"; if they f
There is an old saying (Score:2)
Re:There is an old saying (Score:5, Funny)
Sue the b&stards (Score:2)
Re:Sue the b&stards (Score:3, Funny)
Of course everyone at SCO say that phrase the othere way round.
The best SCO can get. (Score:4, Funny)
If they claim that they did not know that their code was in it, then linux users and other Linux distributors can not be bothered because they too did not know it was SCO's code. The law cannot be more forgiving of SCO for its negligence than to the Linux users/distributors.
SCO should forget about getting anything out lincensing from Linux ever.
The case between SCO and IBM now has boiled down to a contract dispute, which has to do with interpretation of the meaning of derivative works. In any case SCO is doomed because they inherited the documents and can not claim to interpret what it was intended to mean. Since SCO did not draft those documents, expert witnesses from AT&T which drafted those contracts will clearify what they meant by derivative works and SCO would be screwed.
SCO (Score:5, Interesting)
The IBM vs. SCO dispute appears to be something that Linux itself is not involved in except as a matter of evidence of violation of contract, unless I misunderstand what the initial lawsuit was about. (IANAL.) IBM does not have any control over the Linux kernel.
The involvement of free software, and I think the reason many of us are so up in arms, is certain statements SCO has made which seem to indicate it thinks a) it can treat Linux, and all the contributions made to Linux by people everywhere, as SCO property and b) that any Unix like system, of any type, also owes SCO for IP use. Those are the really dangerous thoughts, because a lot of us don't trust the court system to acknowledge common sense. The whole IBM thing is just a prelude as far as Linux is concerned - contract disputes between IBM and SCO are secondary. It's whether SCO thinks they can go after Linux that is the real issue. And the reason for the sound and fury is they seem to think they can, or at least they say that. Not to mention their statements that they don't believe the Linux kernel could be enterprise ready so quickly (whatever that means) without commercial software being included. How do they know that? The attitude of "well, we know you aren't capable of creating this, so if you have it it must be from us" is extremely insulting and arrogant. No one has ever put a bounds on what the free software community can achieve with any success. It's just too diverse.
The nightmare scenario seems to be this: A US Court grants SCO the right to all Linux IP, based on some bizarre reading of derivative work definitons. Consequently, if people in the US want to use Linux they now have to license it from SCO, despite the fact that SCO did not create most of the code in Linux. Our efforts will have essentially been stolen out from under us - most developers for Linux have worked in good faith to create a totally free system. If SCO is allowed to destroy that, the result is many years of work down the drain, because free software and open source both would sooner abandon Linux than pay SCO anything. Indeed, if SCO succeeds in such an attempt, Linux will become non-free. The effort will have to be recreated elsewhere, and if SCO's claims to all Unix like operating systems holds up it will have to be on something completely new. Plan9 perhaps, or Hurd, or maybe something totally new. But in any case, years gone.
The mistake SCO seems to be making is that they can grab Linux and make people pay for it. That is, of course, utter nonsense. People would sooner abandon it and start over. Linux is not special because of its technology. It is the freedom of Linux that makes it a powerful force in the software world. The technology is secondary. SCO controlling the technology would, by definition, destroy that which makes Linux worthwhile. We would be pissed as heck if they somehow managed it, but maybe just for that reason the rise of a new system without any IP ties would probably be all the faster. SCO is like the child who wants to hold a snowflake in their hand - the mere act of grabbing it destroys it.
What their motivations might be, there has been a lot of speculation. The obvious possibilities have already been mentioned time and again. SCO will not succeed if their goal is to make money from controlling open source software, because any software they control is not, by definition, open source. We will go elsewhere.
Do I think it will come to that? No. But the law is a strange animal, and one is never 100% sure what will happen. So the sooner this is over with, the happier we will all be. And whatever happens, SCO can forget about ever being a viable commercial business again. I would not do business with any company who uses methods such as those I have seen from them.
Re:SCO (Score:4, Insightful)
I think we can all be fairly sure it won't come to that. No rational reading of derivative work would grant the entirety of GNU/Linux to SCO.
1) SCO would never have any argument for ownership of the "GNU" part of GNU/Linux.
2) Any current hardware support by the Linux kernel, to name just one important feature, would have no conceivable connection to SCO's code and thus would not be a derivative work.
3) Depending on which code is copied, SCO would have, tops, rights to a small amount of code that interacts with it, but not the entire kernel.
No offense intended, but this is just fearmongering. Popular misconceptions:
"SCO is after the GPL!" Wrong. SCO is bringing a suit based on alleged contract violations by IBM; IP ownership and the GPL don't come into it.
"SCO is after ownership of Linux!" SCO would not be able to gain ownership of Linux as a whole; but rather damages from IBM for disclosure of SCO code. Perfectly fair, in my opinion, if IBM really did disclose SCO code in violations of IBM's contract.
"SCO is just trying to be bought out by IBM." I don't know where this one comes from, but why would IBM buy SCO? Especially after such an antagonistic move like this?
"SCO wants to make all Linux users pay through the nose." How would SCO get back payments from home users of Linux for a contract violation by IBM? The culpability stops with IBM (or perhaps Linux distributors); the letters SCO sent out were a calculated ploy to make "true" Unix look more appealing for corporate users than Linux. SCO doesn't give a shit what we Slashdot users run on our own PCs; it's not like we'd all be buying SCO Unix instead.
Slashdot readers like to complain about SCO "FUD", but they are easily the biggest victims of it.
SCO'ld news (Score:2)
In any case yes Linux = kernel, GNU is all the rest.
SCO is trying to taint the whole GNU movement. I do have to wonder what the FSF's status is on how the HURD is coming along. I have been to the site and saw some info on downloading the GNU/hurd, but was not sure what to install or how. Their docs seemed lacking.
I am getting tired of SCO and all their FUD spreadding and the complete lack of willingness to show what code is really tainted. It would make more sense to show
Re:SCO'ld news (Score:4, Funny)
So is their kernel ... has been for the last 10 years. Remember the Linux Kernel is just a temporary solution. We'll be moving to HURD any day now. You know once they add hardware support for ISA and IDE.
Wondering... (Score:4, Interesting)
I've often wondered if someone wouldn't sue open source software projects based on the argument it isn't fair that they have to compete against a free product, and asking that no one be allowed to distribute free software on the grounds it is unfair competition. Utter nonsense, of course, but the "I have a right to make a profit" thinking in the US is so strong sometimes it makes me wonder if someday we will see it.
Slashdot Editor Checklist (Score:5, Funny)
1) Microsoft Security Hole
2) SCO story 1
3) SCO story 2
3) Web Development with PHP and/or Perl book review
4) Physics story that no-one understands but everyone pretends to
5) New Mozilla build
6) Repost of one of the above
It's a kernel issue, damnit! (Score:2)
When SCO/IBM is talking about Linux in this case, they're talking about the kernel and nothing else, which is rather obvious from the few details that have been given.
The FSF own no kernel copyrights as far as I know, they're just using this stuff to trumpet out RMSs tired old message of "it's GNU/Linux not Linux".
Sometimes I feel it'd be worth porting over the BSD runtime environment just to stop having to hear these sour grapes..
Ulterior motives (Score:2)
Interesting HTML (Score:2)
From the LaTeX-like quotes I guessed the article was written by an Emacs fanatic (hey, I'm an Emacs fanatic myself). I examined the source and bingo!, two spaces after each dot.
More interesting was the lack of closing paragraph tags and weird attribute style. Examining the headers I found the doctype:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
Man, someone's still writing HTML 2.0!
Novell: "Stolen Code" is Actually Public-Domain IP (Score:5, Informative)
"As a result, Novell is supposedly trying to figure out how to lob another discrediting hand grenade at SCO and claim that the code SCO is basing its $3 billion contentions on is actually in the public domain," LinuxGram says.
SCO vs. IBM vs. [INSERT YOUR NAME HERE] (Score:3, Insightful)
There is a general idea that some people have that Linux is THE operating system. The fact of the matter is that Linux is just the kernel. Everything else (for the most part) isn't Linux. People need to be educated on that fact.
My favorite line from the statement:
"... SCO's public statements are at best misleading and irresponsible."
Duh! But not everyone understands, so thanks for saying that.
Confusion created by calling the entire OS "Linux" (Score:4, Interesting)
This is a demonstratable case of where harm is being done to the entire FS and OSS community because of the confusion between Linux the kernel and the GNU/Linux OS, which is at the core of what every distributor (like RedHat, Suse, Gentoo, Debian, etc) distributes as a distribution.
The only reason SCO is able to exploit the confusion between Linux the kernel and the "Linux OS" is because fanatics insist that because most people have always called the entire OS "Linux", we should continue to do so; despite the fact that it creates confusion between the kernel and the OS, while another name (GNU/Linux) ameliorates that confusion.
Now, I'm not saying that if everyone knew that Linux referred properly to the kernel, and GNU/Linux to the set of OS distributions, this lawsuit would have been prevented. SCO still could have sued IBM, and still could have launched this smear-campaign. However, they would have to specify exactly what they were referring to -- the kernel or the entire OS. They would not be able to exploit ambiguity and confusion to as great an extent as they currently are.
Re:Similarities with RMS (Score:3, Insightful)
Re:I certainly wasn't expecting that!! (Score:2)
Ummmm... last I checked, IBM is fully compliant with not only the rules of Free Software, but it's spirit as well. They are playing nice with FOSS, and actually seem to grok what it's all about. Sure they want to make lots of $ from FOSS, but they understand that the collaborative process is the heart of the system, and if they hurt the OSS dev communi
Re:Thank you Michael ... (Score:2)
sure, but only if you have thrown out the proprietary versions of unix utilities, compiler, etc. out. in GNU/Linux systems not only most of the tools come from GNU (along with BSD to be fair), they also do not include alternatives in general. that is the key point.and please don't tell me you
Re:Cash Buys your Lawyers (Score:2)
We'll see what happens, but at the moment all that SCO is paying for is the bandwidth that we make them use every time we visit their site because of this FUD.
Contingency Fee, not cash. (Score:4, Informative)
no shit sherlock (Score:5, Informative)
It took you this long to realize that? The whole point of a business is to make money. Although I do think acting like the GPL is the next messiah is childish. It makes you look like a teenage anarchist who hasn't grown up yet.
Re:Anyone who opposes the GPL is a corporate whore (Score:3, Insightful)
Uhm, what the hell are you smoking? Businesses primarily are supposed to value their own best intrests first, otherwise what is the fucking point in starting a business? The fact that some businesses seem to value their customers is only a side effect of the fact that for them that brings in the most profit.
Individual freedoms must superceded any rights that corporations have. It's time that we really restructure the way business works.
Incase you hadnt noticed, this was the "basis" for marxism, comm
Re:Anyone who opposes the GPL is a corporate whore (Score:5, Insightful)
I am not sure if you goal was to take the polar opposite stance of the post you are replying to but you have made just as grievous errors. Let us begin.
You seem to imply that valuing one's customers is only a side effect of the best interests of the company (which your point seems to be is to make money). This is a terribly cynical POV, however is the the view most companies take. Perhaps on the other hand a company should have a goal of making profit but not have it be the blinding exclusive goal.
Point 2. I am not sure what book you got our definitions from but just generally one does not associate strong personal freedoms with Marxism and communism. Unless you are look only at the alleged 'anti- private business/ownership' angle. Of course both of those are in the theory. As we all know the practice of those philosophies turned out different. As for unions, well (again ideally) they are supposed to advocate the rights of the workers.
Instead of driveling on here let me sum up. I believe that businesses (corporations) should have no 'rights' in the sense that individuals have. Corporations are artificial entities. We as people with rights can grant on to them (corporations) privileges, that may mimic the rights an individual has. However with all privileges we stipulate the responsibilities that that one has to meet in order to keep those privileges. Thus a business can run and make money for its owners, pay its employees, while not gaining the illusion that it it entitled to the rights and actions of an actual human being.
Re:Anyone who opposes the GPL is a corporate whore (Score:4, Insightful)
I'm afraid you are quite incorrect. The 'revocation of rights' for corporations as you call it does not infringe or revoke the rights of the individual. As, you have correctly stated, a corporation is an imaginary construct we are real people can but any or all the limitations on them as we deem fit. To raise a corporation to the level of 'being', that we afford actual people implies that corporations are the equal of said individuals. Thus making a corporation more than it is, or we, people, less than we are.
"By opposing corporate rights, Anticorporatists seek to deny rights to a specific group of individuals who hold views opposing their own: the representatives of corporations. Reborn in modern liberals, it is the age-old totatiltarian instinct to deny rights to those who think differently; Special rights for special classes, not equal rights for all."
All I can say is HUH? Im not quite sure when this became an 'anti-corporation' argument. And I haven not suggested denying rights to any individuals. People who represent corporations have all the rights as an individual has. Being part of a corporation does not grant them some new superset of rights or privileges. Might I remind you that your attempt to 'labelize' liberals as totalitarians is not only currently false but also historically. Generally speaking those who wants equal rights for all people don't usually end up becoming totalitarian dictators. If you are wishing to advocate equal rights for all fine. A corporation is not part of 'all', they are not real, they do not breathe, they do not eat. they do not bleed or have children. Its an abstract construct concocted by humans. Thus human have the final say about what the privileges and responsibilities we foist upon such entities. If you wish to advocate that a non-being has the same level of 'being-ness' as you do, feel free. I choose to think otherwise.
Re:Anyone who opposes the GPL is a corporate whore (Score:5, Insightful)
Think of all the rotten things that businesses have done to consumers in the name of profit. All the dangerous chemicals they's been feeding us in our food and giving us as "medicine"... All the coverups to try and keep critical life saving information from reaching the public. If there is one thing that we all should be aware of as human beings, it's that we should put our fellow man far above profit and personal gain. If you can't do that, you have failed as a human being.
Re:Anyone who opposes the GPL is a corporate whore (Score:2)
Who modded THE parent quoted above up as insightful? If corporations were accountable to their customers, there COULD be modern society, goods and services as well as ethical and moral reponsibility to the consumer. It's all about balancing priorities. Profit is well below human life in the gran scheme of things. I'm sorry, but if a corporation is going to have that much influence ove
Actually there is one (Score:2)
Actually there is a category for these stories. It's called Caldera. Let's not forget that that is who this really is. Much as I never really liked the Santa Cruz Operation, they are not the bloodsuckers that we're talking about here. It's Caldera. I wonder what name they're planning to change to next after they drag this one through the mud?
Most of the stories have been properly filed under that heading. This one actually makes as much sense as it is as there, however, since it's actually about a stateme