'\"macro stdmacro
.if n .pH @(#)system	40.14 of 10/10/89
.\" Copyright 1989 AT&T
.nr X
.if \nX=0 .ds x} system 4 "" "\&"
.if \nX=1 .ds x} system 4 ""
.if \nX=2 .ds x} system 4 "" "\&"
.if \nX=3 .ds x} system "" "" "\&"
.TH \*(x}
.SH NAME
\f4system\f1 \- system configuration information file
.SH DESCRIPTION
The \f4system\fP file is used during the configuration of a new operating system
to obtain configuration information that cannot be obtained
from the Equipped Device Table (EDT).
The system file is \f4/stand/system\f1.
.P
The \f4system\f1 file generally contains a list of
software drivers to include in the new bootable operating system, 
the assignment of system devices such as \f4swapdev\f1 and \f4rootdev\f1,
and instructions for excluding drivers from the configuration
process.
.P
The parser for the \f4system\f1 file is case-sensitive.
All upper case strings in the syntax below should be upper case in the
\f4system\f1 file as well.
Nonterminal symbols are enclosed in angle brackets \f4<>\fP, whereas
optional arguments are enclosed in square brackets \f4[]\fP.
Ellipses (\f4...\fP) indicate optional repetition of the argument
for that line.
.P
The symbols in the syntax description below are interpreted as
follows:
.PP
.TS
center ;
lf2 l lf .
<fname>	::=	pathname
<string>	::=	driver file name from \f4/boot\f1 or EDT entry name
<device>	::=	special device name | \f4DEV(\f2<major>,<minor>\f4)\f1
<major>	::=	\f2<number>\fP
<minor>	::=	\f2<number>\fP
<number>	::=	decimal, octal or hex literal
.TE
The lines listed below may appear in any order.
Blank lines may be inserted at any point.
Comment lines must begin with an asterisk.
Entries for \f4EXCLUDE\fP and \f4INCLUDE\fP are cumulative.
For all other entries, the last line to appear
in the file is used\(emany earlier entries are ignored.
.IP "\f4BOOT:\fP  <\f2fname\fP>"
Specifies the \f4KERNEL\fP object file to be used to build the bootable operating
system;  if <\f2fname\fP> is the keyword \f4DEFAULT\fP, 
the configuration program takes the \f4KERNEL\fP file from whatever
boot directory it is using.
For example, if the user types \f4cunix \-b /\f2my_boot_directory\f1
and the \f4system\fP file contains the \f4DEFAULT\fP keyword for the \f4BOOT\fP
directive, then the \f4KERNEL\fP file used is /\f2my_boot_directory\f4/KERNEL\f1.
If no \f4\-b\fP option is used then \f4cunix\fP searches \f4/boot\fP by
default;  see \f4cunix\fP(1M).
.IP "\f4EXCLUDE:\fP  <\f2string\fP> ..."
Specifies drivers to exclude from the configuration even if the device is found
in the EDT.
.IP "\f4INCLUDE:\fP  <\f2string\fP>[(<\f2number\fP>)] ..."
Specifies software drivers or loadable modules to be
included in the configuration.
The optional <\f2number\fP> (parentheses required)
specifies the number of devices to be controlled by the driver
(defaults to 1).
This number corresponds to the builtin variable
\f4#C\fP
which may be referred to by expressions in part one of the
\f4master\f1
file.
.IP "\f4ROOTDEV:\fP  <\f2device\fP>"
Identifies the device containing the root file system.
.IP "\f4SWAPDEV:\fP  <\f2device\fP> <\f2number\fP> <\f2number\fP>"
Identifies the device to be used as swap space.
The <\f2device\fP> in this case may be a special device file name or
a regular file.
The <\f2number\fP>s correspond to the block number the swap space starts at
and the number of swap blocks available.
.SH FILES
\f4/stand/system\fP
.SH SEE ALSO
\f4crash\fP(1M), \f4cunix\fP(1M), \f4mkboot\fP(1M),
\f4master\fP(4).
.Ee
