August 17, 2012 INSTALL 8 NetBSD

NAME

INSTALL - Installation procedure for NetBSD/evbarm.

CONTENTS

                                                              

About this Document............................................2 What is NetBSD?................................................3 Changes Between The NetBSD 6.0 and 6.0.1 Releases..............3 Security Fixes..............................................3 General kernel..............................................3 Networking..................................................3 File systems................................................3 Drivers.....................................................3 Platforms...................................................4 Userland changes............................................4 The NetBSD Foundation..........................................4 Sources of NetBSD..............................................4 NetBSD 6.0.1 Release Contents..................................4 NetBSD/evbarm subdirectory structure........................5 Binary distribution sets....................................6 NetBSD/evbarm System Requirements and Supported Devices........7 Supported devices (Technologic Systems TS-7200).............7 TS-5620 Real Time Clock..................................7 Serial ports.............................................7 Ethernet adapters........................................7 Other on-board functions.................................7 Supported devices (ARM, Ltd. Integrator)....................8 PrimeCell PL030 Real Time Clock..........................8 Serial ports.............................................8 SCSI host adapters.......................................8 Ethernet adapters........................................8 Supported devices (Intel IQ80310)...........................8 Serial ports.............................................8 Ethernet adapters........................................8 i80312 Companion I/O functions...........................8 Supported devices (Intel IQ80321)...........................8 Serial ports.............................................8 Ethernet adapters........................................8 i80321 I/O Processor functions...........................8 Supported devices (Team ASA Npwr)...........................8 Serial ports.............................................8 SCSI host adapters.......................................8 Ethernet adapters........................................9 Supported devices (Intel IXM1200)...........................9 Serial ports.............................................9 Ethernet adapters........................................9 Supported devices (Samsung SMDK2800)........................9 Serial ports.............................................9 Supported devices (ADI BRH).................................9 Serial ports.............................................9 Ethernet adapters........................................9 Supported devices (Arcom Viper).............................9 Serial ports.............................................9 Ethernet adapters........................................9 Getting the NetBSD System on to Useful Media...................9 Preparing your System for NetBSD installation.................11 Preparation for the Technologic Systems TS-7200............11 Preparation for the Intel IQ80310..........................12 Preparation for the Intel IQ80321..........................13 Installing the NetBSD System..................................15 Installation for the Technologic Systems TS-7200...........15 Installation for the Intel IQ80310.........................16 Installation for the Intel IQ80321.........................17 Post installation steps.......................................18 Upgrading a previously-installed NetBSD System................21 Compatibility Issues With Previous NetBSD Releases............21 Issues affecting an upgrade from NetBSD 5.x releases.......21 Issues affecting an upgrade from NetBSD 4.x releases.......22 Using online NetBSD documentation.............................22 Administrivia.................................................23 Thanks go to..................................................24 We are........................................................24 Legal Mumbo-Jumbo.............................................30 The End.......................................................35

DESCRIPTION

About this Document

This document describes the installation procedure for NetBSD 6.0.1 on the evbarm 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 57 different system architectures (ports) across 15 distinct CPU families, and is being ported to more. The NetBSD 6.0.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. 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.

Changes Between The NetBSD 6.0 and 6.0.1 Releases

The complete list of changes can be found in the CHANGES-6.0.1: http://ftp.NetBSD.org/pub/NetBSD/NetBSD-6.0.1/CHANGES-6.0.1 file in the top level directory of the NetBSD 6.0.1 release tree. An abbreviated list is as follows:

Security Fixes
General kernel
Networking
File systems
Drivers
Platforms
Userland changes

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 6.0.1 Release Contents

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

.../NetBSD-6.0.1/

CHANGES
Changes between the 5.0 and 6.0 releases.

CHANGES-6.0
Changes between the initial 6.0 branch and final release of 6.0.

CHANGES-6.0.1
Changes between the 6.0 and 6.0.1 releases.

CHANGES.prev
Changes in previous NetBSD releases.

LAST_MINUTE
Last minute changes and notes about the release.

README.files
README describing the distribution's contents.

source/
Source distribution sets; see below.

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

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.

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

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

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

SHA512
SHA512 digests in the format produced by the command:
cksum -a SHA512 file.

The SHA512 digest is safer, but MD5 checksums are provided so that a wider range of operating systems can check the integrity of the release files.

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

base
The NetBSD 6.0.1 evbarm 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.

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.

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.

games
This set includes the games and their manual pages.

kern-INTEGRATOR
(see below)

kern-IQ80310
(see below)

kern-IQ80321
(see below)

kern-TEAMASA_NPWR

These sets contain a NetBSD/evbarm 6.0.1 kernel, named /netbsd. Some of these sets also contain a binary format kernel named /netbsd.bin and an S-record format kernel named /netbsd.srec that your firmware may need to boot. You must install the kernel that matches your hardware.

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.

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

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

NetBSD maintains its own set of sources for the X Window System in order to assure tight integration and compatibility. These sources are based on X.Org. Binary sets for the X Window System are distributed with NetBSD. The sets are:

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

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

xfont
Fonts needed by the X server and by X clients.

xetc
Configuration files for X which could be locally modified.

xserver
The X server.

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

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

NetBSD/evbarm System Requirements and Supported Devices

NetBSD6.0.1 runs on the following ARM architecture evaluation boards:

