Hubbry Logo
OpenServerOpenServerMain
Open search
OpenServer
Community hub
OpenServer
logo
8 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Contribute something
OpenServer
OpenServer
OpenServer
View on Wikipedia
from Wikipedia
OpenServer
SCO OpenServer 5.0.7 running the X.desktop interface
DeveloperSCO, Caldera Systems, Caldera International, The SCO Group, Xinuos
OS familyUNIX System V (SVR3.2/SVR5), BSD
Working stateCurrent
Source modelClosed source
Initial release1989; 36 years ago (1989)
Latest release10.3 / 2016; 9 years ago (2016)
Supported platformsIA-32
x86-64 (OpenServer 10)
Kernel typeMonolithic kernel
UserlandPOSIX / SUS
LicenseProprietary
Official websiteOpenServer 6
OpenServer 5
SCO OpenServer Release 5.0.7 box set

Xinuos OpenServer, previously SCO UNIX and SCO Open Desktop (SCO ODT), is a closed source computer operating system developed by Santa Cruz Operation (SCO), later acquired by SCO Group, and now owned by Xinuos. Early versions of OpenServer were based on UNIX System V, while the later OpenServer 10 is based on FreeBSD 10. However, OpenServer 10 has not received any updates since 2018 and is no longer marketed on Xinuos's website, while OpenServer 5 Definitive and 6 Definitive are still supported.

History

[edit]

SCO UNIX/SCO Open Desktop

[edit]

In 1987 AT&T Corporation, Microsoft, and Sun Microsystems agreed to combine their versions of the Unix operating system. Santa Cruz Operation (SCO) sublicensed Microsoft's Xenix and wanted to retain the Xenix name, but AT&T said "If they want to call it Unix, they've got to use it the way it is. We don't want another set of variants".[1]

SCO UNIX was the successor to Xenix, derived from UNIX System V Release 3.2 with an infusion of Xenix device drivers and utilities. SCO UNIX System V/386 Release 3.2.0 was released in 1989, as the commercial successor to SCO Xenix. The base operating system did not include TCP/IP networking or X Window System graphics; these were available as optional extra-cost add-on packages. Shortly after the release of this bare OS, SCO shipped an integrated product under the name of SCO Open Desktop, or ODT. 1994 saw the release of SCO MPX, an add-on SMP package.

At the same time, AT&T completed its merge of Xenix, BSD, SunOS, and UNIX System V Release 3 features into UNIX System V Release 4. SCO UNIX remained based on System V Release 3, but eventually added home-grown versions of most of the features of Release 4.

The 1992 releases of SCO UNIX 3.2v4.0 and Open Desktop 2.0 added support for long file names and symbolic links. The next major version, OpenServer Release 5.0.0, released in 1995, added support for ELF executables and dynamically linked shared objects, and made many kernel structures dynamic.

SCO OpenServer

[edit]

SCO OpenServer 5, released in 1995, would become SCO's primary product and serve as the basis for products like PizzaNet (the first Internet-based food delivery system done in partnership with Pizza Hut) and SCO Global Access, an Internet gateway server based on Open Desktop Lite.[2] To compete with Windows NT and Linux, by 1997 SCO was distributing single-user licenses for educational use for $19, the cost of the CD-ROM, or completely free at trade shows.[3] Due to its large installed base, SCO OpenServer 5 continues to be actively maintained by SCO with major updates having occurred as recently as September 2018.[4]

SCO OpenServer 6, based on the merging of Openserver 5 and large portions of Unixware 7 was initially released by The SCO Group in 2005. It includes support for large files, increased memory, and multi-threaded kernel (light-weight processes). This merged codebase is UNIX System V Release 5 (SVR5) of which the original version is seen in Unixware 7; SVR5 is only used by Xinuos. SCO OpenServer 6 contains the UnixWare 7's SVR5 kernel integrated with SCO OpenServer 5 application and binary compatibility, OpenServer 5 system administration, and OpenServer 5 user environments. Unixware 7 was ironically based on a merger of AT&T UNIX System V Release 4.2MP (Unixware 2) and select technologies from OpenServer 5.[5]

SCO OpenServer has primarily been sold into the small and medium business (SMB) market. It is widely used in small offices, point of sale (POS) systems, replicated sites, and backoffice database server deployments. Prominent larger SCO OpenServer customers include McDonald's, Taco Bell, Big O Tires, Pizza Hut, Costco pharmacy, NASDAQ, The Toronto Stock Exchange, Banco do Brasil, many banks in Russia and China, and the railway system of India.[6][7][8]

UnixWare merger

[edit]
Commemorative cup for the SCO OpenServer 5.0.6 release

SCO purchased the right to distribute the UnixWare system and its System V Release 4 code base from Novell in 1995. SCO was eventually able to re-use some code from that version of UnixWare in later releases of OpenServer. Until Release 6, this came primarily in the compilation system and the UDI driver framework and the USB subsystem written to it.

SCO announced on August 2, 2000, that it would sell its Server Software and Services Divisions, as well as UnixWare and OpenServer technologies, to Caldera Systems, Inc. The purchase was completed in May 2001. The remaining part of the SCO company, the Tarantella Division, changed its name to Tarantella, Inc., while Caldera Systems became Caldera International, and subsequently in 2002, the SCO Group.

Under The SCO Group

[edit]
OpenServer logo at the time of The SCO Group

The SCO Group continued the development and maintenance of OpenServer. On June 22, 2005, OpenServer 6.0 was released, codenamed "Legend", the first release in the new 6.0.x branch. SCO OpenServer 6 is based on the UNIX System V Release 5 kernel, a merged codebase of UNIX System V Release 4.2MP and UnixWare 7. OpenServer 6.0 features multi-threading application support for C, C++, and Java applications through the POSIX interface. OpenServer 6 features kernel-level threading (not found in 5.0.x).

Some improvements over OpenServer 5 include improved SMP support (support for up to 32 processors), support for files over a terabyte on a partition (larger network files supported through NFSv3), better file system performance, and support for up to 64GB of memory.

OpenServer 6.0 maintains backward-compatibility for applications developed for Xenix 286 onwards.[9]

The SCO Group went bankrupt in 2011, after a long series of legal battles.

UnXis / Xinuos (2011–present)

[edit]

The rights to OpenServer, as well as UnixWare, were acquired by UnXis in 2011, which was later renamed Xinuos.

In June 2015, Xinuos announced OpenServer 10, which is based on the FreeBSD 10 operating system. Simultaneously, Xinuos introduced a migration path for existing customers using older OS products. In December 2015, Xinuos released "definitive" versions of OpenServer 5, OpenServer 6, and UnixWare 7.

