Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA5765 ; Fri, 01 Jan 93 01:55:09 EST Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!sdd.hp.com!cs.utexas.edu!natinst.com!hrd769.brooks.af.mil!hrd769.brooks.af.mil!not-for-mail From: news@hrd769.brooks.af.mil (InterNet News) Newsgroups: comp.unix.bsd Subject: Re: iBCS2 / SCO 3.2.4 Date: 30 Dec 1992 16:04:44 -0600 Organization: Armstrong Lab MIS, Brooks AFB TX Lines: 32 Message-ID: <1ht6dsINNo3g@hrd769.brooks.af.mil> References: <1992Dec30.154921.23024@cognos.com> NNTP-Posting-Host: hrd769.brooks.af.mil In article <1992Dec30.154921.23024@cognos.com> nigelc@cognos.com (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. > I was wondering if any of the 386bsd developers had ever heard of the iBCS2 definition, and is it reasonable to try to get 386bsd compliant with it. If this 'standard' is reasonable, it would seem a good thing to be binary compatible with somebody, n'est pas? Just another random thought, TSgt Dave Burgess Two other quick notes. I am using inn/trn to write/deliver this message (which the observant of you will have noticed is probably addressed from 'news@here'). I broke this about three weeks ago and cannot figure out where I broke it. I think I make something setuid() when I shouldn't have. Any good ideas? I have also been helping several folks with EISA SCSI controllers. The ones that have an ISA operating mode seem to work with the wd0 boot drivers, but I am learning all kinds of things about these beasties. Is anyone interested in seeing a short summary of the steps and pitfalls? E-Mail me (please) if you are interested. I will be glad to write/post such a summary if there is interest... TTFN Dave