Validating the rules File

Before you can use a profile and rules file, you must run the check script to validate that the files are set up correctly. If all rules and profiles are correctly set up, the rules.ok file is created, which is required by the custom JumpStart installation software to match a system to a profile.

Table 3-2 describes what the check script does.

Table 3-2 What Happens When You Use the check Script

To Validate the rules File

1. Ensure that the check script is located in the JumpStart directory.

   ---

   Note - The check script is in the Solaris_10/Misc/jumpstart_sample directory on the Solaris Operating System DVD or on the Solaris Software - 1 CD.

   ---

2. Change the directory to the JumpStart directory.
3. Run the check script to validate the rules file:

   $ ./check -p path -r file_name

   -p path

   Validates the rules by using the check script from the Solaris 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 Operating System DVD or a Solaris Software - 1 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 one that is named rules. 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 following information.

   The custom JumpStart configuration is ok

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

See Also

After you validate the rules file, you can learn more about optional custom JumpStart features in Chapter 4, Using Optional Custom JumpStart Features (Tasks). You can learn about performing custom JumpStart installations in Chapter 6, Performing a Custom JumpStart Installation (Tasks).