In December 2017, Xinuos released "Definitive 2018" versions of OpenServer 6 and UnixWare 7, and in October 2018 OpenServer 5 Definitive 2018 was released. The "Definitive 2018" releases were a commitment by Xinuos to keep the legacy OS's updated and supported protecting the applications that customers need to continue to run. The Definitive 2018 products contain major updates over the Definitive releases, and an updated development kit was released which makes it easier to compile current packages for the Definitive 2018 products.

However, by 2023, OpenServer 10 was no longer listed as a product on Xinuos' home page, implying that it had been withdrawn from marketing.[10]

Versions

[edit]
Version Basis Date Codename Editions/Notes
SCO UNIX System V/386 SVR3.2.0 1989 ?
Open Desktop 1.0 SVR3.2.1 1990 ?
Open Desktop 1.1 SVR3.2v2.0 1991 ? Supplement for upgrade to 3.2v2.1
SCO UNIX SVR3.2v4.0 1992 ?
Open Desktop 2.0 SVR3.2v4.1 1992 Phoenix Desktop System, Server
Open Desktop/Server 3.0 SVR3.2v4.2 1994 Thunderbird Open Desktop, Open Desktop Lite, Open Server
OpenServer 5.0 SVR3.2v5.0 1995 Everest Desktop System, Host System, Enterprise System
OpenServer 5.0.2 SVR3.2v5.0.2 1996 Tenzing Desktop System, Host System, Enterprise System, Internet FastStart
OpenServer 5.0.4 SVR3.2v5.0.4 1997 Comet Desktop System, Host System, Enterprise System
OpenServer 5.0.5 SVR3.2v5.0.5 1999 Davenport Host System, Desktop System, Enterprise System
OpenServer 5.0.6 SVR3.2v5.0.6 2000 Freedom Host System, Desktop System, Enterprise System
OpenServer 5.0.7 SVR3.2v5.0.7 2003 Harvey West Host System, Desktop System, Enterprise System
OpenServer 6.0 SVR5 2005 Legend A "merge" of UnixWare 7 and OpenServer 5
OpenServer 5.0.7V SVR3.2v5.0.7 2009 ? OpenServer 5.0.7V import a pre-installed Virtual Appliance/Machine onto the VMware hypervisor.
OpenServer 10 FreeBSD 10 2015 10.0 First release based on FreeBSD 10 and Xinuos enhancements
OpenServer 6 Definitive SVR5 2015 Definitive Upwards compatible with OpenServer 6 Definitive 2018
OpenServer 5 Definitive SVR3.2v5.0.7 2015 Definitive Upwards compatible with OpenServer 5 Definitive 2018
OpenServer 10.3 FreeBSD 10.3 2016 10.3 Release based on FreeBSD & Xinuos enhancements. Update from 10.0 and 10.2
OpenServer 6 Definitive 2018 SVR5 2017 Definitive 2018 In-place upgrade from previous supported versions
OpenServer 5 Definitive 2018 SVR3.2v5.0.7 2018 Definitive 2018 In-place upgrade from previous supported versions

See also

[edit]

References

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

OpenServer

View on Grokipedia
from Grokipedia
Xinuos OpenServer is a closed-source, proprietary operating system originally developed by the (SCO) as a multiuser, multitasking platform for server applications in enterprise environments, particularly suited for low-cost hardware and business-critical tasks like point-of-sale and database operations. Initially released in 1992 as part of the SCO OpenServer family, the system evolved from earlier SCO UNIX products based on AT&T's System V Release 3, providing robust networking, remote administration, and compatibility with legacy applications that continue to rely on its stability decades later. Key versions include OpenServer 5, which introduced enhancements like improved scalability and support for modern peripherals, and OpenServer 6, featuring large file support, kernel-level threading, and broader application compatibility to extend its viability against newer alternatives. Following SCO's financial troubles and acquisition by (later the ), maintenance and updates passed to Xinuos, ensuring ongoing support amid the OS's niche persistence in sectors resistant to migration due to embedded custom software.

Historical Development

Origins in SCO UNIX and SCO Open Desktop

The (SCO), founded in 1979 by Doug and Larry Michels, began as a Unix porting and consulting company specializing in adaptations for x86 processors. Early efforts involved collaboration with on , resulting in SCO's release of SCO XENIX System V/386 in 1983, a commercial Unix derivative based on System III with BSD-like enhancements, targeted at 8086, 286, and 386 architectures for and multi-user environments. This system emphasized reliability and compatibility for hardware, establishing SCO's focus on affordable Unix variants outside mainframe ecosystems. By the late 1980s, SCO shifted from to AT&T's System V Release 3 (SVR3), launching SCO UNIX System V/386 in as a certified SVR3.2 implementation optimized for 32-bit processors, including features like enhanced networking and real-time extensions for enterprise workloads. SCO UNIX prioritized backward compatibility with Xenix applications while incorporating SVR3's standardized development environment and binary portability, making it suitable for servers and workstations in small to medium businesses. In parallel, SCO released SCO Open Desktop in 1989, integrating a 32-bit atop the SCO UNIX kernel, featuring the , OSF/Motif toolkit, and tools for desktop productivity such as integrated file management and application launchers. This marked the first GUI-enabled Unix system for platforms, designed for ease-of-use in office settings with support for TCP/IP networking and SQL databases, though it retained SVR3's core limitations like lack of full SVR4 features such as file locking improvements. SCO Open Desktop shared the same runtime environment as SCO UNIX, allowing seamless transitions between desktop and server deployments. These SVR3-based products—SCO UNIX for core server functionality and SCO Open Desktop for graphical extensions—directly preceded SCO OpenServer, providing the foundational kernel, utilities, and x86-specific optimizations that enabled OpenServer's later evolution into a dedicated server OS with maintained binary compatibility for legacy applications. SCO's approach emphasized pragmatic enhancements over pure AT&T fidelity, prioritizing hardware performance and commercial viability amid competition from Sun and DEC systems.

Launch and Evolution of SCO OpenServer

SCO OpenServer was launched in 1992 by The Santa Cruz Operation (SCO) as a family of server-oriented operating system products built on Release 3.2 version 4.0, targeting 386 and 486 processors to deliver reliable multi-user, multi-tasking capabilities for business computing, including integrated TCP/IP networking and database support. This launch represented an evolution from SCO's prior SCO UNIX System V/386 (introduced in 1989), shifting emphasis toward scalable server deployments with enhanced administrative tools and hardware compatibility for x86 architectures. In 1995, SCO released OpenServer Release 5.0.0, a major upgrade that improved 32-bit application support, expanded disk handling for Extended IDE drives exceeding 528 MB capacities, and bolstered networking performance, making it suitable for emerging enterprise workloads on Pentium-era hardware. This version, internally codenamed , became SCO's core product line, prioritizing stability for mission-critical applications while maintaining binary compatibility with legacy SCO UNIX software. Subsequent updates refined these foundations: Release 5.0.4 arrived in 1999 with optimizations for newer processors; 5.0.5 followed in 2002, addressing Y2K compliance and installation enhancements; and by 2003, Release 5.0.7 incorporated USB 2.0 device support, advanced multi-byte character handling, and SCO MPX extensions for on systems with up to 30 CPUs. These iterations focused on incremental reliability gains, broader peripheral integration, and without disrupting established deployments, ensuring OpenServer's longevity in sectors like retail point-of-sale and prior to UnixWare integration efforts.

