February 2, 2012 INSTALL 8 NetBSD


INSTALL - Installation procedure for NetBSD/sandpoint.



About this Document............................................2 What is NetBSD?................................................2 Dedication.....................................................3 Changes Between the NetBSD 5.1 and 5.1.2 Releases..............3 Security Advisory Fixes.....................................3 Other Security Fixes........................................4 Kernel......................................................4 Networking..................................................4 Miscellaneous...............................................4 Known Problems..............................................4 Features to be removed in a later release......................5 The NetBSD Foundation..........................................5 Sources of NetBSD..............................................5 NetBSD 5.1.2 Release Contents..................................5 NetBSD/sandpoint subdirectory structure.....................6 Binary distribution sets....................................7 NetBSD/sandpoint System Requirements and Supported Devices.....8 Supported processor cards...................................8 Supported devices...........................................8 Unsupported devices.........................................9 Supported boot devices and media............................9 Getting the NetBSD System on to Useful Media...................9 Preparing your System for NetBSD installation.................11 Booting over a serial line.................................11 Installing the NetBSD System..................................11 Booting the installer......................................11 Example of a normal boot...................................11 Common Problems and Error Messages.........................11 Running the sysinst installation program...................11 Introduction............................................11 Possible hardware problems..............................12 General.................................................12 Quick install...........................................12 Booting NetBSD..........................................13 Network configuration...................................13 Installation drive selection and parameters.............13 Selecting which sets to install.........................14 Partitioning the disk...................................14 Preparing your hard disk................................14 Getting the distribution sets...........................15 Installation from CD-ROM................................15 Installation using ftp..................................15 Installation using NFS..................................15 Installation from an unmounted file system..............16 Installation from a local directory.....................16 Extracting the distribution sets........................16 Finalizing your installation............................16 Post installation steps.......................................16 Upgrading a previously-installed NetBSD System................19 Compatibility Issues With Previous NetBSD Releases............19 Issues when running older binaries on NetBSD 5.1.2.........20 Issues affecting an upgrade from NetBSD 3.x releases.......20 Issues affecting an upgrade from NetBSD 4.x releases.......21 Using online NetBSD documentation.............................22 Administrivia.................................................22 Thanks go to..................................................23 We are........................................................24 Legal Mumbo-Jumbo.............................................30 The End.......................................................36


About this Document

This document describes the installation procedure for NetBSD 5.1.2 on the sandpoint platform. It is available in four different formats titled INSTALL.ext, where .ext is one of .ps, .html, .more, or .txt:


Standard Internet HTML.

The enhanced text format used on UNIX-like systems by the more(1) and less(1) pager utility programs. This is the format in which the on-line man pages are generally presented.

Plain old ASCII.

You are reading the HTML version.

What is NetBSD?

The NetBSD Operating System is a fully functional Open Source UNIX-like operating system derived from the University of California, Berkeley Networking Release 2 (Net/2), 4.4BSD-Lite, and 4.4BSD-Lite2 sources. NetBSD runs on 57 different system architectures (ports) across 15 distinct CPU families, and is being ported to more. The NetBSD 5.1.2 release contains complete binary releases for many different system architectures. (A few ports are not fully supported at this time and are thus not part of the binary distribution. Please see the NetBSD web site 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 features a complete set of user utilities, compilers for several 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 community. Without the unique cooperation and coordination the net makes possible, it's likely that NetBSD wouldn't exist.


NetBSD 5.1.2 is dedicated to the memory of Yoshihiro Masuda, who passed away in May 2011.

He was a spiritual pillar of the BSD community in Japan. Through an impressive number of books and articles on BSD, he gave courage to BSD developers. We remember his passion and deep love for BSD.

Changes Between the NetBSD 5.1 and 5.1.2 Releases

NetBSD 5.1.2 is the second critical/security update of the NetBSD 5.1 release branch. It represents a selected subset of fixes deemed critical for security or stability reasons.

Please note that all fixes in security/critical updates (i.e., NetBSD 5.0.1, 5.0.2, etc.) are cumulative, so the latest update contains all such fixes since the corresponding minor release. These fixes also appear in minor releases (i.e., NetBSD 5.1, 5.2, etc.).

The complete list of changes can be found in the CHANGES-5.1.2: http://ftp.NetBSD.org/pub/NetBSD/NetBSD-5.1.2/CHANGES-5.1.2 file in the top level directory of the NetBSD 5.1.2 release tree. Note that since 5.1.1 was not announced, the changes below are relative to 5.1, not 5.1.1. An abbreviated list is as follows:

Security Advisory Fixes

Advisories prior to NetBSD-SA2010-012 do not affect NetBSD 5.1.2: http://www.NetBSD.org/support/security/patches-5.1.2.html.

Other Security Fixes
Known Problems

Using block device nodes (e.g., wd0a) directly for I/O may cause a kernel crash when the file system containing /dev is FFS and is mounted with -o log. Workaround: use raw disk devices (e.g., rwd0a), or remount the file system without -o log.

Occassionally, gdb may cause a process that is being debugged to hang when ``single stepped''. Workaround: kill and restart the affected process.

gdb cannot debug running threaded programs correctly. Workaround: generate a core file from the program using gcore(1) and pass the core to gdb, instead of debugging the running program.

The sparc port does not have functional SMP support in this release.

Features to be removed in a later release

The following features are to be removed from NetBSD in the future:

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 trademark of the word ``NetBSD''. It supports the design, development, 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 5.1.2 Release Contents

The root directory of the NetBSD 5.1.2 release is organized as follows:


Changes between the 4.0 and 5.0 releases.

Changes between the initial 5.0 branch and final release of 5.0.

Changes between the 5.0 and 5.1 releases.

Changes between the 5.1 and 5.1.1 releases.

Changes between the 5.1.1 and 5.1.2 releases.

Changes in previous NetBSD releases.

Last minute changes and notes about the release.

README describing the distribution's contents.

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 5.1.2 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 distribution sets are as follows:

This set contains the ``gnu'' sources, including the source for the compiler, assembler, groff, and the other GNU utilities in the binary distribution sets.

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.

This set contains all of the base NetBSD 5.1.2 sources which are not in gnusrc, sharesrc, or syssrc.

This set contains the sources to the NetBSD 5.1.2 kernel for all architectures as well as the config(1) utility.

This set contains the sources to the X Window System.

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 digests in the format produced by the command:
cksum -a MD5 file.

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/sandpoint subdirectory structure
The sandpoint-specific portion of the NetBSD 5.1.2 release is found in the sandpoint subdirectory of the distribution: .../NetBSD-5.1.2/sandpoint/. It contains the following files and directories:

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.
A gzipped NetBSD kernel containing code for everything supported in this release.
sandpoint binary distribution sets; see below.
sandpoint boot and installation floppies; see below.
Miscellaneous sandpoint installation utilities; see installation section below.
Binary distribution sets
The NetBSD sandpoint binary distribution sets contain the binaries which comprise the NetBSD 5.1.2 release for sandpoint. The binary distribution sets can be found in the sandpoint/binary/sets subdirectory of the NetBSD 5.1.2 distribution tree, and are as follows:

The NetBSD 5.1.2 sandpoint 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.

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.

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.

This set includes the games and their manual pages.

This set contains a NetBSD/sandpoint 5.1.2 GENERIC kernel, named /netbsd. You must install this distribution set.

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.

This set includes the system dictionaries, the typesettable document set, and other files from /usr/share.

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 compatibility. These sources are based on XFree86 4.5.0. Binary sets for the X Window System are distributed with NetBSD. The sets are:

The basic files needed for a complete X client environment. This does not include the X servers.

The extra libraries and include files needed to compile X source code.

Fonts needed by the X server and by X clients.

Configuration files for X which could be locally modified.

The X server.

The sandpoint 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.

Each directory in the sandpoint binary distribution also has its own checksum files, just as the source distribution does.

NetBSD/sandpoint System Requirements and Supported Devices

Currently, NetBSD/sandpoint requires the use of Motorola's DINK32 ROM to load over a serial port. This means that there is no way to boot from a local disk or PCI device.

Supported processor cards

Other PMCs should work, but may need minor adjustments or more substantial work to support additional functionality.

Supported devices
Unsupported devices
Supported boot devices and media
Currently, the only way to boot the system is with the DINK32 ROM monitor's serial download or a JTAG device.

Getting the NetBSD System on to Useful Media

Note that if you are installing or upgrading from writable media, it can be write-protected if you wish. These systems mount a root image from inside the kernel, and will not need to write to the media. If you booted from a floppy, the floppy disk may be removed from the drive after the system has booted.

Installation is supported from several media types, including:

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.

Find out where the distribution set files are on the CD-ROM or DVD. Likely locations are binary/sets and sandpoint/binary/sets.

Proceed to the instructions on installation.

MS-DOS floppy
NetBSD does not include split distribution sets for installation by floppy. However, they can be created on a separate machine using the split(1) command, running e.g. split -b 235k base.tgz base. to split the base.tgz file from sandpoint/binary/sets into files named base.aa, base.ab, and so on. Repeat this for all set_name.tgz files, splitting them into set_name.xx files. Count the number of set_name.xx files that make up the distribution sets you want to install or upgrade. You will need one sixth that number of 1.44 MB floppies.

Format all of the floppies with MS-DOS. Do not make any of them bootable MS-DOS floppies, i.e. don't use format /s to format them. (If the floppies are bootable, then the MS-DOS system files that make them bootable will take up some space, and you won't be able to fit the distribution set parts on the disks.) If you're using floppies that are formatted for MS-DOS by their manufacturers, they probably aren't bootable, and you can use them out of the box.

