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. A match occurs when the system that is being installed matches all the system attributes that are defined in the rule. When 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.
You can install a full archive for an initial installation or if you have already installed an archive, a differential archive for an update. You can use the custom JumpStart installation method or use Solaris Live Upgrade to install an archive on an inactive boot environment. This procedure provides the instructions to install an archive with custom JumpStart.
For an overview of a full or differential archive, see Chapter 1, Solaris Flash (Overview), in Solaris 10 10/08 Installation Guide: Solaris Flash Archives (Creation and Installation).
For procedures about installing an archive on an inactive boot environment by using Solaris Live Upgrade, see To Install a Solaris Flash Archive With a Profile in Solaris 10 10/08 Installation Guide: Solaris Live Upgrade and Upgrade Planning.
Review the following limitations.
On the install server, create the custom JumpStart rules file.
For detailed instructions about creating custom JumpStart files, refer to Chapter 3, Preparing Custom JumpStart Installations (Tasks).
On the install server, create the custom JumpStart profile file.
For examples of Solaris Flash archive profiles, see Profile Examples.
From the existing list of custom JumpStart keywords in Table 8–2, the only keywords valid when you install a Solaris Flash archive are the following:
Keyword |
Initial Installation |
Differential Archive |
---|---|---|
(required)archive_location |
X |
X |
fdisk (x86 only) |
X |
X |
filesys Note – You cannot set the filesys keyword to the value auto. |
X |
|
forced_deployment |
|
X |
(required) install_type |
X |
X |
local_customization |
X |
X |
no_content_check |
|
X |
no_master_check |
|
X |
package |
X |
|
root_device |
X |
X |
Set the value of the keyword install_type to one of the following types.
For a full archive installation, set the value to flash_install.
For a differential archive installation, set the value to flash_update.
Add the path to the Solaris Flash archive by using the archive_location keyword.
For details about the archive_location keyword, refer to archive_location Keyword.
Specify the file system configuration.
The Solaris Flash archive extraction process does not support auto-layout of partitions.
(Optional) If you want to install additional packages at the same time you install an archive, use the package keyword. For more information, see package Profile Keyword (UFS and ZFS).
(Optional) If you want to install an additional Solaris Flash archive on the clone system, add one archive_location line for each archive that you want to install.
On the install server, add the clients that you are installing with the Solaris Flash archive.
For detailed instructions, refer to the following:
Perform the custom JumpStart installation on the clone systems.
For detailed instructions, refer to SPARC: 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 are installing 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 the system's DVD-ROM or CD-ROM drive to install the Solaris software, insert the Solaris Operating System for SPARC Platforms DVD or the Solaris Software for SPARC Platforms - 1 CD in the drive.
If you are using a profile diskette, insert the profile diskette in the system's diskette drive.
Boot the system.
If the system is new, out–of–the–box, turn on the system.
If you want to install or upgrade an existing system, shut down the system. At the ok prompt, type the appropriate options for the boot command. The syntax of the boot command is the following.
ok boot [cd–dvd|net] - install [url|ask] options |
For example, if you type the following command, the OS is installed over the network by using a JumpStart profile.
ok boot net - install http://131.141.2.32/jumpstart/config.tar |
For a description of the boot command options, see the following table.
The system checks hardware and system components and your SPARC based system boots. Booting lasts several minutes.
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
The syntax of the boot command is the following.
ok boot [cd–dvd|net] - install [url|ask] options |
The following table describes the command-line options for the boot command that are appropriate for a JumpStart installation.
Option |
Description |
|||
---|---|---|---|---|
[cd–dvd|net] |
Specifies to boot from a CD or a DVD or to boot from an install server on the network.
|
|||
[url| ask] |
Specifies the location of the custom JumpStart files or prompts you for the location.
|
|||
options |
|