The bootenv keyword identifies boot environment characteristics. A boot environment is created by default during installation with the pool keyword. If you use the bootenv keyword with the installbe option, you can name the new boot environment and create a /var dataset within the boot environment.
This keyword can be used in a profile for installing a UFS file system or a ZFS root pool.
In a UFS file system, this keyword is used for creating an empty boot environment for the future installation of a Solaris Flash archive. For the complete description of the bootenv keyword for UFS, see bootenv Profile Keyword (UFS and ZFS).
For a ZFS root pool, the bootenv keyword changes the characteristics of the default boot environment that is created at install time. This boot environment is a copy of the root file system that you are installing.
The bootenv keyword can be used with the installbe, bename and dataset options. These options name the boot environment and create a separate /var dataset.
bootenv installbe bename new-BE-name [dataset mount-point]
Changes the characteristics of the default boot environment that is created during the installation.
Specifies the name of the new boot environment to be created, new_BE_name. The name can be no longer than 30 characters, can contain only alphanumeric characters, and can contain no multibyte characters. The name must be unique on the system.
Use the optional dataset keyword to identify a /var dataset that is separate from the ROOT dataset. The mount-point value is limited to /var. For example, a bootenv syntax line for separate /var dataset would be similar to the following:
bootenv installbe bename zfsroot dataset /var
For more information about upgrading and activating a boot environment, see Chapter 11, Solaris Live Upgrade and ZFS (Overview), in Solaris 10 5/09 Installation Guide: Solaris Live Upgrade and Upgrade Planning.