Run-Time Configuration Commands
User configuration commands invoke device methods during run time.
Item | Description |
---|---|
mkdev | The mkdev command
is invoked to define or configure, or define and configure, devices
at run time. If just defining a device, the mkdev command invokes
the Define method for the device. The Define method
creates the customized device instance in the Customized Devices (CuDv) object class and writes
the name assigned to the device to the stdout file. The mkdev command
intercepts the device name written to the stdout file by the
Define method to learn the name of the device. If user-specified attributes
are supplied with the -a flag, the mkdev command then
invokes the Change method for the device. If defining and configuring a device, the mkdev command invokes the Define method, gets the name written to the stdout file with the Define method, invokes the Change method for the device if user-specified attributes were supplied, and finally invokes the device's Configure method. If only configuring a device, the device must already exist in the CuDv object class and its name must be specified to the mkdev command. In this case, the mkdev command simply invokes the Configure method for the device. |
chdev | The chdev command is used to change the characteristics, or attributes, of a device. The device must already exist in the CuDv object class, and the name of the device must be supplied to the chdev command. The chdev command simply invokes the Change method for the device. |
rmdev | The rmdev command can be used to undefine or unconfigure, or unconfigure and undefine, a device. In all cases, the device must already exist in the CuDv object class and the name of the device must be supplied to the rmdev command. The rmdev command then invokes the Undefine method, the Unconfigure method, or the Unconfigure method followed by the Undefine method, depending on the function requested by the user. |
cfgmgr | The cfgmgr command can be used to configure all detectable devices that did not get configured at boot time. This might occur if the devices had been powered off at boot time. The cfgmgr command is the Configuration Manager and operates in the same way at run time as it does at boot time. The boot time operation is described in Device Configuration Manager Overview . |