CAN/CSA-ISO/IEC/IEEE 9945-10 - Information technology - Portable operating system interface (POSIX®) base specifications, issue 7 (Adopted ISO/IEC/IEEE 99945-2009, first edition, 2009-09-15)

Preface

Standards development within the Information Technology sector is harmonized with international standards development. Through the CSA Technical Committee on Information Technology (TCIT), Canadians serve as the Canadian Advisory Committee (CAC) on ISO/IEC Joint Technical Committee 1 on Information Technology (ISO/IEC JTC1) for the Standards Council of Canada (SCC), the ISO member body for Canada and sponsor of the Canadian National Committee of the IEC. Also, as a member of the International Telecommunication Union (ITU), Canada participates in the International Telegraph and Telephone Consultative Committee (ITU-T).

Scope

POSIX.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.

POSIX.1-2008 comprises four major components (each in an associated volume):

1. General terms, concepts, and interfaces common to all volumes of POSIX.1-2008, including utility conventions and C-language header definitions, are included in the Base Definitions volume of POSIX.1-2008.

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-2008.

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-2008.

4. Extended rationale that did not fit well into the rest of the document structure, containing historical information concerning the contents of POSIX.1-2008 and why features were included or discarded by the standard developers, is included in the Rationale (Informative) volume of POSIX.1-2008.

The following areas are outside of the scope of POSIX.1-2008:

- Graphics interfaces

- Database management system interfaces

- Record I/O considerations

- Object or binary code portability

- System configuration and resource availability POSIX.1-2008 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-2008 are drawn from the following base documents:

- IEEE Std 1003.1, 2004 Edition (POSIX-1) (incorporating IEEE Std 1003.1-2001, IEEE Std 1003.1-2001/Cor 1-2002, and IEEE Std 1003.1-2001/Cor 2-2004)

- The Open Group Technical Standard, 2006, Extended API Set Part 1

- The Open Group Technical Standard, 2006, Extended API Set Part 2

- The Open Group Technical Standard, 2006, Extended API Set Part 3

- The Open Group Technical Standard, 2006, Extended API Set Part 4

- ISO/IEC 9899: 1999, Programming Languages - C, including ISO/IEC 9899: 1999/Cor.1: 2001(E), ISO/IEC 9899: 1999/Cor.2: 2004(E), and ISO/IEC 9899: 1999/Cor.3

Emphasis has been placed on standardizing existing practice for existing users, with changes and additions limited to correcting deficiencies in the following areas:

- Issues raised by Austin Group defect reports, IEEE Interpretations against IEEE Std 1003.1, and ISO/IEC defect reports against ISO/IEC 9945

- Issues raised in corrigenda for The Open Group Technical Standards and working group resolutions from The Open Group

- Issues arising from ISO TR 24715: 2006, Conflicts between POSIX and the LSB

- Changes to make the text self-consistent with the additional material merged

- Features, marked Legacy or obsolescent in the base documents, have been considered for removal in this version

- A review and reorganization of the options within the standard

- Alignment with the ISO/IEC 9899: 1999 standard, including ISO/IEC 9899: 1999/Cor.2: 2004(E)

---------------------------------------------------------------

CAN/CSA-ISO/IEC 13210-02 - Information technology - Requirements and guidelines for test methods specifications and test method implementations for measuring conformance to POSIX standards (Adopted ISO/IEC 13210:1999, second edition, 1999-12-15)

Scope

This International Standard is applicable to the development and use of conformance test method specifications for POSIX standards and may be applicable to other application programming interface specifications. This International Standard is intended for developers and users of test method specifications and test method implementations.

The users of this standard include

- Assertion Writers: to format assertions

- Assertion Test Writers: to write assertion tests

- Test Suite or System Procurers: to interpret the results of test suites

The purpose of this standard is to define requirements and guidelines for developing assertions and related test methods for measuring conformance of an implementation under test (IUT) to POSIX standards. Test method implementations may include Conformance Test Software (CTS), POSIX Conformance Test Procedures (CTP), and audits of Conformance Documents (CD).

Testing conformance of an implementation to a standard includes testing the capabilities and behavior of the implementation with respect to the conformance requirements of the standard. 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 the standard; that normally would require exhaustive testing (see 7.2.1), which is impractical for both technical and economic reasons.

---------------------------------------------------------------

CAN/CSA-ISO/IEC 14519-04 - Information technology - POSIX ada language interfaces - Binding for system application program interface (API) (Adopted ISO/IEC 14519:2001 / IEEE 1003.5, 1999, second edition, 2001-12-15)

Scope

This standard defines a set of system application program interfaces to operating system services.

These interfaces provide access via the Ada programming language to the same operating system services for which C-language interfaces are specified in ISO/IEC 9945-1:1996 f2g c 1)2) and IEEE P1003.1g fB14g.

The purpose of this standard is to support application portability at the Ada source code level. This standard is intended to be used by both application developers and system implementors.

This standard is intended to be compatible with implementations of the 1995 revision to the Ada language standard (ISO/IEC 8652:1995 f1g). Fall-back approaches compatible with implementations of the original Ada language standard (ISO/IEC 8652:1987 fB5g) are also provided (see 1.3).

---------------------------------------------------------------

