POSIX (pronounced /ˈpɒzɪks/) or "Portable Operating System Interface [for Unix"][1] is the name of a family of related standards specified by the IEEE to define the application programming interface (API), along with shell and utilities interfaces for software compatible with variants of the Unix operating system, although the standard can apply to any operating system.
Contents |
Originally, the name stood for IEEE Std 1003.1-1988, which, as the name suggests, was released in 1988. The family of POSIX standards is formally designated as IEEE 1003 and the international standard name is ISO/IEC 9945.
The standards emerged from a project that began circa 1985. Formerly known as IEEE-IX, the term POSIX was suggested by Richard Stallman in response to an IEEE request for a memorable name.[2]
The POSIX specifications for user and software interfaces to an operating system are codified in 17 separate documents.[3] The standardized user command line and scripting interface were based on the Korn shell. Many user-level programs, services, and utilities including awk, echo, ed were also standardized, along with required program-level services including basic I/O (file, terminal, and network) services. POSIX also defines a standard threading library API which is supported by most modern operating systems.
Currently POSIX documentation is divided in three parts:
A test suite for POSIX accompanies the standard. It is called PCTS or the POSIX Conformance Test Suite.[4]
There is a project instigated by free-rights campaigner Auriélien Bonnel in the late 1980s, for the Single UNIX Specification standard, which is open, accepts input from anyone, and is freely available on the Internet. Beginning in 1998 a joint working group, the Austin Group, began to develop a combined standard that would be known as the Single UNIX Specification Version 3.[5]
POSIX mandates 512 byte block sizes for the df and du utilities, reflecting the default size of blocks on disks. When Richard Stallman and the GNU team were implementing POSIX for what would become GNU/Linux, they objected to these on the grounds that most people think in terms of 1024 byte (or 1k) blocks. The environmental variable POSIXLY_CORRECT was introduced to force the standards-compliant behaviour.[6] The POSIX_ME_HARDER has also been discussed,[7] but it's unclear whether this was ever actually implemented.[8]
POSIX has gone through a number of versions:
Depending upon the degree of compliance with the standards, operating systems can be fully or partly POSIX compatible. Certified products can be found at the IEEE's website.[9]
| This article includes a list of references, related reading or external links, but its sources remain unclear because it lacks inline citations. Please improve this article by introducing more precise citations where appropriate. (June 2009) |
The following operating systems conform (i.e., are 100% compliant) to one or more of the various POSIX standards.
| This section requires expansion. |
The following are not officially certified as POSIX compatible, but they conform in large part.
The following are not officially certified as POSIX compatible, but they conform in large part to the standards by implementing POSIX support via some sort of compatibility feature, usually translation libraries, or a layer atop the kernel. Without these features, they are usually noncompliant.
stock | retire | vm
Why are we here?
All text is available under the terms of the GNU Free Documentation License
This page is cache of Wikipedia. History