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. Chapter 40, 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.
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.
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 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.
How the System's Root Disk Is Determined
A system's root disk is the disk on the system that contains the root (/) file system. In a profile, you can use the rootdisk variable in place of a disk name, which the JumpStart program sets to the system's root disk. Table 28-6 describes how the JumpStart program determines the system's root disk for the installation.
Note - The JumpStart program only determines a system's root disk size during an initial installation. You cannot change a system's root disk during an upgrade.
Table 28-6 How JumpStart Determines a System's Root Disk (Initial Installation)
Stage | Action |
|---|---|
1 | If the root_device keyword is specified in the profile, the JumpStart program sets rootdisk to the root device. |
2 | If rootdisk is not set and the boot_device keyword is specified in the profile, the JumpStart program sets rootdisk to the boot device. |
3 | If rootdisk is not set and a filesys cwtxdysz size / entry is specified in the profile, the JumpStart program sets rootdisk to the disk that is specified in the entry. |
4 | If rootdisk is not set and a rootdisk.sn entry is specified in the profile, the JumpStart program searches the system's disks in kernel probe order for an existing root file system on the specified slice. If a disk is found, the JumpStart program sets rootdisk to the found disk. |
5 | If rootdisk is not set and partitioning existing is specified in the profile, the JumpStart program searches the system's disks in kernel probe order for an existing root file system. If a root file system is not found or more than one is found, an error occurs. If a root file system is found, the JumpStart program sets rootdisk to the found disk. |
6 | If rootdisk is not set, the JumpStart program sets rootdisk to the disk where the root (/) file system is installed. |
system_type Profile Keyword
system_type type_switch |
system_type defines the type of system on which the Solaris environment is to be installed.
type_switch represents the option standalone or server, which you use to indicate the type of system on which the Solaris software is to be installed. If you do not specify system_type in a profile, standalone is used by default.
usedisk Profile Keyword
usedisk disk_name ... |
By default, the JumpStart program uses all of the operational disks on the system when you specify partitioning default. The usedisk profile keyword designates one or more disks that you want the JumpStart program to use. You must specify disk_name in the form cxtydz or cydz, for example, c0t0d0 or c0d0s0.
If you specify usedisk in a profile, the JumpStart program uses only the disks that you specify after the usedisk keyword.
Note - You cannot specify the usedisk keyword and the dontuse keyword in the same profile.
Custom JumpStart Environment Variables
You can use environment variables in your begin and finish scripts. For example, a begin script might extract the disk size, SI_DISKSIZES, and install or not install particular packages on a system, based on the actual disk size the script extracts.
Information that is gathered about a system is stored in these environment variables, which are generally set or not, depending on the rule keywords and values you use in the rules file.
For example, information about which operating system is already installed on a system is only available in SI_INSTALLED after the installed keyword is used.
Table 28-7 describes these variables and their values.
Table 28-7 Installation Environment Variables
Environment Variable | Value |
|---|---|
CHECK_INPUT | The path to the rules file in the JumpStart directory, which is mounted on /tmp/install_config/rules. |
HOME | The root's home directory during installation, which is /tmp/root. |
PATH | The shell search path during installation, which is /sbin:/usr/sbin/install.d:/usr:/usr/sbin:/usr/bin. |
SI_ARCH | The hardware architecture of the install client. The SI_ARCH variable is set when the arch keyword is used in the rules file. |
SI_BEGIN | The name of the begin script, if one is used. |
SI_CLASS | The name of the profile that is used to install the install client. |
SI_CONFIG_DIR | The path to the JumpStart directory, which is mounted on /tmp/instal_config. |
SI_CONFIG_FILE | The path to the rules file in the JumpStart directory, which is mounted on /tmp/install_config/rules. |
SI_CONFIG_PROG | The rules file. |
SI_CUSTOM_PROBES_FILE | The custom_probes.ok file, in which you can define your own rule and probe keywords. If you create a custom_probes.ok file, you can use the file to extend the list of default rule keywords, which are described in "Rule Keywords and Values". You can also use the file to extend the list of default probe keywords that are described in "Probe Keywords and Values". |
SI_DISKLIST | A comma-separated list of disk names on the install client. The SI_DISKLIST variable is set when the disksize keyword is used and matched in the rules file. The SI_DISKLIST and SI_NUMDISKS variables are used to determine the physical disk to use for the rootdisk. rootdisk is described in "How the System's Root Disk Is Determined". |
SI_DISKSIZES | A comma-separated list of disk sizes on the install client. The SI_DISKSIZES variable is set when the disksize keyword is used and matched in the rules file. |
SI_DOMAINNAME | The domain name. The SI_DOMAINNAME variable is set when the dommainname keyword is used and matched in the rules file. |
SI_FINISH | The name of the finish script, if one is used. |
SI_HOSTADDRESS | The install client's IP address. |
SI_HOSTID | The install client's Ethernet address. |
SI_HOSTNAME | The install client's host name. The SI_HOSTNAME variable is set when the hostname keyword is used and matched in the rules file. |
SI_INSTALLED | The device name of a disk with a specific operating system on the disk, for example, Solaris, SunOS, or System V. The SI_INSTALLED variable is set when the installed keyword is used and matched in the rules file. SI_INST_OS and SI_INST_VER are used to determine the value of SI_INSTALLED. |
SI_INST_OS | The name of the operating system. SI_INST_OS and SI_INST_VER are used to determine the value of SI_INSTALLED. |
SI_INST_VER | The version of the operating system. SI_INST_OS and SI_INST_VER are used to determine the value of SI_INSTALLED. |
SI_KARCH | The install client's kernel architecture. The SI_KARCH variable is set when the karch keyword is used and matched in the rules file. |
SI_MEMSIZE | The amount of physical memory on the install client. The SI_MEMSIZE variable is set when the memsize keyword is used and matched in the rules file. |
SI_MODEL | The install client's model name. The SI_MODEL variable is set when the model keyword is used and matched in the rules file. |
SI_NETWORK | The install client's network number. The SI_NETWORK variable is set when the network keyword is used and matched in the rules file. |
SI_NUMDISKS | The number of disks on an install client. The SI_NUMDISKS variable is set when the disksize keyword is used and matched in the rules file. The SI_NUMDISKS and SI_DISKLIST variables are used to determine the physical disk to use for the rootdisk. rootdisk is described in "How the System's Root Disk Is Determined". |
SI_OSNAME | The operating system release on the Solaris 9 software image. For example, you can use the SI_OSNAME variable in a script if you are installing the Solaris software on systems that are based on the version of the operating system on the Solaris 9 DVD or the Solaris 9 Software 1 of 2 CD image. |
SI_PROFILE | The path to the profile in the mounted JumpStart directory. The path is /tmp/install_config/profile_name. If you are creating a derived profile, SI_PROFILE is set to the /tmp/install.input file. |
SI_ROOTDISK | The device name of the disk that is represented by the logical name rootdisk. The SI_ROOTDISK variable is set when the disksize or the installed keyword is set to rootdisk in the rules file. |
SI_ROOTDISKSIZE | The size of the disk that is represented by the logical name rootdisk. The SI_ROOTDISKSIZE variable is set when the disksize or the installed keyword is set to rootdisk in the rules file. |
SI_SYS_STATE | The /a/etc/.sysIDtool.state file. You can edit this file in a finish script to prevent the sysidroot program from prompting for a root password before the system reboots. |
SI_TOTALDISK | The total amount of disk space on the install client. The SI_TOTALDISK variable is set when the totaldisk keyword is used and matched in the rules file. |
SHELL | The default shell during installation, which is /sbin/sh. |
TERM | The install client's terminal type. |
TZ | The default time zone, as specified in the NIS or NIS+ name service. |