Feeds

SCO, Groklaw and the Monterey mystery that never was

Bullets for SCO?

  • alert
  • submit to reddit

Beginner's guide to SSL certificates

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.

Secure remote control for conventional and virtual desktops

Next page: Unix before Linux

More from The Register

next story
Microsoft on the Threshold of a new name for Windows next week
Rebranded OS reportedly set to be flung open by Redmond
'In... 15 feet... you will be HIT BY A TRAIN' Google patents the SPLAT-NAV
Alert system tips oblivious phone junkies to oncoming traffic
Apple: SO sorry for the iOS 8.0.1 UPDATE BUNGLE HORROR
Apple kills 'upgrade'. Hey, Microsoft. You sure you want to be like these guys?
SMASH the Bash bug! Red Hat, Apple scramble for patch batches
'Applying multiple security updates is extremely difficult'
'Google is NOT the gatekeeper to the web, as some claim'
Plus: 'Pretty sure iOS 8.0.2 will just turn the iPhone into a fax machine'
ARM gives Internet of Things a piece of its mind – the Cortex-M7
32-bit core packs some DSP for VIP IoT CPU LOL
'People have forgotten just how late the first iPhone arrived ...'
Plus: 'Google's IDEALISM is an injudicious justification for inappropriate biz practices'
prev story

Whitepapers

Providing a secure and efficient Helpdesk
A single remote control platform for user support is be key to providing an efficient helpdesk. Retain full control over the way in which screen and keystroke data is transmitted.
Intelligent flash storage arrays
Tegile Intelligent Storage Arrays with IntelliFlash helps IT boost storage utilization and effciency while delivering unmatched storage savings and performance.
Beginner's guide to SSL certificates
De-mystify the technology involved and give you the information you need to make the best decision when considering your online security options.
Security for virtualized datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.
Secure remote control for conventional and virtual desktops
Balancing user privacy and privileged access, in accordance with compliance frameworks and legislation. Evaluating any potential remote control choice.