Hubbry Logo
UnixWareUnixWareMain
Open search
UnixWare
Community hub
UnixWare
logo
7 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Contribute something
UnixWare
UnixWare
UnixWare
View on Wikipedia
from Wikipedia

UnixWare
UnixWare 7.1.4, showing the CDE desktop
DeveloperXinuos (previously Univel, Novell, SCO, Caldera Systems, Caldera International, The SCO Group)
OS familyUnix (SVR4.2/SVR5)
Working stateCurrent
Source modelClosed source
Initial release1992; 33 years ago (1992)
Latest release7 Definitive 2018 / 2017; 8 years ago (2017)
Kernel typeMonolithic kernel
UserlandPOSIX / SUS
LicenseProprietary
Preceded byUNIX System V
Official websiteOfficial website

UnixWare is a Unix operating system. It was originally released by Univel, a jointly owned venture of AT&T's Unix System Laboratories (USL) and Novell. It was then taken over by Novell. Via Santa Cruz Operation (SCO), it went on to Caldera Systems, Caldera International, and The SCO Group before it was sold to UnXis (now Xinuos). After the acquisition of SCO by Caldera, the name was briefly changed to Open UNIX before being reverted to the original name in the next release.[1] Binary distributions of UnixWare are available for x86 architecture computers. UnixWare is primarily marketed and deployed as a server operating system.[2][3]

History

[edit]

Univel (1991–1993)

[edit]

After the SVR4 effort to merge SunOS and System V, AT&T's Unix System Laboratories (USL) formed the Univel partnership with Novell to develop a desktop version of Unix for i386 and i486 machines, codenamed "Destiny".[4]

Destiny is based on the Unix System V release 4.2 kernel. The MoOLIT toolkit is used for the windowing system, allowing the user to choose between an OPEN LOOK or MOTIF-like look and feel at runtime. In order to make the system more robust on commodity desktop hardware, the Veritas VXFS journaling file system is used in place of the UFS file system used in SVR4. Networking support in UnixWare includes both TCP/IP and interoperability with Novell's NetWare protocols (IPX/SPX); the former were the standard among Unix users at the time of development, while PC networking was much more commonly based on NetWare.[5]

Destiny was released in 1992 as UnixWare 1.0, with the intention of unifying the fragmented PC Unix market behind this single variant of the operating system. The system was earlier to reach the corporate computing market than Microsoft's Windows NT, but observers of the period remarked that UnixWare was "just another flavor of Unix", Novell's involvement being more a marketing ploy than a significant influx of technology.[5] There two editions of Destiny: a Personal Edition, which includes Novell IPX networking but not TCP/IP, and an Advanced Server Edition with TCP/IP and other server software. The personal edition is limited to two active users, while the server edition includes an unlimited user license. Around 35,000 copies of UnixWare 1.0 were sold.[6]

In 1992, UnixWare 1.0 Personal Edition came with DOS Merge 3.0 and Novell's DR DOS 6.0.

In 1993, Novell purchased USL from AT&T and merged USL and Univel into a new Unix Systems Group.[7]

Novell (1993–1995)

[edit]
UnixWare 2 promotional clock

In 1994 Novell released UnixWare 1.1, which includes TCP/IP in both the personal and advanced server editions.[8] The MOTIF 1.2 runtime libraries are included for COSE compliance. NUC (NetWare Unix Client) software is included for integration with Novell NetWare servers. The Advanced Merge application is installed on both the server and personal editions to allow running DOS and Windows 3.1 applications.

Novell later released bug-fix versions 1.1.1, 1.1.2, 1.1.3 and finally 1.1.4 on 19 June 1995.[9]

UnixWare 2.0, based on the Unix System V release 4.2MP kernel, which added support for multiprocessing, began shipping to OEMs and developers in December 1994,[10] and to the consumer market in March 1995.[11] Both the personal and server editions support two processor systems, with the possibility of buying extra Processor Upgrade licenses for the server edition. Supported multiprocessor systems include standard Intel MP 1.1 SMP machines and Corollary C-bus systems. The system supports NetWare ODI network drivers in an effort to increase the number of supported network interfaces. Other new features in the release include a POSIX Threads library in addition to the older UI threads library.[10]

Before SCO licensed UnixWare in 1995, Novell had also announced a project to create a "SuperNOS" based on NetWare 4.1 and UnixWare 2.0 technologies on top of ChorusOS in the future.[12] This never materialized. Instead, a NetWare 4.10 server on Linux was offered as Caldera NetWare for Linux for OpenLinux since 1998, and Novell's Open Enterprise Server finally came in 2005.

Santa Cruz Operation (1995–2001)

[edit]
At the tail end of Novell's ownership of UnixWare, the company celebrated project completion of "Eiger", the codename for UnixWare 2.1

In 1995, the Santa Cruz Operation (SCO) acquired UnixWare from Novell.[13] The exact terms of this transaction were disputed (see SCO vs Novell); courts have subsequently determined that Novell retained the ownership of Unix.

When the transfer was made public SCO announced that it would work towards merging UnixWare with its OpenServer SVR3.2 based OS,[14] but the first release of UnixWare from SCO was version 2.1 in 1996. At the release of UnixWare 2.1 it was announced that the proposed UnixWare/OpenServer merger was known as project Gemini, to be available in 1997 and a 64-bit version of UnixWare was to be developed for 1998.[15]

One controversial change was the adoption of an OpenServer-like user licensing policy. The Univel and Novell releases of UnixWare allow 2 users on the personal edition or unlimited numbers of users on the server edition. With UnixWare 2.1 the server edition includes a license for up to 5 users. Customers wanting more users could purchase 10, 25, 100, 500 or unlimited user license extensions.[16]

SCO released three updates to UnixWare 2.1. UnixWare 2.1.1, released in 1996 achieved Unix 95 branding.[17] UnixWare 2.1.2 and 2.1.3, available in 1998, are largely bug fix releases.

In 1998 Compaq released a package known as the Integrity XC consisting of a single-system image cluster of Proliant servers with a version of UnixWare 2.1, UnixWare NonStop Clusters.[18]

The first results of the Gemini project were made available in early 1998 as UnixWare 7.[19] SCO named the kernel version Unix System V release 5. The system is largely based on UnixWare 2.1, with features for driver compatibility with OpenServer, allowing use of OpenServer network drivers. System administration utilities from OpenServer, scoadmin, replace the original UnixWare sysadm utility. Major new features of UnixWare 7 include multi-path I/O, large files and file systems and support for large memory systems.[20]

UnixWare 7 lacks the Xenix compatibility features of both its ancestors. This was due to SCO wishing to no longer pay Microsoft more royalties on Xenix.[21][22] For those wanting Xenix compatibility, an optional SCO OpenServer Kernel Personality would later be created.[23]

