From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Not to be confused with Unix, Unix-like, or Linux.

POSIX (/ˈpɒzɪks/ POZ-iks), an acronym for Portable Operating System Interface,[1] is a family of standards specified by the IEEE Computer Society for maintaining compatibility between operating systems. POSIX defines the application programming interface (API), along with command line shells and utility interfaces, for software compatibility with variants of Unix and other operating systems.[2][3]


Originally, the name "POSIX" referred to IEEE Std 1003.1-1988, 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. Richard Stallman suggested the name POSIX to the IEEE instead of former IEEE-IX. The committee found it more easily pronounceable and memorable, and thus adopted it.[2][4][better source needed]


The POSIX specifications for Unix-like operating systems originally consisted of a single document for the core programming interface, but eventually grew to 19 separate documents (POSIX.1, POSIX.2, etc.).[5] The standardized user command line and scripting interface were based on the Bourne Shell.[6][not in citation given] 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. Nowadays, most of POSIX parts are combined into a single standard, IEEE Std 1003.1-2008, also known as POSIX.1-2008.

As of 2014, POSIX documentation is divided in two parts:

  • POSIX.1, 2013 Edition: POSIX Base Definitions, System Interfaces, and Commands and Utilities (which include POSIX.1, extensions for POSIX.1, Real-time Services, Threads Interface, Real-time Extensions, Security Interface, Network File Access and Network Process-to-Process Communications, User Portability Extensions, Corrections and Extensions, Protection and Control Utilities and Batch System Utilities. This is POSIX 1003.1-2008 with Technical Corrigendum 1.)
  • POSIX Conformance Testing: A test suite for POSIX accompanies the standard: VSX-PCTS or the VSX POSIX Conformance Test Suite.[7]

The development of the POSIX standard takes place in the Austin Group, a joint working group linking the IEEE, The Open Group and the ISO/IEC JTC 1 organizations.


Parts before 1997

Before 1997, POSIX comprised several standards:




  • POSIX.1c, Threads extensions (IEEE Std 1003.1c-1995)
    • Thread Creation, Control, and Cleanup
    • Thread Scheduling
    • Thread Synchronization
    • Signal Handling


Versions after 1997

After 1997, the Austin Group developed the POSIX revisions. The specifications are known under the name Single UNIX Specification, before they become a POSIX standard when formally approved by the ISO.


POSIX.1-2001 or IEEE Std 1003.1-2001 equates to the Single UNIX Specification version 3[8]

This standard consisted of:

  • the Base Definitions, Issue 6,
  • the System Interfaces and Headers, Issue 6,
  • the Commands and Utilities, Issue 6.

POSIX.1-2004 (with two TCs)

IEEE Std 1003.1-2004 involved a minor update of POSIX.1-2001. It incorporated two technical corrigenda.[9] Its contents are available on the web.[10]

POSIX.1-2008 (with one TC)

As of 2014 POSIX.1-2008 with TC1 or IEEE Std 1003.1, 2013 edition represents the current version.[11][12] A free online copy is available.[13]

This standard consists of:

  • the Base Definitions, Issue 7,
  • the System Interfaces and Headers, Issue 7,
  • the Commands and Utilities, Issue 7,
  • the Rationale volume.


512- vs 1024-byte blocks

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 the GNU operating system, they objected to this on the grounds that most people think in terms of 1024 byte (or 1 KiB) blocks. The environment variable POSIXLY_CORRECT was introduced to allow the user to force the standards-compliant behaviour.[14] The variable name POSIX_ME_HARDER was also discussed.[15] The variable POSIXLY_CORRECT is now also used for a number of other behaviour quirks, where “POSIX and common sense disagree”.[citation needed]

POSIX-oriented operating systems

Depending upon the degree of compliance with the standards, one can classify operating systems as fully or partly POSIX compatible. Certified products can be found at the IEEE's website.[16]


Some versions of the following operating systems have been certified to conform to one or more of the various POSIX standards. This means that they passed the automated conformance tests.[17]

Mostly POSIX-compliant

The following, while not officially certified as POSIX compatible, comply in large part:

POSIX for Windows

  • Cygwin provides a largely POSIX-compliant development and run-time environment for Microsoft Windows.
  • MinGW, a fork of Cygwin, provides a less POSIX-compliant development environment and supports compatible C-programmed applications via Msvcrt, Microsoft's old Visual C runtime library.
  • Microsoft POSIX subsystem, an optional Windows subsystem included in Windows NT-based operating systems up to Windows 2000. POSIX-1 as it stood in 1990 revision, without threads or sockets.
  • Interix, originally OpenNT by Softway Systems, Inc., is an upgrade and replacement for Microsoft POSIX subsystem that was purchased by Microsoft in 1999. It was initially marketed as a stand-alone add-on product and then later included it as a component in Windows Services for UNIX (SFU) and finally incorporated it as a component in Windows Server 2003 R2 and later Windows OS releases under the name "Subsystem for UNIX-based Applications" (SUA); later made deprecated in 2012 (Windows 8)[30] and dropped in 2013 (2012 R2, 8.1). It enables full POSIX compliance for certain Microsoft Windows products[citation needed].
  • UWIN from AT&T Research implements a POSIX layer on top of the Win32 APIs.
  • MKS Toolkit, originally created for MS-DOS, is a software package produced and maintained by MKS Inc. that provides a Unix-like environment for scripting, connectivity and porting Unix and Linux software to both 32- and 64-bit Microsoft Windows systems. A subset of it was included in the first release of Windows Services for UNIX (SFU) in 1998.[31]
  • Windows C Runtime Library and Windows Sockets API implement commonly used POSIX API functions for file, time, environment, and socket access,[32] although the support remains largely incomplete and not fully interoperable with POSIX-compliant implementations.[33][34][discuss]

