POSIX.1-2024 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 application developers and system implementors. POSIX.1-2024 comprises four major components (each in an associated volume): 1. General terms, concepts, and interfaces common to all volumes of POSIX.1-2024, including utility conventions and C-language… read more header definitions, are included in the Base Definitions volume of POSIX.1-2024. 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 POSIX.1-2024. 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 POSIX.1-2024. 4. Extended rationale that did not fit well into the rest of the document structure, containing historical information concerning the contents of POSIX.1-2024 and why features were included or discarded by the standard developers, is included in the Rationale (Informative) volume of POSIX.1-2024. The following areas are outside of the scope of POSIX.1-2024: --Graphics interfaces --Database management system interfaces --Record I/O considerations --Object or binary code portability --System configuration and resource availability POSIX.1-2024 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. The facilities provided in POSIX.1-2024 are drawn from the following base documents: --IEEE Std 1003.1-2017 (POSIX.1-2017) --IEEE Std 1003.26-2003 (POSIX.26-2003). ISO/IEC 9899: 2018, Programming Languages -- C (C17) --ISO/IEC TR 24731-2: 2010, Programming languages, their environments and system software interfaces — Extensions to the C library — Part 2: Dynamic Allocation Functions --The Open Group Standard, 2021, Additional APIs for the Base Specifications Issue 8, Part 1 --The Open Group Standard, 2022, Additional APIs for the Base Specifications Issue 8, Part 2 read less
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… read more 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. read less
Provide utility program interfaces, service interfaces, managed object definitions, and a standard software packaging layout. Interfaces allow administrators to maintain software products. The managed-object classes provide a common base for the definition and implementation of software administration applications, especially in a distributed environment. The base document for the work is a specification from HP, with reference material drawn from DEC, USL, SNI, ICL, IBM, and SCO.
This standard establishes the minimum performance criteria for portable radiation protection instrumentation for use in ionizing radiation fields under both normal and extreme environmental conditions, i.e., all environmental conditions. For the portable radiation detection instrumentation addressed in this standard, the radiological ranges for the performance tests are as follows: the dose rate range of operation taken as background to 10 Gy/h (1000 rad/h); the activity-per-unit-area range for… read more surface contamination monitors taken as 0.01 Bq/cm (60 dpm/100 cm) or 0.05 Bq/cm (300 dpm/100 cm) to 200 Bq/cm (1.2 × 10 dpm/100 cm). The testing methods verify that the performance criteria are met over the range of operating conditions for each type of instrumentation. This standard does not specify which instruments or systems are required, nor does it consider the number of specific applications of such instruments. read less
IEEE Std 1003.1-2008 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 application developers and system implementors.
User administration includes, but is not limited to, tasks such as the creation and maintenance of user accounts and groups in both single systems and heterogeneous destributed environments. P1003.7 is committed in this standard to provide the distributed management for a system conformant with IEEE P1003.1 and P1003.2.
This standard defines extensions to POSIX.1 {2} to support application portability at the source-code level. It is intended to be used by both application developers and system implementers. The scope of this standard is to define a portable application interface for applications with realtime constraints requiring the ability to control special devices from the application itself. The intent is to take existing realtime operating system practice and add it to the POSIX family of standards.… read more Specifically within the scope is to define interfaces which do not preclude high-performance implementations on traditional uniprocessor realtime systems, as well as on multiprocessors. Wherever possible, the requirements of other application environments were included in the interface definition. read less
The scope of this standard is the definition of a universal framework/footprint and pin configuration utilizing IEEE 1505 receiver-fixture interface (RFI) framework and connector specifications for portable and benchtop test applications. The pin configuration defined within this standard shall apply to commercial, aerospace, and military automatic test equipment (ATE) testing applications.
This document defines a standard for test methods for the interface to command interpretation, or ''shell,'' services and common utility programs for application programs. These test methods are derived from the definitions contained in ISO/IEC 9945-2:1993 (IEEE Std 1003.2-1992) {9}, hereinafter referred to as''POSIX.2 {9}.'' The services and programs described in POSIX.2 {9} are complementary to those specified by ISO/IEC 9945-1:1990 (IEEE Std 1003.1-1990) {8}, hereinafter referred to as ''… read more POSIX.1 {8}.''This standard has been designed to be used by both verification suite authors and system implementors. However, it is intended to be a reference document and not a tutorial on the construction of verification suites or implementations. {12} IEEE Std 2003.1-1992,3) IEEE Standard for Information Technology — Test Methods for Measuring Conformance to POSIX(TM); — Part 1: System Interfaces. read less
This standard defines the general requirements and test methods for measuring conformance to ISO/IEC 9945-1 :1990 (IEEE Std 1003.1-1990) hereinafter referred to as "POSIX.1" {3}.1 It also defines the test assertions for measuring conformance to POSIX.1 {3}. This standard is intended for use by --Developers of POSIX.1 {3} test methods; --Implementors of POSIX.1 {3} implementations; --Application writers for POSIX.1 {3} conforming implementations; --POSIX.1 {3} testing laboratories; and --Otheres… read more interested in validating the conformance of a vendor-claimed POSIX.1 {3} implementation The purpose of this standard is to specify the test assertions and related test methods for measuring conformance of an implementation to POSIX.1 {3}. Testing conformance of an implementation to a standard includes testing the claimed capabilities and behavior of the implementation with respect to the conformance requirements of the standard. These test methods are intended to provide a reasonable, practical assurance that the implementation conforms to the standard. Use of these test methods will not guarantee conformance of an implementation to POSIX.1 {3}; that normally would require exhaustive testing, which is impractical for both technical and economic reasons. The technical specifications for a POSIX System Application Program Interface are defined in POSIX.1 {3}. IEEE Std 2003.1-1992 defines a means of measuring conformance to the POSIX.1 {3} technical specifications. Any question of interpretation of those technical specifications arising from the use of this standard is a question of interpretation of POSIX.1 {3}. read less