decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
When you come to a fork in the road...
Sunday, May 21 2006 @ 10:23 PM EDT

Yogi Berra said once, "When you come to a fork in the road, take it."

It's funny, until someone actually takes that advice literally and tries to go down two conflicting roads at once. For example, take SCO's Reply to Novell's Counterclaims. In paragraph 50, SCO tells the court this:

Admits that SCO, through its SCOsource division, entered into agreements related to UNIX and UnixWare with Sun Microsystems, Inc., and Microsoft Corporation (in that order) and that the Microsoft agreement covered UNIX compatibility products; but denies each and every other allegation of ¶ 50, including the allegation that the Sun and Microsoft agreements were part of the SCOsource licensing program.

Say, what?

Now, I hate to embarrass anybody, but love for truth compels me to point out that SCO said something that sounded very much like the Sun and Microsoft agreements were indeed SCOsource licenses in a 10Q filed for the quarterly period ended April 30, 2003. Now, knowing as I do that there are laws about telling the truth to the SEC and that when you go to court you are supposed to tell the truth, the whole truth and nothing but the truth so help you God, I'm puzzled as to how SCO will explain what seems to be a direct contradiction. Here's what SCO filed with the SEC for the quarter ending April 20, 2003:

Recent Developments

During recent quarters, we have experienced a decline in our product and services revenue primarily attributed to the worldwide economic slowdown, lower information technology spending and increased competition in the operating system market. However, we have implemented cost reduction measures to decrease personnel and excess facilities and have significantly reduced our overall operating expenses. These measures, combined with the revenue from our SCOsource licensing initiative, have resulted in the first profitable quarter in our history.

Over 95 percent of our revenue has been derived from UNIX related products and services. During the quarter ended April 30, 2003, we recognized $8,250,000, or 39 percent of our quarterly revenue, from our intellectual property licensing initiative, SCOsource, launched in January 2003.

One of the assets we acquired from Tarantella was the intellectual property rights to UNIX. These rights had initially been developed by AT&T Bell Labs and over 30,000 licensing and sublicensing agreements have been entered into with approximately 6,000 entities. These licenses led to the development of several proprietary UNIX-based operating systems, including our own SCO UnixWare and SCO OpenServer, Sun’s Solaris, IBM’s AIX, SGI’s IRIX, HP’s UX, Fujitsu’s ICL DRS/NX, Siemens’ SINIX, Data General’s DG-UX, and Sequent’s DYNIX/Ptx. We believe these operating systems are all derivatives of the original UNIX source code owned by us.

We initiated the SCOsource effort to review the status of these licensing and sublicensing agreements and to identify others in the industry that may be currently using our intellectual property without obtaining the necessary licenses. This effort resulted in the execution of two license agreements during the April 30, 2003 quarter. The first of these licenses was with a long-time licensee of the UNIX source code which is a major participant in the UNIX industry and was a “clean-up” license to cover items that were outside the scope of the initial license. The second license was to Microsoft Corporation (“Microsoft”), and covers Microsoft’s UNIX compatibility products, subject to certain specified limitations. These license agreements will be typical of those we expect to enter into with developers, manufacturers, and distributors of operating systems in that they are non-exclusive, perpetual, royalty-free, paid up licenses to utilize the UNIX source code, including the right to sublicense that code. The amount that we receive from any such licensee will generally depend on the license rights that the licensee previously held and the amount and level of our intellectual property the licensee desires to license. The two licensing agreements signed by us to date resulted in revenue of $8,250,000 during the April 30, 2003 quarter and provide for an aggregate of an additional $5,000,000 to be paid to us over the next three quarters. These contracts do not provide for any payments beyond 2003, except that Microsoft was granted the option to acquire expanded licensing rights, at its election, that would result in additional payments to us if exercised. In connection with the execution of the first license agreement, we granted a warrant to the licensee to purchase up to 210,000 shares of our common stock, for a period of five years, at a price of $1.83 per share. This warrant has been valued, using the Black-Scholes valuation method, at $500,000. Because the warrant was issued for no consideration, $500,000 of the license proceeds have been recorded as warrant outstanding and the license revenue reduced accordingly.

During the course of the review of our intellectual property rights, we became concerned generally about the existence of UNIX source code in the Linux operating system. We have discovered that UNIX source code and unauthorized derivatives of UNIX source code are prevalent in the Linux kernel. In March 2003, we filed a complaint against IBM alleging, in part, that it had breached its license agreement with us by, among other things, inappropriately contributing UNIX source code to the open source community and seeking to use its knowledge and methods with respect to UNIX source code and derivative works and modifications licensed to it to destroy the value of the UNIX operating system in favor of promoting the adoption by businesses of the Linux operating system, of which it has been a major backer. Unless IBM cures the breaches we have identified, we will terminate the license agreement we have with it that permitted the use of our UNIX source code in the development of its AIX operating system. In May, 2003, we sent letters to approximately 1,500 large corporations notifying them that the use of the Linux operating system may be a violation of our intellectual property rights.

The success of our SCOsource licensing initiative, at least initially, will depend to a great extent on the perceived strength of our intellectual property and contractual claims and our willingness to enforce our rights. Many, particularly those in the open source community, dispute the allegations of infringement that we have made.

While our SCOsource initiative has already resulted in significant revenue during the April 30, 2003 quarter and we continue negotiations with other industry participants that we believe will lead to additional contracts, as a result of the factors outlined above, we are unable to predict the level or timing of future revenue from this source, if any.

THREE AND SIX MONTHS ENDED APRIL 30, 2003 AND 2002

Revenue

Revenue was $21,369,000 for the second quarter of fiscal year 2003, and $15,476,000 for the second quarter of fiscal year 2002, representing an increase of $5,893,000, or 38 percent. This increase was attributable to $8,250,000 in licensing revenue, which we generated for the first time, offset by a decline in product revenue of $1,484,000 and a decline in services revenue of $873,000. Revenue was $34,909,000 for the first two quarters of fiscal year 2003, and $33,389,000 for the first two quarters of fiscal year 2002, representing an increase of $1,520,000, or 5 percent. This increase was attributable to $8,250,000 in licensing revenue, offset by a decline in product revenue of $5,300,000 and a decline in services revenue of $1,430,000.

As discussed above in Recent Developments, we are unable to predict the level of licensing revenue we may recognize in future periods. During the first two quarters of fiscal year 2003, our product and service revenue continues to be adversely impacted by the continuing worldwide economic slowdown and from the related decrease in information technology spending, as well as from increased competition from other operating system products. Excluding licensing revenue from SCOsource, revenue from international customers accounted for 48 percent of operating system platform revenue for the second quarter of fiscal year 2003 and 50 percent for the second quarter of fiscal year 2002, and revenue from international customers accounted for 47 percent of operating system platform revenue for the first two quarters of fiscal year 2003 and 50 percent for the first two quarters of fiscal year 2002. The decrease in international revenue for the second quarter and first two quarters of fiscal year 2003 compared to the second quarter and first two quarters of fiscal year 2002 is primarily attributable to decreased revenue in our Europe, Middle East and Africa (“EMEA”) region.

Products.

Products revenue was $11,122,000 for the second quarter of fiscal year 2003 and $12,606,000 for the second quarter of fiscal year 2002, representing a decrease of $1,484,000, or 12 percent, and representing a slight increase in products revenue from our first quarter of fiscal year 2003. Products revenue was $22,212,000 for the first two quarters of fiscal year 2003 and $27,512,000 for the first two quarters of fiscal year 2002, representing a decrease of $5,300,000, or 19 percent.

The decrease in products revenue during the second quarter of fiscal year 2003 from the second quarter of fiscal year 2002 as well as during the first two quarters of fiscal year 2003 from the first two quarters of fiscal year 2002 was attributable to decreased sales of OpenServer and UnixWare products primarily resulting from a decrease in information technology spending caused by the worldwide economic slowdown. This impact was largely felt in our distribution channel in the Americas and Europe. Our UNIX-based products revenue has also declined due to increased competition in the operating system market from other software offerings.

