Skip Navigation Links | |
Exit Print View | |
![]() |
Oracle Solaris 10 1/13 Installation Guide: Network-Based Installations Oracle Solaris 10 1/13 Information Library |
Part I Planning to Install Over the Network
1. Where to Find Oracle Solaris Installation Planning Information
2. Preconfiguring System Configuration Information (Tasks)
3. Preconfiguring With a Naming Service or DHCP
Part II Installing Over a Local Area Network
4. Installing From the Network (Overview)
5. Installing From the Network With DVD Media (Tasks)
6. Installing From the Network With CD Media (Tasks)
7. Patching the Miniroot Image (Tasks)
Patching the Miniroot Image (Example)
How to Modify the Miniroot (Example)
8. Installing Over the Network (Examples)
9. Installing From the Network (Command Reference)
Part III Installing Over a Wide Area Network
11. Preparing to Install With WAN Boot (Planning)
12. Installing With WAN Boot (Tasks)
13. SPARC: Installing With WAN Boot (Tasks)
14. SPARC: Installing With WAN Boot (Examples)
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.
The miniroot is a minimal, bootable root (/) file system that resides on the Oracle Solaris installation media. A miniroot consists of all the Oracle 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 Oracle 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 Oracle 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 Oracle Solaris OS.
Note - This procedure is only for patching the miniroot, not for patching the complete network installation image. If you need to patch the network installation image, perform the task after the installation completes.
Before You Begin
These steps assume that you have a system on your network that is running the current Oracle Solaris release, and that system is accessible over the network.
Note - Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
# cd install-server-path/install-dir-path/Solaris_10/Tools
Specifies the path to the install server system on your network, for example, /net/installserver-1.
# ./setup_install_server remote-install-dir-path
Specifies the path on the current Oracle Solaris release in which to create the new installation image.
This command creates a new installation image on the current Oracle Solaris release. In order to patch this image, you must temporarily place this image on a system that is running the current Oracle Solaris release.
# /boot/solaris/bin/root_archive unpackmedia remote-install-dir-path \ destination-dir
Specifies the path to the directory to contain the unpacked boot archive.
PKG_NONABI_SYMLINKS="true" export PKG_NONABI_SYMLINKS
# patchadd -C destination-dir path/patch-ID
Specifies the path to the patch that you want to add, for example, /var/sadm/spool.
Specifies the patch ID that you want to apply.
You can specify multiple patches with the patchadd -M option. For more information, see the patchadd(1M) man page.
![]() | Caution - Don't use the patchadd -C command unless you have read the Patch README instructions or have contacted your local Oracle support office. |
# /boot/solaris/bin/root_archive packmedia remote-install-dir-path \ destination-dir
# 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.