Sponsored Content
Top Forums UNIX for Dummies Questions & Answers UNIX® ?? - vs... um.. non ® Post 49498 by Driver on Friday 2nd of April 2004 10:32:19 AM
Old 04-02-2004
A list of certified systems can be found at http://www.opengroup.org/openbrand/register/.

The benefit of working on UNIX-branded operating systems is that the brand means you can rely on the presence and correctness of the system interfaces and utilities specified in the various versions of the Single UNIX Specification.

Your system will only be branded UNIX if it passes large test suites verifying the compliance with this specification. If a system interface does not function on a UNIX(R) system as documented in this document, this is a bug (the brand ``guarantees'' that this should not happen, or at least be a very unlikely event).

Whether this guaranteed degree of standards conformance is useful to you or not is another question. It can be useful to application programmers. A UNIX-branded system will have many interfaces not found in free ``Unix-like'' systems, such as POSIX message queues, POSIX semaphores and other advanced realtime facilities, as well as *correct* Pthreads and rwlocks/barriers (NPTL finally does a good job on Linux though), to begin with (realtime signals also come to mind, then there's the realtime scheduling class and various timers).

An application written for a UNIX(R) system using only SUS features is supposed to work on all systems complying with that SUS (UNIX95 compliance for example would catch HP-UX, UnixWare, Tru64, AIX, Solaris, IRIX, ...)

> well then, who owns "Linux"? anybody?

Linux is a registered trademark of Linus Torvalds.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

UNIX problem? Unix programm runs windows 2000 CPU over 100%

Okee problems...!! What is happening: Unix server with some programms, workstations are windows 2000, the workstations work good but when you start a programm on the Unix server the CPU of the workstations go to 100% usage resulting that the system gets very slow. The programm well its running so... (2 Replies)
Discussion started by: zerocool
2 Replies

2. UNIX for Dummies Questions & Answers

Unix History Question: Why are filenames/dirnames case sentsitive in Unix?

I tried looking for the answer online and came up with only a few semi-answers as to why file and directory names are case sensitive in Unix. Right off the bat, I'll say this doesn't bother me. But I run into tons of Windows and OpenVMS admins in my day job who go batty when they have to deal... (3 Replies)
Discussion started by: deckard
3 Replies

3. UNIX for Advanced & Expert Users

missing Path(in UNIX) when i launch a job on to unix machine using windows SSh

hi i want run an unix application from a windows program/application.i am using SSH(command line version)to log on to a unix machine from windows. the application has to read a configuration file inorder to run. the configuration file .CFG is in bin in my home directory. but the application... (1 Reply)
Discussion started by: megastar
1 Replies

4. Shell Programming and Scripting

FTP script for sending a file from one unix directory to another unix server director

Hi, My local server is :/usr/abcd/ Remote server is :/Usr/host/test/ I want to send files from local unix directory(All files starting with O_999) to remote host unix directory. Can any body give me the Unix Shell script to do this. One more doubt: Shall we need to change the file... (1 Reply)
Discussion started by: raja_1234
1 Replies

5. Shell Programming and Scripting

Batch job in unix server to move the pdf file from unix to windows.

Hi Experts, I have a requirement where i need to setup a batch job which runs everymonth and move the pdf files from unix server to windows servers. Could some body provide the inputs for this. and also please provide the inputs on how to map the network dirve in the unix like that... (1 Reply)
Discussion started by: ger199901
1 Replies

6. UNIX for Dummies Questions & Answers

How does unix system administration, unix programming, unix network programming differ?

How does unix system administration, unix programming, unix network programming differ? Please help. (0 Replies)
Discussion started by: thulasidharan2k
0 Replies

7. Shell Programming and Scripting

File Transfer from Window server to UNIX and UNIX to UNIX

Dear All, Can someone help to command or program to transfer the file from windows to Unix server and from one unix server to another Unix server in secure way. I would request no samba client. (4 Replies)
Discussion started by: yadavricky
4 Replies

8. Post Here to Contact Site Administrators and Moderators

VIP Membership - The UNIX and Linux Forums - Get Your UNIX.COM Email Address Here

We work hard to make The UNIX and Linux Forums one of the best UNIX and Linux knowledge sources on the net. The site is certainly one of the top UNIX and Linux Q&A sites on the web. In order to provide certain members the best quality account services, you can now get some great extra features by... (2 Replies)
Discussion started by: Neo
2 Replies
STANDARDS(7)						     Linux Programmer's Manual						      STANDARDS(7)

NAME
standards - C and UNIX Standards DESCRIPTION
The CONFORMING TO section that appears in many manual pages identifies various standards to which the documented interface conforms. The following list briefly describes these standards. V7 Version 7, the ancestral UNIX from Bell Labs. 4.2BSD This is an implementation standard defined by the 4.2 release of the Berkeley Software Distribution, released by the University of California at Berkeley. This was the first Berkeley release that contained a TCP/IP stack and the sockets API. 4.2BSD was released in 1983. Earlier major BSD releases included 3BSD (1980), 4BSD (1980), and 4.1BSD (1981). 4.3BSD The successor to 4.2BSD, released in 1986. 4.4BSD The successor to 4.3BSD, released in 1993. This was the last major Berkeley release. System V This is an implementation standard defined by AT&T's milestone 1983 release of its commercial System V (five) release. The previous major AT&T release was System III, released in 1981. System V release 2 (SVr2) This was the next System V release, made in 1985. The SVr2 was formally described in the System V Interface Definition version 1 (SVID 1) published in 1985. System V release 3 (SVr3) This was the successor to SVr2, released in 1986. This release was formally described in the System V Interface Definition version 2 (SVID 2). System V release 4 (SVr4) This was the successor to SVr3, released in 1989. This version of System V is described in the "Programmer's Reference Manual: Operating System API (Intel processors)" (Prentice-Hall 1992, ISBN 0-13-951294-2) This release was formally described in the System V Interface Definition version 3 (SVID 3), and is considered the definitive System V release. SVID 4 System V Interface Definition version 4, issued in 1995. Available online at http://www.sco.com/developers/devspecs/ . C89 This was the first C language standard, ratified by ANSI (American National Standards Institute) in 1989 (X3.159-1989). Sometimes this is known as ANSI C, but since C99 is also an ANSI standard, this term is ambiguous. This standard was also ratified by ISO (International Standards Organization) in 1990 (ISO/IEC 9899:1990), and is thus occasionally referred to as ISO C90. C99 This revision of the C language standard was ratified by ISO in 1999 (ISO/IEC 9899:1999). Available online at http://www.open- std.org/jtc1/sc22/wg14/www/standards. POSIX.1-1990 "Portable Operating System Interface for Computing Environments". IEEE 1003.1-1990 part 1, ratified by ISO in 1990 (ISO/IEC 9945-1:1990). The term "POSIX" was coined by Richard Stallman. POSIX.2 IEEE Std 1003.2-1992, describing commands and utilities, ratified by ISO in 1993 (ISO/IEC 9945-2:1993). POSIX.1b (formerly known as POSIX.4) IEEE Std 1003.1b-1993 describing real-time facilities for portable operating systems, ratified by ISO in 1996 (ISO/IEC 9945-1:1996). POSIX.1c IEEE Std 1003.1c-1995 describing the POSIX threads interfaces. POSIX.1d IEEE Std 1003.1c-1999 describing additional real-time extensions. POSIX.1g IEEE Std 1003.1g-2000 describing networking APIs (including sockets). POSIX.1j IEEE Std 1003.1j-2000 describing advanced real-time extensions. POSIX.1-1996 A 1996 revision of POSIX.1 which incorporated POSIX.1b and POSIX.1c. XPG3 Released in 1989, this was the first significant release of the X/Open Portability Guide, produced by the X/Open Company, a multi- vendor consortium. This multivolume guide was based on the POSIX standards. XPG4 A revision of the X/Open Portability Guide, released in 1992. XPG4v2 A 1994 revision of XPG4. This is also referred to as Spec 1170, where 1170 referred to the number of interfaces defined by this standard. SUS (SUSv1) Single UNIX Specification. This was a repackaging of XPG4v2 and other X/Open standards (X/Open Curses Issue 4 version 2, X/Open Networking Service (XNS) Issue 4). Systems conforming to this standard can be branded UNIX 95. SUSv2 Single UNIX Specification version 2. Sometimes also referred to as XPG5. This standard appeared in 1997. Systems conforming to this standard can be branded UNIX 98. See also http://www.UNIX-systems.org/version2/ .) POSIX.1-2001, SUSv3 This was a 2001 revision and consolidation of the POSIX.1, POSIX.2, and SUS standards into a single document, conducted under the auspices of the Austin group (http://www.opengroup.org/austin/ .) The standard is available online at http://www.unix-sys- tems.org/version3/ , and the interfaces that it describes are also available in the Linux manual pages package under sections 1p and 3p (e.g., "man 3p open"). The standard defines two levels of conformance: POSIX conformance, which is a baseline set of interfaces required of a conforming system; and XSI Conformance, which additionally mandates a set of interfaces (the "XSI extension") which are only optional for POSIX conformance. XSI-conformant systems can be branded UNIX 03. (XSI conformance constitutes the Single UNIX Specification version 3 (SUSv3).) The POSIX.1-2001 document is broken into four parts: XBD: Definitions, terms and concepts, header file specifications. XSH: Specifications of functions (i.e., system calls and library functions in actual implementations). XCU: Specifications of commands and utilities (i.e., the area formerly described by POSIX.2). XRAT: Informative text on the other parts of the standard. POSIX.1-2001 is aligned with C99, so that all of the library functions standardized in C99 are also standardized in POSIX.1-2001. Two Technical Corrigenda (minor fixes and improvements) of the original 2001 standard have occurred: TC1 in 2003 (referred to as POSIX.1-2003), and TC2 in 2004 (referred to as POSIX.1-2004). POSIX.1-2008, SUSv4 Work on the next revision of POSIX.1/SUS was completed and ratified in 2008. The changes in this revision are not as large as those that occurred for POSIX.1-2001/SUSv3, but a number of new interfaces are added and various details of existing specifications are modified. Many of the interfaces that were optional in POSIX.1-2001 become mandatory in the 2008 revision of the standard. A few interfaces that are present in POSIX.1-2001 are marked as obsolete in POSIX.1-2008, or removed from the standard altogether. The revised standard is broken into the same four parts as POSIX.1-2001, and again there are two levels of conformance: the baseline POSIX Conformance, and XSI Conformance, which mandates an additional set of interfaces beyond those in the base specification. In general, where the CONFORMING TO section of a manual page lists POSIX.1-2001, it can be assumed that the interface also conforms to POSIX.1-2008, unless otherwise noted. Further information can be found on the Austin group web site, http://www.opengroup.org/austin/ . SEE ALSO
feature_test_macros(7), libc(7), posixoptions(7) COLOPHON
This page is part of release 3.27 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. Linux 2009-06-01 STANDARDS(7)
All times are GMT -4. The time now is 11:37 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy