idmknod -- update device nodes to reflect kernel configuration


/etc/conf/bin/idmknod [-o device-dir] [-r config-dir] [[-M module-name] ...]
[-s] [-d sdev] [-#]


One of the Installable Driver/Tunable Parameters configuration tools, idmknod reconstructs nodes (block and character special device files) in /dev and its subdirectories, based on the Node(DSP) files for currently configured modules (those with at least one ``Y'' in their System(DSP) files) for entry-type 0 drivers (those with b or c in the ``characteristics'' field of their Master(DSP) files. Any nodes with major numbers corresponding to drivers with a ``K'' flag set in the characteristics fields of their Master file are left unchanged. All other nodes will be removed or created as needed to exactly match the configured Node files.

Any needed subdirectories are created automatically. Subdirectories that become empty as a result of node removal are removed, also.

All other files in the /dev directory tree are left unchanged, including symbolic links.


idmknod takes the following options:

-o device-dir
Install nodes in (or remove them from) the directory specified rather than the default, /dev.

-r config-dir
Use the directory specified, instead of /etc/conf, as the root of the configuration data directories.

Suppress removing nodes; just add new nodes.

-M module-name
Make new nodes in /dev, as specified in the node file for the specified loadable kernel module.

-d sdev
Use the sdev file instead of /etc/conf/cf.d/sdevice for current configuration information.

Print debugging information.

Exit codes

An exit value of zero indicates success. If an error is encountered due to a syntax or format error in a node entry, an advisory message is printed to stdout and the command execution continues. If a serious error is encountered (for example, a required file cannot be found), idmknod exits with a non-zero value and reports an error message.


On the next system reboot after a kernel reconfiguration, in sysinit state, the idmknod command is run automatically (by idmkenv) to establish the correct representation of device nodes in the /dev directory tree for the running kernel. Also, idmknod (with the -M option) is called by idbuild when loadable kernel module configuration is requested. idmknod can be executed as a user level command to test modification of the /dev directory before a Driver Software Package (DSP) is built. It is useful in installation scripts that do not reconfigure the kernel, but that need to create /dev entries.


idbuild(ADM), idinstall(ADM), idmkinit(ADM), Interface(DSP) Master(DSP), mknod(S), Node(DSP), System(DSP)
© 2005 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 - 02 June 2005