Specifications

Driver Installation and Tuning

14-11

2. Generates a valid id ﬁeld value (called a tag) and prepends it to the entry.

3. Generates an rstate ﬁeld with a value of 2, and adds it to the entry, fol-

lowing the id ﬁeld.

Lines of the second form should be used when an rstate value other than 2 must be

speciﬁed. When presented with a line of this form, idmkinit generates only the id ﬁeld

value and prepends it to the entry.

Lines of the third form should be used with caution. When presented with a line of this

form, idmkinit copies the entry to the inittab ﬁle verbatim. It is recommended that

DSPs avoid specifying lines of this form because, if more than one DSP or add-on applica-

tion speciﬁes the same id ﬁeld, idmkinit creates multiple inittab entries containing this

id value. When the init program attempts to process the inittab entries with the

same id, it fails with an error condition.

Note that idmkinit determines which of the three forms is being used by searching each

line for a valid action keyword. Valid action values are:

boot

bootwait

initdefault

off

once

ondemand

powerfail

powerwait

respawn

sysinit

wait

For complete information about the Init ﬁle format, refer to the Init(4) manual page.

Mtune 14

An optional component, the Mtune ﬁle contains deﬁnitions of tunable parameters, includ-

ing default values, for a kernel module type.

When the Mtune component of a DSP is installed, idinstall stores the module's

Mtune ﬁle information in /etc/conf/mtune.d/module-name, where the ﬁle module-

name is the name of the module being installed.

Packages should never access Mtune files in /etc/conf directly; they should use the

idinstall and idtune commands instead.

Following is an example Mtune ﬁle for kma (Kernel Memory Allocation).