There are several circumstances under which a boot can occur
after the system is up and running:
You explicitly request a reboot
following the installation of new hardware or software,
or to correct a problem.
This is done by executing the
command or the
command, or by pressing the
<Ctrl>, <Alt>, and <Del>
In these cases, all system activity is stopped
(all processes are killed, and so on).
The system checks to see whether a new
needs to be configured,
and, if so, configures one.
Then, the system unmounts all filesystems and boots
The system comes up in the state defined by the
The computer crashes and automatically reboots.
In this case, the sequence of events is the same as
described for the first scenario.
``Starting (rebooting) your system''
for more details on rebooting.
Prior to UNIX® System V Release 4,
the programs and data files needed during booting
resided in the root filesystem,
and it was
assumed that a System V (s5) filesystem
was defined on the root slice.
With UNIX System V Release 4 and later releases,
a file-system-independent boot procedure
is implemented through the use of
the boot filesystem (bfs),
and the boot procedure no longer depends on
the filesystem type of the root filesystem.
Where the boot programs reside
Understanding the boot process
© 2005 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 - 02 June 2005