Solaris 10 Installation Guide for IBM BladeCenter Servers

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. This file is required by the custom JumpStart installation software to match a system to a profile.

The following table describes what the check script does.

Table 1–4 check Script Functions

Stage 

Description 

The rules file is checked for correctness of syntax.

 

check verifies that the rule keywords are legitimate and that 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 that is specified in the rules is checked for correct syntax.

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

# version=2 checksum=num

ProcedureHow to Validate the rules File

The check script is in the Solaris_Solaris_version/Misc/jumpstart_sample directory on the Solaris Software DVD or the Solaris Software 1 – CD.

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


    Note –

    The check script is in the Solaris_Solaris_version/Misc/jumpstart_sample directory on the Solaris 10 Software DVD or on the Solaris Software - 1 CD.


  2. Change to the JumpStart directory.

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


    $ ./check -p path -r filename
    
    -p path

    Validates the rules by using the check script from the Solaris 10 software image instead of the check script from the system you are using. path is the image on a local disk or a mounted on the Solaris 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 filename

    Specifies a rules file other than the file 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 on the validity of the rules file and each profile. If no errors are reported, the script generates the following:


    The custom JumpStart configuration is ok
  4. Ensure that root owns the rules.ok file and that the permissions are set to 644.