September 7, 2002 INSTALL 8 NetBSD

NAME

INSTALL - Installation procedure for NetBSD/sun2.

CONTENTS

                                                              

About this Document............................................1 What is NetBSD?................................................2 Upgrade path to NetBSD 1.6.....................................2 Changes Between The NetBSD 1.5 and 1.6 Releases................2 Kernel......................................................2 Networking..................................................3 File system.................................................4 Security....................................................4 System administration and user tools........................4 Miscellaneous...............................................5 sun2 specific...............................................6 The Future of NetBSD...........................................6 Sources of NetBSD..............................................6 NetBSD 1.6 Release Contents....................................6 NetBSD/sun2 subdirectory structure..........................8 Binary distribution sets....................................9 NetBSD/sun2 System Requirements and Supported Devices.........10 Supported hardware.........................................10 Getting the NetBSD System on to Useful Media..................11 Creating boot/install tapes................................11 Boot/Install from NFS server...............................11 Install/Upgrade from CD-ROM................................12 Install/Upgrade via FTP....................................12 Preparing your System for NetBSD installation.................12 Installing the NetBSD System..................................13 Installing from tape.......................................13 Installing from NFS........................................13 Installing from SunOS......................................14 Booting the Miniroot.......................................15 Miniroot install program...................................15 Post installation steps.......................................16 Upgrading a previously-installed NetBSD System................18 Compatibility Issues With Previous NetBSD Releases............19 Issues affecting an upgrade from NetBSD 1.5................19 Issues affecting an upgrade from NetBSD 1.4 or prior.......20 Using online NetBSD documentation.............................21 Administrivia.................................................22 Thanks go to..................................................22 We are........................................................24 Legal Mumbo-Jumbo.............................................29 The End.......................................................31

DESCRIPTION

About this Document

