Slashdot Mirror
Back To SCO
VikingBrad writes "The Sydney Morning Herald has an article on Dr Warwick Toomey of The Unix Heritage Society claiming that SCO may not know the origin of code in System V, including claims that there is a lot of BSD software in Sys V."
Alex writes "I wondered where the 100k+ lines of copied code
in the linux kernel would come from in comparison
to the SCO Unixware stuff. Then a thought popped
up in my head: what if they just compared linewise?
All those empty lines in the code would have the
same content. But how many empty lines are in the
Linux Kernel Code? This small shell script counts them for you:
emptylines=0; function parse_dir () { for file in $1/*; do if [ -d "$file" ]; then parse_dir $file; else while read line; do if [ "$line" = "" ]; then emptylines=$[$emptylines+1]; echo $emptylines; fi; done
Kernel 2.4.22, yet cleaned of the code which SCO
claimed was stolen, has still 733140 empty lines, probably copied and pasted by the bad, bad kernel developers from the good, good SCO guys..."
Is anyone or their linux-related company a member of any wire associations? Some anti-FUD articles really need to be filed as a press release, specifically mentioning SCOX.
Right now, if you go to Yahoo, and search for news on SCOX, you only find their press releases. We need to get some of our opinions out there so they'll show as news on SCO!
Can anyone help? Doesn't this seem like an important thing to do??
Mike
I wonder if SCO intends all this publicity and open source community reply to do their work for them. Meaning: They dont know things like the lineage of certain code, so some of what they say is to get people to dig for them. Think of how much it would cost to figure some of these things out if you were paying people to do so.
SCO should offer, to those who purchase their license, this guarantee of indemnity:
SCO guarantees that all IP associated with the SCO license is the sole, undisputed property of SCO. Should said property be shown to be actual property of a third party, SCO will pay all legal fees, rememdies and any other fees associated with any dispute arising from the third party.
Thus, SCO would show that they are certain they haven't infringed on GPL'd code (or any other party's code).
If SCO is unwilling to make such a guarantee of indemnity, it shows that they don't believe their own case.
Reading Slashdot is ruining my spelling and grammar.
"What comes of litigation? Poverty and degradation to any community that will encourage it. Will it build cities, open farms, build railroads, erect telegraph lines and improve a country? It will not; but it will bring any community to ruin." -Brigham Young, JD 11:259.
The following has been cut and pasted from the InfoWorld article "Torvalds to SCO: Negotiate What?"
--- cut here ---
Open letter to Darl McBride -- please grow up.
Dear Darl,
Thank you so much for your letter.
We are happy that you agree that customers need to know that Open Source is legal and stable, and we heartily agree with that sentence of your letter. The others don't seem to make as much sense, but we find the dialogue refreshing.
However, we have to sadly decline taking business model advice from a company that seems to have squandered all its money (that it made off a Linux IPO, I might add, since there's a nice bit of irony there), and now seems to play the US legal system as a lottery. We in the Open Source group continue to believe in technology as a way of driving customer interest and demand.
Also, we find your references to a negotiating table somewhat confusing, since there doesn't seem to be anything to negotiate about. SCO has yet to show any infringing IP in the Open Source domain, but we wait with bated breath for when you will actually care to inform us about what you are blathering about.
All of our source code is out in the open, and we welcome you point to any particular piece you might disagree with.
Until then, please accept our gratitude for your submission,
Yours truly,
Linus Torvalds
Back in the 1980's, I was just one of many people who noticed that AT&T claimed to have a copyright on blank lines. You can see one of these claims at http://web.42.net/true.html. Google for /bin/true and you'll find more.
/bin/true went through many versions, all of which contained only blank lines and a copyright notice.
/bin/true on several newsgroups as responses to discussions, pointing out that I had posted a copyrighted AT&T program in its entirety, and challenging AT&T to prosecute me. For some mysterious reason, I never heard from them.
/bin/false, which contained only the command "exit 255", so if you do that in any script, you are also inviolation of AT&T/SCO's claimed copyright.
/bin/true to be part of the IP that they inherited from AT&T. This is presumably the basis of the majority of their claim that there are a million lines of stolen SCO code in linux. When you add in all the lines that contain only /*, */ and //, you can easily get to a million lines.
This is the good old "true" program, which on Sys/V was an empty shell script. It works; it does nothing, and then since there were no errors, it exist with a zero status. Some drone at AT&T obviosly wrote a script to run through all their scripts and add an AT&T copyright notice. This also added two blank lines (only one in some later versions), leading to the observation that AT&T really was claiming to own the rights to blank lines.
One fun thing is that their copyrighted version of
Another fun thing that I did was to post the code for
There was also an AT&T copyright notice in
Anyway, it does seem that the SCO gang considers
It could be fun if they actually made the mistake of pressing this claim in court.
Those who do study history are doomed to stand helplessly by while everyone else repeats it.