Tools for Managing Boot Environments

Language:

The beadm utility replaces the lu set of commands for managing ZFS BEs. In most cases, the pkg update command creates and updates a clone BE. However, the command is not guaranteed to create a new or backup BE in every instance. Use the appropriate pkg update command options to specify a desired outcome. Also, new and backup BEs behave differently. For new BEs, updates are made in the new BE. Whereas, if a backup BE is created, updates are made in the current BE.

Table 6-2 Comparing Boot Environment Command Syntax

Oracle Solaris 10 Syntax	Oracle Solaris 11 Syntax	Description
`lucreate -n` `newBE`	`beadm create` `newBE`	Create a new BE
`lustatus`	`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.2 Boot Environments and beadm(1M).

In most cases, the pkg update command, when used with no operands, performs the following actions:

Creates a clone of the current BE that is a bootable image.
Updates the packages in the clone BE, but does not update any packages in the current BE.
Sets the new BE as the default boot option the next time the system is booted. The current BE remains as an alternate boot option.