Follow Techotopia on Twitter

On-line Guides
All Guides
eBook Store
iOS / Android
Linux for Beginners
Office Productivity
Linux Installation
Linux Security
Linux Utilities
Linux Virtualization
Linux Kernel
System/Network Admin
Scripting Languages
Development Tools
Web Development
GUI Toolkits/Desktop
Mail Systems
Eclipse Documentation

How To Guides
General System Admin
Linux Security
Linux Filesystems
Web Servers
Graphics & Desktop
PC Hardware
Problem Solutions
Privacy Policy




Solaris Express Installation Guide: Custom JumpStart and Advanced Installations
Previous Next

SPARC: Performing 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. 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.

To Prepare to Install a Solaris Flash Archive With a Custom JumpStart Installation

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.

  1. Review the following limitations.



    Caution: When using the archive_location keyword to install a Solaris Flash archive, the archive and the installation media must contain identical operating system versions.

    For example, if the archive is a Solaris Express 5/07 operating system and you are using DVD media, then you must use Solaris Express 5/07 DVD media to install the archive. If the operating systems versions do not match, the installation on the clone system fails.

    Caution - A Solaris Flash archive cannot be properly created when a non-global zone is installed. The Solaris Flash feature is not compatible with the Solaris Zones partitioning technology. If you create a Solaris Flash archive, the resulting archive is not installed properly when the archive is deployed under these conditions:

    • The archive is created in a non-global zone

    • The archive is created in a global zone that has non-global zones installed

  2. 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).

  3. 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:


    Initial Installation

    Differential Archive




    fdisk (x86 only)




    Note - You cannot set the filesys keyword to the value auto.




    (required) install_type















    1. 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.

    2. 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.

    3. Specify the file system configuration.

      The Solaris Flash archive extraction process does not support auto-layout of partitions.

    4. (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.
    5. (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.
  4. On the install server, add the clients that you are installing with the Solaris Flash archive.

    For detailed instructions, refer to the following:

  5. 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.

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

  1. If the system is part of a network, ensure that an Ethernet connector or similar network adapter is attached to your system.
  2. 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.

  3. 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.
  4. If you are using a profile diskette, insert the profile diskette in the system's diskette drive.
  5. 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

      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.

  6. If you did not preconfigure system information in the sysidcfg file, when prompted, answer the questions about system configuration.
  7. 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

SPARC: Command Reference for the boot Command

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.




Specifies to boot from a CD or a DVD or to boot from an install server on the network.

  • cd-dvd - Use cdrom to boot from a CD or a DVD.

  • net - Specifies 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.

  • url – Specifies the path to the files. You can specify a URL for files that are located in an HTTP or HTTPS server:

    HTTP server

    • 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:
    • 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:
  • ask – Specifies that the installation program prompt you to type the location of the compressed configuration file. The prompt happens after the system boots and connects to the network. If you use this option, you are not able to do a completely hands off JumpStart installation.

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


  • dhcp – Specifies to use a DHCP server to obtain network installation information that is needed to boot the system. This option is not needed for a JumpStart installation. If you do not specify to use a DHCP server by typing dhcp, the system uses the /etc/bootparams file or the naming service bootparams database. For example, you would not specify dhcp if you wanted keep a static IP address.

  • The options nowin and text do not apply to a JumpStart installation. These options are useful with an interactive installation. For more information, see To Install or Upgrade With the Solaris Installation Program in Solaris Express Installation Guide: Basic Installations.

Previous Next

  Published under the terms fo the Public Documentation License Version 1.01. Design by Interspire