Caution

After you have activated a boot environment, do not change the disk order in the BIOS. Changing the order might cause the GRUB menu to become invalid. If this problem occurs, changing the disk order back to the original state fixes the GRUB menu. 

Activating a boot environment for the first time 

The first time you activate a boot environment, you must use the luactivate command or the Activate menu. The next time you boot, that boot environment's name is displayed in the GRUB main menu. You can thereafter switch to this boot environment by selecting the appropriate entry in the GRUB menu.

To Activate a Boot Environment (Command-Line Interface)

Synchronizing files 

The first time you activate a boot environment, files are synchronized between the current boot environment and the new boot environment. With subsequent activations, files are not synchronized. When you switch between boot environments with the GRUB menu, files also are not synchronized. You can force a synchronization when using the luactivate command with the -s option.

To Activate a Boot Environment and Synchronize Files (Command-Line Interface)

Boot environments created before the Solaris 10 1/06 release

If a boot environment was created with the Solaris 8, 9, or 10 3/05 release, the boot environment must always be activated with the luactivate command or the Activate menu. These older boot environments do not display on the GRUB menu.

To Activate a Boot Environment (Command-Line Interface)

Editing or customizing the GRUB menu entries 

The menu.lst file contains the information that is displayed in the GRUB menu. You can revise this file for the following reasons:

• To add to the GRUB menu entries for operating systems other than the Solaris OS.

• To customize booting behavior. For example, you could change booting to verbose mode or change the default time that automatically boots the OS.

If you want to change the GRUB menu, you need to locate the menu.lst file. For step-by-step instructions, see x86: Locating the GRUB Menu's menu.lst File (Tasks).

Do not use the GRUB menu.lst file to modify Solaris Live Upgrade entries. Modifications could cause Solaris Live Upgrade to fail. Although you can use the menu.lst file to customize booting behavior, the preferred method for customization is to use the eeprom command. If you use the menu.lst file to customize, the Solaris OS entries might be modified during a software upgrade. Changes to the file could be lost.

• GRUB Based Booting (Overview) in Solaris 10 11/06 Installation Guide: Planning for Installation and Upgrade

• Chapter 11, GRUB Based Booting (Tasks), in System Administration Guide: Basic Administration