JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris 10 1/13 Installation Guide: JumpStart Installations     Oracle Solaris 10 1/13 Information Library
search filter icon
search icon

Document Information


1.  Where to Find Oracle Solaris Installation Planning Information

2.  JumpStart (Overview)

3.  Preparing JumpStart Installations (Tasks)

Task Map: Preparing JumpStart Installations

Creating a Profile Server for Networked Systems

How to Create a JumpStart Directory on a Server

Allowing All Systems Access to the Profile Server

Using a Wildcard Entry to Allow All Systems Access to the Profile Server

Creating a Profile Diskette for Stand-alone Systems

SPARC: How to Create a Profile Diskette

x86: How to Create a Profile Diskette With GRUB

Creating the rules File

Syntax of the rules File

How to Create a rules File

rules File Example

Creating a Profile

Syntax of Profiles

How to Create a Profile

Profile Examples

Testing a Profile

How to Create a Temporary Oracle Solaris Environment to Test a Profile

How to Test a Profile

Profile Test Example

Validating the rules File

How to Validate the rules File

4.  Using Optional JumpStart Features (Tasks)

5.  Creating Custom Rule and Probe Keywords (Tasks)

6.  Performing a JumpStart Installation (Tasks)

7.  Installing With JumpStart (Examples)

8.  JumpStart Keyword Reference

9.  Installing a ZFS Root Pool With JumpStart



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 JumpStart installation software to match a system to a profile.

The following table 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.
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

How 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 Oracle Solaris Operating System DVD or on the Oracle 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 Oracle 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 Oracle Solaris Operating System DVD or an Oracle Solaris Software - 1 CD.

    Use this option to run the most recent version of check if your system is running a previous version of Oracle 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 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 JumpStart features in Chapter 4, Using Optional JumpStart Features (Tasks). You can learn about performing JumpStart installations in Chapter 6, Performing a JumpStart Installation (Tasks).