August 22, 2004 INSTALL 8 NetBSD

NAME

INSTALL - Installation procedure for NetBSD/mac68k.

CONTENTS

                                                              

About this Document............................................2 What is NetBSD?................................................2 Changes Between The NetBSD 3.1 release and 3.1.1 update........3 Supported devices...........................................3 Kernel......................................................3 Networking..................................................3 File system.................................................3 Security....................................................3 Miscellaneous...............................................4 alpha specific..............................................4 mac68k specific.............................................4 sparc specific..............................................4 xen specific................................................4 The Future of NetBSD...........................................5 Sources of NetBSD..............................................5 NetBSD 3.1.1 Release Contents..................................5 NetBSD/mac68k subdirectory structure........................7 Binary distribution sets....................................7 NetBSD/mac68k System Requirements and Supported Devices........9 Supported models............................................9 Supported devices...........................................9 Unsupported models.........................................10 Known hardware issues with this release....................10 Getting the NetBSD System on to Useful Media..................11 Preparing your System for NetBSD installation.................12 Installing the NetBSD System (Sysinst Method).................13 Running the sysinst installation program...................13 Introduction............................................13 Possible hardware-specific issues.......................13 General.................................................14 Quick install...........................................14 Booting NetBSD..........................................16 Network configuration...................................17 Preparing a disk for Mac OS and NetBSD..................17 Installation drive selection and parameters.............17 Partitioning the disk...................................17 Preparing your hard disk................................19 Getting the distribution sets...........................20 Installation using ftp..................................20 Installation using NFS..................................20 Installation from CD-ROM................................20 Installation from Mac OS file systems...................21 Installation from an unmounted file system..............21 Installation from a local directory.....................21 Extracting the distribution sets........................21 Finalizing your installation............................21 Installing the NetBSD System (Traditional Method).............21 Preparing the file system(s)...............................22 Installing the files.......................................22 Installation of base files.................................23 Booting the system.........................................23 Post installation steps.......................................24 Upgrading a previously-installed NetBSD System................27 Compatibility Issues With Previous NetBSD Releases............28 Issues affecting an upgrade from NetBSD 3.1 and older......28 Using online NetBSD documentation.............................28 Administrivia.................................................29 Thanks go to..................................................29 We are........................................................34 Legal Mumbo-Jumbo.............................................40 The End.......................................................46

DESCRIPTION

About this Document

This document describes the installation procedure for NetBSD3.1.1 on the mac68k 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 utility programs. This is the format in which the on-line man pages are generally presented.

.txt
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 fifty four different system architectures (ports), featuring seventeen machine architectures across fifteen distinct CPU families, and is being ported to more. The NetBSD3.1.1 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. For information on them, please see the NetBSD web site at http://www.NetBSD.org/.)

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.

Changes Between The NetBSD 3.1 release and 3.1.1 update

The NetBSD 3.1.1 update is the first security/critical update of the NetBSD 3.1 release branch. This represents a selected subset of fixes deemed critical in nature for stability or security reasons.

These fixes will also appear in future releases (NetBSD 3.2 etc), together with other less-critical fixes and feature enhancements.

Specific updates are as follows:

Supported devices
Kernel
Networking
File system
Security
Miscellaneous
alpha specific
mac68k specific
sparc specific
xen specific

NetBSD3.1.1 is the ninth major release of NetBSD for the m68k-based Macintosh.

There is still a lot of work to be done and help is welcomed. NetBSD3.1.1 on the mac68k platform is, as usual, also fully backward compatible with old NetBSD/mac68k binaries, so you don't need to recompile all of your local programs.

The Future of NetBSD

The NetBSD Foundation has been incorporated as a non-profit organization. Its purpose is to encourage, foster and promote the free exchange of computer software, namely the NetBSD Operating System. The foundation will allow for many things to be handled more smoothly than could be done with our previous informal organization. In particular, it provides the framework to deal with other parties that wish to become involved in the NetBSD Project.

The NetBSD Foundation will help improve the quality of NetBSD by:

We intend to begin narrowing the time delay between releases. Our ambition is to provide a full release every six to eight months.

We hope to support even more hardware in the future, and we have a rather large number of other ideas about what can be done to improve NetBSD.

We intend to continue our current practice of making the NetBSD-current development source available on a daily basis.

We intend to integrate free, positive changes from whatever sources submit them, providing that they are well thought-out and increase the usability of the system.

Above all, we hope to create a stable and accessible system, and to be responsive to the needs and desires of NetBSD users, because it is for and because of them that NetBSD exists.

Sources of NetBSD

Refer to http://www.NetBSD.org/mirrors/.

NetBSD 3.1.1 Release Contents

The root directory of the NetBSD3.1.1 release is organized as follows:

.../NetBSD-3.1.1/

CHANGES
Changes since earlier NetBSD releases.

LAST_MINUTE
Last minute changes.

MIRRORS
A list of sites that mirror the NetBSD3.1.1 distribution.

README.files
README describing the distribution's contents.

TODO
NetBSD's todo list (also somewhat incomplete and out of date).

patches/
Post-release source code patches.

source/
Source distribution sets; see below.

In addition to the files and directories listed above, there is one directory per architecture, for each of the architectures for which NetBSD3.1.1 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:

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.
79 MB gzipped, 367 MB uncompressed

pkgsrc
This set contains the ``pkgsrc'' sources, which contain the infrastructure to build third-party packages.
24 MB gzipped, 200 MB uncompressed

sharesrc
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.
5 MB gzipped, 20 MB uncompressed

src
This set contains all of the base NetBSD3.1.1 sources which are not in gnusrc, sharesrc, or syssrc.
37 MB gzipped, 176 MB uncompressed

syssrc
This set contains the sources to the NetBSD3.1.1 kernel for all architectures; config(8); and dbsym(8).
26 MB gzipped, 140 MB uncompressed

xsrc
This set contains the sources to the X Window System.
84 MB gzipped, 450 MB uncompressed

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:

BSDSUM
Historic BSD checksums for the various files in that directory, in the format produced by the command:
cksum -o 1 file.

CKSUM
POSIX checksums for the various files in that directory, in the format produced by the command:
cksum file.

MD5
MD5 digests for the various files in that directory, in the format produced by the command:
cksum-m file.

SYSVSUM
Historic AT&T System V UNIX checksums for the various files in that directory, in the format produced by the command:
cksum -o 2 file.

The MD5 digest is the safest checksum, followed by the POSIX checksum. The other two checksums are provided only to ensure that the widest possible range of system can check the integrity of the release files.

