Return to 1.t CVS log

Up to [CSRG BSD Unix] / 43BSDReno / share / doc / smm / 02.config

Annotation of 43BSDReno/share/doc/smm/02.config/1.t, revision 1.1.1.1

1.1       root        1: .\" Copyright (c) 1983 Regents of the University of California.
                      2: .\" All rights reserved.  The Berkeley software License Agreement
                      3: .\" specifies the terms and conditions for redistribution.
                      4: .\"
                      5: .\"    @(#)1.t 6.3 (Berkeley) 6/3/86
                      6: .\"
                      7: .\".ds RH Introduction
                      8: .ne 2i
                      9: .sp 3
                     10: .NH
                     11: INTRODUCTION
                     12: .PP
                     13: .I Config
                     14: is a tool used in building 4.3BSD system images (the UNIX kernel).
                     15: It takes a file describing a system's tunable parameters and
                     16: hardware support, and generates a collection
                     17: of files which are then used to build a copy of UNIX appropriate
                     18: to that configuration.
                     19: .I Config
                     20: simplifies system maintenance by isolating system dependencies
                     21: in a single, easy to understand, file.
                     22: .PP
                     23: This document describes the content and 
                     24: format of system configuration
                     25: files and the rules which must be followed when creating 
                     26: these files.  Example configuration files are constructed
                     27: and discussed.
                     28: .PP
                     29: Later sections suggest guidelines to be used in modifying
                     30: system source and explain some of the inner workings of the
                     31: autoconfiguration process.  Appendix D summarizes the rules
                     32: used in calculating the most important system data structures
                     33: and indicates some inherent system data structure size
                     34: limitations (and how to go about modifying them).

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.