JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris 10 8/11 Installation Guide: Custom JumpStart and Advanced Installations     Oracle Solaris 10 8/11 Information Library
search filter icon
search icon

Document Information

Preface

Part I Using Custom JumpStart

1.  Where to Find Oracle Solaris Installation Planning Information

2.  Custom JumpStart (Overview)

3.  Preparing Custom JumpStart Installations (Tasks)

4.  Using Optional Custom JumpStart Features (Tasks)

5.  Creating Custom Rule and Probe Keywords (Tasks)

6.  Performing a Custom JumpStart Installation (Tasks)

7.  Installing With Custom JumpStart (Examples)

8.  Custom JumpStart (Reference)

Rule Keywords and Values

Profile Keywords and Values

Profile Keywords Quick Reference

Profile Keyword Descriptions and Examples

archive_location Keyword

backup_media Profile Keyword

boot_device Profile Keyword (UFS and ZFS)

bootenv Profile Keyword (UFS and ZFS)

client_arch Profile Keyword

client_root Profile Keyword

client_swap Profile Keyword

cluster Profile Keyword (Adding Software Groups) (UFS and ZFS)

cluster Profile Keyword (Adding or Deleting Clusters) (UFS and ZFS)

dontuse Profile Keyword (UFS and ZFS)

x86: fdisk Profile Keyword (UFS and ZFS)

filesys Profile Keyword (Mounting Remote File Systems) (UFS and ZFS)

filesys Profile Keyword (Creating Local File Systems)

filesys Profile Keyword (Creating RAID-1 Volumes)

forced_deployment Profile Keyword (Installing Flash Archive Differential Archives)

geo Profile Keyword (UFS and ZFS)

install_type Profile Keyword (UFS and ZFS)

layout_constraint Profile Keyword

local_customization Profile Keyword (Installing Flash Archives)

locale Profile Keyword (UFS and ZFS)

metadb Profile Keyword (Creating State Database Replicas)

no_content_check Profile Keyword (Installing Flash Archives)

no_master_check Profile Keyword (Installing Flash Archives)

num_clients Profile Keyword

package Profile Keyword (UFS and ZFS)

partitioning Profile Keyword

patch Profile Keyword

pool Profile Keyword (ZFS Only)

root_device Profile Keyword (UFS and ZFS)

system_type Profile Keyword

usedisk Profile Keyword (UFS and ZFS)

Custom JumpStart Environment Variables

Probe Keywords and Values

9.  Installing a ZFS Root Pool With JumpStart

Part II Appendices

A.  Troubleshooting (Tasks)

B.  Additional SVR4 Packaging Requirements (Reference)

Glossary

Index

Rule Keywords and Values

Table 8-1 describes the keywords and values that you can use in the rules file. For detailed instructions to create a rules file, see Creating the rules File.

Table 8-1 Descriptions of Rule Keywords and Values

Keyword
Value
Matches
any
minus sign (-)
Anything. The any keyword always succeeds.
arch
processor_type

Valid values for processor_type are the following:

  • SPARC: sparc

  • x86: i386

A system's processor type.

The uname -p command reports the system's processor type.

disksize
actual_disk_name size_range

actual_disk_name – A disk name in the form cxtydz, such as c0t3d0 or c0d0, or the special word rootdisk. If rootdisk is used, the disk to be matched is determined in the following order:

  • SPARC: The disk that contains the preinstalled boot image, which is a new SPARC based system with factory JumpStart, a feature of Oracle Solaris, installed

  • The c0t3d0s0 disk, if the disk exists

  • The first available disk that is searched in kernel probe order

size_range – The size of the disk, which must be specified as a range of Mbytes (x-x).


Note - When calculating size_range, remember that a MB equals 1,048,576 bytes. A disk might be advertised as a “535–MB” disk, but the disk might contain only 510 million bytes of disk space. The JumpStart program views the “535–MB” disk as a 510–MB disk because 535,000,000 / 1,048,576 = 510. A “535–MB” disk does not match a size_range equal to 530–550.


The name and size of a system's disk in MB.

Example:

disksize c0t3d0 250-300

In the example, the JumpStart program attempts to match a system disk that is named c0t3d0. The disk can hold between 250 and 300 MB of information.

Example:

disksize rootdisk 750-1000

