NAME

config − configure a UNIX system

SYNOPSIS

/etc/config [ −p ] [ −[U|B|C] devname ] dfile

DESCRIPTION

config builds a set of system configuration files from a short file, which describes the system, and three other files, which describe the standard and optional files.  If the −p option is supplied, config will configure a system for profiling; c.f.  kgmon(1M) and gprof(1).  The −p option is only functional if kernel source is available. 

The −U −B −C options are query commands that will check the system description file for information about configured device drivers.  Given a device name as an argument the −U option will return the unit number of the device printed to standard output.  The −B option will return the block major number of the device while the −C option will return the character major number of the device printed to standard output.  These options are only valid one per invocation of config, and the normal operation of configuring a system image is not performed.  These options only work for devices that have been configured with an accompanying driver specification. 

The system description file has to be specified as an argument. 

Config should be run from the cf directory (usually /usr/src/uts/machine/cf) within the system source tree. Several files which control the execution of config exist in that directory. 
 
config generates a machine-type specific work directory (if it’s not already there) for configuration dependent files.  The current list of machine-type specific work directories is:

../M88K
This is the Series 4000 kernel.  It runs on Series 4000 machines. It is a multi-threaded, multi-processor kernel. This is the kernel that all Series 4000 customers get on the miniroot and root tapes.

../M88K-RT
This is the Series 4000 kernel with realtime extensions.

../NH5000
This is the Series 5000 kernel.  It runs on Series 5000 machines. It is a multi-threaded, multi-processor kernel. This is the kernel that all Series 5000 customers get on the miniroot and root tapes.

../NH5000-RT
This is the Series 5000 kernel with realtime extensions.

Series 4000 and Series 5000 are terms used to designate a specific architecture.  These terms are used in both hard copy and on-line documentation. 
 
Series 4000 refers to an architecture that is based on the Motorola MC88100 microprocessor family.  Series 4000 systems are all members of the Night Hawk family.  There are two multiprocessor configurations; the HN4400 and HN4800.  The HN4400 is the low-end single cpu board system that can have 1, 2, or 4 processors.  The HN4800 is the high-end system that can have from 1 to 4 cpu boards and from 1 to 8 processors.
 
Series 5000 refers to an architecture that is based on the Motorola MC88110 microprocessor family.  Series 5000 systems are all members of the Night Hawk family.  The HN5800 is a high-end system that can have from 1 to 4 cpu boards and from 1 to 8 processors.

Your system is shipped with some subset of these directories depending on the hardware and software you have purchased. 

When config runs successfully on your configuration file, it generates several files in the work directory. They are:

Makefile
a configuration dependent makefile used by the make(1) utility when linking the kernel. 

config.h
a configuration header file, that defines the system configuration variables (in # define VAR value format). 

ioconf.c
file that contains the I/O configuration tables used by the system during the auto-configuration phase.

depends
a list of the header files which ../cf/space.c and ../cf/comspace.c depend on for your particular configuration. 

vbavec.drivers
file that contains interrupt entry routines for drivers configured with interrupt vectors.

Unless you question the operation of config or the system auto-configuration process, you need not look at any of these files. 

The user must supply dfile; it must contain device information for the user’s system. The configuration file must include at least the following information: o machine type
o node name
o maximum number of users
o location of the root file system
o available hardware

In addition the configuration file may include a set of definitions for system parameters. Parameters which can be defined by the user include:

version - version name of the system
buffers - number of ’system’ buffers
inodes  - number of ’inode table’ entries
files   - number of ’open-file table’ entries
calls   - number of ’callout table’ entries
procs   - number of ’process table’ entries
texts   - number of ’text table’ entries
clists  - number of ’character list’ buffers
maxproc - number of processes per non super-user.

If any or some of those parameters are not defined in the configuration file the default value is used. This value depends on the actual physical memory size (for buffers), and on the maxusers parameter. 

After running config you can generate the new system image by executing make in the cf directory.  To configure a new controller into the system some additional changes are needed. See Configuring a new device driver in the CX/UX System Administration Manual. 

If you get any error messages from config, fix the problems in your configuration file and try again. If you try to compile a system which had configuration errors, you will probably get errors. 

The header file ipcconfig.h contains the configurable parameters for messages, semaphores, and shared memory.  These parameters are changed by editing ipcconfig.h and running config. 

FILES

Makefile.XXXtemplate for makefile for machine type XXX
cputype.XXXvalid cpu types for machine type XXX
depends.XXXsource file dependancies for machine type XXX
devices.XXXdevice descriptions for machine type XXX
fileslist of kernel source files for all machine types
files.XXXlist of kernel source files for machine type XXX
ioconf.ci/o devices attached to the system.
vbavec.driversinterrupt vectors configured in the system.
config.hdevices and system configuration parameters.
ipcconfig.h   configurable parameters for messages,
semaphores, shared memory

SEE ALSO

"Configuring the System" in the CX/UX System Administration Manual. 

BUGS

The line numbers reported in error messages are usually off by one. 

CX/UX Administrator’s Reference