JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Administration: Common Tasks     Oracle Solaris 11 Information Library
search filter icon
search icon

Document Information

About This Book

1.  Locating Information About Oracle Solaris Commands

2.  Managing User Accounts and Groups (Overview)

3.  Managing User Accounts and Groups (Tasks)

4.  Booting and Shutting Down an Oracle Solaris System

What's New in Booting and Shutting Down a System?

Support for Administratively Provided driver.conf Files

Bitmapped Console

Boot and Shutdown Progress Animation

Fast Reboot

x86: Removal of Support for 32-Bit Kernel

Booting and Shutting Down an Oracle Solaris System (Overview)

GRUB Based Booting

Management of Boot Services by the Service Management Facility

Booting a System to a Specified State (Task Map)

Booting a System to a Specified State (Run Level)

Determining a System's Current Run Level

SPARC: How to Boot a System to a Multiuser State (Run Level 3)

x86: How to Boot a System to a Single-User State (Run Level S)

Shutting Down a System (Task Map)

Shutting Down a System

How to Shut Down a System by Using the shutdown Command

Bringing a System to a Shutdown State (Run Level 0) by Using the init Command

How to Shut Down a System by Using the init Command

Booting a System From the Network

Accelerating the Reboot Process (Task Map)

Accelerating the Reboot Process

How to Initiate a Fast Reboot of a SPARC Based System

How to Initiate a Fast Reboot of an x86 Based System

Changing the Default Behavior of the Fast Reboot Feature

Initiating a Standard Reboot of a System That Has Fast Reboot Enabled

Booting From a ZFS Boot Environment (Task Map)

SPARC: Booting From a ZFS Boot Environment

SPARC: How to Display a List of Available Boot Environments During the Boot Sequence

SPARC: How to Boot From a ZFS Boot Environment or Root File System

Modifying Boot Parameters (Task Map)

Modifying Boot Parameters

SPARC: How to Determine the Default Boot Device

SPARC: How to Change the Default Boot Device by Using the Boot PROM

x86: How to Modify Boot Parameters by Using the eeprom Command

x86: How to Modify Boot Parameters at Boot Time

Adding a Linux Entry to the GRUB Menu After an Installation

Keeping a System Bootable (Task Map)

Keeping a System Bootable

Determining Whether the boot-archive SMF Service Is Running

How to Clear a Failed Automatic Boot Archive Update by Manually Updating the Boot Archive

x86: How to Clear a Failed Automatic Boot Archive Update by Using the auto-reboot-safe Property

Where to Find More Information About Booting and Shutting Down a System

5.  Working With Oracle Configuration Manager

6.  Managing Services (Overview)

7.  Managing Services (Tasks)

8.  Using the Fault Manager

9.  Managing System Information (Tasks)

10.  Managing System Processes (Tasks)

11.  Monitoring System Performance (Tasks)

12.  Managing Software Packages (Tasks)

13.  Managing Disk Use (Tasks)

14.  Scheduling System Tasks (Tasks)

15.  Setting Up and Administering Printers by Using CUPS (Tasks)

16.  Managing the System Console, Terminal Devices, and Power Services (Tasks)

17.  Managing System Crash Information (Tasks)

18.  Managing Core Files (Tasks)

19.  Troubleshooting System and Software Problems (Tasks)

20.  Troubleshooting Miscellaneous System and Software Problems (Tasks)


What's New in Booting and Shutting Down a System?

The following features are new Oracle Solaris 11:

Support for Administratively Provided driver.conf Files

In this Oracle Solaris release, vendor-provided driver.conf files can be supplemented with administratively provided driver.conf files. The format of an administratively provided driver.conf file is identical to a vendor-provided driver.conf file. Vendor-provided driver data is installed in the root file system, while administratively provided driver data is stored separately in a new /etc/driver/drv directory.

At boot time, and whenever a driver.conf file for a driver is searched for and loaded, the system checks for a configuration file in the /etc/driver/drv directory for that driver. If found, the system automatically merges the vendor-provider driver.conf files with the local, administratively provided driver.conf files. Note that the driver's view of the system properties consists of these merged properties. Therefore, no driver changes are necessary.

To display the 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 and How to Display Default and Customized Property Values for a Device.

Note - Do not edit vendor-provided driver.conf files that are located 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.

One advantage of customizing the administratively provided configuration file rather than the vendor-provide configuration file is that your changes are preserved during a system upgrade. During a system upgrade, if a vendor-provided driver.conf file has an update available, the file is automatically updated, and all customization is lost. Since there is no way to know which driver configuration files will be updated prior to performing an upgrade, always make it a practice to make any customization to the administratively provided version of the file. Before customizing an administratively provided configuration file, familiarize yourself with the driver.conf file format. See the driver.conf(4) man page for more information.

For detailed instructions, see Chapter 5, Managing Devices (Overview/Tasks), in Oracle Solaris Administration: Devices and File Systems.

Device driver writers should note that driver interfaces are provided to enable a driver to access both the vendor and admin properties. For more information, see the driver(4) man page and Writing Device Drivers.

For instructions, see the ddi_prop_exists(9F) and ddi_prop_lookup(9F) man pages.

Bitmapped Console

Oracle Solaris 11 supports higher resolution and color depth on x86 based systems than the older Video Graphics Array (VGA) 640-480 16-color console. This support is provided for systems that use traditional BIOS and Video Electronics Standards Association (VESA) option read-only memory (ROM). Note that support is limited to when a graphics card or frame buffer is used as a physical or virtual console. There is no impact on the behavior of serial consoles.

For more information, see Support for Bitmapped Console in Booting and Shutting Down Oracle Solaris on x86 Platforms.

Boot and Shutdown Progress Animation

The progress status indicator that is displayed on a system during the boot process is automatically interrupted in the following instances:

During the shutdown process, if the console=graphics option was specified when booting the system, and the shutdown is triggered by the Xorg server, a progress status indicator is displayed. You can prevent the progress status indicator from displaying by setting the new splash-shutdown property of the svc:/system/boot-config SMF service to false.

Fast Reboot

The Fast Reboot feature is supported on both the SPARC and x86 platform. 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. On the x86 platform, Fast Reboot implements an in-kernel boot loader that loads the kernel into memory and then switches to that kernel. The firmware and boot loader processes are bypassed, which enables the system to reboot within seconds.

On both the x86 and SPARC platforms, the Fast Reboot feature is managed by SMF 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 and true on the x86 platform. For task-related information, including how to change the default behavior of Fast Reboot on the SPARC platform, see Accelerating the Reboot Process.

x86: Removal of Support for 32–Bit Kernel

In Oracle Solaris 11, 32–bit kernel support on x86 platforms has been removed. As a result, you cannot boot Oracle Solaris 11 on 32-bit x86 hardware. Systems that have 32-bit hardware must either be upgraded to 64–bit hardware or continue to run Oracle Solaris 10.

Note - This removal of support does not impact 32–bit applications, which remains the same as in previous releases.