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