Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!indri!dogie.macc.wisc.edu!uwvax!tank!cs_bob@gsbacd.uchicago.edu
From: cs_bob@gsbacd.uchicago.edu
Newsgroups: comp.databases
Subject: Re: Ingres User's Association Meeting
Message-ID: <3082@tank.uchicago.edu>
Date: 5 May 89 17:45:43 GMT
Sender: news@tank.uchicago.edu
Distribution: usa
Organization: University of Chicago Graduate School of Business
Lines: 33



 
In article <506@daitc.daitc.mil>, jkrueger@daitc.daitc.mil (Jonathan Krueger) writes...
 
>In article <3044@tank.uchicago.edu>, cs_bob@gsbacd writes:
>>in New Orleans last week. Among the lowlights:
>>
>>1) During their Monday morning marketing hype, several exexcutive [sic]
>>types ballyhooed the large number of various UNIX flavors they run on.
>>No one mentioned the fact that version 6 Ingres no longer works under
>>BSD Unix.
> 
>Were we at the same conference?  At the conference that *I* attended a
>decision was reached and announced that INGRES front ends and
>INGRES/Net will be supported on BSD Unix on VAXes.  Front and back
>ends will be supported on BSD derived systems such as Ultrix and
>SunOS.
> 

As far as I'm concerned, if the back end doesn't run on the machine, 
Ingres doesn't run on the machine. Ingres is supposedly an RDBMS. If
they can't get you the database engine, I think it's fair to say that
they can't give you an RDBMS.

The annoucement you refer to was definitely not made during the Monday
morning session, nor was the decision 'reached and announced' at the
conference. We've known about it for a long time - the problem is that
BSD doesn't support shared memory, and Ingres 6.x requires it. (As an
aside, someone, I think Marty Sprinzen, made a comment to the effect
'so far, all of our bugs have been coding errors, not architecture errors.'
This seems to be an architecture error if there ever was one. Does anyone
else know of another multi-platform DBMS system that REQUIRES shared memory?)