Specifications

D
evice Driver Programming
14-4
NOTE
The exact pathnames of installed files in /etc/conf can change
in future releases. These files should be accessed only by using
idinstall, and should never be accessed directly; this is neces-
sary to ensure they work in the future.
idinstall -a requires that the module specified is not currently installed.
idinstall -u module-name performs an Update DSP (that is, 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.
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 command. idinstall fails if there is
not enough space and exits with a non-zero return code.
After you install or remove a module with idinstall, you must use idbuild to have
the change take effect.
idmkinit 14
idmkinit reconstructs /etc/inittab from the Init files in /etc/conf/init.d.
The new inittab is normally placed in the /etc/conf/cf.d directory, although this
can be changed through the -o option.
In the sysinit state during the next system reboot after a kernel reconfiguration, the
idmkinit command is called automatically (by idmkenv) to establish the correct
/etc/inittab for the running (newly-built) kernel.idmkinit is also called by
idbuild when loadable kernel module configuration is requested.idmkinit can be
executed as a user level command to test a modification of inittab before a DSP is
actually built. It is also useful in installation scripts that do not reconfigure the kernel, but
which need to create inittab entries. In this case, the inittab generated by
idmkinit must be copied to /etc/inittab, and an init q command must be run
for the new entry to take effect.
idmknod 14
idmknod reconstructs nodes (block and character special device files) in /dev and its
subdirectories, based on the Node files for currently configured modules (those with at
least one Y in their System files). Any nodes for devices with an r flag set in the
characteristics fields of their Master file are left unchanged. The boot devices
/dev/root, /dev/rroot, /dev/swap, /dev/rswap are also left unchanged. All
other nodes are removed or created as needed to exactly match the configured Node files.
Any needed subdirectories are created automatically. Subdirectories which become empty
as a result of node removal are removed as well.
All other files in the /dev directory tree are left unchanged, including symbolic links.