idinstall expects to find driver/module component files in the current directory. When components are installed or updated with -a or -u option, they are copied into subdirectories of the /etc/conf directory and then deleted from the current directory, unless the -k flag is used.
In this case, the command requires and installs the DSP Driver.o, Master, and System components, and optionally installs any other components whose files are present in the current directory.
Alternatively, individual components can be installed by using appropriate options. The Dtune and *.bcfg components have no corresponding option letters and are only installed in the default case.
The Driver.o, Modstub.o, Space.c, and Stubs.c components are moved to a directory named /etc/conf/pack.d/module-name. The remaining components are stored in directories under /etc/conf, which are organized by component type, in files named module-name. For example, the Node file would be moved to /etc/conf/node.d/module-name. Driver packages should not directly access /etc/conf files.
When the Driver.o component is installed, idinstall(ADM) looks for any filename that matches the pattern Driver*.o and installs each file. This allows the DSP to install multiple driver binaries that can be dynamically selected by idtype(ADM).
idinstall -a requires that the module specified is not currently installed.
idinstall -u allows an Update DSP (one that replaces an existing device driver component) to be installed. It overlays the files of the old DSP with the files of the new DSP. idinstall -u requires that the module specified is currently installed.
idinstall -M works whether or not the module is currently installed. It copies into the configuration directories any component files which are not yet installed or are newer than the installed versions. In any case, the files in the current directory are not removed.
When the -a or -u options are used, unless the -e option is used as well, idinstall attempts to verify that enough free disk space is available to start the reconfiguration process. This is done by calling the idspace(ADM) command. idinstall will fail if there is not enough space and will exit with a non-zero return code.
When the -a or -u options are used to install hardware drivers (the Master file has an ``h'' in the ``characteristics'' field), idinstall calls idresadd to add a default Resource Manager database entry based on the information in the System file of the DSP, unless the -N or -R option is used.
When the -d option is used with a hardware driver, any default resource manager entries for the driver will be removed. Non-default entries will have their MODNAME parameter removed. See cm_params(D5).
Device package already exists Cannot make the driver package directory Cannot remove driver package directory Local directory does not contain a Driver object (Driver.o) file Local directory does not contain a Master file Local directory does not contain a System file Cannot remove driver entryIf a module fails to install during a kernel reconfiguration (using idbuild), a message is displayed indicating the failure, then the reconfiguration continues.