local_customization Profile Keyword (Installing Solaris Flash Archives)

local_customization local directory

Before you install a Solaris Flash archive on a clone system, you can create custom scripts to preserve local configurations on the clone system. The local_customization keyword designates the directory where you have stored these scripts. local directory is the path to the script on the clone system. For information on predeployment and postdeployment scripts, see Creating Customization Scripts.

locale Profile Keyword

locale locale_name

Note - You can use locale with both the initial installation and upgrade options.

locale designates the locale packages you want to install or add when upgrading for the specified locale_name. The locale_name values are the same as those values that are used for the $LANG environment variable. Appendix D, Locale Values (Reference) contains a list of valid locale values.

When you use the local keyword, consider the following:

• If you have preconfigured a default locale, the locale is automatically installed. The English language packages are installed by default.

• You can specify a locale keyword for each locale you need to add to a system.

metadb Profile Keyword (Creating State Database Replicas)

metadb slice [size size-in-blocks] [count number-of-replicas]

The metadb keyword enables you to create Solaris Volume Manager state database replicas (metadbs) during your custom JumpStart installation. You can use the metadb keyword multiple times in your profile file to create state database replicas on different disk slices.

For more information about creating Solaris Volume Manager state database replicas during your installation, see State Database Replicas Guidelines and Requirements.

no_content_check Profile Keyword (Installing Solaris Flash Archives)

no_content_check

When installing a clone system with a Solaris Flash differential archive, you can use the no_content_check keyword to ignore file-by-file validation. File-by-file validation ensures that the clone system is a duplicate of the master system. Avoid using this keyword unless you are sure the clone system is a duplicate of the original master system.

Caution - If you use no_content_check, all new files are deleted to bring the clone system to the expected state. If you are not certain that you want files deleted, use the default which protects new files by stopping the installation.

no_master_check Profile Keyword (Installing Solaris Flash Archives)

no_master_check

When installing a clone system with a Solaris Flash differential archive, you can use the no_master_check keyword to ignore checking the clone system to make sure it was built from the original master system. Avoid using this keyword unless you are sure the clone system is a duplicate of the original master system. For information on installing Solaris Flash differential archives, see To Prepare to Install a Solaris Flash Archive With a Custom JumpStart Installation.

num_clients Profile Keyword

num_clients client_num

When a server is installed, space is allocated for each diskless client's root (/) and swap file systems. num_clients defines the number of diskless clients, client_num, that a server supports. If you do not specify num_clients in the profile, five diskless clients are allocated by default.

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

package Profile Keyword

package package_name [add_delete_switch]

Note - You can use package with both the initial installation and upgrade options.

package designates whether a package is to be added to or deleted from the software group that is to be installed on the system.

You must specify package_name in the form SUNWname. To view detailed information about packages and their names, on an installed system, use the pkginfo -l command.

add_delete_switch represents the option add or delete, which you use to indicate whether to add or delete the specified package. If you do not specify add_delete_switch, add is used by default.

Note - Some packages are required and cannot be deleted. You cannot individually add or delete localization packages by using the package profile keyword. To add localization packages, use the locale profile keyword.

When you use package for an upgrade, the JumpStart program performs the following actions:

• All packages already on the system are automatically upgraded.

• If you specify package_name add and package_name is not installed on the system, the package is installed.

• If you specify package_name delete and package_name is installed on the system, the package is deleted before the upgrade begins.

• If you specify package_name delete and package_name is not installed on the system, the package is not installed if the package is part of a cluster that is designated to be installed.

partitioning Profile Keyword

partitioning type

partitioning defines how the disks are divided into slices for file systems during the installation.

type - Use one of the following values:

• default - The JumpStart program selects the disks and creates the file systems on which to install the specified software, except for any file systems that are specified by the filesys keywords. rootdisk is selected first. The JumpStart program uses additional disks if the specified software does not fit on rootdisk.

• existing - The JumpStart program uses the existing file systems on the system's disks. All file systems except /, /usr, /usr/openwin, /opt, and /var are preserved. The JumpStart program uses the last mount-point field from the file system superblock to determine which file system mount point the slice represents.

  ---

  Note - When you use both the filesys and partitioning existing profile keywords, you must set size size to existing.

  ---

• explicit - The JumpStart program uses the disks and creates the file systems that are specified by the filesys keywords. If you specify only the root (/) file system with the filesys keyword, all of the Solaris software is installed in the root (/) file system.

  ---

  Note - If you use the explicit profile value, you must use the filesys keyword to specify the disks to use and file systems to create.

  ---

If you do not specify partitioning in the profile, the default type of partitioning is used by default.

root_device Profile Keyword

root_device slice

Note - You can use root_device with both the initial installation and upgrade options.

root_device designates the system's root disk. How the System's Root Disk Is Determined contains additional information.

When you are upgrading a system, root_device designates the root (/) file system and the file systems that are mounted by its /etc/vfstab file to be upgraded. You must specify root_device if more than one root (/) file system can be upgraded on a system. You must specify slice in the form cwtxdysz or cxdysz.

Example:

root_device c0t0d0s2

When you use the root_device keyword, consider the following:

• If you specify root_device on a system with only one disk, the root_device and the disk must match. Also, any filesys keywords that specify the root (/) file system must match root_device.

• If you are upgrading a RAID-1 volume (mirror), the value that is specified for root_device should be one side of the mirror. The other side of the mirror is automatically upgraded.