The bootenv keyword can be used for either a UFS file system or a ZFS root pool installation. The usage is different for a ZFS installation.
For a complete list of keywords that can be used in a UFS or ZFS installation, see Table 8–2
For a description of how the bootenv keyword can be used when installing a ZFS root pool, see JumpStart Keywords for a ZFS Root (/) File System (Reference)
bootenv createbe bename new_BE_name filesystem mountpoint:device:fs_options [filesystem...]
bootenv createbe keyword enables you to quickly create an empty-and-inactive boot environment at the same time you are installing the Solaris OS. At the least, you must create the root (/) file system. The slices are reserved for the file systems specified, but no file systems are copied. The boot environment is named, but not actually created until installed with a Solaris Flash archive. When the empty boot environment is installed with an archive, file systems are installed on the reserved slices. The following lists the values for bename and filesystem.
bename specifies the name of the new boot environment to be created. new_BE_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.
filesystem determines the type and number of file systems that are to be created in the new boot environment. At least one slice that contains the root (/) file system must be defined. File systems can be on the same disk or spread across multiple disks.
mountpoint can be any valid mount point or – (hyphen), indicating a swap slice.
device must be available when the operating system that is being installed is first booted. The device has no relation to JumpStart special storage devices such as free. The device cannot be a Solaris Volume Manager volume or Veritas Volume Manager volume. device is the name of a disk device, of the form /dev/dsk/cwtxdysz.
fs_options can be one of the following:
ufs, which indicates a UFS file system.
swap, which indicates a swap file system. The swap mount point must be a – (hyphen).
For a profile example and background about using this keyword, see the following references:
For an example of a profile
For background about using Solaris Live Upgrade that creates, upgrades, and activates inactive boot environments
For background about using a Solaris Flash archive