and
Dennis Ritchie, principal developers of
Research Unix 1984, including
Dennis Ritchie (center) The Unix system had a significant impact on other operating systems. It achieved its reputation by its interactivity, by providing the software at a nominal fee for educational use, by running on inexpensive hardware, and by being easy to adapt and move to different machines. Unix was originally written in
assembly language, but was soon rewritten in
C, a
high-level programming language. Although this followed the lead of
CTSS,
Multics and
Burroughs MCP, it was Unix that popularized the idea. Unix had a drastically simplified file model compared to many contemporary operating systems: treating all kinds of files as simple byte arrays. The file system hierarchy contained machine services and devices (such as
printers,
terminals, or
disk drives), providing a uniform interface, but at the expense of occasionally requiring additional mechanisms such as
ioctl and mode flags to access features of the hardware that did not fit the simple "stream of bytes" model. The
Plan 9 operating system pushed this model even further and eliminated the need for additional mechanisms. Unix also popularized the hierarchical file system with arbitrarily nested subdirectories, originally introduced by Multics. Other common operating systems of the era had ways to divide a storage device into multiple directories or sections, but they had a fixed number of levels, often only one level. Several major proprietary operating systems eventually added recursive subdirectory capabilities also patterned after Multics. DEC's
RSX-11M's "group, user" hierarchy evolved into
OpenVMS directories,
CP/M's volumes evolved into
MS-DOS 2.0+ subdirectories, and HP's
MPE group.account hierarchy and IBM's
SSP and
OS/400 library systems were folded into broader POSIX file systems. Making the command interpreter an ordinary user-level program, with additional commands provided as separate programs, was another Multics innovation popularized by Unix. The
Unix shell used the same language for interactive commands as for scripting (
shell scripts – there was no separate job control language like IBM's
JCL). Since the shell and OS commands were "just another program", the user could choose (or even write) their own shell. New commands could be added without changing the shell itself. Unix's innovative command-line syntax for creating modular chains of producer-consumer processes (
pipelines) made a powerful programming paradigm (
coroutines) widely available. Many later command-line interpreters have been inspired by the Unix shell. A fundamental simplifying assumption of Unix was its focus on
newline-
delimited text for nearly all file formats. There were no "binary" editors in the original version of Unix – the entire system was configured using textual shell command scripts. The common denominator in the I/O system was the byte – unlike
"record-based" file systems. The focus on text for representing nearly everything made Unix pipes especially useful and encouraged the development of simple, general tools that could easily be combined to perform more complicated
ad hoc tasks. The focus on text and bytes made the system far more scalable and portable than other systems. Over time, text-based applications have also proven popular in application areas, such as printing languages (
PostScript,
ODF), and at the application layer of the
Internet protocols, e.g.,
FTP,
SMTP,
HTTP,
SOAP, and
SIP. Unix popularized a syntax for
regular expressions that found widespread use. The Unix programming interface became the basis for a widely implemented operating system interface standard (POSIX, see above). The
C programming language soon spread beyond Unix, and is now ubiquitous in systems and applications programming. Early Unix developers were important in bringing the concepts of
modularity and
reusability into
software engineering practice, spawning a "software tools" movement. Over time, the leading developers of Unix (and programs that ran on it) established a set of cultural norms for developing software, norms which became as important and influential as the technology of Unix itself; this has been termed the
Unix philosophy. The
TCP/IP networking protocols were quickly implemented on the Unix versions widely used on relatively inexpensive computers, which contributed to the
Internet explosion of worldwide, real-time connectivity and formed the basis for implementations on many other platforms. The Unix policy of extensive on-line documentation and (for many years) ready access to all system source code raised programmer expectations, and contributed to the launch of the
free software movement in 1983.
Free Unix and Unix-like variants In 1983,
Richard Stallman announced the
GNU (short for "GNU's Not Unix") project, an ambitious effort to create a
free software Unix-like system – "free" in the sense that everyone who received a copy would be free to use, study, modify, and redistribute it. The GNU project's own kernel development project,
GNU Hurd, had not yet produced a working kernel, but in 1991
Linus Torvalds released the
Linux kernel as free software under the
GNU General Public License. In addition to their use in the
GNU operating system, many GNU packages – such as the
GNU Compiler Collection (and the rest of the
GNU toolchain), the
GNU C library and the
GNU Core Utilities – have gone on to play central roles in other free Unix systems as well.
Linux distributions, consisting of the Linux kernel and large collections of compatible software, have become popular both with individual users and in business. Popular distributions include
Red Hat Enterprise Linux,
Fedora,
SUSE Linux Enterprise,
openSUSE,
Debian,
Ubuntu,
Linux Mint,
Slackware Linux,
Arch Linux and
Gentoo. A free derivative of
BSD Unix,
386BSD, was released in 1992 and led to the
NetBSD and
FreeBSD projects. With the 1994 settlement of a lawsuit brought against the University of California and Berkeley Software Design Inc. (
USL v. BSDi) by
Unix System Laboratories, it was clarified that Berkeley had the right to distribute BSD Unix for free if it so desired. Since then, BSD Unix has been developed in several different product branches, including
OpenBSD and
DragonFly BSD. Because of the modular design of the Unix model, sharing components is relatively common: most or all Unix and Unix-like systems include at least some BSD code, while some include GNU utilities in their distributions. Linux and BSD Unix are increasingly filling market needs traditionally served by proprietary Unix operating systems, expanding into new markets such as the
consumer desktop,
mobile devices and
embedded devices. In a 1999 interview, Dennis Ritchie voiced his opinion that Linux and BSD Unix operating systems are a continuation of the basis of the Unix design and are derivatives of Unix: In the same interview, he states that he views both Unix and Linux as "the continuation of ideas that were started by Ken and me and many others, many years ago". The Unix system was said to "present several interesting capabilities as an ARPANET mini-host". At the time, Unix required a license from
Bell Telephone Laboratories that cost US$20,000 for non-university institutions, while universities could obtain a license for a nominal fee of $150. It was noted that Bell was "open to suggestions" for an ARPANET-wide license. The RFC specifically mentions that Unix "offers powerful local processing facilities in terms of user programs, several
compilers, an
editor based on
QED, a versatile document preparation system, and an efficient
file system featuring sophisticated access control,
mountable and de-mountable volumes, and a unified treatment of peripherals as
special files." The latter permitted the
Network Control Program (NCP) to be integrated within the Unix file system, treating
network connections as special files that could be accessed through standard Unix
I/O calls, which included the added benefit of closing all connections on program exit, should the user neglect to do so. In order "to minimize the amount of code added to the basic Unix
kernel", much of the NCP code ran in a
swappable user process, running only when needed. == Branding ==