IEEE Std 1003.1-2013：POSIX操作系统接口标准详解

2 浏览量更新于2024-07-14 收藏 13.24MB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

"POSIX Base - Issue 7 - 2013 (C138)" 是一份关于2013年版的开放团体标准——基础规范，第七版，它结合了IEEE Std 1003.1TM-2008及2013年的修正1号。这份文档是信息技术领域便携式操作系统接口（POSIX）的基础规范，由IEEE计算机学会和开放团体共同发布。 POSIX（Portable Operating System Interface）是一个定义了操作系统接口的一系列标准，目的是为了促进软件的可移植性，使得编写在遵循POSIX标准的系统上的程序可以在其他同样遵循POSIX的系统上运行，而无需或只需少量修改。这个标准基于Unix系统，并且广泛应用于各种操作系统，如Linux、AIX、Solaris等。 2013年版的POSIX基础规范包含了2008年版的IEEE Std 1003.1TM标准以及2013年的技术修正1号。技术修正主要是对2008年标准批准后发现的问题进行的修订和澄清，以提高标准的准确性和一致性。该规范的主要内容包括： 1. **命令解释器（Shell）**：它是用户与操作系统交互的主要接口，允许用户输入命令并执行。 2. **公用实用程序**：这些程序提供了基本的文件处理、文本操作、进程控制等功能，是开发应用程序的基础工具。 3. **标准I/O库**：定义了输入输出操作的接口，如打开、关闭、读写文件等。 4. **系统调用接口**：定义了操作系统提供的系统调用，如进程管理、内存管理、文件系统操作等。 5. **线程和同步**：描述了多线程编程的API，包括线程创建、销毁、同步和互斥机制。 6. **信号处理**：定义了进程间通信和异常处理的机制。 7. **错误处理和诊断**：规定了错误代码和错误处理的规则。 8. **国际化和本地化**：支持不同语言和地区的需求，包括字符编码、日期和时间格式等。 POSIX标准对于软件开发者来说具有重要意义，因为它提供了一个统一的开发环境，使得程序员可以编写跨平台的代码，同时也有助于操作系统供应商保持与业界标准的兼容性。对于系统管理员和IT专业人员，了解POSIX标准有助于理解操作系统的工作原理，优化系统性能，以及更好地管理和维护多平台环境。 POSIX Base - Issue 7 - 2013是操作系统接口和环境的重要规范，它定义了标准的操作系统接口，支持应用程序的跨平台开发，促进了信息技术领域的标准化和互操作性。

资源详情

资源推荐

Audience

The intended audience for POSIX.1-2008 is all persons concerned with an industry-wide standard operating

system based on the UNIX system. This includes at least four groups of people:

• Persons buying hardware and software systems

• Persons managing companies that are deciding on future corporate computing directions

• Persons implementing operating systems, and especially

• Persons developing applications where portability is an objective

Purpose

Several principles guided the development of POSIX.1-2008:

• Application-Oriented – The basic goal was to promote portability of application programs across

UNIX system environments by developing a clear, consistent, and unambiguous standard for the

interface specification of a portable operating system based on the UNIX system documentation.

POSIX.1-2008 codifies the common, existing definition of the UNIX system.

• Interface, Not Implementation – POSIX.1-2008 defines an interface, not an implementation. No

distinction is made between library functions and system calls; both are referred to as functions. No

details of the implementation of any function are given (although historical practice is sometimes

indicated in the RATIONALE section). Symbolic names are given for constants (such as signals and

error numbers) rather than numbers.

• Source, Not Object, Portability – POSIX.1-2008 has been written so that a program written and

translated for execution on one conforming implementation may also be translated for execution on

another conforming implementation. POSIX.1-2008 does not guarantee that executable (object or

binary) code will execute under a different conforming implementation than that for which it was

translated, even if the underlying hardware is identical.

• The C Language – The system interfaces and header definitions are written in terms of the standard

C language as specified in the ISO C standard.