In 1999 SCO released the UnixWare 7.1 update which increased the number of editions; the Business (5-user), Department (25 user) and Enterprise (50 user) editions replace the earlier personal and server editions. The WebTop application from Tarantella, Inc. is included.[24]

In 2000 SCO released the UnixWare 7.1.1 update. Simultaneously the UnixWare NonStop Clusters 7.1.1+IP single-system image cluster package was released. This new package allows commodity hardware to be used as well as the proprietary Compaq hardware supported by the earlier Integrity XC product, and was directly available from SCO.[25]

Caldera Systems, Caldera International and The SCO Group (2000–2011)

[edit]
Old SCO UnixWare logo

On 2 August 2000,[26] Santa Cruz Operation (SCO) announced that it would sell its Server Software and Services Divisions, as well as rights to the OpenServer and UnixWare products, to Caldera Systems. In March 2001, Caldera Systems announced they would become Caldera International (CII),[27] and the SCO purchase was completed in May 2001.[28] The remaining part of the Santa Cruz Operation company, the Tarantella Division, changed its name to Tarantella, Inc.

Caldera International's initial release of UnixWare was renamed Open UNIX 8. The name change was intended to highlight the addition of the "Linux Kernel Personality" compatibility layer to the operating system.[29] This release is what would have been UnixWare 7.1.2. Caldera International renamed itself to The SCO Group in August 2002, after broadening its product line to include mobile products and services.

Later, the newly renamed The SCO Group reverted to the previous UnixWare brand and version release numbering, releasing UnixWare 7.1.3[30] and 7.1.4.[31] No further releases were made under the Open UNIX name. The SCO Group continued to maintain UnixWare and issues periodic maintenance updates and support.[32]

Between 2007 and 2011, The SCO Group engaged in a series of legal battles. In September 2007, The SCO Group filed for Chapter 11 bankruptcy protection.[33]

On 11 April 2011, UnXis bought The SCO Group operating assets and intellectual property rights after having been approved by the bankruptcy court in Delaware.[34][35]

The SCO Group, Inc. then renamed itself TSG Group, Inc., and SCO Operations, Inc. became TSG Operations, Inc.,[36] and in August 2012 filed to convert from Chapter 11 to Chapter 7.[37]

UnXis and Xinuos (2011–present)

[edit]

The rights to Unixware, as well as OpenServer, were acquired by UnXis in 2011.

In June 2013 UnXis was renamed as Xinuos[38] and announced product and availability for SCO UnixWare 7.1.4+,[39] now supporting both physical and virtual machines.

Version history

[edit]
Year Release Company Codebase Kernel version Notes
1991 UnixWare 1.0 Univel SVR4.2 1
1993 UnixWare 1.1 Novell 1
UnixWare 1.1.1 Novell 1
UnixWare 1.1.2 Novell 1
UnixWare 1.1.3 Novell 1
1995 UnixWare 2.0 Novell SVR4.2MP 2.0 Support for SMP
UnixWare 1.1.4 Novell 1 Final release of UnixWare 1
UnixWare 2.0.1 Novell 2.0.1
UnixWare 2.0.2 Novell 2.0.2 July 1995
UnixWare 2.0.3 Novell 2.0.3 November 1995
1996 UnixWare 2.1 Santa Cruz Operation 2.1
UnixWare 2.1.1 Santa Cruz Operation 2.1.1
UnixWare 2.1.2 Santa Cruz Operation 2.1.2
1998 UnixWare 2.1.3 Santa Cruz Operation 2.1.3 Final release of UnixWare 2
1998 UnixWare 7 Santa Cruz Operation SVR5 7.0.1 A "merge" of UnixWare 2 and OpenServer 5
UnixWare 7.0.1 Santa Cruz Operation 7.0.1
1999 UnixWare 7.1.0 Santa Cruz Operation 7.1.0
2000 UnixWare 7.1.1 Santa Cruz Operation 7.1.1
2001 Open UNIX 8 Caldera International 7.1.2
2003 UnixWare 7.1.3 The SCO Group 7.1.3 See also Smallfoot (SVR6)
2004 UnixWare 7.1.4 The SCO Group 7.1.4 No longer included the Linux Kernel Personality[40]
2004 UnixWare 7.1.4 MP1 The SCO Group 7.1.4 Maintenance pack 1
2005 UnixWare 7.1.4 MP2 The SCO Group 7.1.4 Maintenance pack 2
2006 UnixWare 7.1.4 MP3 The SCO Group 7.1.4 Maintenance pack 3
2008 UnixWare 7.1.4 MP4 The SCO Group 7.1.4 Maintenance pack 4
2013 UnixWare 7.1.4+ Xinuos 7.1.4 Virtualisation Support[39] for VMware ESX
2015 UnixWare 7 Definitive Xinuos 7.1.4+ Compatible with previous supported UnixWare versions[41]
2017 UnixWare 7 Definitive 2018 Xinuos 7.1.4+ In-place upgrade from previous supported versions[42]

SCO Skunkware and open source

[edit]

All versions of UnixWare have included significant open source components including BIND/X11/Sendmail/DHCP/Perl/Tcl and others. Later releases are bundled with numerous additional open source applications including Apache, Samba, MySQL, PostgreSQL, OpenSSH, and Mozilla software, as well as amenities such as Sudo, Vim, Tar, Gzip, and Red Hat's RPM Package Manager[43]

All versions of SCO operating system distributions including UnixWare also have an extensive set of open source packages available for free download via the SCO Skunkware site.[44][45]

See also

[edit]

References

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

UnixWare

View on Grokipedia
from Grokipedia
UnixWare is a Unix operating system initially developed by Univel, a between and AT&T's Unix System Laboratories, combining elements of Release 4.2 with 's networking capabilities, and first released in November 1992. Following Univel's acquisition by , the system evolved with UnixWare 2.0 in 1995, introducing support for enterprise servers. In the same year, sold the UnixWare business to the (SCO), which continued development, releasing the major UnixWare 7 version in 1998, emphasizing scalability, online data management, and compatibility with large file systems and memory configurations. UnixWare achieved commercial success as an x86-based Unix variant targeted at business applications, including call center systems, but became entangled in prolonged legal controversies after SCO initiated lawsuits asserting ownership of Unix copyrights and alleging infringement by ; federal courts ultimately ruled that retained the copyrights to UNIX and UnixWare, undermining SCO's claims. Ownership later passed to Xinuos, which maintains UnixWare 7 Definitive 2018 with updates for modern hardware and security features like and .

Development and Ownership History

Origins at Univel (1991–1993)

