Feeds

SCO, Groklaw and the Monterey mystery that never was

Bullets for SCO?

  • alert
  • submit to reddit

Build a business case: developing custom apps

Analysis Over the past two years, the influential web site Groklaw has become a focal point for open source advocates discussing The SCO Group's litigation against Linux companies. The community of knowledgeable experts has helped with clarifying contract technicalities, dug through news archives, and filed on-the-spot reports from the Utah the courtroom, much to SCO's discomfort.

But over the past month the site's maintainer Pamela Jones has run a series of articles which could offer SCO some elusive ammunition to discredit the site. [We now understand this series, after some input from your reporter, has been amended.]

Given the internet's well documented "echo chamber" tendencies, what we'll call the Monterey Mystery is now cementing into an orthodoxy. From a Google search for "Project Monterey" the top six results are either the Groklaw articles, or articles about them.

At least five articles published this month suggest that Project Monterey, the joint Unix that was being co-developed by IBM, the Santa Cruz Operation and Sequent beginning in 1998 was only a "stop-gap" measure. The participants, she asserts, had from the start bet that Linux would supplant their proprietary Unix offerings. And more damningly, she claims that SCO knew this at the time, and has declined to reveal this secret strategy.

"Project Monterey was the stopgap, in a way, I gather. It worked for the enterprise right away, and it was a path to smoothly move to Linux as it matured," wrote Jones.

There is a serious problem with this hypothesis: it isn't true.

(Your reporter bases this conclusion on first hand experience with representatives from IBM, SCO, Compaq and Sequent which included attending four of the week-long SCO Forum events between 1998 and 2001 - reports from which have been cited in the litigation, and widely quoted at Groklaw itself).

Let's examine the Groklaw conjectures, their merit, and see how much damage they could do to the open source defense against SCO, which until now has been both exhaustive and exacting. But first, some history.

Boost IT visibility and business value

Next page: Unix before Linux

More from The Register

next story
Why has the web gone to hell? Market chaos and HUMAN NATURE
Tim Berners-Lee isn't happy, but we should be
Linux turns 23 and Linus Torvalds celebrates as only he can
No, not with swearing, but by controlling the release cycle
Apple promises to lift Curse of the Drained iPhone 5 Battery
Have you tried turning it off and...? Never mind, here's a replacement
Sin COS to tan Windows? Chinese operating system to debut in autumn – report
Development alliance working on desktop, mobe software
Microsoft boots 1,500 dodgy apps from the Windows Store
DEVELOPERS! DEVELOPERS! DEVELOPERS! Naughty, misleading developers!
Eat up Martha! Microsoft slings handwriting recog into OneNote on Android
Freehand input on non-Windows kit for the first time
This is how I set about making a fortune with my own startup
Would you leave your well-paid job to chase your dream?
prev story

Whitepapers

A new approach to endpoint data protection
What is the best way to ensure comprehensive visibility, management, and control of information on both company-owned and employee-owned devices?
Implementing global e-invoicing with guaranteed legal certainty
Explaining the role local tax compliance plays in successful supply chain management and e-business and how leading global brands are addressing this.
Maximize storage efficiency across the enterprise
The HP StoreOnce backup solution offers highly flexible, centrally managed, and highly efficient data protection for any enterprise.
How modern custom applications can spur business growth
Learn how to create, deploy and manage custom applications without consuming or expanding the need for scarce, expensive IT resources.
Next gen security for virtualised datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.