INSTALLATION NOTES for NetBSD/hp300 1.0 Be sure to read _ALL_ of this document before you try to install NetBSD/hp300. What is NetBSD? ---- -- ------ NetBSD is a Berkeley Networking Release 2 (Net/2) and 4.4BSD-Lite -derived system. It is a fully functional UN*X-like system which runs on several architectures and is being ported to more. NetBSD, as the name implies, is a creation of the members of the network community and without the net it's likely that this release wouldn't have come about. NetBSD 1.0 is a milestone release. The hardest part of the 4.4BSD-Lite integration, the kernel, has been completed and has been running in "production use" for quite some time. Also, NetBSD 1.0 is the first true multi-architecture release of NetBSD. At the time of NetBSD 0.9, the 1 port was considered 'production quality' and the hp300 port was barely working. The NetBSD 1.0 source supports nine architectures, and complete binary releases for most of them will be made available. NetBSD 1.0 supports many new and improved features, the most important relating to file systems. New and improved versions of both the Berkeley Fast File System and the free implementation of the NFS protocol were provided, as part of the 4.4-Lite release. The new versions include such improvements as support for 64-bit file sizes, for local files, and "lease" support for NFS, to improve performance. In addition to the file system improvements, many other parts of the system have been improved considerably. For instance, the virtual memory code has substantially improved performance, and many of the kernel's interfaces have been cleaned up. Many new user programs have been added in NetBSD 1.0, as well, bringing it closer to our goal of supplying a complete UN*X-like environment. Additionally, support for shared libraries has been added, for most architectures, allowing a significant savings in both RAM consumption and disk space. This is the first public release of NetBSD for the HP 9000/300 series of computers. The Future of NetBSD: --- ------ -- ------ We hope to have regular releases of the full binary and source trees, but these are difficult to coordinate, especially with all of the architectures which we now support! We hope to support even _more_ hardware in the future, and have a rather large number of other ideas about what can be done to improve NetBSD. We intend to continue our current practice of making the NetBSD-current development source available on a daily or nearly-daily basis. We intend to integrate free, positive changes from whatever sources will provide them, providing that they are well thought-out and increase the usability of the system. This includes integrating the remainder of the 4.4BSD-Lite tape, as quickly as we can ensure that everything works properly. Above all, we hope to create a stable and accessible system, and to be responsive to the needs and desires of NetBSD users, because it is for and because of them that NetBSD exists. Sources of NetBSD: ------- -- ------ Host name Services Provided ---- ---- -------- -------- ftp.iastate.edu Anonymous FTP, AFS Anon-FTP path: pub/netbsd/NetBSD-1.0 AFS path: /afs/iastate.edu/public/ftp/pub/netbsd/NetBSD-1.0 ftp.eecs.umich.edu Anonymous FTP Anon-FTP path: BSD/NetBSD/NetBSD-1.0 gatekeeper.dec.com Anonymous FTP Anon-FTP path: pub/BSD/NetBSD/NetBSD-1.0 wipux2.wifo.uni-mannheim.de Anonymous FTP, SUP Anon-FTP path: pub/NetBSD/NetBSD-1.0 SUP: get the file pub/misc/sup/supfile.example via anonymous FTP and read it as an example. ftp.demon.co.uk Anonymous FTP, possibly SUP Anon-FTP path: pub/BSD/NetBSD/NetBSD-1.0 SUP: contact peter@demon.net for SUP server status/information ftp.uni-regensburg.de Anonymous FTP Anon-FTP path: pub/NetBSD/NetBSD-1.0 ftp.unit.no Anonymous FTP Anon-FTP path: pub/NetBSD/NetBSD-1.0 ftp.stacken.kth.se Anonymous FTP Anon-FTP path: pub/OS/NetBSD/NetBSD-1.0 flick.lerc.nasa.gov Anonymous FTP Anon-FTP path: pub/NetBSD/NetBSD-1.0 coombs.anu.edu.au Anonymous FTP Anon-FTP path: pub/NetBSD/NetBSD-1.0 ftp.funet.fi Anonymous FTP Anon-FTP path: pub/unix/NetBSD/NetBSD-1.0 ftp.netbsd.org Anonymous FTP, SUP Anon-FTP path: pub/NetBSD/NetBSD-1.0 SUP: get the file pub/sup/README.sup via anonymous FTP from ftp.netbsd.org, and read it for instructions. If you wish to become a distribution site for NetBSD, contact Chris Demetriou . NetBSD 1.0 Release Contents: ------ --- ------- -------- The NetBSD 1.0 release is organized in the following way: .../NetBSD-1.0/ 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.0 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.0 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, excluding those portions which should not be exported from the U.S. (Those are contained in each architecture's "security" binary distribution set.) The source distribution sets are as follows: gsrc10 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.7M gzipped, 32.0M uncompressed ] ksrc10 This set contains the sources to the NetBSD 1.0 kernel, config(8), config.new(8) and dbsym(8). [ 4.5M gzipped, 20.8M uncompressed ] ssrc10 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.3M gzipped, 8.5M uncompressed ] src10 This set contains all of the NetBSD 1.0 sources which are not mentioned above. [ 7.1M gzipped, 33.4M uncompressed ] It is worth noting that unless all of the source distribution sets are installed, 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) command. 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 hp300-specific portion of the NetBSD 1.0 release is found in the "hp300" subdirectory of the distribution. That subdirectory is layed out as follows: .../NetBSD-1.0/hp300/ binary/ hp300 binary distribution sets; see below. install/ installation utilities and bootstrap root filesystem image; see below. security/ hp300 security distribution; see below; The NetBSD/hp300 binary distribution sets contain the binaries which comprise the NetBSD 1.0 release for the hp300. There are seven binary distribution sets, and the "security" distribution set. The binary distribution sets can be found in the "hp300/binary" subdirectory of the NetBSD 1.0 distribution tree, and are as follows: base10 The NetBSD/hp300 1.0 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 includes shared library support, and excludes everything described below. [ 6.1M gzipped, 16.3M uncompressed ] comp10 The NetBSD/hp300 Compiler tools. All of the tools relating to C, C++, and FORTRAN (yes, there are two!). This set includes the system include files (/usr/include), the linker, the compiler tool chain, and the various system libraries (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. [ 4.1M gzipped, 12.6M uncompressed ] etc10 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.) [ 51K gzipped, 290K uncompressed ] games10 This set includes the games and their manual pages. [ 1.1M gzipped, 2.7M uncompressed ] man10 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. [ 752K gzipped, 2.9M uncompressed ] misc10 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.6M gzipped, 5.6M uncompressed ] text10 This set includes NetBSD's text processing tools, including groff, all related programs, and their manual pages. [ 782K gzipped, 2.8M uncompressed ] The hp300 security distribution set is named "secr10" and can be found in the "hp300/security" subdirectory of the NetBSD 1.0 distribution tree. It contains crypt.c (the source file for the DES encryption algorithm) and the binaries which depend on it. It can only be found on those sites which carry the complete NetBSD distribution and that can legally obtain it. (Remember, because of United States law, this distribution set may not be exported to locations outside of the United States and Canada.) [ 119K gzipped, 270K uncompressed ] The hp300 binary distribution sets are distributed as gzipped tar files. Each hp300 binary distribution set also has its own "CKSUMS" file, just as the source distribution sets do. 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/hp300 1.0 will run on most HP 9000/300 series machines. The lowest amount of RAM that has been tested is 7.5M, though it may run with less. Certainly, if you wish to run X, more RAM is recommended. Until you reach 16M, more RAM is more important than a faster CPU. Here is a table of recommended HD partition sizes for a full install: partition: advise needed root (/) 15M 15M (see note below) user (/usr) 80M 45M swap ----- 2M for every 1M of RAM ----- local (/local) up to you NOTE: Because of the nature of the hp300 bootstrap procedure, the root filesystem is a _fixed_size_! You may want to consider placing /var and /tmp on their own partitions. This, of course is up to you and your judgement. Also, note that the recommended size of /usr is 15M greater than the needed size. This is to allow room for kernel source and compile areas, as you may want to compile your own kernel. The following HP hardware is supported: CPUs: 68020-based: 318, 319, 320, 330, and 350. 68030-based: 340, 345, 360, 370, 375, and 400. 68040-based: 380, 425, and 433. Disks: HP-IB/CS80: 7912, 7914, 7933, 7936, 7937, 7945, 7957, 7958, 7959, 2200, and 2203. SCSI-I, including magneto-optical and CD-ROM. SCSI-II drives should work if they can talk SCSI-I. Tape drives: Low-density CS80 cartridge: 7914, 7946, 9144. High-density CS80 cartridge: 9145. SCSI: HP DAT and Exabyte. RS232 interfaces: 98644 built-in single port (dca). 98642 4-port (dcm). 98638 8-port (dcm). Network interfaces: 98643 built-in and add-on LAN cards. Displays: 98544, 98545, and 98547 color and monochrome Topcat. 98548, 98549, and 98550 color and monochrome Catseye. 98700 and 98710 Gatorbox. 98720 and 98721 Renaissance. 98730 and 98731 DaVinci. A1096A monochrome Hyperion. Input devices: General interface supporting all HIL devices: keyboard, 2 and 3 button mice, and ID module. Miscellaneous: Battery-backed real-time clock. 98625A and 98625B built-in HP-IB interface. 98658A built-in SCSI interface. Printers and plotters on RS232 and HP-IB. SCSI autochanger. If it's not on this list, there is no support for it in this release. Getting the NetBSD System on to Useful Media: ------- --- ------ ------ -- -- ------ ----- Installation is supported from several media types, including: Tape NFS partitions FTP 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 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. 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 HP-UX, this would be something like /dev/rmt/c0ed03inb. 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. To prepare for installing via an NFS partition: 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. 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, acts which will require superuser privileges. Note the numeric IP address of the NFS server and of the router closest to the the new NetBSD machine, if the NFS server is not on a network which is directly attached to the NetBSD machine. 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. Preparing your System for NetBSD Installation: --------- ---- ------ --- ------ ------------ NOTE: These instructions are explicitly for installing NetBSD from an HP-UX system, version 7 or later. It has not been tested with HP-UX versions earlier than 7, and has also not been tested with HP-UX 8, although it is presumed to work. For the creative, similar steps may be taken from a system such as Utah's 4.3BSD release for the hp300, although bootstrapping from such a system has not been tested. Bootstrapping the hp300 is a complicated process, but it's a lot easier than it used to be. For this process you need the following items from the install/ directory: boot NetBSD/hp300 boot block for HP-IB and SCSI disks rootimage.gz bootstrap root filesystem image label prototype disk label makedisk a program for HP-UX that will write a NetBSD disk label, boot block, and root filesystem image to the target disk (NOTE: This is an HP-UX 7.x binary. while it will work under HP-UX 9.x, you may want to compile this yourself. The source may be found in makedisk.tar.gz) VERY IMPORTANT NOTE: This procedure will destroy all data on the target disk. Because NetBSD uses a different filesystem format than HP-UX, your old data will be useless. If you wish to save anything, use tar(1) instead of dump(1M), again because of filesystem differences. First of all, you must have a second disk on which to install NetBSD. If possible, this disk should first be prepared with mediainit(1M). Once this disk is spotless, you should generate a disk label for it. Using the prototype label provided, fill in all of the necessary information. Remember, if you derive geometry information from an HP-UX disktab, your partition size will be off. This is because HP-UX uses a 1024-byte sector size, while NetBSD uses a 512-byte sector size. To avoid the problem, you may simply double the number of cylinders. (That's what I do...works great. -- JRT) IMPORTANT: Partition 'a' must be offset one cylinder. Since partition information is expressed in sectors, the offset of partition 'a' must be the value of `sectors/cylinder'. This is to leave room for the boot block. When you create your disklabel, be sure to specify whether or not the disk is HP-IB or SCSI in the `type:' field. Below is an example of what a disk label should look like. This is an example only! Do not attempt this at home! # Sample disklabel for example only. This is a comment. type: HP-IB disk: label: INSTALL-1_0 flags: bytes/sector: 512 sectors/track: 36 tracks/cylinder: 7 sectors/cylinder: 252 cylinders: 1013 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 7 partitions: # size offset fstype [fsize bsize cpg] a: 30744 252 4.2BSD 1024 8192 16 # (Cyl. 1 - 122) b: 32760 30996 swap # (Cyl. 123 - 252) c: 255276 0 boot # (Cyl. 0 - 1012) e: 20412 63756 4.2BSD 1024 4096 16 # (Cyl. 253 - 333) f: 40824 84168 4.2BSD 1024 8192 16 # (Cyl. 334 - 495) g: 130284 124992 4.2BSD 1024 8192 16 # (Cyl. 496 - 1012) NOTE: Due to the nature of the bootstrapping procedure, your 'a' partition must be at least 30744 sectors long. Increase the size of your 'a' partition just enough to make it end on a cylinder boundary. If you make it any larger, you will just be wasting space, as the filesystem ends after 30744 sectors. Remember to write down the names of the partitions and what you will be using them for (i.e. 'a - root, b - swap, e - /usr, etc.') as you will need this information later on in the installation process. Once you are satisfied with your disklabel, you can write the root filesystem image to the target disk. Use the `makedisk' program for this. So, under HP-UX, do: ./makedisk /dev/rdsk/c7d0s0 mylabel boot rootimage.gz where: /dev/rdsk/c7d0s0 raw flavor of target disk device mylabel disk label you just wrote boot supplied boot block rootimage.gz gzipped root filesystem image NOTE: This requires that gzip be installed on your HP-UX system. If it is not, a gzip binary is provided in the install/ directory. Source for gzip may be found in the gsrc10 distribution set. Again, this gzip is an HP-UX 7.x binary. If you wish to label any additional disks, you will have to do this from NetBSD, although you will not have an editor at your disposal. To do this, simply generate the labels now, and then grab them at the same time and by the same method you use to grab the distrubtion sets. Once this is done, you should be ready to boot NetBSD from the target disk. Installing the NetBSD System: ---------- --- ------ ------ NOTE: In the following examples you will see references to disk devices. For those not familiar with NetBSD, the following prefixes are used to denote drive types: sd SCSI disk rd HP-IB disk In the examples that follow, `rd' will be used. The steps are exactly the same for `sd' disks. Only the names have changed to protect the innocent. Assuming you have read this document thoroughly and kept good notes about your partitions, the rest should be fairly straight forward. Before you begin, you must have already prepared the target disk as detailed in the section on preparing your system for install. The following is a walk-through of the steps necessary to finish what the preparation process has already begun. You may choose to stop the process at any time, but if you do, it's recommended that you start over from scratch. First you need to boot off of the target disk which you have made in the preparation process. To do this, halt HP-UX, power-cycle your machine, and hit the space bar during the boot ROM's probing/testing sequence. You should eventually be presented with a list of systems from which to boot. You want the one called `SYS_PBOOT'. After selecting `SYS_PBOOT', your system should load the NetBSD boot block and ask you for a kernel to load. Enter the following to boot NetBSD into single-user mode. (Note: it will come into single-user anyway, as there is not yet an fstab, but this makes it happen more gracefully.) netbsd -s The kernel will now load, and configure your hardware. Make a note of the device it lists when mounting the root filesystem. It should look something like this: Changing root device to rd0a The message above is an example only. Your message may be different. Check the root filesystem. Use the raw flavor of the device listed during the `Changing root device...' message. Example: fsck -p /dev/rrd0a Mount the root filesystem: mount /dev/rd0a / It's now time to newfs all of the other partitions you listed in your disk label. So, for example, if rd0e and rd0f were to have filesystems put on them, you would do the following: newfs /dev/rrd0e newfs /dev/rrd0f Ensure that the mount-points for these filesystems are clean. If these filesystems are to be /var and /usr, respectively, just check that there are no files in those directories. There shouldn't be. Once you've made sure, go ahead and mount those filesystems. It's now time to get the distribution sets onto the root or other filesystem. There are several programs in /ibin to help you with this. At your disposal, you have: ftp gzip tar extract Except for extract, which is just a script to help the process along, these are statically-linked versions of themselves, which normally appear in /usr/bin. If you placed the distribution sets on tape, go to the directory where you wish to temporarily place them and extract them from tape, using /dev/nrstX for SCSI tapes or /dev/nrctX for HP-IB cartridge tapes, where X is the unit number of the tape, probably 0. tar xvf /dev/nrst0 If this extracts the sets directly into your current directory, terrific. Otherwise, go to the directory in which they live. Skip on to extracting the sets. If you will be grabbing the sets off of the network somehow, configure your network interface: ifconfig le0 inet route add default If you will be ftp'ing the sets from one of the NetBSD ftp sites, go to the directory where you wish to temporarily place them and download them from the ftp site of your choice. Since you haven't yet created a resolv.conf, you'll need to use the IP address. /ibin/ftp If you will be getting the sets from an NFS server, mount the filesystem on the server which has the sets, and go to the directory that has them. Again, you'll need to use the IP address of the server. mount -t nfs : At this point, you have everything necessary to label any additional disks that you wish to label. If you created additional labels in the preparation phase, and have access to them now, go ahead and label the disks they correspond to: disklabel -W rd1 disklabel -r -R rd1 rd1.label where: rd1 additional disk you wish to label rd1.label file containing disk label information You may check these labels once they are on the disk: disklabel -r rd1 where: rd1 additional disk you wish to label A problem with a partition (such as overlaps or not falling on a cylinder boundary) will be noted with a `*'. If you see these, re-edit your label by the method of your choice (on another machine, perhaps, or with ed(1), for the brave), transfer it to a place that's usable (if necessary) and label the disk again. Once these disks have been labeled, you may newfs the partitions that are to contain filesystems and mount them. You should now be ready to extract the filesets. The program /ibin/extract should help you with this. For example: /ibin/extract base -or- /ibin/extract base.tar.gz Do this for all of the filesets you wish to extract. As your disk fills up, you may wish to remove the sets once you have extracted them. You should have everything necessary to use an editor by now. Set your TERM environment variable: setenv TERM hp300h (csh) -or- export TERM=hp300h (sh) hp300h is the terminal type for the HP 9000/300 ITE console. If you are using a serial console, change the TERM variable appropriately. Now, initialize the terminal: tset You should be able to use vi now. Create an /etc/fstab. Example fstabs are provided in /etc/fstab.sd and /etc/fstab.rd. Edit your host table, /etc/hosts. In it, place the IP address of this host and the IP address of your default router. Edit the file /etc/myname. In it, place the symbolic name of your machine. Edit the file /etc/defaultdomain. In it, place the name of your YP domain. If you will not be using YP, simply enter the domain name of your site. Edit the file /etc/mygate. In it, place the name of your default router, as your listed it in /etc/hosts. Edit the file /etc/hostname.le0. In it, place the following information: inet where: is the name corresponsing to the IP address for that interface, as you listed in /etc/hosts. is the netmask for your network. is the broadcast address for your network. Repeat this step for any additional network interfaces you may have. Edit the file /etc/ttys. Make sure that the entries are correct for whichever console type you have. /dev/console is correct for ITE, /dev/tty0 for console on dca, and /dev/tty00 for console on dcm. You may get more information about /etc/ttys by doing `man ttys', providing you have installed the system manual set. Ok, cross your fingers and reboot: sync; sync; sync; reboot Providing you entered all information correctly, your machine will boot into multi-user mode. Your system will need a few tweaks here and there (like /etc/sendmail.cf and /etc/netstart, perhaps), but that's the easy stuff. CONGRATULATIONS! You have successfully installed NetBSD onto your hp300! Pat yourself on the back. This might also be a good time to remove /ibin, as you will no longer need it, and it is provided solely for bootstrapping purposes. Upgrading a previously-installed NetBSD System: --------- - ---------- --------- ------ ------ There is no previous release of NetBSD/hp300 to upgrade. 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 has provided a home for sun-lamp, people to look after it, and a sense of humor. Rob Robertson, too, has added his unique sense of humor to things, and for a long time provided the primary FTP site for NetBSD. Without CVS, this project would be impossible to manage, so our hats go off to Brian Berliner, Jeff Polk, and the various other people who've had a hand in making CVS a useful tool. 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: Brian Carlstrom Demon Internet, UK Michael L. Hitch Herb Peyerl Mike Price Thor Lancelot Simon Bill Sommerfeld 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.) Dave Burgess has been maintaining the 386BSD/NetBSD/FreeBSD FAQ for quite some time, and deserves to be recognized for it. 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 team: Chris G. Demetriou Theo de Raadt Adam Glass Charles Hannum The port-masters (and their ports): Allen Briggs (mac68k) (and the rest of the 'Alice' group) Theo de Raadt (sparc) Charles Hannum (1, hp300) Chris Hopps (amiga) Adam Glass (pmax) Paul Mackerras (da30) Anders Magnusson (vax) Phil Nelson (pc532) Gordon Ross (sun3) Supporting cast: Steve Allen John Brezak Dave Burgess J.T. Conklin Hubert Feyrer Brad Grantham Lawrence Kesteloot Paul Kranenburg Herb Peyerl Matthias Pfaller Chris Provenzano Wolfgang Solfrank 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 Paul Kranenburg. This product includes software developed by Adam Glass. This product includes software developed by Jason R. Thorpe.