Installing Web Start Flash Archives With a Custom JumpStart Installation

This section provides the procedure for using the custom JumpStart installation method to install Web Start Flash archives that are stored on the following:

• NFS server

• HTTP server

• Local tape

• Local device, including CD

• Local file

To Install a Web Start Flash Archive With a Custom JumpStart Installation

1. On the install server, create the custom JumpStart rules file.

   For detailed instructions about creating custom JumpStart files, refer to Chapter 18, Preparing Custom JumpStart Installations.

2. On the install server, create the custom JumpStart profile file.

   1. Set the value of the keyword install_type as flash_install.

   2. Add the path to the Web Start Flash archive by using the new archive_location keyword.

      For details about the archive_location keyword, refer to archive_location Keyword.

   3. Specify the file system configuration.

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

   4. (Optional) If you want to install layered Web Start Flash archives on the clone system, add one archive_location line for each archive that you want to install.

   ---

   Note –

   From the existing list of custom JumpStart keywords in Chapter 18, Preparing Custom JumpStart Installations, the only keywords valid when you install a Web Start Flash archive are:

   • fdisk (IA only)

   • filesys – You cannot set the filesys keyword to the value auto.

   • install_type (required)

   • partitioning – You can only set the partitioning keyword to the values explicit or existing.

   ---

3. On the install server, add the clients that you are installing with the Web Start Flash archive.

   For detailed instructions, refer to Adding Systems to Be Installed From the Network.

4. Perform the custom JumpStart installation on the clone systems.

   For detailed instructions, refer to Chapter 21, Performing a Custom JumpStart Installation.

archive_location Keyword

When you use the custom JumpStart installation method to install a Web Start Flash archive, you must include a new custom JumpStart keyword in the profile file. The new keyword is archive_location and the syntax for the keyword is:

archive_location retrieval_type location

The values of retrieval_type and location depend on where the Web Start Flash archive is stored. The following sections contain the values you can use for retrieval_type and location and examples of how to use the archive_location keyword.

• NFS Server

• HTTP Server

• Local Tape

• Local Device

• Local File

NFS Server

If the archive is stored on an NFS server, use the following syntax for the archive_location keyword.

archive_location nfs server_name:/path/filename retry n

In this command line:

• server_name is the name of the server where you stored the archive.

• path is the location of the archive to be retrieved from the specified server. If the path contains $HOST, the Web Start Flash installation utilities replace $HOST with the name of the clone system that you are installing.

• filename is the name of the Web Start Flash archive file.

• retry n is an optional keyword. n is the maximum number of times the Web Start Flash utilities attempt to mount the archive.

Examples:

archive_location nfs golden:/archives/usrarchive

Or

archive_location nfs://golden/archives/usrarchive

HTTP Server

If the archive is stored on an HTTP server, use the following syntax for the archive_location keyword.

archive_location http server_name:port path/filename optional_keywords

In this command line:

• server_name is the name of the server where you stored the archive. server_name can be a port number or the name of a TCP service that has a port number that is determined at runtime.

• port is an optional port. If you do not specify a port, the Web Start Flash installation utilities use the default HTTP port number, 80.

• path is the location of the archive to be retrieved from the specified server. If the path contains $HOST, the Web Start Flash installation utilities replace $HOST with the name of the clone system that you are installing.

• filename is the name of the Web Start Flash archive file.

• optional_keywords are the optional keywords you can specify when you retrieve a Web Start Flash archive from an HTTP server.

  Table 15–1 Optional Keywords to Use With archive_location http

  Keywords	Value Definitions
  auth basic username password	If the archive is located on an HTTP server that is password protected, you must include the username and password that you need to access the HTTP server in the profile file.   Note – The use of this authentication method in a profile that is intended for use with custom JumpStart is risky, as unauthorized users might have access to the profile file that contains the password.
  timeout min	The timeout keyword enables you to specify, in minutes, the maximum length of time that is allowed to pass without receipt of data from the HTTP server before the connection is closed, reopened, and resumed from the point where the timeout occurred. If you specify a timeout value of 0 (zero), the connection is not reopened because of inactivity. If a timeout reconnection occurs, the Web Start Flash installation utilities attempt to resume at the last known position in the archive. If the Web Start Flash installation utilities cannot resume at the last known position, the retrieval restarts from the beginning of the archive and the data retrieved prior to the timeout is discarded.
  proxy host:port	The proxy keyword allows you to specify a proxy host and proxy port. You can use a proxy host to retrieve a Web Start Flash archive from the other side of a firewall. You must supply a proxy port when you specify the proxy keyword.

Examples:

archive_location http silver /archives/usrarchive auth basic user1 secret timeout 5 

Or

archive_location http://user1:secret@silver/archives/usrarchive timeout 5 

Local Tape

If the archive is stored on a tape, use the following syntax for the archive_location keyword.

archive_location local_tape device  position

In this command line:

• device is the name of the tape drive where you stored the Web Start Flash archive. If the device name is a canonical path, the Web Start Flash installation utilities retrieve the archive from the path to the device node. If you supply a device name that is not a canonical path, the Web Start Flash installation utilities add /dev/rmt/ to the path.

• position designates the place on the tape drive where you saved the archive. If you do not supply a position, the Web Start Flash installation utilities retrieve the archive from the current position on the tape drive. By specifying a position, you can place a begin script or a sysidcfg file on the tape drive before the archive.

Examples:

archive_location local_tape /dev/rmt/0n 5

Or

archive_location local_tape 0n 5

Local Device

You can retrieve a Web Start Flash archive from a local device if you stored the Web Start Flash archive on a file system-oriented, random-access device, such as a diskette or a CD-ROM. Use the following syntax for the archive_location keyword.

You can retrieve an archive from stream-oriented devices, such as tape, by using the syntax for local tape.

archive_location local_device device path/filename file_system_type

In this command line:

• device is the name of the drive where you stored the Web Start Flash archive. If the device name is a canonical path, it is mounted directly. If you supply a device name that is not a canonical path, the Web Start Flash installation utilities add /dev/dsk/ to the path.

• path is the path to the Web Start Flash archive, relative to the root of the file system on the device you specified. If the path contains $HOST, the Web Start Flash installation utilities replace $HOST with the name of the clone system that you are installing.

• filename is the name of the Web Start Flash archive file.

• file_system_type specifies the type of file system on the device. If you do not supply a file system type, the Web Start Flash installation utilities attempt to mount a UFS file system. If the UFS mount fails, the Web Start Flash installation utilities attempt to mount an HSFS file system.

Examples:

To retrieve an archive from a local hard drive that is formatted as a UFS file system:

archive_location local_device c0t0d0s0 /archives/$HOST

To retrieve an archive from a local CD-ROM that has an HSFS file system:

archive_location local_device c0t0d0s0 /archives/usrarchive

Local File

You can retrieve an archive that you stored in the miniroot from which you booted the clone system as a local file. When you perform a custom JumpStart installation, you boot the system from a CD-ROM or an NFS-based miniroot. The installation software is loaded and run from this miniroot. Therefore, a Web Start Flash archive that you stored in the CD-ROM or NFS-based miniroot is accessible as a local file. Use the following syntax for the archive_location keyword.

archive_location local_file path/filename 

In this command line:

• path is the location of the archive. The path must be accessible to the system as a local file while the system is booted from the Solaris 8 Installation CD. The system cannot access /net when it is booted from the Solaris 8 Installation CD.

• filename is the name of the Web Start Flash archive file.

Examples:

archive_location local_file /archives/usrarchive

Or

archive_location local_file:/archives/usrarchive