Project Monterey was an attempt to build a single Unix operating system that ran across a variety of 32-bit and 64-bit platforms, as well as supporting multi-processing. Announced in October 1998, several Unix vendors were involved; IBM provided POWER and PowerPC support from AIX, Santa Cruz Operation (SCO) provided IA-32 support, and Sequent added multi-processing (MP) support from their DYNIX/ptx system.[1] Intel Corporation provided expertise and ISV development funding for porting to their upcoming IA-64 (Itanium Architecture) CPU platform, which was yet to be released at that time.[2] The focus of the project was to create an enterprise-class UNIX for IA-64, which at the time was expected to eventually dominate the UNIX server market.

Logo for Project Monterey

By March 2001, however, "the explosion in popularity of Linux ... prompted IBM to quietly ditch" this;[3] all involved attempted to find a niche in the rapidly developing Linux market and moved their focus away from Monterey. Sequent was acquired by IBM in 1999. In 2000, SCO's UNIX business was purchased by Caldera Systems, a Linux distributor, who later renamed themselves the SCO Group. In the same year, IBM eventually declared Monterey dead.[4] Intel, IBM, Caldera Systems, and others had also been running a parallel effort to port Linux to IA-64, Project Trillian, which delivered workable code in February 2000. In late 2000, IBM announced a major effort to support Linux.[5]

In May 2001, the project announced the availability of a beta test version AIX-5L for IA-64, basically meeting its original primary goal. However, Intel had missed its delivery date for its first Itanium processor by two years, and the Monterey software had no market.[6]

With the exception of the IA-64 port and Dynix MP improvements, much of the Monterey effort was an attempt to standardize existing versions of Unix into a single compatible system. Such efforts had been undertaken in the past (e.g., 3DA) and had generally failed, as the companies involved were too reliant on vendor lock-in[citation needed] to fully support a standard that would allow their customers to leave for other products. With Monterey, two of the key partners already had a niche they expected to continue to serve in the future: POWER and IA-64 for IBM, IA-32 and IA-64 for SCO.

The breakdown of Project Monterey was one of the factors leading to a lawsuit in 2003, where SCO Group sued IBM over their contributions to Linux.

IBM sold only 32 Monterey licenses in 2001, and fewer in 2002.[6][7]

References

edit
  1. ^ Jaikumar Vijayan (February 1, 1999). "Sequent Sketches UNIX/NT Road Map". Computerworld. p. 28. Retrieved 2020-09-29.
  2. ^ Hughes-Rowlands, Richard; Chibib, Ahmed (August 31, 1999). "Project Monterey" (PDF). Retrieved 2020-09-29.
  3. ^ "Caldera loads Linux apps on UnixWare". ZDNet.
  4. ^ Jones, Pamela (April 25, 2005). "More Evidence Project Monterey Partners Knew Linux Was the Future". Groklaw. Archived from the original on June 7, 2007. Retrieved 2007-05-20.
  5. ^ "IBM to spend $1 billion on Linux in 2001". CNET News.com. 2000-12-12. Retrieved 2008-08-19.
  6. ^ a b Jones, Pamela (August 25, 2005). "2002 IBM Internal Email on Project Monterey - "No One Wants It"". Groklaw. Retrieved 2007-05-20.
  7. ^ Borchers, Detlef (2005-08-28). "SCO vs. Linux: 32 mal Monterey". Heise Online. Retrieved 2007-05-20.
edit