Hubbry Logo
History of UnixHistory of UnixMain
Open search
History of Unix
Community hub
History of Unix
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
History of Unix
History of Unix
from Wikipedia

Unix
Evolution of Unix and Unix-like systems
DeveloperKen Thompson, Dennis Ritchie, Brian Kernighan, Douglas McIlroy, and Joe Ossanna at Bell Labs
Written inC and Assembly language
OS familyUnix
Working stateCurrent
Source modelHistorically closed source, now some Unix projects (BSD family and Illumos) are open sourced.
Initial release1969; 57 years ago (1969)
Available inEnglish
Kernel typeMonolithic
Default
user interface
Command-line interface & Graphical (X Window System)
LicenseProprietary
Official websiteopengroup.org/unix

The history of Unix dates back to the mid-1960s, when the Massachusetts Institute of Technology, Bell Labs, and General Electric were jointly developing an experimental time-sharing operating system called Multics for the GE-645 mainframe.[1] Multics introduced many innovations, but also had many problems. Bell Labs, frustrated by the size and complexity of Multics but not its aims, slowly pulled out of the project. Their last researchers to leave Multics – among them Ken Thompson, Dennis Ritchie, Doug McIlroy, and Joe Ossanna[2] – decided to redo the work, but on a much smaller scale.[3]

In 1979, Ritchie described the group's vision for Unix:[3]

What we wanted to preserve was not just a good environment in which to do programming, but a system around which a fellowship could form. We knew from experience that the essence of communal computing, as supplied by remote-access, time-shared machines, is not just to type programs into a terminal instead of a keypunch, but to encourage close communication.

1960s

[edit]

Multics

[edit]

In the late 1960s, Bell Labs was involved in a project with MIT and General Electric to develop a time-sharing system, called Multics, allowing multiple users to access a mainframe simultaneously. A key concept of the Multics system was the use of a single-level store. In this concept, there is no directly accessible file system. Instead, programs simply refer to data as if it is already in memory; if it is not, the virtual memory (VM) system loads it automatically. This means programs do not have to write code to explicitly read and write data from files into memory to manipulate it, the operating system does this all invisibly.[4]

The Multics project began to bog down, and it became clear to the Bell team that the system was unlikely to deliver a working operating system in the near term, let alone a reasonably performant one.[4] Bell Labs management ultimately withdrew from the project, and it seemed likely the company was going to end their lease on the very expensive GE 645 mainframe.[5] Ken Thompson, a programmer in the Labs' computing research department, enjoyed the flexibility of Multics and began considering a new operating system that could run on less sophisticated machines.[4]

New system

[edit]

The basic concept was to use Multics' hierarchical file system, but remove the single-level store.[4] Thompson felt that the idea of a single-level store was ultimately a bad one, as it treats all memory the same, whether program code or data, when in actual use they were treated very differently. Program code is rarely modified at runtime, may be placed in a read-only area of memory, and is randomly accessed due to branching. In contrast, data are almost always writable, as runtime modification of file data is often the entire point of the program, and sequential access, as opposed to random, is a normal means of access. While his new system would require programmers to write their own routines to load and save data, that did not appear to be unreasonable.[4]

Thompson began writing simulations of the new system under Multics, to understand the paging performance of the system. As this appeared promising, Thompson began writing the system for the GE 645, starting with a new custom assembly language. It soon became clear that the 645 would be gone in some months, and the work was abandoned.[6] Throughout this period, Thompson also repeatedly petitioned management to purchase a smaller system than the GE 645 in order to build a similarly programmer-friendly operating system. Management refused all of these requests.[5]

Space Travel, move to PDP-7

[edit]

In 1969, Thompson had also written a video game, Space Travel, under the GECOS operating system on the smaller GE 635 machine. This had the problem that a typical game cost $75 ($643.10 in 2024) worth of billable CPU runtime.[6] When he learned that Visual and Acoustics Research[7] department had a small PDP-7 that was largely unused, he began to rewrite the game for this machine.[6] This was initially performed by building a binary for the PDP-7 using a cross compiler on the 635, and then moving the resulting code to the PDP-7 using paper tape.[6]

This became tedious, and Thompson began considering writing his new operating system on the new machine. This was aided by a timely vacation by his wife, leaving him with a month to work on it full time.[8] Aided by Ritchie and Rudd Canaday, they implemented a version of the hierarchical file system Thompson had studied on the GE 645. The ability to start programs stored in that file system soon followed,[6] and then small programs to copy, delete, print and edit those files, along with a command-line interpreter to allow the user to perform all of these operations interactively. With these in place, a new assembler was written for the machine, and Space Travel moved entirely to the new platform.[9]

A key concept that was added during this period was made by Ritchie,[6] the concept of a device file. This was a file in the file system with the special ability to perform input/output operations. This allowed different devices to be supported simply by placing a file in an appropriate location in the file system. Read and write operations accessing these pseudo-files would perform operations on the device itself. This meant that devices were abstracted away through the file system, and programs could manipulate files no matter what sort of device they were on.[10]

Douglas McIlroy then ported TMG compiler-compiler to PDP-7 assembly, creating the first high-level language running on Unix. Thompson used this tool to develop the first version of his B programming language.[3]

1970s

[edit]
Ken Thompson and Dennis Ritchie
Version 7 Unix for the PDP-11, running in SIMH
Unix time-sharing at the University of Wisconsin, 1978

The new operating system was initially without organizational backing, and without a name. At this stage, the new operating system was a singletasking operating system,[3] not a multitasking one such as Multics. The name Unics (Uniplexed Information and Computing Service, pronounced as "eunuchs"), a pun on Multics (Multiplexed Information and Computer Services), was initially suggested for the project in 1970. Brian Kernighan claims the coining for himself, and adds that "no one can remember" who came up with the final spelling Unix.[11] Dennis Ritchie and Doug McIlroy also credit Kernighan.[3][12]

When the Computing Sciences Research Center wanted to use Unix on a machine larger than the PDP-7, while Bell Labs Patent Department[13] needed a word processor, Thompson and Ritchie added text processing capabilities to Unix and received funding for a PDP-11/20.[14][15] For the first time in 1970, the Unix operating system was officially named and ran on the PDP-11. A text-formatting program called roff and a text editor were added. All three were written in PDP-11 assembly language. Bell Labs used this initial text-processing system, consisting of Unix, roff, and the editor, for text processing of patent applications. Roff soon evolved into troff, the first electronic publishing program with full typesetting capability.

As the system grew in complexity and the research team wanted more users, the need for a manual grew apparent. The UNIX Programmer's Manual was published on 3 November 1971; commands were documented in the "man page" format that is still used, offering terse reference information about usage as well as bugs in the software, and listing the authors of programs to channel questions to them.[12]

As other Bell Labs departments purchased DEC PDP-11s, they also chose[16] to run Unix instead of DEC's own operating system. By Version 4 it was widely used within the laboratory and a Unix Support Group was formed, helping the operating system survive by formalizing its distribution.[14][12]

In 1973, Version 4 Unix was rewritten in the higher-level language C, contrary to the general notion at the time that an operating system's complexity and sophistication required it to be written in assembly language.[17][14] The C language appeared as part of Version 2. Thompson and Ritchie were so influential on early Unix that McIlroy estimated that they wrote and debugged about 100,000 lines of code that year, stating that "[their names] may safely be assumed to be attached to almost everything not otherwise attributed".[12] Although assembly did not disappear from the man pages until Version 8,[12] the migration to C suggested portability of the software, requiring only a relatively small amount of machine-dependent code to be replaced when porting Unix to other computing platforms. Version 4 Unix, however, still had considerable PDP-11-dependent code and was not suitable for porting.

The Unix operating system was first presented formally to the outside world at the 1973 Symposium on Operating Systems Principles, where Ritchie and Thompson delivered a paper.[18] This led to requests for the system, but under a 1956 consent decree in settlement of an antitrust case, the Bell System (the parent organization of Bell Labs) was forbidden from entering any business other than "common carrier communications services", and was required to license any patents it had upon request. Unix could not, therefore, be turned into a product. Bell Labs instead shipped the system for the cost of media and shipping.[8] Ken Thompson quietly began answering requests by shipping out tapes and disks.[19] The only recovered Unix v4 tape as of 2025 had been sent by Thompson to the University of Utah on May 31, 1974.[20][21]