This document describes the installation procedure for NetBSD1.6 on the sun2 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 three different system architectures (ports), featuring seventeen machine architectures across eleven distinct CPU families, and is being ported to more. The NetBSD1.6 release contains complete binary releases for thirty eight different system architectures. (The fifteen remaining 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.

Upgrade path to NetBSD 1.6

If you are not installing your system ``from scratch'' but instead are going to upgrade an existing system already running NetBSD you need to know which versions you can upgrade with NetBSD1.6.

NetBSD1.6 is an upgrade of NetBSD1.5.3 and earlier major and patch releases of NetBSD.

The intermediate development versions of code available on the main trunk in our CVS repository (also known as ``NetBSD-current'') from after the point where the release cycle for 1.6 was started are designated by version identifiers such as 1.6A, 1.6B, etc. These identifiers do not designate releases, but indicate major changes in internal kernel APIs. Note that the kernel from NetBSD 1.6 can not be used to upgrade a system running one of those intermediate development versions. Trying to use the NetBSD 1.6 kernel on such a system will probably result in problems.

Please also note that it is not possible to do a direct ``version'' comparison between any of the intermediate development versions mentioned above and 1.6 to determine if a given feature is present or absent in 1.6. The development of 1.6 and the subsequent ``point'' releases is done on a separate branch in the CVS repository. The branch was created when the release cycle for 1.6 was started, and during the release cycle of 1.6 and its patch releases selected fixes and enhancements have been imported from the main development trunk.

Changes Between The NetBSD 1.5 and 1.6 Releases

The NetBSD1.6 release provides numerous significant functional enhancements, including support for many new devices, integration of hundreds of bug fixes, new and updated kernel subsystems, and many user-land enhancements. The result of these improvements is a stable operating system fit for production use that rivals most commercially available systems.

It is impossible to completely summarize over eighteen months of development that went into the NetBSD1.6 release. Some highlights include:

Kernel
Networking
File system
Security
System administration and user tools
Miscellaneous

Kernel interfaces have continued to be refined, and more subsystems and device drivers are shared among the different ports. You can look for this trend to continue.

sun2 specific

This is the first major release of NetBSD/sun2.

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/Sites/net.html.

NetBSD 1.6 Release Contents

The root directory of the NetBSD1.6 release is organized as follows:

.../NetBSD-1.6/

CHANGES
Changes since earlier NetBSD releases.

LAST_MINUTE
Last minute changes.

MIRRORS
A list of sites that mirror the NetBSD1.6 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 NetBSD1.6 has a binary distribution. There are also README.export-control files sprinkled liberally throughout the distribution tree, which point out that there are some portions of the distribution that may be subject to export regulations of the United States, e.g. code under src/crypto and src/sys/crypto. It is your responsibility to determine whether or not it is legal for you to export these portions and to act accordingly.

The source distribution sets can be found in subdirectories of the source subdirectory of the distribution tree. They contain the complete sources to the system. The source distribution sets are as follows:

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.
55 MB gzipped, 247 MB uncompressed

pkgsrc
This set contains the ``pkgsrc'' sources, which contain the infrastructure to build third-party packages.
12 MB gzipped, 94 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.
4 MB gzipped, 16 MB uncompressed

src
This set contains all of the base NetBSD1.6 sources which are not in gnusrc, sharesrc, or syssrc.
27 MB gzipped, 136 MB uncompressed

syssrc
This set contains the sources to the NetBSD1.6 kernel for all architectures; config(8); and dbsym(8).
22 MB gzipped, 114 MB uncompressed

xsrc
This set contains the sources to the X Window System.
78 MB gzipped, 394 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

The sets/Split/ subdirectory contains split versions of the source sets for those users who need to load the source sets from floppy or otherwise need a split distribution. The split sets are named set_name.xx where set_name is the distribution set name, and xx is the sequence number of the file, starting with ``aa'' for the first file in the distribution set, then ``ab'' for the next, and so on. All of these files except the last one of each set should be exactly 240,640 bytes long. (The last file is just long enough to contain the remainder of the data for that distribution set.)

The split distributions may be reassembled and extracted with cat as follows:


       # cat set_name.?? | ( cd / ; tar -zxpf - )

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/sun2 subdirectory structure
The sun2-specific portion of the NetBSD1.6 release is found in the sun2 subdirectory of the distribution: .../NetBSD-1.6/sun2/
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/
sun2 binary distribution sets; see below.
installation/
miniroot/
sun2 miniroot file system image; see below.
misc/
Miscellaneous sun2 installation utilities; see installation section, below.
netboot/
Two programs needed to boot sun2 kernels over the network.
tapeimage/
Tape boot program, and two shell scripts used to prepare tapes.
Binary distribution sets
The NetBSD sun2 binary distribution sets contain the binaries which comprise the NetBSD1.6 release for the sun2. There are eight binary distribution sets. The binary distribution sets can be found in the sun2/binary/sets subdirectory of the NetBSD1.6 distribution tree, and are as follows:

base
The NetBSD1.6 sun2 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.
53 MB gzipped, 118 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.
13 MB gzipped, 46 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.
6 MB gzipped, 13 MB uncompressed

kern-GENERIC
This set contains a NetBSD/sun2 1.6 GENERIC kernel, named /netbsd. You must install this distribution set.
1 MB gzipped, 2 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.
7 MB gzipped, 27 MB uncompressed

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

text
This set includes NetBSD's text processing tools, including groff(1), all related programs, and their manual pages.
3 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. NetBSD/sun2 currently does not ship with an X server or X clients.

The sun2 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. This utility is used only in a Traditional method installation.

There is a collection of Sun2 kernels in the sun2/binary/kernel subdirectory of the NetBSD1.6 distribution. The one named netbsd.RAMDISK.gz contain a root file system image and should only be used for the initial installation. The others are included for convenience. (Most people will want to use netbsd-GENERIC.gz or netbsd-FOURMEG.gz as appropriate.) Please note that these kernels are simply gzipped and are not tar archives.

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

NetBSD/sun2 System Requirements and Supported Devices

NetBSD/sun2 1.6 runs on Multibus Sun2 machines, including:

2/120 2/170 2/100U

The minimal configuration requires 4 MB of RAM and about 130 MB of disk space. To install the entire system requires much more disk space (approx. 100 MB additional space is necessary for full sources). To compile the system, more RAM is recommended. Good performance requires 7 MB of RAM.

Here is a table of recommended HD partition sizes for a full install:

Partition Suggested Needed
/ (root) 20 MB 15 MB
/usr 210 MB 110 MB
/var 20 MB 5 MB
swap 2*RAM ...

Anything else is up to you!

As you may note, the recommended size of /usr is 100 MB greater than needed. This is to leave room for a kernel source and compile tree as you will probably want to compile your own kernel. (GENERIC is large and bulky to accommodate all people).

Note that the sun2 installation procedure uses a miniroot image which is placed into the swap area of the disk. The swap partition must be at least as large as the miniroot image (12 MB).

Supported hardware

If it's not on this list, there is no support for it in this release.

Getting the NetBSD System on to Useful Media

Installation is supported from several media types, including:

Note:
Installing on a `bare' machine requires some bootable device; either a tape drive or Sun-compatible NFS server.

The procedure for transferring the distribution sets onto installation media depends on the type of media. Instructions for each type of media are given below.

In order to create installation media, you will need all the files in the directory

       .../NetBSD-1.6/sun2/

Creating boot/install tapes
Installing from tape is the simplest method of all. This method uses two tapes; one called the boot tape, and another called the install tape.

The boot tape is created as follows:


       # cd .../NetBSD-1.6/sun2/installation/tapeimage
       # sh MakeBootTape /dev/nrst0

The install tape is created as follows:


       # cd .../NetBSD-1.6/sun2/installation/tapeimage
       # sh MakeInstallTape /dev/nrst0

If the tapes do not work as expected, you may need to explicitly set the EOF mark at the end of each tape segment. It may also be necessary to use the conv=osync argument to dd(1). Note that this argument is incompatible with the bs= argument. Consult the tape-related manual pages on the system where the tapes are created for more details.

Boot/Install from NFS server
If your machine has a disk and network connection, but no tape drive, it may be convenient for you to install NetBSD over the network. This involves temporarily booting your machine over NFS, just long enough so you can initialize its disk. This method requires that you have access to an NFS server on your network so you can configure it to support diskless boot for your machine. Configuring the NFS server is normally a task for a system administrator, and is not trivial.

If you are using a NetBSD system as the boot-server, have a look at the diskless(8) manual page for guidelines on how to proceed with this. If the server runs another operating system, consult the documentation that came with it (i.e. add_client(8) on SunOS).

When instructed to boot over the network, your sun2 expects to be able to download first and second stage bootstrap programs via ND, the Network Disk protocol. The ndbootd(8) program will attempt to serve a second-stage bootstrap file using a name derived from the machine's recently acquired IP address and an extension which corresponds to the machine architecture. (It may be handy to have a hexadecimal calculator for this next step.) The filename prefix is created by converting the machine's assigned IP address into hexadecimal, most-significant octet first, using uppercase characters for the non-decimal (A-F) digits. The filename suffix used by all sun2 machines is SUN2.

For example, a sun2 which has been assigned IP address 130.115.144.11 will be served a second-stage bootstrap file named 8273900B.SUN2. Normally, this file is a symbolic link to the NetBSD/sun2 netboot program, which should be located in a place where the ndbootd(8) daemon can find it. The netboot program may be found in the installation/netboot directory of this distribution.

The netboot program will query a bootparamd server to find the NFS server address and path name for its root, and then load a kernel from that location. The server should have a copy of the netbsd.RAMDISK kernel in the root area for your client, hard-linked under the names netbsd and vmunix (no other files are needed in the client root) and /etc/bootparams on the server should have an entry for your client and its root directory. The client will need access to the miniroot image, which can be provided using NFS or remote shell.

If you will be installing NetBSD on several clients, it may be useful to know that you can use a single NFS root for all the clients as long as they only use the netbsd.RAMDISK kernel. There will be no conflict between clients because the RAM-disk kernel will not use the NFS root. No swap file is needed; the RAM-disk kernel does not use that either.

Install/Upgrade from CD-ROM
This method requires that you boot from another device (i.e. tape or network, as described above). You may need to make a boot tape on another machine using the files provided on the CD-ROM. Once you have booted netbsd-rd (the RAM-disk kernel) and loaded the miniroot, you can load any of the distribution sets directly from the CD-ROM. The install program in the miniroot automates the work required to mount the CD-ROM and extract the files.
Install/Upgrade via FTP
This method requires that you boot from another device (i.e. tape or network, as described above). You may need to make a boot tape on another machine using the files in installation/tapeimage and binary/kernel (which you get via FTP). Once you have booted netbsd.RAMDISK (the RAM-disk kernel) and loaded the miniroot, you can load any of the distribution sets over the net using FTP. The install program in the miniroot automates the work required to configure the network interface and transfer the files.

The preparations for this installation/upgrade method are easy; all you make sure that there's some FTP site from which you can retrieve the NetBSD distribution when you're about to install or upgrade. You need to know the numeric IP address of that site, and, if it's not on a network directly connected to the machine on which you're installing or upgrading NetBSD, you need to know the numeric IP address of the router closest to the NetBSD machine. Finally, you need to know the numeric IP address of the NetBSD machine itself.

Preparing your System for NetBSD installation

Sun2 machines usually need little or no preparation before installing NetBSD, other than the usual, well advised precaution of backing up all data on any attached storage devices.

You will need to know the SCSI target ID of the drive on which you will install NetBSD.

Note:
SunOS on the sun2 uses confusing names for the SCSI devices: target 1 is sd2, target 2 is sd4, etc.

Installing the NetBSD System

Installing NetBSD is a relatively complex process, but if you have this document in hand it should not be too difficult.

There are several ways to install NetBSD onto your disk. If your machine has a tape drive the easiest way is Installing from tape (details below). If your machine is on a network with a suitable NFS server, then Installing from NFS is the next best method. Otherwise, if you have another Sun machine running SunOS you can initialize the disk on that machine and then move the disk. (Installing from SunOS is not recommended.)

Installing from tape
Create the NetBSD/sun2 1.6 boot tape as described in the section entitled Creating boot/install tapes and boot the tape. At the PROM monitor prompt, use one of the commands:


       >b st()
       >b st(0,8,0)

The first example will use the tape on SCSI target 4, where the second will use SCSI target 5. The > is the monitor prompt.

After the tape loads, you should see many lines of configuration messages, and then the following `welcome' screen:

        Welcome to the NetBSD/sun2 RAMDISK root!
                                                                                     

This environment is designed to do only three things: 1: Partition your disk (use the command: edlabel /dev/rsd0c) 2: Copy a miniroot image into the swap partition (/dev/rsd0b) 3: Reboot (using the swap partition, i.e. /dev/sd?b).

Note that the sun2 firmware cannot boot from a partition located more than 1 GB from the beginning of the disk, so the swap partition should be completely below the 1 GB boundary.

Copying the miniroot can be done several ways, allowing the source of the miniroot image to be on any of these: boot tape, NFS server, TFTP server, rsh server

The easiest is loading from tape, which is done as follows: mt -f /dev/nrst0 rewind mt -f /dev/nrst0 fsf 2 dd bs=32k if=/dev/nrst0 of=/dev/rsd0b (For help with other methods, please see the install notes.)

To reboot using the swap partition, first use "halt", then at the PROM monitor prompt use a command like: b sd(,,1) -s

To view this message again, type: cat /.welcome

Copy the miniroot as described in the welcome message, and reboot from that just installed miniroot. See the section entitled Booting the miniroot for details.

Installing from NFS
Before you can install from NFS, you must have already configured your NFS server to support your machine as a diskless client. Instructions for configuring the server are found in the section entitled Getting the NetBSD System onto Useful Media above.

First, at the Sun PROM monitor prompt, enter a boot command using the network interface as the boot device. If your machine has Intel Ethernet, this is ie, and if it has 3Com Ethernet, this is ec. Examples:


       >b ie() -s
       >b ec() -s

After the boot program loads the RAMDISK kernel, you should see the welcome screen as shown in the Installing from tape section above. You must configure the network interface before you can use any network resources. For example the command:


       ssh> ifconfig ie0 inet 192.233.20.198 up

will bring up the network interface with that address. The next step is to copy the miniroot from your server. This can be done using either NFS or remote shell. (In the examples that follow, the server has IP address 192.233.20.195.) You may then need to add a default route if the server is on a different subnet:


       ssh> route add default 192.233.20.255 1

You can look at the route table using:


       ssh> route show

Now mount the NFS file system containing the miniroot image:


       ssh> mount -o rdonly,-r=1024 192.233.20.195:/server/path /mnt

The procedure is simpler and much faster if you have space for an expanded (not compressed) copy of the miniroot image. In that case:


       ssh> dd if=/mnt/miniroot.fs of=/dev/rsd0b bs=8k

Otherwise, you will need to use zcat to expand the miniroot image while copying. This is tricky because the ssh program (small shell) does not handle sh(1) pipeline syntax. Instead, you first run the reader in the background with its input set to /dev/pipe and then run the other program in the foreground with its output to /dev/pipe. The result looks like this:


       ssh> run -bg dd if=/dev/pipe of=/dev/rsd0b obs=8k
       ssh> run -o /dev/pipe zcat /mnt/install/miniroot.fs.gz

To load the miniroot using rsh to the server, you would use a pair of commands similar to the above. Here is another example:


       ssh> run -b dd if=/dev/pipe of=/dev/rsd0b obs=8k
       ssh> run -o /dev/pipe rsh 192.233.20.195 zcat miniroot.fs.gz

Note that decompression on a sun2 is extremely slow, be prepared to wait. For this reason, expanding the miniroot image on the NFS server is highly recommended.

Once the miniroot has been copied using one of the above methods, you reboot from that just installed miniroot. See the section entitled Booting the miniroot for details.

Installing from SunOS
To install NetBSD/sun2 onto a machine already running SunOS, you will need the miniroot image (miniroot.fs.gz) and some means to decompress it.

First, boot SunOS and place the miniroot file onto the hard drive. If you do not have gzip for SunOS, you will need to decompress the image elsewhere before you can use it.

Next, bring SunOS down to single user mode to insure that nothing will be using the swap space on your drive. To be extra safe, reboot the machine into single-user mode rather than using the shutdown command.

Now copy the miniroot image onto your swap device (here /dev/rsd0b) with the command


       gzip -dc miniroot.fs.gz | dd of=/dev/rsd0b obs=32k

or if you have already decompressed the miniroot


       dd if=miniroot.fs of=/dev/rsd0b obs=32k

Finally, reboot the machine and instruct the PROM to boot from the swap device as described in the next section.

Booting the Miniroot
If the machine is not already at the PROM monitor, run the halt command.

If the miniroot was installed on partition `b' of the disk with SCSI target ID=0 then the PROM boot command would be:


       >b sd(0,0,1) -s

With SCSI target ID=2, the PROM is:


       >b sd(0,10,1) -s

The numbers in parentheses above are:

  1. controller (usually zero)
  2. unit number (SCSI-ID * 8, in hexadecimal)
  3. partition number
Miniroot install program
The miniroot's install program is very simple to use. It will guide you through the entire process, and is well automated. Additional improvements are planned for future releases.

The miniroot's install program will:

First-time installation on a system through a method other than the installation program is possible, but strongly discouraged.

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, along the lines of


           ifconfig_de0="inet 123.45.67.89 netmask 255.255.255.0"

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


           ifconfig_de0="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.

    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. 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 useradd(8) for more information on how to add a new user to the system.

  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.

  6. Misc

Upgrading a previously-installed NetBSD System

It is possible to easily upgrade your existing NetBSD/sun2 system using the upgrade program in the miniroot. If you wish to upgrade your system by this method, simply select the upgrade option once the miniroot has booted. The upgrade program with then guide you through the procedure. The upgrade program will:

Using the miniroot's upgrade program is the preferred method of upgrading your system.

However, it is possible to upgrade your system manually. To do this, follow the following procedure:

Note:
You should not extract the etc set if upgrading. Instead, you should extract that set into another area and carefully merge the changes by hand.

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

Issues affecting an upgrade from NetBSD 1.5
The following issues can generally be resolved by extracting the etc set into a temporary directory and running postinstall:
mkdir /tmp/upgrade
cd /tmp/upgrade
pax -zrpe -f /path/to/etc.tgz
./etc/postinstall -s `pwd` check
./etc/postinstall -s `pwd` fix

Issues fixed by postinstall:

The following issues need to be resolved manually:

Issues affecting an upgrade from NetBSD 1.4 or prior

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:
Jun-ichiro itojun Haginoitojun@netbsd.org
Frank van der Lindenfvdl@netbsd.org
Luke Mewburnlukem@netbsd.org
Christos Zoulaschristos@netbsd.org

The portmasters (and their ports):
Simon Burgesimonb@netbsd.org pmax
Simon Burgesimonb@netbsd.org sbmips
Jeremy Cooperjeremy@netbsd.org sun3x
Matt Fredettefredette@netbsd.org sun2
Chris Gilbertchris@netbsd.org cats
Ross Harveyross@netbsd.org alpha
Jun-ichiro itojun Haginoitojun@netbsd.org sh3
Ben Harrisbjh21@netbsd.org acorn26
Eduardo Horvatheeh@netbsd.org sparc64
Darrin Jewelldbj@netbsd.org next68k
Søren Jørvangsoren@netbsd.org cobalt
Søren Jørvangsoren@netbsd.org sgimips
Wayne Knowleswdk@netbsd.org mipsco
Paul Kranenburgpk@netbsd.org sparc
Frank van der Lindenfvdl@netbsd.org i386
Anders Magnussonragge@netbsd.org vax
Phil Nelsonphil@netbsd.org pc532
NISHIMURA Takeshinsmrtks@netbsd.org x68k
Tohru Nishimuranisimura@netbsd.org luna68k
NONAKA Kimihirononaka@netbsd.org prep
Scott Reynoldsscottr@netbsd.org mac68k
Kazuki Sakamotosakamoto@netbsd.org bebox
Noriyuki Sodasoda@netbsd.org arc
Wolfgang Solfrankws@netbsd.org ofppc
Ignatios Souvatzisis@netbsd.org amiga
Jonathan Stonejonathan@netbsd.org pmax
Shin Takemuratakemura@netbsd.org hpcmips
Jason Thorpethorpej@netbsd.org alpha
Jason Thorpethorpej@netbsd.org hp300
Tsubai Masanaritsubai@netbsd.org macppc
Tsubai Masanaritsubai@netbsd.org newsmips
Izumi Tsutsuitsutsui@netbsd.org news68k
Leo Weppelmanleo@netbsd.org atari
Nathan Williamsnathanw@netbsd.org sun3
Steve Woodfordscw@netbsd.org mvme68k
Steve Woodfordscw@netbsd.org mvmeppc
Reinoud Zandijkreinoud@netbsd.org acorn32

The NetBSD 1.6 Release Engineering team:
Erik Berlscyber@netbsd.org
Håvard Eidneshe@netbsd.org
Perry Metzgerperry@netbsd.org
Luke Mewburnlukem@netbsd.org
Jason Thorpethorpej@netbsd.org
Todd Vierlingtv@netbsd.org

NetBSD Developers:
Nathan Ahlstromnra@netbsd.org
Steve Allenwormey@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
Jason Beeganjtb@netbsd.org
Erik Berlscyber@netbsd.org
Hiroyuki Besshobsh@netbsd.org
John Birrelljb@netbsd.org
Mason Loring Blissmason@netbsd.org
Rafal Bonirafal@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
James Chaconjmc@netbsd.org
Bill Coldwellbillc@netbsd.org
Julian Colemanjdc@netbsd.org
Jeremy Cooperjeremy@netbsd.org
Chuck Cranorchuck@netbsd.org
Alistair Crooksagc@netbsd.org
Aidan Cullyaidan@netbsd.org
Johan Danielssonjoda@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
Håvard Eidneshe@netbsd.org
Stoned Elipotseb@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
Matt Fredettefredette@netbsd.org
Thorsten Frueauffrueauf@netbsd.org
Castor Fucastor@netbsd.org
Ichiro Fukuharaichiro@netbsd.org
Thomas Gernerthomas@netbsd.org
Simon J. Gerratysjg@netbsd.org
Justin Gibbsgibbs@netbsd.org
Chris Gilbertchris@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
HAYAKAWA Koichihaya@netbsd.org
René Hexelrh@netbsd.org
Michael L. Hitchmhitch@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
Bernardo Innocentibernie@netbsd.org
Tetsuya Isakiisaki@netbsd.org
ITOH Yasufumiitohy@netbsd.org
IWAMOTO Toshihirotoshii@netbsd.org
Matthew Jacobmjacob@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
Mattias Karlssonkeihan@netbsd.org
KAWAMOTO Yosihisakawamoto@netbsd.org
Mario Kempermagick@netbsd.org
Thomas Klausnerwiz@netbsd.org
Klaus Kleinkleink@netbsd.org
Wayne Knowleswdk@netbsd.org
John Kohljtk@netbsd.org
Paul Kranenburgpk@netbsd.org
Martti Kuparinenmartti@netbsd.org
Kevin Laheykml@netbsd.org
Johnny C. Lamjlam@netbsd.org
Martin J. Laubachmjl@netbsd.org
Ted Lemonmellon@netbsd.org
Frank van der Lindenfvdl@netbsd.org
Joel Lindholmjoel@netbsd.org
Mike Longmikel@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
Minoura Makotominoura@netbsd.org
Luke Mewburnlukem@netbsd.org
der Mousemouse@netbsd.org
Joseph Myersjsm@netbsd.org
Ken Nakatakenn@netbsd.org
Phil Nelsonphil@netbsd.org
Bob Nestorrnestor@netbsd.org
NISHIMURA Takeshinsmrtks@netbsd.org
Tohru Nishimuranisimura@netbsd.org
NONAKA Kimihirononaka@netbsd.org
Jesse Offjoff@netbsd.org
Tatoku Ogaitotacha@netbsd.org
Masaru Okioki@netbsd.org
Atsushi Onoeonoe@netbsd.org
Greg Osteroster@netbsd.org
Herb Peyerlhpeyerl@netbsd.org
Matthias Pfallermatthias@netbsd.org
Chris Pinnockcjep@netbsd.org
Dante Profetadante@netbsd.org
Chris Provenzanoproven@netbsd.org
Michael Rauchmrauch@netbsd.org
Darren Reeddarrenr@netbsd.org
Scott Reynoldsscottr@netbsd.org
Michael Richardsonmcr@netbsd.org
Tim Rightnourgarbled@netbsd.org
Gordon Rossgwr@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
Reed Shadgettdent@netbsd.org
Tim Shepardshep@netbsd.org
Takeshi Shibagakishiba@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
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
Matt Thomasmatt@netbsd.org
Jason Thorpethorpej@netbsd.org
Christoph Toshoktoshok@netbsd.org
Tsubai Masanaritsubai@netbsd.org
Izumi Tsutsuitsutsui@netbsd.org
UCHIYAMA Yasushiuch@netbsd.org
Masao Uebayashiuebayasi@netbsd.org
Shuichiro URATAur@netbsd.org
Todd Vierlingtv@netbsd.org
Aymeric Vincentaymeric@netbsd.org
Paul Vixievixie@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
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, Inc.
This product includes software developed by the NetBSD Foundation, Inc. and its contributors.
This product includes software developed by the Computer Systems Engineering Group at Lawrence Berkeley Laboratory.
This product includes software developed by Adam Glass and Charles Hannum.
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 Alistair G. Crooks.
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 Charles D. Cranor and Washington University.
This product includes software developed by Charles D. Cranor.
This product includes software developed by Charles Hannum, by the University of Vermont and State Agricultural College and Garrett A. Wollman, by William F. Jolitz, and by the University of California, Berkeley, Lawrence Berkeley Laboratory, and its contributors.
This product includes software developed by Charles Hannum.
This product includes software developed by Charles M. Hannum.
This product includes software developed by Chris Provenzano.
This product includes software developed by Christian E. Hopps.
This product includes software developed by Christopher G. Demetriou for the NetBSD Project.
This product includes software developed by Christopher G. Demetriou.
This product includes software developed by Christos Zoulas.
This product includes software developed by David Jones and Gordon Ross.
This product includes software developed by Dean Huxley.
This product includes software developed by Eric S. Hvozda.
This product includes software developed by Ezra Story.
This product includes software developed by Gardner Buchanan.
This product includes software developed by Gordon Ross.
This product includes software developed by Gordon W. Ross and Leo Weppelman.
This product includes software developed by Gordon W. Ross.
This product includes software developed by Hauke Fath.
This product includes software developed by HAYAKAWA Koichi.
This product includes software developed by Hellmuth Michaelis and Joerg Wunsch.
This product includes software developed by Herb Peyerl.
This product includes software developed by Holger Veit and Brian Moore for use with "386BSD" and similar operating systems.
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 W. Dall.
This product includes software developed by Ignatios Souvatzis for the NetBSD Project.
This product includes software developed by Jason R. Thorpe for And Communications, http://www.and.com/.
This product includes software developed by Joachim Koenig-Baltes.
This product includes software developed by Jochen Pohl for The NetBSD Project.
This product includes software developed by John Polstra.
This product includes software developed by Jonathan Stone and Jason R. Thorpe for the NetBSD Project.
This product includes software developed by Jonathan Stone for the NetBSD Project.
This product includes software developed by Jonathan Stone.
This product includes software developed by Julian Highfield.
This product includes software developed by Kenneth Stailey.
This product includes software developed by Leo Weppelman.
This product includes software developed by Lloyd Parkes.
This product includes software developed by Manuel Bouyer.
This product includes software developed by Marc Horowitz.
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 Martin Husemann and Wolfgang Solfrank.
This product includes software developed by Mats O Jansson and Charles D. Cranor.
This product includes software developed by Mats O Jansson.
This product includes software developed by Matthias Pfaller.
This product includes software developed by Michael L. Hitch.
This product includes software developed by Niels Provos.
This product includes software developed by Paul Kranenburg.
This product includes software developed by Paul Mackerras.
This product includes software developed by Peter Galbavy.
This product includes software developed by Philip A. Nelson.
This product includes software developed by Rodney W. Grimes.
This product includes software developed by Roland C. Dowdeswell.
This product includes software developed by Rolf Grossmann.
This product includes software developed by Scott Bartram.
This product includes software developed by SigmaSoft, Th. Lockert.
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 Theo de Raadt and John Brezak.
This product includes software developed by Theo de Raadt.
This product includes software developed by Tohru Nishimura for the NetBSD Project.
This product includes software developed by TooLs GmbH.
This product includes software designed by William Allen Simpson.
This product includes software developed by Winning Strategies, Inc.
This product includes software developed by Zembu Labs, Inc.
This product includes software developed by the Center for Software Science at the University of Utah.
This product includes software developed by the Computer Systems Laboratory at the University of Utah.
This product includes software developed by the University of Calgary Department of Computer Science and its contributors.
This product includes software developed by the University of Vermont and State Agricultural College and Garrett A. Wollman.
This product includes software developed for the FreeBSD project.
This product includes software developed for the Internet Software Consortium by Ted Lemon.
This product includes software developed for the NetBSD Project by Frank van der Linden.
This product includes software developed for the NetBSD Project by Jason R. Thorpe.
This product includes software developed for the NetBSD Project by John M. Vinopal.
This product includes software developed for the NetBSD Project by Matthias Drochner.
This product includes software developed for the NetBSD Project by Matthieu Herrb.
This product includes software developed for the NetBSD Project by Perry E. Metzger.
This product includes software developed for the NetBSD Project by Piermont Information Systems Inc.
This product includes software developed for the NetBSD Project by Ted Lemon.
This product includes software developed for the NetBSD Project by Wasabi Systems, Inc.
This product includes software developed by LAN Media Corporation and its contributors.
This product includes software developed by Michael Graff for the NetBSD Project.
This product includes software developed by Niklas Hallqvist, C Stone and Job de Haas.
This product includes software developed by Eric Young (eay@mincom.oz.au).
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 University of Oregon.
This product includes software developed by the University of Southern California and/or Information Sciences Institute.
This product includes software developed by Internet Initiative Japan Inc.
This product includes software developed by Reinoud Zandijk.
This product includes software developed at the Information Technology Division, US Naval Research Laboratory.

The End