OpenServer and UnixWare products are the largest components of the Company’s products revenue. For the second quarter of fiscal year 2003, OpenServer revenue was $5,750,000, or 52 percent of total products revenue and UnixWare revenue was $3,017,000, or 27 percent of total products revenue. For the first two quarters of fiscal year 2003, OpenServer revenue was $10,491,000, or 47 percent of total products revenue and UnixWare revenue was $7,181,000, or 32 percent of total products revenue.

Licensing.

Licensing revenue was $8,250,000 for the second quarter and first two quarters of fiscal year 2003 as compared to no revenue for the second quarter and first two quarters of fiscal year 2002. This revenue is the result of our intellectual property licensing program, SCOsource, launched in January 2003. We initiated SCOsource for the purpose of protecting the significant intellectual property rights we own surrounding the UNIX source code. The licensing revenue in the second quarter of fiscal year 2003 represents a portion of the fees associated with two licenses executed during the quarter. Under the terms of one of these agreements, we will receive an additional $5,000,000 over the next three quarters. The agreements also grant the right to one of the licensees to acquire an expanded license upon the payment of additional fees. We are in discussions with additional potential licensees, but are unable to predict the amount or timing of the revenue we might expect from this source in future periods. . . .

Our SCOsource licensing revenue to date has been generated from license agreements that are non-exclusive, perpetual, royalty-free, paid up licenses to utilize our UNIX source code, including the right to sublicense. We recognize revenue from licensing agreements when a signed contract exists, the fee is fixed and determinable, collection of the receivable is probable and delivery has occurred. If the payment terms extend beyond our normal payment terms, then revenue is recognized as cash is received.... Our future SCOsource licensing revenue is uncertain.

We initiated the SCOsource licensing effort in January 2003 to review the status of UNIX licensing and sublicensing agreements and to identify others in the industry that may be currently using our intellectual property without obtaining the necessary licenses. This effort resulted in the execution of two license agreements during the April 30, 2003 quarter. These two license agreements will be typical of those we expect to enter into with developers, manufacturers, and distributors of operating systems in that they are non-exclusive, perpetual, royalty-free, paid up licenses to utilize the UNIX source code, including the right to sublicense that code. Due to a lack of historical experience and the uncertainties related to SCOsource licensing revenue, we are unable to estimate the amount and timing of future licensing revenue, if any. If we do receive revenue from this source, it may be sporadic and fluctuate from quarter to quarter. SCOsource licensing revenue is unlikely to produce stable, predictable revenue for the foreseeable future.

Well. If what SCO is telling the court now is true, I certainly hope that no one bought any stock from SCO Group under the false impression that Microsoft and Sun Microsystems executed two SCOsource licensing agreements during the April 30, 2003 quarter. Unless I don't understand what I'm reading, which is always possible, I suppose, I got the distinct impression that the SEC filing says those two licenses were SCOsource licenses. Now, I'm no lawyer and surely no expert on SEC filings, but I can read. Perhaps SCO needs to file an amended April 30, 2003 filing? How does that work?

But, if they wish to start correcting, I think they might need to fix this 10-K for the fiscal year ended October 31, 2003 too:

SCOsource Business

Background

We acquired our rights relating to the UNIX source code and derivative works and other intellectual property rights when we purchased substantially all of the assets and operations of the server and professional services groups of The Santa Cruz Operation, Inc. in May 2001. The Santa Cruz Operation (now known as Tarantella, Inc.) had previously acquired such UNIX source code and other intellectual property rights from Novell in September 1995, which were initially developed by AT&T Bell Labs. Through this process, we acquired all UNIX source code, source code license agreements with thousands of UNIX vendors, all UNIX copyrights, all claims for violation of the above mentioned UNIX licenses and copyrights and other claims, and the control over UNIX derivative works. The UNIX licenses we obtained have led to the development of several proprietary UNIX-based operating systems, including but not limited to our own UnixWare and OpenServer products, Sun's Solaris, IBM's AIX, SGI's IRIX, Hewlett-Packard's UX, Fujitsu's ICL DRS/NX, Siemens' SINIX, Data General's DG-UX, and Sequent's DYNIX/Ptx. These operating systems are all derivatives of the original UNIX source code owned by us.

The success of our SCOsource business depends on our ability to protect our proprietary UNIX source code as well as our copyrights and other intellectual property rights. To protect our proprietary rights, we rely primarily on a combination of copyright laws, contractual rights and a detailed legal strategy. We have dedicated internal personnel and other resources to our SCOsource business and intend to dedicate additional SCOsource sales personnel in fiscal year 2004.

In January 2003, we commenced our first SCOsource initiative in which, as described in more detail below, we began reviewing the status of our existing UNIX license agreements with UNIX vendors and to identify those in the software industry that may be using our intellectual property without obtaining the necessary licenses. As part of this process, we became aware that parts of our proprietary UNIX source code and derivative works have been included in the Linux operating system without attribution or our authorization in violation of our intellectual property rights. To respond to this concern, we have instigated additional SCOsource initiatives related to end users of Linux, which are described in more detail below. Additionally, we filed a complaint against IBM in March 2003 alleging that IBM breached its license agreement with us related to its efforts to promote and support the Linux operating system. We describe our legal action against IBM in more detail below under Part I, Item 3 of this Form 10-K.

SCOsource Initiatives

Reviewing and Evaluating Existing UNIX Licenses. As mentioned above, in January 2003, we began reviewing the status of our existing UNIX license agreements with UNIX vendors. This review is continuing and we will continue to expand our efforts in fiscal year 2004. During fiscal year 2003, we entered into two significant license agreements. The first of these licenses was with Sun, a long-time UNIX licensee and a major participant in the UNIX industry. The second license was to Microsoft and covers Microsoft's UNIX compatible products, subject to certain specified limitations. The Sun and Microsoft license agreements accounted for $25,846,000 of our revenue in fiscal 2003, representing approximately 33 percent of our total revenue for such period.

Warning Letters to Linux End Users. In response to our belief that parts of our UNIX source code and derivative works have been inappropriately included in the Linux operating system, in May 2003, we sent letters to approximately 1,500 large corporations notifying them that using the Linux operating system may violate our asserted intellectual property rights. Subsequently, we began contacting Linux end users about their use of Linux, and in December 2003, we began sending additional letters to selected Fortune 1000 Linux end users specifically asserting that using the Linux operating system in a commercial setting violates our rights under the United States Copyright Act, including the Digital Millennium Copyright Act, because certain copyrighted application binary interfaces, or "ABI Code," have been copied from our copyrighted UNIX code base and derivative works and contributed to Linux without proper authorization and without copyright attribution. In the letter we also warned Linux end users that we intend to take appropriate actions to protect our rights and that they may not use our copyrighted code except as authorized by us.

Linux End User Intellectual Property ("IP") License Initiative. In August 2003, we first offered to Linux end users our IP license in the United States and recently began offering the license in countries outside the United States. The license permits the use of our intellectual property, in binary form only, as contained in the Linux operating system. By purchasing the license, customers will properly compensate us for our UNIX intellectual property as currently found in Linux.

Requiring UNIX Licensees to Certify Full Compliance with License Agreements. Beginning in December 2003, we began delivering written notice to a large number of our UNIX licensees that they must certify in writing to us that they are in full compliance with their license agreements, including certification that they are not using our proprietary UNIX code and derivative works in Linux, have not allowed unauthorized use of our licensed UNIX by their employees or contractors and have not breached confidentiality provisions relating to licensed UNIX code.

Intellectual Property Protection Generally

Our SCOsource initiatives rely primarily on a combination of contract rights, copyright laws and a detailed legal strategy. We also require that our employees and consultants sign confidentiality and nondisclosure agreements. We also regulate access to, and distribution of, our documentation and other proprietary information.

We cannot guarantee the success of our SCOsource initiatives and other efforts to protect our intellectual property rights, but we will continue to seek to enforce and pursue these rights through public awareness and the legal system, if necessary. Additionally, we cannot be certain that we will succeed in preventing the future misappropriation of our copyrights or that we will be able to prevent the unauthorized use of our technology in the future.

Current Status and Strategy

In fiscal 2004, we will continue to pursue our SCOsource initiatives. We will continue to review and evaluate our UNIX license agreements and pursue large vendor contracts similar to those completed in fiscal year 2003 with Sun and Microsoft. Additionally, we will further pursue our SCOsource IP license initiative with end users of Linux. To accomplish this objective, we plan to increase our SCOsource sales team in fiscal year 2004, and may also make the SCOsource IP license available through select SCO resellers. ...