Place all of the set_name.xx files on the MS-DOS disks.

Once you have the files on MS-DOS disks, 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 upgrading.

The preparations for this installation/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 network, 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 upgrading.

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 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 information mentioned above, 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 upgrading.

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_directories

where tape_device is the name of the tape device that describes the tape drive you're using; possibly /dev/rst0, or something similar, but it will vary from system to system. (If you can't figure it out, ask your system administrator.) In the above example, dist_directories are the distribution sets' directories, for the distribution sets you wish to place on the tape. For instance, to put the kern-GENERIC, base, and etc distributions on tape (in order to do the absolute minimum installation to a new disk), you would do the following:

       # cd .../NetBSD-5.1.2
       # cd sandpoint/binary
       # tar -cf tape_device kern-GENERIC base etc

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 installation, go directly to the section on upgrading.

Preparing your System for NetBSD installation

When installing NetBSD for your NetBSD5.1.2 system, you have to decide where you want your root partition and how you'll be downloading your kernel. Since the IBM ROM rather limits your boot options, you won't be able to have the machine boot independently. Once you load the kernel, however, you may have the root file system on a local disk or you can configure a diskless setup.

In either case, you'll need to set up to boot the kernel over the network or over a serial line.

Booting over a serial line
This is not currently documented or supported. If you would like to attempt this and supply documentation, please do!

Installing the NetBSD System

