Patching the Miniroot Image (Tasks)

You might need to Patch the files that are located in the miniroot on the network installation image that was created by setup_install_server.

About the Miniroot Image (Overview)

The miniroot is a minimal, bootable root (/) file system that resides on the Solaris installation media. A miniroot consists of all the Solaris software that is required to boot the system to either install or upgrade the system. The miniroot software is used by the installation media to perform a full installation of the Solaris OS. The miniroot runs only during the installation process.

You might need to patch the miniroot before installation if the boot image has problems booting or if you need to add driver and hardware support. When you patch the miniroot image, the patch is not installed on the system where the Solaris OS installation occurs or on the system that the patchadd command is run. Patching the miniroot image is strictly used for adding driver and hardware support to the process that performs the actual installation of the Solaris OS.

How To Patch the Miniroot Image

Follow these steps to patch a network installation miniroot image.

1. On a system that is running the current Solaris release, log in as superuser or assume an equivalent role.

   ---

   Note - Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.

   ---

2. Change to the Tools directory of the installation image you created in Step 5.

   # cd install-server-path/install-dir-path/Solaris_10/Tools

   install-server-path

   Specifies the path to the install server system on your network, for example, /net/installserver-1.

3. Create a new installation image, and place that image on the system that is running the current Solaris release.

   # ./setup_install_server remote_install_dir_path

   remote_install_dir_path

   Specifies the path on the current Solaris release in which to create the new installation image.

   This command creates a new installation image on the current Solaris release. In order to patch this image, you must temporarily place this image on a system that is running the current Solaris release.

4. On the current Solaris release, unpack the network installation boot archive.

   # /boot/solaris/bin/root_archive unpackmedia remote_install_dir_path \ destination_dir

   remote_install_dir_path

   Specifies the path to the network installation image on the current Solaris release.

   destination_dir

   Specifies the path to the directory to contain the unpacked boot archive.

5. On the current Solaris release, patch the unpacked boot archive.

   # patchadd -C destination_dir path-to-patch/patch-id

   path-to-patch

   Specifies the path to the patch that you want to add, for example, /var/sadm/spool.

   patch-id

   Specifies the patch ID that you want to apply.

   You can specify multiple patches with the patchadd -M option. For more information, see patchadd(1M).

   ---

   Caution - Don't use the patchadd -C command unless you have read the Patch README instructions or have contacted your local Sun support office.

   ---

6. On the current Solaris release, pack the boot archive.

   # /boot/solaris/bin/root_archive packmedia remote_install_dir_path \ destination_dir

7. Copy the patched archives to the installation image on the install server.

   # cd remote_install_dir_path
   # find boot Solaris_10/Tools/Boot | cpio -pdum \
      install-server-path/install_dir_path

Next Steps

After you have set up the install server and patched the miniroot, you might need to set up a boot server or add systems to be installed from the network.

• If you are using DHCP or the install server is on the same subnet as the system to be installed, you do not need to create a boot server. Proceed to Adding Systems to Be Installed From the Network With a DVD Image.

• If you are not using DHCP and the install server and the client are on a different subnet, you must create a boot server. Proceed to Creating a Boot Server on a Subnet With a DVD Image.