Solaris Flash keywords are like custom JumpStart keywords. They define elements of the installation. Each keyword is a command that controls one aspect of how the Solaris Flash software installs the software on a clone system.
Use the following guidelines to format keywords and values:
Keywords and values are separated by a single equal sign with only one pair per line
Keywords are case insensitive
Individual lines can be any length
Each Solaris Flash archive section is defined by the section_begin
and section_end
keywords. For example, the archive
files section includes a section_begin
keyword, though with
a different value. User-defined archive sections are delimited by section_begin
and section_end
keywords, with values appropriate
to each section. The values for the section_begin
and section_end
keywords are described in the following table.
Table 5.2. Values for section_begin
and section_end
Keywords
Archive Section |
Value for |
---|---|
Archive cookie |
|
Archive identification |
|
User-defined sections |
|
Archive files |
|
The following tables describe the keywords for use in the archive identification section and the values you can define for them.
Every section uses the keywords in Table 5–3 to delimit each section.
Table 5.3. Archive Identification Section Keywords: General Keywords
Keywords |
Value Definitions |
Value |
Required |
---|---|---|---|
|
These keywords are used to delimit sections in the archive and are not limited exclusively to the archive identification section. For a description of these keywords, see General Keywords. |
Text |
Yes |
The following keywords, used in the archive-identification section, describe the contents of the archive files section.
Table 5.4. Archive Identification Section Keywords: Contents of Archive Files Section
Keywords |
Value Definitions |
Value |
Required |
---|---|---|---|
|
This keyword uniquely describes the contents of the archive. This value is used by the installation software only to validate the contents of the archive during archive installation. If the keyword is not present, no integrity check is performed. For example, the |
Text |
No |
|
This keyword describes the archive method that is used in the files section.
If the |
Text |
No |
|
This keyword value is the size of the archived files section in bytes. |
Numeric |
No
|
|
This keyword describes the compression algorithm that is used on the files section.
The compression method that is indicated by this keyword is applied to the
archive file created by the archive method indicated by the |
Text |
No |
|
This keyword defines the cumulative size in bytes of the extracted archive. The value is used for file-system size verification. |
Numeric |
No |
The following keywords provide descriptive information about the entire archive. These keywords are generally used to assist you in archive selection and to aid in archive management. These keywords are all optional and are used to help you to distinguish between individual archives. You use options for the flarcreate command to include these keywords. For an example, see Example 3–9.
Table 5.5. Archive Identification Section Keywords: User Describes the Archive
Keywords |
Value Definitions |
Value |
Required |
---|---|---|---|
|
This keyword value is a textual timestamp that represents the time that you created the archive.
|
Text |
No |
|
This keyword value is the name of the master system you used to create the archive.
You can use the flarcreate |
Text |
No |
|
This keyword identifies the archive. The value is generated from the flarcreate
|
Text |
Yes |
|
This keyword value specifies a category for the archive. You use the flarcreate |
Text |
No |
|
The keyword value describes the contents of the archive. The value of this
keyword has no length limit. You use the flarcreate |
Text |
No |
|
This keyword value identifies the creator of the archive. You use the flarcreate
|
Text |
No |
|
This keyword value is a comma-separated list of the kernel architectures that the archive supports.
|
Text list |
No |
The following keywords also describe the entire archive. By default, the values
are filled in by uname when the flash archive is created. If you
create a flash archive in which the root directory is not /
,
the archive software inserts the string UNKNOWN for the keywords. The exceptions
are the creation_node
, creation_release
, and
creation_os_name
keywords.
For creation_node
, the software uses the contents
of the nodename
file.
For creation_release
and creation_os_name
, the software attempts to use the contents of root
directory /var/sadm/system/admin/INST_RELEASE
. If the software is unsuccessful in
reading this file, it assigns the value UNKNOWN.
Regardless of their sources, you cannot override the values of these keywords.
Table 5.6. Archive Identification Section Keywords: Software Describes the Archive
Keyword |
Value |
---|---|
|
The return from uname |
|
The return from uname |
|
The return from uname |
|
The return from uname |
|
The return fromuname |
|
The return from uname |
|
The return from uname |
In addition to the keywords that are defined by the Solaris Flash archive, you can define other keywords. The Solaris Flash archive ignores user-defined keywords, but you can provide scripts or programs that process the archive identification section and use user-defined keywords. Use the following format when creating user-defined keywords:
Begin the keyword name with an X
.
Create the keyword with any characters other than linefeeds, equal signs, and null characters.
Suggested naming conventions for user-defined keywords include the underscore-delimited descriptive method used for the predefined keywords. Another convention is a federated convention similar to the naming of Java packages.
For example, X-department
is a valid name for a user-defined
keyword.
For an example of using options to include user-defined keywords in the archive identification section, see Example 3–9.