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

34 sample VAX-11/780 system on which the hardware can be
36 We then study the rules needed to configure a VAX-11/750
39 VAX-11/780 System
41 Our VAX-11/780 is configured with hardware
43 (this is one of the high-end configurations).
53 MASSBUS controller	Emulex	nexus ?	mba0	hp(4)
56 MASSBUS controller	Emulex	nexus ?	mba1
60 tape controller	Emulex	uba0	tm0	tm(4)
69 Table 1.  VAX-11/780 Hardware support.
77 is ``vax''.  We will assume this system will
81 be a ``vanilla'' VAX.  The system identifier, as mentioned before,
98 system images.  The first will be our standard system with the
100 The second will have the root file system in the same location,
101 but swap space interleaved among drives on each controller.
102 Finally, the third will be a generic system,
115 controller	mba0	at nexus ?
118 controller	mba1	at nexus ?
121 controller	uba0	at nexus ?
122 controller	tm0	at uba0 csr 0172520	vector tmintr
135 our first disk controller were to break.  We would like to recable the
136 drives normally on the second controller so that all our disks could
137 still be used without reconfiguring the system.  To do this we wildcard
144 controller	mba0	at nexus ?
147 controller	mba1	at nexus ?
150 controller	uba0	at nexus ?
151 controller	tm0	at uba? csr 0172520	vector tmintr
162 VAX-11/750 with network support
164 Our VAX-11/750 system will be located on two 10Mb/s Ethernet
165 local area networks and also the DARPA Internet.  The system
166 will have a MASSBUS drive for the root file system and two
188 more powerful cpu without reconfiguring the system.  The
190 force the system data structures to be over-allocated.  That
200 The system images and disks are configured next.
207 controller	mba0	at nexus ?
208 controller	uba0	at nexus ?
211 controller	sc0	at uba? csr 0176700	vector upintr
214 controller	hk0	at uba? csr 0177440 	vector rkintr
221 system's performance is usually the number of disk arms, as opposed
222 to memory or cpu cycles.  The extra UNIBUS controller, ``sc0'',
223 is in case the MASSBUS controller breaks and a spare controller
232 The software loopback device is used for on-machine communications.
235 .I pseudo-device
240 .I pseudo-device
244 pseudo-device	pty
245 pseudo-device	loop
246 pseudo-device	imp
248 pseudo-device	ether
257 It should be noted in these examples that neither system was
260 clean out our current configuration, reconfigure the system, then
261 recompile and relink the system image(s).  This could, of course,