|
|
1.1 root 1: I N G R E S / 8
2:
3: This version of INGRES runs on VAX hardware under VM/UNIX, fourth
4: release. It has, at various times, also been running under VM/UNIX,
5: third release, and version six on a PDP-11/70. Quite probably it
6: would adapt quite easily to a version seven system on a PDP-11 also.
7: The chance of ever getting it running on a non-I/D PDP-11 machine
8: is very small, although theoretically possible.
9:
10: INSTALLATION
11:
12: There exist binaries that are runnable, so no recompilation should
13: be necessary. To prepare the system for running, perform the
14: following steps:
15:
16: 1. Create a user ``ingres'' in /etc/passwd. This user must have
17: the root of the INGRES subtree as its home directory.
18:
19: 2. Log in as ingres.
20:
21: 3. Set up the list of valid INGRES users by typing:
22: ~ingres/bin/usersetup
23: This sets up everyone on your system as an INGRES user.
24:
25: For more details, read the ``setup instructions'':
26:
27: chdir ~ingres/doc/other
28: nroff howto_setup.nr
29:
30: CONSULTING & INFORMATION.
31:
32: This software is unsupported, public domain software. Although we
33: are interested in feedback, it is impossible for us to make any
34: commitment to support in a research environment. However, several
35: companies have already expressed interest in selling and supporting
36: this code -- I'm sure one of them would be more than happy to help
37: you out.
38:
39: If you do want to talk to us, electronic mail is strongly prefered.
40: We can be reached via Arpanet as "ingres@Berkeley" and via UUCP net as
41: "ucbvax!ingres". Please DO NOT contact us for availability information,
42: as the INGRES distribution has been merged into the VM/UNIX distri-
43: bution; we will be able to do nothing except refer you to them. The
44: contact for VM/UNIX is the CSRG office, (415) 642-7780.
45:
46: THE SYSTEM ROAD MAP
47:
48: Following is a brief description of the directory structure. In
49: this description, and in all other READ_ME files, "..." represents
50: the root of the INGRES subtree.
51:
52: bin
53: Holds system binaries. This is actually an internal
54: directory (perhaps we should use lib?) (but lib is
55: already used) and should in general not be included
56: in search paths. The only things that will live here
57: that are intended to be executed directory are various
58: system support routines, "for madmen only".
59: data
60: This is the root of the database subtree. It has a
61: single entry, a directory called "base". That directory
62: in turn has a directory for each database. The two
63: layer scheme is required to insure protection -- data
64: is mode 700 and base is mode 777. Since the database
65: directories themselves are mode 777, it is critical to
66: have data unreadable by mortals, lest your sensitive
67: data disappear in the night.
68: demo
69: The source for the demo database exists in this directory.
70: Basically, it is just a bunch of files that copy uses.
71: doc
72: System documentation exists here. See the READ_ME file
73: in this directory for a more detailed road map.
74: files
75: This is an approximate equivalent to /etc. It includes
76: a bunch of files that are CRITICAL for the system to run.
77: See the READ_ME file in this directory for more info.
78: lib
79: This contains libraries used for recompilation, and can
80: be removed if you are not interested in recompiling the
81: system.
82: source
83: The source code of the system, of course.
84: version
85: A version code. Not critical, but you should probably
86: leave it laying around on general principles.
87:
88: bin7
89: Copies of the version 7 binaries, they are there so
90: the "ingconv" program can convert binaries. It should
91: probably be removed once all the databases have been
92: converted.
93:
94: All of this can live anywhere in your filesystem, but there MUST
95: be a user called "ingres" whose home directory points to it. All
96: of this code MUST be owned by ingres.
97:
98: RECOMPILATION
99:
100: Recompilation is described in source/READ_ME.
101:
102: CONVERSION
103:
104: If you have been running ingres version 7, and want to use your
105: databases under version 8, you will need to run the program
106: ingconv on each database that you want to convert. The useage
107: is just "ingconv database".
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.