diff options
author | Amar Takhar <amar@rtems.org> | 2016-01-16 19:14:55 -0500 |
---|---|---|
committer | Amar Takhar <verm@darkbeer.org> | 2016-05-02 20:51:23 -0400 |
commit | ef0a063a84282f74a9da4a899c555037972873a9 (patch) | |
tree | b49917084fd03c9d3cf0c08a1dc204298eba404b /posix1003_1/preface.rst | |
parent | Fix warnings. (diff) | |
download | rtems-docs-ef0a063a84282f74a9da4a899c555037972873a9.tar.bz2 |
Split document into seperate files by section.
Diffstat (limited to 'posix1003_1/preface.rst')
-rw-r--r-- | posix1003_1/preface.rst | 26 |
1 files changed, 26 insertions, 0 deletions
diff --git a/posix1003_1/preface.rst b/posix1003_1/preface.rst new file mode 100644 index 0000000..f56a8cc --- /dev/null +++ b/posix1003_1/preface.rst @@ -0,0 +1,26 @@ +======= +Preface +======= + +This document lists the functions, constant, macros, feature flags, +and types defined in the POSIX 1003.1 standard. Each section in +this document corresponds to a section in the 1003.1 standard +and the implementation status of the items required by the standard +are listed. + +RTEMS supports a number of POSIX process, user, and group oriented +routines in what is referred to as a "SUSP" (Single-User, Single +Process) manner. RTEMS supports a single process, multithreaded +POSIX 1003.1b environment. In a pure world, there would be +no reason to even include routines like ``getpid()`` when there +can only be one process. But providing routines like ``getpid()`` +and making them work in a sensible fashion for an embedded environment +while not returning ENOSYS (for not implemented) makes it significantly +easier to port code from a UNIX environment without modifying it. + +.. COMMENT: COPYRIGHT (c) 1988-2002. + +.. COMMENT: On-Line Applications Research Corporation (OAR). + +.. COMMENT: All rights reserved. + |