NetBSD/mac68k subdirectory structure
The mac68k-specific portion of the NetBSD3.1.1 release is found in the mac68k subdirectory of the distribution: .../NetBSD-3.1.1/mac68k/. 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-GENERIC.gz
A kernel containing code for everything supported in this release using the standard SCSI driver.
netbsd-GENERICSBC.gz
A kernel containing code for everything supported in this release using the SBC variant of the SCSI driver.
sets/
mac68k binary distribution sets; see below.
installation/
instkernel/
mac68k boot and installation kernels; see installation section (Sysinst Method), below.
misc/
Binary distribution sets
The NetBSD mac68k binary distribution sets contain the binaries which comprise the NetBSD3.1.1 release for the mac68k. The binary distribution sets can be found in the mac68k/binary/sets subdirectory of the NetBSD3.1.1 distribution tree, and are as follows:

base
The NetBSD3.1.1 mac68k base binary distribution. You must install this distribution set. It contains the base NetBSD utilities that are necessary for the system to run and be minimally functional. It includes shared library support, and excludes everything described below.
16 MB gzipped, 46 MB uncompressed

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.
18 MB gzipped, 69 MB uncompressed

etc
This distribution set contains the system configuration files that reside in /etc and in several other places. This set must be installed if you are installing the system from scratch, but should not be used if you are upgrading.
1 MB gzipped, 1 MB uncompressed

games
This set includes the games and their manual pages.
3 MB gzipped, 7 MB uncompressed

kern-GENERIC
This set contains a NetBSD/mac68k 3.1.1 GENERIC kernel, named /netbsd. You must install either this distribution set or kern-GENERICSBC.
2 MB gzipped, 3 MB uncompressed

kern-GENERICSBC
This set contains a NetBSD/mac68k 3.1.1 GENERICSBC kernel, named /netbsd. You must install either this distribution set or kern-GENERIC.
2 MB gzipped, 3 MB uncompressed

man
This set includes all of the manual pages for the binaries and other software contained in the base set. Note that it does not include any of the manual pages that are included in the other sets.
8 MB gzipped, 30 MB uncompressed

misc
This set includes the (rather large) system dictionaries, the typesettable document set, and other files from /usr/share.
3 MB gzipped, 9 MB uncompressed

text
This set includes NetBSD's text processing tools, including groff(1), all related programs, and their manual pages.
2 MB gzipped, 7 MB uncompressed

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, and tightly track XFree86 releases. They are currently equivalent to XFree86 4.4.0. 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.
6 MB gzipped, 17 MB uncompressed

xcomp
The extra libraries and include files needed to compile X source code.
10 MB gzipped, 37 MB uncompressed

xfont
Fonts needed by X.
31 MB gzipped, 39 MB uncompressed

xetc
Configuration files for X which could be locally modified.
0.03 MB gzipped, 0.17 MB uncompressed

xserver
The X server. This includes the Xmac68k monochrome server with man pages.
4 MB gzipped, 10 MB uncompressed

The mac68k 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 -xpf command from the root directory ( / ) of your system.

Kernels suitable for booting from an AppleShare server may be found in the mac68k/binary/kernels subdirectory of the NetBSD3.1.1 distribution tree. These kernels are generally named something like netbsd-GENERIC.gz and can be booted as-is by the NetBSD/mac68k Booter utility, if desired. Please note that these kernels are simply gzipped and are not in tar archives.

The Mac OS based utilities necessary for installing and running NetBSD can be found in the mac68k/installation/misc subdirectory of the NetBSD3.1.1 distribution tree. The important files in this directory are as follows:

Booter.sea.hqx
The NetBSD/mac68k Booter utility. This program is used to boot the NetBSD kernel from within Mac OS.
141 KB archived

Installer.sea.hqx
The NetBSD/mac68k Installer utility. This program is used to install the distribution sets onto your NetBSD partition(s). This utility is used only in a Traditional method installation; it is not used or required for an installation using the sysinst method.
147 KB archived

Mkfs.sea.hqx
The Mkfs utility. This program is used to format your chosen partitions so that they can be used with NetBSD. This utility is used only in a Traditional method installation; it is not used or required for an installation using the sysinst method.
76 KB archived

These files are all BinHexed, self-extracting archives. If you need them, the sources for these utilities are in the src subdirectory. This utility is used only in a Traditional method installation.

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

NetBSD/mac68k System Requirements and Supported Devices

NetBSD/mac68k 3.1.1 runs on several of the older Macintosh computers. About 4 MB of RAM is sufficient to boot a stripped-down custom kernel, and a subset of the system can be squeezed onto a 40 MB hard disk with considerable creativity and persistence. However, an 80 MB disk should be considered a practical minimum, and to do anything more interesting than booting at least 8 MB of RAM and more disk space is recommended. About 180 MB will be necessary to install all of the NetBSD/mac68k 3.1.1 binary system distribution sets (note that this does not count swap space!). You can drop this to 150 MB if you choose not to install the binary X11 distribution sets. Much more disk space is required to install the source and objects as well; a complete source distribution, including X11, consumes nearly 1 GB of storage.

Please note that to install NetBSD/mac68k 3.1.1 using the sysinst method, your system must have a minimum of 6 MB of RAM and 60 MB of available disk space (i.e. not part of an in-use HFS partition).

Supported models
Supported devices

If your 68030 system is not listed above, it may be because of a problem with accessing onboard video, and it may still work with a serial console. Some of the known ones in this category:

If your 68LC040 system is not listed above, it is due to a problem with floating point emulation (FPE) for this type of processor. Machines in this category include:

Unsupported models
Known hardware issues with this release

Getting the NetBSD System on to Useful Media

There are currently two installation methods available for initial installation of NetBSD on Apple Macintosh 68000-based systems. Neither supports all installation media types at this time, so the one you select must be compatible with the media you have available on your system.

The Traditional method of installation is currently supported from the local Macintosh hard drive, from a CD-ROM, or from an AppleShare volume (however, you may ugrade a system from within NetBSD; see the Upgrading a previously-installed NetBSD System section for more details). If you are installing from a local hard drive, this means that you'll need at least enough room for the largest file that you will have to install. This is the 15.2 MB base.tgz file. There has been talk of allowing an install from split files. If you have the time, desire, and knowledge, please feel free to add that functionality.

If the install is being done from an AppleShare-mounted volume, the NetBSD/mac68k Installer must be in the same folder as the binary distribution sets.

Each distribution file is in raw archive format.

