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

Document Information

Preface

Part I Using Custom JumpStart

1.  Where to Find Solaris Installation Planning Information

2.  Custom JumpStart (Overview)

3.  Preparing Custom JumpStart Installations (Tasks)

Task Map: Preparing Custom JumpStart Installations

Creating a Profile Server for Networked Systems

To Create a JumpStart Directory on a Server

Allowing All Systems Access to the Profile Server

To Allow All Systems Access to the Profile Server

Creating a Profile Diskette for Standalone Systems

SPARC: To Create a Profile Diskette

x86: To Create a Profile Diskette With GRUB

Creating the rules File

Syntax of the rules File

To Create a rules File

rules File Example

Creating a Profile

Syntax of Profiles

To Create a Profile

Profile Examples

Testing a Profile

To Create a Temporary Solaris Environment to Test a Profile

To Test a Profile

Profile Test Examples

Validating the rules File

To Validate the rules File

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)

9.  Installing a ZFS Root Pool With JumpStart

Part II Appendixes

A.  Troubleshooting (Tasks)

B.  Additional SVR4 Packaging Requirements (Reference)

Glossary

Index

Task Map: Preparing Custom JumpStart Installations

Table 3-1 Task Map: Preparing Custom JumpStart Installations

Task
Description
For Instructions
Decide how to upgrade the system if a previous version of the Solaris software is installed on the system.
If a previous release of Solaris is installed on the system, you need to determine how to upgrade the system. Ensure that you know what to do before and after you upgrade a system. Planning helps you to create your profiles, begin scripts, and finish scripts.
Create a JumpStart directory.
On a server

If you want to perform custom JumpStart installations on systems that are connected to a network, you must create a profile server. The profile server contains a JumpStart directory for the custom JumpStart files.

On a diskette

If you want to perform custom JumpStart installations on systems that are not connected to a network, you must create a profile diskette. A profile diskette contains the custom JumpStart files.

Add rules to the rules file.
After you decide how you want each group of systems or single systems to be installed, create a rule for each group that you want to install. Each rule distinguishes a group, based on one or more system attributes. The rule links each group to a profile.
Create a profile for every rule.
A profile is a text file that defines how to install the Solaris software, for example, which software group to install on a system. Every rule specifies a profile to define how a system is to be installed with the Solaris software when the rule is matched. You usually create a different profile for every rule. However, the same profile can be used in more than one rule.
(Optional) Test the profiles.
After you create a profile, use the pfinstall(1M) command to test the profile before you use the profile to install or upgrade a system.
Validate the rules file.
The rules.ok file is a generated version of the rules file that the JumpStart program uses to match the system to be installed with a profile. You must use the check script to validate the rules file.