JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Transitioning From Oracle Solaris 10 to Oracle Solaris 11     Oracle Solaris 11 Information Library
search filter icon
search icon

Document Information


1.  Transitioning From Oracle Solaris 10 to Oracle Solaris 11 (Overview)

2.  Transitioning to an Oracle Solaris 11 Installation Method

3.  Managing Devices

4.  Managing Storage Features

5.  Managing File Systems

6.  Managing Software

Oracle Solaris 11 Package Changes

Oracle Solaris 10 SVR4 and IPS Package Comparison

IPS Installation Package Groups

Displaying Information About Software Packages

Updating the Software on Your Oracle Solaris 11 System

Installing Maintenance Updates on an Oracle Solaris 11 System

How to Configure the Oracle Solaris support Repository

Managing Boot Environments

Tools for Managing Boot Environments

Reviewing the Initial ZFS BE After an Installation

How to Update Your ZFS Boot Environment

7.  Managing Network Configuration

8.  Managing System Configuration

9.  Managing Security

10.  Managing Oracle Solaris Releases in a Virtual Environment

11.  User Account Management and User Environment Changes

12.  Using Oracle Solaris Desktop Features

A.  Transitioning From Previous Oracle Solaris 11 Releases to Oracle Solaris 11

Managing Boot Environments

Previously, you could perform a live upgrade or use the patchadd command to update your BE. In Oracle Solaris 11, the pkg update command is used to update a BE, or you can use the beadm command set to create, display, and remove BEs.

Tools for Managing Boot Environments

In Oracle Solaris 11, the beadm utility replaces the lu set of commands for managing ZFS BEs. In addition, the pkg update command updates your existing BE and creates a clone BE, if necessary.

Table 6-2 Comparison of Boot Environment Command Syntax

Oracle Solaris 10 Syntax
Oracle Solaris 11 Syntax
lucreate -n newBE
beadm create newBE
Create a new BE
beadm list
Display BE information
luactivate newBE
beadm activate newBE
Activate a BE
ludelete BE
beadm destroy BE
Destroy an inactive BE
luupgrade or patchadd
pkg update
Upgrade or update a BE

See Creating and Administering Oracle Solaris 11 Boot Environments and beadm(1M).

The system performs the following actions:

  1. Creates a clone of the current BE that is a bootable image.

  2. Updates the packages in the clone BE, but does not update any packages in the current BE.

  3. Sets the new BE as the default boot choice the next time the system is booted. The current BE remains as an alternate boot choice.

Use the beadm command to create, rename, mount, unmount, activate, or destroy BEs. You can use the Package Manager to activate, rename, and delete BEs.

Reviewing the Initial ZFS BE After an Installation

After a system is installed, the following root pool file systems and components are available:

# zfs list -r rpool
NAME                      USED  AVAIL  REFER  MOUNTPOINT
rpool                    5.41G  67.4G  74.5K  /rpool
rpool/ROOT               3.37G  67.4G    31K  legacy
rpool/ROOT/solaris       3.37G  67.4G  3.07G  /
rpool/ROOT/solaris/var    302M  67.4G   214M  /var
rpool/dump               1.01G  67.5G  1000M  -
rpool/export             97.5K  67.4G    32K  /rpool/export
rpool/export/home        65.5K  67.4G    32K  /rpool/export/home
rpool/export/home/admin  33.5K  67.4G  33.5K  /rpool/export/home/admin
rpool/swap               1.03G  67.5G  1.00G  -

How to Update Your ZFS Boot Environment

To update a ZFS boot environment, use the pkg update command. If you update a ZFS BE by using pkg update, a new BE is created and automatically activated. If the updates to the existing BE are minimal, a backup BE is created before the updates are applied. The pkg update command displays whether a backup BE or a new BE is created.

  1. Display your existing BE information.
    # beadm list
    BE        Active Mountpoint Space  Policy Created          
    --        ------ ---------- -----  ------ -------          
    solaris   NR     /          12.24G static 2011-10-04 09:42 

    In the above output, NR means the BE is active now and will be the active BE on reboot.

  2. Update your BE.
    # pkg update
                    Packages to remove:   117
                   Packages to install:   186
                    Packages to update:   315
               Create boot environment:   Yes
    DOWNLOAD                                  PKGS       FILES    XFER (MB)
    Completed                              618/618 29855/29855  600.7/600.7

    If your existing BE name is solaris, a new BE, solaris-1, is created and automatically activated after the pkg update operation is complete.

  3. Reboot the system to complete the BE activation. Then, confirm your BE status.
    # init 6
    # beadm list
    BE        Active Mountpoint Space  Policy Created          
    --        ------ ---------- -----  ------ -------          
    solaris   NR     /          12.24G static 2011-10-04 09:42 
    solaris-1 -      -          6.08G  static 2011-10-11 10:42
  4. If an error occurs when booting the new BE, activate and boot to the previous BE.
    # beadm activate solaris
    # init 6