Risk Factors

We do not have a history of profitable operations.

Our fiscal year ended October 31, 2003 was the first full year we were profitable in our operating history. Our profitability in fiscal year 2003 resulted primarily from our SCOsource licensing initiative. If we do not receive SCOsource licensing revenue in future quarters and our revenue from the sale of our operating system platform products and services continues to decline, we will need to further reduce operating expenses to maintain profitability or generate positive cash flow. ...

Our future SCOsource licensing revenue is uncertain.

We initiated the SCOsource licensing effort in January 2003 to review the status of UNIX licensing and sublicensing agreements. This effort resulted in the execution of two significant vendor license agreements during fiscal year 2003 and generated $25,846,000 in revenue. Due to a lack of historical experience and the uncertainties related to SCOsource licensing revenue, we are unable to estimate the amount and timing of future SCOsource licensing revenue, if any.

So, if the Sun and Microsoft licenses were not SCOsource licenses, they certainly fooled me. Not only did the SEC filings give me the impression those two licenses were SCOsource licenses, my memory was that this is what SCO executives told us at the time that they were. So I started out searching Groklaw's Quote Database, using the keyword SCOsource, and this is what I found:

  • Darl McBride, quoted in eWeek February 26, 2003:

    McBride said SCO expected revenue for the second quarter, ending April 30, 2003, to be in the range of $23 million to $25 million. That forecast was based on anticipated revenue from its current operating platforms of $13 million to $15 million, and from $10 million in revenue from its SCOsource licensing initiative.

  • Darl McBride and Robert Bench, May 28, 2003 2003 Q2 earnings conference call:

    McBride: OK, so let's go ahead and dive into it. As we announced today, for the second quarter of fiscal 2003 ended April 30th, The SCO group reported net income of 4.5 million, or 33 cents per diluted share, on revenue of 21.4 million, compared to a net loss of 6.6 million, or 47 cents per diluted share, on revenue of 15.5 million for the comparable quarter of the prior year. The company reported a net loss of 724,000, or 6 cents per diluted share, on revenue of 13.5 million for the first fiscal quarter of 2003.

    Revenue for the second quarter of fiscal 2003 from the company's Operating System platforms was 13.1 million, and revenue from its ... from our SCOsource licensing initiative was 8.3 million. During the quarter ended April 30th, 2003 the first two licensing agreements relating to our SCOsource initiative, our division for the licensing and protecting the company's Unix intellectual property, derived the company of 8.8 million in cash and added 6.1 million to gross margin.

    We have over six thousand source code licensees of our Unix Operating System, and we believe the SCOsource initiative will continue to gain momentum as we pursue enforcement of the company's intellectual property rights. ...

    Bench: This past quarter marked the completion of our consolidation and restructure of the company's worldwide operations. With thirteen offices and sales activities in 82 countries, our ability to support large and small customers is unequaled for a company our size. We continue to expand our support and product offerings to more than 11 thousand solution provider partners who serve small businesses. Of the 21.4 million in revenue, 61 percent or 13.1 million, was related to our core Unix operating system platforms, of which 11.1 million was products, and 2 million was services. 39 percent, or 8.3 million, of revenues was generated through the SCOsource initiative....

    McBride: Now let's shift gears and talk about the SCOsource part of the business. Two quarters ago when we did our conference call we had, I believe seven people on the call. They just told me now that we have two hundred and forty-four on the call today. My guess is that a number of you tuned it today to hear a number of things we're gonna talk about now of respect to this new licensing division that we created during the second quarter. SCOsource is set up to go out and take our Unix source code, continue to move it forward, continue to propagate it and to protect the property rights that we have there. As we said earlier, we have six thousand licensees of our Unix source-code. During the second quarter we had two big deals that we signed. The two large companies -- one is unnamed at this point based on contractual obligations that we have. I wasn't sure if we were going to be talking about that today or not, but as it stands contractually we will not be talking about that on this call.

    The second licensee is the Microsoft Corporation. We announced that deal last week. In that announcement we essentially said that Microsoft has licensed the Unix source code to ensure compatibility for Windows and Unix customers. The Unix source code license will help with Microsoft's product called Services for Unix. And Microsoft reinforced in their statements that they value the intellectual property that we hold and the source-code license that they took will help them, as they move forward, with integrating the Unix products into Windows. ...

    Operator: Moving on we'll take our next question from Robert Mina (sp??) of Copper Beech Capital.

    Mina: Yes, Thank You. Can you please comment on the visibility of SCOsource revenue stream? How long can we anticipate that to be a contribution to revenue based on the two contracts you've signed? And can you tell us updates on any other contracts that you are in negotiation with right now. Thank you.

    McBride: Sure. Great Question. We started this initiative just this last quarter. As we now sum here, we had 8.2 million of revenue that showed up, and as we said for the coming quarter we see SCOsource contributions being roughly a third. And so far we have only signed two contacts. We see we have visibility currently, even on the contracts we signed that go several quarters out from where we sit right now. As we look at the other deals that are in the pipeline, that we have not signed yet, you know the opportunity on the SCOsource side I would describe as being significant. ...

    Jackson: Sort of a follow-up on the SCOx, as it relates to the two big contracts with Microsoft and the other one. Can you apportion what value of the total contract size relates to the SCOsource type licenses in arrears vs. product sales going forward? Wait, maybe I should rephrase. What portion of the contract value in either or both instances relates to new products that might be tied in to SCOx?

    McBride: Yeah. The deals that have been done on SCOsource side relate more, not too much to our direct lines under SCOx product line, but more to taking our core thread of Unix that we own and giving access to portions of that to these other companies to be able to integrate their product lines better from a Unix operability standpoint. So ....

    Jackson: And I guess what I'm asking is it on a one shot deal or is it ....

    McBride: Yeah. So, what we have here is the first few SCOx deals that we've targeted, we've chosen to bring more money in over several quarters as opposed to a longer term type of royalty stream if you will. So we've got multiple quarters, several quarters of revenue recognition from these original deals. We were last, if you remember on our last call, we were looking at trying to raise some equity capital from the financial markets. We actually had people stepping up ready to invest in the company. We decided not to take those investments, because we were able to generate significantly larger amounts of cash through SCOsource that was non-dilutive. So, the first part was to go ahead and shore up the balance sheet, as we have done. We are debt-free now, cash is growing, we are in good shape on the cash side. As we go forward we expect to start looking at SCOsource licensing deals that will have even a longer term impact, than this over several quarters.

  • Darl McBride, August 14, 2003 conference call on 2003 Q3 Earnings:

    McBride: OK, thank you. And thank all of you for joining our call today. Our quarter that ended July 31, 2003, marked the second consecutive quarter of strong positive earnings. Revenue attributed to our SCOsource intellectual property licensing initiative has generated positive operating margins and has contributed to positive case flows from operations. These activities during the past two quarters have nearly tripled our cash balance and thus strengthening our balance sheet. Over the past four quarters our market cap has gone from under 10 million dollars to over 140 million dollars making SCOX one of the top performing stocks on the NASDAQ market.

    In a moment, Bob Bench, our CFO will give a detailed analysis of the quarter. However, before that analysis, I'd like to review the actions we've taken over the last year since my joining SCO as the Chief Executive Officer that have made the significant accomplishments possible and that will continue to drive greater success in the future.

    We restructured the company to reduce expenses and better manage our assets.

    We reestablished the SCO brand. The SCO brand is 20 plus years old, known worldwide and strongly associated with Unix.

    We formed SCOsource to monetize our Unix intellectual property. ...

    What I'd like to do now is throw the ball over to Bob and have him run with it a bit with respect to more detailed analysis on how the quarter went.

    Robert Bench: Thanks Darl.

    The company has continued to adhere to a viable operating model that will create additional efficiencies in our worldwide operations. We increased the percent of revenue invested in product development this past quarter, while slightly decreasing our other operating costs.

    Of the 20.1 million in revenue, 12.8 million of 64% was related to our core Unix operating system platform. And of the 12.8 million, 10.8 million was product related and 2 million was from services. The other 36% of our 20 million in revenue, or 7.3 million in revenue, was generated from our SCOsource initiatives. Our gross margin of 15.5 million or 77% was slightly higher than last quarter and in line with our operating model....

    Our SCOsource activities and initiatives and our recent announcements regarding Linux may also be causing customers to lengthen their purchase and implementation cycle as they contemplate the appropriate operating platform of the future and asses the current risks related to Linux. Our products are continuing to be used in new businesses and our present cutomers are expanding their current operations. ...

    Operator: And next we'll go to Robert McMillan from IDG. Please go ahead.

    McMillan: Yeah. Actually my question was pretty much what Maureen was ... just asked you. Could you ... maybe you could just tell me a little bit more about this SCOsource revenue, then. Could you tell me where's that going to be coming from? I mean do you have new licensee technology coming, licensing the Unix source source code or ... how are you going to get 10 to 12 million dollars from SCOsource?

    McBride: Well, as we said in our last call, Robert, a quarter ago, we modeled this thing out and we wanted to... pull out and sign up big industry partnerships, and we would choose to model that in a way that we would have more revenue coming in in bigger blocks over multiple-quarter periods of time as a mechanism to shore up our balance sheet. And then, as we got in to the ... more of the end-use licensing part, we would put in the, you know, the more of the blocking and tackling, per-unit royalty licensing that we would roll out.

    And that's, that's really on-track with where we are. We continue to go down the path of having big deals that are done with big companies that provides more of an up-front set of cash payments that come in over multiple quarters, and then this licensing program we just kicked off here over the last couple weeks is something we expect to ramp up, and the the first part in the revenue line-item there with the big blocks coming in isn't something that goes on forever, but on the, you know you get multiple quarter coverage out of that, and then, over time we see the ramp really coming, that shows significant run-up, over time, coming from more of this end-use type of a licensing program.

  • Sun Microsystems VP John Loiacono quoted in eWeek, March 7, 2003:

    Sun Microsystems Inc., whose Solaris operating system is based on Unix, moved quickly Thursday to assure its customers that its licenses are all in order. John Loiacono, vice president of Sun's operating platforms group, told eWEEK Thursday that the company has assured its customers and partners that it has licensing rights to Unix for both SPARC and the recently available x86 systems.

    "As part of a series of licensing agreements, Sun acquired rights to make and ship derivative products based on the intellectual property in Unix. This forms the foundation for the Solaris operating system that ships today," Loiacono said. "Sun's complete line of Solaris and Linux products—including Solaris for the SPARC and x86 platforms, Trusted Solaris, the highly secure operating system, and Sun Linux—are all covered by Sun's portfolio of Unix licensing agreements. As such, Solaris and Sun Linux represent safe choices for those companies that develop and deploy services based on Unix systems."

  • Darl McBride, February 26, 2003, eWeek:
    SCO CEO Darl McBride on Wednesday declined to confirm or deny reports eWEEK has received that SCO is preparing to launch such legal action. But he did confirm that the Lindon, Utah-based firm is expecting to make at least $10 million in revenue in the current financial quarter from its SCOsource licensing initiative.

    SCO, formerly Caldera International Inc., recently created the SCOsource division to create new licensing programs and products for its intellectual property.

    That move followed news last month that the firm was planning to make some users pay for some Unix software they were running, unlicensed, on Linux.

    The first deliverable from SCOsource was the licensing of its Unix shared libraries under a new product license called SCO System V for Linux. That product lets Linux customers run Unix applications, originally written for SCO OpenServer and SCO UnixWare, under Linux in an Intel environment....

    McBride said SCO expected revenue for the second quarter, ending April 30, 2003, to be in the range of $23 million to $25 million. That forecast was based on anticipated revenue from its current operating platforms of $13 million to $15 million, and from $10 million in revenue from its SCOsource licensing initiative.

  • Darl McBride, August 15, 2003, in ZDNET:
    The company said it earned $3.1m (£1.94m), or 19 cents per share, during its fiscal third quarter, compared with a loss of $4.5m, or 35 cents a share, in the year-ago quarter. The company said third-quarter revenue was $20.1m, up from $15.4m a year ago.

    The company said $7.3m of its revenue for the quarter, which ended on 31 July, came from its SCOsource licensing division, which is charged with protecting SCO's Unix-related intellectual property. The company also said it expected fourth-quarter revenue to grow to between $22m and $25m due to expected growth of the SCOsource licensing plan.

    "The magnitude of our SCOsource licensing opportunities and our confidence in the SCOsource revenue pipeline is growing each quarter," the company's chief executive, Darl McBride, said in a statement.

  • Darl McBride, July 10, 2003, ZDNET:
    Speaking to the press in Tokyo Wednesday, Darl McBride, the CEO of SCO Group, repeated his claims that the Linux operating system has source code lifted from Unix.

    He also denied reports that he had come to Japan specifically to meet members of the newly-formed Consumer Electronics Linux Forum.

    "I am here to speak to large Linux vendors about their businesses, so that both sides can find mutually acceptable solutions for the alleged Linux IP infringement issues," said McBride in response to the question about the purpose of his visit to Japan.

    He referred to the lawsuit that SCO filed against IBM as a weapon of last resort, and that he would like to avoid using it again.

    "Actually, Microsoft and Sun Microsystems discussed with us, and got licenses from us. I expect we can repeat it with some Japanese counterparts," said McBride.

    He added that SCO and Hewlett-Packard were in discussions about Unix licensing. However, he did not reveal the names of companies he would meet during the visit.

  • Microsot's Brad Smith, quoted on May 18, 2003 in ZDNET, Microsoft to license Unix code:
    Microsoft will license the rights to Unix technology from SCO Group, a move that could impact the battle between Windows and Linux in the market for computer operating systems.

    According to a statement from Microsoft, the company will license SCO's Unix patents and the source code. That code is at the heart of a $1 billion lawsuit between SCO and IBM, which is aggressively pushing Linux as an alternative to Windows in corporate back shops....

    Late Sunday, Microsoft general counsel Brad Smith said acquiring the license from SCO "is representative of Microsoft's ongoing commitment to respecting intellectual property and the IT community's healthy exchange of IP through licensing. This helps to ensure IP compliance across Microsoft solutions and supports our efforts around existing products like services for Unix that further Unix interoperability." The pact was first reported by the Wall Street Journal.

  • Robin Bloor, IT Director:
    Now Microsoft has stepped in and licensed the source code and patents associated with the Unix operating system from SCO. The stated purpose is to ensure that Microsoft's software complies with SCO's intellectual-property rights and that it can ensure compatibility with Unix software. However, few people believe that to be the major reason for the deal. Most probably, Microsoft wants to stir up the whole argument in the hope of stemming the Linux tide.

    Chris Sontag of SCO immediately claimed that the Microsoft licensing agreement reflected the strength of its intellectual-property suit against IBM. I'm not sure how his logic works here. If IBM already has a license - irrevocable, fully paid up, perpetual etc. then the real implication is that Microsoft was worried that it might have infringed intellectual property. This is possible as Microsoft developed its own version of Unix in the 1980s.

  • Stephen Shankland, July 10, 2003, News.com Sun expands Unix deal with SCO:
    A previously secret licensee of SCO Group's Unix intellectual property has revealed its identity: Unix leader Sun Microsystems.

    SCO's Unix licensing plan got a major boost of publicity in May when Microsoft announced its decision to license Unix from SCO, but Sun actually was the first company to sign on. SCO and Sun confirmed the licensing deal on Wednesday. The pact, signed earlier this year, expanded the rights Sun acquired in 1994 to use Unix in its Solaris operating system. But there's more to the relationship: SCO also granted Sun a warrant to buy as many as 210,000 shares of SCO stock at $1.83 per share as part of the licensing deal, according to a regulatory document filed Tuesday.

    Sun, the No. 1 seller of Unix servers, declined to comment on the option to take a stake in SCO Group. Fortune on Monday published news of the expanded Sun contract.

    Sun's expanded license permits Sun to use some software from Unix System V Release 4 for software components called drivers, which let computers use hard drives, network cards and other devices. Sun needed the software for its version of Solaris that runs on Intel servers, Sun spokesman Brett Smith said. A source familiar with the deal said the new contract was signed in February, but neither Sun nor SCO would comment. ...

    Sun's Smith said the company is being careful to ensure that its Unix intellectual property is "very clean."

    "We've always made sure we're very aboveboard," Smith said. "We've made sure the i's are dotted, the t's are crossed." Before the newest contract was signed, Sun had spent $82 million acquiring rights to use Unix, Smith said. Among Sun's privileges is the right to show Solaris' underlying source code to customers, SCO said....

    Details of Sun's license appeared in a regulatory document that SCO filed to permit various investors to sell 305,000 SCO shares. Of those, 174,000 would be sold by SCO's biggest investor, the Canopy Group, which would see its stake in SCO drop from 41.1 percent to 39.9 percent, according to the filing.

