JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Creating and Administering Oracle Solaris 11 Boot Environments     Oracle Solaris 11 Information Library
search filter icon
search icon

Document Information


1.  Introduction to Managing Boot Environments

2.  beadm Zones Support

3.  Creating Boot Environments and Snapshots

4.  Administering Boot Environments

Listing Existing Boot Environments and Snapshots

Viewing Boot Environment Specifications

Viewing Specifications in Machine-Parsable Output

Viewing Snapshot Specifications

Changing the Default Boot Environment

Mounting and Updating an Inactive Boot Environment

How to Mount and Update a Boot Environment

Unmounting Boot Environments

Destroying a Boot Environment

Creating Custom Names for Boot Environments

Creating Additional Datasets for Boot Environments

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 with 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:

Syntax: beadm rename BeName newBeName

The command changes the name of an existing boot environment to a new name.

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