• No Superuser, No System Administration – There was no intention to specify all aspects of an

operating system. System administration facilities and functions are excluded from this standard,

and functions usable only by the superuser have not been included. Still, an implementation of the

standard interface may also implement features not in POSIX.1-2008. POSIX.1-2008 is also not

concerned with hardware constraints or system maintenance.

• Minimal Interface, Minimally Defined – In keeping with the historical design principles of the

UNIX system, the mandatory core facilities of POSIX.1-2008 have been kept as minimal as

possible. Additional capabilities have been added as optional extensions.

• Broadly Implementable – The developers of POSIX.1-2008 endeavored to make all specified

functions implementable across a wide range of existing and potential systems, including:

— All of the current major systems that are ultimately derived from the original UNIX system code

(Version 7 or later)

— Compatible systems that are not derived from the original UNIX system code

— Emulations hosted on entirely different operating systems

— Networked systems

— Distributed systems

— Systems running on a broad range of hardware

No direct references to this goal appear in POSIX.1-2008, but some results of it are mentioned in the

Rationale (Informative) volume.

• Minimal Changes to Historical Implementations – When the original version – IEEE Std 1003.1-

1988 – was published, there were no known historical implementations that did not have to change.

However, there was a broad consensus on a set of functions, types, definitions, and concepts that

formed an interface that was common to most historical implementations.

The adoption of the 1988 and 1990 IEEE system interface standards, the 1992 IEEE shell and

utilities standard, the various Open Group (formerly X/Open) specifications, and IEEE Std 1003.1-

2001 and its technical corrigenda have consolidated this consensus, and this version reflects the

significantly increased level of consensus arrived at since the original versions. The authors of the

original versions tried, as much as possible, to follow the principles below when creating new

specifications:

— By standardizing an interface like one in an historical implementation; for example, directories

— By specifying an interface that is readily implementable in terms of, and backwards-compatible

with, historical implementations, such as the extended tar format defined in the pax utility

— By specifying an interface that, when added to an historical implementation, will not conflict

with it; for example, the sigaction() function

POSIX.1-2008 is specifically not a codification of a particular vendor's product.

It should be noted that implementations will have different kinds of extensions. Some will reflect

“historical usage” and will be preserved for execution of pre-existing applications. These functions

should be considered “obsolescent” and the standard functions used for new applications. Some

extensions will represent functions beyond the scope of POSIX.1-2008. These need to be used with

careful management to be able to adapt to future extensions of POSIX.1-2008 and/or port to

implementations that provide these services in a different manner.

• Minimal Changes to Existing Application Code – A goal of POSIX.1-2008 was to minimize

additional work for application developers. However, because every known historical

implementation will have to change at least slightly to conform, some applications will have to

change.

POSIX.1-2008

POSIX.1-2008 defines the Portable Operating System Interface (POSIX) requirements and consists of the

following topics arranged as a series of volumes within the standard:

• Base Definitions

• System Interfaces

• Shell and Utilities

• Rationale (Informative)

Base Definitions

The Base Definitions volume provides common definitions for this standard, therefore readers should be

familiar with it before using the other volumes.

This volume is structured as follows:

• Chapter 1 is an introduction.

• Chapter 2 defines the conformance requirements.

• Chapter 3 defines general terms used.

• Chapter 4 describes general concepts used.

• Chapter 5 describes the notation used to specify file input and output formats in this volume and the

Shell and Utilities volume.

• Chapter 6 describes the portable character set and the process of character set definition.

• Chapter 7 describes the syntax for defining internationalization locales as well as the POSIX locale

provided on all systems.

• Chapter 8 describes the use of environment variables for internationalization and other purposes.

• Chapter 9 describes the syntax of pattern matching using regular expressions employed by many

utilities and matched by the regcomp() and regexec() functions.

• Chapter 10 describes files and devices found on all systems.

• Chapter 11 describes the asynchronous terminal interface for many of the functions in the System

Interfaces volume and the stty utility in the Shell and Utilities volume.