Merger with UnixWare

In September 1995, The Santa Cruz Operation (SCO) announced its acquisition of the UnixWare business from Novell, Inc., including rights to UnixWare technology and related SVR4 source code. The deal, valued at approximately $18 million in cash and stock plus ongoing royalties, aimed to consolidate SCO's position in the commercial Unix market by combining UnixWare's advanced SVR4 features—such as symmetric multiprocessing support and real-time extensions—with OpenServer's established SVR3 codebase optimized for x86 hardware. Novell retained ownership of the Unix trademark and certain patents, licensing them back to SCO for use in the merged products. The acquisition closed on December 6, 1995, after which SCO outlined plans to integrate the two operating systems into a unified platform. This merger sought to produce a "standard high-volume UNIX operating system" incorporating Release 5's reliability for business applications with 's networking, workgroup, and transactional processing capabilities, targeting midrange servers and reducing customer fragmentation between the competing Unix variants. SCO committed to maintaining for both and applications through binary emulation layers and source-level ports, while hiring key personnel from 's Florham Park development site to accelerate the effort. The internal project, codenamed Gemini, prioritized 's SVR4 kernel as the foundation due to its alignment with emerging standards like Unix 95 and better scalability for multiprocessor systems, incorporating select OpenServer components for enhanced x86 performance and administrative tools. By November 1997, SCO previewed the result as , a rebranded iteration emphasizing the merger's outcomes, including improved support and clustering options, though full general availability followed in 1998 amid delays from code reconciliation challenges. This integration marked a strategic pivot for SCO, shifting focus from pure SVR3 evolution to a hybrid model that preserved OpenServer's market share in legacy environments while advancing toward SVR4 dominance, though it introduced complexities in certification and support for dual-heritage binaries.

Ownership Transitions Under Caldera International and SCO Group

In August 2000, Caldera Systems Inc., a Linux distributor, announced an agreement to acquire the Server Software Division and Professional Services Division of The Santa Cruz Operation (SCO), encompassing the Unix intellectual property rights, SCO OpenServer operating system, and UnixWare platform. The deal provided SCO with approximately 28 percent ownership in the post-merger Caldera entity and granted Caldera exclusive worldwide distribution rights for OpenServer, while SCO retained its professional services operations temporarily during a transition period. The acquisition closed on May 7, 2001, resulting in the formation of Caldera International Inc. as the surviving entity, which relocated operations to , and assumed full control over OpenServer development, sales, and support. Under Caldera International, OpenServer maintenance continued uninterrupted, with the company committing to ongoing support for existing installations and integration of Unix assets into its broader portfolio alongside offerings. On August 26, 2002, International rebranded itself as The Inc., with Darl McBride assuming the CEO role and a strategic pivot emphasizing Unix-based server products like OpenServer to compete against emerging . This renaming preserved OpenServer's branding and product continuity, while OpenUnix was rebranded as SCO , reflecting a unified focus on proprietary Unix systems amid shifting market dynamics. The transition maintained operational stability for OpenServer users, though it later coincided with intensified legal efforts by The to assert Unix licensing claims against vendors.

Shift to UnXis and Xinuos (2011–Present)

In April 2011, amid The SCO Group's Chapter 11 bankruptcy proceedings, UnXis, Inc., a Las Vegas-based company, completed the acquisition of SCO's Unix software business assets, including the rights to SCO OpenServer and , along with associated and approximately 32,000 service contracts. The transaction, approved by the bankruptcy court following an process initiated in late 2010, included a $25 million commitment from UnXis for product development, technology enhancements, and staff expansion to sustain and modernize the acquired operating systems. UnXis rebranded to Xinuos, Inc., in , shifting focus toward enterprise-grade Unix compatibility and modernization while retaining the core stability of OpenServer for legacy applications in sectors like , , and utilities. Under Xinuos ownership, OpenServer received updates emphasizing with x86 hardware, enhanced support, and integration with contemporary networking protocols, though development prioritized maintenance over radical redesign to preserve reliability for existing deployments. In June 2015, Xinuos released OpenServer 10, a significant update incorporating kernel elements for improved performance on modern processors while maintaining compatibility with prior versions to ease migration for SCO-era users. Subsequent packs addressed vulnerabilities and hardware certifications, with Xinuos committing to through at least 2025, including active development of derivatives for hybrid cloud environments. This era marked a stabilization phase, contrasting SCO's litigation-heavy final years, as Xinuos emphasized commercial viability over disputes, though it pursued enforcement against perceived infringers in 2021.

Technical Architecture and Features

Kernel and Core System Design

SCO OpenServer Release 5 utilizes a derived from Release 3.2, adapted for x86 architectures with SCO-specific enhancements for reliability and performance in multi-user server environments. This kernel handles core functions including process management via priority-based scheduling, with demand paging, and a supporting the standard for CD-ROMs. Device drivers integrate directly into the kernel space, following the Open Development Driver Interface (ODDI) for loadable modules, which allows dynamic loading without rebooting for supported peripherals. The core system design adheres to UNIX principles, treating all devices as files within a unified , which simplifies application development and administration through standard system calls like read(), write(), and ioctl(). Networking and leverage STREAMS modules for modular protocol stacks, enabling TCP/IP support from early releases. Kernel tunable parameters, configurable via /etc/conf/cf.d/stune, control aspects such as buffer sizes and process limits to optimize for workloads like database servers. In OpenServer Release 6, released in 2005, the kernel evolves to a multi-threaded design based on Release 5, merging the 7 codebase with OpenServer 5's application compatibility layer for binary and source-level support of legacy applications. This SVR5 kernel supports (SMP) on up to 32 processors, 64 GB of RAM, and enhanced through kernel threads for concurrent I/O and networking operations. The architecture maintains via the OpenServer Kernel Personality (OKP), allowing unmodified Release 5 binaries to execute atop the new kernel.

Hardware Support and Compatibility

