Follow Techotopia on Twitter

On-line Guides
All Guides
eBook Store
iOS / Android
Linux for Beginners
Office Productivity
Linux Installation
Linux Security
Linux Utilities
Linux Virtualization
Linux Kernel
System/Network Admin
Scripting Languages
Development Tools
Web Development
GUI Toolkits/Desktop
Mail Systems
Eclipse Documentation

How To Guides
General System Admin
Linux Security
Linux Filesystems
Web Servers
Graphics & Desktop
PC Hardware
Problem Solutions
Privacy Policy




Solaris Express Installation Guide: Solaris Live Upgrade and Upgrade Planning
Previous Next

Changing the Name of a Boot Environment

Renaming a boot environment is often useful when you upgrade the boot environment from one 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 x86: Activating a Boot Environment With the GRUB Menu.

To determine the location of the GRUB menu's menu.lst file, see x86: Locating the GRUB Menu's menu.lst File (Tasks).

Table 7-2 Limitations for Naming a Boot Environment


For Instructions

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.

See the “Quoting” section of sh(1).

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.

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.

To Change the Name of an Inactive Boot Environment

  1. Become superuser or assume an equivalent role.

    Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.

  2. Type:
    # lurename -e  BE_name -n  new_name
    -e BE_name

    Specifies the inactive boot environment name to be changed

    -n new_name

    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
Previous Next

  Published under the terms fo the Public Documentation License Version 1.01. Design by Interspire