Please read the file setup.doc on how to install and setup INGRES. THE SYSTEM ROAD MAP Following is a brief description of the directory structure. In this description, and in all other READ_ME files, "..." represents the root of the INGRES subtree. bin Holds system binaries. This is actually an internal directory (perhaps we should use lib?) (but lib is already used) and should in general not be included in search paths. The only things that will live here that are intended to be executed directory are various system support routines, "for madmen only". data This is the root of the database subtree. It has a single entry, a directory called "base". That directory in turn has a directory for each database. The two layer scheme is required to insure protection -- data is mode 700 and base is mode 777. Since the database directories themselves are mode 777, it is critical to have data unreadable by mortals, lest your sensitive data disappear in the night. demo The source for the demo database exists in this directory. Basically, it is just a bunch of files that copy uses. doc System documentation exists here. See the READ_ME file in this directory for a more detailed road map. files This is an approximate equivalent to /etc. It includes a bunch of files that are CRITICAL for the system to run. See the READ_ME file in this directory for more info. lib This contains libraries used for recompilation, and can be removed if you are not interested in recompiling the system. source The source code of the system, of course. version A version code. Not critical, but you should probably leave it laying around on general principles. All of this can live anywhere in your filesystem, but there MUST be a user called "ingres" whose home directory points to it. All of this code MUST be owned by ingres. RECOMPILATION Recompilation is described in source/READ_ME. CONVERSION If you have been running ingres version 7, and want to use your databases under version 8, you will need to run the program ingconv on each database that you want to convert. The useage is just "ingconv database". _________ Changes for version 8.9 This later version of version 8 ingres has many more portability fixs and seems as solid on a Sun as when last compiled on a VAX. Common problems/bugs: header files missing - We do not believe any header files are missing. There are, however, header files in the ctlmod directory which are reached properly only when make properly calls cc with -I../ctlmod. The Makefiles in this distribution are believed to work properly. The version 7 to version 8 convert program may need the version 7 ksort7 binary in the version 8 bin directory. The locking system has been slitely cleaned up. Sysmod now works when ingreslock is running. However, no concurency checking is done on ordered relations. Access methods for ordered relations and the locking system both need to be reworked. ingconv doesn't work right unless run by the appropreate dba of each database. Rumor has it that some versions of Ultrix are not consistant with 4.2 BSD regarding fstat on a socket which will cause database corruption if the lockdriver is run. This is unconfirmed. Ordered relations are SLOW and NOT locked.