SCO OpenServer operates on x86 hardware, supporting 80386 and compatible processors as the foundational platform, with compatibility extending to subsequent Pentium series and equivalents in later releases. Early versions emphasized single-processor systems on industry-standard PC , while updates introduced multi-processor support for enhanced scalability in enterprise environments. For OpenServer 5.0.7, supported processors include and CPUs, with minimum requirements of 64 MB RAM (or 4 MB for highly customized installations), 400 MB disk space, and a 600x800 VGA display with 256 colors. Recommended configurations specify 64 to 256 MB RAM and at least 2 GB on SCSI-3 or superior hard drives to accommodate typical workloads. OpenServer 6 further expanded compatibility to include features, hyper-threaded CPUs, , and , Athlon XP, , processors. Hardware compatibility is verified through SCO's Certified Hardware Products (CHWP) listings, which detail supported systems, adapters, and peripherals to ensure reliable operation. Networking support encompasses EtherExpress adapters and similar ISA/MCA controllers, while storage relies on certified and IDE drives. OpenServer 5.0.7 adds limited USB functionality, including USB 2.0 EHCI host controllers, USB 1.1 OHCI and UHCI controllers, bootable USB drives, and class drivers for keyboards and mice. Drivers for additional components, such as those from eServer xSeries, require adherence to vendor-certified lists to avoid interface mismatches, particularly with DDI versions incompatible across SCO OpenServer and kernels. support emerged in select releases, aligning with and advancements, though full certification depends on the specific hardware configuration tested by SCO. Users must consult release-specific documentation for bus architectures (e.g., PCI, ISA) and processor generations to confirm viability, as unlisted components may necessitate custom drivers or updates from Xinuos.

Networking, Security, and Administrative Tools

SCO OpenServer provides a comprehensive suite of networking capabilities built on a standard TCP/IP , enabling connectivity for enterprise environments. The Network Configuration Manager offers an interactive graphical interface for adding, modifying, viewing, and removing network interface configurations, supporting Ethernet, , and FDDI adapters through loadable kernel modules. Core networking components include NFS for , NIS for name services, and support for via configurable default gateways set in /etc/default/tcp. In SCO OpenServer Release 6, enhancements extend to compatibility, SSH for secure remote access, IP firewall filtering for traffic control, and implementation for encrypting TCP/IP packets and enabling virtual private networks (VPNs). Security features in earlier versions like OpenServer 5 emphasize Unix fundamentals such as file permissions, user authentication via /etc/shadow, and basic auditing, though vulnerabilities like buffer overflows in tools such as have been documented. OpenServer 6 introduces advanced protections including and for encrypted communications, kernel-level for VPNs, and integrated firewall rules to filter IP traffic, alongside tools for monitoring health and device security. These measures address common threats in server deployments, with Xinuos maintenance packs providing patches for known exploits, prioritizing reliability over newer paradigms like SELinux. Administrative tools facilitate system management through the SCOAdmin graphical utility, which centralizes tasks like user account creation, hardware configuration, and software installation via intuitive menus. Command-line equivalents include mkdev for device setup and configure for product licensing, with updates in Release 6 incorporating multi-threaded kernel support for up to 32 processors and an Online Data Manager for real-time maintenance. System monitoring relies on tools like sar for performance metrics and custom scripts for , ensuring compatibility with legacy SCO UNIX workflows while supporting modern integrations under Xinuos stewardship.

Versions and Releases

Major Version Milestones

SCO OpenServer's major version milestones commenced with Release 5.0.0 in 1995, establishing a commercial Unix operating system derived from System V Release 3.2, optimized for x86 hardware with features including TCP/IP networking, support, and multi-user capabilities for servers. Key evolutionary releases within the 5.x series followed, each enhancing stability, hardware compatibility, and security: Release 5.0.4 on July 1, 1999; Release 5.0.5 on June 26, 2002; Release 5.0.6 on December 31, 2005; and Release 5.0.7 around 2003–2007, which added support for USB 2.0, multi-core processors, and . Release 6.0, launched on June 22, 2005, marked a pivotal milestone by adopting a UnixWare-derived kernel, enabling 64-bit addressing, kernel-level threading, support, and file systems accommodating terabyte-scale volumes, thereby addressing scalability limitations of prior versions while maintaining with OpenServer 5 applications. Under Xinuos ownership, definitive editions emerged in 2018: OpenServer 5 Definitive 2018 and OpenServer 6 Definitive 2018, integrating accumulated maintenance packs, updated drivers, and optimizations for extended enterprise viability without introducing new architectural paradigms.

Maintenance Packs and Updates

SCO OpenServer maintenance packs served as cumulative collections of patches, fixes, and minor enhancements, released periodically to address reported issues without constituting full version upgrades. These packs were typically installed via the system's administrative tools, such as SCOAdmin, and required prior installation of earlier packs for compatibility. Update packs complemented maintenance packs by providing additional targeted fixes, often focusing on licensing or specific subsystems. For OpenServer Release 5.0.7, maintenance packs progressed from MP1 to MP5, with MP5 incorporating virtualization-related corrections essential for compatibility with environments like VMware. MP4 for this release aggregated prior fixes and was positioned as a subsequent installment in the series, emphasizing stability improvements. Update Pack 2 for 5.0.7 further bundled security updates and problem resolutions, installable after base maintenance packs. OpenServer Release 6.0.0 received Pack 1 on May 8, 2005, followed by Pack 2 on March 7, 2006, and extending to Pack 4, which addressed ongoing and driver needs. Under Xinuos from 2011, traditional packs evolved into Definitive 2018 editions, such as OpenServer 5 Definitive 2018 (upgrading from 5.0.7 MP5) and OpenServer 6 Definitive 2018 (integrating post-MP4 device drivers like updated AHCI support). Recent supplements include refreshed open-source components, such as 9.9p1a with PAM support, announced in March 2025 for Definitive 2018 variants.
VersionKey Maintenance PacksNotable Features/ Dates
5.0.7MP1–MP5MP5: fixes; cumulative and stability updates.
6.0.0MP1–MP4MP1 (May 2005): Initial fixes; MP2 (March 2006): Enhancements; MP4: Driver integrations.
Definitive editions and supplements continue to receive targeted updates for sustained enterprise use, though earlier packs remain available via official archives for legacy systems.

Intellectual Property Claims Against Linux and Open Source