In the example, the JumpStart program attempts to match a disk in the following order:

  1. A system disk that contains a preinstalled boot image

  2. The c0t3d0s0 disk, if the disk exists

  3. The first available disk that can hold between 750 MB and 1 GB of information

domainname
actual_domain_name
A system's domain name, which controls how a naming service determines information.

If you have a system already installed, the domainname command reports the system's domain name.

hostaddress
actual_IP_address
A system's IP address.
hostname
actual_host_name
A system's host name.

If you have a system that is already installed, the uname -n command reports the system's host name.

installed
slice version

slice – A disk slice name in the form cwtxdysz, such as c0t3d0s5, or the special words any or rootdisk. If any is used, the JumpStart program attempts to match all of the system's disks in kernel probe order. If rootdisk is used, the disk to be matched is determined in the following order:

  • SPARC: The disk that contains the preinstalled boot image, which is a new SPARC based system with factory JumpStart installed

  • The c0t3d0s0 disk, if the disk exists

  • The first available disk that is searched in kernel probe order

version – A version name or the special words any or upgrade. If any is used, any Oracle Solaris release is matched. If upgrade is used, any Oracle Solaris release that is supported and can be upgraded is matched.

If the JumpStart program finds a Oracle Solaris release but is unable to determine the version, the version that is returned is SystemV.

A disk that has a root (/) file system that corresponds to a particular version of Oracle Solaris software.

Example:

installed c0t3d0s1 Solaris 10

In the example, the JumpStart program attempts to match a system that has a Oracle Solaris root (/) file system on c0t3d0s1.

karch
actual_platform_group

Valid values are sun4u, i86pc, and prep. A list of systems and their corresponding platform group is presented in the Oracle Solaris Sun Hardware Platform Guide at http://www.oracle.com/technetwork/indexes/documentation/index.html.

A system's platform group.

If you have a system that is already installed, the arch -k command or the uname -m command reports the system's platform group.

memsize
physical_mem

The value must be a range of MB, x-x, or a single MB value.

A system's physical memory size in MB.

Example:

memsize 64-128

The example tries to match a system with a physical memory size between 64 and 128 MB.

If you have a system that is already installed, the output of the prtconf command, line 2, reports the system's physical memory size.

model
actual_platform_name
A system's platform name. See the Oracle Solaris Sun Hardware Platform Guide at http://www.oracle.com/technetwork/indexes/documentation/index.html for a list of valid platform names.

To find the platform name of an installed system, use the uname -i command or the output of the prtconf command, line 5.


Note - If the actual_platform_name contains spaces, you must replace spaces with underscores (_).

Example:

SUNW, Sun_4_50


network
network_num
A system's network number, which the JumpStart program determines by performing a logical AND between the system's IP address and the subnet mask.

Example:

network 192.168.2.0

The example tries to match a system with a 192.168.2.8 IP address, if the subnet mask is 255.255.255.0.

osname
Solaris_x
A version of Oracle Solaris software that is already installed on a system.

Example:

osname Solaris 10

In the example, the JumpStart program attempts to match a system with the Oracle Solaris 10 8/11 OS already installed.

probe
probe_keyword
A valid probe keyword or a valid custom probe keyword.

Example:

probe disks

The example returns the size of a system's disks in MB and in kernel probe order, for example, c0t3d0s1, c0t4d0s0, on a SPARC based system. The JumpStart program sets the SI_DISKLIST, SI_DISKSIZES, SI_NUMDISKS, and SI_TOTALDISK environment variables.


Note - The probe keyword is unique in that the keyword does not attempt to match an attribute and run a profile. The probe keyword returns a value. Consequently, you cannot specify begin scripts, profiles, and finish scripts with the probe rule keyword.


Probe keywords are described in Chapter 5, Creating Custom Rule and Probe Keywords (Tasks).

totaldisk
size_range

The value must be specified as a range of MB (x-x).


Note - When calculating size_range, remember that one MB equals 1,048,576 bytes. A disk might be advertised as a “535–MB” disk, but the disk might have only 510 million bytes of disk space. The JumpStart program views the “535–MB” disk as a 510–MB disk because 535,000,000 / 1,048,576 = 510. A “535–MB” disk does not match a size_range equal to 530–550.


The total disk space on a system in MB. The total disk space includes all the operational disks that are attached to a system.

Example:

totaldisk 300-500

In the example, the JumpStart program tries to match a system with a total disk space between 300 and 500 MB.