Univel, Inc. was established in 1991 as a between AT&T's Unix System Laboratories (USL), which held primary rights to Unix development, and , aiming to create a commercial Unix operating system optimized for networked enterprise environments on x86 hardware. The partnership sought to address fragmentation in the Unix market by merging USL's advanced System V technologies with Novell's dominant networking software, targeting mid-range servers as mainframes waned in dominance during the early 1990s shift toward . This initiative, internally codenamed Destiny, emphasized ease of use and tight integration between Unix workloads and NetWare services to appeal to businesses seeking scalable, network-centric solutions without proprietary hardware dependencies. UnixWare 1.0, the inaugural release, debuted in November 1992 and was built directly on USL's Release 4.2 (SVR4.2), incorporating multi-processor (MP) capabilities for enhanced performance on systems. It maintained full binary compatibility with existing SVR4 applications, allowing seamless porting from other System V variants, while introducing preliminary interoperability features such as shared file systems and remote procedure calls to unify Unix and administration. The system required a minimum 386 processor, 4 MB of RAM, and supported architectures, positioning it as a high-performance alternative for server applications in environments demanding reliability and networking efficiency. Early marketing highlighted UnixWare's multi-threaded kernel and real-time extensions derived from SVR4.2, which enabled it to handle demanding workloads like database servers and on cost-effective x86 platforms, contrasting with the higher costs of RISC-based Unix systems from competitors. Univel positioned the product to capture in the growing PC server segment, where Unix's open standards promised amid vendor-specific silos, though initial adoption was tempered by the nascent state of x86 hardware.

Novell Era (1993–1995)

In June 1993, completed its acquisition of Unix System Laboratories (USL) from , following an announcement in December 1992, thereby gaining full ownership of the Unix trademark and merging USL with the Univel to form the Novell Unix Systems Group. This move consolidated 's control over UnixWare development, shifting focus toward a network-centric operating system that leveraged NetWare's dominance in enterprise networking to differentiate from competitors. UnixWare 1.1, released in late 1993, introduced tighter integration with , enabling seamless file and print services through native support for IPX/SPX protocols and enhanced interoperability utilities that allowed UnixWare servers to function as NetWare-compatible nodes without additional gateways. These features positioned UnixWare as a bridge between Unix workloads and NetWare environments, supporting up to multi-user configurations for departmental use while incorporating TCP/IP stacks in both personal and server editions. In early 1995, launched UnixWare 2.0, built on SVR4.2 with improvements in hardware support, faster installation processes, and advanced desktop tools based on the for graphical administration. Enhanced scalability targeted mid-sized servers, with demonstrations of clustering prototypes that enabled parallel database operations on platforms, foreshadowing high-availability features amid competition from Windows NT's server ambitions. emphasized proprietary extensions, including planned Directory Services integration, to fortify UnixWare's role in heterogeneous networks rather than pure open standards compliance.

Santa Cruz Operation Ownership (1995–2001)

In December 1995, The Santa Cruz Operation, Inc. (SCO) completed its acquisition of Novell's UnixWare business, which included the UnixWare product line and associated intellectual property rights to UNIX System V. The deal, announced in September 1995 and valued at approximately $59.5 million, enabled SCO to assume full control over UnixWare development and marketing, shifting focus toward Intel-based server environments with enhanced hardware compatibility and driver support for contemporary x86 systems. SCO rebranded UnixWare 2.1 under its stewardship, incorporating optimizations for broader commercial deployment while retaining core System V/4.2 architecture derived from prior Novell efforts. SCO integrated elements of its proprietary operating system into UnixWare, culminating in the release of UnixWare 7 in 1998, which combined OpenServer's networking and desktop features with UnixWare's kernel scalability for unified enterprise use. A key advancement was the introduction of UnixWare NonStop Clusters in 1999, an add-on package enabling fault-tolerant, single-system-image clustering across up to 12 nodes running UnixWare 7. This technology supported high-availability configurations with features like cross-node mirroring and scripting, targeted at mission-critical applications in and requiring 99.999% uptime. NonStop Clusters extended UnixWare's reliability beyond standalone servers, competing with proprietary clustering solutions from vendors like (later ). Prior to 2001, SCO issued updates emphasizing stability and interoperability, including UnixWare 7.1.1 in 2000, which addressed Y2K compliance through kernel-level date handling fixes and provided warranties for millennium rollover in supported releases. Java integration was bolstered via certified runtime environments and development kits compatible with UnixWare 7, facilitating enterprise applications with JVM support for 32-bit architectures. These enhancements positioned UnixWare as a cost-effective, x86-native alternative to RISC-based UNIX variants from and , emphasizing binary stability, on hardware, and avoidance of recompilation needs for legacy SVR4 applications.

Caldera Systems and SCO Group Period (2001–2011)

In May 2001, Caldera Systems completed its acquisition of the Server Software Division and Professional Services Division from The Santa Cruz Operation for approximately $31 million, gaining control of UnixWare and SCO OpenServer product lines. This transaction positioned Caldera, originally a Linux distributor, to pivot toward proprietary Unix assets amid growing open-source competition. In August 2002, Caldera International rebranded its Unix operations as The SCO Group, reviving the SCO name for marketing UnixWare and related services while separating Linux efforts under Caldera branding temporarily. The SCO Group aggressively asserted intellectual property rights derived from its UnixWare ownership, initiating lawsuits to enforce licensing obligations tracing back to AT&T's System V copyrights. In March 2003, SCO sued IBM, alleging breach of a 1985 Unix license agreement through unauthorized disclosure of trade secrets to Linux developers, seeking damages for purported code contributions that undermined SCO's proprietary value. SCO extended claims against Novell, disputing Novell's retention of Unix copyrights under the 1995 Asset Purchase Agreement, and pursued end-users like AutoZone for Linux deployments, framing them as unlicensed Unix derivatives. These actions, including a short-lived SCOsource licensing campaign, generated temporary revenue but escalated legal costs and industry backlash, with courts progressively validating Novell's copyright position in rulings from 2007 onward. Financial pressures mounted as Unix market share eroded against Linux adoption, with SCO's quarterly Unix revenues dropping 16.8% year-over-year in Q3 2003 to $13.4 million and plummeting 58% to $10 million in Q4 2004 amid commoditization. By 2005, Linux-related licensing income had plunged, contributing to overall quarterly revenues of $9.35 million, down from $11.2 million prior year, as customers shifted to free alternatives. SCO continued maintenance releases for UnixWare 7.1.x, such as version 7.1.3 in December 2002, but sustained losses from litigation and market decline led to Chapter 11 bankruptcy filing on September 14, 2007. During bankruptcy proceedings through 2011, UnixWare support persisted under court oversight, though core business viability waned due to unresolved IP disputes and open-source dominance.

Xinuos Ownership (2011–present)

In April 2011, UnXis, Inc. completed the acquisition of The SCO Group's operating assets and rights, including UnixWare, through a process. This transaction transferred ownership of UnixWare 7 and related products to UnXis, enabling continued support for existing deployments amid SCO's financial difficulties. In June 2013, UnXis rebranded to Xinuos, reflecting a focus on Unix-based operating systems while maintaining the acquired portfolio. Under Xinuos ownership, UnixWare 7.1.4 remains the flagship release, positioned as a mature UNIX system for enterprise environments requiring high reliability and minimal downtime. Xinuos has sustained development through periodic patch and technology fixes (PTFs), maintenance packs, and update packs, addressing security vulnerabilities, hardware compatibility, and performance optimizations. For instance, in January 2024, Xinuos released PTF 9151 alongside Update Pack 1 and Maintenance Pack 1 for UnixWare 7 Definitive 2018, incorporating enhancements such as updated libraries, utilities, and device drivers. These updates build on prior maintenance packs by adding support for virtualization platforms like VMware and KVM/ProxMox, as well as tightened security measures and drivers for modern chipsets on host bus adapters and network controllers. As of March 2025, Xinuos continued issuing features and fixes beyond UnixWare 7.1.4 Maintenance Pack 4, including a new development subsystem and further refinements to open-source applications, file systems, and hardware integration to facilitate legacy system migrations and sustained operation on supported platforms. This ongoing maintenance targets niche applications in mission-critical sectors, such as point-of-sale systems and industrial controls, where UnixWare's proven stability and scalability outweigh the need for contemporary features found in newer operating systems. Xinuos provides support services, including installation on virtual machines and updates for leading-edge peripherals, ensuring compatibility for deployments prioritizing long-term uptime over rapid innovation.

Technical Architecture and Features

Core System Design and Kernel

UnixWare's kernel is a monolithic design rooted in the UNIX System V Release 4.2 (SVR4.2) codebase, augmented with (MP) extensions originally developed by UNIX System Laboratories (USL) and further refined by for (SMP) support on x86 architectures. This architecture integrates kernel-level multithreading for , disk operations, and networking protocols, enabling scalable performance in multi-processor configurations suitable for enterprise workloads. The SVR4.2 MP kernel foundation emphasizes efficient resource sharing across processors, with early implementations supporting configurations of multiple CPUs to distribute processing demands symmetrically. The kernel maintains POSIX.1 conformance inherited from its SVR4 lineage, promoting binary portability for applications compiled against SVR4 interfaces and ensuring compatibility with standard UNIX programming models. This compliance extends to system calls, signals, and process management, allowing seamless execution of legacy SVR4 binaries without recompilation in most cases. For (IPC), UnixWare leverages Unix domain sockets, which are addressed via filesystem pathnames (e.g., within /tmp), providing low-overhead, local-domain data transfer between processes on the same host more efficiently than network sockets. Scheduling in the UnixWare kernel relies on a priority-based optimized for predictable task execution in server environments, with MP-aware thread handling to minimize contention in multi-CPU setups. This design prioritizes causal ordering of operations for mission-critical applications, utilizing fixed-priority classes and time-slice mechanisms to bound response times under load, in contrast to the more opportunistic, fairness-oriented scheduling prevalent in non-real-time general-purpose kernels.

Integration with NetWare and Networking Capabilities

UnixWare featured a networking stack that facilitated interoperability between UNIX-based TCP/IP environments and Novell's IPX/SPX protocols, positioning it as an and protocol bridge in heterogeneous enterprise networks. This integration was particularly emphasized during Novell's ownership period, with UnixWare 2 (released March 1995) incorporating multithreaded 32-bit IPX support alongside SPX II for reliable packet sequencing and connection-oriented services over infrastructures. Such capabilities enabled seamless communication in mixed-protocol setups without requiring full protocol emulation, prioritizing efficient data exchange for and directory services in environments dominated by clients. The system's advanced TCP/IP implementation complemented IPX/SPX by supporting features like dynamic IP addressing via BOOTP, subnet masking, and routing to default gateways, configurable during installation or via graphical tools such as Internet_Setup. SNMP monitoring extended across both protocol stacks, allowing over IPX/SPX for NetWare-centric segments and TCP/IP for broader UNIX interoperability. Bi-directional print job handling and enhanced Service Advertising Protocol (SAP) implementation further supported directory services, enabling UnixWare servers to advertise and access resources transparently. For enterprise file sharing, the NetWare UNIX Client File System provided transparent mounting and access to NetWare volumes from UnixWare, with granular access controls bridging UNIX permissions and NetWare bindery semantics. Auto-authentication streamlined user sessions across protocols, reducing administrative overhead in distributed setups. These elements emphasized causal reliability in protocol translation and load distribution, favoring proprietary cohesion over nascent open standards like NFS for high-availability NetWare integrations. Network installations over IPX further extended deployment flexibility in legacy NetWare-dominant enterprises.

Security and Reliability Enhancements

UnixWare incorporates configurable security levels, including Improved (C2) mode compliant with the U.S. Department of Defense's for controlled access protection, enabling mandatory access controls, auditing, and secure labeling of subjects and objects. This C2 capability supports selectable profiles such as Low (basic), Traditional (standard Unix), Improved (C2), and High (enhanced beyond C2), allowing administrators to enforce stricter policies on highly confidential systems without requiring full reconfiguration. In vulnerability assessments, UnixWare in C2 or above-C2 modes demonstrated resistance to common exploits when properly configured, though scanners identified potential issues resolvable via vendor patches. The operating system includes built-in auditing subsystems for tracking security-relevant events, such as user logins, file accesses, and privilege escalations, generating detailed logs via commands like auditon to enable auditing and auditrpt to report trails. Audit masks allow selective monitoring of events, including those from earlier releases, providing forensic capabilities for incident response while minimizing performance overhead in non-critical environments. File-level encryption via the crypt utility and filesystem encryption introduced in UnixWare 7.1.4 Maintenance Pack 1 protect data at rest, with compatibility for editor-based modes and support for block devices underlying filesystems. These features predated native in many competing Unix variants, offering safeguards against unauthorized in enterprise settings. For reliability, UnixWare NonStop Clusters enable high-availability configurations across 2 to 6 nodes, providing automatic and single-system image management to minimize from hardware failures or software faults. Integrated with Reliant HA extensions in the Enterprise Edition, this clustering supports scalable, fault-tolerant deployments, achieving up to 99.99% in editions through redundant components and rapid recovery mechanisms. In performance benchmarks and evaluations, NonStop Clusters demonstrated effective and for transactional workloads, though nature limited community scrutiny compared to open-source alternatives like add-ons. Empirical deployments in mission-critical environments, including telecom, validated sub-0.01% annual via automated , outperforming non-clustered Unix systems in audited metrics.

Version History

Initial Releases (UnixWare 1.x and 2.x)

