JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
System Administration Guide: Basic Administration     Oracle Solaris 11 Express 11/10
search filter icon
search icon

Document Information


1.  Managing User Accounts and Groups (Overview)

2.  Managing User Accounts and Groups (Tasks)

3.  Introduction to Shutting Down and Booting a System

4.  Shutting Down and Booting a System (Overview)

Fundamentals of the Oracle Solaris Boot Design

Overview of the SPARC Boot Architecture

Support for Booting Multiple Kernels

Implementation of the Boot Archives on SPARC

x86: Overview of the GRUB Bootloader

GRUB Based Booting

x86: Support for the findroot Command

x86: Support for Fast Reboot

x86: Fast Reboot Feature Enhancements

quiesce Function

uadmin Function

Booting From an Oracle Solaris ZFS Root File System

5.  Shutting Down a System (Tasks)

6.  Modifying Oracle Solaris Boot Behavior (Tasks)

7.  Booting an Oracle Solaris System (Tasks)

8.  Troubleshooting Booting an Oracle Solaris System (Tasks)

9.  Managing the Oracle Solaris Boot Archives (Tasks)

10.  x86: GRUB Based Booting (Reference)

11.  Managing Services (Overview)

12.  Managing Services (Tasks)


Overview of the SPARC Boot Architecture

The boot processes on the SPARC platform have been redesigned and improved to increase commonality with the x86 boot experience. The SPARC boot design enables the addition of new features, for example new file system types, without necessitating any changes to multiple portions of the boot chain. Changes also include the implementation of boot phase independence.

Highlights of these improvements include:

The following four boot phases are now independent of each other:

  1. Open Boot PROM (OBP) phase

    The OBP phase of the boot process on the SPARC platform is unchanged.

    For disk devices, the firmware driver usually uses the OBP label package's load method, which parses the VTOC label at the beginning of the disk to locate the specified partition. Sectors 1-15 of the partition are then read into the system's memory. This area is commonly called the boot block and usually contains a file system reader.

  2. Booter phase

    During this phase the boot archive is read and executed. Note that this is the only phase of the boot process that requires knowledge of the boot file system format. Protocols that are used for the transfer of the boot loader and the boot archive include local disk access, NFS, and HTTP.

  3. Ramdisk phase

    The ramdisk is a boot archive that is comprised of kernel modules any other components that are required to boot an instance of Oracle Solaris..

    The SPARC boot archive is identical to an x86 boot archive. The boot archive file system format is private. Therefore, knowledge of the file system type that is used during a system boot, for example an HSFS file system, is not required by the booter or the kernel. The ramdisk extracts the kernel image from the boot archive and then executes it.

  4. Kernel phase

    The kernel phase is the final stage of the boot process. During this phase, Oracle Solaris is initialized and a minimal root file system is mounted on the ramdisk that was constructed from the boot archive. In some environments, such as an installation, the ramdisk is used as the root (/) file system and remains mounted.The ramdisk contains a set of kernel files and drivers that is sufficient to mount the root file system on the specified root device.

    The kernel then extracts the remainder of the primary modules from the boot archive, initializes itself, mounts the real root file system, then discards the boot archive.

Support for Booting Multiple Kernels

On SPARC based systems, when you boot the system from the ok prompt, the default boot device is automatically selected. An alternate boot device can be specified by changing the NVRAM variable for the boot-device. You can also specify an alternate boot device or an alternate kernel (boot file) from the command line at boot time. See SPARC: How to Boot a Kernel Other Than the Default Kernel.

Implementation of the Boot Archives on SPARC

The boot archives, previously only available on the x86 platform, are now an integral part of the SPARC boot architecture.

The bootadm command has been modified for use on the SPARC platform. This command functions the same as it does on the x86 platform. The bootadm command handles the details of archive update and verification. On the x86 platform the bootadm command updates the GRUB menu during an installation or system upgrade. You can also use the bootadm command to manually manage the boot archives.

The boot archive service is managed by the Service Management Facility (SMF). The service instance for the boot archive is svc:/system/boot-archive:default. To enable, disable, or refresh this service use the svcadm command. For information about managing services by using SMF, see Chapter 11, Managing Services (Overview).

The files that are included in the SPARC boot archives are located in the /platform directory.

The contents of the /platform directory is divided into two groups of files:

For information about managing the boot archives, see Managing the Oracle Solaris Boot Archives (Task Map).