JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Booting and Shutting Down Oracle Solaris on SPARC Platforms     Oracle Solaris 11 Information Library
search filter icon
search icon

Document Information


1.  Booting and Shutting Down a SPARC Based System (Overview)

What's New in Booting and Shutting Down a System

Administratively Provided driver.conf Files

Fast Reboot on SPARC Platforms

Booting and Shutting Down a SPARC Based System (Topic Map)

Guidelines for Booting a System

Reasons to Boot a System

Service Management Facility and Booting

Changes in Behavior When Using SMF

How Run Levels Work

What Happens When a System Is Booted to a Multiuser State (Run Level 3)

When to Use Run Levels or Milestones

Overview of the Oracle Solaris Boot Architecture

Description of the SPARC Boot Process

SPARC Boot Phases

2.  Booting a SPARC Based System to a Specified State (Tasks)

3.  Shutting Down a System (Tasks)

4.  Rebooting a SPARC Based System (Tasks)

5.  Booting a SPARC Based System From the Network (Tasks)

6.  Modifying Boot Parameters on a SPARC Based System (Tasks)

7.  Creating, Administering, and Booting From ZFS Boot Environments on SPARC Platforms (Tasks)

8.  Keeping a SPARC Based System Bootable (Tasks)

9.  Troubleshooting Booting a SPARC Based System (Tasks)


What's New in Booting and Shutting Down a System

The following boot features are new the Oracle Solaris 11 release:

Administratively Provided driver.conf Files

Driver configuration files (driver.conf) can be supplemented with local, administrative changes without modifying the original vendor provided files in the /kernel and /platform directories. This enhancement provides better preservation of local configuration during a system upgrade. You can now provide local changes to driver configuration by adding driver.conf files to the new /etc/driver/drv directory. At boot time, the system checks for a configuration file in /etc/driver/drv for that driver. If found, the system automatically merges the vendor-provided configuration with the administratively provided changes.

To display these merged properties, use the prtconf command with the new -u option. The -u option enables you to display both the original and updated property values for a specified driver. For more information, see the prtconf(1M) man page. For instructions, see How to Display Default and Customized Property Values for a Device in Oracle Solaris Administration: Common Tasks.

Note - Do not edit vendor-provided driver.conf files in the /kernel and /platform directories. If you need to supplement a driver's configuration, the preferred method is to add a corresponding driver.conf file to the local /etc/driver/drv directory, and then customize that file. For instructions, see Chapter 5, Managing Devices (Overview/Tasks), in Oracle Solaris Administration: Devices and File Systems.

See also the following additional references:

Fast Reboot on SPARC Platforms

The integration of Fast Reboot on the SPARC platform enables the -f option to be used with the reboot command to accelerate the boot process by skipping certain POST tests.

The Fast Reboot feature is managed by the Service Management Facility (SMF) feature of Oracle Solaris and implemented through a boot configuration service, svc:/system/boot-config. The boot-config service provides a means for setting or changing the default boot configuration parameters. When the config/fastreboot_default property is set to true, the system performs a fast reboot automatically, without the need to use the reboot -f command. This property's value is set to false on the SPARC platform. For task-related information, see Accelerating the Reboot Process on a SPARC Based System.

Note - Fast reboot behavior on SPARC is applicable only to certain systems. On sun4v systems, fast reboot is unnecessary because the reboot is actually a hypervisor restart that does not involve POST.