All rights reserved.
Redistribution and use in source and binary forms are permitted
provided that the above copyright notice and this paragraph are
duplicated in all such forms and that any documentation,
advertising materials, and other materials related to such
distribution and use acknowledge that the software was developed
by the University of California, Berkeley. The name of the
University may not be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.
@(#)config.8 6.3 (Berkeley) 10/25/88
Config builds a set of system configuration files from a short file which describes the sort of system that is being configured. It also takes as input a file which tells config what files are needed to generate a system. This can be augmented by a configuration specific set of files that give alternate files for a specific machine. (see the FILES section below) If the -p option is supplied, config will configure a system for profiling; c.f. kgmon (8) and gprof (1).
Config should be run from the conf subdirectory of the system source (usually /sys/conf). Its argument is the name of a system configuration file containing device specifications, configuration options and other system parameters for one system configuration. Config assumes that there is already a directory "../SYSTEM_NAME" created and it places all its output files in there. The output of config consists of a number of files; for the VAX, they are: ioconf.c contains a description of what I/O devices are attached to the system,; ubglue.s contains a set of interrupt service routines for devices attached to the UNIBUS; ubvec.s contains offsets into a structure used for counting per-device interrupts; Makefile is a file used by make (1) in building the system; a set of header files contain definitions of the number of various devices that will be compiled into the system; and a set of swap configuration files contain definitions for the disk areas to be used for swapping, the root file system, argument processing, and system dumps.
After running config , it is necessary to run ``make depend'' in the directory where the new makefile was created. Config prints a reminder of this when it completes.
If any other error messages are produced by config, the problems in the configuration file should be corrected and config should be run again. Attempts to compile a system that had configuration errors are likely to meet with failure.
/sys/conf/Makefile.vax generic makefile for the VAX /sys/conf/files list of common files system is built from /sys/conf/files.vax list of VAX specific files /sys/conf/devices.vax name to major device mapping file for the VAX /sys/conf/files.ERNIE list of files specific to ERNIE system
The SYNOPSIS portion of each device in section 4.