POSIX

Key takeaways

POSIX belongs to science; place it in that map before memorising details.
Learn the definition first, then one example that makes the definition concrete.
Connect POSIX to a quantity you can measure, compute or draw — that is where exam questions come from.
Reproduce the core statement of POSIX from memory before moving on to harder problems.

Reference excerpt

The Portable Operating System Interface (POSIX; IPA: ) is a family of standards specified by the IEEE Computer Society for maintaining compatibility between operating systems. In order to define a level of compatibility, POSIX specifies many aspects of functionality that can be classified as application programming interface (API), command-line shell, and shell commands. Originally derived from commonly-found Unix APIs, shells, and commands (partly because Unix was considered manufacturer-neutral), today many systems conform to the standard – including branded Unix systems, Unix-like systems, and many systems that were historically unrelated to Unix. The standardized user command line and scripting interface were based on the UNIX System V Bourne shell. Many user-level programs, services, and utilities (including awk, echo, ed) were also standardized, based on UNIX System V versions of them, along with required program-level services (including basic I/O: file, terminal, and network). POSIX also defines a standard threading library API which is supported by most modern operating systems. The POSIX standard is developed by the Austin Group (a joint working group among the IEEE, The Open Group, and the ISO/IEC JTC 1/SC 22/WG 15). POSIX is intended to be used by both application and system developers. System developers implement the interface imposed by POSIX, while application developers then use the POSIX interface to ensure compatibility across POSIX compliant systems.

Name The standards emerged from a project that began in 1984 building on work from related activity in the /usr/group association. Richard Stallman suggested the name POSIX to the IEEE instead of the former IEEE-IX. The committee found it more easily pronounceable and memorable, and thus adopted it. Originally, POSIX referred to IEEE Std 1003.1-1988, released in 1988. The family of POSIX standards is formally designated as IEEE 1003 and the ISO/IEC standard number is ISO/IEC 9945. POSIX is a trademark of the IEEE.

Versions POSIX originally consisted of a single document for core services but over time additional documents were published to extend and revise the specification. Before 1997, POSIX comprised multiple documents that were published over the course of several years. After 1997, the Austin Group produces specifications titled Single UNIX Specification (SUS). Over time, the group publishes versions of this specification and later POSIX is amended per some or all of a SUS version. A SUS version consists of a collection of volumes – each for a grouping of required behavior – plus other information (outside of a volume). Each volume is assigned an issue number that is the same for each volume of a version, but is not the same value as the version. For example, SUS version 3 (SUSv3) includes volumes labeled issue 6. As of 2014, POSIX documentation is divided into 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.

Before 1997

POSIX.1 Core Services (IEEE Std 1003.1-1988) incorporates standard ANSI C and includes:

Process Creation and Control Signals

Floating Point Exceptions Segmentation / Memory Violations Illegal Instructions Bus Errors Timers File and Directory Operations Pipes C Library (Standard C) The POSIX terminal interface

POSIX.1b Real-time extensions (IEEE Std 1003.1b-1993, later appearing as librt—the Realtime Extensions library) includes:

Priority Scheduling Real-Time Signals Clocks and Timers Semaphores Message Passing Shared Memory Asynchronous and Synchronous I/O Memory Locking Interface

POSIX.1c Threads extensions (IEEE Std 1003.1c-1995) includes:

Thread Creation, Control, and Cleanup Thread Scheduling Thread Synchronization Signal Handling

POSIX.2 Shell and Utilities (IEEE Std 1003.2-1992) includes:

Command Interpreter Utility Programs

POSIX.1-2001 POSIX.1-2001 (IEEE Std 1003.1-2001) consists of most of SUSv3 which consists of volumes (issue 6): Base Definitions, System Interfaces and Headers, and Commands and Utilities. The POSIX specification specifically excludes the SUSv3 requirements for a curses API (often called X/Open Curses, even though there is no distinct grouping of this in SUSv3). IEEE Std 1003.1-2004 modifies POSIX.1-2001 via two minor updates or errata referred to as technical corrigenda documents.

POSIX.1-2008 Similar to its predecessor, POSIX.1-2008 (IEEE Std 1003.1-2008, 2016 Edition) consists of most of the normative material of SUSv4 (issue 7 of volumes Base Definitions, System Interfaces and Headers, Commands and Utilities). SUSv4 also includes rationale information that largely applies to POSIX although not included per se.

POSIX.1-2017 POSIX.1-2017 (IEEE Std 1003.1-2017) revises the previous version (POSIX.1-2008) via two technical corrigenda.

POSIX.1-2024 POSIX.1-2024 (IEEE Std 1003.1-2024) was published on 14 June 2024. As of POSIX 2024, the standard is aligned with the C17 language standard.

Controversies

512- vs 1024-byte blocks

POSIX mandates 512-byte default block sizes for the df and du utilities, reflecting the typical 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 POSIX_ME_HARDER was introduced to allow the user to force the standards-compliant behaviour. The variable name was later changed to POSIXLY_CORRECT. As of 2025, this variable is also used for a number of other behaviour quirks.

Conformance An operating system can be classified depending upon the degree of conformance with a POSIX standard.

Certified Current 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 and their certification has not expired and the operating system has not been discontinued.

… excerpt ends here. Continue reading the full article.

Worked examples

Example 1 — a first encounter with POSIX

Start with the simplest possible case. Write down what POSIX claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In science, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to POSIX before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about POSIX ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of POSIX

In research: POSIX appears in science research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry: Engineering practice reuses POSIX in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom: POSIX is common in secondary-school and first-year university syllabi. It links to neighbouring topics Application programming interfaces, IEC standards, IEEE standards, so understanding it makes those chapters shorter.
In everyday life: Look for POSIX outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.

How to study POSIX in 20 minutes

Read the reference excerpt below once, without taking notes.
Close the page and write down what POSIX means in your own words.
Compare your version with the excerpt and mark what you missed.
Work through the three examples above with pen and paper.
Explain POSIX out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is POSIX in simple terms?

The Portable Operating System Interface (POSIX; IPA: ) is a family of standards specified by the IEEE Computer Society for maintaining compatibility between operating systems. In order to define a level of compatibility, POSIX specifies many aspects of functionality that can be classified as applic…

Why does POSIX matter?

Because it connects several science ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study POSIX?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on POSIX.