If the Microsoft and Sun licensing agreements were not SCOsource licenses, SCO certainly convinced a lot of people otherwise at the time. By the way, SCO Group didn't have any patent for Microsoft to license, not that has ever come to light that I am aware of. But then, what's a few million between friends? And did you notice that Sun's license covered Linux too, to hear them tell it? So, why isn't that the end of the methods and concepts story right there? If SCO intended to protect methods and concepts, that's a mighty funny way of going about it.

And as long as we're on a truth mission, remember this from Trevor Marshall's interview with Chris Sontag for Byte Magazine, June 16, 2003?

So Why is Linux Being Targeted First?

SCO is targeting Linux first primarily because the Linux source code is open. SCO's lawyers have been poring over the Linux code for much of the past year, looking for fragments and routines which are substantially identical to code from the various releases of UNIX. SCO's "experts" have also found sections of code which SCO believes have been obfuscated—where the order of code execution has been rearranged in a direct attempt to hide its SCO pedigree.

But SCO has been even more thorough. After sifting through e-mails from the Linux developers' mailing list, Sontag says SCO has examples of programmers from AT&T licensees offering to write UNIX code into Linux, and can identify where those UNIX fragments turned up in the codebase.

The lawyers were sifting through emails from LKML for a year? Which lawyers? That takes us back to the summer of 2002, which is when McBride was hired, not January of 2003, as they told the SEC, above, and which is the date Boies Schiller was retained. So, when McBride told Bloomberg News, as reported in the Salt Lake Tribune, the following in August of 2003, was it accurate?

