INSTALLATION NOTES for NetBSD/hp300 1.3.3 Be sure to read _ALL_ of this document before you try to install NetBSD/hp300. 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 HP 9000/300 series of computers. 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 hp300-specific portion of the NetBSD 1.3.3 release is found in the "hp300" subdirectory of the distribution. That subdirectory is laid out as follows: .../NetBSD-1.3.3/hp300/ SOURCE_DATE A file containing the date, in UTC, of the source code from which the release or snapshot was built, in the default format produced by the command: `date -u`. INSTALL Installation notes; this file. binary/ kernel/ Suitably named, gzipped hp300 kernels; see below. security/ Security-related hp300 binaries; see below. sets/ hp300 binary distribution sets; see below. installation/ miniroot/ hp300 miniroot images; see below. misc/ Miscellaneous hp300 installation helper utilities; see installation section below. The NetBSD/hp300 binary distribution sets contain the binaries which comprise the NetBSD 1.3.3 release for the hp300. There are eight binary distribution sets, and the "security" distribution set. The binary distribution sets can be found in the "hp300/binary/sets" subdirectory of the NetBSD 1.3.3 distribution tree, and are as follows: base The NetBSD/hp300 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 includes shared library support, and excludes everything described below. [ 9.2M gzipped, 26.4M uncompressed ] comp The NetBSD/hp300 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. [ 6.8M gzipped, 23.9M uncompressed ] 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.) [ 55K gzipped, 337K uncompressed ] games This set includes the games and their manual pages. [ 2.9M gzipped, 7.5M uncompressed ] kern This set includes a NetBSD/hp300 1.3.3 GENERIC kernel, named "/netbsd". You MUST install this distribution set. [ 547K gzipped, 1.2M uncompressed ] 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.5M gzipped, 10.4M uncompressed ] 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. [ 2.2M gzipped, 8.4M uncompressed ] text This set includes NetBSD's text processing tools, including groff, all related programs, and their manual pages. [ 1.0M gzipped, 3.4M uncompressed ] The hp300 security distribution set is named "secr" and can be found in the "hp300/binary/security" subdirectory of the NetBSD 1.3.3 distribution tree. It contains executables which are built in the "src/domestic" portion if the NetBSD source tree. 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, it may not be legal to distribute this set to locations outside of the United States and Canada.) [ 776K gzipped, 263K uncompressed ] 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. Unfortunatly there is no R6.3 Xserver for NetBSD/hp300 yet, so we can only distribute the X clients this time. You can not yet install them using the new automated install system. However, they are gzipped tarfiles, just like the other sets, so you can always simply extract them once you have your NetBSD system installed and running. The sets are: xbase The basic files needed for a complete X client environment. This does not include the X servers. [ 2.5M gzipped, 7.6M uncompressed ] xcomp The extra libraries and include files needed to compile X source code. [ 1.7M gzipped, 7.1M uncompressed ] xcontrib Programs that were contributed to X. [ 183k gzipped, 686k uncompressed ] xfont Fonts needed by X. [ 5.9M gzipped, 7.3M uncompressed ] The hp300 binary distribution sets are distributed as gzipped tar files named with the extension ".tgz", e.g. "base.tgz". Each hp300 binary distribution set also has its own checksum files, 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 xfp" from /. Also note that if you upgrade or install this way, those programs that you are using at the time will NOT be replaced unless you run "tar" with the "--unlink" option. If you follow the normal installation or upgrade procedures, this will be taken care of for you. The following are included in the `hp300/installation' directory: miniroot/ miniroot.fs.gz A copy of the miniroot filesystem. misc/ HP-IB.geometry A file containing geometry for some HB-IB disk drives. SYS_INST.gz A gzipped copy of the SYS_INST miniroot installation program. SYS_UBOOT.gz A gzipped copy of the universal boot block. Supports Network, tape and disk booting. This is useful if you are installing a diskless NetBSD/hp300 system. rbootd.tgz Source code for the rbootd program included with NetBSD. It requires that the server has a Berkeley Packet Filter (bpf). You will need to compile this version of rbootd if server system does not have this utility already. The following are included in the `hp300/binary/kernel'directory: netbsd.gdb.gz A gzipped GENERIC kernel with debugging symbols. netbsd.gz A gzipped GENERIC kernel. Note: Each directory in the hp300 binary distribution also has its ----- own checksum files, just as the source distribution does: All BSDSUM files are historic BSD checksums for the various files in that directory, in the format produced by the command: cksum -o 1 . All CKSUM files are POSIX checksums for the various files in that directory, in the format produced by the command: cksum . All MD5 files are MD5 digests for the various files in that directory, in the format produced by the command: cksum -m . All SYSVSUM files are historic AT&T System V UNIX checksums for the various files in that directory, in the format produced by the command: cksum -o 2 . The MD5 digest is the safest checksum, followed by the POSIX checksum. The other two checksums are provided only to ensure that the widest possible range of system can check the integrity of the release files. NetBSD System Requirements and Supported Devices: ------ ------ ------------ --- --------- ------- NetBSD/hp300 1.3.3 will run on most HP 9000/300- and 400-series machines. The smallest amount of RAM that has been tested is 4M. If you wish to run X, more RAM is recommended. Here is a table of recommended HD partition sizes for a full install: partition: advise needed root (/) 25M 15M user (/usr) 150M 100M swap (2 or 3 * RAM) 6M (see note below) Anything else is up to you! NOTE: The hp300 installation procedure uses a `miniroot' filesystem which is placed into the swap area of the disk. The swap partition must be large enough to hold this miniroot image. 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. Tape drives: Low-density HP-IB/CS80 cartridge: 7914, 7946, and 9144. High-density HP-IB/CS80 cartridge: 9145. HP-IB/CS80 1/2": 7974A, 7978A/B, 7979A, 7980A, and 7980XC. SCSI: HP DAT, Exabyte, and SCSI QIC drives such as the Archive Viper. 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. 98624 built-in HP-IB interface. 98625A and 98625B `fast' HP-IB interface. 98658A built-in and add-on SCSI interface. Printers and plotters on RS232 and HP-IB. SCSI autochanger. (*) 400-series machines configured for Domain/OS are not fully supported, notably, the keyboard doesn't work and the ROMs must be in `HP-UX mode'. (**) SCSI-II drives are known to work, though this may require changing a jumper on some drives. See your disk's documentation for details. (***) Serial mice connected to a `HIL to quad' converter are also known to work. If it's not on this list, there is no official support for it in this release. Getting the NetBSD System on to Useful Media: ------- --- ------ ------ -- -- ------ ----- Installation is supported from several media types, including: Tape CD-ROM NFS 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: If you wish to load SYS_INST from tape, it must appear on the tape before any other files. To copy this onto tape, use a command like the following: dd if=SYS_INST of= obs=20b conv=osync Note that not all HP BOOTROMs support booting from SCSI tapes. Copying the miniroot to disk from tape is not currently supported. However, it is planned for a future release. If you wish to extract binary sets onto your disk from tape, you must first place them on the tape. The easiest way to do this is with the dd(1) command. Make sure you use a `no-rewind-on-close' tape device. For example: for file in base.tgz etc.tgz; do dd if=${file} of=/dev/nrst0 done Note that depending on your tape drive, you may need to explicitly set the EOF marker at the end of each file. It may also be necessary to use the `conv=osync' argument to dd(1). Note that this argument is incompatible with the `bs=' argument. Consult the tape-related manual pages on the system where the tapes are created for more details. To prepare for installing via NFS: SYS_INST currently requires an NFS server from which to copy the miniroot. * This filesystem must be exported with root permissions, but may be exported read-only. * The miniroot image _must_ reside in the `root' of the mounted filesystem. For example, if the client system mounts `server:/u', then the miniroot image must reside in /u on the server. This is due to limitations in the file lookup code used in SYS_INST, and may be fixed in a future release. * If you also wish to install the binary sets from the NFS server, place them in a properly exported filesystem on the server. Note that these files do not suffer from the same placement restrictions as the miniroot. To prepare for installing via FTP: It is possible, using the `install' and `upgrade' programs in the miniroot, to extract the binary sets directly onto disk from an FTP server. This is by far the easiest installation method, as you may specify to have all sets extracted at once, providing that they are located in the same directory on the server. All that is required in this case is that you have network access to an FTP server. This may be your account on another system, or may even be ftp.NetBSD.ORG itself. If you wish to use ftp.NetBSD.ORG as your FTP file server, you may want to keep the following information handy: IP Address: ftp.NetBSD.ORG Login: anonymous Password: Server path: /pub/NetBSD/NetBSD-1.3.3/hp300/binary/sets Note: if you're not using a nameserver during installation, you might find 204.152.184.75 handy; it's the IP address of ftp.NetBSD.ORG as of December, 29, 1997. Preparing your System for NetBSD Installation: --------- ---- ------ --- ------ ------------ Currently, only installing the miniroot from the network is supported. This may change in a future release. You will need information about your disk's geometry, based on 512-byte sectors. You must have this information before proceeding. The file `.../installation/misc/HP-IB.geometry' has geometry inforomation for several HP-IB disks, but may be incomplete. Geometry may be calculated from an HP-UX `/etc/disktab' entry, but note that HP-UX geometry is based on 1024 byte sectors, while NetBSD's is based on 512 byte sectors. QUICK NOTE ABOUT PARTITIONS: Since the target disk will become the boot disk for your new NetBSD/hp300 installation, you will need to treat the `a' and `c' partitions in a special manner. Due to the size of the NetBSD/hp300 boot program (it spills into the area after the disklabel), it is necessary to offset the `a' partition one cylinder from the beginning of the disk. Later, the `c' partition will be marked with the type `FS_BOOT' and may not be used for a filesystem. (For those unfamiliar with historic BSD partition conventions, the `c' partition is defined as `the entire disk', or the `raw partition'.) A QUICK NOTE ABOUT DISK NUMBERS: While in the SYS_INST program, you may use different unit numbers for the disks than when the NetBSD kernel is running. The unit number for a disk while in SYS_INST is calculated with the following formula: unit = (controller * 8) + slave Controllers are numbered 0, 1, ... starting with the lowest select code. SCSI controllers and HP-IB controllers are counted separately. Therefore, if you had a system with an internal HP-IB interface at select code 7, a fast HP-IB interface at select code 14, and a SCSI interface at select code 16, unit numers might be something like the following: Location Unit -------- ---- HP-IB at 7, slave 2 2 (disk: rd2) HP-IB at 14, slave 5 13 (disk: rd13) SCSI at 16, slave 0 0 (disk: sd0) Miniroot installation via network --------------------------------- NOTE: BOOTING SYS_INST VIA THE NETWORK ON EARLY HP300 MODELS IS ONLY POSSIBLE IF YOUR BOOTROM IS `REV. C' OR LATER. When checking the revision of your BOOTROM, use what it printed on the console during the self-test, not what may be printed on a sticker on the chip itself. In order to complete this process, you will need the following from the `.../installation/misc' directory of the distribution: SYS_INST.gz The standalone disklabel and miniroot installation tool. This file must be un-gzipped before using. And the following from the `.../installation/miniroot' directory of of the distribution: miniroot.fs.gz A miniroot filesystem image. To boot SYS_INST via the network, you will need a system capable of handling boot requests for an HP workstation. If you will use this method, see the special note below. To boot SYS_INST from tape, you need only place SYS_INST on the tape as the first file. -- The following section is specific for loading SYS_INST via the network. -- If you wish to load the SYS_INST program via the network, you may need the following from the `.../installation/misc' directory in addition to the items listed above: rbootd.tgz Source code for the rbootd program included with NetBSD. It requires that the server has a Berkeley Packet Filter (bpf). You will need to compile this version of rbootd if your server system does not have this utility already. First of all, configure your rbootd to handle boot requests from the client. NOTE: NetBSD's `rbootd' is slightly different from HP-UX's. To configure NetBSD's `rbootd', create a file called `/etc/rbootd.conf' and place in it an entry like the following: 08:00:09:04:AA:33 SYS_INST # thunder-egg The first column is the ethernet address of the client's network interface. The second column is the program to send to the client, and anything after the `#' is a comment. Once you have rbootd running, copy the SYS_INST program to the /usr/mdec/rbootd directory on your server. If this directory doesn't exist already, you will need to create it. For information on configuring rbootd under HP-UX, see the rbootd(1M) manual page on your server system. Once `rbootd' is configured and running, you will be ready to continue. ------------------ End of network boot-specific section ---------------------- Make sure that the miniroot filesystem image has been un-gzipped, and that it resides in a filesystem what is exported to the client. See the manual pages on your server system if you need more information about exporting filesystems. You are now ready to SYS_INST. During the client's self-test cycle, press the space bar a few times. Shortly, you should see a menu of possible boot options appear. Select the option corresponding to SYS_INST. SYS_INST will load and prompt you for a command. If this is a new NetBSD installation, you will need to place a disklabel on the disk. sys_inst> disklabel NOTE: it may be worth selecting the `zap' option initially to ensure that the disklabel area is clear. This may be especially important if an HP-UX boot block had been previously installed on the disk. Select the `edit' option, and answer the questions about your disk. There may be several questions which you may not be sure of the answers to. Listed below are guidelines for SCSI and HP-IB disks: Bad sectoring? NO Ecc? NO Interleave? 1 Trackskew? 0 Cylinderskew? 0 Headswitch? 0 Track-to-track? 0 Drivedata 0-4? 0 (for all Drivedata values) Next, you will be asked to fill out the partition map. You must provide responses for all 8 partitions. Remember, you must allocate at least 6M for the `b' partition, or else the miniroot will not fit. Set the size and offset of any unused partition to 0. Note that sizes and offsets are expressed in `n sectors', assuming 512 byte sectors. Care should be taken to ensure that partitions begin and end on cylinder boundaries (i.e. size and offset is an even multiple of the number of sectors per cylinder). While this is not technically necessary, it is generally encouraged. NOTE: When setting the partition type of the `b' partition, make sure to specify it as an `ffs' partition so that the miniroot can be mounted (even if this will be a swap partition). You will be given a chance to clean this up later in the installation process. Once you have edited the label, select the `show' option to verify that it is correct. If so, select `write' and `done'. Otherwise, you may re-edit the label. The next step is to copy the miniroot image onto the target disk. sys_inst> miniroot You will be prompted for the target disk and the source of the miniroot filesytem image. Enter the filename of the miniroot image. Note that this file _must_ reside in the server directory being mounted. Next you will be asked for the client's IP address, netmask, and default router, the server's IP address, and the directory on the server to mount. Once you have entered this information, SYS_INST will attempt to mount the NFS server and begin copying the miniroot filesystem to the `b' partition of the target disk. Is is worth noting that this copy may take a while. It might be worth grabbing a cup of coffee at this point. Once the miniroot filesystem image has been copied onto the target disk, you may boot from the miniroot filesystem. sys_inst> boot Enter the disk from which to boot. The kernel in the miniroot filesystem will be booted into single-user mode. Installing the NetBSD System: ---------- --- ------ ------ The miniroot's install program is very simple to use. It will guide you through the entire process, and is well automated. Additional improvements are planned for future releases. The miniroot's install program will: * Allow you to place disklabels on additional disks. Note that partition sizes and offsets are expressed in sectors. When you fill out the disklabel, you will need to specify partition types and filesystem parameters. If you're unsure what the these values should be, use the following: fstype: 4.2BSD fsize: 1024 bsize: 4096 cpg: 16 If the partition will be a swap partition, use the following: fstype: swap fsize: 0 (or blank) bsize: 0 (or blank) cpg: 0 (or blank) You will also need to specify the number of partitions. The number of partitions is determined by the `index' of the last partition letter, where a == 1, b == 2, etc. Therefore, if the last filled partition is partition `g', there are 7 partitions. Any partitions with size of 0 may be removed from the list. If the disk is the boot disk, you _must_ offset the root partition (`a') one cylinder, as the hp300 boot code if large enough to spill past the label area. In this case, the `c' partition must be fstype `boot'. Anything after a `#' is a comment. The following is an example disklabel partition map: 7 partitions: #size offset fstype [fsize bsize cpg] a: 30912 448 4.2BSD 1024 8192 16 # (Cyl. 1 - 69) b: 130816 31360 swap # (Cyl. 70 - 361) c: 1296512 0 boot # (Cyl. 0 - 2893) e: 81984 162176 4.2BSD 1024 8192 16 # (Cyl. 362 - 544) f: 102592 244160 4.2BSD 1024 4096 16 # (Cyl. 545 - 773) g: 949760 346752 4.2BSD 1024 8192 16 # (Cyl. 774 - 2893) * Create filesystems on target partitions. * Allow you to set up your system's network configuration. Remember to specify host names without the domain name appended to the end. For example use `foo' instead of `foo.bar.org'. If, during the process of configuring the network interfaces, you make a mistake, you will be able to re-configure that interface by simply selecting it for configuration again. * Mount target filesystems. You will be given the opportunity to manually edit the resulting /etc/fstab. * Extract binary sets from the media of your choice. * Copy configuration information gathered during the installation process to your root filesystem. * Make device nodes in your root filesystem. * Copy a new kernel onto your root partition. * Install a new boot block. * Check your filesystems for integrity. First-time installation on a system through a method other than the installation program is possible, but strongly discouraged. Upgrading a previously-installed NetBSD System: --------- - ---------- --------- ------ ------ It is possible to easily upgrade your existing NetBSD/hp300 system using the upgrade program in the miniroot. 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. * Don't forget to extract the `kern' set from the distribution. NOTE: the existing kernel WILL NOT be backed up; doing so would be pointless, since older kernels may not be capable of running NetBSD 1.3.3 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 the NFS subsystem in the NetBSD 1.3.3 kernel may be incompatible with your old binaries. * Back up your pre-existing kernel and copy the 1.3.3 kernel into your root partition. * Reboot with the 1.3.3 kernel into single-user mode. * Check all filesystems: /sbin/fsck -pf * 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 * Run the update(8) daemon, to ensure that new programs are actually stored on disk. update * Make sure you are in the root filesystem and extract the `base' binary set: cd / tar --unlink -zxvpf /path/to/base.tgz NOTE: the `--unlink' option is _very_ important! * Install a new boot block: cd /usr/mdec disklabel -B * 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. 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 the Computer Systems Laboratory at the University of Utah. This product includes software developed at Ludd, University of Lule}, Sweden and its contributors. This product includes software developed by Gordon W. Ross.