![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to 1.t CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [CSRG BSD Unix] / 43BSDReno / share / doc / smm / 01.setup / vax|
Return to 1.t CVS log | Up to [CSRG BSD Unix] / 43BSDReno / share / doc / smm / 01.setup / vax |
1.1 ! root 1: .\" Copyright (c) 1980, 1986, 1988 Regents of the University of California. ! 2: .\" All rights reserved. ! 3: .\" ! 4: .\" Redistribution and use in source and binary forms are permitted ! 5: .\" provided that the above copyright notice and this paragraph are ! 6: .\" duplicated in all such forms and that any documentation, ! 7: .\" advertising materials, and other materials related to such ! 8: .\" distribution and use acknowledge that the software was developed ! 9: .\" by the University of California, Berkeley. The name of the ! 10: .\" University may not be used to endorse or promote products derived ! 11: .\" from this software without specific prior written permission. ! 12: .\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR ! 13: .\" IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED ! 14: .\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. ! 15: .\" ! 16: .\" @(#)1.t 6.3 (Berkeley) 3/7/89 ! 17: .\" ! 18: .ds lq `` ! 19: .ds rq '' ! 20: .ds LH "Installing/Operating \*(4B ! 21: .ds RH Introduction ! 22: .ds CF \*(DY ! 23: .LP ! 24: .nr H1 1 ! 25: .bp ! 26: .LG ! 27: .B ! 28: .ce ! 29: 1. INTRODUCTION ! 30: .sp 2 ! 31: .R ! 32: .NL ! 33: .PP ! 34: This document explains how to install the \*(4B release of the Berkeley ! 35: version of UNIX for the VAX on your system. Because of the file system ! 36: organization used in \*(4B, if you are not currently running 4.2BSD ! 37: or 4.3BSD ! 38: you will have to do a full bootstrap from the distribution tape. ! 39: The procedure for performing a full bootstrap is outlined in chapter 2. ! 40: The process includes booting standalone utilities from tape ! 41: to format a disk if necessary, then to copy a small root filesystem ! 42: image onto a swap area. ! 43: This filesystem is then booted and used to extract a dump of a standard root ! 44: filesystem. ! 45: Finally, that root filesystem is booted, and the remainder of the system ! 46: binaries and sources are read from the archives on the tape(s). ! 47: .PP ! 48: The technique for upgrading a 4.2BSD or 4.3BSD system is described ! 49: in chapter 3 of this document. ! 50: As \*(4B is upward-compatible with 4.2BSD, ! 51: The upgrade procedure involves extracting a new set of system binaries ! 52: onto new root and /usr filesystems. ! 53: The sources are then extracted, and local configuration files are merged ! 54: into the new system. ! 55: 4.2BSD and 4.3BSD user filesystems may up upgraded in place, ! 56: and 4.2BSD and 4.3BSD ! 57: binaries may be used with \*(4B in the course of the conversion. ! 58: It is desirable to recompile most local software after the conversion, ! 59: as there are many changes and performance improvements in the standard ! 60: libraries. ! 61: .NH 2 ! 62: Hardware supported ! 63: .PP ! 64: Note that some VAX models are identical ! 65: to others in all respects except speed. ! 66: The VAX 8650 will be hereafter referred to as a VAX 8600; ! 67: likewise, the VAX 8250 will be referred to as a VAX 8200, ! 68: the VAX-11/785 as an 11/780, and the 11/725 as an 11/730. ! 69: These names are sometimes shortened to ``8600,'' ``8200,'' ! 70: ``780,'' ``750,'' and ``730,'' ! 71: and the MicroVAX II is sometimes called the ``630.'' ! 72: .PP ! 73: This distribution can be booted on a VAX 8600, ! 74: VAX 8200, VAX-11/780, VAX-11/750, VAX-11/730, or MicroVAX II ! 75: cpu with at least 2 megabytes of memory, and ! 76: any of the following disks: ! 77: .DS ! 78: .TS ! 79: lw(1.5i) l. ! 80: DEC MASSBUS: RM03, RM05, RM80, RP06, RP07 ! 81: EMULEX MASSBUS: AMPEX Capricorn, 9300, CDC 9766, 9775, ! 82: FUJITSU 2351 Eagle, 2361* ! 83: DEC UNIBUS: RK07, RL02, RA??*, RC25 ! 84: EMULEX SC-21V, SC-31 AMPEX DM980, Capricorn, 9300, ! 85: UNIBUS*: CDC 9762, 9766, FUJITSU 160M, 330M ! 86: EMULEX SC-31 UNIBUS*: FUJITSU 2351 Eagle ! 87: DEC IDC: R80, RL02 ! 88: DEC BI: RA??* ! 89: DEC QBUS: RD53, RD54, RA??* ! 90: .TE ! 91: .DE ! 92: .FS ! 93: * Other compatible UNIBUS controllers and drives ! 94: may be easily usable with the system, ! 95: but may require minor modifications to the system ! 96: to allow bootstrapping. ! 97: The EMULEX disk and SI tape controllers, and ! 98: the drives shown here are known ! 99: to work as bootstrap devices. ! 100: RA?? includes the RA60, RA70, RA80, RA81, and RA82, ! 101: as well as the RX50 floppy drives on the MicroVAX II. ! 102: Other SMD and MSCP drives can be added with minor or no modifications. ! 103: .FE ! 104: .PP ! 105: The tape drives supported by this distribution are: ! 106: .DS ! 107: .TS ! 108: lw(1.5i) l. ! 109: DEC MASSBUS: TE16, TU45, TU77, TU78 ! 110: EMULEX MASSBUS: TC-7000 ! 111: DEC UNIBUS: TS11, TU80, TU81\(dg ! 112: EMULEX TC-11, AVIV UNIBUS: KENNEDY 9300, STC, CIPHER ! 113: TU45 UNIBUS: SI 9700 ! 114: DEC QBUS: TK50\(dd ! 115: .TE ! 116: .DE ! 117: .FS ! 118: \(dg The TU81 support is untested but is identical to ! 119: the TK50 code. ! 120: .FE ! 121: .FS ! 122: \(dd No TK50 media are included in the distribution, ! 123: hence a machine with only a TK50 ! 124: must already be running some version of UNIX ! 125: that can be used to load the software over a network. ! 126: .FE ! 127: .PP ! 128: The tapes and disks may be on any available UNIBUS or MASSBUS adapter ! 129: at any slot. ! 130: .PP ! 131: This distribution does not support the DEC CI780 or the HSC50 disk controller. ! 132: As such, this ! 133: distribution will not boot on the standard VAX 8600 ! 134: cluster configurations. ! 135: You will need to configure your system to use only UNIBUS, ! 136: MASSBUS, and BI bus disk and tape devices. ! 137: In addition, ! 138: BI Ethernet, tape, and terminal controllers are unsupported. You ! 139: cannot boot this distribution on a VAX 8200 without a UNIBUS. ! 140: .NH 2 ! 141: Distribution format ! 142: .PP ! 143: The basic distribution contains the following items: ! 144: .DS ! 145: (3)\0\0 1600bpi 9-track 2400' magnetic tapes, or ! 146: (1)\0\0 6250bpi 9-track 2400' magnetic tape, and ! 147: (1)\0\0 TU58 console cassette, and ! 148: (1)\0\0 RX01 console floppy disk. ! 149: .DE ! 150: Installation on any machine requires a tape unit. ! 151: Since certain standard VAX packages ! 152: do not include a tape drive, this means one must either ! 153: borrow one from another VAX system or one must be purchased ! 154: separately. The console media distributed with the system ! 155: are not suitable for use as the standard console media; their ! 156: intended use is only for installation. ! 157: .PP ! 158: \fBThe distribution does not fit on several standard ! 159: VAX configurations that contain only small disks\fP. ! 160: If your hardware configuration does not ! 161: provide at least ! 162: \fB75\fP XXX checkme XXX ! 163: Megabytes of disk space you can still ! 164: install the distribution, but you will probably have to operate ! 165: without source for the user level commands and, possibly, the ! 166: source for the operating system. The RK07-only ! 167: distribution format once provided by our group is no longer ! 168: available. Further, no attempt has ever been made to install ! 169: the system on the standard VAX-11/730 hardware configuration ! 170: from DEC that contains only dual RL02 disk drives (though ! 171: the distribution tape may be bootstrapped on an RL211 controller ! 172: and the system provides support for RL02 disk drives either on ! 173: an IDC or an RL211). The labels on the distribution tape(s) ! 174: show the amount of disk space each tape file occupies, ! 175: these should be used in selecting file system layouts on ! 176: systems with little disk space. ! 177: .PP ! 178: If you have the facilities, it is a good idea to copy the ! 179: magnetic tape(s) in the distribution kit to guard against disaster. ! 180: The tapes contain some ! 181: 512-byte records followed by many 10240-byte records. ! 182: There are interspersed tape marks; end-of-tape is signaled ! 183: by a double end-of-file. ! 184: The first file on the tape contains preliminary bootstrapping programs. ! 185: This is followed by a binary image ! 186: of a 2 megabyte ``mini root'' ! 187: file system. Following the mini root ! 188: file is a full dump of the root file system (see \fIdump\fP\|(8)*). ! 189: .FS ! 190: * References of the form X(Y) mean the subsection named ! 191: X in section Y of the ! 192: .UX ! 193: programmer's manual. ! 194: .FE ! 195: Additional files on the tape(s) ! 196: contain tape archive images (see ! 197: \fItar\fP\|(1)). See Appendix A for a description of the contents ! 198: and format of the tape(s). ! 199: One file contains software ! 200: contributed by the user community; refer to the accompanying ! 201: documentation for a description of its contents and an ! 202: explanation of how it should be installed. ! 203: .NH 2 ! 204: VAX hardware terminology ! 205: .PP ! 206: This section gives a short discussion of VAX hardware terminology ! 207: to help you get your bearings. ! 208: .PP ! 209: If you have MASSBUS disks and tapes it is necessary to know the ! 210: MASSBUS that they are attached to, at least for the purposes of bootstrapping ! 211: and system description. The MASSBUSes can have up to 8 devices attached ! 212: to them. A disk counts as a device. A tape \fIformatter\fP counts ! 213: as a device, and several tape drives may be attached to a formatter. ! 214: If you have a separate MASSBUS adapter for a disk and one for a tape ! 215: then it is conventional to put the disk as unit 0 on the MASSBUS with ! 216: the lowest ``TR'' number, and the tape formatter as unit 0 on the next ! 217: MASSBUS. On a 11/780 this would correspond to having the disk on ! 218: ``mba0'' at ``tr8'' and the tape on ``mba1'' at ``tr9''. Here the ! 219: MASSBUS adapter with the lowest TR number has been called ``mba0'' ! 220: and the one with the next lowest number is called ``mba1''. ! 221: .PP ! 222: To find out the MASSBUS that your tape and disk are on you can examine ! 223: the cabling and the unit numbers or your site maintenance guide. ! 224: Do not be fooled into thinking that the number on the front of the ! 225: tape drive is a device number; it is a \fIslave\fP number, ! 226: one of several possible ! 227: tapes on the single tape formatter. ! 228: For bootstrapping, the slave number \fBmust\fP be 0. The formatter ! 229: unit number may be anything distinct from the other numbers on the ! 230: same MASSBUS, but you must know what it is. ! 231: .PP ! 232: The MASSBUS devices are known by several different names by DEC software ! 233: and by UNIX. At various times it is necessary to know both ! 234: names. There is, of course, the name of the device like ``RM03'' ! 235: or ``RM80''; these are easy to remember because they are printed ! 236: on the front of the device. DEC also names devices based on the ! 237: driver name in the system using a convention that reflects ! 238: the interconnect topology of the machine. The first letter of such ! 239: a name is a ``D'' for a disk, the second letter depends on the type ! 240: of the drive, ``DR'' for RM03, RM05, and RM80's, ``DB'' for RP06's. ! 241: The next letter is related to the interconnect; DEC calls the first ! 242: MASSBUS or UNIBUS adapter ``A'', the second ``B'', etc. Thus, ``DRA'' is ! 243: an RM drive on the first MASSBUS adapter. Finally, the name ends ! 244: in a digit corresponding to the unit number for the device on the ! 245: MASSBUS: e.g., ``DRA0'' is a disk at the first device slot on the ! 246: first MASSBUS adapter and is an RM disk. ! 247: .NH 2 ! 248: UNIX device naming ! 249: .PP ! 250: UNIX has a set of names for devices which are different ! 251: from the DEC software names for the devices. The following table lists ! 252: both the DEC and UNIX names for the supported devices: ! 253: .DS ! 254: .TS ! 255: l l l. ! 256: Hardware UNIX DEC ! 257: _ ! 258: RM disks hp DR ! 259: RP disks hp DB ! 260: MASSBUS TE/TU tapes ht MT ! 261: TU78 tape mt MF ! 262: RK disks hk DM ! 263: RL disks rl DL ! 264: TS tapes ts MS ! 265: UDA disks ra DU ! 266: RC25 disks ra DU ! 267: IDC disks rb DQ ! 268: UNIBUS SMD disks up ! 269: TM tapes tm ! 270: TMSCP tapes tms MU ! 271: UNIBUS TU tapes ut ! 272: BI KDB disks kra DU ! 273: .TE ! 274: .DE ! 275: Here UNIBUS SMD disks are disks on an RM-emulating controller on the UNIBUS, ! 276: and TM tapes are tapes on a controller that emulates the DEC TM11. ! 277: UNIBUS TU tapes are tapes on a UNIBUS controller that emulates the DEC TU45. ! 278: IDC disks are disks on an 11/730 Integral Disk Controller. ! 279: TS tapes are tapes on a controller compatible with the DEC TS11 (e.g. ! 280: a TU80). ! 281: TMSCP tapes include the TU81 and TK50. ! 282: .PP ! 283: The normal standalone system, used to bootstrap the full UNIX system, ! 284: uses device names: ! 285: .DS ! 286: xx(a,c,d,p) ! 287: .DE ! 288: where \fIxx\fP is any of the UNIX device names in the table above. ! 289: The parameters \fIa\fP, \fIc\fP, and \fId\fP ! 290: are the \fIadapter\fP, \fIcontroller\fP, and \fIdrive\fP ! 291: numbers respectively. ! 292: The adapter is the index number of the MASSBUS or UNIBUS ! 293: (with the first one found as number 0). ! 294: The controller (or ``device'') number is the index number of ! 295: the device on that adapter. The drive number is ! 296: the index of the disk drive on that controller (or, ! 297: for MASSBUS tapes, of the formatter). The \fIp\fP ! 298: value is interpreted differently for tapes and disks: ! 299: for disks it is a disk \fIpartition\fP (in the range 0-7); ! 300: for tapes it is a file number on the tape.* ! 301: .FS ! 302: * Note that while a tape file consists of a single data stream, ! 303: the distribution tape(s) have data structures in these files. ! 304: Although the tape(s) contain only 7 tape files, they comprise ! 305: several thousand UNIX files. ! 306: .FE ! 307: For example, partition 7 of drive 2 on an RA81 connected to ! 308: the only UDA50 on UNIBUS 1 would be ``ra(1,0,2,7)''. ! 309: Normally, the adapter and controller will both be 0; it ! 310: may therefore be omitted from the device specification, ! 311: and most of the examples in this document do so. ! 312: When not running standalone, this partition would normally ! 313: be available as ``/dev/ra2g''. ! 314: Here the prefix ``/dev'' is the name of the directory where all ! 315: ``special files'' normally live, the ``hp'' serves the obvious purpose, ! 316: the ``2'' identifies this as a partition of hp drive number ``2'' ! 317: and the ``g'' identifies this as the seventh partition. ! 318: .PP ! 319: On the VAX 8200, the adapter numbering is controlled by the ! 320: ordering of the nodes on the BI; the BI is probed from low ! 321: node numbers towards high. Hence if there are two KDB50 adapters, ! 322: one at node 4, and one at node 7, the one at node 4 is kdb0, ! 323: and the one at node 7 is kdb1. ! 324: The numbering for UNIBUS adapters works similarly. ! 325: Usually, the first UNIBUS on an 8200 is at node 0; you will need ! 326: this node number to boot from tape. ! 327: Other VAX models do not permit such chaotic ordering of adapters. ! 328: .PP ! 329: In all simple cases, where only a single controller is present, ! 330: a drive with unit number 0 (in its unit ! 331: plug on the front of the drive) will be called unit 0 in its UNIX ! 332: file name. This is not, however, strictly necessary, since the system ! 333: has a level of indirection in this naming. ! 334: If there are multiple controllers, the disk unit numbers ! 335: will normally be counted sequentially across controllers. ! 336: This can be taken ! 337: advantage of to make the system less dependent on the interconnect ! 338: topology, and to make reconfiguration after hardware ! 339: failure extremely easy. ! 340: .PP ! 341: Each UNIX physical disk is divided into at most 8 logical disk partitions, ! 342: each of which may occupy any consecutive cylinder range on the ! 343: physical device. The cylinders occupied ! 344: by the 8 partitions for each drive type ! 345: are specified initially ! 346: .\" in section 4 of the programmers manual and ! 347: in the disk description file /etc/disktab (c.f. ! 348: \fIdisktab\fP(5)). ! 349: The partition information and description of the drive geometry ! 350: are written in the first sector of each disk with the ! 351: \fIdisklabel\fP(8) program; ! 352: currently, this is possible on hp and ra disks, but not on the other ! 353: types of disks on the VAX. ! 354: Each partition may be used ! 355: for either a raw data area such as a paging area or to store a ! 356: UNIX file system. ! 357: It is conventional for the first partition on a disk to be used ! 358: to store a root file system, from which UNIX may be bootstrapped. ! 359: The second partition is traditionally used as a paging area, and the ! 360: rest of the disk is divided into spaces for additional ``mounted ! 361: file systems'' by use of one or more additional partitions. ! 362: .PP ! 363: The third logical partition of each physical disk also has a conventional ! 364: usage: it allows access to the entire physical device, in many ! 365: cases including bad ! 366: sector forwarding information recorded at the end of the disk (one track ! 367: plus 126 sectors). It is ! 368: occasionally used to store a single large file system or to access ! 369: the entire pack when making a copy of it on another. ! 370: Care must be taken if ! 371: using this partition not to overwrite the last few tracks and thereby ! 372: clobber the bad sector information. ! 373: Note that the sector containing the disk label is normally write-protected ! 374: so that it is not accidentally overwritten. ! 375: Pack-to-pack copies should normally skip the first 16 sectors of a pack, ! 376: which contain the label and the initial bootstrap for some processors. ! 377: .NH 2 ! 378: UNIX devices: block and raw ! 379: .PP ! 380: UNIX makes a distinction between ``block'' and ``raw'' (character) ! 381: devices. Each disk has a block device interface where ! 382: the system makes the device byte addressable and you can write ! 383: a single byte in the middle of the disk. The system will read ! 384: out the data from the disk sector, insert the byte you gave it ! 385: and put the modified data back. The disks with the names ! 386: ``/dev/xx0a'', etc are block devices. ! 387: There are also raw devices available. ! 388: These have names like ``/dev/rxx0a'', the ! 389: ``r'' here standing for ``raw''. ! 390: Raw devices bypass the buffer cache and use DMA directly to/from ! 391: the program's I/O buffers; ! 392: they are normally restricted to full-sector transfers. ! 393: In the bootstrap procedures we ! 394: will often suggest using the raw devices, because these tend ! 395: to work faster. ! 396: Raw devices are used when making new filesystems, ! 397: when checking unmounted filesystems, ! 398: or for copying quiescent filesystems. ! 399: The block devices are used to mount file systems, ! 400: or when operating on a mounted filesystem such as the root. ! 401: .PP ! 402: You should be aware that it is sometimes important whether to use ! 403: the character device (for efficiency) or not (because it wouldn't ! 404: work, e.g. to write a single byte in the middle of a sector). ! 405: Don't change the instructions by using the wrong type of device ! 406: indiscriminately.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.