| Single Unix Specification |
Article Index for Single |
Shopping Specification |
Articles about Single Unix Specification |
Website Links For Single |
Information AboutSingle Unix Specification |
| CATEGORIES ABOUT SINGLE UNIX SPECIFICATION | |
| posix standards | |
|
HISTORY The SUS emerged from a mid- 1980s project to standardize Operating System Interface s for software designed for variants of the Unix operating system. The need for standardization arose because enterprises using computers wanted to be able to develop programs that could be used on the computer systems of different manufacturers without reimplementing the programs. Unix was selected as the basis for a standard system interface partly because it was manufacturer-neutral. These standards became IEEE 1003 (also registered as ''' ISO / IEC 9945'''), or ''' POSIX ''', which loosely stands for '''Portable Operating System Interface'''. Previously, The Open Group's Single UNIX Specification was separate from the official IEEE POSIX. The near-equivalent SUS became more popular with the involvement of several major vendors in the wake of the Unix Wars because it was available for free, whereas the IEEE charged a substantial fee for access to the POSIX specification. Beginning in 1998 a joint Working Group known as the Austin Group , began to develop the combined standard that would be known as the Single UNIX Specification Version 3. SPECIFICATION The user and software interfaces to the OS are specified in four main sections:
The standard user command line and scripting interface is the Bourne Shell . Other user-level programs, services and utilities include Awk , Echo , Ed , and numerous (hundreds) others. Required program-level services include basic I/O ( File , Terminal , and Network ) services. A test suite accompanies the standard. It is called PCTS or the '''Posix Certification Test Suite'''. Note that a system need not include Source Code derived in any way from AT&T Unix to meet the specification. For instance, IBM OS/390 , now Z/OS , qualifies as a "Unix" despite no code in common. MARKS FOR COMPLIANT SYSTEMS There are two official marks for conforming systems:
LINUX AND THE SUS Linus Torvalds designed Linux to be as POSIX conforming as possible. First, this was a lot of guess-work, because he purchased a printout of the standard some time after starting on Linux. He is also said to have based his system call behavior on Man Page s from other systems. Most Linux vendors do not go to the expense of certifying a given version of their Distribution as meeting the SUS. Furthermore, the content of a typical Linux distribution changes so fast that recertification would be required far more often than would be financially viable. For Linux systems, several common extensions and complementary de facto standards are provided by the Linux Standard Base . BSD AND THE SUS No freely available BSD system was registered as SUS compliant, for the same reasons as Linux. SEE ALSO
EXTERNAL LINKS
|
|
|