mirror of
https://gitlab.rtems.org/rtems/rtos/rtems.git
synced 2025-12-06 23:53:18 +00:00
6449498bc7
* SUPPORT, LICENSE: New files. * Numerous files touched as part of merging the 4.5 branch onto the mainline development trunk and ensuring that the script that cuts snapshots and releases works on the documentation.
30 lines
1.1 KiB
Plaintext
30 lines
1.1 KiB
Plaintext
@c
|
|
@c COPYRIGHT (c) 1988-2002.
|
|
@c On-Line Applications Research Corporation (OAR).
|
|
@c All rights reserved.
|
|
@c
|
|
@c $Id$
|
|
@c
|
|
|
|
@ifinfo
|
|
@node Preface, General, Top, Top
|
|
@end ifinfo
|
|
|
|
@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.
|