You will also need to collect the Mac OS installation tools from the mac68k/installation/misc subdirectory of the NetBSD3.1.1 distribution: Mkfs, NetBSD/mac68k Installer, and NetBSD/mac68k Booter. These three are in BinHexed, self-extracting archives as Mkfs.sea.hqx, Installer.sea.hqx, and Booter.sea.hqx, respectively. Extract them as you would any other Macintosh application.

Note:
The Booter is the only Mac OS application needed if the sysinst method of installation is used. The Traditional method of installation is deprecated and will be removed in a future release, and the Mkfs and Installer tools will be retired.

Preparing your System for NetBSD installation

No matter which installation method you use, there is some planning and preparation that is required beforehand. First and foremost, before beginning the installation process, make sure you have a reliable backup of any data on your hard disk that you wish to keep. Mistakes in partitioning your hard disk may lead to data loss.

NetBSD/mac68k uses the same disk mapping scheme as Mac OS: the Apple Disk Partition Map. This permits both systems to reside on the same disk, but introduces some installation problems unique to the Macintosh. There are very few, if any, reliable ways to reduce the size of an existing Mac OS disk partition, so partitioning a disk that currently contains Mac OS will almost always require a backup and reload step under Mac OS.

If you are using the sysinst method of installation you will be able to do most, if not all, of your disk partitioning during the install process. Partitioning the disk with sysinst will destroy any partition that is resized, deleted, converted, or designated for use by NetBSD. All space not planned to be used for Mac OS HFS partitions may be used by NetBSD and can be sub-divided by the sysinst process. This space may be defined within one or more existing disk partitions of any type, including HFS partitions that are no longer needed for Mac OS. However it is best if this space is physically contiguous on the disk as sysinst is not capable of merging non-contiguous disk partitions. If you are using the sysinst method and have sufficient disk space in one or more disk partitions you should skip forward to the section labeled Installing the NetBSD System (Sysinst Method) in this document.

If you are using the Traditional method of installation you must use a disk partitioning utility to designate the different partitions you will want in your final NetBSD configuration. It is not necessary to create NetBSD (or AU/X) type partitions at this stage; the Mkfs utility can convert a partition of any type to one usable for NetBSD.

If disk partitioning is required because you've selected the Traditional method of installation, or because disk space needs to be freed up for use for the sysinst method of installation, follow the directions in the remainder of this section.

Find your favorite disk partitioning utility. Any formatter capable of partitioning a SCSI disk should work. Some of the ones that have been tried and seem to work are:

Apple's HD SC Setup is probably the easiest to use and the most commonly available. Instructions for patching HD SC Setup so that it will recognize non-Apple drives is available at:

http://www.euronet.nl/users/ernstoud/patch.html

First, you need to choose a drive on which to install NetBSD. Try to pick a drive with a low SCSI target number (or "SCSI ID"), especially if you are likely to add or remove drives to your SCSI chain in the future.

Note:
Be certain you have a reliable backup of any data that you may want to keep. Repartitioning your hard drive is an excellent way to destroy important data.

Second, decide how you want to set up your partitions. At minimum, you need a partition to hold the NetBSD installation (the root partition -- /) and a partition to serve as swap space. You may choose to use more than one partition to hold the installation. This allows you to separate the more vital portions of the file system (such as the kernel and the /etc directory) from the more volatile parts of the file system. Typical setups place the /usr directory on a separate partition from the root partition (/). Generally, / can be fairly small while the /usr partition should be fairly large. If you plan to use this machine as a server, you may also want a separate /var partition.

Once you have decided how to lay out your partitions, you need to calculate how much space to allocate to each partition. A minimal install of NetBSD (i.e. base.tgz, etc.tgz, and either kern-GENERIC.tgz or kern-GENERICSBC.tgz) should just fit in a 56 MB partition. For a full installation, you should allocate at least 180 MB (150 MB if you do not wish to install the X sets). A general rule of thumb for sizing the swap partition is to allocate twice as much swap space as you have real memory. Having your swap + real memory total at least 20 MB is also a good idea. Systems that will be heavily used or that are low on real memory should have more swap space allocated. Systems that will be only lightly used or have a very large amount of real memory can get away with less.

Keep in mind that NetBSD currently requires Mac OS in order to boot, so it is likely that you will want to keep at least a minimal install of Mac OS around on an HFS partition for this purpose. The size of this partition may vary depending on the size requirements for the version of Mac OS you are using. Of course, if you have Mac OS on another hard drive or can boot from a floppy, feel free to dedicate the entire drive to NetBSD.

Next, use your favorite partitioning utility to make partitions of the necessary sizes. You can use any type of partition, but partitions of type Apple_Free might save you some confusion in the future.

You are now set to install NetBSD on your hard drive.

Installing the NetBSD System (Sysinst Method)

