|
|
1.1 root 1:
2:
3: install Command install
4:
5:
6:
7:
8: Install COHERENT update
9:
10: /eettcc/iinnssttaallll _i_d _d_e_v_i_c_e _n_d_i_s_k_s
11:
12: install installs an update of the COHERENT system onto your hard
13: disk. id identifies the update to be installed. device is the
14: device from which the update disks will be read. ndisks is the
15: number of disks that comprise the update.
16:
17: ***** Example *****
18:
19: The following installs COHERENT update coh.301, which consists of
20: one disk, from a high-density 5.25-inch floppy drive:
21:
22:
23: /etc/install coh.301 /dev/fha0 1
24:
25:
26: ***** See Also *****
27:
28: commands
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64: COHERENT Lexicon Page 1
65:
66:
67:
68:
69: install Technical Information install
70:
71:
72:
73:
74: Building distribution kits for use by install
75:
76:
77: /etc/install provides a standardized mechanism to install
78: upgrades and add-on software to the COHERENT system.
79:
80: install is invoked with a command line of the form:
81:
82:
83: /eettcc/iinnssttaallll _i_d _d_e_v_i_c_e _n_d_i_s_k_s
84:
85:
86: where id specifies the update or add-on package to be installed,
87: device is the ``mountable'' block device from which the update or
88: add-on package will be installed, and ndisks specifies the number
89: of diskettes in the distribution.
90:
91: The id field should be formed from the set of upper- and lower-
92: case letters, as well as digits, the period (.), and the under-
93: score (_) character. Its length cannot exceed nine characters.
94: Field device should be selected from the standard block-special
95: floppy-disk devices.
96:
97: ***** Distribution Details *****
98:
99: Distributions usable by install consist of a set of mountable
100: floppy disks, each containing a file system created by mkfs.
101: This allows the diskettes to be independent of each other and
102: also allows the user to insert the diskettes in any order. in-
103: stall records the fact that it has read a given diskette from the
104: distribution, thus preventing the user from attempting to read a
105: given diskette more than once during an installation session.
106:
107: Diskettes should be built using mkfs, with possible input being
108: generated by unmkfs. Each diskette in the distribution must con-
109: tain a file of the form
110:
111:
112: /_i_d._s_e_q_u_e_n_c_e
113:
114:
115: in the root directory. Here, id must match the aforementioned
116: field of the same name. The sequence part of the file name in-
117: dicates which diskette in the distribution this diskette is, from
118: one through the total number of diskettes.
119:
120: install uses the command cpdir to copy each of the distribution
121: diskettes to directory / on the current system. Therefore, all
122: diskettes should be ``root based'' (i.e., full path names should
123: be used). Because install is run by the superuser, cpdir preser-
124: ves the date and time for each file, and preserves ownership and
125: modes. To keep file ownership consistent with COHERENT conven-
126: tions, make files that are neither setuid nor setgid owned by
127: user bin and group bin. Directories found on the distribution
128:
129:
130: COHERENT Lexicon Page 1
131:
132:
133:
134:
135: install Technical Information install
136:
137:
138:
139: diskettes will be created on the target file system, as needed.
140: Be careful when choosing the ownership and mode of directories
141: because your system's security could inadvertently be com-
142: promised.
143:
144: ***** Postprocessing *****
145:
146: After all diskettes in a distribution have been successfully
147: copied, install checks for the existence of a file of the form
148:
149:
150: /conf/_i_d.post
151:
152:
153: where id matches the id field found on the install command line.
154: If found, install executes this file to allow special
155: ``postprocessing,'' such as installing additional manual pages or
156: performing installation-specific commands.
157:
158: Before you complete your postprocessing, you should remove any id
159: files of the following form from the target system:
160:
161:
162: /conf/_i_d.post
163: /_i_d._s_e_q_u_e_n_c_e
164:
165:
166: ***** Adding Manual-Page Entries *****
167:
168: As part of building a distribution, you will usually need to
169: generate pre-processed or ``cooked'' manual-page entries for dis-
170: tribution with your upgrade or add-on package. These should
171: reside in subdirectories of /usr/man, with the name of the sub-
172: directory being specific to your product. This naming convention
173: avoids name-space collisions, should multiple applications use
174: the same name for a manual-page entry.
175:
176: If you install new or additional manual pages, you must update
177: the index file used by the man command to locate manual entries.
178: File /usr/man/man.index on the target file system contains index
179: entries for all manual pages on the system. As part of
180: postprocessing, you will generally need to append index informa-
181: tion for your manual pages to the end of the existing index file.
182: In addition, file /usr/man/man.help contains the man command's
183: help message. This includes a list of valid topics and some ex-
184: planatory text. You should also append to this file a brief list
185: of the manual page entries that you have added. For further in-
186: formation on manual pages, see the Lexicon entry for the command
187: man.
188:
189: ***** Logging *****
190:
191: install logs all partial as well as completed installations in
192: file /etc/install.log. This information includes date/time
193: stamps and the command line arguments to install.
194:
195:
196: COHERENT Lexicon Page 2
197:
198:
199:
200:
201: install Technical Information install
202:
203:
204:
205:
206: ***** Files *****
207:
208: /etc/install.log
209:
210: ***** See Also *****
211:
212: install (command), man, mkfs, technical information, unmkfs
213:
214:
215:
216:
217:
218:
219:
220:
221:
222:
223:
224:
225:
226:
227:
228:
229:
230:
231:
232:
233:
234:
235:
236:
237:
238:
239:
240:
241:
242:
243:
244:
245:
246:
247:
248:
249:
250:
251:
252:
253:
254:
255:
256:
257:
258:
259:
260:
261:
262: COHERENT Lexicon Page 3
263:
264:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.