Lines Matching +full:controller +full:- +full:number

80 \-DFUNNY \-DHAHA in the resultant makefile.
106 .IP "\fBtimezone\fP \fInumber\fP [ \fBdst\fP [ \fInumber\fP ] ]"
109 number of hours your timezone is west of GMT.  
113 An optional integer or floating point number may be included
123 This is usually a cute name like ERNIE (short for Ernie Co-Vax) or
128 .IP "\fBmaxusers\fP \fInumber\fP"
130 The maximum expected number of simultaneously active user on this system is
131 .IR number .
132 This number is used to size several system data structures.
142 \fBconfig\fP\ \fIsysname\fP\ \fIconfig-clauses\fP
149 is located and the number and location of paging devices.
161 \fBroot\fP [ \fBon\fP ] \fIroot-device\fP
162 \fBswap\fP [ \fBon\fP ] \fIswap-device\fP [ \fBand\fP \fIswap-device\fP ] ...
163 \fBdumps\fP [ \fBon\fP ] \fIdump-device\fP
164 \fBargs\fP [ \fBon\fP ] \fIarg-device\fP
195 numbers on a per-machine basis.  A file,
198 is used to map a device name to its major block device number.
199 The minor device number is calculated using the standard 
202 other than 0, add 8 times the unit number to get the minor
206 number is incorrect for your configuration, it can be replaced
219 at boot time.  If a non-standard size is to be used for one
254 * While VAX-11/750's and VAX-11/730 do not actually have 
277 \fBmaster\fP \fIdevice-name\fP \fIdevice-info\fP
278 \fBcontroller\fP \fIdevice-name\fP \fIdevice-info\fP [ \fIinterrupt-spec\fP ]
279 \fBdevice\fP \fIdevice-name\fP \fIdevice-info\fP \fIinterrupt-spec\fP
280 \fBdisk\fP \fIdevice-name\fP \fIdevice-info\fP
281 \fBtape\fP \fIdevice-name\fP \fIdevice-info\fP
284 A ``master'' is a MASSBUS tape controller; a ``controller'' is a
285 disk controller, a UNIBUS tape controller, a MASSBUS adapter, or
288 like a disk which connects through a disk controller).  ``Disk''
290 a ``controller'' or ``master.''
293 .I device-name
298 unit number to be assigned the device (the 
300 unit number may be different than the
302 unit number indicated on the front of something
305 unit number is used to refer to the UNIX device, not
306 the physical unit number).  For example, ``hp0'' is logical
311 .I device-info
322 \fBcontroller\fP	mba0	\fBat\fP \fBnexus\fP \fIx\fP
323 \fBcontroller\fP	uba0	\fBat\fP \fBnexus\fP \fIx\fP
326 To tie a controller to a specific nexus, ``x'' would be supplied
327 as the number of that nexus; otherwise ``x'' may be specified as
330 for the specified controller.
334 a controller
335 may be connected to another controller (e.g. a disk controller attached
338 a master is always attached to a controller (a MASSBUS adapter),
343 a disk is always attached to a controller, and
353 \fBcontroller\fP	hk0	\fBat\fP uba0 ...
362 controller may also be wildcarded across multiple controllers.
367 number is sufficient to locate the control status register for the
370 on MASSBUS devices, but not on disks on a UNIBUS controller.
372 given explicitly, as well the number of interrupt vectors used and
378 \fBcontroller\fP	hk0	\fBat\fP uba0 \fBcsr\fP 0177440	\fBvector\fP rkintr
389 are present on each non-standard line printer (i.e. a line printer
399 \fBflags\fP \fInumber\fP
404 .I number
414 Pseudo-devices
416 A number of drivers and software subsystems
418 To include any of these pieces, a ``pseudo-device'' specification
423 \fBpseudo-device\fP	\fIdevice-name\fP [ \fIhowmany\fP ]
429 value indicates the number of pseudo terminals to configure, 32 default),
430 and \fBloop\fP, the software loopback network pseudo-interface.