• Chapter 12 describes the policies for command line argument construction and parsing.

• Chapter 13 defines the contents of headers which declare the functions and global variables, and

define types, constants, macros, and data structures that are needed by programs using the services

provided by the System Interfaces volume.

Comprehensive references are available in the index.

System Interfaces

The System Interfaces volume describes the interfaces offered to application programs by POSIX-

conformant systems. Readers are expected to be experienced C language programmers, and to be familiar

with the Base Definitions volume.

This volume is structured as follows:

• Chapter 1 explains the status of this volume and its relationship to other formal standards.

• Chapter 2 contains important concepts, terms, and caveats relating to the rest of this volume.

• Chapter 3 defines the functional interfaces to the POSIX-conformant system.

Comprehensive references are available in the index.

Shell and Utilities

The Shell and Utilities volume describes the commands and utilities offered to application programs on

POSIX-conformant systems. Readers are expected to be familiar with the Base Definitions volume.

This volume is structured as follows:

• Chapter 1 explains the status of this volume and its relationship to other formal standards. It also

describes the defaults used by the utility descriptions.

• Chapter 2 describes the command language used in POSIX-conformant systems, and special built-in

utilities.

• Chapter 3 describes a set of services and utilities that are implemented on systems supporting the

Batch Environment Services and Utilities option.

• Chapter 4 consists of reference pages for all utilities, other than the special built-in utilities described

in Chapter 2, available on POSIX-conformant systems.

Comprehensive references are available in the index.

Rationale (Informative)

The Rationale volume is published to assist in the process of review. It contains historical information

concerning the contents of this standard and why features were included or discarded by the standard

developers. It also contains notes of interest to application programmers on recommended programming

practices, emphasizing the consequences of some aspects of POSIX.1-2008 that may not be immediately

apparent.

This volume is organized in parallel to the normative volumes of this standard, with a separate part for each

of the three normative volumes.

Within this volume, the following terms are used:

• Base standard – The portions of POSIX.1-2008 that are not optional, equivalent to the definitions of

classic POSIX.1 and POSIX.2.

• POSIX.0 – Although this term is not used in the normative text of POSIX.1-2008, it is used in this

volume to refer to IEEE Std 1003.0™-1995.

• POSIX.1b – Although this term is not used in the normative text of POSIX.1-2008, it is used in this

volume to refer to the elements of the POSIX Realtime Extension amendment. (This was earlier

referred to as POSIX.4 during the standard development process.)

• POSIX.1c – Although this term is not used in the normative text of POSIX.1-2008, it is used in this

volume to refer to the POSIX Threads Extension amendment. (This was earlier referred to as

POSIX.4a during the standard development process.)

• Standard developers – The individuals and companies in the development organizations responsible

for POSIX.1-2008: the IEEE P1003.1 working groups, The Open Group Base working group,

advised by the hundreds of individual technical experts who balloted the draft standards within the

Austin Group, and the member bodies and technical experts of ISO/IEC JTC 1/SC 22.

• XSI option – The portions of POSIX.1-2008 addressing the extension added for support of the

Single UNIX Specification.

Typographical Conventions

The following typographical conventions are used throughout this standard. In the text, this standard is

referred to as POSIX.1-2008, which is technically identical to The Open Group Base Specifications,

Issue 7.

The typographical conventions listed here are for ease of reading only. Editorial inconsistencies in the use

of typography are unintentional and have no normative meaning in POSIX.1-2008.

Reference Example Notes

C-Language Data Structure

aiocb

C-Language Data Structure Member aio_lio_opcode

C-Language Data Type

long

C-Language External Variable errno

C-Language Function system()

C-Language Function Argument arg

C-Language Function Family exec

C-Language Header

C-Language Keyword

return

C-Language Macro with Argument assert()

C-Language Macro with No Argument NET_ADDRSTRLEN

C-Language Preprocessing Directive

#define

Commands within a Utility a, c

Conversion Specifier, Specifier/Modifier Character

