- Overview
- Identifying the Master Machine
- Creating and Administering Archives
- Additional Profile Keywords
- Using Flash in an Example
- Summary
Additional Profile Keywords
Installation of Flash archives is supported by addition off flash_install as a valid value for the installation_type keyword.
NOTE
Specifying a Flash installation type restricts the number of keywords that can be specified in the profile. See the "Adding the Installation Client" on page 1 for specific details.
The archive_location profile keyword has also been added. The archive_location profile keyword specifies the retrieval method and location, specific to the retrieval method, of the archive:
archive_location retrieval_type location_specifier |
where retrieval_type can be any one of the following:
- nfs
- http
- local_tape
- local_device
- local_file
These retrieval types and the location specifier are explained in the following several sections.
Remote Archive Location Specifiers
The nfs and http retrieval types specify the location of the Flash archive on a JumpStart server, NFS server, or HTTP (Web) server. This specification must be provided in one of the following, syntactically equivalent, ways:
archive_location nfs server:/fully/qualified/path/filename |
or:
archive_location nfs://server/fully/qualified/path/filename |
Where:
server is the name of the JumpStart server or the NFS server.
The archive must be shared from the NFS server with options that enable the path to be readable by the client. Additionally, the permissions on the archive file must be such that the file can be read by the client.
The http retrieval type uses the following syntax:
archive_location http server:port_number /URL/to/file opts |
Where:
server is the HTTP server name.
port_number is the optional port number that the HTTP daemon is listening on (defaults to port 80).
/full/path/filename is the fully qualified path to the Flash archive file.
opts are the optional keywords
auth basic username password specifies the user name and password to access
password-protected HTTP server.
NOTE
When the user name and password are stored in the JumpStart software profile, they may be readable by all users on the system. The use of this option may be a security risk. Therefore, the use of the auth basic option is not recommended.
timeout minutes specifies in minutes the HTTP server timeout value.
proxy host:port specifies the HTTP proxy server and port number.
As with the nfs retrieval type, specify the http retrieval type in the alternate syntax of:
archive_location http://server/URL/to/file opts |
Local Archive Location Specifiers
Access the Flash archive from a device local to the installation client. Valid local devices are disk, CD-ROM, or tape devices. To specify a disk device, use the following location specifier:
archive_location local_device cXtYdZsN /full/path/filename FStype |
Where:
cXtYdZsN is the Solaris OE device specification for the disk device.
FStype is the optional filesystem type, either ufs or hsfs. If a filesystem type is not specified, the filesystem is first accessed as ufs. If that fails, hsfs access is then attempted.
Specify a local tape device as follows:
archive_location local_tape tapedevice optional_position |
Where:
tapedevice is the full specification to the tape device, for example, /dev/rmt/0h.
optional_position is the optional position, specifying the number of End Of File (EOF) marks to skip over on the tape.
Additionally, access archive files from the miniroot by using the local_file retrieval type:
archive_location local_file /full/path/filename |