Skip Navigation Links | |
Exit Print View | |
Managing Boot Environments With Oracle Solaris 11 Express Oracle Solaris 11 Express 11/10 |
1. Introduction to Boot Environments
2. Using beadm Utility (Tasks)
Listing Existing Boot Environments and Snapshots
How to Display Information About Your Boot Environments, Snapshots, and Datasets
How to Create a Boot Environment
How to Create a Boot Environment From an Inactive Boot Environment
Taking a Snapshot of a Boot Environment
How to Create a Snapshot of a Boot Environment
How to Create a Boot Environment From an Existing Snapshot
Mounting and Updating an Inactive Boot Environment
How to Mount a Boot Environment
How to Unmount an Existing Boot Environment
How to Destroy an Existing Boot Environment
Creating Custom Names for Boot Environments
You can change an inactive boot environment into an active boot environment. Only one boot environment can be active at a time. The newly activated boot environment becomes the default environment upon reboot.
$ beadm activate beName
beName is a variable for the name of the boot environment to be activated.
Note the following specifications.
beadm activate beName activates a boot environment by setting the bootable pool property, bootfs, to the value of the ROOT dataset of the boot environment that is being activated.
beadm activate sets the newly activated boot environment as the default in the menu.lst file.
Note - When a boot environment is created, whether it is active or inactive, an entry is created for the boot environment on the x86 GRUB menu or the SPARC boot menu. The default boot environment is the last boot environment that was activated.
The newly activated boot environment is now the default on the x86 GRUB menu or SPARC boot menu.
Note - If the boot environment fails to boot, reboot and select the previous boot environment from the GRUB menu or the boot menu.