Sun Microsystems, Inc.
spacerspacer
spacer www.sun.com docs.sun.com |
spacer
black dot
 
 
23.  Preparing Custom JumpStart Installations (Tasks) Testing a Profile To Test a Profile  Previous   Contents   Next 
   
 

Profile Test Examples

The following example shows how to use pfinstall to test a profile that is named basic_prof. The profile is tested against the disk configuration on a system on which the Solaris 9 software is installed. The basic_prof profile is located in the /jumpstart directory, and the path to the Solaris 9 Software 1 of 2 CD image is specified because Volume Manager is being used.

Example 23-5 Profile Test Using a Solaris 9 System

# cd /jumpstart
# /usr/sbin/install.d/pfinstall -D -c /cdrom/pathname basic_prof

The following example shows how to use pfinstall to test the profile that is named basic_prof on a Solaris 9 system. The test is performed against the 535_test disk configuration file. The test checks for 64 Mbytes of system memory. This example uses a Solaris 9 Software 1 of 2 CD image that is located in the /export/install directory.

Example 23-6 Profile Test Using a Disk Configuration File

# SYS_MEMSIZE=64
# export SYS_MEMSIZE
# /usr/sbin/install.d/pfinstall -d 535_test -c /export/install basic_prof

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 23-3 describes what the check script does.

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

Stage

Description

1

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.

2

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

3

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

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_9/Misc/jumpstart_sample directory on the Solaris 9 DVD or on the Solaris 9 Software 1 of 2 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 9 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 9 DVD or a Solaris 9 Software 1 of 2 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 custom JumpStart configuration is ok.

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

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

 		 
 
  Previous   Contents   Next