Skip Navigation Links | |
Exit Print View | |
![]() |
Oracle Solaris 10 1/13 Installation Guide: JumpStart Installations Oracle Solaris 10 1/13 Information Library |
1. Where to Find Oracle Solaris Installation Planning Information
3. Preparing JumpStart Installations (Tasks)
4. Using Optional JumpStart Features (Tasks)
5. Creating Custom Rule and Probe Keywords (Tasks)
Syntax of the custom_probes File
Syntax of Function Names in the custom_probes File
How to Create a custom_probes File
6. Performing a JumpStart Installation (Tasks)
7. Installing With JumpStart (Examples)
8. JumpStart Keyword Reference
Before you can use a profile, rules, and custom_probes file, you must run the check script to validate that the files are set up correctly. If all profiles, rules, and probe and comparison functions are correctly set up, the rules.ok and custom_probes.ok files are created.
When you use the check script, the following process occurs:
check searches for a custom_probes file.
If the file exists, check creates the custom_probes.ok file from the custom_probes file, removes all comments and blank lines, and retains all Bourne shell commands, variables, and algorithms. Then, check adds the following comment line at the end:
# version=2 checksum=num
$ ./check -p path -r file-name
Validates the custom_probes file by using the check script from the Oracle Solaris software image for your platform 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 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.
Specifies a file name other than the one that is named custom_probes. By using the -r option, you can test the validity of a set of functions before integrating the functions into the custom_probes file.
As the check script runs, the script reports the validity of the rules and custom_probes files and each profile. If no errors are encountered, the script reports The JumpStart configuration is ok and creates the rules.ok and custom_probes.ok files in the JumpStart directory.
# chmod +x custom_probes