


Linus Speaks Out, Calls SCO 'Cornered Rat' 598
dexterpexter writes "In an interview with Business Week, Linux founder and guardian Linus Torvalds had, in his usual brand of blunt humor, the following to say about SCO: 'They're a cornered rat, and quite frankly, I think they have rabies to boot. I'd rather not get too close to them,' and 'There are literally several levels of SCO being wrong. And even if we were to live in that alternate universe where SCO would be right, they'd still be wrong.'" In the same issue, there's also an interview with Darl McBride where he admits that the company was failing and the Linux-related lawsuits were a last-ditch effort to prevent bankruptcy.
SCO (Score:2, Insightful)
"...last ditch effort..." (Score:5, Insightful)
Surprised by Linus (Score:5, Insightful)
In the end, I think we'll all look back on this as the time where Linux went from sort of a fringe software in the minds of a lot of people to a mainstream player, where corporations learned they shouldn't mess with the OSS community and when the idea of open-source really started to make people ask "Why *am* I paying for this software?"
After all, that which doesn't kill us, etc. etc.
Not a troll, but.... (Score:0, Insightful)
I find the attention/flames that everybody is giving to SCO highly surprising, as a result it is hard for bystanders to differentiate between the opponents. It would be much more mature of Linus and Co to either ignore the whole matter or respond professionally, instead of playing the same game.
What about the open source community? (Score:5, Insightful)
While it may be humorous to some of the immature individuals on this site, a worm to DDoS SCO is a terrible blunder. It just strengthens SCO's arguments that the open source community is made up of troublemakers that need to be stopped.
Never forget (Score:1, Insightful)
The lawsuit and linux "licensing" program caused SCO to start making a profit for the first time ever because as soon as they did so, they recieved an absolutely huge monetary donation from Microsoft. And it was a donation, not a "license" Microsoft has no use for a license even if one were legally required of them. It was never anything other than a donation, and this is practically the only reason SCO has survived to the new year. This is the reason SCO can go on.
No, Microsoft isn't standing behind the scenes pulling SCO's strings. They don't have to.
When all is said and done (Score:5, Insightful)
Other people have said it and I agree with it... those attempted extortion, excuse me, licensing letters they sent out are should be pursued as federal mail fraud, and the SEC should take a long hard look at Mr. McBride and his lawyers, and how they're playing their own company's stock.
Re:SCO (Score:5, Insightful)
Editor Spin (Score:3, Insightful)
Way to make it sound very sordid. The company was falling towards bankruptcy, yes. It was a last ditch effort, yes. But.....oh.....
Love this quote.... (Score:5, Insightful)
I'm sure everyone would like their money back from the tech-bust, but there's this little thing called reality. Unless you're Darl, of course.
By the way, in this P.R. war... (Score:3, Insightful)
Well, and in the financial sector, which seems to cling to the stubborn belief that there might be something to their tactics and/or allegations.
It's quite likely that "truth will out", as they say, but if public opinion has any bearing on the outcome of this struggle IBM and Linus need to get better visibility in the more widely consumed (and moronic) news channels. I haven't seen anything but negativeish stuff there, but it's what gets out to the masses.
I love this quote... (Score:5, Insightful)
You gotta love that guy's way of making a point.
20% success rate eh? (Score:4, Insightful)
: Have you had direct talks with customers yet?
A: Very carefully over the last quarter, instead of sending out mass invoices, we stepped very carefully and really had a lot of direct one-on-one meetings with 15 or so companies. In the process of doing that, we learned a lot. We listened. We talked. And we went back and forth. About 20% of those companies signed licenses with us.
Q: Can you name any of them?
A: We have taken the stance not to,
let's see 20% of 15, that's what.. ~2. so let's see, Microsoft and Sun perhaps?
What I think is great (Score:5, Insightful)
The linux community, meanwhile, has to be absolutely perfect and saintlike and have not a single user do anything that could be interpreted as unethical, or they get blasted as scary anarchists.
This is even more funny when you consider SCO is a singular organization which can enforce ethical standards, whereas "the linux community" is an open ended, uncontrollable group of people that basically means everyone who downloads a certain program.
We need a media that knows how to do more than reprint press releases.
Re:When all is said and done (Score:5, Insightful)
Granted, if I get busted with a loose joint and I have another in my pocket I'd probably be busted with intent to sell. But lawyers don't seem to be comfortable making those quantum assumptions about fellow lawyers.
Re:SCO (Score:5, Insightful)
more interesting is what will happen to the companies that paid the licensing fees. if they decide they've been ripped off (well, that's only a matter of time) they're going to have a bejesus of a time recouping their costs. there will definitely be civil action. that's a given. but will there be criminal action to follow suit?
you can't sell the brooklyn bridge to tourists, after all. they put you in jail for that.
Re:What about the open source community? (Score:1, Insightful)
No, it makes the virus author look like the rat.
a worm to DDoS SCO is a terrible blunder.
Unless you have firsthand knowledge that it was written by a member of the open source community, how can you call it a "blunder"? That's like saying "Hey, I know your wife got hit by a drunk driver while you were at work, but it was a terrible blunder for you to be drinking and driving."
Again, unless you have proof that this was created by someone in the open source community, shut the fuck up, there are grown-ups having a conversation here.
Google (Score:5, Insightful)
"Q: There has been a rumor in Silicon Valley that you're going to sue Google. A: Yeah, Google gets brought up a lot. They're high-profile, and they're one of the largest users of Linux. They have nearly 10,000 boxes, from what we can tell. They're a poster child. I think what's interesting about them is they have been able to develop a low-cost operating model because of Linux. If your model is going to hold up, you better make sure you don't have any infringing code in there. Otherwise, you need to adjust your financials based on how much you pay for your servers. "
The emphasis is mine. This is SCO's trump card for going after google. You see, any lawsuits based on IP would look VERY bad for potential investors when google wants to go public. I mean, licensing all of their 10k boxes would cost $6,990,000, but any amount looks bad to shareholders, especially since if SCO were to win (yeah yeah I know) they could basically say " we don't care how much you offer, we're not letting you use our IP" and google would be in a tight spot, and probably have to spend a LOT more than 7 mil to fix it.
In a way, SCO has already won (Score:3, Insightful)
It's sorta like arguing if a speech I wrote violates the Kings laws, rather than asking if the king should have the right to restrict peoples speech at all to begin with.
Re:Surprised by Linus (Score:5, Insightful)
Re:20% success rate eh? (Score:4, Insightful)
15 X
But you probably already knew that. That means SCO has enough cash to operate...let's see here...
$699 X 3 = $2,097 - Boies' legal bills = -A Bajillion Dollars
Plus or minus a few bucks for the valet parking guy at their favorite bistro.
SCO is done. IBM simply has to take a print out of this article, hand it to their trial judge, and watch Darl start crying...
IBM's "We don't talk to the media about litigation." response is much better than SCO's "Please, believe us, help, we're desperate, I'll say something stupid so you'll print the interview, just god, please, believe what we have to say..."
Re:Surprised by Linus (Score:3, Insightful)
Re:Surprised by Linus (Score:2, Insightful)
Only delays the inevidible.
Re:Surprised by Linus (Score:5, Insightful)
The corporate community fights legal battles, appeals to the law for redress.
The OSS community fights PR battles, and appeals to the world, and indirectly, the customer base for redress.
Think about the OSS projects that have had code ripped off - they let the company know that there may be misuse of Open Source code. If they get an unfavorable response, the make an announcement, they add the company to their "blacklist", and suddenly a very large group of consumers has been activated against them.
The whole OSS movement operates within the Social Conscience. It's the fact that there exists a social conscience in this world that it works in the first place. It's the companies without a social conscience that cause problems. It's the companies with a social conscience that benefit from the OSS model.
On a side note, I'm just amazed by IBM's social conscience. It's plain how few companies there are that recognize opportunities to invest in community for the benefit of the company and the community.
Re:What about the open source community? (Score:4, Insightful)
The world is quite used to their Windows machines getting infected. This time is exactly the same.
Who's SCO, anyway? Nobody anybody is interested in.
Don't worry about it; it's a WINDOWS virus, not a Linux virus, THAT'S the thing to point out.
Re:What about the open source community? (Score:5, Insightful)
The worm's real goal is to install invisible keystroke monitors in an attempt to gather passwords and bank account numbers of infected users. With all the noise coming from those infected PC's going to SCO, a few packets going elsewhere slip through very easily if you're not looking for it.
It's classic prestidigitation. Make a big show with one hand while the other does the dirty work.
Re:What about the open source community? (Score:3, Insightful)
History is full of examples of people creating or allowing disasters to happen, then blaming some enemy for them.
Re:no, it is so wrong. (Score:4, Insightful)
Since the who fiaSCO is about the kernel, I'd say that leaving out the GNU is quite appropriate. And Linus did do the first work on it.
Re:In a way, SCO has already won (Score:2, Insightful)
SCO has sued Novell over who owns the copyrights to the UNIX source code. Reading of the contracts points towards Novell, but it is ultimately up to a court to decide (IANAL).
SCO has far from won. If anything, it looks like SCO is going to have to brush up on the Chewbacca defense prior to Feb. 6.
Do take note of the fact that even if Linux is violation of SCO's copyrights (highly unlikely), SCO has a responsibility to mitigate damages. Despite repeated, ongoing requests from the Linux community to work with them to identify any questionable code, SCO has failed to do so on the arguments that it would dilute the value of their product. Even if they win (even more unlikely), they will not be able to claim damages going forward from the point they identified the problem since they did not act in good faith to minimize the harm from that infringement.
Lastly, despite SCO's posturing, end users cannot be held liable for violations of others! Period. The best they can do is get damages from the developer who copied code from SysV into Linux. SCO has never claimed that IBM copied code verbatim into Linux (hence, no copyright infringement suit). Since they have not done that, the best they can do is pick on a developer (who rightly will deserve the flogging).
SCO is trying to get users to pay for a license that basically says SCO promises not to sue them. Heck, I could sell you a perpetual license that permitted you unlimited access to water and air for as long as you remained on the surface of the planet in exchange for my promise that I would try to breathe the same air as you in the same space. You'd be an idiot if you choose to purchase such a license from me, but you are within your right to do so (licenses are NOT contacts). SCO's "Linux Property License" is about as ridiculous.
Re:But is the recognition good or bad? (Score:3, Insightful)
Yeah, but those arguments aren't too hard to deflate if you have a half-dozen brain cells. After all, Timothy McVeigh blew up the Murrah building in Oklahoma city and he was a Christian, but I hardly think that makes the rest of the Christian community responible for his actions.
Re:Lies, damn lies (Score:2, Insightful)
I guess, he says exactly what he said last summer when presented with the same arguments, which is that it is just an example of a copyright infringement in Linux code, but not an example of SCO's copyrights infringement.
Tainted Code Removal? (Score:2, Insightful)
From the article:
Emphasis mine. Uhh.. how about when you prove to us that it, in fact, exists by SHOWING US WHERE THE FUCK IT IS!
Re:it's not the open source community.... (Score:3, Insightful)
Note to aforementioned putz:
Why do you think SCO has been using inflammatory language? You're being played. Buying a bumper sticker from Thinkgeek [thinkgeek.com] doesn't make you part of the Linux community or anything else worthwhile. If you think you're coding skills are so hot, get out of your mom's basement and try playing with the big boys for a while. Go to Source Forge [sourceforge.net], pick a project that you can help and do something worthwhile for a change.
Just my humble opinion.
Re:But is the recognition good or bad? (Score:3, Insightful)
The guy who shot Reagan did it to impress Jodie Foster, yet somehow she didn't get the blame. In the unlikely event I get into a conversation about this email virus I'll have to point that out.
Here's my letter to the editor sent to CNN.com (Score:2, Insightful)
http://www.cnn.com/2004/TECH/internet/01/27/myd
The author, Jeordan Legon, stated that 'virus experts' suggested that a 'Linux fan' was responsible for the creation of the myDoom worm. The title of the article clearly implies both that a 'linux war' exists, and that the worm is somehow a direct weapon of that war. Yet the only attributed quote to back up this assertion is from Chris Belthoff, who says, "The MyDoom worm takes the Linux Wars to a new intensity" and "It appears that the author of MyDoom may have taken the war of words from the courtrooms and Internet message boards to a new level by unleashing this worm which attacks SCO's Web site."
Unless Mr. Belthoff is a witness to the crime, or has other direct knowledge of the criminal and his/her activities, his 'expert opinion' on this matter is no more informative than what any random person taken off the street might have to say - which is. not informative at all.
No one knows who wrote the worm, what his or her intentions were, nor what relationship - if any - the worm author has with Linux or the Open Source community. Of course, Mr. Legon doesn't assert such a relationship in his article, he only implies it, leaving factual statements about the worm and how it works several paragraphs down from the top.
Mr Legon, may I ask you: Just what is the job of a reporter? Is it to report facts or spread gossip in the form of irrelevant and nonfactual 'expert opinion'? Because, if your job is to report facts, than may I say that in my 'non-expert opinion' you badly missed the mark with this article.
Thank You,
J. Maynard Gelinas
Re:I'm glad he was honest at least (Score:3, Insightful)
Right, so, if we abolish IP, what's to prevent Microsoft from taking all sorts of open-source software, throwing it into Windows, and continuing to make money off Windows (sure, no more copyrights, but they'll find a way!)? We can redistribute Windows all we want, but we'll never see the code.
Sorry, but IP laws are the only thing that allows the GPL to be enforced. Personally, I don't want to make money off software - I'd rather have people just use it - but I'd be pretty fucking pissed if someone took my work and passed it off as their own, because I didn't have copyright protection for it.
Re:But is the recognition good or bad? (Score:5, Insightful)
Face it: every group of people has people in them that will do something stupid. They are called extremists and they are the real threat, not any one group. RMS himself is extreme enough to be a threat to his own philosophy, but thankfully not extreme enough to write a stupid virus like that luser.
Re:Litigious Bastards! (Score:3, Insightful)
Why?
SCO has shown that it is willing to use every tool at their disposal (bogus lawsuits, attacking public image to damage stock prices, etc). They are acting decidedly unethically.
Google has a very simple, easy way to impact SCO -- simply make it difficult for people using their service to access SCO.
As far as morality goes, SCO is pretty much in the wrong. I mean, if you were supposed to be in a bare-knuckle fight, and someone pulled out a sword and started going at you, and you had a knife, wouldn't you consider it justified to use that?
Google isn't the government. Ultimately, I don't consider them bound by guarantees of non-censorship -- the only thing I demand from them is search results that give me what I'm looking for. They do a pretty good job of that, despite a sizeable industry that does nothing but try to subvert their searches 24/7. If SCO's using dirty tricks on them, and in return they want to stop playing ball with SCO -- heck, let 'em. If you decide that you want to try to terrorize the New York Times, don't be surprised if the NYT decides to stop running positive articles about you.
Re:I'm glad he was honest at least (Score:3, Insightful)
What incentive do I have to do it, then? Frankly, knowing that people are benefitting from my code isn't enough to make me want to spend time writing it, unless I'm getting something else in return. Since I am a (employed) scientist, not a professional programmer, I'm happy to earn recognition simply by authorship credit rather than by money. Alternately, if I was some anonymous cog in Microsoft, I'd be getting plenty of money. But I won't accept neither, and I suspect very few programmers will.
Hell, even the BSD licenses require that the copyright notice be maintained; all of the programmers I'm aware of who release code under this type of license are very concerned with getting proper recognition for it. Without copyright, even the BSD licenses wouldn't be enforceable.
My point is, there's a reason almost nobody releases code immediately into the public domain. It's an all-around bad deal for programmers.
Re:"Operating systems shouldn't be free" (Score:3, Insightful)
Darl's "blanket statement" is patently false. Just go ask IBM for your free copy and source code for MVS, OS/390, VM, OS/400, AIX, OS/2, (see note) etc. and you'll find out that IBM only believes in free/open source OSes for commodity hardware as a alternative to Microsoft. SCO had the bad luck to get caught in the crossfire and to have an idiot like Darl running the place and picking the wrong side in the fight.
I appreciate what IBM is doing to support Linux and open source but I don't for a minute believe they are doing it either out of the goodness of the heart or because they truly believe in open source. IBM is out to make money and selling support for Linux fits their service business model and undercuts Microsoft. Likewise, I'll believe that IBM believes in open source the day they GPL the OSes for their big iron. They're doing good things for Linux and open source but they're doing them to make money (nothing wrong with that either) and they're protecting their closed source products at the same time.
Note: its been since the early '80s that I dealt with IBM on anything other than a PC so I may not have all of their OSes listed correctly but you get the idea.
Re:I'm glad he was honest at least (Score:2, Insightful)
Then don't. If suppressing your own ideas makes you feel better, by all means. There are plenty of people in this world who do things just because they like to. I believe they do better work because of that. If all you're looking for is rocognition, I would have doubts about the quality of your work.
"Without copyright, even the BSD licenses wouldn't be enforceable."
Without copyright, the BSD wouldn't exist. Nobody would need it.
"My point is, there's a reason almost nobody releases code immediately into the public domain. It's an all-around bad deal for programmers."
Of course it's bad under the current enviroment we live in. Right now, we need the money, because the wrong people control the resources that would normally belong to everyone.
Re:The question is... (Score:4, Insightful)
To maintain the maximum amount of portability, don't say /bin/bash. Say /bin/sh instead.
Also, don't assume true is located at /bin/true. On some systems in may be located in /usr/bin/true, or in some cases, somewhere else entirely. You'll probably be better off using ':'
Now we have:
#!/bin/shwhile
do
wget -r -l10 http://www.sco.com -O
done
exit 0; # really unnecessary
Re:What about the open source community? (Score:3, Insightful)
I might be wrong, but somehow I would be willing to bet their best programmers left LONG ago.
Re:The question is... (Score:3, Insightful)
SCO deserves what they are getting (Score:2, Insightful)
Differences in dealing with the OSS world (Score:5, Insightful)
IBM doesn't necessarily (well, as a company) have a social conscience. IBM, however, is smart enough to realize that dealing with the OSS community can be phenomenally profitable -- that acting as if it *does* have one is marvelously beneficial. There are, very many differences in dealing with OSS versus traditional software. Here are some of my guesses as to what to do differently:
* A feeling of good will matters. Goodwill only matters normally as far as wining and dining a negotiator to try and get him to sell out his company a little. The OSS community is *extremely* sensitive to companies, treating them like people, whom are either friendly or unfriendly to OSS. A cohesive positive-sounding OSS company policy does a tremendous amount to keep a company in the good graces of the OSS folks. Press releases about how said company uses OSS, and thinks it's a good idea. Periodically releasing some code as OSS is a nice icing. (Take OpenAFS -- IBM only benefits from having that around, and it generates lots of good will.)
* Legal issues need to be minimized. Dealing with a company, you have lawyers who can hammer things out. The OSS community likes things pretty simple and clear.
* The OSS community doesn't demand masses of money. It's appreciated, like IBM's ongoing investment in open source development (which was probably done for strategic reasons, improving software that they needed worked on, as much as PR value), but a positive attitude toward OSS can count more than donating masses of money toward OSS.
* You don't need to worry about getting screwed over legally, in general. OSS folks are not generally out to shaft people over licenses. Legally, things are simple and nice.
* The OSS community can jump to conclusions quickly, and needs to be spoken to publically when misconceptions start going around. You have a lot of people with individual opinions. If a major Linux Ethernet player, like Donald Becker, writes a letter to, LKML saying that some chipset made by a company is lousy, said company needs an official, public response quickly. If there's a Slashdot story out about how your company is discontinuing production of Mindstorms (and the story is wrong), you should probably have a press release out within the day.
* The OSS community values specs. Take a page from Matrox, who decided what they could and couldn't release (couldn't release source to some on-card microcode, which had to be distributed in binary, but *could* release specs to much of the rest of the card.) Matrox's older G200-G450 series are still among the best supported of video cards under Linux and X.
* Maintain an official presence on relevant public forums, since so much OSS-related stuff takes place in the open. You might just have a mail filter that drops any email on major mailing lists containing your company name or product names into your PR department's inbox.
* Little of the OSS community accepts legal liability. This should be noted -- however, problems like illegal code copying do not seem to be prevalant, simply because of the high visibility of doing so. There are times when you may want indemnification of code you use -- the OSS community doesn't do that.
* Giving gifts can be inexpensive and valuable. In healthy Linux tradition, if someone runs out and implements a driver for your chipset, send 'em something nice in the mail. In rich Linux tradition, a case of beer seems to work well. It also costs you about a ten thousandth of what it would to implement the thing commercially, and ensures future good will. For driver writers, it's frequently a really, really good idea to just send along a few other products that you make (ones without drivers). This encourages people who have already demonstrated willingness to produce, wi
Re:SCO is betting the bank - be worried?? (Score:3, Insightful)
Of course the code will be replaced. But that would be proof that there was a copyright violation, which would help their case. SCO can then work on figuring out who actually violated their copyright and go sue them.
SCO is not acting like anybody who thinks they actually have a copyright case. The fact that they are not saying where the code is damages their case, because you have to demonstrate an interest in mitigating the damages. They are acting exactly like somebody who is being paid to spread FUD about Linux. This either means they are being paid by Microsoft, or (more likely to me) they are trying to make investors think they are being paid by Microsoft.
Re:This is even better! (Score:2, Insightful)