DOC HOME SITE MAP MAN PAGES GNU INFO SEARCH PRINT BOOK
 
Introduction to MDI

SVR5 MDI configuration

Configuration information for SVR5 MDI drivers and associated devices is provided in an enhanced bcfg(DSP/4dsp) file for the driver.

The bcfg file contains all configuration information for network drivers into a single file. It is based on the bcfg file used in SCO SVR5 2.X. It is versioned, with version 0 being the SCO SVR5 2.X bcfg files to provide backward compatibility for Open Datalink Interface (ODI) and DLPI drivers on early version of SVR5.

The version 1 bcfg file format is the native format for SVR5 MDI drivers. It is a collection of shell variables that incorporate most of the information that is in SCO OpenServer 5 Adapter Options Files (AOFs).

All configuration information for the driver and supported devices should be provided through the bcfg files rather than through the driver's Space.c(DSP/4dsp) or space.h header file.

Most SVR5 MDI drivers use the Space.c(DSP/4dsp) file only to declare the MODNAME parameter. However, if an MDI driver has parameters that should not be exposed to users, such as inter-frame gap or debugging parameters, it can use a Space.c file for them.

Use the ndcfg command to display all resource manager parameters and the value(s) for any resource manager key. Use the ndcfg -f bcfg_filecommand to check that the bcfg files are syntactically correct.

See ``Configuring SVR5 MDI drivers'' for more information.


© 2005 The SCO Group, Inc. All rights reserved.
OpenServer 6 and UnixWare (SVR5) HDK - June 2005