Creating the rules File

The rules file is a text file that contains a rule for each group of systems on which you want to install the Solaris operating environment. Each rule distinguishes a group of systems that are based on one or more system attributes. Each rule also links each group to a profile. A profile is a text file that defines how the Solaris software is to be installed on each system in the group. For example, the following rule specifies that the JumpStart program use the information in the basic_prof profile to install any system with the sun4u platform group.

karch sun4u - basic_prof -

The rules file is used to create the rules.ok file, which is required for custom JumpStart installations.

For detailed information about how to create a rules file, see Creating the rules File.

To Create a rules File

1. On the install server, create a text file that is named rules.

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

   For detailed information about how to create a rules file, see Creating the rules File.

3. Save the rules file on the install server.

4. Validate the rules file.

   $ ./check [[-p path -r file-name]]

   -p path

   Validates the rules by using the check script from the Solaris 9 software image instead of the check script from the system you are using. path is the image on a local disk or a mounted Solaris DVD or a Solaris Software 1 of 2 CD.

   Use this option to run the most recent version of check if your system is running a previous version of Solaris.

   -r file_name

   Specifies a rules file other than the file that is named rules. By using this option, you can test the validity of a rule before you integrate the rule into the rules file.

   As the check script runs, the script reports the checking of the validity of the rules file and each profile. If no errors are encountered, the script reports: The custom JumpStart configuration is ok. The check script creates the rules.ok file.

5. Save the rules.ok file in a location that is accessible to the WAN boot server.

   Save the file to one of the following locations.

   • If the WAN boot server and install server are hosted on the same machine, save this file to the flash subdirectory of the document root directory on the WAN boot server.

   • If the WAN boot server and install server are not on the same machine, save this file to the flash subdirectory of the document root directory of the install server.

6. Ensure that root owns the rules.ok file and that the permissions are set to 644.

For examples of rules files, see rules File Example.