UnixWare 1.0, released in November 1992, marked the debut of a commercial UNIX variant ported from System V Release 4.2 (SVR4.2) to the x86 architecture, targeting Intel 80386 and compatible processors. This initial version emphasized integration with Novell's NetWare for networked environments and included a graphical login interface, though it was primarily uniprocessor with limited scalability. Early stability focused on core SVR4.2 kernel reliability for server tasks, but hardware support was constrained to basic x86 configurations without native multiprocessor capabilities. The follow-up, UnixWare 1.1 in 1993, introduced enhancements such as expanded graphical user interface (GUI) tools, including X11R5 support with bit-mapped fonts and Type Manager integration for scalable typography. These additions improved administrative and desktop application handling, addressing feedback on the original's interface limitations while maintaining focus on x86 hardware compatibility and basic stability for enterprise entry points. UnixWare 2.0, released in 1995, advanced hardware scalability with symmetric multiprocessor (SMP) kernel support, enabling configurations beyond single-processor setups through a Platform Support Kit that abstracted multiprocessor interfaces. The kernel became fully multithreaded across the operating system, I/O subsystem, TCP/IP, NFS, IPX, and user-level threads, boosting performance for multi-CPU x86 systems. A key feature was Merge, a allowing binary execution of SCO OpenServer applications, facilitating migration and broadening software ecosystem access without source recompilation. Subsequent updates in the 2.1.x series, starting with 2.1.1 in 1996, delivered compliance with the (Unix 95), enhancing adherence and interoperability. UnixWare 2.1.2 in 1997 added baseline enhancements, including improved TCP/IP stacking for web serving. These releases incrementally expanded hardware support, such as multi-path I/O groundwork and preparations for larger memory addressing toward 64-bit transitions, while prioritizing kernel stability for mission-critical deployments on evolving x86 SMP platforms. By refining SMP threading and device abstractions, the series improved reliability under load, supporting up to licensed multi-CPU configurations for database and application servers.

Mature Versions (UnixWare 7.x Series)

UnixWare 7.0, released in 1998 by the (SCO), introduced the SVR5 kernel, which merged technologies from UnixWare 2.1.2 and SCO OpenServer 5.0, including integration with Directory Services (NDS). The kernel supported large-scale (SMP) configurations and up to 64 GB of memory, positioning it for enterprise workloads on processors. It also included a (JVM) for running applications natively. Subsequent updates in the 7.x series built on this foundation. UnixWare 7.1, released in 1999, expanded licensing options with editions for (5 users), department (25 users), and enterprise (50 users) environments, enhancing scalability for mid-sized deployments. In 2001, Caldera International acquired SCO's Unix assets and rebranded the 7.1.2 release as Open UNIX 8 to emphasize openness while maintaining binary compatibility with prior UnixWare 7 versions. This release incorporated compatibility layers, allowing select Linux binaries to run alongside UnixWare applications. UnixWare 7.1.3, issued in 2002 after SCO reacquired the Unix business, focused on administrative improvements and enhancements, succeeding Open UNIX 8 directly. The 7.1.4 update in added further ease-of-use features, bolstered capabilities, and improved hardware support, marking a major upgrade for ongoing enterprise use. Under Xinuos since 2011, the lineage continued with releases, culminating in UnixWare 7 Definitive 2018, which includes patches for modern virtualization environments like and , alongside compatibility updates for open-source components. These versions emphasize reliability, with user reports highlighting rock-solid stability and minimal downtime in mission-critical setups. Xinuos sustains active development as of 2025, delivering feature enhancements and bug fixes to support legacy enterprise applications on x86 hardware. In September 1995, , Inc. sold its business, including UnixWare, to the (SCO) through an (APA). The APA transferred specified assets such as trademarks, patents, and SVRX licenses but explicitly excluded the copyrights to Unix and UnixWare , retaining those with . SCO later contended that the agreement's intent and a subsequent conveyed full ownership of the copyrights, enabling SCO to enforce them against alleged infringers. SCO's assertions of copyright ownership underpinned its 2002–2003 campaign alleging that incorporated proprietary Unix code from SVRX, estimating over 100,000 lines derived from 's heritage, though an internal SCO code review that year identified no direct infringing code in the . SCO maintained that historical efforts to purge (BSD) code from Unix variants—following AT&T's 1984 lawsuit against BSD developers—left a core of proprietary SVRX material that formed 's foundational structure via unauthorized contributions, a position contested by arguments that much Unix-derived code entered the through settlements and open licensing. The dispute culminated in , Inc. v. , Inc., filed in 2003. A 2006 partial ruled that retained rights to direct SVRX license revenue, but the core ownership question proceeded to trial. On March 30, 2010, a federal jury verdict affirmed that the APA and its amendment did not transfer Unix SVRX copyrights to SCO; retained ownership of those core copyrights, while SCO held rights to UnixWare as a product under licensing terms. The U.S. Court of Appeals for the Tenth Circuit upheld the verdict in August 2011, rejecting SCO's claims and noting the APA's unambiguous exclusion of copyrights. Subsequent empirical code comparisons in related proceedings showed minimal verbatim copies from Unix to , with overlaps attributable to standard APIs and clean-room reimplementations rather than direct infringement of retained copyrights.

SCO Group v. IBM Litigation

In March 2003, The filed a against in the U.S. District Court for the District of Utah, alleging , misappropriation of trade secrets, with contract, and unfair competition. SCO claimed that had violated its license agreements by disclosing proprietary code and methods from IBM's AIX operating system—derived from UNIX—to developers, thereby contributing confidential UNIX elements to the open-source . SCO initially sought at least $1 billion in damages, later amending its complaint in 2004 to demand up to $5 billion, asserting that 's actions unlawfully enhanced at the expense of SCO's UNIX derivatives like UnixWare. IBM denied the allegations, arguing that its Linux contributions were lawful under the terms of its UNIX licenses and that SCO lacked evidence of specific unauthorized disclosures. IBM countersued in August 2003, seeking that it had not breached any contracts, along with claims for by SCO and unfair competition. During discovery, IBM pressed SCO to identify infringing code; SCO eventually specified fewer than 3,700 lines across 17 AIX or Dynix files allegedly contributed to , abandoning broader claims due to inability to substantiate widespread copying. Courts repeatedly criticized SCO's , with a 2006 ruling noting SCO's failure to provide concrete evidence linking alleged disclosures to code. Key rulings narrowed SCO's case progressively. In 2007, following a related decision affirming Novell's ownership of core UNIX copyrights, the district court granted partial to IBM, limiting SCO's ability to terminate IBM's AIX license and dismissing claims dependent on revoked . By 2010, most claims were resolved against SCO, including after the U.S. denied . The remaining unfair competition via misappropriation claim survived initial but faced reversal on appeal; in 2017, the Tenth Circuit vacated the district court's dismissal under New York's independent tort doctrine, remanding for further review while affirming dismissal of . SCO's 2009 complicated proceedings, with a pursuing assets, but no against was ever granted. The litigation concluded in 2021 via settlement, with paying $14.25 million to SCO's bankruptcy trustee to resolve 's lingering counterclaims, far below SCO's original demands and without validating SCO's core allegations of systematic code theft. The case underscored challenges in proving derivative code misuse in open-source contexts but resulted in no liability for on SCO's primary claims and reinforced the validity of UNIX licensing for AIX and contributions under existing agreements.

