openSolaris 2008 - Rule Keywords and Values - Solaris Express Installation Guide: Custom JumpStart and Advanced Installations

Rule Keywords and Values

Table 8-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 8-1 Descriptions of Rule Keywords and Values

Keyword	Value	Matches
`any`	minus sign (`-`)	Anything. The `any` keyword always succeeds.
`arch`	processor_type Valid values for processor_type are the following: SPARC: `sparc` x86: `i386`	A system's processor type. The `uname -p` command reports the system's processor type.
`disksize`	actual_disk_name size_range actual_disk_name – A disk name in the form `c`x`t`y`d`z, 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: SPARC: The disk that contains the preinstalled boot image, which is a new SPARC based system with factory JumpStart installed The `c0t3d0s0` disk, if the disk exists The first available disk that is searched in kernel probe order size_range – The size of the disk, which must be specified as a range of Mbytes (x-x). 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.	The name and size of a system's disk in Mbytes. Example: disksize c0t3d0 250-300 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: disksize rootdisk 750-1000 In the example, the JumpStart program attempts to match a disk in the following order: A system disk that contains a preinstalled boot image The `c0t3d0s0` disk, if the disk exists The first available disk that can hold between 750 Mbytes and 1 Gbyte of information
`domainname`	actual_domain_name	A system's domain name, which controls how a naming service determines information. If you have a system already installed, the `domainname` command reports the system's domain name.
`hostaddress`	actual_IP_address	A system's IP address.
`hostname`	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.
`installed`	slice version slice – A disk slice name in the form `c`w`t`x`d`y`s`z, 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: SPARC: The disk that contains the preinstalled boot image, which is a new SPARC based system with factory JumpStart installed The `c0t3d0s0` disk, if the disk exists The first available disk that is searched in kernel probe 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 release that is supported and 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: installed c0t3d0s1 Solaris 11 In the example, the JumpStart program attempts to match a system that has a Solaris root (`/`) file system on `c0t3d0s1`.
`karch`	actual_platform_group Valid values are `sun4u`, `i86pc`, and `prep`. A list of systems and their corresponding platform group is presented in the Solaris Sun Hardware Platform Guide at https://docs.sun.com.	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.
`memsize`	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: memsize 64-128 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.
`model`	actual_platform_name	A system's platform name. See the Solaris Sun Hardware Platform Guide at https://docs.sun.com 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`	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: network 192.168.2.0 The example tries to match a system with a 192.168.2.8 IP address, if the subnet mask is 255.255.255.0.
`osname`	`Solaris_`x	A version of Solaris software that is already installed on a system. Example: osname Solaris 11 In the example, the JumpStart program attempts to match a system with the Solaris Express 5/07 OS already installed.
`probe`	probe_keyword	A valid probe keyword or a valid custom probe keyword. Example: probe disks The example returns the size of a system's disks in Mbytes and in kernel probe order, for example, `c0t3d0s1`, `c0t4d0s0`, on a SPARC based system. 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 5, Creating Custom Rule and Probe Keywords (Tasks).
`totaldisk`	size_range The value must be specified as a range of Mbytes (x-x). 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.	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: totaldisk 300-500 In the example, the JumpStart program tries to match a system with a total disk space between 300 and 500 Mbytes.