Commit | Line | Data |
---|---|---|
3edcb7c8 KB |
1 | .\" Copyright (c) 1983 The Regents of the University of California. |
2 | .\" All rights reserved. | |
dc395bbe | 3 | .\" |
3edcb7c8 KB |
4 | .\" %sccs.include.redist.roff% |
5 | .\" | |
6 | .\" @(#)5.t 6.3 (Berkeley) %G% | |
dc395bbe | 7 | .\" |
57349e41 MK |
8 | .\".ds RH "Sample Configuration Files |
9 | .ne 2i | |
10 | .NH | |
11 | SAMPLE CONFIGURATION FILES | |
dc395bbe KM |
12 | .PP |
13 | In this section we will consider how to configure a | |
14 | sample VAX-11/780 system on which the hardware can be | |
15 | reconfigured to guard against various hardware mishaps. | |
16 | We then study the rules needed to configure a VAX-11/750 | |
17 | to run in a networking environment. | |
18 | .NH 2 | |
19 | VAX-11/780 System | |
20 | .PP | |
21 | Our VAX-11/780 is configured with hardware | |
22 | recommended in the document ``Hints on Configuring a VAX for 4.2BSD'' | |
23 | (this is one of the high-end configurations). | |
24 | Table 1 lists the pertinent hardware to be configured. | |
25 | .DS B | |
26 | .TS | |
27 | box; | |
28 | l | l | l | l | l | |
29 | l | l | l | l | l. | |
30 | Item Vendor Connection Name Reference | |
31 | _ | |
32 | cpu DEC VAX780 | |
33 | MASSBUS controller Emulex nexus ? mba0 hp(4) | |
34 | disk Fujitsu mba0 hp0 | |
35 | disk Fujitsu mba0 hp1 | |
36 | MASSBUS controller Emulex nexus ? mba1 | |
37 | disk Fujitsu mba1 hp2 | |
38 | disk Fujitsu mba1 hp3 | |
39 | UNIBUS adapter DEC nexus ? | |
40 | tape controller Emulex uba0 tm0 tm(4) | |
41 | tape drive Kennedy tm0 te0 | |
42 | tape drive Kennedy tm0 te1 | |
43 | terminal multiplexor Emulex uba0 dh0 dh(4) | |
44 | terminal multiplexor Emulex uba0 dh1 | |
45 | terminal multiplexor Emulex uba0 dh2 | |
46 | .TE | |
47 | .DE | |
48 | .ce | |
49 | Table 1. VAX-11/780 Hardware support. | |
50 | .LP | |
51 | We will call this machine ANSEL and construct a configuration | |
52 | file one step at a time. | |
53 | .PP | |
54 | The first step is to fill in the global configuration parameters. | |
55 | The machine is a VAX, so the | |
56 | .I "machine type" | |
57 | is ``vax''. We will assume this system will | |
58 | run only on this one processor, so the | |
59 | .I "cpu type" | |
60 | is ``VAX780''. The options are empty since this is going to | |
61 | be a ``vanilla'' VAX. The system identifier, as mentioned before, | |
57349e41 | 62 | is ``ANSEL,'' and the maximum number of users we plan to support is |
dc395bbe KM |
63 | about 40. Thus the beginning of the configuration file looks like |
64 | this: | |
65 | .DS | |
66 | .ta 1.5i 2.5i 4.0i | |
67 | # | |
68 | # ANSEL VAX (a picture perfect machine) | |
69 | # | |
70 | machine vax | |
71 | cpu VAX780 | |
72 | timezone 8 dst | |
73 | ident ANSEL | |
74 | maxusers 40 | |
75 | .DE | |
76 | .PP | |
77 | To this we must then add the specifications for three | |
78 | system images. The first will be our standard system with the | |
79 | root on ``hp0'' and swapping on the same drive as the root. | |
80 | The second will have the root file system in the same location, | |
81 | but swap space interleaved among drives on each controller. | |
82 | Finally, the third will be a generic system, | |
83 | to allow us to boot off any of the four disk drives. | |
84 | .DS | |
85 | .ta 1.5i 2.5i | |
86 | config vmunix root on hp0 | |
87 | config hpvmunix root on hp0 swap on hp0 and hp2 | |
88 | config genvmunix swap generic | |
89 | .DE | |
90 | .PP | |
91 | Finally, the hardware must be specified. Let us first just try | |
92 | transcribing the information from Table 1. | |
93 | .DS | |
94 | .ta 1.5i 2.5i 4.0i | |
95 | controller mba0 at nexus ? | |
96 | disk hp0 at mba0 disk 0 | |
97 | disk hp1 at mba0 disk 1 | |
98 | controller mba1 at nexus ? | |
99 | disk hp2 at mba1 disk 2 | |
100 | disk hp3 at mba1 disk 3 | |
101 | controller uba0 at nexus ? | |
102 | controller tm0 at uba0 csr 0172520 vector tmintr | |
103 | tape te0 at tm0 drive 0 | |
104 | tape te1 at tm0 drive 1 | |
105 | device dh0 at uba0 csr 0160020 vector dhrint dhxint | |
106 | device dm0 at uba0 csr 0170500 vector dmintr | |
107 | device dh1 at uba0 csr 0160040 vector dhrint dhxint | |
108 | device dh2 at uba0 csr 0160060 vector dhrint dhxint | |
109 | .DE | |
110 | .LP | |
111 | (Oh, I forgot to mention one panel of the terminal multiplexor | |
112 | has modem control, thus the ``dm0'' device.) | |
113 | .PP | |
114 | This will suffice, but leaves us with little flexibility. Suppose | |
115 | our first disk controller were to break. We would like to recable the | |
116 | drives normally on the second controller so that all our disks could | |
117 | still be used without reconfiguring the system. To do this we wildcard | |
118 | the MASSBUS adapter connections and also the slave numbers. Further, | |
119 | we wildcard the UNIBUS adapter connections in case we decide some time | |
120 | in the future to purchase another adapter to offload the single UNIBUS | |
121 | we currently have. The revised device specifications would then be: | |
122 | .DS | |
123 | .ta 1.5i 2.5i 4.0i | |
124 | controller mba0 at nexus ? | |
125 | disk hp0 at mba? disk ? | |
126 | disk hp1 at mba? disk ? | |
127 | controller mba1 at nexus ? | |
128 | disk hp2 at mba? disk ? | |
129 | disk hp3 at mba? disk ? | |
130 | controller uba0 at nexus ? | |
131 | controller tm0 at uba? csr 0172520 vector tmintr | |
132 | tape te0 at tm0 drive 0 | |
133 | tape te1 at tm0 drive 1 | |
134 | device dh0 at uba? csr 0160020 vector dhrint dhxint | |
135 | device dm0 at uba? csr 0170500 vector dmintr | |
136 | device dh1 at uba? csr 0160040 vector dhrint dhxint | |
137 | device dh2 at uba? csr 0160060 vector dhrint dhxint | |
138 | .DE | |
139 | .LP | |
140 | The completed configuration file for ANSEL is shown in Appendix C. | |
141 | .NH 2 | |
142 | VAX-11/750 with network support | |
143 | .PP | |
144 | Our VAX-11/750 system will be located on two 10Mb/s Ethernet | |
145 | local area networks and also the DARPA Internet. The system | |
146 | will have a MASSBUS drive for the root file system and two | |
147 | UNIBUS drives. Paging is interleaved among all three drives. | |
148 | We have sold our standard DEC terminal multiplexors since this | |
149 | machine will be accessed solely through the network. This | |
150 | machine is not intended to have a large user community, it | |
151 | does not have a great deal of memory. First the global parameters: | |
152 | .DS | |
153 | .ta 1.5i 2.5i 4.0i | |
154 | # | |
155 | # UCBVAX (Gateway to the world) | |
156 | # | |
157 | machine vax | |
158 | cpu "VAX780" | |
159 | cpu "VAX750" | |
160 | ident UCBVAX | |
161 | timezone 8 dst | |
162 | maxusers 32 | |
163 | options INET | |
57349e41 | 164 | options NS |
dc395bbe KM |
165 | .DE |
166 | .PP | |
167 | The multiple cpu types allow us to replace UCBVAX with a | |
168 | more powerful cpu without reconfiguring the system. The | |
169 | value of 32 given for the maximum number of users is done to | |
170 | force the system data structures to be over-allocated. That | |
171 | is desirable on this machine because, while it is not expected | |
172 | to support many users, it is expected to perform a great deal | |
57349e41 MK |
173 | of work. |
174 | The ``INET'' indicates that we plan to use the | |
175 | DARPA standard Internet protocols on this machine, | |
176 | and ``NS'' also includes support for Xerox NS protocols. | |
177 | Note that unlike 4.2BSD configuration files, | |
178 | the network protocol options do not require corresponding pseudo devices. | |
dc395bbe | 179 | .PP |
57349e41 | 180 | The system images and disks are configured next. |
dc395bbe KM |
181 | .DS |
182 | .ta 1.5i 2.5i 4.0i | |
183 | config vmunix root on hp swap on hp and rk0 and rk1 | |
184 | config upvmunix root on up | |
185 | config hkvmunix root on hk swap on rk0 and rk1 | |
186 | ||
187 | controller mba0 at nexus ? | |
188 | controller uba0 at nexus ? | |
189 | disk hp0 at mba? drive 0 | |
190 | disk hp1 at mba? drive 1 | |
191 | controller sc0 at uba? csr 0176700 vector upintr | |
192 | disk up0 at sc0 drive 0 | |
193 | disk up1 at sc0 drive 1 | |
194 | controller hk0 at uba? csr 0177440 vector rkintr | |
195 | disk rk0 at hk0 drive 0 | |
196 | disk rk1 at hk0 drive 1 | |
197 | .DE | |
198 | .PP | |
199 | UCBVAX requires heavy interleaving of its paging area to keep up | |
200 | with all the mail traffic it handles. The limiting factor on this | |
201 | system's performance is usually the number of disk arms, as opposed | |
202 | to memory or cpu cycles. The extra UNIBUS controller, ``sc0'', | |
203 | is in case the MASSBUS controller breaks and a spare controller | |
204 | must be installed (most of our old UNIBUS controllers have been | |
205 | replaced with the newer MASSBUS controllers, so we have a number | |
206 | of these around as spares). | |
207 | .PP | |
57349e41 MK |
208 | Finally, we add in the network devices. |
209 | Pseudo terminals are needed to allow users to | |
dc395bbe | 210 | log in across the network (remember the only hardwired terminal |
57349e41 MK |
211 | is the console). |
212 | The software loopback device is used for on-machine communications. | |
213 | The connection to the Internet is through | |
dc395bbe KM |
214 | an IMP, this requires yet another |
215 | .I pseudo-device | |
216 | (in addition to the actual hardware device used by the | |
217 | IMP software). And, finally, there are the two Ethernet devices. | |
218 | These use a special protocol, the Address Resolution Protocol (ARP), | |
219 | to map between Internet and Ethernet addresses. Thus, yet another | |
220 | .I pseudo-device | |
221 | is needed. The additional device specifications are show below. | |
222 | .DS | |
223 | .ta 1.5i 2.5i 4.0i | |
dc395bbe | 224 | pseudo-device pty |
dc395bbe KM |
225 | pseudo-device loop |
226 | pseudo-device imp | |
227 | device acc0 at uba? csr 0167600 vector accrint accxint | |
228 | pseudo-device ether | |
229 | device ec0 at uba? csr 0164330 vector ecrint eccollide ecxint | |
230 | device il0 at uba? csr 0164000 vector ilrint ilcint | |
231 | .DE | |
232 | .LP | |
233 | The completed configuration file for UCBVAX is shown in Appendix C. | |
234 | .NH 2 | |
235 | Miscellaneous comments | |
236 | .PP | |
237 | It should be noted in these examples that neither system was | |
238 | configured to use disk quotas or the 4.1BSD compatibility mode. | |
239 | To use these optional facilities, and others, we would probably | |
240 | clean out our current configuration, reconfigure the system, then | |
241 | recompile and relink the system image(s). This could, of course, | |
242 | be avoided by figuring out which relocatable object files are | |
243 | affected by the reconfiguration, then reconfiguring and recompiling | |
244 | only those files affected by the configuration change. This technique | |
245 | should be used carefully. |