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)


Service Management Facility and Booting

SMF provides an infrastructure that augments the traditional UNIX startup scripts, init run levels, and configuration files. With the introduction of SMF, the boot process creates fewer messages now. Services do not display a message by default when they are started. All of the information that was provided by the boot messages can now be found in a log file for each service that is in /var/svc/log. You can use the svcs command to help diagnose boot problems. To generate a message when each service is started during the boot process, use the -v option with the boot command.

When a system is being booted you can select the milestone to boot to or select the level of error messages to be recorded. For instance:

Changes in Behavior When Using SMF

Most of the features that are provided by SMF occur behind the scenes, so users are not typically aware of these features. Other features are accessed by new commands.

Here is a list of the behavior changes that are most visible: