The rules file must have the following attributes:
The rules file can contain any of the following:
Commented text
Any text that is included after the # symbol on a line is treated by JumpStart as commented text. If a line begins with the # symbol, the entire line is treated as a comment.
One or more blank lines
One or more multiline rules
To continue a single rule onto a new line, include a backslash character (\) just before pressing Return.
A rule within a rules file must adhere to the following syntax:
!rule-keyword rule-value && !rule-keyword rule-value ... begin profile finish |
A symbol that is used before a keyword to indicate negation.
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.
A value that provides the specific system attribute for the corresponding rule-keyword. Rule values are described in the section, Rule Keywords and Values in Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations.
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 in Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations.
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 in Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations.
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