Supported devices (Technologic Systems TS-7200)
For devices that have machine-independent drivers, this is not an exhaustive list, but merely reflects the devices that have been tested on this platform.
Supported devices (ARM, Ltd. Integrator)
For devices that have machine-independent drivers, this is not an exhaustive list, but merely reflects the devices that have been tested on this platform.
Supported devices (Intel IQ80310)
For devices that have machine-independent drivers, this is not an exhaustive list, but merely reflects the devices that have been tested on this platform.
Supported devices (Intel IQ80321)
For devices that have machine-independent drivers, this is not an exhaustive list, but merely reflects the devices that have been tested on this platform.
Supported devices (Team ASA Npwr)
The Npwr is a storage appliance based on the Intel IOP310 I/O processor chipset. This is an exhaustive list of devices supported on the Npwr as the Npwr has no expansion capability.
Supported devices (Intel IXM1200)
For devices that have machine-independent drivers, this is not an exhaustive list, but merely reflects the devices that have been tested on this platform.
Supported devices (Samsung SMDK2800)
For devices that have machine-independent drivers, this is not an exhaustive list, but merely reflects the devices that have been tested on this platform.
Supported devices (ADI BRH)
For devices that have machine-independent drivers, this is not an exhaustive list, but merely reflects the devices that have been tested on this platform.
Supported devices (Arcom Viper)
Current this is an exhaustive list, since expansion ports such as PC/104 and USB are not yet supported.

Getting the NetBSD System on to Useful Media

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.

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

Proceed to the instructions on installation.

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

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