Running the sysinst installation program

  1. Introduction

    Using sysinst, installing NetBSD is a relatively easy process. You still should read this document and have it in hand when doing the installation process. This document tries to be a good guideline for 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-specific issues

  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

    Prior to attempting to boot NetBSD/mac68k verify that all the following are done:

    It is probably best to boot your machine with all extensions turned off [1]. You can do this by booting into Mac OS with the SHIFT key held down. You may have to restart your Macintosh for changes to take effect before proceeding.

    [1]
    If your version of the Memory control panel does not have a 32-bit addressing mode radio button, this means that your system is already 32-bit clean and is running in 32-bit addressing mode by default. If the Booter complains that your are not in 32-bit mode, it may be necessary for you to press the "Use Defaults" button in the Memory control panel to restore 32-bit addressing. You should probably reboot after doing so. If you have an older II-class system (including the II, IIx, IIcx, and SE/30), it is necessary to install Connectix's MODE32 to work around ROM issues which prevent you from enabling 32-bit addressing. Please see the NetBSD/mac68k FAQ at http://www.NetBSD.org/Ports/mac68k/faq/ for more information.

    Double-click on the NetBSD/mac68k Booter icon to start the application. Select Booting from the Options menu. Select the Kernel Location to be from Mac OS with the filename corresponding to the name of the Installation Kernel you are using. Typically this will be netbsd-INSTALL.gz.

    If you haven't already put your Macintosh into B&W mode, select the Monitor Options from the Options menu and check the box for B&W mode.

    Try booting NetBSD by selecting Boot Now from the Options menu.

    If the system does not come up, send mail to port-mac68k@NetBSD.org describing your software, your hardware, and as complete a description of the problem as you can. As an alternative, try using the Traditional method of installation described in the next section.

    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 will not use network operation 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 in reply to answers relating to this.

  7. Preparing a disk for Mac OS and NetBSD

    sysinst can manipulate the Apple Disk Partition Map allowing you to partition your disk for use with NetBSD. It does not support resizing existing Mac OS HFS disk partitions. If there is insufficient Free space on the disk to support an installation of NetBSD you will need to backup, repartition and restore your existing Mac OS partitions before proceeding. You may choose to use a Traditional method of creating disk partitions for NetBSD if you wish. They can still be used by sysinst for a NetBSD installation.

  8. Installation drive selection and parameters

    To start the installation, select Install NetBSD to hard disk from the main menu. To start the installation, select the menu option in install NetBSD 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. Depending on how many disks are found, you may get a different message. You should see disk names like wd0, wd1, sd0 or sd1.

    sysinst next tries to figure out how the selected volume has been partitioned. It does this by reading the Apple Disk Partition Map from the disk. If the disk does not have a Partition Map, sysinst will give you the option of writing one, but doing so will not make the disk a Mac OS bootable volume. You will have the option of creating HFS partitions that may be subsequently initialized and used under Mac OS though.

  9. Partitioning the disk

    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.

  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, enter yes at the prompt.

    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.

  11. Getting the distribution sets

    The NetBSD distribution consists of a number of sets, that come in the form of gzipped tarfiles. A few sets must be installed for a working system, others are optional. At this point of the installation, 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'.

  12. Installation using ftp

    To be able to install using ftp, you first need to configure your network setup, if you haven't already at the start of the install procedure. sysinst will do this for you, asking you if you want to use DHCP, and if not to provide data like IP address, hostname, etc. If you do not have name service set up for the machine that you are installing on, you can just press RETURN in answer to these questions, 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 when answering the questions to configure networking, 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.

  13. Installation using NFS

    To be able to install using NFS, you first need to configure your network setup, if you haven't already at the start of the install procedure. sysinst will do this for you, asking you if you want to use DHCP, and if not to provide data like IP address, hostname, etc. If you do not have name service set up for the machine that you are installing on, you can just press RETURN in answer to these questions, 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 when answering the questions to configure networking, you will need to specify an IP address instead of a hostname for the NFS server.

  14. Installation from CD-ROM

    When installing from a CD-ROM, you will be asked to specify the device name for your CD-ROM player (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.

  15. Installation from Mac OS file systems

    NetBSD/mac68k does not currently have in-kernel support for Mac OS HFS/HFS+ or AppleShare filesystems. sysinst therefore can not access the file sets if they are on these filesystems.

  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

    After the install sets containing the NetBSD distribution have been made available, you can either extract all the sets (a full installation), or only extract sets that you have selected. In the latter case, you will be shown the currently selected sets, and given the opportunity to select the sets you want. Some sets always need to be installed (kern, base) and etc they will not be shown in this selection menu.

    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, especially on machines with slow graphics consoles or serial consoles.

    After all the files have been extracted, all the necessary 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 than set a password for the "root" account, to prevent the machine coming up without access restrictions.

  19. Finalizing your installation

    Congratulations, you have successfully installed NetBSD3.1.1. You can now reboot the machine, and boot NetBSD from hard disk.


Installing the NetBSD System (Traditional Method)

The Traditional method of installation can be broken down into three basic steps:

Preparing the file system(s)
Double-click on the Mkfs application icon to start it up. It will ask you for the SCSI-ID (SCSI target number) of the drive that you are installing NetBSD on. Once this is selected, it will present a list of the partitions on that disk. You must first convert the partitions to a type which NetBSD can understand. Select each partition on which you wish to build a file system and click on the Change button. If you are placing the entire installation on a single partition, select the NetBSD Root&Usr radio button. If you are using multiple partitions, select NetBSD Root for the root partition (/) and NetBSD Usr for all the other partitions. You should select NetBSD Swap for the swap partition.

When you have finished converting each partition, select each partition and click on the Format button. You will now be asked for a bunch of parameters for the hard drive and the file system. Usually, you can just take the defaults. If you are installing onto removable media (e.g. a Zip, Jaz, or Syquest), please see the FAQ. Note that although this dialog only has the OK button, you are not committed, yet. Once you get the values you want, press the OK button. A dialog will be presented at this point with two options: Format and Cancel. If you choose Cancel, nothing will be written to your drive. If you choose Format, the program will proceed to make a file system.

Mkfs is not a well-behaved Macintosh application. It will not allow any other tasks to run while it does (cooperative multitasking at its best). When it's finished, the program will put up a dialog to ask if you have scanned the output for any error messages. Usually there won't have been any errors, but do scan the output to make sure. Simply click on the I Read It button and the program will quit.

Repeat as necessary for any extra partitions that you wish to make file systems on. Note that you do not need a file system on your swap partition.

When you are finished, click on the Done button and choose Quit from the File menu to exit Mkfs.

Installing the files
Before using the Installer, it is probably a good idea to increase its memory allocation. Select the Installer icon by clicking on it and choose Get Info from the File menu. Increase both the Minimum and Preferred sizes to as much as you can spare.

Double-click on the Installer icon to start it up. The Installer will present the same SCSI-ID menu that Mkfs did. Select the same SCSI-ID (SCSI target number) that you did for Mkfs - i.e., the one you are installing NetBSD on.

If you are installing onto a single root partition (/), proceed to the Installation of base files section, below.

If you have not created file systems for / (root), usr, and any other file systems, go back to Preparing the file system(s) above.

When you started the Installer, it mounted your root partition (/). Just before it printed

       Mounting partition 'A' as /

it printed lines like:


       sd1 at scsi ID 5

This means that the device for SCSI target 5 ("SCSI ID 5") is sd1. The partitions are signified by a trailing letter. For instance, sd1a would be the root partition (/) of the second SCSI disk in the chain, and sd0g would be the first Usr partition on the first SCSI disk.

You will need to know the proper device to mount the remaining partition(s) by hand:

  1. Select Build Devices from the File menu.

  2. Select Mini Shell from the File menu.

  3. You can use the disklabel command to get a listing of the available partitions and their types and sizes.

  4. Create the directory mount point(s) with the command:


           # mkdir path

    E.g. for the /usr partition type:


           # mkdir /usr

  5. Mount the file systems you wish with the command:


           # mount device path
    For example, if you wish to mount a /usr partition from the first SCSI disk sd0, on /usr, you would type:


           # mount /dev/sd0g /usr

  6. Type
           # fstab force
    to create a proper /etc/fstab file.

  7. Type quit after you have mounted all the file systems.
Installation of base files
Select the Install menu item from the File menu and install base.tgz, etc.tgz, either kern-GENERIC.tgz or kern-GENERICSBC.tgz, and any other sets you wish to install at this time (see the NetBSD 3.1.1 Release Contents for information about what's in each set). The Installer will print out the filename of each file as it is installed, and will take quite some time to install everything (the base package alone can take over two hours on a slow hard drive).

As is the case with Mkfs, this is not a particularly well-behaved Macintosh application and the machine will be completely tied up while the installation takes place.

At some point after installing the base set, select the Build Devices option from the File menu if you have not already done so. This will create a bunch of device nodes for you and will create your initial /etc/fstab. The Installer program also has an option to give you a mini-shell. Do not use this unless you are sure know what you are doing.

When you are finished installing all of the sets you wish to install, exit the Installer by choosing Quit from the File menu.

Booting the system
Prior to attempting to boot NetBSD/mac68k, please verify that all of the following are true:

  1. 32-bit addressing is enabled [2] in the Memory control panel;

  2. All forms of virtual memory are disabled (the Memory control panel, RAM Doubler, or other software-based memory enhancement products); and

  3. Your system is in B&W mode (1-bit color or grayscale) as shown by the Monitors control panel. You may choose to have the Booter do this for you automatically by selecting the appropriate check box and radio button in the Monitors dialog on the Options menu.

It is probably best to boot your machine with all extensions turned off [2]. You can do this by booting into Mac OS with the SHIFT key held down. You may have to restart your Macintosh for changes to take effect before proceeding.

[2]
If your version of the Memory control panel does not have a 32-bit addressing mode radio button, this means that your system is already 32-bit clean and is running in 32-bit addressing mode by default. If the Booter complains that you are not in 32-bit mode, it may be necessary for you to press the Use Defaults button in the Memory control panel to restore 32-bit addressing. You should probably reboot after doing so. If you have an older II-class system (including the II, IIx, IIcx, and SE/30), it is necessary to install Connectix's MODE32 to work around ROM issues which prevent you from enabling 32-bit addressing. Please see the NetBSD/mac68k FAQ at http://www.NetBSD.org/Ports/mac68k/faq/ for more information.

Double-click on the NetBSD/mac68k Booter icon to start the application. Select Booting from the Options menu. Check that all of the items in the resulting dialog look sane - especially the SCSI target number. If not, correct them to your preference (the SCSI target number, or "SCSI ID", should be the only thing you need to change). When you are satisfied with your choices, try booting NetBSD by selecting Boot Now from the Options menu.

If you wish to save your preferences, choose Save Options from the File menu before Booting (your preferences will not be saved if you forget to do this).

If the system does not come up, send mail to port-mac68k@NetBSD.org describing your software, your hardware, and as complete a description of the problem as you can.

If the system does come up, congratulations, you have successfully installed NetBSD3.1.1.

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, with the most important ones 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).

    If your /usr directory is on a separate partition and you do not know how to use ed, you will have to mount your /usr partition to gain access to ex or vi. Do the following:


           # mount /usr
           # export TERM=vt220

    If you have /var on a separate partition, you need to repeat that step for it. After that, you can edit /etc/rc.conf with vi(1). When you have finished, type exit at the prompt to leave the single-user shell and continue with the multi-user boot.

    Other values that need to be set in /etc/rc.conf for a networked environment are hostname and possibly defaultroute, furthermore add an ifconfig_int for your <int> network interface, where your on-board, NuBus or PDS interface may be ae0, mc0 or sn0. For example:


           ifconfig_sn0="inet 123.45.67.89 netmask 255.255.255.0"

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


           ifconfig_sn0="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 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. If you're using the machine in a networked environment, 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.

    Unless you have connected an unusual terminal device as the console you can just press RETURN when it prompts for Terminal type? [...].

  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 have installed the X Window System, look at the files in /usr/X11R6/lib/X11/doc for information.

    Don't forget to add /usr/X11R6/bin to your path in your shell's dot file so that you have access to the X binaries.

  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. This automatically handles any changes necessary to make the software run on NetBSD, retrieval and installation of any other packages on which the software may depend, and simplifies installation (and deinstallation), both from source and precompiled binaries.

    - More information on the package system is at http://www.NetBSD.org/Documentation/software/packages.html

    - A list of available packages suitable for browsing is at ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/README.html

    - Precompiled binaries can be found at ftp://ftp.NetBSD.org/pub/NetBSD/packages/, usually in the 3.1.1/mac68k/All subdir. You can install them with the following commands under sh(1):

    # PKG_PATH=ftp://ftp.NetBSD.org/pub/NetBSD/packages/3.1.1/mac68k/All
    # export PKG_PATH
    # pkg_add -v tcsh
    # pkg_add -v bash
    # pkg_add -v perl
    # pkg_add -v apache
    # pkg_add -v kde
    # pkg_add -v mozilla
    ...
    

    If you are using csh(1) then replace the first two lines with the following:

    # setenv PKG_PATH ftp://ftp.NetBSD.org/pub/NetBSD/packages/3.1.1/mac68k/All
    ...
    

    The above commands will install the Tenex-csh and Bourne Again shell, the Perl programming language, Apache web server, KDE desktop environment and the Mozilla web browser as well as all the packages they depend on.

    - Package sources for compiling packages on your own can be obtained by retrieving the file ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-current/tar_files/pkgsrc.tar.gz They are typically extracted into /usr/pkgsrc (though other locations work fine), with the commands:


           # mkdir /usr/pkgsrc
           #( cd /usr/pkgsrc ; tar -zxpf - ) < pkgsrc.tar.gz

    After extracting, see the README and doc/pkgsrc.txt files in the extraction directory (e.g. /usr/pkgsrc/README) for more information.

  6. Misc

    - Edit /etc/mail/aliases to forward root mail to the right place. Don't forget to run newaliases(1) afterwards.

    - The /etc/mail/sendmail.cf file will almost definitely need to be adjusted; files aiding in this can be found in /usr/share/sendmail. See the README file there for more information. If you prefer postfix as MTA, adjust /etc/mailer.conf.

    - Edit /etc/rc.local to run any local daemons you use.

    - 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 upgrade to NetBSD3.1.1 is a binary upgrade; it can be quite difficult to update the system from an earlier version by recompiling from source, primarily due to interdependencies in the various components.

To do the upgrade, you must boot from the installer kernel using one of the methods described above. You must also have at least the base and kern binary distribution sets available, so that you can upgrade with them, using one of the upgrade methods described above. 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, the boot blocks on your NetBSD partition, 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 using the sysinst tool 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. Getting the binary sets is done in the same manner as the installation procedure; refer to the installation part of the document for how to do this. Also, some sanity checks are done, i.e. file systems are checked before unpacking the sets.

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

NetBSD/mac68k has switched its executable format from the old a.out format to ELF, the now more commonly used and supported format. Your old binaries will continue to work just fine. The installation procedure will try to take the necessary steps to accomplish this. The most important step is to move the old a.out shared libraries in /usr/lib and /usr/X11R6/lib (if X was installed) to /emul/aout, where they will be automatically found if an older a.out binary is executed. Sysinst will use an existing /emul and / or /emul/aout directory if available, and will create it (as a symbolic link to /usr/aout) if necessary.

If you already had a /emul directory, or a symbolic link by that name, sysinst should rename it and tell you about it.

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

Issues affecting an upgrade from NetBSD 3.1 and older releases.
It is very important that you populate the directory /etc/pam.d with appropriate configuration files for the Pluggable Authentication Modules (PAM) because you will not be able to login any more otherwise. Using postinstall as described below will take care of this. Please refer to http://www.netbsd.org/guide/en/chap-pam.html for documentation about PAM.

The following issues can generally be resolved by extracting the etc set into a temporary directory and running postinstall:

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

Issues fixed by postinstall:

- Various files in /etc need upgrading. These include:

The following issues need to be resolved manually:

Using online NetBSD documentation

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

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

instead.

If you are unsure of what man page you are looking for, enter

apropos subject-word

where subject-word is your topic of interest; a list of possibly related man pages will be displayed.

Administrivia

If you've got something to say, do so! We'd like your input. There are various mailing lists available via the mailing list server at 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.

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. Additionally, bug reports can be sent by mail to: netbsd-bugs@NetBSD.org.

Use of send-pr(1) is encouraged, however, because bugs reported with it are entered into the NetBSD bugs database, and thus can't slip through the cracks.

There are also port-specific mailing lists, to discuss aspects of each port of NetBSD. Use majordomo to find their addresses, 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-help@NetBSD.org.

As a favor, please avoid mailing huge documents or files to these mailing lists. Instead, put the material you would have sent up for FTP 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:
Allen Briggsbriggs@NetBSD.org
Matt Thomasmatt@NetBSD.org
Valeriy E. Ushakovuwe@NetBSD.org
YAMAMOTO Takashiyamt@NetBSD.org
Christos Zoulaschristos@NetBSD.org

The portmasters (and their ports):
Ta
Allen Briggsbriggs@NetBSD.org sandpoint
Anders Magnussonragge@NetBSD.org vax
Andrey Petrovpetrov@NetBSD.org sparc64
Ben Harrisbjh21@NetBSD.org acorn26
Chris Gilbertchris@NetBSD.org cats
Christian Limpachcl@NetBSD.org xen
Eduardo Horvatheeh@NetBSD.org evbppc
Frank van der Lindenfvdl@NetBSD.org amd64
Frank van der Lindenfvdl@NetBSD.org i386
Gavan Fantomgavan@NetBSD.org iyonix
IWAMOTO Toshihirotoshii@NetBSD.org hpcarm
Ichiro Fukuharaichiro@NetBSD.org hpcarm
Ignatios Souvatzisis@NetBSD.org amiga
Izumi Tsutsuitsutsui@NetBSD.org hp300
Izumi Tsutsuitsutsui@NetBSD.org news68k
Jason Thorpethorpej@NetBSD.org algor
Jason Thorpethorpej@NetBSD.org evbarm
Jason Thorpethorpej@NetBSD.org shark
Jeremy Cooperjeremy@NetBSD.org sun3
Jonathan Stonejonathan@NetBSD.org pmax
Julian Colemanjdc@NetBSD.org atari
Jun-ichiro itojun Haginoitojun@NetBSD.org evbsh3
Jun-ichiro itojun Haginoitojun@NetBSD.org mmeye
Kazuki Sakamotosakamoto@NetBSD.org bebox
Lennart Augustssonaugustss@NetBSD.org pmppc
Marcus Comstedtmarcus@NetBSD.org dreamcast
Martin Husemannmartin@NetBSD.org sparc64
Matt DeBergalisdeberg@NetBSD.org next68k
Matt Fredettefredette@NetBSD.org hp700
Matt Fredettefredette@NetBSD.org sun2
Matt Thomasmatt@NetBSD.org alpha
Matt Thomasmatt@NetBSD.org netwinder
Matthias Drochnerdrochner@NetBSD.org cesfic
NISHIMURA Takeshinsmrtks@NetBSD.org x68k
NONAKA Kimihirononaka@NetBSD.org prep
Nathan Williamsnathanw@NetBSD.org sun3
Noriyuki Sodasoda@NetBSD.org arc
Paul Kranenburgpk@NetBSD.org sparc
Phil Nelsonphil@NetBSD.org pc532
Reinoud Zandijkreinoud@NetBSD.org acorn32
Ross Harveyross@NetBSD.org alpha
Søren Jørvangsoren@NetBSD.org cobalt
Søren Jørvangsoren@NetBSD.org sgimips
Scott Reynoldsscottr@NetBSD.org mac68k
Shin Takemuratakemura@NetBSD.org hpcmips
Simon Burgesimonb@NetBSD.org evbmips
Simon Burgesimonb@NetBSD.org evbppc
Simon Burgesimonb@NetBSD.org pmax
Simon Burgesimonb@NetBSD.org sbmips
Steve Woodfordscw@NetBSD.org evbsh5
Steve Woodfordscw@NetBSD.org mvme68k
Steve Woodfordscw@NetBSD.org mvmeppc
Tohru Nishimuranisimura@NetBSD.org luna68k
Tsubai Masanaritsubai@NetBSD.org macppc
Tsubai Masanaritsubai@NetBSD.org newsmips
UCHIYAMA Yasushiuch@NetBSD.org hpcsh
UCHIYAMA Yasushiuch@NetBSD.org playstation2
Wayne Knowleswdk@NetBSD.org mipsco
Wolfgang Solfrankws@NetBSD.org ofppc

The NetBSD 3.1.1 Release Engineering team:
Grant Beattiegrant@NetBSD.org
Erik Berlscyber@NetBSD.org
James Chaconjmc@NetBSD.org
Julian Colemanjdc@NetBSD.org
Håvard Eidneshe@NetBSD.org
Jun-ichiro itojun Haginoitojun@NetBSD.org
Geert Hendrickxghen@NetBSD.org
Soren Jacobsensnj@NetBSD.org
SAITOH Masanobumsaitoh@NetBSD.org
Luke Mewburnlukem@NetBSD.org
Jeff Rizzoriz@NetBSD.org
Matthias Schelertron@NetBSD.org
Curt Sampsoncjs@NetBSD.org
Jim Wisejwise@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
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
D'Arcy J.M. Caindarcy@NetBSD.org
Dave Carrelcarrel@NetBSD.org
Daniel Carosonedan@NetBSD.org
James Chaconjmc@NetBSD.org
Bill Coldwellbillc@NetBSD.org
Julian Colemanjdc@NetBSD.org
Ben Collverben@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
Rob Dekerdeker@NetBSD.org
Chris G. Demetrioucgd@NetBSD.org
Tracy Di Marco Whitegendalia@NetBSD.org
Jaromír Dolecekjdolecek@NetBSD.org
Andy Doranad@NetBSD.org
Roland Dowdeswellelric@NetBSD.org
Emmanuel Dreyfusmanu@NetBSD.org
Matthias Drochnerdrochner@NetBSD.org
Jun Ebiharajun@NetBSD.org
Elad Efratelad@NetBSD.org
Håvard Eidneshe@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
Hubert Feyrerhubertf@NetBSD.org
Jason R. Finkjrf@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
Adam Glassglass@NetBSD.org
Michael Graffexplorer@NetBSD.org
Brian C. Graysonbgrayson@NetBSD.org
Matthew Greenmrg@NetBSD.org
Andreas Gustafssongson@NetBSD.org
Jun-ichiro itojun Haginoitojun@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
HAMAJIMA Katsuomihamajima@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
Jachym Holecekfreza@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 Hörnquist Åstrandlha@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
Chris Jonescjones@NetBSD.org
Søren Jørvangsoren@NetBSD.org
Takahiro Kambetaca@NetBSD.org
Antti Kanteepooka@NetBSD.org
Masanori Kanaokakanaoka@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
Paul Kranenburgpk@NetBSD.org
Martti Kuparinenmartti@NetBSD.org
Kentaro A. Kurahonekurahone@NetBSD.org
Kevin Laheykml@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
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
Anders Magnussonragge@NetBSD.org
MAEKAWA Masahidegehenna@NetBSD.org
David Maxwelldavid@NetBSD.org
Dan McMahilldmcmahill@NetBSD.org
Gregory McGarrygmcgarry@NetBSD.org
Jared D. McNeilljmcneill@NetBSD.org
Neil J. McRaeneil@NetBSD.org
Perry Metzgerperry@NetBSD.org
Simas Mockeviciussymka@NetBSD.org
Juan Romero Pardinesxtraeme@NetBSD.org
Julio M. Merino Vidaljmmv@NetBSD.org
Minoura Makotominoura@NetBSD.org
Luke Mewburnlukem@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
Jesse Offjoff@NetBSD.org
Tatoku Ogaitotacha@NetBSD.org
OKANO Takayoshikano@NetBSD.org
Masaru Okioki@NetBSD.org
Atsushi Onoeonoe@NetBSD.org
Greg Osteroster@NetBSD.org
Jonathan Perkinsketch@NetBSD.org
Herb Peyerlhpeyerl@NetBSD.org
Matthias Pfallermatthias@NetBSD.org
Chris Pinnockcjep@NetBSD.org
Adrian Portelliadrianp@NetBSD.org
Rui Paulorpaulo@NetBSD.org
Peter Postmapeter@NetBSD.org
Dante Profetadante@NetBSD.org
Chris Provenzanoproven@NetBSD.org
Niels Provosprovos@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
Gordon Rossgwr@NetBSD.org
Steve Rumblerumble@NetBSD.org
Ilpo Ruotsalainenlonewolf@NetBSD.org
Heiko W. Rupphwr@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
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
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
Jörg Sonnenbergerjoerg@NetBSD.org
Ignatios Souvatzisis@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
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
Nathan Williamsnathanw@NetBSD.org
Rob Windsorwindsor@NetBSD.org
Dan Winshipdanw@NetBSD.org
Jim Wisejwise@NetBSD.org
Michael Wolfsonmbw@NetBSD.org
Steve Woodfordscw@NetBSD.org
Colin Woodender@NetBSD.org
YAMAMOTO Takashiyamt@NetBSD.org
Yuji Yamanoyyamano@NetBSD.org
Reinoud Zandijkreinoud@NetBSD.org
S.P.Zeidlerspz@NetBSD.org
Maria Zevenhovenmaria7@NetBSD.org
Christos Zoulaschristos@NetBSD.org

Other contributors:
Dave Burgessburgess@cynjut.infonet.net
Brian R. Gaekebrg@dgate.org
Brad Granthamgrantham@tenon.com
Lawrence Kestelootkesteloo@cs.unc.edu
Waldi Ravenswaldi@moacs.indiv.nl.net

Legal Mumbo-Jumbo

All product names mentioned herein are trademarks or registered trademarks of their respective owners.

The following notices are required to satisfy the license terms of the software that we have mentioned in this document:

This product includes software developed by the University of California, Berkeley and its contributors.

This product includes software developed by the NetBSD Foundation.
This product includes software developed by The NetBSD Foundation, Inc. and its contributors.
This product includes software developed for the NetBSD Project. See http://www.netbsd.org/ for information about NetBSD.
This product contains software developed by Ignatios Souvatzis for the NetBSD project.
This product contains software written by Ignatios Souvatzis and Michael L. Hitch for the NetBSD project.
This product contains software written by Michael L. Hitch for the NetBSD project.
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 Berkeley Software Design, Inc.
This product includes software developed by David Jones and Gordon Ross
This product includes software developed by Gordon W. Ross and Leo Weppelman.
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 Kortelainen
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 Advanced Risc Machines Ltd.
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 Alistair G. Crooks.
This product includes software developed by Alistair G. Crooks. for the NetBSD project.
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 Software Design, Inc.
This product includes software developed by Berkeley Software 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 Brad Pepers
This product includes software developed by Bradley A. Grantham.
This product includes software developed by Brini.
This product includes software developed by Causality Limited.
This product includes software developed by Charles D. Cranor and Seth Widoff.
This product includes software developed by Charles D. Cranor and Washington University.
This product includes software developed by Charles D. Cranor, Washington University, and the University of California, Berkeley and its contributors.
This product includes software developed by Charles D. Cranor, Washington University, the University of California, Berkeley and its contributors.
This product includes software developed by Charles D. Cranor.
This product includes software developed by Charles Hannum.
This product includes software developed by Charles M. Hannum, by the University of Vermont and State Agricultural College and Garrett A. Wollman, by William F. Jolitz, and by the University of California, Berkeley, Lawrence Berkeley Laboratory, and its contributors.
This product includes software developed by Charles M. Hannum.
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 Christian Limpach
This product includes software developed by Christopher G. Demetriou for the NetBSD Project.
This product includes software developed by Christopher G. Demetriou.
This product includes software developed by Christos Zoulas.
This product includes software developed by 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 Cybernet Corporation and Nan Yang Computer Services Limited
This product includes software developed by Daishi Kato
This product includes software developed by Dale Rahn.
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 Darrin B. Jewell
This product includes software developed by David Miller.
This product includes software developed by Dean Huxley.
This product includes software developed by Eduardo Horvath.
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@@mincom.oz.au)
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 Gary Thomas.
This product includes software developed by Gordon Ross
This product includes software developed by Gordon W. Ross
This product includes software developed by HAYAKAWA Koichi.
This product includes software developed by Harvard University and its contributors.
This product includes software developed by Harvard University.
This product includes software developed by Herb Peyerl.
This product includes software developed by Hubert Feyrer for the NetBSD Project.
This product includes software developed by Iain Hibbert
This product includes software developed by Ian F. Darwin and others.
This product includes software developed by Ian W. Dall.
This product includes software developed by Ichiro FUKUHARA.
This product includes software developed by Ignatios Souvatzis for the NetBSD Project.
This product includes software developed by Internet Initiative 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. Wittkoski.
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 Jukka Marin.
This product includes software developed by Julian Highfield.
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 LAN Media Corporation and its contributors.
This product includes software developed by Leo Weppelman for the NetBSD Project.
This product includes software developed by Leo Weppelman.
This product includes software developed by Lloyd Parkes.
This product includes software developed by Luke Mewburn.
This product includes software developed by Lutz Vieweg.
This product includes software developed by MINOURA Makoto, Takuya Harakawa.
This product includes software developed by Manuel Bouyer.
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 Murray
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 Martin Husemann and Wolfgang Solfrank.
This product includes software developed by Masanobu Saitoh.
This product includes software developed by Masaru Oki.
This product includes software developed by Mats O Jansson and Charles D. Cranor.
This product includes software developed by Mats O Jansson.
This product includes software developed by Matt DeBergalis
This product includes software developed by Matthew Fredette.
This product includes software developed by Matthias Pfaller.
This product includes software developed by Michael Graff for the NetBSD Project.
This product includes software developed by Michael Graff.
This product includes software developed by Michael L. Hitch.
This product includes software developed by Michael Shalayeff.
This product includes software developed by Michael Smith.
This product includes software developed by Mike Glover and contributors.
This product includes software developed by Mike Pritchard.
This product includes software developed by Minoura Makoto.
This product includes software developed by Nan Yang Computer Services Limited.
This product includes software developed by Niels Provos.
This product includes software developed by Niklas Hallqvist, Brandon Creighton and Job de Haas.
This product includes software developed by Niklas Hallqvist.
This product includes software developed by Onno van der Linden.
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. Nelson.
This product includes software developed by Philip L. Budne.
This product includes software developed by RiscBSD.
This product includes software developed by Roar Thronæs.
This product includes software developed by Rodney W. Grimes.
This product includes software developed by Roger Hardiman
This product includes software developed by Roland C. Dowdeswell.
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 contributors.
This product includes software developed by Soren S. Jorvang.
This product includes software developed by Stephan Thesing.
This product includes software developed by Steve Woodford.
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 Terrence R. Lambert.
This product includes software developed by Tetsuya Isaki.
This product includes software developed by Thomas Gerner
This product includes software developed by Thomas Klausner for the NetBSD Project.
This product includes software developed by Tobias Weingartner.
This product includes software developed by Todd C. Miller.
This product includes software developed by Tohru Nishimura and Reinoud Zandijk for the NetBSD Project.
This product includes software developed by Tohru Nishimura for the NetBSD Project.
This product includes software developed by Tohru Nishimura. for the NetBSD Project.
This product includes software developed by TooLs GmbH.
This product includes software developed by Toru Nishimura.
This product includes software developed by Trimble Navigation, 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 Wasabi Systems for Zembu Labs, Inc. http://www.zembu.com/
This product includes software developed by Winning Strategies, Inc.
This product includes software developed by Wolfgang Solfrank.
This product includes software developed by Yasushi Yamasaki
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 Center for Software Science at the University of Utah.
This product includes software developed by the Charles D. Cranor, Washington University, University of California, Berkeley and its contributors.
This product includes software developed by the Computer Systems Engineering Group at Lawrence Berkeley Laboratory.
This product includes software developed by the David Muir Sharnoff.
This product includes software developed by the Harvard University and its contributors.
This product includes software developed by the Kungliga Tekniska Högskolan 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/)
his product includes software developed by the PocketBSD project and its contributors.
This product includes software developed by the RiscBSD kernel team
This product includes software developed by the RiscBSD team.
This product includes software developed by the SMCC Technology 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 contributors.
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 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 Christos Zoulas
This product includes software developed for the NetBSD Project by Emmanuel Dreyfus.
This product includes software developed for the NetBSD Project by Frank van der Linden
This product includes software developed for the NetBSD Project by Ignatios Souvatzis.
This product includes software developed for the NetBSD Project by Jason R. Thorpe.
This product includes software developed for the NetBSD Project by John M. Vinopal.
This product includes software developed for the NetBSD Project by Matthias Drochner.
This product includes software developed for the NetBSD Project by Michael L. Hitch.
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 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 is a component of "386BSD" developed by William F. Jolitz, TeleMuse.
This software was developed by Holger Veit and Brian Moore for use with "386BSD" and similar operating systems. "Similar 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 Services at Carnegie Mellon University (http://www.cmu.edu/computing/).

This product includes software developed by the Alice Group.
This product includes software developed by Allen Briggs.
This product includes software developed by Bradley A. Grantham.
This product includes softwarre developed by Daishi Kato.
This product includes software developed by Takashi Hamada.
This product includes software developed by Scott Reynolds.
This product includes software developed by John P. Wittkoski.
This product includes software developed by Colin Wood.

The End

Contributions

The following people have made contributions of various sorts specifically for the Macintosh port (in alphabetical order):