test

Solaris 9 12/03 Installation Guide

bootenv createbe Profile Keyword

bootenv createbe bename new_BE_name filesystem mountpoint:device:fs_options 
[filesystem...]

bootenv createbe enables you to create an empty-and-inactive boot environment at the same time you are installing the operating environment. At the least, you must create the root (/) file system. Although you are creating file systems, they remain empty. This inactive boot environment can later be populated with a Solaris Flash archive. After the boot environment is installed with the archive, it can be activated to become the current operating environment. The following lists the values for bename and filesystem.

bename new_BE_name

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 mountpoint:device:fs_options

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 environment 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: