The “Unix wars” of the late 1980s and 1990s — competing, incompatible commercial Unix variants each vying for dominance — nearly fragmented Unix into irrelevance, and understanding it explains why Linux’s later unifying role mattered so much.
The Fragmentation
AT&T’s System V and Berkeley’s BSD diverged into genuinely incompatible dialects, and commercial vendors (Sun’s SunOS/Solaris, IBM’s AIX, HP-UX, SGI’s IRIX) each added their own proprietary extensions on top — a program written for one Unix variant frequently wouldn’t compile, let alone run, on another without modification.
Standardization Attempts
POSIX emerged specifically to define a common baseline API that all these fragmented variants could at least nominally claim compliance with — a genuine attempt to paper over the fragmentation, though vendors still differentiated heavily beyond the POSIX baseline.
Why Linux Ultimately Mattered So Much Here
Linux (paired with the GNU userland) offered something none of the fragmented commercial Unix variants could: a single, free, genuinely open codebase that anyone could build on without vendor lock-in or licensing fees — as commercial Unix vendors consolidated or declined through the 2000s, Linux effectively became the de facto unifying “Unix” for a new generation, succeeding where formal standardization efforts alone hadn’t fully resolved the fragmentation.