INSTALLATION NOTES for NetBSD/pmax 1.2 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 derrived 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 current release has built upon the successful NetBSD 1.1 release by integrating many bug fixes, adding new and updated kernel subsystems, and adding various userland enhancements. The results of these improvements is a stable operating system fit for production use and ready for the next phase of development. Significant changes include: Continuing the multi-platform tradition, the integration of the DEC Alpha port has been completed, and new ports to ARM and x68k have been added. NetBSD/sparc now supports 4m machines. NetBSD/amiga now supports the DraCo. Standard C Prototypes have been added to the Kernel. Kernel NTP (Network Time Protocol) phased lock loop support has been added. See http://www.eecis.udel.edu/~ntp/ for more details. The PINT (PINT is not TWAIN) SCSI scanner driver interface has been integrated. See http://www.dol-esa.gov/~kstailey/pint for more details. A new SCSI medium changer driver and the `chio' program used to operate it has been added. The NFS subsystem now supports NFSv3. Several performance enhancements have been made to the networking subsystem. GCC, Libg++, and many other third party programs have been upgraded to more recent versions. 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.2 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. NetBSD 1.2 is the second public release of NetBSD for the DECstation and DECsystem family of computers. This release includes kernel support for ELF shared libraries, much of which is due to work by Per Fogelstrom (pefo@OpenBSD.ORG). Note that NetBSD/1.2 pmax still ships with statically-linked user binaries. Ultrix emulation for tty-aware applications is improved over NetBSD 1.1. Many NetBSD/pmax bugs have been fixed, including annoying bugs in the 4.4bsd-Lite/pmax SCSI drivers. 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 Sep 30, 1996. Host name Services Provided ---- ---- -------- -------- ftp.netbsd.org Anonymous FTP FTP path: ftp://ftp.netbsd.org/pub/NetBSD sup.netbsd.org SUP SUP: See ftp://ftp.netbsd.org/pub/NetBSD/sup/README.sup ftp.iastate.edu Anonymous FTP, AFS FTP path: ftp://ftp.iastate.edu/pub/netbsd AFS path: /afs/iastate.edu/public/ftp/pub/netbsd ftp.eecs.umich.edu Anonymous FTP FTP path: ftp://ftp.eecs.umich.edu/BSD/NetBSD ftp.cs.umn.edu Anonymous FTP, SUP FTP path: ftp://ftp.cs.umn.edu/packages/NetBSD SUP: hostbase=/ftp/ftp/packages/NetBSD, collections are the same as on sup.NetBSD.ORG ftp.cslab.vt.edu Anonymous FTP FTP path: ftp://ftp.cslab.vt.edu/pub/NetBSD ftp.op.net Anonymous FTP FTP path: ftp://ftp.op.net/pub/NetBSD ftp.cetlink.net Anonymous FTP, SUP FTP path: ftp://ftp.cetlink.net/pub/NetBSD SUP: sup.cetlink.net hostbase=/a/anon_ftp/pub netbsd.rmit.edu.au Anonymous FTP, SUP FTP path: ftp://netbsd.rmit.edu.au/pub/NetBSD SUP: ftp://netbsd.rmit.edu.au/README.sup ftp.coppe.ufrj.br Anonymous FTP FTP path: ftp://ftp.coppe.ufrj.br/mirror/netbsd ftp.cevis.uni-Bremen.de Anonymous FTP FTP path: ftp://ftp.cevis.uni-Bremen.de/pub/comp/os/NetBSD netbsd.wifo.uni-mannheim.de Anonymous FTP, SUP FTP path: ftp://netbsd.wifo.uni-mannheim.de/pub/NetBSD SUP: See ftp://netbsd.wifo.uni-mannheim.de/pub/NetBSD/sup/cfg-files/normal ftp.uni-regensburg.de Anonymous FTP FTP path: ftp://ftp.uni-regensburg.de/pub/comp/os/NetBSD/ ftp.uni-trier.de Anonymous FTP, SUP FTP path: ftp://ftp.uni-trier.de/pub/unix/systems/NetBSD SUP: use host=sup.uni-trier.de, hostbase=/ftp/pub/unix/systems/NetBSD collections are the same as on sup.NetBSD.ORG netbsd.tohoku.ac.jp Anonymous FTP FTP path: ftp://netbsd.tohoku.ac.jp/NetBSD ftp.cs.uit.no Anonymous FTP, SUP FTP path: ftp://ftp.cs.uit.no/pub/NetBSD SUP: Get the file README.sup via anonymous ftp, and read it. ftp.ntnu.no Anonymous FTP FTP path: ftp://ftp.ntnu.no/pub/NetBSD/ skarven.itea.ntnu.no SUP SUP: 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 ftp.stacken.kth.se Anonymous FTP FTP path: ftp://ftp.stacken.kth.se/pub/OS/NetBSD ftp.sunet.se Anonymous FTP FTP path: ftp://ftp.sunet.se/pub/os/NetBSD If you wish to become a distribution site for NetBSD, contact mirrors@netbsd.org. NetBSD 1.2 Release Contents: ------ --- ------- -------- The NetBSD 1.2 release is organized in the following way: .../NetBSD-1.2/ 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.2 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.2 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: dsrc12 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 ] gsrc12 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 ] ksrc12 This set contains the sources to the NetBSD 1.2 kernel, config(8), config.old(8) and dbsym(8). [ 6.0M gzipped, 27.0M uncompressed ] ssrc12 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 ] src12 This set contains all of the NetBSD 1.2 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 pmax-specific portion of the NetBSD 1.2 release is found in the "pmax" subdirectory of the distribution. That subdirectory is laid out as follows: .../NetBSD-1.2/pmax/ binary/ pmax binary distribution sets; see below. install/ a GENERIC kernel, installation utilities and a miniroot filesystem; see below. security/ pmax security distribution; see below. The NetBSD/pmax binary distribution sets contain the binaries which comprise the NetBSD 1.2 release for the pmax. There are seven binary distribution sets, and the "security" distribution set. The binary distribution sets can be found in the "pmax/binary" subdirectory of the NetBSD 1.2 distribution tree, and are as follows: base12 The NetBSD/pmax 1.2 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. [ 20.4M gzipped, 19M uncompressed ] comp12 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. [ 7.4M gzipped, 14.7M uncompressed ] etc12 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.) [ 68K gzipped, 348K uncompressed ] games12 This set includes the games and their manual pages. [ 2.8M gzipped, 6.8M uncompressed ] man12 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.9M gzipped, 3.6M uncompressed ] misc12 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, 6.6M uncompressed ] text12 This set includes NetBSD's text processing tools, including groff, all related programs, and their manual pages. [ 1.2M gzipped, 3.18M uncompressed ] The pmax 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 (Remember, because of United States law, this distribution set may not be exported to locations outside of the United States and Canada.) [ 128K gzipped, 275K uncompressed ] 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.2 on a Decstation not already running NetBSD 1.2 is supported by the following files, which are included in the `.../install' directory: miniroot.gz A gzipped copy of a miniroot filesystem. When unzipped, this is suitable for dd'ing onto a raw disk partition. netbsd.gz A gzipped GENERIC kernel. 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.2 runs on the following classes of machines: - Decstation 2100 and 3100, also known as "pmin" and "pmax" - Personal Decstations (5000/20, and /25) also knonw as "MAXINE" - Decstation 5000/120, /125, and /133, also knonw as "3MIN" - Decstation 5000/200, also knonw as "3MAX" - Decstation 5000/240, als knonw as "3MAXPLUS" NetBSD/pmax 1.2 does *not* (yet) run on these machines: - Decstation 5100 (an r2000-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 8800 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 vide 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. SCSI: on-board DEC "sii" SCSI controller (2100 and 3100) on-board "asc" SCSI controller (5000 series machines) TurboChannel "asc" SCSI controller, 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 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 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 beleived 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: --------- ---- ------ --- ------ ------------ Before you start you should familiarize yourself with the boot PROM of your machine. The older Decstation 2100 and 3100 cannot select a kernel from the command line. You need to set the bootpath environment variable to point to the disk and kernel you intend to boot. You should also examine the guide on the NetBSD/pmax web site, which has more complete and more up-to-date instructions than are given in the install document. NOTE that the instructions on old versions of the web site are incorrect. The installation miniroot image for both NetBSD 1.1 and 1.2 include the 8Kbytes reserved for bootblocks and disklabel. The dd commands to write the miniroot to a freshly-labeleld disk should have an 'skip=16' added to them, if the 'skip=16' option is already present. If you're installing NetBSD/pmax for the first time it's a very good idea to look at the partition sizes of disk you intend installing NetBSD on. 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. Asumming a classic partition scheme with root (`/') and /usr filesystems, a comfortable size for the NetBSD root filesystem partition is about 20MB; 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). A full binary installation, without X11 or other additional software, takes about 130MB in `/usr'. This will be substantially reduced in the next release with support fo dynamically-linked shared libraries. Installing the NetBSD System: ---------- --- ------ ------ If at all possible, you should consult the ``Installation Guide'' document on the NetBSD/pmax web page, at http://www.netbsd.org/ports/pmax. Installing NetBSD is a relatively complex process, but if you have the above document in hand it shouldn't be too much trouble. It has not been possible to reproduce the pmax installation Web page in fixed-font hardcopy format for the 1.2 release. You must either visit the URL above, or request a rendered version (e.g, PostScript). Please follow the dinstructions at http://111.netbsd.org/ports/pmax/pmax-install.html, now,and return to this document when you used those instructions to install a miniroot, label a disk, and extract the NetBSD/pmax 1.2 installation tar sets. Post-intallation notes: ---------------------- Some of the files in the NetBSD 1.2 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. Upgrading a previously-installed NetBSD System: --------- - ---------- --------- ------ ------ It may be possible to easily upgrade your existing NetBSD/pmax system using the upgrade program in the miniroot. NOTE: this has not been tested and should be done with caution, after backing up your system. If you wish to upgrade your system by this method, simply select the `upgrade' option once the miniroot has booted. The upgrade program with then guide you through the procedure. The upgrade program will: * Enable the network based on your system's current network configuration. * Mount your existing filesystems. * Extract binary sets from the media of your choice. * Fixup your system's existing /etc/fstab, changing the occurrences of `ufs' to `ffs' and let you edit the resulting file. * Make new device nodes in your root filesystem. * Copy a new kernel onto your root partition. NOTE: the existing kernel WILL NOT be backed up; doing so would be pointless, since a NetBSD 1.1 kernel will not work correctly with all NetBSD 1.2 executables. * Install a new boot block. * Check your filesystems for integrity. While using the miniroot's upgrade program is the preferred method of upgrading your system, it is possible to upgrade your system manually. To do this, follow the following procedure: * Place _at least_ the `base' binary set in a filesystem accessible to the target machine. A local filesystem is preferred, since there may be incompatibilities between the NetBSD 1.2 kernel and older route(8) binaries. * Back up your pre-existing kernel and copy the 1.2 kernel into your root partition. * Reboot with the 1.2 kernel into single-user mode. * Check all filesystems: /sbin/fsck -p * Mount all local filesystems: /sbin/mount -a -t nonfs * If you keep /usr or /usr/share on an NFS server, you will want to mount those filesystems as well. To do this, you will need to enable the network: sh /etc/netstart NOTE: the route(8) commands may fail due to potential incompatibilities between route(8) and the NetBSD 1.2 kernel. Once you have enabled the network, mount the NFS filesystems. If you use amd(8), you may or may not have to mount these filesystems manually. Your mileage may vary. * Make sure you are in the root filesystem and extract the `base' binary set: cd / tar --unlink -zxvpf /path/to/base12.tar.gz NOTE: the `--unlink' option is _very_ important! * Sync the filesystems: sync * At this point you may extract any other binary sets you may have placed on local filesystems, or you may wish to extract additional sets at a later time. To extract these sets, use the following commands: cd / tar --unlink -zxvpf NOTE: you SHOULD NOT extract the `etc' set if upgrading. Instead, you should extract that set into another area and carefully merge the changes by hand. 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: ------------- 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. 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. 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: Bay Area Internet Solutions Jason Brazile Dave Burgess Canada Connect Corporation James Chacon Bill Coldwell Charles Conn Brian Carlstrom Tom Coulter Charles D. Cranor Demon Internet, UK Easynet, UK Free Hardware Foundation Greg Gingerich Michael L. Hitch Scott Kaplan Chris Legrow MS Macro System GmbH, Germany 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: J.T. Conklin Charles Hannum Paul Kranenburg Jason Thorpe Christos Zoulas The port-masters (and their ports): Allen Briggs (mac68k) Mark Brinicombe (arm32) Chuck Cranor (mvme68k) Chris G. Demetriou (alpha) Charles Hannum (1) Chris Hopps (amiga) Paul Kranenburg (sparc) Anders Magnusson (vax) Phil Nelson (pc532) Masaru Oki (x68k) Gordon Ross (sun3) Jonathan Stone (pmax) Jason Thorpe (hp300) Frank van der Linden (1) Leo Weppelman (atari) Supporting cast: Steve Allen John Brezak Aaron Brown Dave Burgess Bill Coldwell Bernd Ernesti Hubert Feyrer Brian R. Gaeke Adam Glass Michael Graff Brad Grantham Matthew Green Michael L. Hitch Lawrence Kesteloot John Kohl Ted Lemon Paul Mackerras Neil J. McRae Perry Metzger Herb Peyerl Matthias Pfaller Chris Provenzano Waldi Ravens Scott Reynolds Karl Schilke (rAT) Thor Lancelot Simon Noriyuki Soda Wolfgang Solfrank Ignatios Souvatzis Kevin Sullivan 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 Christopher G. Demetriou for the NetBSD Project. This product includes software developed by Adam Glass. This product includes software developed by Christian E. Hopps. This product includes software developed by John Kohl. This product includes software developed by Paul Kranenburg. This product includes software developed by Terrence R. Lambert. This product includes software developed for the NetBSD Project by Frank van der Linden. This product includes software developed by Philip A. Nelson. This product includes software developed by Jochen Pohl for the NetBSD Project. 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 for the NetBSD Project by Jason R. Thorpe. This product includes software developed by Jason R. Thorpe for And Communications, http://www.and.com/ This product includes software developed by TooLs GmbH. This product includes software developed for the NetBSD Project by John M. Vinopal. This product includes software developed by Christos Zoulas.