Booting the installer
Once the kernel is downloaded, type "go 90000" to start the kernel.
Example of a normal boot
Of course, a lot of the information in this example depends on your model and what your boot method is, but we'll include this anyways just so you get an idea of what to expect (user-typed commands are in bold).
DINK32>> go 90000
[ XXX - insert boot w/ installer on ramdisk instead of this example ]
Common Problems and Error Messages
Insufficient data.

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 in hand when doing the installation process. This document tries to be a good guide to the installation, and as such, covers many details for the sake of completeness. Do not let this discourage you; the install program is not hard to use.

  2. Possible hardware problems

    Should you encounter hardware problems during installation, try rebooting after unplugging removable devices you don't need for installation. Non-removable devices can be disabled with userconf (use boot -c to enter it).

  3. General

    The following is a walk-through of the steps you will take while getting NetBSD installed on your hard disk. sysinst is a menu driven installation system that allows for some freedom in doing the installation. Sometimes, questions will be asked and in many cases the default answer will be displayed in brackets (``[ ]'') after the question. 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.

  4. Quick install

    First, let's describe a quick install. The other sections of this document go into the installation procedure 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-ROM install as an example.

  5. Booting NetBSD

    Boot your machine. The boot loader will start, and will print a countdown and begin booting.

    If the boot loader messages do not appear in a reasonable amount of time, you either have a bad boot floppy or a hardware problem. Try writing the install floppy image to a different disk, and using that.

    It will take a while to load the kernel from the floppy, probably around a minute or so, then, the kernel boot messages will be displayed. This may take a little while also, as NetBSD will be probing your system to discover which hardware devices are installed. The most important thing to know is that wd0 is NetBSD's name for your first IDE disk, wd1 the second, etc. sd0 is your first SCSI disk, sd1 the second, etc.

    Note that once the system has finished booting, you need not leave the floppy in the disk drive.

    Once NetBSD has booted and printed all the boot messages, you will be presented with a welcome message and a main menu. It will also include instructions for using the menus.

  6. Network configuration

    If you do not intend to use networking during the installation, but you do want your machine to be configured 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.

  7. 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.

  8. Selecting which sets to install

    The next step is to choose which distribution sets you wish to install. Options are provided for full, minimal, and custom installations. If you choose sets on your own, base, etc, and a kernel must be selected.

  9. Partitioning the disk

  10. Editing the NetBSD disklabel

    The partition table of the NetBSD part of a disk is called a disklabel. If your disk already has a disklabel 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 disklabel 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.

    Root partition (/)

    Swap partition.

    The NetBSD portion of the disk.

    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 characters. You don't need to remember this name.

  11. 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 make 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. Otherwise, you can continue the installation program after pressing the return key.

  12. Getting the distribution sets

    The NetBSD distribution consists of a number of sets that come in the form of gzipped tarfiles. 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 load the sets on your hard disk, others will extract the sets directly.

    For all these methods, the first step is making the sets available for extraction, and then do the actual installation. The sets can be made available in a few different ways. The following sections describe each of those methods. After reading the one about the method you will be using, you can continue to the section labeled `Extracting the distribution sets'.

  13. 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 if the files are indeed available in the specified location, and proceed to the actual extraction of the sets.

  14. Installation using ftp

    To be able to install using ftp, 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, 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 specify an IP address instead of a hostname for the ftp server.

    sysinst will proceed to transfer all the default set files from the remote site to your hard disk.

  15. Installation using NFS

    To be able 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.

  16. 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 sd1e) 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.

  17. 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.

  18. Extracting the distribution sets

    Before extraction begins, you can elect to watch the files being extracted; the name of each file that is extracted will be shown. This can slow down the installation process considerably on machines with slow graphics consoles or serial consoles. Alternatively, you can choose to see a progress bar. This is the preferred option as it shows progress without significantly slowing down the installation process.

    After all the files have been extracted, the device node files will be created. If you have already configured 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 configuration files. The next menu will allow you to select the time zone that you're in, to make sure your clock has the right offset from UTC. Finally you will be asked to select a password encryption algorithm and can then set a password for the "root" account, to prevent the machine from coming up without access restrictions.

  19. Finalizing your installation

    Congratulations, you have successfully installed NetBSD 5.1.2. 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. Configuring /etc/rc.conf

    If you or the installation software haven't done any configuration of /etc/rc.conf (sysinst usually 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 whatever is appropriate for your terminal type) and press RETURN. You may need to type one of the following commands to get your delete key to work properly, depending 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 proceed. Default values for the various programs can be found in /etc/defaults/rc.conf, where some in-line documentation 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 continue 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 <int> network interface, along the lines of

           ifconfig_tlp0="inet netmask"

    or, if you have myname.my.dom in /etc/hosts:

           ifconfig_tlp0="inet myname.my.dom netmask"

    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 network and naming service, DHCP can be used by setting dhclient=YES in /etc/rc.conf.

    Other files in /etc that may require modification or setting up include /etc/mailer.conf, /etc/nsswitch.conf, and /etc/wscons.conf.

  2. Logging in

    After reboot, you can log in as root at the login prompt. Unless you've 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.

  3. Adding accounts

    Use the useradd(8) command to add accounts to your system. Do not edit /etc/passwd directly! See vipw(8) and pwd_mkdb(8) if you want to edit the password database.

  4. 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://netbsd.org/docs/guide/en/chap-x.html

  5. 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 necessary to make the software run on NetBSD. This includes the retrieval and installation of any other packages on which the software may depend.

  6. Misc

Upgrading a previously-installed NetBSD System

The easiest way to upgrade to NetBSD 5.1.2 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. If you have a few megabytes free on each of your root (/) and /usr partitions, you should have enough space.

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 operating 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. sysinst will attempt to merge the settings stored in your /etc directory with the new version of NetBSD. Also, file systems are checked before unpacking the sets. Fetching the binary sets is done in the same manner as the installation procedure; refer to the installation part of the document for help.

After a new kernel has been copied to your hard disk, your machine is a complete NetBSD 5.1.2 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

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.

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 5.1.2.

Note: None of the items mentioned below are relevant if upgrading from 5.1. They still apply if you are upgrading from a pre-5.1 release, though.

If your port uses X.Org and you see messages from the X server indicating that no devices were found, you may need to run X -configure and update your existing xorg.conf to use the BusID line from the newly-generated config file.

Dual-head support for PC systems has become broken for many configurations with the update to xorg-server 1.6.x, which has removed the userland PCI configuration mechanism, and needs to rely upon the OS. We hope to correct this for future releases. Workaround: The only workaround is non-trivial and requires programming several PCI BAR registers as they previously were in NetBSD 5.0.

If you are updating to NetBSD 5.1.2 without the aid of sysinst or postinstall and your port uses X.Org, be sure to remove /usr/X11R7/lib/X11/xkb/symbols/pc before extracting the xbase set. In the version of X.Org shipped with 5.0, this was a directory, but in more recent X.Org versions it is a file.

pkg_install now depends on the pkgdb cache for automatic conflict detection. It is recommended to rebuild the cache with

       # pkg_admin rebuild

audit-packages.conf(5) has been superseded by pkg_install.conf(5). The default configuration is the same.

Support for pkg_view(1) has been retired.

The functionality of audit-packages(1) and download-vulnerability-list(1) has moved into pkg_admin(1). However, wrapper scripts that handle the common use cases are provided.

Issues when running older binaries on NetBSD 5.1.2

The pthread libraries from previous versions of NetBSD require that the sysctl(3) node kern.no_sa_support be set to 0. This affects the following environments:

The 5.x kernel defaults to 0 for kern.no_sa_support, which covers the first case. However, please note that a full installation of 5.x (either from scratch or through an upgrade) will set kern.no_sa_support to 1 during the boot process. This means that for the last two cases, you will have to manually set kern.no_sa_support to 0, using either the sysctl(8) command or through sysctl.conf(5).

Note that sysinst will automatically invoke

postinstall fix
and thus all issues that are fixed by postinstall by default (see below) will be handled.
Issues affecting an upgrade from NetBSD 3.x releases
See the section below on upgrading from NetBSD 4.x as well.

The following issues can generally be resolved by running postinstall with the etc set:

postinstall -s /path/to/etc.tgz check
postinstall -s /path/to/etc.tgz fix

Issues fixed by postinstall:

The following issues need to be resolved manually:

Issues affecting an upgrade from NetBSD 4.x releases

The following issues can generally be resolved by running postinstall with the etc set:

postinstall -s /path/to/etc.tgz check
postinstall -s /path/to/etc.tgz fix

Issues fixed by postinstall:

The following issues need to be resolved manually:

Using online NetBSD documentation

Documentation is available if you installed the manual distribution set. Traditionally, the ``man pages'' (documentation) are denoted by `name(section)'. Some examples of this are

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 lowest 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


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.


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. To get help on using the mailing list server, send mail to that address with an empty body, and it will reply with instructions. See http://www.NetBSD.org/mailinglists/ for a web interface.

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 interface 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 this effort, 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 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

We are...

(in alphabetical order)

The NetBSD core group:
Alan Barrettapb@NetBSD.org
Alistair Crooksagc@NetBSD.org
Matthew Greenmrg@NetBSD.org
Chuck Silverschs@NetBSD.org
Matt Thomasmatt@NetBSD.org
YAMAMOTO Takashiyamt@NetBSD.org
Christos Zoulaschristos@NetBSD.org

