test

Solaris 8 Advanced Installation Guide

Creating Finish Scripts

What Is a Finish Script?

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

Possible Uses of Finish Scripts

Important Information About Finish Scripts

Adding Files With a Finish Script

Through a finish script, you can add files from the JumpStart directory to an already installed system. This is possible because the JumpStart directory is mounted on the directory specified by the SI_CONFIG_DIR variable (which 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.

The following procedure enables you to create a finish script to add files to a system after the Solaris software is installed on it:

To Add Files With a Finish Script

  1. Copy all the files you want added to the installed system into the JumpStart directory.

  2. Insert the following line into the finish script for each file you want copied into the newly installed file system hierarchy:

    cp ${SI_CONFIG_DIR}/file_name /a/path_name

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 during a custom JumpStart installation: 

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 Solaris is installed on a system. Adding packages in this way not only saves time, but ensures consistency in what packages and patches are installed on different systems at your site.

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

Example 19–1 shows an example of a finish script that adds packages.

Example 19–1 Adding Packages With a Finish Script

  #!/bin/sh
 
  BASE=/a
  MNT=/a/mnt
  ADMIN_FILE=/a/tmp/admin
 
  mkdir ${MNT}
  mount -f nfs sherlock:/export/package ${MNT}  [Mounts a directory on a server that contains the package
to install.] 
  cat >${ADMIN_FILE} <<DONT_ASK  [Creates a temporary package administration file, admin, to force the pkgadd(1M) command not to perform checks (and prompt
for questions) when installing a package. This enables you to maintain a hands-off
installation when you are adding packages.] 
  mail=root
  instance=overwrite
  partial=nocheck
  runlevel=nocheck
  idepend=nocheck
  rdepend=nocheck
  space=ask
  setuid=nocheck
  conflict=nocheck
  action=nocheck
  basedir=default
  DONT_ASK
 
  /usr/sbin/pkgadd -a ${ADMIN_FILE} -d ${MNT} -R ${BASE} SUNWxyz  [Adds the package by using the -a option (specifying
the package administration file) and the -R option
(specifying the root path).] 
 
  umount ${MNT}
  rmdir ${MNT}
Note –

In the past, the chroot(1M) command was used with the pkgadd and patchadd commands in the finish script environment. In the rare instances in which 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 already installed on a system. For example, the finish script in Example 19–2 customizes the root environment by appending information to the .cshrc file in the root (/) directory.

Example 19–2 Customizing the Root Environment With a Finish Script

#!/bin/sh
#
# 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
EOF
}

Setting a System's Root Password With a Finish Script

After Solaris software is installed on a system, the system reboots. Before the boot process is completed, the system prompts for the root password. Until someone enters a password, the system cannot finish booting.

A finish script called set_root_pw in the auto_install_sample directory shows how to avoid this problem by setting the root password automatically, without prompting. set_root_pw is shown in Example 19–3.

Example 19–3 Setting the System's Root Password With a Finish Script

	 #!/bin/sh
	 #
	 #       @(#)set_root_pw 1.4 93/12/23 SMI
	 #
	 # This is an example Bourne shell script to be run after installation.
	 # It sets the system's root password to the entry defined in PASSWD.
	 # The encrypted password is obtained from an existing root password entry
	 # in /etc/shadow from an installed machine.
 
	 echo "setting password for root"
 
	 # set the root password
     PASSWD=dKO5IBkSF42lw
	 #create a temporary input file  [Sets the variable PASSWD to an encrypted
root password obtained from an existing entry in a system's /etc/shadow file.] 
     cp /a/etc/shadow /a/etc/shadow.orig  [Creates a temporary input file of /a/etc/shadow.] 
 
	 mv /a/etc/shadow /a/etc/shadow.orig
 	nawk -F: '{
              if ( $1 == "root" )  [Changes the root entry in the /etc/shadow file
for the newly installed system using $PASSWD as
the password field.] 
              printf"%s:%s:%s:%s:%s:%s:%s:%s:%s\n",$1,passwd,$3,$4,$5,$6,$7,$8,$9
          else
              printf"%s:%s:%s:%s:%s:%s:%s:%s:%s\n",$1,$2,$3,$4,$5,$6,$7,$8,$9
          }' passwd="$PASSWD" /a/etc/shadow.orig > /a/etc/shadow
     #remove the temporary file
     rm -f /a/etc/shadow.orig  [Removes the temporary /a/etc/shadow
file.] 
     # set the flag so sysidroot won't prompt for the root password
     sed -e 's/0 # root/1 # root/' ${SI_SYS_STATE} > /tmp/state.$$  [Changes the entry from 0 to a 1 in the state file, so that the user is not prompted for the root
password. The state file is accessed using the variable SI_SYS_STATE, whose value currently is /a/etc/.sysIDtool.state.
(To avoid problems with your scripts if this value changes, always reference
this file using $SI_SYS_STATE.) The sed
command shown here contains a tab character after the 0
and after the 1.] 
     mv /tmp/state.$$ ${SI_SYS_STATE}
Note –

If you set the system's root password by using a finish script, safeguard against those who might attempt to discover the root password from the encrypted password in your finish script.