Packaging SCO OpenServer 5 drivers for installation
NOTE:
This chapter has not been reviewed for the current release.
The information is generally accurate,
although some details may have changed.
Check the appropriate manual pages
for the most current information.
SCO OpenServer 5 drivers can be packaged
using any of the following methods:
SCO OpenServer 5 Release 5-
Non-BTLD drivers should be installable using
custom(ADM).
BTLD drivers should be linkable with the kernel
at boot time using the programs
link(HW)
or ahslink.
They should also be installable using custom after
the system has booted.
These drivers may be packaged using the
Custom Distribution Mastering Toolkit (CDMT)
as described in
the SCO OpenServer 5 documentation.
SCO OpenServer Release 5.0.5a and later-
SCO OpenServer Release 5.0.5a and later releases
provide full support for the SVR5 packaging tools
in addition to the CDMT packaging tools.
Driver developers may use whichever packaging scheme
they prefer.
See
``Packaging drivers''
for more information about the SVR5 packaging tools.
SCO operating systems before SCO OpenServer 5 Release 5-
Non-BTLD drivers should be installable using
custom.
BTLD drivers should be linkable with the kernel
at boot time using the link command of
boot(HW).
They should be installable into the Link Kit at boot time using
the btld command of boot.
They should also be installable using
installpkg(ADM).
after the system has booted.
These drivers may be packaged using the Software Mastering Toolkit
(SMT) as described in
``Packaging drivers for releases before SCO OpenServer 5 Release 5''.
Drivers packages that have been mastered using
the SMT are installable under
SCO OpenServer 5 Release 5 but they may not be installable in future releases.
© 2005 The SCO Group, Inc. All rights reserved.