Installing, configuring, and packaging SVR5 drivers

• ``Configuring SVR5 MDI drivers''

• ``Packaging storage device drivers''

• ``Packaging STREAMS modules and drivers''

• SCO OpenServer 5 ODDI drivers are installed and configured with the methods described in ``Linking and testing SCO OpenServer 5 drivers''.

  The native SCO OpenServer 5 packaging tools for drivers are documented in ``Packaging SCO OpenServer 5 drivers for installation''. Drivers that install on SCO OpenServer Release 5.0.5a and later releases can instead be packaged with the SVR5 packaging tools, although the contents of the DSP files must match the SCO OpenServer 5 requirements.

The process of installing, configuring, and packaging a driver can be summarized as follows:

1. Compile the driver source code into a Driver.o file.

2. Create the Driver Software Package (DSP) with the Driver.o file and other files that are required to define the driver and device to the operating system.

3. Run the idinstall command to install the DSP files. idinstall calls idresadd to update the resource manager database with information from the DSP files. When testing a driver, you may want to use the -k option to idinstall so that the DSP files are not deleted from the driver's private directory when they are installed in the appropriate system directories.

4. Run the idbuild command to configure the driver, create special device files for the devices associated with the driver, and rebuild a kernel with the new driver.

5. If necessary, modify the configuration using the dcu command or, for MDI drivers, the netcfg command.

When the driver is released for production, it will need packaging scripts such as postinstall to run the commands that install the driver and DSP on the target system. We recommend that you develop the packaging scripts along with the driver and use those scripts even when installing the driver for preliminary testing during the development cycle. This saves you the effort of having to do a separate testing effort on the packaging scripts after the driver software is completed and enables you to capture all the installation steps that are required at the time you discover them.