Skip Navigation Links | |
Exit Print View | |
Oracle Solaris 10 8/11 Installation Guide: Custom JumpStart and Advanced Installations Oracle Solaris 10 8/11 Information Library |
1. Where to Find Oracle Solaris Installation Planning Information
2. Custom JumpStart (Overview)
3. Preparing Custom JumpStart Installations (Tasks)
4. Using Optional Custom JumpStart Features (Tasks)
5. Creating Custom Rule and Probe Keywords (Tasks)
6. Performing a Custom JumpStart Installation (Tasks)
Limitations for a JumpStart Installation
SPARC: Task Map: Setting Up a System for a Custom JumpStart Installation
SPARC: Performing a Custom JumpStart Installation
To Prepare to Install a Flash Archive With a Custom JumpStart Installation
SPARC: To Perform an Installation or Upgrade With the Custom JumpStart Program
x86: Task Map: Setting Up a System for a Custom JumpStart Installation
x86: Performing a Custom JumpStart Installation
x86: To Perform an Installation or Upgrade With the Custom JumpStart Program and With GRUB
x86: Performing a Custom JumpStart Installation by Editing the GRUB Boot Command
x86: To Modify the GRUB Boot Command
x86: Command Reference for Booting the System
7. Installing With Custom JumpStart (Examples)
8. Custom JumpStart (Reference)
9. Installing a ZFS Root Pool With JumpStart
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 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, Flash Archive (Overview), in Oracle Solaris 10 8/11 Installation Guide: Flash Archives (Creation and Installation).
For procedures about installing an archive on an inactive boot environment by using Live Upgrade, see To Install a Flash Archive With a Profile in Oracle Solaris 10 8/11 Installation Guide: Live Upgrade and Upgrade Planning.
|
For detailed instructions about creating custom JumpStart files, refer to Chapter 3, Preparing Custom JumpStart Installations (Tasks).
For examples of 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 Flash Archive are the following:
|
For a full archive installation, set the value to flash_install.
For a differential archive installation, set the value to flash_update.
For details about the archive_location keyword, refer to archive_location Keyword.
The Flash Archive extraction process does not support auto-layout of partitions.
For detailed instructions, refer to the following:
For detailed instructions, refer to SPARC: To Perform an Installation or Upgrade With the Custom JumpStart Program.
To determine the current dimensions of your tip window, use the stty(1) command.
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.
SPARC only - The system checks hardware and system components and your SPARC based system boots. Booting lasts several minutes.
Note - Starting with the Oracle Solaris 10 9/10 release, if you do not include the auto_reg keyword in the sysidcfg file, you will be prompted to provide your support credentials and proxy information for Auto Registration.
For information about Auto Registration, see Auto Registration in Oracle Solaris 10 8/11 Installation Guide: Planning for Installation and Upgrade.
When the JumpStart program finishes installing the Oracle 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.
|