Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA5780 ; Fri, 01 Jan 93 01:55:35 EST Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!uunet!gatech!destroyer!cs.ubc.ca!uw-beaver!newsfeed.rice.edu!rice!news.Rice.edu!rich From: rich@Rice.edu (& Murphey) Subject: Re: iBCS2 / SCO 3.2.4 In-Reply-To: news@hrd769.brooks.af.mil's message of 30 Dec 1992 16:04:44 -0600 Message-ID: <RICH.92Dec30224113@superego.Rice.edu> Sender: news@rice.edu (News) Reply-To: Rich@rice.edu Organization: Department of Electrical and Computer Engineering, Rice University References: <1992Dec30.154921.23024@cognos.com> <1ht6dsINNo3g@hrd769.brooks.af.mil> Date: Thu, 31 Dec 1992 04:41:13 GMT Lines: 21 Dave> In article <1992Dec30.154921.23024@cognos.com> nigelc@cognos.com Dave> (Nigel Campbell) originally posted in comp.unix.misc: >This follows a recent post looking for a list of vendors who are >'binary' compatible with SCO UNIX (I assume 3.2.4). Is there >a list somewhere of these vendors and commercial software known >to run/not run on systems other than SCO. How does one certify >adherence to the iBCS2 definition. What is it. > Dave> I was wondering if any of the 386bsd developers had ever heard of the iBCS2 Dave> definition, and is it reasonable to try to get 386bsd compliant with it. If Dave> this 'standard' is reasonable, it would seem a good thing to be binary Dave> compatible with somebody, n'est pas? Lynne Jolitz posted a bibliography a few days ago in which she suggested we use '"The Intel 386 Architecture and System V BCS" for an understanding of defined interfaces.' Intel's publishing/sales dept (1-800-548-4724) says it isn't available yet. They do have a generic "386 BCS Spec 2" that Lynne suggested would not be as useful as the System V BCS specific book. Rich