The SCO Group, which acquired the Unix business including OpenServer from Caldera International in 2001, initiated intellectual property claims in 2003 asserting that the Linux kernel incorporated unauthorized portions of proprietary UNIX System V source code. SCO alleged that this code, derived from System V Release 4 (SVRx) and related to their OpenServer and UnixWare products, had been improperly disclosed and contributed to Linux by IBM and other parties under breach of UNIX license agreements originally stemming from AT&T and Novell. Specifically, SCO claimed that IBM violated contractual restrictions by transferring trade secrets and copyrighted material to open-source developers, enabling Linux to achieve UNIX-like performance without licensing fees, and estimated infringing code at up to 1% of the kernel initially, later expanding assertions to broader derivatives. These claims extended beyond to the open-source community at large, with SCO issuing public statements in May 2003 declaring a "" of UNIX and threatening enforcement actions against commercial users for unless they obtained SCOsource licenses, priced at $699 per server plus per-CPU fees. SCO positioned OpenServer's UNIX heritage—rooted in System V Release 3 with SVR4 enhancements—as the basis for their IP portfolio, arguing that 's rapid development and feature parity with UNIX could only result from systematic appropriation rather than independent reinvention. The company released partial lists of allegedly infringing files and methods, citing examples like process scheduling and networking , though without initially providing full evidentiary disclosure. In subsequent years, SCO refined its assertions to include claims of unfair competition and , notifying over 1,500 enterprises via letters warning of potential liability for running unlicensed UNIX derivatives in environments. The open-source model was framed by SCO as facilitating unauthorized distribution of their IP, prompting calls for indemnification from vendors like and demanding royalties to sustain proprietary UNIX development. These positions drew from SCO's interpretation of the 1995 Novell-SCO , which they viewed as transferring UNIX copyrights essential to protecting products like OpenServer against commoditization by . Efforts to revive similar claims persisted under Xinuos, SCO's successor after 2011 bankruptcy proceedings, with a 2021 lawsuit against and alleging continued infringement of UNIX and IP in distributions, including assertions that open-source contributions perpetuated code derived from SCO's . Xinuos maintained that elements enhancing 's enterprise features, such as file systems and kernel modules, traced back to licensed UNIX owned through OpenServer's lineage, seeking damages for decades of alleged unauthorized use.

Key Lawsuits: SCO vs. IBM, Novell, and Others

The SCO Group's litigation strategy centered on asserting ownership of copyrights, acquired through its predecessor Santa Cruz Operation's purchase of from in 1995, and alleging unauthorized use of proprietary code in development. SCO claimed that incorporated trade secrets from Unix, particularly through contributions by under a 1985 licensing agreement that prohibited disclosure of . These suits, initiated amid SCO's financial distress, sought licensing fees from users and damages from alleged infringers, but were undermined by disputes over copyright transfer validity. In the primary suit against , filed on March 7, 2003, in the U.S. District Court for the District of Utah, SCO accused IBM of breaching contracts by contributing approximately 100,000 lines of Unix-derived code to , violating both the 1985 System V license and a 1996 patent cross-license agreement. SCO initially demanded $1 billion, later amending to $3 billion and then $5 billion in damages. IBM countersued in August 2003, alleging SCO violated the GNU General Public License by refusing to release Linux-related and seeking on non-infringement. Key rulings included partial summary judgments favoring IBM on trade secret misuse claims in 2006 and 2007, with evidence showing limited actual code contributions (around 170 lines proven copied). The case, prolonged by appeals and SCO's 2007 Chapter 11 , was dismissed with prejudice on March 1, 2016, after the final claims failed; an appeal followed, but the parties settled confidentially in November 2021, with IBM prevailing on core issues. Parallel to the IBM action, SCO sued Novell on January 23, 2004, for slander of title and , contending that Novell improperly retained Unix copyrights under the 1996 (APA) transferring UnixWare assets to SCO. Novell countered that the APA explicitly excluded copyrights, which it retained to enable ongoing SVRX royalty streams, and moved to waive SCO's claims against . U.S. District Dale Kimball granted for Novell on August 10, 2007, affirming Novell owned the copyrights and could direct of claims. A March 2010 jury trial upheld Novell's position on copyright ownership but awarded SCO $2.4 million on a separate SVRX licensing issue; however, the Tenth of Appeals in September 2011 reversed the licensing damages, affirming Novell's full retention of copyrights and SCO's lack of standing to sue for infringement. This ruling invalidated SCO's foundational IP claims across litigations. SCO also targeted Linux end-users, filing suits against companies like in March 2004 in U.S. District Court in , alleging use of versions containing Unix code, structure, and organization without a . Similar actions followed against DaimlerChrysler in the same month. These "user suits" aimed to extract settlements by threatening business disruption, but most were dismissed post-Novell ruling; for instance, 's case ended in dismissal with prejudice by 2010, as SCO could not prove ownership. SCO's broader campaign included suits against (2002, settled 2009) and Novell's SuSE (2003, dropped), but yielded minimal recoveries and reinforced judicial skepticism of SCO's IP assertions amid evidence of code commonality predating proprietary Unix elements.

Court Rulings and Outcomes

