Adding and Updating Software in Oracle® Solaris 11.2

Exit Print View

Updated: July 2014
 
 

Installing a Package Into a New Boot Environment


Tip  - Explicitly specifying a new BE is the safest way to install or update. See Boot Environment Policy Image Properties for information about when BEs are created.

The new BE is a clone of the current BE with the specified install, uninstall, or update changes applied. The current BE is not modified. The system is not automatically restarted. The new BE is the default boot selection the next time you restart the system. The current BE is still available to be booted.

If you specify the --no-be-activate option, the new BE is not the default boot selection the next time you reboot.

Use the --be-name option to force a new BE to be created or to give the new BE a meaningful name if a new BE would be created by default.

The example in Previewing an Operation showed that a new BE would not be created by default when you install the group/feature/amp package. In the following partial output, a new BE is created because the --be-name option is specified:

$ pkg install -v --be-name s11amp group/feature/amp
           Packages to install:         6
           Mediators to change:         1
     Estimated space available:  22.70 GB
Estimated space to be consumed: 751.08 MB
       Create boot environment:       Yes
     Activate boot environment:       Yes
Create backup boot environment:        No
          Rebuild boot archive:        No

The following message displays at the end of the installation operation:

A clone of s11 exists and has been updated and activated.
On the next boot the Boot Environment s11amp will be
mounted on '/'.  Reboot when ready to switch to this updated BE.

The pkg list command reports that the group/feature/amp package is not installed because the group/feature/amp package is not installed in the current BE. The group/feature/amp package is installed in the new s11amp BE.

$ pkg list group/feature/amp
pkg list: no packages matching 'group/feature/amp' installed

Use the beadm list command to check that the system has a new active BE named s11amp. The “N” BE is currently booted. The “R” BE is the default on reboot. Use the beadm activate command to change which BE is the default on reboot.

$ beadm list
BE           Active Mountpoint Space   Policy Created
--           ------ ---------- -----   ------ -------
s11          N      /          30.92M  static 2014-03-05 08:51
s11amp       R      -          25.75G  static 2014-03-26 10:45

Check that the group/feature/amp package is installed in the new BE. Mount the new BE, and use the -R option to operate on the mounted BE. The “i” in the I column indicates that the group/feature/amp package is installed.

$ beadm mount s11amp /mnt
$ beadm list
BE           Active Mountpoint Space   Policy Created
--           ------ ---------- -----   ------ -------
s11          N      /          30.92M  static 2014-03-05 08:51
s11amp       R      /mnt       25.75G  static 2014-03-26 10:45
$ pkg -R /mnt list group/feature/amp
NAME (PUBLISHER)       VERSION                    IFO
group/feature/amp      0.5.11-0.175.2.0.0.33.0    i--

Remember to unmount the s11amp BE.

$ beadm unmount s11amp