Ptraci writes "Over at Groklaw they have been doing some digging and have found evidence that old SCO and Caldera did in fact contribute those files that they now want to charge us for."
Re:Their contribution...
by
finkployd
·
· Score: 0, Redundant
Which is why expert witnesses exist. The average Judge and jury doesn't understand how MOST evidence works.
Finkployd
You Bastards!
by
Anonymous Coward
·
· Score: 0, Redundant
You Bastards.. you've killed Kenny !
oops
You Bastards, you've slashdotted Groklaw !
All I get is:
Warning: mysql_connect(): Can't connect to MySQL server on 'mysql2.ibiblio.org' (110) in/public/private/groklaw/system/databases/mysql.cla ss.php on line 108
Cannnot connect to DB server
My concern with all of this crap, is the fact that someone hasn't forced SCO to shut the hell up. It reminds me of the Bully in grade school. He would consistantly beat up on kids every day. Some even to the point of actual damage, and he was NEVER suspended. Never. Ever. I think that is what needs to be really focused on. Not so much as "When will all of this madness end?", but rather "How can we prevent this from ever getting this far, if history repeats itself?"
Also, from the article: "[Darl]I've been pounding the table here for a year or so saying there's no free lunch, and there is going to be a day of reckoning for every company that thinks they are going to try and sell a free model."
What is with this messianic attitude? Perhaps what Darl does not realize is that folks contribute to Linux and other open source projects through a variety of reasons. Notably, some contributions to open source have happened via tax-payer funded projects from a variety of nations throughout the world. Other contributions are made from the generous and charitable contributions of others who simply want to make a difference. Darl wants to exploit those contributions and leverage his band of merry lawyers to "liberate" Linux from the rest of us. Only his liberation is not for anything other than selfish desires (like any criminal who sees nothing wrong with theft) with no respect to the common good.
Mod parent up: it's the full text.
by
LouisvilleDebugger
·
· Score: 0, Redundant
Mod parent up: it's the full text.
Re:Groklaw is biased against SCO already
by
slipgun
·
· Score: 0, Redundant
Cut'n'paste of the article
by
GavK
·
· Score: 0, Redundant
Groklaw Takes A Closer Look at the ABI Files, by Frank Sorenson et al Friday, January 30 2004 @ 11:53 PM EST This article is the result of a group research project, compiled and primarily written by Frank Sorenson with Pamela Jones. The special footnoted article explaining some of the terms for nonprogrammers was written by Nick Richards. The research group was primarily composed of Frank Sorenson, Dr. Stupid, Harlan Wilkerson, Rand McNatt, Roland Buresund, and Pamela Jones, all of whom contributed both research and writing, with input from some Linux kernel contributors. Everyone worked on editing, including an invited group of Groklaw regulars. However, Frank carried the load more than anyone else, so his name is on the finished article.
We are now publishing the article and welcome Groklaw readers' further contributions, corrections, improvements, and comments. This is an ongoing project. This article is the first in a series where we'll discuss the System V UNIX ABI, or Application Binary Interface. We approached the research as, What if Linus Torvalds had not already claimed paternity of most of the header files? Then what?
The article will first explain what the ABI is and what it does, then discuss whether the code was released under the GPL and if so whether management at SCO knew and approved, and finally show how the Linux files that pertain to this do not appear to be infringing files that SCO can claim.
For those who are not programmers, such as myself, there is a footnoted section to explain in greater detail and in plain English what ABIs and APIs and shared libraries are and how they work. If you read it first, it will clarify the terminology for you and you will be able to follow the thread in the article more easily. At least, it helped me tremendously.
I think you will see from this article alone that if SCO is planning to sue anyone over the ABI files, unless there are facts we haven't unearthed, they seem to be leaning on a rickety bamboo reed.
GROKLAW TAKES A CLOSER LOOK AT THE ABI FILES ~by Frank Sorenson et al
Back in January 2003, word leaked out that SCO was planning to charge Linux users for "System V Intellectual Property" in Linux. SCO created a new business division called SCOSource to come up with new ways to make money from this "intellectual property". The original SCOSource Presentation (PowerPoint version) talks of licensing SCO's shared UNIX Libraries from OpenServer and UnixWare for use in Linux.
A Little Background: What Are ABI Files? [1]
As background information, shared libraries are files containing information to be loaded when an application is run. They usually implement common routines, and their inclusion simplifies programming, reduces file size, and standardizes interfaces. A simple example of this would be the "copy file" and "move file" commands: both commands check file permissions and manipulate the file system. When applications have a great deal of functionality in common, this functionality is often placed into shared libraries.
Shared libraries are architecture, operating-system, and version specific. Executables for different systems follow various standard formats, such as a.out, ELF, and COFF. To load an application, the system must do several things: the system interprets the format of the executable (or binary), loads any shared libraries referenced, and begins executing the code found in the binary.
If the executable is in a different format from those the system supports, or if the library files are for the wrong architecture or operating system version, the binary normally will not run. In 1991, Intel announced the availability of the iBCS-2 (Intel Binary Compatibility Specification), a specification designed by Intel, SCO, and Unix System Laboratories (USL) to enable binary compatibility and migration capabilities between systems. SCO's Tim Ruckle said this to encourage support:
'The goal of 'shrink wrap' software for the open systems marketplace will not be
--
Gav
"There's no such thing as data that can't be manipulated"
Slashdot Mirror
It's good to see that the slashdot effect still happens early saturday morning!
Now, if you'll excuse me, I have backups to corrupt.
combination hooka and Coffee-maker!
Buy now and we will only sue you once!!
all your linux are belong to SCO!!
move all *nix, for great profits!
Which is why expert witnesses exist. The average Judge and jury doesn't understand how MOST evidence works.
Finkployd
You Bastards .. you've killed Kenny !
/public/private/groklaw/system/databases/mysql.cla ss.php on line 108
Cannnot connect to DB server
oops
You Bastards, you've slashdotted Groklaw !
All I get is:
Warning: mysql_connect(): Can't connect to MySQL server on 'mysql2.ibiblio.org' (110) in
My concern with all of this crap, is the fact that someone hasn't forced SCO to shut the hell up. It reminds me of the Bully in grade school. He would consistantly beat up on kids every day. Some even to the point of actual damage, and he was NEVER suspended. Never. Ever. I think that is what needs to be really focused on. Not so much as "When will all of this madness end?", but rather "How can we prevent this from ever getting this far, if history repeats itself?" Also, from the article: "[Darl]I've been pounding the table here for a year or so saying there's no free lunch, and there is going to be a day of reckoning for every company that thinks they are going to try and sell a free model." What is with this messianic attitude? Perhaps what Darl does not realize is that folks contribute to Linux and other open source projects through a variety of reasons. Notably, some contributions to open source have happened via tax-payer funded projects from a variety of nations throughout the world. Other contributions are made from the generous and charitable contributions of others who simply want to make a difference. Darl wants to exploit those contributions and leverage his band of merry lawyers to "liberate" Linux from the rest of us. Only his liberation is not for anything other than selfish desires (like any criminal who sees nothing wrong with theft) with no respect to the common good.
Mod parent up: it's the full text.
As your post has just demonstrated.
SpamNet - a spam blocker that really works
Groklaw Takes A Closer Look at the ABI Files, by Frank Sorenson et al Friday, January 30 2004 @ 11:53 PM EST
This article is the result of a group research project, compiled and primarily written by Frank Sorenson with Pamela Jones. The special footnoted article explaining some of the terms for nonprogrammers was written by Nick Richards. The research group was primarily composed of Frank Sorenson, Dr. Stupid, Harlan Wilkerson, Rand McNatt, Roland Buresund, and Pamela Jones, all of whom contributed both research and writing, with input from some Linux kernel contributors. Everyone worked on editing, including an invited group of Groklaw regulars. However, Frank carried the load more than anyone else, so his name is on the finished article.
We are now publishing the article and welcome Groklaw readers' further contributions, corrections, improvements, and comments. This is an ongoing project. This article is the first in a series where we'll discuss the System V UNIX ABI, or Application Binary Interface. We approached the research as, What if Linus Torvalds had not already claimed paternity of most of the header files? Then what?
The article will first explain what the ABI is and what it does, then discuss whether the code was released under the GPL and if so whether management at SCO knew and approved, and finally show how the Linux files that pertain to this do not appear to be infringing files that SCO can claim.
For those who are not programmers, such as myself, there is a footnoted section to explain in greater detail and in plain English what ABIs and APIs and shared libraries are and how they work. If you read it first, it will clarify the terminology for you and you will be able to follow the thread in the article more easily. At least, it helped me tremendously.
I think you will see from this article alone that if SCO is planning to sue anyone over the ABI files, unless there are facts we haven't unearthed, they seem to be leaning on a rickety bamboo reed.
GROKLAW TAKES A CLOSER LOOK AT THE ABI FILES
~by Frank Sorenson et al
Back in January 2003, word leaked out that SCO was planning to charge Linux users for "System V Intellectual Property" in Linux. SCO created a new business division called SCOSource to come up with new ways to make money from this "intellectual property". The original SCOSource Presentation (PowerPoint version) talks of licensing SCO's shared UNIX Libraries from OpenServer and UnixWare for use in Linux.
A Little Background: What Are ABI Files? [1]
As background information, shared libraries are files containing information to be loaded when an application is run. They usually implement common routines, and their inclusion simplifies programming, reduces file size, and standardizes interfaces. A simple example of this would be the "copy file" and "move file" commands: both commands check file permissions and manipulate the file system. When applications have a great deal of functionality in common, this functionality is often placed into shared libraries.
Shared libraries are architecture, operating-system, and version specific. Executables for different systems follow various standard formats, such as a.out, ELF, and COFF. To load an application, the system must do several things: the system interprets the format of the executable (or binary), loads any shared libraries referenced, and begins executing the code found in the binary.
If the executable is in a different format from those the system supports, or if the library files are for the wrong architecture or operating system version, the binary normally will not run. In 1991, Intel announced the availability of the iBCS-2 (Intel Binary Compatibility Specification), a specification designed by Intel, SCO, and Unix System Laboratories (USL) to enable binary compatibility and migration capabilities between systems. SCO's Tim Ruckle said this to encourage support:
'The goal of 'shrink wrap' software for the open systems marketplace will not be
Gav
"There's no such thing as data that can't be manipulated"