Solaris 9 4/04 Installation Guide


sun.com \| docs.sun.com	How To Buy \| My Sun \| Worldwide Sites

Previous Contents Index Next Next

To Create a Profile

Use a text editor to 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.

Add profile keywords and values to the profile.
For a list of profile keywords and values, see Profile Keywords and Values.

Note - Profile keywords and their values are case sensitive.

Save the profile in the JumpStart directory.

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

Test the profile (optional).
Testing a Profile contains information about testing profiles.

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 26-2 Mounting Remote File Systems and Adding and Deleting Packages

 
# profile keywords        profile values
# -----------------       -----------------
  install_type            initial_install
  system_type             standalone
  partitioning            default
  filesys                 any 512 swap   # specify size of /swap
  cluster                 SUNWCprog
  package                 SUNWman delete
  cluster                 SUNWCacc

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

`install_type`	The `install_type` keyword is required in every profile.
`system_type`	The `system_type` keyword defines that the system is to be installed as a standalone system.
`partitioning`	The file system slices are determined by the software to be installed with the value `default`. The size of `swap` is set to 512 Mbytes and is installed on any disk, value `any`.
`cluster`	The Developer Solaris Software Group, `SUNWCprog`, is installed on the system.
`package`	If the standard man pages are mounted from the file server, `s_ref`, on the network, the man page packages are not to be installed on the system. The packages that contain the System Accounting utilities are selected to be installed on the system.

Example 26-3 Specifying Where to Install File Systems

# 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 list describes some of the keywords and values from this example.

`partitioning`	The file system slices are determined by the `filesys` keywords, value `explicit`. The size of root (`/`) 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 26-4 x86: Using the fdisk Keyword

# 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 list 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 Distribution software group, `SUNWCall`, is installed on the system.
`cluster`	The system accounting utilities, `SUNWCacc`, are not to be installed on the system.

Example 26-5 Reallocating Disk Space for an Upgrade

# profile keywords         profile values
# ----------------         -------------------
  install_type             upgrade 
  root_device              c0t3d0s2 
  backup_media             remote_filesystem timber:/export/scratch
  layout_constraint        c0t3d0s2 changeable 100
  layout_constraint        c0t3d0s4 changeable
  layout_constraint        c0t3d0s5 movable 
  package                  SUNWbcp delete
  package                  SUNWxwman add
  cluster                  SUNWCacc add   
  locale                   de

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

`install_type`	The profile upgrades a system by reallocating disk space. In this example, disk space must be reallocated because some file systems on the system did not have enough space for the upgrade.
`root_device`	The root file system on `c0t3d0s2` is upgraded.
`backup_media`	A remote system that is named `timber` is to be used to back up data during the disk space reallocation. For more backup-media keyword values, see `backup_media` Profile Keyword.
`layout_constraint`	The `layout_constraint` keywords designate that auto-layout can perform the following when auto-layout attempts to reallocate disk space for the upgrade. Change slices 2 and 4. The slices can be moved to another location and the size can be changed. Move slice 5. The slice can be moved to another location but its size cannot change.
`package`	The binary compatibility package, `SUNWbcp`, is not installed on the system after the upgrade.
`package`	The code ensures that the X Window System man pages and the System Accounting Utilities are to be installed if they are not already installed on the system. All packages already on the system are automatically upgraded.
`locale`	The German localization packages are to be installed on the system.

Example 26-6 Retrieving a Solaris Flash Archive From an HTTP Server

In the following example, the profile indicates that the custom JumpStart program retrieves the Solaris Flash archive from an HTTP server.

# profile keywords         profile values
# ----------------         -------------------
install_type               flash_install
archive_location           http://192.168.255.255/flasharchive/solarisarchive
partitioning               explicit
filesys                    c0t1d0s0 4000 /
filesys                    c0t1d0s1 512 swap
filesys                    c0t1d0s7 free /export/home

Previous Contents Index Next Next