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

Document Information


Part I Using Custom JumpStart

1.  Where to Find Oracle Solaris Installation Planning Information

2.  Custom JumpStart (Overview)

3.  Preparing Custom JumpStart Installations (Tasks)

4.  Using Optional Custom JumpStart Features (Tasks)

Creating Begin Scripts

Important Information About Begin Scripts

Creating Derived Profiles With a Begin Script

Tracking Installation Duration With a Begin Script and Finish Script

Creating Finish Scripts

Important Information About Finish Scripts

To Add Files With a Finish Script

Adding Packages or Patches With a Finish Script

Customizing the Root Environment With a Finish Script

Non-Interactive Installations With Finish Scripts

Creating a Compressed Configuration File

To Create a Compressed Configuration File

Compressed Configuration File Example

Creating Disk Configuration Files

SPARC: To Create a Disk Configuration File

SPARC: Disk Configuration File Example

x86: To Create a Disk Configuration File

x86: Disk Configuration File Example

Using a Site-Specific Installation Program

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 Appendices

A.  Troubleshooting (Tasks)

B.  Additional SVR4 Packaging Requirements (Reference)



Creating Finish Scripts

A finish script is a user-defined Bourne shell script that you specify in the rules file. A finish script performs tasks after the Oracle Solaris software is installed on a system, but before the system reboots. You can use finish scripts only when using custom JumpStart to install Oracle Solaris.

Tasks that you can perform with a finish script include the following:

Important Information About Finish Scripts

To Add Files With a Finish Script

Through a finish script, you can add files from the JumpStart directory to an already installed system. You can add the files because the JumpStart directory is mounted on the directory that is specified by the SI_CONFIG_DIR variable. The directory is set to /tmp/install_config by default.

Note - You can also replace files by copying files from the JumpStart directory to already existing files on the installed system.

  1. Copy all of the files that you are adding to the installed system to the JumpStart directory.
  2. Insert the following line in the finish script for each file that you want to be copied to the newly installed file system hierarchy:
    cp ${SI_CONFIG_DIR}/file_name /a/path_name

Example 4-4 Adding a File With a Finish Script

For example, assume you have a special application, site_prog, developed for all users at your site. If you place a copy of site_prog into the JumpStart directory, the following line in a finish script copies site_prog from the JumpStart directory into a system's /usr/bin directory:

cp ${SI_CONFIG_DIR}/site_prog  /a/usr/bin

Adding Packages or Patches With a Finish Script

You can create a finish script to automatically add packages or patches after the Oracle Solaris software is installed on a system. By adding packages with a finish script, you reduce time and ensure consistency in which packages and patches are installed on different systems at your site.

When you use the pkgadd(1M) or patchadd(1M) commands in finish scripts, use the -R option to specify /a as the root path.

Example 4-5 Adding Packages With a Finish Script

  mkdir ${MNT}
  mount -f nfs sherlock:/export/package ${MNT}
  /usr/sbin/pkgadd -a ${ADMIN_FILE} -d ${MNT} -R ${BASE} SUNWxyz 
  umount ${MNT}
  rmdir ${MNT}

The following describes some commands for this example.

Example 4-6 Adding Patches With a Finish Script



# The location of the patches to add to the system after it's installed.
# The OS rev (5.x) and the architecture (`mach`) will be added to the
# root.  For example, /foo on a 8 SPARC would turn into /foo/5.8/sparc


# Figure out the source and target OS versions
echo Determining OS revisions...
SRCREV=`uname -r`
echo Source $SRCREV


# Add the patches needed
echo Adding OS patches
mount $LUPATCHHOST:$LUPATCHPATH /mnt >/dev/null 2>&1
if [ $? = 0 ] ; then
    for patch in `cat /mnt/*Recommended/patch_order` ; do
        (cd /mnt/*Recommended/$patch ; echo yes | patchadd -u -d -R $BASEDIR .)
    cd /tmp
    umount /mnt
    echo "No patches found"

Note - In the past, the chroot(1M) command was used with the pkgadd and patchadd commands in the finish script environment. In rare instances, some packages or patches do not work with the -R option. You must create a dummy /etc/mnttab file in the /a root path before issuing the chroot command.

To create a dummy /etc/mnttab file, add the following line to your finish script:

cp /etc/mnttab /a/etc/mnttab

Customizing the Root Environment With a Finish Script

You can also use finish scripts to customize files that are already installed on a system. For example, the finish script in Example 4-7 customizes the root environment by appending information to the .cshrc file in the root (/) directory.

Example 4-7 Customizing the Root Environment With a Finish Script

# Customize root's environment
echo "***adding customizations in /.cshrc"
test -f a/.cshrc || {
cat >> a/.cshrc <<EOF
set history=100 savehist=200 filec ignoreeof prompt="\$user@`uname -n`> "
alias cp cp -i
alias mv mv -i
alias rm rm -i
alias ls ls -FC
alias h history
alias c clear
unset autologout

Non-Interactive Installations With Finish Scripts

You can use finish scripts to install additional software after the Oracle Solaris OS is installed. The Oracle Solaris installation program prompts you to enter information during the installation. To maintain a hands-off installation, you can run the Oracle Solaris installation program with the -nodisplay or -noconsole options.

Table 4-1 Oracle Solaris Installation Options

Runs the installer without a graphic user interface. Use the default product installation unless the installation was modified by the -locales option.
Runs the installation without any interactive text console device. Useful when paired with -nodisplay for UNIX script use.

For more information, see the man page installer(1M).