Solaris 8 Advanced Installation Guide

Validating the rules File

Before you can use a profile and rules file, you must run the check script to validate that these 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 18–8 describes what the check script does.

Table 18–8 What Happens When You Use check

Stage 

Description 

The rules file is checked for syntax.

 

check makes sure that the rule keywords are legitimate, and the begin, class, and finish fields are specified for each rule (the begin and finish fields can consist of a minus sign (-) instead of a file name).

If no errors are found in the rules file, each profile specified in the rules is checked for syntax.

If no errors are found, check creates the rules.ok file from the rules file, removes all comments and blank lines, retains all rules, and adds the following comment line at the end:

# version=2 checksum=num


Note –

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


Syntax of check

This is the syntax of the check script you use to test a rules file:


$ ./check [[-p path]] [[-r file_name]]

Table 18–9 Description of check Script Arguments

Argument 

Description 

-p path

Validates the rules file by using the check script from the Solaris 8 Software 1 of 2 SPARC Platform Edition or Solaris 8 Software 1 of 2 Intel Platform Edition CD image, instead of the check script from the system you are using. path is the image on a local disk or a mounted Solaris 8 Software 1 of 2 SPARC Platform Edition or Solaris 8 Software 1 of 2 Intel Platform Edition 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 named rules. Using this option, you can test the validity of a rule before integrating it into the rules file.

To Validate the rules File

  1. Make sure that the check script is located in the JumpStart directory.


    Note –

    The check script is in the Solaris_8/Misc/jumpstart_sample directory on the Solaris 8 Software 1 of 2 SPARC Platform Edition, or the Solaris 8 Software 1 of 2 Intel Platform Edition CD.


  2. Change directory to the JumpStart directory.

  3. Run the check script to validate the rules file:


    $ ./check [[-p path -r file_name]]

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

Once you've validated the rules file, you can learn more about optional custom JumpStart features in Chapter 19, Using Optional Custom JumpStart Features and about performing custom JumpStart installations in Chapter 21, Performing a Custom JumpStart Installation.