Skip Navigation Links | |
Exit Print View | |
Getting Started With Oracle Solaris 11 Express Oracle Solaris 11 Express 11/10 |
1. Exploring Oracle Solaris 11 Express
2. Preparing to Install Oracle Solaris 11 Express
3. Installing Oracle Solaris 11 Express
4. Verifying and Finalizing Your Installed System
5. Understanding Users and Roles
7. Setting Up Your Application Development Environment
8. Keeping Your System Up-To-Date
Updating Software Packages on Your System
Updating Individual Software Packages on Your System by Using pkg Commands
Managing Multiple Boot Environments
Why Use Multiple Boot Environments?
A. Managing the GRUB Menu in the Oracle Solaris Release
A boot environment, also called a BE, is a bootable instance of the Oracle Solaris operating system image, plus any other application software packages that are installed on that image. You can maintain multiple boot environments on a single system, and each boot environment can have a different software version installed.
Upon the initial installation of the operating system, a boot environment is created on your system. Use the Boot Environment Management tool or the beadm command to administer additional boot environments on your system.
With multiple boot environments, the process of updating software becomes a low risk operation because you are able to create backup boot environments before making any software updates to your system. If necessary, you have can boot a backup BE.
Note - The process of creating backup boot environments does not create a backup of all the files on your system and is not the same as backing up a file system.
The ability to create different boot environments enables you to have different environments for different versions of tools that you use. Shared files are not affected by creating a new boot environment. If you modify files in a newer boot environment, and then boot to an older boot environment, the files are also modified for that boot environment. You cannot retrieve an older version of a shared file from an older boot environment.
You can maintain more than one boot environment on your system at the same time and perform various upgrades on each of them. For example, you can clone a boot environment by using the beadm create command. A clone is a bootable copy of a boot environment. Then, you can install, test, and update different software packages on the original boot environment and on its clone.
Although only one boot environment can be active at any given time, you can mount an inactive boot environment by using the beadm mount command. Then you can use the pkg update command to update all of the packages in that inactive, mounted environment that have available updates. Or, use the pkg install package-name command, with the -R option to update specific packages in that boot environment.
You can use Package Manager to manage your boot environments.
The following boot environment management tasks can be performed by using Package Manager:
Display information about all of the boot environments on your installed system
Delete old or unused boot environments
Change the default boot environment on your system
Activate a boot environment
Note - Using Package Manager to manage your boot environments from the desktop does not provide all of the options for managing your boot environments that are available by using the beadm command. For more information, see the beadm(1M) man page.
The Boot Environment Management window opens, displaying all of the available boot environments that are on your installed system. Also displayed is the name of the operating system, the date the boot environment was created, and the size of the boot environment, in GB.
The new boot environment becomes active on the next system reboot.