1.\" Copyright (c) 1980, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. 9.\" 2. Redistributions in binary form must reproduce the above copyright 10.\" notice, this list of conditions and the following disclaimer in the 11.\" documentation and/or other materials provided with the distribution. 12.\" 3. All advertising materials mentioning features or use of this software 13.\" must display the following acknowledgement: 14.\" This product includes software developed by the University of 15.\" California, Berkeley and its contributors. 16.\" 4. Neither the name of the University nor the names of its contributors 17.\" may be used to endorse or promote products derived from this software 18.\" without specific prior written permission. 19.\" 20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 23.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 30.\" SUCH DAMAGE. 31.\" 32.\" @(#)config.8 8.2 (Berkeley) 4/19/94 33.\" $FreeBSD$ 34.\" 35.Dd April 19, 1994 36.Dt CONFIG 8 37.Os BSD 4 38.Sh NAME 39.Nm config 40.Nd build system configuration files 41.Sh SYNOPSIS 42.Nm 43.Op Fl gp 44.Op Fl d Ar destdir 45.Ar SYSTEM_NAME 46.Sh DESCRIPTION 47This is the old version of the 48.Nm 49program. 50It understands the old autoconfiguration scheme 51used on the HP300, i386, DECstation, and derivative platforms. 52The new version of config is used with the 53SPARC platform. 54Only the version of 55.Nm 56applicable to the architecture that you are running 57will be installed on your machine. 58.Pp 59.Nm 60builds a set of system configuration files from the file 61.Ar SYSTEM_NAME 62which describes 63the system to configure. 64A second file 65tells 66.Nm 67what files are needed to generate a system and 68can be augmented by configuration specific set of files 69that give alternate files for a specific machine 70(see the 71.Sx FILES 72section below). 73.Pp 74Available options and operands: 75.Bl -tag -width SYSTEM_NAME 76.It Fl d Ar destdir 77Use 78.Ar destdir 79as the output directory, instead of the default one. 80Note 81that config does not append 82.Ar SYSTEM_NAME 83to the directory given. 84.It Fl g 85Configure a system for debugging. 86.It Fl p 87Configure a system for profiling; for example, 88.Xr kgmon 8 89and 90.Xr gprof 1 . 91If two or more 92.Fl p 93options are supplied, 94.Nm 95configures a system for high resolution profiling. 96.It Ar SYSTEM_NAME 97Specify the name of the system configuration file 98containing device specifications, configuration options 99and other system parameters for one system configuration. 100.El 101.Pp 102.Nm 103should be run from the 104.Pa conf 105subdirectory of the system source (usually 106.Pa /sys/ARCH/conf ) , 107where 108.Pa ARCH 109represents one of the architectures supported by 110.Fx . 111.Nm 112creates the directory 113.Pa ../compile/SYSTEM_NAME 114or the one given with the 115.Fl d 116option 117as necessary and places all output files there. 118The output of 119.Nm 120consists of a number of files; for the 121.Tn i386 , 122they are: 123.Pa ioconf.c , 124a description 125of what I/O devices are attached to the system; 126.Pa Makefile , 127used by 128.Xr make 1 129in building the system; 130header files, 131definitions of 132the number of various devices that will be compiled into the system. 133.Pp 134After running 135.Nm , 136it is necessary to run 137.Dq Li make depend 138in the directory where the new makefile 139was created. 140.Nm 141prints a reminder of this when it completes. 142.Pp 143If any other error messages are produced by 144.Nm , 145the problems in the configuration file should be corrected and 146.Nm 147should be run again. 148Attempts to compile a system that had configuration errors 149are likely to fail. 150.Pp 151If the option "INCLUDE_CONFIG_FILE" is used in the configuration file the 152entire input file is embedded in the new kernel. This means that 153.Xr strings 1 154can be used to extract it from a kernel: 155to extract the configuration information, use the command 156.Bd -literal 157strings kernel | grep ___ 158.Ed 159.Sh DEBUG KERNELS 160Traditional BSD kernels compiled without symbols due to the heavy load on the 161system when compiling a 162.Dq debug 163kernel. A debug kernel contains complete symbols for all the source files, and 164enables an experienced kernel programmer to analyse the cause of a problem. The 165debuggers available prior to 4.4BSD-Lite were able to find some information 166from a normal kernel; 167.Xr gdb 1 168provides very little support for normal kernels, and a debug kernel is needed 169for any meaningful analysis. 170.Pp 171For reasons of history, time and space, building a debug kernel is not the 172default with 173.Fx : 174a debug kernel takes up to 30% longer to build and 175requires about 30 MB of disk storage in the build directory, compared to about 6 176MB for a non-debug kernel. A debug kernel is about 11 MB in size, compared to 177about 2 MB for a non-debug kernel. This space is used both in the root file 178system and at run time in memory. Use the 179.Fl g 180option to build a debug kernel. With this option, 181.Nm 182causes two kernel files to be built in the kernel build directory: 183.Bl -bullet 184.It 185.Nm kernel.debug 186is the complete debug kernel. 187.It 188.Nm kernel 189is a copy of the kernel with the debug symbols stripped off. This is equivalent 190to the normal non-debug kernel. 191.El 192.Pp 193There is currently little sense in installing and booting from a debug kernel, 194since the only tools available which use the symbols do not run on-line. There 195are therefore two options for installing a debug kernel: 196.Bl -bullet 197.It 198.Nm make 199.Ar install 200installs 201.Nm kernel 202in the root file system. 203.It 204.Nm make 205.Ar install.debug 206installs 207.Nm kernel.debug 208in the root file system. 209.El 210.Sh FILES 211.Bl -tag -width /sys/ARCH/compile/LOCAL -compact 212.It Pa /sys/conf/files 213list of common files system is built from 214.It Pa /sys/conf/Makefile.ARCH 215generic Makefile for the 216.Pa ARCH . 217.It Pa /sys/conf/files.ARCH 218list of 219.Pa ARCH 220specific files 221.It Pa /sys/ARCH/compile/LOCAL 222default kernel build directory for system 223.Pa LOCAL 224on 225.Pa ARCH . 226.El 227.Sh SEE ALSO 228The 229.Sx SYNOPSIS 230portion of each device in section 4. 231.Rs 232.%T "Building 4.3 BSD UNIX System with Config" 233.Re 234.Sh BUGS 235The line numbers reported in error messages are usually off by one. 236.Sh HISTORY 237The 238.Nm 239command appeared in 240.Bx 4.1 . 241