INSTALLATION NOTES for NetBSD/alpha 1.3 Be sure to read _ALL_ of this document before you try to install NetBSD/alpha. 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 release is 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. There have been many, many Alpha-specific enchancements since the 1.2 release. These include: * Supporting more system types (including the 8200/8400). * Making many more device drivers (mostly from the i386 port) work on the alpha. * Changing the object file format from COFF to ELF, and adding shared library support NetBSD 1.3 on alpha is, as usual, also fully backward compatible with old NetBSD/alpha binaries, so you don't need to recompile all your local programs. 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 22, 1997 If you wish to become a distribution site for NetBSD, contact mirrors@netbsd.org. FTP mirrors ----------- Australia * ftp://ftp.au.netbsd.org/pub/NetBSD Brazil * ftp://ftp.ravel.ufrj.br/pub/NetBSD Germany * ftp://ftp.de.netbsd.org/pub/NetBSD * ftp://ftp.uni-regensburg.de/pub/comp/os/NetBSD Japan * ftp://netbsd.tohoku.ac.jp/NetBSD Netherlands * ftp://ftp.nl.netbsd.org/pub/comp/NetBSD Norway * ftp://ftp.ntnu.no/pub/NetBSD * ftp://skarven.itea.ntnu.no/pub/NetBSD Sweden * ftp://ftp.stacken.kth.se/pub/OS/NetBSD * ftp://ftp.sunet.se/pub/os/NetBSD UK * ftp://ftp.DOMINO.ORG/pub/NetBSD USA * ftp://ftp.netbsd.org/pub/NetBSD * ftp://ftp.cs.umn.edu/pub/NetBSD * ftp://ftp.cslab.vt.edu/pub/NetBSD * ftp://ftp.eecs.umich.edu/pub/NetBSD * ftp://ftp.iastate.edu/pub/netbsd * ftp://ftp.op.net/pub/NetBSD SUP mirrors ----------- Australia * ftp.au.netbsd.org Instructions: ftp://sup.au.netbsd.org/pub/NetBSD/sup/README.sup Germany * ftp.de.netbsd.org Instructions: ftp://sup.de.netbsd.org/pub/NetBSD/sup/supfile.example Norway * skarven.itea.ntnu.no 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 * ftp.domino.org Instructions: See ftp://ftp.netbsd.org/pub/NetBSD/sup/README.sup USA * sup.netbsd.org Instructions: See ftp://ftp.netbsd.org/pub/NetBSD/sup/README.sup * ftp.cs.umn.edu Instructions: hostbase=/ftp/ftp/packages/NetBSD, collections are the same as on sup.NetBSD.ORG AFS mirrors ----------- USA * ftp.iastate.edu AFS path: /afs/iastate.edu/public/ftp/pub/netbsd NetBSD 1.3 Release Contents: ------ --- ------- -------- The NetBSD 1.3 release is organized in the following way: .../NetBSD-1.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 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 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 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 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 alpha-specific portion of the NetBSD 1.3 release is found in the "alpha" subdirectory of the distribution. That subdirectory is laid out as follows: .../NetBSD-1.3/alpha/ INSTALL Installation notes; this file. binary/ sets/ alpha binary distribution sets; see below. security/ alpha security distribution; see below. kernel/ alpha kernels; see below. toolchain/ alpha toolchain; see below. installation/ floppy/ alpha boot and installation floppies; see below. source/ toolchain/ Toolchain source code; see below. Bootable installation/upgrade floppies: There is a bootable floppy disk image available which contains the software necessary to prepare your hard drive for NetBSD and install the NetBSD distribution, or to upgrading an already installed system from a previous version of NetBSD. Because the kernel on the installation disks is not suitable for use beyond initial installation and configuration, a "generic" kernel has been placed in a distribution set named "kern". This kernel is intended to run your system while you build a custom kernel. It is strongly encouraged that you build a custom kernel for your installation rather than use the prebuilt generic kernel on a long term basis. Please note that the INSTALL kernel (which is booted from the install floppy or the network) is not usable for anything other than installing; it will always use as root an internal ramdisk with the install tools. Also, currently the INSTALL image only supports systems that are likely to have a floppy drive (the NoName, EB64+, EB164, AS500/600; the DECStation 3000 systems and the 8200/8400 are not supported by this floppy). If booting the INSTALL kernel from the network proves popular, we will generate another network version of the INSTALL kernel that supports more systems. The alpha toolchain: The toolchain (compiler, assembler, linker, etc.) for the alpha port is not yet integrated into the main NetBSD source tree, so the binaries for it are still distributed separately. A tar file with the toolchain can be found under binaries/toolchain, and the source can be found under source/toolchain. The toolchain installs under usr/local; to install it, just cd to the root directory and type tar -x -z --unlink -f /path/to/toolchain.tar.gz Note that the "official" toolchain we use with 1.3 is actually the snapshot build of it from 97.11.05; this is based on the sources tagged WORKING-alpha in the NetBSD source tree. The NetBSD/alpha binary distribution sets contain the binaries which comprise the NetBSD 1.3 release for the alpha. There are eight binary distribution sets and the "security" distribution set. The binary distribution sets can be found in the "alpha/binary/sets" subdirectory of the NetBSD 1.3 distribution tree, and are as follows: base The NetBSD/alpha 1.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. [ 13M gzipped, 41M uncompressed ] comp Things needed for compiling programs, other than the actual compiler programs themselves. (These are in the toolchain snapshot file described above.) This set includes the system include files (/usr/include) 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. [ 6M gzipped, 31M 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.) [ 50K gzipped, 320K uncompressed ] games This set includes the games and their manual pages. [ 3M gzipped, 8M uncompressed ] kern This set contains a NetBSD/alpha 1.3 GENERIC kernel, named "/netbsd". You MUST install this distribution set. [ 1M gzipped, 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, 10M 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. [ 2M gzipped, 9M uncompressed ] text This set includes NetBSD's text processing tools, including groff, all related programs, and their manual pages. [ 1M gzipped, 4M uncompressed ] The alpha security distribution set is named "secr" and can be found in the "alpha/binary/security" subdirectory of the NetBSD 1.3 distribution tree. It contains security related binaries which depend on cryptographic source code. You do not need this distribution set to use encrypted passwords in your password file; the "base" distribution includes a crypt library which can perform only the one-way encryption function. The security distribution includes a version of the Kerberos IV network security system, and a Kerberized version of the "telnet" program. The "secr" distribution set can be found only on those sites which carry the complete NetBSD distribution and which can legally obtain it. (Remember, because of United States law, it may not be legal to distribute this set to locations outside of the United States and Canada.) [ 1M gzipped, 3M uncompressed ] 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. NetBSD System Requirements and Supported Devices: ------ ------ ------------ --- --------- ------- NetBSD/alpha 1.3 runs on the following DEC Alpha platforms: DEC 3000/500-family systems DEC 3000/300-family systems Digital AlphaStation 200, 250, 255, and 400 systems Digital AlphaStation 500 and 600 systems Digital AXPpci systems (including UDB and Multia) EB64+-family systems (including Digital EB64+ and third-party AlphaPC 64 systems) EB164-family systems (including Digital EB164 and third-party AlphaPC 164 systems) Digital AlphaServer 8200 and 8400 systems If your system is not listed here, it is not supported in this release, but may be supported in more current versions of NetBSD. Check the alpha port web pages at for the most recent information on this, or ask on the alpha mailing list, . NetBSD/alpha requires the Digital Unix PALcode, which basically means that you need to have the SRM console installed on your machine. This console can be distinguished from the ARC console (which is used to boot Windows NT) by the fact that it has a command line interface, rather than a menu-driven interface. A basic system will fit on a 200 MB disk (including swap) without too much difficulty, but you will probably want at least 500 MB of disk to have any level of comfort. You will also need at least 32 MB of RAM, and you will probably want more than that if you're running X. We support add-in devices on the PCI, ISA, EISA and TurboChannel buses. Because NetBSD has an extremely machine-independent device driver system, many device drivers are the same as used in other ports that use the same bus. For example, the de network card driver is shared by the i386 and Alpha ports. Some drivers on inspection appear as if they will work on the alpha but have not been tested because that hardware was not available to NetBSD testers; these are marked as `UNTESTED' below. If you have one of these devices, and it does work, please get in touch with and let us know that it works. If it doesn't work, do the same thing and we can probably fix it pretty easily. Supported devices by bus type are: PCI Bus Graphics Adapters VGA-compatible video (pcivga) ZLXp-E1 video (DECchip 21030-based video, tga, NOTE: ZLXp-E2 and ZLXp-E3 boards are not supported in NetBSD 1.3.)) Network Cards DECchip 21x40-family 10 and 100 Mbps Ethernet (de) DEC DEFPA FDDI (fpa) PCI LANCE Ethernet (le, UNTESTED) Efficient Networks ENI-155p ATM (en, UNTESTED) 3Com 3c59x and 3c90x (except 3c906) 10 and 100 Mbps Ethernet (ep) Intel EtherExpress Pro 10/100B PCI Ethernet (fxp, UNTESTED) SCSI Controllers Adaptec 294x, 394x, and aic78x0 SCSI (ahc) BusLogic 9xx SCSI (bha, Works on Alpha PC164) Qlogic ISP 10x0-family SCSI (isp) NCR/Symbios 53c8xx-family SCSI (ncr, NCR825 Doesn't always work) Miscellaneous Devices Cyclades Cyclom-Y serial boards (cy, UNTESTED) PCI-PCI bridges (ppb, tested with the DECchip 21050, but should work with all bridges and system firmware revisions that comply with the PCI-PCI bridge specification) ISA Bus Network Cards 3Com 3c509 Ethernet (ep) Miscellaneous Devices PC-style parallel ports (lpt) NS16450 and NS16550 UARTs (com) ISA multi-port 16x50 boards (such as ast, boca--only boca has been tested) EISA Bus Network Cards DEC DEFEA FDDI (fea) 3Com 3c5xx series (ed, UNTESTED) SCSI Controllers Adaptec 274x and aic7770 SCSI (ahc, UNTESTED) BusLogic 7xx SCSI (bha, UNTESTED) Turbochannel Bus Graphics Adapters CFB video (PMAG-BA, cfb) SFB video (PMAGB-BA, sfb) (Note that although these boards are supported by NetBSD/alpha, since there is no keyboard or mouse support available for the TurboChannel systems, they aren't very useful.) Network Cards DEC LANCE Ethernet (PMAD-AA, le, UNTESTED) DEC DEFTA FDDI (PMAF-F, fta) Note that PC-style floppy disk drives are not supported in 1.3 (except to boot from), but are supported to some degree in NetBSD-current. Note that some devices, especially ISA-based devices, have to have certain settings set properly for the install and GENERIC kernels to detect them. (Once installed, you can always rebuild your own kernel to detect them anywhere you wish, of course.) Here is a list of such devices and the necessary settings: Device Name Port IRQ DRQ Misc ------ ---- ---- --- --- ---- Serial ports com0 0x3f8 4 [8250/16450/16550/clones] com1 0x2f8 3 [8250/16450/16550/clones] com2 0x3e8 5 [8250/16450/16550/clones] Parallel ports lpt0 0x378 7 [interrupt-driven or polling] lpt1 0x278 [polling only] lpt2 0x3bc [polling only] AHA-174x SCSI host adapters (in enhanced mode) ahb0 any any any AHA-2X4X or AIC-7XXX-based SCSI host adapters ahc0 any any any Bus Logic BT445, BT74x, or BT9xx SCSI host adapters bha0 0x330 any any bha1 0x334 any any MFM/ESDI/IDE/RLL hard disk controllers wdc0 0x1f0 14 [supports two devices] wdc1 0x170 15 [supports two devices] ATA disks wd0, wd1, ... SCSI disks sd0, sd1, ... SCSI tapes st0, st1, ... SCSI and ATAPI CD-ROMs cd0, cd1, ... For each SCSI and IDE controller found, the SCSI or ATA(PI) devices present on the bus are probed in increasing id order for SCSI and master/slave order for ATA(PI). So the first SCSI drive found will be called sd0, the second sd1, and so on ... 3COM 3x59X or 3COM 3x90X PCI Ethernet boards ep0 any any [you must assign an interrupt in your PCI BIOS, or let it do so for you] Intel EtherExpress 100 Fast Ethernet adapters fxp0 any any [you must assign an interrupt in your PCI BIOS, or let it do so for you] Getting the NetBSD System on to Useful Media: ------- --- ------ ------ -- -- ------ ----- Installation is supported from several media types, including: FTP Remote NFS partition CD-ROM No matter which installation medium you choose, you'll need to have either a 1.44 MB floppy disk (if your Alpha has a floppy drive to boot from) or you'll have to set up a server with BOOTP, TFTP and NFS to boot from as described later in this document. If you are using a UN*X-like system to write the floppy images to disks, you should use the "dd" command to copy the file system image (.fs file) directly to the raw floppy disk. It is suggested that you read the dd(1) manual page or ask your system administrator to determine the correct set of arguments to use; it will be slightly different from system to system, and a comprehensive list of the possibilities is beyond the scope of this document. If you are using DOS to write the floppy image to disk, you should use the "rawrite" utility, provided in the "i386/utilities" directory of the NetBSD distribution. It will write the file system image (.fs file) to disks. Note that, when installing or upgrading, the floppy can be write-protected if you wish. These systems mount ramdisks as their root file systems once booted, and will not need to write to the floppy itself at any time -- indeed, once booted, the floppy may be removed from the disk drive. Obviously, the steps necessary to prepare the distribution sets for installation depend on which installation medium you choose. The steps for the various media are outlined below. To install NetBSD using NFS to get the installation sets, you must do the following: Place the NetBSD distribution sets you wish to install into a directory on an NFS server, and make that directory mountable by the machine on which you are installing or upgrading NetBSD. This will probably require modifying the /etc/exports file on of the NFS server and resetting its mount daemon (mountd). (Both of these actions will probably require superuser privileges on the server.) You need to know the the numeric IP address of the NFS server, and, if the server is not on a network directly connected to the machine on which you're installing or upgrading NetBSD, you need to know the numeric IP address of the router closest to the NetBSD machine. Finally, you need to know the numeric IP address of the NetBSD machine itself. The install program will ask you to provide this information to be able to access the sets. Once the NFS server is set up properly and you have the information mentioned above, you can start the actual installation process. To install NetBSD by using FTP to get the installation sets, you must do the following: The preparations for this installation method are easy; all you make sure that there's some FTP site from which you can retrieve the NetBSD distribution when you're about to install. You need to know the numeric IP address of that site, and, if it's not on a network directly connected to the machine on which you're installing or upgrading NetBSD, you need to know the numeric IP address of the router closest to the NetBSD machine. Finally, you need to know the numeric IP address of the NetBSD machine itself. The install program will ask you to provide this information to be able to access the sets via ftp. Once you have this information, you can proceed to the actual installation. To install NetBSD by using a CD-ROM to get the installation sets, you must do the following: Have a CD-ROM with the installation sets on it, and a CD-ROM drive on your machine. If you are upgrading NetBSD, you also have the option of installing NetBSD by putting the new distribution sets somewhere in your existing file system, and using them from there. To do that, you must do the following: Place the distribution sets you wish to upgrade somewhere in your current file system tree. Please note that the /dev on the floppy used for upgrades only knows about wd0, wd1, sd0, sd1 and sd2. If you have more than two IDE drives or more than three SCSI drives, you should take care not to place the sets on the high numbered drives. At a bare minimum, you must upgrade the "base" and "kern" binary distribution, and so must put the "base" and "kern" sets somewhere in your file system. If you wish, you can do the other sets, as well, but you should NOT upgrade the "etc" distribution; the "etc" distribution contains system configuration files that you should review and update by hand. Once you have done this, you can proceed to the next step in the upgrade process, actually upgrading your system. Preparing your System for NetBSD Installation: --------- ---- ------ --- ------ ------------ There's no particular preparation necessary before installing NetBSD on your Alpha, except to make sure that if you have any data on your disks that you want to keep, you should back it up before starting. Note that NetBSD/alpha does not support having more than one operating system on a single disk, although it's fine to have multiple operating systems on your machine if you have a separate disk for NetBSD. Installing the NetBSD System: ---------- --- ------ ------ 0. Introduction This is the first release of NetBSD/alpha with regular packaging and install tools, and the installation program is still rather primitive. It also hasn't been tested very well, so there may be bugs in both it and this document. However, if you have problems, don't despair; most problems you might encounter are very easy to fix. We strongly suggest you join the port-alpha list (see the section on mailing lists on www.netbsd.org) and ask questions there if you run into any problems. Also report problem you've gotten around there or by using send-pr so that they can be fixed for the next release. 1. General The following is a walk-through of the steps you will take while getting NetBSD installed on your hard disk. It's divided into three basic components: booting NetBSD (section 2 below), preparing the disk (section 3 below), and loading the operating system files onto the disk (section 4 below). 2. Booting NetBSD You have two choices of how to boot your machine. If you have a floppy drive, you may boot from that. This is probably the simplest way of getting started. If you don't have a floppy drive, you will need to set yourself up for a boot from a file server on the network, which is a little more complex. 2.1 Making and Booting a Floppy The 3.5", 1.44 MB boot floppy image is found under the NetBSD/alpha 1.3 distribution directory in the file alpha/installation/floppy/floppy-144. You need to take this disk image and put it on a floppy disk. If you have a Unix system handy, you can do this with a command like the following: dd if=floppy-144 of=/dev/rfd0a If the Unix system you are using is not a NetBSD system, you will probably need to replace `/dev/rfd0a' with the name of the floppy device on your particular system. If you have an MS-DOS or Windows system available, you can use the `rawrite.exe' utility to transfer the image to a floppy disk. (Note that rawrite.exe doesn't work under many, if not all, Windows NT systems.) This utility is provided with the NetBSD/i386 install tools, under i386/installation/misc; a documentation file, `rawrite.doc' is available there as well. Once the floppy has been made, you simply need to put it in the drive and type boot dva0 Now you may skip to section 3. 2.2 Booting over the Network Booting NetBSD/alpha 1.3 over a network requires a BOOTP server, a TFTP server and an NFS server. (These are usually all run on the same machine.) There are three basic stages to the boot: 1.The Alpha console software sends a BOOTP request to get its own address, the address of the TFTP server and the file to download. It downloads this file, which is the second stage bootstrap, via TFTP and then executes it. 2.The second stage bootstrap uses further information in the BOOTP packet that the console received to find the NFS server and path and retreive the kernel (the file /netbsd). After loading the kernel into memory, it executes it. 3.The kernel probes and configures the devices, and then sends out another BOOTP request so it can find out its address, the NFS server, and path. (The kernel probably should get this information from the console, but it currently doesn't.) It then mounts its root via NFS and continues. 2.2.1 Setting Up the Server You will need to set up your server to serve BOOTP, TFTP and NFS. The NFS setup is quite simple. If you want to run a full system from the network, untar the NetBSD snapshot or distribution into a directory on your server and NFS export that directory to the client. (Make sure you put a kernel there as well, and create the device nodes in /dev with `sh ./MAKEDEV all'. In fact, see the full instructions available off the alpha port page at www.netbsd.org.) You'll want to map root to `root' (rather than the default `nobody') when you export your root filesystem. A typical /etc/exports line on a NetBSD system would be: /usr/export/alpha -maproot=0 myclient.mydom.com If you just want to get the install kernel loaded so that you can download sets to the local hard drive of that machine, you need nothing other than the install kernel in the NFS root directory on your server. For the TFTP setup, you need to copy the second stage bootstrap, netboot, into an appropriately named file (I use boot.netbsd.alpha) in the directory used by your TFTP server. If you extracted a full snapshot, you can get the netboot program from /usr/mdec/netboot; if not, you can get this from the installation/netboot directory where you found the alpha distribution. For the BOOTP server you need to specify the: hardware type (Ethernet) hardware address (Ethernet MAC address) IP address of the client subnet mask of the client address of of the TFTP/NFS server name of the second stage bootstrap loaded via TFTP path to the root for the client (mounted via NFS) Here's an example for a Unix system running bootpd: myhost.mydom.com:\ :ht=ethernet:ha=0000c0391ae4:\ :ip=192.168.1.2:sm=255.255.255.0:\ :sa=192.168.1.1:bf=boot.netbsd.alpha:rp=/usr/export/alpha: And here's an example for a Unix system running dhcpd: host axp { hardware ethernet 0:0:c0:39:1a:e4; fixed-address 192.168.1.2; option host-name "myhost.mydom.com"; filename "boot.netbsd.alpha"; option root-path "/usr/export/alpha"; option domain-name-servers 192.168.1.1; option broadcast-address 255.255.255.0; option domain-name "my.domain"; } 2.2.2 The Alpha Console The only Ethernet device the console on most Alpha systems knows how to boot from is the onboard Ethernet interface or a DEC Tulip (21040, 21041, 21140) based PCI Ethernet card. Some older SMC 100 Mbps card that use this chip have been known to work as well. Many older systems will not be able to use the newer 2.0 stepping of the 21140, however. If your system appears not to be receiving packets, this may be the problem. (You may or may not be able to update your firmware to fix this; see the alpha port pages on www.netbsd.org for more information on this.) Once you're set up, you should be able to boot with: boot -proto bootp ewa0 (The command may be different on some very old machines.) 3. Preparing the Disk If you're going to be running a diskless machine, the steps so far have prepared you to run, and you can skip to section 5 ("Configuration") below. If you are going to run NetBSD from a local hard drive, however, this hard drive needs to be prepared. This preparation consists of putting a label on the disk, which includes information on the sizes and placement of the partition into which the disk is divided, putting the boot blocks on the disk, and initialising the filesystems on the partitions. This work is done by the `install' script from the boot floppy (or boot kernel, if you booted it via NFS with the INSTALL kernel). 3.1 Running Install When you first boot the INSTALL kernel you will be given the options of `install' or `shell'. Choose `install' and the install script will start. If, at any time, you have made a mistake in the install script and want to abort, press ^C. This will take you to a shell prompt. You can then restart the install script by typing `/install', or halt the machine by typing `halt'. 3.1 Answering the Install Questions These will for the most part be fairly obvious. You may install on either a SCSI or an IDE disk, and you will be prompted for the disk to install on. The disks in your system will be numbered starting at xd0 (where x is an `s' for SCSI disks, `w' for IDE disks) based on the SCSI ID or IDE drive order; if you have more than one disk, watch the boot messages carefully to see which ones are probed as which numbers. Once you've selected a disk to install on, you'll be prompted for the geometry. This is also displayed in the boot messages, and you'll be given a chance to review the boot messages again to get the exact figures for the number of cylinders, heads and sectors. After this you must specify the size of your partitions. Generally you'll be giving the sizes in cylinders; the install program will tell you how many bytes there are in each cylinder. The swap partition is the second thing you specify, after the root partition. Regardless of the size of your disk, you'll want to specify a swap partition that's at least as large as the amount of RAM you have, and probably not less than 64 MB in any case. If you have a small disk (under 500 MB), it's probably best to devote all of the disk (excepting 64 MB or more for the swap) to the root partition. If you have more space, we recommend devoting at least 32 MB, and preferably 48 MB, to the root partition. /usr will need 150 MB or so if you're not installing X, 200 MB or so if you are. Once you've specified this information, the install script will write the disklabel, install boot blocks to make the disk bootable, initialise the filesystems, and mount them all under /mnt. You're now ready to go on to the next step. 4. Installing NetBSD To install NetBSD you'll have to get access to the tar files that contain the operating system, and extract them to your disk. You can get access to the tar files through either a network or from a CD-ROM. 4.1 Preparing to Install from a CD-ROM All you need to do is mount the CD-ROM, which will generally be device cd0. (The initial boot messages will tell you what the CD-ROM drive as probed as.) This would be done with: mount -r -t cd9660 /dev/cd0a /mnt2 4.2 Preparing to Install from the Network The first thing you need to do is configure the loopback network interface, which is done with the command ifconfig lo0 127.0.0.1 Then you will have to configure your Ethernet card. The command ifconfig -l will give you a list of the network interfaces on your system. It will show you your ethernet cards first, followed by lo0 (the loopback interface that we configured above), ppp0 (the PPP interface) and sl0 (the SLIP interface). To configure your ethernet card, type ifconfig inet [netmask ] [media ] Where is the network card (interface), is the IP address, the optional parameter is the network mask, and the optional parameter is one of: 10base2 BNC connector, 10 Mbps AUI AUI connector, 10 Mbps 10baseT Twisted pair connector, 10 Mbps 100baseTX Twisted pair connector, 100 Mbps 100baseFX Fibre-optic connector, 100 Mbps 100baseT4 T4 twisted pair interface, 100 Mbps If the host you are getting the data files from is not on the local network, you will also have to configure a gateway into your system. Do this with route add default If you will need name services you can set up a /etc/resolv.conf file for those with a `nameserver ' line in it, e.g.: echo "nameserver 198.41.0.4" >>/etc/resolv.conf Once networking has been configured, you may mount the directory with the install files via NFS, or download them via FTP. To mount them via nfs, type mount -t nfs /mnt2 If this volume has been exported read-only, you may need the `-r' option to mount. To download the install sets with ftp, create a directory in which to put them and then use the ftp client to download them. A typical session might be: mkdir /mnt/var/tmp cd /mnt/var/tmp ftp ftp.netbsd.org [all the following commmands are given to the ftp program after logging in] prompt cd /pub/NetBSD/NetBSD-1.3/alpha/binary/sets mget * cd /pub/NetBSD/NetBSD-1.3/alpha/binary/kernel get netbsd-GENERIC.gz cd /pub/NetBSD/NetBSD-1.3/alpha/binary/toolchain get netbsd-GENERIC.gz bye Feel free, of course, to leave off the sets that you don't need if you don't plan to install everything. You are now ready to proceed to step 4.3. 4.3 Extracting the Operating System Files This is quite simple. Change to the root directory of your hard drive (which is /mnt if you've used the standard install script to this point) by typing cd /mnt Then extract the kernel with: zcat /mnt/var/tmp/netbsd-GENERIC.gz >/mnt/netbsd For this and the following commands, replace `/mnt/var/tmp/' with the path to your NFS volume or CD-ROM if that's how you chose to access your install files instead. The sets are extracted with for file in base comp etc games man misc text; do tar --unlink -t -z -f /mnt/var/tmp/$file; done and the toolchain with tar --unlink -t -z -f /mnt/var/tmp/toolchain.tar.gz You will now be ready to reboot from your hard disk. Type `sync' twice to make sure all the data is written out to disk and then type `halt' to halt your system and go back to the monitor. At this point you should be able to reboot your system with boot dka0 (or `boot dka100' if your disk drive is on ID 1, etc.--you can usually use `show device' to see a full list of bootable devices in your system). Your system will come up in single-user mode, ready for you to configure it. 5. Configuring NetBSD Configuring your NetBSD system requires editing the /etc/rc.conf file. Most of this file is fairly self-explanatory, but you can `man rc.conf' for further explanations. Remember to set `rc_configured' to YES so you will boot multi-user, set `hostname' and possibly `defaultroute', and add an ifconfig_int for your interface , along the lines of ifconfig_de0="inet myname.my.dom 123.45.67.89 netmask 255.255.255.0" You will also want either to run named or add an /etc/resolv.conf file (`man resolv.conf' for information on this), use `vipw' to add accounts to your system, edit /etc/aliases to forward root mail to the right place (run `newaliases' afterwards) and edit /etc/rc.local to run any local daemons you use. Upgrading a previously-installed NetBSD System: --------- - ---------- --------- ------ ------ The upgrade to NetBSD 1.3 is a binary upgrade; it would be prohibitive to make users upgrade by compiling and installing the 1.3 sources, and it would be very difficult to even compile a set of instructions that allowed them to do so. Because of the many changes to the system, it is difficult and impractical to upgrade by recompiling from the sources and installing. Since upgrading involves replacing the boot blocks on your NetBSD partition, the kernel, and most of the system binaries, it has the potential to cause data loss. You are strongly advised to BACK UP ANY IMPORTANT DATA ON YOUR DISK, whether on the NetBSD partition or on another operating system's partition, before beginning the upgrade process. The upgrade is done entirely `by hand.' You will need first to boot the new boot floppy or INSTALL kernel and use /usr/mdec/install to install new boot blocks. Then you may extract a new kernel and the distribution sets as described in section 5 of the installation instructions. After this point your machine is a complete NetBSD 1.3 system. However, that doesn't mean that you're finished with the upgrade process. You will probably want to update the set of device nodes you have in /dev. If you've changed the contents of /dev by hand, you will need to be careful about this, but if not, you can just cd into /dev, and run the command "sh ./MAKEDEV all". You must also deal with certain changes in the formats of some of the configuration files. The most notable change is that we now have an /etc/rc.conf file which describes most configuration options, but also the "options" given to many of the file systems in /etc/fstab or by hand have changed, and some of the file systems have changed names. To find out what the new options are, it's suggested that you read the manual page for the file systems' mount commands, for example mount_nfs(8) for NFS. Finally, you will want to delete old binaries that were part of the version of NetBSD that you upgraded from and have since been removed from the NetBSD distribution. Especially important, if you use NFS, is removing /sbin/nfsd and /sbin/nfsiod; the new versions of these programs are in /usr/sbin. 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: * 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: J.T. Conklin Charles Hannum Paul Kranenburg Jason Thorpe Christos Zoulas The port-masters (and their ports): Mark Brinicombe (arm32) Jeremy Cooper (sun3x) Chuck Cranor (mvme68k) Charles Hannum (i386) Chris Hopps (amiga) Paul Kranenburg (sparc) Anders Magnusson (vax) Phil Nelson (pc532) Masaru Oki (x68k) Scott Reynolds (mac68k) Gordon Ross (sun3, sun3x) Jonathan Stone (pmax) Jason Thorpe (hp300) Frank van der Linden (i386) Leo Weppelman (atari) The NetBSD 1.3 Release Engineering team: Ted Lemon Perry Metzger Jason Thorpe Supporting cast: Steve Allen Lennart Augustsson Christoph Badura John Birrell Manuel Bouyer John Brezak Allen Briggs Aaron Brown David Brownlee Simon Burge Dave Burgess Dave Carrel Bill Coldwell Alistair Crooks Rob Deker Chris G. Demetriou Matthias Drochner Bernd Ernesti Erik Fair Hubert Feyrer Brian R. Gaeke Justin Gibbs Adam Glass Michael Graff Brad Grantham Matthew Green Juergen Hannken-Illjes Michael L. Hitch Marc Horowitz Matthew Jacob Lonhyn T. Jasinskyj Lawrence Kesteloot Klaus Klein John Kohl Kevin Lahey Ted Lemon Mike Long Paul Mackerras SAITOH Masanobu Neil J. McRae Perry Metzger Luke Mewburn der Mouse Herb Peyerl Matthias Pfaller Chris Provenzano Waldi Ravens Darren Reed Kazuki Sakamoto Curt Sampson Wilfredo Sanchez Karl Schilke (rAT) Thor Lancelot Simon Noriyuki Soda Wolfgang Solfrank Bill Sommerfeld Ignatios Souvatzis Bill Studenmund Kevin Sullivan Matt Thomas Enami Tsugutomo Todd Vierling Paul Vixie 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 Charles Hannum. 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 the University of Vermont and State Agricultural College and Garrett A. Wollman. This product includes software developed by Dean Huxley. This product includes software developed by Herb Peyerl. In the following statement, "This software" refers to the parallel port driver: This software is a component of "386BSD" developed by William F. Jolitz, TeleMuse.