POSIX for OS/2

Mostly POSIX compliant environments for OS/2:

  • emx+gcc – largely POSIX compliant


Partially POSIX compliant environments for DOS include:

  • emx+gcc – largely POSIX compliant
  • DJGPP – partially POSIX compliant
  • DR-DOS multitasking core via EMM386 /MULTI - a POSIX threads frontend API extension is available

Compliant via compatibility feature

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.

See also


  1. "POSIX.1 FAQ". The Open Group. October 5, 2011. 
  2. 2.0 2.1 "POSIX 1003.1 FAQ Version 1.12". 2 February 2006. Retrieved 16 July 2006. 
  3. "POSIX". Standards. IEEE. 
  4. "The origin of the name POSIX.". 2011. Retrieved 28 September 2013. 
  5. PASC Status (including POSIX) (Report). IEEE Computer Society. 2003-12-04. Retrieved 2015-03-01. 
  6. http://pubs.opengroup.org/onlinepubs/9699919799/
  7. "POSIX". The Open Group. 
  8. "The Open Group announces completion of the joint revision to POSIX and the Single UNIX Specification" (Press release). The Open Group. 30 January 2002. Retrieved 26 July 2009. 
  9. "IEEE Std 1003.1" (2004 ed.). Unix.org. Retrieved 26 July 2009 
  10. "IEEE Std 1003.1" (2004 ed.). The Open Group .
  11. "Base Specifications, Issue 7, 2013 Edition". The Open Group. Retrieved 18 December 2014. 
  12. "The Austin Common Standards Revision Group". The Open Group. Retrieved 27 July 2009. 
  13. "Posix.1-2013". The Open Group. .
  14. "Announce" (Google Groups replica). GNU .
  15. "Freedom, Innovation, and Convenience: The RMS Interview". Linuxdevcenter. 22 December 2004 .
  16. "POSIX Certification". IEEE. 
  17. http://get.posixcertified.ieee.org/docs/POSIX_Certification_Guide.html#Howto.  Missing or empty |title= (help)
  18. "IBM". The Open Group. Retrieved 26 January 2014. 
  19. 19.0 19.1 "Hewlett-Packard". The Open Group. Retrieved 26 January 2014. 
  20. "Silicon Graphics, Inc.". The Open Group. Retrieved 26 January 2014. 
  21. "The Open Brand - Register of Certified Products". Register of Open Branded Products. The Open Group. Retrieved May 20, 2015. 
  22. "Apple Inc". Register of Open Branded Products. The Open Group. Retrieved May 20, 2015. 
  23. "Oracle Corporation". The Open Group. Retrieved 26 January 2014. 
  24. "UnixWare ® 7.1.3 and later". The Open Group. 16 May 2003. 
  25. http://www.qnx.com/news/pr_2862_1.html.  Missing or empty |title= (help)
  26. "Register of Open Branded Products". www.opengroup.org. Retrieved 2016-01-05. 
  27. Schweik. "POSIX utilities". FreeBSD. 
  28. Solter, Nicholas A.; Jelinek, Jerry; Miner, David (2011-03-21). OpenSolaris Bible. John Wiley & Sons. ISBN 9781118080313. 
  29. Enterprise, I. D. G. (1994-11-07). Computerworld. IDG Enterprise. 
  30. Features Removed or Deprecated in Windows Server 2012
  31. Windows NT Services for UNIX Add-On Pack for NT 4; see also the November '98 press release for MKS toolkit 6.1, also archived elsewhere
  32. "MSDN Library: Deprecated CRT Functions". Microsoft. Retrieved 8 Oct 2015. 
  33. "MSDN Library: Porting Socket Applications to Winsock". Microsoft. Retrieved 8 Oct 2015. 
  34. "Winsock Programmer’s FAQ Articles: BSD Sockets Compatibility". Warren Young. 31 Aug 2015. Retrieved 8 Oct 2015. 
  35. "APE — ANSI/POSIX Environment". Plan 9. Bell Labs. 
  36. "POSIX Compatibility". MS Windows NT Workstation Resource Kit. Microsoft. 

External links

Template:Open Group standards