Implications for Linux and Open Source Ecosystem

In 2021, Xinuos, the successor entity holding UnixWare rights, filed a against and , alleging through the incorporation of Unix-derived code into and related antitrust violations, thereby echoing earlier claims of unauthorized use of proprietary Unix elements. The suit sought remedies including damages and scrutiny of IBM's acquisition of Red Hat, but antitrust portions were dropped in 2025 while preserving IP appeal rights, with overall resolutions occurring confidentially without admissions of liability or disruption to . This litigation highlighted ongoing tensions over whether 's model adequately compensates foundational proprietary contributions, yet empirical evidence shows development accelerated post-2003 SCO disputes, expanding from approximately 5 million lines of code in 2003 to over 30 million by 2023 through thousands of community contributors, underscoring the resilience of distributed development against legal challenges. Critics, including SCO and Xinuos executives, have contended that open source ecosystems like effectively "freeload" on decades of closed-source R&D underpinning Unix systems, such as ' investments exceeding hundreds of millions in developing core concepts like hierarchical file systems and multitasking kernels during the and , which were licensed commercially at rates up to $20,000 per entity before widespread commoditization. These arguments posit a causal , where open-source narratives overlook the origins enabling 's compliance and APIs, potentially underincentivizing future foundational research by eroding returns on . However, such views remain contested, as reimplementations often avoid direct code copying, relying instead on clean-room efforts and public standards, with no court-validated proof of systemic infringement in the resolved suits. The rise of ultimately commoditized UnixWare and similar variants by providing cost-free alternatives that captured enterprise workloads, contributing to Unix market contraction from dominance in the to niche status by the , while exposing limitations in the GPL's enforcement model compared to contracts' stricter NDAs and breach remedies. GPL's copyleft mechanism promotes sharing but struggles with aggressive monetization of derivatives, as seen in SCO/Xinuos' licensing demands, which regimes could pursue via targeted injunctions rather than community-driven compliance; this dynamic accelerated open-source adoption but revealed vulnerabilities to IP assertions rooted in historical Unix licenses, prompting enterprises to codebases for derivative risks.

Market Position, Reception, and Legacy

Commercial Deployment and Challenges

UnixWare achieved notable commercial deployment as a server operating system in enterprise settings during the , with The Santa Cruz Operation (SCO) leveraging it alongside for business applications including systems. SCO's overall revenue, heavily derived from Unix products like UnixWare, reached $58.1 million in the quarter ending September 1999, reflecting a 20% year-over-year increase driven by demand for reliable x86-based Unix solutions. By the early 2000s, UnixWare faced mounting challenges from the commoditization of server operating systems, particularly distributions offering no upfront licensing costs, which prompted migrations in cost-sensitive environments. SCO's Unix revenue, encompassing UnixWare, fell to $12.8 million in the third quarter of fiscal 2003, comprising a significant portion of total products revenue but signaling broader erosion in proprietary Unix market share as server sales grew 26.7% year-over-year in 2002 while Unix declined 10%. Migrations to Linux variants like often yielded 20-50% initial cost savings through and commodity hardware, yet independent analyses highlighted potential higher (TCO) for in reliability-focused audits, where proprietary Unix systems demonstrated fewer patching needs and simpler clustering for mission-critical workloads. UnixWare persisted in niches requiring certified stability, such as financial back-end systems, where Unix variants supported high-volume over open-source alternatives due to established vendor support and reduced vulnerability exposure in controlled environments.

Competition Dynamics with Linux and Other Unix Variants

UnixWare's proprietary development model provided a cohesive, SVR4-derived under strict , sidestepping the fragmentation inherent in 's open-source , where divergent distributions and forks complicate unified patching and compatibility. fragmentation, evidenced by hundreds of active distributions and kernel variants, has been critiqued for diluting efforts and prolonging vulnerability remediation across ecosystems. This control in UnixWare ensured consistent behavior, appealing to enterprises prioritizing predictability over 's flexibility. In contrast to RISC-centric proprietary Unix variants like Solaris (tied to processors) and (initially on ), UnixWare's native x86 support capitalized on commoditized hardware, eroding the premium pricing of vendor-specific RISC systems and enabling lower total ownership costs for x86 deployments. By the mid-1990s, x86's scalability undercut RISC architectures' performance claims in cost-sensitive markets, positioning UnixWare as a more accessible alternative for standard servers. The SCO Group's litigation asserting Unix intellectual property infringements in , initiated in 2003 against and others, generated prolonged uncertainty around proprietary Unix licensing, indirectly channeling enterprise migrations toward by highlighting risks in vendor-locked models despite SCO's ownership of UnixWare rights. Courts ultimately invalidated key SCO claims by 2010, but the disputes eroded confidence in sustained proprietary Unix investment, bolstering 's momentum through and validated open-source viability. UnixWare garnered recognition for superior in real-time extensions, leveraging kernel tuning for bounded latencies in mission-critical workloads, where Linux's preemptive scheduling often yielded variable response times without additional patches. analyses reflect UnixWare's closed-source advantages, with minimal disclosed CVEs versus the kernel's accumulation of over 10,000 entries by 2024, stemming from broader scrutiny and code exposure in open distributions. This lower vulnerability footprint supported UnixWare's niche in regulated environments demanding verifiable stability.

Enduring Role in Enterprise Environments

Despite its diminished prominence amid the rise of and commoditized alternatives, UnixWare persists in select enterprise environments prioritizing vendor-guaranteed stability and accountability for mission-critical workloads. As of , Xinuos continues active development and maintenance of UnixWare 7, positioning it as a reliable platform for legacy applications where single-vendor support mitigates risks associated with distributed open-source maintenance models. This appeal stems from UnixWare's proven track record in high-stakes operations, where enterprises value the absence of community-driven fragmentation over the flexibility of open ecosystems, enabling sustained operation of Unix-derived innovations without dilution from unlicensed modifications. In audit-intensive sectors such as and regulated industries, UnixWare's structure facilitates compliance with stringent and liability requirements, as organizations seek verifiable accountability from a dedicated rather than opaque, contributor-dependent codebases. Xinuos reports thousands of deployments underpinning business-critical functions, including network services and , underscoring its role in environments intolerant of the opacity inherent in open-source alternatives. While overall Unix variants hold a marginal share of the server OS market—trailing Linux's dominance at approximately 63% and Windows—the causal necessity for auditable, vendor-backed systems preserves UnixWare's niche utility, influencing hybrid architectures that integrate Unix elements for reliability in core . This enduring footprint reflects a deliberate enterprise preference for causal predictability over hype-driven adoption, as Unix systems like UnixWare avoid the vendor proliferation that can complicate in critical deployments.

