] SCO's references to XFS are completely misplaced. XFS is
] an innovative SGI- created work. It is not a derivative
] work of System V in any sense, and SGI has full rights to
] license it to whomever we choose and to contribute it to
] open source. It may be that SCO is taking the position
] that merely because XFS is also distributed along with
] IRIX it is somehow subject to the System V license. But
] if so, this is an absurd position, with no basis either
] in the license or in common sense. In fact, our UNIX
] license clearly provides that SGI retains ownership and
] all rights as to all code that was not part of AT&Ts UNIX
] System V.

SGI's open letter r.e. SCO

] The SCO Group is extending its royalty campaign to
] encompass Silicon Graphics Inc. The company says it will
] revoke SGI's Irix license on October 14. It's no
] surprise, as SCO CEO Darl McBride has explicitly
] mentioned SGI over a month ago. SGI signed the license
] with AT&T in 1986.

The Register

] SAN JOSE, Calif. (AP) -- Sun Microsystems Inc.'s shares
] plunged more than 15 percent Tuesday after the troubled
] computer maker said it would revise its fourth-quarter
] results to take a $1.05 billion charge.

Oops ...

InformationWeek : Financial News : Sun Stock Plummets After Announcing A $1.05 Billion Charge : September 30, 2003

] Residential fuel cells sound almost too good to be true.
] Take a hydrocarbon fuel such as natural gas, use a
] catalyst to extract hydrogen from it, react the hydrogen
] with air and, presto, you have a home power plant!

Excellent idea!

ScienceDaily News Release: Rating The Performance Of Residential Fuel Cells

] For large UNIX projects, the traditional method of building the
] project is to use recursive make. On some projects, this results in
] build times which are unacceptably large, when all you want to do is
] change one file. In examining the source of the overly long build
] times, it became evident that a number of apparently unrelated
] problems combine to produce the delay, but on analysis all have the
] same root cause.

] This paper explores an number of problems regarding the use of
] recursive make, and shows that they are all symptoms of the same
] problem. Symptoms that the UNIX community have long accepted as a
] fact of life, but which need not be endured any longer. These
] problems include recursive makes which take ``forever'' to work out
] that they need to do nothing, recursive makes which do too much, or
] too little, recursive makes which are overly sensitive to changes in
] the source code and require constant Makefile intervention to keep
] them working.

I'm increasingly of the opinion that make by itself is an inadequate tool. This inadequacy is evidenced by the existence of autoconf, automake and libtool. All of this functionality could be provided by a few perl modules and you would have Makefile.pl or something...

Recursive make Considered Harmful

Also of note: IBM will not indemnify Linux customers:

] In the memo, signed by Robert Samson, an IBM sales
] manager, IBM said that: " Most indemnities are narrowly
] drawn and are often invalidated by customer activities,
] such as making modifications or combining the indemnified
] product with other code, which are central to the
] vitality of open source."
]
] It said the H-P indemnification requirements "will
] inhibit customers from taking full advantage of the open
] source development process."
]
] Mr. Samson's memo says "HP's approach as outlined in the
] press, we believe runs fundamentally counter to the Linux
] value proposition." Many users like Linux because they
] can view the source code making it easy to adapt the
] operating system for their own uses.

IBM Files New Claims Against SCO in Linux Case

Good interview. I keep forgetting about project Monterey ... and how that may have really been the start of this whole mess.

Ransom Love, Co-founder of Caldera and SCO, Speaks of Unix, GPL and the Lawsuit

]
] When SCO CEO Darl McBride wrote his open letter last
] week, he seemed to indicate a hope there could be a
] viable future partnership between his company and Linux.
] There is more than a hint as to what that partnership
] might be like in two research papers prepared back in
] March and April by Renaissance Ventures, a VC firm that
] invested in SCO.

(lots of other good SCO stuff on groklaw today)

This gives some good insight as to what's going on with SCO's stock price and just exactly what crack the investors are smoking. With the new IBM suit filed today, they've dropped another $2.30 (as of midday) to $14.92.

Like I've said before: IBM won't settle -- they can drag out the litigation indefinitely until SCO is bankrupt. Remember that the US tried to sue IBM once ... and threw in the towel after 8 years! SCO's strategy was to bluff IBM into settling before trial -- and IBM called it.

GrokLaw: Visions of Ka-ching Dance in Their Heads

] Particularly controversial was the claim that SCO had the
] capability to launch a wave of invoices within 45 minutes of an
] outbreak of licence infringement.

] This was flatly contradicted by intelligence reports, which
] insisted that the only weapons in the company's armoury were a few
] elderly FUD missiles and the odd bluster bomb.

LOL!

SCO's FUD missiles rain down on the infidel

] LINDON, Utah, Sept. 24 /PRNewswire-FirstCall/ -- The
] following is being issued by The SCO Group (Nasdaq: SCOX
] - News):

Here's SCO's press-release in response to HP. I wonder if Darl is actually so inbred as to believe this nonsense...

HP's Actions Support SCO's Position That Linux is not Free