Custom JumpStart (Reference)
This chapter lists keywords and values that you can use in the rules file, profiles, and begin and finish scripts.
Rule Keywords and Values
Table 28-1 describes the keywords and values that you can use in the rules file. For detailed instructions to create a rules file, see "Creating the rules File".
Table 28-1 Descriptions of Rule Keywords and Values
Keyword | Value | Matches | ||
---|---|---|---|---|
minus sign (-) | Anything. The any keyword always succeeds. | |||
processor_type The valid value for processor_type is sparc | A system's processor type. The uname -p command reports the system's processor type. | |||
actual_disk_name size_range actual_disk_name -- A disk name in the form cxtydz, such as c0t3d0, or the special word rootdisk. If rootdisk is used, the disk to be matched is determined in the following order:
size_range - The size of the disk, which must be specified as a range of Mbytes (x-x). | The name and size of a system's disk in Mbytes. Example:
In the example, the JumpStart program attempts to match a system disk that is named c0t3d0. The disk can hold between 250 and 300 Mbytes of information. Example:
In the example, the JumpStart program first attempts to match a system disk that contains a preinstalled boot image. Next, the JumpStart program attempts to match the c0t3d0s0 disk, if the disk exists. Finally, the JumpStart program attempts to match the first available disk that can hold between 750 Mbytes and 1 Gbyte of information. Note - When calculating size_range, remember that a Mbyte equals 1,048,576 bytes. A disk might be advertised as a "535-Mbyte" disk, but the disk might contain only 510 million bytes of disk space. The JumpStart program views the "535-Mbyte" disk as a 510-Mbyte disk because 535,000,000 / 1,048,576 = 510. A "535-Mbyte" disk does not match a size_range equal to 530-550. | |||
actual_domain_name | A system's domain name, which controls how a name service determines information. If you have a system already installed, the domainname command reports the system's domain name. | |||
actual_IP_address | A system's IP address. | |||
actual_host_name | A system's host name. If you have a system that is already installed, the uname -n command reports the system's host name. | |||
slice version slice - A disk slice name in the form cwtxdysz, such as c0t3d0s5, or the special words any or rootdisk. If any is used, the JumpStart program attempts to match all of the system's disks in kernel probe order. If rootdisk is used, the disk to be matched is determined in the following order:
version - A version name or the special words any or upgrade. If any is used, any Solaris or SunOS release is matched. If upgrade is used, any Solaris 2.1 or compatible release that can be upgraded is matched. If the JumpStart program finds a Solaris release but is unable to determine the version, the version that is returned is SystemV. | A disk that has a root (/) file system that corresponds to a particular version of Solaris software. Example:
In the example, the JumpStart program attempts to match a system that has a Solaris 9 root (/) file system on c0t3d0s1. | |||
actual_platform_group Valid values are sun4m, sun4u, prep. A list of systems and their corresponding platform group is presented in the Solaris 9 Sun Hardware Platform Guide. | A system's platform group. If you have a system that is already installed, the arch -k command or the uname -m command reports the system's platform group. | |||
physical_mem The value must be a range of Mbytes , x-x, or a single Mbyte value. | A system's physical memory size in Mbytes. Example:
The example tries to match a system with a physical memory size between 64 and 128 Mbytes. If you have a system that is already installed, the output of the prtconf command, line 2, reports the system's physical memory size. | |||
actual_platform_name | A system's platform name. See the Solaris 9 Sun Hardware Platform Guide for a list of valid platform names. To find the platform name of an installed system, use the uname -i command or the output of the prtconf command, line 5. Note - If the actual_platform_name contains spaces, you must replace spaces with underscores (_). Example: SUNW,Sun_4_50 | |||
network_num | A system's network number, which the JumpStart program determines by performing a logical AND between the system's IP address and the subnet mask. Example:
The example tries to match a system with a 193.144.2.8 IP address, if the subnet mask is 255.255.255.0. | |||
Solaris_x | A version of Solaris software that is already installed on a system. Example:
In the example, the JumpStart program attempts to match a system with the Solaris 9 operating environment already installed. | |||
probe_keyword | A valid probe keyword or a valid custom probe keyword. Example:
The example returns the size of a system's disks in Mbytes and in kernel probe order, for example, c0t3d0s1, c0t4d0s0. The JumpStart program sets the SI_DISKLIST, SI_DISKSIZES, SI_NUMDISKS, and SI_TOTALDISK environment variables. Note - The probe keyword is unique in that the keyword does not attempt to match an attribute and run a profile. The probe keyword returns a value. Consequently, you cannot specify begin scripts, profiles, and finish scripts with the probe rule keyword. Probe keywords are described in Chapter 25, Creating Custom Rule and Probe Keywords (Tasks). | |||
size_range The value must be specified as a range of Mbytes (x-x). | The total disk space on a system in Mbytes. The total disk space includes all the operational disks that are attached to a system. Example:
In the example, the JumpStart program tries to match a system with a total disk space between 300 and 500 Mbytes. Note - When calculating size_range, remember that one Mbyte equals 1,048,576 bytes. A disk might be advertised as a "535-Mbyte" disk, but the disk might have only 510 million bytes of disk space. The JumpStart program views the "535-Mbyte" disk as a 510-Mbyte disk because 535,000,000 / 1,048,576 = 510. A "535-Mbyte" disk does not match a size_range equal to 530-550. |
Profile Keywords and Values
This section describes the profile keywords and values that you can use in a profile. For detailed instructions to create a profile, see "Creating a Profile".
Profile Keywords at a Glance
Table 28-2 provides a quick way to determine which keywords you can use, based on your installation scenario. Unless otherwise noted in the keyword descriptions, the keyword can only be used with the initial installation option.
Table 28-2 Overview of Profile Keywords
Installation Scenarios | |||||
---|---|---|---|---|---|
Profile Keywords | Standalone System (Non-Networked) | Standalone System (Networked) or Server | OS Server | Upgrade | Upgrade With Disk Space Reallocation |
archive_location | |||||
backup_media | |||||
boot_device | |||||
client_arch | |||||
client_root | |||||
client_swap | |||||
cluster (adding software groups) | |||||
cluster (adding or deleting clusters) | |||||
dontuse | |||||
filesys (mounting remote file systems) | |||||
filesys (creating local file systems) | |||||
geo | |||||
install_type | |||||
isa_bits | |||||
layout_constraint | |||||
locale | |||||
num_clients | |||||
package | |||||
partitioning |
|
| |||
root_device | |||||
system_type |
|
| |||
usedisk |
Profile Keyword Descriptions and Examples
archive_location Keyword
archive_location retrieval_type location |
The values of retrieval_type and location depend on where the Web Start Flash archive is stored. The following sections contain the values you can use for retrieval_type and location and examples of how to use the archive_location keyword.
NFS Server
If the archive is stored on an NFS server, use the following syntax for the archive_location keyword.
archive_location nfs server_name:/path/filename retry n |
server_name | The name of the server where you stored the archive. |
path | The location of the archive to be retrieved from the specified server. If the path contains $HOST, the Web Start Flash installation utilities replace $HOST with the name of the clone system that you are installing. |
filename | The name of the Web Start Flash archive file. |
retry n | An optional keyword. n is the maximum number of times the Web Start Flash utilities attempt to mount the archive. |
Examples:
archive_location nfs golden:/archives/usrarchive archive_location nfs://golden/archives/usrarchive |