|
|
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: .\" @(#)vaxhints.t 1.3 (Berkeley) 3/7/89 ! 17: .\" ! 18: .ds lq `` ! 19: .ds rq '' ! 20: .ds 4B 4.3BSD-tahoe ! 21: .nr Vx 1 \" VAX version ! 22: .ds Mc VAX ! 23: .ds mC vax ! 24: .ds Dk hp ! 25: .ds Dn RM80 ! 26: .ds Pa g ! 27: .ds Ps 4.3BSD ! 28: .bd S B 3 ! 29: .TL ! 30: Hints on Upgrading a 4.3BSD VAX System to 4.3BSD-Tahoe ! 31: .br ! 32: July 14, 1988 ! 33: .AU ! 34: Michael J. Karels ! 35: .AI ! 36: Computer Systems Research Group ! 37: Department of Electrical Engineering and Computer Science ! 38: University of California, Berkeley ! 39: Berkeley, California 94720 ! 40: (415) 642-7780 ! 41: .de IR ! 42: \\fI\\$1\|\\fP\\$2 ! 43: .. ! 44: .de UX ! 45: UNIX\\$1 ! 46: .. ! 47: .PP ! 48: This set of notes is extracted from ! 49: \fIInstalling and Operating \*(4B UNIX* on the VAX.\(dg\fP ! 50: .FS ! 51: *\s-2UNIX\s0 is a register trademark of AT&T in the USA and other countries. ! 52: .FE ! 53: .FS ! 54: \(dgDEC, VAX, IDC, SBI, UNIBUS and MASSBUS are trademarks of ! 55: Digital Equipment Corporation. ! 56: .FE ! 57: It is intended to highlight changes in \*(4B ! 58: that will affect installation on existing VAX systems, ! 59: and to point out areas of the documentation that should be examined ! 60: before installing this system. ! 61: It is \fInot\fP intended to substitute for the standard documentation, ! 62: but only to point out areas that have changed and that should be examined. ! 63: Not all of the documentation is provided in printed form, ! 64: but all of it is in the /usr/doc and /usr/src/man directories on ! 65: the distribution tape. ! 66: .PP ! 67: \fBNote that the \*(4B release contains only Tahoe filesystems and executable ! 68: images.\fP ! 69: The \*(4B distribution tape supplied by Berkeley ! 70: cannot be used to bootstrap a VAX without a running 4.2BSD or 4.3BSD system. ! 71: If you are not currently running 4.2BSD or 4.3BSD you will ! 72: have to do a full bootstrap using a 4.3BSD tape; ! 73: to install the \*(4B release, the new sources must then be loaded ! 74: and compiled. ! 75: It is possible to make a boot tape that can be used with additional machines ! 76: by extracting the sources in the distribution tape on a VAX, compiling, ! 77: and making a tape using the procedures described in Appendix A ! 78: of \fIInstalling and Operating \*(4B UNIX on the VAX.\fP ! 79: .PP ! 80: If you are running 4.2BSD or \*(Ps, upgrading your system ! 81: involves replacing your kernel and system utilities. ! 82: Binaries compiled under \*(Ps will work without recompilation ! 83: under \*(4B, though they may run faster if they are recompiled. ! 84: Binaries compiled under 4.2BSD will probably work without recompilation, ! 85: but it is a good idea to recompile and relink because of the many changes ! 86: in header files and libraries since 4.2BSD. ! 87: Conversion from 4.2BSD is probably done most easily by booting from a 4.3BSD ! 88: distribution tape, then using that system to load and compile the sources ! 89: from \*(4B. ! 90: Sites not running 4.3BSD should read ! 91: \fIInstalling and Operating 4.3BSD on the VAX\fP ! 92: as well as the \*(4B version of that document. ! 93: .PP ! 94: The easiest upgrade path from 4.2BSD or \*(Ps ! 95: (depending on your file system configuration) ! 96: is to build ! 97: new root and \fI/usr\fP file systems on unused partitions, ! 98: then copy or merge site specific files ! 99: into their corresponding files on the new system. ! 100: All user file systems can be retained unmodified, ! 101: except that the new \fIfsck\fP should be run ! 102: before they are mounted (see below). ! 103: If there is insufficient space to load the new root and \fI/usr\fP ! 104: filesystems before reusing the existing partitions, ! 105: it is \fBSTRONGLY\fP advised that you make full dumps of each filesystem ! 106: on magtape before beginning. ! 107: It is also desirable to run file system checks ! 108: of all filesystems to be converted to \*(4B before shutting down. ! 109: If you are running a system older than 4.2BSD, you will have to ! 110: dump and restore your file systems. ! 111: In either case, this is an excellent time to review your disk configuration ! 112: for possible tuning of the layout. ! 113: .PP ! 114: If converting from 4.2BSD or \*(Ps, your old ! 115: file systems must be converted. ! 116: The standard disk partitions in \*(4B are the same as those ! 117: in 4.2BSD and \*(Ps, ! 118: except for those on the DEC UDA50. ! 119: If you've modified the partition ! 120: sizes from the original BSD or CCI ones, and are not already using the ! 121: \*(4B disk labels, you will have to modify the default disk partion ! 122: tables in the kernel. Make the necessary table changes and boot ! 123: your custom kernel \fBBEFORE\fP trying to access any of your old ! 124: file systems! After doing this, if necessary, the remaining filesystems ! 125: may be converted in place by running the \*(4B version of ! 126: .IR fsck (8) ! 127: on each filesystem and allowing it to make the necessary corrections. ! 128: The new version of \fIfsck\fP is more ! 129: strict about the size of directories than the version supplied with 4.2BSD. ! 130: Thus the first time that it is run on a 4.2BSD file system, ! 131: it will produce messages of the form: ! 132: .DS ! 133: .if \n(Vx \{\ ! 134: \fBDIRECTORY ...: LENGTH\fP xx \fBNOT MULTIPLE OF 512 (ADJUSTED)\fP ! 135: .\} ! 136: .if \n(Th \{\ ! 137: \fBDIRECTORY ...: LENGTH\fP xx \fBNOT MULTIPLE OF 1024 (ADJUSTED)\fP ! 138: .\} ! 139: .DE ! 140: Length ``xx'' will be the size of the directory; ! 141: it will be expanded to the next multiple of ! 142: .if \n(Vx \{\ ! 143: 512 ! 144: .\} ! 145: .if \n(Th \{\ ! 146: 1024 ! 147: .\} ! 148: bytes. ! 149: The new \fIfsck\fP will also set default \fIinterleave\fP and ! 150: \fInpsect\fP (number of physical sectors per track) values on older ! 151: file systems, in which these fields were unused spares; this correction ! 152: will produce messages of the form: ! 153: .DS ! 154: \fBIMPOSSIBLE INTERLEAVE=0 IN SUPERBLOCK (SET TO DEFAULT)\fP* ! 155: \fBIMPOSSIBLE NPSECT=0 IN SUPERBLOCK (SET TO DEFAULT)\fP ! 156: .DE ! 157: .FS ! 158: * The defaults are to set \fIinterleave\fP to 1 and ! 159: \fInpsect\fP to \fInsect\fP; ! 160: .if \n(Vx \{\ ! 161: this is correct on many drives. ! 162: Notable exceptions are the RM80 and RA81, ! 163: where npsect should be set to ! 164: one more than nsect. ! 165: This affects only performance (and in the case ! 166: of the RA81, at least, virtually unmeasurably). ! 167: .\} ! 168: .if \n(Th \{\ ! 169: this is correct on all drives supported on the CCI. ! 170: .\} ! 171: .FE ! 172: File systems that have had their interleave and npsect values ! 173: set will be diagnosed by the old \fIfsck\fP as having a bad superblock; ! 174: the old \fIfsck\fP will run only if given an alternate superblock ! 175: .if \n(Vx \{\ ! 176: (\fIfsck \-b32\fP), ! 177: .\} ! 178: .if \n(Th \{\ ! 179: (\fIfsck \-b16\fP), ! 180: .\} ! 181: in which case it will re-zero these fields. ! 182: The \*(4B kernel will internally set these fields to their defaults ! 183: if fsck has not done so; again, the ! 184: .if \n(Vx \{\ ! 185: \fI\-b32\fP ! 186: .\} ! 187: .if \n(Th \{\ ! 188: \fI\-b16\fP ! 189: .\} ! 190: option may be ! 191: necessary for running the old \fIfsck\fP. ! 192: .PP ! 193: In addition, \*(4B removes several limits on file system sizes ! 194: that were present in both 4.2BSD and 4.3BSD. ! 195: The limited file systems ! 196: continue to work in \*(4B, but should be converted ! 197: as soon as it is convenient ! 198: by running \fIfsck\fP with the \fI\-c\fP option. ! 199: If no file systems have been so converted, ! 200: the sequence \fIfsck \-p \-c\fP will update all of them, ! 201: fix the interleave and npsect fields, ! 202: and fix any incorrect directory lengths ! 203: all at once. ! 204: The new unlimited file system formats are treated as read-only ! 205: by older systems. ! 206: A second \fIfsck \-c\fP, however, will ! 207: reconvert the new format to the old if none of the static limits ! 208: of the old file system format have been exceeded. ! 209: The new file systems are otherwise ! 210: compatible between 4.2BSD, \*(Ps, and \*(4B, ! 211: though running a \*(4B file system under older systems ! 212: may cause more of the above ! 213: messages to be generated the next time it is \fIfsck\fP'ed on \*(4B. ! 214: .NH 2 ! 215: Hints on converting from 4.3BSD to \*(4B ! 216: .PP ! 217: The largest visible change between 4.3BSD to \*(4B ! 218: (other than the addition of support for the Tahoe processor) ! 219: is the addition of support for disk labels. ! 220: This facility allows each disk or disk pack to contain all geometry ! 221: information about the disk and the partition layout for the disk. ! 222: Disk labels are supported on all disk types on the Tahoe machines, ! 223: and on hp and ra/rd disks on the VAX. ! 224: See ! 225: .IR disklabel (8) ! 226: and ! 227: .IR disklabel (5). ! 228: Installation of this facility requires use of the new kernel and device ! 229: drivers, bootstraps and other standalone programs, ! 230: /etc/disktab, ! 231: .if \n(Vx \{\ ! 232: .IR bad144 (8V), ! 233: .\} ! 234: .IR newfs (8), ! 235: and probably other programs. ! 236: .if \n(Vx \{\ ! 237: .PP ! 238: \*(4B includes support for the VAX 8200 and 8250, ! 239: with support for the KDB-50 disk controller on the VAX BI bus, ! 240: contributed by Chris Torek. ! 241: .PP ! 242: The bootstrap programs have been fixed to work on MicroVAX IIs ! 243: and VAXstation II's with QVSS (VS II) or QDSS (GPX) displays; ! 244: the kernel includes support for these displays, courtesy of Digital ! 245: Equipment Corp. ! 246: In order to install the bootstrap on RD52/53/54 disks with ! 247: .IR disklabel (8), ! 248: the new /etc/disktab must be used, ! 249: or the block 0 bootstrap must be explictly listed as /usr/mdec/rdboot ! 250: (\fInot\fP raboot). ! 251: .\} ! 252: .PP ! 253: The order in which daemons are started by /etc/rc and /etc/rc.local ! 254: has changed, and network initialization has been split into /etc/netstart. ! 255: Look at the prototype files, and modify /etc/rc.local as necessary. ! 256: .PP ! 257: \*(4B includes the Olson ! 258: timezone implementation, which uses timezone and daylight-savings-time ! 259: rules loaded from files in /etc/zoneinfo; see ! 260: .IR ctime (3) ! 261: and ! 262: .IR tzfile (5). ! 263: .PP ! 264: The type of the ! 265: .IR sprintf (3S) ! 266: function has been changed from \fIchar *\fP in 4.2BSD and 4.3BSD ! 267: to \fIint\fP as in the proposed ANSI C standard and in System V. ! 268: Programers are discouraged from using the return value from ! 269: .I sprintf ! 270: until this change is ubiquitous. ! 271: Fortunately, the previous return value from ! 272: .I sprintf ! 273: was essentially useless. ! 274: .PP ! 275: The ownership and modes of some directories have changed. ! 276: The \fIat\fP programs now run set-user-id ``root'' instead of ``daemon.'' ! 277: Also, the uucp directory no longer needs to be publicly writable, ! 278: as \fItip\fP reverts to privileged status to remove its lock files. ! 279: After copying your version of /usr/spool, you should do: ! 280: .DS ! 281: \fB#\fP \fIchown \-R root /usr/spool/at\fP ! 282: \fB#\fP \fIchown \-R uucp.daemon /usr/spool/uucp\fP ! 283: \fB#\fP \fIchmod \-R o\-w /usr/spool/uucp\fP ! 284: .DE ! 285: .PP ! 286: The MAKEHOSTS file has moved from /usr/hosts to /usr. ! 287: .PP ! 288: The source versions of the manual pages have been moved from ! 289: /usr/man/man[1-8] to /usr/src/man, /usr/src/new/man, and /usr/src/local/man. ! 290: Local manual pages should be moved into their respective source code ! 291: directories, or into /usr/src/local/man/man[1-8], and Makefiles changed to ! 292: install the formatted manual pages into /usr/local/man/cat[1-8]. The shell ! 293: script /usr/man/manroff calls nroff with the standard manual arguments. An ! 294: example of installing a manual page might be: ! 295: .DS ! 296: \fB#\fP \fI/usr/man/manroff example.2 > example.0\fP ! 297: \fB#\fP \fIinstall -o bin -g bin -m 444 example.0 /usr/local/man/cat2\fP ! 298: .DE ! 299: .PP ! 300: If you are using the name server, your \fIsendmail\fP configuration ! 301: file will need some minor updates to accommodate it. ! 302: See the ``Sendmail Installation and Operation Guide'' and the sample ! 303: \fIsendmail\fP configuration files in /usr/src/usr.lib/sendmail/cf. ! 304: The sendmail.cf's supplied with this release are alleged to be ! 305: ``generic'', but have only really seen use at Berkeley. In particular ! 306: there are two points to watch out for. First, all host names in the ! 307: sendmail.cf itself must be fully qualified names. Second, the ! 308: sendmail.cf's assume you have a /usr/lib/sendmail that was compiled ! 309: with the resolver library (i.e., not hosttables). This is necessary ! 310: to canonicalize unqualified names into fully-qualified names (e.g., ! 311: foo -> foo.bar.com). Using these .cf files with a host table can ! 312: probably be done, but it will be difficult. ! 313: Be sure to regenerate your sendmail frozen configuration file after ! 314: installation of your updated configuration file with the command ! 315: \fI/usr/lib/sendmail -bz\fP. ! 316: The aliases file, ! 317: /usr/lib/aliases has also been changed to add certain well-known addresses. ! 318:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.