This case study modifies an existing file during package installation using standard classes and class action scripts. It uses one of three modification methods. The other two methods are described in "Modifying a File Using the sed Class and a postinstall Script" and "Modifying a File Using the build Class". The file modified is /sbin/inittab.
This case study demonstrates how to use installation and removal class action scripts. For more information, see "Writing Class Action Scripts".
To modify /sbin/inittab during installation, using classes and class action scripts, you must complete the following tasks:
Create a class.
Create a class called inittab. You must provide an installation and a removal class action script for this class. Define the inittab class in the
CLASSES parameter in the pkginfo file.
Create an inittab file.
This file contains the information for the entry that you will add to /sbin/inittab. Notice in the prototype file figure that inittab is a member of the inittab class and has a file type of e for editable.
Create an installation class action script (i.inittab).
Remember that class action scripts must produce the same results each time they are executed. The class action script performs the following procedures:
Checks if this entry has been added before
If it has, removes any previous versions of the entry
Edits the inittab file and adds the comment lines so you know where the entry is from
Moves the temporary file back into /sbin/inittab
Executes the init q command when it receives the ENDOFCLASS indicator
Note that the init q command can be performed by this installation script. A one-line postinstall script is not needed by this approach.
Create a removal class action script (r.inittab).
The removal script is very similar to the installation script. The information added by the installation script is removed and the init q command is executed.
This case study is more complicated than the next one; see "Modifying a File Using the sed Class and a postinstall Script". Instead of providing two files, three are needed and the delivered /sbin/inittab file is actually just a place holder containing a fragment of the entry to be inserted. This could have been placed into the i.inittab file except that the pkgadd command must have a file to pass to the i.inittab file. Also, the removal procedure must be placed into a separate file (r.inittab). While this method works fine, it is best reserved for cases involving very complicated installations of multiple files. See "Modifying crontab Files During Installation".
The sed program used in "Modifying a File Using the sed Class and a postinstall Script" supports multiple package instances since the comment at the end of the inittab entry is based on package instance. The case study in "Modifying a File Using the build Class" shows a more streamlined approach to editing /sbin/inittab during installation.
PKG=case5 NAME=Case Study #5 CATEGORY=applications BASEDIR=/opt ARCH=SPARC VERSION=Version 1d05 CLASSES=inittab
i pkginfo i i.inittab i r.inittab e inittab /sbin/inittab ? ? ?
# PKGINST parameter provided by installation service while read src dest do # remove all entries from the table that # associated with this PKGINST sed -e "/^[^:]*:[^:]*:[^:]*:[^#]*#$PKGINST$/d" $dest > /tmp/$$itab || exit 2 sed -e "s/$/#$PKGINST" $src >> /tmp/$$itab || exit 2 mv /tmp/$$itab $dest || exit 2 done if [ "$1" = ENDOFCLASS ] then /sbin/init q || exit 2 fi exit 0
# PKGINST parameter provided by installation service while read src dest do # remove all entries from the table that # are associated with this PKGINST sed -e "/^[^:]*:[^:]*:[^:]*:[^#]*#$PKGINST$/d" $dest > /tmp/$$itab || exit 2 mv /tmp/$$itab $dest || exit 2 done /sbin/init q || exit 2 exit 0