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)
6. Performing a JumpStart Installation (Tasks)
7. Installing With JumpStart (Examples)
8. JumpStart Keyword Reference
Profile Keywords Quick Reference
Profile Keyword Descriptions and Examples
Archive Stored on an NFS Server
Archive Stored on an HTTP or HTTPS Server
Archive Stored on an FTP Server
Archive Stored on a Local Tape
Archive Stored on a Local Device
Archive Stored on a Local File
boot_device Profile Keyword (UFS and ZFS)
bootenv Profile Keyword (UFS and ZFS)
How the Size of swap Is Determined
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)
package Profile Keyword (UFS and ZFS)
Packages Stored on an NFS Server
Packages Stored on an HTTP Server
Packages Stored on a Local Device
Packages Stored on a Local File
Limitations When Using the package Keyword
Upgrade Behavior When Using the package Keyword
Patches Stored on an NFS Server
Patches Stored on an HTTP Server
Patches Stored on a Local Device
Patches Stored on a Local File
Limitations When Using the patch Keyword
pool Profile Keyword (ZFS Only)
root_device Profile Keyword (UFS and ZFS)
How the System's Root Disk Is Determined
usedisk Profile Keyword (UFS and ZFS)
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.
The following table describes these variables and their values.
Table 8-9 Installation Environment Variables
|