NAME

INSTALL - Installation procedure for NetBSD/pmax.

DESCRIPTION

About this Document

This document describes the installation procedure for NetBSD1.5 on the pmax 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 thirty-one different system architectures featuring twelve distinct families of CPUs, and is being ported to more. The NetBSD1.5 release contains complete binary releases for fifteen different machine types. (The sixteen 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.

Changes Since The Last Release

The NetBSD1.5 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 userland 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 one year of development that went into the NetBSD1.5 release. Some highlights include:

Kernel

  • Ports to new platforms including: arc, cobalt, hpcmips, news68k, sgimips, and sparc64.

  • Improved performance and stability of the UVM virtual memory subsystem.

  • Implementation of generic kernel locking code, as well as a restructure and re-tuning of the scheduler, to be used by the future symmetric multi-processing (SMP) implementation.

  • Improved compatibility support for Linux, OSF1, and SVR4 programs.

  • New compatibility support for Win32 programs.

  • Support for dynamically loaded ELF kernel modules.

  • Kernel process tracing using ktruss(1).

  • Deletion of swap devices using swapctl(8).

  • Easier hot-pluggability of keyboards and mice using a new wscons device - wsmux.

  • Improved PCMCIA and Cardbus support, including support for detaching of devices and cards, resulting in better support for notebooks and PDA devices.

  • Numerous hardware improvements, including areas such as: audio, UDMA/66 support for ATA drives, USB, and wireless networking.
Networking

  • Addition of IP version 6 (IPv6) and IPsec to the networking stack, from the KAME project. This includes addition of kernel code for IPv6/IPsec, IPv4/v6 dual-stack user applications and supporting libraries. Due to this, the shlib major version for pcap(3) is incremented and you may need to recompile userland tools. The KAME IPv6 part includes results from the unified-ipv6 effort.
File system

  • Significant Fast file system (FFS) performance enhancements via integration of Kirk McKusick's soft updates and trickle sync code.

  • Support for the Windows NT `NTFS' file system (read-only at this stage).

  • Support for revision 1 of the Linux `ext2fs' file system.

  • Enhanced stability and usability of LFS (the BSD log-structured file system).

  • Various RAIDframe enhancements including: auto-detection of RAID components and auto-configuration of RAID sets, and the ability to configure the root file system (/) on a RAID set.

  • Support for Microsoft Joliet extensions to the ISO9660 CD file system.

  • Improved file system vnode locking mechanisms, thus resolving a source of several panics in the past.

  • Support for NFS and RPC over IPv6.

  • Server part of NFS locking (implemented by rpc.lockd(8)) now works.
Security

  • Strong cryptographic libraries and applications integrated, including the AES cipher Rijndael, the OpenSSL library, more complete Kerberos IV and Kerberos V support, and an SSH server and client.

  • sysctl(3) interfaces to various elements of process and system information, allowing programs such as ps(1), dmesg(1) and the like to operate without recompilation after kernel upgrades, and remove the necessity to run setgid kmem (thus improving system security).

  • Disable various services by default, and set the default options for disabled daemons to a higher level of logging.

  • Several code audits were performed. One audit replaced string routines that were used without bound checking, and another one to identify and disable places where format strings were used in an unsafe way, allowing arbitrary data entered by (possibly) malicious users to overwrite application code, and leading from Denial of Service attacks to compromised system.
System administration and user tools

  • Conversion of the rc(8) system startup and shutdown scripts to an `rc.d' mechanism, with separate control scripts for each service, and appropriate dependency ordering provided by rcorder(8).

  • postfix(1) provided as alternative mail transport agent to sendmail(8).

  • User management tools useradd(8), usermod(8), userdel(8), groupadd(8), groupmod(8), and groupdel(8) added to the system.

  • Incorporation of a login class capability database (/etc/login.conf) from BSD/OS.

  • Improved support for usernames longer than eight characters in programs such as at(1) and w(1).

  • Many enhancements to ftpd(8) providing features found in larger and less secure FTP daemons, such as user classes, connection limits, improved support for virtual hosting, transfer statistics, transfer rate throttling, and support for various IETF ftpext working group extensions.

  • The ftp(1) client has been improved even further, including transfer rate throttling, improved URL support, command line uploads. See the man page for details.
Miscellaneous

  • Updates to the NetBSD source code style code (located in /usr/share/misc/style) to use ANSI C only (instead of K&R) and reflect current (best) practice, and begin migrating the NetBSD source code to follow it.

  • Implementation of many SUSv2 features to the curses(3) library, including support for color.

  • Updates of most third party packages that are shipped in the base system, including file(1), ipfilter(4), ppp(4), and sendmail(8) to the latest stable release.

  • Many new packages in the pkgsrc system, including standard desktops like KDE and GNOME as well as latest Tcl/Tk and perl and many of the components of the Java Enterprise platform. The package framework itself now has full wildcard dependency support.

As has been noted, there have also been innumerable bug fixes.

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.

This is the fifth major release of NetBSD for the DECstation and DECsystem family of computers. Some pmax-specific changes from the previous major release include:

  • (Optional) use of the MI SCSI subsystem.

  • Support for the DECsystem 5100.

  • 5000/xx audio support.

  • Support for booting off RAIDframe RAID1 mirrors, and support for booting off ISO9660 (CD-ROM) and LFS file systems.

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:

  • providing better organization to keep track of development efforts, including co-ordination with groups working in related fields.

  • providing a framework to receive donations of goods and services and to own the resources necessary to run the NetBSD Project.

  • providing a better position from which to undertake promotional activities.

  • periodically organizing workshops for developers and other interested people to discuss ongoing work.

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.5 Release Contents

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

.../NetBSD-1.5/

CHANGES
Changes since earlier NetBSD releases.

LAST_MINUTE
Last minute changes.

MIRRORS
A list of sites that mirror the NetBSD1.5 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.5 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.
22.3 MB gzipped, 98.8 MB uncompressed

pkgsrc
This set contains the ``pkgsrc'' sources, which contain the infrastructure to build third-party packages.
5.6 MB gzipped, 57.0 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.
3.3 MB gzipped, 13.2 MB uncompressed

src
This set contains all of the base NetBSD1.5 sources which are not in gnusrc, sharesrc, or syssrc.
24.2 MB gzipped, 120.6 MB uncompressed

syssrc
This set contains the sources to the NetBSD1.5 kernel for all architectures, config(8), and dbsym(8).
17.6 MB gzipped, 88.6 MB uncompressed

xsrc
This set contains the sources to the X Window System.
35.2 MB gzipped, 176.8 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. They 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/pmax subdirectory structure
The pmax-specific portion of the NetBSD1.5 release is found in the pmax subdirectory of the distribution: .../NetBSD-1.5/pmax/
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/
pmax binary distribution sets; see below.
installation/
floppy/
pmax boot and installation floppies; see below.
misc/
Miscellaneous pmax installation utilities; see installation section, below.
Binary distribution sets
The NetBSD pmax binary distribution sets contain the binaries which comprise the NetBSD1.5 release for the pmax. There are eight binary distribution sets. The binary distribution sets can be found in the pmax/binary/sets subdirectory of the NetBSD1.5 distribution tree, and are as follows:

base
The NetBSD1.5 pmax 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.
19.0 MB gzipped, 61.2 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.4 MB gzipped, 57.2 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. (If you are upgrading, it's recommended that you get a copy of this set and carefully upgrade your configuration files by hand.)
0.1 MB gzipped, 0.6 MB uncompressed

games
This set includes the games and their manual pages.
3.0 MB gzipped, 7.9 MB uncompressed

kern
This set contains a NetBSD/pmax 1.5 GENERIC kernel, named /netbsd. You must install this distribution set.
1.1 MB gzipped, 2.7 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.
5.0 MB gzipped, 19.9 MB uncompressed

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

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

NetBSD maintains its own set of sources for the X Window System in order to assure tight integration and compatibility. These sources are based on XFree86, and tightly track XFree86 releases. They are currently equivalent to XFree86 3.3.6. 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.
3.2 MB gzipped, 11.4 MB uncompressed

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

xcontrib
Programs that were contributed to X.
0.2 MB gzipped, 0.8 MB uncompressed

xfont
Fonts needed by X.
6.2 MB gzipped, 7.5 MB uncompressed

xserver
The Xpmax server with man page. 1.8 MB gzipped, 5.6 MB uncompressed

The pmax 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 files are /-relative and therefore are extracted below the current directory. That is, 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 /.

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

NetBSD/pmax System Requirements and Supported Devices

Supported machines

  • DECstation 2100 and 3100, also known as pmin and pmax

  • DECsystem 5100

  • Personal DECstations (5000/20, /25 and /33) also known as MAXINE

  • DECstation 5000/120, /125, and /133, also known as 3MIN

  • DECstation 5000/200, also known as 3MAX

  • DECstation 5000/240 and DECsystem 5900, also known as 3MAXPLUS

  • DECstation 5000/50, 5000/150, 5000/260 (and DECsystem 5900-260) - R4000 and R4400 variants of the MAXINE, 3MIN and 3MAXPLUS
Unsupported machines

  • DECsystem 5400 and 5500 (Q-bus based systems, similar to the Vax Mayfair or Mayfair II, but with an r2000a or r3000 cpu instead of a CVAX cpu.)

  • DECsystem 5800 (xbi-based multiprocessor, a Vax 6200 with Vax CPU boards replaced with Mips cpu boards)

The minimal configuration requires 8 MB of RAM and ~60 MB of disk space. To install the entire system requires much more disk space, and to run X or compile the system, more RAM is recommended, as NetBSD with 8 MB of RAM feels like Ultrix with 8 MB of RAM - slow. Note that until you have around 16 MB of RAM, getting more RAM is more important than getting a faster CPU.

Supported devices

  • DECstation 2100 and 3100 baseboard video
    - one-bit mono or 8-bit pseudocolor frame buffers.

  • DECstation 5000 series TurboChannel video
    - PMAG-DV Personal DECstation baseboard 1024x768 frame buffer
    - PMAG-BA 1024x768 8-bit color frame buffer
    - PMAGB-BA 1024x768 8-bit color frame buffer
    - PMAG-AA 1280x1024 four-bit greyscale frame buffer
    - PMAG-C (PX) 2D 8-bit accelerated frame buffer.
    - PMAG-D (PXG) 3D 8-bit accelerated frame buffer.
    - PMAG-E (PXG+) 3D 24-bit accelerated frame buffer.
    - PMAG-F (PXG+ Turbo) 3D 24-bit accelerated frame buffer.

    Note:
    All supported DECstation video produces sync-on-green. Be sure to use either a DEC-compatible fixed-sync monitor or a multisync monitor that supports sync-on-green.

  • Serial ports
    - ttya and ttyb (can be used as console if needed)

  • Ethernet
    - on-board AMD Lance ethernet (le0),
    - TURBOchannel AMD Lance ethernet cards (the PMAD)

  • SCSI
    - on-board DEC sii SCSI controller (2100 and 3100)
    - on-board asc SCSI controller (5000 series machines)
    - TurboChannel asc SCSI controller (the PMAZ)

  • DEC LK-201 (or compatible) keyboard

  • DEC hockey puck or compatible mouse
Unsupported devices

  • Q-bus based DECsystems

  • PrestoServe NVRAM on DECsystem 5100 and 5000/2xx machines

  • Audio drivers for Personal DECstation machines

  • Floppy driver for Personal DECstation machines

  • TurboChannel audio hardware (LoFi)

Note:
The primary obstacle to supporting the above is non-availability of sample hardware for development.

Getting the NetBSD System on to Useful Media

First-time installation on a bare machine is not supported, because most DECstations do not have any suitable load device. Some versions of the DECstation PROM are buggy and will not boot via TFTP and bootp; other versions are buggy and do not boot via MOP.

The only DECstation with a floppy-disk drive is the Personal DECstation, and that device is not supported as a boot device.

The recommended installation procedure is to boot an install kernel via TFTP, or to use a ``helper'' system to write a miniroot diskimage onto a disk, move that disk to the target installation system, and then boot the miniroot.

Installation is supported from several media types, including:

  • CD-ROM
  • FTP
  • Remote NFS partition
  • Tape
  • Existing NetBSD partitions, if performing an upgrade

The steps necessary to prepare the distribution sets for installation depend upon which installation medium you choose. The steps for the various media are outlined below.

CD-ROM
Find out where the distribution set files are on the CD-ROM.

Proceed to the instruction 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. 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. If you don't have access to a functioning nameserver during installation, the IP address of ftp.netbsd.org is 204.152.184.75 (as of October, 2000).

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.

Note:
This method of installation is recommended only for those already familiar with using BSD network configuration and management commands. If you aren't, this documentation should help, but is not intended to be all-encompassing.

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

Note:
This method of installation is recommended only for those already familiar with using BSD network configuration and management commands. If you aren't, this documentation should help, but is not intended to be all-encompassing.

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

Note:
the tape devices with which NetBSD/pmax is believed to work is the DEC TK-50. This is a very slow device. Installation via disk or network is recommended if at all possible.

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 misc, 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-1.5
       # cd pmax/binary
       # tar -cf tape_device misc etc kern

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.

Upgrade
If you are upgrading NetBSD, you also have the option of installing NetBSD by putting the new distribution sets somewhere in your existing file system, and using them from there. To do that, you must do the following:

Place the distribution sets you wish to upgrade somewhere in your current file system tree.

At a bare minimum, you must upgrade the base and kern binary distributions, and so must put the base and kern sets somewhere in your file system. If you wish, you can do the other sets, as well, but you should not upgrade the etc distribution; it contains contains system configuration files that you should review and update by hand.

Once you have done this, you can proceed to the next step in the upgrade process, actually upgrading your system.


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 your hard disk that you wish to keep. Mistakes in partitioning your hard disk may lead to data loss.

Installing the NetBSD System

Note:
There may be updates to this procedure available from the NetBSD/pmax web page, at http://www.netbsd.org/Ports/pmax.

To install or upgrade NetBSD, you need to first boot an installation program and then interact with the screen-menu program sysinst. The installation program actually consists of the NetBSD kernel plus an in-memory file system of utility programs.

From most convenient to least convenient, the installation methods are:

  1. Installation from an existing NetBSD or Ultrix system by booting the install kernel from an existing root file system (/). See the Installing from an existing system section later in these INSTALL notes.

  2. Copying a bootable diskimage onto the beginning of a disk and installing onto that disk. See the Install via diskimage section later in these INSTALL notes.

  3. Booting the install kernel over the network and installing onto a local disk. See the Install via netboot install kernel section later in these INSTALL notes.

  4. Using a helper machine with a SCSI controller to copy the bootable diskimage onto the beginning of a disk, and moving the disk to the target machine. See the Install via diskimage section later in these INSTALL notes.

  5. For machines with some PROMs that cannot netboot standard kernels, you will need to set up an NFS server with a diskless root file system for trimmed-down network install kernel and run the installation system from the NFS root file system. See the Install via diskless boot section later in these INSTALL notes.

You should familiarize yourself with the console PROM environment and the hardware configuration. The PROMs on the older DECstation 2100 and 3100 use one syntax. The PROMs on the TurboChannel machines use a completely different syntax. Be sure you know how to print the configuration of your machine, and how to boot from disk or network, as appropriate.

To boot from disk, use:

2100 or 3100:
boot -f rz(0,X,0)netbsd
5000/200:
boot 5/rzX/netbsd
other 5000s:
boot 3/rzX/netbsd

To boot via TFTP, use:

2100 or 3100:
boot -f tftp()
5000/200:
boot 6/tftp
other 5000s:
boot 3/tftp

To boot via MOP, use:

2100 or 3100:
boot -f mop()
5000/200:
boot 6/mop
other 5000s:
boot 3/mop

You will also need to know the total size (in sectors) and the approximate geometry of the disks you are installing onto, so that you can label your disks for the BSD fast file system (FFS). For most SCSI drives (including all SCSI-2 drives), the kernel will correctly detect the disk geometry. The sysinst tool will suggest these as the default.

If you're installing NetBSD/pmax for the first time it's a very good idea to pre-plan partition sizes for the disks on which you're installing NetBSD. Changing the size of partitions after you've installed is difficult. If you do not have a spare bootable disk, it may be simpler to re-install NetBSD again from scratch.

Assuming a classic partition scheme with separate / (root) and /usr file systems, a comfortable size for the NetBSD / partition is about 32 MB. A good initial size for the swap partition is twice the amount of physical memory in your machine (though, unlike Ultrix, there are no restrictions on the size of the swap partition that would render part of your memory unusable). The default swap size is 64 MB, which is adequate for doing a full system build. A full binary installation, with X11R6.3 takes about 150 MB in /usr; a 200 MB /usr should be ample.

Install via a NetBSD CD-ROM
You can obtain the disk image or diskless boot tar file from the NetBSD1.5 CD-ROM.

To mount the CD-ROM from a NetBSD/pmax host, type

       # mount -r -t cd9660 /dev/rzXc /mnt

and from an Ultrix host


       # mount -r -t cdfs -o nodefperm,noversion /dev/rzXc /mnt

where X is the SCSI-ID of the CD-ROM.

Note:
Ultrix does not have Rock Ridge extensions so leave out everything between the first and last period (`.') in the paths on the CD. For example, the path NetBSD-1.4.3 would show up as NetBSD-1.3.

The diskimage file can be found on the CD-ROM at the following location (relative to the mount point of the CD)


       pmax/installation/diskimage/diskimage.gz

and the diskless boot tar file can be found at


       pmax/installation/netboot/diskimage.tgz

Once you have located these files, continue on to either Install via netboot install kernel, Install via diskless boot, Install via diskimage or Installing from an existing system section later in the INSTALL notes.

Installing from an existing system

Note:
If you are installing NetBSD using an existing NetBSD system that is older than NetBSD1.4, you will need to install new bootblocks before installing NetBSD1.5. New bootblocks are in the tar file:


       pmax/installation/misc/bootblocks.tgz

in the NetBSD1.5 distribution. To install the new bootblocks, use the following commands:


       # cd /
       # tar -zxpvf .../pmax/installation/misc/bootblocks.tgz
       # /usr/mdec/installboot /dev/rrzXc /usr/mdec/bootxx_ffs

where X is your boot disk SCSI-ID.

With new NetBSD bootblocks or using the Ultrix bootloader, you can boot the kernel located in:


       pmax/binary/kernel/install.gz

On Ultrix systems you will need to gunzip this kernel before booting it. A copy of the gunzip binary for Ultrix systems is located in:


       pmax/installation/misc/gunzip.ultrix

Then boot using one of:

2100 or 3100:
boot -f rz(0,X,0)install
5000/200:
boot 5/rzX/install
other 5000s:
boot 3/rzX/install

where X is your boot disk SCSI-ID, and continue to the Once you've booted the diskimage section

Install via diskimage
The diskimage file is in


       pmax/installation/diskimage/diskimage.gz.

It is shipped compressed and is around 1150 kbytes, uncompressing to exactly 2 MB.

To install the diskimage onto disk rzX on a NetBSD/pmax system, do:


       # disklabel -W /dev/rrzXc
       # gunzip -c diskimage.gz | dd of=/dev/rrzXc bs=10240

When installing on a disk with no NetBSD or Ultrix label, you may get a message like:


       rzX: WARNING: trying Ultrix label, no disk label

or when installing on an old Ultrix disk, you may get a message like:


       rzX: WARNING: using ULTRIX partition information

when issuing the disklabel -W /dev/rrzXc command. This can safely be ignored.

Most other NetBSD ports are similar, but use `rsdXc' instead of `rrzXc'.

On NetBSD/i386, the ``raw disk partition'' is the `d' parttion, so do:


       # disklabel -W /dev/rsdXd
       # gunzip -c diskimage.gz | dd of=/dev/rsdXd bs=10240

On NetBSD, be sure to use disklabel -W to enable writing to the label area of the disk. If you forget this and/or use the `block' device, the dd command may silently fail.

On Ultrix systems, do:


       # gunzip -c diskimage.gz | dd of=/dev/rrzXc bs=10240

A copy of the gunzip program is located in


       pmax/installation/misc/gunzip.ultrix

if you do not already have it.

On MS-DOS, use an `unzip' utlility, then use rawrite.

Then boot using one of:

2100 or 3100:
boot -f rz(0,X,0)install
5000/200:
boot 5/rzX/install
other 5000s:
boot 3/rzX/install

where X is your boot disk SCSI-ID, and continue to the Once you've booted the diskimage section.

Install via netboot install kernel
Booting NetBSD/pmax 1.5 install kernel over a network requires a BOOTP or DHCP server and a TFTP server. (These are usually all run on the same machine.) There are two basic stages to the boot:

  • The pmax PROM software sends a BOOTP request to get its own address, the address of the TFTP server and the file to download.

  • It downloads the file name obtained from BOOTP, which is the install kernel, via TFTP and then executes it.

You will need to set up servers for BOOTP and TFTP.

For the BOOTP server you need to specify the:

  • hardware type (Ethernet)
  • hardware address (Ethernet MAC address)
  • IP address of the client
  • subnet mask of the client
  • address of the TFTP server
  • name of the kernel loaded via TFTP

Here's an example for a UNIX-like system running bootpd:

myhost.mydom.com:\
      :ht=ethernet:ha=08002b123456:\
      :ip=192.168.1.2:sm=255.255.255.0:\
      :sa=192.168.1.1:bf=install:\
      :rp=/usr/export/pmax:

And here's an example for a UNIX-like system running the ISC dhcpd:

host pmax {
     hardware ethernet 08:0:2b:12:34:56;
     fixed-address 192.168.1.2;
     option host-name "myhost.mydom.com";
     filename "install";
     option domain-name-servers 192.168.1.1;
     option broadcast-address 255.255.255.0;
     option domain-name "my.domain";
     option root-path "/usr/export/pmax";
}

For the TFTP server, You will need to copy the install.ecoff kernel to the directory used by the TFTP server. This file must be gunzipped.

Then boot using one of:

2100 or 3100:
boot -f tftp()
5000/200:
boot 6/tftp
other 5000s:
boot 3/tftp

and continue to the Once you've booted the diskimage section.

Install via diskless boot
The file pmax/installation/netboot/diskimage.tar.gz contains a suitable set of files for installing on an NFS server to set up a diskless root filesytem. (It is a tar copy of the contents of an installation ramdisk file system contained in the install kernel.) You will need to find an NFS server, unpack the tarfile, and setup BOOTP/dhcp service for your pmax. Instructions for setting up an NFS server and diskless booting are on the NetBSD/pmax netboot webpage at http://www.netbsd.org/Ports/pmax/netboot.html

Since the system install utility, sysinst, requires a read/write root, installing via diskless boot is only feasible if your NFS server exports the diskless root read-write. If this is not possible, you should install via other of the other installation procedures.

Once you have booted the kernel, continue to the Once you've booted the diskimage section.

Once you've booted the diskimage
Once you'e booted the installation kernel you will need to select your terminal type. Use pmax for a framebuffer console, vt100 for a serial console with a vt100-compatible terminal, or xterm or xterms for a tip(1) or cu(1) connection running in an xterm(1).

The system will then start the sysinst program.

Running the sysinst installation program

  1. Introduction

    Using sysinst, installing NetBSD is a relatively easy process. You still should read this document and have it in hand when doing the installation process. This document tries to be a good guideline for the installation and as such covers many details to be completed. Do not let this discourage you, the install program is not hard to use.

  2. General

    The following is a walk-through of the steps you will take while getting NetBSD installed on your hard disk. sysinst is a menu driven installation system that allows for some freedom in doing the installation. Sometimes, questions will be asked and in many cases the default answer will be displayed in brackets (``[ ]'') after the question. If you wish to stop the installation, you may press CONTROL-C at any time, but if you do, you'll have to begin the installation process again from scratch.

  3. Quick install

    First, let's describe a quick install. The other sections of this document go into the installation procedure in more detail, but you may find that you do not need this. If you want detailed instructions, skip to section 3. This section describes a basic installation, using a CD-ROM install as an example.

    • What you need.

      - The distribution sets (in this example, they are on CD).

      - A CD-ROM drive (SCSI), a harddisk and a minimum of 8 MB of memory installed.

      - The harddisk should have at least 200 + n megabytes of space free, where n is the number of megabytes of main memory in your system. If you wish to install the X window system as well, you will need at least 60 MB more.

    • The Quick Installation

      - Boot the system as described above. You should be at the sysinst main menu.

      - If you wish, you can configure some network settings immediately by choosing the utilities menu and then configure network. It isn't actually required at this point, but it may be more convenient. Go back to the main menu.

      - Choose install

      - You will be guided through some steps regarding the setup of your disk, and the selection of distributed components to install. When in doubt, refer to the rest of this document for details.

      - After your disk has been prepared, choose CD-ROM as the medium. The default values for the path and device should be ok.

      - After all the files have been unpacked, go back to the main menu and select reboot.

      - NetBSD will now boot. If you haven't already done so in sysinst, you should log in as root, and set a password for that account. You are also advised to edit the file /etc/rc.conf to match your system needs.

      - Your installation is now complete.

      - For configuring the X window system, if installed, see the files in /usr/X11R6/lib/X11/doc. Further information can be found on http://www.xfree86.org/

  4. Booting NetBSD

    Boot the system as described in the previous section.

    You may want to read the boot messages, to notice your disk's name and geometry. Its name will be something like sd0 and the geometry will be printed on a line that begins with its name. As mentioned above, you may need your disk's geometry when creating NetBSD's partitions. You will also need to know the name, to tell sysinst on which disk to install. The most important thing to know is that sd0 is your first SCSI disk, sd1 the second, etc.

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

  5. Network configuration

    If you will not use network operation during the installation, but you do want your machine to be configured for networking once it is installed, you should first go to the utilities menu, and select Configure network option. If you only want to temporarily use networking during the installation, you can specify these parameters later. If you are not using Domain Name Service (DNS), you can give an empty response in reply to answers relating to this.

  6. Installation drive selection and parameters

    To start the installation, select the menu option to install NetBSD from the main menu.

    The first thing is to identify the disk on which you want to install NetBSD. sysinst will report a list of disks it finds and ask you for your selection. Depending on how many disks are found, you may get a different message. You should see disk names like rz0 or rz1

  7. Partitioning the disk

    • Which portion of the disk to use.

      You will be asked if you want to use the entire disk or only part of the disk. If you decide to use the entire disk for NetBSD, it will be checked if there are already other systems present on the disk, and you will be asked to confirm whether you want to overwrite these.

    • Editing the NetBSD disklabel

      The partition table of the NetBSD part of a disk is called a disklabel. There are 3 layouts for the NetBSD part of the disk that you can pick from: Standard, Standard with X and Custom. The first two use a set of default values (that you can change) suitable for a normal installation, possibly including X. The last option lets you specify everything yourself.

      You will be presented with the current layout of the NetBSD disklabel, and given a chance to change it. For each partition, you can set the type, offset and size, block and fragment size, and the mount point. The type that NetBSD uses for normal file storage is called 4.2BSD. A swap partition has a special type called swap. Some partitions in the disklabel have a fixed purpose.

      a
      Root partition. (/),

      b
      Swap partition.

      c
      The entire disk.

      d-h
      Available for other use. Traditionally, d is the partition mounted on /usr, but this is historical practice and not a fixed value.

      You will then be asked to name your disk's disklabel. The default response is mydisk. For most purposes this will be OK. If you choose to name it something different, make sure the name is a single word and contains no special characters. You don't need to remember this name.

  8. Preparing your hard disk

    You are now at the point of no return. Nothing has been written to your disk yet, but if you confirm that you want to install NetBSD, your hard drive will be modified. If you are sure you want to proceed, enter yes at the prompt.

    The install program will now label your disk and make the file systems you specified. The file systems will be initialized to contain NetBSD bootstrapping binaries and configuration files. You will see messages on your screen from the various NetBSD disk preparation tools that are running. There should be no errors in this section of the installation. If there are, restart from the beginning of the installation process. Otherwise, you can continue the installation program after pressing the return key.

  9. Getting the distribution sets

    The NetBSD distribution consists of a number of sets, that come in the form of gzipped tarfiles. A few sets must be installed for a working system, others are optional. At this point of the installation, you will be presented with a menu which enables you to choose from one of the following methods of installing the sets. Some of these methods will first load the sets on your hard disk, others will extract the sets directly.

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

  10. Installation using ftp

    To be able to install using ftp, you first need to configure your network setup, if you haven't already at the start of the install procedure. sysinst will do this for you, asking you to provide some data, like IP number, hostname, etc. If you do not have name service set up for the machine that you are installing on, you can just press RETURN in answer to these questions, and DNS will not be used.

    You will also be asked to specify the host that you want to transfer the sets from, the directory on that host, and the account name and password used to log into that host using ftp. If you did not set up DNS when answering the questions to configure networking, you will need to specify an IP number instead of a hostname for the ftp server.

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

  11. Installation using NFS

    To be able to install using NFS, you first need to configure your network setup, if you haven't already at the start of the install procedure. sysinst will do this for you, asking you to provide some data, like IP number, hostname, etc. If you do not have name service set up for the machine that you are installing on, you can just press RETURN in answer to these questions, and DNS will not be used.

    You will also be asked to specify the host that you want to transfer the sets from, and the directory on that host that the files are in. This directory should be mountable by the machine you are installing on, i.e. correctly exported to your machine.

    If you did not set up DNS when answering the questions to configure networking, you will need to specify an IP number instead of a hostname for the NFS server.

  12. Installation from CD-ROM

    When installing from a CD-ROM, you will be asked to specify the device name for your CD-ROM player (usually cd0), and the directory name on the CD-ROM where the distribution files are.

    sysinst will then check if the files are indeed available in the specified location, and proceed to the actual extraction of the sets.

  13. Installation from an unmounted file system

    In order to install from a local file system, you will need to specify the device that the file system resides on (for example rz1e) the type of the file system, and the directory on the specified file system where the sets are located. sysinst will then check if it can indeed access the sets at that location.

  14. Installation from a local directory

    This option assumes that you have already done some preparation yourself. The sets should be located in a directory on a file system that is already accessible. sysinst will ask you for the name of this directory.

  15. Extracting the distribution sets

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

    Before extraction begins, you can elect to watch the files being extracted; the name of each file that is extracted will be shown. This can slow down the installation process considerably, especially on machines with slow graphics consoles or serial consoles.

    After all the files have been extracted, all the necessary device node files will be created. If you have already configured networking, you will be asked if you want to use this configuration for normal operation. If so, these values will be installed in the network configuration files. The next menu will allow you to select the time zone that you're in, to make sure your clock has the right offset from GMT. Finally you can set a password for the "root" account, to prevent the machine coming up without access restrictions.

  16. Finalizing your installation

    Congratulations, you have successfully installed NetBSD1.5. You can now reboot the machine, and boot NetBSD from harddisk.


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, 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-write. When the system asks you to choose a shell, simply press RETURN to get to a prompt. If you are asked for a terminal type, respond with the correct terminal type as discussed in the Once you've booted the diskimage section. and press RETURN. At this point, you need to configure at least one file in the /etc directory. 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=termtype

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


           ifconfig_le0="inet 123.45.67.89 netmask 255.255.255.0"

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


           ifconfig_le0="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. There is no initial password, but 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

    • Edit /etc/mail/aliases to forward root mail to the right place (run newaliases(1) afterwards.)

    • The /etc/mail/sendmail.cf file will almost definitely need to be adjusted; files aiding in this can be found in /usr/share/sendmail. See the README file there for more information.

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

    • Many of the /etc files are documented in section 5 of the manual; so just invoking


             # man 5 filename

      is likely to give you more information on these files.


Upgrading a previously-installed NetBSD System

The upgrade to NetBSD1.5 is a binary upgrade; it can be quite difficult to advance to a later version by recompiling from source due primarily to interdependencies in the various components.

To do the upgrade, you must install new bootblocks and boot off the install kernel as described in the Installing from an existing system section. You must also have at least the base and kern binary distribution sets available, so that you can upgrade with them, using one of the upgrade methods described above. Finally, you must have sufficient disk space available to install the new binaries. Since the old binaries are being overwritten in place, you only need space for the new binaries, which weren't previously on the system. 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 boot blocks on your NetBSD partition, the kernel, 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 your disk, whether on the NetBSD partition or on another operating system's partition, before beginning the upgrade process.

The upgrade procedure using the sysinst tool is similar to an installation, but without the hard disk partitioning. Another difference is that existing configuration files in /etc are backed up and merged with the new files. Getting the binary sets is done in the same manner as the installation procedure; refer to the installation part of the document for how to do this. Also, some sanity checks are done, i.e. file systems are checked before unpacking the sets.

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

You must also deal with certain changes in the formats of some of the configuration files. The most notable change is that the options given to many of the file systems in /etc/fstab have changed, and some of the file systems have changed names. To find out what the new options are, it's suggested that you read the manual page for the file system's mount commands, for example mount_nfs(8) for NFS.

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

General issues

  • /etc/rc modified to use /etc/rc.d/*

    In previous releases of NetBSD, /etc/rc was a traditional BSD style monolithic file. As of NetBSD1.5, each discrete program or substem from /etc/rc and /etc/netstart has been moved into separate scripts in /etc/rc.d/.

    At system startup, /etc/rc uses rcorder(8) to build a dependency list of the files in /etc/rc.d and then executes each script in turn with an argument of `start'. Many rc.d scripts won't start unless the appropriate rc.conf(5) entry in /etc/rc.conf is set to `YES.'

    At system shutdown, /etc/rc.shutdown uses rcorder(8) to build a dependency list of the files in /etc/rc.d that have a ``KEYWORD: shutdown'' line, reverses the resulting list, and then executes each script in turn with an argument of `stop'. The following scripts support a specific shutdown method: cron, inetd, local, and xdm.

    Local and third-party scripts may be installed into /etc/rc.d as necessary. Refer to the other scripts in that directory and rc(8) for more information on implementing rc.d scripts.

Issues affecting an upgrading from NetBSD 1.4 or later

  • named(8) leaks version information

    Previous releases of NetBSD disabled a feature of named(8) where the version number of the server could be determined by remote clients. This feature has not been disabled in NetBSD1.5, because there is a named.conf(5) option to change the version string:

    option {
         version "newstring";
    };
    

  • sysctl(8) pathname changed

    sysctl(8) is moved from /usr/sbin/sysctl to /sbin/sysctl. If you have hardcoded references to the full pathname (in shell scripts, for example) please be sure to update those.

  • sendmail(8) configuration file pathname changed

    Due to sendmail(8) upgrade from 8.9.x to 8.10.x, /etc/sendmail.cf is moved to /etc/mail/sendmail.cf. Also, the default sendmail.cf(5) refers different pathnames than before. For example, /etc/aliases is now located at /etc/mail/aliases, /etc/sendmail.cw is now called /etc/mail/local-host-names, and so forth. If you have customized sendmail.cf(5) and friends, you will need to move the files to the new locations. See /usr/share/sendmail/README for more information.

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

  • intro(1),
  • man(1),
  • apropros(1),
  • passwd(1), and
  • passwd(5).

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 [email protected]. 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: [email protected].

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: [email protected].

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: [email protected].

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

  • The former members of UCB's Computer Systems Research Group, including (but not limited to):
    Keith Bostic
    Ralph Campbell
    Mike Karels
    Marshall Kirk McKusick
    

    for their ongoing work on BSD systems, support, and encouragement.

  • Also, our thanks go to:
    Mike Hibler
    Rick Macklem
    Jan-Simon Pendry
    Chris Torek
    

    for answering lots of questions, fixing bugs, and doing the various work they've done.

  • UC Berkeley's Experimental Computing Facility provided a home for sun-lamp in the past, people to look after it, and a sense of humor. Rob Robertson, too, has added his unique sense of humor to things, and for a long time provided the primary FTP site for NetBSD.

  • Vixie Enterprises for hosting the NetBSD FTP, SUP, and WWW servers.

  • Redback Networks, Inc. for hosting the NetBSD mail and GNATS server.

  • The Helsinki University of Technology in Finland for hosting the NetBSD CVS server.

  • The Internet Research Institute in Japan for hosting the server which runs the CVSweb interface to the NetBSD source tree.

  • The many organisations that provide NetBSD mirror sites.

  • Without CVS, this project would be impossible to manage, so our hats go off to Brian Berliner, Jeff Polk, and the various other people who've had a hand in making CVS a useful tool.

  • Dave Burgess [email protected] has been maintaining the 386BSD/NetBSD/FreeBSD FAQ for quite some time, and deserves to be recognized for it.

  • The following individuals and organizations (each in alphabetical order) have made donations or loans of hardware and/or money, to support NetBSD development, and deserve credit for it:

    Steve Allen
    Jason Birnschein
    Mason Loring Bliss
    Jason Brazile
    Mark Brinicombe
    David Brownlee
    Simon Burge
    Dave Burgess
    Ralph Campbell
    Brian Carlstrom
    James Chacon
    Bill Coldwell
    Charles Conn
    Tom Coulter
    Charles D. Cranor
    Christopher G. Demetriou
    Scott Ellis
    Hubert Feyrer
    Castor Fu
    Greg Gingerich
    William Gnadt
    Michael Graff
    Guenther Grau
    Ross Harvey
    Charles M. Hannum
    Michael L. Hitch
    Kenneth Alan Hornstein
    Jordan K. Hubbard
    S�ren J�rvang
    Scott Kaplan
    Noah M. Keiserman
    Harald Koerfgen
    John Kohl
    Chris Legrow
    Ted Lemon
    Norman R. McBride
    Neil J. McRae
    Perry E. Metzger
    Toru Nishimura
    Herb Peyerl
    Mike Price
    Dave Rand
    Michael Richardson
    Heiko W. Rupp
    Brad Salai
    Chuck Silvers
    Thor Lancelot Simon
    Bill Sommerfeld
    Paul Southworth
    Eric and Rosemary Spahr
    Ted Spradley
    Kimmo Suominen
    Jason R. Thorpe
    Steve Wadlow
    Krister Walfridsson
    Jim Wise
    Christos Zoulas
    

    AboveNet Communications, Inc.
    Advanced System Products, Inc.
    Avalon Computer Systems
    Bay Area Internet Solutions
    Brains Corporation, Japan
    Canada Connect Corporation
    Co-operative Research Centre for Enterprise Distributed Systems Technology
    Demon Internet, UK
    Digital Equipment Corporation
    Distributed Processing Technology
    Easynet, UK
    Free Hardware Foundation
    Innovation Development Enterprises of America
    Internet Software Consortium
    MS Macro System GmbH, Germany
    Numerical Aerospace Simulation Facility, NASA Ames Research Center
    Piermont Information Systems Inc.
    Salient Systems Inc.
    VMC Harald Frank, Germany
    Warped Communications, Inc.
    Whitecross Database Systems Ltd.
    
    (If you're not on that list and should be, tell us! We probably were not able to get in touch with you, to verify that you wanted to be listed.)

  • Finally, we thank all of the people who've put sweat and tears into developing NetBSD since its inception in January, 1993. (Obviously, there are a lot more people who deserve thanks here. If you're one of them, and would like to mentioned, tell us!)

We are...

(in alphabetical order)


The NetBSD core group:
Alistair Crooks[email protected]
Jun-ichiro itojun Hagino[email protected]
Frank van der Linden[email protected]
Luke Mewburn[email protected]
Christos Zoulas[email protected]

The portmasters (and their ports):
Mark Brinicombe[email protected] arm32
Jeremy Cooper[email protected] sun3x
Ross Harvey[email protected] alpha
Jun-ichiro itojun Hagino[email protected] sh3
Ben Harris[email protected] arm26
Eduardo Horvath[email protected] sparc64
Darrin Jewell[email protected] next68k
S�ren J�rvang[email protected] cobalt
S�ren J�rvang[email protected] sgimips
Wayne Knowles[email protected] mipsco
Paul Kranenburg[email protected] sparc
Anders Magnusson[email protected] vax
Minoura Makoto[email protected] x68k
Phil Nelson[email protected] pc532
Tohru Nishimura[email protected] luna68k
NONAKA Kimihiro[email protected] prep
Scott Reynolds[email protected] mac68k
Kazuki Sakamoto[email protected] bebox
Noriyuki Soda[email protected] arc
Wolfgang Solfrank[email protected] ofppc
Ignatios Souvatzis[email protected] amiga
Jonathan Stone[email protected] pmax
Shin Takemura[email protected] hpcmips
Jason Thorpe[email protected] alpha
Jason Thorpe[email protected] hp300
Tsubai Masanari[email protected] macppc
Tsubai Masanari[email protected] newsmips
Izumi Tsutsui[email protected] news68k
Frank van der Linden[email protected] i386
Leo Weppelman[email protected] atari
Nathan Williams[email protected] sun3
Steve Woodford[email protected] mvme68k

The NetBSD 1.5 Release Engineering team:
Chris G. Demetriou[email protected]
Havard Eidnes[email protected]
Ted Lemon[email protected]
John Hawkinson[email protected]
Perry Metzger[email protected]
Curt Sampson[email protected]
Jason Thorpe[email protected]
Todd Vierling[email protected]

Developers and other contributors:
Steve Allen[email protected]
Julian Assange[email protected]
Lennart Augustsson[email protected]
Christoph Badura[email protected]
Robert V. Baron[email protected]
Erik Berls[email protected]
John Birrell[email protected]
Mason Loring Bliss[email protected]
Manuel Bouyer[email protected]
John Brezak[email protected]
Allen Briggs[email protected]
Aaron Brown[email protected]
David Brownlee[email protected]
Frederick Bruckman[email protected]
Jon Buller[email protected]
Simon Burge[email protected]
Dave Burgess[email protected]
Robert Byrnes[email protected]
D'Arcy J.M. Cain[email protected]
Dave Carrel[email protected]
James Chacon[email protected]
Bill Coldwell[email protected]
Julian Coleman[email protected]
Chuck Cranor[email protected]
Aidan Cully[email protected]
Johan Danielsson[email protected]
Matt DeBergalis[email protected]
Rob Deker[email protected]
Chris G. Demetriou[email protected]
Jaromir Dolecek[email protected]
Andy Doran[email protected]
Roland Dowdeswell[email protected]
Matthias Drochner[email protected]
Jun Ebihara[email protected]
Havard Eidnes[email protected]
Enami Tsugutomo[email protected]
Bernd Ernesti[email protected]
Erik Fair[email protected]
Hubert Feyrer[email protected]
Thorsten Frueauf[email protected]
Castor Fu[email protected]
Ichiro Fukuhara[email protected]
Brian R. Gaeke[email protected]
Thomas Gerner[email protected]
Simon J. Gerraty[email protected]
Justin Gibbs[email protected]
Adam Glass[email protected]
Michael Graff[email protected]
Brad Grantham[email protected]
Brian C. Grayson[email protected]
Matthew Green[email protected]
Juergen Hannken-Illjes[email protected]
Charles M. Hannum[email protected]
Eric Haszlakiewicz[email protected]
John Hawkinson[email protected]
HAYAKAWA Koichi[email protected]
Ren� Hexel[email protected]
Michael L. Hitch[email protected]
Christian E. Hopps[email protected]
Ken Hornstein[email protected]
Marc Horowitz[email protected]
Nick Hudson[email protected]
Martin Husemann[email protected]
Dean Huxley[email protected]
Bernardo Innocenti[email protected]
ITOH Yasufumi[email protected]
IWAMOTO Toshihiro[email protected]
Matthew Jacob[email protected]
Lonhyn T. Jasinskyj[email protected]
Chris Jones[email protected]
Takahiro Kambe[email protected]
Antti Kantee[email protected]
Lawrence Kesteloot[email protected]
Thomas Klausner[email protected]
Klaus Klein[email protected]
Wayne Knowles[email protected]
John Kohl[email protected]
Kevin Lahey[email protected]
Johnny C. Lam[email protected]
Martin J. Laubach[email protected]
Ted Lemon[email protected]
Joel Lindholm[email protected]
Mike Long[email protected]
Warner Losh[email protected]
Federico Lupi[email protected]
Brett Lymn[email protected]
Paul Mackerras[email protected]
David Maxwell[email protected]
Dan McMahill[email protected]
Gregory McGarry[email protected]
Neil J. McRae[email protected]
Perry Metzger[email protected]
der Mouse[email protected]
Joseph Myers[email protected]
Ken Nakata[email protected]
Bob Nestor[email protected]
NONAKA Kimihiro[email protected]
Masaru Oki[email protected]
Atsushi Onoe[email protected]
Greg Oster[email protected]
Herb Peyerl[email protected]
Matthias Pfaller[email protected]
Dante Profeta[email protected]
Chris Provenzano[email protected]
Waldi Ravens[email protected]
Darren Reed[email protected]
Michael Richardson[email protected]
Tim Rightnour[email protected]
Gordon Ross[email protected]
Heiko W. Rupp[email protected]
SAITOH Masanobu[email protected]
Curt Sampson[email protected]
Wilfredo Sanchez[email protected]
Ty Sarna[email protected]
SATO Kazumi[email protected]
Matthias Scheler[email protected]
Karl Schilke (rAT)[email protected]
Konrad Schroder[email protected]
Reed Shadgett[email protected]
Tim Shepard[email protected]
Takao Shinohara[email protected]
Takuya SHIOZAKI[email protected]
Chuck Silvers[email protected]
Thor Lancelot Simon[email protected]
Jeff Smith[email protected]
Bill Sommerfeld[email protected]
Bill Squier[email protected]
Bill Studenmund[email protected]
Kevin Sullivan[email protected]
SUNAGAWA Keiki[email protected]
Kimmo Suominen[email protected]
Matt Thomas[email protected]
Christoph Toshok[email protected]
UCHIYAMA Yasushi[email protected]
Shuichiro URATA[email protected]
Todd Vierling[email protected]
Aymeric Vincent[email protected]
Paul Vixie[email protected]
Krister Walfridsson[email protected]
Lex Wennmacher[email protected]
Assar Westerlund[email protected]
Todd Whitesel[email protected]
Rob Windsor[email protected]
Dan Winship[email protected]
Jim Wise[email protected]
Michael Wolfson[email protected]
Colin Wood[email protected]

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.

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 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 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 ([email protected]).

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

This product includes software contributed to Berkeley by Ralph Campbell.

This product includes software contributed to Berkeley by Ralph Campbell and Rick Macklem.

This product includes software contributed to Berkeley by Van Jacobson of Lawrence Berkeley Laboratory and Ralph Campbell.

This product includes software developed by Chris G. Demetriou, and Jonathan Stone.

This product includes software developed by Keith Bostic, Chris G. Demetriou, and Jonathan Stone.

This product includes software developed by the University of California, Lawrence Berkeley Laboratory.

This product includes software developed by Jonathan Stone for the NetBSD Project.

This product includes software developed by Tohru Nishimura for the NetBSD Project.

Some files have the following copyright:

Mach Operating System
Copyright (c) 1991,1990,1989 Carnegie Mellon University
All Rights Reserved.

Permission to use, copy, modify and distribute this software and its documentation is hereby granted, provided that both the copyright notice and this permission notice appear in all copies of the software, derivative works or modified versions, and any portions thereof, and that both notices appear in supporting documentation.

CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN ITS CONDITION. CARNEGIE MELLON DISCLAIMS ANY LIABILITY OF ANY KIND FOR ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.

Carnegie Mellon requests users of this software to return to

Software Distribution Coordinator or [email protected]
School of Computer Science
Carnegie Mellon University
Pittsburgh PA 15213-3890

any improvements or extensions that they make and grant Carnegie the rights to redistribute these changes.

Some files have the following copyright:

Copyright (c) 1994, 1995 Carnegie-Mellon University.
All rights reserved.

Author: Chris G. Demetriou

Permission to use, copy, modify and distribute this software and its documentation is hereby granted, provided that both the copyright notice and this permission notice appear in all copies of the software, derivative works or modified versions, and any portions thereof, and that both notices appear in supporting documentation.

CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN ITS "AS IS" CONDITION. CARNEGIE MELLON DISCLAIMS ANY LIABILITY OF ANY KIND FOR ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.

Carnegie Mellon requests users of this software to return to

Software Distribution Coordinator or [email protected]
School of Computer Science
Carnegie Mellon University
Pittsburgh PA 15213-3890

any improvements or extensions that they make and grant Carnegie the rights to redistribute these changes.

Some files have the following copyright:

Copyright (C) 1989 Digital Equipment Corporation.
Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies. Digital Equipment Corporation makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.

Some files have the following copyright:

Copyright 1987 by Digital Equipment Corporation, Maynard, Massachusetts, and the Massachusetts Institute of Technology, Cambridge, Massachusetts.

All Rights Reserved

Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the names of Digital or MIT not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission.

DIGITAL DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL DIGITAL BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

Some files have the following copyright:

Copyright 1996 The Board of Trustees of The Leland Stanford Junior University. All Rights Reserved.

Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies. Stanford University makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.