For a list of rules file keywords and values, see Rule Keywords and Values.
!rule_keyword rule_value && !rule_keyword rule_value ... begin profile finish
A predefined lexical unit or word that describes a general system attribute, such as host name, hostname, or memory size, memsize. rule_keyword is used with the rule value to match a system with the same attribute to a profile. For the list of rule keywords, see Rule Keywords and Values.
A value that provides the specific system attribute for the corresponding rule keyword. Rule values are described in Rule Keywords and Values.
A symbol you must use to join rule keyword and rule value pairs in the same rule (a logical AND). During a custom JumpStart installation, a system must match every pair in the rule before the rule matches.
The name of an optional Bourne shell script that can be executed before the installation begins. If no begin script exists, you must type a minus sign (-) in this field. All begin scripts must be located in the JumpStart directory.
Information about how to create begin scripts is presented in Creating Begin Scripts.
The name of a text file that defines how the Solaris software is to be installed on the system when a system matches the rule. The information in a profile consists of profile keywords and their corresponding profile values. All profiles must be located in the JumpStart directory.
The name of an optional Bourne shell script that can be executed after the installation is completed. If no finish script exists, you must type a minus sign (-) in this field. All finish scripts must be located in the JumpStart directory.
Information about how to create finish scripts is presented in Creating Finish Scripts.
At the minimum, each rule must contain the following:
A keyword, a value, and a corresponding profile
A minus sign (-) in the begin and finish fields if no begin or finish scripts are specified
Save the rules file in the JumpStart directory.
Ensure that root owns the rules file and that the permissions are set to 644.