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)

4.  Using Optional JumpStart Features (Tasks)

5.  Creating Custom Rule and Probe Keywords (Tasks)

Probe Keywords

Creating a custom_probes File

Syntax of the custom_probes File

Syntax of Function Names in the custom_probes File

How to Create a custom_probes File

Validating the custom_probes File

How to Validate the custom_probes File

6.  Performing a JumpStart Installation (Tasks)

7.  Installing With JumpStart (Examples)

8.  JumpStart Keyword Reference

9.  Installing a ZFS Root Pool With JumpStart



Probe Keywords

A probe keywords are related to rule keywords. A rule keyword is a predefined lexical unit or word that describes a general system attribute, such as host name, hostname, or memory size, memsize. Rule keywords and the values that are associated with them enable you to match a system that has the same attribute to a profile. This match of a system's attributes defines how the Oracle Solaris software is to be installed on each system in the group.

JumpStart environment variables, which you use in begin and finish scripts, are set on demand. For example, information about which operating system is already installed on a system is only available in SI_INSTALLED after the installed rule keyword is used.

In some situations, you might need to extract the same information in a begin or finish script for a purpose other than to match a system and run a profile. Probe keywords provide the solution. Probe keywords extract attribute information and remove the need for you to set up a matching condition and run a profile.

For a list of probe keywords and values, see Probe Keywords and Values.