Chief Financial Officer Robert Bench began the selling by SCO insiders, four days after SCO filed the suit against IBM. Bench is selling to help pay a $150,000 tax bill, McBride said. Under the Sarbanes-Oxley law, companies are no longer able to loan executives money to pay taxes or other expenses.

Bench submitted a sale plan in January, months before any legal action against IBM was contemplated, McBride said. His agreement called for the sales to begin on March 8. He planned to sell 5,000 shares a month for the next 12 months, according to the plan.

Just exactly when did SCO begin contemplating legal action, if its lawyers were sifting though Linux kernel message boards looking for evidence in 2002? And are these the emails that SCO just filed in December with the court, their "evidence" of allegedly misused materials? After all the code that SCO got the court to order IBM to turn over, they end up filing a bunch of emails it seems they had before discovery began?

But might I inquire, if they told Byte Magazine in 2003 that they could trace from the emails precisely where code ended up in Linux, why aren't they telling the court now by file, line and version?

Man, it gets confusing when their story keeps changing. At some point, SCO will have to pick a story and not only stick to it, it will have to prove it. And then the words of Robert Frost will be more applicable than Yogi's: that when you came to a fork in the road, the direction you took ends up being what makes all the difference.

That's poetry for you reap what you sow.


PS: Here's Robert Bench's certification attached to the April 2003 SEC filing. Darl's certification.

And Rule 11 of the Federal Rules of Civil Procedure requires the following:

(b) Representations to Court.

By presenting to the court (whether by signing, filing, submitting, or later advocating) a pleading, written motion, or other paper, an attorney or unrepresented party is certifying that to the best of the person's knowledge, information, and belief, formed after an inquiry reasonable under the circumstances,--

(1) it is not being presented for any improper purpose, such as to harass or to cause unnecessary delay or needless increase in the cost of litigation;

(2) the claims, defenses, and other legal contentions therein are warranted by existing law or by a nonfrivolous argument for the extension, modification, or reversal of existing law or the establishment of new law;

(3) the allegations and other factual contentions have evidentiary support or, if specifically so identified, are likely to have evidentiary support after a reasonable opportunity for further investigation or discovery; and

(4) the denials of factual contentions are warranted on the evidence or, if specifically so identified, are reasonably based on a lack of information or belief.

(c) Sanctions.

If, after notice and a reasonable opportunity to respond, the court determines that subdivision (b) has been violated, the court may, subject to the conditions stated below, impose an appropriate sanction upon the attorneys, law firms, or parties that have violated subdivision (b) or are responsible for the violation....

Subdivisions (a) through (c) of this rule do not apply to disclosures and discovery requests, responses, objections, and motions that are subject to the provisions of Rules 26 through 37.


  


When you come to a fork in the road... | 430 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Corrections Here
Authored by: feldegast on Sunday, May 21 2006 @ 10:28 PM EDT
So PJ can find them

---
IANAL
The above post is (C)Copyright 2006 and released under the Creative Commons
License Attribution-Noncommercial 2.0
P.J. has permission for commercial use

