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
The rules file is checked for 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 syntax.
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
To Validate the rules File
- Ensure that the check script is located in the JumpStart directory.
Note - The check script is in the Solaris_11/Misc/jumpstart_sample directory on the Solaris Operating
System DVD or on the Solaris Software - 1 CD.
- Change the directory to the JumpStart directory.
- 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
- Ensure that root owns the rules.ok file and that the permissions are set
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).