How to Create the rules File

1. Open a new text file (it must be named rules) using the editor of your choice.

   You can create a new rules file or edit the sample rules file provided in the JumpStart directory you created.

2. Add a rule in the rules file for each group of systems you want to install using custom JumpStart.

   Refer to the following information as you add rules to the rules file:

   • "Important Information About the rules File"

   • "Rule Examples"

   • Table 8-2

   A rule within the rules file must have the following syntax:

   [!]rule_keyword rule_value [&& [!]rule_keyword rule_value]... begin profile finish

   !	Is a symbol used before a rule keyword to indicate negation.
   [ ]	Is a symbol used to indicate an optional expression or field.
   ...	Is a symbol used to indicate the preceding expression may be repeated.
   rule_keyword	Is a predefined keyword that describes a general system attribute, such as host name (hostname) or memory size (memsize). It is used with the rule value to match a system with the same attribute to a profile. See Table 8-2 for the list of rule keywords.
   rule_value	Is a value that provides the specific system attribute for the corresponding rule keyword. See Table 8-2 for the list of rule values.
   &&	Is a symbol that must be used to join rule keyword and rule value pairs together 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.
   begin	Is a name of an optional Bourne shell script that can be executed before the installation begins. If no begin script exists, you must enter a minus sign (-) in this field. All begin scripts must reside in the JumpStart directory. See "Creating Begin Scripts" for detailed information on how to create begin scripts.
   profile	Is a name of a text file that defines how the Solaris software will 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 reside in the JumpStart directory.  Note - There are optional ways to use the profile field, which are described in "Using a Site-Specific Installation Program" and "Creating Derived Profiles With Begin Scripts".
   finish	Is a name of an optional Bourne shell script that can be executed after the installation completes. If no finish script exists, you must enter a minus sign (-) in this field. All finish scripts must reside in the JumpStart directory.   See "Creating Finish Scripts" for detailed information on how to create finish scripts.

3. Save the rules file into the JumpStart directory.

   The rules file should be owned by root and have permissions equal to 644.

Where to Go Next

This completes the procedure to create a rules file. To create profiles, go to "Creating a Profile".