Table 6-3 describes the keywords and values that you can use in the rules file.
Table 6-3 Descriptions of Rule Keywords and Values
Keyword |
Value |
Matches |
||
---|---|---|---|---|
minus sign (-) |
Anything (this keyword always succeeds). |
|||
processor_type Valid values for processor_type are:
|
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 c0d0, 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).
In this example, JumpStart attempts to match a system disk named c0t3d0 that can hold between 250 to 300 Mbytes of information.
In this example, JumpStart attempts to match first, a system disk that contains a preinstalled boot image, next the c0t3d0s0 disk, if it exists, and finally the first available disk that can hold between 750 Mbytes to 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 it might contain only 510 million bytes of disk space. JumpStart actually views the "535 Mbyte" disk as a 510 Mbyte disk because 535,000,000 / 1,048,576 = 510. So, a "535 Mbyte" disk would 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 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, JumpStart 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, Solaris_2.x, 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 later release that can be upgraded is matched. If JumpStart finds a Solaris release but is unable to determine the version, the version returned is SystemV. |
A disk that has a root (/) file system corresponding to a particular version of Solaris software.
In the example, JumpStart attempts to match a system that has a Solaris 8 root (/) file system on c0t3d0s1. |
|||
actual_platform_group Valid values are: sun4d, sun4m, sun4u, i86pc. (A list of systems and their corresponding platform group is presented in Appendix A, Platform Names and Groups.) |
A system's platform group. If you have a system 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).
The example tries to match a system with a physical memory size between 16 and 32 Mbytes. If you have a system 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 Appendix A, Platform Names and Groups 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). |
|||
network_num |
A system's network number, which JumpStart determines by performing a logical AND between the system's IP address and the subnet mask.
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_2.x |
A version of Solaris software already installed on a system.
In this example, custom JumpStart attempts to match a system with Solaris 7 already installed. |
|||
probe_keyword |
A valid probe or custom probe keyword.
The example returns the size of a system's disks (in Mbytes) in kernel probe order (c0t3d0s0, c0t3d0s1, c0t4d0s0, on a SPARC based system, for example) and sets the SI_DISKLIST, SI_DISKSIZES, SI_NUMDISKS, and SI_TOTALDISK environment variables. Note - The probe keyword is unique in that it doesn't attempt to match an attribute and consequently run a profile; it simply returns a value. Consequently, you cannot specify begin scripts, profiles, and finish scripts with the probe rule keyword. Probe keywords are described in Chapter 8, Creating Custom Rule and Probe Keywords. |
|||
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 attached to a system.
In this example, JumpStart 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 it might have only 510 million bytes of disk space. JumpStart actually views the "535 Mbyte" disk as a 510 Mbyte disk because 535,000,000 / 1,048,576 = 510. So, a "535 Mbyte" disk does not match a size_range equal to 530-550. |