Less Known Solaris features: Jumpstart Enterprise Toolkit - Part 10: A polished basic installation

Okay, now we´ve done a basic installation. But mostly we do a standard set of customizations on every system we touch, like installing a few essential tools or integrating the actual recommended patch cluster. So we want to polish the standard installation a little bit. We will extend a basic Solaris 10 Update 5 installation with the following items:

Adding the recommended patch cluster

Okay, at first we have to copy the patches into the the jumpstart. JET provides the copy_solaris_patches command to do so.

# copy_solaris_patches 10_x86 /export/home/jmoekamp/10_x86_Recommended<br />

The second parameter specifies where your unpacked your patch cluster. You don´t have to configure anything in the templates. Every new Solaris 10 installation from now on with the x86 architecture will be installed with the matching recommended patch cluster.

Adding custom packages

Okay, almost everybody installs some custome packages on his/her system. For example, one of the first things i´m installing on new systems is \verb=joe= to have an WordStar compatible editor:

# pkgtrans joe-3.5-sol10-x86-local /tmp all<br />
Transferring <SMCjoe> package instance<br />
# copy_custom_packages /tmp i386 SMCjoe<br />
Transferring <SMCjoe> package instance<br />
Packages copied

joe depends on the ncurses library. So we copy this package as well to our JET server.

<br />
# pkgtrans ncurses-5.6-sol10-x86-local /tmp all<br />
Transferring <SMCncurs> package instance<br />
# copy_custom_packages /tmp i386 SMCncurs<br />
Transferring <SMCncurs> package instance<br />
Packages copied<code></blockquote>
<h3>Extending the template</h3>
Okay, we need  more modules to fullfil this tasks. You don´t need to delete the old one and retype all the data in the template. The <code>make_template</code> script can use an an old template to create a new one with while retaining all the old values. Basically you use the same name for the old and new template.
<blockquote><code># ./make_template -f  -T togusa togusa base_config custom sbd<br />
Adding product configuration information for<br />
        + custom<br />
        + sbd<br />
Updating base_config template specifics<br />
Client template created in /opt/SUNWjet/Templates

When you look into /opt/SUNWjet/Templates/togusa you will recognise your old configuration, with a large amount of new lines. But we have to change only a few ones:At first we change the operation system. We´ve used Opensolaris in the last example, but there are no patches for this release. But we´ve copied a Solaris 10 media with the name sol10u5 earlier:


Okay, now we want to install the additional packages. You have to add the names of the packages in the line \verb=custom_packages=.

custom_packages="SMCncurs SMCjoe"

You don´t have to configure the Secure by default module, as this module configures the \verb=limited= service set when it´s used in the template. Patching of the Solaris OE doesn´t need configuration as well. So we have to change only this two lines.

The installation

Okay, you can start the installation by starting a network boot. This time the installation takes a little bit longer. First the system starts to install the recommended patch cluster. As i´ve used a quite actual update, most patches are already installed. but a few ones will find their way into the installation.

BASE_CONFIG: Installing base_config....<br />
BASE_CONFIG: Product base_config started<br />
BASE_CONFIG: Installing additional patches from : 10_x86_Recommended<br />
BASE_CONFIG: Using patch_order file for patch installation sequence<br />
BASE_CONFIG: ------ Installing patches for product: 10_x86_Recommended ------<br />
BASE_CONFIG: Patch 120720-02 is already installed.<br />
BASE_CONFIG: Patch 124458-01 is already installed.<br />
[...]<br />
BASE_CONFIG: <<< 120273-20 (25 of 98) >>><br />
[...]<br />
BASE_CONFIG: Patch 122175-03 is already installed.<br />
BASE_CONFIG: Patch installation completed.<br />
BASE_CONFIG: No HW specific packages for platform i86pc<br />
BASE_CONFIG: No HW specific patches for platform i86pc

Okay, now the system starts to install the additional packages.

CUSTOM: Installing custom....<br />
CUSTOM: Installing SMCncurs from: /a/var/opt/sun/jet/js_media/pkg/custom/i386<br />
Installation of <SMCncurs> was successful.<br />
CUSTOM: SMCncurs installation complete<br />
CUSTOM: Installing SMCjoe from: /a/var/opt/sun/jet/js_media/pkg/custom/i386<br />
Installation of <SMCjoe> was successful.<br />
CUSTOM: SMCjoe installation complete

The following module doesn´t do really much, as the configuration of the service profile is activated by the \verb=sysidcfg= file.

SBD: Installing sbd....<br />
SBD: configured

Effects of the new modules

Let´s check the results of the installation. At first, we look for the custom packages:

<br />
# pkginfo | grep "SMC"<br />
application SMCjoe                           joe<br />
application SMCncurs                         ncurses

When we look for one of the installed patches, we will see it´s successful installation to the system:

# showrev -p | grep "120273-20"<br />
Patch: 120273-20 Obsoletes:  Requires: 119043-09, 121902-01, 122532-04 Incompatibles:  Packages: SUNWbzip, SUNWsmagt, SUNWsmcmd, SUNWsmmgr