[ Reply to This | # ]

Off Topic
Authored by: feldegast on Sunday, May 21 2006 @ 10:29 PM EDT
Please make links clickable

---
IANAL
The above post is (C)Copyright 2006 and released under the Creative Commons
License Attribution-Noncommercial 2.0
P.J. has permission for commercial use

[ Reply to This | # ]

Splendid
Authored by: kberrien on Sunday, May 21 2006 @ 10:47 PM EDT
Absolutely splendid!

[ Reply to This | # ]

Please don't confuse me with the facts
Authored by: lsmft on Sunday, May 21 2006 @ 10:56 PM EDT
<eom>

[ Reply to This | # ]

Confusion
Authored by: Anonymous on Sunday, May 21 2006 @ 11:05 PM EDT
I think PJ has confused the SCOSource licensing initiative, or perhaps the intellectual property licensng program named SCOSource, with the SCOsource licensing program.

Look for SCO to have John Cleese clarify the various programs, about which there are no contradictions.

[ Reply to This | # ]

Cross-examination and prior inconsistent statements
Authored by: AllParadox on Sunday, May 21 2006 @ 11:08 PM EDT
This is bread-and-butter for trial lawyers.

The adversary process, executed through incisive cross-examination, has been
called the finest engine for the discovery of truth ever invented by man. I
have taken this statement as truth, for a long time.

The better I got at cross-examination, the more I believed it. Messr's. Pozner
and Dodd helped a great deal, too. I had to travel to that well a number of
times before I had wisdom enough to drink deep.

I still say that Bill Gates himself did not have enough money to hire a law firm
to do as much for Linux and open-source as has been done by "The SCO
Group" and their lost traffic-ticket lawyers.

Eventually, this will all be over. Until then, they keep adding to the
collection of inconsistencies.

If any part of any of these cases ever gets to trial, the biggest job of the
attorneys for "The SCO Group" will not be persuading a fact-finder of
the truth of their presentation, the biggest part will be persuading the
fact-finder that *this* is what they are actually claiming, as opposed to all
the other claims that they have made.

I still have some sympathy for the poor sod at the bottom of B,S,&F. He or
she is sampling the worst of legal practice right now.

---
PJ deletes insult posts, not differences of opinion.

AllParadox; retired lawyer and chief Groklaw iconoclast. No legal opinions,
just my opinion.

[ Reply to This | # ]

The Big Lie continues
Authored by: SpaceLifeForm on Sunday, May 21 2006 @ 11:08 PM EDT
Link.

---

You are being MICROattacked, from various angles, in a SOFT manner.

[ Reply to This | # ]

    That's not a lie...
    Authored by: chrisbrown on Sunday, May 21 2006 @ 11:19 PM EDT
    ...it's a terminological inexactitude. Also, a tactical misrepresentation.
    - Alexander Haig

    [ Reply to This | # ]

    SCOSource division vs. SCOSource license program
    Authored by: hardmath on Sunday, May 21 2006 @ 11:22 PM EDT

    In a previous article's thread I described this very response as SCO's
    "quibble" about the Sun and MS licenses as having been negotiated
    through the SCOSource division without being part of the SCOSource license
    program.

    It seems to me likely that SCO wishes to maintain that 1) the SCOSource license
    program is only "protecting" Linux customers for the binary use of
    their product (and provides no protection to those who -- gasp -- may edit the
    underlying source code that embodies SCO's IP of some flavor), and 2) that the
    Sun and MS licenses (which could not conceivably be of this nature) are -- take
    SCO's word for it, please -- not reviewable by Novell even as evidence in this
    dispute over their respective rights under the APA.

    Nice try SCO, but that is unlikely to fly except in extreme meteorological
    circumstances. Pray for a tornado to strike Utah real soon now.


    regards, hm


    ---
    Well, when the President does it, that means it is not illegal. -- Nixon, 1977
    interview with David Frost

    [ Reply to This | # ]

    When you're in a hole .....
    Authored by: Anonymous on Sunday, May 21 2006 @ 11:22 PM EDT
    you really should stop digging!

    In this case, it looks like SCO is not only digging their own graves but
    filling it in behind them as they go. One wonders how much air they have left?

    <shakes head>

    Don K.

    [ Reply to This | # ]

    Back and back
    Authored by: Anonymous on Sunday, May 21 2006 @ 11:47 PM EDT
    If the lawyers started sifting in 2002, how long had things gone on for before?
    They would have had to recognise the problem, develop a stratergy, hire the
    lawyers etc. That takes time. Could a start date been 2001? I recall Mad
    Scientist and BrianS looking into a starting time around the time of the Caldera
    settlement. Yarrow the boy on the inside?

    Tufty

    [ Reply to This | # ]

    • Strategy? - Authored by: Anonymous on Monday, May 22 2006 @ 02:47 AM EDT
      • Strategy? - Authored by: LarryVance on Monday, May 22 2006 @ 08:34 AM EDT
      • Strategy? - Authored by: Anonymous on Monday, May 22 2006 @ 04:52 PM EDT
    • Strategy - Authored by: argee on Monday, May 22 2006 @ 03:42 AM EDT
    Slightly OT: When you come to a fork in the road...Sneeze on It
    Authored by: Dave23 on Monday, May 22 2006 @ 12:02 AM EDT
    Also caught in both SEC filings:
    ... These licenses led to the development of several proprietary UNIX-based operating systems, including our own SCO UnixWare and SCO OpenServer, Sun’s Solaris, IBM’s AIX, SGI’s IRIX, HP’s UX, Fujitsu’s ICL DRS/NX, Siemens’ SINIX, Data General’s DG-UX, and Sequent’s DYNIX/Ptx. We believe these operating systems are all derivatives of the original UNIX source code owned by us.
    And thus SCO's arbitrary contagion theory of contract-non-disclosure-and-consequential-copyright-violation á là methods-and-concepts (on top) was borne onto the unsuspecting World.

    At least they've been consistent about that, although they've tried to hide the topic and keep it from being discussed explicitly before the court as long as possible. </sarcasm>

    IANAL

    ---
    Gawker

    [ Reply to This | # ]

    PJ, I don't believe you...
    Authored by: Anonymous on Monday, May 22 2006 @ 12:32 AM EDT
    when you say you do not enjoy 'outing' liars. Your glee comes through clearly
    in this thread. It also confirms what I said some time ago, Darl is not smart.
    Certainly not smart enough to concoct this travesty, and pull if off. The
    'smart' ones looked for someone lacking morals, judgement, and with a background
    in extortion. KEEP UP THE GOOD WORK, PJ. I trust Darl, at el will not sleep
    well tomorrow night.

    [ Reply to This | # ]

    I think scox is safe with this
    Authored by: Anonymous on Monday, May 22 2006 @ 12:37 AM EDT
    Of course scox is lying, we've known that for years. And, of course, scox will
    eventually lose this bogus case, we've all know that also.

    At this point, it's all about keeping the scam on life support for the sake of
    msft PR/FUD; and to keep their jobs etc.

    Scox can tell the courts that scox is lying to the SEC. And scox can tell the
    SEC that scox is lying to the courts. That's if the issue ever comes up, and I
    doubt it will.

    It will be a verifiable fact that scox is lying about something, but what? Scox
    can dance around that issue forever.

    JMHO.

    [ Reply to This | # ]

    When you come to a fork in the road...
    Authored by: sef on Monday, May 22 2006 @ 12:39 AM EDT

    So... as this appears to me, TSG's options are that either they committed perjury with the Court, or they committed perjury (and fraud) with the SEC filing

    That's... an interesting position to be in, isn't it?

    [ Reply to This | # ]

    What I've learned from this.
    Authored by: Anonymous on Monday, May 22 2006 @ 12:42 AM EDT
    It's ok to lie.

    On TV, they make perjury out to be this big deal. In real life, the courts
    don't care. Well maybe if you lie and send someone to prison, or lie and help
    them get found innocent when they shouldv'e been guilty, but in civil cases, lie
    your shoes off... you won't get in trouble.

    And the SEC doesn't care either, unless you are a big fry. They just have
    priorities. If you are small.. little lies on your SEC filings will go through.
    The people in authority don't care.

    [ Reply to This | # ]

    When you come to a fork in the road...
    Authored by: Anonymous on Monday, May 22 2006 @ 12:47 AM EDT
    In Yogi's case, he was giving directions on how to find his house, which is at
    the top of a loop road. It didn't matter which side of the fork you took, it
    was about the same distance either way.

    [ Reply to This | # ]

    The two key sentences
    Authored by: Anonymous on Monday, May 22 2006 @ 12:49 AM EDT
    Quite often in reading NewSCO's documents, there is so much that is
    objectionable, that rejoinders become like targeting one fish out of a school,
    your have trouble picking a starting point.

    But I think there are two sentences from the 10Q that are going to award Novel
    those NewSCO licencing fees:
    "These license agreements will be typical... in that they are ... licenses
    to utilize the UNIX source code...."
    and the subsequent sentence:
    "The amount that we receive from any such licensee will generally depend on
    the license rights that the licensee previously held and the amount and level of
    our intellectual property the licensee desires to license."

    Because they used the word "the" in front of "UNIX source"
    and provided for customized licences, the reader understands they mean ALL the
    code, except where an individual licence limits what is licenced. "ALL the
    code" necessarily includes the Novell controlled old code.

    Remember, NewSCO had the right to create a new software product, and licence
    that product for their exclusive revenue stream. They didn't have the right to
    issue new or revised licences for the old UNIX code, or to capture revenue from
    that old UNIX code, without Novell's permission.

    Unless those SUN/MS licences explicly limited the licencing to the new software
    product's code, not even BSF can tap dance around these two sentences.

    The 10Q makes almost the same statements in several location throughout, but
    these two sentences are the most concise version that I could see. Gee do ya
    wonder why NewSCO doesn't want to give Novell a copy of those licences?

    IANL, IDEPOOTV
    JG

    [ Reply to This | # ]

    SCOsource whateveryouwant
    Authored by: IMANAL on Monday, May 22 2006 @ 01:13 AM EDT
    Could it be that simple that they play with words? Note how Novell use SCOsource program whereas SCO calls it something else. Maybe SCO can get away with this as their internal SCOspeak probably had numerous very similar terms for a whole suite of subtle but important distinctive businesses; think of the break-up of OldCaldera into NewCaldera1., NewCaldera2, and Dump, one of which later rename into NewSCO.

    Novell, #50: As part of the SCOsource program, SCO entered into at least two license agreements.

    SCO, #50: Admits that SCO, through its SCOsource division, entered into agreements related to UNIX and UnixWare with Sun Microsystems, Inc., and Microsoft Corporation (in that order) and that the Microsoft agreement covered UNIX compatibility products; but denies each and every other allegation of ¶ 50, including the allegation that the Sun and Microsoft agreements were part of the SCOsource licensing program.


    ---
    --------------------------
    IM Absolutely Not A Lawyer

    [ Reply to This | # ]

    When you come to a fork in the road...
    Authored by: gbl on Monday, May 22 2006 @ 03:09 AM EDT
    It's fairly obvious that TSG is using a quantum superposition world view where
    all possible paths are taken simultaniously.

    Only when observed does their state collapse.

    (Insert here a very clever joke about Schrodinger's SCO which I can't quite work
    out.)



    ---
    If you love some code, set it free.

    [ Reply to This | # ]

    What is the difference between a duck?
    Authored by: thorpie on Monday, May 22 2006 @ 03:38 AM EDT
    There is apparently an answer to this and I think that SCO should possibly find
    out what it is.

    ---
    The memories of a man in his old age are the deeds of a man in his prime -
    Floyd, Pink

    [ Reply to This | # ]

    Compuware and SCOSource
    Authored by: kb8rln on Monday, May 22 2006 @ 03:47 AM EDT

    If I remember correctly. Compuware needed some UNIX licenses and got SCOScource instead. Then SCOG said we sold a SCOSource licence to Compuware. Compuware said they did not buy SCOSource licences they where paper clip in. Can someone help me find the quote.

    Who knows maybe all UNIX licences now come with a FREE SCOSource Licence. Then SCO is telling the true. :-)

    Enjoy,


    Richard Rager
    http://penguinman.com


    ---
    Director Of Infrastructure Technology (DOIT)
    Really this is my Title so I not a Lawyer.

    [ Reply to This | # ]

    The Producers
    Authored by: Chaosd on Monday, May 22 2006 @ 03:57 AM EDT
    When the dust settles all this fluff and bluster will make a good film script - sort of like the 'Producers', except instead of a crap musical of questionable taste, it's a dubious legal claim of questionable motive. All we need now is Darl in fishnets leading the big dance number and SCO, finally, have a hit (although critics will complain it runs for too long, and the plot is too predictable).

    ---
    -----
    No question is stupid || All questions are stupid

    [ Reply to This | # ]

    For many years
    Authored by: Anonymous on Monday, May 22 2006 @ 04:35 AM EDT
    I was a scientist before transferring to the murky world of the sysadmin. There
    is a well known saying amongst Scientists of all colours "Science's
    greatest tragedy, a beautiful theory spoiled by an ugly fact". Bunglers
    Schyters & Fool are co-opting this in a misquoted form "Sco's greatest
    tragedy, an ugly scam, spoiled by a million inconvenient facts, quotes, lies,
    evasions..."

    [ Reply to This | # ]

    • For many years - Authored by: Anonymous on Tuesday, May 23 2006 @ 07:46 PM EDT
    When you have eliminated all other possibilities...
    Authored by: Anonymous on Monday, May 22 2006 @ 04:49 AM EDT
    In keeping with PJs reference to Yogi Berra, I'll base these comments on the
    words of the great [though fictional] detective, Sherlock Holmes.

    The full meme is something to the effect of,

    "When you have eliminated all other possibilities, whatever is left, no
    matter how improbable, is the truth."

    So we've seen the shifting sands of TSGs explanations to various courts and
    financial regulators. We will no doubt see them twist and wriggle and perhaps
    use weasel words to explain to various authorities how they did not mis-state
    themselves, but it was merely a case of that pesky Pamela Jones and her FOSS
    Community Posse all ganging up on them.

    Frankly, I don't care about that.

    I'm much more interested in where this is all going.

    Here is my theory, for what it's worth.

    Nowhere in all of the legal explanations we have seen so far, is there anything
    to say that TSG have to stop their research into the discovery documents at any
    point in time. So they can pay researchers to trawl everything that IBM provided
    right up to and during any court case, and both legal teams know this.

    Assuming [and I'll concede this is a big assumption on my part] that TSG+BSF
    survive the PSJ motions and other motions to limit claims filed by or about to
    be filed by IBM, this whole mess goes to court.

    We've seen from transcripts and other discussions the idea that it is in the
    interests of the plaintiff to withold as much of their specific allegations from
    the defendant until trial. That's just basic courtroom tactics for people
    working for TSG. One thing we've also learned, to my absolute dismay, is the
    willingness of BSF to perhaps re-interpret legal ethics on this case.

    So my prediction is very simply that, come any court action in this case
    [assuming we're talking here about TSG as the plaintiff] they will announce to
    the court one morning, "See here, your Honour, last night our diligent
    researchers, who are still working their way through that horrible haystack of
    code those pesky IBM people dumped on us, they found this infringing code!"


    I am not, specifically, speculating that there will be any truth or significance
    in claims that may emerge in this way. What I am saying, instead, is that the
    means by which they are introduced would give Cravath, Swaine and Moore, not to
    say IBM too, absolutely zero opportunity to research and respond.

    We've seen Todd Shaunnessy make exactly this argument before the court, and
    we've seen TSG's legal team deny it utterly. Yeah, right.

    BSF might have made a big mistake in taking on this case, but don't anybody take
    them for fools. David Boies is a powerful and capable litigator, and if my
    memories of the DoJ vs Microsoft case are still accurate, he knows exactly how
    to keep a defendant dancing around to his tune.

    I would say that it is the threat of this court action, and nothing else, that
    TSG/BSF are trying to use to encourage IBM to settle out of court. After all,
    they have nothing else.


    A final thought on methods and concepts, with perhaps a question or two thrown
    in for good measure. TSG have been looking for a ladder theory, a series of code
    examples that show how SysV code went from TSG controlled source through an
    intermediate like Dynix/PTX or AIX and wound up in Linux. Based on what we've
    seen, they have no direct examples and are now talking methods and concepts.

    Say this goes to court. Say TSG point to some NUMA code in Linux which was
    donated by an IBM employee. Their accusation is that it uses a method or concept
    found in SVR4. Say IBM call up a witness who says, "But your honour, I got
    the ideas for this code from a friend of mine who works on [ OS/390 {zOS}, or
    OS/400, or OS/2 : delete as appropriate] and [s]he got the idea from the
    university course they attended, where this was part of the syllabus..."

    Because TSG cannot point to their ladder theory code, and can only quote a
    method or concept, they cannot prove, beyond reasonable doubt, that the
    "method" or "concept" came directly from unix. It *could*
    have come from anywhere... What jury would find otherwise?

    One of the reasons that I think the above argument would stand up in court is
    the hardware platform we are talking about. TSG have argued that it is only
    their IP that properly exploited the "PC" platform, that before Xenix
    et al there were no good examples of an OS on the platform.

    Two thoughts: firstly, has anyone paid any attention to the rate at which the
    kernel, KDE, MySQL, PHP, Apache and any one of a score of popular FOSS projects
    have improved *since* this case started. I think that provides a body of
    evidence to suggest that FOSS developers get along just fine on their own, thank
    you very much.

    Secondly, and perhaps more importantly, we have to consider the hardware being
    used. When all is said and done, the hardware of your average multi-processor PC
    is largely a commodity item. There are only so many ways that you can write
    low-level software [ie the device drivers and components such as NUMA] that will
    still work within the constraints put in place by that hardware.

    In other words, given the underlying restrictions of of a platform, if you set
    up a challenge to write some NUMA code for the PC architecture from scratch, and
    defined the basics of the target OS, then got 1000 programmers to write the
    code, exactly how much variation would you expect to see in the results? I'd
    argue that there would be many near-exact duplications, even if those developers
    had no contact with eachother.

    If this is going down to a burden of proof argument, I see all the cards stacked
    in IBM's favour, UNLESS TSG are holding back a handful of un-dealt cards...

    Anyone care to comment on the viability of my argument regarding common hardware
    producing similar code? It might help...

    Thanks

    sproggit

    [ Reply to This | # ]

    Great find again, PJ
    Authored by: Anonymous on Monday, May 22 2006 @ 05:32 AM EDT
    Like yesterday and the day before, the collective effort to lift your confusion
    made everything clear again for most of us.
    I hope it helped.
    The SCOSource licensing program under which SCO sells the SCO IP License for
    Linux is part of the activities deployed under the SCOSource licensing
    initiative.
    Don't blame SCO for your stupefying lack of comprehension.
    Leave that to Novell.

    [ Reply to This | # ]

    Why?
    Authored by: Alan(UK) on Monday, May 22 2006 @ 05:35 AM EDT
    I ask myself, "Why did SCO add that phrase to their reply?"

    In other places they are prepared to make very non-specific replies like,
    "Admits that SCO made statements (correctly quoted in part in ¶
    53)..."

    They could perfectly well ended their reply to paragraph 50 with, "...but
    denies each and every other allegation of ¶ 50." It would not actually
    change the meaning at all.

    But what that does not make clear is that SCO considers that the rather
    innocuous initial phrase, "As part of the SCOsource program," is in
    dispute.

    Why should SCO want to dispute that? Because SCO does not want the Novell
    lawyers defining what is meant by the "SCOsource program". After all,
    if you invent a word (and I suppose it is a registered trademark), you have the
    right to give it its initial meaning. SCO want to give themselves room to make
    adjustments to the meaning before it becomes set in stone.

    Sorry, but I think that it is as unexciting as that.

    [ Reply to This | # ]

    • Because - Authored by: Anonymous on Monday, May 22 2006 @ 11:17 AM EDT
    • Why? - Authored by: TomWiles on Tuesday, May 23 2006 @ 01:02 PM EDT
    They lied to the SEC
    Authored by: Anonymous on Monday, May 22 2006 @ 05:52 AM EDT
    "We have discovered that UNIX source code and unauthorized derivatives of
    UNIX source code are prevalent in the Linux kernel."

    Not methods and concepts. Source code. And that's what they told the SEC that
    they knew - KNEW - back then. The dozen or so actual source code claims (if
    that) in their suit - after years of discovery and full access to IBMs RCS - do
    not amount to "prevalent".

    Why is Darl not in jail?

    [ Reply to This | # ]

    Why did they bother?
    Authored by: rsteinmetz70112 on Monday, May 22 2006 @ 10:54 AM EDT
    They admit entering into the agreements, why did they take specific exception to
    those agreements being part of SCOsource?

    The important point is whether the agreements are about SysV, not whether they
    are SCOsource. Why not simply deny everything and deal with it later? That would
    seem the normal, standard, almost boring form of response. Why call attention to
    SCOsource? Just so PJ could write this article?

    I suspect Darl is involved in practicing law again and has some weird hang up on
    SCOsource.

    ---
    Rsteinmetz - IANAL therefore my opinions are illegal.

    "I could be wrong now, but I don't think so."
    Randy Newman - The Title Theme from Monk

    [ Reply to This | # ]

    So what unix rights did sun actually get
    Authored by: Anonymous on Monday, May 22 2006 @ 11:48 AM EDT
    I kinda wonder if they even have the right to Open Source Solaris as they said
    they did. It seems like they have some rights to show code to some people, but
    it's not at all clear to me how far those rights extend.

    [ Reply to This | # ]

    When you come to a fork in the road...
    Authored by: Anonymous on Monday, May 22 2006 @ 12:04 PM EDT
    IF SCO's lawyers have been looking at the code for a year before they brought
    the suit, then the "reporter" who recently wrote that this has been
    going on for four years was right! Does that imply that the reporter was
    looking at an internal time-line?

    [ Reply to This | # ]

    Simple
    Authored by: Anonymous on Monday, May 22 2006 @ 12:23 PM EDT
    They made a mistake in their SEC filing. They will need to send an update to
    the SEC.

    [ Reply to This | # ]

    • Simple - Authored by: stend on Monday, May 22 2006 @ 05:11 PM EDT
      • Simple - Authored by: Anonymous on Tuesday, May 23 2006 @ 09:42 AM EDT
    Santa Cruz failed in their fiduciary responsibility
    Authored by: GLJason on Monday, May 22 2006 @ 01:21 PM EDT
    Caldera only spent $6 million for the technology they bought from Santa Cruz (about $60 million of the purchase price was "goodwill", the other $30 million was for the distribution channel). Here they say Sun spent $82 million just for expanded rights to the unix code. SCO got "SCOSource" licenses from Sun and Microsoft worth tens of millions. SCO is suing IBM for billions. Clearly Santa Cruz didn't shop around for a buyer. If I owned Tarentella stock, I would start a class-action lawsuit because they sold such a valuable asset so cheaply.

    In the alternative, maybe Santa Cruz was just selling their 32-bit x86 operating system and never had the copyrights to UNIX to begin with...

    [ Reply to This | # ]

    PJ's Irish?
    Authored by: finman on Monday, May 22 2006 @ 02:43 PM EDT
    "Maureen was calling PJ a Harrigan, . . ."

    I think you meant harridan, which was an insult. There are many that would take
    being referred to as Irish as a compliment.

    ---
    "Remember, no matter where you go, there you are." Pigkiller, Mad Max Beyond
    Thunderdome

    [ Reply to This | # ]

    When you come to a fork in the road...
    Authored by: Anonymous on Monday, May 22 2006 @ 08:38 PM EDT
    What's one little lie between friends -- the Federal government -- judges --
    investors -- corporations -- the press ... ???

    [ Reply to This | # ]

    Initiating securities fraud investigation
    Authored by: Anonymous on Monday, May 22 2006 @ 09:42 PM EDT
    I am a danish citizen and there is something I have never quite understood. Here
    it seems some crimes need to be reported to the police before they can start an
    investigation, while the rules may be different in USA I am sure you have
    something similar. Can anyone explain your rules?
    I am basically wondering what needs to happen before SEC can start an
    investigation. Could a shareholder who feels defrauded by SCOX be needed to
    report it to police/SEC before they can start investigation?
    I allmost wish I bought a share back then, not only could I report them to
    police. Attending shareholder meetings could be fun too ;-) In my country we
    have a political party that makes even the most liberal americans seem like
    bible wielding conservative fashists by comparison, who have bought shares in
    big multinational compagnies just for the sake of creating havoc at shareholder
    meetings. I imagine some of the people here could create an
    "interesting" atmosphere at SCOX shareholder meetings too ;-)

    [ Reply to This | # ]

    Is this really a complete turn around?
    Authored by: Anonymous on Monday, May 22 2006 @ 09:57 PM EDT

    I'm still searching for the quotes (perhaps someone could point out some candidates) but I thought that TSG had always claimed the Sun and MS licenses were "regular Unix licenses".

    Sure this was grosely misrepresented in the SEC filings but everywhere else, I think TSG always called them Unix licenses not licenses for binary only use of Linux.

    Ironically, SCOsource licenses didn't cover source code, just binaries. They really do grapple with computing concepts don't they? They new that they would face massive numbers of civil suits including class actions if they started selling licenses or invoicing linux users.
    See: letter from GL to SCO
    "Should we receive invoices from you, we will initiate civil actions under the anti-fraud and consumer protection statutes wherever we live, according to our respective circumstances. We also intend to contact our state attorneys general to request that they seek criminal as well as civil penalties against you, in addition to injunctive relief. In addition, we will file complaints with the FTC and other federal and state agencies, as appropriate. Some individuals have already sent letters to legislators in their respective states and in Washington, DC."

    They knew it would be a really bad idea to sell the SCOsource licenses they wanted to but they had to let the shareholders think thier diabolical plan was working

    $0.02

    [ Reply to This | # ]

    Will Microsoft sue SCO?
    Authored by: Anonymous on Wednesday, May 24 2006 @ 05:29 PM EDT
    ..." Now Microsoft has stepped in and licensed the source code and patents associated with the Unix operating system from SCO. "...

    ..." irrevocable, fully paid up, perpetual etc.
    "...

    Did SCO really have the authority to sell a irrevocable, fully paid up perpetual license to any of Unix? From the sounds of Novell, they did not. So this brings up the question of what happens when Novell wins the case brought by SCO. Will this not put Microsoft in harms way, making it necessary to negotinate with Novell for the rights it needs, then having to go back and sue SCO to get it's money back?

    Would Microsoft really sue SCO?

    [ Reply to This | # ]

    • Why? - Authored by: Anonymous on Wednesday, May 24 2006 @ 07:10 PM EDT
    Groklaw © Copyright 2003-2013 Pamela Jones.
    All trademarks and copyrights on this page are owned by their respective owners.
    Comments are owned by the individual posters.

    PJ's articles are licensed under a Creative Commons License. ( Details )