Lines Matching +full:on +full:- +full:device

23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
46 device specifications.
55 The system is to run on the machine type specified.  No more than
63 This system is to run on the cpu type specified.
80 \-DFUNNY \-DHAHA in the resultant makefile.
94 of the manual page for the device.
123 This is usually a cute name like ERNIE (short for Ernie Co-Vax) or
130 The maximum expected number of simultaneously active user on this system is
142 \fBconfig\fP\ \fIsysname\fP\ \fIconfig-clauses\fP
150 The device used by the system to process argument lists during
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
166 (the ``on'' is optional.)  Multiple configuration clauses
174 to be taken on a particular device, and the ``args'' clause
177 should be done on a particular device.
179 The device names supplied in the clauses may be fully specified
180 as a device, unit, and file system partition; or underspecified
185 as they are dependent on the overall system configuration.
187 the root device is specified; in this case the swap area is
193 The device names are translated to the
194 appropriate major and minor device
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 
200 disk partitioning rules: on unit 0, partition ``a'' is minor device
201 0, partition ``b'' is minor device 1, and so on; for units
203 device.
205 If the default mapping of device name to major/minor device
207 by an explicit specification of the major/minor device.
212 where the device name would normally be found.  For example,
215 \fBconfig\fP kernel \fBroot\fP \fBon\fP \fBmajor\fP 99 \fBminor\fP 1
219 at boot time.  If a non-standard size is to be used for one
222 device name specified for a swap area should have a ``size''
226 \fBconfig\fP kernel \fBroot\fP \fBon\fP hp0 \fBswap\fP \fBon\fP hp0b \fBsize\fP 1200
237 Device specifications
239 Each device attached to a machine must be specified
244 specified in the configuration need not actually be present on
250 configured.  On the VAX, this means that a configuration file must
254 * While VAX-11/750's and VAX-11/730 do not actually have 
257 to simplify device configuration.
261 to one or more adapters.  A device description may provide a
265 device configuration list to match many possible physical
274 A device specification takes one of the following forms:
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
286 a UNIBUS adapter.  A ``device'' is an autonomous device which
293 .I device-name
294 is one of the standard device names, as
298 unit number to be assigned the device (the 
302 unit number indicated on the front of something
305 unit number is used to refer to the UNIX device, not
307 unit 0 of a MASSBUS storage device, even though it might
308 be physical unit 3 on MASSBUS adapter 1.
311 .I device-info
313 connected in the interconnection hierarchy.  On the VAX,
332 The remaining interconnections on the VAX are:
358 \fBdevice\fP	dz0	\fBat\fP uba0 ...
365 devices is some indication of where or how a device will interrupt.
368 device.
370 on MASSBUS devices, but not on disks on a UNIBUS controller.
383 \fBdevice\fP	dz0	\fBat\fP uba0 \fBcsr\fP 0160100	\fBvector\fP dzrint dzxint
386 Certain device drivers require extra information passed to them
389 are present on each non-standard line printer (i.e. a line printer
394 .IR device ,
411 The exact syntax for each specific device is given in the Synopsis
414 Pseudo-devices
417 are treated like device drivers without any associated hardware.
418 To include any of these pieces, a ``pseudo-device'' specification
419 must be used.  A specification for a pseudo device takes the form
423 \fBpseudo-device\fP	\fIdevice-name\fP [ \fIhowmany\fP ]
430 and \fBloop\fP, the software loopback network pseudo-interface.
435 More information on configuring each of these can also be found