In the , Inc. v. , Inc. lawsuit, initiated in 2004, U.S. District Judge Dale A. Kimball granted in August 2007, ruling that retained ownership of the Unix and copyrights under the 1995 , despite SCO's acquisition of the Unix business from the . This decision invalidated SCO's core assertion of copyright ownership necessary for its broader claims against contributors. The U.S. of Appeals for the Tenth Circuit partially affirmed the ruling in August 2009 but remanded for on whether SCO owned specific Unix copyrights and on 's counterclaim of slander of by SCO. A federal jury in , in a March 2010 verdict, confirmed 's ownership of the copyrights and found SCO liable for slandering 's , leading to a $2.55 million restitution to for withheld Unix licensing revenues. The Tenth Circuit affirmed the jury's findings in 2012, and the U.S. denied SCO's petition for in 2013, finalizing 's copyright ownership. Parallel to the Novell case, SCO's 2003 breach-of-contract suit against alleged improper disclosure of Unix to Linux developers, seeking damages exceeding $1 billion. Multiple claims were dismissed on , including trade secret misappropriation in 2010 after a found insufficient evidence of specific secrets imparted to . Remaining contract and claims survived until March 2016, when Judge Ted Stewart dismissed them with prejudice for failure to state viable causes of action, a decision upheld on appeal. The case concluded in August 2021 via settlement during SCO's bankruptcy proceedings, with agreeing to pay $14.25 million to TSG Group Holdings, Inc. (SCO's successor entity), resolving all outstanding issues without admission of liability. These rulings effectively dismantled SCO's Unix intellectual property enforcement strategy, as the absence of copyright ownership precluded successful claims of infringement in . SCO's subsequent in and asset sales underscored the financial toll, with no appellate reversals altering the core outcomes by 2025. Secondary suits against entities like settled out of court for undisclosed sums, typically involving license compliance rather than validating SCO's broader IP theories.

Market Reception, Adoption, and Criticisms

Enterprise Deployment and Reliability Achievements

SCO OpenServer demonstrated high reliability in enterprise environments, with reports of systems achieving uptime exceeding 99.999% and supporting up to 32-way (SMP) configurations for scalable performance. Independent assessments highlighted its exceptional stability on platforms, with administrators recounting instances of servers operating continuously for years without reboots or significant failures, attributing this to robust kernel design and minimal resource contention. Such dependability made it suitable for mission-critical applications where downtime could incur substantial costs. In point-of-sale (POS) and retail sectors, OpenServer powered thousands of deployments in "set it and forget it" scenarios, including and systems that required consistent operation under high loads. Major pharmacy chains, such as , , and CVS, integrated SCO software—including OpenServer variants—for backend operations, leveraging its compatibility with legacy x86 hardware and proven in volume-driven environments. Accounting and firm Zenziz relied on it to serve over 1,000 customers across industries like and , citing its role in enabling reliable, multi-user database hosting without frequent interventions. Production support records from the late onward showed OpenServer handling diverse scales, from single-user setups to enterprise clusters managing hundreds of concurrent sessions, often in sectors demanding and 24/7 availability. Third-party vendors emphasized its commercial-grade error handling, where systems frequently ran for months without reboots, outperforming contemporaries in stability for Intel-based Unix workloads. These attributes contributed to its selection for embedded and departmental servers where empirical reliability metrics trumped newer alternatives during its peak adoption in the and early 2000s.

Challenges, Decline, and Competitive Pressures

The rise of in the late 1990s and early 2000s exerted significant competitive pressure on SCO OpenServer by offering a free, open-source alternative with comparable functionality, broader hardware support, and faster innovation driven by community contributions. SCO OpenServer, based on an aging System V Unix foundation, struggled to match Linux's cost advantages and adaptability for small to medium enterprises, leading to gradual erosion of its user base in sectors like retail and point-of-sale systems where SCO had previously held over 40% among U.S. retailers. Microsoft's and Server editions further intensified pressures through aggressive marketing, binary compatibility with legacy applications, and integration with dominant desktop ecosystems, capturing workloads previously suited to Unix variants. SCO's revenue reflected these market shifts, with fiscal second-quarter 2005 figures dropping to $9.3 million from $10.1 million the prior year, amid broader Unix vendor declines attributed to and Windows encroachment. Overall sales fell 44% year-over-year to $11.2 million in another reported period, as licensing income plummeted from $7.3 million to $678,000, underscoring OpenServer's diminishing viability. Internal factors compounded external , including years of mismanagement that hindered timely updates and hardware porting, leaving OpenServer vulnerable on newer x86 architectures while rivals advanced. Efforts to counter these pressures, such as the 2005 release of OpenServer 6 with enhanced and features, failed to reverse the trajectory, as Unix market contraction continued and SCO's focus on litigation diverted resources from product development. By the mid-2000s, OpenServer's adoption waned as enterprises migrated to distributions for cost savings and compatibility, with Unix systems like SCO's relegated to legacy niches.

Perspectives from Proprietary vs. Open Source Advocates

Proprietary software advocates, including executives from SCO and its successor Xinuos, have emphasized OpenServer's established reliability and enterprise-grade stability as advantages over alternatives like . They argue that proprietary UNIX variants such as OpenServer provide superior multi-processing performance and , citing an IDC survey of 1,000 IT professionals that ranked UNIX ahead of in these areas. Xinuos has positioned OpenServer as delivering the "legendary" scalability, reliability, and flexibility of UNIX on affordable hardware, contrasting it with 's perceived risks in mission-critical deployments where vendor accountability is paramount. Former SCO CEO Darl McBride contended that development, particularly , unlawfully incorporated proprietary UNIX code contributed by parties like , undermining incentives for innovation by eroding protections essential to investment. In contrast, open source advocates view OpenServer's proprietary model as outdated and restrictive, crediting collaborative development for Linux's rapid evolution and cost efficiencies that displaced SCO's market share. The Open Source Initiative (OSI) has defended Linux against SCO's allegations, asserting that claims of widespread UNIX code infringement lacked evidence and threatened the open source ecosystem's legal foundations without basis in contract violations. Community analyses, such as those from LWN.net, highlighted SCO's lawsuits as aggressive assertions of trademark and source code control that failed to materialize into proven breaches, with courts ultimately dismissing key claims of copyright ownership and code theft by 2016. Advocates like those in the Linux community argue that open source scrutiny and free distribution foster superior code quality and adaptability, rendering proprietary systems like OpenServer vulnerable to commoditization without the benefits of widespread peer review and zero licensing costs. This perspective frames SCO's legal campaigns not as legitimate IP defense but as attempts to impose royalties on derivative works, a strategy rejected in rulings favoring open source continuity.

Current Status and Future Prospects

Ongoing Maintenance by Xinuos

Xinuos, formerly UnXis, acquired the assets of SCO OpenServer and related Unix products from the bankrupt in 2011, enabling continued development and support under its stewardship after rebranding to Xinuos in 2013. This acquisition preserved access to and binaries, allowing Xinuos to issue updates independently of prior legal entanglements. Since then, Xinuos has maintained OpenServer through periodic releases of maintenance packs, update packs, security supplements, and drivers, available via official download portals for licensed customers. For instance, Maintenance Pack 4 for OpenServer 6.0.0 addresses stability and compatibility enhancements, while OpenServer 6 Definitive 2018 integrates prior maintenance packs with additional features like multi-threaded kernel support for up to 32 processors and 64 GB of RAM. In September 2024, Xinuos released KVM support alongside Update Pack 1 and Maintenance Pack 1 specifically for OpenServer 6 Definitive 2018, facilitating migration to modern hypervisors without hardware dependencies. Support extends to OpenServer 5, with ongoing provisions for network services, , and legacy application compatibility as of late 2024. Xinuos offers tiered support contracts, including incident resolution, access, and for deployment and , with product lifecycles typically extending up to 14 months post-retirement announcements—none of which have been issued for active OpenServer variants as of 2025. These efforts sustain enterprise use in sectors reliant on stable, certified Unix environments, such as point-of-sale systems and industrial controls.

Modern Virtualization and Integration Options

Xinuos offers virtualization solutions for OpenServer variants to enable deployment on contemporary hardware platforms, thereby extending the operational lifespan of legacy installations. OpenServer 5.0.7V is certified for and environments, facilitating physical-to-virtual migrations while preserving application compatibility. Similarly, OpenServer 6V provides initial support on , leveraging its layer for access to advanced hardware features such as multi-core processors and larger memory allocations. In September 2024, Xinuos extended OpenServer 6 Definitive 2018 compatibility to (KVM) hypervisors running on various distributions, including installation via updated ISO images for enhanced flexibility in open-source setups. This KVM integration allows OpenServer instances to operate as guest systems on cost-effective hosts, supporting up to 32 processors, 64 GB of RAM, and 1 TB file sizes inherent to the OS6 kernel. These options address hardware obsolescence by abstracting legacy OpenServer requirements from physical servers, enabling consolidation in data centers alongside other virtualized workloads. For broader , virtualized OpenServer deployments can interface with modern networks and storage via hypervisor-provided drivers, though custom configurations may be required for SCSI-based legacy drives. OpenServer 10, a prior modernization effort, incorporated binary compatibility and deployment options, including AWS instances manageable via RDP or SSH with vendor support, allowing hybrid on-premises-to-cloud transitions for compatible applications. However, as of 2025, primary maintenance emphasizes OpenServer 6 variants, with serving as the principal pathway for sustaining enterprise relevance without native or orchestration.

Relevance in Legacy Systems as of 2025

As of 2025, SCO OpenServer maintains niche relevance in legacy enterprise environments through sustained maintenance by Xinuos, which supports active versions including OpenServer 5 Definitive 2018 and OpenServer 6 Definitive 2018. These releases enable continued operation of mission-critical applications developed for earlier Release 5 architectures, particularly in sectors such as , healthcare, , and , where the high costs and risks of software rewrites or migrations deter replacement. Xinuos provides packages, incident resolution, and knowledge resources, with retired earlier variants (e.g., OpenServer 5.0.7 and OpenServer 6) ineligible for updates, underscoring the incentive for upgrades to sustained editions. OpenServer 6 Definitive 2018, featuring a multi-threaded kernel, support for up to 32 processors, 64 GB of memory, and 1 TB of , alongside tools like the Online Data Manager for volume administration and I/O optimization, facilitates reliable performance for legacy workloads on both physical x86 hardware and virtualized setups such as KVM. In 2024, Xinuos released Maintenance Pack 1 and Update Pack 1 for this version, delivering bug fixes, performance refinements, and integrations of updated open-source elements including SAMBA, GCC, , and to address security and compatibility needs without disrupting established applications. Similarly, OpenServer 5 Definitive 2018 incorporates the Virtual Disk Manager to enhance handling and application reliability, preserving functionality for unmodified legacy code. Despite these efforts, OpenServer's footprint remains limited to organizations prioritizing operational continuity over modernization, as evidenced by its focus on enterprise licensing rather than broad . Challenges include to unpatched exploits in aging codebases and the affecting 32-bit implementations like OpenServer 5, which could disrupt time-dependent operations post-2038 unless addressed through hardware emulation or version transitions. Xinuos targets existing deployments with paid Update Packs and free maintenance for registered users, but the absence of widespread migration incentives signals a stabilizing yet diminishing role amid pressures from cloud-native alternatives and open-source Unix derivatives.

References

  1. https://osr600doc.xinuos.com/en/USE_oview/SCO_UNIX.html
  2. https://www.xinuos.com/products/openserver-5/
  3. http://landley.net/history/mirror/unix/scohistory.html
  4. https://www.fundinguniverse.com/company-histories/the-santa-cruz-operation-inc-history/
  5. https://www.sco.com/products/openserver6/
  6. https://www.xinuos.com/
  7. https://www.operating-system.org/betriebssystem/_english/fa-sco.htm
  8. https://williambader.com/museum/dell/xenixhistory.html
  9. https://www.historyofdomains.com/sco/
  10. https://www.computerhope.com/jargon/s/sco-unix.htm
  11. https://winworldpc.com/product/xenix/openserver-5x
  12. https://www.scosales.com/ta/kb/104717.html
  13. https://skunkware.dev/skunkware/96/dist/Tools/gds-95q4/sco_ds.html
  14. https://www.sco.com/support/programs/legacy.html
  15. https://www.novell.com/news/press/archive/1995/12/pr95274.html
  16. https://www.cnet.com/tech/tech-industry/sco-readies-merged-os/
  17. https://rcpmag.com/articles/2000/08/02/caldera-buys-sco-server-software-professional-services-divisions.aspx
  18. https://www.forbes.com/2000/08/03/feat2.html
  19. https://www.hpcwire.com/2001/05/11/caldera-completes-acquisition-of-two-sco-divisions/
  20. https://www.eweek.com/servers/caldera-renames-itself-sco-group/
  21. https://www.computerworld.com/article/1333453/sco-name-returns-as-caldera-rebrands-itself.html
  22. https://www.prnewswire.com/news-releases/unxis-completes-purchase-of-sco-unix-assets-119609744.html
  23. https://www.ksl.com/article/15133030/las-vegas-company-buys-unix-operating-system-firm
  24. https://www.wsj.com/articles/DJFDBS0020110413e74d0002u?gaa_at=eafs&gaa_n=AWEtsqfgznSOek8FxQ1DhPFZ4Ykdy8Aoawn_UvVDZOD3ESjaXUKJOJ3g76fD&gaa_ts=68feb45e&gaa_sig=Jutv_tbArqvfKwWZqNAgzUyWmvaK7xt2LLhR3XYmOITh9zRAWWOg26X4S6f0_0nrbXQAv9x-Fmw21sy7klNyZQ%253D%253D
  25. https://www.xinuos.com/company/
  26. https://www.xinuos.com/if-you-thought-sco-operating-systems-were-obsolete-think-again/
  27. https://channelbuzz.ca/2016/01/xinuos-launches-modernization-of-sco-openserver-with-openserver-10-16068/
  28. https://www.osnews.com/story/141690/unixware-in-2025-still-actively-developed-and-maintained/
  29. https://www.zdnet.com/article/sco-linux-fud-returns-from-the-dead/
  30. http://www.bitsavers.org/pdf/sco/OpenServer/BH1205P000_SCO_UNIX_Operating_System_Installation_Guide_3.2.4C_Jan92.pdf
  31. http://uw714doc.xinuos.com/en/HDK_oddi/CONTENTS.html
  32. http://osr600doc.xinuos.com/en/SDK_sysprog/SDK_sysprog_pref_FD_IO.html
  33. https://www.scosales.com/ta/kb/107228.html
  34. https://www.sco.com/developers/hdk/overview/overview.html
  35. https://www.xinuos.com/products/openserver-6/
  36. https://www.scosales.com/ta/kb/125155.html
  37. http://osr600doc.sco.com/en/GetStart/chwp.html
  38. https://www.opengroup.org/openbrand/register/sco.htm
  39. https://www.sco.com/products/openserver507/System_Requirements.html
  40. http://osr507doc.xinuos.com/fr/GetStart/gsgC.hwreqs.html
  41. https://www.sco.com/products/openserver6/technical_whitepaper3.html
  42. http://osr600doc.xinuos.com/en/HW_config/hardware_issues_general.html
  43. https://www.scosales.com/ta/kb/101579.html
  44. https://www.sco.com/products/openserver507/
  45. http://uw714doc.xinuos.com/en/HW_config/hwconfigC.compatibility.html
  46. https://www.scosales.com/ta/kb/126167.html
  47. http://osr507doc.xinuos.com/en/GetStart/gsgC.sysreqs.html
  48. http://osr600doc.sco.com/en/HW_network/ncfgN.ncfg.html
  49. https://www.experts-exchange.com/questions/20345201/Setting-the-default-gateway-for-SCO-Openserver-5.html
  50. https://www.networkcomputing.com/data-center-networking/sco-makes-its-pitch-with-openserver-6
  51. https://www.sco.com/products/openserver6/security.html
  52. https://www.giac.org/paper/gsec/427/sco-openserver-505-security-systems-administrator/101048
  53. https://www.exploit-db.com/exploits/19362
  54. https://www.sco.com/itscoming/
  55. https://kb.pocnet.net/wiki/SCO_Openserver_5.0.7_installation
  56. http://osr600doc.sco.com/en/OSR_FEATS/feats600.featsSYSMGMT.html
  57. http://osr600doc.xinuos.com/en/Navpages/SMhome.html
  58. https://www.xinuos.com/wp-content/uploads/OpenServer6D2M1-GettingStartedGuide-201712.pdf
  59. https://www.sco.com/products/openserver507v/vmware/507v_vmware.pdf
  60. https://www.e-channelnews.com/sco-releases-major-upgrade-with-sco-openserver-6/
  61. https://commons.wikimedia.org/wiki/File:SCO_OpenServer_Release_6_Launch_Event_at_Yankee_Stadium_attendees_in_stands_June_2005.jpg
  62. https://www.xinuos.com/wp-content/uploads/OpenServer5D2M1-ReleaseNotes-201809.pdf
  63. https://landing.sco.com/xinuos-releases-new-sco-openserver-6-definitive-2018/
  64. https://mirror.rqsall.com/ftp.sco.com/pub/openserver5/507/old/scoupdate/up2/osr507up2.htm
  65. https://unix.stackexchange.com/questions/43259/installing-sco-openserver-5-0-7-maintenance-pack
  66. https://www.scosales.com/ta/kb/125205.html
  67. https://partnerweb.vmware.com/GOSIG/SCO_OpenServer_5.html
  68. https://ftp.sco.com/openserver5/507/mp/osr507mp4/osr507mp4.pdf
  69. https://www.scosales.com/ta/kb/126117.html
  70. https://www.sco.com/products/openserver6/mp2/
  71. https://www.sco.com/support/docs/openserver/
  72. https://www.xinuos.com/wp-content/uploads/OpenServer6D2M1-ReleaseNotes-201712.pdf
  73. https://www.xinuos.com/updated-open-source-packages-for-openserver-6d-2018-unixware-7d-2018/
  74. https://www.sco.com/support/update/download/osr507list.html
  75. https://www.scl.org/1006-the-sco-open-source-litigation-saga-the-community-fights-back/
  76. https://opensourcewatch.beehiiv.com/p/sco-vs-linux-saga-20-years-opensource-turmoil
  77. https://lwn.net/Articles/924577/
  78. https://www.linuxjournal.com/article/6956
  79. https://www.cnet.com/tech/services-and-software/years-into-case-sco-asserts-copyright-infringement/
  80. https://www.eweek.com/servers/vetting-scos-linux-lawsuits/
  81. https://www.theregister.com/2021/03/31/ibm_redhat_xinuos/
  82. https://linux.slashdot.org/story/21/11/09/0022228/last-of-original-sco-v-ibm-linux-lawsuit-settled
  83. https://www.hollywoodreporter.com/business/business-news/court-ruling-gives-novell-copyright-147631/
  84. https://natlawreview.com/article/sco-can-t-claim-ownership-unix-operating-system
  85. https://www.crn.com/news/applications-os/18841140/sco-sues-autozone-for-copyright-infringement
  86. https://www.networkworld.com/article/881535/software-sco-sues-linux-users-daimlerchrysler-autozone.html
  87. https://opensource.com/law/10/4/sco-reaping-litigation-whirlwind
  88. https://caselaw.findlaw.com/us-10th-circuit/1115203.html
  89. https://www.computerworld.com/article/1572388/sco-loses-another-round-in-unix-fight-must-pay-2-55m-to-novell.html
  90. https://www.quimbee.com/cases/the-sco-group-inc-v-novell-inc
  91. https://law.justia.com/cases/federal/appellate-courts/ca10/16-4040/16-4040-2017-10-30.html
  92. https://www.zdnet.com/article/last-of-original-sco-v-ibm-linux-lawsuit-settled/
  93. https://www.theregister.com/2021/08/30/sco_tsg_vs_ibm_settlement/
  94. https://lwn.net/Articles/925136/
  95. https://arstechnica.com/gadgets/2021/04/xinuos-finishes-picking-up-scos-mantle-by-suing-red-hat-and-ibm/
  96. https://www.sco.com/5reasons/
  97. https://www.eweek.com/servers/sco-openserver-is-a-winner/
  98. https://news.ycombinator.com/item?id=42041544
  99. https://www.channelinsider.com/tech-companies/sco-openserver-6-pushes-unix-line-forward/
  100. http://larrykarnis.com/lk/skills/openServer.php
  101. https://www.claritysoftwaresystems.com/products/sco-unix
  102. https://www.linuxinsider.com/story/sco-faces-competitors-head-on-with-openserver-6-44158.html
  103. https://www.zdnet.com/article/unix-decline-extends-sco-revenue-drop/
  104. https://www.linuxinsider.com/story/scos-woes-too-late-to-turn-back-36572.html
  105. https://fossforce.com/2015/03/when-sco-was-cool/
  106. https://www.deseret.com/2004/2/16/19812212/the-man-the-geeks-hate/
  107. http://www.catb.org/~esr/hackerlore/sco-vs-ibm.html
  108. https://lwn.net/Articles/24747/
  109. https://www.sco.com/support/update/download/index.html
  110. https://www.xinuos.com/kvm-support-update-pack-1-and-maintenance-pack-1-now-available-for-os6/
  111. https://www.xinuos.com/support/
  112. https://www.sco.com/products/unix/virtualization/faq.html
  113. https://www.sco.com/products/openserver60v/
  114. https://community.spiceworks.com/t/virtualize-a-sco-openserver-5-0-6/157822
  115. https://www.xinuos.com/wp-content/uploads/Xinuos-Data-Sheet-OpenServer-10.3.pdf
  116. https://computerbusiness.com/news/the-impending-date-issue-in-business-the-implications-of-32-bit-operating-systems-in-2038/
Add your contribution
Related Hubs
Contribute something
User Avatar
No comments yet.