MASTER(5) — UNIX 3.0
NAME
master − master device information table
DESCRIPTION
This file is used by the config(1M) program to obtain device information that enables it to generate the configuration files. The file consists of 3 parts, each separated by a line with a dollar sign ($) in column 1. Part 1 contains device information; part 2 contains names of devices that have aliases; part 3 contains tunable parameter information. Any line with an asterisk (∗) in column 1 is treated as a comment.
Part 1 contains lines consisting of at least 10 fields and at most 13 fields, with the fields delimited by tabs and/or blanks:
Field 1: device name (8 chars. maximum).
Field 2: interrupt vector size (decimal, in bytes).
Field 3: device mask (octal)−each “on” bit indicates that the handler exists:
000100 initialization handler
000040 power-failure handler
000020 open handler
000010 close handler
000004 read handler
000002 write handler
000001 ioctl handler.
Field 4: device type indicator (octal):
000200 allow only one of these devices
000100 suppress count field in the conf.c file
000040 suppress interrupt vector
000020 required device
000010 block device
000004 character device
000002 floating vector
000001 fixed vector.
Field 5: handler prefix (4 chars. maximum).
Field 6: device address size (decimal).
Field 7: major device number for block-type device.
Field 8: major device number for character-type device.
Field 9: maximum number of devices per controller (decimal).
Field 10: maximum bus request level (4 through 7).
Fields 11-13: optional configuration table structure declarations (8 chars. maximum).
Part 2 contains lines with 2 fields each:
Field 1: alias name of device (8 chars. maximum).
Field 2: reference name of device (8 chars. maximum; specified in part 1).
Part 3 contains lines with 2 or 3 fields each:
Field 1: parameter name (as it appears in description file; 20 chars. maximum)
Field 2: parameter name (as it appears in the conf.c file; 20 chars. maximum)
Field 3: default parameter value (20 chars. maximum; parameter specification is required if this field is omitted)
Devices that are not interrupt-driven have an interrupt vector size of zero. The 040 bit in Field 4 causes config(1M) to record the interrupt vector although the low.s (univec.c on the VAX-11/780) file will show no interrupt vector assignment at those locations (interrupts here will be treated as strays).
SEE ALSO
May 16, 1980