Use of the System Disk
Disk-based NitrOS-9 systems use a system disk to load many parts of
the operating system during the system startup and to provide files
frequently used during normal system operations. Therefore, the
system disk is generally kept in disk drive zero ("/D0") when the
system is running.
Two files used during the system startup operation, OS9Boot and
startup must
reside in the system disk's root directory. Other
files are organized into three directories:
CMDS (commands),
DEFS (system-wide definitions),
and SYS (other system files). Other files
and directories created by the system manager and/or users may also
reside on the system disk. These frequently include each user s
initial data directory.
The OS9Boot File
The file called OS9Boot loaded into RAM memory by the
"bootstrap" routine located in the NitrOS-9 firmware. It includes file
managers, device drivers and descriptors, and any other modules
which are permanently resident in memory. The NitrOS-9
distribution disk's OS9Boot file contains the following modules:
KernelP2
NitrOS-9 Kernel, Part 2
IOMan
NitrOS-9 Input/Output Manager
Init
Initialization Data Module
RBF
Random Block (disk) File Manager
SCF
Sequential Character (terminal) File Manager
PipeMan
Pipe File Manager
Piper
Pipe Driver
Pipe
Pipe Device Descriptor
CC3IO
CoCo 3 Keyboard/Video Device Driver
WindInt
CoCo 3 Graphics Co-Module
VDGInt
CoCo 2 Compatible Graphics Co-Module
Term
Terminal Device Descriptor
CC3Disk
CoCo 3 Disk Driver
DD, D0, D1
Disk Device Descriptors
Printer
Printer Device Driver
p
Printer Device Descriptor
Clock
Real-Time Clock Module
Clock2
Second Part of Real-Time Clock Module
SysGo
System Startup Process
Users may create new bootstrap files which may include additional
modules (see OS9Gen command). Any module loaded as part of the
bootstrap cannot be unlinked and is stored in memory with a minimum
of fragmentation. It may be advantageous to include in the OS9Boot
file any module used constantly during normal system operation.
This can be done with the OS9GEN command.
The SYS Directory
The directory /d0/SYS contains several important files:
password
the system password file (see login command)
errmsg
the error message file
helpmsg
the help database file
These files (and the SYS directory itself) are not absolutely
required to boot NitrOS-9, they are needed if login, tsmon, or
help will be used. Users may add other system-wide files of
similar nature if desired.
The Startup File
The file startup in the root directory is a shell procedure file which
is automatically processed immediately after system startup. The
user may include in startup any legal shell command line. Often
this will include setime to start the system clock. If this file
is not present the system will still start correctly but the user
must run the SETIME command manually.
The CMDS Directory
The directory CMDS is the system-wide command object code
directory, which is normally shared by all users as their working
execution directory. If shell is not part of the
OS9Boot file (and it shouldn't be in a Level 2 system), it must be present in this directory. The system
startup process "sysgo" makes CMDS the initial execution directory.
The DEFS Directory
The directory DEFS is a directory that contains assembly
language source code files which contain common system-wide symbolic
definitions, and are normally included in assembly language programs
by means of the NitrOS-9 Assembler "use" directive. The presence and
use of this directory is optional, but highly recommended for any
system used for assembly language programs. The files commonly
contained in this directory are:
OS9Defs
main system-wide definition file
RBFDefs
RBF file manager definition file
SCFDefs
SCF file manager definition file
Systype
System types definition file
Changing System Disks
The system disk is not usually removed while the system is running, especially
on multiuser systems. If it is, the chx and
chd (if the working data directory was on the system disk)
commands should be executed to reset the working directory pointers
because the directories may be at different addresses on the new
disk, for example:
chx /d0/cmds
chd /d0
In general, it is unwise to remove a disk and replace it with
another if any paths are open to files resident on the disk. It is
dangerous to exchange any
disk if any files on it are open in WRITE or UPDATE modes.
Making New System Disks
To make a system disk, the following steps must be performed:
The new disk must be formatted.
The OS9Boot file must be created and linked by the OS9Gen or
Cobbler commands.
The startup file must be created or copied.
The CMDS and
SYS directories and the files they contain must be
copied.
For Level 2, the sysgo file in the root directory must be
copied.
Steps 2 through 5 may be performed manually, or automatically by any
of the following methods:
By a shell procedure file created by the user.
By a shell procedure file generated by the dsave command
By the backup command