![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to config.5 CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [Research Unix] / researchv9 / sys / conf / src / config|
Return to config.5 CVS log | Up to [Research Unix] / researchv9 / sys / conf / src / config |
1.1 root 1: .TH CONFIG 5
2: .SH NAME
3: config \- system configuration template files
4: .SH DESCRIPTION
5: These files are used as input by
6: .IR config (8).
7: Except as noted,
8: they are kept in
9: .IR /usr/sys/conf .
10: .PP
11: .I Files
12: names the source files
13: that make up the kernel.
14: Each line consists of a filename
15: (relative to
16: .IR /usr/sys )
17: followed by some magic words.
18: For example:
19: .IP
20: sys/acct.c standard
21: .PP
22: is a file used by any version of the system;
23: .IP
24: dev/uba.c standard device-driver
25: .PP
26: is also always used,
27: and contains device register references
28: (which may require special compilation hacks);
29: .IP
30: dev/ju.c optional ju device-driver
31: .PP
32: is included only if the
33: .I ju
34: device is expected;
35: .IP
36: dev/ttyld.c optional tty pseudo-device
37: .PP
38: is included only if the
39: .I tty
40: pseudo-device is requested.
41: .PP
42: .I Devices
43: describes possible device drivers,
44: file system handlers,
45: and line disciplines;
46: the information is used to generate
47: handler dispatch tables.
48: It consists of lines with the following blank-separated fields:
49: .IP
50: Type of handler:
51: .I device
52: for character devices,
53: .I stream-device
54: for character stream devices,
55: .I block-device
56: for block devices,
57: .I file-system
58: for file system handlers,
59: .I line-discipline
60: for line discipline handlers.
61: If the type is preceded by the word `standard'
62: .RI ( e.g.
63: .IR "standard block-device" ),
64: the handler is always included;
65: otherwise,
66: it is included only if requested.
67: .IP
68: Table index:
69: major device number,
70: filesystem type,
71: or line discipline number.
72: .IP
73: Driver name.
74: Used in
75: .IR files
76: and
77: .IR conf .
78: .I Config
79: writes a header file
80: .I name.h
81: for each device;
82: if that device
83: is configured,
84: NAME
85: is defined to be
86: the number of devices
87: of that type.
88: .IP
89: Entry point name.
90: Used as a prefix for data structure
91: and driver entry points.
92: .IP
93: Entry points.
94: For block devices,
95: some of
96: .IR open ,
97: .IR close ,
98: .IR strategy ,
99: .IR dump ,
100: .IR B_TAPE
101: (the last puts the flag
102: .I B_TAPE
103: in the
104: .I d_flags
105: entry in the block device switch);
106: for character devices,
107: .IR open ,
108: .IR close ,
109: .IR read ,
110: .IR write ,
111: .IR ioctl ,
112: .IR reset .
113: For stream devices
114: and line disciplines,
115: .I info
116: should be specified.
117: For file system handlers,
118: .IR put ,
119: .IR get ,
120: .IR free ,
121: .IR updat ,
122: .IR read ,
123: .IR write ,
124: .IR trunc ,
125: .IR stat ,
126: .IR nami ,
127: .IR mount ,
128: .IR ioctl .
129: .PP
130: As a special case,
131: lines beginning with
132: .RB ` : '
133: are copied intact to
134: .IR conf.c .
135: This can be used for hacks like
136: .IP
137: : int mem_no = 3; /* major device number of memory special file */
138: .PP
139: Addenda to
140: .I files
141: and
142: .I devices
143: specific to a particular machine
144: may be kept in
145: .IR /usr/sys/ machine /files
146: and
147: .IR /usr/sys/ machine /devices .
148: The addenda are treated as if appended to the
149: general files.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.