Solaris 10 Installation Guide for IBM BladeCenter Servers

Creating a Profile

A profile is a text file that defines how to install the Solaris software on a system. A profile defines the elements of an installation, for example, which software group to install. Every rule specifies a profile that defines how a system is to be installed. You can create different profiles for every rule. You can also use the same profile in more than one rule. See Creating the rules File.

A profile consists of one or more profile keywords and their values. Each profile keyword is a command that controls one aspect of how the JumpStart program is to install the Solaris software on a system. For example, the following profile keyword and value specify that the JumpStart program install the system as a server:

system_type server

Note –

Sample profiles are already located in the JumpStart directory, if you created the JumpStart directory by using the procedure, Creating a Profile Server for Networked Systems.


Syntax of Profiles

A profile must contain the following:

A profile can contain the following:

ProcedureHow to Create a Profile

  1. Using a text editor, create a text file. Name the file descriptively. Or, open a sample profile in the JumpStart directory that you created.


    Note –

    Ensure that the name of the profile reflects how you intend to use the profile to install the Solaris software on a system. For example, you might name the profiles basic_install, eng_profile, or user_profile.


  2. Add profile keywords and values to the profile.

    See Profile Examples.


    Note –

    Profile keywords and their values are case-sensitive.


  3. Save the profile in the JumpStart directory.

  4. Ensure that root owns the profile and that the permissions are set to 644.

  5. (Optional) Test the profile.

    See How To Test a Profile.

Profile Examples

The following examples of profiles show how to use different profile keywords and profile values to control how the Solaris software is installed on a system. Profile keywords and values contains a description of profile keywords and values.


Example 1–7 Specifying Where to Install File Systems by Using a Profile

# profile keywords        profile values
# ----------------        -------------------
  install_type            initial_install
  system_type             standalone 
  partitioning            explicit
  filesys                 c0t0d0s0 auto /
  filesys                 c0t3d0s1 auto swap
  filesys                 any auto usr
  cluster                 SUNWCall

The following describes some of the keywords and values from this example:

partitioning

The file system slices are determined by the filesys keywords that are value explicit. The size of the root (/) directory is based on the selected software, value auto, and is installed on c0t0d0s0. The size of swap is set to the necessary size and is installed on c0t3d0s1. usr is based on the selected software and the installation program determines where usr is installed, based on the value any.

cluster

The Entire Solaris Software Group, SUNWCall, is installed on the system.



Example 1–8 Using the fdisk Keyword in a Profile

# profile keywords      profile values
# ----------------      -------------------
  install_type          initial_install
  system_type           standalone

  fdisk                 c0t0d0 0x04 delete
  fdisk                 c0t0d0 solaris maxfree
  cluster               SUNWCall
  cluster               SUNWCacc delete

The following describes some of the keywords and values from this example:

fdisk

All fdisk partitions of type DOSOS16 (04 hexadecimal) are deleted from the c0t0d0 disk.

fdisk

A Solaris fdisk partition is created on the largest contiguous free space on the c0t0d0 disk.

cluster

The Entire Solaris Software Group, SUNWCall, is installed on the system.

cluster

The system accounting utilities, SUNWCacc, are not to be installed on the system.