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

Custom JumpStart Environment Variables

You can use environment variables in your begin and finish scripts. For example, a begin script might extract the disk size, SI_DISKSIZES, and install or not install particular packages on a system, based on the actual disk size the script extracts.

Information that is gathered about a system is stored in these environment variables, which are generally set or not, depending on the rule keywords and values you use in the rules file.

For example, information about which operating system is already installed on a system is only available in SI_INSTALLED after the installed keyword is used.

Table 8-9 describes these variables and their values.

Table 8-9 Installation Environment Variables

Environment Variable
Value
SI_ARCH
The hardware architecture of the install client. The SI_ARCH variable is set when the arch keyword is used in the rules file.
SI_BEGIN
The name of the begin script, if one is used.
SI_CLASS
The name of the profile that is used to install the install client.
SI_DISKLIST
A comma-separated list of disk names on the install client. The SI_DISKLIST variable is set when the disksize keyword is used and matched in the rules file. The SI_DISKLIST and SI_NUMDISKS variables are used to determine the physical disk to use for the rootdisk. rootdisk is described in How the System's Root Disk Is Determined.
SI_DISKSIZES
A comma-separated list of disk sizes on the install client. The SI_DISKSIZES variable is set when the disksize keyword is used and matched in the rules file.
SI_DOMAINNAME
The domain name. The SI_DOMAINNAME variable is set when the dommainname keyword is used and matched in the rules file.
SI_FINISH
The name of the finish script, if one is used.
SI_HOSTADDRESS
The install client's IP address.
SI_HOSTNAME
The install client's host name. The SI_HOSTNAME variable is set when the hostname keyword is used and matched in the rules file.
SI_INSTALLED
The device name of a disk with a specific operating system on the disk, for example, Oracle Solaris or System V. The SI_INSTALLED variable is set when the installed keyword is used and matched in the rules file. SI_INST_OS and SI_INST_VER are used to determine the value of SI_INSTALLED.
SI_INST_OS
The name of the operating system. SI_INST_OS and SI_INST_VER are used to determine the value of SI_INSTALLED.
SI_INST_VER
The version of the operating system. SI_INST_OS and SI_INST_VER are used to determine the value of SI_INSTALLED.
SI_KARCH
The install client's kernel architecture. The SI_KARCH variable is set when the karch keyword is used and matched in the rules file.
SI_MEMSIZE
The amount of physical memory on the install client. The SI_MEMSIZE variable is set when the memsize keyword is used and matched in the rules file.
SI_MODEL
The install client's model name. The SI_MODEL variable is set when the model keyword is used and matched in the rules file.
SI_NETWORK
The install client's network number. The SI_NETWORK variable is set when the network keyword is used and matched in the rules file.
SI_NUMDISKS
The number of disks on an install client. The SI_NUMDISKS variable is set when the disksize keyword is used and matched in the rules file. The SI_NUMDISKS and SI_DISKLIST variables are used to determine the physical disk to use for the rootdisk. rootdisk is described in How the System's Root Disk Is Determined.
SI_OSNAME
The operating system release on the Oracle Solaris software image. For example, you can use the SI_OSNAME variable in a script if you are installing the Oracle Solaris software on systems that are based on the version of the operating system on the Oracle Solaris Operating System DVD or the Oracle Solaris Software - 1 CD image.
SI_ROOTDISK
The device name of the disk that is represented by the logical name rootdisk. The SI_ROOTDISK variable is set when the disksize or the installed keyword is set to rootdisk in the rules file. The SI_ROOTDISK variable sets the device to boot from during the installation.

Note - You cannot set the place of installation by using the probe keyword “rootdisk” in the rules file. For information on the “rootdisk” variable that is set in a JumpStart profile, see How the System's Root Disk Is Determined.


SI_ROOTDISKSIZE
The size of the disk that is represented by the logical name rootdisk. The SI_ROOTDISKSIZE variable is set when the disksize or the installed keyword is set to rootdisk in the rules file.
SI_TOTALDISK
The total amount of disk space on the install client. The SI_TOTALDISK variable is set when the totaldisk keyword is used and matched in the rules file.