AIX compliance?

[jsalter at ibmpa.awdpa.ibm.com]

In article <1991Apr12.141503.8691 at ux1.cso.uiuc.edu> allender at cs.uiuc.edu (Mark Allender) writes:
>In article <977 at vax.cs.athabascau.ca>, willis at cs.athabascau.ca (Tony
>Willis) writes:
>|> Can AIX be considered either Sys V or BSD Unix compliant? I gather
>|> that its really neither, and that IBM has decided to essentially
>|> develop its own independent version of Unix, but I'd appreciate
>|> comments from those who are more in the know than I am.
>|> Tony Willis >|> twillis at drao.nrc.ca

>As far as I know, AIX is neither BSD or SYSV, and is both BSD and SYSV.  I have
>installed applications where I have had to define BSD, and others where I have
>had to define SYSV, and still others where there was a #define RS6000.

Actually, AIX v3 has it's roots in System V, and passes the conformance
test for SVID Issue 2 (I think this means Sys V Rel. 3.2, correct me if I'm
wrong).  Because of the industry standards that came out at the time, the
order of importance could be considered:

	POSIX (1003.1) > X/Open Issue 3 (XPG3) > ANSI-C > System V > BSD

(with some others like AIX RT, ... thrown in, too).

Because of the amount of interest for BSD programs, much of the functionality
for BSD was integrated into the system.  The files:

	/usr/lpp/bos/bsdport	- Porting BSD programs to AIX Version 3
and
	/usr/lpp/bos/bsdadm	- BSD System Administration for AIX Version 3

If these don't explain your problems, please post to let us know.  By the way,
the proper define for AIX on the 6000 is _IBMR2 and _AIX (defined in the
compiler's setup file: /etc/xlc.cfg).  RS6000 is probably not the thing to
use.

>-Mark Allender
>-allender at cs.uiuc.edu

jim/jsalter  IBM PSP, Palo Alto  T465/(415)855-4427  VNET: JSALTER at AUSVMQ
Internet: jsalter at slo.awdpa.ibm.com         UUCP: ..!uunet!ibmsupt!jsalter 
"IBM part #23521, aka Lt. Commander Data"    The stuff above is on my own.