The portmasters (and their ports):
Erik Berlscyber@NetBSD.org cobalt
Manuel Bouyerbouyer@NetBSD.org xen
Simon Burgesimonb@NetBSD.org evbmips
Simon Burgesimonb@NetBSD.org pmax
Simon Burgesimonb@NetBSD.org sbmips
Julian Colemanjdc@NetBSD.org atari
Andrew Doranad@NetBSD.org amd64
Andrew Doranad@NetBSD.org i386
Matthias Drochnerdrochner@NetBSD.org cesfic
Gavan Fantomgavan@NetBSD.org iyonix
Nick Hudsonskrll@NetBSD.org hp700
Martin Husemannmartin@NetBSD.org sparc64
Sren Jrvangsoren@NetBSD.org sgimips
Takayoshi Kochikochi@NetBSD.org ia64
Michael Lorenzmacallan@NetBSD.org macppc
Anders Magnussonragge@NetBSD.org vax
Tohru Nishimuranisimura@NetBSD.org luna68k
Tohru Nishimuranisimura@NetBSD.org sandpoint
Scott Reynoldsscottr@NetBSD.org mac68k
Tim Rightnourgarbled@NetBSD.org ofppc
Tim Rightnourgarbled@NetBSD.org prep
Tim Rightnourgarbled@NetBSD.org rs6000
Noriyuki Sodasoda@NetBSD.org arc
Ignatios Souvatzisis@NetBSD.org amiga
Ignatios Souvatzisis@NetBSD.org amigappc
NISHIMURA Takeshinsmrtks@NetBSD.org x68k
Matt Thomasmatt@NetBSD.org alpha
Matt Thomasmatt@NetBSD.org ibmnws
Matt Thomasmatt@NetBSD.org netwinder
Izumi Tsutsuitsutsui@NetBSD.org ews4800mips
Izumi Tsutsuitsutsui@NetBSD.org hp300
Izumi Tsutsuitsutsui@NetBSD.org news68k
Valeriy E. Ushakovuwe@NetBSD.org hpcsh
Valeriy E. Ushakovuwe@NetBSD.org landisk
Steve Woodfordscw@NetBSD.org evbppc
Steve Woodfordscw@NetBSD.org mvme68k
Steve Woodfordscw@NetBSD.org mvmeppc
Reinoud Zandijkreinoud@NetBSD.org acorn32
The NetBSD 5.1.2 Release Engineering team:
Stephen Borrillsborrill@NetBSD.org
Manuel Bouyerbouyer@NetBSD.org
David Brownleeabs@NetBSD.org
James Chaconjmc@NetBSD.org
Julian Colemanjdc@NetBSD.org
Hvard Eidneshe@NetBSD.org
Alistair Grooksagc@NetBSD.org
John Heasleyheas@NetBSD.org
Martin Husemannmartin@NetBSD.org
Soren Jacobsensnj@NetBSD.org
Mark Kirbymkirby@NetBSD.org
Phil Nelsonphil@NetBSD.org
Jeremy C. Reedreed@NetBSD.org
Jeff Rizzoriz@NetBSD.org
SAITOH Masanobumsaitoh@NetBSD.org

NetBSD Developers:
Nathan Ahlstromnra@NetBSD.org
Steve Allenwormey@NetBSD.org
Jukka Andbergjandberg@NetBSD.org
Julian Assangeproff@NetBSD.org
Lennart Augustssonaugustss@NetBSD.org
Christoph Badurabad@NetBSD.org
Bang Jun-Youngjunyoung@NetBSD.org
Dieter Barondillo@NetBSD.org
Robert V. Baronrvb@NetBSD.org
Alan Barrettapb@NetBSD.org
Grant Beattiegrant@NetBSD.org
Jason Beeganjtb@NetBSD.org
Erik Berlscyber@NetBSD.org
Hiroyuki Besshobsh@NetBSD.org
John Birrelljb@NetBSD.org
Mason Loring Blissmason@NetBSD.org
Charles Blundellcb@NetBSD.org
Rafal Bonirafal@NetBSD.org
Stephen Borrillsborrill@NetBSD.org
Sean Boudreauseanb@NetBSD.org
Manuel Bouyerbouyer@NetBSD.org
John Brezakbrezak@NetBSD.org
Allen Briggsbriggs@NetBSD.org
Mark Brinicombemark@NetBSD.org
Aaron Brownabrown@NetBSD.org
Andrew Brownatatat@NetBSD.org
David Brownleeabs@NetBSD.org
Frederick Bruckmanfredb@NetBSD.org
Jon Bullerjonb@NetBSD.org
Simon Burgesimonb@NetBSD.org
Robert Byrnesbyrnes@NetBSD.org
Pavel Cahynapavel@NetBSD.org
D'Arcy J.M. Caindarcy@NetBSD.org
Daniel Carosonedan@NetBSD.org
Dave Carrelcarrel@NetBSD.org
James Chaconjmc@NetBSD.org
Mihai Chelarukefren@NetBSD.org
Bill Coldwellbillc@NetBSD.org
Julian Colemanjdc@NetBSD.org
Ben Collverben@NetBSD.org
Marcus Comstedtmarcus@NetBSD.org
Jeremy Cooperjeremy@NetBSD.org
Chuck Cranorchuck@NetBSD.org
Alistair Crooksagc@NetBSD.org
Aidan Cullyaidan@NetBSD.org
Garrett D'Amoregdamore@NetBSD.org
Johan Danielssonjoda@NetBSD.org
John Darrowjdarrow@NetBSD.org
Jed Davisjld@NetBSD.org
Matt DeBergalisdeberg@NetBSD.org
Arnaud Degrootedegroote@NetBSD.org
Rob Dekerdeker@NetBSD.org
Chris G. Demetrioucgd@NetBSD.org
Tracy Di Marco Whitegendalia@NetBSD.org
Jaromr Dolecekjdolecek@NetBSD.org
Andy Doranad@NetBSD.org
Roland Dowdeswellelric@NetBSD.org
Emmanuel Dreyfusmanu@NetBSD.org
Matthias Drochnerdrochner@NetBSD.org
Jun Ebiharajun@NetBSD.org
Hvard Eidneshe@NetBSD.org
Jaime A Fournierober@NetBSD.org
Stoned Elipotseb@NetBSD.org
Michael van Elstmlelstv@NetBSD.org
Enami Tsugutomoenami@NetBSD.org
Bernd Ernestiveego@NetBSD.org
Erik Fairfair@NetBSD.org
Gavan Fantomgavan@NetBSD.org
Hauke Fathhauke@NetBSD.org
Hubert Feyrerhubertf@NetBSD.org
Jason R. Finkjrf@NetBSD.org
Matt J. Flemingmjf@NetBSD.org
Marty Foutsmarty@NetBSD.org
Liam J. Foyliamjfoy@NetBSD.org
Matt Fredettefredette@NetBSD.org
Thorsten Frueauffrueauf@NetBSD.org
Castor Fucastor@NetBSD.org
Ichiro Fukuharaichiro@NetBSD.org
Quentin Garniercube@NetBSD.org
Thomas Gernerthomas@NetBSD.org
Simon J. Gerratysjg@NetBSD.org
Justin Gibbsgibbs@NetBSD.org
Chris Gilbertchris@NetBSD.org
Eric Gillespieepg@NetBSD.org
Brian Ginsbachginsbach@NetBSD.org
Paul Goyettepgoyette@NetBSD.org
Michael Graffexplorer@NetBSD.org
Brian C. Graysonbgrayson@NetBSD.org
Matthew Greenmrg@NetBSD.org
Andreas Gustafssongson@NetBSD.org
Ulrich Habelrhaen@NetBSD.org
Jun-ichiro itojun Haginoitojun@NetBSD.org
HAMAJIMA Katsuomihamajima@NetBSD.org
Adam Hamsikhaad@NetBSD.org
Juergen Hannken-Illjeshannken@NetBSD.org
Charles M. Hannummycroft@NetBSD.org
Ben Harrisbjh21@NetBSD.org
Ross Harveyross@NetBSD.org
Eric Haszlakiewiczerh@NetBSD.org
John Hawkinsonjhawk@NetBSD.org
HAYAKAWA Koichihaya@NetBSD.org
John Heasleyheas@NetBSD.org
Geert Hendrickxghen@NetBSD.org
Ren Hexelrh@NetBSD.org
Iain Hibbertplunky@NetBSD.org
Kouichirou Hiratsukahira@NetBSD.org
Michael L. Hitchmhitch@NetBSD.org
dm Hkaahoka@NetBSD.org
Jachym Holecekfreza@NetBSD.org
David A. Hollanddholland@NetBSD.org
Christian E. Hoppschopps@NetBSD.org
Ken Hornsteinkenh@NetBSD.org
Marc Horowitzmarc@NetBSD.org
Eduardo Horvatheeh@NetBSD.org
Nick Hudsonskrll@NetBSD.org
Shell Hungshell@NetBSD.org
Martin Husemannmartin@NetBSD.org
Dean Huxleydean@NetBSD.org
Love Hrnquist strandlha@NetBSD.org
Roland Illigrillig@NetBSD.org
Bernardo Innocentibernie@NetBSD.org
Tetsuya Isakiisaki@NetBSD.org
ITOH Yasufumiitohy@NetBSD.org
IWAMOTO Toshihirotoshii@NetBSD.org
Matthew Jacobmjacob@NetBSD.org
Soren Jacobsensnj@NetBSD.org
Lonhyn T. Jasinskyjlonhyn@NetBSD.org
Darrin Jewelldbj@NetBSD.org
Nicolas Jolynjoly@NetBSD.org
Chris Jonescjones@NetBSD.org
Sren Jrvangsoren@NetBSD.org
Takahiro Kambetaca@NetBSD.org
Masanori Kanaokakanaoka@NetBSD.org
Antti Kanteepooka@NetBSD.org
Frank Kardelkardel@NetBSD.org
Mattias Karlssonkeihan@NetBSD.org
KAWAMOTO Yosihisakawamoto@NetBSD.org
Mario Kempermagick@NetBSD.org
Min Sik Kimminskim@NetBSD.org
Thomas Klausnerwiz@NetBSD.org
Klaus Kleinkleink@NetBSD.org
John Klosjklos@NetBSD.org
Wayne Knowleswdk@NetBSD.org
Takayoshi Kochikochi@NetBSD.org
John Kohljtk@NetBSD.org
Daniel de Kokdaniel@NetBSD.org
Jonathan A. Kollaschjakllsch@NetBSD.org
Paul Kranenburgpk@NetBSD.org
Lubomir Kundraklkundrak@NetBSD.org
Jochen Kunzjkunz@NetBSD.org
Martti Kuparinenmartti@NetBSD.org
Kentaro A. Kurahonekurahone@NetBSD.org
Arnaud Lacombealc@NetBSD.org
Kevin Laheykml@NetBSD.org
David Laightdsl@NetBSD.org
Johnny C. Lamjlam@NetBSD.org
Martin J. Laubachmjl@NetBSD.org
Greg Leheygrog@NetBSD.org
Ted Lemonmellon@NetBSD.org
Christian Limpachcl@NetBSD.org
Frank van der Lindenfvdl@NetBSD.org
Joel Lindholmjoel@NetBSD.org
Tonnerre Lombardtonnerre@NetBSD.org
Mike Longmikel@NetBSD.org
Michael Lorenzmacallan@NetBSD.org
Warner Loshimp@NetBSD.org
Tomasz Luchowskizuntum@NetBSD.org
Federico Lupifederico@NetBSD.org
Brett Lymnblymn@NetBSD.org
Paul Mackerraspaulus@NetBSD.org
MAEKAWA Masahidegehenna@NetBSD.org
Anders Magnussonragge@NetBSD.org
Cherry G. Mathewcherry@NetBSD.org
David Maxwelldavid@NetBSD.org
Gregory McGarrygmcgarry@NetBSD.org
Dan McMahilldmcmahill@NetBSD.org
Jared D. McNeilljmcneill@NetBSD.org
Neil J. McRaeneil@NetBSD.org
Julio M. Merino Vidaljmmv@NetBSD.org
Perry Metzgerperry@NetBSD.org
Luke Mewburnlukem@NetBSD.org
Jean-Yves Migeonjym@NetBSD.org
Brook Milliganbrook@NetBSD.org
Minoura Makotominoura@NetBSD.org
Simas Mockeviciussymka@NetBSD.org
der Mousemouse@NetBSD.org
Joseph Myersjsm@NetBSD.org
Ken Nakatakenn@NetBSD.org
Takeshi Nakayamanakayama@NetBSD.org
Phil Nelsonphil@NetBSD.org
John Nemethjnemeth@NetBSD.org
Bob Nestorrnestor@NetBSD.org
NISHIMURA Takeshinsmrtks@NetBSD.org
Tohru Nishimuranisimura@NetBSD.org
NONAKA Kimihirononaka@NetBSD.org
Takehiko NOZAKItnozaki@NetBSD.org
Tobias Nygrentnn@NetBSD.org
OBATA Akioobache@NetBSD.org
Jesse Offjoff@NetBSD.org
Tatoku Ogaitotacha@NetBSD.org
OKANO Takayoshikano@NetBSD.org
Masaru Okioki@NetBSD.org
Atsushi Onoeonoe@NetBSD.org
Greg Osteroster@NetBSD.org
Rui Paulorpaulo@NetBSD.org
Jonathan Perkinsketch@NetBSD.org
Andrey Petrovpetrov@NetBSD.org
Herb Peyerlhpeyerl@NetBSD.org
Matthias Pfallermatthias@NetBSD.org
Chris Pinnockcjep@NetBSD.org
Adrian Portelliadrianp@NetBSD.org
Peter Postmapeter@NetBSD.org
Dante Profetadante@NetBSD.org
Chris Provenzanoproven@NetBSD.org
Niels Provosprovos@NetBSD.org
Mindaugas Rasiukeviciusrmind@NetBSD.org
Michael Rauchmrauch@NetBSD.org
Marc Rechtrecht@NetBSD.org
Darren Reeddarrenr@NetBSD.org
Jeremy C. Reedreed@NetBSD.org
Antoine Reillestonio@NetBSD.org
Tyler R. Retzlaffrtr@NetBSD.org
Scott Reynoldsscottr@NetBSD.org
Michael Richardsonmcr@NetBSD.org
Tim Rightnourgarbled@NetBSD.org
Alan Ritterrittera@NetBSD.org
Jeff Rizzoriz@NetBSD.org
Hans Rosenfeldhans@NetBSD.org
Gordon Rossgwr@NetBSD.org
Steve Rumblerumble@NetBSD.org
Ilpo Ruotsalainenlonewolf@NetBSD.org
Heiko W. Rupphwr@NetBSD.org
Blair J. Sadewitzbjs@NetBSD.org
David Saintydsainty@NetBSD.org
SAITOH Masanobumsaitoh@NetBSD.org
Kazuki Sakamotosakamoto@NetBSD.org
Curt Sampsoncjs@NetBSD.org
Wilfredo Sanchezwsanchez@NetBSD.org
Ty Sarnatsarna@NetBSD.org
SATO Kazumisato@NetBSD.org
Jan Schaumannjschauma@NetBSD.org
Matthias Schelertron@NetBSD.org
Silke Schelersilke@NetBSD.org
Karl Schilke (rAT)rat@NetBSD.org
Amitai Schlairschmonz@NetBSD.org
Konrad Schroderperseant@NetBSD.org
Georg Schwarzschwarz@NetBSD.org
Lubomir Sedlaciksalo@NetBSD.org
Christopher SEKIYAsekiya@NetBSD.org
Reed Shadgettdent@NetBSD.org
John Shannonshannonjr@NetBSD.org
Tim Shepardshep@NetBSD.org
Takeshi Shibagakishiba@NetBSD.org
Naoto Shimazakiigy@NetBSD.org
Takao Shinoharashin@NetBSD.org
Takuya SHIOZAKItshiozak@NetBSD.org
Daniel Siegerdsieger@NetBSD.org
Chuck Silverschs@NetBSD.org
Thor Lancelot Simontls@NetBSD.org
Jeff Smithjeffs@NetBSD.org
Noriyuki Sodasoda@NetBSD.org
Wolfgang Solfrankws@NetBSD.org
SOMEYA Yoshihikosomeya@NetBSD.org
Bill Sommerfeldsommerfeld@NetBSD.org
Jrg Sonnenbergerjoerg@NetBSD.org
Ignatios Souvatzisis@NetBSD.org
T K Spindlerdogcow@NetBSD.org
Bill Squiergroo@NetBSD.org
Jonathan Stonejonathan@NetBSD.org
Bill Studenmundwrstuden@NetBSD.org
Kevin Sullivansullivan@NetBSD.org
SUNAGAWA Keikikei@NetBSD.org
Kimmo Suominenkim@NetBSD.org
Robert Swindellsrjs@NetBSD.org
Shin Takemuratakemura@NetBSD.org
TAMURA Kentkent@NetBSD.org
Shin'ichiro TAYAtaya@NetBSD.org
Ian Lance Taylorian@NetBSD.org
Matt Thomasmatt@NetBSD.org
Jason Thorpethorpej@NetBSD.org
Christoph Toshoktoshok@NetBSD.org
Greg Troxelgdt@NetBSD.org
Tsubai Masanaritsubai@NetBSD.org
Izumi Tsutsuitsutsui@NetBSD.org
UCHIYAMA Yasushiuch@NetBSD.org
Masao Uebayashiuebayasi@NetBSD.org
Shuichiro URATAur@NetBSD.org
Valeriy E. Ushakovuwe@NetBSD.org
Todd Vierlingtv@NetBSD.org
Aymeric Vincentaymeric@NetBSD.org
Paul Vixievixie@NetBSD.org
Mike M. Volokhovmishka@NetBSD.org
Krister Walfridssonkristerw@NetBSD.org
Lex Wennmacherwennmach@NetBSD.org
Leo Weppelmanleo@NetBSD.org
Assar Westerlundassar@NetBSD.org
Todd Whiteseltoddpw@NetBSD.org
Frank Willephx@NetBSD.org
Nathan Williamsnathanw@NetBSD.org
Rob Windsorwindsor@NetBSD.org
Dan Winshipdanw@NetBSD.org
Jim Wisejwise@NetBSD.org
Michael Wolfsonmbw@NetBSD.org
Colin Woodender@NetBSD.org
Steve Woodfordscw@NetBSD.org
YAMAMOTO Takashiyamt@NetBSD.org
Yuji Yamanoyyamano@NetBSD.org
David Youngdyoung@NetBSD.org
Reinoud Zandijkreinoud@NetBSD.org
Maria Zevenhovenmaria7@NetBSD.org
Christos Zoulaschristos@NetBSD.org

