Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #650
Difficulty: Medium
Linux distributions have not define their own applications menu for Window Maker.
True or False?
Linux & Unix Commands - Search Man Pages

config(8) [osf1 man page]

config(8)						      System Manager's Manual							 config(8)

config - Builds system configuration files SYNOPSIS
/sys/conf/config [-k] [-p] [-q] system_name FLAGS
Creates a define variable 'KDEBUG' that can be used to conditionally compile source code for kernel debugging. Configure the system for profiling. You must have sources to use this flag. Concatenates and displays all the system configuration files, including any configura- tion files described in the /sys/conf/NAME.list file. DESCRIPTION
The doconfig command calls the config command to build a set of system configuration files from a file that describes the sort of system that is being configured. The config command also takes as input another file that tells it what files are needed to generate a system. This other file can be augmented by a configuration-specific set of files that name alternate files for a specific machine. Normally, you should run the doconfig program and not the config command. If you need to issue the config command, be sure to change your directory to the /sys/conf directory. As an argument to the config command, specify the name of a system configuration file containing device specifications, configuration options and other system parameters for that specific system configuration. The config command places all its output files in the directory The output of config consists of a number of files; each machine type has its own specific set of files. All machine types have a makefile which is used by make during the system build. Typically, there are also a set of header files which 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, you run make depend in the directory where the new makefile was created. 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 be unsuccessful. NOTES
The line numbers reported in error messages are usually off by one. FILES
List of common files used to build the system List of files specific to NAME, where NAME is the value specified for the ident option in the system configuration file Machine-independent portion of the makefile template used for building kernels from binaries Machine-independent portion of the makefile template used for building kernels from sources Machine-dependent portion of the makefile template List of machine- specific files Machine-specific name to major device mapping file RELATED INFORMATION
Commands: make(1), doconfig(8) System Administration delim off config(8)

Check Out this Related Man Page

rc.config(4)						     Kernel Interfaces Manual						      rc.config(4)

rc.config, rc.config.d - files containing system configuration information SYNOPSIS
The system configuration used at startup is contained in files within the directory The file sources all of the files within and and exports their contents to the environment. /etc/rc.config The file is a script that sources all of the scripts, and also sources To read the configuration definitions, only this file need be sourced. This file is sourced by whenever it is run, such as when the command is run to transition between run states. Each file that exists in is sourced, without regard to which startup scripts are to be executed. /etc/rc.config.d The configuration information is structured as a directory of files, rather than as a single file containing the same information. This allows developers to create and manage their own configuration files here, without the complications of shared ownership and access of a common file. /etc/rc.config.d/* Files This is where files containing configuration variable assignments are located. Configuration scripts must be written to be read by the POSIX shell, and not the Bourne shell, or In some cases, these files must also be read and possibly modified by control scripts or the sam program. See sd(4) and sam(1M). For this reason, each variable definition must appear on a separate line, with the syntax: No trailing comments may appear on a variable definition line. Comment statements must be on separate lines, with the comment character in column one. This example shows the required syntax for configuration files: Configuration variables may be declared as array parameters when describing multiple instances of the variable configuration. For example, a system may contain two network interfaces, each having a unique IP address and subnet mask (see ifconfig(1M)). An example of such a dec- laration is as follows: Note that there must be no requirements on the order of the files sourced. This means configuration files must not refer to variables defined in other configuration files, since there is no guarantee that the variable being referenced is currently defined. There is no protection against environment variable namespace collision in these configuration files. Programmers must take care to avoid such prob- lems. /etc/TIMEZONE The file contains the definition of the environment variable. This file is required by POSIX. It is sourced by at the same time the files are sourced. SEE ALSO
rc(1M). rc.config(4)

Featured Tech Videos