JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris 10 1/13 Installation Guide: JumpStart Installations     Oracle Solaris 10 1/13 Information Library
search filter icon
search icon

Document Information

Preface

1.  Where to Find Oracle Solaris Installation Planning Information

2.  JumpStart (Overview)

3.  Preparing JumpStart Installations (Tasks)

Task Map: Preparing JumpStart Installations

Creating a Profile Server for Networked Systems

How to Create a JumpStart Directory on a Server

Allowing All Systems Access to the Profile Server

Using a Wildcard Entry to Allow All Systems Access to the Profile Server

Creating a Profile Diskette for Stand-alone Systems

SPARC: How to Create a Profile Diskette

x86: How to Create a Profile Diskette With GRUB

Creating the rules File

Syntax of the rules File

How to Create a rules File

rules File Example

Creating a Profile

Syntax of Profiles

How to Create a Profile

Profile Examples

Testing a Profile

How to Create a Temporary Oracle Solaris Environment to Test a Profile

How to Test a Profile

Profile Test Example

Validating the rules File

How to Validate the rules File

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

9.  Installing a ZFS Root Pool With JumpStart

Glossary

Index

Task Map: Preparing JumpStart Installations

Table 3-1 Task Map: Preparing JumpStart Installations

Task
Description
For Instructions
Decide how to upgrade the system if a previous version of the Oracle Solaris software is installed on the system.
If a previous release of Oracle 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 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 JumpStart files.

On a diskette

If you want to perform JumpStart installations on systems that are not connected to a network, you must create a profile diskette. A profile diskette contains the 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 Oracle 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 Oracle 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.