Lines Matching +full:system +full:- +full:controller

40 configuration parameters global to all system images 
44 system image to be generated, and
51 cpu types, options, timezone, system identifier, and maximum users.
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.
76 Compile the listed optional code into the system. 
80 \-DFUNNY \-DHAHA in the resultant makefile.
89 Other kernel options controlling system sizes and limits
97 Options that are used within the system makefile
108 Specifies the timezone used by the system.  This is measured in the
112 \fBdst\fP, the system will operate under daylight savings time.
121 This system is to be known as
123 This is usually a cute name like ERNIE (short for Ernie Co-Vax) or
127 to this system.
130 The maximum expected number of simultaneously active user on this system is
132 This number is used to size several system data structures.
134 System image parameters
138 and devices, but the location of the root file system and other
139 system specific devices may be different.  A system image is specified
142 \fBconfig\fP\ \fIsysname\fP\ \fIconfig-clauses\fP
146 field is the name given to the loaded system image; almost everyone
147 names their standard system image ``kernel''.  The configuration clauses
148 are one or more specifications indicating where the root file system
150 The device used by the system to process argument lists during
156 system 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
171 The ``root'' clause specifies where the root file system
173 area(s), the ``dumps'' clause can be used to force system dumps
180 as a device, unit, and file system partition; or underspecified
184 system partitions.  The defaulting rules are a bit complicated
185 as they are dependent on the overall system configuration.
189 file system is located.  Appendix B contains a complete list
190 of the defaulting rules used in selecting system configuration
195 numbers on a per-machine basis.  A file,
218 Normally, the areas configured for swap space are sized by the system
219 at boot time.  If a non-standard size is to be used for one
242 so that the system generated will know to probe for it during
245 the machine where the generated system is to be run.  Only the
246 hardware actually found at boot time will be used by the system.
254 * While VAX-11/750's and VAX-11/730 do not actually have 
255 nexi, the system treats them as having 
263 or it may leave certain parameters undefined and make the system
267 at UNIBUS adapter 0, or at any UNIBUS adapter which the system
270 allows more flexibility in the physical configuration of a system;
271 if a disk must be moved around for some reason, the system will
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
311 .I device-info
315 system bus through
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
329 case the system will probe all nexi present looking
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.
364 The final piece of information needed by the system to configure
370 on MASSBUS devices, but not on disks on a UNIBUS controller.
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
414 Pseudo-devices
418 To include any of these pieces, a ``pseudo-device'' specification
423 \fBpseudo-device\fP	\fIdevice-name\fP [ \fIhowmany\fP ]
430 and \fBloop\fP, the software loopback network pseudo-interface.