INSTALL(8) NetBSD System Manager's Manual INSTALL(8) NAME INSTALL -- Installation procedure for NetBSD/sgimips. CONTENTS About this Document............................................2 What is NetBSD?................................................2 Changes Between The NetBSD 8.1 and 8.2 Releases................3 Features to be removed in a later release......................3 The NetBSD Foundation..........................................3 Sources of NetBSD..............................................3 NetBSD 8.2_STABLE Release Contents.............................3 NetBSD/sgimips subdirectory structure.......................5 Binary distribution sets....................................5 NetBSD/sgimips System Requirements and Supported Devices.......8 Supported machines..........................................8 Unsupported machines........................................8 Supported devices...........................................8 Unsupported devices.........................................9 Getting the NetBSD System on to Useful Media...................9 Preparing your System for NetBSD installation.................11 Installing the NetBSD System..................................12 Install via a bootable CD-ROM..............................13 Installation for diskless configurations...................13 Installation to local disk from the network................14 Once you've booted the diskimage...........................14 Running the sysinst installation program...................14 Introduction............................................14 General.................................................14 Quick install...........................................15 Booting NetBSD..........................................16 Network configuration...................................16 Installation drive selection and parameters.............16 Selecting which sets to install.........................16 Partitioning the disk...................................16 Preparing your hard disk................................17 Getting the distribution sets...........................17 Installation from CD-ROM................................18 Installation using FTP..................................18 Installation using NFS..................................18 Installation from an unmounted file system..............18 Installation from a local directory.....................19 Extracting the distribution sets........................19 Configure additional items..............................19 Finalizing your installation............................19 Post installation steps.......................................19 Upgrading a previously-installed NetBSD System................22 Compatibility Issues With Previous NetBSD Releases............23 Issues affecting an upgrade from NetBSD 5.x releases.......23 Issues affecting an upgrade from NetBSD 6.x releases.......23 Issues affecting an upgrade from NetBSD 7.x releases.......23 Using online NetBSD documentation.............................23 Administrivia.................................................24 Thanks go to..................................................25 We are........................................................25 Legal Mumbo-Jumbo.............................................32 The End.......................................................39 DESCRIPTION About this Document This document describes the installation procedure for NetBSD 8.2_STABLE on the sgimips platform. It is available in four different formats titled INSTALL.ext, where .ext is one of .ps, .html, .more, or .txt: .ps PostScript. .html Standard Internet HTML. .more The enhanced text format used on UNIX-like systems by the more(1) and less(1) pager util- ity programs. This is the format in which the on-line man pages are generally presented. .txt Plain old ASCII. You are reading the ASCII version. What is NetBSD? The NetBSD Operating System is a fully functional Open Source UNIX-like operating system derived from the Univer- sity of California, Berkeley Networking Release 2 (Net/2), 4.4BSD-Lite, and 4.4BSD-Lite2 sources. NetBSD runs on many different different system architectures (ports) across a variety of distinct CPU families, and is being ported to more. The NetBSD 8.2_STABLE release contains complete binary releases for most of these system architectures, with preliminary support for the others included in source form. Please see the NetBSD website at http://www.NetBSD.org/ for information on them.) NetBSD is a completely integrated system. In addition to its highly portable, high performance kernel, NetBSD fea- tures a complete set of user utilities, compilers for sev- eral languages, the X Window System, firewall software and numerous other tools, all accompanied by full source code. NetBSD is a creation of the members of the Internet commu- nity. Without the unique cooperation and coordination the net makes possible, NetBSD would not exist. Changes Between The NetBSD 8.1 and 8.2 Releases The NetBSD 8.2_STABLE release is the first security/critical update of the NetBSD 8 release branch. It represents a selected subset of fixes deemed important for security or stability reasons. The complete list of changes can be found in the CHANGES-8.2: https://cdn.netbsd.org/pub/NetBSD/NetBSD-8.2/CHANGES-8.2 file in the top level directory of the NetBSD 8.2_STABLE release tree. The release anouncements, status, updates and links to other resources can be found at https://www.netbsd.org/releases/formal-8/ Features to be removed in a later release The following features are to be removed from NetBSD in the future: o dhclient(8) in favor of dhcpcd(8). o groff(1). Man pages are now handled with mandoc(1), and groff(1) can still be found in pkgsrc as textproc/groff. o rtsol(8) and rtsold(8). The NetBSD Foundation The NetBSD Foundation is a tax exempt, not-for-profit 501(c)(3) corporation that devotes itself to the traditional goals and Spirit of the NetBSD Project and owns the trade- mark of the word ``NetBSD''. It supports the design, devel- opment, and adoption of NetBSD worldwide. More information on the NetBSD Foundation, its composition, aims, and work can be found at: http://www.NetBSD.org/foundation/ Sources of NetBSD Refer to http://www.NetBSD.org/mirrors/ NetBSD 8.2_STABLE Release Contents The root directory of the NetBSD 8.2_STABLE release is orga- nized as follows: .../NetBSD-8.2_STABLE/ CHANGES Changes between the 7.0 and 8.0 releases. CHANGES-8.0 Changes between the initial 8.0 branch and final release of 8.0. CHANGES-8.1 Changes between the 8.0 release and the 8.1 release. CHANGES-8.2 Changes between the 8.1 release and the 8.2 release. CHANGES.prev Changes in previous NetBSD releases. LAST_MINUTE Last minute changes and notes about the release. README.files README describing the distribution's contents. images/ Images (ISO 9660 or USB) for installing NetBSD. Depending on your system, these may be bootable. 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 architec- tures for which NetBSD 8.2_STABLE has a binary distribution. 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 dis- tribution sets are as follows: gnusrc This set contains the ``gnu'' sources, including the source for the compiler, assembler, groff, and the other GNU utilities in the binary distribution sets. sharesrc This set contains the ``share'' sources, which include the sources for the man pages not associ- ated with any particular program; the sources for the typesettable document set; the dictionaries; and more. src This set contains all of the base NetBSD 8.2_STA- BLE sources which are not in gnusrc, sharesrc, or syssrc. syssrc This set contains the sources to the NetBSD 8.2_STABLE kernel for all architectures as well as the config(1) utility. xsrc This set contains the sources to the X Window Sys- tem. All the above source sets are located in the source/sets subdirectory of the distribution tree. The source sets are distributed as compressed tar files. Except for the pkgsrc set, which is traditionally unpacked into /usr/pkgsrc, all sets may be unpacked into /usr/src with the command: # cd / ; tar -zxpf set_name.tgz In each of the source distribution set directories, there are files which contain the checksums of the files in the directory: MD5 MD5 digests in the format produced by the com- mand: cksum -a MD5 file. SHA512 SHA512 digests in the format produced by the command: cksum -a SHA512 file. The SHA512 digest is safer, but MD5 checksums are provided so that a wider range of operating systems can check the integrity of the release files. NetBSD/sgimips subdirectory structure The sgimips-specific portion of the NetBSD 8.2_STABLE release is found in the sgimips subdirectory of the distri- bution: .../NetBSD-8.2_STABLE/sgimips/. It contains the following files and directories: INSTALL.html INSTALL.ps INSTALL.txt INSTALL.more Installation notes in various file formats, including this file. The .more file contains underlined text using the more(1) conventions for indicating italic and bold display. binary/ kernel/ netbsd-GENERIC32_IP12.gz A kernel suitable for booting on R3000 Indigo, IRIS 4D/3x and similar machines. netbsd-GENERIC32_IP12.ecoff.gz GENERIC32_IP2x targeted for being bootable on the above machines with PROMs that do not understand the ELF binary format. netbsd-GENERIC32_IP2x.gz A kernel suitable for booting on Indy, Indigo 2 and similar machines. netbsd-GENERIC32_IP2x.ecoff.gz GENERIC32_IP2x targeted for being bootable on older Indigo 2 and possi- bly Indy machines with PROMs that do not under- stand the ELF binary for- mat. netbsd-GENERIC32_IP3x.gz A kernel suitable for booting on O2. sets/ sgimips binary distribution sets; see below. installation/ netboot/ NFS-root images Binary distribution sets The NetBSD sgimips binary distribution sets contain the binaries which comprise the NetBSD 8.2_STABLE release for sgimips. The binary distribution sets can be found in the sgimips/binary/sets subdirectory of the NetBSD 8.2_STABLE distribution tree, and are as follows: base The NetBSD 8.2_STABLE sgimips base binary distribu- tion. You must install this distribution set. It contains the base NetBSD utilities that are neces- sary for the system to run and be minimally func- tional. comp Things needed for compiling programs. 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. debug This distribution set contains debug information for all base system utilities. It is usefull when reporting issues with binaries or during develope- ment. This set is huge, if the target disk is small, do not install it. etc This distribution set contains the system configu- ration 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. games This set includes the games and their manual pages. kern-GENERIC32_IP2x This set contains a NetBSD/sgimips 8.2_STABLE GENERIC32_IP12 kernel (for R3000 Indigo, IRIS 4D/3x machines), named /netbsd. This set also contains an ECOFF kernel named /netbsd.ecoff that your sys- tem may need to boot. kern-GENERIC32_IP2x This set contains a NetBSD/sgimips 8.2_STABLE GENERIC32_IP2x kernel (for Indy, Indigo 2 and Chal- lenge S/M machines), named /netbsd. This set also contains an ECOFF kernel named /netbsd.ecoff that your system may need to boot. kern-GENERIC32_IP3x This set contains a NetBSD/sgimips 8.2_STABLE GENERIC32_IP3x kernel (for O2), named /netbsd. You must install one of these distribution sets for your machine. 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 man- ual pages that are included in the other sets. misc This set includes the system dictionaries, the typesettable document set, and other files from /usr/share. modules This set includes kernel modules to add functional- ity to a running system. text This set includes NetBSD's text processing tools, including groff(1), all related programs, and their manual pages. NetBSD maintains its own set of sources for the X Window System in order to assure tight integration and compatibil- ity. These sources are based on X.Org. Binary sets for the X Window System are distributed with NetBSD. The sets are: xbase The basic files needed for a complete X client environment. This does not include the X servers. xcomp The extra libraries and include files needed to compile X source code. xdebug This distribution set contains debug information for all X11 binaries. It is usefull when reporting issues with these binaries or during developement. This set is huge, if the target disk is small, do not install it. xfont Fonts needed by the X server and by X clients. xetc Configuration files for X which could be locally modified. xserver The X server. The sgimips binary distribution sets are distributed as gzipped tar files named with the extension .tgz, e.g. base.tgz. 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 filenames stored in the sets are relative and therefore the files are extracted below the current directory. Therefore, if you want to extract the binaries into your system, i.e. replace the system binaries with them, you have to run the tar -xzpf command from the root directory ( / ) of your system. The following are included in the sgimips/installation directory: diskimage/ diskimage.gz FFS disk image of the installa- tion filesystem. netboot/ diskimage.tgz Minimal file set necessary for NFS-root installations; to be extracted on the NFS server. The following are included in the sgimips/binary/kernel directory: netbsd-GENERIC32_IPxx.ecoff.gz An ECOFF version of the GENERIC32_IPxx kernel (gzipped). This kernel can be used when booting machines whose PROMs do not understand the ELF binary format. netbsd-INSTALL32_IPxx.gz A gzipped INSTALL32_IPxx kernel, which includes an embedded ramdisk with the installation tools. netbsd-INSTALL32_IPxx.ecoff.gz An ECOFF version of the netbsd-INSTALL32_IPxx kernel (also gzipped). netbsd-INSTALL32_IPxx.symbols.gz Symbols for netbsd-INSTALL32_IPxx.gz. Note: Each directory in the sgimips binary distribution also has its own checksum files, just as the source distribution does. NetBSD/sgimips System Requirements and Supported Devices NetBSD/sgimips is aimed to run on MIPS-based computers manu- factured by SGI. Supported machines o IP12 R3000 - Indigo, Personal Iris 4D/30, Personal Iris 4D/35 o IP20 R4000/R4400 - Indigo o IP22 R4000/R4400/R4600 - Challenge M, Challenge S, Indigo 2 and Indy o IP22 R5000 - Challenge S, Indy o IP32 R5000 - O2 o IP32 R10000 - O2 Unsupported machines o IP19 R4000 - Challenge Onyx o IP21 R8000 - Power Challenge / Power Onyx o IP25 R10000 - Power Challenge 10000 / Power Onyx 10000 o IP26 R8000 - Indigo 2 R8000 o IP27 R10000/R12000 - O200 / Origin 2000 / Onyx2 o IP28 R10000 - Indigo 2 R10000 o IP30 R10000/R12000 - Octane o IP35 R12000A - Origin 3000 / Onyx 3000 Supported devices o Serial ports - On-board Zilog Z8530 Dual Uart (IP12, IP20, IP22/24) (ttyz), - On-board 16C550 Serial ports (IP32). (ttyC). o Ethernet - On-board SGI Seeq 80c03 ethernet controller (IP12, IP20, IP22/24) (sq), - Phobos G100/G130/G160 Fast Ethernet adapters (IP20, IP22/IP24) (tlp), - On-board MACE Ethernet controller (IP32) (mec), - Most PCI Ethernet controllers (IP32) o SCSI - On-board Western Digital WD33C93 SCSI con- troller(s) (IP12, IP20, IP22/24) (wdsc), - On-board Adaptec AIC-7889 SCSI controller (IP32) (aic), o Audio - On-board HAL2 controller (IP22/24) (haltwo) o Graphics adapters - SGI CRIME (Found in O2s) (crmfb), - SGI NG1 "newport" (IP22/24) (newport), - SGI GR2 (various models) (grtwo) o Keyboard and mouse devices - PC keyboard/mouse controller (IP22/24) (pckbc) - zs keyboard/mouse controller (IP12/20) (zs) o Miscellaneous Devices - On-board Parallel Port (IP22/24) (pi1ppc) Unsupported devices o Some graphics adapters o Video hardware o Some parallel ports Getting the NetBSD System on to Useful Media Installation is supported from several media types, includ- ing: o CD-ROM / DVD / USB-stick o FTP o Remote NFS partition o Tape o Existing NetBSD partitions, if performing an upgrade The steps necessary to prepare the distribution sets for installation depend upon which installation medium you choose. The steps for the various media are outlined below. CD-ROM / DVD / USB-stick Find out where the distribution set files are on the CD-ROM, DVD or USB stick. Likely locations are binary/sets and sgimips/binary/sets. (You only need to know this if you are mix- ing installer and installation media from different versions - the installer will know the proper default location for the sets it comes with). Proceed to the instructions on installation. FTP The preparations for this instal- lation/upgrade method are easy; all you need to do is make sure that there's an FTP site from which you can retrieve the NetBSD distribution when you're about to install or upgrade. If you don't have DHCP available on your net- work, you will 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. Once you have this information, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrad- ing. NFS Place the NetBSD distribution sets you wish to install into a direc- tory on an NFS server, and make that directory mountable by the machine on which you are installing or upgrading NetBSD. This will probably require modify- ing the /etc/exports file on 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 numeric IP address of the NFS server, and, if you don't have DHCP available on your network and 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. Once the NFS server is set up properly and you have the informa- tion mentioned above, you can pro- ceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on pre- paring your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading. Tape To install NetBSD from a tape, you need to make a tape that contains the distribution set files, in `tar' format. If you're making the tape on a UNIX-like system, the easiest way to do so is probably something like: # tar -cf tape_device dist_sets where tape_device is the name of the tape device that represents the tape drive you're using. This might be /dev/rst0, or something similar, but it will vary from system to system. In the above example, dist_sets is a list of filenames corresponding to the distribution sets that you wish to place on the tape. For instance, to put the kern-GENERIC, base, and etc distributions on tape (the absolute minimum required for installation), you would do the following: # cd .../NetBSD-8.2_STABLE # cd sgimips/binary # tar -cf tape_device kern-GENERIC.tgz base.tgz etc.tgz Note: You still need to fill in tape_device in the example. Once you have the files on the tape, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installa- tion, go directly to the section on upgrading. Preparing your System for NetBSD installation First and foremost, before beginning the installation process, make sure you have a reliable backup of any data (e.g., an old IRIX installation) you wish to preserve. Booting NetBSD/sgimips for the first time is most commonly done from the network. You must set up DHCP, TFTP, and pos- sibly NFS for the installation procedure to be successful. Although newer SGI bootproms can read ELF kernels directly from the network, others require that you boot an ECOFF ver- sion of the kernel. Attempting to boot an ELF kernel on a system with a PROM that only supports ECOFF binaries will result in the following message being displayed by the PROM: Illegal f_magic number 0x7f45, expected MIPSELMAGIC or MIPSEBMAGIC. You can convert the standard ELF format kernel into an ECOFF kernel using the objcopy tool. Note that some older bootproms have an interesting bug in reading the kernel via TFTP. They handle the port number as a signed entity, and can thus not connect to ports >32767. You can work around this problem on the TFTP server (given that it is a NetBSD host) by using ``sysctl'' to set ``net.inet.ip.anonportmin'' and ``net.inet.ip.anonportmax'' to more suitable values. For example: # sysctl -w net.inet.ip.anonportmin=16384 # sysctl -w net.inet.ip.anonportmax=32767 # cu -l /dev/ttyXX where XX is the serial port used on your remote machine (usually /dev/tty00 or /dev/tty01). Enter the Command Moni- tor from the System Maintenance Menu. In order to boot the kernel properly you also have to modify the PROM environment with > setenv console serial Afterwards, just continue with the normal installation pro- cedure. Installing the NetBSD System To install or upgrade NetBSD, you need to first boot an installation program and then interact with the screen-menu program sysinst. The installation program actually consists of the NetBSD kernel plus an in-memory file system of util- ity programs. The installation methods are: 1. Installation from an existing NetBSD or IRIX system by booting the install kernel from an existing file sys- tem. 2. Installation in a diskless environment. This means that you will install your entire system onto a remotely shared disk. 3. Booting the install kernel over the network and installing onto a local disk. The beginning of the procedure is similar to diskless installation, but you will eventually end up writing the system onto your local disk. You should familiarize yourself with the console PROM envi- ronment and the hardware configuration. A good place to study PROM tricks is the IRIX "prom" manual page. Be sure you know how to print the configuration of your machine, and how to boot from disk or network, as appropriate. To boot from disk, use: o All machine types: >> setenv systempartition scsi(0)disk(X)rdisk(0)partition(8) >> setenv osloadpartition scsi(0)disk(X)rdisk(0)partition(0) >> setenv osloadfilename netbsd >> setenv osloadoptions auto >> setenv osloader boot For all drives (including all SCSI-2 drives), the kernel should correctly detect the disk geometry. If you're installing NetBSD/sgimips for the first time it's a very good idea to pre-plan partition sizes for the disks onto which you're installing NetBSD. Changing the size of partitions after you've installed is difficult. If you do not have a spare bootable disk, it may be simpler to re- install NetBSD again from scratch. To be able to boot from local disk an SGI Volume Header par- tition is required. This special partition is accessed by the PROM to load the NetBSD/sgimips boot program. The par- tition should be about 2 MB in size, but can be reduced somewhat. The minimum size can approach 150k, but this doesn't leave room for upgrade boot programs. Install via a bootable CD-ROM The NetBSD/sgimips CD-ROM is not ISO-formatted. Since SGI PROMs can not boot from an ISO/CD-9660 filesystem, the CD- ROM image is generated with an SGI Volume Header for the bootstrap loader and an ISO/CD-9660-formatted partition for the distribution. To install from a NetBSD/sgimips CD-ROM, enter the PROM com- mand-line environment and execute one of the following com- mands, replacing X with the SCSI-ID of the CD-ROM: (for most Indigo2 (IP22) and Indy (IP24) machines) >> boot -f scsi(0)cdrom(X)rdisk(0)partition(8)ip2xboot (for Indigo (IP20) and Indigo2/Indy machines with old PROMs) >> boot -f scsi(0)cdrom(X)rdisk(0)partition(8)aoutboot (for O2 (IP32) machines) >> boot -f pci(0)scsi(0)cdrom(X)rdisk(0)partition(8)ip3xboot Installation for diskless configurations This section assumes you know how to configure DHCP, TFTP, and NFS services on your server. 1. Place the kernel into the TFTP server's download area. If the kernel has a ``.gz'' suffix, you must first uncompress it using the gunzip program. You must also decide which kernel you need to boot. Because of dif- ferences in SGI hardware between different machines, the kernel load addresses differ. You will need GENERIC32_IP2x for the Indy and Indigo2, GENERIC32_IP2x.ecoff for the Indigo (and Indy/Indigo2 machines with old PROMs), and GENERIC32_IP3x for the O2. server# gzip -d -c netbsd-GENERIC32_IP2x.gz > /tftpboot/netbsd-sgimips or server# gzip -d -c netbsd-GENERIC32_IP2x.ecoff.gz > /tftpboot/netbsd-sgimips or server# gzip -d -c netbsd-GENERIC32_IP2x.gz > /tftpboot/netbsd-sgimips Note that your DHCP server must be configured to spec- ify this file as the boot file for the client. 2. Unpack the distribution sets into the client's root directory on the server. server# cd /export/client/mipseb server# gzcat .../base.tgz | tar xvpf - server# gzcat .../etc.tgz | tar xvpf - [ repeat for all sets you wish to unpack ] 3. Load the kernel from the TFTP server: >> setenv SystemPartition bootp(): >> setenv netaddr your.ip.here.please >> boot The installation of your diskless NetBSD/sgimips system is now complete! You may now skip ahead to any post-installa- tion instructions. Installation to local disk from the network This section is a subset of the above section, and also assumes that you know how to configure DHCP and TFTP ser- vices on your server. 1. Place the install kernel into the TFTP server's down- load area. Just as above, you need to place the cor- rect bootable kernel into the TFTP server's download area. However, instead of a GENERIC kernel, you must use the correct INSTALL kernel. This kernel contains a ramdisk with the installation tools and will allow you to proceed with installation without further setup. If the kernel has a ``.gz'' suffix, you must first uncompress it using the gunzip program. As above, you must choose either the netbsd-INSTALL32_IP2x, netbsd- INSTALL32_IP2x.ecoff, or netbsd-INSTALL32_IP3x kernel. Note that your DHCP server must be configured to spec- ify this file as the boot file for the client. 2. Load the kernel from the TFTP server: >> setenv SystemPartition bootp(): >> setenv netaddr your.ip.here.please >> boot Once you've booted the diskimage Once you've booted the installation kernel you will need to select your terminal type. Use vt100 for a serial console with a vt100-compatible terminal, or xterm or xterms for a tip(1) or cu(1) connection running in an xterm(1). The system will then start the sysinst program. Running the sysinst installation program 1. Introduction Using sysinst, installing NetBSD is a relatively easy process. Still, you should read this document and have it available during the installation process. This document tries to be a good guide to the installation, and as such, covers many details for the sake of com- pleteness. Do not let this discourage you; the install program is not hard to use. 2. General The following is a walk-through of the steps you will take while installing NetBSD on your hard disk. sysinst is a menu driven program that guides you through the installation process. Sometimes questions will be asked, and in many cases the default answer will be displayed in brackets (``[ ]'') after the ques- tion. If you wish to stop the installation, you may press CONTROL-C at any time, but if you do, you'll have to begin the installation process again from scratch by running the /sysinst program from the command prompt. It is not necessary to reboot. 3. Quick install First, let's describe a quick install. The other sec- tions of this document go into the installation proce- dure in more detail, but you may find that you do not need this. If you want detailed instructions, skip to the next section. This section describes a basic installation, using a CD / DVD as the install media. o What you need. - The distribution sets (in this example, they are on the CD or DVD). - A minimum of 16 MB of memory installed. - An optical drive. - A hard drive with at least 600 MB of free space for a complete base install, not including room for swap. If you wish to install the X Window System as well, you will need at least 225 MB more. o The Quick Installation - Boot the system as described above. You should be at the sysinst main menu. .***********************************************. * NetBSD-8.2_STABLE Install System * * * *>a: Install NetBSD to hard disk * * b: Upgrade NetBSD on a hard disk * * c: Re-install sets or install additional sets * * d: Reboot the computer * * e: Utility menu * * f: Config menu * * x: Exit Install System * .***********************************************. - If you wish, you can configure some network settings immediately by choosing the Utility menu and then Configure network. It isn't actually required at this point, but it may be more convenient. Go back to the main menu. - Choose Install. - You will be guided through the setup of your disk. - You will be asked to choose which distribution sets to install. - When prompted, choose CD-ROM as the install medium if booted from CD-ROM. The default val- ues for the path and device should be ok. - After the installation process has completed, you will be brought back to the main menu, where you should select Reboot. - Once the system reaches the PROM prompt, you will need to modify your PROM environment set- tings for SystemPartition, OSLoadPartition, OSLoader, OSLoadFilename and OSLoadOptions and then boot the hard drive. - NetBSD will now boot. If you didn't set a password for the root user when prompted by sysinst, logging in as root and setting a pass- word should be your first task. You are also advised to read afterboot(8). 4. Booting NetBSD You may want to read the boot messages, to notice your disk's name and capacity. Its name will be something like sd0 and the geometry will be printed on a line that begins with its name. As mentioned above, you may need your disk's geometry when creating NetBSD's parti- tions. You will also need to know the name, to tell sysinst which disk to use. The most important thing to know is that sd0 is your first SCSI disk, sd1 the sec- ond, etc. Once NetBSD has booted and printed all the boot mes- sages, you will be presented with a welcome message and a main menu. It will also include instructions for using the menus. 5. Network configuration If you do not intend to use networking during the installation, but you do want your machine to be con- figured for networking once it is installed, you should first go to the Utility menu and select the Configure network option. If you only want to temporarily use networking during the installation, you can specify these parameters later. If you are not using the Domain Name System (DNS), you can give an empty response when asked to provide a server. 6. Installation drive selection and parameters To start the installation, select Install NetBSD to hard disk from the main menu. The first thing is to identify the disk on which you want to install NetBSD. sysinst will report a list of disks it finds and ask you for your selection. You should see disk names like sd0 or sd1. 7. Selecting which sets to install The next step is to choose which distribution sets you wish to install. Options are provided for full, mini- mal, and custom installations. If you choose sets on your own, base, etc, and a kernel must be selected. 8. Partitioning the disk o Please note that shared installs of IRIX and NetBSD on the same drive have not been tested, and as such may cause problems or may not work. It is strongly recommended that all data is backed before attempt- ing such installs. 9. Editing the NetBSD disklabel The partition table of the NetBSD part of a disk is called a disklabel. If your disk already has a diskla- bel written to it, you can choose Use existing partition sizes. Otherwise, select Set sizes of NetBSD partitions. After you have chosen your partitions and their sizes (or if you opted to use the existing partitions), you will be presented with the layout of the NetBSD diskla- bel and given one more chance to change it. For each partition, you can set the type, offset and size, block and fragment size, and the mount point. The type that NetBSD uses for normal file storage is called 4.2BSD. A swap partition has a special type called swap. Some partitions in the disklabel have a fixed purpose. a Root partition (/) b Swap partition. c The entire disk. d The SGI volume header (boot partition) e-p Available for other use. Traditionally, e is the partition mounted on /usr, but this is historical practice and not a fixed value. You will then be asked to name your disk's disklabel. The default response will be ok for most purposes. If you choose to name it something different, make sure the name is a single word and contains no special char- acters. You don't need to remember this name. 10. Preparing your hard disk You are now at the point of no return. Nothing has been written to your disk yet, but if you confirm that you want to install NetBSD, your hard drive will be modified. If you are sure you want to proceed, select yes. The install program will now label your disk and create the file systems you specified. The file systems will be initialized to contain NetBSD bootstrapping binaries and configuration files. You will see messages on your screen from the various NetBSD disk preparation tools that are running. There should be no errors in this section of the installation. If there are, restart from the beginning of the installation process. Other- wise, you can continue the installation program after pressing the return key. 11. Getting the distribution sets The NetBSD distribution consists of a number of sets that come in the form of gzipped tar files. At this point, you will be presented with a menu which enables you to choose from one of the following methods of installing the sets. Some of these methods will first transfer the sets to your hard disk, others will extract the sets directly. For all these methods, the first step is to make the sets available for extraction. The sets can be made available in a few different ways. The following sec- tions describe each of the methods. After reading about the method you will be using, you can continue to the section labeled `Extracting the distribution sets'. 12. Installation from CD-ROM When installing from a CD-ROM, you will be asked to specify the device name for your CD-ROM drive (usually cd0) and the directory name on the CD-ROM where the distribution files are. sysinst will then check that the files are actually present in the specified location and proceed to the extraction of the sets. 13. Installation using FTP To install using ftp, you first need to configure your network setup if you haven't already done so. sysinst will help you with this, asking if you want to use DHCP. If you do not use DHCP, you can enter network configuration details yourself. If you do not have DNS set up for the machine that you are installing on, you can just press RETURN in answer to this question, and DNS will not be used. You will also be asked to specify the host that you want to transfer the sets from, the directory on that host, the account name and password used to log into that host using ftp, and optionally a proxy server to use. If you did not set up DNS, you will need to spec- ify an IP address instead of a hostname for the ftp server. sysinst will then transfer the set files from the remote site to your hard disk. 14. Installation using NFS To install using NFS, you first need to configure your network setup if you haven't already done so. sysinst will do this for you, asking you if you want to use DHCP. If you do not use DHCP, you can enter network configuration details yourself. If you do not have DNS set up for the machine that you are installing on, you can just press RETURN in answer to this question, and DNS will not be used. You will also be asked to specify the host that you want to transfer the sets from and the directory on that host that the files are in. This directory should be mountable by the machine you are installing on, i.e., correctly exported to your machine. If you did not set up DNS, you will need to specify an IP address instead of a hostname for the NFS server. 15. Installation from an unmounted file system In order to install from a local file system, you will need to specify the device that the file system resides on (for example wd1e), the type of the file system, and the directory on the specified file system where the sets are located. sysinst will then check if it can indeed access the sets at that location. If this is a CD-ROM installation, the device used will be the name for your CD-ROM player with partition let- ter 'a' (usually cd0a). 16. Installation from a local directory This option assumes that you have already done some preparation yourself. The sets should be located in a directory on a file system that is already accessible. sysinst will ask you for the name of this directory. 17. Extracting the distribution sets A progress bar will be displayed while the distribution sets are being extracted. After all the files have been extracted, the device node files will be created. If you have already con- figured networking, you will be asked if you want to use this configuration for normal operation. If so, these values will be installed in the network configu- ration files. 18. Configure additional items The next menu will allow you to select a number of additional items to configure, including the time zone that you're in, to make sure your clock has the right offset from UTC, the root user's shell, and the initial root password. You can also enable installation of binary packages, which installs the pkgin(1) tool for managing binary packages for third-party software. This will feel familiar to users of package tools such as apt-get or yum. If you prefer to install third-party software from source, you can install the pkgsrc(7) tree. Finally, you can enable some daemons such as sshd(8), ntpd(8), or mdnsd(8). 19. Finalizing your installation Congratulations, you have successfully installed NetBSD 8.2_STABLE. You can now reboot the machine and boot NetBSD from hard disk. Post installation steps Once you've got the operating system running, there are a few things you need to do in order to bring the system into a properly configured state. The most important steps are described below. 1. Before all else, read postinstall(8). 2. Configuring /etc/rc.conf If you or the installation software haven't done any configuration of /etc/rc.conf (sysinst normally will), the system will drop you into single user mode on first reboot with the message /etc/rc.conf is not configured. Multiuser boot aborted. and with the root file system (/) mounted read-only. When the system asks you to choose a shell, simply press RETURN to get to a /bin/sh prompt. If you are asked for a terminal type, respond with vt220 (or what- ever is appropriate for your terminal type) and press RETURN. You may need to type one of the following com- mands to get your delete key to work properly, depend- ing on your keyboard: # stty erase '^h' # stty erase '^?' At this point, you need to configure at least one file in the /etc directory. You will need to mount your root file system read/write with: # /sbin/mount -u -w / Change to the /etc directory and take a look at the /etc/rc.conf file. Modify it to your tastes, making sure that you set rc_configured=YES so that your changes will be enabled and a multi-user boot can pro- ceed. Default values for the various programs can be found in /etc/defaults/rc.conf, where some in-line doc- umentation may be found. More complete documentation can be found in rc.conf(5). When you have finished editing /etc/rc.conf, type exit at the prompt to leave the single-user shell and con- tinue with the multi-user boot. Other values that may need to be set in /etc/rc.conf for a networked environment are hostname and possibly defaultroute. You may also need to add an ifconfig_int for your network interface, along the lines of ifconfig_sq0="inet 192.0.2.123 netmask 255.255.255.0" or, if you have myname.my.dom in /etc/hosts: ifconfig_sq0="inet myname.my.dom netmask 255.255.255.0" To enable proper hostname resolution, you will also want to add an /etc/resolv.conf file or (if you are feeling a little more adventurous) run named(8). See resolv.conf(5) or named(8) for more information. Instead of manually configuring networking, DHCP can be used by setting dhcpcd=YES in /etc/rc.conf. 3. Logging in After reboot, you can log in as root at the login prompt. If you didn't set a password in sysinst, there is no initial password. You should create an account for yourself (see below) and protect it and the ``root'' account with good passwords. By default, root login from the network is disabled (even via ssh(1)). One way to become root over the network is to log in as a different user that belongs to group ``wheel'' (see group(5)) and use su(1) to become root. 4. Adding accounts Use the useradd(8) command to add accounts to your sys- tem. Do not edit /etc/passwd directly! See vipw(8) and pwd_mkdb(8) if you want to edit the password database. 5. The X Window System If you installed the X Window System, you may want to read the chapter about X in the NetBSD Guide: http://www.NetBSD.org/docs/guide/en/chap-x.html 6. Installing third party packages If you wish to install any of the software freely available for UNIX-like systems you are strongly advised to first check the NetBSD package system, pkgsrc. pkgsrc automatically handles any changes nec- essary to make the software run on NetBSD. This includes the retrieval and installation of any other packages the software may depend upon. o More information on the package system is available at http://www.NetBSD.org/docs/software/packages.html o A list of available packages suitable for browsing is at ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/README.html o Precompiled binaries can be found at ftp://ftp.NetBSD.org/pub/pkgsrc/packages/NetBSD/ usually in the sgimips/8.2_STABLE/All subdir. If you installed pkgin(1) in the sysinst post-instal- lation configuration menu, you can use it to auto- matically install binary packages over the network. Assuming that /usr/pkg/etc/pkgin/repositories.conf is correctly configured, you can install them with the following commands: # pkgin install tcsh # pkgin install bash # pkgin install perl # pkgin install apache # pkgin install kde # pkgin install firefox ... Note: Some mirror sites don't mirror the /pub/pkgsrc directory. The above commands will install the Tenex-csh and Bourne Again shells, the Perl programming language, Apache web server, KDE desktop environment and the Firefox web browser as well as all the packages they depend on. o If you did not install it from the sysinst post- installation configuration menu, the pkgsrc(7) framework for compiling packages can be obtained by retrieving the file ftp://ftp.NetBSD.org/pub/pkgsrc/pkgsrc.tar.gz It is typically extracted into /usr/pkgsrc (though other locations work fine) with the commands: # cd /usr # tar -zxpf pkgsrc.tar.gz After extracting, see the doc/pkgsrc.txt file in the extraction directory (e.g., /usr/pkgsrc/doc/pkgsrc.txt) for more information. 7. Misc o Edit /etc/mail/aliases to forward root mail to the right place. Don't forget to run newaliases(1) afterwards. o Edit /etc/rc.local to run any local daemons you use. o Many of the /etc files are documented in section 5 of the manual; so just invoking # man 5 filename is likely to give you more information on these files. Upgrading a previously-installed NetBSD System The easiest way to upgrade to NetBSD 8.2_STABLE is with binaries, and that is the method documented here. To do the upgrade, you must have one form of boot media available. You must also have at least the base and kern binary distribution sets available. Finally, you must have sufficient disk space available to install the new binaries. Since files already installed on the system are overwritten in place, you only need additional free space for files which weren't previously installed or to account for growth of the sets between releases. Since upgrading involves replacing the kernel, boot blocks, 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 the NetBSD partition or on another operat- ing system's partition on your disk before beginning the upgrade process. The upgrade procedure is similar to an installation, but without the hard disk partitioning. Fetching the binary sets is done in the same manner as the installation procedure; refer to the installation part of the document for help. File systems are checked before unpacking the sets. After a new kernel has been copied to your hard disk, your machine is a complete NetBSD 8.2_STABLE 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 sysinst will attempt to merge the settings stored in your /etc directory with the new version of NetBSD using the postinstall(8) utility. However, postinstall(8) is only able to deal with changes that are easily automated. It is recommended that you use the etcupdate(8) tool to merge any remaining configuration changes. 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 8.2_STABLE. Note that sysinst will automatically invoke postinstall fix and thus all issues that are fixed by postinstall by default will be handled. Issues affecting an upgrade from NetBSD 5.x releases See the section below on upgrading from NetBSD 6.x and 7.x as well. The following users need to be created: o _mdnsd o _tests o _tcpdump o _tss The following groups need to be created: o _mdnsd o _tests o _tcpdump o _tss The implementation of SHA2-HMAC in KAME_IPSEC as used in NetBSD 5.0 and before did not comply with current standards. FAST_IPSEC does, with the result that old and new systems cannot communicate over IPSEC if one of the affected authen- tication algorithms (hmac_sha256, hmac_sha384, hmac_sha512) is used. Issues affecting an upgrade from NetBSD 6.x releases See the section on upgrading from NetBSD 7.x as well The following user needs to be created: o _rtadvd The following groups need to be created: o _gpio o _rtadvd Issues affecting an upgrade from NetBSD 7.x releases The following user needs to be created: o _unbound o _nsd The following groups need to be created: o _unbound o _nsd Using online NetBSD documentation Documentation is available if you installed the manual dis- tribution set. Traditionally, the ``man pages'' (documenta- tion) are denoted by `name(section)'. Some examples of this are o intro(1), o man(1), o apropos(1), o passwd(1), and o passwd(5). The section numbers group the topics into several cate- gories, but three are of primary interest: user commands are in section 1, file formats are in section 5, and administra- tive 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 lowest num- bered section name will be displayed. For instance, after logging in, enter # man passwd to read the documentation for passwd(1). To view the docu- mentation 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 pos- sibly 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 majordomo@NetBSD.org. See http://www.NetBSD.org/mailinglists/ for details. 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(1) command shipped with NetBSD, and fill in as much information about the problem as you can. Good bug reports include lots of details. Bugs also can be submitted and queried with the web inter- face at http://www.NetBSD.org/support/send-pr.html There are also port-specific mailing lists, to discuss aspects of each port of NetBSD. Use majordomo to find their addresses, or visit http://www.NetBSD.org/mailinglists/ 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 NetBSD, and have an idea as to how you could be useful, send us mail or subscribe to: netbsd-users@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 or WWW somewhere, then mail the appro- priate list about it. If you'd rather not do that, mail the list saying you'll send the data to those who want it. Thanks go to o The 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 work on BSD systems, support, and encourage- ment. o The Internet Systems Consortium, Inc. for hosting the NetBSD FTP, CVS, AnonCVS, mail, mail archive, GNATS, SUP, Rsync and WWW servers. o The Internet Research Institute in Japan for hosting the server which runs the CVSweb interface to the NetBSD source tree. o The Columbia University Computer Science Department for hosting the build cluster. o The many organizations that provide NetBSD mirror sites. o 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. o We list the individuals and organizations that have made donations or loans of hardware and/or money, to support NetBSD development, and deserve credit for it at http://www.NetBSD.org/donations/ (If you're not on that list and should be, tell us! We probably were not able to get in touch with you, to ver- ify that you wanted to be listed.) o Finally, we thank all of the people who've put sweat and tears into developing NetBSD since its inception in Jan- uary, 1993. (Obviously, there are a lot more people who deserve thanks here. If you're one of them, and would like to be mentioned, tell us!) We are... (in alphabetical order) The NetBSD core group: Alistair Crooks agc@NetBSD.org Matthew Green mrg@NetBSD.org Martin Husemann martin@NetBSD.org Chuck Silvers chs@NetBSD.org Matt Thomas matt@NetBSD.org YAMAMOTO Takashi yamt@NetBSD.org Christos Zoulas christos@NetBSD.org The portmasters (and their ports): Reinoud Zandijk reinoud acorn32 Matt Thomas matt alpha Ignatios Souvatzis is amiga Ignatios Souvatzis is amigappc Noriyuki Soda soda arc Julian Coleman jdc atari Matthias Drochner drochner cesfic Erik Berls cyber cobalt Antti Kantee pooka emips Simon Burge simonb evbmips Steve Woodford scw evbppc Izumi Tsutsui tsutsui ews4800mips Izumi Tsutsui tsutsui hp300 Nick Hudson skrll hppa Valeriy E. Ushakov uwe hpcsh Matt Thomas matt ibmnws Gavan Fantom gavan iyonix Valeriy E. Ushakov uwe landisk Izumi Tsutsui tsutsui luna68k Scott Reynolds scottr mac68k Michael Lorenz macallan macppc Steve Woodford scw mvme68k Steve Woodford scw mvmeppc Matt Thomas matt netwinder Izumi Tsutsui tsutsui news68k Tim Rightnour garbled ofppc Simon Burge simonb pmax Tim Rightnour garbled prep Tim Rightnour garbled rs6000 Tohru Nishimura nisimura sandpoint Simon Burge simonb sbmips Soren Jorvang soren sgimips SAITOH Masanobu msaitoh sh3 Martin Husemann martin sparc64 Anders Magnusson ragge vax NISHIMURA Takeshi nsmrtks x68k Manuel Bouyer bouyer xen The NetBSD 8.2_STABLE Release Engineering team: Stephen Borrill sborrill@NetBSD.org Manuel Bouyer bouyer@NetBSD.org David Brownlee abs@NetBSD.org Julian Coleman jdc@NetBSD.org Alistair G. Crooks agc@NetBSD.org Havard Eidnes he@NetBSD.org Martin Husemann martin@NetBSD.org Soren Jacobsen snj@NetBSD.org Phil Nelson phil@NetBSD.org Jeremy C. Reed reed@NetBSD.org Jeff Rizzo riz@NetBSD.org SAITOH Masanobu msaitoh@NetBSD.org NetBSD Developers: Hikaru Abe hikaru@NetBSD.org Nathan Ahlstrom nra@NetBSD.org Steve Allen wormey@NetBSD.org Jukka Andberg jandberg@NetBSD.org Julian Assange proff@NetBSD.org Lennart Augustsson augustss@NetBSD.org Zafer Aydogan zafer@NetBSD.org Christoph Badura bad@NetBSD.org Marc Balmer mbalmer@NetBSD.org Bang Jun-Young junyoung@NetBSD.org Dieter Baron dillo@NetBSD.org Robert V. Baron rvb@NetBSD.org Alan Barrett apb@NetBSD.org Grant Beattie grant@NetBSD.org Erik Berls cyber@NetBSD.org Hiroyuki Bessho bsh@NetBSD.org John Birrell jb@NetBSD.org Rafal Boni rafal@NetBSD.org Stephen Borrill sborrill@NetBSD.org Sean Boudreau seanb@NetBSD.org Manuel Bouyer bouyer@NetBSD.org Allen Briggs briggs@NetBSD.org Mark Brinicombe mark@NetBSD.org Aaron Brown abrown@NetBSD.org Andrew Brown atatat@NetBSD.org David Brownlee abs@NetBSD.org Jon Buller jonb@NetBSD.org Simon Burge simonb@NetBSD.org Robert Byrnes byrnes@NetBSD.org Pavel Cahyna pavel@NetBSD.org D'Arcy J.M. Cain darcy@NetBSD.org Taylor R. Campbell riastradh@NetBSD.org Daniel Carosone dan@NetBSD.org Dave Carrel carrel@NetBSD.org James Chacon jmc@NetBSD.org Mihai Chelaru kefren@NetBSD.org Aleksey Cheusov cheusov@NetBSD.org Bill Coldwell billc@NetBSD.org Sean Cole scole@NetBSD.org Julian Coleman jdc@NetBSD.org Marcus Comstedt marcus@NetBSD.org Jeremy Cooper jeremy@NetBSD.org Thomas Cort tcort@NetBSD.org Chuck Cranor chuck@NetBSD.org Alistair Crooks agc@NetBSD.org Masatake Daimon pho@NetBSD.org Johan Danielsson joda@NetBSD.org John Darrow jdarrow@NetBSD.org Jed Davis jld@NetBSD.org Matt DeBergalis deberg@NetBSD.org Arnaud Degroote degroote@NetBSD.org Felix Deichmann flxd@NetBSD.org Rob Deker deker@NetBSD.org Chris G. Demetriou cgd@NetBSD.org Tracy Di Marco White gendalia@NetBSD.org Jaromir Dolecek jdolecek@NetBSD.org Andy Doran ad@NetBSD.org Roland Dowdeswell elric@NetBSD.org Steven Drake sbd@NetBSD.org Emmanuel Dreyfus manu@NetBSD.org Matthias Drochner drochner@NetBSD.org Jun Ebihara jun@NetBSD.org Elad Efrat elad@NetBSD.org Havard Eidnes he@NetBSD.org Jaime A Fournier ober@NetBSD.org Stoned Elipot seb@NetBSD.org Michael van Elst mlelstv@NetBSD.org Robert Elz kre@NetBSD.org Enami Tsugutomo enami@NetBSD.org Bernd Ernesti veego@NetBSD.org Erik Fair fair@NetBSD.org Gavan Fantom gavan@NetBSD.org Hauke Fath hauke@NetBSD.org Hubert Feyrer hubertf@NetBSD.org Jason R. Fink jrf@NetBSD.org Matt J. Fleming mjf@NetBSD.org Marty Fouts marty@NetBSD.org Liam J. Foy liamjfoy@NetBSD.org Matt Fredette fredette@NetBSD.org Thorsten Frueauf frueauf@NetBSD.org Castor Fu castor@NetBSD.org Hisashi Todd Fujinaka htodd@NetBSD.org Makoto Fujiwara mef@NetBSD.org Ichiro Fukuhara ichiro@NetBSD.org Quentin Garnier cube@NetBSD.org Thomas Gerner thomas@NetBSD.org Simon J. Gerraty sjg@NetBSD.org Justin Gibbs gibbs@NetBSD.org Chris Gilbert chris@NetBSD.org Eric Gillespie epg@NetBSD.org Brian Ginsbach ginsbach@NetBSD.org Oliver V. Gould ver@NetBSD.org Paul Goyette pgoyette@NetBSD.org Michael Graff explorer@NetBSD.org Matthew Green mrg@NetBSD.org Andreas Gustafsson gson@NetBSD.org Ulrich Habel rhaen@NetBSD.org Jun-ichiro itojun Hagino itojun@NetBSD.org HAMAJIMA Katsuomi hamajima@NetBSD.org Adam Hamsik haad@NetBSD.org Juergen Hannken-Illjes hannken@NetBSD.org Charles M. Hannum mycroft@NetBSD.org Yorick Hardy yhardy@NetBSD.org Ben Harris bjh21@NetBSD.org Kenichi Hashimoto hkenken@NetBSD.org Eric Haszlakiewicz erh@NetBSD.org John Hawkinson jhawk@NetBSD.org Emile Heitor imil@NetBSD.org John Heasley heas@NetBSD.org Lars Heidieker para@NetBSD.org Geert Hendrickx ghen@NetBSD.org Wen Heping wen@NetBSD.org Rene Hexel rh@NetBSD.org Iain Hibbert plunky@NetBSD.org Kouichirou Hiratsuka hira@NetBSD.org Michael L. Hitch mhitch@NetBSD.org Adam Hoka ahoka@NetBSD.org Jachym Holecek freza@NetBSD.org David A. Holland dholland@NetBSD.org Christian E. Hopps chopps@NetBSD.org Daniel Horecki morr@NetBSD.org Ken Hornstein kenh@NetBSD.org Marc Horowitz marc@NetBSD.org Eduardo Horvath eeh@NetBSD.org Nick Hudson skrll@NetBSD.org Shell Hung shell@NetBSD.org Darran Hunt darran@NetBSD.org Martin Husemann martin@NetBSD.org Dean Huxley dean@NetBSD.org Love Hoernquist Astrand lha@NetBSD.org Roland Illig rillig@NetBSD.org Bernardo Innocenti bernie@NetBSD.org Tetsuya Isaki isaki@NetBSD.org ITOH Yasufumi itohy@NetBSD.org IWAMOTO Toshihiro toshii@NetBSD.org Matthew Jacob mjacob@NetBSD.org Soren Jacobsen snj@NetBSD.org Sevan Janiyan sevan@NetBSD.org Lonhyn T. Jasinskyj lonhyn@NetBSD.org Darrin Jewell dbj@NetBSD.org Nicolas Joly njoly@NetBSD.org Soren Jorvang soren@NetBSD.org Takahiro Kambe taca@NetBSD.org Antti Kantee pooka@NetBSD.org Frank Kardel kardel@NetBSD.org KAWAMOTO Yosihisa kawamoto@NetBSD.org Min Sik Kim minskim@NetBSD.org KIYOHARA Takashi kiyohara@NetBSD.org Thomas Klausner wiz@NetBSD.org Klaus Klein kleink@NetBSD.org John Klos jklos@NetBSD.org Wayne Knowles wdk@NetBSD.org Takayoshi Kochi kochi@NetBSD.org Mateusz Kocielski shm@NetBSD.org Jonathan A. Kollasch jakllsch@NetBSD.org Joseph Koshy jkoshy@NetBSD.org Radoslaw Kujawa rkujawa@NetBSD.org Jochen Kunz jkunz@NetBSD.org Martti Kuparinen martti@NetBSD.org Arnaud Lacombe alc@NetBSD.org Kevin Lahey kml@NetBSD.org David Laight dsl@NetBSD.org Johnny C. Lam jlam@NetBSD.org Guillaume Lasmayous gls@NetBSD.org Martin J. Laubach mjl@NetBSD.org Greg Lehey grog@NetBSD.org Ted Lemon mellon@NetBSD.org Christian Limpach cl@NetBSD.org Frank van der Linden fvdl@NetBSD.org Joel Lindholm joel@NetBSD.org Tonnerre Lombard tonnerre@NetBSD.org Mike Long mikel@NetBSD.org Sergio Lopez slp@NetBSD.org Michael Lorenz macallan@NetBSD.org Warner Losh imp@NetBSD.org Tomasz Luchowski zuntum@NetBSD.org Federico Lupi federico@NetBSD.org Palle Lyckegaard palle@NetBSD.org Brett Lymn blymn@NetBSD.org MAEKAWA Masahide gehenna@NetBSD.org Anders Magnusson ragge@NetBSD.org Anthony Mallet tho@NetBSD.org John Marino marino@NetBSD.org Roy Marples roy@NetBSD.org Pedro Martelletto pedro@NetBSD.org Cherry G. Mathew cherry@NetBSD.org David Maxwell david@NetBSD.org Gregory McGarry gmcgarry@NetBSD.org Dan McMahill dmcmahill@NetBSD.org Jared D. McNeill jmcneill@NetBSD.org Neil J. McRae neil@NetBSD.org Julio M. Merino Vidal jmmv@NetBSD.org Perry Metzger perry@NetBSD.org Luke Mewburn lukem@NetBSD.org Jean-Yves Migeon jym@NetBSD.org Brook Milligan brook@NetBSD.org Minoura Makoto minoura@NetBSD.org Simas Mockevicius symka@NetBSD.org Ryosuke Moro szptvlfn@NetBSD.org der Mouse mouse@NetBSD.org Youri Mouton youri@NetBSD.org Constantine A. Murenin cnst@NetBSD.org Joseph Myers jsm@NetBSD.org Tuomo Maekinen tjam@NetBSD.org Zoltan Arnold NAGY zoltan@NetBSD.org Kengo NAKAHARA knakahara@NetBSD.org Ken Nakata kenn@NetBSD.org Takeshi Nakayama nakayama@NetBSD.org Alexander Nasonov alnsn@NetBSD.org Phil Nelson phil@NetBSD.org John Nemeth jnemeth@NetBSD.org Lourival Pereira Vieira Neto lneto@NetBSD.org NISHIMURA Takeshi nsmrtks@NetBSD.org Tohru Nishimura nisimura@NetBSD.org NONAKA Kimihiro nonaka@NetBSD.org Takehiko NOZAKI tnozaki@NetBSD.org Tobias Nygren tnn@NetBSD.org OBATA Akio obache@NetBSD.org Jesse Off joff@NetBSD.org Tatoku Ogaito tacha@NetBSD.org OKANO Takayoshi kano@NetBSD.org Masaru Oki oki@NetBSD.org Rin Okuyama rin@NetBSD.org Ryo ONODERA ryoon@NetBSD.org Atsushi Onoe onoe@NetBSD.org Greg Oster oster@NetBSD.org Ryota Ozaki ozaki-r@NetBSD.org Jonathan Perkin sketch@NetBSD.org Fredrik Pettai pettai@NetBSD.org Herb Peyerl hpeyerl@NetBSD.org Matthias Pfaller matthias@NetBSD.org Chris Pinnock cjep@NetBSD.org Adrian Portelli adrianp@NetBSD.org Pierre Pronchery khorben@NetBSD.org Chris Provenzano proven@NetBSD.org Maya Rashish maya@NetBSD.org Mindaugas Rasiukevicius rmind@NetBSD.org Nils Ratusznik nils@NetBSD.org Michael Rauch mrauch@NetBSD.org Marc Recht recht@NetBSD.org Darren Reed darrenr@NetBSD.org Jeremy C. Reed reed@NetBSD.org Jens Rehsack sno@NetBSD.org Antoine Reilles tonio@NetBSD.org Tyler R. Retzlaff rtr@NetBSD.org Scott Reynolds scottr@NetBSD.org Tim Rightnour garbled@NetBSD.org Jeff Rizzo riz@NetBSD.org Hans Rosenfeld hans@NetBSD.org Steve Rumble rumble@NetBSD.org Rumko rumko@NetBSD.org Jukka Ruohonen jruoho@NetBSD.org Kamil Rytarowski kamil@NetBSD.org Blair J. Sadewitz bjs@NetBSD.org David Sainty dsainty@NetBSD.org SAITOH Masanobu msaitoh@NetBSD.org Kazuki Sakamoto sakamoto@NetBSD.org Guilherme Salazar salazar@NetBSD.org Curt Sampson cjs@NetBSD.org Wilfredo Sanchez wsanchez@NetBSD.org Ty Sarna tsarna@NetBSD.org SATO Kazumi sato@NetBSD.org Jan Schaumann jschauma@NetBSD.org Matthias Scheler tron@NetBSD.org Silke Scheler silke@NetBSD.org Karl Schilke (rAT) rat@NetBSD.org Amitai Schlair schmonz@NetBSD.org Konrad Schroder perseant@NetBSD.org Georg Schwarz schwarz@NetBSD.org Lubomir Sedlacik salo@NetBSD.org Christopher SEKIYA sekiya@NetBSD.org Reed Shadgett dent@NetBSD.org John Shannon shannonjr@NetBSD.org Tim Shepard shep@NetBSD.org Naoto Shimazaki igy@NetBSD.org Ryo Shimizu ryo@NetBSD.org Takao Shinohara shin@NetBSD.org Takuya SHIOZAKI tshiozak@NetBSD.org Daniel Sieger dsieger@NetBSD.org Chuck Silvers chs@NetBSD.org Thor Lancelot Simon tls@NetBSD.org Nathanial Sloss nat@NetBSD.org Jeff Smith jeffs@NetBSD.org Noriyuki Soda soda@NetBSD.org Wolfgang Solfrank ws@NetBSD.org Joerg Sonnenberger joerg@NetBSD.org Ignatios Souvatzis is@NetBSD.org T K Spindler dogcow@NetBSD.org Matthew Sporleder mspo@NetBSD.org Bill Squier groo@NetBSD.org Adrian Steinmann ast@NetBSD.org Bill Studenmund wrstuden@NetBSD.org Hiroki Suenaga hsuenaga@NetBSD.org Kevin Sullivan sullivan@NetBSD.org Kimmo Suominen kim@NetBSD.org Gregoire Sutre gsutre@NetBSD.org Sergey Svishchev shattered@NetBSD.org Robert Swindells rjs@NetBSD.org Leonardo Taccari leot@NetBSD.org Shin Takemura takemura@NetBSD.org TAMURA Kent kent@NetBSD.org Shin'ichiro TAYA taya@NetBSD.org Hasso Tepper hasso@NetBSD.org Matt Thomas matt@NetBSD.org Jason Thorpe thorpej@NetBSD.org Hiroshi Tokuda hiroshi@NetBSD.org Christoph Toshok toshok@NetBSD.org Tamas Toth ttoth@NetBSD.org Greg Troxel gdt@NetBSD.org Tsubai Masanari tsubai@NetBSD.org Izumi Tsutsui tsutsui@NetBSD.org UCHIYAMA Yasushi uch@NetBSD.org Masao Uebayashi uebayasi@NetBSD.org Shuichiro URATA ur@NetBSD.org Valeriy E. Ushakov uwe@NetBSD.org Todd Vierling tv@NetBSD.org Maxime Villard maxv@NetBSD.org Aymeric Vincent aymeric@NetBSD.org Paul Vixie vixie@NetBSD.org Mike M. Volokhov mishka@NetBSD.org Krister Walfridsson kristerw@NetBSD.org Mark Weinem weinem@NetBSD.org Lex Wennmacher wennmach@NetBSD.org Leo Weppelman leo@NetBSD.org Assar Westerlund assar@NetBSD.org Sebastian Wiedenroth wiedi@NetBSD.org Frank Wille phx@NetBSD.org Nathan Williams nathanw@NetBSD.org Rob Windsor windsor@NetBSD.org Jim Wise jwise@NetBSD.org Colin Wood ender@NetBSD.org Steve Woodford scw@NetBSD.org YAMAMOTO Takashi yamt@NetBSD.org Abhinav Upadhyay abhinav@NetBSD.org Yuji Yamano yyamano@NetBSD.org David Young dyoung@NetBSD.org Arnaud Ysmal stacktic@NetBSD.org Reinoud Zandijk reinoud@NetBSD.org S.P.Zeidler spz@NetBSD.org Tim Zingelman tez@NetBSD.org Christos Zoulas christos@NetBSD.org Legal Mumbo-Jumbo All product names mentioned herein are trademarks or regis- tered trademarks of their respective owners. The following notices are required to satisfy the license terms of the software that we have mentioned in this docu- ment: NetBSD is a registered trademark of The NetBSD Foundation, Inc. This product includes software developed by the University of California, Berkeley and its contributors. This product includes software developed by the NetBSD Foun- dation. This product includes software developed by The NetBSD Foun- dation, Inc. and its contributors. This product includes software developed for the NetBSD Project. See http://www.NetBSD.org/ for information about NetBSD. This product includes software developed by Intel Corpora- tion and its contributors. This product includes cryptographic software written by Eric Young (eay@cryptsoft.com) This product includes cryptographic software written by Eric Young (eay@mincom.oz.au) This product includes software designed by William Allen Simpson. This product includes software developed at Ludd, University of Lulea, Sweden and its contributors. This product includes software developed at Ludd, University of Lulea. This product includes software developed at the Information Technology Division, US Naval Research Laboratory. This product includes software developed by David Jones and Gordon Ross This product includes software developed by Hellmuth Michaelis and Joerg Wunsch This product includes software developed by Internet Research Institute, Inc. This product includes software developed by Leo Weppelman and Waldi Ravens. This product includes software developed by Mika Korte- lainen This product includes software developed by Aaron Brown and Harvard University. This product includes software developed by Adam Ciarcinski for the NetBSD project. This product includes software developed by Adam Glass and Charles M. Hannum. This product includes software developed by Adam Glass. This product includes software developed by Alex Zepeda, and Colin Wood for the NetBSD Projet. This product includes software developed by Alex Zepeda. This product includes software developed by Allen Briggs. This product includes software developed by Amancio Hasty and Roger Hardiman This product includes software developed by Berkeley Soft- ware Design, Inc. This product includes software developed by Bill Paul. This product includes software developed by Bodo Moeller. (If available, substitute umlauted o for oe) This product includes software developed by Boris Popov. This product includes software developed by Brini. This product includes software developed by Bruce M. Simp- son. This product includes software developed by Causality Lim- ited. This product includes software developed by Charles Hannum. This product includes software developed by Charles M. Han- num, 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 M. Han- num. This product includes software developed by Christian E. Hopps, Ezra Story, Kari Mettinen, Markus Wild, Lutz Vieweg and Michael Teske. 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 Chuck Silvers. This product includes software developed by Colin Wood for the NetBSD Project. This product includes software developed by Colin Wood. This product includes software developed by Daan Vreeken. This product includes software developed by Daishi Kato This product includes software developed by Daniel Widenfalk and Michael L. Hitch. This product includes software developed by Daniel Widenfalk for the NetBSD Project. This product includes software developed by David Miller. This product includes software developed by Dean Huxley. This product includes software developed by Emmanuel Dreyfus This product includes software developed by Eric S. Hvozda. This product includes software developed by Eric S. Raymond This product includes software developed by Eric Young (eay@cryptsoft.com) This product includes software developed by Eric Young (eay@mincom.oz.au) This product includes software developed by Ezra Story and by Kari Mettinen. This product includes software developed by Ezra Story, by Kari Mettinen and by Bernd Ernesti. This product includes software developed by Ezra Story, by Kari Mettinen, Michael Teske and by Bernd Ernesti. This product includes software developed by Ezra Story, by Kari Mettinen, and Michael Teske. This product includes software developed by Ezra Story. This product includes software developed by Frank van der Linden for the NetBSD Project. This product includes software developed by Gardner Buchanan. This product includes software developed by Garrett D'Amore. This product includes software developed by Gary Thomas. This product includes software developed by Gordon Ross This product includes software developed by Harvard Univer- sity and its contributors. This product includes software developed by Harvard Univer- sity. This product includes software developed by Henrik Vester- gaard Draboel. This product includes software developed by Herb Peyerl. This product includes software developed by Hidetoshi Shimokawa. This product includes software developed by Hubert Feyrer for the NetBSD Project. This product includes software developed by Ian W. Dall. This product includes software developed by Internet Initia- tive Japan Inc. This product includes software developed by James R. Maynard III. This product includes software developed by Jared D. McNeill. This product includes software developed by Jason L. Wright 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 Joerg Wunsch This product includes software developed by John Birrell. This product includes software developed by John P. Wit- tkoski. This product includes software developed by John Polstra. This product includes software developed by Jonathan R. Stone for the NetBSD Project. This product includes software developed by Jonathan Stone and Jason R. Thorpe for the NetBSD Project. This product includes software developed by Jonathan Stone. This product includes software developed by Jonathan Stone for the NetBSD Project. This product includes software developed by Julian High- field. This product includes software developed by K. Kobayashi. This product includes software developed by K. Kobayashi and H. Shimokawa. This product includes software developed by Kazuhisa Shimizu. This product includes software developed by Kazuki Sakamoto. This product includes software developed by Kenneth Stailey. This product includes software developed by Kiyoshi Ikehara. This product includes software developed by Klaus Burkert,by Bernd Ernesti, by Michael van Elst, and by the University of California, Berkeley and its contributors. This product includes software developed by Lloyd Parkes. This product includes software developed by Lutz Vieweg. This product includes software developed by MINOURA Makoto, Takuya Harakawa. This product includes software developed by Marc Horowitz. This product includes software developed by Marcus Comstedt. This product includes software developed by Mark Brinicombe for the NetBSD project. This product includes software developed by Mark Brinicombe. This product includes software developed by Mark Tinguely and Jim Lowe This product includes software developed by Markus Wild. This product includes software developed by Marshall M. Mid- den. This product includes software developed by Masanobu Saitoh. This product includes software developed by Masaru Oki. This product includes software developed by Matthew Fre- dette. This product includes software developed by Matt DeBergalis. This product includes software developed by Michael Smith. This product includes software developed by Microsoft. This product includes software developed by Mike Pritchard. This product includes software developed by Mike Pritchard and contributors. This product includes software developed by Minoura Makoto. This product includes software developed by Niels Provos. This product includes software developed by Niklas Hal- lqvist, Brandon Creighton and Job de Haas. This product includes software developed by Niklas Hal- lqvist. This product includes software developed by Paolo Abeni. This product includes software developed by Paul Kranenburg. This product includes software developed by Paul Mackerras. This product includes software developed by Per Fogelstrom This product includes software developed by Peter Galbavy. This product includes software developed by Phase One, Inc. This product includes software developed by Philip A. Nel- son. This product includes software developed by QUALCOMM Incor- porated. This product includes software developed by RiscBSD. This product includes software developed by Roar Thronaes. This product includes software developed by Rodney W. Grimes. This product includes software developed by Roger Hardiman This product includes software developed by Rolf Grossmann. This product includes software developed by Ross Harvey for the NetBSD Project. This product includes software developed by Ross Harvey. This product includes software developed by Scott Bartram. This product includes software developed by Scott Stevens. This product includes software developed by Shingo WATANABE. This product includes software developed by Softweyr LLC, the University of California, Berkeley, and its contribu- tors. This product includes software developed by Stephan Thesing. This product includes software developed by Steven M. Bellovin. This product includes software developed by Takashi Hamada. This product includes software developed by Takumi Nakamura. This product includes software developed by Tatoku Ogaito for the NetBSD Project. This product includes software developed by Texas A&M Uni- versity and its contributors. This product includes software developed by Thomas Gerner. This product includes software developed by TooLs GmbH. This product includes software developed by Trimble Naviga- tion, Ltd. This product includes software developed by WIDE Project and its contributors. This product includes software developed by Waldi Ravens. This product includes software developed by Winning Strate- gies, Inc. This product includes software developed by Yasushi Yamasaki. This product includes software developed by Yen Yen Lim and North Dakota State University. This product includes software developed by Zembu Labs, Inc. This product includes software developed by the Alice Group. This product includes software developed by the Computer Systems Engineering Group at Lawrence Berkeley Laboratory. This product includes software developed by the David Muir Sharnoff. This product includes software developed by the Harvard Uni- versity and its contributors. This product includes software developed by the Kungliga Tekniska Hoegskolan and its contributors. This product includes software developed by the Network Research Group at Lawrence Berkeley Laboratory. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.OpenSSL.org/) This product includes software developed by the PocketBSD project and its contributors. This product includes software developed by the RiscBSD ker- nel team. This product includes software developed by the RiscBSD team. This product includes software developed by the SMCC Tech- nology Development Group at Sun Microsystems, Inc. This product includes software developed by the University of California, Berkeley and its contributors, as well as the Trustees of Columbia University. This product includes software developed by the University of California, Lawrence Berkeley Laboratory and its contrib- utors. This product includes software developed by the University of California, Lawrence Berkeley Laboratory. This product includes software developed by the University of Illinois at Urbana and their contributors. This product includes software developed by the Urbana-Cham- paign Independent Media Center. This product includes software developed by the University of Vermont and State Agricultural College and Garrett A. Wollman. This product includes software developed 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 for the FreeBSD project This product includes software developed for the NetBSD Project by Bernd Ernesti. This product includes software developed for the NetBSD Project by Christopher G. Demetriou. 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 by Kyma Systems. This product includes software developed for the NetBSD Project by Kyma Systems LLC. This product includes software developed for the NetBSD Project by Matthias Drochner. This product includes software developed for the NetBSD Project by Perry E. Metzger. This product includes software developed for the NetBSD Project by Scott Bartram and Frank van der Linden This product includes software developed for the NetBSD Project by Allegro Networks, Inc., and Wasabi Systems, Inc. This product includes software developed for the NetBSD Project by Eiji Kawauchi. This product includes software developed for the NetBSD Project by Genetec Corporation. This product includes software developed for the NetBSD Project by Jonathan Stone. This product includes software developed for the NetBSD Project by Piermont Information Systems Inc. This product includes software developed for the NetBSD Project by SUNET, Swedish University Computer Network. This product includes software developed for the NetBSD Project by Shigeyuki Fukushima. This product includes software developed for the NetBSD Project by Wasabi Systems, Inc. This product includes software developed under OpenBSD by Per Fogelstrom Opsycon AB for RTMX Inc, North Carolina, USA. This product includes software developed under OpenBSD by Per Fogelstrom. This software was developed by Holger Veit and Brian Moore for use with "386BSD" and similar operating systems. "Simi- lar operating systems" includes mainly non-profit oriented systems for research and education, including but not restricted to "NetBSD", "FreeBSD", "Mach" (by CMU). This software includes software developed by the Computer Systems Laboratory at the University of Utah. This product includes software developed by Computing Ser- vices at Carnegie Mellon University (http://www.cmu.edu/com- puting/). This product includes software developed or owned by Caldera International, Inc. The Institute of Electrical and Electronics Engineers and The Open Group, have given us permission to reprint portions of their documentation. In the following statement, the phrase ``this text'' refers to portions of the system documentation. Portions of this text are reprinted and reproduced in electronic form in NetBSD, from IEEE Std 1003.1, 2004 Edition, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2004 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between these versions and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html. This notice shall appear on any product containing this material. 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. Some files have the following copyright: Mach Operating System Copyright (c) 1991,1990,1989 Carnegie Mellon Univer- sity All Rights Reserved. Permission to use, copy, modify and distribute this software and its documentation is hereby granted, pro- vided that both the copyright notice and this permis- sion notice appear in all copies of the software, de- rivative works or modified versions, and any portions thereof, and that both notices appear in supporting documentation. CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN ITS CONDITION. CARNEGIE MELLON DISCLAIMS ANY LIABIL- ITY OF ANY KIND FOR ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE. Carnegie Mellon requests users of this software to return to Software Distribution Coordinator or Software.Dis- tribution@CS.CMU.EDU School of Computer Science Carnegie Mellon University Pittsburgh PA 15213-3890 any improvements or extensions that they make and grant Carnegie the rights to redistribute these changes. Some files have the following copyright: Copyright (c) 1994, 1995 Carnegie-Mellon University. All rights reserved. Author: Chris G. Demetriou Permission to use, copy, modify and distribute this software and its documentation is hereby granted, pro- vided that both the copyright notice and this permis- sion notice appear in all copies of the software, de- rivative works or modified versions, and any portions thereof, and that both notices appear in supporting documentation. CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN ITS "AS IS" CONDITION. CARNEGIE MELLON DISCLAIMS ANY LIABILITY OF ANY KIND FOR ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE. Carnegie Mellon requests users of this software to return to Software Distribution Coordinator or Software.Dis- tribution@CS.CMU.EDU School of Computer Science Carnegie Mellon University Pittsburgh PA 15213-3890 any improvements or extensions that they make and grant Carnegie the rights to redistribute these changes. Some files have the following copyright: Copyright (C) 1989 Digital Equipment Corpora- tion. Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies. Digital Equipment Corporation makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied war- ranty. Some files have the following copyright: Copyright 1996 The Board of Trustees of The Leland Stanford Junior University. All Rights Reserved. Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies. Stanford Uni- versity makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty. The End NetBSD May 13, 2019 NetBSD