Other contributors:
Dave 'qmP~>? K?r0r[6TV7r{чU.CF wƉ5wIm]C>mZn%rlV ; 9O̚RIL)8Ɂ֥`RF,Ɣ}ψ4v_e ڨK̀s:Fm ,#[2,uP=L_eē0ۚ\u>[w7ꒊko՚37&>+v3), #KE}I;'&vye+5<ΐaƞ$Q&&Eob*:v SάR` w5UWk?`E'S(.vrO40AGyz*Wuu vMg;R/V 5(\Yo8n|7mSXoykca޻_(1=V ~tnVuOծrfU K~'d{iϗ71ªL=krܜ,uRl’ĎY|T~ofDHJMicC a+4M²XGe!`Q0 -?~ tm ?83u`,ZDuŪe/ҟE213K-Ц?h;[r)`Iݺ>\mŭ.dVow+p՛P_bx'Mbc1So8V'8+|>3^ 5WkNG ;E]1, {pcO[\gԩԚ'Ҵ"MM11MC՜+0KMa{Bg$l"]`F{nj0vXrJNfVInZF=e@י@WKLznq' e8x+oj:ŸK(+~\S#-Oio+&!zfST7sgkӧ{Foߓ]0FSi0O8R=Hh7b[QKC)l'*P-%fPV`DCxv@ v^y-.#u-܀1g[rG엻" M X+Q WnS `$Wfn9sN>4PHzsÒG3j]_&W\bF&D]-M5&4ˁ1\*Bo#*nA/?/+He;ӐpYް~Vm^CY72Gɶu30ٗBFY&<n%2_\M|/U5ߛ۱M)l?-gaؽ2f= c(\bV*:@T5'976ݳ5}7k.m^uF~ ƯiΖW5m׵#&x *ڙm) q~gO@pWEwɲQ;n}g uC@mF+5xv>k@x(0 T- [99nb; 0V <MmX\ll,@pRg:`c D~쉟mؤ]NY8Sfy;⋶5U=x ":ὅfW+ NNy7{Lj{ɇߜzա1-lV𠥥aj-5uF J0L:aH54}/y/Ngر!rgNG6[{4.ND ,R{B6ًoZ{ŗm 3,7 i*ߐ 6狦Ji6ʼ25g%5ip=wM9 C4:TRu~{8+pg}5Q3 {YD[–b\,ͥeb1U2YЀlxe A|]~sVx[` %!s2`MlrLMf+b"3Vf ]1uc<,;@} ux=#\{4y0)F쪁q n%#[l :Eײ3Է3l(~T6g;#v?ikbXaH3Jp@c s{Ukxo[NL7$U:?k`bًgyn>|& W_s<1XE |d{3L2eUlӢs1痚z%_jERؼ_MG}^: :EBEM̧ôy/޼V |Cǀ):N2A|lY.clCW:(]sj#,\݃`t0 j&FSS s5&D]"|V[ إ/]{&'?WU[jY)ٌo BP8IbL=Y&Kݎ׷, ^yEW%KdZŤ\56vyNXdyX'xY0Fr$x\Y#5liqu]ȾVtq)pt4b2w vbbvXK_yi'(`Yym <`}NvUBzGZS+;9+&@: Ø5Awvsh9bkۓx4U[#ԯ#vV9R0_ٗPt'-˔{ߛ5c,A= kaCW(͛C?2]r8ae''$€*bZ RJg7Loĸvi ll2z7oJh8AW e l"Ffu6_zƔq`y[0%X{'oc e+K:dq*;25AT1 ; o߻!wA2Flˠ6(sk<|×-`='i:XvDJff,7o2u̠]*Q ? |lzi.bnݳ`kp"I&aZ6m:ڧr%!g?cmg4zixod9Ӻ@^\ó鷧45}9_{F=ћ ²EG/>޼eEX(bՒiS*,%7tzl&*a+)\',ZSdbnU ف-S,mKuwJe;%œt؁1UByv{4sVG0Oo{I!!81}Hk?euo}r>wFp9;ef ܒgkzmiiOw[u"g_Oq%t1}4,2;dy@4TL`t,<]%3~{gyaO {fg$W`>کfb\ξI 'Bf@zVY~{NG_WNƢ^X3# 1C_Ly TJ[퍽3C{}H2<5$̲{{?_'YEؽ&Xe)@Y =Uc<9V5HFas)}Di0r.X-K p)N+i_ϓW|rl]UNj*9#@&gv2hnqҜ"ݦsXo$9 ߻ ,r`: iF\1x(*ş> %Sr[#nW=.ꆚOx66tL/TF`R k<+$Q?AU{B a9Q;B/|gKi'Ry)L3Nw"ps^.saw33o kZ:MX}2s,.>,\]N2+Ѝl#xѩ1b t"#aMTk#.0d{ ̬?d=ŇȌ;t> S,E;TySԵ]k9%!8@!Ɯ1Qvd:MG~~ж#wQ66p,v $iJE$~7-_ʋ7RKH+(=x,ž+0wYph8GK&&'RRsłoo0Qc/͕ݬY[QVG 7#\ ܺi 5ek允!N9A,os^lZ^Z=v.Q[m.o_l=iϳڸucdP$ EХЙ;|q^@騗|dynlu0[A O < /]=札Ϗ{RWŮˮx- (Õ,E|㤭8ޤe|m)ʀ5caU$x6qyl=i/s_jpz R񑹰TQgd\R{?|^DѺVfS˼L@]L\|ӞOZB]X 9G S7K‡_yy r.,9νL@X'4r:t3"qVR;z/[ kyEJG l Ȧby'1lMjϖ7c6:f!^PTIۓ2?f fUж,ԁ_i/ejH3c&ar3*%*.5 xG2cRb>JP,\GGKE :-,y,Q{_r؋+غv(Se@j(:oxۓu`7[2Mx3{mX@b-nM5h{e{..h4ʴ/C͜~nakZd:UN C 7> F-9+hTdUO h"35oy7>{tAJ piYL d$ 'r֟h?{щB(yzu ?q@ bjɷoNkv^%ypk9d\8~3QNtLU0+3ZXvj +yhݞhMt=Tg @X:kƀLݾiQGי5; BmSbkblRT[~Ӯ{at s^Rpl&9g0.%\ZiUVMN*FڰVI)*܈vߞ+i-v2C*&fȎGV|v<{$si))9X`"KljNۓx=I?oaxAtj睕њlh й 1NbkN&Tz6}Ib,L|=U[b"2p8"z K#3: |1 &v7vrŽlF2>nL{{}Μ,L3&vWOދ~jlV*CQ['X:&۱ge.>3_Vu%֓90[/gؓ>|ثW/^jc:0S:IšBkR:bp=4YW-{~4&`(ne~)z6+;ᯏK>wLW_Njf8T;ϲf^\E X٩Y{zvfbEe7yb.>[HVG6[oR=:062ZKMM|QxWN uP1چ woS2=¬!uĖEZgNP&je oBv0ͥlHN^="ػ#oOijmOq`DݚfV{^N/tmwl3f}ň->V ,Gߜm ,5d*8-Tz(XM%~mSElUl=D0G.D1N2Fm+q&(ыJIi+Q!s\^m؟%yi)Oȩ̬X-mR*o?ZOrqq`w?d']!<ň٠X5/L71Ǹ$l86V iFK6rz7xOO+Ͽ|ƬlhT&ӡX!1 Y>>{?_=qk2&U%%lEx1 OvEb`@e8 f7!+x^3d<maRHě6Q_ǹS[9w#4ZjK*ZNjƦ77WK9x*QɑJڈ T~c칦!텸%VuY}eϝ'7<.K iVj:*S"fM<7sC2~ d߬4^Uj[E$ܽ,FTZUހQE82#%n2|ɮkj[r' ̬ˢz}ěZjT%-:heOZͪ20D,Ru?34/zܸ bMziU3EIU|`!wj%V@9"붫FLFx얊?ΦC. ^Q ,rEBBB4N.Ƚj*#dҦSևF- H*hNxhs(&̡s3q9ڇN!Ck M'CR5cKefo'CwF ߹10vcWh4ʴyi2e!)KRcBǣaFU" b|jTcPU̘]RP 2${w3Q$"ؽJb#N <35ټE %%gפ}en p0ds@Z|eo5i&}G&w\PȯyYןfR!s[a׆9 Z4RohD/|ZN~8CiGyf]$Kؿbj3{˧po'K/ա]C5 ^ ۤ\gݷr0%,:Vj.=MS:##ć]1ңvObɫR.ywͥwf?ow߇N8uxp1vՔ*m3ESw|(s1&j>YE5jTQU 1Ln^}WOշx#}{{_׷~(r[2U{$4yzuIotObΟDu۫_G?o/p.y"'-({-JC0s7ZVj_Åq⻧찌Hrj< r{v.4ˑ#N7KHOҰ2s=ڴh񓰎o$/#m a$FN1Kp8R!x|l^qys\~UO?B(ˣy:ތoFanxx EcssMWqsd[D4YdȇUqVB-! -o΋|S^ع΢g [SQ g'Hg lX>Bړ׍Cuُ{^oG8wQHjydGpvݕŤ=ݳ'Q=\~ryl!nb#gOB.K&>?x&8r~Fdz.C5h@i/vz'wrӏ{]$1tN <yc4F[j42H)X7G0749Rl# ̦-hp)䂎|ϛo7]ŏ9q7QKbem Nr ~I7G?7HH}p+FBWGmϙzsU`*X&?y{w}MOݱ)>=rFplPÔs].a'ozv)۹;2)Ƙ+J#V6hL)7-m1_|*~]µ[O]r"ǻ;!!Y%V/x7Go!7&=/cCVTh2^pڥ2@s.'7]ƇcꎘSQ/[6jat oVg | ݱoLjUލiKõh87#pː> {Mo_.#P%kIfbւ{dqMoGq$c"i83,na鰚COfGMu|ǘیc+|g|:dZX?Rxtsx p"J5_ ^)WJ{Z:Jh:W2)e|8zy1ݱOue/83N' ;БT0DorO>$ۋoǸ73K/8NاQr0)ZˡE'+^o?x=#Qe Rk"{->z3c]ݝg=W7̿Id譈UA/֮:s#9l5+6'ѽNb;hA4u(c͘o'JZ "!TjKɲN-nVVT_GzSeceUL /dw6}h(kU\g責~߽}l(VU0(QY imA.3u{kuj.}sA"~2}+->0̦QPapܐfGv|g9zi lUлݍ >;O8}MzӎW'a V e1:P K1TyI2~FnflashSG~ (~ZGykn/ .LbE$D|%F 5"DXmY?2۩@q1)*8$X F[ۃ:Ywx\ @r5l}Cc!3EE-U{2KBf6u·cL¢is@Br(3żح tѾ!:a;) &qҿ~J~ɴ4_ tu0yxe TШ\ n3gy qف+ AuZkġ͉L 8c7pEU5Oirp#a+j̫?y;G>TLWK\BX^~oXj %8:5(RבPl5듛v=4)3,=Wv >Zt]63.t2Qa QsdWvl@nufQScOHKkh yi;5K e&Bgɘ!CJjc#IY[M)l>xtbb6(C'Gۚ@x*+xՐ΂ЁXLKªDñxn{?6-A/H{Z$.C*^]oB@\i߸Te ,);cW͌!^f@%fzvXYZ\1m&9[|`4R X!묲sUz&%1#cy'd7 bΥFGn,29Az :d? Q/?cSot8"+ֺ̔Xy^Я୽}3ZAQ8* FWWH &0B!NTV AMr1t1&:!dzcq"7#[4i3wCi#HV9:`'5\p>77ofRSo4龦<ΟJ0z:7pu31etVojg7+ 6 sCFvLoo7s`*cb+" SѷF0*MK$S,CUӓUNT ~Su d~A:!_"yJmsHp&ZPWMŃYd+:0e_JdyK;?O~c =ˀ!1"@gL=.wyr:bOgDOA )=xd n,?j:Qu'Bq?ŏaͽ|n3d&;^?+vS߄?k~9|>(u,f/{XgE[E2/XZ}(Z>>GWuޟA;O}LǗ8Ä.>'O?&ull[`@ _wTHS|MF_og<7 x3|.xv9Mqd'/|C1m;yzgv}. }eLj+CDж~ ^~X/8}~⌚k2ǃ$wX|s_k9+tk@>~ׯqO/?y b!o@T]T6/nn50#_~E|=I%]!B| ݎyj`=ECp|kqQAK)@mBO&$7Bwr=1ɽO1!<h!alNlLr)wh@7Vb 4$S<st#O{!bw+ ўrDmto -1{pߏto|T*B&9}ӯAވePٷw=2Sz+3ӡ&N?q̶?;NFO?JD9y5rՑ?@S*qq@?m+}po&}\h9%z6<'q w:sp!!G؋siHAħv򵉯k{;+<_d//W} 4g_FҖV,!SMX0ǂEEK :fH:# xV22Y=5`oy͍x^Oy'tycx[rO3qDxrǼ%Lc{sA c+zgB6{i OxUvŭQlv7 On zm=cw?g;.@Ի=^) =Yo 2<_ 'BdFx b IwSZxX&‡wAL&X?n˦-ާHx뷘n|xǪZ2'B_ p,߂xCAI3/FGI3MSx)^ d|稨vJx3 %o7&7{ 17h C35Ϩo4},̩ejmJsxoM;-bRE>=Jأ7 xokcz=S0֤ˊbdEϱD[IUaUmJ1 oY/V)ͪ |Fwh-My#u̿*= Ϻ,¯ҿ4hOj[0/-"č&L3O6M{|t"SXzBk י7kOx>d )G_yԨD^^{iI M9nS7L#74vN/h-m@8==Yx%;/!>pPH#Cb%ïAdľI/>dM D?fr&BGDh?#Pw% "{{Lʃ42,'(RKk/ߖ]4 bIazf]$˯1WE*b,ï \x "(?>M{dn~[ުW~ 6G~MΉ +g m--c^ZZ|hK{s|oQW-V[=7uxymigԛhjlhšp0ʧյn NۓJ}1r65D3&\%JVQ.n4u}:c;ߺSEt.:Ƞ"}vݼ?/O087QG/]jck$|5Z}-x;:ZL36;ٸ} 0j'h/uuwϢ#λ7:8_Hݧ#r&"nմv?:hr#+3%)A`,A /a2'HL| de<ȂSd|72d2y["ߒa %H#[`!^## 2 8zVþyLӪVN2͐p8[^XZޏU41TZffIK2-an1 [ϖi(8ϕ0$A͒ X4Vsr$ + 6?aC?H!kT'-7NxH&tT?.wHo/򾧕kQdq._䍛ʏʏ坯j㋺# p2 S€b O˫aIƊd3-~~"2}Z&>2͋ZiiNji~Jc~[&*ݭ֦Ջ7+1jiPh/U 5;01V*<7rA5ڋsKX'~XK 4+in`QW iWY τ B2^c $c$cΖp@Q0* K>Lԅpckdjg"jg!-q-I-ϴ-~TOɷ2'ji*4j;iGUS4S*͔B-͝Zj-}j}QS6ipV.Z9r|5 d9S~A3ֈ$C--EFVT4إߨpH >/j^3dZ9cTP34Sw͜&.02 iLS/oxBy3x"\5Y>G_?ھt(n-M i@$oo:𪙻D&o;k{/je$)/x3V+"=𤙿,Yg["=ƿxmgjnE9&%FE8QOҧ$=v,-ޡ) tHfb,R`L}2'R+Uq;OyXq5H8Iohyyr@/).aCnJMTɞJ&MUrh:OvOJgj,ҵvH6aS{o2_ulR;>wh-Zh'j_xKڼΘɘtw*|24z34zxQKsXKD\KQAr>"mƨMo)DojmZξ < ঠLMRd} VOJدpM=JW0w9U*}%*s3I%rz-5sx)sYCjW..џwsGT? cei)|'E"ܨYK݂g-1iVeL-' ,ڸsX_7jyii5X;-<7/IU9yUy1$BXUSI ᷴf~sY4FJ‡g-Ui U[ rU[ J_L'Pspj{\say-KZ M-{Z ZTEE:SU{2-a-M)<+<4G5X[tjmq^/)x&./ks>*|kإw(X/[)Xwki=!2_QhO}^^fhiJF^m5_=-zZ)EӔ~H]t¿H_Jە=@R}+Eڞȯ֢^?)zBO-:WES}UꫢcVӢ_yZ}tkzkh K7̿Yyr+~>-Z%7%Oq_}L:g)^"Uq=`xfXw`ƹ yw`Z.E݁9%f=+P]esV'D|HϵcГn`+!2cJчZ^ f3q."_x&~~%7ϴC}M VGu?7p,hE_/bBG"yJWv}Kn1:G[DBCGFCP)GZc4nH# ]BL6gƉwxiOy#Wߍľ@%;-BSNy1-ͤvbEY"ok~?B~[CBԄ~q/Ș>O~}xkwb}Ľo~݃G3D띈Wl'#4tʍwi8~݉vf]`Aw_$c䷴:eUٳ$8[Y @ЇO%ǎ }"ΡYb0tGu\yշhI'a02(ebyz6!NJ#<#lK&M xVBd#$dcgxqvɘ1̀lH?`N3}OݪSUNsq5YKX%sO85^~/9q$J7yNv3=طFC bú=CUtGٳQ-ZB/Ȼ5SyR}WboÖ5'kn̉W_'ƩI zn1ژ57FY|@9scAƪW+Qa1{΅8yp*.16"