POSIX - Austin Joint Working Group

Andrew Josey

IEEE Std 1003.1-202x defines a standard operating system interface and environment, including a command interpreter (or "shell"), and common utility programs to support applications portability at the source code level. It is intended to be used by both applications developers and system implementors. IEEE Std 1003.1-202x comprises four major components (each in an associated volume): 1. General terms, concepts, and interfaces common to all volumes of IEEE Std 1003.1-202x, including utility conventions and C-language header definitions, are included in the Base Definitions volume of IEEE Std 1003.1-202x. 2. Definitions for system service functions and subroutines, language-specific system services for the C programming language, function issues, including portability, error handling, and error recovery, are included in the System Interfaces volume of IEEE Std 1003.1-202x. 3. Definitions for a standard source code-level interface to command interpretation services (a "shell") and common utility programs for application programs are included in the Shell and Utilities volume of IEEE Std 1003.1-202x. 4. Extended rationale that did not fit well into the rest of the document structure, containing historical information concerning the contents of IEEE Std 1003.1-202x and why features were included or discarded by the standard developers, is included in the Rationale (Informative) volume of IEEE Std 1003.1-202x. The following areas are outside of the scope of IEEE Std 1003.1-202x: * Graphics interfaces * Database management system interfaces * Record I/O considerations * Object or binary code portability * System configuration and resource availability IEEE Std 1003.1-202x describes the external characteristics and facilities that are of importance to applications developers, rather than the internal construction techniques employed to achieve these capabilities. Special emphasis is placed on those functions and facilities that are needed in a wide variety of commercial applications.

The Portable Applications Standards Committee of the IEEE Computer Society carried out a series of analyses of various problems encountered by users of IEEE Std 1003.1 -1990, IEEE Standard for Information Technology- Portable Operating System Interface (POSIX)- Part 1: System Application Program Interface (API) and IEEE Std 2003.1 -1992, IEEE Standard for Information Technology- Test Methods for Measuring Conformance to POSIX- Part 1: System Interfaces. The results of its deliberations are presented in this document. The intent is to give the POSIX community reasonable ways of interpreting unclear portions of these standards.

This standard defines a standard operating system interface and environment, including a command interpreter (or "shell"), and common utility programs to support applications portability at the source code level. It is the single common revision to IEEE Std 1003.1-1996, IEEE Std 1003.2-1992, and the Base Specifications of The Open Group Single UNIX(TM)? Specification, Version 2. This standard is intended to be used by both applications developers and system implementors and comprises four major components (each in an associated volume)

This Technical Corrigendum addresses problems discovered since the approval of The Open Group Base Specifications, Issue 6, IEEE Std 1003.1-2001, and ISO/IEC 9945: 2002. These are mainly due to resolving integration issues raised by the merger of the original Base documents.

This standard is simultaneously ISO/IEC 9945, IEEE Std 1003.1, and forms the core of the Single Unix Specification, Version 3. This 2004 edition includes IEEE Std 1003.1-2001/Cor 1-2002 and IEEE Std 1003.1-2001/Cor 2-2004 incorporated into IEEE Std 1003.1-2001 (the base document). The two Corrigenda address problems discovered since the approval of IEEE Std 1003.1-2001. These changes are mainly due to resolving integration issues raised by the merger of the base documents that were incorporated into the IEEE Std 1003.1-2001, which is the single common revision to IEEE Std 1003.1-1996, IEEE Std 1003.2-1992, ISO/IEC 9945-1:1996, ISO/IEC 9945-2:1993, and the Base Specifications of The Open Group Single UNIX? Specification, Version 2.

This Technical Corrigendum addresses problems discovered since the approval of IEEE Std 1003.1TM -2008.

Problems discovered since the approval of IEEE Std 1003.1-2008 and IEEE Std 1003.1-2008/Cor 1-2013 are addressed.

POSIX.1-2017 is simultaneously IEEE Std 1003.1-2017 and The Open Group Standard Base Specifications, Issue 7. POSIX.1-2017 defines a standard operating system interface and environment, including a command interpreter (or ?shell?), and common utility programs to support applications portability at the source code level. POSIX.1-2017 is intended to be used by both application developers and system implementors and comprises four major components (each in an associated volume): ? General terms, concepts, and interfaces common to all volumes of this standard, including utility conventions and C-language header definitions, are included in the Base Definitions volume. ? Definitions for system service functions and subroutines, language-specific system services for the C programming language, function issues, including portability, error handling, and error recovery, are included in the System Interfaces volume. ? Definitions for a standard source code-level interface to command interpretation services (a ?shell?) and common utility programs for application programs are included in the Shell and Utilities volume. ? Extended rationale that did not fit well into the rest of the document structure, which contains historical information concerning the contents of POSIX.1-201x and why features were included or discarded by the standard developers, is included in the Rationale (Informative) volume. The following areas are outside the scope of POSIX.1-201x: ? Graphics interfaces ? Database management system interfaces ? Record I/O considerations ? Object or binary code portability ? System configuration and resource availability POSIX.1-2017 describes the external characteristics and facilities that are of importance to application developers, rather than the internal construction techniques employed to achieve these capabilities. Special emphasis is placed on those functions and facilities that are needed in a wide variety of commercial applications.