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:
- installing the SMCjoe package
- nstalling the recommended Patch Cluster
- configuring the Secure-by-default mechanism to limited
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.
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:
joe depends on the
ncurses library. So we copy this package as well to our JET server.
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
Okay, now we want to install the additional packages. You have to add the names of the packages in the line \verb=custom_packages=.
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.
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.
Okay, now the system starts to install the additional packages.
The following module doesn´t do really much, as the configuration of the service profile is activated by the \verb=sysidcfg= file.
Effects of the new modules
Let´s check the results of the installation. At first, we look for the custom packages:
When we look for one of the installed patches, we will see it´s successful installation to the system: