Mercurial > hg > Members > kono > nitros9-code

comparison docs/nitros9guide/chap6.chapter @ 146:88ae6ed51be6

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
More splitups.
author roug
date Sun, 07 Jul 2002 09:54:04 +0000
parents
children 2e21fb7216af
comparison
equal deleted inserted replaced
145:099333bc912e 146:88ae6ed51be6
1 <chapter>
2 <title>Use of the System Disk</title>
3 <para>
4 Disk-based OS-9 systems use a system disk to load many parts of
5 the operating system during the system startup and to provide files
6 frequently used during normal system operations. Therefore, the
7 system disk is generally kept in disk drive zero (&quot;/D0&quot;) when the
8 system is running.
9 </para>
10 <para>
11 Two files used during the system startup operation, &quot;OS9Boot&quot; and
12 &quot;startup&quot; <emphasis>must</emphasis>
13 reside in the system disk's root directory. Other
14 files are organized into three directories: CMDS (commands), DEFS
15 (system-wide definitions), and SYS (other system files). Other files
16 and directories created by the system manager and/or users may also
17 reside on the system disk. These frequently include each user s
18 initial data directory.
19 </para>
20
21 <section>
22 <title>The OS9BOOT File</title>
23
24 <para>
25 The file called &quot;OS9Boot&quot; loaded into RAM memory by the
26 &quot;bootstrap&quot; routine located in the OS-9 firmware. It includes file
27 managers, device drivers and descriptors, and any other modules
28 which are permanently resident in memory. A typical Microware OS-9
29 distribution disk's &quot;OS9Boot&quot; file contains the following modules:
30 </para>
31 <informaltable frame="none">
32 <tgroup cols="2">
33 <colspec colwidth="1.5in">
34 <colspec colwidth="3.5in">
35 <tbody>
36 <row>
37 <entry>IOMAN</entry>
38 <entry>OS-9 Input/Output Manager</entry>
39 </row>
40 <row>
41 <entry>RBF</entry>
42 <entry>Random Block (disk) File Manager</entry>
43 </row>
44 <row>
45 <entry>SCF</entry>
46 <entry>Sequential Character (terminal) File Manager</entry>
47 </row>
48 <row>
49 <entry>Pipeman</entry>
50 <entry>Pipeline File Manager</entry>
51 </row>
52 <row>
53 <entry>Piper</entry>
54 <entry>Pipeline Driver</entry>
55 </row>
56 <row>
57 <entry>Pipe</entry>
58 <entry>Pipeline Device Descriptor</entry>
59 </row>
60 <row>
61 <entry>KBDVID</entry>
62 <entry>Keyboard/video/Graphics Device Driver</entry>
63 </row>
64 <row>
65 <entry>PRINTER</entry>
66 <entry>Printer Device Driver</entry>
67 </row>
68 <row>
69 <entry>DDISK</entry>
70 <entry>Disk Driver</entry>
71 </row>
72 <row>
73 <entry>D0, D1</entry>
74 <entry>Disk Device Descriptor</entry>
75 </row>
76 <row>
77 <entry>TERM</entry>
78 <entry>Terminal Device Descriptor</entry>
79 </row>
80 <row>
81 <entry>P</entry>
82 <entry>Printer Device Descriptor</entry>
83 </row>
84 <row>
85 <entry>CLOCK</entry>
86 <entry>Real-Time Clock Module</entry>
87 </row>
88 <row>
89 <entry>SYSGO</entry>
90 <entry>System Startup Process</entry>
91 </row>
92 </tbody>
93 </tgroup>
94 </informaltable>
95
96 <para>
97 Users may create new bootstrap files which may include additional
98 modules (see &quot;OS9Gen&quot; command). Any module loaded as part of the
99 bootstrap cannot be unlinked and is stored in memory with a minimum
100 of fragmentation. It may be advantageous to include in the OS9Boot
101 file any module used constantly during normal system operation.
102 This can be done with the OS9GEN command.
103 </para>
104 </section>
105
106 <section>
107 <title>The SYS Directory</title>
108
109 <para>
110 The directory &quot;/d0/SYS&quot; contains two important files:
111 </para>
112 <informaltable frame="none">
113 <tgroup cols="2">
114 <colspec colwidth="1in">
115 <colspec colwidth="4in">
116 <tbody>
117 <row>
118 <entry>password</entry>
119 <entry>the system password file (see &quot;login&quot; command)</entry>
120 </row>
121 <row>
122 <entry>errmsg</entry>
123 <entry>the error message file (see 4.7)</entry>
124 </row>
125 </tbody>
126 </tgroup>
127 </informaltable>
128 <para>
129 These files (and the SYS directory itself) are not absolutely
130 required to boot OS-9, they are needed if &quot;login&quot;, &quot;tsmon&quot;, or
131 &quot;printerr&quot; will be used. Users may add other system-wide files of
132 similar nature if desired.
133 </para>
134 </section>
135
136 <section>
137 <title>The Startup File</title>
138
139 <para>
140 The file &quot;/d0/startup&quot; is a shell procedure file (see 4.6) which
141 is automatically processed immediately after system startup. The
142 user may include in &quot;startup&quot; any legal shell command line. Often
143 this will include &quot;setime&quot; to start the system clock. If this file
144 is not present the system will still start correctly but the user
145 must run the SETIME command manually.
146 </para>
147 </section>
148
149 <section>
150 <title>The CMDS Directory</title>
151
152 <para>
153 The directory &quot;/d0/CMDS&quot; is the system-wide command object code
154 directory, which is normally shared by all users as their working
155 execution directory (see 3.7). If &quot;shell&quot; is not part of the
156 &quot;OS9Boot&quot; file, it must be present in this directory. The system
157 startup process &quot;sysgo&quot; makes CMDS the initial execution directory.
158 </para>
159 </section>
160
161 <section>
162 <title>The DEFS Directory</title>
163
164 <para>
165 The directory &quot;/d0/DEFS&quot; is a directory that contains assembly
166 language source code files which contain common system-wide symbolic
167 definitions, and are normally included in assembly language programs
168 by means of the OS-9 Assembler &quot;use&quot; directive. The presence and
169 use of this directory is optional, but highly recommended for any
170 system used for assembly language programs. The files commonly
171 contained in this directory are:
172 </para>
173 <informaltable frame="none">
174 <tgroup cols="2">
175 <colspec colwidth="1in">
176 <colspec colwidth="4in">
177 <tbody>
178 <row>
179 <entry>OS9Defs</entry>
180 <entry>main system-wide definition file</entry>
181 </row>
182 <row>
183 <entry>RBFDefs</entry>
184 <entry>RBF file manager definition file</entry>
185 </row>
186 <row>
187 <entry>SCFDefs</entry>
188 <entry>SCF file manager definition file</entry>
189 </row>
190 <row>
191 <entry>Systype</entry>
192 <entry>System types definition file</entry>
193 </row>
194 </tbody>
195 </tgroup>
196 </informaltable>
197
198 </section>
199
200 <section>
201 <title>Changing System Disks</title>
202
203 <para>
204 The system disk is not usually removed while the system is running, especially
205 on multiuser systems. If it is, the &quot;chx&quot; and
206 &quot;chd&quot; (if the working data directory was on the system disk)
207 commands should be executed to reset the working directory pointers
208 because the directories may be at different addresses on the new
209 disk, for example:
210 </para>
211
212 <screen>
213 chx /d0/cmds
214 chd /d0
215 </screen>
216
217 <para>
218 In general, it is unwise to remove a disk and replace it with
219 another if any paths are open to files resident on the disk. It is
220 <emphasis>dangerous</emphasis> to exchange <emphasis>any</emphasis>
221 disk if any files on it are open in WRITE or UPDATE modes.
222 </para>
223
224
225 </section>
226
227 <section>
228 <title>Making New System Disks</title>
229
230 <para>
231 To make a system disk, the following steps must be performed:
232
233 <orderedlist numeration="arabic">
234 <listitem><para>
235 The new disk must be formatted.
236 </para></listitem>
237
238 <listitem><para>
239 The &quot;OS9Boot&quot; file must be created and linked by the &quot;OS9Gen&quot; or
240 &quot;Cobbler&quot; commands.
241 </para></listitem>
242
243 <listitem><para>
244 The &quot;startup&quot; file must be created or copied.
245 </para></listitem>
246
247 <listitem><para>
248 The CMDS and SYS directories and the files they contain must be
249 copied.
250 </para></listitem>
251 </orderedlist>
252
253 Steps 2 through 4 may be performed manually, or automatically by any
254 of the following methods:
255 <orderedlist numeration="arabic">
256 <listitem><para>
257 By a shell procedure file created by the user.
258 </para></listitem>
259
260 <listitem><para>
261 By a shell procedure file generated by the &quot;dsave&quot; command
262 </para></listitem>
263
264 <listitem><para>
265 By the &quot;backup&quot; command
266 </para></listitem>
267 </orderedlist>
268 </para>
269 </section>
270 </chapter>