Boot PROM 

1. The PROM displays system identification information and then runs self-test diagnostics to verify the system's hardware and memory. 

2. Then, the PROM loads the primary boot program, bootblk, whose purpose is to load the secondary boot program (that is located in the ufs file system) from the default boot device.

Boot Programs 

3. The bootblk program finds and executes the secondary boot program, ufsboot, and loads it into memory.

4. After the ufsboot program is loaded, the ufsboot program loads the kernel.

Kernel Initialization 

5. The kernel initializes itself and begins loading modules by using ufsboot to read the files. When the kernel has loaded enough modules to mount the root (/) file system, the kernel unmaps the ufsboot program and continues, using its own resources.

6. The kernel creates a user process and starts the /sbin/init process, which starts other processes by reading the /etc/inittab file.

init

7. The /sbin/init process starts the run control (rc) scripts, which execute a series of other scripts. These scripts (/sbin/rc*) check and mount file systems, start various processes, and perform system maintenance tasks.

Primary Boot Subsystem 

This menu appears if the disk you are booting from contains multiple operating environments, including the Solaris operating environment. 

Secondary Boot Subsystem 

This menu appears each time you boot the Solaris release. The Solaris release is booted automatically unless you choose to run the Solaris Device Configuration Assistant by interrupting the autoboot process. 

Solaris Device Configuration Assistant/Boot Diskette 

There are two ways to access the Solaris Device Configuration Assistant menus:  

1. Use the Solaris Device Configuration Assistant boot diskette or the Solaris installation CD (on systems that can boot from the CD-ROM drive) to boot the system.

2. Interrupt the autoboot process when you boot the Solaris software from an installed disk.

Current Boot Parameters Menu 

This menu appears when you boot the Solaris release from the disk, CD-ROM, or the network. The menu presents a list of boot options. 

Solaris Device Configuration Assistant

The Solaris(TM) (Intel Platform Edition) Device Configuration Assistant
scans to identify system hardware, lists identified devices, and can
boot the Solaris software from a specified device. This program must be
used to install the Solaris operating environment, add a driver,
or change the hardware on the system.
 
> To perform a full scan to identify all system hardware, choose Continue.
 
> To diagnose possible full scan failures, choose Specific Scan.
 
> To add new or updated device drivers, choose Add Driver.

About navigation...
    - The mouse cannot be used.
    - If the keyboard does not have function keys or they do not respond, 
      press ESC. The legend at the bottom of the screen will change to 
      show the ESC keys to use for navigation.
    - The F2 key performs the default action.

F2_Continue		F3_Specific Scan		F4_Add Driver		F6_Help

Bus Enumeration

Determining bus types and gathering hardware configuration data ...

Please wait ...

Scanning Devices

The system is being scanned to identify system hardware.

If the scanning stalls, press the system's reset button. When the
system reboots, choose Specific Scan or Help.


Scanning: Floppy disk controller

#######################
|      |        |         |         |         |
0	 		 20       40        60	       80       100

Please wait ...

Identified Devices

The following devices have been identified on this system. To identify
devices not on this list or to modify device characteristics, such as
keyboard configuration, choose Device Tasks. Platform types may be
included in this list.

ISA: Floppy disk controller
	ISA: Motherboard
	ISA: PnP bios: 16550-compatible serial controller
	ISA: PnP bios: 16550-compatible serial controller
	ISA: PnP bios: Mouse controller
	ISA: PnP bios: Parallel port
	ISA: System keyboard (US-English)
	PCI: Bus Mastering IDE controller
	PCI: Universal Serial Bus
	PCI: VGA compatible display adapter

F2_Continue   F3_Back   F4_Device Tasks   F6_Help

Boot Solaris
Select one of the identified devices to boot the Solaris kernel and
choose Continue.

To perform optional features, such as modifying the autoboot and property
settings, choose Boot Tasks.

An asterisk (*) indicates the current default boot device.

> To make a selection use the arrow keys, and press Enter to mark it [X].

[X]  DISK: (*) Target 0:QUANTUM  FIREBALL1280A
on Bus Mastering IDE controller on Board PCI at Dev 7, Func 1
[ ]  DISK: Target 1:ST5660A
on Bus Mastering IDE controller on Board PCI at Dev 7, Func 1
[ ]  DISK: Target 0:Maxtor 9 0680D4
	on Bus Mastering IDE controller on Board PCI at Dev 7, Func 1
[ ]  CD  : Target 1:TOSHIBA  CD-ROM XM-5602B  1546
	on Bus Mastering IDE controller on Board PCI at Dev 7, Func 1

F2_Continue   F3_Back   F4_Boot Tasks   F6_Help

                     <<< Current Boot Parameters >>>
Boot path: /pci@0,0/pci-ide@7,1/ide@0/cmdk@0,0:a
Boot args: 
Type    b [file-name] [boot-flags] <ENTER>       to boot with options
or      i <ENTER>                                to enter boot interpreter
or      <ENTER>                                  to boot with defaults
 
 
                     <<< timeout in 5 seconds >>>
 
Select (b)oot or (i)nterpreter: 

BIOS 

1. When the system is turned on, the BIOS runs self-test diagnostics to verify the system's hardware and memory. The system begins to boot automatically if no errors are found. If errors are found, error messages are displayed that describe recovery options. 

The BIOS of additional hardware devices are run at this time. 

2. The BIOS boot program tries to read the first physical sector from the boot device. This first disk sector on the boot device contains the master boot record mboot, which is loaded and executed. If no mboot file is found, an error message is displayed.

Boot Programs 

3. The master boot record, mboot, which contains disk information needed to find the active partition and the location of the Solaris boot program, pboot, loads and executes pboot.

4. The Solaris boot program, pboot loads bootblk, the primary boot program, whose purpose is to load the secondary boot program that is located in the ufs file system.

5. If there is more than one bootable partition, bootblk reads the fdisk table to locate the default boot partition, and builds and displays a menu of available partitions. You have a 30-second interval to select an alternate partition from which to boot. This step only occurs if there is more than one bootable partition present on the system.

6. bootblk finds and executes the secondary boot program, boot.bin or ufsboot, in the root (/) file system. You have a 5–second interval to interrupt the autoboot to start the Solaris Device Configuration Assistant.

7. The secondary boot program, boot.bin or ufsboot, starts a command interpreter that executes the /etc/bootrc script, which provides a menu of choices for booting the system. The default action is to load and execute the kernel. You have a 5–second interval to specify a boot option or to start the boot interpreter.

Kernel initialization 

8. The kernel initializes itself and begins loading modules by using the secondary boot program (boot.bin or ufsboot) to read the files. When the kernel has loaded enough modules to mount the root (/) file system, the kernel unmaps the secondary boot program and continues, using its own resources.

9. The kernel creates a user process and starts the /sbin/init process, which starts other processes by reading the /etc/inittab file.

init

10. The /sbin/init process starts the run control (rc) scripts, which execute a series of other scripts. These scripts (/sbin/rc*) check and mount file systems, start various processes, and perform system maintenance tasks.