master(4)
_________________________________________________________________
master File Format
master file directory and master files containing device
information
_________________________________________________________________
DESCRIPTION
Device information is contained in a set of master files that are
kept in the master file directory. The device information in the
master files are used by the config(1m) program to configure your
DG/UX system.
The DG/UX system supports three standard master files called
dgux, nfs, and tcpip. These are stored in the default master
file directory called /etc/master.d. If you add your own device
you will need to supply information about that device in a master
file. You may add this information to one of the existing master
files or create a new master file of your own. Any file found in
the master file directory is automatically treated as a master
file. If you are not adding a new device you will probably only
use the master files as reference when setting up your system
file (see system(4)).
A master file can contain entries describing hardware devices,
software devices, parameters, aliases, protocols and/or streams.
Different types of information are grouped into their own
sections with their own entry format. There are six different
section types as follows:
Device Section describes hardware and software devices
Keyword Section describes user configurable parameters
Protocol Section describes parameters for supported network and
kernel protocols
Stream Section describes parameters for supported stream
modules
Aliases Section allows you to define aliases for master file
device or parameter entries. You use these
aliases in the system file to reference master
file entries.
Local Aliases allows you to define constants for use within
the master file.
Each section is started by a dollar sign ($) in column 1 followed
by the name of the section. The section name keywords are:
DG/UX 4.00 Page 1
Licensed material--property of copyright holder(s)
master(4)
device, keyword, stream, protocol, alias, local_alias.
You need not have sections of all six types, only those that you
use. You may list the sections in any order. You can also have
more that one section of the same type if this is convenient for
you.
Each entry in a section consists of a single line broken into a
number of fields separated by blanks and/or tabs. Comments are
preceded by a pound sign (#) and can begin at any position on a
line. Blank lines and comments are ignored.
Entries in the device section have four fields all of which must
be filled in:
Field 1: Device name or alias as specified in the system
file. The kernel uses this name as a prefix to
names for device driver routines in conf.c.
Field 2: Block and character major number. See Installing
and Managing the DG/UX System for details on how
to define your major number.
Field 3: Maximum units per controller.
Field 4: Restrictions on this device. Restrictions are:
o only one device of this type allowed
r this device is required
s this device is a stream device
n no restrictions
Entries in the keyword section can have four fields; the first
two are required:
Field 1: Name of kernel variable to be set.
Field 2: The default value that you want this variable to
have. The default value can be overridden through
the system file.
Field 3: The kernel variable's data type. The default type
is long integer. You need only specify this field
if another data type is required. You may not use
a type that requires use of an include file.
Field 4: The implied value for a variable that is listed in
the system file without a value.
DG/UX 4.00 Page 2
Licensed material--property of copyright holder(s)
master(4)
Entries in the aliases section have two required fields:
Field 1: Alias name (up to 64 characters long)
Field 2: Name of master file entry being referenced (up to
64 characters long)
Entries in the local alias section has two fields both of which
are required:
Field 1: Alias name (up to 64 characters long)
Field 2: The value you want this alias name to have. You
may use either a numeric or character string
value.
You need only create a protocol section if you have TCP/IP. See
Programming with DG TCP/IP (DG/UX) for additional protocol
information.
Entries in the protocol section have six fields all of which are
required:
Field 1: Name you used in the system file to reference this
protocol. ONLY THOSE PROTOCOLS LISTED IN THE
SYSTEM FILE ARE CONFIGURED TO THE KERNEL.
Field 2: The protocol's protocol number as defined in the
/etc/protocols file.
Field 3: The socket's domain number as defined in the
socket.h include file.
Field 4: The protocol's type as defined in the socket.h
include file.
Field 5: The infix name. The kernel will use this name to
generate names for the protocol's control
routines. You may use any name you want and then
match this name with the names of your protocol
control routines.
Field 6: Restriction flag. For no restrictions specify the
n restriction flag. To make a protocol a default
protocol specifiy the d restriction flag. The
default protocol is used by the socket system call
when no protocol is specified and when one or more
protocols have the same domain number and socket
type.
Entries in the stream section have three fields all of which are
DG/UX 4.00 Page 3
Licensed material--property of copyright holder(s)
master(4)
required:
Field 1: Name of the stream control module as given in the
system file.
Field 2: The infix name. The kernel will use this name to
generate names for the stream's control module
routines. You may use any name you want and then
match this name with the names of your stream
control module routines.
Field 3: Restriction flag. For no restrictions, specify
the n restriction flag.
SEE ALSO
system(4).
config(1m), sysdef(1m) in the System Manager's Reference for the
DG/UX System and Installing and Managing the DG/UX System.
DG/UX 4.00 Page 4
Licensed material--property of copyright holder(s)