POSIX

From Wikipedia, the free encyclopedia

Not to be confused with Unix, *NIX, or Linux.

POSIX (IPA: /ˈpɒzɪks/) or "Portable Operating System Interface"[1] is the collective 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. 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 near 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]

Contents

[edit] Overview

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 include 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:

  • POSIX Kernel APIs (which include extensions for POSIX.1, Real-time Services, Threads Interface, Real-time Extensions, Security Interface, Network File Access and Network Process-to-Process Communications)
  • POSIX Commands and Utilities (with User Portability Extensions, Corrections and Extensions, Protection and Control Utilities and Batch System Utilities)
  • POSIX Conformance Testing

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]

[edit] Versions

POSIX has gone through a number of versions:

  • POSIX.1, Core Services (incorporates Standard ANSI C)
    • Process Creation and Control
    • Signals[6]
    • Floating Point Exceptions
    • Segmentation Violations
    • Illegal Instructions
    • Bus Errors
    • Timers
    • File and Directory Operations
    • Pipes
    • C Library (Standard C)
    • I/O Port Interface and Control
  • POSIX.1b, Real-time extensions
    • Priority Scheduling
    • Real-Time Signals
    • Clocks and Timers
    • Semaphores
    • Message Passing
    • Shared Memory
    • Asynch and Synch I/O
    • Memory Locking Interface
  • POSIX.1c, Threads extensions
    • Thread Creation, Control, and Cleanup
    • Thread Scheduling
    • Thread Synchronization
    • Signal Handling

[edit] POSIX-oriented operating systems

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.[7]

[edit] Fully POSIX-compliant

The following operating systems conform (i.e., are 100% compliant) to one or more of the various POSIX standards.

[edit] Mostly POSIX-compliant

 Please help improve this section by expanding it.
Further information might be found on the talk page or at requests for expansion.

The following are not officially certified as POSIX compatible, but they conform in large part.

[edit] POSIX for Windows

[edit] Compliant via compatibility feature

The following are not officially certified as POSIX compatible, however 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.

[edit] Notes and references

  1. ^ POSIX. Standards. IEEE.
  2. ^ POSIX® 1003.1 FAQ Version 1.12 (2006-02-02). Retrieved on 2006-07-16.
  3. ^ Introduction. GNU/Linux C Programming.
  4. ^ POSIX. NIST.
  5. ^ Version 3. Single Unix Specification. Unix.
  6. ^ Linux Signals.
  7. ^ POSIX Certification. IEEE.
  8. ^ OS Comparison.
  9. ^ Schweik. POSIX utilities. FreeBSD.
  10. ^ APE — ANSI/POSIX Environement. Plan 9. Bell Labs.
  11. ^ POSIX Compatibility. MS Windows NT Workstation Resource Kit. Microsoft.

[edit] Industrial resources

  • International Journal of IT Standards and Standardization Research, IGI Global

[edit] See also

[edit] External links

v • d • e
Computing signals
POSIX
SIGABRT · SIGALRM · SIGFPE · SIGHUP · SIGILL · SIGINT · SIGKILL · SIGPIPE · SIGQUIT · SIGSEGV · SIGTERM · SIGUSR1 · SIGUSR2 · SIGCHLD · SIGCONT · SIGSTOP · SIGTSTP · SIGTTIN · SIGTTOU · SIGBUS · SIGPOLL · SIGPROF · SIGSYS · SIGTRAP · SIGURG · SIGVTALRM · SIGXCPU · SIGXFSZ · Realtime signals are user definable (SIGRTMIN+n through SIGRTMAX)
non-POSIX