How to Create the rules File

Overview - The procedure to create a rules file involves:

• Editing a file

• Selecting rule keywords and rule values for each group of workstations you want to install using custom JumpStart. Any workstations that match the rule keyword and rule value will be installed as specified by the corresponding profile.

  Follow this procedure to create a rules file.

1. As secadmin, at label admin_low, open the Admin Editor.

   See "To Create or Open a File from the Trusted Editor" if you are unfamiliar with the steps.

2. To edit the sample rules file:

   File to Edit: /jumpstart/rules

3. To create a rules file in /export/tmp:

   File to Edit: /export/tmp/rules

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

   Be aware of these things as you add rules to the rules file:

   • "Rule Examples" provides some examples of rules.

   • "Rule Keyword and Rule Value Descriptions" provides the list of valid rule keywords and values.

   • The rules file must have at least one rule

   • A rule must have at least a rule keyword, a rule value, and a corresponding profile.

   An individual rule in the rules file must have the following syntax:

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

   The fields of a rule are described below:

   Field Descriptions of a Rule

   !

   A symbol used before a rule keyword to indicate negation.

   [ ]

   A symbol used to indicate an optional expression or field.

   ...

   A symbol used to indicate the preceding expression may be repeated.

   &&

   A symbol that must be used to join (logically AND) rule keyword and rule value pairs together in the same rule. During a custom JumpStart installation, a workstation must match every pair in the rule before the rule matches.

   rule_keyword

   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 workstation with the same attribute to a profile. See "Rule Keyword and Rule Value Descriptions" for the list of rule keywords.

   rule_value

   A value that provides the specific system attribute for the corresponding rule keyword. See "Rule Keyword and Rule Value Descriptions" for the list of rule values.

   begin

   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

   A name of a text file used as a template that defines how to install Trusted Solaris on a workstation. 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

   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.

   This completes the procedure to create a rules file. To validate the rules file, see "How to Use check to Validate the rules File".