CAN/CSA-ISO/IEC 14766-01 - Information technology - Telecommunications and information exchange between systems - Use of OSI applications over the internet transmission control protocol (TCP) (Adopted ISO/IEC 14766:1997, first edition, 1997-04-01)

Scope

This International Standard defines a mechanism which allows OSI upper layers (all session, presentation, and application entities) to operate over the Internet Transmission Control Protocol (TCP) without being aware that they are running on a TCP/IP internetwork.

It provides similar functionality to ISO/IEC Transport Protocol Class 4.

It does not provide a gateway facility between Internet and OS1 applications.

---------------------------------------------------------------

CAN/CSA-ISO/IEC 15068-2-02 - Information technology - Portable operating system interface (POSIX) system administration - Part 2: Software administration (Adopted ISO/IEC 15068-2:1999, first edition, 1993-03-15, adopted ANSI/IEEE 1387.2-1995)

Scope

This part of ISO/IEC 15068 defines a software packaging layout and utilities that operate on that packaging layout as well as software installed from that packaging layout. The scope of this part of ISO/IEC 15068 is administration of software across distributed systems. This administration includes, but is not limited to, packaging of software for distribution, distribution of software to systems, installation and configuration of software on systems, and removal of software from systems.

This part of ISO/IEC 15068 is motivated by many factors, including a desire by system administrators and software suppliers to have a common way of installing an removing software. To meet the needs of these groups, this part of ISO/IEC 15068 consists of several components, listed below. The readers of this part of ISO/IEC 15068 include system administrators, suppliers of software that implement this part of ISO/IEC 15068, and suppliers of software that use implementation of this part of ISO/IEC 15068. Readers in each of these categories may find their attention drawn to different sections. The key components are listed below.

Software structures

This part of ISO/IEC 15068 defines a hierarchical set of structures used to define software. Information is kept about the software based on these structure definitions. The structure definitions apply both to installed software and to software prepared for installation but not yet installed. Software packaging layout This part of ISO/IEC 15068 defines the organization of software on a distribution medium, the information held about that software, and the way in which such information is represented. This enables both portability of software distributions across systems of different architecture, and the use of different media to distribute software (including both file system and serial image forms).

Information kept about software

This part of ISO/IEC 15068 defines the information that is held about software, both installed software and distributions. This provides a consistent viewof software, even when that software is provided from various sources. The way in which the information is held is undefined within this part of ISO/IEC 15068.

Utilities to administer software

This part of ISO/IEC 15068 defines a utility to convert software into the packaging layout, known as a distribution. This part of ISO/IEC 15068 also contains utilities to examine the information in a distribution, copy software from one distribution to another, install software from a distribution, remove software from a distribution, and verify the integrity of a distribution. There are also utilities for configuring installed software, verifying the integrity of installed software, examining and modifying the information held about installed software, and for removing installed software from a system. This provides administrators with a consistent method of dealing with software across all conforming systems.

Distributed software administration

This part of ISO/IEC 15068 defines the concepts, and the utility syntax and behaviors, for managing software in a distributed environment. This includes the concept of different software administration roles (developer, packager, manager, source, target, and client). Different utilities involve different roles, and different roles may be distributed across multiple systems within a single command execution.

This part of ISO/IEC 15068 is based upon the knowledge of, and documentation for, existing programs that assume an interface and architecture similar to that described by POSIX.1 {2}1) and POSIX.2 {3}. Any questions regarding the definition of terms or the semantics of an underlying concept should be referred to POSIX.1 {2} and POSIX.2 {3}. This part of ISO/IEC 15068 does not require the use of any specific programming language and, in particular, does not require the use of the C language. This part of ISO/IEC 15068 is based upon the knowledge of, and documentation for, existing programs that utilize C-language interfaces. Any questions regarding the definition of terms or the semantics of an underlying concept in this language should be referred to C Standard {B13}.

NOTE: The numbers in curly brackets correspond to those of the references in 1.2. When preceded by a ..B,.. the numbers correspond to those of the bibliography in Annex A.

---------------------------------------------------------------

CAN/CSA-ISO/IEC ISP 15287-2:12 - Information technology - Standardized application environment profile - Part 2: Posix realtime application support (AEP) (Adopted ISO/IEC ISP 15287-2:2000, first edition, 2000-03-15)

Preface

Standards development within the Information Technology sector is harmonized with international standards development. Through the CSA Technical Committee on Information Technology (TCIT), Canadians serve as the Canadian Advisory Committee (CAC) on ISO/IEC Joint Technical Committee 1 on Information Technology (ISO/IEC JTC1) for the Standards Council of Canada (SCC), the ISO member body for Canada and sponsor of the Canadian National Committee of the IEC. Also, as a member of the International Telecommunication Union (ITU), Canada participates in the International Telegraph and Telephone Consultative Committee (ITU-T).
   At the time of publication, ISO/IEC ISP 15287-2:2000 is available from ISO and IEC in English only. CSA will publish the French version when it becomes available from ISO and IEC.

Overview

This standard establishes a set of Realtime Environment Profiles based on ISO/IEC 9945-1:1990 {3} as amended by IEEE Std 1003.1b-1993 {5}, IEEE Std 1003.5b-1996 {9}, and ISO/IEC 9945-2:1993 {4} (POSIX) work and related standards specifying foundations for realtime applications.

The Application Environment Profiles specified herein are appropriate for the development and execution of realtime applications using the services and utilities provided by standards called out in this document.