Skip Navigation Links | |
Exit Print View | |
Oracle Solaris 10 1/13 Installation Guide: Live Upgrade and Upgrade Planning Oracle Solaris 10 1/13 Information Library |
Part I Upgrading With Live Upgrade
1. Where to Find Oracle Solaris Installation Planning Information
4. Using Live Upgrade to Create a Boot Environment (Tasks)
5. Upgrading With Live Upgrade (Tasks)
6. Failure Recovery: Falling Back to the Original Boot Environment (Tasks)
7. Maintaining Live Upgrade Boot Environments (Tasks)
Overview of Live Upgrade Maintenance
Maintenance Activities for Boot Environments
Displaying the Status of All Boot Environments
Updating a Previously Configured Boot Environment
Canceling a Scheduled Create, Upgrade, or Copy Job
Deleting an Inactive Boot Environment
Displaying the Name of the Active Boot Environment
Adding or Changing a Description Associated With a Boot Environment Name
Viewing the Configuration of a Boot Environment
8. Upgrading the Oracle Solaris OS on a System With Non-Global Zones Installed
Part II Upgrading and Migrating With Live Upgrade to a ZFS Root Pool
10. Live Upgrade and ZFS (Overview)
11. Live Upgrade for ZFS (Planning)
12. Creating a Boot Environment for ZFS Root Pools
13. Live Upgrade for ZFS With Non-Global Zones Installed
A. Live Upgrade Command Reference
C. Additional SVR4 Packaging Requirements (Reference)
Renaming a boot environment is often useful when you upgrade the boot environment from one Oracle Solaris release to another release. For example, following an operating system upgrade, you might rename the boot environment solaris8 to solaris10.
Use the lurename command to change the inactive boot environment's name.
x86 only - Starting with the Solaris 10 1/06 release, the GRUB menu is automatically updated when you use the Rename menu or lurename command. The updated GRUB menu displays the boot environment's name in the list of boot entries. For more information about the GRUB menu, see Booting Multiple Boot Environments.
To find out how to determine the location of the GRUB menu's menu.lst file, see Chapter 13, Managing the Oracle Solaris Boot Archives (Tasks), in Oracle Solaris Administration: Basic Administration.
Note the following limitations for naming a boot environment:
The name must not exceed 30 characters in length.
The name can consist only of alphanumeric characters and other ASCII characters that are not special to the UNIX shell. For more information, see the “Quoting” section of the sh(1) man page.
The name can contain only single-byte, 8-bit characters.
The name must be unique on the system.
A boot environment must have the status Complete before you rename it. For more information, see Displaying the Status of All Boot Environments to determine a boot environment's status.
You cannot rename a boot environment that has file systems mounted with lumount or mount.
The syntax of the lurename command is as follows:
# lurename -e BE-name -n new-name
Specifies the inactive boot environment name to be changed
Specifies the new name of the inactive boot environment
In this example, second_disk is renamed to third_disk.
# lurename -e second_disk -n third_disk