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


Part I Using Custom JumpStart

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)

Sample Site Setup

Create an Install Server

x86: Create a Boot Server for Marketing Systems

Create a JumpStart Directory

Share the JumpStart Directory

SPARC: Create the Engineering Group's Profile

x86: Create the Marketing Group's Profile

Update the rules File

Validate the rules File

SPARC: Set Up Engineering Systems to Install From the Network

x86: Set Up Marketing Systems to Install From the Network

SPARC: Boot the Engineering Systems and Install Solaris Software

x86: Boot the Marketing Systems and Install Solaris Software

8.  Custom JumpStart (Reference)

9.  Installing a ZFS Root Pool With JumpStart

Part II Appendixes

A.  Troubleshooting (Tasks)

B.  Additional SVR4 Packaging Requirements (Reference)



SPARC: Create the Engineering Group's Profile

For the engineering systems, you create a file that is named eng_prof in the /jumpstart directory. The eng_prof file contains the following entries, which define the Solaris 10 9/10 software to be installed on systems in the engineering group:

install_type  initial_install
system_type   standalone
partitioning  default
cluster       SUNWCprog
filesys       any 512 swap

The previous example profile specifies the following installation information.


The installation is to be treated as an initial installation, as opposed to an upgrade.


The engineering systems are standalone systems.


The JumpStart software uses default disk partitioning for installing Solaris software on the engineering systems.


The Developer System Support software group is to be installed.


Each system in the engineering group is to have 512 Mbytes of swap space.