In 1973, AT&T released Version 5 Unix and licensed it to educational institutions, and licensed 1975's Version 6 to companies for the first time,[22] starting with Yourdon, Inc.[23] While commercial users were rare because of the US$20,000 (equivalent to $116,871 in 2024) cost, the latter was the most widely used version into the early 1980s. Anyone could purchase a license, but the terms were very restrictive; licensees only received the source code, on an as-is basis.[22] The licenses also included the machine-dependent parts of the kernel, written in PDP-11 assembly language. Copies of the Lions' Commentary on UNIX 6th Edition, with Source Code circulated widely, which led to considerable use of Unix as an educational example. The first meeting of Unix users took place in New York in 1974, attracting a few dozen people; this would later grow into the USENIX organization. The importance of the user group stemmed from the fact that Unix was entirely unsupported by AT&T,[8] although from about 1975 it was the standard for building operational systems within the company.[24]

Versions of the Unix system were determined by editions of its user manuals;[22] for example, "Fifth Edition UNIX" and "UNIX Version 5" have both been used to designate the same version. The Bell Labs developers did not think in terms of "releases" of the operating system, instead using a model of continuous development, and sometimes distributing tapes with patches (without AT&T lawyers' approval).[8] Development expanded, adding the concept of pipes, which led to the development of a more modular code base, and quicker development cycles. Version 5, and especially Version 6, led to a plethora of different Unix versions both inside and outside Bell Labs, including PWB/UNIX and the first commercial Unix, IS/1.

Unix still only ran on DEC systems.[22] As more of the operating system was rewritten in C (and the C language extended to accommodate this), portability also increased; in 1977, Bell Labs procured an Interdata 8/32 with the aim of porting Unix to a computer that was as different from the PDP-11 as possible, making the operating system more machine-independent in the process. Unix next ran as a guest operating system inside a VM/370 hypervisor at Princeton. Simultaneously, a group at the University of Wollongong ported Unix to the similar Interdata 7/32.[25][26] Target machines of further Bell Labs ports for research and AT&T-internal use included an Intel 8086-based computer (with custom-built MMU) and the UNIVAC 1100.[27][14]

In May 1975, ARPA documented the benefits of the Unix time-sharing system which "presents several interesting capabilities" as an ARPA network mini-host in RFC 681.

In 1978, UNIX/32V was released for DEC's then new VAX system. By this time, over 600 machines were running Unix in some form. Version 7 Unix, the last version of Research Unix to be released widely, was released in 1979. In Version 7, the number of system calls was only around 50, although later Unix and Unix-like systems would add many more:[28]

Version 7 of the Research UNIX System provided about 50 system calls, 4.4BSD provided about 110, and SVR4 had around 120. The exact number of system calls varies depending on the operating system version. More recent systems have seen incredible growth in the number of supported system calls. Linux 3.2.0 has 380 system calls and FreeBSD 8.0 has over 450.

A microprocessor port of Unix, to the LSI-11, was completed in 1978,[29] and an Intel 8086 version was reported to be "in progress" the same year.[25] The first microcomputer versions of Unix, and Unix-like operating systems like Whitesmiths' Idris, appeared in the late 1970s.[22]

1980s

[edit]
LSI ADM-3A terminal, physical interface for BSD Unix
The DEC VT100 terminal, widely used for Unix timesharing
USENIX 1984 Summer speakers. USENIX was founded in 1975, focusing primarily on the study and development of Unix and similar systems.
The X Window System with twm and a number of core X applications

Bell developed multiple versions of Unix for internal use, such as CB UNIX (with improved support for databases) and PWB/UNIX, the "Programmer's Workbench", aimed at large groups of programmers. It advertised the latter version, as well as 32V and V7, stating that "more than 800 systems are already in use outside the Bell System" in 1980,[30] and "more than 2000" the following year.[31] Research Unix versions 8 (1985[32][33]), 9 (1986[34][33]), and 10 (1989[35][36][33][37]) were developed through the 1980s but were only released to a few universities, though they did generate papers[38] describing the new work.[citation needed]

  • "Many of the (Version 10 Unix) medium-size tool programs (and their documentation) survived into the Plan 9 system, and are described in its programmer's manual and its own collection of papers."
  • "Even so, the lesser-known editions within AT&T's Unix System Laboratories were the Eighth Edition in 1985, the Ninth Edition in 1986, and in 1989 the Tenth Edition".[35][39]

This research focus then shifted to the development of Plan 9, a new portable distributed operating system, and later of Inferno.

Perkin-Elmer began distributing Wollongong Unix for Interdata as Perkin-Elmer Edition 7, the first version supported by a computer company.[26] Microcomputer Unix became commercially available in 1980, when Onyx Systems released its Zilog Z8000-based C8002[22] and Microsoft announced its first Unix for 16-bit microcomputers called Xenix, which the Santa Cruz Operation (SCO) ported to the 8086 processor in 1983. Other companies began to offer commercial versions of Unix for their own minicomputers and workstations. Many of these new Unix flavors were developed from the System V base under a license from AT&T; others were based on BSD. One of the leading developers of BSD, Bill Joy, went on to co-found Sun Microsystems in 1982 and created SunOS for its workstations.

Because AT&T widely and inexpensively licensed Unix, thousands of students trained on it unlike rivals such as Pick. By the 1980s "hundreds of software programs were written for Unix because the author didn't know anything else", an analyst said.[40][41][42] As computer science students moved from universities into companies they wanted to continue to use it. Observers began to see Unix as a potential universal operating system, suitable for all computers. Less than 20,000 lines of code – almost all in C – composed the Unix kernel as of 1983, and more than 75% was not machine-dependent. By that year Unix or a Unix-like system was available for at least 16 different processors and architectures from about 60 vendors; BYTE noted that computer companies "may support other [operating] systems, but a Unix implementation always happens to be available".[14][22][43] The Ingres database was an example of software that benefited from running on Unix compared to IBM System R, which did not.[41]

DEC and IBM were examples of companies that supported Unix.[44] Although DEC[45] and IBM[46] were both reluctant to offer alternative to their proprietary operating systems, by the mid-1980s they and most other computer companies did so. An industry analyst said that Prime Computer released Primix, for example, to prevent customers from leaving for lack of Unix support.[47]

AT&T announced UNIX System III – based on Version 7, and PWB – in 1981. Licensees could sell binary sublicenses for as little as US$100 (equivalent to $345.86 in 2024), which observers believed indicated that AT&T now viewed Unix as a commercial product.[22] This also included support for the VAX. AT&T continued to issue licenses for older Unix versions. To end the confusion between all its differing internal versions, AT&T combined them into UNIX System V Release 1. This introduced a few features such as the vi editor and curses from the Berkeley Software Distribution of Unix developed at the University of California, Berkeley Computer Systems Research Group. This also included support for the Western Electric 3B series computers. AT&T provided support for System III and System V through the Unix Support Group (USG), and these systems were sometimes referred to as USG Unix.[citation needed]

In 1983, the U.S. Department of Justice settled its second antitrust case against AT&T, causing the breakup of the Bell System. This relieved AT&T of the 1956 consent decree that had prevented the company from commercializing Unix. AT&T promptly introduced Unix System V into the market. The newly created competition nearly destroyed the long-term viability of Unix, because it stifled the free exchanging of source code and led to fragmentation and incompatibility.[19] The GNU Project was founded in the same year by Richard Stallman.

Since the newer commercial UNIX licensing terms were not as favorable for academic use as the older versions of Unix, the Berkeley researchers continued to develop BSD as an alternative to UNIX System III and V. Many contributions to Unix first appeared in BSD releases, notably the C shell with job control (modelled on ITS). Perhaps the most important aspect of the BSD development effort was the addition of TCP/IP network code to the mainstream Unix kernel. The BSD effort produced several significant releases that contained network code: 4.1cBSD, 4.2BSD, 4.3BSD, 4.3BSD-Tahoe ("Tahoe" being the nickname of the Computer Consoles Inc. Power 6/32 architecture that was the first non-DEC release of the BSD kernel), Net/1, 4.3BSD-Reno (to match the "Tahoe" naming, and that the release was something of a gamble), Net/2, 4.4BSD, and 4.4BSD-lite. The network code found in these releases is the ancestor of much TCP/IP network code in use today, including code that was later released in AT&T System V UNIX and early versions of Microsoft Windows. The accompanying Berkeley sockets API is a de facto standard for networking APIs and has been copied on many platforms.

During this period, many observers expected that UNIX, with its portability, rich capabilities, and support from companies like DEC and IBM, was likely to become an industry-standard operating system for microcomputers.[44][48] Industry analyst Jean Yates said that IBM lacked enthusiasm for Unix, however, and AT&T was the only company that could afford the "multimillion-dollar investment" necessary to help create software. Unix's lack of a killer app like VisiCalc or Lotus 1-2-3 prevented widespread adoption of the operating system on corporate desktops, she said.[46] Citing its much smaller software library and installed base than that of MS-DOS and the IBM PC, others expected that customers would prefer personal computers on local area networks to Unix multiuser systems.[49] Microsoft planned to make Xenix MS-DOS's multiuser successor;[22] by 1983 a Xenix-based Altos 586 with 512 KB RAM and 10 MB hard drive cost US$8,000 (equivalent to $25,256 in 2024).[50] BYTE reported that the Altos "under moderate load approaches DEC VAX performance for most tasks that a user would normally invoke", while other computers from Sun and MASSCOMP were much more expensive but equaled the VAX. The magazine added that both PC/IX and Venix on the IBM PC outperformed Venix on the PDP-11/23.[44] uNETix, a commercial microcomputer Unix, implemented the first Unix color windowing system.[citation needed]

Thompson and Ritchie were given the Turing Award in 1983 for their work on Unix.

UnixWorld in November 1985 reported that "the supermicro has yet to live up to its expectations; in fact, the market now seems hopelessly stalled". Unix vendors like Fortune Systems, Convergent Technologies, and Tandy Corporation had not been as successful as expected because of high prices, lack of distribution channels, difficulty in ongoing support, and competition from PC LANs and traditional minicomputers like IBM System/36 or DEC MicroVAX II.[51] Ingres ported the database from Unix to DEC's VMS for commercial viability. Demand for the VMS version was at first so much greater that the company neglected the original.[52] The beginning in 1984 of the annual Unix Expo trade show in New York reflected the growing commercial presence of Unix,[53] although Roger Sippl said that the first UniForum was "80 percent Birkenstock attendees".[45] Microsoft's Bill Gates wrote in the same UnixWorld issue that that Unix installed base was still too small, citing the lack of binary compatibility unlike MS-DOS as a reason, although he thought that Xenix could achieve 400,000 installations in the next 18 months.[54] (When Ingres ported its software back to Unix it had to support more than 40 variants of the operating system.[52])

In 1986, Computerworld wrote that "Until very recently, almost no one associated Unix with corporate data processing. [...] the operating system traveled almost exclusively in academic and technical circles ... But now — almost entirely because of strenuous efforts by AT&T — some people are beginning to perceive Unix as a viable option for large commercial installations". Unix became commercially available for the mainframe via Amdahl UTS in 1981, and now IBM started offering Unix as IX/370 and VM/IX. The total installed base of Unix, however, remained small at some 230,000 machines.[55]

Despite its academic reputation – Computerworld wrote in 1986 of "the ominous wizard images that surround Unix and its administration",[23] and InfoWorld stated in 1989, "Until recently, Unix conjured up visions of long-haired bearded technoids stuck in the bowels of an R&D lab, coding software until the wee hours of the morning" – the increasing power of microcomputers in the late 1980s, and in particular the introduction of the 32-bit Intel 80386, caused Unix to "explode" in popularity for business applications; Xenix, 386/ix, and other Unix systems for the PC-compatible market competed with OS/2 in terms of networking, multiuser support, multitasking, and MS-DOS compatibility.[56] A few years after the first UniForum "ties were outnumbering the sandals", Sippl said.[45][24]

By the late 1980s the industry recognized that RISC technology had much better performance per cost than traditional computer architectures. Minicomputer vendors developed their own RISC-based workstations to divert customers migrating from VAX VMS and other legacy systems. Whether from large older companies like DEC, Hewlett-Packard (HP), Data General, or newer ones like Sun or Solbourne, these systems ran Unix.[57] Small value-added resellers customizing Unix systems for customers were vital to the industry's growth.[24][45] During this time a number of vendors including DEC, Sun, and Addamax began building trusted versions of UNIX for high security applications, mostly designed for military and law enforcement applications.

Standardization and the Unix wars

[edit]

A problem that plagued Unix in this period was the multitude of implementations, based on either System V, BSD, or what Poul-Henning Kamp later described as a "more or less competently executed" combination of the two,[58] usually with home-grown extensions to the base systems from AT&T or Berkeley.[59] Xenix was effectively a third lineage, being based on the earlier System III.[60] The rivalry between vendors was called the Unix wars; customers soon demanded standardization[60] as did vendors such as Informix Corporation, which by the late 1980s had more than 1000 SKUs of its products to serve variants.[24]

AT&T responded by issuing a standard, the System V Interface Definition (SVID, 1985), and required conformance for operating systems to be branded "System V". In 1984, several European computer vendors established the X/Open consortium with the goal of creating an open system specification based on Unix (and eventually the SVID).[61] Yet another standardization effort was the IEEE's POSIX specification (1988), designed as a compromise API readily implemented on both BSD and System V platforms. In 1993, POSIX was mandated by the United States government for many of its own systems.[62]

In the spring of 1988, AT&T took the standardization a step further. First, it collaborated with SCO to merge System V and Xenix into System V/386.[60] Next, it sought collaboration with Sun Microsystems (vendor of the 4.2BSD derivative SunOS and its Network File System) to merge System V, BSD/SunOS and Xenix into a single unified Unix, which would become System V Release 4. AT&T and Sun, as UNIX International (UI), acted independently of X/Open and drew ire from other vendors, which started the Open Software Foundation to work on their own unified Unix, OSF/1, ushering in a new phase of the Unix wars.[60]

1990s

[edit]
Unix workstations of the 1990s, including those made by DEC, HP, SGI, and Sun
The Common Desktop Environment (CDE) was widely used on Unix workstations.

An industry analyst said in 1989 that despite OSF and UI's fierce rivalry, "Two Unixes are a lot better than 225 — which is what we have had until now".[57] The Unix wars continued into the 1990s, but turned out to be less of a threat than originally thought: AT&T and Sun went their own ways after System V.4, while OSF/1's schedule slipped behind.[60] By 1993, most commercial vendors changed their variants of Unix to be based on System V with many BSD features added. The creation of the Common Open Software Environment (COSE) initiative that year, by the major players in Unix, marked the end of the most notorious phase of the Unix wars, and was followed by the merger of UI and OSF in 1994. The new combined entity retained the OSF name and stopped work on OSF/1. By that time the only vendor using it was Digital Equipment Corporation, which continued its own development, rebranding their product Digital UNIX in early 1995. POSIX became the unifying standard for Unix systems (and some other operating systems).[60]

Meanwhile, the BSD world saw its own developments. The group at Berkeley moved its operating system toward POSIX compliance and released a stripped-down version of its networking code, supposedly without any code that was the property of AT&T. In 1991, a group of BSD developers (Donn Seeley, Mike Karels, Bill Jolitz, and Trent Hein) left the University of California to found Berkeley Software Design, Inc. (BSDi), which sold a fully functional commercial version of BSD Unix for the Intel platform, which they advertised as free of AT&T code. They ran into legal trouble when AT&T's Unix subsidiary sued BSDi for copyright infringement and various other charges in relation to BSD; subsequently, the University of California countersued.[63] Shortly after it was founded, Bill Jolitz left BSDi to pursue distribution of 386BSD, the free software ancestor of FreeBSD, OpenBSD, and NetBSD.

In 1991, USL and Novell teamed up to develop a version of System 4 for i386 and i486 computers that would combine TCP/IP and Novell's IPX/SPX networking protocols, called the Destiny Project. They formed the Univel subsidiary as a jointly owned company to develop, market, and support the product, which was given the official name UnixWare (aka SVR4.2) and was sold as Univel UnixWare 1.0 that same year. Shortly after Univel released UnixWare 1.0 produced, AT&T sold USL and its share of Univel to Novell meaning Novell now owned all of AT&T's rights to Unix. Dennis Ritchie likened this sale to the Biblical story of Esau selling his birthright for the mess of pottage.[64] Novell tried to use the fact that UnixWare combined both TCP/IP and NetWare networking technologies as a marketing tool against Windows NT, but their core markets suffered considerably. It also quickly settled the court battles with BSDi and Berkeley.[63]

In 1993, Novell decided to transfer the UNIX trademark and certification rights to the X/Open Consortium.[65] In 1996, X/Open merged with OSF, creating the Open Group. Various standards by the Open Group now define what is and what is not a UNIX operating system, notably the post-1998 Single UNIX Specification.

In 1993, Unix was used as a minor plot element in the blockbuster film Jurassic Park.[66]

In 1995, the business of administering and supporting the existing UNIX licenses, plus rights to further develop the System V code base, were sold by Novell to the Santa Cruz Operation.[67] Whether Novell also sold the copyrights would later become the subject of litigation (see below).

With the legal troubles between AT&T/Novell and the University of California over, the latter did two more releases of BSD before disbanding its Computer Systems Research Group in 1995. The BSD code lived on, however, in its free derivatives and in what Garfinkel et al. call a second generation of commercial Unix systems, based on BSD. The first exponent of these was BSDi's offering, popular at internet service providers but eventually not successful enough to sustain the company.[68] The other main exponent would be Apple Computer.

In 1997, Apple sought a new foundation for its Macintosh operating system and chose NeXTSTEP, an operating system developed by NeXT. The core operating system, which was based on BSD and the Mach kernel, was renamed Darwin after Apple acquired it. The deployment of Darwin in Mac OS X makes it, according to a statement made by an Apple employee at a USENIX conference, the most widely used Unix-based system in the desktop computer market.[citation needed]

In supercomputer list Top500 Linux eclipsed Unix 1998–2017

Meanwhile, Unix got competition from the copyleft Linux kernel, a reimplementation of Unix from scratch, using parts of the GNU project that had been underway since the mid-1980s. Work on Linux began in 1991 by Linus Torvalds; in 1998, a confidential memo at Microsoft stated, "Linux is on track to eventually own the x86 UNIX market," and further predicted, "I believe that Linux – moreso than NT – will be the biggest threat to SCO in the near future."[69]

2000s

[edit]

In 2000, SCO sold its entire UNIX business and assets to Caldera Systems, which later changed its name to The SCO Group.

The bursting of the dot-com bubble (2001–03) led to significant consolidation of versions of Unix. Of the many commercial variants of Unix that were born in the 1980s, only Solaris, HP-UX, and AIX were still doing relatively well in the market, though SGI's IRIX persisted for quite some time. Of these, Solaris had the largest market share in 2005.[70]

In 2003, the SCO Group started legal action against various users and vendors of Linux. SCO had alleged that Linux contained copyrighted Unix code now owned by the SCO Group. Other allegations included trade-secret violations by IBM, or contract violations by former Santa Cruz customers who had since converted to Linux. However, Novell disputed the SCO Group's claim to hold copyright on the UNIX source base. According to Novell, SCO (and hence the SCO Group) are effectively franchise operators for Novell, which also retained the core copyrights, veto rights over future licensing activities of SCO, and 95% of the licensing revenue. The SCO Group disagreed with this, and the dispute resulted in the SCO v. Novell lawsuit. On 10 August 2007, a major portion of the case was decided in Novell's favor (that Novell had the copyright to UNIX, and that the SCO Group had improperly kept money that was due to Novell). The court also ruled that "SCO is obligated to recognize Novell's waiver of SCO's claims against IBM and Sequent". After the ruling, Novell announced they have no interest in suing people over Unix and stated, "We don't believe there is Unix in Linux".[71][72][73] SCO successfully got the 10th Circuit Court of Appeals to partially overturn this decision on 24 August 2009 which sent the lawsuit back to the courts for a jury trial.[74][75][76]

On 30 March 2010, following a jury trial, Novell, and not The SCO Group, was "unanimously [found]" to be the owner of the UNIX and UnixWare copyrights.[77] The SCO Group, through bankruptcy trustee Edward Cahn, decided to continue the lawsuit against IBM for causing a decline in SCO revenues.[78] On 1 March 2016, SCO's lawsuit against IBM was dismissed with prejudice.

In 2005, Sun Microsystems released the bulk of its Solaris system code (based on UNIX System V Release 4) into an open source project called OpenSolaris. New SunOS technologies, notably the ZFS file system, were first released as open source code via the OpenSolaris project. Soon afterwards, OpenSolaris spawned several non-Sun distributions. In 2010, after Oracle acquired Sun, OpenSolaris was officially discontinued, but the development of derivatives continued.

Since the early 2000s, Linux is the leading Unix-like operating system and macOS leads for all Unix variants, with all other Unix variants having only a negligible market share (see Usage share of operating systems).

See also

[edit]

References

[edit]

Further reading

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia
from Grokipedia
The history of Unix traces the development of a pioneering operating system that began in 1969 at , where and created an initial version on a minicomputer following AT&T's withdrawal from the collaborative project. This effort resulted in the first official Unix edition released in November 1971, featuring a , assembler, and basic text-processing tools, marking the birth of a multi-user, multitasking environment designed for efficiency and simplicity. Over the subsequent decades, Unix evolved through successive versions, with key innovations like the introduction of in the third edition (1973) for command chaining and the rewriting of the entire system in in the fourth edition (1973), which dramatically improved portability across hardware platforms. In the 1970s, Unix gained traction beyond , with the sixth edition (1975) widely distributed to universities and research institutions, fostering an ecosystem of tools such as the in the seventh edition (1979) and early networking capabilities via . The 1980s saw commercialization and fragmentation, as released System V (1983) for broader enterprise adoption—reaching an installed base of 45,000 systems by then—while the Berkeley Software Distribution (BSD) variants, starting with 4BSD (1980), introduced innovations like TCP/IP networking in 4.2BSD (1983), laying groundwork for the . Legal battles, including the 1992 lawsuit by Unix System Laboratories against Berkeley Software Design Inc. and the over BSD code, highlighted tensions between proprietary and open development models. Standardization efforts in the late 1980s and 1990s unified the ecosystem, with the formation of X/Open in 1984 leading to the standards and the (first introduced by X/Open in the early 1990s and continued by The Open Group, formed in 1996), culminating in UNIX 95 branding (1995) and Version 3 (2001) that reconciled System V and BSD lineages. By the 1990s, Unix's influence extended to open-source derivatives like (initiated by in 1991, inspired by but rooted in Unix principles), powering servers, mobile devices, and embedded systems worldwide. Unix's legacy endures, with the broader ecosystem (dominated by ) supporting a server operating system market valued at over $25 billion as of 2024 and underpinning modern computing—including mobile OS like and Android, cloud infrastructure, and embedded systems—through its emphasis on modularity, portability, and developer tools.

Origins in the 1960s

The Multics Project

The Multics project, short for Multiplexed Information and Computing Service, began in the fall of as a cooperative effort led by MIT's Project MAC to develop an advanced operating system. The initiative involved collaboration with General Electric's Computer Department, which provided the hardware base in the form of modified GE-645 mainframes, and later included Bell Telephone Laboratories starting in 1965. The primary goals were to create a secure, multi-user system capable of supporting remote access, continuous operation, scalable resource sharing among diverse users, and reliable data management as a public utility-like computing service. Key planned features of included segmented with demand paging to enable efficient use of large address spaces, a supporting lists for secure data sharing, and dynamic linking of procedures to facilitate modular . These innovations aimed to address limitations in earlier systems like CTSS by providing robust protection mechanisms and flexible in a multi-user environment. Despite its ambitious scope, faced significant technical challenges, including performance discrepancies between simulated and actual implementations that necessitated multiple redesigns, as well as over-engineering that contributed to slow progress and escalating complexity. , which had contributed expertise in and , withdrew from the project in March 1969 due to mounting costs, underutilized equipment draining budgets, regulatory constraints from the 1956 antitrust limiting non-telecommunications activities, and frustration with the system's delayed delivery of a practical . This withdrawal marked a pivotal shift, as the experiences with ' complexities later influenced Unix's emphasis on simplicity and practicality.

Birth of Unix at Bell Labs

Following the withdrawal of Bell Labs from the Multics project in 1969 due to dissatisfaction with its complexity and slow progress, initiated informal experiments to develop a simpler operating system. Motivated by the need for an interactive environment to support text processing tasks, such as handling patent documents, and his personal interest in programming tools, Thompson began this as a hobby project using on spare equipment at Bell Labs. In August 1969, he wrote the first rudimentary and command-line shell, establishing the foundational structure for what would become Unix. Dennis Ritchie soon joined Thompson in this informal development effort, contributing ideas and code that shaped the system's early evolution. Other colleagues at , including Rudd Canaday, assisted in aspects like design, fostering a small-team collaboration driven by practical needs rather than formal directives. The project remained low-priority within the lab, allowing the developers freedom to prioritize simplicity and usability for programming and text manipulation over ambitious features. By 1970, the system acquired its initial name, Unics—short for Uniplexed Information and Computing Service—a playful pun on that highlighted its scaled-down, single-processor focus. The name was later shortened to Unix, reflecting its growing identity as a cohesive operating system. This naming evolution underscored the project's origins as a minimalist response to the earlier collaborative ambitions of , emphasizing efficiency for everyday computational tasks at .

First Implementation on PDP-7

Following ' withdrawal from the project in early 1969, repurposed an underutilized DEC minicomputer at , which had been acquired for a now-defunct circuit-analysis initiative, to prototype his ideas for a simpler operating system inspired by concepts. This choice of hardware was driven by its availability and Thompson's need for an accessible machine after losing access to the larger GE-645 used for . During the summer of 1969, while his family was away, Thompson single-handedly developed the foundational components of what would become Unix entirely in PDP-7 assembly language, including a , a basic command-line shell, and essential utilities for file manipulation and process handling. The impetus for this effort stemmed from Thompson's desire to efficiently run his simulation game Space Travel, originally written for and later ported to the ; the game's demands for file storage and execution prompted the creation of supporting system tools to test and refine the environment. By November 1969, these elements coalesced into the first functional environment, capable of and running simple programs on the . The initial PDP-7 implementation was severely constrained by the machine's architecture, featuring only 8K words of 18-bit memory, which limited the system to single-user operation without multi-user or capabilities. Despite these restrictions, this bare-bones setup marked a pivotal shift toward a portable, minimalist operating system, laying the groundwork for future expansions.

Development and Early Adoption in the 1970s

Initial Versions and the Rewrite in C

In 1970, the Unix development team at transitioned from the to the more powerful PDP-11/20 minicomputer, which provided 24 KB of core memory and enabled the implementation of multi-user features such as and a . This upgrade, with the system completed by December 1970, marked a significant advancement in Unix's capabilities, allowing it to support multiple concurrent users and fostering further development of its core components. The first formal documentation, the Unix Programmer's Manual (First Edition), was released on November 3, 1971, documenting the system as it ran on the PDP-11 and including early utilities like the line editor ed, developed by in 1969 and refined for the new hardware. Unix evolved through Versions 1 to 6 between 1971 and 1975, with incremental enhancements to its utilities and shell. Version 1 (November 1971) introduced basic text-processing tools, while Version 2 (June 1972) added support for more devices and improved the command interpreter. Version 3 (February 1973) introduced , a concept proposed by Douglas McIlroy and implemented by Thompson to enable via standard input and output, revolutionizing command chaining. Subsequent versions, including 4 (), 5 (June 1974), and 6 (May 1975), incorporated additional utilities like the roff formatter and expanded the shell's functionality, emphasizing modularity and simplicity. To overcome the limitations of assembly language, which hindered portability and maintenance on the PDP-11, began developing in 1972 as an extension of earlier languages like . By early 1973, C's core features—such as structured types and a preprocessor—were mature enough for system-level use. In the summer of 1973, and Thompson rewrote nearly the entire Unix kernel (except the bootstrap loader) in C, dramatically improving portability across hardware platforms while preserving performance. This rewrite, completed for Version 4, was presented by Thompson at the Fourth Symposium on Operating Systems Principles (SOSP) in October 1973, highlighting Unix's innovative design and influencing future operating systems.

Academic and Research Spread

In 1974, following the publication of the seminal paper "The UNIX Time-Sharing System" by and M. Ritchie in Communications of the ACM, the first external releases of Unix were distributed via to select academic and research institutions, including the (UCB). These distributions, licensed at a nominal cost due to AT&T's antitrust restrictions on commercial activities, marked Unix's transition from an internal tool to a platform for external experimentation. At , Unix saw expanded internal adoption for development tools and system maintenance, further solidifying its role in research workflows. By 1976, Unix's academic footprint grew with contributions from key figures such as , a graduate student at UCB, who developed the vi text editor as an enhancement to the existing ex editor, providing a visual interface that became a cornerstone for in research environments. That same year, engineer Mike Lesk created (UNIX-to-UNIX Copy), a utility program enabling file transfers, remote execution, and over dial-up lines, which facilitated early networking among Unix sites within the labs and beyond. This tool's implementation on approximately 82 internal machines by 1978 underscored Unix's utility for distributed collaboration in a pre-internet era. In 1977, the rewrite of Unix in the enabled its first significant port outside DEC hardware to the Interdata 8/32 , conducted by researchers Steve Johnson and Thompson. This portability effort demonstrated Unix's adaptability to diverse architectures, broadening its appeal to academic computing centers. Overall, these mid-1970s developments fostered groundbreaking research in networking protocols and system utilities, as Unix's modular design and source availability empowered institutions like UCB to innovate on tools that influenced subsequent computing paradigms.

Version 7 and Portability

Research Unix Version 7, released by Bell Laboratories in January 1979, marked a pivotal advancement in the operating system's evolution, incorporating the as its primary and providing comprehensive documentation in the form of the Unix Programmer's Manual. The , developed by , introduced structured scripting capabilities, including variables, control structures, and pipelines, which became foundational for subsequent Unix shells. This release also featured extensive manuals spanning two volumes, detailing system calls, programming tools, and user commands, facilitating broader adoption in academic and research environments. A key innovation of Version 7 was its full portability, enabled by the rewrite of the kernel and utilities in , allowing recompilation on diverse hardware without major modifications. This portability was further demonstrated in 1978 with ports to hardware like the DEC VAX-11/780 minicomputer, where developers John Reiser and Tom Lyon adapted the Version 7 codebase using a PDP-11 as a cross-compilation host. The resulting UNIX/32V system for the VAX established a precedent for Unix's migration to 32-bit architectures, influencing later commercial variants. Version 7 included essential development tools that enhanced its utility for software creation, such as (Yet Another ) for generating parsers from grammars, lex for producing lexical analyzers, and the (pcc) for compiling code across platforms. These tools, developed by researchers including and M. E. Lesk, streamlined compiler construction and program development, contributing to Unix's role as a programmer-friendly environment. The 1979 tape distribution of Version 7 represented the final free release from Bell Laboratories before the onset of commercialization efforts, with source code tapes provided to universities and research institutions under non-exclusive licenses. This distribution solidified Version 7's status as the canonical research Unix, influencing ports and derivatives in the academic community. In recognition of their foundational contributions to Unix, including the development of its portable design and implementation, Ken Thompson and Dennis Ritchie received the ACM A.M. Turing Award in 1983, with the citation emphasizing Unix's elegant architecture and impact on operating systems theory.

Commercialization in the 1980s

AT&T's Market Entry and System V

Following the 1982 consent decree that dismantled AT&T's monopoly and permitted entry into computer markets, AT&T shifted Unix from internal research tool to commercial product, enabling widespread licensing and development of standardized versions. This transition was catalyzed by the Modified Final Judgment, effective January 1, , which removed prior antitrust restrictions on software . In late 1981, announced , its first commercial Unix release, with shipments beginning in 1982; this version consolidated elements from prior internal variants like and marked the initial public distribution outside . served as a foundational commercial offering, emphasizing reliability for business applications while building on the portable implementation from earlier research editions. By 1983, released Release 1 (SVR1), establishing a unified development path under the newly formed UNIX System Development Laboratory, which merged the Computer Research Group, UNIX System Group, and Product Engineering Group to streamline commercialization efforts. SVR1 introduced key enhancements for enterprise use, including System V (IPC) mechanisms such as semaphores, message queues, and , and the System V Interface Definition (SVID) to promote portability and vendor compliance. These features positioned System V as a robust platform for professional computing, with subsequent releases like SVR2 (1984) and SVR3 (1986) expanding support for real-time extensions, remote file systems, and the framework for modular I/O processing to support networked and device-independent communications. The culmination came in 1989 with SVR4, developed jointly by and , which integrated (BSD) innovations such as TCP/IP networking protocols directly into the System V core for improved interoperability and internet readiness. SVR4 also incorporated management and enhancements, solidifying its role as a for commercial Unix implementations. AT&T's commercialization strategy through System V drove significant market adoption, with source code licensing agreements enabling vendors like to develop derivatives such as AIX (announced in 1986 and based on SVR2/SVR3), which powered 's RS/6000 workstations and mainframes for enterprise computing. By the late , System V licensing had proliferated Unix into diverse hardware ecosystems, contributing to an estimated installed base exceeding 250,000 systems globally and fostering industry-wide standardization efforts.

Berkeley Software Distribution (BSD)

In the early 1970s, the University of California, Berkeley received a copy of the Sixth Edition of Unix from Bell Labs, which laid the groundwork for subsequent enhancements by the Computer Systems Research Group (CSRG). The Berkeley Software Distribution (BSD) began in 1978 with the release of 1BSD, a set of add-ons to Version 6 Unix developed primarily by graduate student Bill Joy and his collaborators at the CSRG. This initial distribution included the Pascal programming language compiler and the ex text editor, a precursor to vi, and was distributed on approximately 30 tapes to interested parties in the first half of the year. 1BSD marked the start of Berkeley's contributions to Unix, focusing on user tools and portability rather than a full operating system replacement. Building on this foundation, the CSRG advanced BSD through intermediate releases, culminating in 4BSD in October 1980, which incorporated support introduced in the prior 3BSD and began integrating networking capabilities. Funded by the , the 4BSD project emphasized the implementation of TCP/IP protocols to support connectivity, with Joy leading the effort to enhance Unix for academic and research networks. Approximately 150 copies of 4BSD were distributed over the following nine months, establishing BSD as a robust platform for system-level innovations. The 4.2BSD release in August 1983 represented a major milestone, fully integrating the DARPA-funded TCP/IP stack along with a new fast , making it widely adopted in universities and institutions. Over 1,000 site licenses were issued within 18 months, reflecting its influence on networked computing environments. played a pivotal role in these developments, authoring key components like the vi editor and overseeing the networking implementation before co-founding in 1982, which based its operating system on BSD derivatives to power affordable workstations. Further refinements appeared in 4.3BSD, released in June 1986, which optimized performance through improvements in the system, networking stack, and , while supporting experiments with advanced kernel architectures. At (CMU), researchers integrated elements of the Mach with 4.3BSD to explore multiprocessor support and compatibility, using unmodified 4.3BSD code as the basis for their parallelization efforts. This release solidified BSD's evolution from academic add-ons to a foundational Unix variant, influencing commercial and open-source systems alike.

The Unix Wars and Standardization

In the mid-1980s, efforts to standardize Unix intensified amid growing commercial interest, but rivalries soon escalated into what became known as the . In 1984, a consortium of European vendors including , ICL, , , and Nixdorf formed X/Open to promote portable applications across Unix implementations by defining common interfaces and behaviors, selecting Unix as the foundation for open systems interoperability. The Unix Wars formally began in 1987 when AT&T and Sun Microsystems announced an alliance to develop a unified Unix system, merging features from AT&T's System V and Sun's BSD-derived SunOS to consolidate the market around System V as the dominant base. This pact faced significant opposition from other vendors wary of AT&T's influence, leading to its partial failure in achieving broad unification and sparking factional divides. In response, in 1988, a group of competitors including Digital Equipment Corporation (DEC), Hewlett-Packard (HP), and IBM established the Open Software Foundation (OSF) to create an alternative standard based on elements like IBM's AIX and Carnegie Mellon's Mach kernel, aiming for a more collaborative approach. Simultaneously, AT&T and its allies, including Sun, formed UNIX International (UI) to advance their System V-centric vision, pitting OSF against UI in a battle for control over Unix's future direction. Amid these conflicts, independent standardization progressed with the publication in 1988 of the IEEE POSIX 1003.1 standard, which defined a core set of application programming interfaces (APIs) for portability across Unix variants, focusing on commands, utilities, and system calls without favoring any proprietary base. By 1990, unification attempts continued as OSF released OSF/1, its reference implementation incorporating POSIX compliance, Mach microkernel technology, and BSD elements to serve as a neutral platform for future development. X/Open also advanced its efforts that year with the XPG3 portability guide, building on POSIX to specify broader conformance for applications. The ultimately resulted in significant fragmentation, with over 30 incompatible commercial Unix variants by 1991, which raised development costs, deterred application portability, and delayed broader market adoption by undermining Unix's promise of a unified .

The 1990s: Fragmentation and Unification

POSIX and Open Standards

In the late , efforts to standardize Unix interfaces culminated in the development of by the IEEE, with the initial standard IEEE Std 1003.1-1988 defining core system application program interfaces for portability. This was followed by its adoption as the ISO/IEC 9945-1:1990, marking a key milestone in promoting interoperability among Unix variants. Extensions soon addressed additional areas, including IEEE Std 1003.2-1992 (ratified in 1992 and adopted as ISO/IEC 9945-2:1993), which standardized shell command language and common utilities to enhance script portability across systems. The push for open standards intensified in 1993 when acquired Unix System Laboratories from in June, gaining control of the Unix . Later that year, transferred the Unix and rights to the to the X/Open Company, a aimed at unifying Unix through vendor-neutral specifications, thereby decoupling the trademark from specific implementations. In 1994, X/Open introduced the initial (also known as Spec 1170), building on to define a comprehensive set of interfaces for conformant Unix systems and enabling the UNIX 95 branding program for certified products. This was further consolidated in 1996 with the formation of The Open Group through the merger of X/Open and the , which streamlined governance of Unix standards. The following year, 1997, saw the release of Version 2, incorporating real-time extensions from IEEE Std 1003.1b-1993 to support time-critical applications in embedded and industrial environments. These standards had a profound impact on commercial Unix vendors, fostering compliance and certification that reduced fragmentation. For instance, certified under UNIX 95 and subsequent brands, while achieved similar certifications for Solaris, allowing these systems to market themselves as fully conformant Unix implementations and easing application migration across proprietary platforms.

Rise of Linux

In the late 1980s, developed , a lightweight, operating system released in 1987 to accompany his Operating Systems: Design and Implementation. Intended primarily as an educational tool for teaching operating system principles, MINIX featured a architecture and was distributed with full under a permissive license, making it accessible to students and hobbyists. Linus Torvalds, a computer science student at the University of Helsinki, began working on a new kernel in 1991 after becoming frustrated with MINIX's limitations, such as its restrictive licensing and lack of support for certain features like virtual memory and multitasking on the Intel 80386 processor. Influenced by MINIX's design and source code, which he studied extensively, Torvalds aimed to create a freely available alternative but diverged significantly by adopting a monolithic kernel architecture for better performance. On September 17, 1991, Torvalds publicly announced the initial release of Linux kernel version 0.01 via the Usenet newsgroup comp.os.minix, targeting the x86 architecture and consisting of approximately 10,000 lines of C code. This early version supported basic file systems, processes, and a simple terminal interface but lacked networking or advanced features. By early 1992, Torvalds relicensed the Linux kernel under the GNU General Public License (GPL) version 2, a copyleft license developed by Richard Stallman that ensured all modifications and derivatives would remain free and open-source. This decision, applied starting with version 0.12, facilitated collaboration and addressed concerns about proprietary restrictions in prior releases. The kernel's integration with the GNU project's userland tools—such as the GNU C compiler (GCC), Bash shell, and core utilities—transformed Linux into a functional Unix-like system, leveraging the free software ecosystem to provide a complete operating environment without relying on proprietary components. In 1993, the first comprehensive Linux distributions emerged, simplifying installation and packaging the kernel with tools, , and other software. The (SLS), initially released in 1992 but gaining prominence through updates like version 1.02, became a key example, offering bootable floppies and support for TCP/IP networking. These distributions spurred adoption in academic settings, where Linux's low cost and source availability appealed to universities for teaching and research; institutions like the and others in began using it for and small-scale projects, fostering a growing developer community. Linux's design also pursued compatibility as a goal to ensure portability of Unix applications, aligning it with emerging open standards. A notable early application occurred in 1994 when researchers Thomas Sterling and Donald Becker constructed the first at , linking 16 80486-based PCs running to achieve supercomputing performance at a fraction of traditional costs. This prototype demonstrated 's viability for in high-performance environments, influencing subsequent cluster designs and highlighting its scalability for scientific workloads. In April 1992, Unix System Laboratories (USL), an subsidiary, initiated a against Berkeley Software Design, Inc. (BSDi) and the Regents of the , claiming that BSDi's commercial BSD/386 operating system unlawfully incorporated proprietary Unix code and trade secrets from earlier distributions. The suit specifically targeted the Networking Release 2 (Net/2) distribution, which USL argued included unlicensed elements despite Berkeley's efforts to remove -derived code. This legal action stemmed from 's renewed commercialization push after the 1984 divestiture, aiming to protect its amid growing competition from BSD variants. The lawsuit disrupted the burgeoning BSD community, prompting Berkeley to countersue USL in California state court for breaching prior licensing agreements. In December 1992, a federal judge denied USL's request for an , limiting the case to recent s and trade secrets rather than broader claims. By late 1993, had acquired USL, shifting the dynamics, and the parties reached a settlement in 1994. Under the agreement, Berkeley removed three specific files deemed encumbered, made minor modifications to others, and added USL notices to approximately 70 files, while USL dropped nearly all remaining claims, acknowledging the bulk of Net/2 as freely redistributable. Parallel to the litigation, independent BSD efforts accelerated on x86 hardware. In 1992, William and Lynne Jolitz released , the first complete, bootable port of Net/2 to the 80386 processor, developed through a series of articles and aimed at providing an experimental platform for PC users. However, maintenance challenges with led to the formation of two major forks in 1993: , founded by Chris Demetriou, , Adam Glass, and Charles M. Hannum to emphasize portability across architectures and code quality, drawing directly from and Net/2; and , initiated by Nate Williams, Rod Grimes, and Jordan Hubbard as a more user-friendly PC-focused derivative, also rooted in the Unofficial 386BSD Patchkit. The 1994 settlement enabled these projects to realign with Berkeley's official 4.4BSD-Lite release, which excluded the disputed elements and became the foundation for unencumbered BSD development. , for instance, transitioned to 4.4BSD-Lite with its 1.1.5.1 release in July 1994, resolving prior uncertainties. In 1995, forked to create , prioritizing proactive security auditing, code correctness, and cryptographic innovations to address perceived vulnerabilities in the broader ecosystem. Ultimately, the resolution of the USL lawsuit cleared legal hurdles, allowing BSD variants to evolve as fully open-source systems without encumbrances, fostering widespread adoption and innovation in the late .

The 2000s: Open Source Dominance

SCO Litigation and Unix IP

In 2000, Systems announced its acquisition of the Unix and professional services divisions from (SCO), a move that integrated Unix assets into a company previously focused on . The deal was completed in May 2001, marking a significant expansion for into proprietary Unix markets. By August 2002, rebranded itself as The SCO Group, shifting its strategy toward leveraging Unix intellectual property (IP) while continuing operations. The SCO Group's legal troubles escalated in March 2003 when it filed a high-profile against , alleging that IBM had breached its Unix licensing agreements by contributing proprietary System V code to the open-source , seeking damages of at least $1 billion. SCO claimed this unauthorized disclosure undermined the commercial value of its Unix products, including , and threatened Linux users with potential license fees for alleged IP infringement. The suit drew widespread attention, prompting preemptive actions such as Red Hat's August 2003 countersuit seeking that its Linux distributions did not infringe SCO's copyrights. By 2004–2005, SCO expanded its litigation strategy, filing suits against over the ownership of Unix copyrights and trademarks—disputing Novell's retention of key IP rights from its 1995 sale of Unix assets to SCO's predecessor—and targeting end-users like for running unlicensed versions purportedly containing Unix code. SCO also pursued claims against in ongoing disputes, alleging interference with its Unix licensing business through promotion, though Red Hat's earlier suit complicated the proceedings. These cases highlighted tensions over Unix IP transfers dating back to the 1990s, when acquired the trademark and copyrights from before partial sales. In August 2007, a federal judge ruled in Novell's favor, determining that SCO did not acquire the Unix and copyrights under the 1995 , severely weakening SCO's position in all related suits. Appeals prolonged the battles into the , culminating in a March 2010 jury verdict reaffirming Novell's ownership of the copyrights, with SCO ordered to pay royalties it had withheld. SCO filed for Chapter 11 bankruptcy in September 2007 amid mounting legal defeats and financial strain from the litigation. The SCO litigation ultimately discredited the company's IP claims, leading to its effective dissolution and reinforcing the legal viability of open-source software like by demonstrating that Unix-derived code in open projects did not constitute widespread infringement. The litigation continued through appeals and was finally settled in February 2022, with paying SCO $14.25 million, a fraction of the original claims, further affirming the lack of merit in SCO's allegations. This outcome alleviated fears in the tech industry about proprietary Unix encumbrances on , paving the way for broader open-source dominance in enterprise computing.

OpenSolaris and Other Open Variants

In 2005, Sun Microsystems released the source code for its Solaris operating system under the (CDDL), launching the project to foster community-driven development of an open-source variant of Solaris. This initiative included the open-sourcing of key technologies such as the file system, introduced in November 2005 as part of Solaris 10, which provided advanced features like pooled storage and built-in data integrity checks. Similarly, the dynamic tracing framework was released under the CDDL in January 2005, enabling low-overhead instrumentation of running systems for performance analysis and debugging. maintained compliance, ensuring compatibility with Unix standards. The trajectory of shifted following 's acquisition of , announced on April 20, 2009, for $7.4 billion. After the deal closed in January 2010, discontinued the community aspects of in August 2010, halting public contributions and shifting development to proprietary Solaris releases. In response, former Sun engineers and community members forked the last open-source release ( 2009.06) to create the project on August 3, 2010, preserving and advancing the codebase under the CDDL and the permissive Indiana License. Beyond Solaris derivatives, other open Unix variants emerged in the 2000s, including Apple's Darwin, released as in April 2000 and serving as the foundational core for macOS, incorporating elements from BSD and Mach. Additionally, , forked from in 1995, emphasized security through proactive code auditing, privilege separation, and features like , establishing it as a benchmark for secure open-source operating systems.

Linux and Unix-like Systems Proliferation

In the early 2000s, the underwent significant maturation with the release of version 2.6 on December 17, 2003, introducing improvements in scalability, device drivers, and support for that enhanced its suitability for enterprise and high-performance environments. This kernel version marked a shift toward greater stability, enabling broader adoption beyond its origins in the as a hobbyist project by . User-friendly distributions further accelerated Linux's proliferation; for instance, , launched on October 20, 2004, by , emphasized ease of installation and regular release cycles, quickly becoming one of the most popular desktop and server variants. Corporate backing propelled Linux's dominance in server markets during this period. In 2003, IBM launched an aggressive advertising and investment campaign to position Linux as a viable alternative to systems, committing billions to development and integration across its hardware portfolio, which helped standardize Linux in data centers. Standardization efforts also advanced, with the Version 3 (SUSv3) released on January 30, 2002, by The Open Group, providing a comprehensive framework for Unix conformance that influenced Linux implementations aiming for compatibility. Unix-like systems expanded into consumer and mobile domains. Apple's Mac OS X 10.5 Leopard, released on October 26, 2007, achieved official UNIX 03 certification under SUSv3 on May 18, 2007, for Intel-based systems, solidifying its status as a certified Unix operating system and bridging proprietary Unix heritage with open-source elements. Similarly, introduced Android on September 23, 2008, as a kernel-based platform for mobile devices, qualifying it as and rapidly capturing market share in embedded and applications. Linux's proliferation extended to high-performance computing and embedded systems. By the mid-2000s, Linux powered a majority of entries on the TOP500 list of supercomputers, rising from about 50 systems in 2000 to over 90% by 2009, due to its cost-effectiveness and customizability for parallel processing clusters. In embedded applications, adoption surged in the early 2000s with tools like MontaVista Linux, enabling deployment in , routers, and industrial devices, where its modular kernel supported resource-constrained hardware.

Modern Era (2010s–Present)

Discontinuation of Proprietary Unix

In 2010, following its acquisition of , discontinued the community project, which had been an open-source distribution of Solaris since 2005, effectively ending community-driven development of the operating system. shifted its focus to the proprietary 11, releasing Solaris 11 Express as a developer preview later that year, while ceasing binary distributions under the banner. This move marked a significant retreat from open-source collaboration in proprietary Unix variants, prioritizing enterprise support and commercial licensing over broader contributions. Oracle Solaris continued with periodic updates, but the last major traditional release came in 2017 with the introduction of the for Solaris 11, abandoning plans for a full Solaris 12 version in favor of ongoing support releases (SRUs) for existing installations. Under this model, new features are delivered incrementally through updates rather than discrete major versions, reflecting a stabilization rather than expansion of the platform amid declining demand. Solaris remains available for x86 and architectures, but its deployment has increasingly been limited to legacy enterprise environments requiring high reliability for mission-critical workloads. Meanwhile, other proprietary Unix systems like Hewlett-Packard’s HP-UX and IBM’s AIX have persisted into the 2010s and beyond, but primarily in niche roles within large-scale, mission-critical enterprise settings such as banking, finance, and industrial automation. HP-UX, optimized for HP’s Itanium-based Integrity servers, supports secure, high-availability operations but has seen limited new development as hardware transitions to x86 alternatives. Standard support for HP-UX 11i v3 is scheduled to end on December 31, 2025. Similarly, AIX, tailored for IBM Power Systems, excels in virtualization and scalability for enterprise applications, yet its adoption has contracted as customers migrate to more cost-effective Linux distributions on compatible hardware. These systems maintain certification for key enterprise software like SAP and Oracle Database, underscoring their role in long-tail legacy support rather than broad market growth. The decline of proprietary Unix was further exemplified by the resolution of The ’s prolonged legal battles over Unix , with its proceedings from 2009 to 2011 and the final settlement of the SCO v. case in 2021. Amid ongoing litigation stemming from 2000s disputes with and regarding Unix copyrights, SCO auctioned its Unix assets in 2010, with the sale closing in April 2011 to UnXis, a newly formed Las Vegas-based company bidding $2.4 million in cash plus $850,000 in assumed liabilities. This transfer of SCO’s Unix and technologies to an unproven entity effectively diminished SCO’s influence, as UnXis (later rebranded Xinuos) struggled to revitalize the products amid market shifts toward open-source alternatives. By 2015, the overall of Unix operating systems in the server segment had declined to around 6% of revenue, driven by migrations to and cloud-native solutions that offered greater flexibility and lower costs. According to industry analyses, Unix server shipments represented a shrinking fraction of the total market, with revenues declining due to reduced demand for specialized RISC and hardware. This trend underscored the erosion of Unix’s dominance, as enterprises prioritized and over vendor-specific ecosystems.

Unix Influence on Mobile and Embedded Systems

In the 2010s, Android emerged as the dominant , built on a modified that provides core functionalities such as process management, memory allocation, and . Launched in during the late , Android rapidly captured the market, achieving over 70% global smartphone share by 2020 through its open-source nature and support for diverse hardware from manufacturers like and . This foundation, derived from Linux's compliance, enabled Android to integrate Unix principles like multi-user support and command-line tools, influencing app development and system stability in billions of devices. Similarly, Apple's and macOS trace their roots to Darwin, an open-source operating system released in 2000 that combines the Mach microkernel with BSD subsystems for networking, file systems, and userland utilities. This BSD heritage, originating from enhancements to AT&T Unix at the , in the 1970s and 1980s, underpins the security model and portability of for mobile devices and macOS for desktops. Both systems maintained (SUSv3) certification from The Open Group through the 2020s, ensuring compatibility with Unix standards for enterprise and developer tools until at least macOS 15 Sequoia in 2024. Unix variants also permeated embedded systems, where stability and modularity are critical. , a direct descendant of BSD Unix, forms the basis of 's PlayStation operating systems, including Orbis OS for the PS4 and subsequent consoles, leveraging 's kernel for real-time graphics and network handling since the early 2010s. In networking hardware, powers numerous routers and embedded devices due to its high portability across architectures, with deployments in industrial controllers and access points from companies like and various OEMs. Efforts to extend Unix-like systems to mobile platforms continued with , a Linux-based operating system announced in 2010 and released in 2011 as a collaboration between and for smartphones, tablets, and netbooks. incorporated Linux kernel features for power management and multimedia, aiming to unify mobile experiences but facing discontinuation after 's pivot to . Its successor, , emerged in 2011 under the with backing from and , retaining Linux foundations while shifting toward for user interfaces in wearables and smart devices. By the 2020s, Unix influence expanded into IoT and automotive sectors through lightweight distributions. Systems like , a -based , dominate IoT routers and smart home gateways for its customizable networking stack derived from Unix tools. In automotive applications, Automotive Grade (AGL), launched in 2015 by the , provides a standardized platform for infotainment, telematics, and autonomous driving features, adopted by over 140 members including and Ford for production vehicles. These adaptations highlight Unix's enduring principles of modularity and openness in resource-constrained environments.

Legacy and Ongoing Developments

The foundational principles of Unix, including the concept that "," modularity through small, interoperable tools, and emphasis on portability, continue to underpin modern operating system design and development practices. These tenets, articulated in seminal works on , enable uniform treatment of hardware devices, processes, and data streams via file-like interfaces, fostering simplicity and extensibility in systems like and its derivatives. Modularity promotes the composition of complex applications from reusable components, while portability ensures code can run across diverse hardware without significant rework, influences evident in contemporary cloud-native architectures and technologies. In the 2010s, , as a system, became the dominant force in , powering the majority of virtual machines on platforms such as (AWS) and . AWS relies heavily on its Amazon Linux distribution, a customized environment optimized for cloud workloads, while Azure supports various Linux distributions that collectively outpace Windows in usage. By 2020, operating systems, predominantly , accounted for over 90% of websites hosted globally, reflecting their scalability and reliability in server environments. This proliferation extended to hyperscale data centers, where 's open-source nature and Unix heritage facilitated cost-effective, high-performance infrastructure. The (SUS) Version 4, published in 2018 and incorporating updates through the , remains the core standard for Unix compliance, with ongoing efforts by The Open Group to refine it for emerging needs like real-time extensions and security enhancements. In 2020, drafts for POSIX-related alignments under SUSv4 were circulated to harmonize with IEEE Std 1003.1, ensuring continued . The Open Group's UNIX Certification Program persists as of 2025, validating systems against SUSv4 to grant the UNIX trademark, with active test suites confirming conformance in areas like multithreading and file systems. Commemorative events marking over 50 years since Unix's inception, including the 50th anniversary in 2019 with gatherings at Bell Labs and USENIX conferences, extended into subsequent years with retrospectives and exhibits in 2023, highlighting Unix's enduring impact on computing. Concurrently, integration of the Rust programming language into the Linux kernel advanced significantly in 2023, with developers contributing Rust-based drivers, such as for the Asix AX88796B Ethernet controller, to enhance memory safety while preserving Unix-like modularity. By 2025, Rust support is stable in kernel versions beyond 6.1, enabling hybrid codebases that blend C and Rust for critical components. As of 2025, The Open Group maintains the UNIX trademark exclusively for systems certified compliant with SUSv4, ensuring a benchmark for portability and standards adherence across vendors like and . Hybrid environments, such as Microsoft's (WSL), exemplify Unix's ongoing evolution by embedding full distributions—including Bash shells and tools—directly into Windows, allowing seamless Unix-like development without dual-booting. These developments underscore Unix's adaptability, with its principles driving innovations in , , and cross-platform tools.

References

Add your contribution
Related Hubs
Contribute something
User Avatar
No comments yet.