The driver package consists of the compiled driver object file and the DSP (Driver Software Package). files that the system uses to install and configure the driver on the target system. See ``DSP (Driver Software Package)''.
For information about packaging SCO OpenServer 5 drivers, see ``Packaging SCO OpenServer 5 drivers for installation''.
Use the following tools to install and configure drivers:
|idinstall||Install driver and configuration files. idinstall calls idresadd to update the resource manager with information from the System(DSP/4dsp) file.|
|idbuild||Configure/rebuild new kernel with newly installed (or removed) driver|
|idtune||Set value for tunable driver parameters|
Use the pkgmk command to create a DSP package that contains all the driver component files. Then, use the pkgtrans command to transfer the package to the destination media (usually a floppy disk).
Once your loadable driver is installed, the next step is to configure it into the system using the idbuild command.
There are two ways you can configure your loadable driver using idbuild: a deferred build and an immediate build:
When no options are given, the idbuild command does not rebuild the kernel. It simply sets a rebuild flag and exits. The next time the system is rebooted, the reboot process rebuilds the kernel and reconfigures all modules flagged as loadable.
Some of the tasks the -M option performs to configure your loadable driver include placing the driver's loadable image in the /etc/conf/mod.d directory, and creating the necessary nodes in the /dev directory. If your DSP contains an Init(DSP/4dsp) component, idinstall adds and activates your driver's inittab entries; they will take effect the next time the system's init state changes. idbuild also registers your driver with the kernel to make it available to the rest of the system.
The -S option is available to configure drivers as if all had been marked as static, and not loadable. If this option is specified, all the modules are treated as static modules. Use of this option does not prevent the configuration of any newly installed loadable modules later.
SVR5 drivers are packaged with the pkg* tools. SCO OpenServer 5 drivers can be packaged with either the CDMT tools or, for SCO OpenServer Release 5.0.5a and later, can use the SVR5 pkg* tools.
This article summarizes the packaging facilities for SVR5. For more information, see:
The SVR5 packaging tools include a set of commands that work with a set of specifically-named files. See ``Packaging your software applications'' for general information about using these tools.
The packaging tools are:
The packaging commands use the following files: