summaryrefslogtreecommitdiffstats
path: root/doc/posix1003.1/preface.texi
diff options
context:
space:
mode:
Diffstat (limited to 'doc/posix1003.1/preface.texi')
-rw-r--r--doc/posix1003.1/preface.texi29
1 files changed, 29 insertions, 0 deletions
diff --git a/doc/posix1003.1/preface.texi b/doc/posix1003.1/preface.texi
new file mode 100644
index 0000000000..33272e47f7
--- /dev/null
+++ b/doc/posix1003.1/preface.texi
@@ -0,0 +1,29 @@
+@c
+@c COPYRIGHT (c) 1988-2002.
+@c On-Line Applications Research Corporation (OAR).
+@c All rights reserved.
+@c
+@c $Id$
+@c
+
+@ifnottex
+@node Preface, General, Top, Top
+@end ifnottex
+
+@unnumbered 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 @code{getpid()} when there
+can only be one process. But providing routines like @code{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.