1.HE 2.de pd 3.ie \\n(.$-1 \\$1 \\$2 \\$3 4.el \\*(DY 5.. 6.in 4.1i 7.pd 8.in 9.sp 2 10.LP 11Dear Colleague: 12.sp 13.PP 14We are happy to send you information about our June 1988 15revision of the Fourth Berkeley Software Distribution, 16hereafter referred to as the ``4.3BSD tahoe'' distribution. 17The purpose of this release is to provide 4.3BSD support 18for the ``tahoe'' processor and to get feedback on some new 19features and facilities that we expect to include in future 20Berkeley releases. 21This distribution is not a standard Berkeley release; 22it is an interim release intended for testing and evaluation rather 23than production use by naive users. 24The distribution is available 25to users with licenses for the April 1986 4.3BSD release for the VAX\(dg. 26.FS 27\(dgVAX is a trademark of Digital Equipment Corporation 28.FE 29.PP 30The enclosed information is designed to serve two purposes. 31The first purpose is to acquaint you with the details of our distribution 32so you can decide whether or not you would like to receive it. 33The second purpose is to tell you how to obtain our distribution. 34.SH 35What is the 4.3BSD Tahoe Release? 36.PP 37The distribution consists of one 6250 BPI or three 1600 BPI magnetic tapes, 38certain updated manual pages, 39and a copy of ``Installing and Operating 4.3BSD on the Tahoe.'' 40The magnetic tape(s) contain copies of source code and documentation 41for both the VAX and the tahoe, and binaries for the tahoe. 42On the three-tape 1600 BPI set, 43parts of the user-contributed software are shipped 44as compressed archives to save space. 45.PP 46The primary purpose of this release is to provide support 47for the ``tahoe'' processor, the CPU used by 48Computer Consoles, Inc. (CCI Power 6/32, 6/32SX), 49and high end lines of Harris (HCX-7 and HCX-9), 50Unisys (7000/40), and ICL (Clan 7). 51Support for this processor is derived from the 4.2BSD system 52done by CCI. 53Support for new DEC equipment has also been added, 54including support for the 8250 BI-based CPU and the KDB-50 BI disk controller 55from Chris Torek, 56and the QVSS and QDSS display drivers for the MicroVAX II, contributed 57by Digital Equipment Corporation. 58We expect to provide support for both the VAX and the tahoe 59processors in future releases. 60.LP 61The major new software systems include the following features: 62.IP \(bu 63The TCP and IP code is the same as that 64recently made available via the ARPANET and Usenet. 65Several new algorithms are used in TCP, 66in particular Van Jacobson's slow start and dynamic 67window size selection algorithms and Phil Karn's modification 68to the round-trip timing algorithm. 69These changes increase throughput 70and reduce congestion and retransmission. 71Several fixes were made in the handling of IP options 72and other gateway support. 73.IP \(bu 74The file system has been generalized to remove the limits on the 75maximum number of inodes per cylinder group, cylinders per cylinder 76group, and number of distinguished rotational positions. 77The kernel and file system utilities operate normally on both 78new and old format file systems; 79old kernels treat the new file systems as read-only. 80This change allows better utilization of newer disks with larger numbers 81of sectors per cylinder. 82.IP \(bu 83The system has full support for disk labels 84that contain disk geometry information and partition layout on each disk. 85Labels are used on disks using the 86.B hp 87or 88.B uda 89drivers on the VAX (hp or ra disks) 90and all supported disks on the tahoe. 91The utility to read and write disk labels can be used with 92the system running multiuser; 93the labels are used and updated as appropriate by \fInewfs\fP, \fIbad144\fP, 94the kernel and the bootstrap programs. 95Basic file system parameters are stored in the label 96so that \fIfsck\fP can locate alternate superblocks. 97The filesystem and \fInewfs\fP use additional information about 98the disk geometry that is now available, such as track-to-track skew. 99.IP \(bu 100A new general-purpose dynamic memory allocator has been written 101that can be used by all the kernel subsystems. 102The design of this allocator takes advantage of known memory usage 103patterns in the UNIX kernel, using a hybrid strategy that is time-efficient 104for small allocations and space-efficient for large allocations. 105This allocator replaces most of the previous memory allocation interfaces 106with a single easy-to-program interface, 107results in more efficient use of global memory by eliminating 108partitioned and specialized memory pools, 109and is quick enough that no performance loss is observed 110relative to the previous implementations. 111Most of the kernel memory allocation is now done using this allocator. 112.IP \(bu 113The source code has been reorganized to ease support of multiple 114machine types. 115.IP \(bu 116The Olson/Harris/Elz timezone implementation has been added to the 117system. 118.IP \(bu 119Numerous bug fixes and enhancements have been made throughout the system, 120including new versions of the nameserver \fInamed\fP and the routing daemon 121\fIrouted\fP. 122Several years' backlog of bug fixes have been applied. 123.IP \(bu 124We have started a process of identifying the code in the 4.3BSD distribution 125that is not derived from AT&T code. 126The copyrights in this code have been changed to indicate that it 127may be freely distributed if the copyright notice is 128retained and that due credit for its origin is given to 129The Regents of the University of California. 130Over 1000 files have been identified in this distribution. 131.SH 132How to obtain the 4.3BSD tahoe release 133.PP 134This section should be read by existing licensees as well as new licensees. 135All previous 4.3BSD licensees will be able to receive 136the 4.3BSD tahoe release by simply executing the steps outlined below. 1374.2BSD licensees who have not yet upgraded to 4.3BSD will be required 138to do so as well as following the steps outlined below for the 139tahoe distribution. 140For further information on ordering the standard 4.3BSD distribution, 141contact our distribution office at the address given below. 142.PP 143Because we are a research and development organization and not a commercial 144organization, we make our research results available for a fee 145which covers only our costs for the distribution. 146We distribute only the whole system 147and cannot send individual pieces of the system. 148Because the software is distributed ``As Is'' and is partially derived 149from licensed material, we are required 150to have a formal license arrangement with each 151organization to which we distribute. 152.PP 153Specifically, we must receive from your organization the 154following material before the distribution can be sent: 155.IP \(bu 156Two appropriate signed Addenda for the tahoe distribution if you are a 1574.3BSD licensee. Add to that the appropriate Addendum to 158receive the upgrade if you are a 4.2BSD licensee. 159For new licensees, two executed copies of the Berkeley License 160Agreement (4/86) with the appropriate Addendum, i.e., for foreign 161or US government sites, plus the Addendum for the tahoe distribution. 162We require two copies of all Agreements/Addenda with original 163signatures, one of which is returned to the Licensee. 164.IP \(bu 165A check from a U.S. bank for $400.00 U.S. (for a single 6250 BPI tape) 166or $450.00 (for three 1600 BPI tapes) payable to 167``The Regents of the University of California'' 168must be received before the distribution can be sent. 169If you must issue a Purchase Order, please issue one that is blank-backed. 170If this is not possible, insert and initialize in the body of the Purchase 171Order the following clause: 172``The terms and conditions of this Purchase 173Order are not accepted by The Regents of the University of California. 174The revised Berkeley License Agreement (4/86) governs.'' 175For 4.2 licensees that have updated to 4.3BSD, substitute 176``The terms and conditions of this Purchase Order are not 177accepted by The Regents of the University of California. 178The revised Berkeley License Agreement (6/83) 179and Addendum Number One govern.'' 180.IP \(bu 181A completed Site Information Form and Equipment List. 182The distribution itself will be sent to the technical contact. 183The site information is kept confidential 184and is for our use in identifying sites with specific configurations. 185Please note that we cannot ship to post office boxes; 186therefore, please have the 187technical contact's address supplied without use of a post office box. 188.PP 189A checklist is included to aid you in assembling this material. 190All the above material must be sent to: 191.DS 192Pauline Schwartz, Distribution Coordinator 193Computer Systems Research Group 194Computer Science Division, EECS 195University of California 196Berkeley, California 94720 197.DE 198Once all these items have been received and are in proper order, the 199distribution will be sent to the technical address indicated on the Site 200Information Form that you provided when you placed your order; 201We cannot provide delivery dates. 202Once the material is assembled and packaged, 203the distribution is shipped by commercial carrier. 204Order of shipment will be based on time 205of arrival of the properly completed paperwork. 206Because of the differential in costs of shipping outside the United States, 207we ask that organizations beyond the North American continent pay 208the collect shipping charges. 209.PP 210The most expedient way to insure that your full distribution is sent 211as quickly as possible is to include in a single package the signed 212appropriate Addenda for the tahoe distribution plus any other 213necessary signed legal papers, depending on your licensing status, 214the appropriate check properly made out to 215``The Regents of the University of California,'' 216and a completely filled out Site Information Form and Equipment List, 217and to send this single package to the address noted above. 218.SH 219Large Organizations 220.PP 221Many large organizations have multiple entities that act independently 222from one another and are licensed independently from AT&T. 223Others have the parent organization licensed 224by AT&T and copies of the software distribution sent 225to each independent entity. The Berkeley License Agreement must be 226executed with the organization holding the appropriate AT&T Software Agreement. 227.PP 228If your organization has an AT&T license 229and chooses not to redistribute internally, 230please contact us for a copy of the letter of authorization 231to be executed by the parent company. 232.sp 233.SH 234Special Cases 235.PP 236\fBUniversity of California Sites\fR. 237If you are a part of the University of California, 238\fByou must use the following procedure:\fR 239Ask Pam True (415) 642-6348 in Berkeley Campus Materiel Management 240for an application for an additional CPU 241authorization under The Regents of the University 242of California's Software Agreement with AT&T. 243We will receive the completed application from Materiel Management. 244In addition, the following items must 245be sent to the Computer Systems Research Group: 2461) a letter signed by the Director or Head of Department requesting 4.3BSD, 247stating that you have read and understood the Berkeley 248License Agreement and that your organization will abide by it, 2492) an IOC for $400.00 or $450.00 (1600 BPI), and 2503) a Site Information Form and Equipment List if it has changed. 251.PP 252\fBDARPA Sites\fR. 253The research on which the Berkeley Software Distributions are based 254is sponsored by DARPA (Defense Advanced Research Projects Agency). 255Provision has been made for prepayment of distribution 256costs for a few designated DARPA sites. 257In place of the check for $400.00 or $450.00, you should include a letter 258from your Program Manager stating that you are designated as such a site. 259However, you \fBmust\fR comply with all 260other requirements in applying for the distribution. 261.SH 262Additional Copies of Documentation 263.PP 264If you wish additional copies of the documentation, please contact 265the Usenix Association at 415-528-8649. 266.SH 267A Special Note 268.PP 269The procedures and rules set out in this document are University 270and AT&T constraints that must be followed in order for the 271distribution of software to be possible. 272The Computer Systems Research Group has no control 273over these constraints and must reject your application 274if material submitted is not in order. 275.SH 276.ne 2.5i 277If You Have Read Everything and Still Need Help 278.PP 279If you have questions about the licensing process after reading 280this letter, you may call Pauline Schwartz at (415) 642-7780, 281write to her, or contact her via electronic mail at 282pauline@Berkeley.EDU. or ucbvax!pauline. 283She will not be able to answer technical questions. 284.sp 2 285.ti +2.5i 286Sincerely yours, 287.sp 3 288.ti +2.5i 289Mike Karels 290.br 291.ti +2.5i 292Computer Systems Research Group 293