Open Source and Third-Party Contributions

SCO Skunkware Program

The SCO Skunkware program, initiated by The (later International and ) in the late , involved the porting, compilation, and free distribution of packages tailored for SCO's Unix variants, including UnixWare 7 and . This effort provided pre-built binaries installable via standard package tools like pkgadd, enabling users to deploy applications without manual compilation on SCO hardware. By 1998, Skunkware distributions were bundled with new OS releases on , expanding the ecosystem for SCO systems while preserving the closed-source kernel and core utilities. Key components included ports of the Apache HTTP server (e.g., version 1.3.6 for UnixWare 7, dependent on graphics libraries and Java servlet kits), Samba for cross-platform file sharing, and Squid proxy server, which facilitated web hosting and network services on SCO platforms. Other notable releases encompassed BIND for DNS resolution and Sendmail for email handling, contributing to UnixWare's viability in enterprise networking before widespread Linux adoption around 2000. These ports empirically supported early web serving deployments, as evidenced by their integration in production environments for SMB interoperability and HTTP traffic management, without requiring users to navigate source-level adaptations. Perl interpreter ports were also available, aiding scripting and automation tasks common in Unix administration. The program's selective focus on user-space applications fostered developer adoption by reducing porting barriers, yet it maintained SCO's proprietary stance by not contributing kernel-level modifications back to upstream open-source projects or adopting full reciprocal licensing like the GPL for system components. This approach contrasted with fully open ecosystems, prioritizing compatibility enhancements over wholesale code surrender, though it drew from community-developed software under permissive licenses.

Compatibility Layers and Hybrid Approaches

UnixWare versions from 7.1.2 onward incorporated a Linux Kernel Personality compatibility layer, enabling the execution of unmodified ELF binaries alongside native UnixWare applications. This subsystem translated Linux system calls to UnixWare equivalents, providing access to tools and libraries without requiring recompilation or full platform migration. Introduced by International as part of efforts to enhance interoperability, the layer supported mounting Linux filesystems under /linux and invoking a Linux environment via simple commands, facilitating gradual integration of OSS components into established UnixWare deployments. Hybrid approaches further bridged UnixWare to Linux ecosystems through . Xinuos-maintained UnixWare 7 Definitive 2018 includes Lennox KVM support, allowing UnixWare to host virtual guests, though primary configurations emphasize UnixWare as a guest on Linux KVM hosts for modernization paths. This setup permits legacy UnixWare applications to run in isolated virtual machines on scalable infrastructure, preserving UnixWare's SVR5-certified reliability—demonstrated in enterprise environments since 1998—while leveraging 's hardware support and OSS tooling. Such hybrids mitigate risks associated with abrupt migrations, as UnixWare's fault-tolerant features, like process replication, remain intact without exposure to variances. In NonStop Clusters extensions, UnixWare enabled single-system-image clustering for , with underlying technologies influencing open-source adaptations like OpenSSI for . While direct guest support in UnixWare clusters was limited, the framework allowed hybrid scaling by combining UnixWare nodes with -based load balancing, prioritizing verifiable stability over full OSS dependency. Xinuos continues to advocate these methods for container-adjacent , where legacy applications are encapsulated in VMs rather than native containers, ensuring compliance with UnixWare's deterministic performance model.

