INSTALLATION NOTES for NetBSD/pmax 1.3.3 Be sure to read _ALL_ of this document before you try to install NetBSD/pmax. What is NetBSD? ---- -- ------ The NetBSD Operating System is a fully functional UN*X-like system derived from the Berkeley Networking Release 2 (Net/2), 4.4BSD-Lite, and 4.4BSD-Lite2 sources. NetBSD runs on many architectures and is being ported to more. NetBSD is a creation of the members of the Internet community. Without the unique cooperation and coordination the net makes possible, it's likely that this release wouldn't have come about. The NetBSD 1.3.3 release is a security and bug fix update for the NetBSD 1.3 release. The NetBSD 1.3 release was a landmark. Building upon the successful NetBSD 1.2 release, we have provided numerous and significant functional enhancements, including support for many new devices, integration of many bug fixes, new and updated kernel subsystems, and many userland enhancements. The results of these improvements is a stable operating system fit for production use that rivals most commercially available systems. It is impossible to summarize the 18 months of development that went into the NetBSD 1.3 release. Some of the significant changes include: Support for machine independent device drivers has been radically improved with the addition of the "bus.h" interface, providing a high quality abstraction for machine and architecture independent device access. The bus_dma interface has also been integrated, providing a machine-independent abstraction for DMA mapping. This permits many good things, including (among many) clean multi-platform bounce buffer support. Framework support for ISA "Plug and Play" has been added, as well as support for numerous "Plug and Play" devices. APM support has been added to NetBSD/i386. An initial cut of multi-platform PCMCIA support has been added. Support for ATAPI devices (initially just ATAPI CD-ROM drives) has been added. Support for Sun 3/80s (sun3x architecture) has been added. Support for R4000 DECstations has been added. Integration/merger of 4.4BSD Lite-2 sources into userland programs has nearly been completed. Most of userland now compiles with high levels of gcc warnings turned on, which has lead to the discovery and elimination of many bugs. The i386 boot blocks have been completely replaced with a new, libsa based two stage boot system. This has permitted integration of compressed boot support (see below). Many ports now support booting of compressed kernels, and feature new "Single Floppy" install systems that boot compressed install kernels and ramdisks. We intend to do substantial work on improving ease of installation in the future. "ypserv" has been added, thus completing our support for the "yp" network information system suite. Support for the Linux "ext2fs" filesystem and for FAT32 "msdosfs" filesystems has been added. TCP now has a SYN "compressed state engine" which provides increased robustness under high levels of received SYNs (as in the case of "SYN flood" attacks.) (Much of this code was derived from sources provided by BSDI.) An initial implementation of Path MTU discovery has been integrated (though it is not turned on by default). An initial kernel based random number generator pseudodevice has been added. Several major fixes have been integrated for the VM subsystem, including the fix of a notorious VM leak, improved synchronization between mmap()ed and open()ed files, and massively improved performance in low real memory conditions. A new swap subsystem has radically improved configuration and management of swap devices and adds swapping to files. Userland ntp support, including xntpd, has been integrated. The audio subsystems have been substantially debugged and improved, and now offer substantial emulation of the OSS audio interface, thus providing the ability to cleanly run emulated Linux and FreeBSD versions of sound intensive programs. A "packages" system has been adapted from FreeBSD and will provide binary package installations for third party applications. The XFree86 X source tree has been made a supported part of the NetBSD distribution, and X servers (if built for this port), libraries and utilities are now shipped with our releases. The ftp(1) program has been made astoundingly overfunctional. It supports command line editing, tab completion, status bars, automatic download of URLs specified on the command line, firewall support and many other features. All ports now use "new" config. Old config has been laid to rest. The ARP subsystem and API has been rewritten to make it less ethernet-centric. A new if_media subsystem has been added which allows network interfaces to be configured using media type names rather than device-specific mode bits. Many kernel interface manual pages have been added to manual section 9. Several ports support much more hardware. Many updates to bring NetBSD closer to standards compliance. Most third party packages have been updated to the latest stable release. As has been noted, there have also been innumerable bug fixes. Kernel interfaces have continued to be refined, and more subsystems and device drivers are shared among the different ports. You can look for this trend to continue. NetBSD 1.3 also includes some refinement to the NetBSD binary emulation system (which includes FreeBSD, HP-UX, iBCS2, Linux, OSF/1, SunOS, SVR4, Solaris and Ultrix compatibility), bringing NetBSD closer to the goal of making the emulation as accurate as possible. In the near future, we hope to integrate a fully rewritten Virtual Memory subsystem, kernel threads, and SMP support. This is the third public release of NetBSD for the DECstation and DECsystem family of computers. This release includes support for either mips1 (r2000, r3000) and mips3 (r4000, r4400, r4600) CPUs. mips1 and mips3 support can be configured into a single kernel. NetBSD 1.3 can be installed onto DECstation 5000/50, 5000/150, 5000/260, or 5900 models, as well as all previously-supported hardware. Though stable NetBSD/pmax snapshots with shared-library support have been available for over a year, this is the first full NetBSD/pmax release to ship with ELF shared libraries. Much of the user-space support for this is due to work by Per Fogelstrom (pefo@OpenBSD.ORG) and ported to NetBSD by Manuel Bouyer. Ultrix emulation for Internet applications is improved over NetBSD 1.2. The Ultrix `ifconfig' command and multicast applications now work in Ultrix compatibility mode. A ecoff-format NetBSD kernel in an Ultrix root filesystem should boot multi-user, though this is not recommended as an installation method. A bug in 1 interrupt handling from 4.4BSD, which could cause `remrunque' panics under heavy load in both NetBSD prior to 1.2E and OpenBSD, is fixed in this release. There are yet more enhancements for the 4.4bsd-Lite/pmax SCSI drivers, which now correctly probes newer, faster, SCSI-2 disks, and handles large transfers (up to 64K) on 3100s. Intermediate copies of disk I/O on IOASIC-based machines are eliminated, yielding a modest improvement on old disks like the rz25, and a bigger improvement on faster disks. Kernel performance tuning includes lower system call overhead, a faster bcopy() routine, faster IP checksumming code, and other imrprovemnts. These combine to show a dramatic (e.g., 1.5x-2.5x) improvement on microbenchmarks like the lmbench suite, and a modest improvement on larger benchmarks like kernel builds. The Future of NetBSD: --- ------ -- ------ The NetBSD Foundation has been incorporated as a non-profit organization. Its 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. 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 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: ------- -- ------ NetBSD Mirror Site List The following sites mirror NetBSD as of December 01, 1998. If you wish to become a distribution site for NetBSD, contact mirrors@netbsd.org. FTP mirrors ----------- Australia * ftp.au.netbsd.org RMIT University, Melbourne ftp://ftp.au.netbsd.org/pub/NetBSD * ftp2.au.netbsd.org University of Queensland, Brisbane ftp://ftp2.au.netbsd.org/pub/NetBSD Austria * ftp.at.netbsd.org University of Technology, Vienna ftp://ftp.at.netbsd.org/pub/NetBSD Brazil * ftp.ravel.ufrj.br Cidade Universitaria ftp://ftp.ravel.ufrj.br/pub/NetBSD Denmark * ftp.dk.netbsd.org Aalborg University ftp://ftp.dk.netbsd.org/pub/NetBSD Finland * ftp.fi.netbsd.org The Finnish University and Research Network, Espoo ftp://ftp.fi.netbsd.org/pub/NetBSD France * ftp.fr.netbsd.org Paris University ftp://ftp.fr.netbsd.org/pub/NetBSD Germany * ftp.de.netbsd.org University of Trier ftp://ftp.de.netbsd.org/pub/NetBSD * ftp2.de.netbsd.org University of Erlangen-Nuremberg ftp://ftp2.de.netbsd.org/pub/NetBSD * ftp.uni-regensburg.de University of Regensburg ftp://ftp.uni-regensburg.de/pub/comp/os/NetBSD Japan * ftp.jp.netbsd.org Internet Research Institute Inc., Tokyo ftp://ftp.jp.netbsd.org/pub/NetBSD * ftp.dti.ad.jp ftp://ftp.dti.ad.jp/pub/NetBSD/ * mirror.nucba.ac.jp Nagoya University of Commerce and Business ftp://mirror.nucba.ac.jp/mirror/NetBSD * netbsd.tohoku.ac.jp Tohoku University ftp://netbsd.tohoku.ac.jp/NetBSD Korea * sunsite.kren.ne.kr Seoul National University ftp://sunsite.kren.ne.kr/pub/OS/NetBSD Netherlands * ftp.nl.netbsd.org University of Amsterdam ftp://ftp.nl.netbsd.org/pub/NetBSD Norway * ftp.no.netbsd.org ftp://ftp.no.netbsd.org/pub/NetBSD * ftp.ntnu.no Norwegian University of Science and Technology ftp://ftp.ntnu.no/pub/NetBSD * skarven.itea.ntnu.no Norwegian University of Science and Technology ftp://skarven.itea.ntnu.no/pub/NetBSD Russia * ftp.ru.netbsd.org Landau Institute for Theoretical Physics, Chernogolovka ftp://ftp.ru.netbsd.org/pub/NetBSD Sweden * ftp.stacken.kth.se Royal Institute of Technology, Stockholm ftp://ftp.stacken.kth.se/pub/OS/NetBSD * ftp.sunet.se Swedish University NETwork, Uppsala ftp://ftp.sunet.se/pub/os/NetBSD UK * ftp.uk.netbsd.org Domino, London ftp://ftp.uk.netbsd.org/pub/NetBSD * sunsite.org.uk ftp://sunsite.org.uk/packages/netbsd USA * ftp.netbsd.org Silicon Valley, California ftp://ftp.netbsd.org/pub/NetBSD * ftp.cs.umn.edu University of Minnesota ftp://ftp.cs.umn.edu/pub/NetBSD * ftp.eecs.umich.edu University of Michigan, Ann Arbor ftp://ftp.eecs.umich.edu/pub/NetBSD * ftp.iastate.edu Iowa State University ftp://ftp.iastate.edu/pub/netbsd * ftp.op.net ftp://ftp.op.net/pub/NetBSD AFS mirrors ----------- Sweden * ftp.stacken.kth.se Royal Institute of Technology, Stockholm AFS path: /afs/stacken.kth.se/ftp/pub/OS/NetBSD USA * ftp.iastate.edu Iowa State University AFS path: /afs/iastate.edu/public/ftp/pub/netbsd NFS mirrors ----------- UK * sunsite.org.uk Instructions: mount -o ro sunsite.org.uk:/public/packages/netbsd /mnt SUP mirrors ----------- Australia * sup.au.netbsd.org RMIT University, Melbourne Instructions: ftp://sup.au.netbsd.org/pub/NetBSD/sup/README.sup France * sup.fr.netbsd.org Paris University Instructions: Similar to sup.netbsd.org Germany * sup.de.netbsd.org University of Trier Instructions: ftp://sup.de.netbsd.org/pub/NetBSD/sup/supfile.example * sup.owl.de Instructions: ftp://sup.owl.de/pub/sup/supfile.example Japan * sup.jp.netbsd.org Internet Research Institute Inc., Tokyo Instructions: ftp://sup.jp.netbsd.org/pub/NetBSD/sup/README.sup Norway * skarven.itea.ntnu.no Norwegian University of Science and Technology Instructions: Use this line as your sup file to get /usr/README.supinfo- skarven:current release=supinfo host=skarven.itea.ntnu.no use-rel-suffix backup delete old base=/usr prefix=/usr hostbase=/supmirror UK * sup.uk.netbsd.org Domino, London Instructions: See ftp://ftp.netbsd.org/pub/NetBSD/sup/README.sup USA * sup.netbsd.org Silicon Valley, California Instructions: See ftp://ftp.netbsd.org/pub/NetBSD/sup/README.sup * ftp.cs.umn.edu University of Minnesota Instructions: hostbase=/ftp/ftp/packages/NetBSD, collections are the same as on sup.NetBSD.ORG WWW mirrors ----------- Australia * www.au.netbsd.org RMIT University, Melbourne http://www.au.netbsd.org/ Austria * www.at.netbsd.org University of Technology, Vienna http://www.at.netbsd.org/ Finland * www.fi.netbsd.org Global Wire Oy, Lappeenranta http://www.fi.netbsd.org/ France * www.fr.netbsd.org Paris University http://www.fr.netbsd.org/ Germany * www.de.netbsd.org http://www.de.netbsd.org/ Japan * www.jp.netbsd.org Internet Research Institute Inc., Tokyo http://www.jp.netbsd.org/ Norway * www.no.netbsd.org http://www.no.netbsd.org/ USA * www.netbsd.org Western Washington State University http://www.netbsd.org/ * www2.us.netbsd.org New York http://www.us.netbsd.org/ NetBSD 1.3.3 Release Contents: ------ ----- ------- -------- The NetBSD 1.3.3 release is organized in the following way: .../NetBSD-1.3.3/ 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.3.3 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 for which NetBSD 1.3.3 has a binary distribution. There are also 'README.export-control' files sprinkled liberally throughout the distribution tree, which point out that there are some portions of the distribution (i.e. the `domestic' portion) that may be subject to export regulations of the United States. It is your responsibility to determine whether or not it is legal for you to export these portions and to act accordingly. 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: secrsrc.tgz: This set contains the "domestic" sources. These sources may be subject to United States export regulations. [ 412K gzipped, 1.8M uncompressed ] gnusrc.tgz: This set contains the "gnu" sources, including the source for the compiler, assembler, groff, and the other GNU utilities in the binary distribution sets. [ 15.6M gzipped, 66.4M uncompressed ] syssrc.tgz: This set contains the sources to the NetBSD 1.3.3 kernel, config(8), and dbsym(8). [ 10.7M gzipped, 50.0M uncompressed ] sharesrc.tgz: 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.9M gzipped, 11.1M uncompressed ] src.tgz: This set contains all of the NetBSD 1.3.3 sources which are not mentioned above. [ 13.9M gzipped, 60.7M 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. Most of the above source sets are located in the source/sets subdirectory of the distribution tree. The secrsrc.tgz set is contained in the source/security subdirectory. This set, which is available only to users in the United States and Canada, contains the sources normally found in /usr/src/domestic -- primarily kerberos and other cryptographic security related software. (Remember, because of United States law, it may not be legal to distribute this set to locations outside of the United States and Canada.) The source sets are distributed as compressed tar files. They may be unpacked into /usr/src with the command: cat set_name.tgz | gunzip | (cd /; tar xpf - ) The sets/Split/ and security/Split/ subdirectories contain split versions of the source sets for those users who need to load the source sets from floppy or otherwise need a split distribution. The split sets are are 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.) The split distributions may be reassembled and extracted with "cat" as follows: cat set_name.?? | gunzip | (cd /; tar xpf - ) 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. Checksums based on other algorithms may also be present -- see the release(7) man page for details. The pmax-specific portion of the NetBSD 1.3.3 release is found in the "pmax" subdirectory of the distribution. That subdirectory is laid out as follows: .../NetBSD-1.3.3/pmax/ binary/ pmax binary distribution sets and kernel images; see below. installation/ installation materials: disk images of a complete root filesystem, for both network and diskful installation; see below. misc/ miscellaneous binaries including a copy of the sysinst instalation tool. The NetBSD/pmax binary distribution sets contain the binaries which comprise the NetBSD 1.3.3 release for the pmax. There are eight binary distribution sets, plus optional X11 sets. The binary distribution sets can be found in the "pmax/binary/sets" subdirectory of the NetBSD 1.3.3 distribution tree, and are as follows: base The NetBSD/pmax 1.3.3 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 does NOT include shared library support, and excludes everything described below. [ 11.6M gzipped ] comp The NetBSD/pmax Compiler tools. All of the tools relating to C and C++. This set includes the system include files (/usr/include), the linker, the compiler tool chain, and the various system libraries (except the shared libraries, which are included as part of the base set). This set also includes the manual pages for all of the utilities it contains, as well as the system call and library manual pages. [ 10.9M gzipped ] etc 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.) [ 53K gzipped ] games This set includes the games and their manual pages. [ 3.0M gzipped ] kern This set is a placeholder for bootable kernels. man 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. [ 2.6M gzipped ] misc 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, 8.3M uncompressed ] text This set includes NetBSD's text processing tools, including groff, all related programs, and their manual pages. [ 1.1M gzipped, 3.7M uncompressed ] The pmax security distribution set is named "secr" and can be found in the "pmax/binary/security" subdirectory of the NetBSD 1.3.3 distribution tree. It contains security related binaries which depend on cryptographic source code. You do not need this distribution set to use encrypted passwords in your password file; the "base" distribution includes a crypt library which can perform only the decryption function. The security distribution includes a version of the Kerberos IV network security system, and a Kerberized version of the "telnet" program. The "secr" distribution set can be found only on those sites which carry the complete NetBSD distribution and which can legally obtain it. (Remember, because of United States law, it may not be legal to distribute this set to locations outside of the United States and Canada.) At the time of release, the pmax distribution set does not include a security distribution. A binary will be built shortly after the release by a US permanent resident. In the meantime, if you are in the US or Canada 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 Since NetBSD 1.3, binary sets for the X Window system are also distributed with each NetBSD release. The binaries are based on X11R6.3 and can be installed using the 'sysinst' utility. xbase The basic files needed for a complete X client environment. This does not include the X servers. [ 3.25M gzipped ] xcomp The extra libraries and include files needed to compile X source code. [ 2.1M gzipped, 7.3M uncompressed ] xcontrib Programs that were contributed to X. [ 216 gzipped ] xfont Fonts needed by X. [ 5.8M gzipped, 7M uncompressed ] xserver X servers built from X11R5, supporting the 4.3bsd-derived Xserver/framebuffer protocol used in NetBSD/pmax. See the /usr/X11R6/bin/README.pmax file in this set for more information on conifguring the X11 R5 servers to work with X11R6 clients and with compressed fonts. [ 712k gzipped, 2.4 unzipped ] The pmax binary distribution sets are distributed as gzipped tar files. Each pmax binary distribution set also has its own "CKSUMS" file, just as the source distribution sets do. The initial installation of NetBSD 1.3.3 on a Decstation not already running NetBSD 1.3.3 is supported by the following files, which are included in the `./installation' subdirectory: diskimage/diskimage.gz A gzipped copy of a full root filesystem. When unzipped, this is suitable for dd'ing onto a raw disk partition. netboot/diskimage.tar.gz A gzipped copy of a tar file containing the same files as diskimage.gz. When unzipped, this is suitable for setting up an NFS server for diskless boot or installing via netboot. Distribution kernel images (e.g., for installalling on Ultrix) are also available separately in the ./binary/kernel subdirectory: netbsd.aout An a.out-format generic kernel, bootable on an existing NetBSD system. netbsd.ecoff An ECOFF-format kernel, suitable for diskless boot via TFTP or for upgrading from Ultrix. nfsnetbsd.ecoff An minimal ECOFF-format kernel, minimized to boot on bugggy PROMs that cannot boot kernels larger than ~1 Mbyte. The instructions given for extracting the source sets work equally well for the binary sets, but it is worth noting that if you use that method, the files are extracted "below" the current directory. That is, if you want to extract the binaries "into" your system, i.e. replace the system binaries with them, you have to run the "tar xvfp" from /. Also note that if you upgrade or install this way, those programs that you are using at the time will NOT be replaced. If you follow the normal installation or upgrade procedures, this will be taken care of for you. NetBSD System Requirements and Supported Devices: ------ ------ ------------ --- --------- ------- NetBSD/pmax 1.3.3 runs on the following classes of machines: - Decstation 2100 and 3100, also known as "pmin" and "pmax" - Personal Decstations (5000/20, and /25) also known as "MAXINE" - Decstation 5000/120, /125, and /133, also known as "3MIN" - Decstation 5000/200, also known as "3MAX" - Decstation 5000/240, als known as "3MAXPLUS" - Decstation 5000/50, 5000/150 and 5000/260 - R4000 and R4400 variants of the the MAXINE, 3MIN and 3MAXPLUS NetBSD/pmax 1.3.3 does *not* (yet) run on these machines: - Decstation 5100 (an r3000-based cousin of the Decstation 3100) - Decsystem 5400 and 5500 (Qbus-based systems, similar to a Vax 'Mayfair' and 'Mayfair II', but with an r2000a or r3000 cpu instead of a CVAX cpu.) - Decsystem 5800 (xbi-based multiprocessor, a Vax 6200 with Vax CPU boards replaced with Mips cpu boards) The minimal configuration requires 8M of RAM and ~60M of disk space. To install the entire system requires much more disk space, and to run X or compile the system, more RAM is recommended. (NetBSD with 8M of RAM feels like Ultrix with 8M of RAM.) Note that until you have around 16M of RAM, getting more RAM is more important than getting a faster CPU. Supported devices include: Decstation 2100 and 3100 baseboard video: pm one-bit mono or 8-bit pseudocolour fraem buffers. Decstation 5000 series TurboChannel video: PMAG-DV Personal Decstation baseboard 1024x768 frame buffer. PMAG-BA 1024x768 8-bit colour frame buffer. PMAGB-BA 1024x768 8-bit colour frame buffer. PMAG-AA 1280x1024 four-bit greyscale frame buffer. NOTE: All supported DECstation video produces sync-on-green. Be sure to use either a DEC-compatible fixed-sync monitor or a multisync monitor that supports sync-on-green. serial ports: ttya and ttyb (can be used as console if needed) ethernet: on-board AMD Lance ethernet ("le0"), TURBOchannel AMD Lance ethernet cards (the "PMAD"). SCSI: on-board DEC "sii" SCSI controller (2100 and 3100) on-board "asc" SCSI controller (5000 series machines) TurboChannel "asc" SCSI controller (the "PMAZ"). DEC (LK-201 or compatible) keyboard DEC ("hockey puck" or compatible) mouse. Hardware the we do NOT currently support, but get questions about from time to time: Q-bus Decsystem machines Decstation 5100 machines PrestoServe NVRAM on Decstation 5100 and 5000/2xx machines audio drivers for Personal Decstation machines floppy driver for Personal Decstation machines TurboChannel audio hardware (LoFi) PMAG-C 2-D accelerated framebuffers with onboard i860 processors NOTE: the primary obstacle to support of all but the very last item is non-availability of sample hardware for development. The primary obstacle for the i860-based framebuffers is that there is no documentation on the accelerator board. Getting the NetBSD System on to Useful Media: ------- --- ------ ------ -- -- ------ ----- First-time installation on a bare machine is not supported, because most DECstations do not have any suitable load device. Some versions of DECstation PROMs are buggy and will not boot via TFTP/bootp; still other versions are buggy and do not boot via MOP. The only DECstation with a floppy-disk drive is the Personal Decstation, and that device is not supported as a boot device. The recommended installation procedure is to boot a miniroot via TFTP, or to use a "helper" system to write a miniroot onto a disk, move that disk to the target installation system, and then boot the miniroot. Once the miniroot is booted, a disklabel should be written. At that point, Installation is supported from several media types, including: NFS partitions FTP Tape CD-ROM The steps necessary to prepare the distribution sets for installation depend on which method of installation you choose. The various methods are explained below. To prepare for installing via an NFS partition: Place the NetBSD software you wish to install into a directory on an NFS server, and make that directory mountable by the machine which you will be installing NetBSD on. This will probably require modifying the /etc/exports file of the NFS server, and resetting mountd. Both these actions will require superuser privileges on the NFS server. Note the numeric IP address of the NFS server. If the NFS server is not on a network which is directly attached to the NetBSD machine, you must also note the numeric address of the router closest to the the new NetBSD machine. If you are using a diskless setup to install NetBSD on your machine, you can take advantage of the fact that the above has already been done on your machine's server. So, you can conveniently put the NetBSD filesets in your machine's root filesystem on the server where the install program can find them. Once you have done this, you can proceed to the next step in the installation process, preparing your system for NetBSD installation. To prepare for installing via FTP: NOTE: this method of installation is recommended only for those already familiar with using the BSD network-manipulation commands and interfaces. If you aren't, this documentation should help, but is not intended to be all-encompassing. The preparations for this method of installation are easy: all you have to do is make sure that there's some FTP site from which you can retrieve the NetBSD installation when it's time to do the install. You should know the numeric IP address of that site, the numeric IP address of your nearest router if one is necessary Once you have done this, you can proceed to the next step in the installation process, preparing your system for NetBSD installation. To prepare for installing via a tape: To install NetBSD from a tape, you need to somehow get the NetBSD filesets you wish to install on your system on to the appropriate kind of tape, in tar format. NOTE: the tape devices with which NetBSD/pmax is believed to work is the DEC TK-50. This is a very slow device. Installation via disk or network is recommended if at all possible. If you're making the tape on a UN*X system, the easiest way to do so is: tar cvf where "" is the name of the tape device that describes the tape drive you're using (possibly something like /dev/nrst0, but we make no guarantees 8-). Under SunOS 5.x, this would be something like /dev/rmt/0mbn. Again, your mileage may vary. If you can't figure it out, ask your system administrator. "" are the names of the "set_name.nnn" files which you want to be placed on the tape. Once you have done this, you can proceed to the next step in the installation process, preparing your system for NetBSD installation. Preparing your System for NetBSD Installation: --------- ---- ------ --- ------ ------------ Installing NetBSD/pmax using the sysinst tool and an image of a full bootable root filesystem is now a relatively painless process. The diskimage is avaiable via (either a diskimage, dd'able to a raw disk or tarfile to for NFS . From most convenient to least convenient, the installation methods are: 1. Booting as a diskless workstation via Ethernet, followed by initialization of the local disk and installing onto the local disk over NFS. 2. Copying a bootable diskimage onto the beginning of a disk and installing onto that disk 3. installation using a helper machine to set up a bootable NetBSD/pmax root filesystem, and moving the disk to the target. 4. Installation from Ultrix or other OSes by putting a copy of the diskimage into the existing swap partition and a copy of the NetBSD kernel into your Ultrix root filesystem. Before you start, you must choose an installation method. If you have an Ethernet connection to an NFS server that can provide even ~30M for a diskless-root filesystem, then installation via the net is best. Next best, if your DECstation is already running Ultrix and has two disk drives (or one, if you live dangerously), is to copy a diskimage onto one drive. Finally, you can install by using a second machine as a helper to prepare a bootable NetBSD/pmax disk. If your target is going to run diskless, then installation proceeds as for method 1. This release of NetBSD/pmax uses the new sysinst installation utility. You should examine the guide on the NetBSD/pmax web site, which has more complete and more up-to-date instructions for sysinst. The following is a brief synopsis which has been successfully followed by both first-time NetBSD/pmax installers and to upgrade existing gsystems. You should familiarize yourself with the console PROM environment and the hardware configuration. The PROMs on the older Decstation 2100 and 3100 use one syntax. The PROMs on the TurboChannel machines use a completely different syntax. Be sure you know how to print the configuration of your machine, and how to boot from disk or network, as appropriate. On the 2100/3100, that's boot -f rz(0,N,0)netbsd (boot from rzN) boot -f tftp() (boot diskless via TFTP) boot -f tftp() (boot via MOP from an Ultrix server) On the 5000/200, the equivalent is boot 5/rzN/netbsd boot 6/tftp boot 6/mop and on other 5000 series machines, boot 3/rzN/netbsd boot 3/tftp boot 3/mop You will also need to know the total size (in sectors) and the approximate geometry of the disks you are installing onto, so that you can label your disks for the BSD fast filesystem (FFS). For most SCSI drives (including all SCSI-2 drives), the kernel will correctly detect the disk geometry. The sysinst tool will suggest these as the default. If you're installing NetBSD/pmax for the first time it's a very good idea to pre-plan partition sizes for the disks on which you're installing NetBSD. Changing the size of partitions after you've installed is difficult. If you do not have a spare bootable disk, it may be simpler to re-install NetBSD again from scratch. If you install by copying a disk image, and you want to change the size of the root partition from the default 32Mbytes, you will need a second `scratch' disk. You should copy the diskimage onto the `scratch' disk, boot the scratch disk, and use it to create a tailored root filesystem. This is because you cannot change the size of an active partition (i.e., the root filesysem you booted). The standard trick to get around this is to put a cut-down miniroot into the swap partition, boot the miniroot, and use that system to change the root filesystem size. DECstation PROMs don't reliably support booting off partitions other than the 'a' partition, which is why you need two disks to tailor the root filesystem size. Assuming a classic partition scheme with separate root (`/') and /usr filesystems, a comfortable size for the NetBSD root filesystem partition is about 32M. A good initial size for the swap partition is twice the amount of physical memory in your machine (though, unlike Ultrix, there are no restrictions on the size of the swap partition that would render part of your memory unusable). The default swap size is 64Mbytes, which is adequate for doing a full system build. A full binary installation, with X11R6.3, takes about 150MB in `/usr'. Installing the NetBSD System: ---------- --- ------ ------ Reminder: Always back up files before installing or upgrading. If installing from source, always install and boot a new kernel before installing a new userland! If at all possible, you should consult the ``Installation Guide'' document on the NetBSD/pmax web page, at http://www.netbsd.org/Ports/pmax. It has not been possible to reproduce the pmax installation Web page in fixed-font hardcopy format for the 1.3.3 release. You must either visit the URL above, or request a rendered version (e.g., PostScript). Please check the NetBSD/pmax 1.3.3 installation instructions at http://www.netbsd.org/Ports/pmax/pmax-install.html now, and return to this document when you used those instructions to install a diskimage, and used sysinst to label a disk and extract the NetBSD/pmax 1.3.3 installation tar sets. Install via the NetBSD CDROM. ----------------------------- You can obtain the disk image or diskless boot tar file from the NetBSD 1.3.3 CDROM. To mount the CDROM from a NetBSD/pmax host, type mount -r -t cd9660 /dev/rzXc /mnt and from an Ultrix host mount -r -t cdfs -o nodefperm,noversion /dev/rzXc /mnt where X is the SCSI id of the CDROM. ** NOTE: Ultrix does not have Rock Ridge extensions so leave out everything between the first and last . in the paths on the CD. For example, the path NetBSD-1.3.2 would show up as NetBSD-1.2. The diskimage file can be found on the CDROM at the following location (relative to the mount point of the CD) NetBSD-1.3.3/pmax/installation/diskimage/diskimage.gz and the diskless boot tar file can be found at NetBSD-1.3.3/pmax/installation/netboot/diskimage.tgz Once you have located these files, continue on to either the "Install via diskless boot", "Install via diskimage" or "Installing from Ultrix" section later in the INSTALL notes. Install via diskless boot. -------------------------- The preferred path is to upgrade or install by diskless-booting a minimal system via NFS, and using that to upgrade or install. The file installation/netboot/diskimage.tar.gz contains a suitable set of files. (it is a tar copy of the contents of a root filesystem diskimage) . You will need to find an NFS server, unpack the tarfile, and setup BOOTP/dhcp service for your pmax. Complete instructions are in the installation notes or the pmax web page. Since the system install utility, sysinst, requires a read/write root, netbooting is only feasible if your NFS server exports the diskless root read-write. If this is not possible, you should install via diskimage. Install via diskimage. ---------------------- If netbooting with a _writable_ NFS root is not possible, the recommended installation is to unpack and copy a diskimage onto the raw partition of a disk. The diskimage file is in installation/diskimage/diskimage.gz is shipped compressed and is around 8020 kBytes; it uncompresses to exactly 32Mbytes. To install the diskimage onto disk rzX on a NetBSD/pmax system, do: disklabel -W /dev/rrzXc gunzip -c diskimage.gz | dd of=/dev/rrzXc bs=10240 When installing on a disk with not NetBSD or Ultrix label, you may get a message like: rzX: WARNING: trying Ultrix label, no disk label or when installing on an old Ultrix disk, you may get a message like: rzX: WARNING: using ULTRIX partition information when issuing the "disklabel -W /dev/rrzXc" command. This can safely be ignored. Most other NetBSD ports are similar, but use rsdXc instead of rrzXc. On NetBSD/i386, the `raw disk partition' is the 'd' parttion, so do: disklabel -W /dev/rsdXd gunzip -c diskimage.gz | dd of=/dev/rsdXd bs=10240 On NetBSD, be sure to use disklabel -W to enable writing to the label area of the disk. If you forget this and/or use the `block' device, the dd command will silently fail. On MS-DOS, use an unzip utlility, then use rawrite. Then boot using, e.g, >> boot -f rz(0,X,0)netbsd # 3100 >> boot 5/rzX/netbsd # 5000/200 >> boot 3/rzX/netbsd # other machines (NOTE: replace the X with the unit number of your disk: boot 3/rz2/netbsd to boot drive 2 on a 5000/xxx.) then continue from ``Once you've booted the diskimage''. Installing from Ultrix ---------------------- The Ultrix bootloader can boot ECOFF-format NetBSD kernels. So the technique of dd'ing a disk image into swap, copying a kernel to the root, and then booting via the "n" argument should work with Ultrix too. Since Ultrix cannot mount 4.4BSD format FFS filesystems, just dd the diskimage into your swap partition, copy a netbsd.ecoff kernel from the FTP site, and proceed from step #5 of the `Upgrade via diskimage' above. You should do this from single-user mode, to ensure that swapping is not enabled when you copy the diskimage into the swap partition. On Ultrix, use the "chpt -q /dev/rz?c" command to be sure your swap partition (typically "b") is big enough to hold the diskimage (32Mbytes or more). Again, be sure to specify the partition where you dd'ed the NetBSD diskimage as your root device in step #7! Details of dd'ing a disk image into the swap partition are covered in the "QUICK.INSTALL" file, which should be in the same directory where these install notes are located. Once you've booted the diskimage -------------------------------- Once you'e booted a diskimage and pointed the kernel at the approriate devices to use for root, and dump, NetBSD kernel will prompt you for a single-user shell; Enter pathname of shell or RETURN for sh: At this point, press the RETURN key. NOTE: If you see the message: WARNING: clock gained 365 days -- CHECK AND RESET THE DATE! you will need to manually set the clock back to the current date with the `date' command. The argument to the `date' command is one string with the format of "YYMMDDhhmm". For example, to set the date to November 30th, 1998 at 11:34pm, type date 9811302334 This problem will be fixed in NetBSD 1.4 When you get a standalone root prompt, set your terminal type TERM=pmax; export TERM; for a framebuffer console, or TERM=vt100; export TERM if using a serial console with a vt100-compatible terminal. Next, you need to ensure that the root filesystem is writable so that sysinst can create temporary files, temporary disklabels, etc. If you booted via NFS, the diskless root should already be writable. If you booted from disk, type mount /dev/rzXY / where X is the disk unit you booted from, and Y is either a or b, (e.g., use /dev/rz2a for drive 2 with diskimage in the 'a' partition, and rz2b for diskimage in swap.) CD-ROM INSTALLATION NOTE: If you are installing from a CD-ROM, sysinst will offer you a default choice of "cd0" for the CD-ROM device. Unlike other NetBSD ports, NetBSD/pmax currently uses the same device driver for both hard disks and CD-ROMs. You will need to specify "rzX" (where X is the SCSI id of the CD-ROM) as the CD-ROM device. Also note that sysinst doesn't expect a partition - just the base device. If you still have problems, you can try issuing the following command before starting sysinst mount -r -t cd9660 /dev/rzXc /mnt2 where X is the SCSI id of the CD-ROM. You can then ignore any errors trying to mount the CD-ROM from within sysinst. Then, start sysinst sysinst Then, choose 'install' or 'upgrade'. When you've finished the install/upgrade, be sure to edit /etc/rc.conf and set "rc_configured" to YES when you are done. If you're doing an upgrade, merge your old etc from /etc.old into /etc. You're then ready to reboot! Post-intallation notes: ---------------------- Some of the files in the NetBSD 1.3.3 distribution might need to be tailored for your site. In particular, the /etc/sendmail.cf file will almost definitely need to be adjusted, and other files in /etc will probably need to be modified. If you are unfamiliar with UN*X-like system administration, it's recommended that you buy a book that discusses it. NetBSD/pmax 1.3 uses an X11R5 X server. These servers cannot read the compressed fonts which are shipped with standard X11R6 configurations. If you installed X11 and want to run a local Xserver, you must take post-installation steps to make the X11R5 server work that are standard for X11R6.3. The distribution file /usr/X11R6/bin/README.pmax contains information on how to choose an Xserver and how to access compressed fonts via a font server or to decompress the X fonts after installation. Please follow the directions there. Upgrading a previously-installed NetBSD System: --------- - ---------- --------- ------ ------ The preferred upgrade path is to set up a diskless-boot host, unpack and boot boot 1.3 diskimage as for a network installation, and to use the sysinst tool to upgrade your system. Please see the `Installation' section for further information. Upgrade via diskimage. ---------------------- If you cannot netboot, the recommended path is to upgrade by booting a diskimage from your swap partition. Pmaxes cannot boot out out of anything but the 'a' partition. However, you *can* boot an upgrade kernel off your 'a' partition and tell that kernel to use your 'b' partition as its root. The steps to do this (after you've fetched the diskimage) with a current root of rzX are: 1) boot single-user from your current root, rzX. Be *sure* not to start swapping: >> boot -f rz(0,X,0)netbsd -s # 3100 >> boot 5/rzX/netbsd -s # 5000/200 >> boot 3/rzX/netbsd -s # others (NOTE: replace the X with the unit number of your disk: boot 3/rz2/netbsd to boot drive 2 on a 5000/xxx.) 2) When you get a single-user prompt, remount the root filesystem read-write. (You wil need to update the kernel soon.) # mount / Then mount the filesystem with the diskimage, and uncompress and dd the diskimage into swap (b) partition. You will also need /usr mounted to run gunzip: # mount /usr # gunzip -c diskimage.gz | dd bs=10240 of=/dev/rrzXb 3) Mount swap (b) partition readonly on /mnt: # mount -r -t ffs /dev/rzXb /mnt 4) Copy the kernel from the B partition to your root: cp -p /mnt/netbsd /netbsd-1.3 (this is important; you want the kernel in / and swap to be a release kernel, or the release binaries will not work.) 5) halt: # halt 6) Reboot with an argument of "n", telling the kernel to ask what device to use as root: >> boot -f rz(0,X,0)netbsd-1.3 n # 3100 >> boot 5/rzX/netbsd-1.3 n # 5000/200 >> boot 3/rzX/netbsd-1.3 n # others (NOTE: the n after the kernel name is a literal "n", not the disk unit number or partition. It is an argument telling the kernel to ask for a root device. NOTE: replace the X with the unit number of your disk: boot 3/rz2/netbsd to boot drive 2 on a 5000/xxx.) 7) The "n" argument tells the kernel to prompt you for the root device, dump device, and root fileysystem type. Enter when the kernel asks for Root device: Tell it rzXb, where X is the same disk unit as in step 6. Here's an example, again assuming drive 2 as in step 6: KN03-AA V5.2b (PC: 0x80051f1c, SP: 0xffffdeb0) >> boot 3/rz2/netbsd n boot device: rz2 root device (default rz2a): <<< enter `rz2b' >>> dump device (default rz2b): <<< enter `none' >>> file system (default generic): <<< enter `ffs' >>> root on rz2b then continue from the ``Once you've booted the diskimage'' step of the Installation instructions. Compatibility Issues With Previous NetBSD Releases: ------------- ------ ---- -------- ------ -------- Users upgrading from previous versions of NetBSD may wish to bear the following problems and compatibility issues in mind when upgrading to NetBSD 1.3.3: * Swap configuration Description: All swap partitions are now configured by the swapctl(8) program. The kernel no longer configures a "default" swap partition. Because of this, all swap partitions (even the old "default") must be listed in /etc/fstab. Many users of previous releases relied on the kernel configuring a "default" swap partition and did not list any swap space in /etc/fstab at all -- such users will now have no swap space configured unless they list swap partitions in /etc/fstab! Common symptoms of of this problem include machine crashes during builds, and similar memory intensive activities. Fix: The most common position for a swap partition is the `b' partition of the drive the root file system is on. For diskless systems, check the new swapctl(8) manual for more detail on how this is done. Example fstab entries: /dev/sd0b none swap sw,priority=0 /dev/sd1b none swap sw,priority=5 * NFS daemons and other programs in /sbin moved Description: The NFS daemons (nfsd, nfsiod, mountd) have been moved from the /sbin to the /usr/sbin directory. When new binaries are loaded over old ones during upgrade, most programs get overlaid and replaced, but unless these binaries are explicitly removed they will not disappear. The installation subsystems on some NetBSD architectures will not properly remove these binaries. Due to changes in the NFS subsystem, the old NFS daemon binaries will not work correctly, and will cause serious problems. Unfortunately, the default startup script (/etc/rc) will run the old binaries in /sbin if they are present instead of the new ones in /usr/sbin. Some other programs (dumpfs, dumplfs and quotacheck) have also been moved from /sbin to /usr/sbin, and old versions may be left behind by accident. They, too, may cause difficulties. Fix: Remove the old daemon binaries (/sbin/nfsiod, /sbin/nfsd, /sbin/mountd, etc.) after your upgrade has finished. You may wish to do an "ls -lt /sbin | more" to help determine which binaries were not replaced/removed during your upgrade. * AMANDA, The Advanced Maryland Automatic Network Disk Archiver, from http://www.amanda.org Description: Due to a change in the output of dump(8) to ensure consistency in the messages, AMANDA's dump output parser breaks. Error messages such as the following may be an indication that this problem is present: FAILURE AND STRANGE DUMP SUMMARY: hostname wd0e lev 1 FAILED [no backup size line] Versions affected: 2.3.0.4, and most likely earlier versions Workaround/Fix: One of: * Apply the patch found at: ftp://ftp.netbsd.org/pub/NetBSD/misc/patches/amanda-pre-2.4.patch * Upgrade to AMANDA 2.4.0 or newer. The side effect of this is that the network protocol is incompatible with earlier versions. Using online NetBSD documentation ----- ------ ------ ------------- Documentation is available if you first install the manual distribution set. Traditionally, the "man pages" (documentation) are denoted by 'name(section)'. Some examples of this are intro(1), man(1), apropros(1), passwd(1), and passwd(5). The section numbers group the topics into several categories, but three are of primary interest: user commands are in section 1, file formats are in section 5, and administrative information is in section 8. The 'man' command is used to view the documentation on a topic, and is started by entering 'man [section] topic'. The brackets [] around the section should not be entered, but rather indicate that the section is optional. If you don't ask for a particular section, the topic with the least-numbered section name will be displayed. For instance, after logging in, enter man passwd to read the documentation for passwd(1). To view the documentation for passwd(5), enter man 5 passwd instead. If you are unsure of what man page you are looking for, enter apropos subject-word where "subject-word" is your topic of interest; a list of possibly related man pages will be displayed. Administrivia: ------------- 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. Best Internet Communications for hosting the NetBSD FTP and SUP server. Cygnus Support for hosting the NetBSD Mail server. 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. 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: Bay Area Internet Solutions Jason Brazile David Brownlee Simon Burge Dave Burgess Ralph Campbell Canada Connect Corporation Brian Carlstrom James Chacon Bill Coldwell Charles Conn Tom Coulter Charles D. Cranor Christopher G. Demetriou Demon Internet, UK Easynet, UK Scott Ellis Free Hardware Foundation Greg Gingerich Michael L. Hitch Innovation Development Enterprises of America Scott Kaplan Chris Legrow Neil J. McRae Perry E. Metzger MS Macro System GmbH, Germany Numerical Aerospace Simulation Facility, NASA Ames Research Center Herb Peyerl Mike Price Thor Lancelot Simon Bill Sommerfeld Paul Southworth Jason R. Thorpe 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: Paul Kranenburg Herb Peyerl Scott Reynolds Christos Zoulas The port-masters (and their ports): Mark Brinicombe (arm32) Jeremy Cooper (sun3x) Chuck Cranor (mvme68k) Charles Hannum (i386) Ross Harvey (alpha) Chris Hopps (amiga) Eduardo Horvath (sparc64) Paul Kranenburg (sparc) Ted Lemon (pmax) Anders Magnusson (vax) Tsubai Masanari (macppc, newsmips) Phil Nelson (pc532) Masaru Oki (x68k) Scott Reynolds (mac68k) Gordon Ross (sun3, sun3x) Kazuki Sakamoto (bebox) Wolfgang Solfrank (powerpc) Jonathan Stone (pmax) Jason Thorpe (hp300) Frank van der Linden (i386) Leo Weppelman (atari) The NetBSD 1.3.3 Release Engineering team: Chris G. Demetriou Ted Lemon Perry Metzger Jason Thorpe Supporting cast: Steve Allen Lennart Augustsson Christoph Badura Manuel Bouyer Robert V. Baron John Birrell Manuel Bouyer John Brezak Allen Briggs Aaron Brown David Brownlee Simon Burge Dave Burgess Dave Carrel Bill Coldwell Alistair Crooks Aidan Cully Rob Deker Chris G. Demetriou Matthias Drochner Enami Tsugutomo Bernd Ernesti Erik Fair Hubert Feyrer Thorsten Frueauf Brian R. Gaeke Thomas Gerner Justin Gibbs Adam Glass Michael Graff Brad Grantham Matthew Green Juergen Hannken-Illjes Charles M. Hannum Eric Haszlakiewicz Michael L. Hitch Ken Hornstein Marc Horowitz ITOH Yasufumi Matthew Jacob Lonhyn T. Jasinskyj Darrin Jewell Lawrence Kesteloot Klaus Klein John Kohl Kevin Lahey Ted Lemon Mike Long Paul Mackerras Neil J. McRae Perry Metzger Luke Mewburn Minoura Makoto der Mouse Tohru Nishimura Greg Oster Herb Peyerl Matthias Pfaller Dante Profeta Chris Provenzano Waldi Ravens Darren Reed Tim Rightnour Heiko W. Rupp SAITOH Masanobu Kazuki Sakamoto Curt Sampson Wilfredo Sanchez Ty Sarna Matthias Scheler Karl Schilke (rAT) Tim Shepard Chuck Silvers Thor Lancelot Simon Noriyuki Soda Wolfgang Solfrank Bill Sommerfeld Ignatios Souvatzis Bill Studenmund Kevin Sullivan Kimmo Suominen Matt Thomas Christoph Toshok Todd Vierling Paul Vixie Krister Walfridsson Nathan Williams Colin Wood Steve Woodford Dedication: ---------- The Release Engineering team would like to dedicate the NetBSD 1.3 release to the memory of the late Koji Imada, who was killed in a motorcycle accident in August, 1997 at the age of 28. A doctoral student in Mathematical Science at Nagoya University, he was a user of NetBSD and a contributor to the project since 1993. Well remembered by his friends, he was also known as a connoisseur of gins, teas, and the motorcycles he loved to ride. His death came as a shock, and he will be greatly missed by all of us. May he rest in peace. 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 the NetBSD Foundation, Inc. and its contributors. This product includes software developed by Adam Glass and Charles Hannum. This product includes software developed by Adam Glass. This product includes software developed by Berkeley Software Design, Inc. This product includes software developed by Charles D. Cranor and Washington University. This product includes software developed by Charles D. Cranor. This product includes software developed by Charles Hannum, by the University of Vermont and State Agricultural College and Garrett A. Wollman, by William F. Jolitz, and by the University of California, Berkeley, Lawrence Berkeley Laboratory, and its contributors. This product includes software developed by Charles Hannum. This product includes software developed by Charles M. Hannum. This product includes software developed by Chris Provenzano. This product includes software developed by Christian E. Hopps. This product includes software developed by Christopher G. Demetriou for the NetBSD Project. This product includes software developed by Christopher G. Demetriou. This product includes software developed by Christos Zoulas. This product includes software developed by David Jones and Gordon Ross. This product includes software developed by Dean Huxley. This product includes software developed by Eric S. Hvozda. This product includes software developed by Ezra Story. This product includes software developed by Gordon Ross. This product includes software developed by Gordon W. Ross and Leo Weppelman. This product includes software developed by Gordon W. Ross. This product includes software developed by Herb Peyerl. This product includes software developed by Ian W. Dall. This product includes software developed by Ignatios Souvatzis for the NetBSD Project. This product includes software developed by Jason R. Thorpe for And Communications, http://www.and.com/. This product includes software developed by Joachim Koenig-Baltes. This product includes software developed by Jochen Pohl for The NetBSD Project. This product includes software developed by John Polstra. This product includes software developed by Jonathan Stone and Jason R. Thorpe for the NetBSD Project. This product includes software developed by Jonathan Stone for the NetBSD Project. This product includes software developed by Jonathan Stone. This product includes software developed by Julian Highfield. This product includes software developed by Kenneth Stailey. This product includes software developed by Leo Weppelman. This product includes software developed by Lloyd Parkes. This product includes software developed by Mark Brinicombe. This product includes software developed by Markus Wild. This product includes software developed by Martin Husemann and Wolfgang Solfrank. This product includes software developed by Mats O Jansson and Charles D. Cranor. This product includes software developed by Mats O Jansson. This product includes software developed by Matthias Pfaller. This product includes software developed by Paul Kranenburg. This product includes software developed by Paul Mackerras. This product includes software developed by Peter Galbavy. This product includes software developed by Philip A. Nelson. This product includes software developed by Rodney W. Grimes. This product includes software developed by Scott Bartram. This product includes software developed by SigmaSoft, Th. This product includes software developed by Terrence R. Lambert. This product includes software developed by Theo de Raadt and John Brezak. This product includes software developed by Theo de Raadt. This product includes software developed by TooLs GmbH. This product includes software developed by Winning Strategies, Inc. This product includes software developed by the Center for Software Science at the University of Utah. This product includes software developed by the University of Calgary Department of Computer Science and its contributors. This product includes software developed by the University of Vermont and State Agricultural College and Garrett A. Wollman. This product includes software developed for the FreeBSD project. This product includes software developed for the Internet Software Consortium by Ted Lemon. This product includes software developed for the NetBSD Project by Frank van der Linden. This product includes software developed for the NetBSD Project by Jason R. Thorpe. This product includes software developed for the NetBSD Project by John M. Vinopal. This product includes software developed for the NetBSD Project by Matthias Drochner. This product includes software developed for the NetBSD Project by Matthieu Herrb. This product includes software developed for the NetBSD Project by Perry E. Metzger. This product includes software developed for the NetBSD Project by Piermont Information Systems Inc. This product includes software developed for the NetBSD Project by Ted Lemon. This product includes software developed by Jonathan Stone. This product includes software developed by Ted Lemon. This product includes software contributed to Berkeley by Ralph Campbell. This product includes software contributed to Berkeley by Ralph Campbell and Rick Macklem. This product includes software contributed to Berkeley by Van Jacobson of Lawrence Berkeley Laboratory and Ralph Campbell. This product includes software developed by Christopher G. Demetriou. This product includes software developed by Chris G. Demetriou, and Jonathan Stone. This product includes software developed by Keith Bostic, Chris G. Demetriou, and Jonathan Stone. This product includes software developed by Jonathan Stone for the NetBSD Project. This product includes software developed by the University of California, Berkeley and its contributors. This product includes software developed by the University of California, Lawrence Berkeley Laboratory. This product includes software developed by the NetBSD Foundation, Inc. and its contributors. Some files have the following copyright: * Mach Operating System * Copyright (c) 1991,1990,1989 Carnegie Mellon University * 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 ALLOWS FREE USE OF THIS SOFTWARE IN ITS * CONDITION. CARNEGIE MELLON DISCLAIMS 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 the * rights to redistribute these changes. Some files have the following copyright: * Copyright (c) 1994, 1995 Carnegie-Mellon University. * All rights reserved. * * Author: Chris G. Demetriou * * 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 ALLOWS FREE USE OF THIS SOFTWARE IN ITS "AS IS" * CONDITION. CARNEGIE MELLON DISCLAIMS 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 the * rights to redistribute these changes. Some files have the following copyright: * Copyright (C) 1989 Digital Equipment Corporation. * 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. * Digital Equipment Corporation makes no representations about the * suitability of this software for any purpose. It is provided "as is" * without express or implied warranty. Some files have the following copyright: Copyright 1987 by Digital Equipment Corporation, Maynard, Massachusetts, and the Massachusetts Institute of Technology, Cambridge, Massachusetts. 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 appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the names of Digital or MIT not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. DIGITAL DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL DIGITAL BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN 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: * Copyright 1996 The Board of Trustees of The Leland Stanford * Junior University. 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 appear in all copies. Stanford University * makes no representations about the suitability of this * software for any purpose. It is provided "as is" without * express or implied warranty.