USENIX is an American 501(c)(3) nonprofit membership organization based in Berkeley, California and founded in 1975 that supports advanced computing systems , operating system (OS), and computer networking research. It organizes several conferences in these fields.
76-508: USENIX was established in 1975 under the name "Unix Users Group," focusing primarily on the study and development of the Unix OS family and similar systems. In June 1977, a lawyer from AT&T Corporation informed the group that they could not use the word "Unix" in their name as it was a trademark of Western Electric (the manufacturing arm of AT&T until 1995), which led to the change of name to USENIX. Since its founding, it has published
152-429: A time-sharing configuration, as well as portability. Unix systems are characterized by various concepts: the use of plain text for storing data; a hierarchical file system ; treating devices and certain types of inter-process communication (IPC) as files; and the use of a large number of software tools , small programs that can be strung together through a command-line interpreter using pipes , as opposed to using
228-484: A time-sharing operating system for the GE 645 mainframe computer. Multics featured several innovations , but also presented severe problems. Frustrated by the size and complexity of Multics, but not by its goals, individual researchers at Bell Labs started withdrawing from the project. The last to leave were Ken Thompson , Dennis Ritchie , Douglas McIlroy , and Joe Ossanna , who decided to reimplement their experiences in
304-519: 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: I think the Linux phenomenon is quite delightful, because it draws so strongly on the basis that Unix provided. Linux seems to be among the healthiest of the direct Unix derivatives, though there are also the various BSD systems as well as
380-460: A convenient platform for programmers developing software to be run on it and on other systems, rather than for non-programmers. The system grew larger as the operating system started spreading in academic circles, and as users added their own tools to the system and shared them with colleagues. At first, Unix was not designed to support multi-tasking or to be portable . Later, Unix gradually gained multi-tasking and multi-user capabilities in
456-502: A file system is created, some file systems allocate a fixed number of inodes. This means that it is possible to run out of inodes on a file system, even if there is free space remaining in the file system. This situation often arises in use cases where there are many small files, such as on a server storing email messages, because each file, no matter how small, requires its own inode. Other file systems avoid this limitation by using dynamic inode allocation. Dynamic inode allocation allows
532-471: A file system to create more inodes as needed instead of relying on a fixed number created at the time of file system creation. This can "grow" the file system by increasing the number of inodes available for new files and directories, thus avoiding the problem of running out of inodes. It can make sense to store very small files in the inode itself to save both space (no data block needed) and lookup time (no further disk access needed). This file system feature
608-491: A generic term such as system to help avoid the creation of a genericized trademark . Inode The inode (index node) is a data structure in a Unix-style file system that describes a file-system object such as a file or a directory . Each inode stores the attributes and disk block locations of the object's data. File-system object attributes may include metadata (times of last change, access, modification), as well as owner and permission data. A directory
684-459: A library file even as another process is replacing that same file. This operation should be performed atomically , meaning it should appear as a single operation that is either entirely completed or not done at all, with no intermediate state visible to other processes. During the replacement , a new inode is created for the new library file , establishing an entirely new mapping. Subsequently, future access requests for that library will retrieve
760-464: A magazine called ;login: that appears four times a year. From 2021, it has become an all-digital magazine and openly accessible. ;login: content informs the community about practically relevant research, useful tools, and relevant events. From 1988–1996, USENIX published the quarterly journal Computing Systems , about the theory and implementation of advanced computing systems in the UNIX tradition. It
836-405: A new project of smaller scale. This new operating system was initially without organizational backing, and also without a name. The new operating system was a single-tasking system. In 1970, the group coined the name Unics for Uniplexed Information and Computing Service as a pun on Multics , which stood for Multiplexed Information and Computer Services . Brian Kernighan takes credit for
SECTION 10
#1732797874178912-512: A potential universal operating system, suitable for computers of all sizes. The Unix environment and the client–server program model were essential elements in the development of the Internet and the reshaping of computing as centered in networks rather than in individual computers. Both Unix and the C programming language were developed by AT&T and distributed to government and academic institutions, which led to both being ported to
988-420: A reference directory layout for Unix-like operating systems; it has mainly been used in Linux. The Unix system is composed of several components that were originally packaged together. By including the development environment, libraries, documents and the portable, modifiable source code for all of these components, in addition to the kernel of an operating system, Unix was a self-contained software system. This
1064-504: A representation like Un*x , *NIX , or *N?X is used to indicate all operating systems similar to Unix. This comes from the use of the asterisk ( * ) and the question mark characters as wildcard indicators in many utilities. This notation is also used to describe other Unix-like systems that have not met the requirements for UNIX branding from the Open Group. The Open Group requests that UNIX always be used as an adjective followed by
1140-449: 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
1216-487: A single monolithic program that includes all of the same functionality. These concepts are collectively known as the " Unix philosophy ". Brian Kernighan and Rob Pike summarize this in The Unix Programming Environment as "the idea that the power of a system comes more from the relationships among programs than from the programs themselves". By the early 1980s, users began seeing Unix as
1292-544: A single nine-track magnetic tape , earning its reputation as a portable system. The printed documentation, typeset from the online sources, was contained in two volumes. The names and filesystem locations of the Unix components have changed substantially across the history of the system. Nonetheless, the V7 implementation has the canonical early structure: The Unix system had a significant impact on other operating systems. It achieved its reputation by its interactivity, by providing
1368-471: A table of inodes on the file system. From the inode number, the kernel's file system driver can access the inode contents, including the location of the file, thereby allowing access to the file. A file's inode number can be found using the ls -i command. The ls -i command prints the inode number in the first column of the report. On many older file systems, inodes are stored in one or more fixed-size areas that are set up at file system creation time, so
1444-573: A technical journal titled ;login: . USENIX was started as a technical organization. As commercial interest grew, a number of separate groups started in parallel, most notably the Software Tools Users Group (STUG), a technical adjunct for Unix-like tools and interface on non-Unix operating systems, and /usr/group, a commercially oriented user group. USENIX's founding President was Lou Katz. USENIX hosts numerous conferences and symposia each year, including: USENIX publishes
1520-479: 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
1596-508: 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
SECTION 20
#17327978741781672-402: A wider variety of machine families than any other operating system. The Unix operating system consists of many libraries and utilities along with the master control program, the kernel . The kernel provides services to start and stop programs, handles the file system and other common "low-level" tasks that most programs share, and schedules access to avoid conflicts when programs try to access
1748-476: Is a list of inodes with their assigned names. The list includes an entry for itself, its parent, and each of its children. There has been uncertainty on the Linux kernel mailing list about the reason for the "i" in "inode". In 2002, the question was brought to Unix pioneer Dennis Ritchie , who replied: In truth, I don't know either. It was just a term that we started to use. "Index" is my best guess, because of
1824-414: Is associated with an inode , which is identified by an integer, often referred to as an i-number or inode number . Inodes store information about files and directories (folders), such as file ownership, access mode (read, write, execute permissions), and file type. The data may be called stat data, in reference to the stat system call that provides the data to programs. The inode number indexes
1900-418: Is called inlining. The strict separation of inode and file data thus can no longer be assumed when using modern file systems. If the data of a file fits in the space allocated for pointers to the data, this space can conveniently be used. For example, ext2 and its successors store the data of symlinks (typically file names) in this way if the data is no more than 60 bytes ("fast symbolic links"). Ext4 has
1976-408: Is denoted by the phrase "file serial number", defined as a per-file system unique identifier for a file. That file serial number, together with the device ID of the device containing the file, uniquely identify the file within the whole system. Within a POSIX system, a file has the following attributes which may be retrieved by the stat system call: Filesystems designed with inodes will have
2052-466: Is still defined as root. The most notable exception to this prohibition is found in Mac OS X (versions 10.5 and higher) which allows hard links of directories to be created by the superuser. When a file is relocated to a different directory on the same file system, or when a disk defragmentation alters its physical location, the file's inode number remains unchanged. This unique characteristic permits
2128-609: The Bell Labs research center by Ken Thompson , Dennis Ritchie , and others. Initially intended for use inside the Bell System , AT&T licensed Unix to outside parties in the late 1970s, leading to a variety of both academic and commercial Unix variants from vendors including University of California, Berkeley ( BSD ), Microsoft ( Xenix ), Sun Microsystems ( SunOS / Solaris ), HP / HPE ( HP-UX ), and IBM ( AIX ). Early versions of Unix ran on PDP-11 computers; Unix
2204-782: 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 ,
2280-535: The UNIX 98 or UNIX 03 trademarks today, after the operating system's vendor pays a substantial certification fee and annual trademark royalties to The Open Group. Systems that have been licensed to use the UNIX trademark include AIX , EulerOS , HP-UX , Inspur K-UX , IRIX , macOS , Solaris , Tru64 UNIX (formerly "Digital UNIX", or OSF/1 ), and z/OS . Notably, EulerOS and Inspur K-UX are Linux distributions certified as UNIX 03 compliant. Sometimes
2356-460: The kernel to speed up filesystem operations by storing information about directory links in RAM . Historically, it was possible to hard link directories. This made the directory structure an arbitrary directed graph contrary to a directed acyclic graph . It was even possible for a directory to be its own parent. Modern systems generally prohibit this confusing state, except that the parent of root
USENIX - Misplaced Pages Continue
2432-487: The Open Group Base Specification. In 1999, in an effort towards compatibility, several Unix system vendors agreed on SVR4's Executable and Linkable Format (ELF) as the standard for binary and object code files. The common format allows substantial binary compatibility among different Unix systems operating on the same CPU architecture. The Filesystem Hierarchy Standard was created to provide
2508-491: The UNIX trademark to The Open Group , an industry consortium founded in 1996. The Open Group allows the use of the mark for certified operating systems that comply with the Single UNIX Specification (SUS). Unix-like operating systems have been relevant since the 1990s which function similarly to Unix: popular examples are GNU (including Linux ), FreeBSD and macOS . Unix was originally meant to be
2584-632: 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. In October 1993, Novell , the company that owned the rights to the Unix System V source at the time, transferred the trademarks of Unix to the X/Open Company (now The Open Group ), and in 1995 sold
2660-465: 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
2736-435: 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. 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
2812-492: 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
2888-479: The core of the Mac OS X operating system, later renamed macOS . Unix-like operating systems are widely used in modern servers , workstations , and mobile devices . In the late 1980s, an open operating system standardization effort now known as POSIX provided a common baseline for all operating systems; IEEE based POSIX around the common structure of the major competing variants of the Unix system, publishing
2964-477: The directory it just moved up from. Because the child directory's inode still exists as an entry in its parent directory , it allows the function to reconstruct the absolute path of the current working directory . Some operating systems maintain extra information to make this operation run faster. For example, in the Linux VFS, directory entry cache, also known as dentry or dcache, are cache entries used by
3040-440: The directory resides. The entry found thereby (the file's i-node ) contains the description of the file. Additionally, Maurice J. Bach wrote that the word inode "is a contraction of the term index node and is commonly used in literature on the UNIX system". A file system relies on data structures about the files, as opposed to the contents of that file. The former are called metadata —data that describes data. Each file
3116-546: 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
USENIX - Misplaced Pages Continue
3192-462: The file (via the inode) by any processes will now point to the new version of the library. Thus, making it possible to perform updates even when the library is in use by another process. One significant advantage of this mechanism is that it eliminates the need for a system reboot to replace libraries currently in use. Consequently, systems can update or upgrade software libraries seamlessly without interrupting running processes or operations. When
3268-433: The file to be moved or renamed even during read or write operations, thereby ensuring continuous access without disruptions. This feature—having a file's metadata and data block locations persist in a central data structure , irrespective of file renaming or moving—cannot be fully replicated in many non-Unix file systems like FAT and its derivatives, as they lack a mechanism to maintain this invariant property when both
3344-470: The file's directory entry and its data are simultaneously relocated. In these file systems, moving or renaming a file might lead to more significant changes in the data structure representing the file, and the system does not keep a separate, central record of the file's data block locations and metadata as inodes do in Unix-like systems. inode file systems allow a running process to continue accessing
3420-428: The filename. As a result, functions like getcwd() and getwd() which retrieve the current working directory of the process, cannot directly access the filename. Beginning with the current directory, these functions search up to its parent directory , then to the parent's parent, and so on, until reaching the root directory . At each level, the function looks for a directory entry whose inode matches that of
3496-406: The filesystem, its deletion is deferred until all processes with access to the file have finished using it, including executable files which are implicitly held open by the processes executing them. It is typically not possible to map from an open file to the filename that was used to open it. When a program opens a file, the operating system converts the filename to an inode number and then discards
3572-423: The filesystem. A file that has been deleted or lacks directory entries pointing to it is termed an 'unlinked' file. Such files are removed from the filesystem, freeing the occupied disk space for reuse. An inode without links remains in the filesystem until the resources (disk space and blocks) freed by the unlinked file are deallocated or the file system is modified. Although an unlinked file becomes invisible in
3648-679: The first POSIX standard in 1988. In the early 1990s, a separate but very similar effort was started by an industry consortium, the Common Open Software Environment (COSE) initiative, which eventually became the Single UNIX Specification (SUS) administered by The Open Group . Starting in 1998, the Open Group and IEEE started the Austin Group , to provide a common definition of POSIX and the Single UNIX Specification, which, by 2008, had become
3724-455: The fixed-size table include B-trees and the derived B+ trees . File names and directory implications: The operating system kernel's in-memory representation of this data is called struct inode in Linux . Systems derived from BSD use the term vnode (the "v" refers to the kernel's virtual file system layer). The POSIX standard mandates file-system behavior that is strongly influenced by traditional UNIX file systems. An inode
3800-433: The following administrative characteristics: Files can have multiple names. If multiple names hard link to the same inode then the names are equivalent; i.e., the first to be created has no special status. This is unlike symbolic links , which depend on the original name, not the inode (number). An inode may have no links. An inode without links represents a file with no remaining directory entries or paths leading to it in
3876-420: The idea, but adds that "no one can remember" the origin of the final spelling Unix . Dennis Ritchie, Doug McIlroy, and Peter G. Neumann also credit Kernighan. The operating system was originally written in assembly language , but in 1973, Version 4 Unix was rewritten in C . Version 4 Unix, however, still had much PDP-11 specific code, and was not suitable for porting. The first port to another platform
SECTION 50
#17327978741783952-476: The late 1970s and early 1980s, the influence of Unix in academic circles led to large-scale adoption of Unix ( BSD and System V ) by commercial startups, which in turn led to Unix fragmenting into multiple, similar — but often slightly and mutually incompatible — systems including DYNIX , HP-UX , SunOS / Solaris , AIX , and Xenix . In the late 1980s, AT&T Unix System Laboratories and Sun Microsystems developed System V Release 4 ( SVR4 ), which
4028-480: The maximum number of inodes is fixed at file system creation, limiting the maximum number of files the file system can hold. A typical allocation heuristic for inodes in a file system is one inode for every 2K bytes contained in the filesystem. Some Unix-style file systems such as JFS , XFS , ZFS , OpenZFS , ReiserFS , btrfs , and APFS omit a fixed-size inode table, but must store equivalent data in order to provide equivalent capabilities. Common alternatives to
4104-428: 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
4180-443: The more official offerings from the workstation and mainframe manufacturers. 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". OpenSolaris was the free software counterpart to Solaris developed by Sun Microsystems , which included a CDDL -licensed kernel and a primarily GNU userland. However, Oracle discontinued
4256-497: The networks and creating the Internet: Commercialization, privatization, broader access leads to the modern Internet: Examples of Internet services: Unix ( / ˈ j uː n ɪ k s / , YOO -niks ; trademarked as UNIX ) is a family of multitasking , multi-user computer operating systems that derive from the original AT&T Unix, whose development started in 1969 at
4332-424: The newly installed version. When the operating system is replacing the file (and creating a new inode), it places a lock on the inode and possibly the containing directory. This prevents other processes from reading or writing to the file (inode) during the update operation, thereby avoiding data inconsistency or corruption. Once the update operation is complete, the lock is released. Any subsequent access to
4408-406: The notion of "index" being the etymological origin of inodes. They wrote: […] a directory entry contains only a name for the associated file and a pointer to the file itself. This pointer is an integer called the i-number (for index number) of the file. When the file is accessed, its i-number is used as an index into a system table (the i-list ) stored in a known part of the device on which
4484-475: The operating system should provide a set of simple tools, each of which performs a limited, well-defined function. A unified and inode -based filesystem and an inter-process communication mechanism known as " pipes " serve as the main means of communication, and a shell scripting and command language (the Unix shell ) is used to combine the tools to perform complex workflows. In the early 1990s, AT&T sold its rights in Unix to Novell , which then sold
4560-503: 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
4636-599: The project upon their acquisition of Sun, which prompted a group of former Sun employees and members of the OpenSolaris community to fork OpenSolaris into the illumos kernel. As of 2014, illumos remains the only active, open-source System V derivative. In May 1975, RFC 681 described the development of Network Unix by the Center for Advanced Computation at the University of Illinois Urbana-Champaign . The Unix system
SECTION 60
#17327978741784712-591: The related business operations to Santa Cruz Operation (SCO). Whether Novell also sold the copyrights to the actual software was the subject of a federal lawsuit in 2006, SCO v. Novell , which Novell won. The case was appealed, but on August 30, 2011, the United States Court of Appeals for the Tenth Circuit affirmed the trial decisions, closing the case. Unix vendor SCO Group Inc. accused Novell of slander of title . The present owner of
4788-482: The same resource or device simultaneously. To mediate such access, the kernel has special rights, reflected in the distinction of kernel space from user space , the latter being a lower priority realm where most application programs operate. The origins of Unix date back to the mid-1960s when the Massachusetts Institute of Technology , Bell Labs , and General Electric were developing Multics ,
4864-484: 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
4940-427: 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
5016-426: The slightly unusual file system structure that stored the access information of files as a flat array on the disk, with all the hierarchical directory information living aside from this. Thus the i-number is an index in this array, the i-node is the selected element of the array. (The "i-" notation was used in the 1st edition manual; its hyphen was gradually dropped.) A 1978 paper by Ritchie and Ken Thompson bolsters
5092-654: 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
5168-418: 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
5244-459: The trademark UNIX is The Open Group, an industry standards consortium. Only systems fully compliant with and certified to the Single UNIX Specification qualify as "UNIX" (others are called " Unix-like "). By decree of The Open Group, the term "UNIX" refers more to a class of operating systems than to a specific implementation of an operating system; those operating systems which meet The Open Group's Single UNIX Specification should be able to bear
5320-536: Was a port of Version 6, made four years later (1977) at the University of Wollongong for the Interdata 7/32 , followed by a Bell Labs port of Version 7 to the Interdata 8/32 during 1977 and 1978. Bell Labs produced several versions of Unix that are collectively referred to as Research Unix . In 1975, the first source license for UNIX was sold to Donald B. Gillies at the University of Illinois Urbana–Champaign (UIUC) Department of Computer Science. During
5396-431: Was commonly used on minicomputers and mainframes from the 1970s onwards. It distinguished itself from its predecessors as the first portable operating system: almost the entire operating system is written in the C programming language , which allows Unix to operate on numerous platforms. Unix systems are characterized by a modular design that is sometimes called the " Unix philosophy ". According to this philosophy,
5472-402: Was one of the key reasons it emerged as an important teaching and learning tool and has had a broad influence. See § Impact , below. The inclusion of these components did not make the system large – the original V7 UNIX distribution, consisting of copies of all of the compiled binaries plus all of the source code and documentation occupied less than 10 MB and arrived on
5548-587: Was published first by the University of California Press, then by the MIT Press. The issues have been scanned and are online. USENIX conferences became open access in 2008. Since 2011, they have provided audio and video recordings of paper presentations and conference talks in their open-access materials, free of charge. This award, also called the "Flame" award, has been presented since 1993. Unix Early research and development: Merging
5624-514: 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
5700-516: 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 ,
5776-404: Was subsequently adopted by many commercial Unix vendors. In the 1990s, Unix and Unix-like systems grew in popularity and became the operating system of choice for over 90% of the world's top 500 fastest supercomputers , as BSD and Linux distributions were developed through collaboration by a worldwide network of programmers. In 2000, Apple released Darwin , also a Unix system, which became
#177822