References

  1. http://www.lib.ru/UNIXFAQ/faq-unixware-general.txt
  2. https://gunkies.org/wiki/UnixWare
  3. https://www.xinuos.com/products/unixware-7/
  4. https://www.sec.gov/Archives/edgar/data/1102542/000095013407020063/v33836e10vq.htm
  5. http://www.catb.org/~esr/hackerlore/sco-vs-ibm.html
  6. https://www.ericgoldman.org/Articles/scovunix.pdf
  7. https://www.krsaborio.net/unix-scalability/research/1992/0616.html
  8. https://unix.org/what_is_unix/history_timeline.html
  9. https://www.krsaborio.net/unix/research/1993/0614.htm
  10. https://www.abortretry.fail/p/the-history-of-novell
  11. https://www.networkcomputing.com/network-infrastructure/opinion-novell-buys-unix-again
  12. https://www.techmonitor.ai/technology/novell_releases_version_11_of_unixware/
  13. https://www.os2museum.com/wp/netware-history/netware-timeline/
  14. https://support.novell.com/techcenter/articles/ana19950305.html
  15. https://www.hpcwire.com/1995/11/17/pentium-pro-round-up-ii-unisys-novell-micronics-announce-support/
  16. https://www.novell.com/news/press/archive/1995/12/pr95274.html
  17. https://www.nytimes.com/1995/09/21/business/novell-to-sell-its-unix-business-in-a-deal-worth-59.5-million.html
  18. https://www.deseret.com/1995/9/24/19194280/seeking-its-roots-novell-prunes-out-unix/
  19. https://archiveos.org/unixware/
  20. https://www.cnet.com/tech/tech-industry/sco-adds-cluster-feature-to-operating-system/
  21. https://www.hpcwire.com/1999/01/08/sco-unixware-nonstop-cluster-posts-specint_rate95-benchmark/
  22. https://igsi.tripod.com/unix.htm
  23. https://www.sco.com/developers/products/devkits.html
  24. https://www.operating-system.org/betriebssystem/_english/bs-unixware.htm
  25. https://www.cnet.com/tech/tech-industry/caldera-completes-unix-acquisition/
  26. https://www.zdnet.com/article/caldera-sweetens-deal-for-scos-unix-products/
  27. https://www.computerworld.com/article/1333453/sco-name-returns-as-caldera-rebrands-itself.html
  28. https://www.theregister.com/2002/08/27/sco_lives_caldera_reinvents_itself/
  29. https://www.informationweek.com/software-services/more-details-on-sco-s-linux-suit
  30. https://www.wired.com/2010/03/unix-copyrights/
  31. https://www.computerworld.com/article/1722514/sco-q3-unix-revenue-down-16-8-overall-revenue-up-23.html
  32. https://www.computerworld.com/article/1712609/sco-group-revenue-drops-58-losses-increase-as-legal-fight-continues.html
  33. https://www.zdnet.com/article/failing-sco-sees-linux-licence-revenue-plunge/
  34. https://www.theregister.com/2002/12/14/sco_completes_rebirth_with_unixware/
  35. https://www.cnet.com/tech/computing/sco-group-files-for-bankruptcy-protection/
  36. https://www.cnet.com/tech/tech-industry/sco-group-admits-it-may-fold/
  37. https://www.prnewswire.com/news-releases/unxis-completes-purchase-of-sco-unix-assets-119609744.html
  38. https://channelbuzz.ca/2016/01/xinuos-launches-modernization-of-sco-openserver-with-openserver-10-16068/
  39. https://www.sco.com/products/unixware714/
  40. https://www.xinuos.com/update-pack-1-and-maintenance-pack-1-now-available-for-unixware-7-definitive-2018/
  41. https://www.xinuos.com/features-and-fixes-since-unixware-7-1-4-maintenance-pack-4-mp4/
  42. https://www.novell.com/news/press/archive/1995/03/pr00026.html
  43. http://uw714doc.xinuos.com/en/SDK_netapi/sockC.basics.html
  44. https://blakeley.com/rooms/my-articles/Unixware.PCW210394.html
  45. https://www.sco.com/products/unixware/datacenter/index.html
  46. https://www.linux.com/news/review-unixware-714-suitable-basic-server-duty/
  47. https://www.networkworld.com/article/868963/software-sco-unixware.html
  48. http://uw714doc.xinuos.com/en/SEC_audit/_Audit_Event_Masks.html
  49. http://uw714doc.xinuos.com/en/FEATS/features_714mp.html
  50. http://uw714doc.xinuos.com/en/man/html.1/crypt.1.html
  51. https://www.hpe.com/psnow/doc/c04283579
  52. https://www.sco.com/products/unixware/enterprise/index.html
  53. https://public.dhe.ibm.com/software/mktsupport/techdocs/projmont.pdf
  54. https://support.novell.com/techcenter/articles/ana19950903.html
  55. https://www.sco.com/products/merge/
  56. https://www.edn.com/sco-announces-unix-95-compliance-update-to-its-operating-system/
  57. https://www.krsaborio.net/unix-scalability/research/1997/0407.html
  58. https://ridl.cfd.rit.edu/products/manuals/sunix/scsi/2203/html/UNIXWARE.HTM
  59. http://www.faqs.org/faqs/unix-faq/unixware/general/
  60. https://www.techmonitor.ai/technology/sco_sets_out_unixware_7_roadmap
  61. https://www.sco.com/products/unixware/business/index.html
  62. https://www.zdnet.com/article/caldera-loads-linux-apps-on-unixware/
  63. https://www.osnews.com/story/5416/unixware-713-review/
  64. https://www.e-channelnews.com/sco-announces-broad-array-of-new-unix-products-channel-support-and-training-programs/
  65. https://www.xinuos.com/wp-content/uploads/UnixWare7D2M1-ReleaseNotes-201712.pdf
  66. https://www.g2.com/products/sco-unixware-7/reviews
  67. https://www.osnews.com/story/141690/unixware-in-2025-still-actively-developed-and-maintained/
  68. https://www.xinuos.com/wp-content/uploads/Features-and-Fixes-Since-UnixWare-7-press-release.pdf
  69. https://www.cnet.com/tech/services-and-software/contract-illuminates-novell-sco-spat/
  70. https://www.steptoe.com/a/web/4536/254b.pdf
  71. https://arstechnica.com/uncategorized/2005/07/5099-2/
  72. https://arstechnica.com/information-technology/2010/03/sco-loses-again-jury-says-novell-owns-unix-svrx-copyrights/
  73. https://natlawreview.com/article/sco-can-t-claim-ownership-unix-operating-system
  74. https://lwn.net/Articles/924577/
  75. https://www.theregister.com/2004/02/07/sco_abandons_trade_secret_attack/
  76. https://www.cnet.com/tech/tech-industry/sco-claim-reaches-5-billion/
  77. https://law.justia.com/cases/federal/appellate-courts/ca10/16-4040/16-4040-2017-10-30.html
  78. https://www.scl.org/1006-the-sco-open-source-litigation-saga-the-community-fights-back/
  79. https://caselaw.findlaw.com/us-10th-circuit/1884893.html
  80. https://www.scotusblog.com/wp-content/uploads/2010/03/09-1061_pet.pdf
  81. https://arstechnica.com/tech-policy/2017/10/appeals-court-keeps-alive-the-never-ending-linux-case-sco-v-ibm/
  82. https://www.theregister.com/2021/08/30/sco_tsg_vs_ibm_settlement/
  83. https://www.zdnet.com/article/after-almost-20-years-the-sco-vs-ibm-lawsuit-may-finally-be-ending/
  84. https://www.xinuos.com/xinuos-sues-ibm-and-red-hat/
  85. https://www.prnewswire.com/news-releases/xinuos-sues-ibm-and-red-hat-for-antitrust-violations-and-copyright-infringement-alleges-ibm-has-been-misleading-its-investors-since-2008-301259756.html
  86. https://news.bloomberglaw.com/antitrust/xinuos-ibm-agree-to-toss-antitrust-claims-leave-ip-issue-open
  87. https://www.cnet.com/tech/services-and-software/sco-warns-open-source-community/
  88. https://interestingengineering.com/innovation/unix-building-the-most-important-os-in-the-world
  89. https://corporate.findlaw.com/business-operations/the-risks-of-open-source-software.html
  90. https://www.techmonitor.ai/technology/sco_ends_four_year_slump_with_17m_profits_new_business
  91. https://www.information-age.com/unix-loses-ground-as-server-market-stabilises-23897/
  92. https://www.serverwatch.com/os/is-unix-cheaper-than-linux/
  93. https://www.quora.com/Why-do-top-banks-use-UNIX-as-a-back-end-OS-for-the-transactions-server-and-not-Linux
  94. https://financialit.net/workstation-os/unix
  95. https://www.dedoimedo.com/computers/linux-fragmentation-sum-egos.html
  96. https://danwalsh.livejournal.com/424.html
  97. https://www.linkedin.com/pulse/story-risc-x86-linux-e-bruce-turgeon-ucupc
  98. https://www.stromasys.com/resources/comparing-unix-versions-aix-hp-ux-and-solaris/
  99. https://www.cvedetails.com/top-50-products.php
  100. https://www.linuxjournal.com/article/5407
  101. https://www.xinuos.com/products/
  102. https://www.sco.com/5reasons/
  103. https://www.xinuos.com/wp-content/uploads/Xinuos-Data-Sheet-UnixWare-7-Definitive-2018-4-page.pdf
  104. https://www.sco.com/products/unix/
  105. https://www.xinuos.com/company/
  106. https://www.usenix.org/legacyurl/linux-emulation-sco-getting-started
  107. https://www.sco.com/skunkware/
  108. https://www.sco.com/skunkware/net/index.html
  109. https://www.sco.com/skunkware/relnotes.html
  110. https://www.scosales.com/skunkware/uw7/COMPONENTS.html
  111. https://aplawrence.com/FAQ_scotec6skunkware.html
  112. https://www.xinuos.com/wp-content/uploads/UnixWare7D2M1b-ReleaseNotesSupplement-220305.pdf
  113. https://www.scosales.com/ta/kb/128003.html
  114. https://sourceforge.net/p/ssic-linux/news/
Add your contribution
Related Hubs
Contribute something
User Avatar
No comments yet.