Skip Navigation Links | |
Exit Print View | |
![]() |
Oracle Solaris 10 9/10 Installation Guide: Custom JumpStart and Advanced Installations |
1. Where to Find 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)
Profile Keywords Quick Reference
Profile Keyword Descriptions and Examples
boot_device Profile Keyword (UFS and ZFS)
bootenv Profile Keyword (UFS and ZFS)
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 Solaris Flash Differential Archives)
geo Profile Keyword (UFS and ZFS)
install_type Profile Keyword (UFS and ZFS)
layout_constraint Profile Keyword
local_customization Profile Keyword (Installing Solaris Flash Archives)
locale Profile Keyword (UFS and ZFS)
metadb Profile Keyword (Creating State Database Replicas)
no_content_check Profile Keyword (Installing Solaris Flash Archives)
no_master_check Profile Keyword (Installing Solaris Flash Archives)
package Profile Keyword (UFS and ZFS)
pool Profile Keyword (ZFS Only)
root_device Profile Keyword (UFS and ZFS)
usedisk Profile Keyword (UFS and ZFS)
9. Installing a ZFS Root Pool With JumpStart
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
|