|
|
1.1 root 1: .\" Copyright (c) 1980 The Regents of the University of California.
2: .\" All rights reserved.
3: .\"
4: .\" Redistribution and use in source and binary forms are permitted provided
5: .\" that: (1) source distributions retain this entire copyright notice and
6: .\" comment, and (2) distributions including binaries display the following
7: .\" acknowledgement: ``This product includes software developed by the
8: .\" University of California, Berkeley and its contributors'' in the
9: .\" documentation or other materials provided with the distribution and in
10: .\" all advertising materials mentioning features or use of this software.
11: .\" Neither the name of the University nor the names of its contributors may
12: .\" be used to endorse or promote products derived from this software without
13: .\" specific prior written permission.
14: .\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
15: .\" WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
16: .\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
17: .\"
18: .\" @(#)config.8 6.4 (Berkeley) 6/24/90
19: .\"
20: .TH CONFIG 8 "June 24, 1990"
21: .UC 4
22: .SH NAME
23: config \- build system configuration files
24: .SH SYNOPSIS
25: .B config
26: [
27: .B \-p
28: ]
29: .I SYSTEM_NAME
30: .SH DESCRIPTION
31: .PP
32: .I Config
33: builds a set of system configuration files from a short file which describes
34: the sort of system that is being configured. It also takes as input a file
35: which tells
36: .I config
37: what files are needed to generate a system.
38: This can be augmented by a configuration specific set of files
39: that give alternate files for a specific machine.
40: (see the FILES section below)
41: If the
42: .B \-p
43: option is supplied,
44: .I config
45: will configure a system for profiling; c.f.
46: .IR kgmon (8)
47: and
48: .IR gprof (1).
49: .PP
50: .I Config
51: should be run from the
52: .B conf
53: subdirectory of the system source (usually /sys/conf).
54: Its argument is the name of a system configuration file
55: containing device specifications, configuration options
56: and other system parameters for one system configuration.
57: .I Config
58: assumes that there is already a directory
59: .I "../SYSTEM_NAME"
60: created and it places all its output files in there.
61: The output of
62: .I config
63: consists of a number of files; for the VAX, they are:
64: .B ioconf.c
65: contains a description
66: of what I/O devices are attached to the system,;
67: .B ubglue.s
68: contains a set of interrupt service routines for devices
69: attached to the UNIBUS;
70: .B ubvec.s
71: contains offsets into a structure used for counting per-device interrupts;
72: .B Makefile
73: is a file used by
74: .IR make (1)
75: in building the system; a set of header files contain definitions of
76: the number of various devices that will be compiled into the system;
77: and a set of swap configuration files contain definitions for
78: the disk areas to be used for swapping, the root file system,
79: argument processing, and system dumps.
80: .PP
81: After running
82: .IR config ,
83: it is necessary to run ``make depend'' in the directory where the new makefile
84: was created.
85: .I Config
86: prints a reminder of this when it completes.
87: .PP
88: If any other error messages are produced by
89: .I config,
90: the problems in the configuration file should be corrected and
91: .I config
92: should be run again.
93: Attempts to compile a system that had configuration errors
94: are likely to meet with failure.
95: .SH FILES
96: .nf
97: /sys/conf/Makefile.vax generic makefile for the VAX
98: /sys/conf/files list of common files system is built from
99: /sys/conf/files.vax list of VAX specific files
100: /sys/conf/devices.vax name to major device mapping file for the VAX
101: /sys/conf/files.ERNIE list of files specific to ERNIE system
102: .fi
103: .SH SEE ALSO
104: ``Building 4.3BSD UNIX System with Config''
105: .br
106: The SYNOPSIS portion of each device in section 4.
107: .SH BUGS
108: The line numbers reported in error messages are usually off by one.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.