%A, g, E

Environment Variable PATH

Error Number [EINTR]

Example Output

Hello, World

Filename

/tmp

Literal Character

'c', '\r'

Literal String

"abcde"

Optional Items in Utility Syntax

[ ]

Parameter <directory pathname>

Reference Example Notes

Special Character <newline> 3

Symbolic Constant _POSIX_VDISABLE

Symbolic Limit, Configuration Value {LINE_MAX} 4

Syntax

#include <sys/stat.h>

User Input and Example Code

echo Hello, World

Utility Name awk

Utility Operand file_name

Utility Option

-c

Utility Option with Option-Argument -w width

Note that:

1. Conversion specifications, specifier characters, and modifier characters are used primarily in date-

related functions and utilities and the fprintf() and fscanf() formatting functions.

2. Unless otherwise noted, the quotes shall not be used as input or output. When used in a list item, the

quotes are omitted. The literal characters <apostrophe> (also known as single-quote) and

<backslash> are either shown as the C constants '\' and '\\', respectively, or as the special

characters <apostrophe>, single-quote, and <backslash> depending on context.

3. The style selected for some of the special characters, such as <newline>, matches the form of the

input given to the localedef utility. Generally, the characters selected for this special treatment are

those that are not visually distinct, such as the control characters <tab> or <newline>.

4. Names surrounded by braces represent symbolic limits or configuration values which may be

declared in appropriate headers by means of the C #define construct.

5. Brackets shown in this font, "[ ]", are part of the syntax and do not indicate optional items. In

syntax the '|' symbol is used to separate alternatives, and ellipses ("...") are used to show that

additional arguments are optional.

Shading is used to identify extensions and options.

Footnotes and notes within the body of the normative text are for information only (informative).

Informative sections (such as Rationale, Change History, Application Usage, and so on) are denoted by

continuous shading bars in the margins.

Ranges of values are indicated with parentheses or brackets as follows:

1. (a,b) means the range of all values from a to b, including neither a nor b.

2. [a,b] means the range of all values from a to b, including a and b.

3. [a,b) means the range of all values from a to b, including a, but not b.

4. (a,b] means the range of all values from a to b, including b, but not a.

Note: A symbolic limit beginning with POSIX is treated differently, depending on context. In a C-

language header, the symbol POSIXstring (where string may contain underscores) is represented

by the C identifier _POSIXstring, with a leading underscore required to prevent ISO C standard

name space pollution. However, in other contexts, such as languages other than C, the leading

underscore is not used because this requirement does not exist.

剩余3905页未读，继续阅读

weixin_38570519

粉丝: 2
资源: 975

IEEE Std 1003.1-2013：POSIX操作系统接口标准详解

winlibs-x86_64-posix-seh-gcc-11.3.0-llvm-14.0.3-mingw-w64msvcrt-10.0.0-r3.zip

x86-64-13.2.0-release-posix-seh-rev1.7z

IEEE POSIX Base Specifications, Issue 7-1003.1- 2004-Edition

IEEE POSIX Base Definitions-1003.1- 2004-Edition

PosixThread - 20200228.rar

High Res POSIX timers-开源

Extensions to POSIX Packaging-开源

Programming with POSIX Threads - Part 3

Programming with POSIX Threads - Part 2

Programming with POSIX Threads - Part 4

Programming with POSIX Threads - Part 1

POSIX标准 - IEEE Std 1003.1-2017

Using the POSIX API - Threads, real-time and IPC

ldapscripts:简单的Shell脚本来处理LDAP目录中的POSIX条目-开源

MinGW-x86-64-posix-seh-gcc-12.2

mingw-x86-64-8.1.0-release-posix-seh-rt-v6-rev

x86-64-12.2.0-release-posix-seh-rt-v10-rev0

x86-64-13.2.0-release-posix-seh-msvcrt-rt-v11-rev0

x86-64-12.2.0-release-posix-seh-msvcrt-rt-v10-rev2

最新资源