IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New SCO's other shoe drops: SCO source code found in Linux
[link|http://news.com.com/2100-1016_3-999371.html?tag=fd_lede1_hed}They're not saying which lines, though|http://news.com.com/...ich lines, though].

Lines from Unix's source code have been copied into the heart of Linux, sometimes exactly and sometimes in a modified form designed to disguise their origin, SCO Group Chief Executive Darl McBride said Thursday.

McBride's accusation cuts to the heart of the open-source movement's legal and philosophical underpinnings.

As part of its billion-dollar lawsuit against IBM, which charges that Big Blue misappropriated SCO's Unix trade secrets and built them into Linux, SCO hired several consultants to compare the source codes of the two operating systems.

"We're finding...cases where there is line-by-line code in the Linux kernel that is matching up to our UnixWare code," McBride said in an interview. In addition, he said, "We're finding code that looks likes it's been obfuscated to make it look like it wasn't UnixWare code--but it was."


I like this part:
"There is not an intellectual property policeman sitting in at the check-in counter saying this is OK, this is not OK. It is a free-for-all," McBride said. "At the end of the day, there's not a basis for making sure code is clean when it goes in there."

There's a simpler solution to the issue, Perens said. "They should show us what code they have problems with. We'll take a look at it or we'll just replace it. Keeping us in the dark is just silly," he said.

An impassioned McBride, however, said there's a matter of principle at stake. SCO Group can't just let its intellectual property be used willy-nilly.

"This is not about 10 lines of code, it's about 20 years of extremely valuable intellectual property we're trying to protect...Am I supposed to lie down and not say anything about it?" McBride said. "There's a certain point here where you stand up for what's right and let the chips fall where they will."
Translated: "No, we'd rather sue everyone, because we need the money." :-P
Regards,

-scott anderson

"Welcome to Rivendell, Mr. Anderson..."
New Simple solution
Linus may have only recently started using a version control system, but someone can produce a record of who checked in every line of code in the kernel. SCO need simply point out the offending sections, identify the people who checked it in, and pursue them for infringement. Then the kernel maintainers can strip those developers' check-in rights, and solicit re-writes of the affected portions.
===

Implicitly condoning stupidity since 2001.
New Wouldn't it be funny...
To find out that the Developer that submitted the code, Actually works/worked for SCO and or Caldera at the time of Inclusion?

If that is the case, they got a bigger problem than they thought. They get to sue themselves and or the employee of thier own... UNLESS he/she has thier butt covered with "agreements" that are notary stamped. :)
[link|mailto:curley95@attbi.com|greg] - IT Grand-Master for Anti-President
[link|http://www.iwethey.org/ed_curry/|REMEMBER ED CURRY!]
-----BEGIN GEEK CODE BLOCK-----\nVersion: 3.12+\nGAT d+ s+:++ a C++++ UBHLO++++ P+ L+++ E---/E---- W+++ N+ o--\nK--- w--- O+ M+ V-- PS-- PE Y+ PGP++ t+ 5++ X+ R tv+ b+++ DI+++\nD++ Q2+++ Q3A+++ UT+++ UT2K3+++ G e* h--- r+++ z+++*\n------END GEEK CODE BLOCK------
New Linux revision control

Little-known (but not AFIAK secret) fact is that Larry McVoy (Bitkeeper) has been tracking changes to the kernel source for years. Sort of a pre-adoption proof-of-concept of BitKeeper, not to mention the sort of thing which might become commercially valuable to a party that wanted to track its own deltas to the core tree (this is one of the features of BitKeeper -- making and tracking satellite repositories with one-way transitivity to core is reasonably trivial)...or a large monied interest with an interest in legal discovery.

\r\n\r\n

Another interesting point this raises is the question of who is responsible for introduction of encumbered code into the kernel. SCO is certainly making the case that it's IBM. However one possible legal argument is that the code submitter him- or herself is representing the code to be legally clear, and assumes responsibility in the event that it is not. Time will tell.

--\r\n
Karsten M. Self [link|mailto:kmself@ix.netcom.com|kmself@ix.netcom.com]\r\n
[link|http://kmself.home.netcom.com/|http://kmself.home.netcom.com/]\r\n
What part of "gestalt" don't you understand?\r\n
[link|http://twiki.iwethey.org/twiki/bin/view/Main/|TWikIWETHEY] -- an experiment in collective intelligence. Stupidity. Whatever.\r\n
\r\n
   Keep software free.     Oppose the CBDTPA.     Kill S.2048 dead.\r\n[link|http://www.eff.org/alerts/20020322_eff_cbdtpa_alert.html|http://www.eff.org/alerts/20020322_eff_cbdtpa_alert.html]\r\n
New Wouldn't that *have* to be the case?
However one possible legal argument is that the code submitter him- or herself is representing the code to be legally clear, and assumes responsibility in the event that it is not.
As SCO's code is not available for comparison, what expectation is there that IBM (for instance) would even be able to identify infringement? For that matter, what assurenaces does SCO have that Microsft (for instance) hasn't included some of SCO's intellectual property into their (closed-source) products?

If SCO would like to ensure their products aren't copied, they should file for patent protectin rather than pursuing copyright infringement claims. Then the code would be public, so other companies could compare new susbmissions for similarity, but still protected by the force of law. Or do they not think te ideas encapsulated in the code are original enough to be patented? Which would tend to shoot a hole in their entire argument that only be misappropriating their IP could Linux by where it is today.

And that, boys and girls, is called a Catch-22.
===

Implicitly condoning stupidity since 2001.
New SCO stabs their own lawyers in the back
[link|http://www.infoworld.com/article/03/04/16/HNscolinux_1.html|SCO releases Linux for Itanium]
The SCO Group has released a Linux server operating system for the 64-bit Intel Itanium processor, the company announced Tuesday.

SCO Linux Server 4.0 for the Itanium Processor Family is based on UnitedLinux 1.0, the Linux operating system being marketed by a coalition of four Linux companies, in an effort to promote Linux interoperability and compete with U.S. market Linux leader Red Hat.
By releasing this system under the GPL, SCO has just agreee to share any of their intellectualy property they included. So what are they suing for again?
===

Implicitly condoning stupidity since 2001.
New ROFL
And it's hard to stab a snake in the back...
Regards,

-scott anderson

"Welcome to Rivendell, Mr. Anderson..."
New Hey! You're maligning snakes everywhere with that one
--\n-------------------------------------------------------------------\n* Jack Troughton                            jake at consultron.ca *\n* [link|http://consultron.ca|http://consultron.ca]                   [link|irc://irc.ecomstation.ca|irc://irc.ecomstation.ca] *\n* Kingston Ontario Canada               [link|news://news.consultron.ca|news://news.consultron.ca] *\n-------------------------------------------------------------------
New Sorry.
Regards,

-scott anderson

"Welcome to Rivendell, Mr. Anderson..."
New :)
--\n-------------------------------------------------------------------\n* Jack Troughton                            jake at consultron.ca *\n* [link|http://consultron.ca|http://consultron.ca]                   [link|irc://irc.ecomstation.ca|irc://irc.ecomstation.ca] *\n* Kingston Ontario Canada               [link|news://news.consultron.ca|news://news.consultron.ca] *\n-------------------------------------------------------------------
New So 10 lines of code == 20 years of [...] IP?
Boy does that skew the productivity average! ;-\ufffd

BTW, how does he know that the lines have been "obfuscated to make it look like it wasn't UnixWare code--but it was." Is his claim that the only way to do something was to use his code, even if it doesn't look like his code?

Sounds like Gatesian arrogance to me....
jb4
"We continue to live in a world where all our know-how is locked into binary files in an unknown format. If our documents are our corporate memory, Microsoft still has us all condemned to Alzheimer's."
Simon Phipps, SUN Microsystems
New Hmmm - I wonder 'which' code they refer to ... IBM

Worked with Bell Labs in the 1970s to implement UNIX ver6/ver7 on IBM System/360 mainframes & IBM contributed substantial portions of kernel code to the product. It was argued at the time that Unix raw had very little by way of robust memory management and locking etc: mechanisms.

The IBM 360 Unix was the first major usage outside Bell (Ken, Dennis & others had been mostly developing and using Unix on Digital PDP computers). Bell was the company that did most of the work on Unix ver6 / ver7 later DEC computers as Ken Olsen (then DEC CEO) always thought of Unix as 'snake oil'.

So am wondering just where these portions of Unix code really came from :-)

Cheers

Doug Marker


Spectres from our past: Beware the future when your children & theirs come after you for what you may have been willing to condone today - dsm 2003


Motivational: When performing activities, ask yourself if the person you most want to be would do, or say, it - dsm 2003
New Reminds me of Ashton Tate vs. Fox
Ashton Tate sued Fox Software for "stealing" their language (not source code in this case, but the XBase language).

It turned out that the language was originally developed in NASA's JPL lab by a guy fiddling with better ways to track football stats. It was done on gov time so no private firm could claim ownership. The case was dropped.

In the SCO case, all they seem to know is that some of the code is the same or similar, but have no evidence of who put it there, when, or who had it first so far.

What needs to be done is an investigation rather than lawsuits. It is sue first and ask questions later.
________________
oop.ismad.com
New Depends on level of difference
As a part time professor I've seen a number of programs that had different formatting, comments, variable names, but could be mechanically shown to be equivalent (via a fairly trivial set of search and replace operations). There are [link|http://www.berkeley.edu/news/media/releases/97legacy/11_19_97b.html|programs] that have been developed that check for this.

So lets see how the MOSS metric works on the various "obfuscated regions" and then we can make an informed judgement.



"Packed like lemmings into shiny metal boxes.
Contestants in a suicidal race."
    - Synchronicity II - The Police
Expand Edited by tuberculosis Aug. 21, 2007, 06:35:33 AM EDT
New Eric Raymond deconstructs SCO's argument.
[link|http://www.opensource.org/sco-vs-ibm.html|Here]. (Found via [link|http://weblog.siliconvalley.com/column/dangillmor/|Dan Gillmor's blog]'s pointer to [link|http://amywohl.weblogger.com/|Amy Wohl's blog] to the link above.)

SCO alleges (Paragraph 57): \ufffdWhen SCO acquired the UNIX assets from Novell in 1995, it acquired rights in and to all (1) underlying, original UNIX software code developed by AT&T Bell Laboratories.\ufffd

SCO neglects to mention that those rights had been substantially impaired before its acquisition of the ancestral Bell Labs source code. There was a legal action in 1992-1993, in which Unix Systems Laboratories and Novell (SCO's predecessors in interest) sued various parties including the University of California at Berkeley and Berkeley Systems Design, Inc. for alleged copyright infringement, trade secret disclosures, and trademark violations with regard to the release of the open-source 4.4BSD operating system[10].

The suit was settled after AT&T's request for an injunction blocking distribution of BSD was denied in terms that made it clear the judge thought BSD not unlikely to win its defense. The University of California then threatened to countersue over license violations by AT&T and USL. It seems that from as far back as before 1985, the historical Bell Labs codebase had been incorporating large amounts of software from the BSD sources. The University's cause of action lay in the fact that AT&T, USL and Novell had routinely violated the terms of the BSD license by removing license attributions and copyrights.

The exact terms of final settlement, and much of the judicial record, were sealed at Novell's insistence. The key provisions are, however, described in Twenty Years of Berkeley Unix: From AT&T-Owned to Freely Redistributable, [McKusick99]. Only three files out of eighteen thousand in the distribution were found to be the licit property of Novell and removed. The rest were ruled to be freely redistributable, and continue to form the basis of the open-source BSD distributions today.

That is, ten years ago at a time when Linux was in its infancy, the courts already found the contributions of other parties to what is now UnixWare to be so great, and Novell's proprietary entitlement in the code so small, that Novell's lawyers had to settle for a minor, face-saving gesture from the University of California or walk away with nothing at all.

This history is well-known in the open-source community, and helps explain why SCO's claim that ownership of the historical Bell Labs code gives it substantial rights over other Unixes such as AIX is regarded among old Unix hands with near-universal disdain. Some of the court documents, including the 1993 ruling are now available on the web [11].

[...]

Since IBM's AIX is well known to contain large portions of Berkeley code (towards which IBM has by all accounts met its license obligations) SCO's theory is at best extremely dubious. In other words, to prove its right to relief SCO will need to show that whatever code IBM gave to the open-source community was neither legally obtained by both IBM and SCO from a common source nor independently developed.

[... Much later ...]

Furthermore, SCO is barred by the terms of the GNU General Public License from making copyright or patent-infringement claims on any technology shipped in conjunction with the Linux kernel that SCO/Caldera itself has been selling for the last eight years. Therefore, SCO may accuse IBM of misappropriating SCO-owned software to improve the Linux kernel only if that software does not actually ship with the Linux kernel it is alleged to be improving!

Finally, SCO is barred from making trade-secret claims on the contents of the Linux kernel, not merely by the fact that the kernel source is generally available, but by the fact that SCO has made the sources of its Linux kernel available for download from SCO's own website! [23].


Cheers,
Scott.
New Excellent resource. Thanks Scott
Just a few thoughts,

Screamer


Living is easy with eyes closed
misunderstanding all you see,
it's getting hard to be someone but it all works out
it doesn't matter much to me


J. Lennon - Strawberry Fields Forever
New The GPL argument is particularly compelling IMO

Distributing a GPLd work incorporating the copyrighted works of others, while denying others the right to distribute the same work under claims of copyright infringement, spells "proprietizing a GPLd work" to me.

\r\n\r\n

It's also interesting to see how SCO's complaint has "evolved". Initial speculation was that it concerned patents. Don Marti destroyed that myth by showing SCO held no patents. [link|http://lwn.net/Articles/25149/|My own essay] and ESR's work largely destroy the trade secrets claims for the most part (ESR's history on AT&T Unix and the BSD wars is an interesting add). Now the claim is copyright...and in what seems like a classic chess endgame pincer move, it appears SCO's skewered on this as well.

--\r\n
Karsten M. Self [link|mailto:kmself@ix.netcom.com|kmself@ix.netcom.com]\r\n
[link|http://kmself.home.netcom.com/|http://kmself.home.netcom.com/]\r\n
What part of "gestalt" don't you understand?\r\n
[link|http://twiki.iwethey.org/twiki/bin/view/Main/|TWikIWETHEY] -- an experiment in collective intelligence. Stupidity. Whatever.\r\n
\r\n
   Keep software free.     Oppose the CBDTPA.     Kill S.2048 dead.\r\n[link|http://www.eff.org/alerts/20020322_eff_cbdtpa_alert.html|http://www.eff.org/alerts/20020322_eff_cbdtpa_alert.html]\r\n
     SCO's other shoe drops: SCO source code found in Linux - (admin) - (16)
         Simple solution - (drewk) - (3)
             Wouldn't it be funny... - (folkert)
             Linux revision control - (kmself) - (1)
                 Wouldn't that *have* to be the case? - (drewk)
         SCO stabs their own lawyers in the back - (drewk) - (4)
             ROFL - (admin) - (3)
                 Hey! You're maligning snakes everywhere with that one -NT - (jake123) - (2)
                     Sorry. -NT - (admin) - (1)
                         :) -NT - (jake123)
         So 10 lines of code == 20 years of [...] IP? - (jb4) - (3)
             Hmmm - I wonder 'which' code they refer to ... IBM - (dmarker) - (1)
                 Reminds me of Ashton Tate vs. Fox - (tablizer)
             Depends on level of difference - (tuberculosis)
         Eric Raymond deconstructs SCO's argument. - (Another Scott) - (2)
             Excellent resource. Thanks Scott -NT - (screamer)
             The GPL argument is particularly compelling IMO - (kmself)

Whenever someone says, "Show, don't tell," aren't they violating that exact rule?
71 ms