From 2c3cf2166dd35152bb006d027476400be8759615 Mon Sep 17 00:00:00 2001 From: Joel Sherrill Date: Mon, 28 Aug 2017 13:03:40 -0500 Subject: New version of POSIX Compliance Guide This is a replacement of the POSIX 1003.1 Compliance Guide. It will be generated from a .csv file. Updates #3177. --- posix1003-1/preface.rst | 28 ---------------------------- 1 file changed, 28 deletions(-) delete mode 100644 posix1003-1/preface.rst (limited to 'posix1003-1/preface.rst') diff --git a/posix1003-1/preface.rst b/posix1003-1/preface.rst deleted file mode 100644 index 5c8fa59..0000000 --- a/posix1003-1/preface.rst +++ /dev/null @@ -1,28 +0,0 @@ -.. comment SPDX-License-Identifier: CC-BY-SA-4.0 - -======= -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. - -- cgit v1.2.3