boot_device Profile Keyword

boot_device device eeprom

boot_device designates the device where the JumpStart program is to install the root (/) file system and the system's boot device.

If you do not specify the boot_device keyword in a profile, the following boot_device keyword is specified by default during the installation: boot_device any update.

device - Use one of the following values.

• SPARC: cwtxdysz or cxdysz - The disk slice where the JumpStart program places the root (/) file system, for example, c0t0d0s0.

• x86: cwtxdy or cxdy - The disk where the JumpStart program places the root (/) file system, for example, c0d0.

• existing - The JumpStart program places the root (/) file system on the system's existing boot device.

• any - The JumpStart program chooses where to place the root (/) file system. The JumpStart program attempts to use the system's existing boot device. The JumpStart program might choose a different boot device if necessary.

eeprom - Choose to update or preserve the system's EEPROM.

SPARC: Choose if you want to update or preserve the system's EEPROM to the specified boot device.

x86: You must specify the preserve value.

• update - The JumpStart program updates the system's EEPROM to the specified boot device so that the installed system automatically boots from it.

• preserve - The boot device value in the system's EEPROM is not changed. If you specify a new boot device without changing the system's EEPROM, you need to change the system's EEPROM manually so it can automatically boot from the new boot device.

Note - SPARC: On SPARC systems, the eeprom value also allows you to update the system's EEPROM if you change the system's current boot device. By updating the system's EEPROM, the system can automatically boot from the new boot device.

Example:

boot_device c0t0d0s2 update

Note - boot_device must match any filesys keywords that specify the root (/) file system and the root_device keyword, if specified.

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, no file system is created on the slice. No copy of file systems from the current boot environment occurs. The new boot environment is named and is ready for file systems to be added. This empty 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:

• For an example of a profile, see Example 26-9.

• For background about using Solaris Live Upgrade that creates, upgrades, and activates inactive boot environments, see Chapter 32, Solaris Live Upgrade (Topics).

• For background about using a Solaris Flash archive, see Chapter 19, Solaris Flash Installation Feature (Topics).

client_arch Profile Keyword

client_arch karch_value ...

client_arch specifies that the operating system server is to support a different platform group than the server uses. If you do not specify client_arch in the profile, any diskless client that uses the operating system server must contain the same platform group as the server. You must specify each platform group that you want the operating system server to support.

Valid values for karch_value are sun4m, sun4u, and i86pc. For a detailed list of platform names and various systems, see Solaris 9 Sun Hardware Guide.

Note - You can use client_arch only when system_type is specified as server.

client_root Profile Keyword

client_root root_size

client_root defines the amount of root space, root_size in Mbytes, to allocate for each client. If you do not specify client_root in a server's profile, the installation software allocates 15 Mbytes of root space per client. The size of the client root area is used in combination with the num_clients keyword to determine how much space to reserve for the /export/root file system.

Note - You can use client_root only when system_type is specified as server.

client_swap Profile Keyword

client_swap swap_size

client_swap defines the amount of swap space, swap_size in Mbytes, to allocate for each diskless client. If you do not specify client_swap in the profile, 32 Mbytes of swap space is allocated by default.

Example:

client_swap 64

The example specifies that each diskless client is to have a swap space of 64 Mbytes.

Note - You can use client_swap only when system_type is specified as server.

How the Size of swap Is Determined

If a profile does not specify the size of swap, the JumpStart program determines the size of the swap space, based on the system's physical memory. Table 31-5 shows how the size of swap is determined during a custom JumpStart installation.

Table 31-5 Determining swap Size

The JumpStart program makes the size of swap no more than 20 percent of the disk where swap is located, unless the disk contains free space after laying out the other file systems. If free space exists, the JumpStart program allocates the free space to swap, and if possible, allocates the amount that is shown in Table 31-5.

Note - Physical memory plus swap space must total a minimum of 32 Mbytes.