Creating and Administering Oracle® Solaris 11.2 Boot Environments

Exit Print View

Updated: July 2014

Creating Custom Names for Boot Environments

The beadm rename command enables you to rename an existing boot environment so you can supply a name that is more meaningful for your particular situation. For example, you could rename boot environments to specify how you customized that environment. The boot environment's dataset name is also changed to conform to the new boot environment name.

When you rename a boot environment, that change does not impact the names of the zones or the names of the datasets that are used for those zones in that boot environment. The change does not affect the relationships between the zones and their related boot environments.

An active boot environment cannot be renamed. Only an inactive boot environment can be renamed.

You cannot rename the boot environment that is currently booted. If you want to rename the active boot environment, you must first make a different boot environment active and boot that environment. Then you can rename the inactive boot environment.

The command syntax is as follows:

beadm rename BeName newBeName

The command renames Bename to newBeName.

If the new name is already in use, the beadm rename command fails.

Note -  A new boot environment or a backup boot environment might be created when you install, update, or uninstall a package using the pkg command. You can create custom names for new or backup boot environments by using the –be-name or –backup-be-name options with the pkg command. For information, see Boot Environment Options in Adding and Updating Software in Oracle Solaris 11.2 .