INSTALLATION NOTES for NetBSD/pc532 1.1 Be sure to read _ALL_ of this document before you try to install NetBSD/pc532. What is NetBSD? ---- -- ------ NetBSD is a Berkeley Networking Release 2 (Net/2) and 4.4BSD-Lite -derived Operating System. It is a fully functional UN*X-like system which runs on many architectures and is being ported to more. NetBSD, as the name implies, is a creation of the members of the network community and without the net it's likely that this release wouldn't have come about. NetBSD 1.1 is a evolutionary release which contains over a year of changes to the kernel, user-level utilities, and documentation. Continuing the multi-platform tradition, NetBSD has added ports to atari and mvme68k based machines. Kernel interfaces have continued to be refined, and now several subsystems and device drivers are shared among the different ports. You can look for this trend to continue. NetBSD 1.1 has significantly enhanced the binary emulation subsystem (which includes iBCS2, Linux, OSF/1, SunOS, SVR4, Solaris and Ultrix compatibility) and several kernel subsystems have been generalized to support this more readily. The binary emulation strategy is aimed at making the emulation as accurate as possible. NetBSD 1.1 is also the first release to see machine-independent disk striping. The concatenated disk driver (ccd), which was previously supported only by the hp300 port, has been vastly improved. Many bugs were fixed, and explicit references to device-dependent routines removed and replaced by calls to the generic "vnode operation" routines. In addition, several features were added, including partition support, dynamic configuration and unconfiguration via a user space system utility program, and virtually unlimited number of component devices. Many new user programs have been added in NetBSD 1.1, as well, bringing it closer to our goal of supplying a complete UN*X-like environment. For the pc532 port, there are a few known problems. They include: a) ppp reports a lot of input errors on some machines. b) Some tape drives do not work very well. Some have hung the system. c) The serial drivers do not have all the desired features. (ttyflags is the most glaring.) d) The disk driver is polled, not interrupt driven. The Future of NetBSD: --- ------ -- ------ The NetBSD Foundation was recently incorporated as a non-profit organization. It's purpose is to encourage, foster and promote the free exchange of computer software, namely the NetBSD Operating System. The foundation will allow for many things to be handled more smoothly than could be done with our previous informal organization. In particular, it provides the framework to deal with other parties that wish to become involved in the NetBSD Project. (IN WHAT WAY? Money, donations, etc) We believe that the NetBSD Foundation will help improve the quality of NetBSD by: * providing better organization to keep track of development efforts, including co-ordination with groups working in related fields. * providing a framework to receive donations of goods and services and to own the resources necessary to run the NetBSD Project. * providing a better position from which to undertake promotional activities. * periodically organizing workshops for developers and other interested people to discuss ongoing work. We hope to have regular releases of the full binary and source trees, but these are difficult to coordinate, especially with all of the architectures which we now support! We hope to support even _more_ hardware in the future, and have a rather large number of other ideas about what can be done to improve NetBSD. We intend to continue our current practice of making the NetBSD-current development source available on a daily or nearly-daily basis. We intend to integrate free, positive changes from whatever sources will provide them, providing that they are well thought-out and increase the usability of the system. Above all, we hope to create a stable and accessible system, and to be responsive to the needs and desires of NetBSD users, because it is for and because of them that NetBSD exists. Sources of NetBSD: ------- -- ------ Host name Services Provided ---- ---- -------- -------- ftp.iastate.edu Anonymous FTP, AFS Anon-FTP path: pub/netbsd AFS path: /afs/iastate.edu/public/ftp/pub/netbsd ftp.eecs.umich.edu Anonymous FTP Anon-FTP path: BSD/NetBSD gatekeeper.dec.com Anonymous FTP Anon-FTP path: pub/BSD/NetBSD wipux2.wifo.uni-mannheim.de Anonymous FTP, SUP Anon-FTP path: pub/NetBSD SUP: get the file pub/misc/sup/supfile.example via anonymous FTP and read it as an example. ftp.demon.co.uk Anonymous FTP, possibly SUP Anon-FTP path: pub/BSD/NetBSD SUP: contact peter@demon.net for SUP server status/information ftp.uni-regensburg.de Anonymous FTP Anon-FTP path: pub/NetBSD ftp.unit.no Anonymous FTP Anon-FTP path: pub/NetBSD ftp.stacken.kth.se Anonymous FTP Anon-FTP path: pub/OS/NetBSD flick.lerc.nasa.gov Anonymous FTP Anon-FTP path: pub/NetBSD coombs.anu.edu.au Anonymous FTP Anon-FTP path: pub/NetBSD ftp.funet.fi Anonymous FTP Anon-FTP path: pub/unix/NetBSD ftp.netbsd.org Anonymous FTP, SUP Anon-FTP path: pub/NetBSD SUP: get the file pub/sup/README.sup via anonymous FTP from ftp.netbsd.org, and read it for instructions. If you wish to become a distribution site for NetBSD, contact mirrors@netbsd.org. NetBSD 1.1 Release Contents: ------ --- ------- -------- The NetBSD 1.1 release is organized in the following way: .../NetBSD-1.1/ BUGS Known bugs list (incomplete and out of date). CHANGES Changes since NetBSD's last release (and before). LAST_MINUTE Last minute changes. MIRRORS A list of sites that mirror the NetBSD 1.1 distribution. README.files README describing the distribution's contents. TODO NetBSD's todo list (incomplete and out of date). patches/ Post-release source code patches. source/ Source distribution sets; see below. In addition to the files and directories listed above, there is one directory per architecture, for each of the architectures that NetBSD 1.1 has a binary distribution for. There are also 'README.export-control' files sprinkled liberally throughout the distribution tree, which point out that there are some portions of the distribution (e.g. those containing crypt(3)) that should not be exported from the United States, and that if you do export them, it's your fault, not ours. The source distribution sets can be found in subdirectories of the "source" subdirectory of the distribution tree. They contain the complete sources to the system. The source distribution sets are as follows: dsrc11 This set contains the "domestic" sources. These sources contain export-restricted encryption code and should not be exported from the U.S. [ 140K gzipped, 655K uncompressed ] gsrc11 This set contains the "gnu" sources, including the source for the compiler, assembler, groff, and the other GNU utilities in the binary distribution sets. [ 7.1M gzipped, 30.4M uncompressed ] ksrc11 This set contains the sources to the NetBSD 1.1 kernel, config(8), config.old(8) and dbsym(8). [ 6.0M gzipped, 27.0M uncompressed ] ssrc11 This set contains the "share" sources, which include the sources for the man pages not associated with any particular program, the sources for the typesettable document set, the dictionaries, and more. [ 2.4M gzipped, 8.9M uncompressed ] src11 This set contains all of the NetBSD 1.1 sources which are not mentioned above. [ 9.3M gzipped, 41.6M uncompressed ] It is worth noting that unless all of the source distribution sets are installed (except the domestic set), you can't rebuild and install the system from scratch, straight out of the box. However, all that is required to rebuild the system in that case is a trivial modification to one Makefile. The source distribution sets are distributed as groups of files named "set_name.xx" where "set_name" is the distribution set name, and "xx" is the sequence number of the file, starting with "aa" for the first file in the distribution set, then "ab" for the next, and so on. All of these files except the last one of each set should be exactly 240,640 bytes long. (The last file is just long enough to contain the remainder of the data for that distribution set.) Catted together, the files belonging to a source distribution set comprise a gzipped tar file. If you want to look at list of the files contained in the set, you could use the command: cat set_name.?? | gunzip | tar tvf - or to actually extract the files contained in the set: cat set_name.?? | gunzip | tar xfp - In each of the source distribution set directories, there is a file named "CKSUMS" which contains the checksums of the files in that directory, as generated by the cksum(1) utility. You can use cksum to check the integrity of the archives, if you suspect that one of the files is corrupt and have access to a cksum binary. The pc532-specific portion of the NetBSD 1.1 release is found in the "pc532" subdirectory of the distribution. That subdirectory contains the files as follows: .../NetBSD-1.1/pc532/ INSTALL Installation notes; this file. CKSUM output of "cksum *.gz" inst-11.fs.gz Installation file system. download.c.gz Source for a pc532 ROM compat download pgm netbsd.default.gz Upgrade kernel base.tar.gz base distribution comp.tar.gz compiler tools & libraries etc.tar.gz files for /etc games.tar.gz /usr/games and friends man.tar.gz /usr/man misc.tar.gz various text.tar.gz groff and friends The binary distribution consists of the following files: base.tar.gz The NetBSD/pc532 1.1 base binary distribution. You MUST install this distribution set. It contains the base NetBSD utilities that are necessary for the system to run and be minimally functional. It excludes everything described below. [ 6.8M gzipped ] comp.tar.gz The NetBSD/pc532 Compiler tools. All of the tools relating to C, C++, and FORTRAN (yes, there are two!). This set includes the system include files (/usr/include), the linker, the compiler tool chain, and the various system libraries. This set also includes the manual pages for all the utilities it contains, as well as the system call and library manual pages. [ 4.7M gzipped ] etc.tar.gz This distribution set contains the system configuration files that reside in /etc and in several other places. This set MUST be installed if you are installing the system from scratch, but should NOT be used if you are upgrading. (If you are upgrading, it's recommended that you get a copy of this set and CAREFULLY upgrade your configuration files by hand.) [ 63K gzipped ] games.tar.gz This set includes the games and their manual pages. [ 2.8M gzipped ] man.tar.gz This set includes all of the manual pages for the binaries and other software contained in the base set. Note that it does not include any of the manual pages that are included in the other sets. [ 0.8M gzipped ] misc.tar.gz This set includes the system dictionaries (which are rather large), the typesettable document set, and man pages for other architectures which happen to be installed from the source tree by default. [ 1.9M gzipped ] text.tar.gz This set includes NetBSD's text processing tools, including groff, all related programs, and their manual pages. [ 0.8M gzipped ] The pc532 distribution set does not include a security distribution. If you are in the US and want the security distribution you must get the security source distribution and recompile libcrypt.a and recompile the following programs: ed, ftpd, makekey, rexecd, uucpd, init, lock, login, passwd, skeyinit, su, tn3270, pppd The initial installation process on a pc532 without NetBSD/pc532 is supported by the following files: Initial file system used via SCSI floppy or downloaded into memory: inst-11.fs -- file system containing boot loader and install kernel with 2MB ram root file system. download.c -- source for the program to download inst-11.fs into memory via the pc532 ROM monitor. The upgrade process is supported by having a copy of a 1.1 kernel available. This file is: netbsd.default.gz -- a kernel produced from the DEFAULT configuration file in pc532/conf. NetBSD System Requirements and Supported Devices: ------ ------ ------------ --- --------- ------- NetBSD/pc532 1.1 runs on a PC532 computer. It supports a subset of the "standard" hardware to date. This is defined as: 4 - 32 Megs of memory 8 serial lines done by 4 scn2681 chips the NCR DP8490 SCSI chip (scsi only) Most SCSI disks work (fixed and floppy) A few SCSI tapes work Some SCSI CD-ROM drives work The Matthias Pfaller Parallel Port. NetBSD/pc532 currently expects the ROM monitor to be the "autoboot monitor" of Oct/Nov 1991. It includes support to set up auto booting of NetBSD, including a secondary boot program that the autoboot monitor will load that in turn loads the NetBSD kernel from a NetBSD file system. Most of the pc532 specific development of NetBSD/pc532 was done on a machine with 8-Megs of memory. It should run with 4-Megs of memory although it may be slower. Getting the NetBSD System on to Useful Media: ------- --- ------ ------ -- -- ------ ----- The "standard" method of getting NetBSD/pc532 onto your pc532 is via the console terminal and using the downloading parts of the ROM monitor. As such, usually another computer has the distribution on disk and is connected via a serial line to your pc532's console port. A terminal connected to the attached host computer is used to access the pc532 console via a terminal program. The source for a program called download is part of this distribution. Download sends data to the ROM monitor over the serial line. You may need to find and read the documentation about the ROM monitor download command and other low level comands. Other methods of getting NetBSD/pc532 on your pc532 may include SCSI tape or SCSI floppy disk or cloning a disk on a system already running NetBSD/pc532. If you have some operating system already running on your pc532, you can use that OS to get NetBSD/pc532 on a hard disk much easier than with the ROM monitor. (NetBSD/pc532 was developed from Minix/pc532 until it was self hosting. You can run NetBSD and Minix or other OS off the same disk.) Preparing your System for NetBSD Installation: --------- ---- ------ --- ------ ------------ The major preparation needed is to make sure you can recover any current bits stored on your pc532. If you don't care about your data on the disk, you don't need to do anything. Installing the NetBSD System: ---------- --- ------ ------ (IF you already have NetBSD/pc532 installed and you only want to update your system, see the next section.) To install NetBSD/pc532, there are several things you need to know. First, NetBSD "autoconfigs" the scsi devices. inst-11.fs has only support for disks configured into the kernel. Starting the search at SCSI address 0, lun 0 and increasing, the first disk found will be sd0 regardless of the address, the second will be sd1. KLONDIKE for example has the following devices installed: sd0 -> ID 0 LUN 0: Quantum LP52S hard disk drive sd1 -> ID 1 LUN 0: Micropolis 4110 hard disk drive sd2 -> ID 2 LUN 0: Teac FC-1, 3.5" floppy disk drive sd3 -> ID 2 LUN 1: Teac FC-1, 5.25" floppy disk drive cd0 -> ID 3 LUN 0: Toshiba XM-4101TA CD-ROM drive st0 -> ID 4 LUN 0: Tandberg TDC3600 QIC tape drive Only sd0-sd3 are supported by the inst-11.fs kernel. Next you need to know what the install script wants to do. This install is script on the ram disk root that can do most of the work of configuring your disk. a) The script assumes your are using the first n sectors of your disk, where you can specify n. It will allow you to create up to 5 file system partitions, one swap partition and one boot partition. b) You should know how many total sectors are on your disk. The configure will report a head, track, and cylinder count, but I have found that on my disks, it reports something that makes a smaller disk than I really had. c) It is possible to have the install script make a partition over your save area AND not make a new file system, thus preserving what is there. Then, later you can make a new file system after you no longer need the stuff there. You will need to do only one boot to get things working from the disk. The Install Procedure: a) Adjust your console device settings. The inst-11.fs kernel will come up with 9600 baud, 7 bits, even parity and one stop bit. Adjust your terminal to match these settings. The monitor's baud rate can be changed with "baud d'9600". b) Get inst-11.fs and boot the kernel. From Floppy: (and using the autoboot monitor) If you have a 1.44 meg SCSI floppy drive, you can put inst-11.fs onto a 3.5" floppy disk. Insert the disk into your floppy drive and use the monitor's boot command to boot the default image from the floppy. The image booted will ask you for a kernel to load. Answer sdXa:/netbsd Replace X with your drive number. For KLONDIKE X would be "2". Tape: You will need to load a copy of inst-11.fs into RAM. - load the inst-11.fs at 0x288000 - run at 0x3E8820 The boot program will ask you now for a kernel to load. Answer rd0a:/netbsd Serial line: Provided with the distribution is source for program called download. (download.c) This program when used as "download file" will read the contents of the file and output to standard output a byte sequence used by the pc532 ROM monitor to download a binary file into RAM. Using this program on a computer connected to the pc532, one can load a copy of inst-11.fs into RAM at 0x288000. The boot sequence is now the same as with tape. c) Choose a disk geometry. For me, the reported geometry left some sectors "unallocated". That is, the autoconfig message said the disk had 2428 cylinders, 9 heads, and 93 sectors/track. This gives a total of 2032236 sectors, but I knew that I had 2053880 sectors. To help in this process, there is a program "factor" that is on the inst-11.fs. The usage is "factor number" and it lists the prime factors of number. For example, with the 2053880 sector disk I got: ---->~/sd1 steelhead[3]$ factor 2053880 2053880: 2 2 2 5 51347 Not many to choose from, so I tried ... ---->~/sd1 steelhead[4]$ factor 2053820 2053820: 2 2 5 103 997 Now I'd like to get about a meg per track: steelhead[5]$ echo "2 * 997"|bc 1994 Now I need the number of tracks (or cylinders): steelhead[5]$ echo "2 * 5 * 103"|bc 1030 So I ended up choosing 1030 cylinders, 1 head, 1994 sectors/track. I "lost" only 60 sectors, but got a "resonable geometry". d) run "install" -- it will ask you for the disk geometry and other questions. It will ask you for the geometry and then ask you how many of those sectors you want to use for NetBSD. It also wants to know the size of your boot partition (to be used with the auto-boot monitor), your root partition, your swap partition, and then any other partitions you may want. For the "other" partitions, it will ask for a mount point. The mount point will be "relative to /" and should not include the leading "/". Also, IF you do not want the partition to have newfs run on it (that is it might be the last one and have a copy of inst-11.fs) enter "NO" to the mount point and it will not run newfs on the partition. It will enter the partition into the disklabel. e) look around, if you want ... and then halt NetBSD. f) reboot the machine. Using the autoboot monitor, all you should have to do is give the ROM monitor command "boot". The secondary UFS boot program eventually times out and auto-loads /netbsd. You can get it to do it faster by hitting "return". If you are NOT using the autoboot monitor, it's time to warm up your eprom burner :-) g) Now it is time to load all the other files of the distribution: You can do this via -- a) a TCP/IP link (slip, ppp or plip) you have ifconfig, slattach, route, netstat, hostname and ftp on the mini-root. You can even use nfs... Plip is only an option if you have installed a centronics port in your pc532. You do have access to vi to edit your network files. (/etc/resolv.conf, ...) b) floppy disk c) tape d) cdrom (If you have a CD with NetBSD/532 ...) e) Use the ROM compatable "download" program. The program download is included in the initial installation and can be used as the receive end of the download by using it as "download -r file_to_write". If the CRC is correct, the file is retained. If the CRC is not correct, the file is deleted. f) some other method? (Let me know about it.) h) Load the tar.gz files. Choose a place to put them. I would make a directory /gz.files and put them there. If you are "short on space," you might want to load them and extract them one at a time. A minimum installation is "base" and "etc". It takes about 32 Megs installed + 15 Megs for the base.tar.gz. i) Extract the tar files in /. For example, if your *.tar.gz were in a directory /gz.files, to extract base.tar.gz you would: - cd / - tar -xpzf /gz.files/base.tar.gz --unlink Add v to the flags if you want a verbose extract. The --unlink is to make sure that the install versions of sh, init, ... are replaced by their proper versons in base.tar.gz. I think it is wise to include the --unlink for other things. j) Extract at least "base" and "etc" for a new installation. For "update" extracts, don't extract "etc" directly unless you have saved your current /etc tree. For "full" installations, extract all files. k) Edit the information in /etc - hosts - host name and address information - myname - your host name - mygate - hostname of gateway (assuming you have one) - resolv.conf - which nameserver to use - hostname.{sl0,ppp0,plip0} - interface hostname - netstart - configures the network and says if sendmail should be started - ttys - make sure the console entry has the correct speed - gettytab - I find "ap" instead of "ep" in the default entry works better for me. - fstab - make sure it includes all partitions you want mounted - localtime - this is usually a link into /usr/share/zoneinfo Now you can adjust the kernel's default baud rate to match your monitor's default baud rate. Do the following: gdb -w /netbsd set scndefaultrate = YOUR_BAUD_RATE quit where YOUR_BAUD_RATE is the actual value, 19200, 38400 or something slower than 9600. If you set scndefaultrate to something bogus, you'll probably not be able to reboot... So be carefull! l) Reboot the machine and it should come up in multi-user mode *IF* you got it configured correctly. m) Enjoy! And help fix bugs and improve NetBSD/pc532! Upgrading a previously-installed NetBSD System: --------- - ---------- --------- ------ ------ The upgrade to NetBSD 1.1 is a binary upgrade; it would be prohibitive to make users upgrade by compiling and installing the 1.1 sources, and it would be very difficult to even compile a set of instructions that allowed them to do so. To do the upgrade, you must have at least base.tar.gz on disk and a copy of the proper netbsd.default. It will require quite a bit of disk space to do the upgrade. Since upgrading involves replacing the kernel, and most of the system binaries, it has the potential to cause data loss. You are strongly advised to BACK UP ANY IMPORTANT DATA ON YOUR DISK, whether on the NetBSD partition or on another operating system's partition, before beginning the upgrade process. To upgrade your system, follow the following instructions: Make sure your are root. Just in case the new binaries don't run with the old kernel, make copies of several key binaries from /bin, /sbin and /usr/bin in some directory. (Things like sh, cp, ls, rm, tar, halt, and others.) Extract the tar.gz files. Remember to use the --unlink option with tar so it can replace binaries currently in use. For example, to extract base.tar.gz: cd / tar -xpzf /gz.files/base.tar.gz --unlink Extract all the tar.gz files you want. You should carefully work at upgrading /etc. There may be changes to file formats depending on what version of NetBSD/pc532 you are running. BE CAREFUL IF YOU ARE NOT RUNNING WITH SECURITY. The 1.1 distribution does contain support for password encription. It would be reasonable to save a copy of master.passwd and remove all passwords until after you upgrade. Place netbsd.default in / as the file netbsd. Reboot. (Remember, detbsd.default is a 9600 console line kernel. Read the last part of the new installation part of these notes to find out how to change your default speed.) After reboot, you should make sure you check your new file systems. Administrivia: ------------- Registration? What's that? If you've got something to say, do so! We'd like your input. There are various mailing lists available via the mailing list server at . To get help on using the mailing list server, send mail to that address with an empty body, and it will reply with instructions. There are various mailing lists set up to deal with comments and questions about this release. Please send comments to: netbsd-comments@NetBSD.ORG To report bugs, use the 'send-pr' command shipped with NetBSD, and fill in as much information about the problem as you can. Good bug reports include lots of details. Additionally, bug reports can be sent by mail to: netbsd-bugs@NetBSD.ORG Use of 'send-pr' is encouraged, however, because bugs reported with it are entered into the NetBSD bugs database, and thus can't slip through the cracks. There are also port-specific mailing lists, to discuss aspects of each port of NetBSD. Use majordomo to find their addresses. If you're interested in doing a serious amount of work on a specific port, you probably should contact the "owner" of that port (listed below). If you'd like to help with this effort, and have an idea as to how you could be useful, send mail and/or subscribe to: netbsd-help@NetBSD.ORG As a favor, please avoid mailing huge documents or files to these mailing lists. Instead, put the material you would have sent up for FTP somewhere, then mail the appropriate list about it, or, if you'd rather not do that, mail the list saying you'll send the data to those who want it. Thanks go to: ------ -- -- Members and former members of UCB's Computer Systems Research Group, including (but not limited to): Keith Bostic Ralph Campbell Mike Karels Marshall Kirk McKusick for their ongoing work on BSD systems, support, and encouragement. Also, our thanks go to: Mike Hibler Rick Macklem Jan-Simon Pendry Chris Torek for answering lots of questions, fixing bugs, and doing the various work they've done. UC Berkeley's Experimental Computing Facility provided a home for sun-lamp in the past, people to look after it, and a sense of humor. Rob Robertson, too, has added his unique sense of humor to things, and for a long time provided the primary FTP site for NetBSD. Without CVS, this project would be impossible to manage, so our hats go off to Brian Berliner, Jeff Polk, and the various other people who've had a hand in making CVS a useful tool. Alistair G. Crooks has been producing tar file snapshot reports for NetBSD-current users, a very valuable service. Dave Burgess has been maintaining the 386BSD/NetBSD/FreeBSD FAQ for quite some time, and deserves to be recognized for it. The following people (in alphabetical order) have made donations or loans of hardware and/or money, to support NetBSD development, and deserve credit for it: Jason Brazile Dave Burgess Charles Conn Canada Connect Corporation Brian Carlstrom Tom Coulter Charles D. Cranor Demon Internet, UK Greg Gingerich Michael L. Hitch Scott Kaplan Chris Legrow Herb Peyerl Mike Price Thor Lancelot Simon Bill Sommerfeld Paul Southworth Steve Wadlow (If you're not on that list and should be, tell us! We probably were not able to get in touch with you, to verify that you wanted to be listed.) Finally, we thank all of the people who've put sweat and tears into developing NetBSD since its inception in January, 1993. (Obviously, there are a lot more people who deserve thanks here. If you're one of them, and would like to mentioned, tell us!) We are: -- --- (in alphabetical order) The NetBSD core group: J.T. Conklin Charles Hannum Paul Kranenburg The port-masters (and their ports): Allen Briggs (mac68k) Chuck Cranor (mvme68k) Chris G. Demetriou (alpha) Charles Hannum (1) Chris Hopps (amiga) Paul Kranenburg (sparc) Ted Lemon (pmax) Anders Magnusson (vax) Phil Nelson (pc532) Gordon Ross (sun3) Jason Thorpe (hp300) Leo Weppelman (atari) Supporting cast: Steve Allen John Brezak Dave Burgess Hubert Feyrer Adam Glass Brad Grantham Matthew Green Michael L. Hitch Lawrence Kesteloot John Kohl Paul Mackerras Neil J. McRae Perry Metzger Herb Peyerl Matthias Pfaller Chris Provenzano Waldi Ravens Scott Reynolds Thor Lancelot Simon Wolfgang Solfrank Frank van der Linden Christos Zoulas Legal Mumbo-jumbo: ----- ----- ----- The following notices are required to satisfy the license terms of the software that we have mentioned in this document: This product includes software developed by the University of California, Berkeley and its contributors. This product includes software developed by the Computer Systems Engineering Group at Lawrence Berkeley Laboratory. This product includes software developed by Christopher G. Demetriou. This product includes software developed by Adam Glass. This product includes software developed by Christian E. Hopps. This product includes software developed by Paul Kranenburg. This product includes software developed by John Kohl. This product includes software developed by Terrence R. Lambert. This product includes software developed by Frank van der Linden. This product includes software developed by Philip A. Nelson. This product includes software developed by Jochen Pohl. This product includes software developed by Chris Provenzano. This product includes software developed by Theo de Raadt. This product includes software developed by the David Muir Sharnoff. This product includes software developed by SigmaSoft, Th. Lockert. This product includes software developed by Jason Thorpe. This product includes software developed by TooLs GmbH. This product includes software developed by Christos Zoulas. This product includes software developed by the Alice Group. This product includes software developed by Philip L. Budne. This product includes software developed by Christopher G. Demetriou. This product includes software developed by Philip A. Nelson. This product includes software at the Helsinki University of Technology. Some files have the following copyright: /* * Copyright (c) 1992 Helsinki University of Technology * All Rights Reserved. * * Permission to use, copy, modify and distribute this software and its * documentation is hereby granted, provided that both the copyright * notice and this permission notice appear in all copies of the * software, derivative works or modified versions, and any portions * thereof, and that both notices appear in supporting documentation. * * HELSINKI UNIVERSITY OF TECHNOLOGY ALLOWS FREE USE OF THIS SOFTWARE IN * ITS "AS IS" CONDITION. HELSINKI UNIVERSITY OF TECHNOLOGY DISCLAIMS ANY * LIABILITY OF ANY KIND FOR ANY DAMAGES WHATSOEVER RESULTING FROM THE * USE OF THIS SOFTWARE. */ At least one file contains: * Copyright 1990 by Open Software Foundation, * Grenoble, FRANCE * * All Rights Reserved * * Permission to use, copy, modify, and distribute this software and * its documentation for any purpose and without fee is hereby granted, * provided that the above copyright notice appears in all copies and * that both the copyright notice and this permission notice appear in * supporting documentation, and that the name of OSF or Open Software * Foundation not be used in advertising or publicity pertaining to * distribution of the software without specific, written prior * permission. * * OSF DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE * INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, * IN NO EVENT SHALL OSF BE LIABLE FOR ANY SPECIAL, INDIRECT, OR * CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM * LOSS OF USE, DATA OR PROFITS, WHETHER IN ACTION OF CONTRACT, * NEGLIGENCE, OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION * WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. */ Some files have the following copyright: /* * Mach Operating System * Copyright (c) 1992 Carnegie Mellon University * Copyright (c) 1992 Helsinki University of Technology * All Rights Reserved. * * Permission to use, copy, modify and distribute this software and its * documentation is hereby granted, provided that both the copyright * notice and this permission notice appear in all copies of the * software, derivative works or modified versions, and any portions * thereof, and that both notices appear in supporting documentation. * * CARNEGIE MELLON AND HELSINKI UNIVERSITY OF TECHNOLOGY ALLOW FREE USE * OF THIS SOFTWARE IN ITS "AS IS" CONDITION. CARNEGIE MELLON AND * HELSINKI UNIVERSITY OF TECHNOLOGY DISCLAIM ANY LIABILITY OF ANY KIND * FOR ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE. * * Carnegie Mellon requests users of this software to return to * * Software Distribution Coordinator or Software.Distribution@CS.CMU.EDU * School of Computer Science * Carnegie Mellon University * Pittsburgh PA 15213-3890 * * any improvements or extensions that they make and grant Carnegie Mellon * the rights to redistribute these changes. */