Tape
To install NetBSD from a tape, you need to make a tape that contains the distribution set files, in `tar' format.

If you're making the tape on a UNIX-like system, the easiest way to do so is probably something like:

       # tar -cf tape_device dist_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-6.0.1
       # cd evbarm/binary
       # tar -cf tape_device kern-GENERIC base etc

Note:
You still need to fill in tape_device in the example.

Once you have the files on the tape, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading.


Preparing your System for NetBSD installation

First and foremost, before beginning the installation process, make sure you have a reliable backup of any data on the target system that you wish to keep. Mistakes in partitioning may lead to data loss.

Preparation for the Technologic Systems TS-7200
The TS-7200 uses RedBoot firmware which supports loading the kernel via serial port and the on-chip Ethernet. These notes assume that the Ethernet will be used to load the kernel. RedBoot can either use TFTP or HTTP to load the kernel via the network.

These notes also assume the the TS-7200 will be run from the CompactFlash; that a FFS filesystem on the CompactFlash card will provide the root file system. The minimum size of the CompactFlash card is 64MB with 512MB being the recommended minimum size if attempting a full installation.

The first step to install NetBSD is to interrupt normal system bootup and drop to the RedBoot prompt by hitting Ctrl-C immediately after applying power. To load both the installation kernel and the generic post-installation TS7200 kernel you will need network connectivity from RedBoot which you will have to configure using the RedBoot fconfig command; see the RedBoot documentation for more information.

A compressed kernel image and loader suitable for placing into flash is provided with the distribution. Use of this image is optional; a kernel that can be directly loaded over the network by RedBoot is also provided.

The image for the TS-7200 can be found under the NetBSD/evbarm 6.0.1 distribution directory in evbarm/binary/gzimg/gzimg_TS7200_flash_0x60660000.gz, and corresponds to the kernel in evbarm/binary/kernel/netbsd-TS7200.gz. The following steps describe how to copy the compressed kernel image into flash.

  1. Uncompress the gzimg file and place it into the TFTP server's download area (note, the kernel inside the gzimg is still compressed after this step).

           server# gzcat gzimg_TS7200_flash_0x60660000.gz > /tftpboot/gzimg_TS7200_flash_0x60660000

  2. Load the gzimg from the TFTP server.

    RedBoot> load -r -b 0x00200000 gzimg_TS7200_flash_0x60660000
    Raw file loaded 0x00200000-0x00605fe0
    

  3. Use the RedBoot fis command to copy the image into flash. For more information on the RedBoot Flash Image System, see the RedBoot documentation. The factory default Linux image may already be present in flash and must be deleted before continuing.
    RedBoot> fis delete vmlinux
    RedBoot> fis create -b 0x00200000 -f 0x60660000 -l 0x00160000 netbsd.gz
    

Once the compressed kernel image has been copied into flash, it may be started by jumping to the flash address of the image:

RedBoot> g 0x60660000
Preparation for the Intel IQ80310
The IQ80310 uses RedBoot firmware from Red Hat, Inc. RedBoot supports loading the kernel via the serial port and the on-board Ethernet. These notes assume that the Ethernet will be used to load the kernel. RedBoot uses the Trivial File Transfer Protocol (TFTP) to load the kernel via the network.

These notes also assume that the IQ80310 will be run as a diskless system; that an NFS server will provide the root file system. The NetBSD kernel uses the Dynamic Host Configuration Protocol (DHCP) to obtain network address and root file system information.

The first step is to configure your DHCP, NFS, and TFTP server software. You will need the MAC address for the on-board Ethernet, which RedBoot can provide; see the RedBoot documentation for more information.

The next step is to configure RedBoot to obtain its IP address from your DHCP server; see the RedBoot documentation for more information.

Once your DHCP server and RedBoot are properly configured, you should see information similar to the following when the IQ80310 is reset or powered-up:

RedBoot(tm) debug environment - built 17:16:14, Feb 12 2001
Platform: IQ80310 (XScale)
Copyright (C) 2000, Red Hat, Inc.
                                                                                     

RAM: 0xa0000000-0xa2000000 FLASH: 0x00000000 - 0x00800000, 64 blocks of 0x00020000 bytes each. IP: 192.168.0.10, Default server: 192.168.0.1 RedBoot>

A compressed kernel image and loader suitable for placing into flash is provided with the distribution. Use of this image is optional; a kernel that can be directly loaded over the network by RedBoot is also provided.

The image for the IQ80310 can be found under the NetBSD/evbarm 6.0.1 distribution directory in evbarm/binary/gzimg/gzimg_IQ80310_flash_0x00080000.gz, and corresponds to the kernel in evbarm/binary/kernel/netbsd-IQ80310.gz. The following steps describe how to copy the compressed kernel image into flash.

  1. Uncompress the gzimg file and place it into the TFTP server's download area (note, the kernel inside the gzimg is still compressed after this step).


           server# gzcat gzimg_IQ80310_flash_0x00080000.gz > /tftpboot/gzimg_IQ80310_flash_0x00080000

  2. Load the gzimg from the TFTP server.

    RedBoot> load -r -b 0xa0200000 gzimg_IQ80310_flash_0x00080000
    Raw file loaded 0xa0200000-0xa0305fe0
    

  3. Use the RedBoot fis command to copy the image into flash. For more information on the RedBoot Flash Image System, see the RedBoot documentation.
    RedBoot> fis create -b 0xa0200000 -f 0x00080000 -l 0x00200000 netbsd.gz
    ... Erase from 0x00080000-0x00280000: ....................
    ... Program from 0xa0200000-0xa0400000 at 0x00080000: ....................
    ... Unlock from 0x007e0000-0x00800000:.
    ... Erase from 0x007e0000-0x00800000:.
    ... Program from 0xa1fd0000-0xa1ff0000 at 0x007e0000:.
    ... Lock from 0x007e0000-0x00800000:.
    

Once the compressed kernel image has been copied into flash, it may be started by jumping to the flash address of the image:

RedBoot> g 0x00080000
                                                                                     

>> NetBSD/IQ80310 Gzip Boot, Revision 1.1 >> (root@tgm, Thu Mar 28 18:32:45 PST 2002) >> RAM 0xa0000000 - 0xafffffff, heap at 0xaffd0000 >> Load address: 0xa0200000 >> Image size: 741244 Uncompressing image...done. Jumping to image @ 0xa0200000...

NetBSD/evbarm (IQ80310) booting ... Resetting secondary PCI bus... initarm: Configuring system ... physmemory: 65536 pages at 0xa0000000 -> 0xafffffff init subsystems: stacks vectors undefined pmap irq done. [ using 155084 bytes of netbsd ELF symbol table ] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved.

NetBSD 1.5ZC (IQ80310) #20: Fri Mar 29 10:25:53 PST 2002 root@tgm:/u1/netbsd/src/sys/arch/evbarm/compile/IQ80310 total memory = 256 MB avail memory = 232 MB using 1228 buffers containing 13208 KB of memory mainbus0 (root) cpu0 at mainbus0: i80200 step A-0 (XScale core) cpu0: DC enabled IC enabled WB enabled LABT cpu0: 32KB/32B 32-way Instruction cache cpu0: 32KB/32B 32-way write-back-locking Data cache obio0 at mainbus0: board rev. F, CPLD rev. D, backplane present com0 at obio0 addr 0xfe810000: ns16550a, working fifo com0: console com1 at obio0 addr 0xfe800000: ns16550a, working fifo iopxs0 at mainbus0: i80312 Companion I/O, acting as PCI host iopxs0: configuring Secondary PCI bus pci0 at iopxs0 bus 1 pci0: i/o space, memory space enabled ppb0 at pci0 dev 7 function 0: Digital Equipment DECchip 21154 PCI-PCI Bridge (rev. 0x05) pci1 at ppb0 bus 2 pci1: i/o space, memory space enabled fxp0 at pci1 dev 0 function 0: i82559S Ethernet, rev 9 fxp0: interrupting at iq80310 irq 1 fxp0: Ethernet address 00:80:4d:46:0b:b9 inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 4 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto clock: hz=100 stathz=0 profhz=0 boot device: <unknown> root device:

Preparation for the Intel IQ80321
The IQ80321 uses RedBoot firmware from Red Hat, Inc. RedBoot supports loading the kernel via the serial port and the on-board Ethernet. These notes assume that the Ethernet will be used to load the kernel. RedBoot uses the Trivial File Transfer Protocol (TFTP) to load the kernel via the network.

These notes also assume that the IQ80321 will be run as a diskless system; that an NFS server will provide the root file system. The NetBSD kernel uses the Dynamic Host Configuration Protocol (DHCP) to obtain network address and root file system information.

The first step is to configure your DHCP, NFS, and TFTP server software. You will need the MAC address for the on-board Ethernet, which RedBoot can provide; see the RedBoot documentation for more information.

The next step is to configure RedBoot to obtain its IP address from your DHCP server; see the RedBoot documentation for more information.

Once your DHCP server and RedBoot are properly configured, you should see information similar to the following when the IQ80321 is reset or powered-up:

Ethernet eth0: MAC address 00:07:e9:03:38:40
IP: 192.168.0.11, Default server: 192.168.0.1
                                                                                     

RedBoot(tm) bootstrap and debug environment [ROM] Non-certified release, version UNKNOWN - built 11:21:56, Feb 1 2002

Platform: IQ80321 (XScale) Copyright (C) 2000, 2001, 2002, Red Hat, Inc.

RAM: 0x00000000-0x08000000, 0x00017008-0x01ddd000 available FLASH: 0xf0000000 - 0xf0800000, 64 blocks of 0x00020000 bytes each. RedBoot>

A compressed kernel image and loader suitable for placing into flash is provided with the distribution. Use of this image is optional; a kernel that can be directly loaded over the network by RedBoot is also provided.

The image for the IQ80321 can be found under the NetBSD/evbarm 6.0.1 distribution directory in evbarm/binary/gzimg/gzimg_IQ80321_flash_0xf0080000.gz, and corresponds to the kernel in evbarm/binary/kernel/netbsd-IQ80321.gz. The following steps describe how to copy the compressed kernel image into flash.

  1. Uncompress the gzimg file and place it into the TFTP server's download area (note, the kernel inside the gzimg is still compressed after this step).


           server# gzcat gzimg_IQ80321_flash_0xf0080000.gz > /tftpboot/gzimg_IQ80321_flash_0xf0080000

  2. Load the gzimg from the TFTP server.

    RedBoot> load -r -b 0x00200000 gzimg_IQ80321_flash_0xf0080000
    Raw file loaded 0x00200000-0x00305fe4
    

  3. Use the RedBoot fis command to copy the image into flash. For more information on the RedBoot Flash Image System, see the RedBoot documentation.
    RedBoot> fis create -b 0x00200000 -f 0xf0080000 -l 0x00200000 netbsd.gz
    * CAUTION * about to program 'netbsd.gz'
                at 0xf0080000..0xf027ffff from 0x00200000 - are you sure (y/n)? y
    ... Erase from 0xf0080000-0xf0280000: .......................
    ... Program from 0x00200000-0x00400000 at 0xf0080000: ......................
    ... Unlock from 0xf07e0000-0xf0800000:.
    ... Erase from 0xf07e0000-0xf0800000:.
    ... Program from 0x01ddf000-0x01dff000 at 0xf07e0000:.
    ... Lock from 0xf07e0000-0xf0800000:.
    

Once the compressed kernel image has been copied into flash, it may be started by jumping to the flash address of the image:

RedBoot> g 0xf0080000
                                                                                     

>> NetBSD/IQ80321 Gzip Boot, Revision 1.1 >> (root@tgm, Thu Mar 28 18:32:45 PST 2002) >> RAM 0xa0000000 - 0xa7ffffff, heap at 0xa7fd0000 >> Load address: 0xa0200000 >> Image size: 739495 Uncompressing image...done. Jumping to image @ 0xa0200000...

NetBSD/evbarm (IQ80321) booting ... initarm: Configuring system ... physmemory: 32768 pages at 0xa0000000 -> 0xa7ffffff init subsystems: stacks vectors undefined pmap irq done. [ using 155076 bytes of netbsd ELF symbol table ] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved.

NetBSD 1.5ZC (IQ80321) #1: Thu Mar 28 18:31:58 PST 2002 root@tgm:/u1/netbsd/src/sys/arch/evbarm/compile/IQ80321 total memory = 128 MB avail memory = 113 MB using 1228 buffers containing 6656 KB of memory mainbus0 (root) cpu0 at mainbus0: i80321 step A-0 (XScale core) cpu0: DC enabled IC enabled WB enabled LABT cpu0: 32KB/32B 32-way Instruction cache cpu0: 32KB/32B 32-way write-back-locking Data cache obio0 at mainbus0 com0 at obio0 addr 0xfe800000: ns16550a, working fifo com0: console iopxs0 at mainbus0: i80321 I/O Processor, acting as PCI host iopxs0: configuring PCI bus pci0 at iopxs0 bus 0 pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok wm0 at pci0 dev 4 function 0: Intel i82544 1000BASE-T Ethernet, rev. 2 wm0: interrupting at iop321 irq 27 wm0: Ethernet address 00:07:e9:03:38:40 makphy0 at wm0 phy 1: Marvell 88E1000 Gigabit PHY, rev. 0 makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto clock: hz=100 stathz=0 profhz=0 boot device: <unknown> root device:


Installing the NetBSD System

Installation for the Technologic Systems TS-7200
The following steps describe how to set up a CompactFlash card for the TS-7200. The TS-7200 can use the interactive installation program sysinst to perform an internet installation from ftp.netbsd.org on the CompactFlash.

  1. Place the netbsd-TS7200_INSTALL.bin kernel into the TFTP server's download area. It must be decompressed from the gzipped image in the release directory evbarm/installation/instkernel/netbsd-TS7200_INSTALL.srec.gz

           server# gunzip netbsd-TS7200_INSTALL.srec.gz
           server# cp netbsd-TS7200_INSTALL.srec /tftpboot/netbsd-TS7200_INSTALL

  2. Load the kernel from the TFTP server.

    RedBoot> load netbsd-TS7200_INSTALL
    

  3. Start the kernel running.

    RedBoot> go
    

    The kernel will display boot messages, probe for devices, and invoke the interactive sysinst installation tool. Once sysinst has completed installation, the system will reboot back into RedBoot. If the preparation instructions above have been followed, the post-installation NetBSD kernel will be in the FIS ready to be jumped into. You can have RedBoot automatically start NetBSD by putting the command go 0x60660000 into the RedBoot bootscript using the fconfig command.

Installation for the Intel IQ80310
The following steps describe how to set up an NFS root environment for the IQ80310 and how to boot the IQ80310.

  1. Place the kernel into the TFTP server's download area.

    RedBoot only loads S-Records, so select a kernel with the ``.srec'' filename suffix. In this example, we will boot the kernel hard-wired to use the on-board Ethernet as the root device.


           server# cp netbsd-fxp0.srec /tftpboot/netbsd-iq80310-fxp0

  2. Unpack the distribution sets into the target's root directory.


           server# cd /export/client/iq80310
           server# gzcat .../base.tgz | tar xvpf -
           server# gzcat .../etc.tgz | tar xvpf -
           [repeat for all sets you wish to unpack]

  3. Load the kernel from the TFTP server.

    RedBoot> load netbsd-iq80310-fxp0
    Entry point: 0xa0200000, address range: 0xa0200000-0xa035e07c
    RedBoot>
    

  4. Start the kernel running. The kernel will display boot message, probe for devices, and mount the root file system. If you used a kernel hard-wired to use the on-board Ethernet, it will attempt to mount the root file system automatically. Otherwise, it will prompt for the root device to use.

    Since the system's run-time environment has not yet been configured, the system should boot into single-user mode.

    RedBoot> go
                                                                                         

    NetBSD/evbarm (IQ80310) booting ... Resetting secondary PCI bus... initarm: Configuring system ... physmemory: 65536 pages at 0xa0000000 -> 0xafffffff init subsystems: stacks vectors undefined pmap irq done. [ using 155084 bytes of netbsd ELF symbol table ] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved.

    NetBSD 1.5ZC (IQ80310) #20: Fri Mar 29 10:25:53 PST 2002 root@tgm:/u1/netbsd/src/sys/arch/evbarm/compile/IQ80310 total memory = 256 MB avail memory = 232 MB using 1228 buffers containing 13208 KB of memory mainbus0 (root) cpu0 at mainbus0: i80200 step A-0 (XScale core) cpu0: DC enabled IC enabled WB enabled LABT cpu0: 32KB/32B 32-way Instruction cache cpu0: 32KB/32B 32-way write-back-locking Data cache obio0 at mainbus0: board rev. F, CPLD rev. D, backplane present com0 at obio0 addr 0xfe810000: ns16550a, working fifo com0: console com1 at obio0 addr 0xfe800000: ns16550a, working fifo iopxs0 at mainbus0: i80312 Companion I/O, acting as PCI host iopxs0: configuring Secondary PCI bus pci0 at iopxs0 bus 1 pci0: i/o space, memory space enabled ppb0 at pci0 dev 7 function 0: Digital Equipment DECchip 21154 PCI-PCI Bridge (rev. 0x05) pci1 at ppb0 bus 2 pci1: i/o space, memory space enabled fxp0 at pci1 dev 0 function 0: i82559S Ethernet, rev 9 fxp0: interrupting at iq80310 irq 1 fxp0: Ethernet address 00:80:4d:46:0b:b9 inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 4 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto clock: hz=100 stathz=0 profhz=0 boot device: <unknown> root on fxp0 nfs_boot: trying DHCP/BOOTP nfs_boot: DHCP next-server: 192.168.0.1 nfs_boot: my_name=iq80310.lab.wasabisystems.com nfs_boot: my_domain=wasabisystems.com nfs_boot: my_addr=192.168.0.10 nfs_boot: my_mask=255.255.255.0 nfs_boot: gateway=192.168.0.254 root on 192.168.0.1:/export/client/iq80310 /etc/rc.conf is not configured. Multiuser boot aborted. Enter pathname of shell or RETURN for sh:

Installation for the Intel IQ80321
The following steps describe how to set up an NFS root environment for the IQ80321 and how to boot the IQ80321.

  1. Place the kernel into the TFTP server's download area.

    RedBoot only loads S-Records, so select a kernel with the ``.srec'' filename suffix. In this example, we will boot the kernel hard-wired to use the on-board Ethernet as the root device.


           server# cp netbsd-wm0.srec /tftpboot/netbsd-iq80321-wm0

  2. Unpack the distribution sets into the target's root directory.


           server# cd /export/client/iq80321
           server# gzcat .../base.tgz | tar xvpf -
           server# gzcat .../etc.tgz | tar xvpf -
           [repeat for all sets you wish to unpack]

  3. Load the kernel from the TFTP server.

    RedBoot> load netbsd-iq80321-wm0
    Entry point: 0x00200000, address range: 0x00200000-0x00396a40
    RedBoot>
    

  4. Start the kernel running. The kernel will display boot message, probe for devices, and mount the root file system. If you used a kernel hard-wired to use the on-board Ethernet, it will attempt to mount the root file system automatically. Otherwise, it will prompt for the root device to use.

    Since the system's run-time environment has not yet been configured, the system should boot into single-user mode.

    RedBoot> go
                                                                                         

    NetBSD/evbarm (IQ80321) booting ... initarm: Configuring system ... physmemory: 32768 pages at 0xa0000000 -> 0xa7ffffff init subsystems: stacks vectors undefined pmap irq done. [ using 156468 bytes of netbsd ELF symbol table ] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved.

    NetBSD 1.5ZC (IQ80321) #1: Thu Mar 28 18:20:34 PST 2002 root@tgm:/u1/netbsd/src/sys/arch/evbarm/compile/IQ80321 total memory = 128 MB avail memory = 113 MB using 1228 buffers containing 6656 KB of memory mainbus0 (root) cpu0 at mainbus0: i80321 step A-0 (XScale core) cpu0: DC enabled IC enabled WB enabled LABT cpu0: 32KB/32B 32-way Instruction cache cpu0: 32KB/32B 32-way write-back-locking Data cache obio0 at mainbus0 com0 at obio0 addr 0xfe800000: ns16550a, working fifo com0: console iopxs0 at mainbus0: i80321 I/O Processor, acting as PCI host iopxs0: configuring PCI bus pci0 at iopxs0 bus 0 pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok wm0 at pci0 dev 4 function 0: Intel i82544 1000BASE-T Ethernet, rev. 2 wm0: interrupting at iop321 irq 27 wm0: Ethernet address 00:07:e9:03:38:40 makphy0 at wm0 phy 1: Marvell 88E1000 Gigabit PHY, rev. 0 makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto clock: hz=100 stathz=0 profhz=0 boot device: <unknown> root on wm0 nfs_boot: trying DHCP/BOOTP nfs_boot: DHCP next-server: 192.168.0.1 nfs_boot: my_name=iq80321.lab.wasabisystems.com nfs_boot: my_domain=wasabisystems.com nfs_boot: my_addr=192.168.0.11 nfs_boot: my_mask=255.255.255.0 nfs_boot: gateway=192.168.0.254 root on 192.168.0.1:/export/client/iq80321 /etc/rc.conf is not configured. Multiuser boot aborted. Enter pathname of shell or RETURN for sh:


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_fxp0="inet 192.0.2.123 netmask 255.255.255.0"

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


           ifconfig_fxp0="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. 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 6.0.1 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 6.0.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.

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

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 5.x releases

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.0 kernel defaults to 0 for kern.no_sa_support, which covers the first case. However, please note that a full installation of 5.0 (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).

The implementation of SHA2-HMAC in KAME_IPSEC as used in NetBSD-5 and before did not comply to current standards. FAST_IPSEC does, with the result that old and new systems cannot communicate over IPSEC, if one of the affected authentication algorithms (hmac_sha256, hmac_sha384, hmac_sha512) is used.

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

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. 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):
Reinoud Zandijkreinoud acorn32
Matt Thomasmatt alpha
Ignatios Souvatzisis amiga
Ignatios Souvatzisis amigappc
Noriyuki Sodasoda arc
Julian Colemanjdc atari
Matthias Drochnerdrochner cesfic
Erik Berlscyber cobalt
Antti Kanteepooka emips
Simon Burgesimonb evbmips
Steve Woodfordscw evbppc
Izumi Tsutsuitsutsui ews4800mips
Izumi Tsutsuitsutsui hp300
Nick Hudsonskrll hp700
Valeriy E. Ushakovuwe hpcsh
Matt Thomasmatt ibmnws
Gavan Fantomgavan iyonix
Valeriy E. Ushakovuwe landisk
Izumi Tsutsuitsutsui luna68k
Scott Reynoldsscottr mac68k
Michael Lorenzmacallan macppc
Steve Woodfordscw mvme68k
Steve Woodfordscw mvmeppc
Matt Thomasmatt netwinder
Izumi Tsutsuitsutsui news68k
Tim Rightnourgarbled ofppc
Simon Burgesimonb pmax
Tim Rightnourgarbled prep
Tim Rightnourgarbled rs6000
Tohru Nishimuranisimura sandpoint
Simon Burgesimonb sbmips
Søren Jørvangsoren sgimips
SAITOH Masanobumsaitoh sh3
Martin Husemannmartin sparc64
Anders Magnussonragge vax
NISHIMURA Takeshinsmrtks x68k
Manuel Bouyerbouyer xen

The NetBSD 6.0.1 Release Engineering team:
Stephen Borrillsborrill@NetBSD.org
Manuel Bouyerbouyer@NetBSD.org
David Brownleeabs@NetBSD.org
James Chaconjmc@NetBSD.org
Julian Colemanjdc@NetBSD.org
Alistair G. Crooksagc@NetBSD.org
Håvard Eidneshe@NetBSD.org
John Heasleyheas@NetBSD.org
Martin Husemannmartin@NetBSD.org
Soren Jacobsensnj@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
Zafer Aydoganzafer@NetBSD.org
Christoph Badurabad@NetBSD.org
Marc Balmermbalmer@NetBSD.org
Bang Jun-Youngjunyoung@NetBSD.org
Dieter Barondillo@NetBSD.org
Robert V. Baronrvb@NetBSD.org
Alan Barrettapb@NetBSD.org
Grant Beattiegrant@NetBSD.org
Erik Berlscyber@NetBSD.org
Hiroyuki Besshobsh@NetBSD.org
John Birrelljb@NetBSD.org
Rafal Bonirafal@NetBSD.org
Stephen Borrillsborrill@NetBSD.org
Sean Boudreauseanb@NetBSD.org
Manuel Bouyerbouyer@NetBSD.org
Allen Briggsbriggs@NetBSD.org
Mark Brinicombemark@NetBSD.org
Aaron Brownabrown@NetBSD.org
Andrew Brownatatat@NetBSD.org
David Brownleeabs@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
Taylor R. Campbellriastradh@NetBSD.org
Daniel Carosonedan@NetBSD.org
Dave Carrelcarrel@NetBSD.org
James Chaconjmc@NetBSD.org
Mihai Chelarukefren@NetBSD.org
Aleksey Cheusovcheusov@NetBSD.org
Bill Coldwellbillc@NetBSD.org
Julian Colemanjdc@NetBSD.org
Marcus Comstedtmarcus@NetBSD.org
Jeremy Cooperjeremy@NetBSD.org
Thomas Corttcort@NetBSD.org
Chuck Cranorchuck@NetBSD.org
Alistair Crooksagc@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
Jaromír Dolecekjdolecek@NetBSD.org
Andy Doranad@NetBSD.org
Roland Dowdeswellelric@NetBSD.org
Steven Drakesbd@NetBSD.org
Emmanuel Dreyfusmanu@NetBSD.org
Matthias Drochnerdrochner@NetBSD.org
Jun Ebiharajun@NetBSD.org
Håvard 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
Makoto Fujiwaramef@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
Oliver V. Gouldver@NetBSD.org
Paul Goyettepgoyette@NetBSD.org
Michael Graffexplorer@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
Yorick Hardyyhardy@NetBSD.org
Ben Harrisbjh21@NetBSD.org
Eric Haszlakiewiczerh@NetBSD.org
John Hawkinsonjhawk@NetBSD.org
Emile Heitorimil@NetBSD.org
John Heasleyheas@NetBSD.org
Lars Heidiekerpara@NetBSD.org
Geert Hendrickxghen@NetBSD.org
René Hexelrh@NetBSD.org
Iain Hibbertplunky@NetBSD.org
Kouichirou Hiratsukahira@NetBSD.org
Michael L. Hitchmhitch@NetBSD.org
Ádám Hókaahoka@NetBSD.org
Jachym Holecekfreza@NetBSD.org
David A. Hollanddholland@NetBSD.org
Christian E. Hoppschopps@NetBSD.org
Daniel Horeckimorr@NetBSD.org
Ken Hornsteinkenh@NetBSD.org
Marc Horowitzmarc@NetBSD.org
Eduardo Horvatheeh@NetBSD.org
Nick Hudsonskrll@NetBSD.org
Shell Hungshell@NetBSD.org
Darran Huntdarran@NetBSD.org
Martin Husemannmartin@NetBSD.org
Dean Huxleydean@NetBSD.org
Love Hörnquist Å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
Søren Jørvangsoren@NetBSD.org
Takahiro Kambetaca@NetBSD.org
Antti Kanteepooka@NetBSD.org
Frank Kardelkardel@NetBSD.org
KAWAMOTO Yosihisakawamoto@NetBSD.org
Min Sik Kimminskim@NetBSD.org
KIYOHARA Takashikiyohara@NetBSD.org
Thomas Klausnerwiz@NetBSD.org
Klaus Kleinkleink@NetBSD.org
John Klosjklos@NetBSD.org
Wayne Knowleswdk@NetBSD.org
Takayoshi Kochikochi@NetBSD.org
Jonathan A. Kollaschjakllsch@NetBSD.org
Radoslaw Kujawarkujawa@NetBSD.org
Jochen Kunzjkunz@NetBSD.org
Martti Kuparinenmartti@NetBSD.org
Arnaud Lacombealc@NetBSD.org
Kevin Laheykml@NetBSD.org
David Laightdsl@NetBSD.org
Johnny C. Lamjlam@NetBSD.org
Guillaume Lasmayousgls@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
MAEKAWA Masahidegehenna@NetBSD.org
Anders Magnussonragge@NetBSD.org
John Marinomarino@NetBSD.org
Roy Marplesroy@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
Constantine A. Murenincnst@NetBSD.org
Joseph Myersjsm@NetBSD.org
Tuomo Mäkinentjam@NetBSD.org
Zoltán Arnold NAGYzoltan@NetBSD.org
Ken Nakatakenn@NetBSD.org
Takeshi Nakayamanakayama@NetBSD.org
Alexander Nasonovalnsn@NetBSD.org
Phil Nelsonphil@NetBSD.org
John Nemethjnemeth@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
Ryo ONODERAryoon@NetBSD.org
Atsushi Onoeonoe@NetBSD.org
Greg Osteroster@NetBSD.org
Jonathan Perkinsketch@NetBSD.org
Fredrik Pettaipettai@NetBSD.org
Herb Peyerlhpeyerl@NetBSD.org
Matthias Pfallermatthias@NetBSD.org
Chris Pinnockcjep@NetBSD.org
Adrian Portelliadrianp@NetBSD.org
Chris Provenzanoproven@NetBSD.org
Mindaugas Rasiukeviciusrmind@NetBSD.org
Michael Rauchmrauch@NetBSD.org
Marc Rechtrecht@NetBSD.org
Darren Reeddarrenr@NetBSD.org
Jeremy C. Reedreed@NetBSD.org
Jens Rehsacksno@NetBSD.org
Antoine Reillestonio@NetBSD.org
Tyler R. Retzlaffrtr@NetBSD.org
Scott Reynoldsscottr@NetBSD.org
Tim Rightnourgarbled@NetBSD.org
Jeff Rizzoriz@NetBSD.org
Hans Rosenfeldhans@NetBSD.org
Steve Rumblerumble@NetBSD.org
Rumkorumko@NetBSD.org
Jukka Ruohonenjruoho@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
Naoto Shimazakiigy@NetBSD.org
Ryo Shimizuryo@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
Jörg Sonnenbergerjoerg@NetBSD.org
Ignatios Souvatzisis@NetBSD.org
T K Spindlerdogcow@NetBSD.org
Matthew Sporledermspo@NetBSD.org
Bill Squiergroo@NetBSD.org
Adrian Steinmannast@NetBSD.org
Bill Studenmundwrstuden@NetBSD.org
Kevin Sullivansullivan@NetBSD.org
Kimmo Suominenkim@NetBSD.org
Grégoire Sutregsutre@NetBSD.org
Sergey Svishchevshattered@NetBSD.org
Robert Swindellsrjs@NetBSD.org
Shin Takemuratakemura@NetBSD.org
TAMURA Kentkent@NetBSD.org
Shin'ichiro TAYAtaya@NetBSD.org
Hasso Tepperhasso@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
Mark Weinemweinem@NetBSD.org
Lex Wennmacherwennmach@NetBSD.org
Leo Weppelmanleo@NetBSD.org
Assar Westerlundassar@NetBSD.org
Frank Willephx@NetBSD.org
Nathan Williamsnathanw@NetBSD.org
Rob Windsorwindsor@NetBSD.org
Jim Wisejwise@NetBSD.org
Colin Woodender@NetBSD.org
Steve Woodfordscw@NetBSD.org
YAMAMOTO Takashiyamt@NetBSD.org
Yuji Yamanoyyamano@NetBSD.org
David Youngdyoung@NetBSD.org
Arnaud Ysmalstacktic@NetBSD.org
Reinoud Zandijkreinoud@NetBSD.org
S.P.Zeidlerspz@NetBSD.org
Tim Zingelmantez@NetBSD.org
Christos Zoulaschristos@NetBSD.org

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:

NetBSD is a registered trademark of The NetBSD Foundation, Inc.

This product includes software developed by the University of California, Berkeley and its contributors.
This product includes software developed by the NetBSD 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 includes software developed by Intel Corporation and its contributors.
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)
This product includes cryptographic software written by Eric Young (eay@mincom.oz.au)
This product includes software designed by William Allen Simpson.
This product includes software developed at Ludd, University of Lulea, Sweden and its contributors.
This product includes software developed at Ludd, University of Lulea.
This product includes software developed at the Information Technology Division, US Naval Research Laboratory.
This product includes software developed by David Jones and Gordon Ross
This product includes software developed by Hellmuth Michaelis and Joerg Wunsch
This product includes software developed by Internet Research Institute, Inc.
This product includes software developed by Leo Weppelman and Waldi Ravens.
This product includes software developed by Mika 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 Amancio Hasty and Roger Hardiman
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 Brini.
This product includes software developed by Bruce M. Simpson.
This product includes software developed by Causality Limited.
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 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 Daan Vreeken.
This product includes software developed by Daishi Kato
This product includes software developed by Daniel Widenfalk and Michael L. Hitch.
This product includes software developed by Daniel Widenfalk for the NetBSD Project.
This product includes software developed by Dean Huxley.
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 K. Kobayashi.
This product includes software developed by K. Kobayashi and H. Shimokawa.
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 Florian Stoehr.
This product includes software developed by Frank van der Linden for the NetBSD Project.
This product includes software developed by Gardner Buchanan.
This product includes software developed by Garrett D'Amore.
This product includes software developed by Gary Thomas.
This product includes software developed by Gordon Ross
This product includes software developed by Harvard University and its contributors.
This product includes software developed by Harvard University.
This product includes software developed by Henrik Vestergaard Draboel.
This product includes software developed by Herb Peyerl.
This product includes software developed by Hidetoshi Shimokawa.
This product includes software developed by Ian W. Dall.
This product includes software developed by Ignatios Souvatzis for the NetBSD Project.
This product includes software developed by Internet Initiative Japan Inc.
This product includes software developed by James R. Maynard III.
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 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 Lloyd Parkes.
This product includes software developed by Lutz Vieweg.
This product includes software developed by MINOURA Makoto, Takuya Harakawa.
This product includes software developed by Marc Horowitz.
This product includes software developed by Marcus Comstedt.
This product includes software developed by Mark Brinicombe for the NetBSD project.
This product includes software developed by Mark Brinicombe.
This product includes software developed by Mark Tinguely and Jim Lowe
This product includes software developed by Markus Wild.
This product includes software developed by Masanobu Saitoh.
This product includes software developed by Masaru Oki.
This product includes software developed by Matthew Fredette.
This product includes software developed by Michael Smith.
This product includes software developed by Mike Pritchard.
This product includes software developed by Mike Pritchard and contributors.
This product includes software developed by Minoura Makoto.
This product includes software developed by Niels Provos.
This product includes software developed by Niklas Hallqvist, Brandon Creighton and Job de Haas.
This product includes software developed by Niklas Hallqvist.
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 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 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 Stephan Thesing.
This product includes software developed by Steven M. Bellovin.
This product includes software developed by Takashi Hamada.
This product includes software developed by Takumi Nakamura.
This product includes software developed by Tatoku Ogaito for the NetBSD Project.
This product includes software developed by Terrence R. Lambert.
This product includes software developed by TooLs GmbH.
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 Yen Yen Lim and North Dakota State University.
This product includes software developed by Zembu Labs, Inc.
This product includes software developed by the Alice Group.
This product includes software developed by the 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 Network Research Group at Lawrence Berkeley Laboratory.
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.OpenSSL.org/)
This product includes software developed by the PocketBSD project and its contributors.
This product includes software developed by the RiscBSD 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 Urbana-Champaign Independent Media Center.
This product includes software developed by the University of Vermont and State Agricultural College and Garrett A. Wollman.
This product includes software developed by the University of Vermont and State Agricultural College and Garrett A. Wollman, by William F. Jolitz, and by the University of California, Berkeley, Lawrence Berkeley Laboratory, and its contributors.
This product includes software developed for the FreeBSD project
This product includes software developed for the NetBSD Project by Bernd Ernesti.
This product includes software developed for the NetBSD Project by Christopher G. Demetriou.
This product includes software developed for the NetBSD Project by 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 by Kyma Systems.
This product includes software developed for the NetBSD Project by Kyma Systems LLC.
This product includes software developed for the NetBSD Project by Matthias Drochner.
This product includes software developed for the NetBSD Project by Perry E. Metzger.
This product includes software developed for the NetBSD Project by Scott Bartram and Frank van der Linden
This product includes software developed for the NetBSD Project by Allegro Networks, Inc., and Wasabi Systems, Inc.
This product includes software developed for the NetBSD Project by 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 Marshall M. Midden.
This product includes software developed or owned by Caldera International, Inc.
The Institute of Electrical and Electronics Engineers and The Open Group, have given us permission to reprint portions of their documentation.

In the following statement, the phrase ``this text'' refers to portions of the system documentation.

Portions of this text are reprinted and reproduced in electronic form in NetBSD, from IEEE Std 1003.1, 2004 Edition, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2004 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between these versions and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document.

The original Standard can be obtained online at http://www.opengroup.org/unix/online.html.

This notice shall appear on any product containing this material

This product includes software developed by Advanced Risc Machines Ltd.
This product includes software developed by Microsoft.
This product includes software developed by the RiscBSD kernel team.
This product includes software developed by Scott Stevens.

The End