Solaris 9 Installation Guide

x86: Performing a Custom JumpStart Installation

x86: Task Map: Setting Up a System for a Custom JumpStart Installation

During a custom JumpStart installation, the JumpStart program attempts to match the system that is being installed to the rules in the rules.ok file. The JumpStart program reads the rules from the first rule through the last rule. A match occurs when the system that is being installed matches all of the system attributes that are defined in the rule. As soon as a system matches a rule, the JumpStart program stops reading the rules.ok file and begins to install the system, based on the matched rule's profile.

Table 26–3 x86: Task Map: Setting Up a System for a Custom JumpStart Installation


Task	Description	For Instructions
Determine if you need to preserve an existing operating system and user data	If the existing operating system on the system uses the entire disk, you must preserve the existing operating system so it can co-exist with the Solaris 9 software. This decision determines how to specify the fdisk(1M) keyword in the system's profile.	x86: `fdisk` Profile Keyword
Check if the system is supported	Check the hardware documentation for system support in the Solaris 9 environment.	Hardware manufacturer's documentation
Check if the system has enough disk space for the Solaris 9 software	Verify that you have planned enough space to install the Solaris software on your system.	Chapter 5, Guidelines for Allocating Disk Space and Swap Space (Planning)
(Optional) Preconfigure system configuration information	You can use the `sysidcfg` file or the name service to preconfigure installation information for a system. If you preconfigure system information, the installation program does not prompt you to supply the information during the installation.	Chapter 7, Preconfiguring System Configuration Information (Tasks)
Prepare the system for custom JumpStart installation	Create and validate a `rules` file and profile files.	Chapter 23, Preparing Custom JumpStart Installations (Tasks)
(Optional) Prepare optional custom JumpStart features	If you are using `begin` scripts, `finish` scripts, or other optional features, prepare the scripts or files.	Chapter 24, Using Optional Custom JumpStart Features (Tasks) and Chapter 25, Creating Custom Rule and Probe Keywords (Tasks)
(Optional) Set up the system to install over the network	To install a system from a remote Solaris 9 x86 Platform Edition DVD or Solaris 9 Software x86 Platform Edition CD image, you need to set up the system to boot and install from an install server or a boot server.	Chapter 12, Preparing to Install From the Network With CD Media (Tasks)
Install or upgrade	Boot the system to initiate the installation or upgrade.	x86: To Perform an Installation or Upgrade With the Custom JumpStart Program

x86: To Perform an Installation or Upgrade With the Custom JumpStart Program

If the system is part of a network, ensure that an Ethernet connector or similar network adapter is attached to your system.

If you want to install a system that is connected through a tip(1) line, ensure that your window display is at least 80 columns wide and 24 rows long.

To determine the current dimensions of your tip window, use the stty(1) command.

If you are using a profile diskette, insert the profile diskette into the system's diskette drive.

Note –
The profile diskette contains a copy of the Solaris 9 Device Configuration Assistant in addition to profile information. If you are using PXE network boot to boot the system over the network, you must configure your system so that the system boots from the network and not from the diskette.

If you are using the system's DVD-ROM or CD-ROM drive to install the Solaris 9 software, insert the Solaris 9 x86 Platform Edition DVD or the Solaris 9 Software 1 of 2 x86 Platform Edition CD in the drive.

Decide how to boot the system.
- If you boot from the Solaris 9 DVD or the Solaris 9 Installation CD, insert the disc. Your system's BIOS must support booting from a DVD or CD.
- If you boot from the network, use Preboot Execution Environment (PXE) network boot. The system must support PXE. Enable the system to use PXE by using the systems's BIOS setup tool or the network adapter's configuration setup tool.
- If you boot from a Diskette – Use the profile diskette that you inserted into the drive in Step 3 or insert the Solaris 9 Device Configuration Assistant x86 Platform Edition diskette into the system's diskette drive.
  
  x86 only –
  You can copy the Device Configuration Assistant software to a diskette by the following methods:
  - Copy the software to a diskette from the Solaris 9 x86 Platform Edition DVD or Solaris 9 Software 2 of 2 x86 Platform Edition CD by using the procedure in Appendix I, x86: Preparing to Boot From the Solaris 9 Device Configuration Assistant or the Network (Tasks).
  - Download and copy the software to a diskette from the Solaris Developer Connection at http://soldc.sun.com/support/drivers/dca_diskettes.

If the system is off, turn the system on. If the system is on, reboot the system.

The Device Configuration Assistant identifies the system's devices.

On the Boot Solaris screen, select the device from which to boot the system. Select DVD, CD, Net, or Disk.

At the prompt, perform one of the following:

Select the type of installation you want to perform:
 
         1 Solaris Interactive
         2 Custom JumpStart
 
Enter the number of your choice followed by the <ENTER> key.
 
If you enter anything else, or if you wait for 30 seconds,
an interactive installation will be started.

To select the custom JumpStart method, perform one of the following actions:

Note –

If you do not type 2 or type a boot command within 30 seconds, the Solaris suninstall program begins. You can stop the timer by typing any key on the command line.

Type 2 and press Enter.
To specify the location of the custom JumpStart configuration files, type the following command.
b install [[url:ask]] [[dhcp]] [[nowin]]
url
Specifies the location of the custom JumpStart files. You can specify a URL for files that are located in the following places:
- Local hard disk
  file://jumpstart_dir_path/compressed_config_file
- NFS server
  nfs://server_name:IP_address/jumpstart_dir_path/compressed_config _file
- HTTP server
  http://server_name:IP_address/jumpstart_dir_path/ compressed_config_file&proxy_info
If you placed a sysidcfg file in the compressed configuration file, you must specify the IP address of the server that contains the file, as in the following example:
http://131.141.2.32/jumpstart/config.tar
If you saved the compressed configuration file on an HTTP server that is behind a firewall, you must use a proxy specifier during boot. You do not need to specify an IP address for the server that contains the file. You must specify an IP address for the proxy server, as in the following example:
http://www.shadow.com/jumpstart/ config.tar&proxy=131.141.6.151
ask

Specifies that the installation program prompt you to type the location of the compressed configuration file after the system boots and connects to the network.

If you bypass the prompt by pressing Return, the installation program interactively configures the network parameters. The installation program then prompts you for the location of the compressed configuration file. If you bypass the prompt by pressing Return, the Solaris suninstall program begins.

dhcp

Specifies to use a DHCP server to obtain network installation information that is needed to boot the system.

If you do not specify to use a DHCP server, the system uses the /etc/bootparams file or the name service bootparams database.

nowin

Specifies not to begin the X program. You do not need to use the X program to perform a custom JumpStart installation, so you can reduce the installation time by using the nowin option.

If you did not preconfigure system information in the sysidcfg file, when prompted, answer the questions about system configuration.

Follow the instructions on the screen to install the software.

When the JumpStart program finishes installing the Solaris software, the system reboots automatically.

After the installation is finished, installation logs are saved in a file. You can find the installation logs in the following directories:
- /var/sadm/system/logs
- /var/sadm/install/logs