Ignite-UX Reference (March 2010, B3921-90005)

instl_adm(4) instl_adm(4)
all clients that have access to that server must have an identical secrets file. The
sd_secrets keyword allows you to specify the contents of the secrets file that are used by
the Ignite-UX server performing the installation.
sysadm_message = cplx_string
Sets the message displayed when the client first boots the cold install process. This message is
only recognized when stored in the configuration that exists in the first 8KB of the *INSTALLFS
file. The instl_adm -a option makes this easy to set and change.
error = cplx_string
error += cplx_string
Used to indicate an error condition such that the cplx_string is displayed to you and the installa-
tion process is not allowed to proceed. The use of the += operator adds a new message separate
from any others. The = operator clears out any other messages previously added so that
cplx_string is the only message seen. If the = operator is used with an empty cplx_string (""), all
error messages using this mechanism are cleared.
warning = cplx_string
warning += cplx_string
Sets the warning message to cplx_string, similar to the error keyword described above;
however, cplx_string is considered a warning message and does not prevent the installation
from proceeding.
note = cplx_string
note += cplx_string
Sets the note message to cplx_string, similar to the error and warning keywords
described above; howev er, cplx_string is considered a notice message and will not prevent
the installation from proceeding.
mod_kernel = cplx-string
mod_kernel += cplx-string
Used to add drivers or tunable parameters to the client’s kernel that is built during the Ignite-UX
process. The format of cplx-string may be either "driver" or "tunable value".
The largest of any tunable parameter that exists in either the /stand/system file or that is
specified by you is used. Beginning with the B.11.23 release, if a tunable is not found in
/stand/system, it is compared with the default value as reported by kctune. Ignite-UX does
not compare the values of formulas to discrete numeric values, two formulas, or hexadecimal val-
ues, in order to determine which is larger. It issues a note message stating that it assumes the last
mod_kernel keyword parsed is larger (regardless of whether it is a formula or discrete numeric
value) and applies it. There is no bounds checking done on tunable parameters.
Decimal values should be in the range from 0 to 2147483647 (2ˆ31-1). The shell that is used to
evaluate these values uses signed 32-bit arithmetic for decimal values, and problems occur when
values exceed this limit. If larger values are needed, the values must be converted to hexadecimal
because the shell does not evaluate them.
Note that any allowable syntax supported by the config command may be used in
mod_kernel keywords. This includes formulas. For example, it is possible to use:
mod_kernel += "ninode (20+8*MAXUSERS+NPTY+" + ${"%d" _inc} + ")"
This example assumes _inc has been initialized to some value in the configuration file.
The = operator overrides any prior global mod_kernel assignments. The += operator adds to
any prior settings. Notice that mod_kernel statements may also be associated with a sw_sel
definition. The = operator does not have any effect on mod_kernel assignments made in a
sw_sel.
Beginning with the B.11.23 release, the format for cplx_string arguments is enhanced. There are
additional formats:
26